Related
Has anyone had this error message with their Z3? I have searched the web, and all that I can find is that Tmo needs to send an update to the phone to fix. Called customer service, waited for the update, restarted phone, and nothing. They then said to switch out the SIM card, and that did nothing either. Any others?
Yup, the same exact problem, they sent a sim update, new sim card, hell I even had them send me a new phone. Same thing. E911 is also set up correctly, lol they know where to send the bill. My daughters all have the one touch fierce and their WiFi calling works perfectly. My wife's m8 also works fine. What's the freaking problem.
I had that for a day and it dissapeared, my dad's M8 had it too and it went away somehow in a day or two.
This has been going on for 2 weeks now and no one seems to have an answer
I guess mine was slightly different.
Apparently TMO has to send you an OTA update. Also make sure its enabled in services in your MyTmobile account under services if not just tick the box and enable it.
TMO Forums:
https://support.t-mobile.com/thread/78656
I had same issue
Artood2s said:
Has anyone had this error message with their Z3? I have searched the web, and all that I can find is that Tmo needs to send an update to the phone to fix. Called customer service, waited for the update, restarted phone, and nothing. They then said to switch out the SIM card, and that did nothing either. Any others?
Click to expand...
Click to collapse
I bought my mother-in-law this same phone (as I already have the D6616). Her phone had the same problem as you. Took me awhile to figure what happened, but like others have said, you need to contact T-Mobile and give them the error code. (I did this over T-Mobile chat) They in turn will push out a quick OTA update (can take up to two hours). Bad thing is I never received notification that it had updated, and I even asked the T-Mobile rep if I will see the update, and she stated yes. So, after two hours, and you still don't see the update, go ahead and restart your device. Once it reboots, your wifi calling feature will be updated and will then work. Oh, MAKE SURE YOUR WIFI IS TURNED OFF and WIFI CALLING IS TURNED OFF AS WELL! Your device will not update if you are not on the T-Mobile cellular network (as needed to push out the OTA). Be sure to turn on wifi calling once phone restarts and then you’re free to also turn on wifi.
Wifi calling error code reg90
U need to setup "e911" information with your service provider.
Hey M8 crew!
New to the M8, just bought the phone from swappa. Apparently it has root/s-off/some lollipop build installed on it. Clean ESN.
Took it into verizon to activate it on my line, but the sim doesn't appear to activate as they expect. It detects that it was inserted, says to reboot, after reboot still says no service, and never performs any activation. Verizon rep was claiming that the rom was causing the failures, and it does appear to likely be software related if it is never launching the activation. VZW tech support was no help other than saying it may take up to 12 hours to activate the sim (bs meter going off). Spent 2 hours in the store trying to get it to activate, saying everything was fine on their end. Tried a couple sims in store to rule out a bad sim. Have even tried the tape on the sim trick to see if that might have something to do with it.
Has anyone ever seen / heard of this sort of situation before and have any idea of how to fix it?
Would a stock RUU flash help out in anyway?
Is it because it is not a verizon rom that the activation is not happening? Would I somehow be able to use a different verizon phone to activate the sim, then put it in my phone and have service start working?
Any ideas?
nectur said:
Hey M8 crew!
New to the M8, just bought the phone from swappa. Apparently it has root/s-off/some lollipop build installed on it. Clean ESN.
Took it into verizon to activate it on my line, but the sim doesn't appear to activate as they expect. It detects that it was inserted, says to reboot, after reboot still says no service, and never performs any activation. Verizon rep was claiming that the rom was causing the failures, and it does appear to likely be software related if it is never launching the activation. VZW tech support was no help other than saying it may take up to 12 hours to activate the sim (bs meter going off). Spent 2 hours in the store trying to get it to activate, saying everything was fine on their end. Tried a couple sims in store to rule out a bad sim. Have even tried the tape on the sim trick to see if that might have something to do with it.
Has anyone ever seen / heard of this sort of situation before and have any idea of how to fix it?
Would a stock RUU flash help out in anyway?
Is it because it is not a verizon rom that the activation is not happening? Would I somehow be able to use a different verizon phone to activate the sim, then put it in my phone and have service start working?
Any ideas?
Click to expand...
Click to collapse
If the phone was used on another carrier it might be stuck in a non lte/CDMA mode. Flash stock vzw ruu. Do a factory reset. Go into mobile settings and make sure it's set to global. Then see if default network is set to vzw. Then check provisioning.
That did it. Thanks!
nectur said:
That did it. Thanks!
Click to expand...
Click to collapse
Np...bought an m8 for my dad a couple months back and same thing happened. I finally realized it was used on a different carrier.
It's an H950 from the $250 ebay deal. I am on ATT service and the phone worked fine at H95010d
I contacted ATT customer service and had them pushed OTA software update to me. The first agent pushed H95011x to me, and things went wrong since then.
The phone cannot read the sim card (but no missing sim notice), baseband shown as unknown, if I press the "status" under the "about phone" page, the screen will flash black then go back to the about phone page.
Then I tried a factory reset. The phone started normal as if everything was fine, it just works on the first boot after the reset. But once I restart the phone, it went back to the same situation as above. I tried many times and the whole process is highly repeatable.
After that, I contacted ATT again, had the H95011z pushed to me, and it did not change the problem. Replacing sim card does not help, either.
Then I tried to get to those recovery methods on the forum, including installing the LGE mobile device drivers. But then under download mode, the phone (LGE Android MTP device) is shown as "this device cannot start (code 10)". Thus I was not able to perform fix with the tools.
I am kinds of stuck in the middle. Any help and/or suggestions would be appreciated. Thanks!
neeviour said:
It's an H950 from the $250 ebay deal. I am on ATT service and the phone worked fine at H95010d
I contacted ATT customer service and had them pushed OTA software update to me. The first agent pushed H95011x to me, and things went wrong since then.
The phone cannot read the sim card (but no missing sim notice), baseband shown as unknown, if I press the "status" under the "about phone" page, the screen will flash black then go back to the about phone page.
Then I tried a factory reset. The phone started normal as if everything was fine, it just works on the first boot after the reset. But once I restart the phone, it went back to the same situation as above. I tried many times and the whole process is highly repeatable.
After that, I contacted ATT again, had the H95011z pushed to me, and it did not change the problem. Replacing sim card does not help, either.
Then I tried to get to those recovery methods on the forum, including installing the LGE mobile device drivers. But then under download mode, the phone (LGE Android MTP device) is shown as "this device cannot start (code 10)". Thus I was not able to perform fix with the tools.
I am kinds of stuck in the middle. Any help and/or suggestions would be appreciated. Thanks!
Click to expand...
Click to collapse
I am having exactly the same problem. I also replaced the SIM card, but instead of trying the 11z version I tried the rooted 11x version without any change.
As you wrote, a factory reset will restore the ability to make calls until the first reboot. For data, there is no APN listed. Manually inputing the APN info will cause data to work perfectly, but all APN data is lost/missing again on reboot.
icherub said:
I am having exactly the same problem. I also replaced the SIM card, but instead of trying the 11z version I tried the rooted 11x version without any change.
As you wrote, a factory reset will restore the ability to make calls until the first reboot. For data, there is no APN listed. Manually inputing the APN info will cause data to work perfectly, but all APN data is lost/missing again on reboot.
Click to expand...
Click to collapse
I've sent the phone back for an exchange, and the new one is coming tomorrow. Just noticed your reply.
So there is no fix for this? Or is there a problem with the ATT OTA update we should be aware of?
neeviour said:
I've sent the phone back for an exchange, and the new one is coming tomorrow. Just noticed your reply.
So there is no fix for this? Or is there a problem with the ATT OTA update we should be aware of?
Click to expand...
Click to collapse
This may not be a widespread issue, so there might've been an issue particularly with your Flex (maybe corrupt file?). I've used 11x/z without encountering this.
Ace42 said:
This may not be a widespread issue, so there might've been an issue particularly with your Flex (maybe corrupt file?). I've used 11x/z without encountering this.
Click to expand...
Click to collapse
Feels nervous when finding others had the same issue.
Just want to make sure if there's anything i should know of before dealing with the new unit coming tomorrow.
quick report:
Received the exchange. Seems new as the last one but does not contain the ATT sim as the last one did.
Tried update with date changing, for like 20 times no luck. Chatted ATT service to push the two updates (11x and 11z) in, one after another. Gone through the process without problem, and seems working fine now.
So, it may be device dependent or case specific. Thank you for your input.
I also had to send mine back. It's sitting on my front step now. The strange thing is that the email telling me the phone was being sent back only listed a speaker problem, which I did not have and never mentioned. We'll see.
neeviour said:
quick report:
Received the exchange. Seems new as the last one but does not contain the ATT sim as the last one did.
Tried update with date changing, for like 20 times no luck. Chatted ATT service to push the two updates (11x and 11z) in, one after another. Gone through the process without problem, and seems working fine now.
So, it may be device dependent or case specific. Thank you for your input.
Click to expand...
Click to collapse
Are you an AT&T customer? I can not get the update to come OTA, whether with an ATT valid SIM or a different SIM. I also tried calling and because I have a business ATT line, I got business support and the lady was clueless about pushing the update to my phone from her end.
hamzer11 said:
Are you an AT&T customer? I can not get the update to come OTA, whether with an ATT valid SIM or a different SIM. I also tried calling and because I have a business ATT line, I got business support and the lady was clueless about pushing the update to my phone from her end.
Click to expand...
Click to collapse
What time of day are you calling? I found calling during east coast business hours got me the right people. Ask the agent if they can do a google search from their computer, when/if they say yes ask them to search for H95011x or H95011z. The first or second result should be the AT&T page that explains the update, once my rep had that info things went MUCH better. (I just noticed for me the first result is my post on this forum LOL)
I got my Flex 2 back and LG did nothing to fix it. The repair said "fixed speaker". I never said anything about a speaker. After a couple frustrated calls I had to send it a second time. The second time, it was returned "no problem found". The phone is unusable as it can only be used after a reset and before a reboot or power off. More fun with LG later today. Ultimately, though, the reps don't give a crap; I couldn't even get the last rep to increase shipping speed, even though they failed to repair it the first time.
So a few weeks ago I bought a pixel for my son from someone local. It was very cheap and my son was using it for school using his mobile data. Today I have then tried to use the phone as I await for delivery of another handset and am faced with some issues. First the phone won’t connect to the WiFi. It’s currently running Android 8.1.0 May security patch and no matter what WiFi wont connect. At times it will say saved network but won’t connect. I have tried to reset the phone but alas no luck. The other issue is that phone is sim unlocked and can use my ee and 3uk SIM cards but the oem option states “connect to the internet or contact your carrier”. Unfortunately I cannot get the person who sold me the phone and all I remember is he told me he bought it from Very UK. Any suggestions please to fix this?. I as under the impression only phones which are sim locked have locked bootloader and also any ideas on how to fix my WiFi thanks.
marvi0 said:
So a few weeks ago I bought a pixel for my son from someone local. It was very cheap and my son was using it for school using his mobile data. Today I have then tried to use the phone as I await for delivery of another handset and am faced with some issues. First the phone won’t connect to the WiFi. It’s currently running Android 8.1.0 May security patch and no matter what WiFi wont connect. At times it will say saved network but won’t connect. I have tried to reset the phone but alas no luck. The other issue is that phone is sim unlocked and can use my ee and 3uk SIM cards but the oem option states “connect to the internet or contact your carrier”. Unfortunately I cannot get the person who sold me the phone and all I remember is he told me he bought it from Very UK. Any suggestions please to fix this?. I as under the impression only phones which are sim locked have locked bootloader and also any ideas on how to fix my WiFi thanks.
Click to expand...
Click to collapse
Seems like you've bought a Verizon locked phone. Those phones has locked bootloaders and recently there was a tutorial on how to unlock those bootloaders. So it can't be done on the traditional way. Here's the tutorial: https://www.google.se/amp/s/forum.x...unlock-bootloader-verizon-pixel-t3796030/amp/
You say you're running may security patch see if there's an update first to June. The non Verizon phones got that already on Monday.
Another thing you could try is to do a factory reset and don't restore any backups at all. Because some backups tries to restore previously remembered wifi. So try that and connect to the wifi. If all this doesn't work then you could try to enroll into Android P beta and see if that fixes it. If that doesn't work then it's an hardware defect. If you cannot get a hold of the person who sold you it then I'm sorry to say that's probably why he sold it to you cheap as he probably knew about the problems it was having. I personally would try to get a hold of him first.
Arju said:
Seems like you've bought a Verizon locked phone. Those phones has locked bootloaders and recently there was a tutorial on how to unlock those bootloaders. So it can't be done on the traditional way. Here's the tutorial: https://www.google.se/amp/s/forum.x...unlock-bootloader-verizon-pixel-t3796030/amp/
You say you're running may security patch see if there's an update first to June. The non Verizon phones got that already on Monday.
Another thing you could try is to do a factory reset and don't restore any backups at all. Because some backups tries to restore previously remembered wifi. So try that and connect to the wifi. If all this doesn't work then you could try to enroll into Android P beta and see if that fixes it. If that doesn't work then it's an hardware defect. If you cannot get a hold of the person who sold you it then I'm sorry to say that's probably why he sold it to you cheap as he probably knew about the problems it was having. I personally would try to get a hold of him first.
Click to expand...
Click to collapse
hmm many thanks. How do i tell its a verizon device as its currently working with a 3 uk and ee sim card. Am just installing the android P better now and does this resolve the wifi issue because without wifi I wont even be able to follow the bootloader unlock guide above.
marvi0 said:
hmm many thanks. How do i tell its a verizon device as its currently working with a 3 uk and ee sim card. Am just installing the android P better now and does this resolve the wifi issue because without wifi I wont even be able to follow the bootloader unlock guide above.
Click to expand...
Click to collapse
Bootloader unlock has nothing to do with carrier. If you could use 3 UK Sim then you're fine. Unlocking bootloader is only needed to flash custom ROM with some exceptions. Are you able to turn on WiFi and see your wifi but not able to connect or does it not turn on at all?
Arju said:
Bootloader unlock has nothing to do with carrier. If you could use 3 UK Sim then you're fine. Unlocking bootloader is only needed to flash custom ROM with some exceptions. Are you able to turn on WiFi and see your wifi but not able to connect or does it not turn on at all?
Click to expand...
Click to collapse
Hi thanks WiFi can be turned on but it won’t connect. At times it says connected and just saves the network. Mobile data is working fine so completely lost, and now trying to flash the P beta.
Just tried android p and same issue. WiFi will try and connect and just end up with saved but it won’t actually connect. Any other ideas please?
marvi0 said:
Just tried android p and same issue. WiFi will try and connect and just end up with saved but it won’t actually connect. Any other ideas please?
Click to expand...
Click to collapse
Have you tried pressing the wifi name and then press forget and try to put in the wifi password again. Is it the same issue on all wifi? Like at home, school, friends home or only at home? If it happens everywhere then I don't have any more ideas. My thought would be that it's a hardware defect. Is there no chance of getting hold of the previous owner?
Arju said:
Have you tried pressing the wifi name and then press forget and try to put in the wifi password again. Is it the same issue on all wifi? Like at home, school, friends home or only at home? If it happens everywhere then I don't have any more ideas. My thought would be that it's a hardware defect. Is there no chance of getting hold of the previous owner?
Click to expand...
Click to collapse
Yes tried all that different WiFi connections no luck at all. I will try and call google tomorrow but chances are they will need the receipt which I have absolutely no way of getting phew.
marvi0 said:
Yes tried all that different WiFi connections no luck at all. I will try and call google tomorrow but chances are they will need the receipt which I have absolutely no way of getting phew.
Click to expand...
Click to collapse
They would probably only need the IMEI number, but if it's out of warranty they'll refer you to a repair center. Wish you all the best and hope that they'll be able to fix it. Let us know what Google says if you do contact them. Keep us updated please.
Arju said:
They would probably only need the IMEI number, but if it's out of warranty they'll refer you to a repair center. Wish you all the best and hope that they'll be able to fix it. Let us know what Google says if you do contact them. Keep us updated please.
Click to expand...
Click to collapse
Thanks will update you as soon as I have spoken to them. The person I bought it from did say it was only bought last year from Very UK and it also looks mint. Has anyone had any dealings with Google RMA with phones without receipt?
I don't know if anyone else has noticed, but after I updated to the latest OTA update (1.25.617.4) I can no longer access call forwarding settings nor call waiting settings. It gives me error saying 'Network Error or sim card error' when trying to view either. I thought it was an issue with my sim cause I just used the one from my HTC 10 so went to AT&T and got a new one only to have same issue. Did a factory reset and same issue. After that I figured it could have possibly been the update, so I used the ROM exe from HTC to get back to 1.21.617.3 and can access those settings again. It was nice to get VoLTE, but I don't want to lose some settings access to get that.
If anybody has had the same issue, have you found a fix other then going back to 1.21.617.3 or staying on 1.25.617.4 and not being able to access call forwarding and call waiting?
Thanks
Interesting. Mine is completely normal with the same SIM card from my HTC 10 as well. Have you tried wiping the cache partition? That actually helped me get VoLTE on my HTC 10.
Here's a link how to do it in case you don't know...
https://support.t-mobile.com/docs/DOC-25804
holz75 said:
Interesting. Mine is completely normal with the same SIM card from my HTC 10 as well. Have you tried wiping the cache partition? That actually helped me get VoLTE on my HTC 10.
Here's a link how to do it in case you don't know...
https://support.t-mobile.com/docs/DOC-25804
Click to expand...
Click to collapse
Yeah, tried that as well. I don't know if it matters but I see that link is from T-Mobile, I use AT&T.
Yusuke14 said:
Yeah, tried that as well. I don't know if it matters but I see that link is from T-Mobile, I used AT&T.
Click to expand...
Click to collapse
I know, but it's just instructions (from T-Mobile) on how to do it on your HTC 10.
No issues here, on t-mobile and used same sim as HTC 10. I know it doesn't resolve your issue, but maybe there is an issue with the update and AT&T. See if anyone else on AT&T has same issue.
I'm on Verizon and I get the following when I try to go to either Call forwarding or Additional Settings. It never gets any further.
Have not tried going to these on the previous OTAs.
mr_salvador said:
No issues here, on t-mobile and used same sim as HTC 10. I know it doesn't resolve your issue, but maybe there is an issue with the update and AT&T. See if anyone else on AT&T has same issue.
Click to expand...
Click to collapse
I was hoping to hear from others on AT&T (and other networks) by posting here. Seems T-Mobile is ok and Verizon has a similar but different issue.
Yusuke14 said:
Yeah, tried that as well. I don't know if it matters but I see that link is from T-Mobile, I use AT&T.
Click to expand...
Click to collapse
Yusuke14 said:
I was hoping to hear from others on AT&T (and other networks) by posting here. Seems T-Mobile is ok and Verizon has a similar but different issue.
Click to expand...
Click to collapse
I don't know if I mentioned it before but I'm on AT&T, and everything is normal.
I'm on AT&T, U12+ on 1.25 firmware (+ Viper 1.01), SIM card is from HTC 10 (actually even further back than that, same SIM card since 2014 or 2015).
No issues accessing call forwarding / call waiting settings. All of those features are working for me (forwarding to YouMail, waiting definitely works, so does conference/merging calling) and also now VoLTE.
You mentioned it didn't work on 1.25 even after factory resetting. Were you modded in any way? So you RUU'ed back to 1.21 and it works. Have you tried OTA'ing back to 1.25 and seeing if it now works? I'm just trying to think of anything. Sorry dude, that stinks. I'm on 1.25 and heavily modified and it all works...
I get the same error message as well. But im on T-mobile. Really doesn't matter to me personally as i don't use settings in there.
But you're not the only one that gets the error.
turbo jjjang said:
I'm on AT&T, U12+ on 1.25 firmware (+ Viper 1.01), SIM card is from HTC 10 (actually even further back than that, same SIM card since 2014 or 2015).
No issues accessing call forwarding / call waiting settings. All of those features are working for me (forwarding to YouMail, waiting definitely works, so does conference/merging calling) and also now VoLTE.
You mentioned it didn't work on 1.25 even after factory resetting. Were you modded in any way? So you RUU'ed back to 1.21 and it works. Have you tried OTA'ing back to 1.25 and seeing if it now works? I'm just trying to think of anything. Sorry dude, that stinks. I'm on 1.25 and heavily modified and it all works...
Click to expand...
Click to collapse
Hadn't done anything to phone at the time, was completely stock, nothing done at all as of yet. Only thing i have done now after going back to 1.21 is unlock the bootloader and so far that's all. Going to try taking the OTA to 1.25 again and see if it wasn't just some fluke of nature.
Will update afterwards.
Edit: went back to 1.25, getting same error and can't access call forwarding or call waiting settings.
JWhetstone02 said:
I'm on Verizon and I get the following when I try to go to either Call forwarding or Additional Settings. It never gets any further.
Have not tried going to these on the previous OTAs.
Click to expand...
Click to collapse
I'm still on the original firmware (no rush to update as of yet) and I get the same situation when accessing those settings.
1.25 RUU is available. I'm on T-Mobile with an Unlocked boot loader and custom kernel however everything works on this end.
I have the 1.25 update and I'm on ATT, and I apparently have the issue as well. No bother, though, since I don't use call forwarding.
And, this is the sim card from my 10.
I am on AT&T and my firmware 1.25.617.4 and everything working fine here
I realize this thread is a a little old but I am having the same issue. I am on AT&T. The only tweaks I have made is to unlock the bootloader and disabled tethering guard. The problem existed on 1.25.617.4 and persists on 1.30.617.2. I thought the problem was a provisioning issue with AT&T. After multiple calls with them and a couple with HTC, I found this thread. Of course I should have stopped here first. I actually need call forwarding and calling AT&T to have them manually provision it every time I need it just won't cut it. Has anyone been able to figure this out?