[TUT] How to upgrade HOX with a RUU(hboot.img, etc..) after installed a custom rom

Search This thread

GabrielSousa

Senior Member
Feb 15, 2011
4,438
2,072
Leiria
OnePlus 9 Pro
(this is the only way we have now to upgrade the hboot.img, bct.img, rcdata.img, etc...)

Method 1



  • Install stock rom of your CID
-fastboot oem readcid (to know your CID)
-all roms are based on x.xx.401.xx , so you need to download the right RUU(that matches your CID) and extract rom.zip to cook a stock rom for you
-flash custom stock rom(extracted and cooked from right RUU) on custom recovery
-fastboot flash boot c:\boot.img (flash stock kernel that's inside custom stock rom boot.img file)



  • RElock the bootloader (you can allways unlock)
-fastboot oem lock



  • Right RUU file for your CID
-put your phone on fastboot (it will not boot because you have a custom rom on a locked bootloader)
-now you can run the RUU exe file and upgrade your phone


Method 2




  • Extract the rom.zip from RUU of your CID (google how extract ruu.exe)
-fastboot oem readcid (to know your CID)

  • Extract boot.img, system.img, signed_recovery.img from rom.zip

  • Flash
-fastboot flash recovery signed_recovery.img
-fastboot flash boot boot.img
-fastboot flash system system.img
-fastboot erase cache
-fastboot oem lock

  • Power on the phone

  • Run the RUU exe file (of your CID) and upgrade your phone

Method 3 (like Method 2, but we dont need to flash the system) (thanks to EddyOS)




  • Extract the rom.zip from RUU of your CID (google how extract ruu.exe)
-fastboot oem readcid (to know your CID)

  • Extract boot.img, signed_recovery.img from rom.zip

  • Flash
-fastboot flash recovery signed_recovery.img
-fastboot flash boot boot.img
-fastboot oem lock

  • Run the RUU exe file (of your CID) in fastboot mode



  • SuperCID 11111111
  • AirTel-India ????????
  • Asia-HK-CHT HTC__622
  • ATT CWS__001
  • BM BM___001
  • Bouygues-Telecom BOUYG201
  • Brightstar-PTB BSTAR502
  • Brightstar-SPA BSTAR301
  • Chunghwa-Taiwan CHT__601
  • CT HTCCN702
  • CU HTCCN703
  • DCM DOCOM801
  • DOPOD DOPOD701
  • Era T-MOB009
  • Fastweb-IT FASTW401
  • GOOGLE GOOGL001
  • H3G-DAN H3G__F05
  • H3G-Italy H3G__402
  • H3G-ROI H3G__003
  • H3G-SWE H3G__G04
  • H3G-UK H3G__001
  • HTC-Asia-SEA HTC__037
  • HTC-Asia-SEA-WWE HTC__044
  • HTC-Australia HTC__023
  • HTC-BE HTC__E41
  • HTC-Czech HTC__C24
  • HTC-Denmark HTC__F08
  • HTC-Dutch HTC__E11
  • HTC-EastEurope HTC__032
  • HTC-ELL HTC__N34
  • HTC-FRA HTC__203
  • HTC-FRA-Bouygues HTC__247
  • HTC-GCC HTC__J15
  • HTC-GER HTC__102
  • HTC-India HTC__038
  • HTC-ITA HTC__405
  • HTC-Nor HTC__Y13
  • HTC-Norway HTC__H10
  • HTC-Poland HTC__B25
  • HTC-PTG HTC__506
  • HTC-Russia HTC__A07
  • HTC-Singapore ????????
  • HTC-SPA HTC__304
  • HTC-Sweden HTC__G09
  • HTC-Turkey HTC__M27
    [*]HTC-WWE HTC__001
  • Hutch-Australia HUTCH001
  • O2-DE O2___102
  • O2-UK O2___001
  • Open-Channel HTCCN701
  • Optus-Australia OPTUS001
  • ORANGE-AT ORANG113
  • ORANGE-BE ORANG012
  • ORANGE-CH-FRA ORANG203
  • ORANGE-CH-GER ORANG104
  • ORANGE-ES ORANG309
  • ORANGE-French ORANG202
  • ORANGE-PL ORANGB10
  • ORANGE-PO ORANG008
  • ORANGE-SK ORANG006
  • ORANGE-SW ORANG216
  • ORANGE-UK ORANG001
  • Rogers ROGER001
  • SMC-Voda-HK SMCVD001
  • StarHub-Singapore ????????
  • TELEF-Spain TELEF301
  • Telstra TELST001
  • TELUS TELUS001
  • TIM-Italy TIM__401
  • TMA T-MOB102
  • TMCZ T-MOB004
  • TMD T-MOB101
  • TMH T-MOB007
  • TMHR T-MOB006
  • TMMK T-MOBL11
  • TMNL T-MOB003
  • TMSK T-MOB008
  • TMUK T-MOB005
  • TMUS T-MOB010
  • TWM-TW HTC__621
  • VIRGIN-UK VIRGI001
  • VODA-Africa-South HTC__016
  • VODA-Australia VODAP021
  • VODA-Germany VODAP102
  • VODA-Greece VODAP006
  • VODA-Ireland VODAP019
  • VODA-Italy VODAP405
  • VODA-Mobilkom VODAP120
  • VODA-Netherland VODAPE17
  • VODA-New-Zealand VODAP022
  • VODA-Portugal VODAPD18
  • VODA-Proximus VODAP024
  • VODA-SA VODAP026
  • VODA-SFR VODAP203
  • VODA-Spain VODAP304
  • VODA-Swisscom-DE VODAP110
  • VODA-Swisscom-FR VODAP212
  • VODA-Swisscom-IT VODAP416
  • VODA-Swisscom-WWE VODAP015
  • VODA-TR VODAPM27
  • VODA-UK VODAP001

  • x.xx.61.x - Orange UK (United Kingdom)
  • x.xx.65.x - Orange CH (Switzerland)
  • x.xx.75.x - Orange ES (Spain)
  • x.xx.110.x - T-Mobile UK (United Kingdom)
  • x.xx.111.x - T-Mobile DE (Germany)
  • x.xx.112.x - T-Mobile AT (Austria)
  • x.xx.114.x - T-Mobile NL (Netherlands)
  • x.xx.118.x - T-Mobile PL (Poland)
  • x.xx.161.x - Vodafone UK (United Kingdom)
  • x.xx.166.x - Vodafone CH-DE (Switzerland - Germany)
  • x.xx.163.x - Vodafone FR (France)
  • x.xx.169.x - Vodafone AT (Austria)
  • x.xx.206.x - O2 UK (United Kingdom)
  • x.xx.207.x - O2 DE (Germany)
  • x.xx.401.x - World Wide English
  • x.xx.707.x - Asia WWE (World Wide English)
  • x.xx.720.x - Asia India
  • x.xx.771.x - Hutchison 3G UK (United Kingdom)
  • x.xx.862.x - Voda-Hutch AU (Australia)
  • x.xx.980.x - Optus AU (Australia)
  • x.xx.1400.x - HTC China
 
Last edited:

wolfraim

Senior Member
Dec 9, 2009
374
78
Santiago
orgulloateo.tumblr.com
Sometimes when you have a custom rom, you can not update your stock ruu for signature problems (difference between boot, hboot, recovery versions), try to include the TUT to flash the stock RUU and then your TUT :)
 
  • Like
