Database Info

Hboot 2.02.0002

Does this hboot makes more complicated to flash roms? I've read that is not possible to format system/lib, so some roms have to be changed. How to delete system/lib then?
Is it advised to stay on that hboot or should be downgraded or s-off?

As far as i know only few latest ICS based ROMs require new HBOOT. I am on Fallout 5.0, worked fine with older HBOOT 6.98.2000 (Revolutionary root)

poled said:
Does this hboot makes more complicated to flash roms? I've read that is not possible to format system/lib, so some roms have to be changed. How to delete system/lib then?
Is it advised to stay on that hboot or should be downgraded or s-off?
Click to expand...
Click to collapse
You can stay on that hboot and use 4EXT Recovery to format /system/lib. It will remain empty when you flash a ROM that is not supporting it so there is nothing to worry about
EDIT: I may be wrong, just saw the post in Scanob thread. But you can test it. Make a nandroid backup (and/or put a ROM on the SDcard), wipe /system/lib from recovery and reboot. If the ROM boots then it is true (/system/lib cannot be wiped). If does not boot (then /system/lib is wiped) reboot back to recovery: "adb reboot recovery" - you need USB debugging enabled in ROM and adb drivers on the PC or with the 3 key combo (hold Vol Down + Vol Up + Power) and restore the backup or flash the new ROM

Can anyone confirm that /system/lib can't be wiped or formated with hboot 2.02.0002 ?
I'd like to try the stock ICS update but I'm afraid that the RUU will replace my hboot (2.00.0002 unlocked) with hboot 2.02.0002.
Sent from my HTC Desire S using xda app-developers app

htc desire s rooted s-on
yaonos said:
Can anyone confirm that /system/lib can't be wiped or formated with hboot 2.02.0002 ?
I'd like to try the stock ICS update but I'm afraid that the RUU will replace my hboot (2.00.0002 unlocked) with hboot 2.02.0002.
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
==========================================================================================================
hello sorry to bother you
well i have a htc desire s with s-0n rooted with HTCDev.com. hboot 2.00.0002
well i have got cwm and backed up my rom.and flashed others no problem but with loading a rom i had to go into command promps and flash a boot.img. well no problem there as i downloaded roms with a boot.img with them.now i want to go back to my original stock rom and load it it loads ok but when i load the boot.img it dose not work.i got the boot img from the back up that i made of my stock original rom.
please help as i would love to know whar i am doing wrong cheers

2009joseph said:
==========================================================================================================
hello sorry to bother you
well i have a htc desire s with s-0n rooted with HTCDev.com. hboot 2.00.0002
well i have got cwm and backed up my rom.and flashed others no problem but with loading a rom i had to go into command promps and flash a boot.img. well no problem there as i downloaded roms with a boot.img with them.now i want to go back to my original stock rom and load it it loads ok but when i load the boot.img it dose not work.i got the boot img from the back up that i made of my stock original rom.
please help as i would love to know whar i am doing wrong cheers
Click to expand...
Click to collapse
Did you try to flash your boot.img in CLI with fastboot like you did when you installed your cutom ROM ?
Edit : Your question has nothing to do with the subject of this thread (Hboot 2.02.0002 ).

The RUU ICS Update installs:
hboot: 2.02.0002
radio: 3831.19.00.110
This also prevents me from updating cause i´m also afraid that rooting and installing custom roms won´t work afterwards.
Is there an opportunity to downgrade from 2.02.0002 to another hboot and install a previous RUU to root it via revolutionary for example?

I'm no expert but, I have HBoot 2.00.0002. HTC dev unlocked. And I have had no problem flashing any rom. I have tried Andromadus, Flinny, NK111, Codename android, and I'm currently using Jelly Time R15.0 as my daily use rom.

I'm not afraid of not being able to root my DS after the ICS RUU. I would be able to unlock the hboot again, flash ext4, then install SuperSu from the recovery.
I'm just afraid that the 2.02.0002 hboot will make it difficult for me to install custom ROMs in the future if this hboot restricts effectively the acess to /system/lib. But I would also like to try the new radio of the ICS RUU.
The alternate path I'm considering to follow is downgrading my hboot, S-OFF by revolutionary, flash hboot 2.00.2002, then flash stock ICS using a PG88IMG.zip where hboot and recovery would be removed.
Sent from my HTC Desire S using xda app-developers app

CUSTOM ROM > Stock ICS from RUU > CUSTOM ROM
Had no problem with the Custom Rom installation..

poled said:
Does this hboot makes more complicated to flash roms? I've read that is not possible to format system/lib, so some roms have to be changed. How to delete system/lib then?
Is it advised to stay on that hboot or should be downgraded or s-off?
Click to expand...
Click to collapse
Yes, this hboot makes it more complicated to flash ROMs because you have to flash the kernel - boot.img - separately using fastboot. But if the ROMs all share the same kernel, then you can skip this step.
The hboot has the extra system/lib partition, but that is only used by the latest stock HTC GB OTA and the HTC ICS RUU. Custom ROMs generally don't use it.
This partition can be formatted, for example using 4EXT, just like the other partitions.
Sent from my Nexus 7

