Database Info

How to root hboot 2.00.0002

Hey guys, normally I would just lurk and avoid posting threads but I need help.
I want to root my Desire S.
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
When I click recovery on the bootloader screen I get taken to "Android system recovery <3e>", but when I try to apply an update through USB I get the following error message:
"Invalid operation:
reason: oem-00"
And then the phone just reboots.
If anyone can help I'd be very grateful.
Thanks.

Since you are unlocked via HTCDEV you can do...
If all you need is root then just run superoneclick, easy as that.
If you have your heart set on using recovery.... You need to flash a custom one (the stock one won't do), download clockworkmod .img and flash it in recovery.
Also if you ever choose to flash roms etc you will need a custom recovery.
If you choose to to go the custom recovery path here is a how to.
______________________________________
-Download attached file titled "android-tools.zip", it has the adb and fastboot files needed to proceed
-Extract the file to "c:\" so that the path looks like this C:\android-tools
-Install HTCDriver (Fastboot drivers) here's
-Open cmd and type "cd/"
-then type "cd android-tools"
*To test whether you have set up all the files correctly and your phone is connected correctly you can do the following;
*Plug your phone in (when plugging in select CHARGE ONLY (i.e. leave on the home screen)
*In cmd type "adb" and press enter, it should show a list of commands, then type "fastboot"and press enter, it should also show a list of commands)
*If both these commands work you have extracted the files to the right place and have setup cmd right.
*then type "adb devices"
*Should show connected phone serial if not then try get the latest HTCdrivers
-Download clockworkmod (here) for your phone and place .img in C:\android-tools folder (i.e. where the files adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll and fastboot.exe are)
*To make life easier rename the file to recovery.img
-start fastboot (boot Hboot, plug phone in "HBoot USB plug" shows once phone is plugged in and press the power button (fastboot is highlighted by default) then it says "Fastboot USB")
*(As a test to ensure you have put your phone into fastboot type "fastboot devices" in cmd, it will show your phones serial, if it shows nothing you have not put your phone into fastboot yet)
-run command "fastboot flash recovery recovery.img" in cmd
-then run "fastboot reboot"
NEXT - to get root
-Copy su-3.0.5-efgh-signed.zip to sdcard root (get latest from clockworkmod site if you wish)
-Start clockworkmod recovery (Hboot/recovery)
-Select install zip from sdcard"
-select Choose zip from sdcard
-Select copied file
-select Yes - install su-3.0.5-efgh-signed.zip to confirm
-Go back
-Then reboot.
All Done.

I would like to do the same thing, but mine says
*** LOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
Does that mean that I'm f**ked ?

@kryddan
Since you are locked and hboot 2.00.0002 you can either downgrade to an older hboot or unlock your bootloader with HTCdev (may void warranty).
Both are very well discussed here.

foX2delta said:
@kryddan
Since you are locked and hboot 2.00.0002 you can either downgrade to an older hboot or unlock your bootloader with HTCdev (may void warranty).
Both are very well discussed here.
Click to expand...
Click to collapse
Downgrade sounds like going backwards. Think I'll search for HTCdev instead
It worked fine with HTCdev to unlock Ok, so it wiped the phone clean from personal data and apps, but who cares. It worked.
Thank you for your help. but go from S-ON to S-OFF seems a bit harder, without downgrade?
p.s. Have already voided my warranty. Got a new mainboard last week. d.s.

kryddan said:
Downgrade sounds like going backwards. Think I'll search for HTCdev instead
It worked fine with HTCdev to unlock Ok, so it wiped the phone clean from personal data and apps, but who cares. It worked.
Thank you for your help. but go from S-ON to S-OFF seems a bit harder, without downgrade?
p.s. Have already voided my warranty. Got a new mainboard last week. d.s.
Click to expand...
Click to collapse
the hboot is your bootloader and manages things like partitioning your volume for system, data etc.
downgrading it will never mean going backwards.
what you could have done was downgrading hboot, s-off with revolutionary and get root with superoneklick. thats what i did (but hboot was already fine for me ) then you could install new recovery and done.
its not that hard
but since you have unlocked with htcdev anything you do with your phone will be (at least a bit) harder than with s-off.

Can't flash recovery/ROMs/achieve root?

I achieved the unlocked bootloader, at least I believe, per instructions via the HTC website. But I can't seem to be able to flash a recovery or achieve root. I can boot into HBOOT, when I try to click Recovery, it takes me to some page explaining software is not to be distributed, blah blah. Then it just boots up like normal?
I'm afraid I don't understand? Everything i've tried fails, why is that?

New Jer-Z said:
I achieved the unlocked bootloader, at least I believe, per instructions via the HTC website. But I can't seem to be able to flash a recovery or achieve root. I can boot into HBOOT, when I try to click Recovery, it takes me to some page explaining software is not to be distributed, blah blah. Then it just boots up like normal?
I'm afraid I don't understand? Everything i've tried fails, why is that?
Click to expand...
Click to collapse
You skipped right over the "can't seem to able to flash a recovery."
Please explain in detail the instructions you followed AFTER unlocking via HTCdev.com. This includes files you downloaded, where you put them, how you attempted to flash, etc.
These details will be very helpful. Don't worry, sounds like you're not in any serious trouble at all. Just don't go flashing anything you see.
Also, please post this to the Q&A forum or General next time. This development forum is intended for development posts ONLY (ie. ROMs, Kernels, Radio's, etc). Just a heads up. Welcome to the forums

Aahhh, forgive me!
And thank you for the patience and understanding!
I used the Hasooon2000 toolkit. I got as far as getting to the screen where HTC wants to confirm with me that I do want to unlock the bootloader, I clicked yes, and it rebooted. Then I tried to flash recovery. The CMD prompt will say it was pushed to the phone successfully, but when I try to reboot into recovery, I don't get very far. To my understanding, I can't apply perm root without getting to recovery, but with the bootloader unlocked, why can't I even flash one?

Moved To Q&A​
Please post all questions in the Q&A section​

New Jer-Z said:
Aahhh, forgive me!
And thank you for the patience and understanding!
I used the Hasooon2000 toolkit. I got as far as getting to the screen where HTC wants to confirm with me that I do want to unlock the bootloader, I clicked yes, and it rebooted. Then I tried to flash recovery. The CMD prompt will say it was pushed to the phone successfully, but when I try to reboot into recovery, I don't get very far. To my understanding, I can't apply perm root without getting to recovery, but with the bootloader unlocked, why can't I even flash one?
Click to expand...
Click to collapse
Ahhh, not to stir up the pot here, but you're getting vague again with what's going on. You say "when I try to reboot into recovery, I don't get very far". What do you mean by this? Details are extremely important in helping you. Sounds like you're saying that recovery was successfully pushed, but then I didn't get any details as to what's going on when you attempt to load recovery. Also, which recovery file did you use? Use this one
I'm not trying to get on to your case here, but you've got to be really specific when you say stuff doesn't work, because that doesn't help us diagnose your issue. When your recovery is done flashing, you should be able to access the bootloader by holding Pwr + Vol-Down for like 5 secs, then choose recovery (that or fastboot>recovery....I cant recall if recovery is a main menu item). What happens after you choose that? Mine shows the htc splash screen, with a development message in red, and then it boots Clockworkmod.

No, no, lol I totally understand, I guess I am being vague.
I was going to go into details, but I was at work. Interestingly enough, my phone died, and when I plugged it and let it charge for a little bit, the phone booted right into CWM touch - so odd! So I was like, ok, i've achieved root - well, no, cuz I opened ROM Manager and it says SU couldn't be found.
BEFORE, when I would do what you said I should do, it would take me to the HTC splash screen where it was in red text, some disclaimer about some proprietary information crap, then it would skip recovery and just boot into Android -___-
Let's see if I can replicate booting into recovery now. (What method are you using to flash your recoveries?)
EDIT: Well it looks like I can't get back into recovery. Same thing as mentioned above. I can get to the fastboot screen, but if I click recovery, it takes me to that HTC disclaimer screen, the little loading bar loads then - poof - screen goes blank and Android boots up.

I have the same problem -_-! Can someone help please
The recovery image was flashed succesfully from Hasoon2000's toolkit. But when i go to the bootloader and select Recovery, I get the red warning for from HTC about how this is for development purpose only... then the phone's screen goes black, then it boots into the stock ROM.

Cant flash recovery
Hello everyone.
I have a similar problem. I successfully proceeded with the bootloader, but now I can't install the recovery. It simply wont flash.
I was following the xda tutorial that's in this very forum, but i got stuck: In my desktop i downloaded the needed files (or so I believe), and so i have in my desktop a folder called "carpeta" (random name) with these files within: adb.exe, adbwinapi.dll, fastboot and 3 different recovery images i have tried to flash.
I use mac, so i open the command prompt for mac (terminal) and go to the "carpeta" folder and after that, I type "cd fastboot flash recovery xxxxx.img" (the xxx are the names of the recovery images that i have in the folder, one at a time) but it simply wont flash anything. I attach a screenshot to ilustrate what happens...
Please help me
http :// img710.imageshack.us/img710/6026/capturadepantalla201205.png

Guys it works if you flash the recovery manually through the command prompt. I think there might be a bug or something in the toolkit because the manual way worked for me.
Here is what I did:
(I am not a programmer so I can't guarantee this will work for you. Worked for me, but try at your own risk)
-Copied the recovery image to the same folder as abd
-Plugged in the phone with USB debugging on
-Opened command prompt
-navigated to the folder with adb with "cd folder_location"
-typed: "adb kill-server", then "adb devices"to make sure the device was connected
-typed "adb reboot-bootloader" to boot into bootloader
-typed "fastboot flash recovery recovery_file_name.img"
-Select bootloader>recovery using the vol up and down and pwr button
and voila recovery
Hope this helps

I'll give it a shot later tonight on my lunch break.

batiste93 said:
Guys it works if you flash the recovery manually through the command prompt. I think there might be a bug or something in the toolkit because the manual way worked for me.
Here is what I did:
(I am not a programmer so I can't guarantee this will work for you. Worked for me, but try at your own risk)
-Copied the recovery image to the same folder as abd
-Plugged in the phone with USB debugging on
-Opened command prompt
-navigated to the folder with adb with "cd folder_location"
-typed: "adb kill-server", then "adb devices"to make sure the device was connected
-typed "adb reboot-bootloader" to boot into bootloader
-typed "fastboot flash recovery recovery_file_name.img"
-Select bootloader>recovery using the vol up and down and pwr button
and voila recovery
Hope this helps
Click to expand...
Click to collapse
tried unsuccessfully.
on screen this is what I see in my htc one s:
***unlocked***
vle put ship s-on rl
radio- o.15.315018.19_2
opendsp-v21.1.0.32.0314
emmc-boot
mar 15 2012.23:37:23
fastboot usb
bootloader
reboot
reboot bootloader
powerdown
------------------
and each time i try to flash the recovery, i get a "not a directory" or "no such file or directory" message...

alexjuanes said:
tried unsuccessfully.
on screen this is what I see in my htc one s:
***unlocked***
vle put ship s-on rl
radio- o.15.315018.19_2
opendsp-v21.1.0.32.0314
emmc-boot
mar 15 2012.23:37:23
fastboot usb
bootloader
reboot
reboot bootloader
powerdown
------------------
and each time i try to flash the recovery, i get a "not a directory" or "no such file or directory" message...
Click to expand...
Click to collapse
Make sure that you navigate to the proper folder using the "cd" command.(for example" cd C:\Fastboot ", if your adb and recovery are in that location)
Make sure that the Clockwork Mod recovery file is in the same folder as the adb and make sure that you type the file name correctly
I used these file and put the recovery image inside the folder after unzipping
http://www.mediafire.com/?50baad8rykng2j0
Here is the recovery I used :
http://loadbalancing.modaco.com/download.php?file=r2-modaco-recovery-clockwork-touch-ville.img
But your running Mac so I don't know if the method I used will work for you because I'm on Windows

Doesnt work...
I have the bootloader (when i start in bootloader mode my phone says ***tampered*** and also ***unlocked***.
BUT
I've been 2 days trying to flash my recovery on my htc one s from my macbook, and after i use the command prompt to get to the folder where i have adb, fastboot, my recovery .img file,etc... this is what happens:
-----
MacBook-Pro-de-Alejandrolatform-tools alexjuanes$ fastboot flash recovery r2-modaco-recovery-clockwork-touch-ville.img
-bash: fastboot: command not found
MacBook-Pro-de-Alejandrolatform-tools alexjuanes$
-----
ive already updated all that i could in the sdk manager, or whatever its name is...
please some help?

batiste93 said:
Guys it works if you flash the recovery manually through the command prompt. I think there might be a bug or something in the toolkit because the manual way worked for me.
Here is what I did:
(I am not a programmer so I can't guarantee this will work for you. Worked for me, but try at your own risk)
-Copied the recovery image to the same folder as abd
-Plugged in the phone with USB debugging on
-Opened command prompt
-navigated to the folder with adb with "cd folder_location"
-typed: "adb kill-server", then "adb devices"to make sure the device was connected
-typed "adb reboot-bootloader" to boot into bootloader
-typed "fastboot flash recovery recovery_file_name.img"
-Select bootloader>recovery using the vol up and down and pwr button
and voila recovery
Hope this helps
Click to expand...
Click to collapse
This actually worked for me. I am rooted, and am now running a custom ROM.
Thanks so much for all your help!

Hey everyone
i seem to have made a very tiny bit of progress here since now i can type the commands and make it start, but only that... starting.
my command box is stuck in a "waiting for device" message that will start nothing, and my phone is just there, untouched.
i never thought flashing a recovery would give me this much of a long headache...
help anyone? how do i make my pc stop "waiting for device"?

Have you tried a different USB cable/port? I had a similar problem but moving to a different port worked.
Sent from my HTC VLE_U

I have the same problem i did everything as in the guide posted here http://forum.xda-developers.com/showthread.php?t=1583427
But when i flash recovery through fastboot ( fastboot flash recovery recoveryname.img) everything goes ok but when i want to boot into recovery i get stuck on the HTC screen.
Than i wanted to go to recovery trough fastboot ( fastboot boot recovery ) i get message cannot load recovery.
If you need more info for help i can provide you guys with the screenshots.
Thanks in advance Nikola.

Red triangle after official ICS

Hello,
I have troubles with my phone which won't boot. I installed official ICS exe on my computer and after update wizard said that was successfully finished.
When I turn on phone first is HTC sign and then is blank black screen (lightly illuminated) and stays there.
If I remove SD card then I get the red triangle message.
What could be wrong? How do I fix this?
regards
If i press volume down and power:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3831.19.00.110
eMMC-boot
Mar 10 2011, 14:58:38
HBOOT
If i press recovery it goes to black screen again

Do not, ever, EVER, install an official ROM throught the RUU while being on S-OFF

yes, your phone was s-off and you should update by using PG88IMG.zip instead of RUU file.
Do you have goldcard backup? If so you can use goldcard to unbrick.

Yeah I know that now.
I have nothing backed up.
Please do tell me I have hope.

usyn1 said:
Yeah I know that now.
I have nothing backed up.
Please do tell me I have hope.
Click to expand...
Click to collapse
volume up + pwr button ?

Nothing,
only power button + vol down works.
Actuly I have somewhat backup file on SD. It is located in clockworkmod --> backup --> folder --> 6 files in it.

usyn1 said:
Nothing,
only power button + vol down works.
Actuly I have somewhat backup file on SD. It is located in clockworkmod --> backup --> folder --> 6 files in it.
Click to expand...
Click to collapse
may be it is nandroid backup
can you boot to custom recovery? If yes you can restore from there

I can boot up to bootloader (vol down + pwr)
I can select:
FASTBOOT (reboot reboot bootloader and power down) -> all works
RECOVERY (do not work) phone restarts to HTC logo and then blank screen
FACTORY RESET (do not work) phone restarts to HTC logo and then blank screen
SIMLOCK (dont know?)
IMAGE CRC (work)
In backup folder:
boot.img
cache.img
data.img
nandroid.md5
recovery.img
system.img

usyn1 said:
I can boot up to bootloader (vol down + pwr)
I can select:
FASTBOOT (reboot reboot bootloader and power down) -> all works
RECOVERY (do not work) phone restarts to HTC logo and then blank screen
FACTORY RESET (do not work) phone restarts to HTC logo and then blank screen
SIMLOCK (dont know?)
IMAGE CRC (work)
Click to expand...
Click to collapse
If you can get to fastboot then surely you should be able to use ADB to connect to your phone?

Please tell me more about ADB? How can I try if I am able to use ADB?

have you tried to enter fastboot, connect to PC with USB, and flash the custom recovery once more? Probably, when you tried to apply the RUU - it overwrote the custom recovery with the official one, so you need to reflash the custom one back, access it, and restore a nandroid backup from within it. Then, either use the method to upgrade to ICS but keep root and s-off, or go completely stock and and upgrade to official ICS (with a possibility to root it), or simply flash the prerooted official ICS ROM

Sorry for my noob questions.
I need some software on my PC to flash from computer? Thank you for all you are helping.

usyn1 said:
Sorry for my noob questions.
I need some software on my PC to flash from computer? Thank you for all you are helping.
Click to expand...
Click to collapse
things that you need are:
- ADB.exe
- Fastboot.exe
- few .dll files that allow these two to work on your computer
- Fastboot drivers
- and an .img file of the required custom recovery
You can find all of these somewhere in Desire S forums, just search for keywork "[GUIDE]"
Then you can simply follow the instructions from the guide on how to use the adb and fastboot, and you'll be back up and running in no time
And because you're already S-OFF, all you need to do is get the files I listed above, unpack the archive with them in somewhere like C:/, open command prompt, get into bootloader, select "FASTBOOT", and enter the "fastboot flash recovery (recovery name).img" command, then reboot into bootloader again with "fastboot reboot-bootloader" command, and then you'll be able to access the newly flashed custom recovery to restore your backup, and return your phone to life
Seems complicated in text format, but it's actually easier than you might think
EDIT #1: Look here - http://forum.xda-developers.com/showthread.php?t=1186401

Many thanks, I will try and report back!
And if I understand when I install ADB I must go for cmd..?

usyn1 said:
Many thanks, I will try and report back!
And if I understand when I install ADB I must go for cmd..?
Click to expand...
Click to collapse
you don't need to install anything other than drivers to allow your PC to work with adb/fastboot commands through CMD. And, if I remember correctly, you should also deinstall HTC Sync program and delete any HTC drivers present on your system currently. Then install fastboot drivers, and you're good to go.
Good luck mate

F.Y.I, if your hboot is ENG S-OFF you can run RUU to update and it will NOT brick your phone.
And here is some link for you to install custom recovery:
- HTC Driver:
www.htcaddicts.com/download.php?id=318
- Android tool (contains adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll, fastboot.exe):
http://www.mediafire.com/?4dx982z93w8z7wk
- Custom recovery image (4EXT):
http://downloads.saga-lbc-mod.de/recovery-images/4EXTRecovery_v2.1.0_saga.zip
Download and extract recovery.img from the zip file.
How to flash recovery: open DOS command prompt in the folder where edb.exe is located (recovery.img file should be in the same folder) and type:
adb reboot bootloader
fastboot flash recovery recovery.img
Hope this help, good luck

Wow vndnguyen!
I managed to acess 4EXT recovery v2.1.0.
Now I restored system to 2.3.5 sense 3.0 HBOOT and other is the same.
What I need now to do to get ICS the right way? Is this guide good? http://forum.xda-developers.com/showthread.php?t=1858508 I am getting: can't open '/sdcard/hboot.img': No such file or directory

You probably forgot to enable the USB debugging mode? And try to download ADB again

I swapped SD card then it worked.
Successfully installed ICS thank you guys, hope this will be useful for someone.

congratulation

[Q] Help please - only able to boot to Bootloader

Ok, so this is a bit of a cry for help. I'm not a non-techie, but am not massively familiar with this stuff - my first foray into trying to root my HTC One Mini has not gone so well so far.
First off, I unlocked the Bootloader as per HTCDev. On reboot, that left me in a boot loop, with just the htc splash, followed by a One Mini splash, then reboot.
Noting some others had had similar problems, I carried on following iconspiracy's method here: http://forum.xda-developers.com/showthread.php?t=2442043.
However, at step 9 of that, I was still in the same old boot loop. Spotting some advice that re-locking the bootloader would remove the boot loop, I foolishly re-locked it. Now it will only boot into the bootloader, and I am unable to get into the recovery. Help!? Any ideas welcomed.
Here is what is showing on the screen:
***TAMPERED***
***RELOCKED***
***Security Warning***
M4_UL PVT SHIP S-ON RL
HBOOT-2.19.0000
RADIO-1.19.40d.00.14
OpenDSP-v13.2.0268.0620
OS-1.31.401.1
eMMC-boot 1024MB
Aug 7 2013, 17:37:54.0
then the usual bootloader stuff.
Thanks massively in advance!

Aha. Now re-unlocked and back in to TWRP. Would someone be kind enough as to suggest a next step - I'm a bit at a loss?

Well, I tried the same thing again, flashing the ROM and Kernel through adb sideload. Back to the same old boot loop.

Try doing a system restore, if that doesn't work try flashing a rom (Jmz's or MagioRom) in case yours somehow got messed up.

Returning to my phone this morning it booted, after a bit of a wait. Then I noticed SuperSU wasn't installed and went back into the recovery to do that. On reboot, back to that boot loop! Will try again after work.

asb56 said:
Returning to my phone this morning it booted, after a bit of a wait. Then I noticed SuperSU wasn't installed and went back into the recovery to do that. On reboot, back to that boot loop! Will try again after work.
Click to expand...
Click to collapse
Hey man! I know it's a hassle to get the phone to reboot until you're s off and relock the bootloader. I found it working better to power off and leave it off for a while and then power on instead of the regular reboot. It also helps if you do a super whipe and factory restore to be able to boot while your bootloader is unlocked.
HTC ONE mini
S-OFF

iconspiracy said:
Hey man! I know it's a hassle to get the phone to reboot until you're s off and relock the bootloader. I found it working better to power off and leave it off for a while and then power on instead of the regular reboot. It also helps if you do a super whipe and factory restore to be able to boot while your bootloader is unlocked.
HTC ONE mini
S-OFF
Click to expand...
Click to collapse
Thanks for replying! I did manage to get it to boot once more, but then I decided to see if that was a stable state - no dice, back to the loop.
Weird thing is, if I re-lock the bootloader at this point, I can only boot to the bootloader.

By the way, here's what I've done (anything leap out as wrong?):
boot into TWRP
wipe Dalvik, Cache, Data, System
boot into bootloader
fastboot flash boot boot.img (using the boot.img from jmz's stock Odexed WWE ROM)
boot into TWRP, set up sideload
adb sideload ROM.zip (using the same ROM)
wipe dalvik, cache
boot into bootloader
fastboot flash boot boot.img (using the boot.img from jmz's Kernel)
boot into TWRP, set up sideload
adb sideload Kernel.zip (using the same Kernel)
wipe Dalvik, Cache, Data
Try to boot (=bootloop) / re-lock bootloader and try (=boot to bootloader only)

asb56 said:
By the way, here's what I've done (anything leap out as wrong?):
boot into TWRP
wipe Dalvik, Cache, Data, System
boot into bootloader
fastboot flash boot boot.img (using the boot.img from jmz's stock Odexed WWE ROM)
boot into TWRP, set up sideload
adb sideload ROM.zip (using the same ROM)
wipe dalvik, cache
boot into bootloader
fastboot flash boot boot.img (using the boot.img from jmz's Kernel)
boot into TWRP, set up sideload
adb sideload Kernel.zip (using the same Kernel)
wipe Dalvik, Cache, Data
Try to boot (=bootloop) / re-lock bootloader and try (=boot to bootloader only)
Click to expand...
Click to collapse
Boot into TWRP
Whipe cache, system, dalvik and data
Flash the odexed JMZ rom via sideload
Wipe dalvik and cache
Flash JMZ kernel
Boot into bootloader and flash kernel boot.img via fastboot
Boot into TWRP and install superSU binaries via sideload
Wipe dalvik and cache
Reboot system
Might have a few bootloops before you get booted correctly!
When you're booted into android you'll see a message telling you Androind is updating! When that's done you get into the setup phone process! Don't do anything here not even connecting to wifi maybe just selecting what carrier settings you want if that option appears. Because next you'll probably get an OTA notice and if you're connected to wifi you're screwed cuz you'll only have the option to download it and it will install it and it didn't work for me so I suggest you stay away from it as well.
After that without any reboot open the superSU app and make sure you see that it's installed correctly. When that's done you're successfully rooted and you can download revone from your phone and it will be downloaded to your downloads folder on your sdcard. You also need to connect to play store and download a file explorer that can handle root privileges like root explorer and also install terminal emulator from play store.
Open root explorer and move the revone file from downloads to /data/local/tmp
Open terminal emulator and type su
Grant the terminal root access when the superSU popup shows and ask you that
Type the command cd /data/local/tmp
Type the command chmod 775 revone (might be revone.bin just use the exact name here)
Type the command ./revone -P
You'll probably get the message "error code: 2" here but here it's time to make your phone reboot and I suggest you turn off your device and wait for a minute and then turn it on again. The phone should boot up but you might have a few loops but just wait for it to boot up properly. Once you're back into the OS start the terminal emulator and type the following commands
su
revone -s 0 -u (remember to use the exact name of revone here as well. If it's revone.bin you use that!)
Now you should get the message that revone was successful and you can reboot into bootloader and relock your bootloader and then reboot the system
It will boot up normally now and you can run the command revone -t to remove the tampered flag now
Hope this helps
HTC One Mini
S-OFF
---------- Post added at 09:59 PM ---------- Previous post was at 09:53 PM ----------
Just to clarify use the exact name of the revone file in every command that includes revone! Make sure you include the file extension if there is one!!
HTC One Mini
S-OFF

Mega thanks. Will try when I get a moment - trying to move house at the same time.
Do you suppose it's actually necessary to be S-OFF to fix this boot loop? I mean, I can re-lock and re-unlock without that no probs...

asb56 said:
Mega thanks. Will try when I get a moment - trying to move house at the same time.
Do you suppose it's actually necessary to be S-OFF to fix this boot loop? I mean, I can re-lock and re-unlock without that no probs...
Click to expand...
Click to collapse
You probably don't generally and you can try without the s-off part but when you're s-off you can do all the things you want even with the bootloader locked
Skickat från min C6903 med Tapatalk 4

Can't access recovery

A friend has given me his Desire S to fix what I originally thought was just a stuck power button that prevented it from starting up. But the button is now fixes and I've been trying the last few days to get it to start up.
What I have tried so far is to enter Recovery mode, but upon choosing it, the phone would just go to the HTC logo screen, fibrate once and then fibrate agian after a second or two for a few times and the screen would go blank. The same happens with normal bootup. It also seems that the phone is still running with the blank screen because I have to pull the battery to startup again.
I then tried to use the latest RUU (Android 4.0) from HTC but the phone is not recognized by the computer (I think it is because it didn't startup enough to be able to present itself to the computer). So I unlocked it and used fastboot (from Ubuntu as OS) to flash the recovery (recovery_signed.img) and boot (boot_signed.img) from the RUU. With this recovery and normal startup would remain at the HTC screen and wouldn't go blank as before - still fibrates a few times.
I also tried to rename the rom.zip to PG88IMG.zip and putting it on a SD and the bootloader does detect it, but presents the normal boot screen afterwards (I think it complains about it being incorrect - the display is too quick for me to see the error).
Now I also have a Desire S and made a backup of it before I installed a custom ROM. So I also tried the recovery.img that I have from this backup, but then recovery is stuck on the blank screen again.
Is there anything that I did wrong, missed or may not have tried yet? And how can I go about to fix it?
PHONE DETAILS (from bootloader screen)
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot

The PG88IMG wont work coz ur s-on. Ul need to extract the zip file and put the recovery.img in ur fastboot folder and then flash it from fastboot, volume down + power then select select fastboot then plug ur phone into pc and open a fastboot command window and type
fastboot flash recovery recovery.img
Also a ruu u run from fastboot and u need to relock ur bootloader.
(i dunno how all this is done using ubuntu but thats how on windows so im sure ul know or figure it out)

Ok, didn't know that I needed S-OFF for PG88IMG - thanks for pointing that out . I did flash the recovery (paragraph 3), it is just named `recovery_signed.img` and not 'recovery.img` - I assume that there isn't a difference between the two?
Do I open the RUU while in fastboot on the phone (after relocking) or do I run it from a fastboot command?
(On Ubuntu fastboot is installed as a program so I can call it after I CD to the extracted rom folder and I assume it is working since I didn't get any errors)

Pieter2627 said:
Ok, didn't know that I needed S-OFF for PG88IMG - thanks for pointing that out . I did flash the recovery (paragraph 3), it is just named `recovery_signed.img` and not 'recovery.img` - I assume that there isn't a difference between the two?
Click to expand...
Click to collapse
Well it depends, could be 4ext recovery, CWM, or TWRP. But as far as the name, could be called peterpan.img and it wouldnt matter haha
Pieter2627 said:
Do I open the RUU while in fastboot on the phone (after relocking) or do I run it from a fastboot command?
Click to expand...
Click to collapse
Yh boot ur phone into fastboot, connect it to pc, relock bootloader and then run ruu. The ruu should be exe file so just double click it to run.

Ok, relocked it and went into fastboot mode and then opened the RUU, but was not recognized. Then followed this (droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/) since I used Win 8.1 for the RUU and it flashed successfully.
But it is still stuck on the HTC screen - gave it 30 minutes for the first boot after flash. Recovery is also still stuck, so I reflashed and same issue.
Radio is now 3831.19.00.110