Reactions: abarg28

GabrielSousa

Senior Member
Feb 15, 2011
4,438
2,072
Leiria
OnePlus 9 Pro
Sometimes when you have a custom rom, you can not update your stock ruu for signature problems (difference between boot, hboot, recovery versions), try to include the TUT to flash the stock RUU and then your TUT :)

thats why you need to flash a stock custom rom, on recovery first, to avoid signature problems (the same rom from the right RUU)
 
Last edited:
  • Like
Reactions: gt4steve

Neo XL

Senior Member
Feb 24, 2006
1,071
142
62
Kassel
OPPO Reno 10x Zoom
Tell me, why should be this way the only way to get the updates? Yesterday i tried it, like its written here and all went okay. The only correction to do is in point 2: fastboot erase cache

http://xdaforums.com/showthread.php?t=1609190

  1. Flash a ROM and boot image based on 1.26 (e.g ARHD 2.1)
  2. Clear fastboot cache Code:
    fastboot clear cache
  3. Boot your phone
  4. Charge you phone completely
  5. Download stock recovery
  6. Flash stock recovery Code:
    fastboot flash recovery endeavoru_recovery_signed.img
  7. Relock bootloader Code:
    fastboot oem lock
  8. Run 1.26 RUU
 
  • Like
Reactions: nbicho

