Database Info

ROM Manager having some trouble flashing ClockworkMod

So, basically ever since I've had my phone rooted and had ROM Manager on it, it has had trouble flashing Clockwork Recovery for me. I'll select for it to flash, it will appear to do so, but when I try to boot into recovery, either manually or from ROM Manager, it will just go to the default bootloader. When I attempt to choose Recovery from there, nothing will happen, and I'll have to reboot my phone and attempt to flash CWM again, and again, until it finally boots into it.
This always used to work after about 3 tries though, but now suddenly, it's just not even going anymore.
Is there anything I can do to make this process easier (or actually work)?

Set cwm to erase before flashing.
Sent from my Nexus S using xda premium

Or just use the fastboot command and flash recovery that way.

krohnjw said:
Set cwm to erase before flashing.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Just tried doing this, didn't work.
NYYFan325 said:
Or just use the fastboot command and flash recovery that way.
Click to expand...
Click to collapse
What command would that be? /noob

The command is called fastboot. You run it from a command prompt. You need to download the recovery image, then from the command prompt type:
fastboot flash recovery nameofrecoveryimage.img
There are multiple guides on here that explain it step by step

NYYFan325 said:
The command is called fastboot. You run it from a command prompt. You need to download the recovery image, then from the command prompt type:
fastboot flash recovery nameofrecoveryimage.img
There are multiple guides on here that explain it step by step
Click to expand...
Click to collapse
First off, sorry for taking so long to reply.
That was extremely noobish of me, I had completely forgotten about fastboot.
Turned out that solved it. I'm not sure what was going on, but all seems to be well now.
Thank you for your help!

use qbking77 guide in rooting ns/s 4g it is superb tutorial... go to youtube and type qbking77 ^_^

There was a file you have to delete. Look around Q&A, It's in there
Sent from my Nexus S 4G using XDA App

Ok so either delete these two files below or change the permissions so it has none (000)
"Install-recovery.sh" located in /system/etc
"Recovery-from-boot.sh" located in /system

[Solved]

SOLVED!!
Hey guys, i've seemed to set myself up for a soft brick upon me not reading everything clearly and correctly.
I was trying to take an easy route and simply misread a few numbers.
I really need help here, I unlocked my bootloader then proceeded to use a 1 click root solution from here; http://android.modaco.com/topic/327000-08-aug-grj22-colour-revert-superboot-rooting-the-nexus-s/
I just went back to stock after wanting to start clean when I got this phone, anyway I didn't see that this was intended for 2.3 where as my phone was running 2.3.4 and thats where I think I went wrong.
I can access bootloader, after trying this method the phone just boots and hangs at the unlock screen and nothing else. I don't have recovery so I can't get into that, I tried locking and unlocking the bootloader to see if that would help but no luck.
Where do I go from here?
**at&t model

If you can access the bootloader, you're fine. Just install ADB on your computer and flash a custom recovery image. From there, you can flash a ROM.

deejaylobo said:
If you can access the bootloader, you're fine. Just install ADB on your computer and flash a custom recovery image. From there, you can flash a ROM.
Click to expand...
Click to collapse
im trying to push a recovery img from cmd and it's telling me "error: cannot load clockworkXXXXXXXX

I think you may not have entered the full file path when pushing the recovery image.

deejaylobo said:
I think you may not have entered the full file path when pushing the recovery image.
Click to expand...
Click to collapse
I was trying to follow this recent guide here; http://forum.xda-developers.com/showpost.php?p=18257219&postcount=1
the very last part about unlocking the bootloader
and it just keeps giving me that error

Okay, been awhile since I did the whole unlocking bootloader/flashing recovery thing. If I remember correctly, in the command prompt, you should navigate to fastboot which is located in <whatever you named your Android SDK folder>/platform-tools folder. Also, place your recovery image in the same folder. Then enter the command from the tutorial. "fastboot flash recovery <image recovery file name>"

