Update Hboot 3.18-3.19 - AT&T HTC One (M8)

Hello all, I have been searching the internet for an easy and current method to update Hboot so I can flash the roms I want. I am currently unlocked with S-On running an unofficial CM12 ROM. Any help will be greatly appreciated

Backup any personal data you want to keep (off phone, it will be wiped). Relock the bootloader, run the latest AT&T RUU.
Then after RUU, unlock the bootloader again, re-install the latest version TWRP and flash whatever custom ROM you want.

Related

Set Device to original firmware

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?

[Q] Reverting to Stock for Sense 6

I'm aware of the OTA update next week that'll update me to Sense 6.
Currently displays in recovery:
Tampered
Unlocked
S-OFF
Currently on stock 4.4.2 rooted, no other kernel changes, etc. but the ROM I'm using has custom black boot screens added (literally just black instead of default white boot background).
Rooting is nice and all but getting tired and would just like to revert to pretty much locked bootloader, unrooted, factory condition, etc. and be able to also do OTA for future updates.
Any help is appreciated. Baby steps please.
Anyone?
First, relock your bootloader. To do that, start your phone in bootloader mode, connect your phone to pc via usb cable and type "fastboot oem lock" on command prompt. Next, download the proper ruu exe file from htc1guru.com. By proper,I mean the one that matches your phones actual model number and custom id. Execute the ruu while connecting your phone to pc in fastboot mode. Follow the on screen instructions and when finished, you will have s phone that says re locked and s-off. You will get ota in this condition and will be able to install ota and upgrade to Sense 6.0 without any problems.
http://forum.xda-developers.com/showthread.php?t=2695749
Can I just flash that RUU in the link above? It should take me back to stock 4.4.2 with no modifications, stock recovery, and since I have an unlocked bootloader + S-OFF I should be able to get OTA's.
I'm just getting replies and finding info in other threads with different methods so I just don't want to screw up anything.
SaHiLzZ said:
If you are only rooted with stock ATT software, unroot using the SuperSU app, make sure you have stock recovery, and you are golden. DO NOT turn S-ON, and also no need to lock bootloader, as with S-OFF, you will get updates with unlocked bootloader
Click to expand...
Click to collapse
I'm running stock AT&T 4.4.2 but the person who uploaded the ROM used a custom black boot screen (black HTC background instead of white when the phone boots) and so I was worried that might affect things. Hence I thought I could just flash an RUU to go back to 100% stock AT&T 4.4.2 (+ unroot) and maintaining unlocked bootloader + S-OFF so I can OTA.
EDIT: Could I just convert it to a Developer Edition using the link in your signature? Will there be any problems with my AT&T SIM card? All I have to do is relock bootloader and flash the Dev. Edition ROM.
Yes you can flash the decrypted ruu. It is the same as using the ruu exe.
If you haven't changed your mid and/cid,then what you need to is just lock the bootloader and flash the ruu (zip or exe). You will be on stock with s-off which is fine for getting ota.
Yes you can convert to developer edition. The DE and the at&t version are the same hardware-wise (except DE have 64gb storage instead of 32gb on at&t version) and have the same radio bands. You will get faster Android upgrades with no at&t bloats.
mch277 said:
http://forum.xda-developers.com/showthread.php?t=2695749
Can I just flash that RUU in the link above? It should take me back to stock 4.4.2 with no modifications, stock recovery, and since I have an unlocked bootloader + S-OFF I should be able to get OTA's.
I'm just getting replies and finding info in other threads with different methods so I just don't want to screw up anything.
I'm running stock AT&T 4.4.2 but the person who uploaded the ROM used a custom black boot screen (black HTC background instead of white when the phone boots) and so I was worried that might affect things. Hence I thought I could just flash an RUU to go back to 100% stock AT&T 4.4.2 (+ unroot) and maintaining unlocked bootloader + S-OFF so I can OTA.
EDIT: Could I just convert it to a Developer Edition using the link in your signature? Will there be any problems with my AT&T SIM card? All I have to do is relock bootloader and flash the Dev. Edition ROM.
Click to expand...
Click to collapse
You may want to just try and apply the OTA when released. I'm not aware that S-OFF is a problem, I know an unlocked bootloader nor rooted isn't an issue. I got the Rogers OTA with an unlocked bootloader a rooted (by the way was still rooted after the OTA)
Just my 0.02
mb_guy said:
You may want to just try and apply the OTA when released. I'm not aware that S-OFF is a problem, I know an unlocked bootloader nor rooted isn't an issue. I got the Rogers OTA with an unlocked bootloader a rooted (by the way was still rooted after the OTA)
Just my 0.02
Click to expand...
Click to collapse
My understanding is that, if there's any modification in system files, applying OTA may result in a bootloop/brick. I agree that rooted devices remain rooted after OTA. As the OP said that s/he us using a rom with modified boot animation, I suggested him/her to return to stock first.

