Database Info

Using fastboot without ENG or S-OFF

As many of you may know, you are locked out of using fastboot commands unless you have an engineering SPL. But I made a little discovery last night about how the HTC Rom Update Utility actually installs ROMs. Turns out it uses... fastboot!
Here's how it works:
With phone powered on, do "adb reboot bootloader" to enter fastboot.
-OR- With phone powered down, power on phone while holding VOL DOWN. From there press VOL UP to enter fastboot.
Run the command "fastboot oem rebootRUU"
Now you should see a black screen with a silver HTC logo. Look familiar? This is the screen you'll see when using the RUU.
From here you can re-flash an original HTC ZIP, with "fastboot flash zip filename.zip", where filename is the name of your signed HTC image.
As an added bonus, if your phone is S-OFF (even if you're not using the ENG SPL), you can flash ANY fastboot-compatible ZIP from here, signed or not.
When you're done, "fastboot reboot" will boot the device.
Found this by accident trying to help someone on IRC who had screwed up both their ROM and recovery somehow. All they could get into was fastboot/hboot, and they were S-ON.

Thankyou!
Just wanted to say I'm the guy that messed up his phone and needed Jason's help. He got me into a Sense ROM and was able to then get clockwork running again and restore my Nand. Really save my bacon.
Also, I've followed your advice. I now have a rooted AND S-off hero running Gingerbread.
Thanks again!

jasonmaloney said:
As many of you may know, you are locked out of using fastboot commands unless you have an engineering SPL. But I made a little discovery last night about how the HTC Rom Update Utility actually installs ROMs. Turns out it uses... fastboot!
Here's how it works:
With phone powered on, do "adb reboot bootloader" to enter fastboot.
-OR- With phone powered down, power on phone while holding VOL DOWN. From there press VOL UP to enter fastboot.
Run the command "fastboot oem rebootRUU"
Now you should see a black screen with a silver HTC logo. Look familiar? This is the screen you'll see when using the RUU.
From here you can re-flash an original HTC ZIP, with "fastboot flash zip filename.zip", where filename is the name of your signed HTC image.
As an added bonus, if your phone is S-OFF (even if you're not using the ENG SPL), you can flash ANY fastboot-compatible ZIP from here, signed or not.
When you're done, "fastboot reboot" will boot the device.
Found this by accident trying to help someone on IRC who had screwed up both their ROM and recovery somehow. All they could get into was fastboot/hboot, and they were S-ON.
Click to expand...
Click to collapse
Really? Thanks for the Info... Helpful, and Good to Know!!
Sent from my Hero using XDA App

wow, this is valuable information. couldnt this be put into the wiki or something? i tend to go to the wiki often, but i dont know how to properly edit a wiki.

jasonmaloney said:
As many of you may know, you are locked out of using fastboot commands unless you have an engineering SPL. But I made a little discovery last night about how the HTC Rom Update Utility actually installs ROMs. Turns out it uses... fastboot!
Here's how it works:
With phone powered on, do "adb reboot bootloader" to enter fastboot.
-OR- With phone powered down, power on phone while holding VOL DOWN. From there press VOL UP to enter fastboot.
Run the command "fastboot oem rebootRUU"
Now you should see a black screen with a silver HTC logo. Look familiar? This is the screen you'll see when using the RUU.
From here you can re-flash an original HTC ZIP, with "fastboot flash zip filename.zip", where filename is the name of your signed HTC image.
As an added bonus, if your phone is S-OFF (even if you're not using the ENG SPL), you can flash ANY fastboot-compatible ZIP from here, signed or not.
When you're done, "fastboot reboot" will boot the device.
Found this by accident trying to help someone on IRC who had screwed up both their ROM and recovery somehow. All they could get into was fastboot/hboot, and they were S-ON.
Click to expand...
Click to collapse
I have a similar problem with my CDMA hero. I tried the "Run the command "fastboot oem rebootRUU" and I get
<bootloader> [ERR] command error !!!
What am I doing wrong ? Probably everything.
Thanks.

Houndog101 said:
I have a similar problem with my CDMA hero. I tried the "Run the command "fastboot oem rebootRUU" and I get
<bootloader> [ERR] command error !!!
What am I doing wrong ? Probably everything.
Thanks.
Click to expand...
Click to collapse
Which bootloader version do you have, and where did you get the fastboot binary?

jasonmaloney said:
Which bootloader version do you have, and where did you get the fastboot binary?
Click to expand...
Click to collapse
HBOOT-1.47.0000 (HERO20000) is this what you mean ?
I got the fastboot off this site with SDK tools Android SDK updater ,revision 10. Is this what you need ?
Thanks for helping me..

hey Jason here's some background on his problem, I linked him this thread, hopefully you have more patience than me, but you know me, I don't really and I'm a dink http://forum.xda-developers.com/showthread.php?t=984688

Houndog101 said:
HBOOT-1.47.0000 (HERO20000) is this what you mean ?
I got the fastboot off this site with SDK tools Android SDK updater ,revision 10. Is this what you need ?
Thanks for helping me..
Click to expand...
Click to collapse
Not sure why it would be giving you issue. Make sure you're in fastboot mode and not hboot mode. You should see "Fastboot USB" on the screen if memory serves.
Alternatively, try the copy of fastboot.exe on my site. I pulled this directly from HTC's Rom Update Utility, so it might work better.

jasonmaloney said:
Not sure why it would be giving you issue. Make sure you're in fastboot mode and not hboot mode. You should see "Fastboot USB" on the screen if memory serves.
Alternatively, try the copy of fastboot.exe on my site. I pulled this directly from HTC's Rom Update Utility, so it might work better.
Click to expand...
Click to collapse
Jason, Thanks a million times, That was a problem, I d/l your fast.boot and it got me to the Black with silver htc screen. I'll see what I can do from here. Just want to get it to where I can boot into recovery.. Thanks again for helping me.

I've followed all the instructions but with a slightly different problem. I can't get to bootloader at all, but if I plug my hero to my pc and turn it on then it will say "fastboot usb" in a red rectangle at the top left, but is still otherwise the white HTC screen. when I do "fastboot oem rebootRUU" the terminal says okay, but the phone reboots into the same state instead of the black and silver screen I am hoping to see. Is it a brick or is there another option?

I get to where I want to load the image and it says "error: cannot load 'HERCIMG.zip'". Is this because it is not signed. I have the zip on the root of my sd card. I'm trying to install just a stock ROM and unroot so I can sell my phone.

beand1p said:
I get to where I want to load the image and it says "error: cannot load 'HERCIMG.zip'". Is this because it is not signed. I have the zip on the root of my sd card. I'm trying to install just a stock ROM and unroot so I can sell my phone.
Click to expand...
Click to collapse
If you look in the hero dev section you can find a thread called ruu in zip format. It will take you back to stock all the way no recovery no nothing just like fresh out the box. I've used it myself when I couldn't flash sense roms. And it works great. I would link you but I'm mobile. You might have to dig a little but its worth it. Good luck.
Yea It's Me Again With the
Modified Hero

laie1472 said:
If you look in the hero dev section you can find a thread called ruu in zip format. It will take you back to stock all the way no recovery no nothing just like fresh out the box. I've used it myself when I couldn't flash sense roms. And it works great. I would link you but I'm mobile. You might have to dig a little but its worth it. Good luck.
Click to expand...
Click to collapse
I get the same error even with that zip. I am S-OFF also. I have HBOOT-1.47 with radio 2.42.01.04.27.
I've tried almost everything to unroot and get back to stock. I am about ready to throw in the towel.

Why not just leave it rooted and put a stock rooted rom? Seems at that point you could remove superuser permissions somehow if It's that important for them to not have root. That would essentially take away root for all intensive purposes I would think. I'm just thinking out loud here and definitely you may want another opinion, but having root on the phone won't really cause them any real problems as long as they have a stock rom. They can still activate it, it still has the same menu options for a hard reset...maybe I'm missing the point other than you should be able to do what you're trying?
[dpeeps74]

dpeeps74 said:
Why not just leave it rooted and put a stock rooted rom? Seems at that point you could remove superuser permissions somehow if It's that important for them to not have root. That would essentially take away root for all intensive purposes I would think. I'm just thinking out loud here and definitely you may want another opinion, but having root on the phone won't really cause them any real problems as long as they have a stock rom. They can still activate it, it still has the same menu options for a hard reset...maybe I'm missing the point other than you should be able to do what you're trying?
[dpeeps74]
Click to expand...
Click to collapse
All the stock RUU's I have tried always give me the RUU Error [140]: BOOTLOADER VERSION ERROR
EDIT
I was able to RUU after using this method: http://forum.xda-developers.com/showthread.php?t=843544

I'm currently hitting a roadblock with this. Whenever i try the fastboot update zip command, and add the filename, i get an error saying that it cannot load said filename. i have no clue what i'm doing wrong.

zbach said:
I'm currently hitting a roadblock with this. Whenever i try the fastboot update zip command, and add the filename, i get an error saying that it cannot load said filename. i have no clue what i'm doing wrong.
Click to expand...
Click to collapse
The zip file should be on your computer, not your phone. Make sure to specify an absolute path for the zip file if the fastboot.exe file is not in the same folder as the zip file.

jasonmaloney said:
The zip file should be on your computer, not your phone. Make sure to specify an absolute path for the zip file if the fastboot.exe file is not in the same folder as the zip file.
Click to expand...
Click to collapse
I have the zip file in the android file along with the fastboot.exe program. I still get a "Cannot load" error message

thank you x100000.
I couldnt flash the original ruu because of the weird bootloader issue, but this worked like a charm and i was able to flash with a .zip of the ruu.
Thanks again.

[Q] Can't access root and Google apps

I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.

SounderBruce said:
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
Click to expand...
Click to collapse
Ok! first download : http://www.4shared.com/zip/XG506hyV/icsroot-fastboot-recovey.html
just unpack, connect your device and click run.bat.....Good luck!

I ran the .bat, but I get an error saying "Device already rooted", but it is still not recognized as rooted by SuperUser.
Alternatively, is it possible to completely wipe the phone of everything (including root) so I can start over with a fresh phone?

Of course you can, and might be the best idea if you don't mind doing it.
Make sure you have the latest CWM recovery on your phone, download the FULL ROM from this thread (i'm not american so i don't know exactly, but from what i know yours is the I9020T, so get that ROM) and copy it to the SDCard. Now go into recovery, wipe system/data and dalvik cache, then flash the ROM.
Do make sure you have the right ROM though. This will get you 100% fresh and untouched 4.0.3. You can probably clear out any non-personal folders on the sdcard too, but that shouldn't do any harm anyway.
After this, use the attached file from this thread to root, and feel free to update root/superuser.

Actually, that's what I did...I can't use CWM recovery because its displaying an error of no root. So how do I wipe this or fix CWM?

Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.

Harbb said:
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Click to expand...
Click to collapse
My bootloader is apparently unlocked and I'm trying to flash through fastboot.

Are you sure the following is satisfied:
-open padlock and google logo on boot
-fastboot (on phone) says "bootloader status: unlocked" or something of the like
-you are using: "fastboot flash recovery "C:\path\to\recovery.img""
-you are using the above command while connected to the PC via USB (with working drivers) and that you are in fastboot mode on the phone (turn off phone --> hold Vol. Up then hold Power TOGETHER for about 2 seconds, should give you reboot and recovery options)
It is necessary to be in the bootloader/fastboot interface on the phone when you run the command. Hopefully it was something simple that i said above, otherwise i'm completely lost.

1. Yes
2. Yes
3. I didn't use that method to root...
4. I'll try that.

3 is just flashing recovery, that is the code u type into cmd/terminal to reflash the recovery img. It isn't rooting the phone. 4 is how to get into the mode on the phone to use the command.
Its a bit confusing at first but makes much more sense once you do it one or two times.

Where do I go to get the recovery image?

The latest ClockWorkMod Recovery can be found on this page. Just scroll down to Nexus S and download 5.0.2.0 crespo .img. Then just direct fastboot to the folder you have it saved in while using the "fastboot flash recovery C:\path\to\recovery.img" command.

Ok. I've tried this, but in command prompt, I get the following error:
C:\Users\Bruce>fastboot flash recovery C:\Users\Bruce\Downloads\recovery.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.

Check out this rooting guide, however only go up to step 5 (and do NOT type "fastboot oem unlock", do everything up until that point). This will setup fastboot for you, and setup drivers for your computer. Once this is done, do what you did above and it should work successfully.
Remember to cd (change directory) in cmd to where you unzipped that folder.

There isn't a link...

Sorry, stuffed that up. I fixed the link in my previous post pointing to NexusSHacks - How to Root Nexus S.

It's worked, but when I try to go to the recovery menu, the Google/unlocked padlock screen freezes or it displays an Android with its chest compartment open and a red triangular ! symbol.

I just had a really long reply and managed to lose it by closing the page..
That's the stock bootloader you see there, it probably didnt flash or you rebooted your phone. And make sure that you are flashing the latest CWM you downloaded before.

I flashed the latest CWM, but when I try to go to recovery, my phone freezes at the Google logo with the unlocked padlock.

Have you tried flashing it again, or maybe redownloading the file? And of course making sure it is the NEXUS S version which you are downloading.
Alternatively, try just "fastboot boot recovery.img", replacing recovery.img with the full name and path of cwm.
edit: btw, i'll be gone for an hour or two Bruce so i can answer any more questions/issues when i get back

[Q] Nexus s 4g locked up

Okay, first of all I know, I'm a total noob. I have followed these forums a long time and have successfully rooted a few phones. One of which was my nexus s 4g. I was trying to unroot the phone so I could get ics. This is when I ran into problems and right now I just want to be able to get my phone working again. Right now I am stuck on the Miui boot up screen and no matter how long I wait it stays on that screen. If I do a battery pull and hold down power and vol up I can get into the bootloader screen with the information as follows: fastboot mode, product name-Herring, HW Version Rev 34, Bootloader version-D720SPAKE1, Baseband version-D720SPAKE1, Carrier info, SPR, serial number-37308B81276A00EC, Lock State-locked. Then the different options I can choose are reboot bootloader, reboot, recovery, power off. If I choose reboot, it takes me back to the mius screen and stays there. If I choose recovery, I get the triangle with the exclamation point. I then hold power and up volume again and I get a screen that says Android system recovery <3e> with reboot system now, apply update from sd card wipe data/factory reset and wipe cache partition. I have tried all of these as well with no luck. When I go to apply update from sd card I get matrix-cfs_v15.5 zip, root.zip, update.zip and then what looks like apps such as Alarms/, Android/,MIUI?, etc. If I try to select any of the first ones such as matrix-cfs_v15.5 zip, I get Install /sdcard... , finding update package..., opening update package..., verifying update package..., E.signature verification failed, Installation aborted. Then it gives me the system recovery options again. Any help would be appreciated.

Did you try ADB fastboot method?

Not sure how to try that

I tried doing the adb, followed all directions and installed and when I go to the command prompt and type in anything, such as, adb reboot bootloader I get, adb is not recognized as an internal or external command, operable program or batch file.

ok I got that working now but when I type adb devices and press enter I get a message saying List of devices attached and then it doesn't show anything and I get the command prompt again saying:c:\android\android-sdk\platform-tools>

also since the phone is stuck in either the miui screen or bootloader I can't get into it to put it in usb debugging mode. I am trying on my own to get this going and am stuck any and all help would be very much appreciated.

TerryUK98 said:
Lock State-locked.
Click to expand...
Click to collapse
I think that means you have a locked bootloader.
And from what you're telling, I believe you have stock recovery.
Also, when you're in fastboot mode, I don't think adb commands apply. Use fastboot commands instead (i.e. fastboot devices).
Search for guides showing you how to install and use fastboot.

I did fastboot as well and the problem I think I am having is it's not recognizing my phone because usb debugging wasn't turned on before it locked up. How would I get it to recognize my phone or download an img to my phone if it is not being recognized. Sorry if this is a stupid question.

You don't need usb debugging in fastboot mode.
You either:
1. Don't have drivers installed.
2. Don't have fastboot installed correctly.
You really need to read a guide or two, through and thoroughly.
Bc it sounds like you have no clues.

Yeah dude. Take a step back and go over what you have installed and where you installed it.Yes, fastboot commands start with fastboot instead of adb. And you're on stock recovery.

Thanks for the answer that I don't need usb debugging in fastboot mode, I wasn't sure of that. I have downloaded and installed my drivers multiple times and when I use the device manager to update drivers it says I have the latest drivers installed already. Whenever I do fastboot commands I will type in fastboot devices and shouldn't my device serial number come up? It just gives me the line c:\android\android-sdk\platform-tools>
And is waiting on me to type a command in. And yes I have been looking at guides all night. I appreciate any help you guys might have and remember we were all noobs at one time.

The zip in this tutorial should help.
It has adb, fastboot, and the drivers needed.
And unlock the bootloader because it is locked.

Finally got it, I had everything downloaded that I needed already, but looking at different forums, etc, it seemed like everyone named it something different. So I just used the one link you gave me and did it exactly the same way and it worked. Thanks so much! and again thanks for your patience.

Rooting- error: cannot load "flashboot flash recovery r1-modaco-reco... .img"

Rooting- error: cannot load "flashboot flash recovery r1-modaco-reco... .img"
I'm rooting my HTC One S the first time. And I was stupid and thought that HTC One X Clockworkmod flash would work.
Now I know how flashing and clockworkmod installing works but before that I accidentally flashed the One X command: "fastboot flash recovery recovery-clockwork-touch-5.8.2.7-endeavoru.img" and now when I go to recovery it gives me a red text and nothing works.
I searched everywhere for a guide to remove it and did not found. So I thought I could flash it over with an One S flash, but then when I entered the command: "fastboot flash recovery r1-modaco-recovery-clockwork-touch-ville.img" It gave me this: "error: cannot load 'recovery r1-modaco-recovery-clockwork-touch-ville.img'. My phone is connected perfectly, when I type 'fastboot devices' it shows me my phone is there.
So I think this is not a big problem for developers. Can anyone tell me what to flash or do to get rid of the One X recovery? Otherwise I just have to live with a phone with unlocked Bootloader and no access to root

Do you have the IMG I the directory from which you are running fast boot?

edscholl said:
Do you have the IMG I the directory from which you are running fast boot?
Click to expand...
Click to collapse
Ofcourse

rixrasta said:
Ofcourse
Click to expand...
Click to collapse
mabey I should just do a factory reset :/

Why don't you dl goo manager from market, open it and open menu and tap on Install OpenScriptRecovery and let it install twrp--although, I guess if you aren't rooted yet that won't work
Did you try fastbooting the cwmr from here--
http://www.clockworkmod.com/rommanager
Did you check the md5 on the modaco recovery before flashing
At the red text did you try hitting vol+ or vol- not sure which one takes you to stock recovery. What does red text say--
Did you hard reboot with holding down vol- and power at same time then release pwr after screen goes off and continue to hold vol-
Not sure what is wrong, just giving some ideas--

rugmankc said:
Why don't you dl goo manager from market, open it and open menu and tap on Install OpenScriptRecovery and let it install twrp--although, I guess if you aren't rooted yet that won't work
Did you try fastbooting the cwmr from here--
Did you check the md5 on the modaco recovery before flashing
At the red text did you try hitting vol+ or vol- not sure which one takes you to stock recovery. What does red text say--
Did you hard reboot with holding down vol- and power at same time then release pwr after screen goes off and continue to hold vol-
Not sure what is wrong, just giving some ideas--
Click to expand...
Click to collapse
Tyvm for your reply,
the cwmr for HTC One S does not exist any more on the page you gave me. There's only a blank page if you click on it
yes I did hard reboot and the red text says: This build is for development purposes only do not distribute outside HTC without HTC's written permission. Failure to comply my lead to legal action.
I tried the superboot from this site: htt p://w ww.m odaco.co m/to pic/352493-how-to-root-your-htc-one-s-for-windows-mac-and-linux/
This just brought up the recovery message again...
Then I tried flashing these files:h ttp://ww w.m odaco.c om/topic/353006-interim-clockworkmod-touch-recovery-for-the-htc-one-s-stock-download/
no help.
Any other ideas I should try?
However the flashing went through this time and there were no error, but the recovery is still f**ked.

rixrasta said:
Tyvm for your reply,
the cwmr for HTC One S does not exist any more on the page you gave me. There's only a blank page if you click on it
yes I did hard reboot and the red text says: This build is for development purposes only do not distribute outside HTC without HTC's written permission. Failure to comply my lead to legal action.
I tried the superboot from this site: htt p://w ww.m odaco.co m/to pic/352493-how-to-root-your-htc-one-s-for-windows-mac-and-linux/
This just brought up the recovery message again...
Then I tried flashing these files:h ttp://ww w.m odaco.c om/topic/353006-interim-clockworkmod-touch-recovery-for-the-htc-one-s-stock-download/
no help.
Any other ideas I should try?
However the flashing went through this time and there were no error, but the recovery is still f**ked.
Click to expand...
Click to collapse
Try this twrp .img
http://teamw.in/project/twrp2/100
The red text will stay till you relock, I believe, or flash stock recovery--

twrp recovery is the way to go. Me too I couldn't install the clockwork one!

rugmankc said:
Try this twrp .img
h ttp://team w. in/projec t/twrp 2/100
The red text will stay till you relock, I believe, or flash stock recovery--
Click to expand...
Click to collapse
I flashed the "openrecovery-twrp-2.2.2.0-ville.img". Didnnt change anything :/

sorry to hear that, not sure what else to do, so you still have onex recovery?
even if you run an ruu, i think you still have to flash the stock recovery first. haven't read up on that much, as never needed to run one
Don't know if trying to flash the stock recovery will help. I have the original one at home, but not sure if that is what they still call stock recovery with new ota's having come out

If it cannot load it, you probably spelt the name wrong. rename the image file to recovery.img (make sure it isn't .img.img) and flash that. Make sure the file path is correct! (e.g fastboot flash recovery C:\Users\Me\Desktop\recovery.img)

usaff22 said:
If it cannot load it, you probably spelt the name wrong. rename the image file to recovery.img (make sure it isn't .img.img) and flash that. Make sure the file path is correct! (e.g fastboot flash recovery C:\Users\Me\Desktop\recovery.img)
Click to expand...
Click to collapse
no no, the flashing finished successfully. I entered "fastboot flash recovery openrecovery-twrp-2.2.2.0-ville.img" and then it flashed without problems, but in the phone it didn't change a thing. If I enter recovery then there's the android icon with a white background and under it is the red text.
But keep guessing, maybe I really am doing something stupid wrong
When I go to Fastboot USB mode with my phone then I open the command prompt and firstly type "cd c:\CWM" (the folder where my flashing files are). Then secondly I type "fastboot devices" (just to be shure). And thirdly depending on what I am flashing I type "fastboot flash recovery name.img". I have tried "fastboot flash recovery openrecovery-twrp-2.2.2.0-ville.img", "fastboot flash recovery r2-modaco-recovery-clockwork-touch-ville" and "fastboot flash recovery ville_recovery_signed". Every one of them finishes successfully but doesn't change anything in the phone. I already have recovery-clockwork-touch-5.8.2.4-ville.zip and CWM-SuperSU-v0.96.zip in my phones directory to install root when I get into the recovery. In the C:\CWM folder in my computer are these files:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
(these where exctracted from fastboot.zip)
openrecovery-twrp-2.2.2.0-ville.img
r2-modaco-recovery-clockwork-touch-ville.img
ville_recovery_signed.img

the text won't disappear with unlocked bootloader, so that's ok.
Try to boot into bootloader hit fastboot reboot bootloader and then choose recovery. It can take a while to boot into recovery.
Gesendet von meinem HTC One S mit Tapatalk 2

stunner2002 said:
the text won't disappear with unlocked bootloader, so that's ok.
Try to boot into bootloader hit fastboot reboot bootloader and then choose recovery. It can take a while to boot into recovery.
Gesendet von meinem HTC One S mit Tapatalk 2
Click to expand...
Click to collapse
fastboot ->reboot bootloader ->bootloader ->recovery. Absolutely no change, It took half a second to bring up the "HTC quietly brilliant" logo and about two seconds for the red text to appear under it. No buttons work after that and I just have to hold the power button down to shut it down.
And by bootloader is unlocked!

As stunner said above it can take a while to boot into recovery, how long have you waited?
Give it a few minutes... Also you could try flashing stock recovery, it is distributed in the all-in-one tool and also in paulobriens posts about superboot. Then run a RUU.
But my best to would be to try fastboot booting a custom recovery, "fastboot boot cwm.img".

If this is the thing where you go int recovery for a millisecond and then back to the 'red text' screen (you have to watch carefully to notice), you should try erasing your cache in fastboot mode.
fastboot erase cache
Click to expand...
Click to collapse
-Jobo

It's gotten a little confusing and some suggestions are being repeated. I wonder if the android icon you are describing is the stock recovery symbol. At that screen have you tried to press vol+ or maybe volume-. I forget which one takes you to stock recovery. May want to check on that.
Also, have you tried typing "fastboot boot recovery" to go straight to recovery, bypassing htc restrictions
Here is very early stock recovery--not sure if it is still considered "stock" with new versions out now--I did mention that earlier--
https://www.dropbox.com/sh/yhrq0tia8512rj9/go28kc1NeP/ville_recovery_signed.img
I did have issues fastbooting recovery before. You can as mentioned try fastboot erase cache before fastbooting recovery. And change the name of your recovery to just recovery.img before you fastboot.
I assume you have nandroid backup on phone and copies of it and sdcard backup on pc.
I think when I had issues with recovery sticking it was my N1 and I typed "fastboot erase system" first, then fastbooted recovery. Then wiped all and restored nandroid. I am not sure we can do that on the 1s with no s-off. Someone else may know.
Can you access sdcard where you could reformat it fat32 thru a windows formatter program. Of course copy all to pc first. Sometimes sdcard formats help things you wouldn't expect it to.
Some folks have reported formatting works better thru phone on the 1s, maybe because it is an internal card. I did it once and think I had to redo it thru phone. But, if it gets recovery working, no big deal.
All these are suggestions and as the devs say--at your own risk--
I thought you said you said in first post, phone works, just no root capabilty. If that is true it should be fixable--I hope.
---------- Post added at 05:06 PM ---------- Previous post was at 04:32 PM ----------
rixrasta said:
no no, the flashing finished successfully. I entered "fastboot flash recovery openrecovery-twrp-2.2.2.0-ville.img" and then it flashed without problems, but in the phone it didn't change a thing. If I enter recovery then there's the android icon with a white background and under it is the red text.
But keep guessing, maybe I really am doing something stupid wrong
When I go to Fastboot USB mode with my phone then I open the command prompt and firstly type "cd c:\CWM" (the folder where my flashing files are). Then secondly I type "fastboot devices" (just to be shure). And thirdly depending on what I am flashing I type "fastboot flash recovery name.img". I have tried "fastboot flash recovery openrecovery-twrp-2.2.2.0-ville.img", "fastboot flash recovery r2-modaco-recovery-clockwork-touch-ville" and "fastboot flash recovery ville_recovery_signed". Every one of them finishes successfully but doesn't change anything in the phone. I already have recovery-clockwork-touch-5.8.2.4-ville.zip and CWM-SuperSU-v0.96.zip in my phones directory to install root when I get into the recovery. In the C:\CWM folder in my computer are these files:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
(these where exctracted from fastboot.zip)
openrecovery-twrp-2.2.2.0-ville.img
r2-modaco-recovery-clockwork-touch-ville.img
ville_recovery_signed.img
Click to expand...
Click to collapse
you should also have adb.exe if you are using adb--

frdd said:
As stunner said above it can take a while to boot into recovery, how long have you waited?
Give it a few minutes... Also you could try flashing stock recovery, it is distributed in the all-in-one tool and also in paulobriens posts about superboot. Then run a RUU.
But my best to would be to try fastboot booting a custom recovery, "fastboot boot cwm.img".
Click to expand...
Click to collapse
Okay I waited for 10 minutes, nothing happens. I've even tried to hold down all the button combinations(with the three buttons) for a few minutes.
I've tried flashing everything and fastboot boot just takes me directly to the recovery with the red text. I flashed both the recoveries in the all-in-one tool.
As I know absolutely nothing about RUU(only what the letters stand for) then I'd rather not do that because I read from some threads that RUU has quite a high chance to mess up your phone. Or if you direct me to a tutorial that u insure me that is 100% good then I could give it a go : D

[
I think I have made ​​the same mistake of flash recovery, but I can not get into cwm recovery, I only appear for 1 second the recovery, then restarts and returns to the operating system. SD card, all changes are discarded when you restart the phone, which is also only if I try to install or remove some utility. Can not install any recovery, even if fastboot works well and looks real mind install the recovery but when I reboot, it returns to its previous behavior, with recovery not working. I tried to install the recovery in every way, from fastboot, from All in one with quickroot, but none of these operations has changed the state of the system.
Unfortunately you can not install a Stock RUU because the bootloader unlocked and the recovery is not the stock, and especially not when there is no tutorial to follow to bring this situation to the ONE S, to its original state
Hopefully someone will be able to find a solution to your and my problem.

One option you guys may need to entertain, if applicable, would be to exchange phones with Carrier. Worth a shot--
I have not heard of this exact issue, but most comments say if you can't boot to recovery you are bricked--
Has anyone tried "fastboot boot recovery" command in terminal window?

Boot Loop

A few days ago I tried getting my phone to s-off using the "[how to] manually achieve s-off,simunlock,supercid for Inspire 4g/DHD" guide on the Android forums. (Sorry, I can't post direct links.)
I got to the part where I was supposed to type in "fastboot flash boot boot.img" to the command line but I accidentally skipped that part and typed in "fastboot boot recovery recovery.img". I stopped everything and tried to start over but when I turned my phone back on I was stuck in a boot loop. Going to hboot and trying to choose Recovery or Factory Reset only results in more boot looping.
I've tried putting PD98IMG.zip on the SD card and booting it, but it only reads it and says "Parsing..." before doing nothing. Attempting to enter recovery mode after this makes it enter the boot loop again.
I've also tried using the HTC Sense and RUU from AT&T on my computer to fix the issue. My phone can connect to my PC after choosing fastboot from the hboot menu. The RUU can see the device and it starts recovering it, as my phone shows a black background with HTC on it. But the RUU stops after trying to update the signature saying "The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again." I am 99% positive I am using the correct RUU.
I've searched high and low on the internet for a similar situation, but everyone else seems to have their problems solved using either of these steps. Thanks for any help.

Without knowing what you did (since you haven't given us a step-by-step and can't post links), we don't know how to help.

Sorry about that. I'll try to explain what I did the best I can.
Before using the guide, I managed to root my phone and used it for a few days, so everything was fine then. I later decided to s-off it so I could flash a custom ROM to it. Using the guide I mentioned above, I created a mini-adb directory in my C: drive with the ace-tools.zip that I downloaded. Using the command line I copied my stock boot image, though to where I do not know. (I feel like a fool for doing all this without being sure of what I was doing exactly. I deserve what came to me.) Then, using the command line I made my SD card a gold card. After that I changed the "misc version" (?) to allow installation of the downgrade firmware, and then relocked the boot loader and booted back into fastboot. Then I flashed the downgrade software and unlocked it again. It's here that my phone was supposed to be unable to boot, and I was supposed to flash the boot image but skipped that step.
Now I'm unsure of what I have to do, and I only want to get my device working again.
I wish I could post the link to the exact topic, but since I can't I guess you'd have to search the topic name to see exactly what the directions were trying to get me to do.
Thanks again.

Can you boot the phone into fastboot and flash the boot.img from fastboot?

No, with the PD98IMG.zip file it simply says "Parsing..." and stops there. With any other boot image it doesn't acknowledge it at all. Even though the computer makes the sound that it's connected to the device when it's in fastboot, adb can't recognize that's it's there in the command line.

SammichMonster said:
No, with the PD98IMG.zip file it simply says "Parsing..." and stops there. With any other boot image it doesn't acknowledge it at all. Even though the computer makes the sound that it's connected to the device when it's in fastboot, adb can't recognize that's it's there in the command line.
Click to expand...
Click to collapse
Wait. What? Not PD98IMG.zip from hboot. Extract the boot.img and flash from fastboot, not adb.

Ah, thanks for the clarification. I'm supposed to extract the boot.img to the SD card and enter fastboot on my phone, correct? Because I've just done so and nothing happened. I have the options Bootloader, Reboot, Reboot Bootloader, and Power Down, and the Bootloader option only takes me back to the hboot screen.
Sorry if I've misunderstood you.

SammichMonster said:
Ah, thanks for the clarification. I'm supposed to extract the boot.img to the SD card and enter fastboot on my phone, correct? Because I've just done so and nothing happened. I have the options Bootloader, Reboot, Reboot Bootloader, and Power Down, and the Bootloader option only takes me back to the hboot screen.
Sorry if I've misunderstood you.
Click to expand...
Click to collapse
No, the boot.img needs to be on your computer. Your phone needs to be in fastboot mode. From the folder where the boot.img is saved,
Code:
fastboot flash boot boot.img

I can't use the command prompt to connect with the device because it can't see it. I always get an "error: device not found" instead.

Is your phone in fastboot mode?

Yes. It's odd: the RUU software identifies it and knows it's there, but can't actually fix the issue. The command prompt just doesn't notice it at all.

SammichMonster said:
Yes. It's odd: the RUU software identifies it and knows it's there, but can't actually fix the issue. The command prompt just doesn't notice it at all.
Click to expand...
Click to collapse
So you're booting into hboot, navigating to fastboot with the volume buttons, and selecting it with the power button? What does fastboot devices say?

I'm assuming by "fastboot devices" you mean what it says in the command prompt.
...Well what do you know, it recognized it. I was typing in "adb devices" instead of "fastboot devices". So it can recognize it after all.
I'm assuming I have to load the boot.img now?

Hey hey, wa-hey!
That was much easier than I thought it would be! A simple "fastboot flash boot boot.img" followed by a fastboot flash recovery recovery.img" using some image files I made before messing everything up did the trick. Thank god I did so.
Everything's back to normal; my phone escaped the boot loop. And last but not least, I don't have to buy a new phone.
Thanks so much for helping me out, even if it was clearing a few things up for me. I appreciate it.

SammichMonster said:
...Well what do you know, it recognized it. I was typing in "adb devices" instead of "fastboot devices". So it can recognize it after all.
Click to expand...
Click to collapse
That's what i figured you were doing, so that's why I clarified.
SammichMonster said:
Hey hey, wa-hey!
That was much easier than I thought it would be! A simple "fastboot flash boot boot.img" followed by a fastboot flash recovery recovery.img" using some image files I made before messing everything up did the trick. Thank god I did so.
Everything's back to normal; my phone escaped the boot loop. And last but not least, I don't have to buy a new phone.
Thanks so much for helping me out, even if it was clearing a few things up for me. I appreciate it.
Click to expand...
Click to collapse
You're welcome. You could also have fastboot flashed any custom recovery image, flashed a ROM from recovery, and fastboot flashed that ROM's boot.img. So you weren't too badly off.