sent you a PM

a huge thanks to deejaylobo for helping me out, a folder wasnt renamed so I had a hard time pushing recovery but he got me back on my feet!
thanks again!!

[Guide] How to root, install EXT4 recovery and custom ROM on HBOOT 2.00.0002

Hi, A short but effective guide for people who want to root their Desire S while keeping HBOOT 2.00.0002 and S-ON. This is what I did with my phone yesterday, but took me a lot of time to figure things out, so I'm writing this for myself and other people.
1) First of all set up ADB and Fastboot. [GUIDE] Easy and simple adb and fastboot setup for newbies (Windows only)
Also download the ROM you wish to install on your Desire S and put it on your microSD card. For this tutorial I choose Reaper v2.1 rom by lowveld.
2) You have to unlock your bootloader first via HTCdev so that you can install EXT4 recovery and custom roms. In the dropdown list select ''All other supported models'' and follow the instructions.
If you successfully finished the HTCdev unlock tutorial, your phone has a unlocked bootloader.
3) We're going to install EXT4 recovery. But first download ''4EXT_Recovery_v2.2.7_RC5.zip'' and extract the recovery.img file to the folder where you installed fastboot and adb. If you followed the tutorial in step 1 the folder will be ''C:\android-tools''
Now make sure Fast Boot is turned off on your phone. Go to ''Settings > Power > Fast Boot'' to turn it off. Unplug your phone from your computer, it's time to turn of your phone and boot into your bootloader.
Press Volume Down Button and Power Button at the same time to boot into recovery. Now connect your phone to your computer and select fastboot.
(Power button to select, Volume Down/Up to navigate)
Go to start->run-> type cmd and press enter. A command prompt will now appear.
Type:
cd c:\android-tools [press enter]
fastboot flash recovery recovery.img [press enter]
Click to expand...
Click to collapse
EXT4 recovery is now installed on your phone. Turn off your phone in bootloader menu.
4) Open the rom (.zip file) you downloaded in step 1 and put the ''boot.img'' file in ''C:\android-tools''
If you followed this tutorial correctly, you already copied your desired rom your onto your MicroSD card.
Now we boot into the bootloader again, this time we select recovery.
Go to: wipe | format>and select: wipe data/factory reset (this may take a while), then select wipe cache and wipe dalvik cache.
Go back to main menu in EXT4 recovery and select ''install from sdcard'' select ''Reaper_V2.1.ZIP''. After the rom is installed turn your phone off again.
Boot into recovery, connect your phone to your computer and select fastboot on your phone.
Go to start->run-> type cmd and press enter. A command prompt will now appear.
Type:
cd c:\android-tools [press enter]
fastboot flash boot boot.img [press enter]
Click to expand...
Click to collapse
After it's successfully installed, turn of your phone and just boot normally. It may take a while for your phone to boot up.
Your phone is unlocked,rooted and has a custom ROM.
Enjoy
Note: Some new ICS roms require different kind of HBOOT. I use Fallout v5.0.0 without any problems.
Just press the 'Thanks' button instead of saying thanks.
Changelog:
*03-03-2012 Updated guide
*14-03-2012 Updated guide
*12-09-2012 Added Notes/updated guide
Click to expand...
Click to collapse

Tx!
Was thinking about rooting/unlocking but wasnt really sure of myself doing it without bricking it. Most of this guide i already knew but it gives me confidence before making the jump
Sent from my HTC Desire S using xda premium

Why did you temp root at step 2? As soon as you restart your phone it'll be gone.

foX2delta said:
Why did you temp root at step 2? As soon as you restart your phone it'll be gone.
Click to expand...
Click to collapse
So it's not permanent? meaning step 2 is unnecessary?

@n0elite
Yeah, if your phone is locked (2. hboot) or s-on (0.98 hboot) if will just give you shell root, useful but not required for what you doing.

