Clockwork Recovery 4.0.0.5 prob? - Desire HD Q&A, Help & Troubleshooting

im having trouble updating my recovery clockwork image, the 4.0.0.5 img is on my sdcard, ive installed terminal emulator and put
$su
#flash_image recovery /sdcard/recovery.img
and it comes up with (error scanning partitions) can anyone help?

Related

help! deleted recovery.img

just wondering if anyone can help me out here, i was trying to flash the cyanogen hero recovery image to my phone using fastboot so i erased my stock recovery image, only to get the message "remote: signature verify fail" so im now stuck with no recovery image and dont know how to get it back, can anyone help me out please?
ok so i managed to mount my system as read write in fastboot and put the recovery.img from the wwe version in to system which has gave me my recovery back but when i boot it just stays on the hero screen and says fastboot usb at the top if i have it plugged into my pc. i have no idea how to reset the original files and i didnt back up, can anyone help me pleas?
Well after trying for hours to fix this, I give up. I can't install the system.img from wwe rom posted on here it says verify failed or something similar so I stupidly tried to flash the magic 32a heroski port hoping it would work and still nothing. Is there anyway someone could post there nandroid backup file and help me flash it to see if that works? Or should I just give up. I'm really stuck now lol
you can't flash anything from fastboot because the images need to be signed.
what version of hero do you have?
if you have the wwe hero(it's not needed ) i can send you (later, now i'm at work) my nandroid backup (system,boot,recovery, splash...) so you can restore them
I have the orange hero. I used fastboot to load cyanogens recovery image then flashed the heroski rom hoping it might work lol so I ended up using fastboot to erase system. Question is do you think your nandroid backup would work? I sure hope so it would be a great help!!! Thanks.
i have the unlocked wwe hero. i'm uploading now the system, boot and recovery to rapidshare . it'll be up in a couple of minutes. if you find a orange hero backup you can restore in the same way ;-)
restoring hero wwe
download the backup from(it's better if you verify the md5):
http://rapidshare.com/files/263636068/bkp.rar.html
MD5: BEAE167BCBB1FF6D3D2701FB64604203
Put the contents on sdcard (i'm assuming that you put the images in a folder named bkp on the sdcard)
so:
download the recovery from here: http://rapidshare.com/files/262621147/cm-hero-recovery.img.zip and extract it
put your phone in fastboot mode (with the phone off, press the back key then turn the phone on).
then:
boot with the downloaded recovery
Code:
fastboot boot cm-hero-recovery.img
0) mount the partitions
Code:
adb shell mount /system
adb shell mount /sdcard
1) do a wipe
select the wipe option from the recovery menu
2) restore boot
Code:
adb shell flash_image boot /sdcard/bkp/boot.img
3) restore recovery
Code:
adb shell flash_image recovery /sdcard/bkp/recovery.img
4)restore system
Code:
adb shell
cd /system
rm -rf * (ignore the errors)
unyaffs /sdcard/bkp/system.img
5) unmount the partitions
Code:
umount /system
6) reboot
Code:
reboot
hope it helps
Ok thanks. Have to wait 4 hours to try it as I'm in work lol, what is an md5 for, just out of curiosity?
A MD5sum is a checksum to verifiy that your downloaded file isn't corrupt.
maxisma said:
A MD5sum is a checksum to verifiy that your downloaded file isn't corrupt.
Click to expand...
Click to collapse
Ok dude makes sense thanks.
thanks
enlightener said:
download the backup from(it's better if you verify the md5):
http://rapidshare.com/files/263636068/bkp.rar.html
MD5: BEAE167BCBB1FF6D3D2701FB64604203
Put the contents on sdcard (i'm assuming that you put the images in a folder named bkp on the sdcard)
so:
download the recovery from here: http://rapidshare.com/files/262621147/cm-hero-recovery.img.zip and extract it
put your phone in fastboot mode (with the phone off, press the back key then turn the phone on).
then:
boot with the downloaded recovery
Code:
fastboot boot cm-hero-recovery.img
0) mount the partitions
Code:
adb shell mount /system
adb shell mount /sdcard
1) do a wipe
select the wipe option from the recovery menu
2) restore boot
Code:
adb shell flash_image boot /sdcard/bkp/boot.img
3) restore recovery
Code:
adb shell flash_image recovery /sdcard/bkp/recovery.img
4)restore system
Code:
adb shell
cd /system
rm -rf * (ignore the errors)
unyaffs /sdcard/bkp/system.img
5) unmount the partitions
Code:
umount /system
6) reboot
Code:
reboot
hope it helps
Click to expand...
Click to collapse
ok so i finally got time to fix my phone and just did what you said and can now happily say it worked. thanks enlightener you enlightened me lol. in future i will refrain from doing random terminal stuff without researching first lol.
Bad new : My hero is out of service area
Hello,
Sorry for my english, i'm french
I made a big mistake in my files system ... A too long story
My Hero :
HBOOT-1?76.0004
Radio-6.35.04.25
July, 3 2009
Well, now, my htc hero do not work 'first page, out of service area"... I would like to make your post, but i had error :
First, fastboot Ok, Adb shell mount system and sdcard ok, wipe ok
Second, when i do this code" adb shell flash_image boot /sdcard/bkp/boot.img", my hero "said" : "header is the same, note flashing boot". Same thing for restore recovery
Can you help me ?
pitou21 said:
Hello,
Sorry for my english, i'm french
I made a big mistake in my files system ... A too long story
My Hero :
HBOOT-1?76.0004
Radio-6.35.04.25
July, 3 2009
Well, now, my htc hero do not work 'first page, out of service area"... I would like to make your post, but i had error :
First, fastboot Ok, Adb shell mount system and sdcard ok, wipe ok
Second, when i do this code" adb shell flash_image boot /sdcard/bkp/boot.img", my hero "said" : "header is the same, note flashing boot". Same thing for restore recovery
Can you help me ?
Click to expand...
Click to collapse
in this case, you don't have to restore boot or recovery because they are the same as the images posted here.
proceed with system
Ok thanks, now it's goog !

