Database Info

S-off Original Roms

Well i did s-off my device first and then i did flash the original RUU roms and boot in to bootloader and shocked to find that s-off is still there.... so for whoever asking if flashing the original HTC rom will it s-on back well the ans is no ?

I assume s-off would stay permanently, just the original rom should no longer be rooted.
Sent from my HTC Sensation Z710e using XDA App

yeah so you have to manually flash the su zip file and clockwork mod recovery file... such a pain in the arse lol...

Downgrade Hboot?

hi i upgraded my phone to ics with the rcmix rom. I want to go back to stock because i have to send my phone in but i the ruu utility will not work. i suspect its because of my hboot. is there any way to downgrade it from 1.27.1100 to 1.18.0000? Any help is appreciated

Flash the 1.17 FW, then run the RUU

Your phone is s-off now? If so, extract rom.zip from ruu, and rename PG58IMG, copy to micro sd. reboot to bootloader.
Sent from my HTC Sensation Z710e using xda premium

Which RUU
calvin0512 said:
Your phone is s-off now? If so, extract rom.zip from ruu, and rename PG58IMG, copy to micro sd. reboot to bootloader.
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
Which RUU are you referring to please? Thanks. I have the same issue. I don't like waiting lol.
A
EDIT: Never mind, I got root access now by pushing superuser 3.0 something instead of 2.3.

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.

How to update from 1.85 to 2.20?

I have my phone rooted since the first days of having it.
Never taken OTA update so it's still on 1.85 and it's unlocked but S-ON.
Has TWRP 2.4.3.0 and custom kernel and ROM.
Wanted to try some new roms that require new 2.20 and S-OFF.
Found a method to root 2.20 and get S-OFF, but my question now is how to safely upgrade from my existing condition 1.85/S-ON to 2.20?
Thanks

Why don't you just s-off, then RUU to 3.18, flash TWRP 2.3.3.1, downgrade touchscreen firmware, and then you can flash whatever you want.
Sent from my Evita

timmaaa said:
Why don't you just s-off, then RUU to 3.18, flash TWRP 2.3.3.1, downgrade touchscreen firmware, and then you can flash whatever you want.
Click to expand...
Click to collapse
Agree. Just S-off now, then run the 3.18 RUU.
If you are on 1.85, 2.20 is just an obsolete and unnecessary middle step, at this point.

Thanks to you both. Would you point me to see off procedure for 1.85?
Or it is the same as for 2. 20?
Thanks again
Sent from my HTC One X using xda app-developers app

Soff is the same regardless of software version. There's a sticky in the original android development section.
Sent from my HTC One X using xda app-developers app

Help with RUU'ing to 2.20

I've been running AOSP ROM's on my evita for a while now, but apparently with the 3.4 kernel you now need hboot 2.14 or higher and mine's at 1.09. My phone was unlocked with S-ON, but I did "fastboot oem lock" this morning because I read that it's necessary for an RUU. I downloaded the 2.20 RUU and tried to run the installer but I always get an Error [170] USB Connection Error. I have the HTC and adb drivers installed successfully and have tried to run the RUU as admin in both Sense and fastboot (bootloader). I'm a bit stumped and would really like to get AOSP back on my phone.

You need to S-off first.
Sent from my HTC One X using xda premium

tlazarus said:
You need to S-off first.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Should I use facepalm for that then?
EDIT
I got s-off, but still no go. Still the error 170.
I know on my old Incredible I was able to rename the rom.zip from the RUU as PB99IMG.zip and put it on the root of my sdcard. Then in hboot it would detect it and ask to flash it. This isn't happening on my evita though. Is there a way to do that, or is that only for older htc devices?

Put phone into fastboot and try again. Check error log to see if it fails to identify your phone.
Open command prompt and type adb devices, if it does not see it then try installing new drivers. If it does see it then enter " adb shell reboot oem-78" that will reboot your phone in to RUU ready fastboot. Open ruu and try running it again.
Sent from my HTC One X using xda premium

Venomtester said:
Put phone into fastboot and try again. Check error log to see if it fails to identify your phone.
Open command prompt and type adb devices, if it does not see it then try installing new drivers. If it does see it then enter " adb shell reboot oem-78" that will reboot your phone in to RUU ready fastboot. Open ruu and try running it again.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Where can I find this error log? It did see my device, I did that command (which ended at the black htc screen) and I ran the RUU again but I still get the error 170. I'm also using this RUU http://bugsylawson.com/index.php/fi...320911-2-101053225l-release-271865-signedexe/

