Hello all,
First post on XDA; I've been searching for this issue for the past 4 hours, and found very little. I hope I haven't missed anything.
Long Story
Had a rooted phone, tried to flash JellyBAM; worked, except that kernel got messed up (touchscreen didn't work). Problem remained even after restoring HTC Sense. I assumed it was b/c my phone still had S-ON.
After successfully running DirtyRacun on my Evo 4g LTE, I flashed JellyBAM 7.6.2 (using TWRP 2.4.4.0, wiped Dalvik, Cache, Factory Reset & System first). Everything worked fine, except that there is no mobile network whatsoever. When booting JellyBAM, it prompts me to activate my phone:
"A special call needs to be made to activate your phone service. After pressing 'Activate', listen to the instructions provided to activate your phone."
I do this, but the problem is that I get an automated message: "Your account is not authorized to make calls to this phone number. If you would like to have additional capabilities added to your account, please call Customer Service."
This is the same message I get trying to make any phone call. Nothing (data, calls, etc) works on the mobile network now. I called Sprint to see if they could simply de-active then reactive my phone, but it appears to them as already activated. The tech I spoke w/ thinks I may have deleted the Sprint programming.
This sounds plausible, but what's REALLY WEIRD is that *2 still dials Sprint perfectly, and holding 1 still tries to check voicemail. So clearly some aspects of it connect with Sprint still. I have no idea what's messed up, unfortunately.
I don't believe JellyBAM is the culprit here, b/c after DirtyRacun but before flashing JellyBAM, I still had this problem.
Helpful Info
Android Version: 4.2.2
Radio Version: 1.12.11.1119
Kernel version: 3.0.73-g5d13a2c
JellyBAM 7.6.2
Question
Is there anything I can do to fix this so that my phone can reconnect with and use Sprint's mobile network? I'd really like to preserve JellyBAM, S-Off, and Root, given the amount of time and effort it took to get those working. Thank you so much, any help would be greatly appreciated.
First, try updating your radio.
I'd say to RUU back to stock and see if the problem persists. If it does then take it to Sprint and they should give you a replacement if you have the YEP. I had a similar but not so screwey situation, a few actually, like yours and when I lost all network Sprint replaced my phone. I've always had success dialing my voicemail after attempted activations and then my phone would kick back in within about 15 minutes while keep texting and calling my home phone.
Sent from my EVO using xda app-developers app
Delakit said:
First, try updating your radio.
I'd say to RUU back to stock and see if the problem persists. If it does then take it to Sprint and they should give you a replacement if you have the YEP. I had a similar but not so screwey situation, a few actually, like yours and when I lost all network Sprint replaced my phone. I've always had success dialing my voicemail after attempted activations and then my phone would kick back in within about 15 minutes while keep texting and calling my home phone.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Thank you for your response, I really appreciate the help.
I updated my radio, which went smoothly, but unfortunately it didn't work. What's frustrating is that I don't even know what the problem is. I know it isn't the ROM I flashed (since it had the same problem on HTC Sense before I flashed JellyBAM). It seems to have started after DirtyRacun S-Off process.
I'm still pretty noob so I don't know what else besides radio it could be. I'm really reluctant to try and restore my phone to stock due to the amount of time I spent learning to root and S-Off it. Wouldn't want that to be in vain, though I might not have a choice at this point.
Is there something I should try next?
Daedalus146 said:
Thank you for your response, I really appreciate the help.
I updated my radio, which went smoothly, but unfortunately it didn't work. What's frustrating is that I don't even know what the problem is. I know it isn't the ROM I flashed (since it had the same problem on HTC Sense before I flashed JellyBAM). It seems to have started after DirtyRacun S-Off process.
I'm still pretty noob so I don't know what else besides radio it could be. I'm really reluctant to try and restore my phone to stock due to the amount of time I spent learning to root and S-Off it. Wouldn't want that to be in vain, though I might not have a choice at this point.
Is there something I should try next?
Click to expand...
Click to collapse
Flash back to a sense rom and update Profile and PRL if that doesn't work call Sprint and have them re-provision your phone
bigdaddy619 said:
Flash back to a sense rom and update Profile and PRL if that doesn't work call Sprint and have them re-provision your phone
Click to expand...
Click to collapse
Before calling sprint, Google the 4g lte dialer codes, I'm sure there is one that activates the wireless reactivation process (that was the case with my old gs3)
Sent from my HTC Evo 4g lte using Tapatalk 2
I know after achieving S-off, I had to call Sprint due to a security issue. I couldn't make calls or anything.
It was painless and took all of 5 minutes.
Sent from my EVO using xda app-developers app
Has anyone got HTC Watch to work on their phone? I keep getting a connection error. THis is on both my phone which I am running a debranded t-mobile device, and also my wifes which is completley stock. Any ideas would be appreciated.
NOPE. mine is failing as well. Cant get past the "Downloading License Agreement" I get a pop up box saying Connection Error - There was an error while communicating with the server.
I did open a tick with HTC support but that didnt do me any good.
I also checked with a HTC One in a TMO store and same issue with thiers.
fatduke720 said:
Has anyone got HTC Watch to work on their phone? I keep getting a connection error. THis is on both my phone which I am running a debranded t-mobile device, and also my wifes which is completley stock. Any ideas would be appreciated.
Click to expand...
Click to collapse
What is HTC watch?
HTCs store to buy and rent movies and tv shows..
My wife's is still not working. Hers is completely stock. Mine is now working I am HTC dev newest I think it's .17 maybe that's all this update fixed.
Sent from my HTC One using xda premium
Im T-Mobile stock. Checked it again just now and still not working for me.
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.
Hi everyone! I got this Unlocked ATT One M8 from someone, and i have a very old software on it, it's like the first one, and when i hit the update buton it tells me that the software is up to date. I am on other carrier than att. Does this matter? Can I update manually? Any help appreciated!
Not sure what the fix is but I had the same issue with mine. No matter what I did (changing date/time/timezone) nothing would make it work and it seemed like it would never check for updates just tell me that I am up to date right away. I ended up using the RUU that was posted in the general section and reinstalling everything.
For me it checks for updates, but after some seconds it tells me I am up to date
popab said:
I am on other carrier than att. Does this matter? Can I update manually?
Click to expand...
Click to collapse
It certainly does matter (carrier). AT&T is unique in this regard, in that you need to be connected to AT&T's network to get updates on their devices. One of the many reasons I recommend against getting AT&T devices (or for that matter, most US variants) if you aren't in the US.
RUU, as previously mentioned, if your best bet to update.
I am on the out of box firmware for the M9. I have gotten TWRP, Root and Badboys rom on my phone but am experiencing a very unusual problem of random Handsfree activations on any rom. I am aware that going onto the latest RUU is very difficult atm due to no S-Off, but I cannot find a solution as to why I am getting this happening. It causes the phone to go through half a set up phase and does a PRL and Profile Update. Are there any fixes or should I get a replacement for my M9? This problem really blows since I did the HTC Champions for my upgrade.
I was told switching sims might help but the new m9 uses a 63.05 sim versus the m8's 53.05 sim card and the site says they are incompatible.
I don't think it's that difficult, there are threads with the RUU and completely stock (x.xx.xxx.15) operating systems available if you need/want to start over from scratch. Assuming your out of the box software was 1.32.651.15
asacado said:
I am on the out of box firmware for the M9. I have gotten TWRP, Root and Badboys rom on my phone but am experiencing a very unusual problem of random Handsfree activations on any rom. I am aware that going onto the latest RUU is very difficult atm due to no S-Off, but I cannot find a solution as to why I am getting this happening. It causes the phone to go through half a set up phase and does a PRL and Profile Update. Are there any fixes or should I get a replacement for my M9? This problem really blows since I did the HTC Champions for my upgrade.
I was told switching sims might help but the new m9 uses a 63.05 sim versus the m8's 53.05 sim card and the site says they are incompatible.
Click to expand...
Click to collapse
My only other concern was if I updated to the latest firmware, if it would stop the constant sprint updates on a custom rom.
I Would try latest firmware first.
OMJ thinks all you need is to relock for RUU to work.
The RUU has the latest OTA.
I think OMJ mentioned something about Extra HFA's (before OTA).
Let us know how it goes.
it's a known bug on 1.32.651.17...it's fixed on 1.32.651.30...I was having the same issue, very irritating...especially when I was trying to s-off & HFA kept interrupting
I am still facing this problem even after the update. I'm running the latest bad boys rom on the most up to date firmware and rom even with s off I'm still getting this hfa problem
Mine doesn't even seem to want to activate at all. I updated to 1.32.651.30 and it will just sit there at HFA and fail eventually. This is very frustrating because I opened up a phone number to try it out and can't even use this thing. I actually work in wireless and in fact every M9 I've sold (only a few) had a HFA problem which I thought was Sprint's fault, but I guess not. I don't even want to sell them at this point, because when I sell the S6 they activate in like 10 seconds. Ugh.
I'm Wondering if it's a sim issue. Or if getting an international rom would help.
Just got off the phone with tech support and there is now a workaround for this issue until they fix it. What you need to do is go into Mobile Data settings and change the mode to 'CDMA Only' and let it activate, then set it back to 'LTE/CDMA'. Worked for me.