[HOWTO] Unbrick After Factory Reset From Privacy Screen

So everyone says never do this, but what can I say, I was curious
My Optimus was previously rooted using sublimewolf's method: http://forum.xda-developers.com/showthread.php?t=935312
I then proceeded to brick it by using the Factory Reset found in the Privacy Screen. This forced my phone into a recovery loop.
If you can't even get to your custom recovery, your phone might be your newest paperweight But as long as you can both get to recovery and access the phone via adb, you'll be okay.
So here's how to unbrick it:
This is the flash_image: http://www.mediafire.com/?bx14hzq5i2pq3ps
And here's the stock recovery image + nand backup: http://www.mediafire.com/?ac0e2ksq0eslytk
(In my case, I was able to skip to Step 4 in the Nandroid Instructions because I had performed a Nand Backup when I rooted, therefore the necessary files were already in place)
Nandroid Instructions:
1) Unzip both downloaded archives
2) Move the BCDS-20110203-0357 dir into /sdcard/nandroid/mem=477M (also extract recovery.img and flash_image to root dir of your SD card, as you will need to later anyway)
2a) For Clockwork Recovery, place the BCDS-20110203-0357 dir into /sdcard/clockworkmod/backup
3) Mount SD into phone if it isn't already, boot into recovery if your phone isn't already there
4) Go into the "Backup/Restore" menu, and select "nand restore", confirm and wait
5) Reboot, proceed to Recovery Instructions below
Recovery Instructions:
1) Extract recovery.img and flash_image to root dir of your SD card if you haven't already done so
2) Connect to your phone via the adb shell and input the following commands:
# su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5
# flash_image recovery /sdcard/recovery.img
# reboot recovery
3) If everything was done correctly, your phone should boot up normally to the OS
If the links above go down, let me know and I'll re-up
(thanks to tankhull for putting this info together)
(oh and you're welcome for being a guinea pig )
Thank you very much for putting this together
I am one of the curious one too.
You saved me....
If you can't get into recovery, I'm sure you can flash one through fastboot. No?
Sent from my VM670 using XDA App
Hi!
I had stock rom, but my phone was rooted.
So if whenever I turn my phone on, it goes to Clockwork Mod, does that mean it is bricked?
And will there be any way to unroot my phone after I do this? BC my 3G wasn't working at all, it should be working, but its not, so I did a factory reset.
Didn't work for me
when typing su after nand restore i get
/sbin/sh: su: not found
Ok so I have followed the instructions to the letter. And am attemptingto access adb shell. But in cmd prompt when I type adb devices it comes up with list of devices attached and says nothing. So how are we supposed to be accessing adb shell?
In clockworkmod, I went to the option for mounting and mounted the sd card, and a folder popped up on my comp, and there was no folder called Nandroid or clockworkmod
Any help guys?
I don't understand how to do the Nandroid instructions part... do I have to go to ADB?
atr0phy said:
So everyone says never do this, but what can I say, I was curious
My Optimus was previously rooted using sublimewolf's method: http://forum.xda-developers.com/showthread.php?t=935312
I then proceeded to brick it by using the Factory Reset found in the Privacy Screen. This forced my phone into a recovery loop.
If you can't even get to your custom recovery, your phone might be your newest paperweight But as long as you can both get to recovery and access the phone via adb, you'll be okay.
So here's how to unbrick it:
This is the flash_image: http://www.mediafire.com/?bx14hzq5i2pq3ps
And here's the stock recovery image + nand backup: http://www.mediafire.com/?ac0e2ksq0eslytk
(In my case, I was able to skip to Step 4 in the Nandroid Instructions because I had performed a Nand Backup when I rooted, therefore the necessary files were already in place)
Nandroid Instructions:
1) Unzip both downloaded archives
2) Move the BCDS-20110203-0357 dir into /sdcard/nandroid/mem=477M (also extract recovery.img and flash_image to root dir of your SD card, as you will need to later anyway)
2a) For Clockwork Recovery, place the BCDS-20110203-0357 dir into /sdcard/clockworkmod/backup
3) Mount SD into phone if it isn't already, boot into recovery if your phone isn't already there
4) Go into the "Backup/Restore" menu, and select "nand restore", confirm and wait
5) Reboot, proceed to Recovery Instructions below
Recovery Instructions:
1) Extract recovery.img and flash_image to root dir of your SD card if you haven't already done so
2) Connect to your phone via the adb shell and input the following commands:
# su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5
# flash_image recovery /sdcard/recovery.img
# reboot recovery
3) If everything was done correctly, your phone should boot up normally to the OS
If the links above go down, let me know and I'll re-up
(thanks to tankhull for putting this info together)
(oh and you're welcome for being a guinea pig )
Click to expand...
Click to collapse
In the nandroid instructions, for placing BCDS-20110203-0357 into the /sdcard/nandroid/mem=477M
Do I have to do that, or step 2a if I have Clockworkrecoverymod, "For Clockwork Recovery, place the BCDS-20110203-0357 dir into /sdcard/clockworkmod/backup"
Also, how do I put this directory into the /sdcard/clockworkmod/backup folder or /sdcard/nandroid/mem=477M
Do I use ADB? And if so, how do I, because I have no idea about what commands/etc to use.. or could somebody please link me to a guide on how to push a file/folder into a folder like the ones I previously mentioned (/sdcard/clockworkmod/backup folder or /sdcard/nandroid/mem=477M)
Thank you in advance for your help!
Wreak_Peace said:
In the nandroid instructions, for placing BCDS-20110203-0357 into the /sdcard/nandroid/mem=477M
Do I have to do that, or step 2a if I have Clockworkrecoverymod, "For Clockwork Recovery, place the BCDS-20110203-0357 dir into /sdcard/clockworkmod/backup"
Also, how do I put this directory into the /sdcard/clockworkmod/backup folder or /sdcard/nandroid/mem=477M
Do I use ADB? And if so, how do I, because I have no idea about what commands/etc to use.. or could somebody please link me to a guide on how to push a file/folder into a folder like the ones I previously mentioned (/sdcard/clockworkmod/backup folder or /sdcard/nandroid/mem=477M)
Thank you in advance for your help!
Click to expand...
Click to collapse
You are making this harder than it has to be. All you are trying to do is place a folder and some files on your micro sdcard. Place the micro sd card on your computer. Grab the folder "BCDS-20110203-0357" and drag it to "/sdcard/clockworkmod/backup" (yes, that one because you have the clockworkmod recovery). If you have no way of placing the micro sd card onto your computer (card reader, micro sd to sdcard converter), then leave the card in the phone, connect the phone to your compter via USB, boot into the recovery, and then turn on USB massstorage mode through the recovery options. This should make the micro sd card pop up on your computer like a usb harddrive. Drag and drop the files.
mmarz said:
You are making this harder than it has to be. All you are trying to do is place a folder and some files on your micro sdcard. Place the micro sd card on your computer. Grab the folder "BCDS-20110203-0357" and drag it to "/sdcard/clockworkmod/backup" (yes, that one because you have the clockworkmod recovery). If you have no way of placing the micro sd card onto your computer (card reader, micro sd to sdcard converter), then leave the card in the phone, connect the phone to your compter via USB, boot into the recovery, and then turn on USB massstorage mode through the recovery options. This should make the micro sd card pop up on your computer like a usb harddrive. Drag and drop the files.
Click to expand...
Click to collapse
I put my microsd card into my computer, and there are no folders called sdcard, clockworkmod, or nandroid :/
Wreak_Peace said:
I put my microsd card into my computer, and there are no folders called sdcard, clockworkmod, or nandroid :/
Click to expand...
Click to collapse
Lol, first off, the sd card IS the folder "sdcard". That will only show up on your phone. Secondly, if the folders aren't there, just make them. They are not magic folders. Just right click, and select new -> folder, and name them as described.
clockworkmod\backup\
And then copy "BCDS-20110203-0357" into the "backup" folder.
You do have the Clockworkmod Recovery, right?
I do, and now, when i opened up my cmd
I did "cd c:\android\platform-tools"
then "adb shell"
then this came up "~#"
so even then, I went ahead and did "su"
and it said,
"su
/sbin/sh: su: not found"
So, what do I do now?
and I went ahead anyways did the next step
i typed in "mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system"
then it said
"mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
(next line) mount: mounting /dev/block/mtdblock5 on /system failed: invalid arguement"
Try doing only the last two lines,
Code:
flash_image recovery /sdcard/recovery.img
reboot recovery
So I just do
"cd C:\android\platform-tools
adb shell
flash_image recovery /sdcard/recovery.img
reboot recovery"
Or do i add the su in an additional line after adb shell
?
Wreak_Peace said:
So I just do
"cd C:\android\platform-tools
adb shell
flash_image recovery /sdcard/recovery.img
reboot recovery"
Or do i add the su in an additional line after adb shell
?
Click to expand...
Click to collapse
You don't need the su because you already have the "#" sign. That means you have super user privileges.
mmarz said:
Try doing only the last two lines,
Code:
flash_image recovery /sdcard/recovery.img
reboot recovery
Click to expand...
Click to collapse
K, so this is what I came out with when doing what you said.. this is without typing in su after adb shell.
Code:
cd c:\android\platform-tools
c:\Android\platform-tools>adb shell
~ # flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
failed with error: -1
error opening /sdcard/recovery.img~ # flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
failed with error: -1
error opening /sdcard/recovery.img~ # reboot recovery
reboot recovery
This is what I came up with when i did type su after adb shell..
Code:
cd c:\android\platform-tools
c:\Android\platform-tools>adb shell
~ # flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
failed with error: -1
error opening /sdcard/recovery.img~ # flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
failed with error: -1
error opening /sdcard/recovery.img~ # reboot recovery
reboot recovery
c:\Android\platform-tools>adb shell
I've never done this method so I can't tell you why it is not working or how it should work. Sorry.
I do have my own method for solving the bootloop issue. Try flashing this with your recovery: http://www.mediafire.com/?fbaoutnaw717pnb
Place it on your SD card and then use your recovery's flash zip option to flash it. It has helped others. It will replace your recovery with the Xionia recovery. If it works, you should boot into the LG logo. Once you can do that, boot into your recovery by using the correct button combo and flash any rom that you want to use.
mmarz said:
I've never done this method so I can't tell you why it is not working or how it should work. Sorry.
I do have my own method for solving the bootloop issue. Try flashing this with your recovery: http://www.mediafire.com/?fbaoutnaw717pnb
Place it on your SD card and then use your recovery's flash zip option to flash it. It has helped others. It will replace your recovery with the Xionia recovery. If it works, you should boot into the LG logo. Once you can do that, boot into your recovery by using the correct button combo and flash any rom that you want to use.
Click to expand...
Click to collapse
So i extract it to root of the micro sd? all of it? and then instead of recovery.img its vrecovery.img?
And so if it replaces my recovery with xionias recovery, it will boot into android and I can use my phone normally?

Fixed my phone :)

