flashing recovery, after root access, help please. - Hero CDMA Q&A, Help & Troubleshooting

i have two recovery images on my sdcard, and neither of them are flashing, i rooted using z4root. that was the only method i could find to root my phone after the weeklong search. ive recently had to re root because i got a refurb. either way they stuck me with .7 i updated to .2 because i could not root .7 got it rooted , yay, but now i am having the hardest time flasing a recovery image. i tried using rom manager to get clockworks but the download from the market would not download, so i put it on my sdcard and did it myself. so i have rom manager now, but it keeps telling me i need reliable connection, im on wifi and i have five bars. ive had no luck.
i pushed both the recovery images i have on my sd card, and i tried to flash them but it keeps telling me they cant find them.
kyle-markss-macbook:tools kylemarks$ ./adb shell
$ su
# flash_image recovery /sdcard/recovery-RA-heroc-v1.5.2.img
flash_image: not found
# flash_image recovery /sdcard/recovery.img
flash_image: not found
# kyle-markss-macbook:tools kylemarks$
is what im getting in my terminal. i need help. please.

i have two recovery images on my sdcard, and neither of them are flashing, i rooted using z4root. that was the only method i could find to root my phone after the weeklong search. ive recently had to re root because i got a refurb. either way they stuck me with .7 i updated to .2 because i could not root .7 got it rooted , yay, but now i am having the hardest time flasing a recovery image. i tried using rom manager to get clockworks but the download from the market would not download, so i put it on my sdcard and did it myself. so i have rom manager now, but it keeps telling me i need reliable connection, im on wifi and i have five bars. ive had no luck.
i pushed both the recovery images i have on my sd card, and i tried to flash them but it keeps telling me they cant find them.
kyle-markss-macbook:tools kylemarks$ ./adb shell
$ su
# flash_image recovery /sdcard/recovery-RA-heroc-v1.5.2.img
flash_image: not found
# flash_image recovery /sdcard/recovery.img
flash_image: not found
# kyle-markss-macbook:tools kylemarks$
is what im getting in my terminal. i need help. please.
Click to expand...
Click to collapse
If you haven't already checked it. Try making sure the recovery is named .img & not. img.img on your sd card
Edit also make sure the recovery img is not in any folder. As in just on your sd/card
Yea its me again. With the
Modified Hero

Just get rom manager from the market and install clockwork recovery from the app. It sounds like you dont have the binary for flash_image.
sent from a series of tubes.

il Duce said:
Just get rom manager from the market and install clockwork recovery from the app. It sounds like you dont have the binary for flash_image.
sent from a series of tubes.
Click to expand...
Click to collapse
i installed the rom manager from apk. the market wouldn't download it for some reason. but it wont let me install the recovery, it says i dont have a reliable signal, which i do.
laie1472 said:
If you haven't already checked it. Try making sure the recovery is named .img & not. img.img on your sd card
Edit also make sure the recovery img is not in any folder. As in just on your sd/card
Yea its me again. With the
Modified Hero
Click to expand...
Click to collapse
check, check and check.
i have two on the root of my sdcard named, recovery.img and the other one is recovery-RA-heroc-v1.5.2.img they are both the same file, i just used recovery.img as instructed in the old how to root by regaw, back when i knew what i was doing, ahaha.

Sent you a pm
Sent from my HTC Hero CDMA using XDA App

just a wild guess, but how about
flash_image recovery /mnt/sdcard/recovery-RA-heroc-v1.5.2.img
?

Related

No recovery screen after cyanogen recovery 1.4

