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.

Xperia L stuck at recovery screen

Model - Sony xperia l - C 2014
I wanted to flash CM12 to my device. I followed the instructions on Cyanogenmod site.
I enabled USB debugging mode.
I unlocked the bootloader (as per the instructions on sony)
I'm using a linux machine. I've installed adb and fastboot tools.
I havent backed up my bootloader or system (but ive taken data backup before starting the process)
1) When i try to flash the CM ROM using adb sideload method, i get the error..
this package is for device c2105 c2104 c2105 c2104 taoshan this device is .
2) If i try to use fastboot method to flash new recovery, using the folowing command
#fastboot flash recovery cm-12-20150906-NIGHTLY-taoshan-recovery.img
i get the error..
sending 'recovery' (9702 KB)...
OKAY [ 0.308s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.310s
Now my phone is unable to boot normally. it gets stuck at recovery.
This is the first time i've tried to flash a new ROM. Any suggestion would be greatly appreciated.
Thank you

abhishek.karvi said:
Model - Sony xperia l - C 2014
I wanted to flash CM12 to my device. I followed the instructions on Cyanogenmod site.
I enabled USB debugging mode.
I unlocked the bootloader (as per the instructions on sony)
I'm using a linux machine. I've installed adb and fastboot tools.
I havent backed up my bootloader or system (but ive taken data backup before starting the process)
1) When i try to flash the CM ROM using adb sideload method, i get the error..
this package is for device c2105 c2104 c2105 c2104 taoshan this device is .
2) If i try to use fastboot method to flash new recovery, using the folowing command
#fastboot flash recovery cm-12-20150906-NIGHTLY-taoshan-recovery.img
i get the error..
sending 'recovery' (9702 KB)...
OKAY [ 0.308s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.310s
Now my phone is unable to boot normally. it gets stuck at recovery.
This is the first time i've tried to flash a new ROM. Any suggestion would be greatly appreciated.
Thank you
Click to expand...
Click to collapse
1.boot to recovery
2.connect to pc
3. use this commands in adb:
adb shell
setprop ro.product.device taoshan
4. flash cm12 or any other rom for taoshan
do this all while in same session (dont reboot after the terminal command or it will be gone)
Sent from my mint using XDA Free mobile app

SdtBarbarossa said:
1.boot to recovery
2.connect to pc
3. use this commands in adb:
adb shell
setprop ro.product.device taoshan
4. flash cm12 or any other rom for taoshan
do this all while in same session (dont reboot after the terminal command or it will be gone)
Sent from my mint using XDA Free mobile app
Click to expand...
Click to collapse
Thank you for the reply SdtBarbarossa .
I've done steps 1,2.
On 3rd step, when i give command #adb shell , im getting error....
error: device unauthorized. Please check the configuration dialog on your device.
Now since the device is stuck at recovery and does not boot, i cant re-authorize my computer from my phone.
I'd like to mention that i started fooling around with my ROM on a different workstation and im trying to fix this on a different workstation right now... having said that, do i need to retry the mentioned steps from the previous computer?
Thanks again.

abhishek.karvi said:
Thank you for the reply SdtBarbarossa .
I've done steps 1,2.
On 3rd step, when i give command #adb shell , im getting error....
error: device unauthorized. Please check the configuration dialog on your device.
Now since the device is stuck at recovery and does not boot, i cant re-authorize my computer from my phone.
I'd like to mention that i started fooling around with my ROM on a different workstation and im trying to fix this on a different workstation right now... having said that, do i need to retry the mentioned steps from the previous computer?
Thanks again.
Click to expand...
Click to collapse
Thats bad ;-( flash aromafm and use the inbuild terminal!
Then you need only the setprop command
Sent from my mint using XDA Free mobile app

SdtBarbarossa said:
Thats bad ;-( flash aromafm and use the inbuild terminal!
Then you need only the setprop command
Sent from my mint using XDA Free mobile app
Click to expand...
Click to collapse
ive downloaded aromafm. It says 1) copy the file to phones sdcard and 2) boot into recovery and select "install from zip"
The problem is :
1) I'm unable to copy anything to phone, since the phone is stuck at recovery and MTP is not working when i connect it to USB
2) My recovery doesnt have option "install from zip".... (recovery screen says - Cyanogen recovery)
Can i forcibly push the file to my sd card using flashtool or adb? or will keeping the file on external sd card work too? if so, how do i proceed?
Also i forgot to mention earlier that when i give the command # adb devices, it says unauthorised.
But im able to use the command #adb sideload *.zip (although it fails)
When i try the sideload method..flash starts but fails with the error..
On my computers terminal it says
Total xfer: 1.00x
On my phone the error is
this package is for device c2105 c2104 c2105 c2104 taoshan this device is .
E: Failed to install /sideload/package.zip
.
.
Installation aborted
I have downloaded the zip file from cyanogenmod official site, and im sure that ive taken the correct file for my device, and have checked that the hash mathces.
Thnx again.

