I have an att version of this device with boot loader 3.16, software version 1.58.502.1
HTC Dev unlocked bootloader, rooted, S-Off.
I'm confused about which firmware I need to flash in order to change to the dev edition.
I see different instructions, some say no firmware update needed, others list various ones (flash 2.22, then a later one, etc.
Any updates guides or instructions on this?
Thanks,
Dan
This is the guide I used: http://htc-one.wonderhowto.com/how-...edition-for-super-fast-sense-updates-0156524/
One reason for the confusion may be that there are 2 very different ways you can "change" to Dev Edition.
1) Flash a Dev Ed ROM. In which case, your firmware is not changed, so will therefore likely not match what is needed to run the ROM. You need to flash the firmware manually. Depending on what firmware package, you may need to do it incrementally (OTA firmware) or not (RUU firmware).
2) RUU, which is a "full conversion" meaning it will not only flash the ROM, but also flash matching firmware including updated hboot, radio, stock recovery, and other modules. Once done, this will also allow you to get (I believe) Dev Ed OTAs in the future. To do this, you need to have s-off (which you do already) than change your CID to either the Dev Ed CID, or SuperCID. Than run the RUU:
http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777
Be aware that RUU will wipe your internal storage. So backup any personal data to your computer or removable SD.
Pretty much like @redpoint73 said
Change your CID to Supercid and flash the full up to date Dev edition ruu with your external sdcard
Related
Hello everyone
I hope someone can help me with this.
I have signal issues with my device, htc one x+, and thinking of sending it back as is still under warranty.
I have the revolution firmware on it and want to know how I can effectively set the original firmware on it so that I can then send it back.
Thank you
cpu2007 said:
Hello everyone
I hope someone can help me with this.
I have signal issues with my device, htc one x+, and thinking of sending it back as is still under warranty.
I have the revolution firmware on it and want to know how I can effectively set the original firmware on it so that I can then send it back.
Thank you
Click to expand...
Click to collapse
Depending on your devices bootloader (HBOOT) version and CID, you may be able to use an RUU to get back stock easily. If there's no matching RUU for your phone, you will have to search for stock backups and recovery matching your CID in order to apply stock HTC rom/firmware/recovery.
What is your bootloader version and CID?
reaper90 said:
Depending on your devices bootloader (HBOOT) version and CID, you may be able to use an RUU to get back stock easily. If there's no matching RUU for your phone, you will have to search for stock backups and recovery matching your CID in order to apply stock HTC rom/firmware/recovery.
What is your bootloader version and CID?
Click to expand...
Click to collapse
I don't know how to find the bootloader.
I found the CID using CID getter from the play store.
it shows it as : HTC__001
cpu2007 said:
I don't know how to find the bootloader.
I found the CID using CID getter from the play store.
it shows it as : HTC__001
Click to expand...
Click to collapse
reboot into bootloader (power off your phone and then press and hold power & volumedown button) there you can see your version number. If i remember right you need version 1.35 or lower to use a RUU, or your phone has to be S-OFF.
reaper90 said:
reboot into bootloader (power off your phone and then press and hold power & volumedown button) there you can see your version number. If i remember right you need version 1.35 or lower to use a RUU, or your phone has to be S-OFF.
Click to expand...
Click to collapse
This is what I see in the screen
Unlocked
ENRC2B_U PVT SHIP S-ON RL
HBOOT-1.30.0000
CPLD-None
MICROP-None
RADIO-3.1204.167.31
eMMC-bootmode:disabled
CPU-bootmode: disabled
HW secure boot:enabled
MODEM PATH: OFF
I've tried the following commands
adb bugreport | find "bootloader"
and I got this
6 un.ofs=362 androidboot.engid=0x
[ro.boot.bootloader]: [1.30.0000]
[ro.bootloader]: [1.30.0000]
http://www.androidruu.com/index.php?developer=ENRC2B
download the 1.17.401.1 RUU, it should work on your device. Make sure you backup all your stuff before using it, this will erase everything on your phone!!
reaper90 said:
http://www.androidruu.com/index.php?developer=ENRC2B
download the 1.17.401.1 RUU, it should work on your device. Make sure you backup all your stuff before using it, this will erase everything on your phone!!
Click to expand...
Click to collapse
Thank you, what information you've used to decide what RUU to use?
is that because 1.17 is the latest version and because they bootloeader and cid I've given you tell you that my phone is european and factory unlocked?
In addition:
I'm aware of a few methods that can be used to backup: Titanium,through adb,clockworld twrp but none of these does a full complete backup.
What's the best way to back up all the date so that all my messages,contacts,apps settings and messages(viber,skype logs and chats) can be restored once I have installed the stock firmware.
Can you also point out a simple guide that shows me how to install the stock firmware?
Thank you
cpu2007 said:
Thank you, what information you've used to decide what RUU to use?
is that because 1.17 is the latest version and because they bootloeader and cid I've given you tell you that my phone is european and factory unlocked?
In addition:
I'm aware of a few methods that can be used to backup: Titanium,through adb,clockworld twrp but none of these does a full complete backup.
What's the best way to back up all the date so that all my messages,contacts,apps settings and messages(viber,skype logs and chats) can be restored once I have installed the stock firmware.
Can you also point out a simple guide that shows me how to install the stock firmware?
Thank you
Click to expand...
Click to collapse
HTC__001 is a so called WWE (world wide edition) cid and i mostly read about people in europe having this, don't know what country exactly. and RUU is bound to certain cid and we only have those few RUUs for this device, so if someone does not have a matching cid for those RUUs you aren't able to use them. Also (as you've seen) your phone's bootloader is S-ON (Security-ON) like most people here have it, which means we're not allowed to do everything with our phones, for example we can't flash boot.img in recovery and we can't downgrade our bootloader version. This is the reason why i needed to know your bootloader version because the latest RUU we have is this 1.17.401.1 which includes bootloader 1.35 if i remember right. So if you had version 1.40 you wouldn't be able to use it because you can't downgrade bootloader version.
As for backup: I use titanium backup for all my user apps and app data (settings, savegames, chats, ...) and SMS Backup & Restore for sms backup.
But you also will need root to restore those backups.
To use the RUU, simply connect your phone to your computer and execute it. It should guide you to the process.
reaper90 said:
HTC__001 is a so called WWE (world wide edition) cid and i mostly read about people in europe having this, don't know what country exactly. and RUU is bound to certain cid and we only have those few RUUs for this device, so if someone does not have a matching cid for those RUUs you aren't able to use them. Also (as you've seen) your phone's bootloader is S-ON (Security-ON) like most people here have it, which means we're not allowed to do everything with our phones, for example we can't flash boot.img in recovery and we can't downgrade our bootloader version. This is the reason why i needed to know your bootloader version because the latest RUU we have is this 1.17.401.1 which includes bootloader 1.35 if i remember right. So if you had version 1.40 you wouldn't be able to use it because you can't downgrade bootloader version.
As for backup: I use titanium backup for all my user apps and app data (settings, savegames, chats, ...) and SMS Backup & Restore for sms backup.
But you also will need root to restore those backups.
To use the RUU, simply connect your phone to your computer and execute it. It should guide you to the process.
Click to expand...
Click to collapse
Thank you for explaining.
So I understand that if there's no a compatible RUU, it will not be possible to downgrade to the stock firmware, does this mean that after using custom rom, if I endup with a higher bootloader, I can't get back to my stock firmware but only change from one custom to another custom rom?
Where do these RUU come from? aren't they supplied by HTC, I mean if someone has a device with stock firmware but want's to flash his/her phone again, how would they do it? (for example in iphones you can get stock firmware for every phone)
Is it there a way to create a RUU when I have a stock firmware so that in case I need to revert back I can use that?
I'm on version 4.1.1 i guess, which i think isn't the latest version, after going stock firmware, if I upgrade, will i get my bootloader upgraded too?
sorry for too many questions
cpu2007 said:
Thank you for explaining.
So I understand that if there's no a compatible RUU, it will not be possible to downgrade to the stock firmware, does this mean that after using custom rom, if I endup with a higher bootloader, I can't get back to my stock firmware but only change from one custom to another custom rom?
Where do these RUU come from? aren't they supplied by HTC, I mean if someone has a device with stock firmware but want's to flash his/her phone again, how would they do it? (for example in iphones you can get stock firmware for every phone)
Is it there a way to create a RUU when I have a stock firmware so that in case I need to revert back I can use that?
I'm on version 4.1.1 i guess, which i think isn't the latest version, after going stock firmware, if I upgrade, will i get my bootloader upgraded too?
sorry for too many questions
Click to expand...
Click to collapse
Bootloader version is not rom version, custom roms won't update your bootloader. There's a difference between "firmware" and custom rom. you can update your phones firmware (bootloader etc.) with a cid matching "firmware.zip" from an OTA or RUU or on stock this is done automatically when applying OTA updates that include new versions of those. So if your bootloader version was too high, you can't use the RUU anymore and you have to get back to stock by using a stock TWRP/CWM backup and additionally flash stock recovery and boot.img and then relock your bootloader.
and yes RUUs are made by HTC, but there are no RUUs for latest software updates yet. either they don't exist or they're not leaked...
Your bootloader will probably be updatet to 1.35 if i remember right, but as long as the RUU includes the same version or a higher one, you're able to use it, so you can still use this RUU when used once.
just don't do OTA update to Sense 5/Android 4.2.2 or your bootloader will be upgraded to 1.72 and you won't be able to use any of those ruu again.
I just forgot one thing, I have linux at home, it's not possible to update through linux as it's an exe file.
is it there an alternative?
cpu2007 said:
I just forgot one thing, I have linux at home, it's not possible to update through linux as it's an exe file.
is it there an alternative?
Click to expand...
Click to collapse
I'm sry, as far as i know there's no way for RUU on linux. But i think i remember seeing a guide (either here at some xda forum or somewhere else on the internet) with a description on how to extract the stock rom and firmware.zip (which includes stock boot.img and recovery) from a RUU. So you could flash stock rom, boot.img and recovery and then relock bootloader, which should have the same effect. But i think you will need windows here too...
After running the RUU, it asked me to update the image, however it fails and it stays on the HTC black screen.
I've searched around and the way to install the RUU is to run it until the wizard windows open, search the temp folder and and a file in it called rom.zip.
extract the recovery or recovery_signed file from it and use fastboot command on the phone.
However when I try to extract the recovery_signed file, winrar says it's corrupt
how can I solve this or is it there another way to install the stock firmware?
my bad I had to fastboot oem lock
back to stock ,thank you!
is it there anything else I need to do in order to make sure that my phone is in the warranty guideline( i mean softwarewise)
Now I have got the phone fixed hopefully.
The phone details are as [email protected]
HTC ONE X+
android v: 4.2.2
htc sense version: 5.0
software num: 2.18.401.2
htc sdk api level: 5.41
How can I make a full backup of this stock firmware so if I decide to go back after using some custom firmwares, I can do so by restoring it back.
THank you
cpu2007 said:
Now I have got the phone fixed hopefully.
The phone details are as [email protected]
HTC ONE X+
android v: 4.2.2
htc sense version: 5.0
software num: 2.18.401.2
htc sdk api level: 5.41
How can I make a full backup of this stock firmware so if I decide to go back after using some custom firmwares, I can do so by restoring it back.
THank you
Click to expand...
Click to collapse
- unlock bootloader
- install custom recovery (CWM/TWRP)
- nandroid backup (all partitions)
You can restore this any time you need. Don't forget, you have to flash the boot/kernel backup separately in fastboot from your pc, so copy that backup to your computer once you have it.
BUT: if you want to go completely back to stock (relocked bootloader) you also need to flash stock recovery. i don't know how to dump stock recovery... maybe you can find some stock recovery.img for your version number here on xda or via google.
reaper90 said:
- unlock bootloader
- install custom recovery (CWM/TWRP)
- nandroid backup (all partitions)
You can restore this any time you need. Don't forget, you have to flash the boot/kernel backup separately in fastboot from your pc, so copy that backup to your computer once you have it.
BUT: if you want to go completely back to stock (relocked bootloader) you also need to flash stock recovery. i don't know how to dump stock recovery... maybe you can find some stock recovery.img for your version number here on xda or via google.
Click to expand...
Click to collapse
I have done all the steps but the one in bold is confusing me.
when you say flash boot/kernel separately ,you mean for the custom rom? how do I get the boot/kernel file to flash for my stock firmware?
I used TWRP to do a full backup, is nandroid backup necessary and what's the difference between that and TWRP backup?
cpu2007 said:
I have done all the steps but the one in bold is confusing me.
when you say flash boot/kernel separately ,you mean for the custom rom? how do I get the boot/kernel file to flash for my stock firmware?
I used TWRP to do a full backup, is nandroid backup necessary and what's the difference between that and TWRP backup?
Click to expand...
Click to collapse
nandroid backup = backup in custom recovery.
i mean if you want to restore your stock backup, you also have to flash the stock boot.img/kernel in fastboot because with S-ON phones we're not allowed to flash boot.img/kernel in recovery, hence we can't restore it using recovery restore function.
HTC ONE X+ RUU needed
Hi guys, i used to have a custom rom on my htc one x+ but now i want to put the stock RUU but i relocked and dicovered that my hboot is 1.40.0000 and my version-main is 1.17.401.3. So what can i do now?
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.
Okay since my phone is my baby I just want to make sure I got the steps right to upgrade from 4.4.4 skydragon gpw to 5.x skydragon gpe.
1. upgrade firmware
Curent setup:
s-off
CID__001
HBOOT-3.16
planning to use this RUU (do i have to go through htc to unlock again?)
2. reinstall twrp
htconem8gsm right?
3. flash skydragon here
4. install elementalx (also do i have to buy the kernel manager again?)
Again I just want some one else's eyes to look at what i'm going to do to make this a smooth as possible.
1) Not sure how you came up with the notion that RUU is the one you want. But its wrong, and will just put you on the same firmware (1.x, hboot 3.16) you presently have. The latest AT&T RUU is number 4.28.502 (Android 5.0.2) which you can find linked on my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
Since you are s-off, there is no need to relock the bootloader to RUU (this is only needed when s-on). And its also not recommended to relock the bootloader in this situation (just makes more work and more steps for yourself for no good reason and with no added benefit).
2) Correct. You will also want the latest version TWRP 2.8.7. Anything older than the last few versions will not work on Lollipop firmware.
3) Yes
4) I haven't used that kernel. But as long as you've checked that its compatible with the ROM, then its fine. The ElementalX thread says it supports GPE 5.1, so it should be fine, I think.
Also don't use Kernel Manager, so I don't know. Is that a Play Store purchase, an in-app purchase, or otherwise?
redpoint73 said:
1) Not sure how you came up with the notion that RUU is the one you want. But its wrong, and will just put you on the same firmware (1.x, hboot 3.16) you presently have. The latest AT&T RUU is number 4.28.502 (Android 5.0.2) which you can find linked on my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
Since you are s-off, there is no need to relock the bootloader to RUU (this is only needed when s-on). And its also not recommended to relock the bootloader in this situation (just makes more work and more steps for yourself for no good reason and with no added benefit).
2) Correct. You will also want the latest version TWRP 2.8.7. Anything older than the last few versions will not work on Lollipop firmware.
3) Yes
4) I haven't used that kernel. But as long as you've checked that its compatible with the ROM, then its fine. The ElementalX thread says it supports GPE 5.1, so it should be fine, I think.
Also don't use Kernel Manager, so I don't know. Is that a Play Store purchase, an in-app purchase, or otherwise?
Click to expand...
Click to collapse
okay thank you it was mainly the firmware stuff, again thanks.
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
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.