Related
Hi there.
As the above title says, what happen if I do so?
I do not have recovery version 2.5.1.3 in my ROM Manager anymore(I have no idea know why). Also do not have 3.0.2.5.
The only recovery I have is 2.5.1.4, 3.0.0.5, 3.0.0.6 and 3.0.2.4. Plus I am unable to flash 2.5.1.4 version(it pops up an error)
Some have no issues, but some have experienced issues when trying to restore cwm backups.
Have a look in the LeeDrOiD 2.2.3 thread a few days ago. I have posted methods to manually flash it via a tool or adb commands. I have also provided dl links as well.
Sent from my Desire HD using XDA App
Hi Upintheair
Thanks for the reply. Erm.. do you remember the exact date you post that in LeeDroid's thread? The thread is overloading. I cannot find them. =(
From Index of /cm/recoveries Download recovery-clockwork-2.5.1.3-ace.img
Try one of these 2 tools, instructions are on the threads;
1. Thread: [TOOL][All devices & OS] Fastboot Commander [v.1.1]
Download: Fastboot Commander v1.1
2. Thread: Android Flasher
Download: [UTILITY] Android Flasher(Recovery,splash1,Radio,HBOOT,bootanim)[V1.7.4]
OR
Manually through ADB:
1. Place the image in where fastboot.exe is located.
2. Connect phone to PC with Bootloader FASTBOOT USB
3. Using commands "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img", then "fastboot reboot", recovery
3. Using commands "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img", then "fastboot reboot", recovery
Click to expand...
Click to collapse
I tried many threads and find no answer to my question.
On my ubuntu I installed adb and can't remember about fastboot.exe whether it was installed by default or I downloaded it. And know I lost it - deleted accidentally.
1.My ques is where can I find it I mean fastboot? I reconfigured my adb back but there is no fastboot.
2. Can I use fastboot-linux from CWM 3.0.2.8 Installer instead?
It flashed cwm perfectly. But I am not shure about flashing radios and stuff.
Thanks for the links to the Leedroid cwm version
Sent from my DHD using XDA App
kgulruh said:
I tried many threads and find no answer to my question.
On my ubuntu I installed adb and can't remember about fastboot.exe whether it was installed by default or I downloaded it. And know I lost it - deleted accidentally.
1.My ques is where can I find it I mean fastboot? I reconfigured my adb back but there is no fastboot.
2. Can I use fastboot-linux from CWM 3.0.2.8 Installer instead?
It flashed cwm perfectly. But I am not shure about flashing radios and stuff.
Thanks for the links to the Leedroid cwm version
Sent from my DHD using XDA App
Click to expand...
Click to collapse
Warning: Flashing wrong radios or incorrectly can result in a BRICK !!! Your own risk..........
Edit: I would advise flashing through a battery only powered notebook, don't want a power surge or cut 1/2 way through a flash . Also ensure notebook & phone batteries have near full charge.
Fastboot Commander v1.1 is compatabe with Linux, there is instruction how to install the tool in the Dev's thread. It has everything you need in the zip, and no need for the adb / fastboot commands in CMD.
...............The first result Mr. Google gave me with the search string "download fastboot.exe" Choice of platforms; Windoes, Mac, Linux
Once extracted, just copy the files into your SDK folder where adb.exe is located (maybe tools or platform-tools........)
To make sure fastboot is working ok, boot phone into FASTBOOT, connect to PC & it will change to FASTBOOT USB. Open up CMD and navigate (cd\......) to the folder where adb & fastboot.exe is now located. Now type "fastboot devices", if connected & communicating correctly using Fastboot commands -> HTxxxxxxxxx, giving the device serial number.
If you want to use CMD:
Place image inside SDK folder where fastboot & adb.exe are located.
Rename it to radio.img (unless you like to type the whole name again)
CMD type: " fastboot flash radio radio.img", then
"fastboot reboot"
I am not too sure about Linux PCs, always been Windows until Android.
It is strange that CWM is not available to update TO 3.0.2.6 in ROM MANAGER...
this version is compatible with leedroid. you must to have installed ROM manager ver.4.1.0.0 from the android market..
SERGI.3210 said:
It is strange that CWM is not available to update TO 3.0.2.6 in ROM MANAGER...
this version is compatible with leedroid. you must to have installed ROM manager ver.4.1.0.0 from the android market..
Click to expand...
Click to collapse
You'll have to post that question to the ROM Manager Koush.
If you require a CWM Recovery version not listed in ROM Manager, flash through the methods I posted above. Links to Index of /cm/recoveries is there as well as xxxxxxx2.5.1.3-ace.img
OR
CMD: "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
Thanks UpInTheAir
I'll try it later tonight. Guess I will try to manually flash them.
It is exactly how we flash radio using the radio flash tool but this time change the "radio" to "recovery"?? this time im suppose to use back the same tool right?
I just recalled I read it somewhere last time when I was learning how to flash new radio. x)
superstick1 said:
It is exactly how we flash radio using the radio flash tool but this time change the "radio" to "recovery"?? this time im suppose to use back the same tool right?
Click to expand...
Click to collapse
If you are referring to the "tool" as in the CMD (Command Prompt)?
If this is what you mean, the answer is Yes & Yes.
Most of the tools, some examples & links I've given, just save you time, not having to use the adb or fastboot commands, cd\ (navigate) to the location of adb.exe or fastboot.exe in the SDK folder etc. These tools can also do a lot more, particularly Fastboot Commander which can be run on Windows or Linux.
I just try it and it says "error: cannot load 'recovery-clockwork-2.5.1.3-ace.img" =(
This is what I do
1) Firstly when i was at the cmd window.. I type "adb reboot bootloader"
2) Then "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
and it pops up that error. =/
superstick1 said:
I just try it and it says "error: cannot load 'recovery-clockwork-2.5.1.3-ace.img" =(
This is what I do
1) Firstly when i was at the cmd window.. I type "adb reboot bootloader"
2) Then "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
and it pops up that error. =/
Click to expand...
Click to collapse
Ensure Fastboot is OFF & USB debugging ON in phone settings
When in FASTBOOT, does it say FASTBOOT USB when phone is connected?
Did you test Fastboot communication by command "fastboot devices"?
Make sure the recovery image is copied to the SDK folder where fastboot.exe & adb.exe is located.
Make sure the name is exact. You could also rename it to recovery.img , and the change the command to "fastboot flash recovery recovery.img" (NO "quotes")
Edit: I see your signature is ENG S-off?, double check in HBOOT Bootloader. If the above still doesn't work, try the Fastboot Commander Tool, maybe your making a typo somewhere........
1. Ensure Fastboot is OFF & USB debugging ON in phone settings
Erm Im not sure about this, but I thought if we want to do anything such as flashing recovery we need to have Fastboot ON? Just to double confirm first before I do anything. ^^
2. When in FASTBOOT, does it say FASTBOOT USB when phone is connected?
How do I check this? =/
3. Did you test Fastboot communication by command "fastboot devices"?
Same as the above. How do I check this?
4. Make sure the recovery image is copied to the SDK folder where fastboot.exe & adb.exe is located.
Yes. Checked.
5. Make sure the name is exact. You could also rename it to recovery.img , and the change the command to "fastboot flash recovery recovery.img" (NO "quotes")
Tried. Did not work. Same error coming out.
I try flashing other recovery such as 3.0.2.6 but still the same error.
superstick1 said:
1. Ensure Fastboot is OFF & USB debugging ON in phone settings
Erm Im not sure about this, but I thought if we want to do anything such as flashing recovery we need to have Fastboot ON? Just to double confirm first before I do anything. ^^
2. When in FASTBOOT, does it say FASTBOOT USB when phone is connected?
How do I check this? =/
3. Did you test Fastboot communication by command "fastboot devices"?
Same as the above. How do I check this?
4. Make sure the recovery image is copied to the SDK folder where fastboot.exe & adb.exe is located.
Yes. Checked.
5. Make sure the name is exact. You could also rename it to recovery.img , and the change the command to "fastboot flash recovery recovery.img" (NO "quotes")
Tried. Did not work. Same error coming out.
I try flashing other recovery such as 3.0.2.6 but still the same error.
Click to expand...
Click to collapse
1. Mine works fine with usb debugging on & fastboot off.
2. Power off phone. HOLD volume down (don't release) & press power button once. Phone will boot into HBOOT, you will see FASTBOOT. Connect to pc with usb cable. Wait a few seconds and HBOOT will change to FASTBOOT USB.
3. Use Cmd (command prompt) in Windows. Pc to navigate to the sdk tools or platform tools folder (where fastboot.exe is located). Now type "fastboot devices", if you are communicating in fastboot, you will get HTxxxxxx (device serial number), and can now proceed with "fastboot flash recovery recovery.img"
If it doesn't work, you have not setup properly, or typo, I would suggest using fastboot commander tool.
Sent from my Desire HD using XDA App
I got my device number of HT0CCRX00128. Guess I've followed the steps you gave me correctly. Lol. But still the same results, error in flashing the recovery.
I will try that fastboot commander tool later tomorrow. It's getting late here and have to wake up early for work. Plus I havent read that thread properly yet. Lol.
Anyway thanks a lot ya.
UpInTheAir said:
You'll have to post that question to the ROM Manager Koush.
If you require a CWM Recovery version not listed in ROM Manager, flash through the methods I posted above. Links to Index of /cm/recoveries is there as well as xxxxxxx2.5.1.3-ace.img
OR
CMD: "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
Click to expand...
Click to collapse
i know, and I understand you, only I say that there are CWM's versions you very validate for flash apart from the recommended ones that work perfectly, I am flashing with the current one (leedroid, coredroid, hd rev ..) and it me works to the perfection and the nandroid also.
Certainly .... which is the meaning of "koush"???
superstick1 said:
I got my device number of HT0CCRX00128. Guess I've followed the steps you gave me correctly. Lol. But still the same results, error in flashing the recovery.
I will try that fastboot commander tool later tomorrow. It's getting late here and have to wake up early for work. Plus I havent read that thread properly yet. Lol.
Anyway thanks a lot ya.
Click to expand...
Click to collapse
Here are two zip files: Recovery 3.0.2.8 & 2.5.1.3.
3.0.2.8 doesn't show in ROM Manager, but version shows when boot into CWM Recovery, so no worries.
Reference Thread: [RELEASE][25/04/2011] ClockworkMod Recovery 3.0.2.8
I downloaded 3.0.2.8 from the above thread, extracted replaced the 3.0.2.8 image with 2.5.1.3 image (renamed recovery.img), and zipped again to upload.
View attachment Recovery_Ace_v2.5.1.3.zip
View attachment Recovery_Ace_v3.0.2.8.zip
Installation:
1. Power off your DHD
2. Put it in bootloader mode; Power+Vol down and select Fastboot from menu.
3. Plug-in the USB cable. (FASTBOOT USB)
4. Extract xxxx.zip
5. Double click on install-recovery-windows.bat if you're using windows, execute install-recovery-linux.sh if you're on linux or install-recovery-mac.sh if MacOSX.
6. Done! The device will be automatically rebooted.
7. If the version doesn't show in ROM Manager, reboot into recovery to check version actually installed.
I tested the windows commands and worked perfect Linux should too!!
I do recommend you read up a bit yourself on adb & fastboot commands, and if you aren't able to do that, use the flashing tools provided by the various Devs, thanks to them, life is much easier.
Thanks UpInTheAir!
I actually managed to get 2.5.1.3 installed and now I can continue flashing ROMs! Lol.
Erm why wouldnt recovery version show in the ROM Manager? My ROM Manager still shows it is 3.0.0.6 but in the recovery it shows as 2.5.1.3. Thats pretty weird isnt it?
Oops. I am trying to flash ARHD now, but halfway through it "stuck" in recovery and says: /tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. please open ROM Manager to report the issue.
What happen here? Its getting complex. =/
UpInTheAir said:
Warning: Flashing wrong radios or incorrectly can result in a BRICK !!! Your own risk..........
Click to expand...
Click to collapse
Thanks a lot man, used the one in cwm 3.0.2.8 update tool "fastboot-linux" and it works perfectly just need to rename it for consistency.
For me typing in linux is better then knowing nothing in windows
superstick1 said:
Thanks UpInTheAir!
I actually managed to get 2.5.1.3 installed and now I can continue flashing ROMs! Lol.
Erm why wouldnt recovery version show in the ROM Manager? My ROM Manager still shows it is 3.0.0.6 but in the recovery it shows as 2.5.1.3. Thats pretty weird isnt it?
Oops. I am trying to flash ARHD now, but halfway through it "stuck" in recovery and says: /tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. please open ROM Manager to report the issue.
What happen here? Its getting complex. =/
Click to expand...
Click to collapse
I always boot into CWM Recovery menu to flash, and not through ROM Manager (wherever possible).
Try that way.
hi...
can any1 tell me how to install custom roms using pc...........
i have searched the forum....but couldnt find any answer.................
sorry for starting a new thread........
thanks in advance
General Method:
- find, download and copy a flashable rom called "fullwipe 1.3" to the sd
- copy the zip with the rom you want to load in it to your sd card
- reboot into cwm recovery
- install zip from sd card
- choose the fullwipe 1.3 zip
- install
- then choose the rom's zip
- install
- reboot
wait for it to load. there you go.
For more advanced rom's, you must make directory's on your sd card for them to work properly. Follow instructions posted by the Rom's developer for proper installation.
thanks bro..........4 all ur help..............
1 more question........
what about using it through the fone......
i mean .....after downloading through the rom manager..........should i follow the same procedure ????
question
I rooted today, s-off & eng-off, installed rom manager
what do i have to do to get clockwork to work
I try booting into recovery but, display goes blank & has a red triangle symbol & after many minutes nothing happens..... can some inform me of the step I may have missed or something i can do to verify that i have the device set up properly.
Hopefully Thanks in advance.
gixer131 said:
question
I rooted today, s-off & eng-off, installed rom manager
what do i have to do to get clockwork to work
I try booting into recovery but, display goes blank & has a red triangle symbol & after many minutes nothing happens..... can some inform me of the step I may have missed or something i can do to verify that i have the device set up properly.
Hopefully Thanks in advance.
Click to expand...
Click to collapse
Flash CWM recovery from rom manager again.
Hawks556 said:
Flash CWM recovery from rom manager again.
Click to expand...
Click to collapse
I can appreciate that, but I need to know what to do. I try to do that & i get an error while attempting to run privileged commands. Flashing sounds all great but I cant seem to get it to do anything in recovery... error issues trying to do that, or anything else, I also have super user update issues that say they put a recovery image on the sd card & to go boot that from within recovery.
Just hoping to find out why i cant do the simple things everyone speaks of.
gixer131 said:
I can appreciate that, but I need to know what to do. I try to do that & i get an error while attempting to run privileged commands. Flashing sounds all great but I cant seem to get it to do anything in recovery... error issues trying to do that, or anything else, I also have super user update issues that say they put a recovery image on the sd card & to go boot that from within recovery.
Just hoping to find out why i cant do the simple things everyone speaks of.
Click to expand...
Click to collapse
Well if you can't flash recovery from Rom Manager then there's something wrong with your root privileges or s-offs... Just to make things clear, how did you try to flash the recovery?
AT THE TOP OF THE BOOTLOADER IT MUST SAY "... ENG S-OFF RL" FOR THIS TO WORK
With the device connected, boot into bootloader and select FASTBOOT and press power once.
It will now show FASTBOOT USB, and give you 4 options.
Download the newest 4.x.x.x version of the cwm recovery from the dev section.
Download My Toolkit and Extract to C:\
In the recovery zip that you downloaded from the dev thread, find the "recovery.img" and extract it to the RESOURCE folder of my toolkit. (make sure its only the recovery.img and not the folders it sits in)
open up a command prompt (windows key + R, type "cmd" and hit enter)
type in: cd "C:\HTC ACE TOOLKIT\RESOURCE" and hit enter.
the prompt should now be in that directory.
now type in the following EXACTLY and press enter afterwards:
fastboot flash recovery recovery.img
Let it flash, and badaboom, you have just flash cwm recovery.
JSLEnterprises said:
AT THE TOP OF THE BOOTLOADER IT MUST SAY "... ENG S-OFF RL" FOR THIS TO WORK
With the device connected, boot into bootloader and select FASTBOOT and press power once.
It will now show FASTBOOT USB, and give you 4 options.
Download the newest 4.x.x.x version of the cwm recovery from the dev section.
Download My Toolkit and Extract to C:\
In the recovery zip that you downloaded from the dev thread, find the "recovery.img" and extract it to the RESOURCE folder of my toolkit. (make sure its only the recovery.img and not the folders it sits in)
open up a command prompt (windows key + R, type "cmd" and hit enter)
type in: cd "C:\HTC ACE TOOLKIT\RESOURCE" and hit enter.
the prompt should now be in that directory.
now type in the following EXACTLY and press enter afterwards:
fastboot flash recovery recovery.img
Let it flash, and badaboom, you have just flash cwm recovery.
Click to expand...
Click to collapse
The BOOTLOADER SAYs "... ENG S-OFF but no RL @ the end
Can someone instruct me to what I may have done wrong? I know if I try to s-off or ENG-off I now get a connection problem but the first time I tried it seemed to work properly.
Thanks
Thanks for the help, I have successfuly flached clockwork now & a new rom.... What should I do to update a radio for my device on telus? Thanks
gixer131 said:
Thanks for the help, I have successfuly flached clockwork now & a new rom.... What should I do to update a radio for my device on telus? Thanks
Click to expand...
Click to collapse
well, in that toolkit i told you to download is a command script that does pretty much what I told you do to for the recovery.
Since you and I have the exact same phone I recommend grabbing the radio from the 2.52 korean build (Radio_12.59.60.26U_26.11.04.21_M), and the rill's as well.
Here is the radio and ril (first 2 links, download via the dropbox links): http://forum.xda-developers.com/showthread.php?t=996630
make sure you're in bootloader > fastboot and it says FASTBOOT USB on the screen
take a radio.img from within the zip and drop it into the resource folder and then run the shorcut in the toolkit.
It will now flash the radio to your phone and reboot.
Now with the rill's you flash via cwm recovery, from the RIL zip you downloaded, off your sd card in the same way you would flash a rom.
JSLEnterprises said:
well, in that toolkit i told you to download is a command script that does pretty much what I told you do to for the recovery.
Since you and I have the exact same phone I recommend grabbing the radio from the 2.52 korean build (Radio_12.59.60.26U_26.11.04.21_M), and the rill's as well.
Here is the radio and ril (first 2 links, download via the dropbox links): http://forum.xda-developers.com/showthread.php?t=996630
make sure you're in bootloader > fastboot and it says FASTBOOT USB on the screen
take a radio.img from within the zip and drop it into the resource folder and then run the shorcut in the toolkit.
It will now flash the radio to your phone and reboot.
Now with the rill's you flash via cwm recovery, from the RIL zip you downloaded, off your sd card in the same way you would flash a rom.
Click to expand...
Click to collapse
I would Like to thank you for your help & support, I was a the step of having fastboot usb And on my pc I unziped the radio And droped the image in the resource folder, a window pops up (disk burner) only option to choose is DVD R Drive.... do I have to have the SD card unmouted as a disk drive to the computer?
leave disk burner outta this. lol
The phone should be in bootloader under "fastboot" so the highlighted area will say FASTBOOT USB (since your phone is connected to your pc).
If radio.img is in the RESOURCE folder of my toolkit, go back to the main folder (HTC ACE TOOLKIT) and just double click the "Flash Radio" shorcut.
JSLEnterprises said:
leave disk burner outta this. lol
The phone should be in bootloader under "fastboot" so the highlighted area will say FASTBOOT USB (since your phone is connected to your pc).
If radio.img is in the RESOURCE folder of my toolkit, go back to the main folder (HTC ACE TOOLKIT) and just double click the "Flash Radio" shorcut.
Click to expand...
Click to collapse
Most excellent! Thanks & Thank you, your help has been most usefull & is quite appreciated!
Changed Rom
Changed rom last night & wanted to know weather I should flash the "rill's" & "radio" each time I change roms. I just did the radio now so hope that cures the tinny sound, also it sounded kinda tinny just playing music, is there a patch or something else to do or is all that fixed in the radio?
Any suggestion on roms to try? using Revolution HD right now.
I've been posting here and there around here lately but thought I'd get a cleaner, more focused thread going for those of us who used HTC's unlock tool and want root.
I managed to get the bootloader unlocked with HTC's tool and installed SU and clockwork onto my Inc2 but I think I'm having problems because I'm still S-On instead of S-Off.
So, what do we do next after unlocking the bootloader? I'm under the impression that because I'm S-On still, I can flash a custom ROM, but not only the ones with the stock kernel intact. This would be why Sabotage was able to install, but Mik wouldn't. Still only a theory, though.
ANY HELP PLEASE!!!
Kayak83 said:
I've been posting here and there around here lately but thought I'd get a cleaner, more focused thread going for those of us who used HTC's unlock tool and want root.
I managed to get the bootloader unlocked with HTC's tool and installed SU and clockwork onto my Inc2 but I think I'm having problems because I'm still S-On instead of S-Off.
So, what do we do next after unlocking the bootloader? I'm under the impression that because I'm S-On still, I can flash a custom ROM, but not only the ones with the stock kernel intact. This would be why Sabotage was able to install, but Mik wouldn't. Still only a theory, though.
ANY HELP PLEASE!!!
Click to expand...
Click to collapse
There are 2 options to flash a custom ROM that has a custom kernel on an unlocked bootloader.
1. Instead of booting to recovery mode directly, you need to boot in Fastboot mode and issue the command:
Fastboot boot [path to custom recovery.img]
This will boot you into recovery mode using the custom recovery image. Then you can flash a custom ROM with a custom kernel correctly.
2. Extract the boot.img from the custom ROM zip file and copy it to your SDK tool directory.
Then boot into recovery mode and flash the custom ROM. Next you must reboot into bootloader mode and enter Fastboot mode. Enter the following command:
Fastboot flash boot [path to the boot.img file].
Try either option 1 or option 2. You do not need to do both.
Hope this helps.
tpbklake said:
There are 2 options to flash a custom ROM that has a custom kernel on an unlocked bootloader.
1. Instead of booting to recovery mode directly, you need to boot in Fastboot mode and issue the command:
Fastboot boot [path to custom recovery.img]
This will boot you into recovery mode using the custom recovery image. Then you can flash a custom ROM with a custom kernel correctly.
2. Extract the boot.img from the custom ROM zip file and copy it to your SDK tool directory.
Then boot into recovery mode and flash the custom ROM. Next you must reboot into bootloader mode and enter Fastboot mode. Enter the following command:
Fastboot flash boot [path to the boot.img file].
Try either option 1 or option 2. You do not need to do both.
Hope this helps.
Click to expand...
Click to collapse
Tried option 1 and when I go to select install zip from sd card after booting to cwm the phone restarts. Trying option 2 now...
Option #2 won't work since I get stuck at the HTC screen when trying to load a custom ROM.
Kayak83 said:
Option #2 won't work since I get stuck at the HTC screen when trying to load a custom ROM.
Click to expand...
Click to collapse
How did you try to reboot into bootloader from recovery once the ROM was flashed. Once I get into recovery I connect the phone with a USB cable and then type
Adb reboot bootloader
This will boot you into HBOOT straight from recovery and should prevent the hang at the HTC.
Ok. Let's start fresh and complete:
1- Plug phone into computer.
2- select HTC sync on phone
3- open cmd and get to sdk
4- type "adb reboot bootloader"
5- phone should reboot to HTC's recovery thing
now what?
I have cwm installed already.
Kayak83 said:
Ok. Let's start fresh and complete:
1- Plug phone into computer.
2- select HTC sync on phone
3- open cmd and get to sdk
4- type "adb reboot bootloader"
5- phone should reboot to HTC's recovery thing
now what?
I have cwm installed already.
Click to expand...
Click to collapse
Just select Charge Only, not HTC Sync.
Once you type adb reboot bootloader you should get the HBOOT screen and it should show FASTBOOT USB.
At this point you should enter Fastboot commands from you PC command prompt.
So you said you tried fastboot boot [path to recovery.img file] and it did boot you into recovery, right? Then you should be able to flash the custom ROM and reboot normally when the install is complete.
For option 2 once you are in recovery mode flash the custom ROM and then when it is finished connect the phone with the USB cable and at the command prompt you should be able to type adb devices and it will respond with your device id.
If it does, then type adb reboot bootloader and it will take you back to the HBOOT screen. From there you would then enter the following Fastboot command:
Fastboot flash boot [path to boot.img file]
Then Fastboot reboot
tpbklake said:
Just select Charge Only, not HTC Sync.
Once you type adb reboot bootloader you should get the HBOOT screen and it should show FASTBOOT USB.
At this point you should enter Fastboot commands from you PC command prompt.
So you said you tried fastboot boot [path to recovery.img file] and it did boot you into recovery, right? Then you should be able to flash the custom ROM and reboot normally when the install is complete.
For option 2 once you are in recovery mode flash the custom ROM and then when it is finished connect the phone with the USB cable and at the command prompt you should be able to type adb devices and it will respond with your device id.
If it does, then type adb reboot bootloader and it will take you back to the HBOOT screen. From there you would then enter the following Fastboot command:
Fastboot flash boot [path to boot.img file]
The Fastboot reboot
Click to expand...
Click to collapse
I'm able to fastboot into cwm. But when I go to select install zip from sd card via the phone controls (volume up/down/power), the phone reboots.
Kayak83 said:
I'm able to fastboot into cwm. But when I go to select install zip from sd card via the phone controls (volume up/down/power), the phone reboots.
Click to expand...
Click to collapse
Which version of CWM are ou using. I use CWM 5.0.2 and it works fine.
SUCCESS. Thanks for your help!
Glad you got it goin!
Sent from my ADR6350 using xda premium
Kayak83 said:
SUCCESS. Thanks for your help!
Click to expand...
Click to collapse
Which option did you have success with?
dumb question but...
how do you find the path to your custom recovery?
mza929 said:
dumb question but...
how do you find the path to your custom recovery?
Click to expand...
Click to collapse
You determine what the path is when you download the recovery image to your PC. The best place to download or copy it to is the same folder you run adb.exe and fastboot.exe from.
tpbklake said:
You determine what the path is when you download the recovery image to your PC. The best place to download or copy it to is the same folder you run adb.exe and fastboot.exe from.
Click to expand...
Click to collapse
great thank you... i was thinking i had to use a path to the recovery on my phone's storage not my PC's...
Can someone link me to a cwm recovery that works. I'm having the reboot issue after selecting choose file from SD card.
Sent from my dinc2 using XDA App
mza929 said:
Can someone link me to a cwm recovery that works. I'm having the reboot issue after selecting choose file from SD card.
Sent from my dinc2 using XDA App
Click to expand...
Click to collapse
You should look for and use CWM 5.0.2
Kayak83 said:
I've been posting here and there around here lately but thought I'd get a cleaner, more focused thread going for those of us who used HTC's unlock tool and want root.
I managed to get the bootloader unlocked with HTC's tool and installed SU and clockwork onto my Inc2 but I think I'm having problems because I'm still S-On instead of S-Off.
So, what do we do next after unlocking the bootloader? I'm under the impression that because I'm S-On still, I can flash a custom ROM, but not only the ones with the stock kernel intact. This would be why Sabotage was able to install, but Mik wouldn't. Still only a theory, though.
ANY HELP PLEASE!!!
Click to expand...
Click to collapse
OK maybe I am missing something here. Do you actually have full root? If you do, how did you get it? I don't know how to get the su binary and busybox installed. I have unlocked my bootloader using the htc supertool and I don't have root, which is keeping me from installing CWM or anything root related for that matter. I have not seen any instructions on how to root this thing since the unlock tool became compatible 3 days ago. But maybe I have missed something.
Thanks for any help.
Still cant get rom to boot... however, i have been able to fastboot into custom recovery and complete the flashing process...
Now i am just stuck at the HTC screen after reboot.
Any suggestions?
Thank you all so far. You have been most helpful.
***** update ***** I finally got it after fast booting into recovery, flashing rom, and then extracting boot.img from that rom and flashing it via fastboot.
mza929 said:
Still cant get rom to boot... however, i have been able to fastboot into custom recovery and complete the flashing process...
Now i am just stuck at the HTC screen after reboot.
Any suggestions?
Thank you all so far. You have been most helpful.
***** update ***** I finally got it after fast booting into recovery, flashing rom, and then extracting boot.img from that rom and flashing it via fastboot.
Click to expand...
Click to collapse
Yes good job. The last part is the key to getting a custom ROM installed. Glad it worked for you.
---------- Post added at 09:13 AM ---------- Previous post was at 09:09 AM ----------
hackweed said:
OK maybe I am missing something here. Do you actually have full root? If you do, how did you get it? I don't know how to get the su binary and busybox installed. I have unlocked my bootloader using the htc supertool and I don't have root, which is keeping me from installing CWM or anything root related for that matter. I have not seen any instructions on how to root this thing since the unlock tool became compatible 3 days ago. But maybe I have missed something.
Thanks for any help.
Click to expand...
Click to collapse
After you have an unlocked HBOOT, you need to flash CWM recovery image in FASTBOOT mode. Once you have CWM installed, you can install the latest SU-3.0.xx.zip to root your current ROM and then you can installl and use root programs like ROM Manager, Busybox, Titianium Backup, etc. or you can install a rooted custom ROM.
I have the old TWRP installed via KFU and now want to update it.
Can I just install it straight over the old one and if so how do I do it ?
I understand that it's not as simple as using KFU to do it.
Any advice appreciated.
Use fastboot if you can. Assuming you have FFF installed and know how to use fastboot:
fastboot flash recovery /path/to/twrp.img
...or you could use one of smirkis' scripts.
http://forum.xda-developers.com/showthread.php?p=22608974
Is there an advantage to the new TWRP? I'm currently at 2.0 and trying to flash AOKP and hung at the opening animation and wondering if it has to do with an old TWRP .
I have FFF but as fire as I know that just takes me into twrp.
How do I get into fastboot. I've previously done this through KFU I think.
All I need is a step by step of how to do the install.
I get that I put the twrp 2.1.1 file on my pc and point the fire at it by running the fastboot command but I'm really not sure how to get into fastboot.
wigsey, I couldn't figure this out either. I had switched from TWRP 2 to CWM. Messed around with ADB and Kindle Fire Utility and I was only able to get back to TWRP 2; then I followed soupmagnet's advice. Installed Root Browser, downloaded and installed the scriptfiles. BEFORE running the scripts, however, I moved the latest version of TWRP into the Files folder of the scripts; renamed the twrp2-blaze.img version that was in there to "old" out of habit; copied over the new version of TWRP and renamed that to "twrp2-blaze.img" and then ran the script. Rebooted and had the 2.1.1 come up.
I am sure that there is an easier way, but for whatever reason using ADB just didn't work for me and this did.
So basically use the soupmagnet method but replace his twrp file with the new one renamed to the same name.
When you renamed the old one did you move it or leave it there. Wouldn't it be easier to delete it ?
Is the based place to get the new file from the TWRP website by the way ?
wigsey said:
So basically use the soupmagnet method but replace his twrp file with the new one renamed to the same name.
When you renamed the old one did you move it or leave it there. Wouldn't it be easier to delete it ?
Is the based place to get the new file from the TWRP website by the way ?
Click to expand...
Click to collapse
If you can, you want to get into fastboot and flash it from there. You don't have to copy it over to your KF first, fastboot knows where your recovery partition is located, it will do some basic checks to see that it will fit on the partition, etc.
Code:
fastboot flash recovery twrp.img
If at all possible, do it this way.
Alternatively, you can put the image on your /sdcard partition (this is what pops up when you mount the Kindle Fire's USB mass storage device on your computer) and write it directly to the recovery partition.
From the terminal emulator app...
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p5
This is essentially identical to the way smirkis' script will do the job.
It's a pain to type this on a virtual keyboard, so you can also use adb like this...
Code:
adb shell dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p5
In both cases above, you must have the mass storage device unmounted from your computer so your KF can access the file.
If you need fastboot or adb help, you can find it in the 3rd post of this thread...
http://forum.xda-developers.com/showthread.php?t=1552547
It should be noted that the "dd" command is nothing to be trifled with. It's been nicknamed "data destroyer" for a reason.
Pay CLOSE attention and verify what you have typed is correct before entering.
kinfauns, I tried the fastboot method, having renamed the 2.1.1 IMG file and it did not work for me. Seemed to go along, but when I rebooted into recovery, I still had 2.0.
The scripting method is a kludge, granted, but in my case it was idiot-proof.
---------- Post added at 03:00 PM ---------- Previous post was at 02:58 PM ----------
wigsey said:
So basically use the soupmagnet method but replace his twrp file with the new one renamed to the same name.
When you renamed the old one did you move it or leave it there. Wouldn't it be easier to delete it ?
Is the based place to get the new file from the TWRP website by the way ?
Click to expand...
Click to collapse
Actually I renamed the old one ".old" in case I needed it later. After success I deleted it. And yes, the TWRP website seems to be the best place to get the latest version.
koop1955 said:
kinfauns, I tried the fastboot method, having renamed the 2.1.1 IMG file and it did not work for me. Seemed to go along, but when I rebooted into recovery, I still had 2.0.
The scripting method is a kludge, granted, but in my case it was idiot-proof.
Click to expand...
Click to collapse
This sounds like you used the wrong fastboot command. The old install directions for 2.0 had you "fastboot boot" the image and now you need to "fastboot flash recovery" for version 2.1.0 and beyond. Any chance you just mixed up the commands? If you were not successful with the "fastboot flash recovery" command, it would have told you so... otherwise, it almost certainly would have wrote it out to the recovery partition.
"Any chance you just mixed up the commands? "
Always a chance of that, but I am all sorted anyway. FFF 1.3 and TWRP 2.1.1
koop1955 said:
"Any chance you just mixed up the commands? "
Always a chance of that, but I am all sorted anyway. FFF 1.3 and TWRP 2.1.1
Click to expand...
Click to collapse
You're on a roll, may as well get the latest FFF while you're hot.
Hashcode's new FFF 1.4
Very nice...damn near brick-proof now.
My Sprint Galaxy Nexus Jellybean is not rooting and will not flash a recovery. Here is what i did before the problem
Installed the Samsung Drivers
Installed and set up ADB and SDK tools
unlocked my bootloader
flashed TWRP recovery
Made a Nandroid Backup
flashed a rooted rom that was apparently for ICS (but I didn't know at the time)
These were all per qbking77's root method for Sprint Galaxy Nexus. After I flashed the rom I waited for 20 minutes for my phone to reboot and it never did. So I pulled the battery and went back into the recovery. I restored my original backup and rebooted successfully. I decided to attempt flashing the rom (that I didn't know wasn't meant for my software) again. This time when i went into recovery mode, the picture of the android with the caution symbol appeared, meaning that there was no recovery found. Now when I attempt to reflash TWRP recovery or any recovery for that matter (Now using the Galaxy Nexus toolkit for Jellybean) the program says
sending 'recovery' <xxxx KB>
FAILED <remote: Invalid command>
finished. total time: 0.012s
An Error Occurred.
and on the phone side for TWRP it says FASTBOOT STATUS - download 0055d000
and for Clockwork mod touch it says FASTBOOT STATUS - download 004c8000
Before I do anything but plug my phone into the computer, the phone says FASTBOOT STATUS - FAILInvalid Command
Since this started happening I have tried
Re-Locking and unlocking the bootloader
Uninstalling and reinstalling the toolkit
uninstalling and reinstalling the drivers
Factory resetting my phone
Is my phone just unrootable now? Please someone help!
sonshadsil94 said:
My Sprint Galaxy Nexus Jellybean is not rooting and will not flash a recovery. Here is what i did before the problem
Installed the Samsung Drivers
Installed and set up ADB and SDK tools
unlocked my bootloader
flashed TWRP recovery
Made a Nandroid Backup
flashed a rooted rom that was apparently for ICS (but I didn't know at the time)
These were all per qbking77's root method for Sprint Galaxy Nexus. After I flashed the rom I waited for 20 minutes for my phone to reboot and it never did. So I pulled the battery and went back into the recovery. I restored my original backup and rebooted successfully. I decided to attempt flashing the rom (that I didn't know wasn't meant for my software) again. This time when i went into recovery mode, the picture of the android with the caution symbol appeared, meaning that there was no recovery found. Now when I attempt to reflash TWRP recovery or any recovery for that matter (Now using the Galaxy Nexus toolkit for Jellybean) the program says
sending 'recovery' <xxxx KB>
FAILED <remote: Invalid command>
finished. total time: 0.012s
An Error Occurred.
and on the phone side for TWRP it says FASTBOOT STATUS - download 0055d000
and for Clockwork mod touch it says FASTBOOT STATUS - download 004c8000
Before I do anything but plug my phone into the computer, the phone says FASTBOOT STATUS - FAILInvalid Command
Since this started happening I have tried
Re-Locking and unlocking the bootloader
Uninstalling and reinstalling the toolkit
uninstalling and reinstalling the drivers
Factory resetting my phone
Is my phone just unrootable now? Please someone help!
Click to expand...
Click to collapse
The "picture of the android with the caution symbol" is the stock recovery. You booted into android after restoring your nandroid. During that boot, android automatically reflashed the stock recovery which overwrote TWRP. To prevent this, you need to rename or remove either the stock recovery image or the script that will flash it on boot. Look at the 101 & FAQ post linked in my signature to find out where these files are.
As for unable to flash a custom recovery, don't use a toolkit. Just use fastboot from the commandline.
Petrovski80 said:
The "picture of the android with the caution symbol" is the stock recovery. You booted into android after restoring your nandroid. During that boot, android automatically reflashed the stock recovery which overwrote TWRP. To prevent this, you need to rename or remove either the stock recovery image or the script that will flash it on boot. Look at the 101 & FAQ post linked in my signature to find out where these files are.
As for unable to flash a custom recovery, don't use a toolkit. Just use fastboot from the commandline.
Click to expand...
Click to collapse
I know where the files are, but how am I supposed to remove or rename them without root access?
sonshadsil94 said:
I know where the files are, but how am I supposed to remove or rename them without root access?
Click to expand...
Click to collapse
just remount /system on recovery, either by adb shell, either by the recovery menu after fastboot flash. boot the recovery directly from bootloader.
after /system is rw, through 'adb shell', custom recoveries have a pre-rooted/busyboxed environment, which allows you to do maintenance. this is the mount command to run in adb shell:
'mount -o rw /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system'
then just remove the files, 'umount /system' when you're done, reboot.
sent from my i9250
bk201doesntexist said:
just remount /system on recovery, either by adb shell, either by the recovery menu after fastboot flash. boot the recovery directly from bootloader.
after /system is rw, through 'adb shell', custom recoveries have a pre-rooted/busyboxed environment, which allows you to do maintenance. this is the mount command to run in adb shell:
'mount -o rw /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system'
then just remove the files, 'umount /system' when you're done, reboot.
sent from my i9250
Click to expand...
Click to collapse
When I try to flash a custom recovery using command prompt, it gives me the same error message as when using the toolkit. So, how do you do it with adb shell?
sonshadsil94 said:
When I try to flash a custom recovery using command prompt, it gives me the same error message as when using the toolkit. So, how do you do it with adb shell?
Click to expand...
Click to collapse
What are you trying to do exactly? I've read the entire thread, and I'm confused. If you want to go back to stock, look at the "flash" link in my sig. If you want to root, look at the "root" link. If you want to know about mounting /system, look at the "basics" link.
sonshadsil94 said:
When I try to flash a custom recovery using command prompt, it gives me the same error message as when using the toolkit. So, how do you do it with adb shell?
Click to expand...
Click to collapse
whats the exact fastboot command you're using to flash twrp?
problem was you made a backup of stock, which has files that restore, on boot, the stock recovery.
sent from my i9250
efrant said:
What are you trying to do exactly? I've read the entire thread, and I'm confused. If you want to go back to stock, look at the "flash" link in my sig. If you want to root, look at the "root" link. If you want to know about mounting /system, look at the "basics" link.
Click to expand...
Click to collapse
I tried your root method, and clockwork mod booted up, but the version of superuser that you linked to failed, so i rebooted my device and downloaded the jellybean version of superuser. When I tried to restart clockworkmod using the same method as before, I got the error message you see in the picture.
sonshadsil94 said:
I tried your root method, and clockwork mod booted up, but the version of superuser that you linked to failed, so i rebooted my device and downloaded the jellybean version of superuser. When I tried to restart clockworkmod using the same method as before, I got the error message you see in the picture.
Click to expand...
Click to collapse
Try using a different USB cable, and try using a different port on the back of your PC.
efrant said:
Try using a different USB cable, and try using a different port on the back of your PC.
Click to expand...
Click to collapse
I tried both of those just now, with the same error message as before.
sonshadsil94 said:
I tried both of those just now, with the same error message as before.
Click to expand...
Click to collapse
The only thing I can think of is flash the LC03 bootloader. Try flashing that first, and make sure you have the latest version of fastboot. Then try again.
would running terminal in windows with admin privileges help?
sent from my i9250
Use the command
fastboot flash recovery cwm.img
And not fastboot boot cwm.img as seen in the screenshots and see if it works this way.
If not try to do a fresh install of everything
Use fastboot erase.... to wipe everything and Fastboot install ...to install everything from scratch.
Sent from my Galaxy Nexus using Tapatalk 2
deeren said:
Use the command
fastboot flash recovery cwm.img
And not fastboot boot cwm.img as seen in the screenshots and see if it works this way.
If not try to do a fresh install of everything
Use fastboot erase.... to wipe everything and Fastboot install ...to install everything from scratch.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
thanks deeren, i asked him what was the exact command he was using, that error had to be syntax error.
sent from my i9250
Thanks all you guys but what actually ended up happening was I successfully booted into clockworkmod touch recovery since that was the only one my phone hadn't blocked yet. While in recovery i flashed supersu (the right version) and rebooted. It asked if I wanted to remove the files that flash stock recovery on boot and I selected yes. Well that didn't do jack crap, so with my newly acquired superuser powers, I deleted the files i needed to. Then I tried to flash another recovery, but they were still giving me errors. So here is the process I took completely out of luck and hopefulness that I knew what I was doing. From the command prompt with my phone in fastboot, I typed "fastboot flash recovery cwmt.img". this gave me the same "fastboot <remote: invalid command>" error, so I typed the same command and it once again gave me the "sending xxxxkb" message where it would sit on that same line until I killed the program. So I did kill the program and opened another command prompt in the same folder. I typed the same command for the third time, and everything went smoothly from there. I'm currently rooted and running Cyanogenmod 10. Once again, thanks to everyone who helped I greatly appreciate it.
sonshadsil94 said:
Thanks all you guys but what actually ended up happening was I successfully booted into clockworkmod touch recovery since that was the only one my phone hadn't blocked yet. While in recovery i flashed supersu (the right version) and rebooted. It asked if I wanted to remove the files that flash stock recovery on boot and I selected yes. Well that didn't do jack crap, so with my newly acquired superuser powers, I deleted the files i needed to. Then I tried to flash another recovery, but they were still giving me errors. So here is the process I took completely out of luck and hopefulness that I knew what I was doing. From the command prompt with my phone in fastboot, I typed "fastboot flash recovery cwmt.img". this gave me the same "fastboot <remote: invalid command>" error, so I typed the same command and it once again gave me the "sending xxxxkb" message where it would sit on that same line until I killed the program. So I did kill the program and opened another command prompt in the same folder. I typed the same command for the third time, and everything went smoothly from there. I'm currently rooted and running Cyanogenmod 10. Once again, thanks to everyone who helped I greatly appreciate it.
Click to expand...
Click to collapse
please edit the title of the thread to include the tag "[SOLVED]".
bk201doesntexist said:
please edit the title of the thread to include the tag "[SOLVED]".
Click to expand...
Click to collapse
How do you edit the title?
I have same problem to...
sonshadsil94 said:
How do you edit the title?
Click to expand...
Click to collapse
Edit first post?
Sent from my i9250