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] factory reset problem

I have a problem. I inadvertantly did a factory reset running AOKP 4.2.2 mr 1 when trying to move over to mr 1 mb2. I am unlocked, hboot 2.14.0000 S-on CID 1111111. I know I need to reformat my SD card. The problem is that HTC sync does not see my phone when it is connected by USB. The device manager sees the phone and lists it under portable devices, drives, and cameras. Unfortunately it is not listed in "My Computer" where I can do the format.
Any help with this issue would be greatly appreciated!

How are you mounting the sd card? If you mount it through TWRP it should show up properly, and then you can format it.
Sent from my Evita

timmaaa said:
How are you mounting the sd card? If you mount it through TWRP it should show up properly, and then you can format it.
Sent from my Evita
Click to expand...
Click to collapse
I have not been using TWRP. I am on Clockwork. Can I work with TWRP through ADB or Fastboot? I'm in unfamiliar waters here and need some tutorial instruction.
Thanks for all of your help!

If you want to mount through recovery you'll need to install TWRP instead of CWM, I don't think CWM includes a mount feature, right? If you want to install it just follow these instructions:
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter TWRP recovery on your phone and mount your storage via the mount menu.
Sent from my Evita

timmaaa said:
If you want to mount through recovery you'll need to install TWRP instead of CWM, I don't think CWM includes a mount feature, right? If you want to install it just follow these instructions:
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter TWRP recovery on your phone and mount your storage via the mount menu.
Okay. I installed TWRP recovery and formatted the /SD into FAT32. All appears to have gone well. I downloaded the latest CM 10.2 nightly for 10/4/2013. I unzipped the file to a folder on my desktop. I copied the boot.img into my platform-tools folder that contains fastboot.exe and adb.exe. I copied the zipped file for the ROM onto the freshly formatted /SD (now D: in My Computer). I used fastboot flash boot boot.img. It wrote correctly. I then went into recovery and launched TWRP. It did not give me the option of mounting the folder as indicated in the FAQ tutorial in this forum. I instead used the Install button in TWRP. It failed:
Updating partition details...
Installing '/sdcard/cm-10.2-20131004-NIGHTLY-evita.zip'...
Checking for MD5 file ...
Skipping MD5 check: no MD5 file found.
Verifying zip signature...
assert failed: getprop("ro.bootloader") == "2.14.0000" ||
getprop("ro.bootloader") == "2.15.0000"
E:Error executing updater binary in zip '/sdcard/cm-10.2-20131004-NIGHTLY-evita.zip'
Updating partition details ...
Failed
What am I doing wrong? I've tried clearing caches, rebooting into the bootloader through adb, rebooting into fastboot.
So far the help has been outstanding. Get me over this last hurdle please!
Click to expand...
Click to collapse

Since your first post have you updated your firmware/hboot to 2.15? It looks like the bootloader check in the installer is failing because you don't have the correct hboot.
Sent from my Evita

timmaaa said:
Since your first post have you updated your firmware/hboot to 2.15? It looks like the bootloader check in the installer is failing because you don't have the correct hboot.
Sent from my Evita
Click to expand...
Click to collapse
I went back on Friday night and installed an old version of AOKP that uses hboot 2.14 and it loaded perfectly. The phone has been up and running all weekend. Thank you so much for your help!
Can I update the firmware with S-on? I thought it was locked down.
Is a firmware update done in the same way as a ROM update? e.g. download the .zip file and fastboot flash hboot "hboot 2.15 package.zip"?
Learning on the fly...
Thanks again!

You can't update firmware unless you have s-off. The firmware is flashed a bit differently, it's best to refer to the instructions found with the download in Turge's stock ROM thread.
Sent from my Evita

Problem [BOOTLOADER]