hi i tried searching for this but couldnt really find anything on it. i tried updating to the cyanogen recovery.img 1.4 using terminal as the guide said here http://forum.xda-developers.com/showthread.php?t=533731, however now whenever i boot into recovery, the bootloader screen comes up instead. i have tried reflashing the recovery numerous times but the problem still persists. am i doing something wrong? any help would be great. thanks in advance
also i am rooted currently running JF 1.5 rom with latest radio and hard spl.
Put the recovery image on the SD card yourself. Get the file from here http://forum.xda-developers.com/showthread.php?t=523558
i have also tried that. once i placed the file on the sd card, i opened up terminal and typed in the command:
flash_image recovery /sdcard/cm-recovery-1.4.img
after i pressed enter nothing happend on screen, so i turned off the phone and tried to boot into recover, but the bootloader screen still appears. am i typing in the wrong command or something?
Do it again and this time wait for the # to appear again. Then type reboot and hold home button while it's booting. Should take you to Cyan's awesome recovery screen
Good luck
... Have you tried flashing it from fastboot like cyanogen recommended if you ran into any issues?
djosiah said:
i have also tried that. once i placed the file on the sd card, i opened up terminal and typed in the command:
flash_image recovery /sdcard/cm-recovery-1.4.img
after i pressed enter nothing happend on screen, so i turned off the phone and tried to boot into recover, but the bootloader screen still appears. am i typing in the wrong command or something?
Click to expand...
Click to collapse
After you open the terminal, did you type "su"?
billquinn1 said:
After you open the terminal, did you type "su"?
Click to expand...
Click to collapse
yeah i did type in su. i have been away for a few days so i ma going to try the suggestions mentioned. and no i havent tried doing it using fastboot as i havent got adb set up yet. i will also try that later. thanks for the suggestions.
I have the same problem. When holding power+home, it flashes t-mobile G1, then the screen disintegrates and it reboots a couple times, finally stopping on a blank black screen.
I have no problem booting straight into the O.S., I've just lost my recovery.
I've done this before and it worked, but I recently had a catastrophic failure and had to start from scratch.
If all else fails or you don't fell like using adb, should be fine if you downgrade and re-root, etc.... unless there is something else messing up your recovery partition.
Put the recovery.img file on the root of your sdcard
Then try:
Code:
mount -o remount,rw /dev/block/mtdblock3 /system
cd /system
cat /sdcard/recovery.img > recovery.img
flash_image recovery recovery.img
I've gone from JF 1.5ADP to Modaco using the cyanogen 1.4 recovery without any problems.
when you flash using terminal, you need to wait till you get the # back, and then restart the phone
which recovery image were you previously using as I was using JF 1.43 recovery
djosiah said:
hi i tried searching for this but couldnt really find anything on it. i tried updating to the cyanogen recovery.img 1.4 using terminal as the guide said here http://forum.xda-developers.com/showthread.php?t=533731, however now whenever i boot into recovery, the bootloader screen comes up instead. i have tried reflashing the recovery numerous times but the problem still persists. am i doing something wrong? any help would be great. thanks in advance
also i am rooted currently running JF 1.5 rom with latest radio and hard spl.
Click to expand...
Click to collapse
Hi djosiah
did you read this post ?
http://forum.xda-developers.com/showthread.php?p=4569666#post4569666
(Please substitude by the file name "update-cm-4.0.4-signed.zip" by "cm-recovery-1.4.img" in my post - sorry, I was misaken as to the file name ...!!)
My problem was a corrupted cm-recovery-1.4.img (a few thousand bytes of the MBs were missing ...!) A new downloaded cm-recovery-1.4.img (from another URL) solved the problem finally. The rest was cream - totally happy now.
Good luck!
My problem was solved.
Unroot the phone
reformat sd card using gparted live cd to fat32
redo root
flash new radio
flash new spl
flash cyanogen rom
flash cyanogen recovery
tada

biggest trouble ever installing 2.2