this looks promising, i think i'll try it someday
so i'll be root after i finished this procedure, or just temporary?

Finally. This was the missing link in this forum!
I had the intention do write one, but I am S-OFF and cannot verify the steps without going to Stock then doing the steps and then downgrade and S-OFF again. Too many things to do just in the name of a correct tutorial. Anyway thanks I am glad that somebody finally wrote it!
P. S. : please notify ben_pyett to include it in the Index thread
Sent from my Desire S using Tapatalk

foX2delta said:
@n0elite
Yeah, if your phone is locked (2. hboot) or s-on (0.98 hboot) if will just give you shell root, useful but not required for what you doing.
Click to expand...
Click to collapse
Wouldn't swapping step 2 and 3 fix that?
Sent from my HTC Desire S using xda premium

@dan-fish
Yip

Guide updated. Thanks for the comments

I've followed your Guide ... but i stuck on the bootscreen
i installed the ROM via recovery ... and then the phone restarted and started to boot, i just pulled out the battery to turn off the phone and then to flash "boot.img" via fastboot, but now i stuck on the bootscreen ... anybody knows what to do?

yxsunnyxy said:
I've followed your Guide ... but i stuck on the bootscreen
i installed the ROM via recovery ... and then the phone restarted and started to boot, i just pulled out the battery to turn off the phone and then to flash "boot.img" via fastboot, but now i stuck on the bootscreen ... anybody knows what to do?
Click to expand...
Click to collapse
Damn, where did you read to pull the battery? NEVER PULL BATTERY AT RUNNING OR BOOTING SYSTEM EXCEPT YOUR AWARE OF THE POSSIBILITY TO GET A PAPERWEIGHT AND DON'T MIND IT!!
Did really take a look at the recovery? What is written as last line?
Ok, but your phone is off now, if not reboot to bootloader with
adb reboot bootloader
at the command line.
Otherwise start it with vol down and power.
There use the fastboot command to flash the boot.img, if you're lucky it will work.
Swifted from my Desire S far away from my PC

Tectas said:
Damn, where did you read to pull the battery? NEVER PULL BATTERY AT RUNNING OR BOOTING SYSTEM EXCEPT YOUR AWARE OF THE POSSIBILITY TO GET A PAPERWEIGHT AND DON'T MIND IT!!
Did really take a look at the recovery? What is written as last line?
Ok, but your phone is off now, if not reboot to bootloader with
adb reboot bootloader
at the command line.
Otherwise start it with vol down and power.
There use the fastboot command to flash the boot.img, if you're lucky it will work.
Swifted from my Desire S far away from my PC
Click to expand...
Click to collapse
I tried it, but it will still stuck on the HTC Splash screen ...
When i'm flashing the ROM everything works and in the end it starts restarting ... and i have no chance to stop the restarting? Or i'm blind
Update: Found the solution ... noob mistake

yxsunnyxy said:
I tried it, but it will still stuck on the HTC Splash screen ...
When i'm flashing the ROM everything works and in the end it starts restarting ... and i have no chance to stop the restarting? Or i'm blind
Click to expand...
Click to collapse
What rom do you use? Maybe the recovery script forces a restart, sry, but anyways use vol down vol up and power or adb reboot bootloader to force a reboot.
If it's really needed only pull battery in between the small gap after shutdown and boot, but not at running system.
Try it the other way round, first flash the boot.img, afterwards flash the rom.
Swifted from my Desire S far away from my PC

Please help .
I am new to android and I did know a great stupidity, I removed the battery while charging the 4EXT Recovery image I thought was locked and now i do not know what to do, please teach me download it another rom as it related to furniture.

stroescu76 said:
I am new to android and I did know a great stupidity, I removed the battery while charging the 4EXT Recovery image I thought was locked and now i do not know what to do, please teach me download it another rom as it related to furniture.
Click to expand...
Click to collapse
So what is the problem? Phone doesn't boot or what?