abhishek.karvi said:
ive downloaded aromafm. It says 1) copy the file to phones sdcard and 2) boot into recovery and select "install from zip"
The problem is :
1) I'm unable to copy anything to phone, since the phone is stuck at recovery and MTP is not working when i connect it to USB
2) My recovery doesnt have option "install from zip".... (recovery screen says - Cyanogen recovery)
Can i forcibly push the file to my sd card using flashtool or adb? or will keeping the file on external sd card work too? if so, how do i proceed?
Also i forgot to mention earlier that when i give the command # adb devices, it says unauthorised.
But im able to use the command #adb sideload *.zip (although it fails)
When i try the sideload method..flash starts but fails with the error..
On my computers terminal it says
Total xfer: 1.00x
On my phone the error is
this package is for device c2105 c2104 c2105 c2104 taoshan this device is .
E: Failed to install /sideload/package.zip
.
.
Installation aborted
I have downloaded the zip file from cyanogenmod official site, and im sure that ive taken the correct file for my device, and have checked that the hash mathces.
Thnx again.
Click to expand...
Click to collapse
Copy the file to external sd
Sent from my mint using XDA Free mobile app

SdtBarbarossa said:
Copy the file to external sd
Sent from my mint using XDA Free mobile app
Click to expand...
Click to collapse
Even if I copy the file to external sd card, I'm unable to install it from there since I don't get a "install" option in recovery.
Its been too long so I went to the Sony store and got it fixed.
Anyways, Thanks for your help SdtBarbarossa, i appreciate it.
Once again, thank you