so back when i had 1.5 on my hero i had no problem at all installing roms. so when i updated to 2.1 stock awhile back i tried to root it and install a rom on it with the command prompt and unevoked method. it got it rooted and when i got to the recovery menu i nanidroid backedup and wiped and installed it. it then got stuck on the htc boot screen so i tried different rom and still would hang on it. so i said screw it and stayed on stock. i then later used the unlock univeral to root it but i can not stand the stock rom it is so slow and lags so i tried the offiical htc update from .6 to .7 to see if it would be faster but once it downloaded and i pressed install it would yet again hang on the htc screen. i cant even make calls with out lagging. so i tried once more to install 2.2 on it with a recovery img. i download rom manger and put froyo on the sd card but it would yet again hang when i click install rom from sd card. what do i do?!!!!!
update: i tried doing it through the teminal but it say flash_recovery not found
so i tried to do it through rom manger and it did the back up and installed it through the recovery menu but once it was done and rebooted it yet again is stuck on the htc boot screen.
help please!
It might b the recovery ur using if your able to boot into any rom access terminal you can get it from the market try to flash a different recovery I recommend. Darchstar RA 1.6 once u download it place it on the root of ur SD card not in any folders / then open up terminal and type su once the # appears type flash_image recovery /sdcard/ recovery- name of recovery. img wen that's done type reboot recovery and you should boot into recovery then try and flash ur rom from there hope this helps good luck
Root-Hack-Mod-Always™
laie1472 said:
It might b the recovery ur using if your able to boot into any rom access terminal you can get it from the market try to flash a different recovery I recommend. Darchstar RA 1.6 once u download it place it on the root of ur SD card not in any folders / then open up terminal and type su once the # appears type flash_image recovery /sdcard/ recovery- name of recovery. img wen that's done type reboot recovery and you should boot into recovery then try and flash ur rom from there hope this helps good luck
Root-Hack-Mod-Always™
Click to expand...
Click to collapse
ill try this when i get home tonite. thanks!
i tried doing it through the teminal but it say flash_recovery not found
so i tried to do it through rom manger and it did the back up and installed it through the recovery menu but once it was done and rebooted it yet again is stuck on the htc boot screen.
I recommend you boot into recovery - wipe your system / cache / dalvik cache and then flash the 2.2 rom of your choice -
if you were just flashing rom after rom without flashing then that could be a lot of your troubles -
also - you mentioned that the recovery file was not found on your sdcard - did you remember to unzip it first before attempting to flash it through terminal emulator? because it wont work otherwise ...
if you have extracted it to the root of your sdcard you shouldnt have any trouble
type
su
flash_image recovery /sdcard/nameofyourrecovery.img
reboot recovery
and you should be good to go - let me know how you do and we'll see if we can't help you further if needed
good luck!
cbwhat said:
i tried doing it through the teminal but it say flash_recovery not found
Click to expand...
Click to collapse
did you type:
su
flash_image recovery /sdcard/yourrecovery.img
or su
flash_recovery like your post shows - because you dont want to do it like that - just checking -
Vandelay007 said:
did you type:
su
flash_image recovery /sdcard/yourrecovery.img
or su
flash_recovery like your post shows - because you dont want to do it like that - just checking -
Click to expand...
Click to collapse
no it i type in
su
flash_image recovery /sdcard/recovery7.img
flash_image not found
cbwhat said:
no it i type in
su
flash_image recovery /sdcard/recovery7.img
flash_image not found
Click to expand...
Click to collapse
you said that you are doing this in a terminal window? (i am assuming that is on the phone) is your phone connected via usb to your computer? is the sdcard mounted by the computer? if it is unplug the usb and try again. if the computer has mounted the sdcard you can't access it from the phone.
i dont have it plugged in when i use the terminal on the phone
cbwhat said:
i dont have it plugged in when i use the terminal on the phone
Click to expand...
Click to collapse
ok just checking.... that was the only thing that i could think of that would stop you from reading the sdcard.
It may sound silly, bt when I do it I always make sure I account for case sensitivity...
Like flash_image recovery /sdcard/RA-Darchstar.img
Have you tried that?
Sent from my HERO200 using XDA App
yep make sure everything that has a capitals in it i capitalized in the terminal
this may sound silly as well.. sometimes when i use adb to push i mistype the location for example: adb push myfile.ext /adcard
everything goes fine until i go to find the file....
don't know though.
i still can't figure out how to install a custom rom.
Try backing up you sd and reformatting it on ur pc then just place the recovery img on your sd and nothing else then try to flash it good luck feel free to pm me I know how u feel man so if I can help I will good luck
Root-Hack-Mod-Always™