How about flashing RUU_Saga_hTC_Asia_WWE_1.48.707.1_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199476_signed.exe over current Hboot 2.02.0002 with custom ROM?

yaonos said:
Can anyone confirm that /system/lib can't be wiped or formated with hboot 2.02.0002 ?
I'd like to try the stock ICS update but I'm afraid that the RUU will replace my hboot (2.00.0002 unlocked) with hboot 2.02.0002.
Click to expand...
Click to collapse
I personally found that it couldn't flash custom roms without s-off due to being unable to write the /system directory. I had to downgrade the RUU so that I could get S-OFF with revolutionary in order to be able to. If you are upgrading with the ICS stock ROM you won't need to, but you will need to re-lock your hboot to flash the RUU

androvoid said:
I personally found that it couldn't flash custom roms without s-off due to being unable to write the /system directory. I had to downgrade the RUU so that I could get S-OFF with revolutionary in order to be able to. If you are upgrading with the ICS stock ROM you won't need to, but you will need to re-lock your hboot to flash the RUU
Click to expand...
Click to collapse
Not able to write the /system directory? Never heard that one before...
Sent from my Desire S using xda app-developers app

teadrinker said:
Not able to write the /system directory? Never heard that one before...
Sent from my Desire S using xda app-developers app
Click to expand...
Click to collapse
Yeah, I have hboot 2.02.0002 with htc dev unlock and I can write to /system without issues.
Must be something else wrong.

[Q] How to flash BeastMode v3.0 in 1.14 hboot?

Hi all. I am rooted on 2.20, have 1.14 hboot. My understanding in flashing Kernels under the 1.14 hboot is to extract the boot.img from the kernel zip I downloaded, flash it in fastboot, then flash the entire zip within TWRP. BUT I do not see the boot.img in the BeastMode v3.0 zip file that I extracted. Am I missing something? I am trying to flash the BeastMode v3.0 kernel in the ViperXL ROM. Any help is appreciated. Thanks.

robjbw said:
Hi all. I am rooted on 2.20, have 1.14 hboot. My understanding in flashing Kernels under the 1.14 hboot is to extract the boot.img from the kernel zip I downloaded, flash it in fastboot, then flash the entire zip within TWRP. BUT I do not see the boot.img in the BeastMode v3.0 zip file that I extracted. Am I missing something? I am trying to flash the BeastMode v3.0 kernel in the ViperXL ROM. Any help is appreciated. Thanks.
Click to expand...
Click to collapse
You must extract the boot.img via adb after you flash the kernel. Have a look at post #10 in http://forum.xda-developers.com/showthread.php?t=1959395. Thats what worked for me.

ImagioX1 said:
You must extract the boot.img via adb after you flash the kernel. Have a look at post #10 in http://forum.xda-developers.com/showthread.php?t=1959395. Thats what worked for me.
Click to expand...
Click to collapse
THANKS!

Beastmode 4 is out. You can now flash in recovery. Even with the new hboot.
Sent from my HTC One XL using Tapatalk 2

[Q]Kernel flashing not working?

I've flashed every single compatible kernel there is for android 4.0.4 (I'm using the lastest ViperXL Rom) and it keeps returning to the original kernel that comes with the rom.
Is this a rom limitation or something wrong with my recovery?

acompres said:
I've flashed every single compatible kernel there is for android 4.0.4 (I'm using the lastest ViperXL Rom) and it keeps returning to the original kernel that comes with the rom.
Is this a rom limitation or something wrong with my recovery?
Click to expand...
Click to collapse
What's your hboot?
Are you flashing boot.img from fastboot first before you install the kernel, if you have 1.14?

Myrder said:
What's your hboot?
Are you flashing boot.img from fastboot first before you install the kernel, if you have 1.14?
Click to expand...
Click to collapse
I do have 1.14, although all the instructions on the kernels i've downloaded stated to just flash through twrp and enjoy?

acompres said:
I do have 1.14, although all the instructions on the kernels i've downloaded stated to just flash through twrp and enjoy?
Click to expand...
Click to collapse
fastboot flash boot boot.img
Or downgrade your hboot

[Q] Flashing Desire XS version 1.1, S-On