[Q] ¿Can i take an OTA whit S-OFF?

(SOLVED)
Im in stock 4.1.2 whit S-OFF, unlocked bootloader (1.55) and then RELOCKED.
¿Can i take the last OTA?
Im not rooted, and i dont have custom recoverys (i recently flashed a RUU.zip to return to stock, but i could not remove the S-OFF and RELOCKED status because the hboot 1.55).
I have economic (health) problems and I'll really need to sell my phone, but I'm afraid that the new owner will come out error when trying to update.
conquesoextra said:
Im in stock 4.1.2 whit S-OFF, unlocked bootloader (1.55) and then RELOCKED.
¿Can i take the last OTA?
Im not rooted, and i dont have custom recoverys (i recently flashed a RUU.zip to return to stock, but i could not remove the S-OFF and RELOCKED status because the hboot 1.55).
I have economic (health) problems and I'll really need to sell my phone, but I'm afraid that the new owner will come out error when trying to update.
Click to expand...
Click to collapse
Yes. You can get OTAs while S-OFF. And assuming you haven't unlocked the bootloader since flashing the RUU, all the system files it verifies should be in place to accept OTAs. However, considering you are currently on 4.1.2, you'll need to run through a progression of OTAs to get up to the latest version, 4.4.2 w/ Sense 6. Might be better to just run the latest RUU to bring it up to 4.4.2 w/ Sense 5.5 then OTA to Sense 6. Be aware that you'll need to be on the AT&T network in order to get the updates OTA. If you're not on AT&T, you'll need to flash the updates manually, in which case you'll need to be S_OFF.
Also, once the phone is S-OFF there is no good reason to change that back to S-ON. There's the potential of bricking the phone by doing so. And even if it doesn't brick, the updates in firmware may make it more difficult to obtain S-OFF again.
Thank you very much.
At the begining i did this:
1- Unlocked bootloader and flashed TWRP.
2- Root
3- Gained S-Off
When i decide to sell it i did this:
1- Removed xposed and root.
2 - Relocked bootloader.
3 - Flashed RUU.zip (4.1.2)
¿What do you mean whit AT&T network? I unlocked the phone vía imei (using it in mexico whit Telcel) and still have the update appearing.
Sorry for my terrible english
conquesoextra said:
Thank you very much.
At the begining i did this:
1- Unlocked bootloader and flashed TWRP.
2- Root
3- Gained S-Off
When i decide to sell it i did this:
1- Removed xposed and root.
2 - Relocked bootloader.
3 - Flashed RUU.zip (4.1.2)
¿What do you mean whit AT&T network? I unlocked the phone vía imei (using it in mexico whit Telcel) and still have the update appearing.
Sorry for my terrible english
Click to expand...
Click to collapse
First off, since you are S-OFF there is no need to relock the bootloader in order to flash an RUU. It will run just fine with an unlocked bootloader. Also when you flash an RUU, all the partitions get wiped so there is no need to do anything within the ROM such as remove xposed & root prior to flashing. The RUU will set the device essentially in a factory state.
As far as I understand it, the OTAs for carrier specific devices are served up by the carrier. So if the phone has been SIM unlocked and is being used on another network, if you go into Settings>AT&T software update, it will not receive any available OTA update. You will need to flash the update file manually using the information in this thread, http://forum.xda-developers.com/showthread.php?t=2659374.
Since you are still on 4.1.2, you will need to run one of the recent RUUs in order to manually flash the OTA updates in that thread. The latest RUU available for AT&T devices is KK4.4.2 w/Sense 5.5.
http://androidruu.com/getdownload.p...09_10.26.1718.01L_release_356565_signed_2.exe
Flash that then you can manually flash the OTA update to get Sense 6.
You are the man.
THANK YOU SO MUCH!

