So in the process of performing following the Root/Unlock guide that @jcase put together I've had an odd result and we're wondering if I am the only one or if others may be seeing this issue.
Everything through step 10 is fine and the device gets rooted and boots with no issues and wifi calling is working. After s-off however the device won't connect to wifi calling at all. It just shows Error ER081 unable to connect. We've gone all the way back and reloaded the backup, taken the device s-on, etc and it won't work.
Has any other T-Mobile users been through S-Off and have wifi calling working, or anyone else seeing the same error?
Just for reference I confirmed mobile data worked fine, checked with multiple wifi networks, and nothing works. It doesn't even act like it's trying to connect it just goes straight to that message.
Oh, that's no good. I plan to S-off eventually but I usually give it a week or two to make sure my phone doesn't have early death syndrome. I'll hold off doing S-off until I hear a conclusion on this issue.
For what it's worth, My USA unlocked is S-on with bootloader unlocked and TWRP installed. No root at this point but I'm going to do that shortly. WiFi calling is working perfectly on T-Mobile for me (I did a test call just now to verify).
I noticed they moved the WiFi calling preferences (now it's under phone | call | Wi-Fi Calling all the way at the bottom) and the dialer now says WiFi call.
EDIT: Just rooted and T-Mobile WiFi calling still works. Must be exclusively a S-off thing.
FreydNot said:
Oh, that's no good. I plan to S-off eventually but I usually give it a week or two to make sure my phone doesn't have early death syndrome. I'll hold off doing S-off until I hear a conclusion on this issue.
For what it's worth, My USA unlocked is S-on with bootloader unlocked and TWRP installed. No root at this point but I'm going to do that shortly. WiFi calling is working perfectly on T-Mobile for me (I did a test call just now to verify).
I noticed they moved the WiFi calling preferences (now it's under phone | call | Wi-Fi Calling all the way at the bottom) and the dialer now says WiFi call.
EDIT: Just rooted and T-Mobile WiFi calling still works. Must be exclusively a S-off thing.
Click to expand...
Click to collapse
I am not convinced it's an s-off issue, I am working with Jcase and we've even gone as far as to put it back S-on and it doesn't seem to come back. I suspect most likely I screwed up in the process somewhere along the line.
That's why I am trying to find if someone was able to go through that process and confirm its working.
PG
marked as solved!
Update
Ok so I had decided I was going to change carriers anyway because TMOs wifi calling has been buggy in general so I decided to go back and s-off again.
As I was going through that process it generated an error and wanted a restart and run again which I did.
I then was getting errors that no internet connection was present and such so working with @jcase we began to suspect router issue. I did a restart on the router and ran sunshine again, this time it went through and worked, then ran the patch for encryption, and wiped data and did restart.
Just to check I put my T-Mobile sim back in as I was setting up the device and when I connected to wifi I noticed that wifi calling came back up and was working. No further issues and at this point both @jcase and I think this may have been a router issue all along and not related to sunshine.
Thanks to @jcase and all the extra time and help he provided, it certainly was more than worth the $25 and those folks do a great job of trying to help even when it turns out not to be something related their product.
Glad to hear it all worked out.
I am getting the same error er081 unable to connect.
The phone was updated to latest OTA, rooted, and s-on.
I upgraded from HTC M7 so I had to trim my SIM card to nano size one so I can put it in this HTC 10 unlocked version. I don't know if trimming the SIM card has something to do with wifi-calling.
I have another HTC M8 from T-mobile and its wi-fi calling works just fine.
Does any one have similar situation getting this error and may suggest a solution>?
Yeah also having this issue after s-off. No issue with sunshine other than delayed paypal verification
I had an odd issue with ATT after s-off where my handset wouldn't provision properly so I couldn't use VoLTE etc, just basic services.
It's been resolved by letting the phone fully boot and then, once fully booted up, put the SIM in and let it provision vs booting with the SIM in.
Might not be an S-off Issue at all and might simply have been a provisioning issue.
Sent from my HTC 10 using Tapatalk
Just for clarification, after s-off & formatting data, should twrp still ask for decryption when it starts?
Tried wiping data and another data format then inserted sim after setup and immediately got wifi calling error popup.
Alarand said:
Just for clarification, after s-off & formatting data, should twrp still ask for decryption when it starts?
Tried wiping data and another data format then inserted sim after setup and immediately got wifi calling error popup.
Click to expand...
Click to collapse
Try re provisioning the sim card
yungyeh said:
I am getting the same error er081 unable to connect.
The phone was updated to latest OTA, rooted, and s-on.
I upgraded from HTC M7 so I had to trim my SIM card to nano size one so I can put it in this HTC 10 unlocked version. I don't know if trimming the SIM card has something to do with wifi-calling.
I have another HTC M8 from T-mobile and its wi-fi calling works just fine.
Does any one have similar situation getting this error and may suggest a solution>?
Click to expand...
Click to collapse
try re provisioining hte sim card
jcase said:
Try re provisioning the sim card
Click to expand...
Click to collapse
I have to contact Tmo to do this for me right? Will try in a bit
Alarand said:
I have to contact Tmo to do this for me right? Will try in a bit
Click to expand...
Click to collapse
paging @captainthrowback
Alarand said:
Just for clarification, after s-off & formatting data, should twrp still ask for decryption when it starts?
Tried wiping data and another data format then inserted sim after setup and immediately got wifi calling error popup.
Click to expand...
Click to collapse
I believe that's true. And you have to keep it that way (don't format the data to remove encryption) or you will lose Radio. At least that's what I was told. I got the error without wiping the data tho~.
Take a look at this post http://forum.xda-developers.com/showpost.php?p=66347165&postcount=2
The Wi-Fi calling option just completely disappeared after I achieved S-OFF on my HTC 10. Honestly, I'm starting to get a little disappointed with this device, initially I was psyched to receive the shipment, but with the inconveniences of mobile data not working with decrypted data, not being able to access internal storage in recovery, and the disappearing Wi-Fi calling, I'm considering just sending the device back. If anyone knows how to bring Wi-Fi calling back, I'd greatly appreciate it.
jcase said:
paging @captainthrowback
Click to expand...
Click to collapse
Think you missed half his name, @Captain_Throwback ;p
I tried contacting T-Mobile and they told me there's nothing they can do on their end. Said the sim is already provisioned to work properly with the features by default (volte/wfc) Rep seemed hesitant to do anything other than sell me a tmo brand phone, he might not have understood what I was asking either though. tbh i've never had sim issues before so unfamiliar with what exactly I have to do here.
Thanks for the help, other than this tiny issue everything else works wonderfully
Alarand said:
Think you missed half his name, @Captain_Throwback ;p
I tried contacting T-Mobile and they told me there's nothing they can do on their end. Said the sim is already provisioned to work properly with the features by default (volte/wfc) Rep seemed hesitant to do anything other than sell me a tmo brand phone, he might not have understood what I was asking either though. tbh i've never had sim issues before so unfamiliar with what exactly I have to do here.
Thanks for the help, other than this tiny issue everything else works wonderfully
Click to expand...
Click to collapse
Well we have had two people ask about this issue, one turned out to be a router issue on their end, the other one (captain Throwback) put a sprint sim in the phone, rebooted, then put tmoible in, which caused it to re provision and work again
jcase said:
Well we have had two people ask about this issue, one turned out to be a router issue on their end, the other one (captain Throwback) put a sprint sim in the phone, rebooted, then put tmoible in, which caused it to re provision and work again
Click to expand...
Click to collapse
Well that was easy. Put at&t sim in, prompted restart, tmobile sim in again and another restart, and voila working perfectly.
I imagine there's a manual way to go about this but I couldn't seem to find it. Resetting apn settings gave me a sim setup prompt so if I had removed sim prior to doing that it may have also fixed it, not really sure though.
Thanks again!
Alarand said:
Well that was easy. Put at&t sim in, prompted restart, tmobile sim in again and another restart, and voila working perfectly.
I imagine there's a manual way to go about this but I couldn't seem to find it. Resetting apn settings gave me a sim setup prompt so if I had removed sim prior to doing that it may have also fixed it, not really sure though.
Thanks again!
Click to expand...
Click to collapse
Good news!
Don't worry I went through 15 flashes and 2 days trying to fix my ATT issue only to randomly discover it's a provisioning bug.
Sweet phone though eh!
Sent from my HTC 10 using Tapatalk
Related
Ok just recently unbricked my phone and started flashing once again. First I did the HARD SPL change from 2.03 to 2.10 Olipro. I flashed the current vp3G a few times but I was getting no phone service. I flashed the schaps and it did the same. My was getting no service and when I clicked on settings it said this.
Unknown SIM status.
Only emergency calls can be made without a PIN.
Click to expand...
Click to collapse
Did some googling and found some sources where it said my default PIN was either 1111 or 2222. I went ahead and called ATT and explained to them I was getting no service but of course never mentioned I had a cooked ROM. They said the same that the default was 1111. Of course for some reason when I was talking to them I could not get to the settings to enter it. I told them I would call them back.
Finally got to enter it in and nothing. It is still not working. I'm in some desperate need of suggestions. Thank You.
- Monty
Flash the OEM ROM from your provider. This should get your service back if your using a legit SIM
i see you have unbricked your phone, try loading up a new radio
http://rapidshare.com/files/60589318/radio1.54.07.00.rar
oh yea, thats the radio im using for my 8525, its the updated version 1.54 it works pretty well, hope that fixes your problem
I have that same problem but it seems that changing the radio does not work, although I havent tried every single radio. Some radios will give say i have no service even when i don't have the sim card in (it should be saying no sim)
This might help
If you are in USA and if you have a CINULAR sim card in your phone go to a AT&T store for a FREE AT&T sim card. It might resolve the issue as AT&T just changed some settings in some towers.
Read about in VP's 3.62
here: http://forum.xda-developers.com/showpost.php?p=1637422&postcount=445:)
fuzzvirus said:
If you are in USA and if you have a CINULAR sim card in your phone go to a AT&T store for a FREE AT&T sim card. It might resolve the issue as AT&T just changed some settings in some towers.
Read about in VP's 3.62
here: http://forum.xda-developers.com/showpost.php?p=1637422&postcount=445:)[/QUOTE
I have a new AT&T sim card and I still have the problem
Click to expand...
Click to collapse
Monty, have you found a solution?
ihavetinyballs said:
Flash the OEM ROM from your provider. This should get your service back if your using a legit SIM
Click to expand...
Click to collapse
That is how I bricked my phone in the first place. Could not flash OEM either 2.15 or the most recent 3.62 WM6 upgrade.
asianr0cker said:
oh yea, thats the radio im using for my 8525, its the updated version 1.54 it works pretty well, hope that fixes your problem
Click to expand...
Click to collapse
When I got unbricked I updated my SPL like you mentioned and now I'm running 2.10. I did try to update the radio but that also got locked up and had to hard reset to get it back. I was trying 1.54 also.
cjchriscj said:
Monty, have you found a solution?
Click to expand...
Click to collapse
No I have not.
More reading and more reading. Ok I realize I have no GSM and no Radio. When I try to install radio it gets stuck on 0% then locks me out. Then I'm stuck in the Tri-Color mode and am forced to reflash ROM. I'm thinking "Problem 5" is the problem I'm having but can anyone confirm or help me out please.
My ATT flash screen says:
R None
G None
D 3.62
Click to expand...
Click to collapse
That means I have no Radio and GSM correct? What do I do?
warranty?
How far into your warranty are you, assuming you're still under warranty? Same thing happened to me. I played stupid with AT&T tech support (then Cingular), had no distinguishable drop marks or water damage, and they replaced it under warranty I even had it stuck on the bootloader screen If you're still under warranty, try to load an oem rom back on it and see if you can get them to replace it.
kalrykh said:
How far into your warranty are you, assuming you're still under warranty? Same thing happened to me. I played stupid with AT&T tech support (then Cingular), had no distinguishable drop marks or water damage, and they replaced it under warranty I even had it stuck on the bootloader screen If you're still under warranty, try to load an oem rom back on it and see if you can get them to replace it.
Click to expand...
Click to collapse
Unfortunatley im out of warranty
Is there anyway to completely erase everything that is on the hermes at once? except for the stuff on the eeprom, i already had to deal with that
can no one help us?
i heard from my friend who works at an att non corp store that just recently non corp stores were given the ability to give the new contract discounts. that he just has to make a 5 min call and it gets approved and they can offer you the 2yr discount although it might extend your contract.
reason im saying this is even if your not up for an update, any att store should be able to (if the guy chooses to be helpful) hook you up with the discount regardless of how long or how little you've been in contract.
just food for thought in case you cant find a solution.
when I reset my device i see no GSM ocassionaly, well since an hour ago, its been saying nothing but No GSM, I have tried to fix it using the unbrick direction in the wiki, but to no avail.
I got my phone around the begining of last month and decided the other night that it was time to root as I have rooted every android device I have owned since the wildfire s. I had previously taken the OTA so I was on vs98512b. I used LG flashtool to downgrade to vs98510b. The downgrade it's self went fine. I then rooted using stumproot again nothing out of the ordinary. I downloaded Supersu and enabled survival mode. I tried to check for New updates and it says "your phone is not registered" I found that to be strange so I checked some other settings and found that my imei was 000000000000000. I found that to be strange. I attempted to make a call and my phone switched to roaming and I lost all my signal bars. I performed a factory reset and after the reset I have all network function, I'm connected to Verizon 4g lte and can make calls, no more roaming. I checked the imei again at this point and it is still showing 000000000000000 and I was still unable to update. So I then reflashed the stock firmware for vs98510b. Again I had the roaming issue that went into being unable to connect to network. Again I performed a hard rest on my phone and got full network function back. I had a new micro SIM tucked away for a rainy day so I put the New SIM card in and activated it with no change to imei. What can I do from here? My phone is working fine with the imei being 000000000000000 it seems like the only issue is not being able to get an OTA, when I try using Verizon's upgrade assistant it won't even list my phone. If I check my Verizon it shows up as a non vow device. Thanks in advanced.
wcallah04 said:
I got my phone around the begining of last month and decided the other night that it was time to root as I have rooted every android device I have owned since the wildfire s. I had previously taken the OTA so I was on vs98512b. I used LG flashtool to downgrade to vs98510b. The downgrade it's self went fine. I then rooted using stumproot again nothing out of the ordinary. I downloaded Supersu and enabled survival mode. I tried to check for New updates and it says "your phone is not registered" I found that to be strange so I checked some other settings and found that my imei was 000000000000000. I found that to be strange. I attempted to make a call and my phone switched to roaming and I lost all my signal bars. I performed a factory reset and after the reset I have all network function, I'm connected to Verizon 4g lte and can make calls, no more roaming. I checked the imei again at this point and it is still showing 000000000000000 and I was still unable to update. So I then reflashed the stock firmware for vs98510b. Again I had the roaming issue that went into being unable to connect to network. Again I performed a hard rest on my phone and got full network function back. I had a new micro SIM tucked away for a rainy day so I put the New SIM card in and activated it with no change to imei. What can I do from here? My phone is working fine with the imei being 000000000000000 it seems like the only issue is not being able to get an OTA, when I try using Verizon's upgrade assistant it won't even list my phone. If I check my Verizon it shows up as a non vow device. Thanks in advanced.
Click to expand...
Click to collapse
have you backuped the efs partition like the rooting thread said
Of course not. That would have been to easy. If I had I would have been able to avoid making a new thread. I really do Google first. Except with the back up of the eds partition. I knew nothing about that until I searched imei problems.
wcallah04 said:
I got my phone around the begining of last month and decided the other night that it was time to root as I have rooted every android device I have owned since the wildfire s. I had previously taken the OTA so I was on vs98512b. I used LG flashtool to downgrade to vs98510b. The downgrade it's self went fine. I then rooted using stumproot again nothing out of the ordinary. I downloaded Supersu and enabled survival mode. I tried to check for New updates and it says "your phone is not registered" I found that to be strange so I checked some other settings and found that my imei was 000000000000000. I found that to be strange. I attempted to make a call and my phone switched to roaming and I lost all my signal bars. I performed a factory reset and after the reset I have all network function, I'm connected to Verizon 4g lte and can make calls, no more roaming. I checked the imei again at this point and it is still showing 000000000000000 and I was still unable to update. So I then reflashed the stock firmware for vs98510b. Again I had the roaming issue that went into being unable to connect to network. Again I performed a hard rest on my phone and got full network function back. I had a new micro SIM tucked away for a rainy day so I put the New SIM card in and activated it with no change to imei. What can I do from here? My phone is working fine with the imei being 000000000000000 it seems like the only issue is not being able to get an OTA, when I try using Verizon's upgrade assistant it won't even list my phone. If I check my Verizon it shows up as a non vow device. Thanks in advanced.
Click to expand...
Click to collapse
check this out...this is how i solved mine...its something i did on my own...theres instructiong for the sprint but i did it on my verizon...check out my post... http://forum.xda-developers.com/showpost.php?p=57849643
please note i did it a little different then the instructions...i didnt use a1 or b1 instruction bc it was different for my phone..
crazy4android said:
check this out...this is how i solved mine...its something i did on my own...theres instructiong for the sprint but i did it on my verizon...check out my post... http://forum.xda-developers.com/showpost.php?p=57849643
please note i did it a little different then the instructions...i didnt use a1 or b1 instruction bc it was different for my phone..
Click to expand...
Click to collapse
Did it put your imei back in? Or just made it so you can talk and text?
wcallah04 said:
Did it put your imei back in? Or just made it so you can talk and text?
Click to expand...
Click to collapse
i rewrote my orignal imei...u can change it if u want but its illeagal...but who cares...i just fixed mine...and data and everything works perfectly...even using at&t on a verizon phone and it humming like a humming bird... its not hard or complicated....very simple dont even have to get nervous...
That's all I need is to put my imei back in. Lol I'll try it as soon as I get home from work. Thanks.
crazy4android said:
check this out...this is how i solved mine...its something i did on my own...theres instructiong for the sprint but i did it on my verizon...check out my post... http://forum.xda-developers.com/showpost.php?p=57849643
please note i did it a little different then the instructions...i didnt use a1 or b1 instruction bc it was different for my phone..
Click to expand...
Click to collapse
No luck. I can't get my phone to diag mode.
suljo94 said:
have you backuped the efs partition like the rooting thread said
Click to expand...
Click to collapse
Is it possible to backup my efs prior to gaining root access?
wcallah04 said:
No luck. I can't get my phone to diag mode.
Click to expand...
Click to collapse
which service provider did u use...with verizon i used ##228378 in the dialer code nd i left it in the menu that pop up nd on my pc it showed up a a serial com port...make sure ur drivers are working properly...nd when connecting to cdma tool u pick serial port...
crazy4android said:
which service provider did u use...with verizon i used ##228378 in the dialer code nd i left it in the menu that pop up nd on my pc it showed up a a serial com port...make sure ur drivers are working properly...nd when connecting to cdma tool u pick serial port...
Click to expand...
Click to collapse
Hmmm... I have verizon. The only thing I can get the cdma tool to to connect to is the modem port. Nothing else replies...
wcallah04 said:
Hmmm... I have verizon. The only thing I can get the cdma tool to to connect to is the modem port. Nothing else replies...
Click to expand...
Click to collapse
hey check out this tool...i also used this once...it worked great..http://forum.xda-developers.com/gal...ol-updated-09-06-14-efs-professional-t1308546 first open efs professional.exe./qualcomm nv tool/...connect to port for the drop down menu on top...i used serial since thats the only one that responded...then press connect...then try and read phone info to see if it sees ur phone...then go to the secure ops tab.....select the imei(dec) box and enter ur imei and then write it...then select meid(hex) box.....write ur meid...same as imei minus the last digit.... thats the best instruction i can give on the top of my head..i did it a while ago...so if confused feel free to ask questions...
VS985: Lost IMEI, Can't Make Phone Calls
I'm having problems with my VS985 after downgrading including losing the IMEI and especially the ability to make phone calls.
So I got a used VS985W that had 35B installed on it for one of my kids. Having put CyanogenMod on my LG G3 (VS985) successfully, I started down that path. I used the TOT method to flash back to 10B, then used KDZ to upgrade to 12B. Then I rooted, installed TWRP, and then CyanogenMod. But I couldn't make phone calls.
There are numerous things I've tried, but it's still unable to make phone calls, usually giving out of service area, but when trying to use the *#06# code, I get an error of "missing IMMI or such".
At one point I found the IMEI had gone to all zeros. I managed to find a method to fix that. I also switched out SIM cards between phones; same issue - it's the phone and firmware.
The only thing that seems to fix it is to go back to stock 35B. Then it makes phone calls. But then I can't root it and restore the apps/data we backed up from the previous phone (LG Spectrum running CM 11).
I have done hours of searching and reading these forums along with others. I've redone the downgrade and root and TWRP install and tried numerous things but still can't get phones calls in stock versions less than 35B or in CyanogenMod (12.1, not 13, which I did try to install but never could get it to reliably boot back up after an installation, so finally gave up and went back to 12.1).
Anyone heard of this before? I can't find it. I did see in this thread post #4:
Google~Android said:
check this out...this is how i solved mine...its something i did on my own...theres instructiong for the sprint but i did it on my verizon...check out my post... http://forum.xda-developers.com/showpost.php?p=57849643
Click to expand...
Click to collapse
Unfortunately this link doesn't work (moved or deleted). I'm continuing to search, but it almost seems like I managed to royally muck up some partition I didn't mean to? I've tried following the advice of a number of posts, too, on related, similar aspects, but I'm getting to a point of slight insanity. Along with a kid that wants their phone (and the old one has the older style SIM so not just that easy to deal with just switching unfortunately).
Any guidance or thoughts Much appreciated. Am going to continue to try the various things I'm reading about. Thanks, -Mark
Hi, I recently flashed the skydragon rom v 10 for my AT&T M8. Everything seems to be working fine except I cannot get incoming calls. I can send calls and texts but cannot get incoming calls. Anyone know a fix for this?
grrrdn said:
Hi, I recently flashed the skydragon rom v 10 for my AT&T M8. Everything seems to be working fine except I cannot get incoming calls. I can send calls and texts but cannot get incoming calls. Anyone know a fix for this?
Click to expand...
Click to collapse
Answered your question here: http://forum.xda-developers.com/att-htc-one-m8/help/skydragon-rom-getting-incoming-calls-t3166763
Please don't ask the same question in multiple places.
redpoint73 said:
Answered your question here: http://forum.xda-developers.com/att-htc-one-m8/help/skydragon-rom-getting-incoming-calls-t3166763
Please don't ask the same question in multiple places.
Click to expand...
Click to collapse
Sorry about posting it in multiple places. Do you know if the disable is right away or takes some time? I called AT&T and they told me it was disabled and would send me notification, but incoming calls still not working and no notification. I will be calling back later today to verify though
grrrdn said:
Sorry about posting it in multiple places. Do you know if the disable is right away or takes some time? I called AT&T and they told me it was disabled and would send me notification, but incoming calls still not working and no notification. I will be calling back later today to verify though
Click to expand...
Click to collapse
Don't know. I wouldn't think an account change like that would take long. I wonder if they just told you that to get you to hang up?
redpoint73 said:
Don't know. I wouldn't think an account change like that would take long. I wonder if they just told you that to get you to hang up?
Click to expand...
Click to collapse
Even with VoLTE off, no incoming calls. But did see that sky dragon team is working on it so I guess I'll be off LTE until then. Thanks!
Is there a way to return to stock? I know you can use RUU but I am getting confused with all the talk about S-Off and S-On. My M8 is S-On with skydragon v9.0 with the lollipop updates from April. Do I need S-Off to use the RUU or do I simply lock the bootloader then use the RUU as instructed??
grrrdn said:
Even with VoLTE off, no incoming calls. But did see that sky dragon team is working on it so I guess I'll be off LTE until then. Thanks!
Click to expand...
Click to collapse
Are you sure they turned off HD Voice for your account? Understanding of this feature by the first tier customer service reps seems dodgy, at best. One user here reported that one rep said it couldn't be disabled; so he just called again, and got a rep that could do it.
grrrdn said:
Is there a way to return to stock? I know you can use RUU but I am getting confused with all the talk about S-Off and S-On. My M8 is S-On with skydragon v9.0 with the lollipop updates from April. Do I need S-Off to use the RUU or do I simply lock the bootloader then use the RUU as instructed??
Click to expand...
Click to collapse
Of course there is a way to return to stock.
If you made a TWRP nandroid of the stock ROM (which is always recommended before modding the phone), just restore it in TWRP.
Alternately, you can restore to stock with RUU. RUU will run fine with s-on with the following conditions:
1) Must be equal or greater main version (in getvar all, or OS version on hboot screen), hboot, etc. that is installed on the phone. In other words, no "downgrading" by RUU is allowed with s-on. So if you are on Lollipop firmware, you can only run the 4.28 AT&T RUU (not any of the previous ones).
Speaking of firmware, are you on the latest AT&T Lollipop firmware?
2) As you have somewhat determined, you must relock the bootloader to RUU. Relock with the command: fastboot oem lock
3) You can only run an AT&T RUU, not a RUU for another carrier version (but you may already know that).
4) Additionally, the RUU will wipe the phone, including internal storage. So backup any personal data you want to keep accordingly before RUU.
Another option (although not quite stock) is to use the following custom ROM. Its based on AT&T software (just debloated, optimized, etc.) and should therefore work correctly on AT&T's network: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
I ended up going the second option with the Rom by WNC.
I'm not 100% sure about the HD calling. First customer care told me they turned it off then I called again and the second told me it was off. Anyway to check?
Again, thanks for the help!:good:
grrrdn said:
I'm not 100% sure about the HD calling. First customer care told me they turned it off then I called again and the second told me it was off. Anyway to check?
Click to expand...
Click to collapse
Not that I am aware. If you were told by 2 different reps that its off, then that is prob the best you can do.
The problem did not occur if you manually switched off LTE (HSPA and GSM only)?
Did switching to WNC's ROM solve the incoming call issue?
Also, you didn't answer my question on whether you are on the Lollipop AT&T firmware?
A slight feeling this may be a different issue than the HD Voice problem, since:
1) Disabling HD Voice on your account did not solve the issue
2) You mentioned in your OP that SMS worked fine. Other folks with the HD Voice issue had problems sending/receiving SMS.
redpoint73 said:
Not that I am aware. If you were told by 2 different reps that its off, then that is prob the best you can do.
The problem did not occur if you manually switched off LTE (HSPA and GSM only)?
Did switching to WNC's ROM solve the incoming call issue?
Also, you didn't answer my question on whether you are on the Lollipop AT&T firmware?
A slight feeling this may be a different issue than the HD Voice problem, since:
1) Disabling HD Voice on your account did not solve the issue
2) You mentioned in your OP that SMS worked fine. Other folks with the HD Voice issue had problems sending/receiving SMS.
Click to expand...
Click to collapse
I was able to get calls if I manually switched to HSPA and I am running the latest lollipop firmware. Flashing WNC's Rom made everything work again. I'm guessing HD voice was switched off because when I call out, I am switched to hspa if I'm on LTE.
Not sure why the work around didn't work for me, probably unlucky
When I first got my HTC LTE was working fine then it suddenly stopped. I called T-Mobile who was clueless, so I popped the sim back into my S7 Edge and Nexus 6P age LTE worked perfectly. I decided to try unlocking s-off etc to flash a more current firmware since mine was on a really old one. I flagged 1.30xx stock then LeeDroid rom being sure to not decrypt data during the process. LTE still won't won't, I'm only getting HSPA+ which sucks. I have another sim card I could activate, but I want to know if there's another way to fix this? My APN seems fine, as does the preferred radio mode. Any suggestions/additional troubleshooting that I can do before sending the phone back
Update:
Here are some videos I made showing the issue:
Part 1
Part 2
I will add another one using the stock ROM to further prove the issue exists on both the unlocked firmware, and T-Mobile one.
You root your phone, mess it up and then send it back? Kinda messed up.
Did you try flashing the latest modem?
iamtimmah said:
You root your phone, mess it up and then send it back? Kinda messed up.
Click to expand...
Click to collapse
He said this happened before, and he tried rooted and flashing a ROM to see if it made a difference.
iamtimmah said:
You root your phone, mess it up and then send it back? Kinda messed up.
Click to expand...
Click to collapse
No, I stated the issue was there before then. I only unlocked it and flashed updated firmware in an attempt to fix the issue which it didn't. Clearly we all need to read thoroughly before responding to an OP so we don't look arrogant in the end.
Now, on another note I mentioned this issue was already present from the moment I started using the phone 100% stock. It will sometimes still get LTE, but it only sticks for 10-30 seconds then drops to H/H+ immediately. My S7 Edge and Nexus 6P do not have this issue whatsoever therefore I'm certain something with the firmware is not right.
geoff5093 said:
Did you try flashing the latest modem?
He said this happened before, and he tried rooted and flashing a ROM to see if it made a difference.
Click to expand...
Click to collapse
Thank you, for reading the OP , and no I don't have just the modem files, although I do have the RUU so I know it's in there
Pilz said:
When I first got my HTC LTE was working fine then it suddenly stopped. I called T-Mobile who was clueless, so I popped the sim back into my S7 Edge and Nexus 6P age LTE worked perfectly. I decided to try unlocking s-off etc to flash a more current firmware since mine was on a really old one. I flagged 1.30xx stock then LeeDroid rom being sure to not decrypt data during the process. LTE still won't won't, I'm only getting HSPA+ which sucks. I have another sim card I could activate, but I want to know if there's another way to fix this? My APN seems fine, as does the preferred radio mode. Any suggestions/additional troubleshooting that I can do before sending the phone back
Click to expand...
Click to collapse
Did you try 1.53 us unlocked ruu that's worth a try
bbell101584 said:
Did you try 1.53 us unlocked ruu that's worth a try
Click to expand...
Click to collapse
No, I can't get it to flash, but I'm going to try another method for updating it to that version
Mine has been extremely inconsistent in sticking to LTE. Sometimes I have to force it to LTE only and then when I switch back to GSM/WCDMA/LTE auto, it ****s the bed for a few minutes before correcting itself.
Pilz said:
No, I can't get it to flash, but I'm going to try another method for updating it to that version
Click to expand...
Click to collapse
Did you try downloading the ruu.exe on the computer and then running it as administrator also make sure you have either changed your cid to the US unlocked one or to supercid I used the exe version of the ruu it went fine on my end I hope you get your situation worked out
I don't know your phone model, but since you are in the US. I would suggest you run US unlocked RUU for eliminating any software issues.
If you have an unlocked device, then you can simply download from @Behold's thread about us unlocked RUU.
If you have a T-mobile device, I would suggest you to get s-off and then run RUU.
Send back your modified phone is likely the least preferred option to do/recommend.
bbell101584 said:
Did you try downloading the ruu.exe on the computer and then running it as administrator also make sure you have either changed your cid to the US unlocked one or to supercid I used the exe version of the ruu it went fine on my end I hope you get your situation worked out
Click to expand...
Click to collapse
I changed my CID/MID to the unlocked model, but the RUU app keeps giving me an error code 155 (I think that's what it was).
frankcck said:
I don't know your phone model, but since you are in the US. I would suggest you run US unlocked RUU for eliminating any software issues.
If you have an unlocked device, then you can simply download from @Behold's thread about us unlocked RUU.
If you have a T-mobile device, I would suggest you to get s-off and then run RUU.
Send back your modified phone is likely the least preferred option to do/recommend.
Click to expand...
Click to collapse
If you read the OP I do have S-Off and an unlcoked BL, but the RUU will not flash, what steps are you using to do it? I may have made a mistaken given how I normally flash my Shied or Nexus which are both really easy to do.
Pilz said:
I changed my CID/MID to the unlocked model, but the RUU app keeps giving me an error code 155 (I think that's what it was).
If you read the OP I do have S-Off and an unlcoked BL, but the RUU will not flash, what steps are you using to do it? I may have made a mistaken given how I normally flash my Shied or Nexus which are both really easy to do.
Click to expand...
Click to collapse
Boot into download mode and run RUU again.
frankcck said:
Boot into download mode and run RUU again.
Click to expand...
Click to collapse
That's exactly what I did, and I just confirmed the error code was "155 unknown error"
Pilz said:
I changed my CID/MID to the unlocked model, but the RUU app keeps giving me an error code 155 (I think that's what it was).
If you read the OP I do have S-Off and an unlcoked BL, but the RUU will not flash, what steps are you using to do it? I may have made a mistaken given how I normally flash my Shied or Nexus which are both really easy to do.
Click to expand...
Click to collapse
Did you right click the ruu.exe and choose to run as administrative that's the only thing else I can say maybe a more experienced person can help you further sorry
---------- Post added at 02:10 PM ---------- Previous post was at 02:09 PM ----------
Redownload the ruu or just try from a whole different computer if you have access to one
bbell101584 said:
Did you right click the ruu.exe and choose to run as administrative that's the only thing else I can say maybe a more experienced person can help you further sorry
Click to expand...
Click to collapse
Yep, following the instructions to the t (so to speak), it ran fine, booted into whatever that weird screen is with the % on it then after about 15 seconds gave me the error
I just gave the extSD method again, now it is saying
Code:
22 RU_HEADER_ERROR
22 RU_HEADER_ERROR
FAIL22 22 RU_HEADER_ERROR
Pilz said:
That's exactly what I did, and I just confirmed the error code was "155 unknown error"
Click to expand...
Click to collapse
I did not boot into download mode. Left it on the home screen, Just made sure USB debugging was on. The RUU handled everything after that.
Quick update:
I changed my CID to 111111 and it flashed via the RUU .exe file (surprisingly). I still cannot get LTE other than a ran moment where it might connect for a second before dropping back to H+. I even made a new APN (copied from my S7 Edge) and it still won't get LTE. Could this be some bizarre sim issue despite it working on every other phone I own (4 other phones work fine with LTE and my sim)?
Pilz said:
Quick update:
I changed my CID to 111111 and it flashed via the RUU .exe file (surprisingly). I still cannot get LTE other than a ran moment where it might connect for a second before dropping back to H+. I even made a new APN (copied from my S7 Edge) and it still won't get LTE. Could this be some bizarre sim issue despite it working on every other phone I own (4 other phones work fine with LTE and my sim)?
Click to expand...
Click to collapse
Have them re register the device on the network? The US unlocked base should work fine on TMOUS, I know as I have used it and both LTE, VoLTE, and WiFi calling fully work.
Mikee4fun said:
Looks like a sim issue. Try re seating the sim and if that does not work have TMO give you another sim from the store.
Click to expand...
Click to collapse
I have another sim, and I've reinserted it s few times now without success. I might call them and activate the other sim. It's just odd how it works flawlessly with LTE on every phone but this one.
I just bought a factory unlocked htc one m9 and plugged the sim card in.
After cache partition wipes, two hour-long customer support calls, a factory reset, and a bottle of Tylenol, nothing happened.
(Okay, I'm joking about the Tylenol.)
The big issues are that the only mobile network operator detected in settings is AT&T, and that I can not change any APN settings (though they are T-mobile anyway, so that shouldn't matter.)
The T-mobile rep and I both checked, and the phone IS compatible with the t-mobile data bands in my area, so there is no physical reason that it shouldn't work.
Any help with this would be massively appreciated!
iateapietod said:
I just bought a factory unlocked htc one m9 and plugged the sim card in.
After cache partition wipes, two hour-long customer support calls, a factory reset, and a bottle of Tylenol, nothing happened.
(Okay, I'm joking about the Tylenol.)
The big issues are that the only mobile network operator detected in settings is AT&T, and that I can not change any APN settings (though they are T-mobile anyway, so that shouldn't matter.)
The T-mobile rep and I both checked, and the phone IS compatible with the t-mobile data bands in my area, so there is no physical reason that it shouldn't work.
Any help with this would be massively appreciated!
Click to expand...
Click to collapse
I had a similar problem with my phone (developer edition) when I first put in the sim card. A phone restart with the sim in it solved it right off.
computerslayer said:
I had a similar problem with my phone (developer edition) when I first put in the sim card. A phone restart with the sim in it solved it right off.
Click to expand...
Click to collapse
Okay, I just tried that and it didn't help.
iateapietod said:
Okay, I just tried that and it didn't help.
Click to expand...
Click to collapse
Now that you've restarted, try going into the network settings and manually choosing T-Mobile.
(Settings, Mobile Data, Network operators, search for networks)
It doesn't find anything other than AT&T.
I'm guessing that choosing the automatic option dues any good.
My next move would be to redo the setup process.... probably by resetting the phone. I'm off to Google the issue and see if anything comes up.
[EDIT] Before you do that, double check that your network mode is set to GSM/WCDMA/LTE auto. Anything else will (artificially) limit you to 2G or 3G [/EDIT]
[EDIT #2] T-Mobile has the APN information for manual input. It may be worth trying to create a new APN profile to see if that makes a difference [/EDIT]
I tried both of those. Now I'm having issues even just connecting it to my computer over USB. (HTC site says there's a software update that I think might help, but the phone isnt detecting it)
iateapietod said:
I tried both of those. Now I'm having issues even just connecting it to my computer over USB. (HTC site says there's a software update that I think might help, but the phone isnt detecting it)
Click to expand...
Click to collapse
Ah. Probably worth applying the latest RUU. The executable is here - best to install it with your phone connected to your computer in download mode. Alternatively, you can use the SD card method, though you'll have to search around for the Android 7 Rui zip file.
computerslayer said:
Ah. Probably worth applying the latest RUU. The executable is here - best to install it with your phone connected to your computer in download mode. Alternatively, you can use the SD card method, though you'll have to search around for the Android 7 Rui zip file.
Click to expand...
Click to collapse
I think I'm going to have to use the SD card method - the m9 keeps disconnecting randomly over usb and if that happens during the install.... I'd really like to not brick the phone.
I've been looking around all over google and can't seem to find a .zip for the update, I found one in a thread on here (still can't link things yet, under ten posts) but the download site said file not found.
In addition, do I need to use S-Off before trying the update? In some of the forums that was mentioned but I think it was for a different version of the phone. HTC has the update files and doesn't say anything about it, but it also doesn't say anything about updating over SD card.
iateapietod said:
I think I'm going to have to use the SD card method - the m9 keeps disconnecting randomly over usb and if that happens during the install.... I'd really like to not brick the phone.
I've been looking around all over google and can't seem to find a .zip for the update, I found one in a thread on here (still can't link things yet, under ten posts) but the download site said file not found.
In addition, do I need to use S-Off before trying the update? In some of the forums that was mentioned but I think it was for a different version of the phone. HTC has the update files and doesn't say anything about it, but it also doesn't say anything about updating over SD card.
Click to expand...
Click to collapse
Head on over to the General forum and check out the thread by Flippy498 about stock ROMs. It should be a few posts in, but the zip file is linked!
For anyone else having this type of issue - even though they're all unlocked, some versions of the htc one m9 (potentially other phones by HTC as well) are produced in different regions. The Taiwanese version does not have band 12, and others potentially lack other bands.
iateapietod said:
For anyone else having this type of issue - even though they're all unlocked, some versions of the htc one m9 (potentially other phones by HTC as well) are produced in different regions. The Taiwanese version does not have band 12, and others potentially lack other bands.
Click to expand...
Click to collapse
Oh dear. I assumed that you were referring to the unlocked version sold directly from HTC, as opposed to a branded M9 (produced for a specific carrier & region) that had subsequently sim-unlocked.
computerslayer said:
Oh dear. I assumed that you were referring to the unlocked version sold directly from HTC, as opposed to a branded M9 (produced for a specific carrier & region) that had subsequently sim-unlocked.
Click to expand...
Click to collapse
That's fine, I assumed I was too. Thank you again for all of the help computerslayer!
iateapietod said:
That's fine, I assumed I was too. Thank you again for all of the help computerslayer!
Click to expand...
Click to collapse
My pleasure. Did you end up successfully getting the phone on T-Mobile?
computerslayer said:
My pleasure. Did you end up successfully getting the phone on T-Mobile?
Click to expand...
Click to collapse
Nope! I'm trying to unlock the lte bands before using S-off (just because it doesn't seem like anyone's tried it yet.) I'll post results as soon as I finish trying, but it's slow-going.