Database Info

[Q] Cannot load Recovery Clockwork

I'm trying to root my Nexus S 2.3.4 and so far I have unlocked it but when trying to flash Recovery Clockwork in the Command Prompt I get the error mesage "signature verification failed".
Any help would be appreciated.

XCarBoneX said:
I'm trying to root my Nexus S 2.3.4 and so far I have unlocked it but when trying to load Recovery Clockwork I get the error mesage "signature verification failed".
Any help would be appreciated.
Click to expand...
Click to collapse
How are you trying to flash your recovery?

krohnjw said:
How are you trying to flash your recovery?
Click to expand...
Click to collapse
I'm using [GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020/T only)
http://forum.xda-developers.com/showthread.php?t=895545

XCarBoneX said:
I'm using [GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020/T only)
http://forum.xda-developers.com/showthread.php?t=895545
Click to expand...
Click to collapse
You're getting Signature verification failed using fastboot flash recovery filename.img?
If so ensure a few things - 1.) you've got the correct file name and 2.) you have a good download of the img.

Filename is correct and img seems OK.
Boot Nexus S into Recovery Mode with USB debugging on
Command prompt:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
error: cannot load 'recovery-clockwork-3.0.2.4-crespo.img
Win 7 64-bit SP1
Android 2.3.4 GRJ22 unlocked
Device Manager:
ADB Interface
Android Original ADB Interface
fastboot devices in Command shows:
33332EFE0C9300EC

XCarBoneX said:
Filename is correct and img seems OK.
Boot Nexus S into Recovery Mode with USB debugging on
Command prompt:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
error: cannot load 'recovery-clockwork-3.0.2.4-crespo.img
Win 7 64-bit SP1
Android 2.3.4 GRJ22 unlocked
Device Manager:
ADB Interface
Android Original ADB Interface
fastboot devices in Command shows:
33332EFE0C9300EC
Click to expand...
Click to collapse
The error message did not say anything about signature verification failed. The problem is fastboot cannot find the file you specify in the command line.
SOLUTION: you have to go into the folder that you saved the "recovery-clockwork-3.0.2.4-crespo.img" (for example, if you saved the file in C:\android\) using the following commands:
Code:
c:
cd android
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img

I have already set Path variables in Windows for the Andriod tools folder which contains Fastboot and the Recovery image file.
Could the problem be with the Android driver or Android 2.3.4 GRJ22?

XCarBoneX said:
I have already set Path variables in Windows for the Andriod tools folder which contains Fastboot and the Recovery image file.
Could the problem be with the Android driver or Android 2.3.4 GRJ22?
Click to expand...
Click to collapse
No - Fastboot can't find the file.
c:\Downloads>fastboot flash recovery fakefile.img
error: cannot load 'fakefile.img'
This takes place before checking if your device is connected, if you are unlocked to write the recovery, etc.
You're sure the cwd of the cmd prompt is the directory you downloaded the file to? Alternatively provide the full path to the recovery image.
Edit: Rereading your post above you have the recovery file in the directory as the tools. This won't resolve via the path. You either need to cd into that dir or provide the full path. Fastboot takes a local img file as the argument (local to your cwd unless you specify the full path).

Got it!!
Firmly rooted in Mother Earth.
You were absolutely correct with the cd\ command.
Running Cyanogen 7.02
Thanks so much!!

To fix hanging on cyanogen screen:
Factory data reset
wipe cache
advanced
wipe dalvik
All's good in Roots Reggae land.

XCarBoneX said:
Not quite done yet.
On reboot it hangs on the cyanogen screen.
Click to expand...
Click to collapse
You can either try reflashing or hook it up via adb and run a logcat - it will show you what it's hanging on or waiting on. Unless it's stuck *very* early on you should be able to adb shell and then run logcat.

Same problem here - Fastboot repeatedly returns "error: cannot load recovery.img" when trying to load CWM
Tried this solution:
suksit said:
SOLUTION: you have to go into the folder that you saved the "recovery-clockwork-3.0.2.4-crespo.img" (for example, if you saved the file in C:\android\) using the following commands:
Code:
c:
cd android
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
Click to expand...
Click to collapse
but I get "The system cannot find the path specificed." when "cd android" is entered.
- ";C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools" is the path
EDIT: Fixed.
1) Moved .img file to root in C:
2) c:
3) cd\
4) fastboot flash recovery recovery.img
Got it finally.

need help flashing recovery