GabrielSousa

Senior Member
Feb 15, 2011
4,438
2,072
Leiria
OnePlus 9 Pro
Tell me, why should be this way the only way to get the updates? Yesterday i tried it, like its written here and all went okay. The only correction to do is in point 2: fastboot erase cache

http://xdaforums.com/showthread.php?t=1609190

  1. Flash a ROM and boot image based on 1.26 (e.g ARHD 2.1)
  2. Clear fastboot cache Code:
    fastboot clear cache
  3. Boot your phone
  4. Charge you phone completely
  5. Download stock recovery
  6. Flash stock recovery Code:
    fastboot flash recovery endeavoru_recovery_signed.img
  7. Relock bootloader Code:
    fastboot oem lock
  8. Run 1.26 RUU

whats your CID ? and what RUU file did you run ?
i think the rom on the phone must be from the same CID of the RUU, but dont have sure. (only applies to non super CID phones)
 
Last edited:

Neo XL

Senior Member
Feb 24, 2006
1,071
142
62
Kassel
OPPO Reno 10x Zoom
That´s right. The CID is inside the device and the RUU has to be the same. But custom roms don´t change the cid, because for this you must have S-Off. At this time the original cid will not be replaced by another. But in the old method all runs well.
I have an o2 device, cid is O2___102, this was never changed by any custom rom.
 
Last edited:

GabrielSousa

Senior Member
Feb 15, 2011
4,438
2,072
Leiria
OnePlus 9 Pro
That´s right. The CID is inside the device and the RUU has to be the same. But custom roms don´t change the cid, because for this you must have S-Off. At this time the original cid will not be replaced by another. But in the old method all runs well.
I have an o2 device, cid is O2___102, this was never changed by any custom rom.

EXACTLY .... the ARHD 2.1 is base on x.xx.401.xx ?
401 is RUU_ENDEAVOR_U_ICS_40_HTC_Europe


so i dont understand how your method worked for you....
you should use a rom base from a O2-DE O2___102 RUU

because a rom base on on x.xx.401.xx didnt work for me (my CID VODA-UK VODAP001)
 
Last edited:
  • Like
Reactions: brenopoubel

graemeg

Senior Member
Dec 16, 2011
309
50
Dumfries and Galoway
HI

Firstly thanks for all the effort you put in around the forum, ive read quite a few of your posts.
I notice youve done a custom Vode rom, is there any chance of doing a H3G__001, im on the 3 network and would like to be able to flash the latest H3G rom if i ever want to go stock again, obviously being an unlocked Orange phone it wont let me, or if you arent able too, time concerned and stuff which i understand, could you point me in the direction of where i could find the info needed on whats involved.

Many Thanks.
 

brenopoubel

Senior Member
Jan 16, 2010
220
15
I already tried to flash rom.zip from

RUU_ENDEAVOR_U_ICS_40_hTC_Asia_TW_1.29.709.7_Radio_1.1204.104.14_release_259284_signed

and

RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.7_Radio_1.1204.104.14_release_259281_signed

both i got

E: Can't open /sdcard/rom.zip
(bad)
Installation aborted.

Any ideas?
 

GabrielSousa

Senior Member
Feb 15, 2011
4,438
2,072
Leiria
OnePlus 9 Pro
HI

Firstly thanks for all the effort you put in around the forum, ive read quite a few of your posts.
I notice youve done a custom Vode rom, is there any chance of doing a H3G__001, im on the 3 network and would like to be able to flash the latest H3G rom if i ever want to go stock again, obviously being an unlocked Orange phone it wont let me, or if you arent able too, time concerned and stuff which i understand, could you point me in the direction of where i could find the info needed on whats involved.

Many Thanks.


for you is RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.28.771.9 , i will make it a stock rom. give me 1 or 2 days ;)
 
  • Like
Reactions: graemeg

GabrielSousa

Senior Member
Feb 15, 2011
4,438
2,072
Leiria
OnePlus 9 Pro
I already tried to flash rom.zip from

RUU_ENDEAVOR_U_ICS_40_hTC_Asia_TW_1.29.709.7_Radio_1.1204.104.14_release_259284_signed

and

RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.7_Radio_1.1204.104.14_release_259281_signed

both i got

E: Can't open /sdcard/rom.zip
(bad)
Installation aborted.

Any ideas?


since we dont have s-off you cant change your CID to superCID.you have to use the right RUU,

for you is RUU_ENDEAVOR_U_ICS_40_hTC_Asia_India_1.26.720.2 ( i think)
 
Last edited:

EddyOS

Senior Member
Jan 2, 2010
15,279
4,034
London
I already tried to flash rom.zip from

RUU_ENDEAVOR_U_ICS_40_hTC_Asia_TW_1.29.709.7_Radio_1.1204.104.14_release_259284_signed

and

RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.7_Radio_1.1204.104.14_release_259281_signed

both i got

E: Can't open /sdcard/rom.zip
(bad)
Installation aborted.

Any ideas?

You don't flash the ROM.zip from the RUU in CWM - you have to rename it PJ46IMG.zip and flash it from HBOOT
 