Sounds like a bad download. Is it 568.22 mbs? Try roomyshare.com/ruu-evita-ul-cingular.html
You can find it in the list.
Sent from my HTC One X using xda premium

Venomtester said:
Sounds like a bad download. Is it 568.22 mbs? Try roomyshare.com/ruu-evita-ul-cingular.html
You can find it in the list.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
It is that size, though I may try the link you gave.
EDIT
Okay, I think I found out what I've been doing wrong. I found this link http://forum.xda-developers.com/showthread.php?t=2119610 and it turns out that the file I've been trying does NOT include the 2.14 hboot that I need. The one I need is the latest JB release, but someone said that if you flash it with superCID and S-ON that it will brick your device. I have superCID but S-OFF, does anyone think that will brick my device? Should I flash the RUU with the 1.09 hboot (which I'm running) first, and then flash the newest RUU? Also, it looks like the link I provided offers flashable OTA's of each update. Would those work/be recommended for TWRP?

Change cid to cingular "cws_001" I think. Super cid can cause brick.
Sent from my HTC One X using xda premium

Venomtester said:
Change cid to cingular "cws_001" I think. Super cid can cause brick.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Well I didn't do that...haha. I read on another forum that TWRP doesn't support that cid check function or something and to just remove it from the updater-script so I tried that and flashed the latest OTA zip in TWRP and it failed after a few steps. I tried booting and it didn't get to the boot animation so I rebooted to recovery and restored my backup. I'm going to try a stock zip without the modified updater-script and restore my CID to normal and try again.
EDIT
Well, I restored the CID to CWS__001 and I still get that check_cid error

dshoe said:
Well I didn't do that...haha. I read on another forum that TWRP doesn't support that cid check function or something and to just remove it from the updater-script so I tried that and flashed the latest OTA zip in TWRP and it failed after a few steps. I tried booting and it didn't get to the boot animation so I rebooted to recovery and restored my backup. I'm going to try a stock zip without the modified updater-script and restore my CID to normal and try again.
EDIT
Well, I restored the CID to CWS__001 and I still get that check_cid error
Click to expand...
Click to collapse
To run a ota you need to flash stock recovery image.. and bootloader needs to be unlocked for that
Sent from my HTC One XL using xda premium

31ken31 said:
To run a ota you need to flash stock recovery image.. and bootloader needs to be unlocked for that
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Hm, okay then, let me ask another question. I'm on hboot 1.09 and I need 2.14 to run AOSP ROM's now. What's the best way to get there if I already have ROM's installed. Is it what I'm doing right now or should it be something else?
EDIT
The latest JB RUU is picking up my device now and offering the update, 2 seconds away from doing it....

dshoe said:
Hm, okay then, let me ask another question. I'm on hboot 1.09 and I need 2.14 to run AOSP ROM's now. What's the best way to get there if I already have ROM's installed. Is it what I'm doing right now or should it be something else?
EDIT
The latest JB RUU is picking up my device now and offering the update, 2 seconds away from doing it....
Click to expand...
Click to collapse
Just make sure you are s-off before running ruu or risk a brick..
Sent from my HTC One XL using xda premium

Hi. I am looking my update my hboot from 1.09 to 2.14. I am S-OFF now, also running the Sense 5 rom now(TWRP recovery).
I have downloaded the Latest JB 3.18 RUU from instructions here http://forum.xda-developers.com/showthread.php?t=2064621.
What else do I need to do before flashing the RUU to the device?

For what it's worth, I was on stock 2.20, got s-off and unlocked bootloader with superCID, and ran the 3.18 RUU with no problems. I didn't need to relock or anything.

knanda said:
Hi. I am looking my update my hboot from 1.09 to 2.14. I am S-OFF now, also running the Sense 5 rom now(TWRP recovery).
I have downloaded the Latest JB 3.18 RUU from instructions here http://forum.xda-developers.com/showthread.php?t=2064621.
What else do I need to do before flashing the RUU to the device?
Click to expand...
Click to collapse
You can go ahead and run the RUU. No real risk because you're s-off. Maybe make a backup though.
Sent from my Evita