I had errors in my previous recovery which showed:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount /sdcard
Also errors such as error formatting system and mounting system.
So i flashed a new recovery, amon_ra's recovery, this one included the option to move the recovery log to sd. Then re-installed my rom.
Here's how i did it.
Plugged in the phone, booted to fastboot.
I opened the cmd and typed:
cd C:\Users\Francis\Documents\ANDROID files\Android SDK Windows\tools
This is the path that contains the fastboot.exe. I then typed fastboot.exe.
Downloaded recovery-RA-desire-v2.0.0.img and cut n pasted into the tools folder.
I typed: fastboot oem enableqxdm 0
I then typed fastboot flash recovery recovery-RA-desire-v2.0.0.img
The recovery file was obtained from this link: http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-desire-v2.0.0.img
I then went into bootloader, then recovery and re-installed my rom.
If you use an EXT, you would be better off with 2.0.1
It is common problem with PVT4 and Clockwork recovery 2.5.0.7 which is installed during rooting with Unrevoked
I used AmonRa 2.0.1 but recently switched to 4EXTRecovery.
OP: Are you seriously that stupid you had to create third thread for it?!

[Q] Trying to Flash TWRP with no Avail...

I am trying to flash TWRP by using the following commands in Terminal Emulator (can't get KFU to recognize my KF):
Code:
SU
flash_image recovery /sdcard/twrp.img
But I recieve:
Code:
failed with error: -1
Dunno what's going on here. Any ideas?
Running CM7, rooted, have FFF, current recovery is Custom CWM-Based Touch Recovery by DooMLoRD.
ratchetandclankf said:
I am trying to flash TWRP by using the following commands in Terminal Emulator (can't get KFU to recognize my KF):
Code:
SU
flash_image recovery /sdcard/twrp.img
But I recieve:
Code:
failed with error: -1
Dunno what's going on here. Any ideas?
Running CM7, rooted, have FFF, current recovery is Custom CWM-Based Touch Recovery by DooMLoRD.
Click to expand...
Click to collapse
Why don't you use gscripts to flash TWRP? Or uninstall/reinstall your drivers so KFU will recognize.
Sent from my Amazon Kindle Fire using xda premium
ratchetandclankf said:
I am trying to flash TWRP by using the following commands in Terminal Emulator (can't get KFU to recognize my KF):
Code:
SU
flash_image recovery /sdcard/twrp.img
But I recieve:
Code:
failed with error: -1
Dunno what's going on here. Any ideas?
Running CM7, rooted, have FFF, current recovery is Custom CWM-Based Touch Recovery by DooMLoRD.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1483280
If you really want to flash it from the command line...
Code:
dd if=/path/to/twrp.img of=/dev/block/mmcblk0p5
Use at your own risk.

[Q] CWM - No such file or directory

Hello,
I'm new in this forum.
I have problem, I download recovery.img (working) for Android 4.4.2 CM 11 and i try to install this img, but I can't. I use cmd.exe on Windows or emulator on Phone and I have the same problem:
No such file or directory
Click to expand...
Click to collapse
I have recovery. img on sdcard and flash_image on system/bin
With cmd.exe I use
adb shell
flash_image recoveryonly /sdcard/recovery.img
and with emulator
su
flash_image recoveryonly /sdcard/recovery.img
I can't install CWM RECOVERY for GIO
What I did wrong ?
I use this code
Code:
adb push c:\flash_image /sdcard/
adb push c:\recovery.img /sdcard/
adb shell
su
mount -o remount, rw /system
cp /sdcard/flash_image /system/bin
cd /system/bin
chmod 777 flash_image
flash_image recovery /sdcard/recovery.img
I tried to put recovery.img to lastest zip package but it crashed
Please help me I searched very much but I can't find answer. Can anyone make zip package of CWM RECOVERY for GIO, Thanks
FenoMenAG
Just download any CWM flashable .zip and replace recovery.img ( I used CWM 5.0.2.7 ext4only zip and it worked )
Sent from my GT-S5660 using Tapatalk 2
Thanks, I have CWM Recovery 6.0.4.7 i packed wrong files to zip.
I have other problem when I install the latest verision of experminental system (i do wipe data/factory reset, wipe cache partition i wipe dalvik cache)
I mount data i system and install it and rebot i go to CWM not to system any idea what I do wrong ?
Sorry...I've installed CM11 with CWM6.0.4.7 :
1. Wipe data/cache and dalvik cache
2. Flash CM11 nightly ( experimental shoul work too )
P.S. I don't mount data or system , after flash just "reboot system now"
Sent from my GT-S5660 using Tapatalk 2
Thanks, I have CWM Recovery 6.0.4.7 i packed wrong files to zip.
I have other problem when I install the latest verision of experminental system (i do wipe data/factory reset, wipe cache partition i wipe dalvik cache)
I mount data i system and install it and rebot i go to CWM not to system any idea what I do wrong ?
i had kind of the same problem,rebooting only in recovery,when i installed the recovery.img the second time i waited a while before restarting the gio and that is the trick...
download the recovert.img from the cm11 31january or 1february (about 5mb)
put it on sdcard
terminal on gio, su
flash_image recoveryonly /sdcard/recovery.img
wait a while!!! than reboot or reboot in recovery
I have Android 4.4.2 with CM 11 !!!
FenoMenAG said:
I have Android 4.4.2 with CM 11 !!!
Click to expand...
Click to collapse
when you get in recoverymode after rebooting you have to reinstall your recovery 6.0.4.7
so first reinstall (sideload,see [guide][how to] cwm 6.0.4.7)your cm11 again,than you should be able to boot in cm11 again.
than do the reinstall of cwm 6.0.4.7 see topic above and beware to take some time after the flash_image command so the cwm is completely!!! installed

Categories

Resources