Any ideas? I have a Plain Jane rooted TB that has been stuck in 1X despite (in order):
- rebooting
- pulling battery
- restoring a known good saved ROM from ROM Manager
- toggling enable on RevA
- installing jcase's rooted 1.70.605 OTA and MR2 radio
- factory reset
I am in midtown Manhattan. I should have stellar 3G/4G. Is there anything left to do but return the phone to VZ?
Bluecat.NYC said:
Any ideas? I have a Plain Jane rooted TB that has been stuck in 1X despite (in order):
- rebooting
- restoring a known good saved ROM from ROM Manager
- toggling enable on RevA
- installing jcase's rooted 1.70.605 OTA and MR2 radio
- factory reset
I am in midtown Manhattan. I should have stellar 3G/4G. Is there anything left to do but return the phone to VZ?
Click to expand...
Click to collapse
You should check your settings and see if your mobile network is on(obvious answer and I feel like you have probably done that). Make sure you dont have any apps that are turning it off i.e. juicedefender or any other apps that control your mobile network. It could be the ROM you are using so try and use your stock ROM and see if you get 3G/4G in that. Make sure your SIM card is in properly. I do not know if that will be an issue but it could help. Also along with ROMs make sure the ROM you are using is friendly with the radio you are using. I can not think of much else. Google it too and search this forum or others that might help too! Good luck.
The simplest and most obvious possibility that still has to be asked: Do you have the back cover on the phone?
wichi2010 said:
You should check your settings and see if your mobile network is on(obvious answer and I feel like you have probably done that). Make sure you dont have any apps that are turning it off i.e. juicedefender or any other apps that control your mobile network. It could be the ROM you are using so try and use your stock ROM and see if you get 3G/4G in that. Make sure your SIM card is in properly. I do not know if that will be an issue but it could help. Also along with ROMs make sure the ROM you are using is friendly with the radio you are using. I can not think of much else. Google it too and search this forum or others that might help too! Good luck.
Click to expand...
Click to collapse
I have the Stock ROM w/corret radio and yes mobile is on, airplane mode off. Also tried pulling the battery. This sucker stuck on 1X for dear life.
FreemanB said:
The simplest and most obvious possibility that still has to be asked: Do you have the back cover on the phone?
Click to expand...
Click to collapse
yes, back cover is on
I had the same problem you did. I used Bamf 3.0 and flash the newest leak radio. My phone all of the sudden the next day dropped 3G. I went into the VZ store today and told them my sim card died and they gave me a new one. It working now, so I said unroot your phone like I did and get a new sim card. Make sure you update to their newest software before going into the store.
Seem like alot of people on the forum are saying they are not getting 3G/4G lately after the new radio that was out. I got my radio the day it was leak.
gammagogeta said:
I had the same problem you did. I used Bamf 3.0 and flash the newest leak radio. My phone all of the sudden the next day dropped 3G. I went into the VZ store today and told them my sim card died and they gave me a new one. It working now, so I said unroot your phone like I did and get a new sim card. Make sure you update to their newest software before going into the store.
Seem like alot of people on the forum are saying they are not getting 3G/4G lately after the new radio that was out. I got my radio the day it was leak.
Click to expand...
Click to collapse
Thanks. But I had my problem before I flashed the new radio. I've been using the original plain jane root from back in March. It worked two nights ago, was stuck in 1X the next morning.
Since I now have the new OTA stock is there an easy way to get it out of root or should I just follow the sticky instructions and go all the way back to original ROM?
Instead of taking it in you could also just give them(verizon) a call. I know they can see if your phone is rooted from there and many verizon workers have theirs rooted and might be able to help you!
Yeah mine worked 2 days ago too but yesterday it died I was using bamf for a while now. I flashed the radio before that too, all of the sudden it just dropped. The guy at VZ store told me that never happened before that a sim card just die like that.
wichi2010 said:
Instead of taking it in you could also just give them(verizon) a call. I know they can see if your phone is rooted from there and many verizon workers have theirs rooted and might be able to help you!
Click to expand...
Click to collapse
Thanks, but I spoke to VZ last night. The rep was nice and all but said the factory reset should fix the problem (it didn't) He said the next step would be to replace the phone. I might call again tonight to see if I can bump up the tech support ladder to someone more knowledgeable. Still hoping someone here could help me out.
Like I said, I had the original plain jane root that everyone did back in March when the phone came out. No reason for it to suddenly get stuck in 1X the other day.
Ive had that problem twice now. The first time my 4g antenna stopped working for whatever reason. I replaced the battery cover and it worked again for a few days. When it stopped again I called verizon and they sent me a new phone which is probably what youre gonna have to do.
So... VZ is next-day mailing me a new phone. I wanted to exchange it in the city but they said once you have the phone for more than 14 days exchanges have to be done by mail. Still, I'd love to know why the phone died.
Hello all,
I have had no data connection in the last few days. solid signal, but no data. i have done almost everything i can do and still the same result. switched back to Rev.A and i can get 3g "ok", not sure whats up. Any suggestions? I also reflashed the Mr2 radio and no change.
Another thought is my SIM card might have taken a dump. Id be willing to take it into verizon and get a new sim but dont want to unroot, revert to stock. got way to much going on with my phone to just start from scratch again : ( just so i can "try" if a new SIM would work. what would happen if i took my rooted thunderbolt into a verizon store for a new SIM card?. Would they Deny me service?or put a note on my account stating i have rooted and voided my warranty?. Just curious as to what would happen. they would deffidently notice right off the bat because of my sense 3.0 rom, kernal, gingerbread, signal icons,lock ring,signal bars, spash screen, boot animation and sound, etc...
need help guys! thanks in advance! : )
Well I know you said you don't want to but just make a nandroid backup before you unroot and stick it on your pc for safe keeping. Then when you are re-rooted just wipe everything and restore the backup and you are EXACTLY where you were before. Plus with Revolutionary re-rooting takes all of 5-10 minutes.
Sent from my HTC Thunderbolt
Talk to the guys there. Get a feel for them... The guys at the shops near me couldn't care less about a rooted device. As long as the software isn't the issue, which a bum SIM shouldn't be, they shouldn't really care. I'd feel them out a bit before assuming unrooting is a must. You might get lucky.
I will send this thread up. This is exactly the problem I am experiencing. The Thunderbolt has perfectly good network signal but data connection is not working. It complains about "SIM card not found" when entering the Settings and APNs. The SIM card is detected by the device otherwise, it's possible to save contacts to it and retrieve them. But 4G data is completely dead.
I visited a VZW store yesterday and received a new SIM card but the problem is still there. I have also tried to reflash to the latest leaked radio without any solution.
The ROM used is the latest Synergy Nightly.
I begin to consider the possibility of restoring the Thunderbolt back to stock and get a replacement but it would be good if this problem can be solved.
THUNDEROID said:
Hello all,
I have had no data connection in the last few days. solid signal, but no data. i have done almost everything i can do and still the same result. switched back to Rev.A and i can get 3g "ok", not sure whats up. Any suggestions? I also reflashed the Mr2 radio and no change.
Another thought is my SIM card might have taken a dump. Id be willing to take it into verizon and get a new sim but dont want to unroot, revert to stock. got way to much going on with my phone to just start from scratch again : ( just so i can "try" if a new SIM would work. what would happen if i took my rooted thunderbolt into a verizon store for a new SIM card?. Would they Deny me service?or put a note on my account stating i have rooted and voided my warranty?. Just curious as to what would happen. they would deffidently notice right off the bat because of my sense 3.0 rom, kernal, gingerbread, signal icons,lock ring,signal bars, spash screen, boot animation and sound, etc...
need help guys! thanks in advance! : )
Click to expand...
Click to collapse
Theres a issue with some roms not being desprinted enough and flashing them can corupt the vzw setup. Either flash back to orig and reroot or do the ##whatever and make sure your data config is right. If i helped and im sure i did click thanks
Sent from my ADR6400L using xda premium
Starting on Monday night 02/18/13 I was going through settings on my phone and accidentally selected Band 800 not knowing what I was doing. Immediately I noticed I was unable to send sms/mms. Later I discovered unable to send/receive calls. I can receive mms/sms and data works just fine.
The phone shows a 4g connection (cdma+lte) but if I switch to cdma it loses signal.
I have already spent the past 2 days on the phone with Verizon and HTC. Neither of them can figure out how to fix my problem. I have factory reset the phone, replaced SIM card with a new one, updated OS to ICS from http://forum.xda-developers.com/showthread.php?t=2136273 and updated the radio from the same post.
I used the DEBLOATED Rom Deodexed version: 7.02.605.06 710RD
Phone is rooted with Revolutionary.
After several more factory resets as directed by Verizon and HTC, the initial issue remains.
I rooted my phone in 2011 and have had zero issues til Monday when I selected that band 800 setting.
I am unable to receive a factory replacement due to the phone being quite worn and used. I am not willing to pay Verizon a $100 deductible to replace my phone (pointless having insurance if I have to dish out more $$$ to use it)
Please if anyone out there knows how to fix this...help me.
Go back to what you messed around with and see if you can change it back
If I hadn't already tried that and it worked, I wouldn't have made a thread on here. Verizon and HTC both can't even figure out why it won't work.
The craziest thing is I had switched service over to a different phone (HTC Imagio Windows Mobile) and still had the same issue. That phone isn't rooted or modified in any way. Had never been used til I took it out of the box and had Verizon change service over to it.
It is definitely something with Verizon and HTC phone on their end, not mine.
I am now on a 3 year old Blackberry Curve that isn't having any of the issues either of the HTC phones had.
Hmm strange but i remember back in september i flashed Newts sense 4.0 rom and it was too laggy so i went back to stock 2.1 and my data was out it had the 4g icon and everything and but it would timeout and my texts would come in late even though i tried many radios and even called verizon but no luck. In the end I went to the Rom Roll up thread and flashed the Froyo Ruu from Hboot and let it do its thing then i upgraded it all the way to Gingerbread rooted again with revolutionary and that fixed my radio problem might fix yours too im not sure just sharing my experience
I've got a rooted unlocked s-off AT&T M8. I took the 4.4.4 update, then promptly moved to ARHD 34.0. Didn't realize it at first, but I am no longer able to receive calls while on LTE. (works fine for data, and outgoing calls)
If I force it down to 3g, I'm fine. I also noticed that outgoing calls automatically kick it down to 3g- then learned that LTE calls are not an option yet for AT&T. What I'm trying to figure out is, how was I able to have my stock rom on AT&T in LTE mode and still receive a call?
I've checked all the APN settings and it all is set to recommended parameters on AT&T's website. Is this an Android Revolution HD issue? SIM issue? AT&T issue?
I'm going to have to back out of ARHD if there is no solution here, and that would suck.
thanks.
ARHD 34.0 is Android 5.0 based (software 4.16); not 4.4.4 (software 3.x). You might be experiencing this issue due to firmware mismatch. My advice would be to flash the US Dev Edition RUU or firmware zip to get on the 4.x based firmware, and see if that helps. You can try the Euro 4.16.401 firmware, but my experience the US Dev Edition (4.16.1540) plays better on AT&T (as its designed to work on AT&T's network).
Even with the proper firmware, some folks have also had some random network issues running an "international" based ROM on AT&T's network. Most notably losing Google services while on LTE (possibly due to build.prop differences). So its possible your LTE issue may be related. Not to knock the ROM developers, but devs from Europe and other regions often aren't that familiar with the nuances of AT&T's network.
So if being on the proper firmware still does not resolve the issue, it might be the ROM itself doesn't play well with AT&T in your location.
Thanks Redpoint-
I hadn't considered that and am also shy to using the Dev RUU due to brick risk but will reassess that. (I have to convert my device to GPE to put that on don't I?) I recall some warnings about bricking if I change the ID of my phone and apply the wrong RUU or something- but I'll have to refresh myself on those caveats. Would have been so much simpler if AT&T had just released Lollipop but who knows how long I'd be waiting for that.
Thanks again.
jeremyenos said:
Didn't realize it at first, but I am no longer able to receive calls while on LTE. (works fine for data, and outgoing calls)
If I force it down to 3g, I'm fine. I also noticed that outgoing calls automatically kick it down to 3g- then learned that LTE calls are not an option yet for AT&T. .
Click to expand...
Click to collapse
Voice over LTE (VoLTE) not being available yet should not be the cause. VoLTE is not currently available on most carrier worldwide. Its a very new technology, and deployment is still ongoing in most regions. Only a few Asian countries currently have VoLTE.
That being the case, voice calls should be kicking down to 3G. The lack of VoLTE should not prevent you from receiving calls. As mentioned, I believe the issue is either a firmware mismatch, or ROM not playing well on AT&T's network.
---------- Post added at 10:50 AM ---------- Previous post was at 10:46 AM ----------
jeremyenos said:
Thanks Redpoint-
I hadn't considered that and am also shy to using the Dev RUU due to brick risk but will reassess that. (I have to convert my device to GPE to put that on don't I?) I recall some warnings about bricking if I change the ID of my phone and apply the wrong RUU or something- but I'll have to refresh myself on those caveats. Would have been so much simpler if AT&T had just released Lollipop but who knows how long I'd be waiting for that.
Click to expand...
Click to collapse
No, you don't need to convert to GPE to run Dev Edition RUU. Dev Ed not the same as GPE. Dev Ed is Sense, just without the AT&T branding. The US Dev Edition Lollipop ROM is actually pretty sweet (what I am currently on via RUU).
You won't likely brick the device with RUU unless you run an RUU for the wrong device.
Changing CID is safe as long as you type the command properly.
There is always some tiny risk of a brick if you mess with things s-off, and flashing hboot and radio. But I wouldn't say the risk is any more than installing the OTA (which also replaces hboot and radio) as long as you follow instructions carefully, and do the proper research, and take the proper care while performing the steps.
So thanks redpoint for the advice-
Dev edition RUU installed just fine, and updated my radio and hboot as I had hoped. I go to restore ARHD, and it fails though... even fresh install of ARHD fails with some symlink error. I think after reading up on it that this is due to partition resizing that Dev edition does. So now I can't seem to find a way to get ARHD back on the device. I have no idea what to do to the partitions to restore them to something ARHD can use again if that's the problem, and I can't find anything about it on XDA or elsewhere.
Kind of surprised by this if I'm on the only one hitting the issue... all of the issues. To my knowledge, without a radio update, no AT&T m8 in America with ARHD 34 is going to be receiving incoming calls with LTE enabled. The only way to get a radio update is to use an RUU- of which dev edition is the only one. AT&T/HTC only releasing the 4.4.4 RUU for right now it seems, without the radio and hboot update.
Maybe I've got this all wrong somehow... I can't be the only ARHD m8 AT&T LTE USA user that wants to have incoming calls right? How has anyone else accomplished this?
Stuck with Cyanogenmod for now... slower, less stable than ARHD.
jeremyenos said:
Dev edition RUU installed just fine, and updated my radio and hboot as I had hoped. I go to restore ARHD, and it fails though... even fresh install of ARHD fails with some symlink error. I think after reading up on it that this is due to partition resizing that Dev edition does. So now I can't seem to find a way to get ARHD back on the device. I have no idea what to do to the partitions to restore them to something ARHD can use again if that's the problem, and I can't find anything about it on XDA or elsewhere.
Click to expand...
Click to collapse
You're still misunderstanding about Dev Edition (DE) versus GPE. Only GPE has different partitioning from Sense. DE is still Sense, and has the same partitioning scheme as the stock AT&T (and other carrier) Sense setup.
Don't know why you are having the issues restoring ARHD nandroid and even flashing ARHD. Wipe cache and try to re-install TWRP or try a different version. Then try a "clean install" (factory reset in TWRP) of ARHD.
Or you might have a case where the DE firmware does not play well with ARHD. You can try the 401 firmware, for which ARHD is based. But this might cause as many issues as it solves, as the US DE firmware usually plays better with AT&T's network than the international firmware. But it might be worth a try.
---------- Post added at 11:31 AM ---------- Previous post was at 11:27 AM ----------
jeremyenos said:
The only way to get a radio update is to use an RUU- of which dev edition is the only one. AT&T/HTC only releasing the 4.4.4 RUU for right now it seems, without the radio and hboot update.
Click to expand...
Click to collapse
Since you are s-off, you can flash any carrier's M8 firmware, or flash the radio independently. Although a side note that you should stay away from flashing anything for CDMA (Sprint & VErizon) M8's or dual SIM M8.
If you mean there is no updated LP radio intended for AT&T, aside from the DE RUU that you are currently on; than yes that is correct.
Has this been solved? Im experiencing the same thing. I updated my m8 to the latest at&t lollipop ota. And installed xenon rom. Now i just noticed im not getting any calls. Wife is pissed lol
redpoint had my problem pegged. Just had the wrong rom w/o the radio update I think. I needed to get the developer edition from here. After applying it, I could put ARHD back on and all was good. It's been awhile, but that's how I roughly remember it.
simpl3lang said:
Has this been solved? Im experiencing the same thing. I updated my m8 to the latest at&t lollipop ota. And installed xenon rom. Now i just noticed im not getting any calls. Wife is pissed lol
Click to expand...
Click to collapse
There is no true fix for this, that I know of. Only workaround: turn off LTE in phone settings, or contact AT&T to have HD Voice (what AT&T is calling Voice Over LTE) turned off for your account. The latter is probably the best workaround if you want to continue using non-ATT ROMs; since it allows you to still utilize LTE speeds for data, and HD Voice only works if both parties have devices that support the feature (and many folks don't at this time).
redpoint73 said:
There is no true fix for this, that I know of. Only workaround: turn off LTE in phone settings, or contact AT&T to have HD Voice (what AT&T is calling Voice Over LTE) turned off for your account. The latter is probably the best workaround if you want to continue using non-ATT ROMs; since it allows you to still utilize LTE speeds for data, and HD Voice only works if both parties have devices that support the feature (and many folks don't at this time).
Click to expand...
Click to collapse
thank you for the quick reply. i will call at&t right now. and i will throw in an update.
redpoint73 said:
There is no true fix for this, that I know of. Only workaround: turn off LTE in phone settings, or contact AT&T to have HD Voice (what AT&T is calling Voice Over LTE) turned off for your account. The latter is probably the best workaround if you want to continue using non-ATT ROMs; since it allows you to still utilize LTE speeds for data, and HD Voice only works if both parties have devices that support the feature (and many folks don't at this time).
Click to expand...
Click to collapse
Update: i called, and the nice customer service lady couldnt turn off the feature. She said its part of billing something something. Damn what to do now besides turning off lte.
Should i input some apn or something? Revert radio image to an older one? Go back to kitkat?
simpl3lang said:
Update: i called, and the nice customer service lady couldnt turn off the feature. She said its part of billing something something. Damn what to do now besides turning off lte.
Click to expand...
Click to collapse
Just call again, the CS rep probably just didn't know what they were talking about. I think another user mentioned you need to talk to tech support, not the front line CS reps. Turning off HD Voice with AT&T was confirmed by at least 2 other XDA members to work.
simpl3lang said:
Should i input some apn or something? Revert radio image to an older one? Go back to kitkat?
Click to expand...
Click to collapse
Swapping radios or APNs probably won't help. Not sure about reverting to Kitkat.
redpoint73 said:
Just call again, the CS rep probably just didn't know what they were talking about. I think another user mentioned you need to talk to tech support, not the front line CS reps. Turning off HD Voice with AT&T was confirmed by at least 2 other XDA members to work.
.
Click to expand...
Click to collapse
+1000000000000000000
i guess third time calling is the charm. the first 2 calls i made, they said they couldnt turn it off, saying it was restricted. but the third person i spoke to made me turn my phone off and when it restarted it worked. i can receive calls now.. he said he turned the hd lte off in his side by putting me back to the settings i had before hd voice was added.
thanks again.
edit:
i was actually looking at this prior to making my third call to at&t. maybe it could help others. worth a try? do it at your own risk...
If for some reason the HD Voice Calling option is disabled or inaccessible on your phone after updating to Android 5.1, then you can try the following steps to fix the issue.
Navigate to Settings > More > Cellular Networks and enable the toggle switch for Enhanced 4G LTE Mode. However, if the toggle is missing then follow the steps provided below:
1.Launch the Dialer app on your phone, and dial *#*#4636#*#*.
2.Choose Phone information.
3.Enable or select VoLTE Provisioned Flag.
4.Restart the phone.
5.Go to Settings " More " Cellular networks and toggle the switch for Enhanced 4G LTE Mode, and the HD Voice calling feature should now be activated on your device running Android 5.1.
i got as far as rebooting my phone but the toggle was still missing.
Was working on Insert Coin 4.4.4, flash to OTA 4.16 5.0.2 works fine then I flashed to latest Insert Coin 7.1.9 5.0.2 I tried the following step suggested on post #13 don't see option #3 after click Choose Phone Info.
By calling AT&T turn off HD Voice you'll sacrifice anything?
First call attempt, att technical rep had me turn off phone, 1min later turn it back on and it's working now! Yay!!!
Sent from my HTC One_M8 using Tapatalk
@simpl3lang @redpoint73 Soo glad I found this thread, this was driving me nuts on my m9 running ARHD. When I called ATT they were able to take care of it and turn it off. I cannot find the setting under the *#4636#*, nor under phone settings in ARHD, Is this a setting that developers forget to include in their ROMS?
tc3sean said:
@simpl3lang @redpoint73 Soo glad I found this thread, this was driving me nuts on my m9 running ARHD. When I called ATT they were able to take care of it and turn it off. I cannot find the setting under the *#4636#*, nor under phone settings in ARHD, Is this a setting that developers forget to include in their ROMS?
Click to expand...
Click to collapse
The reason you won't find it in settings, is that "HD Voice" (or I forget what the actual toggle is called) is not a feature on non-ATT ROMs. Its an ATT-specific branding of what is more broadly being calling "Voice over LTE" or VoLTE. Further, most (or at least many) carriers worldwide have not started deploying VoLTE yet (or just starting to do so), so that is another reason why you won't see such a toggle in settings on most ROMs.
Even if such a toggle was present, I'm skeptical whether it would resolve the problem being discussed. It seems there is something unique in the way that ATT is deploying VoLTE, that is screwing with "international" based ROMs. So my hunch is that unless the ATT-specific tweaks are applied, you would still have the voice/SMS issue on LTE.
redpoint73 said:
The reason you won't find it in settings, is that "HD Voice" (or I forget what the actual toggle is called) is not a feature on non-ATT ROMs. Its an ATT-specific branding of what is more broadly being calling "Voice over LTE" or VoLTE. Further, most (or at least many) carriers worldwide have not started deploying VoLTE yet (or just starting to do so), so that is another reason why you won't see such a toggle in settings on most ROMs.
Even if such a toggle was present, I'm skeptical whether it would resolve the problem being discussed. It seems there is something unique in the way that ATT is deploying VoLTE, that is screwing with "international" based ROMs. So my hunch is that unless the ATT-specific tweaks are applied, you would still have the voice/SMS issue on LTE.
Click to expand...
Click to collapse
I can confirm that getting AT&T to turn off HD Voice fixed the issue with me. I installed SkyDragon v10. I had to call twice and go through a lot of crap to get them to do it. The last guy told me he was going to put the "opt-out" code on my number, but that wasn't technically supposed to do it. He said he was putting in that I had "requested" to opt-out (I was taking the line that it just stopped working, as I didn't want to have to deal with any fallout about having rooted and flashed my phone, perhaps that wasn't necessary, idk). So, I think you might take the short cut by saying that you want to opt out of HD voice, and that your "Brother-in-law" just did it, so you know it works. If you stick to your guns, and ask for a technical person and don't let them say no to that, you can definitely get it done.
Thanks to all of the participants on this thread I am out of a tight spot and would like to offer up a few more observations that may be helpful to the next person.
I had an LG G3 running CM13 20160504 that became unstable and I had to replace with my wife's old HTC One m8 also running CM13 20160504 (also tried 20160510 and 20160511) which, like the other phones discussed in this thread, did not get incoming calls, in fact calls did not even roll over to my Google Voice number.
Thanks to this thread I tried forcing the phone to 3g, found that I got calls and then got AT&T to turn of VoLTE (aka HD Voice) and now I can get calls while running with LTE data.
Rather than a fire-hose of details I'll just say that it seems that the G3 would get incoming calls on LTE, and I would not get the first ring then it would ring on what the caller perceived as the second ring. Whenever I was on a call I would note that I was running in 3G, after the call it went back to LTE. I assumed that it was a bandwidth issue but now I think in that lag between the callers first ring and my first ring the phone was negotiating down to a 3G connection like an old school high speed modem negotiating a call with a slower modem (anyone remember those days?). It looks like my HTC does not have the ability to negotiate down or that it was been somehow hardwired not to as there is a flag in the test menu (*#*#4636#*#*) marked "TURN OFF VOLTE PROVISIONED FLAG" which has no effect, i.e. I can press it and the is a visible deflection indicating that the phone knows that the button was pressed but the button text does not change to indicate that a toggle has been effected, calls continue to not ring and even rebooting after pressing does not make any difference.
In summary, having AT&T turn off HD Voice has me working fine with the HTC On m8 on CM13 and I am grateful to all of you for the conversation that got me out of that corner.
So I tried to use a RUU for 5.1 update for AT&T. My device is unlocked being used under the T-Mobile network. I cannot get OTA updates. So when the RUU was occurring, the update failed and the phone was stuck on a download screen and it wouldn't load.
So I called HTC to help and they told me to hold down the power buttons w/ both the volume keys together. The phone seemed to start working with everything in tact, but then the phone constantly reboots. Especially when I play music, it makes static noises. I cannot seem to get it to be on for more than two minutes because it constantly restarts.
I plan on using my Uh-Oh carrier swap option to T-Mobile but rather fix it since it's a software issue and their troubleshooting doesn't seem to help.
Can anyone help me with my situation please? It's on 5.0.2 so far.
sounds like you didnt fully update with the RUU, try it again or you can do it the other way and flash the zip
Hello,
I didn't know where to post my problem and I'm not sure if it is worth creating another thread so here it is. I bought a new HTC ONE M9 ATT with stock software. Connecting to wifi, settings, system update and it says that there are no updates available for my phone. Why is that happening?
Thanks
dohcvtec said:
Hello,
I didn't know where to post my problem and I'm not sure if it is worth creating another thread so here it is. I bought a new HTC ONE M9 ATT with stock software. Connecting to wifi, settings, system update and it says that there are no updates available for my phone. Why is that happening?
Thanks
Click to expand...
Click to collapse
What software version is on the phone
Sent from my HTC One M9 using Tapatalk