Locked in HTC logo.
He remained in the HTC logo, and nothing happens, I would be very grateful if you help me, I think not uploaded image.: (

stroescu76 said:
He remained in the HTC logo, and nothing happens, I would be very grateful if you help me, I think not uploaded image.: (
Click to expand...
Click to collapse
What did you do before the phone wouldn't boot?

I followed your directions, I installed version Reaper_V2.1'''' I closed, I opened the phone and I gave in "Fastboot", give the command:
cd c: \ android-tools [press enter]
fastboot flash boot boot.img [press enter],
but it says "error: can not load boot.img", if I saw a video where I realize I'm wrong or my phone failed.

Put boot.img in c:\android-tools and then run the command again
Sent from my HTC Desire S using XDA

[Q] home to root

please dont shout, just take pitty on me.
I have been getting into the world of rooting and have used the HTC Bootloader unlock, and have installed clockwork. i then had a few issues but managed to get some roms working but Im still not fully understanding exactly what im doing.
but i can flash by:
1. Power on'ing and vol down,
2. fastboot - bootloader - loading PG58IMG
3. recovery -wipe data/factory reset - yes
4. install zip from sdcard - chose zip from sdcard - Sensation_3.32.401.5_deodexed - Yes
5. wait for: install from sdcard complete
7. go back - rebootsystem now
Ive tried a few roms, 2 didnt work but this is the 3rd (Sensation_3.32.401.5_deodexed) that has loaded up.
My issue is I dont get how to get my wireless to work. If someone could give simple instructions Id be more than helpfl as all guides i read are too full of jargon. . . . .im not afraid to hit your thanks buttons . . .
Thanks
Tim
PS
my cid is VADAP001
my MID is PG5813000

taffytim said:
please dont shout, just take pitty on me.
I have been getting intot he world of routing and have used the HTC Bootloader unlock, and have installed clockwork. i then had a few issues but managed to get some roms working but Im still not flly understanding exactly what im doing.
but i can flashing by
1. Power on'ing and vol down,
2. fastboot - bootloader - loading PG58IMG
3. recovery -wipe data/factory reset - yes
4. install zip from sdcard - chose zip from sdcard - Sensation_3.32.401.5_deodexed - Yes
5. wait for: install from sdcard complete
7. go back - rebootsystem now
Ive tried a few roms, 2 didnt work but this is the 3rd (Sensation_3.32.401.5_deodexed) that has loaded up.
My issue is I dont get how to get my wireless to work. If someone could give simple instructions Id be more than helpfl as all guides i read are too full of jargon. . . . .im not afraid to hit your thanks buttons . . .
Thanks
Tim
Click to expand...
Click to collapse
Hi,
Are you talking about wifi?
Have you got a router?

When you use HTC Dev to unlocj your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read rose partitions. But Terri is a catch, if you want to flash a custom recovery you have to use ABD fastoot commands to flash it. When you flash as ROM in a .zip file via Recovery, it only flashes the System partition. You then have to open the dot zip file and extract the boot.img and then use ADB fastboot commands to flash the boot.img to your boot partition. If you do not you will still have the boot.img of the ROM you was using before you flashed te New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just watt te name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of eat is called a Lenox kernel. This means that your bootloader boots the Lenox kernel and the hardware of the device. The Lenox kernel then boots the Android OS. The kernel is also te connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on te system partition you will have troubles like WiFi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for te ROM are you will more than likely have troubles.

Malybru, i do have a router but my wifi wont turn on so i cant connect to it.

T-Macgnolia said:
When you use HTC Dev to unlocj your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read rose partitions. But Terri is a catch, if you want to flash a custom recovery you have to use ABD fastoot commands to flash it. When you flash as ROM in a .zip file via Recovery, it only flashes the System partition. You then have to open the dot zip file and extract the boot.img and then use ADB fastboot commands to flash the boot.img to your boot partition. If you do not you will still have the boot.img of the ROM you was using before you flashed te New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just watt te name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of eat is called a Lenox kernel. This means that your bootloader boots the Lenox kernel and the hardware of the device. The Lenox kernel then boots the Android OS. The kernel is also te connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on te system partition you will have troubles like WiFi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for te ROM are you will more than likely have troubles.
Click to expand...
Click to collapse
That is very informative thanks T-Macgnolia. I understand the theorybut i cant work out the process?
How do i get to flash the boot image?
If i go into my rom folder on my pc then try to open the boot file i just get a Windows Disc Image Burner message box asking me to burn to disc.
I used to burn images using virtal drives when making dvds. Will i need to do the same again here with a virtual drive?
Can you break the process down for me?

taffytim said:
That is very informative thanks T-Macgnolia. I understand the theorybut i cant work out the process?
How do i get to flash the boot image?
If i go into my rom folder on my pc then try to open the boot file i just get a Windows Disc Image Burner message box asking me to burn to disc.
I used to burn images using virtal drives when making dvds. Will i need to do the same again here with a virtual drive?
Can you break the process down for me?
Click to expand...
Click to collapse
First you have to download and install the Android SDK. Here is a video by Elite Recognized Developer Adam Outler that shows you how to install the Android SDK. After you have the SDK installed and all the packages are downloaded and installed. Take the boot.img and copy it to the same folder in ADB that has fastboot in it. Now while you are in the folder with fastboot in it hold down the shift key and right click anywhere on the screen and select "open command promt here". This will open a command promt with you already on the right directory. Now boot your Sensation into Hboot by holding the volume down button down while booting your Sensation. when in Hboot select fastboot and connect your Sensation to your computer with your USB cable. Now type the following into the command promt.
Code:
fastboot flash boot boot.img
That is all it is to it. Also the boot.img is a iso file that is why you get that message when you try to open it. You have to use a Android kitchen or another program that can decompile the file if you want to open it and look around.

T-Macgnolia said:
First you have to download and install the Android SDK. Here is a video by Elite Recognized Developer Adam Outler that shows you how to install the Android SDK. After you have the SDK installed and all the packages are downloaded and installed. Take the boot.img and copy it to the same folder in ADB that has fastboot in it. Now while you are in the folder with fastboot in it hold down the shift key and right click anywhere on the screen and select "open command promt here". This will open a command promt with you already on the right directory. Now boot your Sensation into Hboot by holding the volume down button down while booting your Sensation. when in Hboot select fastboot and connect your Sensation to your computer with your USB cable. Now type the following into the command promt.
Code:
fastboot flash boot boot.img
That is all it is to it. Also the boot.img is a iso file that is why you get that message when you try to open it. You have to use a Android kitchen or another program that can decompile the file if you want to open it and look around.
Click to expand...
Click to collapse
You sir deserve a big pint of something great. Point by point I:
1. I already had sdk installed so didnt need to install this.
2. I cleared the phone back to factory with Recovery (Power on with holding -Vol, RECOVERY, Wipe data/Factory Reset, Power Off)
3. I went into HBOOT (by powering on holding down -vol)
4. Opened FASTBOOT and connected phone to computer via USB
5. Opened up command prompt on PC (start menu, typed cmd in the search box)
6. I then Typed the following:
7. "cd c:\Android" (to get me into the folder where my files are)
8. "fastboot flash boot boot.img"
9. this then loaded my boot file and bosh, Im done.
I then restarted the phone and bobs your mothers brother Im using wiresless again. Its such an easy process but on the first go it seems like rocket science.
You cant appreciate how greatful i am for your help. Thank you more than a lot.
If i chose a different ROM at what point is it best to do this stage? Are you able to do this to the boot image before you use recovery to 'insatll zip from sd card'? Or do you have to install then come back to it like i did?

For every custom rom you install you need to follow the same procedure.
1. First flash/install the rom via recovery
2. Get the boot.img and flash it via fastboot (some rom's have more than one kernel then choose the best you want)
As long as you stay in HTC unlocked bootloader the above steps are necessary to flash the rom completely to prevent bootloops and wifi errors
sent from my blazing fast pyramid through sonic waves

ta gane shp, this is a good place with good people

Thanks this post helped me a lot!
I got Android Revolution fully working, but I'm trying to flash the newest OC Kernel of SebastianFM over it. But his zip doesn't have a "boot.img", it does however contain the following: mkbootimg, mkbootimg.sh and unpackbootimg. Is it any of those I need to flash, if not, which "boot.img" do I flash then?

Asskicker2 said:
Thanks this post helped me a lot!
I got Android Revolution fully working, but I'm trying to flash the newest OC Kernel of SebastianFM over it. But his zip doesn't have a "boot.img", it does however contain the following: mkbootimg, mkbootimg.sh and unpackbootimg. Is it any of those I need to flash, if not, which "boot.img" do I flash then?
Click to expand...
Click to collapse
Hi,
I believe the boot.img refers to the ROM you are flashing.
This is a kernel.
So,make a nandroid backup,
wipe cache and dalvik,
and flash the kernel from the root of the sd card,choosing install zip from sd card in recovery.

malybru said:
Hi,
I believe the boot.img refers to the ROM you are flashing.
This is a kernel.
So,make a nandroid backup,
wipe cache and dalvik,
and flash the kernel from the root of the sd card,choosing install zip from sd card in recovery.
Click to expand...
Click to collapse
Yeah, that isn't working.
Wifi ain't working now.

Asskicker2 said:
Yeah, that isn't working.
Wifi ain't working now.
Click to expand...
Click to collapse
Hi,
Just restore the nandroid backup you made.

malybru said:
Hi,
Just restore the nandroid backup you made.
Click to expand...
Click to collapse
Yeah, but I wanted to update to newest kernel. Thanks though

Doesn't work with me.
taffytim said:
You sir deserve a big pint of something great. Point by point I:
1. I already had sdk installed so didnt need to install this.
2. I cleared the phone back to factory with Recovery (Power on with holding -Vol, RECOVERY, Wipe data/Factory Reset, Power Off)
3. I went into HBOOT (by powering on holding down -vol)
4. Opened FASTBOOT and connected phone to computer via USB
5. Opened up command prompt on PC (start menu, typed cmd in the search box)
6. I then Typed the following:
7. "cd c:\Android" (to get me into the folder where my files are)
8. "fastboot flash boot boot.img"
9. this then loaded my boot file and bosh, Im done.
I then restarted the phone and bobs your mothers brother Im using wiresless again. Its such an easy process but on the first go it seems like rocket science.
You cant appreciate how greatful i am for your help. Thank you more than a lot.
If i chose a different ROM at what point is it best to do this stage? Are you able to do this to the boot image before you use recovery to 'insatll zip from sd card'? Or do you have to install then come back to it like i did?
Click to expand...
Click to collapse
I tried this with OrDroid and ViperS laterst versions and the wifi still doesnot work with my device.
It does nor even turn on from the settings, someone please help!

Wi-Fi Issues
theumairahmad said:
I tried this with OrDroid and ViperS laterst versions and the wifi still doesnot work with my device.
It does nor even turn on from the settings, someone please help!
Click to expand...
Click to collapse
Post 3 in this thread explains exactly where the problem is. But ........you will never unlock that boot partition if ur phone is S-ON. The trick with the wire works...it took me couple of times to do it but it worked. Then.....the lates ViperS version does it for you. You do not have to use ADB or whatever that program was to flash the boot.img It is all in the ROM. I even flashed the newest bricked 1.4 kernel on top.....but that 3rd comment is the key to all problems with Wi-Fi and other kernel issues:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:

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.