Related
Several days ago, my Verizon Galaxy Nexus began showing an "R" in the signal area, and "Roaming" in the pulldown. Sure enough, it shows that I'm roaming in the about phone information.
The strange thing is that I'm still getting 4G speeds, but my phone is no longer seeing 3G at all, and any time I make a phone call it goes from "R" to 4G.
I cannot dial any Verizon short codes as it tells me they are not valid.
I was on Liquid ROM with 4.0.4 radios when I noticed the issue, and switched to the 4.0.2 radios but the issue persists. I'm currently running CM9 and can't seem to fix it.
Verizon tech support was clueless too. I've verified with my wife's Galaxy Nexus that this isn't a specific issue with our tower, and my sim works great in her phone without issues.
Anyone seen this before?
What happens if you return to stock?
I'm doing that now
Flashed back to stock 4.0.2, same issue persists.
Anyone else have any suggestions?
I am having the same issue, did you find a resolution?
Verizon GNEX
Rom: ParanoidAndroid 1.4
Kernel: Lean Kernel 3.10.0
I have the same problem, but mine maybe a bit different.
I am stuck on "R" here, but I was roaming for 2 weeks in Canada. I am a crack flasher and I flashed JellyBean while in Canada so I am thinking I am provisioned for roaming there? I am downloading a new rom to flash here back in the USA on Verizon, hoping to fix the problem. I cannot access my dialer in JellyBean after I *228, so I cannot hit 1 to provision.
SoI will do a SuperWipe and flash will hopefully do the trick. If anyone figures out what to do please update
I ended up having to do an exchange on mine :-(
damn, that is gonna be lame if that is the case. I bought mine at BestBuy, so I have to do their Rapid Exchange program. Glad I purchased the warranty while I worked there
oc3rulz said:
damn, that is gonna be lame if that is the case. I bought mine at BestBuy, so I have to do their Rapid Exchange program. Glad I purchased the warranty while I worked there
Click to expand...
Click to collapse
Shouldn't really matter where you bought it. It's still under the manufacturers warranty so Verizon should take care of it unless I'm mistaken.
URPREY said:
Shouldn't really matter where you bought it. It's still under the manufacturers warranty so Verizon should take care of it unless I'm mistaken.
Click to expand...
Click to collapse
Verizon will take care of it if it is still under the manufactures warranty, just don't tell them where you bought it (they won't ask). I got mine from Wire Fly, and had to get it replaced due to faulty hardware, they sent it no questions asked.
thanks for the info guys!
Wanted to let you know my problem did indeed go away after I reflashed Slim Bean Alpha 4 here in the USA. I was roaming when I flashed JB, so I guess it picked up their provisions.
did you turn it off, pull the sim card.. wait 1min, then put the sim back in and start it up
Zep, I tried everything originally to make this thing work correctly. nothing helped every time to phone booted it went straight to R and never moved!
HOWEVER I do believe I have found the culprit!!! So everything worked beautifully all yesterday, no problems at all. This morning I decided that I would change the T-CDMA 64 on the bottom back to Verizon Wireless, well guess what. The second I added the "eri.xml" file to /data and reboot, I STARTED ROAMING!!!!
I went to root explorer and deleted the /data/eri.xml file and rebooted! VIOLA I have 4G back and it's not switching over!! So something is causing that eri.xml file to freak my phone and most likely others phones out!
oc3rulz said:
Zep, I tried everything originally to make this thing work correctly. nothing helped every time to phone booted it went straight to R and never moved!
HOWEVER I do believe I have found the culprit!!! So everything worked beautifully all yesterday, no problems at all. This morning I decided that I would change the T-CDMA 64 on the bottom back to Verizon Wireless, well guess what. The second I added the "eri.xml" file to /data and reboot, I STARTED ROAMING!!!!
I went to root explorer and deleted the /data/eri.xml file and rebooted! VIOLA I have 4G back and it's not switching over!! So something is causing that eri.xml file to freak my phone and most likely others phones out!
Click to expand...
Click to collapse
Glad that worked for you. I tried everything including a complete wipe and mine was still roaming even after reflashing the stock ROM.
Hi and thanks for any help that you can provide me.
I bought an Galaxy Note 2 SGH-T889 Tmobile version like 7 months ago from a store or reseller in Toronto Canada, the phone was in theory factory unlock, to use with the Wnmobile network which uses the same frequency as Tmobile. The phone was working until 2 days ago. Well always the phone has issue connecting to the network in some specific areas, specially because the Wind network it's not that good, but during the last 2 weeks I noticed more and more problems and some times it was just disconnected showing a circle with an slash or crossed out. After reboot the phone usually fixed the problem, until 2 days ago I had to do it every 2 hours and then the next day it just was permanent. I tried everything so far:
Remove battery and reboot
Remove battery and SIM card and reboot
Use a diiferent SIM card from my son's phone
Replace for a new SIM card
Clear Cache
Factory Reset
Reflash the modem with Odin
The phone has the latest stock ROM 4.1.2, BASE T889UVBMD1
The problem is Samsung say because it's a Tmobile they can not support it here, I have to send the phone to Samsung USA, I still fighting with the store because they said it will be covered locally, but that is another story.
I red many post talking about similar problems with the Galaxy S3 or S4 and one said that installing Jedi X14 fixed the problem, but to do that I think I have to root the phone, which not be a big problem.
The other weird thing is the phone works using other SIM card GSM, not tested with a LTE SIM.
There is any way to test if the radio/antenna for the WCMDA is disabled or broken
Thanks
fasterfoxy said:
Hi and thanks for any help that you can provide me.
I bought an Galaxy Note 2 SGH-T889 Tmobile version like 7 months ago from a store or reseller in Toronto Canada, the phone was in theory factory unlock, to use with the Wnmobile network which uses the same frequency as Tmobile. The phone was working until 2 days ago. Well always the phone has issue connecting to the network in some specific areas, specially because the Wind network it's not that good, but during the last 2 weeks I noticed more and more problems and some times it was just disconnected showing a circle with an slash or crossed out. After reboot the phone usually fixed the problem, until 2 days ago I had to do it every 2 hours and then the next day it just was permanent. I tried everything so far:
Remove battery and reboot
Remove battery and SIM card and reboot
Use a diiferent SIM card from my son's phone
Replace for a new SIM card
Clear Cache
Factory Reset
Reflash the modem with Odin
The phone has the latest stock ROM 4.1.2, BASE T889UVBMD1
The problem is Samsung say because it's a Tmobile they can not support it here, I have to send the phone to Samsung USA, I still fighting with the store because they said it will be covered locally, but that is another story.
I red many post talking about similar problems with the Galaxy S3 or S4 and one said that installing Jedi X14 fixed the problem, but to do that I think I have to root the phone, which not be a big problem.
The other weird thing is the phone works using other SIM card GSM, not tested with a LTE SIM.
There is any way to test if the radio/antenna for the WCMDA is disabled or broken
Thanks
Click to expand...
Click to collapse
If the phone is working fine with a friends sim card . There is nothing more then a issue with your sim. go to the store and have them to give you a new sim card or flash the one you have. I had that issue similar here with at&t all the time.. sims would just loose network.. The fix for me LEAVE AT&T
Good luck.
Yes, I replaced the SIM card and I got a new one.
Just trying to eliminate all the options, I just did a factory reset again, and put it back the SIM card, located outside in an area where I know there is a strong signal and the phone was able to connect to the network and I install the account ans the apps just to test the data connection and it works fine. I was outside for 20 minutes with no problem. Later go back in the building, as soon I was inside for a few minutes the phone lose connection and the circle is back, then reboot again several times, and the phone does not recognize any network, Searching and no network is available.
Aww you left out that it only does this inside but works outside.. I Would say something is blocking the signal. LIKE maybe the building..
i have two bars in my house 3 on the deck and full signal in my yard ...
its just how it is..
erica_renee said:
Aww you left out that it only does this inside but works outside.. I Would say something is blocking the signal. LIKE maybe the building..
i have two bars in my house 3 on the deck and full signal in my yard ...
its just how it is..
Click to expand...
Click to collapse
But he said it was working in side for many month then all a sudden it doesn't work? I understand I live in a mobile home and reception sucks but that from the start but his was working for couple months. I would say he's phone reception receiver w/e it is or something in the phone is screwing up and it will need repairment or replace or service just taking a dump and getting worse.
jcervantes11 said:
But he said it was working in side for many month then all a sudden it doesn't work? I understand I live in a mobile home and reception sucks but that from the start but his was working for couple months. I would say he's phone reception receiver w/e it is or something in the phone is screwing up and it will need repairment or replace or service just taking a dump and getting worse.
Click to expand...
Click to collapse
You could be right.. or maybe even the provider having issues with that tower .. its a tough thing to figure out..
Thanks for your ideas.
I get tired of trying to figure out was is the problem, so I got a SIM card from a diiferent provider which has the best network coverage and power, and i'ts happending the same, the majority of th etime the strength level is around -110 db even outside, with both providers, so it's the phone.
Now the question is could be possible that the antenna cable got disconnected or broken, (yes I dropped the phone a few times but nothing major) and it was working fine until few days ago. Another option it's some internal hardware is not working normally.
Now I have to find a way to repair becasue Samsung Canada does not want to do it becasue its a Tmobile phone.
Thanks, again.
fasterfoxy said:
Thanks for your ideas.
I get tired of trying to figure out was is the problem, so I got a SIM card from a diiferent provider which has the best network coverage and power, and i'ts happending the same, the majority of th etime the strength level is around -110 db even outside, with both providers, so it's the phone.
Now the question is could be possible that the antenna cable got disconnected or broken, (yes I dropped the phone a few times but nothing major) and it was working fine until few days ago. Another option it's some internal hardware is not working normally.
Now I have to find a way to repair becasue Samsung Canada does not want to do it becasue its a Tmobile phone.
Thanks, again.
Click to expand...
Click to collapse
Anybody with same provider as you? Invite them in you're home see if they have connection. It's best if the person have same phone and same company. Can you send directly to Samsung? I have bad phone service my area with s2 and note 2 but my friend with evo 3d has more bar then me and its made by htc but could be two things ur phone crapping out on you which need repairment or like the guy above said tower signal getting weaker. It is hard to find out. Maybe for now for a bit since it's screw up try a rom but then again rom doesn't control radio settings section but wouldn't harm. Good luck.
I'm having the same issue since last month... but with any SIM card.
The network signal strengh rests between -89 to -110 dBm. (Horrible)
The network type is always UNKNOWN:0.
What I already tried:
- Using other SIM.
- Flashing Stock ROM
- Flashing Custom ROM (CM 10.1)
- Flashing all 5 avaliable modems.
What happens:
When I get VERY close to a network antenna... I can make calls and stuff...
What can be happening:
Hardware issues - T-Mobile latest LTE unlocking update maybe burned my antenna (or some network signal related hardware).
Software issues - Can't see how since I used many variations of ROM/Modem.
I live in Brazil and my network is TIM 47. I have a Samsung Galaxy Note II T889.
If anyone can confirm perfectly to me what composes the T889 antenna components... that would be nice...
I want to buy those parts from eBay and trying fixing my phone.
Thanks for your feedback it's really valuable becasue it's almost the same situation. Today I cleared up the situation with Samsung, if I want to be service under the warranty I have to bring the phone to one of repair centres in USA which it's kind of problem because I can do it only in the weekends but not impossible or what I'm doing tomorrow is to have an assessment by one of the repair centres in Toronto and I have to pay in this case, if it's something reasonable.
In my case I did not update the phone in 2 months at least so it's not software in my case, but one difference could be I got a new job 3 months ago, in my previous job the majority of the time I got 5 bars , I guess the cell tower was close to that place, and in my house the coverage it's good. In my new job, my office it's in the middle of the building, far from the windows, so the signal always was really bad, 0-1 bar.
Wondering if could be possible that a bad connection can burn the antenna or the circuit that controls the connection.
The other thing is there are many customers specially for the Galay S4 complaining about a similar problem, and I did not find any answer on how to fix this problem.
I'll post any update just in case it can help someone else.
Thanks.
Did you try to disable lte and use 4g/3g/2g only?
Sent from my SGH-T889 using xda app-developers app
darekz said:
Did you try to disable lte and use 4g/3g/2g only?
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Well... I did... and the problem persists.
Try to enable and disable wifi calling.
Sent from my SGH-T889 using xda app-developers app
A also have this problem with T-Mobile Note 2 and have already tried everything you guys have...I guess I got no choice but to request a replacement which sucks because my phone was pristine and worked perfectly otherwise. It's just the damn weak to no signal that's driving me crazy. Especially since I'm paying for premium data coverage and it's pretty much money in the trash every month.
That's it. I made the call and the replacement arrives in a couple days. They offered me the "jump" program. Anyone on that? Is that worth doing on T-Mobile?
I traded an unlocked i317m for a g pro. I just picked up a unlocked t889 as welll. The person with my old i317m want my t889 since hes using simple mobile. Problem is when I went to trade I put his sim in my t899 it wont register on tmobile. Seems its only working with at&t as thats the service I have. Now with the i317m I gave him originally it works with any sim. How is this possible that a unlocked tmobile t889 wont register with his sim on tmobile network but the unlocked i317m works with any sim?
Yesterday I replaced the microUSB module that is connected with the antenna and replaced the SIM card module too.
That did NOT worked.
So... the problems is problably on the mainboard/chipset... too expensive to fix.
Another big hardware failure for Samsung's history.
I've had the replacement for about a week now. So far no signal problems. It's like when I first got my original phone. I'm sticking with the note 2 for at least another 6 months since I joined the jump program. Can't wait to see the note 3 next week
Update just to close this case
Well, after I sent the phone for repair to Samsung USA, I got it back and the problems happened again after a few days, then I sent it back for the second time to Samsung, got it back and the problem happened again after a few weeks. Basically, I'm getting rid of this phone, now the warranty is already expired and half of the time the phone was full of problems with the network.
The lesson in this case is to avoid getting hardware from the first batch (to wait a few months after the launch) or without a long term warranty (3 years), and probably will be my last Samsung device.
:crying:
Diesel-30 said:
Can't wait to see the note 3 next week
Click to expand...
Click to collapse
You mean Note 4, no?
I just got my G3 and left the country. Voice and SMS work fine, but I can't get a data connetion while out of the country. It didn't work in either the UK or India.
I'm guessing there's some sort of APN issue and I have a call into TMO tech support. The original call was to do #RON#, but that didn't help.
When I swap my SIM to my trusty Nexus 5, data works, so it's something device specific.
I've read about needing to force IPv4 when roaming and I tried creating a new APN with only that changed. One thing I noticed that's different between my N5 and G3 is there is no APN setting for Roaming Protocol.
Any ideas?
Thanks!
did you enable roaming in the settings?
amosconf said:
did you enable roaming in the settings?
Click to expand...
Click to collapse
Yes. One interesting thing is that the data roaming setting seems to reset on every reboot.
I have the exact same problem. Lg g3 t mobile, been to Germany twice in last two weeks and no data. All settings on phone are correct. After many phone calls with tech support, found someone who said they seem to have growing pains with new devices and the more they get feedback and realize there is a phone specific problem they can go to lg . Very frustrating but hopefully gets ironed out soon. I also came from a nexus 5.
That's not too encouraging. I was hoping that I'd have data sometime on this trip so I can actually use my new phone! Since it's new and still in my return window, I'd like a solution before I go home to decide if I should return the phone. I travel internationally a lot and it's one of the reasons I shifted to T-mobile from AT&T.
Tech support has told me they will have some sort of reply within 72 hours so hopefully I'll head something by end of day Wednesday.
jrglasson said:
That's not too encouraging. I was hoping that I'd have data sometime on this trip so I can actually use my new phone! Since it's new and still in my return window, I'd like a solution before I go home to decide if I should return the phone. I travel internationally a lot and it's one of the reasons I shifted to T-mobile from AT&T.
Tech support has told me they will have some sort of reply within 72 hours so hopefully I'll head something by end of day Wednesday.
Click to expand...
Click to collapse
I agree totally !!! Unfortunately we are early adopters of this phone. Tech support told me flat out that it will not be fixed for me while on my trip. I travel internationally for work and not being able to use data for google navigation and train schedule apps has been very upsetting. I will post something here as soon as they get back to me as well.
I've been trying to troubleshoot the tethering and found some interesting things. Looks like in an effort to avoid people enabling tethering without using the pcweb apn, they have broken the international roaming.
I think the problem is that you cannot use an ipv4 only APN. I added a new APN which was an exact copy of the built in one (which you cannot edit) and if I change it to ipv4 only, I get no data (in the US). Data only works when setting it to ipv6 or ipv4/ipv6. I haven't tried to debug this, but I think this could be the problem since when roaming internationally I doubt ipv6 is supported.
I also travel often to Mexico, so this is a big drawback.
Same issue in Canada
I just spent about an hour on the phone with Tech Support. Very friendly, but alas, I have the same issue. A ticket was entered, and she said she would get back to me today. If the LG G3 can't go International, my local T-Mobile store is about to get my returned handset. I'll try something else, I suppose. Glad I found this out within the first week of having it, what with the 10 day return policy.
Of note, the tech support person mentioned to me that I had to create an IPv4 APN (otherwise identical to the existing fast.t-mobile.com APN, which is IPv6).
I also tried selecting IPv4/IPv6, but that didn't work either. Neither GSM nor WCDMA works.
My co-worker here is happily connected on his Samsung Note 3. Frustrating to have a newer phone with a better processor, just to have my boasting neutralized by no roaming. :crying:
If I get a resolution, other than returning home or getting a new phone, I'll post it.
I really hope this isn't the case. I'm deployed overseas right now and get service just fine on my N5. If I can't get data with my G3 when it gets here in a few days, I'm going to be pissed.
Thanks for all the ideas. It's nice to know that I'm not alone in this.
I still haven't heard back from T-mobile and it's at 72 hourse since I reported the issue. I'm on another flight tomorrow to the UK, so if I don't hear anything by the time I land, I'm going to give them another call.
If they can't get this to work or at least give me a timeline for resolution, I think I'm returning the phone and will wait for the N6 (if one exists). Hopefully I can get them to waive the $50 restocking on return since I'm returning it for not working reasons.
jrglasson said:
Thanks for all the ideas. It's nice to know that I'm not alone in this.
I still haven't heard back from T-mobile and it's at 72 hourse since I reported the issue. I'm on another flight tomorrow to the UK, so if I don't hear anything by the time I land, I'm going to give them another call.
If they can't get this to work or at least give me a timeline for resolution, I think I'm returning the phone and will wait for the N6 (if one exists). Hopefully I can get them to waive the $50 restocking on return since I'm returning it for not working reasons.
Click to expand...
Click to collapse
This is a pretty big bug, I can't believe no one tested this before launching the phone. I sold my N5 a day after I got the G3, so if I were to need my roaming while abroad I would be SOL too. Not sure if I want to return it yet, once we get a custom ROM I'm sure we'll be able to get around this.
If it were me, I'd trade out to a different phone before I left for the UK. Still within the 10 day return period, so there's no penalty, and so you have data abroad.
jrglasson said:
Thanks for all the ideas. It's nice to know that I'm not alone in this.
I still haven't heard back from T-mobile and it's at 72 hourse since I reported the issue. I'm on another flight tomorrow to the UK, so if I don't hear anything by the time I land, I'm going to give them another call.
If they can't get this to work or at least give me a timeline for resolution, I think I'm returning the phone and will wait for the N6 (if one exists). Hopefully I can get them to waive the $50 restocking on return since I'm returning it for not working reasons.
Click to expand...
Click to collapse
mattspammail said:
If it were me, I'd trade out to a different phone before I left for the UK. Still within the 10 day return period, so there's no penalty, and so you have data abroad.
Click to expand...
Click to collapse
I'm already in India, so it's not another trip. I'm home on Sunday evening, and Monday will still be within 10 day. I didn't really need a new phone, but what sold me on the G3 was the 3Gb of RAM and bigger battery. My N5 is sluggish and the battery doesn't last all day with all the software I have installed.
I wanted to post an update. I hadn't heard anything from TMO so I called them back to check on what's going on. I'm now in the UK and still have the problem (again). They really gave me the runaround this time saying that they needed to file a new ticket since my original ticket was filed for problems in India. They also told me that enginnering had responded that there were no roaming partners in India, which is just false. I kept mentioning that other people are having this issue in other countries and mt Nexus 5 worked just fine.
At the end of the call, they did file a new ticket and escalated to some other support team to resolve. I'm really not hopeful anything will happen before I return to the US. I told them I'm flying home on Sunday and that if I didn't have resolution, I would be returning the phone upon return.
If something happens in the next day (the timeframe I was told I would get a response), I'll post another update.
Guys use this apk offlune apn database
Sent from my GT-S5367 using xda app-developers app
musiklover said:
Guys use this apk offlune apn database
Sent from my GT-S5367 using xda app-developers app
Click to expand...
Click to collapse
That won't work for this issue. I have a TMO US SIM and my free international roaming isn't working. The phone is locked, so I can't get another SIM.
To all having this problem - I am having a similar, but different issue. I just purchased a brand new T-Mo USA G3 yesterday. I run it on a T-Mo MVNO (Roam Mobility) since I don't live in the US. Voice works fine, I can see I'm on the "Roam" LTE network (which is really just a T-Mo USA LTE network), but no data. Proper APN is inserted and the SIM gets LTE data in the same location on my Moto X.
In the meantime I unlocked the G3 fully, no change.
Finally tried changing the network to WCDMA / GSM only and...I have data.
No idea why T-Mobile is blocking LTE when not on T-Mo itself. Will try in Canada tomorrow but expecting same results as everyone else, but will be interesting to see if it runs on HSPA+.
I tried disabling LTE and creating a new APN with IPv4 and after about 15 minutes powered on, still no data. Then I tried WCDMA only and still no go.
Latest update:
Just got off the phone with support again. The engineering team came back saying this was a handset problem and there are no known issues. I just did a full reset under direction of the support guy and still nothing.
I'll be returning the phone next week when I return to the states.
The support guy also said he will be posting on the TMO message board for other people to post issues with roaming. When that comes up, please post so they understand this is a wide-spread issue.
Maybe I'll rebuy the phone after I know the issue is resolved or by then there might be something better...
Quick update - just arrived back in Canada, and pleasant surprise - full LTE data on Fido! Just had to manually add the APN.
As most of you know its an issue with phones with a serial of 505 and H/W Rev 1... Didn't know it would happen on Verizon or not... Well i can confirm it. Was browsing YouTube and it randomly froze. Now all it does it bootloop. Verizon was cool to deal with on the issue and didn't try to claim it wasn't a problem.
Surprised no one has asked or said anything...
That sucks. I got a 507 serial, so I hope I will be spared. But it will be difficult if you paid off the phone and are not associated with Verizon anymore. Then you have to mail the phone to LG, and I heard their repair service is pretty spotty.
Still under manufacturer warranty. I am thinking of buying out the phone and going to Googles project fi. Verizon is getting too expensive and big for their britches....
I have a 505 but I am still on he original firmware. I think it is the 10B. Is it the firmware version that causes the problems? I have delaying the update since I got the phone in November.
Sent from my VS986 using Tapatalk
wekurtz74 said:
I have a 505 but I am still on he original firmware. I think it is the 10B. Is it the firmware version that causes the problems? I have delaying the update since I got the phone in November.
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
100% sure the answer is no - firmware has nothing to do with it. I had a 505 since the day it was released and I was still running 10B too when the dreaded bootloop issue hit my device a couple of weeks ago. I know others who were running upgraded firmware on Verizon and they got the bootloop issue too.
Yup i got the issue of it bootlooping. I got my replacement every time i do alot of thi gs on my first g4 it will freaze and reboot then a bootloop for a bit
Happened to me in Thursday night. Got my replacement today. I was on rooted 13B on 505
dman1049 said:
Still under manufacturer warranty. I am thinking of buying out the phone and going to Googles project fi. Verizon is getting too expensive and big for their britches....
Click to expand...
Click to collapse
I have been kickin around the idea of switching to project FI also because Verizon is so damn expensive. But I still have my unlimited plan with Verizon, also I am concern with poor coverage.
I also just got mine back from warranty repair this weekend,
The coverage is a little less abundant than Verizon. I noticed I've used less data since going to project Fi. I don't feel like I need to get my moneys worth out of my plan every month.
My Verizon LG G4 505x/v1.0 hardware "pre-order" hit the bootloop issue today. It started with a random reboot while I was going to lunch, another reboot a minute later, then 30 seconds of straight vibrating, then... dead. I've gotten it to show a battery symbol when plugging it in since then, and now it does the same bootloop everyone has mentioned. I've started a replacement via Best Buy's Geek Squad, otherwise I have to mail the phone out to LG, wait for them to assess it, then send me one back. It's already 5-7 days because they're backlogged... which makes me wonder if tons of these have started failing or if stock is just low because the V10 came out a while back.
Does anyone know if Best Buy or Verizon can connect (JTAG method?) to the old phone and extract data from internal storage when it's stuck like this?
LG g4 verizon stuck in bootloop. Pretty much the same thing, I was using an app and it froze and now is stuck.
After a few phone calls Verizon is replacing the device. It was painful though. I had to play dumb and act like I was doing everything "tech" support asked me to do. Even though I already tried everything.
Now the question is with my phone being rooted will they still replace it. Ive had to do a warranty replacement a couple years back and didnt have a problem. Ill update everyone.
This happened to mine about a month ago. I don't know what the serial number was on it, but I got it at Launch. My wife's G4 started having this problem on Friday and her serial number starts with 506. VZW is shipping another.
eastmesawhat said:
LG g4 verizon stuck in bootloop. Pretty much the same thing, I was using an app and it froze and now is stuck.
After a few phone calls Verizon is replacing the device. It was painful though. I had to play dumb and act like I was doing everything "tech" support asked me to do. Even though I already tried everything.
Now the question is with my phone being rooted will they still replace it. Ive had to do a warranty replacement a couple years back and didnt have a problem. Ill update everyone.
Click to expand...
Click to collapse
I sent mine back, it was rooted so we'll see if Verizon charges.
Temporary fix that might work for you guys
I decided to see if I can get my data off my phone using any means necessary and I do mean any means necessary. I was able to get my data off my phone by baking the motherboard. I've included a crappy YouTube video that I made in order to show you that it does work. Hope this helps people out that want to get their data off the phone before they throw it away.
youtu.be/MPDVynnH0zg
Not sure if there's a thread already for this, feel free to delete. Anyone experienced loss of mobile network connectivity when you are not using wifi anymore? You will need to restart the phone in order to get the mobile network back.
I'm not sure what actually triggers it for me, but there have been 2 or 3 times in the past 2 weeks since I got my Note where mobile data is dead and restarting my phone is the only way to fix. Not sure what's going on. Hasn't happened in several days.
s1l3ntm0use said:
I'm not sure what actually triggers it for me, but there have been 2 or 3 times in the past 2 weeks since I got my Note where mobile data is dead and restarting my phone is the only way to fix. Not sure what's going on. Hasn't happened in several days.
Click to expand...
Click to collapse
It happens all the time when im out of range from a wifi and the phone wont switch to mobile network automatically.
My wife and I have both been experiencing the same problems with our Note 7.
No solution found for us except restarting phone. It seems to happen when the following occurs: (1) temporary initial loss of mobile signal, like from being in an elevator, combined with (2) not being connected to WiFi network. Fwiw, we are on T-mobile in a major market area. Previously had Note 5's with same carrier in same area for over a year without experiencing this issue.
Same thing here and a buddy of mine same thing on tmobile. Fringe areas wreak havoc on this damn thing. Lags...loses signal..etc. my s7 had MUCH STRONGER reception in the same areas this damn thing can barely keep a signal! Smh
**UPDATE**
I got around to calling T-Mobile today, and they said that this is now listed in their system as a known issue with the device. Rep I spoke with said he didn't really have much more information other than they've gotten enough reports of signal loss with the Note 7 to have it be flagged as a known issue.
According to the rep, the only known fix at the moment is rebooting the device. Obviously this is a pain in the ass if you have to reboot the phone every time you get on an elevator and lose signal.
Given the circumstances, this at least rules out it being a network carrier issue or an Android OS issue. The rep was not sure if the problem was related to hardware or software. If its software, it something that can be corrected; but if its hardware, then there really is no solution.
My plan is to deal with it for another 3-4 weeks and see how the Note 7 recall pans out, which should also provide a bit more time for them to figure out the cause of the signal loss problem. If it seems like it's not going to be fixed, then I'm just going to trade in the phone for something different. Fwiw, I asked if they had similar reports for the S7 or S7 Edge, and they said there were no system flags for this issue on those devices.
12345123456 said:
**UPDATE**
I got around to calling T-Mobile today, and they said that this is now listed in their system as a known issue with the device. Rep I spoke with said he didn't really have much more information other than they've gotten enough reports of signal loss with the Note 7 to have it be flagged as a known issue.
According to the rep, the only known fix at the moment is rebooting the device. Obviously this is a pain in the ass if you have to reboot the phone every time you get on an elevator and lose signal.
Given the circumstances, this at least rules out it being a network carrier issue or an Android OS issue. The rep was not sure if the problem was related to hardware or software. If its software, it something that can be corrected; but if its hardware, then there really is no solution.
My plan is to deal with it for another 3-4 weeks and see how the Note 7 recall pans out, which should also provide a bit more time for them to figure out the cause of the signal loss problem. If it seems like it's not going to be fixed, then I'm just going to trade in the phone for something different. Fwiw, I asked if they had similar reports for the S7 or S7 Edge, and they said there were no system flags for this issue on those devices.
Click to expand...
Click to collapse
Same boat here. I'll swap to the s7 if it's not sorted out. Happened 2 times support work already.
Sent from my SM-N930T using Tapatalk