abhishek.karvi said:
Model - Sony xperia l - C 2014
I wanted to flash CM12 to my device. I followed the instructions on Cyanogenmod site.
I enabled USB debugging mode.
I unlocked the bootloader (as per the instructions on sony)
I'm using a linux machine. I've installed adb and fastboot tools.
I havent backed up my bootloader or system (but ive taken data backup before starting the process)
1) When i try to flash the CM ROM using adb sideload method, i get the error..
this package is for device c2105 c2104 c2105 c2104 taoshan this device is .
2) If i try to use fastboot method to flash new recovery, using the folowing command
#fastboot flash recovery cm-12-20150906-NIGHTLY-taoshan-recovery.img
i get the error..
sending 'recovery' (9702 KB)...
OKAY [ 0.308s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.310s
Now my phone is unable to boot normally. it gets stuck at recovery.
This is the first time i've tried to flash a new ROM. Any suggestion would be greatly appreciated.
Thank you
Click to expand...
Click to collapse
Try this command for installing recovery: " fastboot flash boot recovery.img"
change "recovery" word with your downloaded recovery file name.

@SdtBarbarossa
Hi, I have run into the same problem as OP, and have been trying to install aromafm but get the following output:
Code:
E: Cannot load volume /misc!
Finding update package...
Opening update package...
Verifying update package...
E: footer is wrong
E: signature verification failed
Installation aborted.
E: Cannot load volume /misc!
I have tried several aroma zips but its the same with all of them
I have checked and indeed the device ID is set to "".

Alhaj said:
Try this command for installing recovery: " fastboot flash boot recovery.img"
change "recovery" word with your downloaded recovery file name.
Click to expand...
Click to collapse
Ok, I was afraid to try this but finally dared, and it fixed my situation!
I ran it, and unlike trying to flash to recovery, flashing to boot proved successful (no "command not allowed" message). Then unplugged USB, and phone booted to recovery (I highly recommend TWRP), from where I installed the system and additional apps (surprisingly, without errors about device ID or incorrect signatures), and afterwards booted into system flawlessly.
Thanks!

severoraz said:
Ok, I was afraid to try this but finally dared, and it fixed my situation!
I ran it, and unlike trying to flash to recovery, flashing to boot proved successful (no "command not allowed" message). Then unplugged USB, and phone booted to recovery (I highly recommend TWRP), from where I installed the system and additional apps (surprisingly, without errors about device ID or incorrect signatures), and afterwards booted into system flawlessly.
Thanks!
Click to expand...
Click to collapse
Well its been a long time since i last had the time to pick up my XL ... but nice to hear that the fix still worked if you have any other question send me a pn since im no longer monitoring these threads ( due to missing time ;-( )

SdtBarbarossa said:
Well its been a long time since i last had the time to pick up my XL ... but nice to hear that the fix still worked if you have any other question send me a pn since im no longer monitoring these threads ( due to missing time ;-( )
Click to expand...
Click to collapse
Thanks! I picked mine up as a backup phone but this community has kept it running smooth

[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!

Need help! Willing to pay!

XDA Friends,
WOULD YOU LIKE TO MAKE A LITTLE MONEY TODAY???
I am calling out to you in DIRE need. I have royally screwed up my brand new Razer phone (US) and as far as I can tell there is only one way back and that is to get one of you gracious souls to do me a very big favor. What I need is a SD Card that has been formatted to work on a Razor phone and that contains, an ENTIRE cheryl-global-3005.zip. One that has not only the boot.img but the system.img. The reason I need to get this from one of you is that while I was in TWRP I accidentally flashed boot.img in System instead of Boot. This overwrote System and so now I cannot boot into the main system, it essentially goes into a boot loop. So that means I cannot get adb to work which means I cannot move files onto the SD Card (that is specially formatted for that phone and cannot be used to move files physically). And I failed to get the entire image onto the sd card prior to this happening so I do not have a system.img file on the phone in any capacity with which to flash to at least get back to factory.
So I'm thinking that if I can get someone to send me a formatted sd card that contains the full cheryl zip then I can put that card in my phone flash the system.img file from it that should get me back.
If you are willing to help me out with this I WILL PAY YOU.
PLEASE send me a private message here so we can arrange this as soon as possible. I'm phoneless without this fix.

You forgot to mention where are you from, my friend.

My advice comes free of charge:
Hold the power key until the device shuts off. Then download the system images from https://developer.razerzone.com/razer-phone-dev-tools/factory-images/
Unzip this file and run the flash_all.bat file. (I assume you have fastboot set up already considering you've flashed TWRP). Once this completes you should see it booting up to a stock system.
You also have the option of manually flashing the system.img from this factory image using fastboot. No SD card required

Unfortunately, I cannot get to the download mode anymore in order to use fastboot. The only thing I can get to is TWRP. Any other attempt just sends it into bootloop.
@Kimbaroth I'm from North Carolina, United States.

Unfortunately, I cannot get to the download mode anymore in order to use fastboot. The only thing I can get to is TWRP. Any other attempt just sends it into bootloop.
@Kimbaroth I'm from North Carolina, United States.

OK scratch that I am able to get into download mode now. @Flippy125 thanks for the advice. I'll give that a try.

Ok, I am able to run fastboot devices and I can see that it recognizes the device. However, when i try to run "fastboot flash flash_all.bat" I get the following error message: unknown partition 'flash_all.bat'
error: cannot determine image filename for 'flash_all.bat'
I also tried "fastboot push cheryl-global-3005.zip" and that failed with error: unknown command push
I also tried "fastboot flash system.img" and that failed with error: unknown partition 'system.img'
error: cannot determine image filename for 'system.img'
Not sure what I'm doing wrong here. Any thoughts?

lostnsound said:
Ok, I am able to run fastboot devices and I can see that it recognizes the device. However, when i try to run "fastboot flash flash_all.bat" I get the following error message: unknown partition 'flash_all.bat'
error: cannot determine image filename for 'flash_all.bat'
I also tried "fastboot push cheryl-global-3005.zip" and that failed with error: unknown command push
I also tried "fastboot flash system.img" and that failed with error: unknown partition 'system.img'
error: cannot determine image filename for 'system.img'
Not sure what I'm doing wrong here. Any thoughts?
Click to expand...
Click to collapse
I think you meant "fastboot flash system_a system.img"
And you don't need to do "fastboot flash flash_all.bat", you just double click flash_all.bat that is inside the folder and it should work, as long as you have fastboot correctly installed
EDIT: I'm not sure, but I think "flash_all.bat" would erase all your files. Can anyone confirm this?

lostnsound said:
Ok, I am able to run fastboot devices and I can see that it recognizes the device. However, when i try to run "fastboot flash flash_all.bat" I get the following error message: unknown partition 'flash_all.bat'
error: cannot determine image filename for 'flash_all.bat'
I also tried "fastboot push cheryl-global-3005.zip" and that failed with error: unknown command push
I also tried "fastboot flash system.img" and that failed with error: unknown partition 'system.img'
error: cannot determine image filename for 'system.img'
Not sure what I'm doing wrong here. Any thoughts?
Click to expand...
Click to collapse
fastboot flash system system.img

@el4nimal and @waiflih
What is the difference between system and system_a?
Also, can you explain what slot A and slot B are? I have not run into those terms before when rooting other phones (previous was a Nexus 6p).
Thanks for the help guys! I really appreciate it. I'm at work right now so I will try your suggestions at lunch when I can run home for bit.

lostnsound said:
@el4nimal and @waiflih
What is the difference between system and system_a?
Also, can you explain what slot A and slot B are? I have not run into those terms before when rooting other phones (previous was a Nexus 6p).
Thanks for the help guys! I really appreciate it. I'm at work right now so I will try your suggestions at lunch when I can run home for bit.
Click to expand...
Click to collapse
I'm not sure, but I think those are partitions like C:/ and D:/ on a PC.
"System_a" would flash system.img only on Slot A, "System_b" on Slot B, I don't know what "system" does....i think it flashes both

IT'S ALIVE!
So "fastboot flash system system.img" is what worked. Appears that running that command updated system_a based on what I could see in the cmd prompt logging. But it worked as I am now able to boot into the operating system. THANK YOU GUYS SO MUCH!!! You saved me $700. What can I do to support you?

lostnsound said:
IT'S ALIVE!
So "fastboot flash system system.img" is what worked. Appears that running that command updated system_a based on what I could see in the cmd prompt logging. But it worked as I am now able to boot into the operating system. THANK YOU GUYS SO MUCH!!! You saved me $700. What can I do to support you?
Click to expand...
Click to collapse
I'm glad that it worked. Just enjoy it!

Reading this brought a warm feeling to my heart. Have fun with the phone. It's great!

Glad this got sorted. I think I can speak for all of us tinkerers when I say we've all been in this situation before and called upon the forum for advice. Pay it forward ^_^

unsupported file system error "raw"

Hey, i messed up my phone by installing something via magisk. Now im trying to install a new rom.
When i open the phone (lenovo p2a42), i get encryption error. For able to fix that problem i have to use "fastboot format userdata" command but i get raw file system error. How can i fix this? Disk manager doesn't see the phone.
Code:
adb reboot bootloader
error: no devices/emulators found
fastboot devices
ZY223TNMLC fastboot
fastboot format userdata
(bootloader) has-slot:userdata: not found
fastboot: error: Formatting is not supported for file system with type 'raw'.
edit ok i figure it out. power button, adv setting, recovery than continued to next step, there is no need to format

Jhumsmt said:
continued to next step
Click to expand...
Click to collapse
You mean continue to regular boot or continue to recovery?