Hi,
I'm totally new in the rooting/customROM business. I want to flash the Desire XS version 1.1 on my desire s, since the 2.3.5 is a little old now...
I just chose this ROM, because it looked good, no idea... good choice?
I tried to avoid having to ask questions, but I reached a point where I can't get the Inforamtions just from reading anymore and am scared of causing irreperable damage to my phone.
I wanted to ask in the Desire XS version 1.1 directly, but wasn't allowed to.
Well I followed this guide:
http://forum.xda-developers.com/showthread.php?t=1525100
and unlocked my bootloader via HTCdev. I'm still on HBOOT 2.00.0002 and S-On
After having done this, I want FIRST do a full recovery of my system, to be able to go back to 2.3.5 if the new ROM doesn't work. Or is this not necessary?
Furthermore I don't want Reaper v2.1, but Desire XS version 1.1. So I downloaded this and copied on the SD. Now, I "have to copy boot.img into the folder where I have adb and fastboot ". But where can I find boot.img within the ROM? I found it 2 times in \Kernel\b2b and \Kernel\patched. Is one of them the right one?!
Also in the Desire XS version 1.1 thread it is says "I recommend that all users be on radio 20.76.30.0835U_3831.19.00.110 before installing this rom"
But I couldn't find any information to switch to this specific radio (just others).
Some information on my phone:
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2. 00. 0002
RADIO-3822.10.08.04_M
eMMC-boot
Somewhere in the Desire XS-Thread I found this:
Quote:
Originally Posted by roman_kaczynski View Post
Can i use this rom with hboot 2.02.0002 S-ON and radio 3831.19.00.110?
Yes, you have the last radio.
You are s-on, flash boot.img whit fastboot.
Click to expand...
Click to collapse
I'm sorry for opening a new thread, for the many questions and the long explanation, but I tried to make my problem as clear as possible and wasn't allowed to post in the developer's thread about radio and boot.img...
Thanks for the help!

While flashing the rom you have a choice of 2 kernels (b2b and patched). Use the boot.img of the kernel you will be choosing.
If you want to upgrade the radio (while still s-on) you need to relock your bootloader, flash the Ics RUU, unlock your bootloader again. (some users reported camera issues on desire xs with an older radio version, you could try it first with your current radio).

teadrinker said:
While flashing the rom you have a choice of 2 kernels (b2b and patched). Use the boot.img of the kernel you will be choosing.
If you want to upgrade the radio (while still s-on) you need to relock your bootloader, flash the Ics RUU, unlock your bootloader again. (some users reported camera issues on desire xs with an older radio version, you could try it first with your current radio).
Click to expand...
Click to collapse
Thanks. I guess I'll take the b2b kernel then, since it's the one mentioned in the description. or is the other better?!
Also when flashed is there a way back to the version I have now?! (since you didn't answer my question regarding a recovery of the current system) Can I afterwards just recover via a RUU?!
I'm still scared of ending up with a broken phone

You can make a backup in recovery before flashing, just remember to flash the boot.img from your backup as well if you restore it.
The main difference is, the patched kernel supports overclocking and undervolting, the b2b doesn't.

but how can I do a recovery? My phone is not rooted yet and S-Off (it's just unlocked), is it possible to create a recovery like that?
edit: I found my exact system (2.10.166.3) on htcdev, I guess in the worst case I'll be able to get it back from there. I hope just hope for the best! =)

eggerph said:
but how can I do a recovery? My phone is not rooted yet and S-Off (it's just unlocked), is it possible to create a recovery like that?
edit: I found my exact system (2.10.166.3) on htcdev, I guess in the worst case I'll be able to get it back from there. I hope just hope for the best! =)
Click to expand...
Click to collapse
You have to flash the recovery.img in fastboot. (fastboot flash recovery recovery.img)
Them you can choose recovery from the bootloader.

it worked all good. New system is stable and fluent! lot's of fun, thanks!

Can't install any custom Roms....

.....because I've got Hboot 1.27
Tried, but just stuck in boot loop etc.
I've unlocked etc....but nothing works for s-off...the tool says device not supported etc.
Can someone help me out with sensation z710e?
need s-off, but cant do it.....been trying for hours.
thanks
Matt

matthew33 said:
.....because I've got Hboot 1.27
Tried, but just stuck in boot loop etc.
I've unlocked etc....but nothing works for s-off...the tool says device not supported etc.
Can someone help me out with sensation z710e?
need s-off, but cant do it.....been trying for hours.
thanks
Matt
Click to expand...
Click to collapse
You CAN flash roms with hboot 1.27 and S-ON.
The most likely reason for a bootloop is incorrect boot.img
Either flash roms using 4ext SmartFlash
Or manually flash boot.img via
Code:
fastboot flash boot boot.img

matthew33 said:
.....because I've got Hboot 1.27
Tried, but just stuck in boot loop etc.
I've unlocked etc....but nothing works for s-off...the tool says device not supported etc.
Can someone help me out with sensation z710e?
need s-off, but cant do it.....been trying for hours.
thanks
Matt
Click to expand...
Click to collapse
Look here for flashing ROMs with s-on:
http://forum.xda-developers.com/showthread.php?p=25587345
Look here for s-off(unlocked bootloader):
http://forum.xda-developers.com/showthread.php?p=25202517
Sent from my Ouya

Far_SighT said:
You CAN flash roms with hboot 1.27 and S-ON.
The most likely reason for a bootloop is incorrect boot.img
Either flash roms using 4ext SmartFlash
Or manually flash boot.img via
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
I've downloaded viper rom 1.6.3.....do i have to locate a certain file/folder from the extracted rom in order to flash it?
Matt

matthew33 said:
I've downloaded viper rom 1.6.3.....do i have to locate a certain file/folder from the extracted rom in order to flash it?
Matt
Click to expand...
Click to collapse
IF you have 4ext recovery (enable smartflash), perform a full wipe (after backup) and flash.
ELSE, extract boot.img from your rom, boot into fastboot and use
Code:
fastboot flash boot boot.img