I went ahead and did the oem unlock but when I try and flash the recovery (or boot) image through fastboot using this:
C:\androidsdk\tools\fastboot flash recovery XXXXXXX.img
or
C:\androidsdk\tools\fastboot flash boot rootboot.img
I keep getting this error:
error: cannot load 'XXXXXXX.img'
I've trouble shooted all of the main things. ...my device is definitely attached. I have the recovery .img file in the same folder as fastboot (along with the 2 needed .dll files). I've also done stuff like re-install usb drivers, re-install sdk, I've oem unlocked 3 times.
I have a stock wifi xoom with 3.2
Here are the 2 main root guides I've been using
http://forum.xda-developers.com/showthread.php?t=1170760&highlight=how+to+root
http://forum.xda-developers.com/showthread.php?t=1242241&highlight=how+to+root
Thank you for your help

in cmd(assuming windows) type cd c:/•••••tools
your xoom should be in adb reboot bootloader
type fastboot flash recovery recovery.img
rename recovery file as recovery.img and place in tools/platformtools as the case may be.
sending this message from stock xoom.

awesome, thanks. What you told me was enough to show me what I was doing wrong.
In case someone else reads this later on I had to type
cd C:\androidsdk\tools ...hit enter
then it looked like this
C:\androidsdk\tools> ...and I then typed
fastboot flash recovery XXXX.img
earlier I also renamed the folder to androidSDK from android-sdk

[Q] BRICKED My Phone! I Need To HelpEMERGENCY PLS

I had a problem now and i am not found the solution. I bricked my phone after Full wipe
sorry for my bad english.
Phone is: HTC ONE S (s4)
super cid, unlocked, rooted, hboot 2.16, radio 1.35a
recovery: TWRP 2.7.x
last rom before i full wipe; viperOneS 3 (4.2.2) and before i installed the kernel maximus hd 's kernel
Pls not send me the link; because i try to everything to i found the forum links/posts. i search to forums for 4-5 hours no result for my kind of problem
Now: i can't flash rom and i phone not open
what i did ?
1. adb reboot-bootloader and open the Recovery (TWRP 2.7.x)
2. I do Full Wipe; Factory Reset, Wipe Cache, data, system, dalvik & format Data menus
3. my rom zip is gone on the SD CArd. ok it's normal. i need to recopy rom.zip to sd card
i think ; flash the rom via sideload / adb push methods. WTF ! 2 options are not work for some errors.
Problems;
ADB Sideload feature ; error device not found. i investigate the problem and i see the Phone driver not installed on the Windows. (win 8.1.1)
Device Manager look; One S (unknown device)
EDIT: i try on the Windows 7 laptop but result is same. windows doesn't recognize the phone when the Recovery Mode. and i can't sideload feature
Ok , i try to push .
Phone is start screen but no start because no have OS ! but when the mode device manager phone is OK
try this things;
adb push rom.zip /sdcard ERROR : No such file or directory
adb push rom.zip sdcard ERROR : No such file or directory
adb push rom.zip /sdcard/ ERROR: no such file or directory
adb push rom.zip /sdcard/rom.zip ERROR: Is a Directory
adb push rom.zip /data/media/0/ ERROR: Is a directory
bla bla bla i try to every possibilities
i m tired and i think to destroy my phone PLS HELP ME
I arrived at the point; i need to flash rom but how to copy zip to SD card ?

Sorry for my english too xD
I had the same problem last week.
Try to go in bootloader, then in fastboot and connect the device to the PC, from the PC with the Promt go in your adb folder
Code:
cd c:/[I]position of your folder[/I]
then test if adb sees your device with the command
Code:
adb devices
If it's ok then try again to push again the ROM with the command
Code:
adb push [I]name_of_the_file.zip[/I] /sdcard/zip.rom

casu91 said:
Sorry for my english too xD
I had the same problem last week.
Try to go in bootloader, then in fastboot and connect the device to the PC, from the PC with the Promt go in your adb folder
Code:
cd c:/[I]position of your folder[/I]
then test if adb sees your device with the command
Code:
adb devices
If it's ok then try again to push again the ROM with the command
Code:
adb push [I]name_of_the_file.zip[/I] /sdcard/zip.rom
Click to expand...
Click to collapse
thnx man, but when i go to fastboot, ADB devices are empty ? no adb push command work.
fastboot devices command works but did not help me the problem
thanks in other adviseee

natmacax said:
thnx man, but when i go to fastboot, ADB devices are empty ? no adb push command work.
fastboot devices command works but did not help me the problem
thanks in other adviseee
Click to expand...
Click to collapse
Then you should fix the driver problem first, have you tried it with both Win 8.1 and 7?

doesn't work ADB on fastboot mode. both of win 7 and win 8.
BUT in the fastboot mode no driver problem ! i dont understand, you say ; when phone in the fastboot mode, adb push command should work ?
BTW, just now in the fastboot mode, its finally fastboot flash zip rom.zip command works, but *UCKN the new problem occurs
when the write flash command, error : data length is too large!
i investigate this problem now, do you know the problem root cause ?