[HOWTO] get root back after ota update!

this is how i did it anyways. i had to flash the boot.img and update via stock recovery to get the ota to flash. but then no root!
so heres how i got it back:
download the superboot/paulobrien method (http://forum.xda-developers.com/showthread.php?t=882333).
boot phone to fastboot.
Code:
fastboot boot boot.superboot.img
let phone boot, open terminal, su, just to check.
reboot phone.
rooted and ota'd now!
I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
The method I used was:
1. Boot into fastboot.
2.
Code:
fastboot flash recovery recovery-clockwork-3.0.0.0-crespo.img
3. Reboot from fastboot directly into recovery (not doing so will cause android to replace CWR).
4. Mount USB, copy su-2.3.6.1-ef-signed.zip to the /sdcard via windows/linux
5. Mount /system
6. Install update from zip (browse to were you put su-2.3.6.1-ef-signed.zip).
7. Install it, and reboot.
8. open root explorer, and rename /etc/install-recovery.sh to install-recovery.sh.old
9. open ROM Manager, reflash CWR.
now you are all done, rooted, w/ CWR
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Luxferro said:
I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
Click to expand...
Click to collapse
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.
distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
im using stock recovery.
I'm rooted on 2.3.1 but I lose clockwork recovery when I reboot an gota reflash it using rom manager. Anyone having this problem
k0mpresd said:
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.
Click to expand...
Click to collapse
Sure it is. But on Android bootup, a script is running somewhere to replace it with stock recovery. They did this on Droid_1 after the first or second update (that's my only other android phone... so my android experience is limited).
edit: I just found the script. It's /etc/install-recovery.sh .... just renamed my to install-recovery.sh.old. gonna reflash CWR and test it now.
edit2: yep, works great now. CWR, and retained my 2.3.1 boot.img
So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone
chris6278 said:
So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone
Click to expand...
Click to collapse
No, it's a safety mechanism so you can't lose recovery... It has nothing to do with clockworkmod. Someone can make a root script or app that disables it easily. Or people can just do it themselves manually.
edit: actually, all that needs to be done is add some code to the update script inside su-2.3.6.1-ef-signed.zip so when it installs the update, it renames install-recovery.sh
distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks
If u dont mind can u please provide the instructions on how to do it manually. Id really appreciate it. Sorry im a noob lol
Where in root explorer do i need to rename
Where in root explorer do i rename it
plmiller0905 said:
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks
Click to expand...
Click to collapse
chmod needs to be done at a # prompt.
chris6278 said:
Where in root explorer do i rename it
Click to expand...
Click to collapse
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...
Is it just me or does adb remount no longer work?
If I use the old koush rootboot.img it works, but no wifi, if I use the stock boot.img, I get no wifi but am able to remount.
I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes
chris6278 said:
I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes
Click to expand...
Click to collapse
do you have root explorer? if not, it's just a file explorer that has root access. by default when you open it you are at /
you need to scroll down to /etc
go in that folder and find the install-recovery.sh
look up top for the button to turn it from read-only to read-write, click it
go back to the file long press it, and then choose rename.
Luxferro said:
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...
Click to expand...
Click to collapse
Thanks..I already rerooted but thanks anways
I got root explorer an followed ur directions an now everything works great. Thanx for ur help an sorry for being a pain lol

[Q] sprint hero recovery mode

hey guys right now im using darchstar's godspeed recovery.. but whats the most recommended recovery mode that everyone uses?
My personal favorite is Clockwork Mod Recovery. You can find the latest for our phone in the Andorid Development section, on the first page of the aospGBmod thread. Should be easy to find as it is right on top 99% of the time due to popularity.
DARCH All the way if your running GB then clockwork because I've read people have had problems with Darch's recovery with GB but if your running CM6 then stick with Darch
Root-Hack-Mod-Always™
laie1472 said:
DARCH All the way if your running GB then clockwork because I've read people have had problems with Darch's recovery with GB but if your running CM6 then stick with Darch
Root-Hack-Mod-Always™
Click to expand...
Click to collapse
Anyone Have The Apk. Or Zip File For Darch's Recovery?
Sent from my HERO200 using XDA App
PMGRANDS said:
Anyone Have The Apk. Or Zip File For Darch's Recovery?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I got it off of darch's website but it's been down as far as I know for a little while now.. Luckily I backed it up on my dropbox when I first downloaded it
I attached it so it'll be on XDA for everyone
Download the Darchstar_ra.zip and extract it onto the root of your sdcard.
Boot up into your rom
Open up terminal emulator and enter the following:
Code:
su
flash_image recovery /sdcard/darchdroid_ra.img
reboot
2 questions will this restore previous RA nandroids and also can this do the complete wipe like clockwork?
kyouko said:
I got it off of darch's website but it's been down as far as I know for a little while now.. Luckily I backed it up on my dropbox when I first downloaded it
I attached it so it'll be on XDA for everyone
Download the Darchstar_ra.zip and extract it onto the root of your sdcard.
Boot up into your rom
Open up terminal emulator and enter the following:
Code:
su
flash_image recovery /sdcard/RA-Darchstar.img
reboot
Click to expand...
Click to collapse
sent from my twopointtwo themed hero
thoughtlesskyle said:
2 questions will this restore previous RA nandroids and also can this do the complete wipe like clockwork?
sent from my twopointtwo themed hero
Click to expand...
Click to collapse
I don't see why it would have problems restoring older nandroids, I've never had problems after updating.
And yes, you can wipe data/cache, cache, davlik-cache, battery stats, and rotation settings in the wipe menu.
I currently use ClockworkMod Recovery 2.5.0.1 for recovery mode.
Specs of my Sprint HTC Hero/APA6277 are...
Android version: AOSP
Baseband version 2.42.02.10.29,
Kernel version 2.6.29.6-aospMD [email protected] #1
Mode version: aospMOD-0.9.9.2
Build number: FRG83
I plan on flashing the AOSP GB Mod to my device as soon as a stable version of it becomes available.
kyouko said:
I don't see why it would have problems restoring older nandroids, I've never had problems after updating.
And yes, you can wipe data/cache, cache, davlik-cache, battery stats, and rotation settings in the wipe menu.
Click to expand...
Click to collapse
have you had any issues with wiping and flashing gingerbread because i didnt at first but lately it seems like its not a full wipe, then again im using a really old version of RA
kyouko said:
I got it off of darch's website but it's been down as far as I know for a little while now.. Luckily I backed it up on my dropbox when I first downloaded it
I attached it so it'll be on XDA for everyone
Download the Darchstar_ra.zip and extract it onto the root of your sdcard.
Boot up into your rom
Open up terminal emulator and enter the following:
Code:
su
flash_image recovery /sdcard/RA-Darchstar.img
reboot
Click to expand...
Click to collapse
Thanx A lot Kyouko!!
I Downloaded It....
But I Wanted To Pick Your Brain A Bit, Before I Flashed It.... Lol!
As I'm Sure You Know,
*Rom Manager* Has The Option "Flash Alternate Recovery" Which Switches The Users Recovery From Clockwork, To Amon_Ra, Right?
So I Guess My Question To You Is, What's The Difference Between This Recovery & The Other Two?
Is There More Features??
Oh, One More Thing.... Sorry!!
I Have A **** Load Of Backups From *Rom Manager* Will The Still Be Compatible, Since I Made'em With Clockwork?
Sent from my HERO200 using XDA App
thoughtlesskyle said:
have you had any issues with wiping and flashing gingerbread because i didnt at first but lately it seems like its not a full wipe, then again im using a really old version of RA
Click to expand...
Click to collapse
That issue was fixed in the newer RA versions (which includes this one and godspeed)
There was a problem wiping with the older RA after the cache location got moved in newer rom versions or something along those lines
PMGRANDS said:
As I'm Sure You Know,
*Rom Manager* Has The Option "Flash Alternate Recovery" Which Switches The Users Recovery From Clockwork, To Amon_Ra, Right?
So I Guess My Question To You Is, What's The Difference Between This Recovery & The Other Two?
Is There More Features??
Oh, One More Thing.... Sorry!!
I Have A **** Load Of Backups From *Rom Manager* Will The Still Be Compatible, Since I Made'em With Clockwork?
Click to expand...
Click to collapse
I'm not sure what the "flash alternate recovery" does because I only tried clockwork once and flashed over the recovery using terminal
As for features I took screens of each menu on the recovery
And I don't know what kind of backups rom manager does. If they're structured like nandroids it might work You may have to create a folder named "nandroid" and inside that folder create another and throw the backups in there. It'd be structured something like this:
/sdcard/nandroid/oldbackups/*folders go here*
And worst case scenario if they don't work but you really want all of them back you can just flash clockwork back to restore them.
kyouko said:
That issue was fixed in the newer RA versions (which includes this one and godspeed)
There was a problem wiping with the older RA after the cache location got moved in newer rom versions or something along those lines
I'm not sure what the "flash alternate recovery" does because I only tried clockwork once and flashed over the recovery using terminal
As for features I took screens of each menu on the recovery
And I don't know what kind of backups rom manager does. If they're structured like nandroids it might work You may have to create a folder named "nandroid" and inside that folder create another and throw the backups in there. It'd be structured something like this:
/sdcard/nandroid/oldbackups/*folders go here*
And worst case scenario if they don't work but you really want all of them back you can just flash clockwork back to restore them.
Click to expand...
Click to collapse
Darch's Recovery is an overclocked version of AmonRa with EXT4 Support. See here for more info
kyouko said:
That issue was fixed in the newer RA versions (which includes this one and godspeed)
There was a problem wiping with the older RA after the cache location got moved in newer rom versions or something along those lines
I'm not sure what the "flash alternate recovery" does because I only tried clockwork once and flashed over the recovery using terminal
As for features I took screens of each menu on the recovery
And I don't know what kind of backups rom manager does. If they're structured like nandroids it might work You may have to create a folder named "nandroid" and inside that folder create another and throw the backups in there. It'd be structured something like this:
/sdcard/nandroid/oldbackups/*folders go here*
And worst case scenario if they don't work but you really want all of them back you can just flash clockwork back to restore them.
Click to expand...
Click to collapse
Thanx For The Screenshots,
Now I'm Curious! And I Already Like The Way It Looks Better Than Clockwork! But To Be Honest Im A Little Nervous About Using ADB. Or Terminal Emulator!
Is It Easy/Hard?
I Heard You Can Brick Your Phone If You Enter A Command Wrong, Is That True?
Sent from my HERO200 using XDA App
PMGRANDS said:
Thanx For The Screenshots,
Now I'm Curious! And I Already Like The Way It Looks Better Than Clockwork! But To Be Honest Im A Little Nervous About Using ADB. Or Terminal Emulator!
Is It Easy/Hard?
I Heard You Can Brick Your Phone If You Enter A Command Wrong, Is That True?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
As long as you don't put "flash_image (BOOT or any other partition here)" you should be fine.
If you input it incorrectly it won't flash,
example: flashimage recovery /sdcard/darchdroid_ra.img
How to flash it via ADB:
Code:
adb shell
su
flash_image recovery /sdcard/darchdroid_ra.img
reboot
kyouko said:
As long as you don't put "flash_image (BOOT or any other partition here)" you should be fine.
If you input it incorrectly it won't flash,
example: flashimage recovery /sdcard/darchdroid_ra.img
How to flash it via ADB:
Code:
adb shell
su
flash_image recovery /sdcard/darchdroid_ra.img
reboot
Click to expand...
Click to collapse
followed the code lines for terminal emu and adb both times got Flash_img: not found even tried entering Darchstar_ra.img same error
thoughtlesskyle said:
followed the code lines for terminal emu and adb both times got Flash_img: not found even tried entering Darchstar_ra.img same error
Click to expand...
Click to collapse
Weird.. Do this for me, open up terminal emulator and type:
Code:
su
flash_image
you should get a return line saying:
Code:
usage: flash_image partition file.img
*see attached picture for example*
Make sure you're inputing it exactly the way I had it in the previous post - underscores and all. If the recovery.img name is different make sure whatever you type is exactly what the img is called.
If it's not in the /sdcard/ directory enter the correct one.
Example) /sdcard/downloads/oldrecovery.img
On my second attached picture you can see that the command worked, but since I already have that recovery flashed it aborts.
thoughtlesskyle said:
have you had any issues with wiping and flashing gingerbread because i didnt at first but lately it seems like its not a full wipe, then again im using a really old version of RA
Click to expand...
Click to collapse
I'd just use CW for Gingerbread, RA doesn't wipe boot or system I believe.
Does anyone know if you are able to Wipe Data/cache/dalvik from adb shell?
just making a script to automate the process.
anyone know the commands?
thanks

corrupted recovery

I have HTC Hero CDMA obviously lol
but anyways i have the latest HBOOT without S-OFF and i have a corrupt recovery i have tried restoring with the latest offical RUU with no luck as i get the 170 usb error connection error
Why not just reflash your recovery ???
#Root-Hack\Mod*Always_
""Shooter on Deck""
i try to with rom manager and i get an error
any othere method other than hboot as i dont have s-off and need a recovery to get that
omg i can not find any way to get a working recovery with out S-OFF *RAGE FACE*
evoandroidevo said:
i try to with rom manager and i get an error
any othere method other than hboot as i dont have s-off and need a recovery to get that
omg i can not find any way to get a working recovery with out S-OFF *RAGE FACE*
Click to expand...
Click to collapse
Go to my signature and click on the CWM link. Then unzip a version and place the recovery.img on the root of your SD card. Now download Busybox installer, and terminal emulator. Install busybox and after installing open terminal emulator and then enter these commands:
Code:
$ su
# flash_image recovery /sdcard/recovery.img
私のEVO 3Dから送信される。
i did all that installed busybox and all that stuff and i always get flash_image not found or something like that
EDIT:
Got it to work jsut need to go to 2.27.651.5 instead of 2.27.651.6
I seem to be having nearly this exact same problem. Maybe If I can flash a recovery to my hero I wont need to create a thread of my own asking for help.
What did you mean by "need to go to 2.27.651.5 instead of 2.27.651.6"?
I have root... or at least the "su" command in terminal gives me a #. I have placed the recovery image on the root directory of my sd just as dastin said and run the command but I am getting the flash_image not found error.
That's the RUU version.
Sent from my PG86100 using xda premium
Okay. Maybe my issue is not so similar after all.
I have stock that has been rooted. That is as far as I got. There were countless problems during the rooting process but I have achieved the # in the terminal. This means it's rooted right?
At this point I think I just need to flash a recovery and for some reason I can't install "ROM manager" as I get a "Parse error" when running the .apk. So I thought this manual method would solve my issues.
Maybe I should start my own thread. This might get complicated.
Jacob_newton said:
Okay. Maybe my issue is not so similar after all.
I have stock that has been rooted. That is as far as I got. There were countless problems during the rooting process but I have achieved the # in the terminal. This means it's rooted right?
At this point I think I just need to flash a recovery and for some reason I can't install "ROM manager" as I get a "Parse error" when running the .apk. So I thought this manual method would solve my issues.
Maybe I should start my own thread. This might get complicated.
Click to expand...
Click to collapse
Install busybox.
私のEVO 3Dから送信される。
busybox says my device is rooted.
busybox location: /system/xbin v.119.3.
I still get that same not found error.
Jacob_newton said:
busybox says my device is rooted.
busybox location: /system/xbin v.119.3.
I still get that same not found error.
Click to expand...
Click to collapse
Why not just flash the recovery ??? From terminal,hooot, or adb.
#Root-Hack\Mod*Always_
""Shooter on Deck""
If I use the command prompt and enter:
cd ...\android-sdk\platform-tools
adb shell
# flash_image
I still get "flash_image: not found" it's as if it's missing the command. It's the same error if I tell it where to get the .img from
edit: this is the exact same when I do it from terminal and i have no idea what hooot is.
Jacob_newton said:
If I use the command prompt and enter:
cd ...\android-sdk\platform-tools
adb shell
# flash_image
I still get "flash_image: not found" it's as if it's missing the command. It's the same error if I tell it where to get the .img from
edit: this is the exact same when I do it from terminal and i have no idea what hooot is.
Click to expand...
Click to collapse
Were did you place the recovery img at ??
#Root-Hack\Mod*Always_
""Shooter on Deck""
The image file is on the root directory of my sd card.
I'm not sure but it seems like the "flash_image" command just doesn't work. If I type "flash_image" and hit enter, it gives the same error as if I type "dead_bears".
dead_bears: not found
I don't think this has anything to do with my image file. I think something is wrong with the command.
Jacob_newton said:
The image file is on the root directory of my sd card.
I'm not sure but it seems like the "flash_image" command just doesn't work. If I type "flash_image" and hit enter, it gives the same error as if I type "dead_bears".
dead_bears: not found
I don't think this has anything to do with my image file. I think something is wrong with the command.
Click to expand...
Click to collapse
Let me ask you this are you trying to flash this from terminal or from adb ?? If there isn't a copy of the recovery img in your adb tools folder then trying to flash it threw adb wouldn't take because the image isn't there. Since the img is on your SD card then you should flash it threw terminal if your not trying it already. If you want to flash it threw adb then place a copy of the recovery img in your adb tools folder and then run the commands from cmd terminal VIA pc/laptop. Also have you made sure that the recovery img is named correctly ?? Also will you post your setup, as in rom,kernel,baseband/radio, and hboot. Also how did you obtain root ??? Thanks
#Root_Hack-Mod*Always\
I am using the terminal and I have tried ADB as well. Both do the exact same thing. I obtained root manually but I had so many problems that don't remember where the guide that I followed is. I named the recovery image "r.img" for ease of typing.
I don't know about rom,kernel,baseband/radio, and hboot. I flashed stock to the phone after purchasing it so that I could get it activated, so these things are likely at defaults.
I still don't think that the "flash_image: not found" error has anything to do with the image file itself.
Jacob_newton said:
I am using the terminal and I have tried ADB as well. Both do the exact same thing. I obtained root manually but I had so many problems that don't remember where the guide that I followed is. I named the recovery image "r.img" for ease of typing.
I don't know about rom,kernel,baseband/radio, and hboot. I flashed stock to the phone after purchasing it so that I could get it activated, so these things are likely at defaults.
I still don't think that the "flash_image: not found" error has anything to do with the image file itself.
I think you should ruu back to stock and reroot again. Reason why I suggest this is because of how you gained root. If something wasn't done correctly we could be at this for hours and days trying to figure this out. But before you take that route I'll send you a pm with something I would like you to try that might work.
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
Jacob_newton said:
I am using the terminal and I have tried ADB as well. Both do the exact same thing. I obtained root manually but I had so many problems that don't remember where the guide that I followed is. I named the recovery image "r.img" for ease of typing.
I don't know about rom,kernel,baseband/radio, and hboot. I flashed stock to the phone after purchasing it so that I could get it activated, so these things are likely at defaults.
I still don't think that the "flash_image: not found" error has anything to do with the image file itself.
Click to expand...
Click to collapse
Quick??? Are you able to boot up into your Rom ???
#Root-Hack_Mod*Always\
I'm not sure what you mean by that, but I decided to flash stock the other night so now I'm going to try and re-root and flash a custom ROM.
I am considering this method for re-rooting: http://forum.xda-developers.com/showthread.php?t=909258&highlight=root
Any suggestions before I get started?
What I meant by have to be on the 2.27.651.5 RUU instead of 2.27.651.6 RUU as the flash_image is not in thr 2.27.651.6 RUU so you need to be on the 5 version of stock in order to use flash_image
Sent from my Shooter using XDA

Categories

Resources