I just bought an AT&T HTC One M8 that came with android 4.4.2 KitKat. It apparently doesn't have any available android lollipop updates since checking for updates using the "AT&T Software Update" option in settings returns a "no updates available" which was weird, but I didn't mind since I was planning to root this and flash a custom rom.
I read up on guides on rooting and unlocking the bootloader which was pretty standard for most android devices. However, S-on/S-off and hboot are 2 things that are confusing me a bit right now despite doing quite a lot of searching on XDA. To my understanding, S-on/S-off is some kind of HTC protection that needs to be disabled to flash certain roms, and hboot seems to be what people are calling the HTC Bootloader (someone correct me if I'm wrong). If I'm correct, I seem to have hboot version 3.16 according to CPU-Z (I checked the Bootloader version number).
After enough reading, it seems like having the latest hboot version is relatively important for flashing many roms (3.18-3.19 I believe), but I have found no guides on how to do this. My only lead so far is the following thread with 1 reply: http://forum.xda-developers.com/att-htc-one-m8/help/update-hboot-3-18-3-19-t3236897
"Backup any personal data you want to keep (off phone, it will be wiped). Relock the bootloader, run the latest AT&T RUU."
So ok, I guess it's a good thing I'm doing this before rooting the device. However, What's the AT&T RUU? My closest guess was using the HTC Sync Manager on windows to find firmware updates manually, but upon trying this (installing htc sync manager and connecting my HTC One M8) and on the menu clickling "Check for updates", I just get an error message saying "Unable to connect to the live update service".
Then, after some more searching I found this thread: http://forum.xda-developers.com/att-htc-one-m8/help/how-update-bootloader-to-3-18-0-0000-t3006738 which said the following:
"Follow instruction on the following thread for updating firmware, and select the 3.28.1540 firmware file: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-n"
So, here I am. Unsure whether to follow this instructions since I have no idea what that firmware is or if it will brick my device, or whether it will work since I still haven't rooted or unlocked my device's bootloader and I don't have S-Off (and that thread clearly states S-Off is mandatory for flashing to work). Any ideas?
---------------------------------------------------
edit: I just found out what RUU stands for, but I have been unable to find this "Rom Update Utility". It's spoken as Windows software, but I can't find where to download it. Any help would be very appreciated
sarxion said:
I just bought an AT&T HTC One M8 that came with android 4.4.2 KitKat. It apparently doesn't have any available android lollipop updates since checking for updates using the "AT&T Software Update" option in settings returns a "no updates available" which was weird
Click to expand...
Click to collapse
Are you connected to the AT&T network?
sarxion said:
I read up on guides on rooting and unlocking the bootloader which was pretty standard for most android devices. However, S-on/S-off and hboot are 2 things that are confusing me a bit right now despite doing quite a lot of searching on XDA. To my understanding, S-on/S-off is some kind of HTC protection that needs to be disabled to flash certain roms.
Click to expand...
Click to collapse
S-off is not needed to flash any ROMs. S-off is one way to update the firmware needed to run a ROM (more on what "firmware" is in a bit), but s-off isn't strictly need to update firmware either (other ways to do it s-on).
s-off is needed to modify (hack) certain partitions that are protected even with the bootloader unlocked. Such as hboot, radio, and some others. But its only needed for those specific things; and not needed to flash custom recovery or ROMs. And note that you can still update hboot, radio, and other firmware by "official" means even with s-on.
sarxion said:
hboot seems to be what people are calling the HTC Bootloader (someone correct me if I'm wrong).
After enough reading, it seems like having the latest hboot version is relatively important for flashing many roms (3.18-3.19 I believe)
Click to expand...
Click to collapse
Yes, hboot and bootloader are the same thing, as far as HTC devices are concerned.
Not only is the latest hboot needed to flash the current ROMs, but its important to update the entire firmware package. Firmware includes not only hboot, but also a number of other critical modules such as radio, WiFi, Bluetooth, and others; that all need to be updated in order for the current ROMs to function properly.
Good news, you are on the right track, and the proper RUU will update not only hboot, but all the firmware.
sarxion said:
What's the AT&T RUU?
edit: I just found out what RUU stands for, but I have been unable to find this "Rom Update Utility". It's spoken as Windows software, but I can't find where to download it.
Click to expand...
Click to collapse
I've created an AT&T index thread to catalog such things (sticky to the top of the General AT&T M8 section). It explains what an RUU is, and has links to all AT&T RUUs. You will want the latest RUU (4.28.502.1 or 4.28.502.2 - they are mainly the same except the latter has the Stagefright fix):
http://forum.xda-developers.com/showthread.php?t=2751432
The RUU is rather self-explanatory. As mentioned previously in this thread (and on the Index) your phone will be wiped by the RUU. So backup anything you want to keep by your method of choice. Then simply download the RUU to a PC, connect the phone. Then run the RUU program, and it will walk you through the process (you basically just need to confirm a couple dialogue boxes, and the RUU will do the rest and automatically update all the software/firmware).
After that, what you want to do in short is:
1) Unlock the bootloader using HTCDev.com
2) Install TWRP 2.8.7
3) Flash your custom ROM of choice
4) Beer
Related
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!
FOUND THE RECOVERY (See below)
Right now my goal is to go back to stock to flash the OTA Update. I am running my nandroid back up I first made when which is the 4.4.4 w/ Software # 1.58.502.1. and right now I have TWRP as my recovery.
Also can someone confirm something for me. This nandroid I am running is rooted obviously and has SuperUser on it. If I go back to the stock recovery can I still do the OTA update even though SuperUser is there and the phone is unlocked?
Also in order to get the stock recovery back on the phone I need to use ABD and the windows command prompt method correct?
Thanks
found this link and was able to find the stock recovery finally. I clicked "Non-WWE- Recovery Images" Ten on the site it opens I clicked the more recoveries folder at the top and 1.58.502.1 was the first one.
http://forum.xda-developers.com/showthread.php?t=2701376
Now the only thing I need to know is if going back to stock recovery will allow me to update to OTA even though there is SuperUser on my device and even though I am rooted and unlock (S-on)
magicbumm328 said:
found this link and was able to find the stock recovery finally. I clicked "Non-WWE- Recovery Images" Ten on the site it opens I clicked the more recoveries folder at the top and 1.58.502.1 was the first one.
http://forum.xda-developers.com/showthread.php?t=2701376
Now the only thing I need to know is if going back to stock recovery will allow me to update to OTA even though there is SuperUser on my device and even though I am rooted and unlock (S-on)
Click to expand...
Click to collapse
As long as the ROM is stock (nothing modified by root) and stock recovery, you can update by OTA (root okay, unlocked bootloader okay).
Another option, just relock the bootloader and run the 4.4.4 RUU. It saves you from all the hassle (finding stock ROM and stock recovery), plus installing 2 OTAs. Only reason to do it the way you are, is to keep user data (RUU wipes phone) and it also saves you from having to relock.
redpoint73 said:
As long as the ROM is stock (nothing modified by root) and stock recovery, you can update by OTA (root okay, unlocked bootloader okay).
Another option, just relock the bootloader and run the 4.4.4 RUU. It saves you from all the hassle (finding stock ROM and stock recovery), plus installing 2 OTAs. Only reason to do it the way you are, is to keep user data (RUU wipes phone) and it also saves you from having to relock.
Click to expand...
Click to collapse
Well I do have the stock ROM. Idk if it having super user on it counts as being modified by root though? If not then its fine. And as mentioned I found the stock recovery as well.
The only reason I was looking to do it this way was because I do not really know what RUU is or how to do any of it. Idk how difficult it would be to relock the boot loader then figure out the RUU thing. Idk what the differences are between that and my phone being rooted as it is now are. I'll have to see if there is a thread that explains this RUU thing to me.
Thanks for the help and suggestion too btw
magicbumm328 said:
Well I do have the stock ROM. Idk if it having super user on it counts as being modified by root though? If not then its fine.
Click to expand...
Click to collapse
SuperUser is same as root, and is fine.
When I say "modifed by root" that often is when a user deletes "bloatware" they don't want, or adds apps, or modifies apps in the system partition.
If you didn't explicitly do any of those things, you should be fine. You will know this is the problem when you install the OTA, as the install will fail with the error message that the "system has been modified".
magicbumm328 said:
The only reason I was looking to do it this way was because I do not really know what RUU is or how to do any of it. Idk how difficult it would be to relock the boot loader then figure out the RUU thing. Idk what the differences are between that and my phone being rooted as it is now are. I'll have to see if there is a thread that explains this RUU thing to me.
Click to expand...
Click to collapse
RUU = ROM update utility
RUU is super easy, you don't really need much guidance to use it. LOCKED or RELOCKED bootloader is required to run it (UNLOCKED if okay if you have s-off). PC required, and the RUU will wipe the phone (so backup any personal data you want to keep, into your PC, cloud, etc.). Aside from those points, RUU is a self-explanatory executable (.exe) program that runs from your PC, and simple to use.
Relocking the bootloader is accomplished easily with a single fastboot command (after connecting phone to PC and booting into fastboot mode): fastboot oem lock
This is also assuming you did the bootloader unlock yourself, and therefore have fastboot/adb setup on your computer.
Running the RUU itself (after relocking the bootloader) is very easy. Boot into OS (some folks have better success being booted into fastboot mode, but I think the RUU is designed to run when booted into OS), connect to PC, then just run the RUU executable on your PC. The RUU executable will then just guide you what you need to do. Its mostly automated, you just need to confirm a few dialogue screens, etc. The RUU will reboot the phone a couple times, install the needed files automatically, and that's really it.
However, since you seem confidant you already have a stock ROM and corresponding stock recovery, I suppose the RUU doesn't gain you too much. But if you hadn't done those steps already, it often saves folks the hassle of tracking down the right stock ROM and recovery for their CID and current firmware. RUU in my opinion is a cleaner install, as it installs a complete stock image (not just updating piecemeal, like an OTA often does).
Also, since OTAs typically need to be installed in sequence, you will probably need to OTA to 2.23 software, than another OTA to 3.42 software. As RUU is a complete image, it would get you to 3.42 software in one fell swoop.
One other thing to note, is that if you are for some reason not connected to AT&T's network (using another carrier, another country, etc.) you will not get any OTAs on the AT&T branded device. AT&T oddity here, most other version will still OTA, even when not connected to a specific carrier. In contrast the AT&T RUU is able to be downloaded and run by anyone with an internet connection and PC (regardless of country, carrier, etc.). I'm under the assumption that most folks on this forum section are on AT&T's network, although I know that some are not (you haven't stated either way).
RUU links are included on my Index thread under heading "RUUs": http://forum.xda-developers.com/showthread.php?t=2751432
Aside from wiping the phone (OTA keeps user data, but you may end up wiping anyway if you run into bugs after OTA), the other downside to RUU is that you need to relock the bootloader. Then you need to unlock the bootloader again (via the HTCDev.com site, or alternately sunshine) if you want to install custom recovery, install custom ROMs, root, etc.
So the choice is really yours (RUU versus OTA). I'm just giving it as an alternative.
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
There is a master list of stock recovery versions for the HTC One. How do I determine which version I should be using?
None of those. That is hardly a "master" list. It's over 3 years old, never updated past the original Kitkat (M8 release) recoveries, and woefully obsolete. You'll want your recovery number to match your OS number (main version on bootloader screen or getvar all). Also, none of those are valid for AT&T version M8 (which is what I assume you have, since this section is specifically for the AT&T M8). It would need to have "502" in the version number x.xx.502.x which specifically denotes AT&T.
Why exactly do you want stock recovery? Most folks want this, in order to get OTA updates. But you will also need a stock, never rooted ROM (unrooting doesn't work), and also must be connected to the AT&T network. It's probably easier to relock the bootloader, and update by RUU. Note that RUU will wipe all data from the phone. See RUU section in my Index thread: https://forum.xda-developers.com/showthread.php?t=2751432
If you really want stock recovery, you should be able to extract it from the firmware.zip. Find the right firmware version number from the firmware collection, and extract recovery.img from the "Stock, Full Wipe" firmware zip:
https://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
That is definitely helpful. Thank you. I didn't realize that I could pull the bootloader out of the firmware.zip. The phone was AT&T and later unlocked and made in to a rooted Cyanogenmod phone. I had to un-root and install Android GPE. It's not really AT&T anymore. Now I can download OTA updates, but cannot install them because TWRP is still the bootloader. I would rather do the OTA updates since the phone is already stock-ish and resetting everything is only slightly preferable to stabbing my eye out.
Since I'm unlocked on marshmallow, it looks like I want the 6.12.1540.4 zip.
mortifyxda said:
I didn't realize that I could pull the bootloader out of the firmware.zip.
Click to expand...
Click to collapse
Recovery and bootloader are two completely different things! You can pull recovery.img from firmware.zip, and flash with fastboot. I would not do this with bootloader, which would require s-off (to flash manually) and it would still be risky. Better to flash the whole firmware.zip or RUU, if you want to update bootloader. But I don't think that is what you meant.
mortifyxda said:
I had to un-root and install Android GPE. It's not really AT&T anymore. Now I can download OTA updates, but cannot install them because TWRP is still the bootloader. I would rather do the OTA updates since the phone is already stock-ish and resetting everything is only slightly preferable to stabbing my eye out.
Since I'm unlocked on marshmallow, it looks like I want the 6.12.1540.4 zip.
Click to expand...
Click to collapse
Your description is confusing, and I think you're mixing the terms up again. 6.12.1540.4 is the version number for the US Developer's Edition, which is Sense, and not the same as Google Play Edition (GPE) which is not Sense.
To OTA, the version number of the current stock ROM needs to match your firmware number (in bootloader and getar all), and you also need matching stock recovery.
To be clear, what is the current ROM (and version number) as shown in Settings? And also do fastboot getvar all, and post the result (delete IMEI and serial number). Need those pieces of info, before I can properly advise what stock recovery to use.