Related
Hi guys,
Hoping someone can help, have bricked my Australian Optus stock One X. I have tried to follow all threads related to loading stock or custom roms from fastboot and am unable to. I still have CWM recovery 5.8.2.7 touch installed.
I had previously rooted it and installed Android Revolution HD 5.1.0 and seemed to be fine but was unstable and would crash and reboot in certain apps. In trying to revert back to stock I stupidly formatted the SD card, DUMB ASS!
I have downloaded stock rom 1.29.401.7-DUO, all-in-one rootkit, and the ARHD ROM and have tried to either:
1) flash ARHD with bootloader still unlocked, doesn't work
2) follow reflashing stock process ie flash stock recovery, relock bootloader, then flash stock ROM, and am getting stuck on just reflashing the stock recovery. When I try to open stock recovery it takes me to a black screen with a red ! in a triangle, this is with the bootloader relocked.
If anyone is able to help an enthusiast noob like me I'd be very appreciative and would also be more than willing to donate for the trouble.
MAKE SURE you have exactly the right RUU for your phone, whatever the rom was on you were using, ie, 1.26, 1.28, 1.29, you need the same version of RUU, i discovered the problem trying to flash RUUs and after 2 days finally got the correct one, thats when i realised, unlike on other phones, you cant downgrade the One X and when recovering it seems to prefer the one that matches what you were using.
Also make sure youre cid is supported in that RUU, ie, HTC 001, TMOB 054, etc etc, mine can only accept 401 roms, so they must match exactly, until we can get S-Off this problem will remain, dont worry about recovery, so the guide on in case of disaster, you cant go wrong with it, relock your bootloader and get your RUU installed, from their update it to your latest ics version and then if you must reflash your cwm and root it.
Thanks for the info, graemeg. After downloading an RUU that was .exe file, I felt I was getting closer, as it was an AU Optus RUU. But it turns out that my current version is 1.28.980.10 and the RUU version was 1.26.980.3 and so yes I met with the non-downgrading issue.
It seems that there is not currently a stock 1.28.980.10 RUU at the moment, so might be using this as an ornament for much longer than I would have hoped/thought. Bummer.
agentorange82 said:
Thanks for the info, graemeg. After downloading an RUU that was .exe file, I felt I was getting closer, as it was an AU Optus RUU. But it turns out that my current version is 1.28.980.10 and the RUU version was 1.26.980.3 and so yes I met with the non-downgrading issue.
It seems that there is not currently a stock 1.28.980.10 RUU at the moment, so might be using this as an ornament for much longer than I would have hoped/thought. Bummer.
Click to expand...
Click to collapse
You can get 1.28.980.10 from htcdev downloads. I would link but I'm a new user, just filter by One X, Optus, and it's there.
Thanks again for the help. I have seen those files on htcdev website, but don't know how to use them
I don't know how to load a RUU that is not a .exe file...if anyone is able to assist, again, I would really appreciate it and will donate once up and running again.
Edit: I just wanted to add that I have tried to follow the thread that explains how to load/flash recovery and boot images via fastboot in command prompt, and have not been able to. So I don't think I'm a complete dumb ass, but do need someone with the knowledge and patience to guide me through it. Please!
First thing first, do you have the right RUU with you ?
If not, maybe this is the one for you : http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.103.14_release_258004_signed.exe
second: do you have fastboot directory set up on your pc ? and htc usb driver too ?
Just starting the download now, I think that could be the RUU I've been looking for. Yes I have the drivers and fastboot directory. Will give this RUU a go and let you know, thanks for the quick reply, ckpv5!
Most important before you run the RUU, you need to:
1) have a stock recovery flashed to you your device first (I believe you already have one)
2) relock the bootloader - fastboot oem lock
3) run RUU, it should work.
THANK YOU!
ckpv5, thank you for the link to the updated RUU. Phone is functioning again, stock. Donation coming your way. Thanks for all your help. agentorange82.
Hey guys,
First post and thread, unfortunately. May have been done before, so sorry if that's the case (and if it is I guess a quick link can clear this confusion up!)
I've got a tmobile HTC One M8 running Android 4.4.4 with an unlocked boot loader, clockworkmod 6.0.4.8 with s-on.
New android update is out and while I'm not necessarily keen on updating it, the icon is annoying. As well, I originally rooted the phone for some apps and sorts that I don't even use and I'm mainly interested in just bringing the phone back to a stock recovery so I can unroot it.
Tried using the RUU posted but I believe due to the s-on and unlocked boot loader, it doesn't work for me. Step one is an error on it.
What can I do here to bring the phone back to stock recovery? I'm not 100% I made a backup before I put cwm on it. May have but for arguments sake let's say I didn't.
Any and all help is appreciated. thanks so much everyone.
Metilinos said:
Tried using the RUU posted but I believe due to the s-on and unlocked boot loader, it doesn't work for me. Step one is an error on it.
Click to expand...
Click to collapse
RUUs run fine with s-on, and I don't know why folks keep posting that it doesn't.
But you do however, need to relock the bootloader (since you are s-on) to run the RUU. Its absolutely mandatory (with s-on), and almost certainly why the RUU fails. THe RUU also needs to match your CID (but if you are properly trying a T-Mob RUU on a T-Mob version M8, that is not the issue), and further you cannot "downgrade" or run an older version RUU (older hboot) than what is on the phone.
But again, unlocked bootloader alone will make the RUU fail.
I haven't really seen a whole lot of s-off since firewater hasn't worked any longer. I kind of figured the unlocked bootloader was an issue as well. Mobile right now and working so not a whole lot I can do. Basically make sure the CID matches the RUU and relock the bootloader and I should be good to go? I picked up the T-Mobile RUU and I have a tmobIle M8, I didn't really think to check the CID, I just mainly assumed the failed run was from other sources.
Metilinos said:
I haven't really seen a whole lot of s-off since firewater hasn't worked any longer. I kind of figured the unlocked bootloader was an issue as well. Mobile right now and working so not a whole lot I can do. Basically make sure the CID matches the RUU and relock the bootloader and I should be good to go? I picked up the T-Mobile RUU and I have a tmobIle M8, I didn't really think to check the CID, I just mainly assumed the failed run was from other sources.
Click to expand...
Click to collapse
As long as you have the right carrier RUU, the CID will also match. I assume T-Mobile US? As there is also T-Mobile in Europe.
As long as its right carrier (CID) and not trying to run an older version RUU, the unlocked bootloader is the only problem.
Yes T-Mobile US.
I'll have to double check the RUU, I'm pretty sure I grabbed it off here from a different thread, but like you said, the unlocked bootloader obviously was an issue.
In the case, and I'm assuming it's rare, that it could be that, is there an easy way to tell whether or not I have the most current RUU?
Thanks a bunch, really appreciating the help. I've been kind of at a standstill with this and haven't really tried much in fear of killing the phone.
Metilinos said:
In the case, and I'm assuming it's rare, that it could be that, is there an easy way to tell whether or not I have the most current RUU?
Click to expand...
Click to collapse
Do you mean its rare to run the wrong version RUU? If so, I'd say no, its not rare at all. Folks are often not aware of the version requirement (with s-on, this requirement is bypassed with s-off) and try to run an "old" RUU.
All the T-Mob US RUUs are posted here: http://forum.xda-developers.com/showthread.php?t=2714456
3.32 is Android 4.4.4
4.20 is Android 5.0
3.32 is what I have at the moment. With android 5 coming over the air a week or so ago for myself and 4.4.4 being on the phone when I got it just a couple months back, that's what I guess I was insinuating by rare. But thank you a bunch for your help. Again it's very much appreciated. Obviously got myself in a little over my head here.
I've been having a hell of a time trying to unroot my HTC One M8... It was an AT&T one I converted to Skydragon GPE, S-off. All the resources I try to use keep on failing somehow—anyone have suggestions? There's a million different tutorials on how to do it and none of them seem to work for me, getting really frustrated...
(I would link the below guides I've been trying to follow but I'm too new a user so it won't let me):
- The Unlockr guide: The Hassoon toolkit no longer exists.
- DroidViews guide: Everything's good until I try to restore the RUU image, then the executable fails with no explanation. Same when flashing the RUU from HTC's website.
- Restoring from a Nandroid backup in TWRP: Also never makes it through the entire process, I'd have to rerun it to see what the particular error was.
Ughhh is there any definitive set of steps I can take to actually restore to default settings? Preferably with the tampered flags not tripped, but honestly I don't even care at this point... Do I need to flash some stock AT&T HTC One M8 firmware or something before doing this all? Where might I be going wrong? I know it's vague but I'd love a solid walkthrough.
Thanks everyone
The simplest way would be to get an RUU from htc.com for AT&T, putting your phone in fastboot mode (power off, then pressing power+volume down, and selecting "fastboot"), and then simply launching the ruu. It should restore your phone to nearly being stock, except for your CID number and s-off. There are tutorials on how to change your cidnumber, however i am not sure how to turn s-off back to s-on.
http://www.htc.com/us/support/rom-downloads.html here you can find appropriate downloads
Ok, firstly, you might check out this thread: http://forum.xda-developers.com/showthread.php?t=2733523
None of the instructions require the use of anything beyond fastboot/adb. Also, make sure you put your CID/MID back if you changed them to run GPE. That isn't required to run Skydragon, but if you have altered them, put them back. Then rerun the RUU. Finally, since you are S-off, you can trivially fix any flags, so don't worry about that. (Running the RUU successfully will clear the modified flag anyway)
jshamlet said:
Ok, firstly, you might check out this thread: http://forum.xda-developers.com/showthread.php?t=2733523
None of the instructions require the use of anything beyond fastboot/adb. Also, make sure you put your CID/MID back if you changed them to run GPE. That isn't required to run Skydragon, but if you have altered them, put them back. Then rerun the RUU. Finally, since you are S-off, you can trivially fix any flags, so don't worry about that. (Running the RUU successfully will clear the modified flag anyway)
Click to expand...
Click to collapse
So I did this, starting from the Skydragon Sense 7 ROM:
made nandroid backup
flash 1.54.401.5 firmware
set cid to CWS__001
run RUU for the latest AT&T one. It says it will update from 1.54.401.5 to 2.6.502.16.
Result? Error 155 "Unknown Error", no other information.
Any ideas?
osdiab said:
I've been having a hell of a time trying to unroot my HTC One M8... It was an AT&T one I converted to Skydragon GPE, S-off.
Click to expand...
Click to collapse
Did you actually "fully convert" to GPE, or just flash Skydragon GPE?
What color is your hboot screen?
What hboot number, radio number?
osdiab said:
- The Unlockr guide: The Hassoon toolkit no longer exists.
Click to expand...
Click to collapse
The toolkit still exists. But it hasn't been updated in a very long time, and will therefore cause many many issues. So don't use the toolkit!
osdiab said:
- DroidViews guide: Everything's good until I try to restore the RUU image, then the executable fails with no explanation. Same when flashing the RUU from HTC's website.
Click to expand...
Click to collapse
Don't know what guide that is, or what RUU it tells you to use; but be aware that there are many RUU versions for the M8, and the RUU needs to be the proper one for your CID and MID. Also, Win7 or 8.1 is recommended (Win8 and especially Win10 will cause the RUU to fail).
redpoint73 said:
Did you actually "fully convert" to GPE, or just flash Skydragon GPE?
What color is your hboot screen?
What hboot number, radio number?
The toolkit still exists. But it hasn't been updated in a very long time, and will therefore cause many many issues. So don't use the toolkit!
Don't know what guide that is, or what RUU it tells you to use; but be aware that there are many RUU versions for the M8, and the RUU needs to be the proper one for your CID and MID. Also, Win7 or 8.1 is recommended (Win8 and especially Win10 will cause the RUU to fail).
Click to expand...
Click to collapse
hboot screen is white. hboot number is 3.19.0.0000. radio number is [email protected] I was using windows 8.1, though the computer I was using only has USB 3.0 ports (Apparently people say 2.0 is better?)
This is on the firmware that I was using for Skydragon, I can reflash the other firmware I had used for the failed RUU upgrade if that would be useful.
osdiab said:
hboot screen is white. hboot number is 3.19.0.0000. radio number is [email protected]
This is on the firmware that I was using for Skydragon, I can reflash the other firmware I had used for the failed RUU upgrade if that would be useful.
Click to expand...
Click to collapse
I'd leave it alone, and just try running the RUU.
osdiab said:
I was using windows 8.1, though the computer I was using only has USB 3.0 ports (Apparently people say 2.0 is better?)
Click to expand...
Click to collapse
Yes, folks have reported issues with RUU and USB 3.0. You can always try, the worst that will happen is the PC won't be able to talk to the phone.
Another user mentioned you can "disable" USB 3.0 in settings, but I'm not familiar with that.
redpoint73 said:
I'd leave it alone, and just try running the RUU.
Yes, folks have reported issues with RUU and USB 3.0. You can always try, the worst that will happen is the PC won't be able to talk to the phone.
Another user mentioned you can "disable" USB 3.0 in settings, but I'm not familiar with that.
Click to expand...
Click to collapse
OK, I've tried doing it on a computer that has USB 2.0 ports and once again, no go.
Trying to run the Developer/Unlocked RUU on HTC's website, it's stuck forever at 0/7 sending.
Trying to run the AT&T one, it errors out with a 155: Unknown Error message as soon as it boots to RUU mode.
Any other thoughts?
osdiab said:
Trying to run the AT&T one, it errors out with a 155: Unknown Error message as soon as it boots to RUU mode.
Click to expand...
Click to collapse
I think this means you need to relock your bootloader (required to RUU with s-on).
Hey so here's my situation:
Installed the CM Nightly on my AT&T One M9, didn't like it, so I tried to revert to stock. I didn't want to pay $25 to S-OFF so I just tried installing various RUUs, but none would work. I read somewhere that I needed to relock my bootloader in order for the RUUs to work, so I did that, and now my phone just boots to Recovery Mode. I've tried installing AT&T RUU 2.6.502.16 (which didn't work because my phone is on a more recent firmware) and reinstalling 2.11.502.18/flashing its 0PJAIMG.zip (which didn't work because it's apparently broken). I've even tried installing T-Mobile's 2.11.531.19 RUU, which of course didn't work because my CID doesn't match and I can't change it because I'm S-ON.
I realize I went about this very badly almost from the start--no stock backup in TWRP, etc. This is my first Android phone so I've been learning this as I go and I was a bit sloppy.
I'm pretty sure I'm screwed, at least until a new update comes out or the current AT&T RUU is fixed, but I'm wondering if there's something else I can try. Any ideas? Thanks.
StageProps said:
Hey so here's my situation:
Installed the CM Nightly on my AT&T One M9, didn't like it, so I tried to revert to stock. I didn't want to pay $25 to S-OFF so I just tried installing various RUUs, but none would work. I read somewhere that I needed to relock my bootloader in order for the RUUs to work, so I did that, and now my phone just boots to Recovery Mode. I've tried installing AT&T RUU 2.6.502.16 (which didn't work because my phone is on a more recent firmware) and reinstalling 2.11.502.18/flashing its 0PJAIMG.zip (which didn't work because it's apparently broken). I've even tried installing T-Mobile's 2.11.531.19 RUU, which of course didn't work because my CID doesn't match and I can't change it because I'm S-ON.
I realize I went about this very badly almost from the start--no stock backup in TWRP, etc. This is my first Android phone so I've been learning this as I go and I was a bit sloppy.
I'm pretty sure I'm screwed, at least until a new update comes out or the current AT&T RUU is fixed, but I'm wondering if there's something else I can try. Any ideas? Thanks.
Click to expand...
Click to collapse
I downloaded and flashed the 2.11.502.18 ruu from the HTC website with no problem. Ate you getting an error?
Edit: in my experience, if an ruu.exe starts to run and then never does (like you get the spinning wheel for a minute and then nothing) it's either a bad download or antivirus is blocking the file. But just to repeat...the exe on the HTC website works fine. I used it about three weeks ago.
Hm. Out of the myriad RUU.exes I've tried the most recent AT&T one was the only one I couldn't get to start, and when I tried installing it via .zip it would just restart the phone and nothing else. That in combination with other posts I've seen on this forum saying it's borked (although I might have misread the numbers/misinterpreted the jargon) just lead me to think it was broken. I'll redownload and try again. Thanks!
Edit: Well, it worked! I don't know what I was doing wrong. Thanks a lot!
I have a Dev edition M8 that i zip RUU'ed back to lollipop. i took a security update successfully, then the 3 preinstall updates in prep for marshmallow. however, I now get an error when taking the actual OTA for marshmallow. I am s-off and bootloader unlocked. I then downloaded the RUU from HTC to run the exe, but i always get error 155. I read @Sneakyghost post about firmware and it said it was either region ID's not matching, or the bootloader being unlocked. I don't see why the unlocked bootloader would be a problem when im s-off and its a dev edition, which is bootloader unlocked out of the box. Anyone know what is causing this?
fyarf said:
I have a Dev edition M8 that i zip RUU'ed back to lollipop. i took a security update successfully, then the 3 preinstall updates in prep for marshmallow. however, I now get an error when taking the actual OTA for marshmallow. I am s-off and bootloader unlocked. I then downloaded the RUU from HTC to run the exe, but i always get error 155. I read @Sneakyghost post about firmware and it said it was either region ID's not matching, or the bootloader being unlocked. I don't see why the unlocked bootloader would be a problem when im s-off and its a dev edition, which is bootloader unlocked out of the box. Anyone know what is causing this?
Click to expand...
Click to collapse
Haha nice man I just finished downloading that exact RUU and I have that exact phone in the exact same state. I got it from someone in the US.
I'll let you know how it goes on mine...
Sneakyghost said:
Haha nice man I just finished downloading that exact RUU and I have that exact phone in the exact same state. I got it from someone in the US.
I'll let you know how it goes on mine...
Click to expand...
Click to collapse
heres my recovery message, just to maybe help troubleshoot it. it mentions userdata being busy (i got an error in the zip ruu flash for userdata, had to flash the ruu zip twice to get an okay), then kidmode missing. not sure what to do besides flash the firmware from http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
Modified system apps, sir. That's what it is. Did you root your system?
Edit:
Maybe not. Maybe just can't find those apps cuz it can't mount data.
Something wrong there.
No idea.
I'll see where I end up.
Sneakyghost said:
Modified system apps, sir. That's what it is. Did you root your system?
Edit:
Maybe not. Maybe just can't find those apps cuz it can't mount data.
Something wrong there.
No idea.
I'll see where I end up.
Click to expand...
Click to collapse
i did a factory reset from stock recovery, and kid mode is present now, maybe im onto something...
Edit: not rooted directly from a factory ruu zip (well, hopefully the zip creator did a factory dump and was unmodified) but kid mode wasnt an option before the factory reset
fyarf said:
i did a factory reset from stock recovery, and kid mode is present now, maybe im onto something...
Edit: not rooted directly from a factory ruu zip (well, hopefully the zip creator did a factory dump and was unmodified) but kid mode wasnt an option before the factory reset
Click to expand...
Click to collapse
Unfortunately, I'm with family tonight and won't be able to assist until much later. But note this: the factory reset could well help. I can explain later.
Sneakyghost said:
Unfortunately, I'm with family tonight and won't be able to assist until much later. But note this: the factory reset could well help. I can explain later.
Click to expand...
Click to collapse
ok so i got mine to work.. apparently the zip RUU isnt good. i ran the exe 4.16.1540.8 from here http://forum.xda-developers.com/showthread.php?t=2701376 and then updated ota from there without issue. so my guess is the RUU zip wasnt perfect system-wise,while the exe is straight from htc.
fyarf said:
ok so i got mine to work.. apparently the zip RUU isnt good. i ran the exe 4.16.1540.8 from here http://forum.xda-developers.com/showthread.php?t=2701376 and then updated ota from there without issue. so my guess is the RUU zip wasnt perfect system-wise,while the exe is straight from htc.
Click to expand...
Click to collapse
ok. Where you got that zip from? Cuz I downloaded the 6.xx RUU.exe straight from HTC USA...
Sneakyghost said:
ok. Where you got that zip from? Cuz I downloaded the 6.xx RUU.exe straight from HTC USA...
Click to expand...
Click to collapse
zip was from the same thread, i tried the exe instead because it was an HTC file instead of a contributor. now on MM sense. The 6.xx RUU refused to work no matter what i did, so i OTA'd to the latest version.
fyarf said:
zip was from the same thread, i tried the exe instead because it was an HTC file instead of a contributor. now on MM sense. The 6.xx RUU refused to work no matter what i did, so i OTA'd to the latest version.
Click to expand...
Click to collapse
I seem to be having an entirely different problem. After swapping cables, phones and laptop ports as well as updating drivers, it appears that the usb port of my M8 is broken. I'll have to see at someone else's computer, maybe tomorrow. Pretty frustrating right now as I'm liking the M8 better than my M9 and M7.
[EDIT]
I could stabilize the connection enough to run another, international RUU. The RUU worked fine while the 6.12.1540.4 kept getting stuck at either "checking header" or "sending" - both times with a successfully established connection. I already tweeted HTC asking to have that RUU checked. I assume your findings were correctly indicating a bad RUU, since a.) It also didn't work here and b.) people from my team have confirmed seeing several fail scenarios with that RUU spread over XDA.
Guess that's that then. Thanks for raising the issue. I would have messed around with it much longer otherwise since the error messages are not clearly pointing towards a broken RUU.
[EDIT]
More updates: searching the M8 forum for 6.12.1540.4 turned up this: http://forum.xda-developers.com/showthread.php?p=64320571
That'd mean the RUU fails at the hboot pre-update reboot. All that's needed apparently is to flash only the hboot manually first, so it can proceed. Hence also error 155 which usually indicates issues with the system image. You experienced that most likely because the older hboot couldn't extract the system.img from the rom.zip.
Usually, the procedure is:
RUU updates hboot
RUU reboots to boatloader
RUU updates rest of firmware
RUU sends over the system image in parts
Hboot now decrypts and flashes the part.zips
It just looks like mandatory hboot-first-flash didn't happen right, either not rebooting after it or not flashing it at all.
However, this seems to be fixable by running the hboot/firmware package first and then the complete RUU.
Sneakyghost said:
I seem to be having an entirely different problem. After swapping cables, phones and laptop ports as well as updating drivers, it appears that the usb port of my M8 is broken. I'll have to see at someone else's computer, maybe tomorrow. Pretty frustrating right now as I'm liking the M8 better than my M9 and M7.
[EDIT]
I could stabilize the connection enough to run another, international RUU. The RUU worked fine while the 6.12.1540.4 kept getting stuck at either "checking header" or "sending" - both times with a successfully established connection. I already tweeted HTC asking to have that RUU checked. I assume your findings were correctly indicating a bad RUU, since a.) It also didn't work here and b.) people from my team have confirmed seeing several fail scenarios with that RUU spread over XDA.
Guess that's that then. Thanks for raising the issue. I would have messed around with it much longer otherwise since the error messages are not clearly pointing towards a broken RUU.
[EDIT]
More updates: searching the M8 forum for 6.12.1540.4 turned up this: http://forum.xda-developers.com/showthread.php?p=64320571
That'd mean the RUU fails at the hboot pre-update reboot. All that's needed apparently is to flash only the hboot manually first, so it can proceed. Hence also error 155 which usually indicates issues with the system image. You experienced that most likely because the older hboot couldn't extract the system.img from the rom.zip.
Usually, the procedure is:
RUU updates hboot
RUU reboots to boatloader
RUU updates rest of firmware
RUU sends over the system image in parts
Hboot now decrypts and flashes the part.zips
It just looks like mandatory hboot-first-flash didn't happen right, either not rebooting after it or not flashing it at all.
However, this seems to be fixable by running the hboot/firmware package first and then the complete RUU.
Click to expand...
Click to collapse
I'm not sure about OP, but that worked perfectly for me. I wonder how HTC let a broken RUU.exe past testing?
Double_a2013 said:
I'm not sure about OP, but that worked perfectly for me. I wonder how HTC let a broken RUU.exe past testing?
Click to expand...
Click to collapse
They frequently do. Nothing exciting. That's why I notified HTC. They take their time with fixing them. The earlier the better.
Sneakyghost said:
They frequently do. Nothing exciting. That's why I notified HTC. They take their time with fixing them. The earlier the better.
Click to expand...
Click to collapse
Wow, I didn't realize that. Now if only they'd fix the ATT LTE issues on the dev rom :silly:
Double_a2013 said:
Wow, I didn't realize that. Now if only they'd fix the ATT LTE issues on the dev rom :silly:
Click to expand...
Click to collapse
My ota to the latest dev version got lte on at&t no problem, sure your apn settings are correct?
fyarf said:
My ota to the latest dev version got lte on at&t no problem, sure your apn settings are correct?
Click to expand...
Click to collapse
I've never had to reconfigure them before, regardless of if I'm using GPE or Sense RUUs. I'll give it another shot, and get back in a more timely manner
Edit: Apn settings seem fine. It's using the Nextgenphone one from ATT
Edit #2:
http://forum.xda-developers.com/att...ming-calls-lte-mode-m8-att-arhd-34-0-t3026710
Found this thread about a similar issue. I guess I'll disable HD Voice (Honestly, its borderline useless anyway) and see if that solves anything