Top Liked Posts

  • There are no posts matching your filters.
  • 57
    (this is the only way we have now to upgrade the hboot.img, bct.img, rcdata.img, etc...)

    Method 1



    • Install stock rom of your CID
    -fastboot oem readcid (to know your CID)
    -all roms are based on x.xx.401.xx , so you need to download the right RUU(that matches your CID) and extract rom.zip to cook a stock rom for you
    -flash custom stock rom(extracted and cooked from right RUU) on custom recovery
    -fastboot flash boot c:\boot.img (flash stock kernel that's inside custom stock rom boot.img file)



    • RElock the bootloader (you can allways unlock)
    -fastboot oem lock



    • Right RUU file for your CID
    -put your phone on fastboot (it will not boot because you have a custom rom on a locked bootloader)
    -now you can run the RUU exe file and upgrade your phone


    Method 2




    • Extract the rom.zip from RUU of your CID (google how extract ruu.exe)
    -fastboot oem readcid (to know your CID)

    • Extract boot.img, system.img, signed_recovery.img from rom.zip

    • Flash
    -fastboot flash recovery signed_recovery.img
    -fastboot flash boot boot.img
    -fastboot flash system system.img
    -fastboot erase cache
    -fastboot oem lock

    • Power on the phone

    • Run the RUU exe file (of your CID) and upgrade your phone

    Method 3 (like Method 2, but we dont need to flash the system) (thanks to EddyOS)




    • Extract the rom.zip from RUU of your CID (google how extract ruu.exe)
    -fastboot oem readcid (to know your CID)

    • Extract boot.img, signed_recovery.img from rom.zip

    • Flash
    -fastboot flash recovery signed_recovery.img
    -fastboot flash boot boot.img
    -fastboot oem lock

    • Run the RUU exe file (of your CID) in fastboot mode



    • SuperCID 11111111
    • AirTel-India ????????
    • Asia-HK-CHT HTC__622
    • ATT CWS__001
    • BM BM___001
    • Bouygues-Telecom BOUYG201
    • Brightstar-PTB BSTAR502
    • Brightstar-SPA BSTAR301
    • Chunghwa-Taiwan CHT__601
    • CT HTCCN702
    • CU HTCCN703
    • DCM DOCOM801
    • DOPOD DOPOD701
    • Era T-MOB009
    • Fastweb-IT FASTW401
    • GOOGLE GOOGL001
    • H3G-DAN H3G__F05
    • H3G-Italy H3G__402
    • H3G-ROI H3G__003
    • H3G-SWE H3G__G04
    • H3G-UK H3G__001
    • HTC-Asia-SEA HTC__037
    • HTC-Asia-SEA-WWE HTC__044
    • HTC-Australia HTC__023
    • HTC-BE HTC__E41
    • HTC-Czech HTC__C24
    • HTC-Denmark HTC__F08
    • HTC-Dutch HTC__E11
    • HTC-EastEurope HTC__032
    • HTC-ELL HTC__N34
    • HTC-FRA HTC__203
    • HTC-FRA-Bouygues HTC__247
    • HTC-GCC HTC__J15
    • HTC-GER HTC__102
    • HTC-India HTC__038
    • HTC-ITA HTC__405
    • HTC-Nor HTC__Y13
    • HTC-Norway HTC__H10
    • HTC-Poland HTC__B25
    • HTC-PTG HTC__506
    • HTC-Russia HTC__A07
    • HTC-Singapore ????????
    • HTC-SPA HTC__304
    • HTC-Sweden HTC__G09
    • HTC-Turkey HTC__M27
      [*]HTC-WWE HTC__001
    • Hutch-Australia HUTCH001
    • O2-DE O2___102
    • O2-UK O2___001
    • Open-Channel HTCCN701
    • Optus-Australia OPTUS001
    • ORANGE-AT ORANG113
    • ORANGE-BE ORANG012
    • ORANGE-CH-FRA ORANG203
    • ORANGE-CH-GER ORANG104
    • ORANGE-ES ORANG309
    • ORANGE-French ORANG202
    • ORANGE-PL ORANGB10
    • ORANGE-PO ORANG008
    • ORANGE-SK ORANG006
    • ORANGE-SW ORANG216
    • ORANGE-UK ORANG001
    • Rogers ROGER001
    • SMC-Voda-HK SMCVD001
    • StarHub-Singapore ????????
    • TELEF-Spain TELEF301
    • Telstra TELST001
    • TELUS TELUS001
    • TIM-Italy TIM__401
    • TMA T-MOB102
    • TMCZ T-MOB004
    • TMD T-MOB101
    • TMH T-MOB007
    • TMHR T-MOB006
    • TMMK T-MOBL11
    • TMNL T-MOB003
    • TMSK T-MOB008
    • TMUK T-MOB005
    • TMUS T-MOB010
    • TWM-TW HTC__621
    • VIRGIN-UK VIRGI001
    • VODA-Africa-South HTC__016
    • VODA-Australia VODAP021
    • VODA-Germany VODAP102
    • VODA-Greece VODAP006
    • VODA-Ireland VODAP019
    • VODA-Italy VODAP405
    • VODA-Mobilkom VODAP120
    • VODA-Netherland VODAPE17
    • VODA-New-Zealand VODAP022
    • VODA-Portugal VODAPD18
    • VODA-Proximus VODAP024
    • VODA-SA VODAP026
    • VODA-SFR VODAP203
    • VODA-Spain VODAP304
    • VODA-Swisscom-DE VODAP110
    • VODA-Swisscom-FR VODAP212
    • VODA-Swisscom-IT VODAP416
    • VODA-Swisscom-WWE VODAP015
    • VODA-TR VODAPM27
    • VODA-UK VODAP001

    • x.xx.61.x - Orange UK (United Kingdom)
    • x.xx.65.x - Orange CH (Switzerland)
    • x.xx.75.x - Orange ES (Spain)
    • x.xx.110.x - T-Mobile UK (United Kingdom)
    • x.xx.111.x - T-Mobile DE (Germany)
    • x.xx.112.x - T-Mobile AT (Austria)
    • x.xx.114.x - T-Mobile NL (Netherlands)
    • x.xx.118.x - T-Mobile PL (Poland)
    • x.xx.161.x - Vodafone UK (United Kingdom)
    • x.xx.166.x - Vodafone CH-DE (Switzerland - Germany)
    • x.xx.163.x - Vodafone FR (France)
    • x.xx.169.x - Vodafone AT (Austria)
    • x.xx.206.x - O2 UK (United Kingdom)
    • x.xx.207.x - O2 DE (Germany)
    • x.xx.401.x - World Wide English
    • x.xx.707.x - Asia WWE (World Wide English)
    • x.xx.720.x - Asia India
    • x.xx.771.x - Hutchison 3G UK (United Kingdom)
    • x.xx.862.x - Voda-Hutch AU (Australia)
    • x.xx.980.x - Optus AU (Australia)
    • x.xx.1400.x - HTC China
    3
    i have made a stock rom for VODAP001 (x.xx.161.xx)

    i can share it ;)
    2
    YES! It worked. Thanks EddyOS. This is what I did to make it work. Maybe something for first post?

    1. Get the latest RUU for your device here
    2. Open the downloaded exe file.
    3. It takes about a minute before the installer starts
    4. Leave the installer open
    5. Open %temp% and search for rom.zip
    6. Open rom.zip and search for boot_signed.img and recovery_signed.img
    7. Copy those 2 files to the fastboot directory.
    8. Close the installer.
    9. Reboot the phone with power+volume down
    10. Enter fastboot
    11. Connect phone to computer
    12. Use fastboot on computer
    13. Open command and go to fastboot directory.
    14. fastboot flash boot boot_signed.img
    15. fastboot flash recovery recovery_signed.img
    16. fastboot oem lock (to lock your bootloader)
    17. Run the installer exe again and follow instructions
    18. After completion shutdown your phone and reboot the phone with power+volume down
    19. Unlock bootloader with htcdev.com
    20. Install Clockworkmod
    21. Install your custom rom
    2
    added 2 more stock roms ;)
    2
    One should also be VERY careful that you have enough battery % left before you perform the RUU update. The software checks if your battery has sufficient voltage before it proceeds, otherwise it is impossible. And, if you have a custom ROM with a bootloader which has just been re-locked, you can get into trouble.

    The reason is is that the phone will not boot into the custom ROM with a relocked bootloader, nor will your custom recovery (CWM or other) load and you will have no access to it in order to charge. You will be stuck in fastboot mode in which it's impossible to charge.

    The following little script saved my ass when my battery was too low in order to even re-unlock the bootloader in order to get back into the custom ROM. (fastboot commands also check your voltage before it can perform a re-unlock).

    Here's the script if you need to charge your battery if you're ever stuck in fastboot with a custom ROM, re-locked bootloader, and a low battery.

    You need to create BATCH file that essentially reboots the phone every 6 or so seconds in order for the phone to turn off sufficiently long enough to accept a charge. (And, no, simply attempting to turn off the phone and plug it in turns on the screen in fastboot mode and it doesn't charge.) This was the ONLY way I could get enough charge to either re-unlock or perform an RUU update. Once your battery reaches around 1.68 V (1,680 mV), you should have enough charge to re-unlock it to charge normally the rest of the way so that you can again re-lock the bootloader and update with the RUU. Here is the script:

    " @echo off
    :start
    fastboot getvar battery-voltage

    fastboot reboot-bootloader

    ping /n 6 localhost >nul

    goto start
    "