natmacax said:
I had a problem now and i am not found the solution. I bricked my phone after Full wipe
[..]
i m tired and i think to destroy my phone PLS HELP ME
I arrived at the point; i need to flash rom but how to copy zip to SD card ?
Click to expand...
Click to collapse
In a last try you can simply downgrade your hboot and run last ruu. Then re-uprade your hboot and so
Edit : ADB doesn't work in fastboot mode

benJX said:
In a last try you can simply downgrade your hboot and run last ruu. Then re-uprade your hboot and so
Edit : ADB doesn't work in fastboot mode
Click to expand...
Click to collapse
just now in the fastboot mode, its finally fastboot flash zip rom.zip command works, but i have a new problem
when the write flash command, error : data length is too large!
does have a any solution for this ?
also, you sayed upgrade downgrade hboot.... this is solution of the adb push problem ?
thnx

natmacax said:
doesn't work ADB on fastboot mode. both of win 7 and win 8.
BUT in the fastboot mode no driver problem ! i dont understand, you say ; when phone in the fastboot mode, adb push command should work ?
BTW, just now in the fastboot mode, its finally fastboot flash zip rom.zip command works, but *UCKN the new problem occurs
when the write flash command, error : data length is too large!
i investigate this problem now, do you know the problem root cause ?
Click to expand...
Click to collapse
Sorry if I wasn't clear, what i was saying is that adb push command should work if your adb drivers are working!
benJX said:
In a last try you can simply downgrade your hboot and run last ruu. Then re-uprade your hboot and so
Edit : ADB doesn't work in fastboot mode
Click to expand...
Click to collapse
I think that's a good solution if you can't push the zip with adb commands, I didn't think of that because when I had the problem I did it with the adb command

casu91 said:
I think that's a good solution if you can't push the zip with adb commands, I didn't think of that because when I had the problem I did it with the adb command
Click to expand...
Click to collapse
natmacax said:
also, you sayed upgrade downgrade hboot.... this is solution of the adb push problem ?
Click to expand...
Click to collapse
I'm not sure about what I'm saying but adb sideload doesn't work on recoveries made for hboot 2.16, aswell as mounting sdcard.
When you try to adb sideload from modded recovery for 2.16, it recognizes only 48mb of memory that's why you can't use it. But I repeat I'm not sure about it I never had to use adb sideload.
Edit : And you cannot flash a rom with fastboot. Flashing zip from it has to be done only when you want ot uprgade/downgrade firmware files in ruu mode

