the error i get every time i try every method i have found... yea i searched... it just keeps saying when i get to the flash_image recovery command
it says that command doesnt exist?
can some one help me out?
Just download rom manager from the market and use it to flash. You can do clockwork or amon ra
Sent from my HERO200 using XDA App
You should be entering "flash_image recovery" either using a terminal emulator on your phone OR using adb shell. Both of which you should enter the "su" command to get the substitute user (hash sign "#").
Try this:
Open up terminal emulator on your phone and type "flash_image"
Regardless of whether you get root (#) or not ($) you should get a response saying "usage: flash_image partition file.img" So it'll look something like this:
Code:
$flash_image <- this is what you enter
usage: flash_image partition file.img <-this is what gets returned to you
$
Let me know what response you get.
AbKc0rax said:
the error i get every time i try every method i have found... yea i searched... it just keeps saying when i get to the flash_image recovery command
it says that command doesnt exist?
can some one help me out?
Click to expand...
Click to collapse
As the other posters have said, rom manager from the market is your easiest choice,
as far as flashing a recovery manually, put the recovery image of your choice
on your sd card, and either from the terminal emulator, or from adb shell,
you need to make sure you have the # prompt, indicating you have
superuser rights. If you just see $ you need to type su first.
Once you have the # prompt, the command would be
flash_image recovery /sdcard/recovery.img
(replace recovery.img with the exact name of the recovery image you
are trying to flash). as the filenames are case sensitive, I usually rename
the recovery image to a more manageable form, (ie: I rename clockwork to
clockwork.img or amonra to amonra.img, shortening the names and ensuring
that I don't have an issue with missing a capitalized letter).
Related
I currently am running an older version of jf's recovery image and would like to upgrade to Cm recovery 1.4.
I have looked through the fourms and can't find any help on installing a new recovery image over the old one. I was just wondering if I would have to install it like I did with the first one, downgrade my phone and all that or is there a way I can insatll it with out having to do all those steps over again.
Thanks for you help in advance
Ps. Didn't really know where to post this thread sorry if it is in the wrong area..
Hi,
This should really be in the Q&A section.
To answer your question, save the .img on to your SD card, do not rename it, go to your terminal emulator and type flash_image recovery /sdcard/cm-recovery-1.4.img
As long as you did not rename the file, and you spell the commands right, then you should be golden.
QUESTION !!!!!!!!!! >>>> Q&A Section !!!
don't forget the su. also you will want to do reboot recovery so you can see your pretty new recovery image.
thanks
Thanks for all the help guys
ps
And I guess I brain farted not putting it in the Q&A section, my bad
still not working
ironnius said:
Hi,
This should really be in the Q&A section.
To answer your question, save the .img on to your SD card, do not rename it, go to your terminal emulator and type flash_image recovery /sdcard/cm-recovery-1.4.img
As long as you did not rename the file, and you spell the commands right, then you should be golden.
Click to expand...
Click to collapse
I did what you said it it didn't work, it gave me the message, this was all done in terminal emulator.
"error writing recovery : Permission denied"
Is there something i have to do to allow this?
do the following in terminal emu
su
flash_image recovery /sdcard/cm-recovery-1.4.img
Put the recovery img on the root of your ad card
Installing the CyangenMod Recovery IMG
1. Open up the Terminal App on your phone
2. Type in su then press on "Always Allow"
3. Type in the following:
Code:
cd /sdcard
wget http://n0rp.chemlab.org/android/cm-recovery-1.4.img
flash_image recovery /sdcard/cm-recovery-1.4.img4. Done! Easy as Pie
Fingerlickin said:
do the following in terminal emu
su
flash_image recovery /sdcard/cm-recovery-1.4.img
Click to expand...
Click to collapse
thank you that worked
1sickat said:
Put the recovery img on the root of your ad card
Installing the CyangenMod Recovery IMG
1. Open up the Terminal App on your phone
2. Type in su then press on "Always Allow"
3. Type in the following:
Code:
cd /sdcard
wget http://n0rp.chemlab.org/android/cm-recovery-1.4.img
flash_image recovery /sdcard/cm-recovery-1.4.img4. Done! Easy as Pie
Click to expand...
Click to collapse
yes please download the recovery image and put it on the sdcard, THEN download the recovery image AGAIN using the wget command and replace the first one. THEN use the flash_image command which requires su permissions WITHOUT getting those permissions first.
Sorry, in a bad mood today.
I wanted to try Cyanogens new Rom when I bumped into snag on the first step.
I cant get in Recovery mode! I have done it befor to get root access but I dont know what happened. It always freezes at the Rogers Logo when I hold Home and push power.
I have very little knowledge of this stuff but Ive tried to install Cyans Pimped recovery.img but It keeps telling me cannot load recovery.img. I think I only tried through fastboot though, I have attempted to through adb shell but I'm not 100% how that works, so I assumed it failed.** Oh and I also Tried erasing my old Recovery Image, which was successful but didnt help anything
I have root access and I own a Canadian HTC Dream. I have Cupcake, Thanks for your help in advance ^^
Hi, it sounds like you erased the standard recovery image, but haven't sucsessfully flashed a new one, which is why the phone will have.
Try flashing it on your phone using the terminal. First grab "terminal emuator" or "Better Terminal".
Put the recovery image on the root of your SD card and name it recovery.img
Open terminal and type:
su <- when the prompt appears, choose always allow
flash_image recovery /sdcard/recovery.img
It's done when the cursor drops down to the next line. Turn the phone off and hopefully recovery will be working.
Hey thanks for the response but still having the same problem.
When I type su it always says Access Granted Courtesy of yada yada. Im assuming this isnt a problem. I flashed my recovery.img and it didnt give me a response. I guess it worked but yet, Still Freezes on Rogers Logo.
I found the Right Recovery.img for a Rogers Dream but now I cant seem to flash it into the Phone. When I type the cmd in Terminal It doesnt give me any errors. But when i go to Erase it in Fast boot it says the remote partition does not exist. Can anyone figure this one out? Im probably doing something small and stupid wrong but any help would be greatly appreciated.
Sounds like you have few different tutorials mixed up. You don't type cmd in terminal. cmd is Windows command to get into command prompt, from there you type your adb commands so if we assume that you placed your NEW recovery image in the root of you sd card and named it recovery.img you would type
From your computer
Window's key +r
cmd
adb shell
flash_image recovery /sdcard/recovery.img
reboot recovery
OR
From terminal
su
flash_image recovery /sdcard/recovery.img
and wait for # to appear, then type
reboot recovery and see what happens
There's a way to do it from fast boot screen as well, you can find a tut in developement section.
Good luck
Hey thanks, That does clear a few things up. I just ended up resetting my phone and it was a breeze from there. Thanks for your help.
After I got my nexus back from HTC for a faulty power button, my nexus has been rooted via a replaced motherboard. Now I have already root my phone and unlocked the bootloader, however when I try to flash the recovery image I get
sending 'recovery' (4074 KB)... OKAY
writing 'recovery'... FAILED (remote: image update error)
Also I can somehow access recovery, and it looks as it should. However when I try to backup my rom it says "Run 'nandroid-moblie.sh' via adb!" and similar things when I try any other the other options. Could someone please help with this?
How are you trying to flash it? Fastboot is the best foolproof way to do flash the recovery. I have never really seen that error before, what recovery are you trying to flash?
Your nandroid error is most likely because the sdcard thinks it's still mounted, or is mounted. Also, I don't know if this still happens but make sure you only do a backup, not backup +ext if you don't have an ext partition on the sdcard.
he's obviously using fastboot...
Did you make sure recovery.img had the right MD5 hashes as amon_ra posted?
I have check the MD5 checksums, and they match up. Also, i am using fastboot to flash, and I am trying to flash RA-nexus v2.0.0. Are you suggesting that I remount the sd card to get it to flash the recovery image?
cajer said:
I have check the MD5 checksums, and they match up. Also, i am using fastboot to flash, and I am trying to flash RA-nexus v2.0.0. Are you suggesting that I remount the sd card to get it to flash the recovery image?
Click to expand...
Click to collapse
I would suggest you try in command line with the adb commands as follows:
adb shell
su
mount -o rw,remount /dev/block/mtdblock4 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 775 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
You need flash_image for this, check the wiki for the file...don't forget to put the recovery in the root of the sdcard and rename it to recovery.img for convenience purpose
gravufo said:
I would suggest you try in command line with the adb commands as follows:
adb shell
su
mount -o rw,remount /dev/block/mtdblock4 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 775 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
You need flash_image for this, check the wiki for the file...don't forget to put the recovery in the root of the sdcard and rename it to recovery.img for convenience purpose
Click to expand...
Click to collapse
What do I do with flash_image? Also this device came back stock with frg 83, which I am trying to flash the recovery on. When I type in adb shell, I get "error: device not found" even though I can see it through "fastboot devices".
cajer said:
What do I do with flash_image? Also this device came back stock with frg 83, which I am trying to flash the recovery on. When I type in adb shell, I get "error: device not found" even though I can see it through "fastboot devices".
Click to expand...
Click to collapse
flash image has to be placed in the root of your sd card as well as the recovery!
As for the adb shell, try enabling USB Debugging in Setting > Applications > Development
Make sure you're rooted too (use SuperOneClick if you're not already)
I can get through that string of commands until
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
Then it says "No such file or directory". I have already rooted, and both the flash_image and recovery file have been placed in the root directory of the sd card.
Well, after you did that string of commands, does the problem persist?
Also, do you have at least 400MB free on your SD card?
Well, I can't get
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
to work as it responds with "No such file or directory". Even if I go through after the errors, the recovery still gives 'nandroid-moblie.sh' via adb!" and similar messages. Do I need to find a way to put the file install-recovery.sh in my sd card root directory if so, where can I get it? In addition when I try to flash recovery with nexus one superboot I get "(remote: signature verify fail)" even though the MD5 sum matches up.
Yes I have over 5 gbs on the sd card.
rm = remove
The steps you are trying to perform with the 2 rm command is to remove the 2 files that automatically rewrite your recovery.
If you reboot without succeeding in removing these files, the recovery image you just flashed will be written over by the stock recovery...
Since you have rebooted, and are still having the problem, you need to do the whole list of commands again... be careful how you type...
Sent from my Nexus One using XDA App
Danger, it seems as I can't remove those two files as I get the error message "rm failed for /system/etc/install-recovery.sh, No such file or directory". Any ways to successfully remove them?
Sounds like the files aren't actually there then, unless you're making a typing error...
Did your recovery update after the last attempt? Did it look different, what is the recovery version that is listed on the recovery screen?
Sent from my Nexus One using XDA App
I have been flashing different themed recoveries to see if any data transfers, and the background changes. But as before the actions all say "Run 'nandroid-moblie.sh' via adb!" or something similar.
cajer said:
I have been flashing different themed recoveries to see if any data transfers, and the background changes. But as before the actions all say "Run 'nandroid-moblie.sh' via adb!" or something similar.
Click to expand...
Click to collapse
if the rm doesn't work it's fine.
But what about your flashing command? It simply works or outputs an error too?
When u flashed themed ones, did the background change?
The background did change when I flashed the themed ones, however it still outputs errors like "Run 'nandroid-moblie.sh' via adb!" when i try to run any of the options under recovery. The fastboot flashing command gives this "writing 'recovery'... FAILED (remote: image update error)" error.
cajer said:
The background did change when I flashed the themed ones, however it still outputs errors like "Run 'nandroid-moblie.sh' via adb!" when i try to run any of the options under recovery. The fastboot flashing command gives this "writing 'recovery'... FAILED (remote: image update error)" error.
Click to expand...
Click to collapse
When you try running a NAND backup or restore a previous NAND?
When restoring, the backup must be at the exact position where it was when you did it: /sdcard/nandroid/HT#####/BCD######
I was trying to backup my current image, and this happens with all other actions even the shut down action on the recovery page just with "Run 'reboot -p' via adb!"
lawl xD that seems useful...
well, that's extremely odd to be honest...uhm...I think you should try and contact amon_ra if possible...He knows the code of his recovery and might know what's wrong...
I really have no clue, sorry =\
PS: Have u tried clockworkmod recovery?
Alright I will try contacting amon_ra, and I will try clockwork tomorrow. I was going for amon_ra recovery to get Sense HD on it with sd partition. Thanks for the help though I learned more stuff about my phone.
EDIT: Wow, clockwork installed like a charm, and I didn't even have to do anything. I'm now a clockwork convert.
somehow i screwed up my recovery. i'm running ads-magpie with no problems. I need to get my recovery working again. either amon-ra or clockwork. in adb shell i type: flash_image recovery /sdcard/recovery-RA-dream-v1.7.0.img It says /system/bin/sh: flash_image: not found
please help
if you are able to boot into the phone then go into your terminal app and then type:
su
mount /sdcard
flash_image recovery /sdcard/recovery-RA-dream-v1.7.0.img
and you're good to go...
still doesn't work?
then flash the recovery using a fastboot zip
newellj79 said:
somehow i screwed up my recovery. i'm running ads-magpie with no problems. I need to get my recovery working again. either amon-ra or clockwork. in adb shell i type: flash_image recovery /sdcard/recovery-RA-dream-v1.7.0.img It says /system/bin/sh: flash_image: not found
please help
Click to expand...
Click to collapse
Can you get into fastboot (hold down the camera button when you restart)? If so, then flash recovery image from there.
Open command prompt in directory where you have recovery image stored. Command:
fastboot flash recovery recovery-RA-dream-v1.7.0.img
yes but hopefully he has fastboot set up. if not then i'm sure we can walk you through or forward you to a tut on how to do so
I got it working, truth be told I don't how. I tried a command string that previously didn't work. It responded out if memory, twice. For kicks I tried boot into recovery and low and behold clockworkmod. thanks guys.
no problem anytime
I have an MTS CDMA HTC Hero, and I'm un able to put a custom recovery image on. I went into that HBOOT menu and at the top it says "S-ON" and I was reading that it needs to say "S-OFF" in order for me to put a custom recovery like Clockwork Mod onto it. My phone is rooted, I used z4root. I have no idea how to put the custom recovery on. And I cannot find the free version of ROM Manager in the market, and I tried the appbrain method and putting the .apk on my sd card method and nothing is working
Any help would be appreciated
Thanks!
xcolester5x said:
I have an MTS CDMA HTC Hero, and I'm un able to put a custom recovery image on. I went into that HBOOT menu and at the top it says "S-ON" and I was reading that it needs to say "S-OFF" in order for me to put a custom recovery like Clockwork Mod onto it. My phone is rooted, I used z4root. I have no idea how to put the custom recovery on. And I cannot find the free version of ROM Manager in the market, and I tried the appbrain method and putting the .apk on my sd card method and nothing is working
Any help would be appreciated
Thanks!
Click to expand...
Click to collapse
Our phone does not require S-OFF to flash a custom recovery. When I get to a computer I'll upload a recovery.img for you to download. Until then download Terminal Emulator and Busybox Installer. With Busybox Installer open it and install busybox
私のEVO 3Dから送信される。
there should be aman ra or an older recovery in the wiki
Whenever I put my hero into recovery mode I also get this red exclamation mark with a phone beside it. Is that because I don't have a custom recovery installed on the phone or?
And I'm also not too sure how to install a custom recovery on the phone.
Flash recovery using: ADB
NOTE: This method will work while you are booting into the current recovery on the phone.
1.Download the ClockworkMod Recovery: HeroC
2.Copy the recovery.img to root of the SD card.
3.Boot the phone into recovery.
4.Open command prompt, cd to the Android SDK directory & type the following commands:
adb shell
mount /sdcard
flash_image recovery /sdcard/"name of recovery".img
reboot recovery
5.Your phone should now reboot into the ClockworkMod Recovery (orange text for 3.0+).
Flash recovery using: Terminal Emulator Note: Requires s-off, otherwise you'll recieve "out of memory" errors.
1.Download the ClockworkMod Recovery: HeroC Download Optimus V Download.
2.Move recovery.img to root of the SD card.
3.Open the Terminal Emulator on the phone & type the following commands:
4.:
su
flash_image recovery /sdcard/"name of recovery".img
reboot recovery
5.The phone should now reboot into the ClockworkMod Recovery (orange text for 3.0+).
Whenever I type in the first code I get "error: device not found" and I have my phone in recovery mode
do you have android sdk installed on your computer, if no , install it. if yes, open a command prompt and type,
cd C:\android-sdk-windows\tools
next type:
adb devices
it should list your device
next type:
adb shell
you should get a # sign
then procede from there
or try the terminal emulator method,,,much easier. you can get "terminal emulator " from android market...good luck
whenever I change my directory to the tools folder ADB doesn't work, but when I change it to the "Platform-Tools" folder ADB works.
Sorry for being such a pain-in-the-butt, but I'm new to this whole rooting stuff.
What's the terminal emulator method?
I was trying to do this method
"Type in the following commands:
adb push recovery-clockwork-2.5.0.7-heroc.img /sdcard/recovery-clockwork-2.5.0.7-heroc.img
adb shell
su
cd /sdcard/
flash_image recovery recovery-clockwork-2.5.0.7-heroc.img
reboot recovery"
but that doesn't seem to be working for me either, that's where I get the "Flash_Image: not found" error