Describing my problem :
Since yesterday my OPO did some random reboots. I was running Paranoid Android and it worked perfectly...
Yesterdayevening after it rebooted another time, my OPO didn't start at all... It seems that my bootloader won't load the OS.
This morning, I did a complete wipe and I've put the stock ROM from the CM site back on my OPO ( XNPH33R signed boot).
-Fastboot works
-Recovery works
-Bootloader won't load OS. ( only the One Plus logo pops up (not the bootanimation)). After that it reboots over and over...
Update 1 17:30 5/10/2014 :
I'm in a bootloop, I have no ROM. I have the TWRP recovery. And the bootloader is LOCKED.
So I tried to unlock the bootloader with the toolkit for the OnePlus one. ( I tried it also manually with cmd).
----WHAT IT DOES in CMD/ Phone-------
In CMD : " OKAY [0.012 s]
Finished. total time : 0.012 s
OPO : It opens up my TWRP recovery but it does not unlock the bootloader
Update 2 19:52 5/10/2014 :
I've been able to unlock the bootloader...
with the command " fastboot oem device-info" , I received :
Bootloader tampered : True
Bootloader unlocked : False ( because the toolkit only did " fastboot oem unlock " , I did an adb sideload with a zip "OnePlusOne-OnlyBootloaderToggle" from the thread
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912. Now my bootloader is back UNLOCKED.
I hope the bootloop will stop when I do a factory / reset.
10:40 6/10/2014 :
I tried several times to flash stock roms from the official site / from the forum. None of them 'work'.
Can someone please help me?? He still bootloops!!! How frustrating thazt is,I tried everything from threads on the forum. Nobody is ansering my thread. Any reason for that ?

My suggestion is this: grab one of the recovery flashable versions of CM11S from here, boot into your TWRP recovery and use adb to push the ROM zip to your phone, then use the install function in TWRP to flash it.
To push the zip to your phone you first need to put it in your adb/fastboot folder (wherever you have adb.exe and fastboot.exe located on your PC), make sure your phone is booted into TWRP and connected to your PC, open a command prompt from within your adb/fastboot folder (shift + right click anywhere in the folder, then select open command prompt here), and issue this command:
Code:
adb push <name of file.zip> /sdcard/
*Please note the '<' and '>' symbols are not included in the command.
From there just flash the ROM like you would flash any other ROM.
Transmitted via Bacon

Failure with E:
timmaaa said:
My suggestion is this: grab one of the recovery flashable versions of CM11S from here, boot into your TWRP recovery and use adb to push the ROM zip to your phone, then use the install function in TWRP to flash it.
To push the zip to your phone you first need to put it in your adb/fastboot folder (wherever you have adb.exe and fastboot.exe located on your PC), make sure your phone is booted into TWRP and connected to your PC, open a command prompt from within your adb/fastboot folder (shift + right click anywhere in the folder, then select open command prompt here), and issue this command:
Code:
adb push <name of file.zip> /sdcard/
*Please note the '<' and '>' symbols are not included in the command.
Transmitted via Bacon
Click to expand...
Click to collapse
Pushing the zip into sdcard :good:
Installing the zip gives a message about E:
example :
something with E: path
E: unable to wipe
E: error executing updater binary in zip 'sdcard/cm11.0... .zip
Proberly more

Are you sure you're attempting to flash one of the recovery flashable zips? What's the full filename?
Transmitted via Bacon

timmaaa said:
Are you sure you're attempting to flash one of the recovery flashable zips? What's the full filename?
Transmitted via Bacon
Click to expand...
Click to collapse
cm-11.0-XNPH33R-bacon-signed
Links
1. Recovery flashable zips of the complete ROMz:
XNPH22R
XNPH25R
XNPH33R
From your link
EDIT-----
1. I had flashed the stock recovery back.
2. Did a factory reset
3. Wiped cache
4. Wiped media
5. Flashed TWRP back
6. ADB push zip in /sdcard/
7. Flashed the zip SUCCESSFUL after these steps
I still have a bootloop

Have you tried to format your internal sd card and flash your zip. Remember if you format though you will lose everything on your sdcard. Make sure you backup everything first if you want to try this. Also if you do this you will have to push your zip back to the phone

Who can even solve this?...
playya said:
Have you tried to format your internal sd card and flash your zip. Remember if you format though you will lose everything on your sdcard. Make sure you backup everything first if you want to try this. Also if you do this you will have to push your zip back to the phone
Click to expand...
Click to collapse
My internal storage was already formatted. I just have the TWRP and the zip on my phone.
[Q] In the TWRP recovery menu in 'Advanced' what has to be between Copy Log to SD and Terminal Command? There is a blank spot ,there should be button normally?
How is it even possible i have nothing but the recovery and the zip and I still got a bootloop...
Is there somebody that knows something else that i can try?
Is it possible to flash perhaps with odin?

VictorByttebier said:
My internal storage was already formatted. I just have the TWRP and the zip on my phone.
[Q] In the TWRP recovery menu in 'Advanced' what has to be between Copy Log to SD and Terminal Command? There is a blank spot ,there should be button normally?
How is it even possible i have nothing but the recovery and the zip and I still got a bootloop...
Is there somebody that knows something else that i can try?
Is it possible to flash perhaps with odin?
Click to expand...
Click to collapse
definitely not odin thats Samsung my friend. Partition SD Card is whats missing in TWRP for you. I asked about formatting internal because a similar thing happened to my friend. We had to format internal then adb push recovery and rom and all was well again. If you have tried this recently then my bad but if you have not it wont hurt to try it again in that order
format internal
adb push recovery
adb push rom
reboot
Take a look in here as well http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061

Bootloop fixed
It finally worked!!! How weird that i already found a zip like on the thread but with XNPH33R and also with the persist and recovery.img and flash-all etc... but it didn't work.
Now i just have to update from the settings
At beginning I was convinced that a bootloop could be fixed with factory/reset would do it. Like it always worked on my previous smartphone.
Thank you playya and timmaaa for the responses!:good: You are awesome! See me sitting here with a

Need help to root into moto g3

Hi Team,
I was able to unlock the bootloader on motg3 and do a twrp img. However when I ran the command
adb reboot recovery it doesn't boot into the recovery img and it just says no command on the phone screen. Please help.
Thanks,
Arun

'No Command' means you've still got the stock recovery. Flash TWRP again by:
Code:
fastboot flash recovery twrp.img
(Where twrp.img is the filename of the custom recovery).
Do *not* reboot the phone into system, instead scroll down to select 'recovery' and press power button to load TWRP.
TWRP should load now, swipe to confirm modification (important). Now go to reboot>recovery. Allow the phone to reboot back to TWRP. Now you can select reboot>system and TWRP shall stick permanently.
Broadcasted from Zeta Reticuli

Volume buttons aren't working on the mobile. So I tried adb reboot recovery. But still it didn't boot into recovery. Here is what I had tried.
https://pasteboard.co/HhTTVr1n.png

TWRP will be overwritten by stock recovery if the system is booted up before booting TWRP once.
If the volume buttons are broken, then I'd suggest you first copy twrp.img into phone memory, boot the recovery by :
Code:
fastboot boot recovery.img
Allow modifications, then go to Install>Select Image (img), browse twrp.img on phone>select 'recovery' and swipe to flash.
Now reboot>recovery and then reboot>system. Now it should stick.
I'd recommend being extra careful if your volume button, especially volume down button is broken. If you somehow end up with a non-booting phone, you'd have no way (that I know of) to get to the bootloader mode.
Broadcasted from Zeta Reticuli

I tried fastboot boot recovery.img but it says waiting for device and nothing happens.
https://pasteboard.co/HhVmOD9.png

Make sure your phone is in the bootloader mode and is being recognized by the pc. Run:
Code:
fastboot devices
and make sure it returns with 1 entry of the device along with the text 'fastboot'. Then the command should work.
Broadcasted from Zeta Reticuli

arunkumar413 said:
Hi Team,
I was able to unlock the bootloader on motg3 and do a twrp img. However when I ran the command
adb reboot recovery it doesn't boot into the recovery img and it just says no command on the phone screen. Please help.
Thanks,
Arun
Click to expand...
Click to collapse
Make sure you have installed proper Motorola drivers & Fastboot on you're PC / laptop,
You can get those files from this thread https://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
After installing proper drivers goto this thread https://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537 download & flash latest twrp by given instructions by OP..

I just checked the usb drivers page but there aren't any usb drivers for Linux.
https://mobilesupport.lenovo.com/us/en/solution/MS88481
I tried the command sudo fastboot boot recovery.img and it returned there is no such file or directory. Should recovery file be on phone or on the laptop. Also should all these commands be run from a specific folder either on phone or system?
[email protected] ~ $ sudo fastboot boot recovery.img
cannot load 'recovery.img': No such file or directory
[email protected] ~ $

arunkumar413 said:
I just checked the usb drivers page but there aren't any usb drivers for Linux.
https://mobilesupport.lenovo.com/us/en/solution/MS88481
I tried the command sudo fastboot boot recovery.img and it returned there is no such file or directory. Should recovery file be on phone or on the laptop. Also should all these commands be run from a specific folder either on phone or system?
[email protected] ~ $ sudo fastboot boot recovery.img
cannot load 'recovery.img': No such file or directory
[email protected] ~ $
Click to expand...
Click to collapse
Yes, the terminal should be open to the directory containing the recovery.img file. For simplicity, place twrp into your home folder. The default location for most terminals is home, so no worries about directory now.
Just to be sure, type in :
Code:
ls
(LS lowercase)
Your file should be in the list. You are ready to flash now.
Try the fastboot boot command again.
As you're using GNU/Linux (guessed it early from your screenshots), drivers should not be a problem, at least for this device; unless you are running a minimal or highly customised distro like Gentoo or Arch.
Note: And yes, you'll need another copy of TWRP inside phone storage to actually flash into the device, the PC one is just used to boot temporarily into TWRP.
Broadcasted from Zeta Reticuli

To add more clarity. There are two files here:
1) recovery.img
2)twrp.img
I was able to get the twrp.img file but where do I get the recovery.img file?

