I've been doing a bit of reading on the steps to flash a custom ROM on the EVO LTE. To summarize my findings (and please correct me if I'm wrong about any of the following): I've noted that there is currently no way to achieve S-OFF with newer hboot (1.15 and 1.19), but you can still unlock the bootloader with HTC's official method. The disadvantage being (other than the red disclaimer splash screen at boot time) that you cannot flash a new radio firmware with HTC's official unlock method, where as you can with S-OFF.
So my question is, under what circumstances would you want to flash a new radio firmware?
During OTA's theres usually a new radio released. That is supposed to help with various connections (data, wifi, LTE) depending on whats updated.
morfinx said:
I've been doing a bit of reading on the steps to flash a custom ROM on the EVO LTE. To summarize my findings (and please correct me if I'm wrong about any of the following): I've noted that there is currently no way to achieve S-OFF with newer hboot (1.15 and 1.19), but you can still unlock the bootloader with HTC's official method. The disadvantage being (other than the red disclaimer splash screen at boot time) that you cannot flash a new radio firmware with HTC's official unlock method, where as you can with S-OFF.
So my question is, under what circumstances would you want to flash a new radio firmware?
Click to expand...
Click to collapse
You mainly just want to make sure that you're radio is from the same firmware version as the base of the ROM you're running. So if your ROM is based on the 1.22.651.3 software, you would ideally want the radio from the same OTA. It's generally not required, but you could have compatibility issues when running different versions.
Sent from my EVO LTE
Rxpert said:
During OTA's theres usually a new radio released. That is supposed to help with various connections (data, wifi, LTE) depending on whats updated.
Click to expand...
Click to collapse
premo15 said:
You mainly just want to make sure that you're radio is from the same firmware version as the base of the ROM you're running. So if your ROM is based on the 1.22.651.3 software, you would ideally want the radio from the same OTA. It's generally not required, but you could have compatibility issues when running different versions.
Sent from my EVO LTE
Click to expand...
Click to collapse
So if I'm running a custom ROM, that means I can't get an OTA update right? In that case, if I used HTC's official unlock method and can't flash a new radio separately on my own, how do I get the new radio?
morfinx said:
So if I'm running a custom ROM, that means I can't get an OTA update right?
Click to expand...
Click to collapse
If you're running a custom ROM, you *might* be able to receive/download the OTA, but it will not update properly because the recovery mode, the OTA checks all/most of the files in /system/app and /system/framework to verify they haven't been modified since the previous OTA before applying the new OTA. This check will definitely fail if any of the files have been modified in /system/app and /system/framework, which most custom ROMs make at least some minor modifications to the files in these directories.
morfinx said:
In that case, if I used HTC's official unlock method and can't flash a new radio separately on my own, how do I get the new radio?
Click to expand...
Click to collapse
Essentially, you'll have to get back to some form of stock to allow the stock bootloader to process the radio image contained in the OTA/RUU. There might be a better way to approach this, but off the top of my head, I'd make a nandroid backup of everything, re-lock the bootloader, run the RUU from the latest OTA/software version, which will update the radio, then unlock, flash custom recovery, make a nandroid of the stock ROM/kernel as a known good backup, then reload my previous nandroid to restore the custom ROM/kernel.
As recommended above, it is generally a good idea to keep the software version in sync with the radio version, but personally I rarely update the radio and rarely have an issue .. but that is just my personal experience.
Hope that helps!
joeykrim said:
If you're running a custom ROM, you *might* be able to receive/download the OTA, but it will not update properly because the OTA checks all files in /system/app and /system/framework to verify they haven't been modified since the previous OTA before applying the new OTA. This check will definitely fail if any of the files have been modified in /system/app and /system/framework, which most custom ROMs make at least some minor modifications to the files in these directories.
Essentially, you'll have to get back to some form of stock to allow the stock bootloader to process the radio OTA. There might be a better way to approach this, but off the top of my head, I'd make a nandroid backup of everything, re-lock, run the RUU from the latest OTA/software version, which will update the radio, then unlock, and reload my previous nandroid.
Click to expand...
Click to collapse
Thanks for the explanation. Wow, that sounds like an enormous PITA.
joeykrim said:
As recommended above, it is generally a good idea to keep the software version in sync with the radio version, but personally I rarely update the radio and rarely have an issue .. but that is just my personal experience.
Hope that helps!
Click to expand...
Click to collapse
Maybe it's not as a big of a deal as I'm thinking then to not be able to update the radio (easily). I'm still on an OG EVO with S-OFF, and I haven't updated my radio for probably close to 2 years. All of my connections seem to be fine still.
Related
I need a little help. I unlocked the bootloader, rooted my phone, made TWRP my recovery, and got s-off. I did not flash a custom ROM. Now though, there is an update for my phone. I want to update it to the latest via OTA and remain on the stock ROM until 4.2.2 comes out. It is my understanding that I may need to run an RUU since I have TWRP as my recovery. This is where I'm a little confused.
1) Which RUU do I select? (I currently have the stock T-Mobile US build version 1.27.531.7 CL170484 release-keys if that helps)
2) Afterr I flash the RUU, do I need to perform s -on and re-lock the bootloader prior to performing the OTA update?
3) Am I missing any major steps?
4) Would it be better to just use a custom ROM like Android Revolution rather than trying to revert back to stock, etc?
Thanks for any and all input.
bloodbath said:
I need a little help. I unlocked the bootloader, rooted my phone, made TWRP my recovery, and got s-off. I did not flash a custom ROM. Now though, there is an update for my phone. I want to update it to the latest via OTA and remain on the stock ROM until 4.2.2 comes out. It is my understanding that I may need to run an RUU since I have TWRP as my recovery. This is where I'm a little confused.
1) Which RUU do I select? (I currently have the stock T-Mobile US build version 1.27.531.7 CL170484 release-keys if that helps)
2) Afterr I flash the RUU, do I need to perform s -on and re-lock the bootloader prior to performing the OTA update?
3) Am I missing any major steps?
4) Would it be better to just use a custom ROM like Android Revolution rather than trying to revert back to stock, etc?
Thanks for any and all input.
Click to expand...
Click to collapse
you need to flash the original recovery to install ota updates,, you will lose root access doing so
Or wait until some package it into a ZIP file and flash using TWRP.
Right?
Just wait a week.
All you need to do is put the stock Tmo recovery on your one. Then go update with ota and you will still be unlocked but you do lose root.
So it seems like there is disagreement to whether the stock ROM causes you to lose root or not. Either way, I would need to "lock" the bootloader again right?
Does the update add anything really worth having? I'm thinking that ARHD would be the best bet until an RUU comes out.
bloodbath said:
So it seems like there is disagreement to whether the stock ROM causes you to lose root or not. Either way, I would need to "lock" the bootloader again right?
Does the update add anything really worth having? I'm thinking that ARHD would be the best bet until an RUU comes out.
Click to expand...
Click to collapse
I'm sorry I was wrong you will lose root after you update ota. But you can do ota while being unlocked so no need to relock bootloader just flash the stock Tmo recovery and update.
chong67 said:
Or wait until some package it into a ZIP file and flash using TWRP.
Right?
Just wait a week.
Click to expand...
Click to collapse
U mean something like this!? https://copy.com/aSLnP
Team-Noctural.com/androidtechy.com/droidnow.com
I'm trying to return my HTC One back to being unrooted because I wanna update it and almost everywhere I read, you need to unroot to get over the air updates. So I got S-Off and I relocked my bootloader, but whenever I try running the RUU, it always fails. I tried flashing it and I tried running the exe file. Why does it keep failing? Also, is it true you can't get OTA updates while being rooted? The RUU I use is for Cingular (which from my understanding is the one AT&T uses) and I have Super CID. Lastly, if anyone knows an easier way to return my phone to being completely stock and unrooted that would be great. Thanks in advance!
Which RUU did you use? Apparently the last official one was JB 4.3 w/ Sense 5.0, ver. 3.17.502.3. The one for KK4.4.2 w/ Sense 5.0, ver. 4.18.502.7 was apparently not actually released by ATT and many people were having problems with it.
clsA said:
Well near as I can tell the RUU did not originate from HTC, someone was able to create it and sign it same as HTC would. But the files behave differently than the "Real" HTC RUU. The only solution I found was to use the True HTC RUU from 3.xx.502.x and OTA to 4.xx.502.x to 5.xx.502.x. It requires s-off to flash the OTA's so it's not the perfect solution for everyone.
Click to expand...
Click to collapse
So if you tried with the KK4.4.2 RUU, download the JB4.3 RUU from http://www.htc1guru.com/. Since you're S-OFF, you can use either the .exe or the decrypted .zip. I used the decrypted .zip before and it worked fine. Once you get that flashed you can then take the OTAs to update to KK4.4.2 w/ Sense 6. You'll need to be on the AT&T network to get those OTA. Otherwise you'll need to manually flash the updates, as clsA states in his post that I quoted above.
As for not getting OTAs while being rooted....
It's not so much that being rooted prevents getting OTAs. It's the process of getting to root that modifies or deletes system files that need to be intact for the OTA to work. OTA need to be installed through stock recovery. If you're rooted, it's most likely that you have a custom recovery. Also, unlocking the bootloader deletes some files the OTA checks for. If those files not there, the OTA will not install.
Flashing an RUU is the easiest way to get completely stock. It resets the phone to an out-of-the-box state. Whereas a factory reset done from bootloader or recovery basically just wipes the data partition, which will remove any apps you installed and user data. But any modifications to the system partition that are done remain. You don't get back the files that are deleted when you unlocked the bootloader.
Also, since you are S-OFF, there's no need to relock your bootloader to run an RUU. That's only required if you're S-ON. And once you get S-OFF, there is no reason to go back to S-ON.
Since I just want to get the new OTA update, do you recommend I just flash the update as opposed to going back to stock recovery because I don't mind having a rooted phone? Also, my phones camera suddenly became blurry, is it possible that the rooting had something to do with it? If it did, would flashing the OTA update fix it or would I need to go back to stock recovery or would neither fix it? Sorry for so many questions.
First off, what version is currently on your phone? Depending on where you're currently at you may need to flash more than one update in order to get it to the latest version. And no matter what, you'll need to flash stock recovery in order for the updates to flash. OTA updates, whether taken OTA or flashed manually, require stock recovery, as I mentioned before. Also, again as I mentioned before, the process of rooting your phone (more specifically, the process of unlocking your bootloader) most likely deleted files from your system partition that need to be in place in order for the OTA updates to install. If they are not there, the update will fail. So to answer your question...No, I don't recommend "just flash the update as opposed to going back to stock recovery". It won't work.
Since you didn't answer my question and state which RUU you tried, I don't know if you tried a bad 4.4.2 RUU or if there are other issues with your device and/or computer that's preventing any RUU from installing. If you just don't want to flash the RUU, then you can try flashing the update in the phone's current state and when it fails, you can analyze the error report, try to track down stock versions of the files you're missing and restore them if you find them, then try the update again, hoping you found everything. That's a lot more of a hassle than just flashing the RUU, flashing the updates, rooting, and setting up your phone.
Another option is to just flash a custom ROM. Most of them will bring the phone up to the latest version. Some will even take it higher than what is officially available from AT&T.
As for your camera problem, can't see how just rooting would cause that, but maybe it did. Without knowing the cause of the issue, I can't say if just flashing the OTA would fix it. If it's a software issue, then possibly it would. If it's a hardware issue, then probably not. Focus on updating the phone and worry about the camera issue if it still persists once updated.
Sorry, I forgot about your question. First of all, I got it working using RUU Zip M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3-decrypted. The one that didn't work for me is RUU Zip M7 UL JB 50 Cingular - 1.26.502.12. Second, I am running 4.4.2. Thats for anyone who comes across this and was wondering. Thanks for your help sharksfan7. Also, in case you were wondering, my camera is still blurry, but I'll start a different thread for that.
I'm fairly new to the rooting and flashing scene and had a quick question about firmware.
I'm currently running Dirty Unicorns 9/26 official build with furnace kernel 1.0.9. I wanted to try arhd 20.1, so I made a backup, factory wiped and flashed it. I went thru the aroma installer and everything installed fine, once it finished, however, it turned off and wouldn't turn back on. I finally got it working again into the bootloader, but when I try and boot it, it just hangs on the HTC logo screen with the red text.
I browsed the thread to see what the issue could be, and although I couldn't find the someone else who had that problem, most of the problems people are having are because they didn't upgrade to the latest firmware.
So is that what the issue could've been? I downloaded the new firmware, just need to flash it, but before I do, I want to ask, will I have to flash a custom recovery again if I flash the new firmware? And will I also lose my data?
I'm soff with sunshine, twrp is my recovery
Probably due to outdated firmware, you are correct. Flashing a Sense ROM based on a newer version number (1.x, 2.x, 3.x) than your current firmware will often result in long boot time The phone probably will boot, just take a really long time (like 10 minutes) with no boot animation, making many folks think its "stuck" on the boot screen. Other issues are also common, such as broken WiFi.
Although, if you intend on flashing the firmware associated withe ARHD 20 (firmware 3.28) be aware that this is an "international" based firmware, and those are known to not play well with AT&T's network (at least for past 2.x firmware). You can give it a try, but you may have reception issues and may need to flash another firmware, or at least a different radio.
I know...I'm probably gonna kick myself for admitting I can't find the firmware version I'm on...but I can't...I'm on dirty unicorns as well...want to update firmware so I can try various Roms and I don't know which one to download...im still s-on but I know there's a thread that said I can still update...just can't find the number... any number that resembles the ones in many lists. I googled it but it doesn't tell me
rjcormier said:
I know...I'm probably gonna kick myself for admitting I can't find the firmware version I'm on...but I can't...I'm on dirty unicorns as well...want to update firmware so I can try various Roms and I don't know which one to download...im still s-on but I know there's a thread that said I can still update...just can't find the number... any number that resembles the ones in many lists. I googled it but it doesn't tell me
Click to expand...
Click to collapse
Your confusion is not without reason. There is in fact technically no "number" for firmware. That being the base, its been the normal thing here on XDA to refer to the software number which the firmware deployed with. So "firmware 3.28" actually just refers to the various modules (hboot, radio, recovery, kernel, WiFi, Bluetooth, and others) that deployed with the 3.28 OTA software. But the number 3.28 is just for the OS, which can easily be changed simply by flashing the ROM; while the firmware is actually not touched when you flash a ROM. In your case, since Dirty Unicorn is AOSP, its software number probably has nothing to do with HTC's software numbering scheme.
Best you can do is go by hboot and radio number. Either boot into bootloader, and get those numbers there and post them. Or adb getvar all (delete IMEI if you cut and paste the getvar output).
Wonders_Never_Cease has all the recent AT&T firmwares posted here: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
But s-off is required to update firmware manually. If you want to stay s-on and update firmware, your alternative is to return to stock ROM and recovery, and OTA to update the firmware. Or relock the bootloader and RUU. Either way, 2.23 is the latest firmware/software you can update this way, until AT&T officially rolls out 3.xx.
Your confusion is not without reason. There is in fact technically no "number" for firmware. That being the base, its been the normal thing here on XDA to refer to the software number which the firmware deployed with. So "firmware 3.28" actually just refers to the various modules (hboot, radio, recovery, kernel, WiFi, Bluetooth, and others) that deployed with the 3.28 OTA software. But the number 3.28 is just for the OS, which can easily be changed simply by flashing the ROM; while the firmware is actually not touched when you flash a ROM. In your case, since Dirty Unicorn is AOSP, its software number probably has nothing to do with HTC's software numbering scheme.
Best you can do is go by hboot and radio number. Either boot into bootloader, and get those numbers there and post them. Or adb getvar all (delete IMEI if you cut and paste the getvar output).
Wonders_Never_Cease has all the recent AT&T firmwares posted here: http://forum.xda-developers.com/att...-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
But s-off is required to update firmware manually. If you want to stay s-on and update firmware, your alternative is to return to stock ROM and recovery, and OTA to update the firmware. Or relock the bootloader and RUU. Either way, 2.23 is the latest firmware/software you can update this way, until AT&T officially rolls out 3.xx.
Click to expand...
Click to collapse
Thank you! Soo hboot is 3.16.0.0000, and radio is 1.16.21331931
rjcormier said:
Thank you! Soo hboot is 3.16.0.0000, and radio is 1.16.21331931
Click to expand...
Click to collapse
I believe those are the hboot and radio numbers that go with the 1.58 software. You can update to 2.23 firmware by RUU (the OTA was actually pulled/cancelled). But that means you will only be able to run custom ROMs based on Sense software 2.x. The newer ROMs are based on Sense software 3.x. So if you want to run those, you either need to S-off, or wait until AT&T releases 3.x.
redpoint73 said:
I believe those are the hboot and radio numbers that go with the 1.58 software. You can update to 2.23 firmware by RUU (the OTA was actually pulled/cancelled). But that means you will only be able to run custom ROMs based on Sense software 2.x. The newer ROMs are based on Sense software 3.x. So if you want to run those, you either need to S-off, or wait until AT&T releases 3.x.
Click to expand...
Click to collapse
OK thank you for your help!
I have a Rezound that is not active. It just gets used around the house on wifi for checking email, facebook, and to control the wifi thermostat. I would like to get the latest OTA but cannot do it from the phone as it does not have an active sim. I don't really want to root the phone. I did the PH98IMG zip method to get 4.03.605.2 but it seams a little slow and it is my understanding that there is a new version of 4.05 or perhaps newer OTA... Does anyone have a link to a zip of the OTA that I can download?
Thanks for the help!
happyharvick said:
I have a Rezound that is not active. It just gets used around the house on wifi for checking email, facebook, and to control the wifi thermostat. I would like to get the latest OTA but cannot do it from the phone as it does not have an active sim. I don't really want to root the phone. I did the PH98IMG zip method to get 4.03.605.2 but it seams a little slow and it is my understanding that there is a new version of 4.05 or perhaps newer OTA... Does anyone have a link to a zip of the OTA that I can download?
Thanks for the help!
Click to expand...
Click to collapse
Well, your in a bad spot actually... 4.3.605.2 does not have an upgrade path at all, there is no OTA from it, or to it for that matter... it was an unofficial leaked firmware that is not supported in the standard software streams. Even if it was active on Verizon, it would never see an upgrade... ever.
You have 3 choices here:
1) S-OFF the device and get back to an official software build and manually OTA up (See the instructions for Full Downgrade/Upgrade here)
2) Assuming you are already Hboot unlocked, flash a custom ROM or a stock-ish ROM, there is a pre-rooted 4.5.605.14 ROM in the dev section
3) Stick with what you got, to be honest the ROM you have is pretty stable.
acejavelin said:
Well, your in a bad spot actually... 4.3.605.2 does not have an upgrade path at all, there is no OTA from it, or to it for that matter... it was an unofficial leaked firmware that is not supported in the standard software streams. Even if it was active on Verizon, it would never see an upgrade... ever.
You have 3 choices here:
1) S-OFF the device and get back to an official software build and manually OTA up (See the instructions for Full Downgrade/Upgrade here)
2) Assuming you are already Hboot unlocked, flash a custom ROM or a stock-ish ROM, there is a pre-rooted 4.5.605.14 ROM in the dev section
3) Stick with what you got, to be honest the ROM you have is pretty stable.
Click to expand...
Click to collapse
Thanks for taking the time to reply but I am not sure what you are referring to by "s-off" or hboot unlocked"
Can you point me in the right direction to learn a little more?
Thanks!
Hboot unlock is a process which is done via htcdev.com, it unlocks the phone to allow custom ROMs and recovery... Go to their site for more details or check out any of several YouTube videos.
S-Off is a means of turning off all security checks in the device, such as flashing an older RUU to downgrade. It is accomplished after Hboot unlock with a tool like RumRunner, check out rumrunner.us for more info.
If you are completely unfamiliar with unlocking, rooting, romming, or that kind of stuff, Google can be your friend here to learn the ins and outs, plus the sticky threads in the Rezound sections here.
"Unfortunately, AT&T Ready2Go has stopped." Is stuck looping on my phone.
About a year ago I rooted my phone, following these directions. (I can't yet post a link, but the first option on google when searching "how to root m8" is the site, htconeroot.com, that I used.)
This morning I noticed that my phone was not vibrating anymore no matter if I restarted the phone or what settings were applied. So I checked online to see if there was a fix, and a factory reset was recommended.
So when I got back from work today, I thought I had successfully uninstalled the root using SuperSU. Then I performed a factory reset. My phone then went into TWRP recovery which was alarming. So I rebooted the system from TWRP , then the message in the title kept popping up over and over again, so I am in a bit of a pickle. I can message and call at the moment but that is about it.
I'm thinking the problem is similar to this one someone had on a note 3, except I was trying to factory reset rather than update. http://forum.xda-developers.com/showthread.php?t=2663120
Has this happened to anyone else, and do you have any suggested fixes for resetting this phone???
Thanks in advance.
I've seen a number of cases on the M8 forums of various processes stopping with message "XXX has stopped" after a factory reset. Not sure what is causing this. But there are a variety of ways to recover.
Since you have TWRP, you can try to restore a TWRP backup of your own (if you made one) or install a stockish ROM. Those methods may be helpful if you want to retain or retrieve any personal data.
Otherwise, relock the bootloader and RUU back to full stock (RUU will wipe the phone).
redpoint73 said:
Otherwise, relock the bootloader and RUU back to full stock (RUU will wipe the phone).
Click to expand...
Click to collapse
Honestly I'd be fine returning to full stock, at least for the time being, to see if the vibration problem would fix itself. But do I need to be S-OFF for RUU?
eaflook said:
But do I need to be S-OFF for RUU?
Click to expand...
Click to collapse
No, and I wish folks would stop saying you need s-off to RUU (not you, but I assume you got this notion from another post/thread).
You can run the an RUU made for the AT&T M8, as long as you aren't "downgrading" to a previous version (such as Lollipop to Kitkat). For that, you need s-off; or to change the CID and run another carrier version RUU.
You do need to relock the bootloader to run RUU while s-on, with command: fastboot oem lock
Are you currently on LP or MM (what does it say for OS number on the bootloader screen)?
redpoint73 said:
No, and I wish folks would stop saying you need s-off to RUU (not you, but I assume you got this notion from another post/thread).
You can run the an RUU made for the AT&T M8, as long as you aren't "downgrading" to a previous version (such as Lollipop to Kitkat). For that, you need s-off; or to change the CID and run another carrier version RUU.
You do need to relock the bootloader to run RUU while s-on, with command: fastboot oem lock
Are you currently on LP or MM (what does it say for OS number on the bootloader screen)?
Click to expand...
Click to collapse
Um... the OS line on the bootloader screen looks blank, unless I'm looking in the wrong place.
Should I do this? http://forum.xda-developers.com/htc-one-m8/help/guide-how-to-solve-soft-brick-phone-t2824193
eaflook said:
Um... the OS line on the bootloader screen looks blank, unless I'm looking in the wrong place.
Click to expand...
Click to collapse
No, you're looking in the right place. Its somewhat common for OS number to be blank, its a known bug in older TWRP versions that it deletes the OS number.
What does it say for hboot number and radio number?
If the phone still on the stock ROM you originally rooted on? If so, is it Lollipop, Kitkat, etc.?
eaflook said:
U
Should I do this? http://forum.xda-developers.com/htc-one-m8/help/guide-how-to-solve-soft-brick-phone-t2824193
Click to expand...
Click to collapse
You can do that. All that "guide" describes is one way to get a ROM on an SD and flash it, which is one of the options I already suggested in Post #2 above.
But what ROM will work, somewhat depends on the info I requested above.
redpoint73 said:
What does it say for hboot number and radio number?
Click to expand...
Click to collapse
hboot number-3.19.0.0000
radio [email protected]
redpoint73 said:
If the phone still on the stock ROM you originally rooted on? If so, is it Lollipop, Kitkat, etc.?
Click to expand...
Click to collapse
Yes it is still on the stock root ROM. I am running Lollipop 5.0.2.
eaflook said:
hboot number-3.19.0.0000
radio [email protected]
Yes it is still on the stock root ROM. I am running Lollipop 5.0.2.
Click to expand...
Click to collapse
You should be fine flashing most any ROM on the AT&T or "international" M8 development forums. Just avoid other dev sections for variants, such as the Sprint or Verizon dev sections.
Before flashing a ROM, you may want to update your TWRP version to 3.0.whatever.
Although I have to admit, I'm still on TWRP 2.8.4, and its worked fine flashing LP and MM custom ROMs. Any older than 2.8.something may cause issues.
Alternately, relock bootloader and run RUU 4.28.502.2 (Lollipop). If you want to run the Marshmallow RUU (6.20.502.5), you'll need to flash the MM firmware first, then RUU. Link that describes that process, as well as all ATT RUUs is on my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
redpoint73 said:
You should be fine flashing most any ROM on the AT&T or "international" M8 development forums. Just avoid other dev sections for variants, such as the Sprint or Verizon dev sections.
Before flashing a ROM, you may want to update your TWRP version to 3.0.whatever.
Although I have to admit, I'm still on TWRP 2.8.4, and its worked fine flashing LP and MM custom ROMs. Any older than 2.8.something may cause issues.
Alternately, relock bootloader and run RUU 4.28.502.2 (Lollipop). If you want to run the Marshmallow RUU (6.20.502.5), you'll need to flash the MM firmware first, then RUU. Link that describes that process, as well as all ATT RUUs is on my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
Click to expand...
Click to collapse
Do you know how I might update TWRP from 2.7.0.2?-----Nevermind, I got it.
eaflook said:
Do you know how I might update TWRP from 2.7.0.2?-----Nevermind, I got it.
Click to expand...
Click to collapse
Good practice is to post what you did (or going to do) for the benefit of others that may have the same question; or so we can verify you are on the right track.
In case others may have the same question (or you get stuck again), all TWRP versions, and instructions (recommend install with fastboot method) are here: https://twrp.me/devices/htconem8gsm.html