SIM Unlock Sprint HTC One Max

I almost cannot believe how many different ROMs I've tried to flash after wiping out my original ROM.
Bootloader unlocked and rooted I managaged to relock the bootloader while trying to fastboot flash a stock ROM, which also failed.
Beleive it or not, I've have found a couple that will boot up with my Sprint HTC One Max . I was able to re-unlock the bootloader, flash a new rom and even recover user data I had backed up to my PC via adb backup.
All this for not, as I still cannot find a Sense ROM that will flash on my device and allow me to unnlock the Sim via Sim Unlock Helper.
Any help would be greatly appreciated!!!
TAMPERED
UNLOCKED
Sprint HTC One T6WL S-OFF
CID-SPCS_001
HBOOT-2.49.000
RADIO-1.48.50.0425
I recall reading somewhere that the Unlock Sim Helper should work on Sense 4.1.2 ROM. ????
Greetings,
I moved your thread to the correct forum (hopefully) for you to get the help you need.
Thanks,
BD619
RUU back to anything pre-4.4 and it should work. afaik you need a lower hboot/radio version

[Q] No OS, locked bootloader, S-off

Hey Everyone! So i will be receiving my M8 i got used in the mail on monday and i'm doing some research because it is softbricked due to no OS being installed. It is (presumably) S-Off with Bootoader locked and "possibly" no custom recovery. What i'm planning to do is once the battery is charged completely.
-Connect it to my PC (windows)
-Power into fastboot
-Run the stock AT&T RUU and get everything running and up to date.
From there i will be unlocking the bootloader, custom recovery, root, and all the good stuff.
I'm just wanting to know from the way more knowledgeable folks then i when it comes to this stuff, is if this is the proper procedure. Is there anything else i should do first or after? Any help will be great! I'll know more tomorrow night on if recovery is installed or not, but i'm going with the opinion that there is no custom recovery, as i feel this would be harder.
any help would be GREATLY appreciated!
I agree with the above described approach. Especially since its not clear what the previous owner did (appears previously bootloader unlocked, s-off, then possibly a botched return to stock attempt?) its good to run the AT&T RUU to return to a full stock "baseline" image to all partitions.
Since you are going to run RUU, it doesn't matter whether custom recovery is currently installed or not. The RUU will install the stock recovery image.
After RUU, unlock the bootloader via HTCDev.com. Then install current version TWRP and flash SuperSU 2.46 to obtain root (older versions SuperSU won't work on Lollipop - common mistake).
redpoint73 said:
I agree with the above described approach. Especially since its not clear what the previous owner did (appears previously bootloader unlocked, s-off, then possibly a botched return to stock attempt?) its good to run the AT&T RUU to return to a full stock "baseline" image to all partitions.
Since you are going to run RUU, it doesn't matter whether custom recovery is currently installed or not. The RUU will install the stock recovery image.
After RUU, unlock the bootloader via HTCDev.com. Then install current version TWRP and flash SuperSU 2.46 to obtain root (older versions SuperSU won't work on Lollipop - common mistake).
Click to expand...
Click to collapse
Thank you so much Redpoint! I only have a small amount of knowledge with this area. I've sideloaded an OS over ADB due to a mistake i made with no OS on an old tablet, but never had to deal with possibly stock recovery with a locked bootloader, so knowing my approach will presumably work is a real relief.
Thank you again!!!:good::fingers-crossed:

Categories

Resources