Hi All,
Thanks for all the help. I'm now able to root into the device.

arunkumar413 said:
To add more clarity. There are two files here:
1) recovery.img
2)twrp.img
I was able to get the twrp.img file but where do I get the recovery.img file?
Click to expand...
Click to collapse
I apologize for confusing you. They are the one and same. Just rename the downloaded TWRP img file to twrp.img and copy it over to both home folder in pc and into phone.
Use fastboot boot command on pc to temporarily boot up twrp in phone, allow modifications by swiping, go to Install>Install Image (img) option on the bottom>select the twrp.img inside the phone and flash it to 'recovery' partition.
Now reboot>recovery. This time the twrp should be permanently flashed and working properly. You are done.
Edit: Didn't see your last post, glad that you worked it out
Broadcasted from Zeta Reticuli

arunkumar413 said:
To add more clarity. There are two files here:
1) recovery.img
2)twrp.img
I was able to get the twrp.img file but where do I get the recovery.img file?
Click to expand...
Click to collapse
There can be only one either recovery.img file or twrp.img.....as you are trying to replace your stock recovery by TWRP... And you need .img file for this.... Just check the name there should be just one if you have TWRP.img then there is no need for recovery.img file

Hi All,
After I was able to flash twrp and root into the phone I switched off the phone and turned on after couple of days. But now the display isn't turning on. However adb is able to detect the device and also I was able to access the file system through usb. Could you please help me troubleshoot the display issue?

arunkumar413 said:
Hi All,
After I was able to flash twrp and root into the phone I switched off the phone and turned on after couple of days. But now the display isn't turning on. However adb is able to detect the device and also I was able to access the file system through usb. Could you please help me troubleshoot the display issue?
Click to expand...
Click to collapse
Try rebooting into the recovery mode by:
Code:
adb reboot recovery
And doing a Cache/ART cleanup.
If the phone boots up (it should vibrate) but the screen doesn't light up (not even a blank dark grey screen), then I'm afraid the display is at fault.

How to root moto g3
I try to root my motor but network has gone
Then how I root