benJX said:
I'm not sure about what I'm saying but adb sideload doesn't work on recoveries made for hboot 2.16, aswell as mounting sdcard.
When you try to adb sideload from modded recovery for 2.16, it recognizes only 48mb of memory that's why you can't use it. But I repeat I'm not sure about it I never had to use adb sideload.
Edit : And you cannot flash a rom with fastboot. Flashing zip from it has to be done only when you want ot uprgade/downgrade firmware files in ruu mode
Click to expand...
Click to collapse
IT'S FINALLY OVER
THANKS FOR ALL
i think the problem as you sad, hboot & TWRP version !
i downgrade hboot 2.16 > modded 2.15 (then i try flash rom sideload or pus, via twrp 2.7 didn't work)
then i reflash recovery downgrade TWRP 2.6.3 and all it works
i flash the rom via adb sideload, all it works.

[ROOT] [SOLVED] flashing recovery twrp MOTOROLA MOTO 3rd 2015

I've unlocked the bootloader and now i'm trying to start a twrp recovery to access and install SuperSU which is copied (zip file) inside my internal storage of my phone. I'm using adb fastboot and an osprey twrp downloaded from this site, i write in the command prompt (opend from the adb fastboot folder, where there's the twrp file) :
>fastboot flash recovery twrp-osprey-3.0.2-r1.img
target reported max download size of 268435456 bytes
error: cannot load 'twrp-osprey-3.0.2-r1.img': No error
what should i do to load this recovery (or another one, it doesn't matter) and to open SuperSU to let me to root my phone???

leodom01 said:
I've unlocked the bootloader and now i'm trying to start a twrp recovery to access and install SuperSU which is copied (zip file) inside my internal storage of my phone. I'm using adb fastboot and an osprey twrp downloaded from this site, i write in the command prompt (opend from the adb fastboot folder, where there's the twrp file) :
>fastboot flash recovery twrp-osprey-3.0.2-r1.img
target reported max download size of 268435456 bytes
error: cannot load 'twrp-osprey-3.0.2-r1.img': No error
what should i do to load this recovery (or another one, it doesn't matter) and to open SuperSU to let me to root my phone???
Click to expand...
Click to collapse
First verify that you have debugging enabled from the developer options, second check that the recovery file is located in the folder plataform tools (Tools with which the flashing process is done).
Third, verify that you have the device drivers installed correctly.
If it does not work try to do root with kingroot (Look for the official page, download the same apk), the process is not difficult ... Clarify the device will restart repeatedly, at each restart reopen the application to continue with the process, it may work as it may not. (Do it at your own risk). If this method works follow the steps in this video to install TWRP recovery: https://www.youtube.com/watch?v=xwFC41d-7Yg
I think that for process of rooteo you can go ahead alone.

leodom01 said:
I've unlocked the bootloader and now i'm trying to start a twrp recovery to access and install SuperSU which is copied (zip file) inside my internal storage of my phone. I'm using adb fastboot and an osprey twrp downloaded from this site, i write in the command prompt (opend from the adb fastboot folder, where there's the twrp file) :
>fastboot flash recovery twrp-osprey-3.0.2-r1.img
target reported max download size of 268435456 bytes
error: cannot load 'twrp-osprey-3.0.2-r1.img': No error
what should i do to load this recovery (or another one, it doesn't matter) and to open SuperSU to let me to root my phone???
Click to expand...
Click to collapse
Your answer is here "error: cannot load 'twrp-osprey-3.0.2-r1.img': No error"... Everything is working perfectly, except there is no file by that name that fastboot can find, therefore it didn't do anything, thus no error. The problem is your TWRP img is in the wrong place or named incorrectly. Your problem is basic commands or file structure, not a problem with the phone or fastboot.

leodom01 said:
I've unlocked the bootloader and now i'm trying to start a twrp recovery to access and install SuperSU which is copied (zip file) inside my internal storage of my phone. I'm using adb fastboot and an osprey twrp downloaded from this site, i write in the command prompt (opend from the adb fastboot folder, where there's the twrp file) :
>fastboot flash recovery twrp-osprey-3.0.2-r1.img
target reported max download size of 268435456 bytes
error: cannot load 'twrp-osprey-3.0.2-r1.img': No error
what should i do to load this recovery (or another one, it doesn't matter) and to open SuperSU to let me to root my phone???
Click to expand...
Click to collapse
i guess the name of recovery is wrongly typed so rename the recovery in that folder to something simple like twrp.img take note of the extension as in windows the extension is hidden by default. hope it helps you.
---------- Post added at 09:04 AM ---------- Previous post was at 09:03 AM ----------
Arcade said:
i guess the name of recovery is wrongly typed so rename the recovery in that folder to something simple like twrp.img take note of the extension as in windows the extension is hidden by default. hope it helps you.
Click to expand...
Click to collapse
Or also you then have to use the command
fastboot flash recovery twrp.img
Click to expand...
Click to collapse

Thank you! I did it in past too, but I wasn't working I tried again today and I worked, don't ask me why! Thank you anyway guys!

[TWRP RECOVERY] + [ROOT] Teclast Tbook 11 (E5A6) Android 5.1

Hello,
This is my first post on how to root and install TWRP recovery on the Teclast Tbook 11 (E5A6) android 5.1
The TWRP works with touch and I haven't encounterd any problems with it
I have not created the TWRP, it is made by nik2670
We only flash or boot the recovery, then install SuperSU 2.82- 201705271822. Nothing else !
Sorry for the mirrors. (I will remove them if you're the owner)
Be sure to have ADB drivers v1.4.3 installed before you continue.
Download TWRP 2.8.7.0. Recovery Tbook 11 and ADB and Fastboot and put it in a folder on your desktop
Enable USB debugging on your tablet (Settings->Developers->usb-debugging)
Connect your tablet with your PC
Open up a CMD prompt in the folder you have your ADB. Win+R type CMD, hit enter. Copy the path of ADB and put in the CMD prompt
Code:
cd [path]
Mine was cd "C:\Users\Thermaltake\Desktop\ADB FASTBOOT FILES WINDOWS"
In the CMD prompt, type
Code:
adb devices
If you see your device you good to go.
Type
Code:
adb reboot bootloader
your tablet reboots, select android while it reboots
Now we're in fastboot mode, just to be sure we see the device type
Code:
fastboot devices
. If you can't see your device like me you have to manually install drivers.
Do you have the recovery.img in the same folder as ADB? Good. Type
Code:
fastboot boot recovery.img
OR
Code:
fastboot flash recovery recovery.img
to permanently have the TWRP recovery on your device (I recommand boot)
Your tablet is now in recovery mode! You can acces the internal storage. Add SuperSU-v2.82 on your device.
Hit Install->SuperSU-v2.82-201705271822->Swipe to confirm flash->Wipe dalvik cache->Reboot----> DONE !
Image of succesfully root
Thanks for following my guide, if there are any problems I try to update the tutorial or provide more information to you!
Mathero11
Thanks to nik2670 for the recovery, chainfire for supersu and unpersonally xda developers for other flash/root tutorials