[Q] Flash_Image?? - Hero CDMA Q&A, Help & Troubleshooting

Okay so I have recently rooted my HTC Hero and would like to flash a custom ROM, but I am getting held up in ADB when trying to flash_image my custom recovery.
I have tried to put the Flash_Image file in the root of my SD Card, in my ADB folder, etc.... But nothing has worked so far.
Here is what I am doing, with the outcomes.
C:\Program Files\Android\Android-sdk\Platform-tools\>adb shell
$ su
# flash_image recovery /sdcard/CWRecovery.img
flash_image: not found
# ./flash_image recovery /sdcard/CWRecovery.img
flash_image: not found
Also I have adb pushed all the files required, and shortened the CWM Recovery image to 'CWRecovery.img' so I don't have to type as much lol.
My phone is rooted successfully, have installed BusyBox, SU, etc. So I don't know where the problem is coming from, but if anyone with any information could help, it would be greatly appreciated!

I couldn't tell you what is wrong with it, but have you tried using a terminal emulator on your phone to get it done? From there I'd just
$ su
#flash_image recovery /sdcard/CWRecovery.img
like you've done in adb.

I have tried doing it through Terminal Emulator.. But after trying for about 3 days, I have come up with something. Apparently in the 2.27.651.6 update there is no flash_image. So I had to downgrade to 2.27.651.5.
So I followed this guide http://forum.xda-developers.com/showthread.php?t=694572
Thanks to regaw_leinad for posting that!

Ah, now you've refreshed my memory. I actually had trouble with rooting my phone because mine was at 2.27.651.6 as well. I tried a bunch of the one-click methods and stuff, and they weren't compatible with it... Glad it worked out.

I think if you install busybox (via the Busybox installer app), that'll give you the flash_image executable on your phone. You shouldn't have to downgrade anything to get that functionality.

Not around my laptop atm but I believe Windows has two Android folders. One named "android-sdk-windows" and the other "AndroidSDK" . Have you checked to make sure you put the recovery.img into the "AndroidSDK" folder and not the
"android-sdk-windows" folder???
Also have you checked to make sure both img's are named exactly alike??
#Root-Hack_Mod*Always\

Thank you for the responses fellas, I tried to install BusyBox by downloading the App on the Market, and it said that BusyBox was already installed and asked if I would like to remove it or install over it, tried both options and still nothing. Tried re RUU-ing with .6 and doing z4Root, SuperOneClick, and tried RegrawMOD. Still could not access the flash_image.

Yeah, when I tried to root mine I also tried z4Root, SuperOneClick, andRegrawMOD, none of which worked for me either. I really didn't want to do the whole command line thing, but that's what I ended up having to do. This is the guide I used for root:
http://wiki.cyanogenmod.com/index.php?title=HTC_Hero_(CDMA):_Full_Update_Guide
I followed the directions in step one to install the SDK, then completed the rest of them. It actually wasn't as bad as I thought it would be, and after that I was able to flash a recovery.

Use Rom Manager from the market to flash a recovery
Sent from my HERO200 using XDA

Related

Problem with one click root method and me lol

Hey all. I upgraded to froyo 2.2 manually on my droid x a couple weeks ago and then used the one click root method for root. i downloaded several programs that required root and used them successfully. but these programs suddenly stopped working. set cpu for instance says it cant get root and i installed clockwork to try some of the mods out there and none of the commands in that program work (like i cant boot into clockwork recovery or install a rom). I've also tried unrooting it using the same program i rooted it with and THAT doesnt work. Does anyone have any suggestions? Thanks in advance for the help.
arstinince said:
Hey all. I upgraded to froyo 2.2 manually on my droid x a couple weeks ago and then used the one click root method for root. i downloaded several programs that required root and used them successfully. but these programs suddenly stopped working. set cpu for instance says it cant get root and i installed clockwork to try some of the mods out there and none of the commands in that program work (like i cant boot into clockwork recovery or install a rom). I've also tried unrooting it using the same program i rooted it with and THAT doesnt work. Does anyone have any suggestions? Thanks in advance for the help.
Click to expand...
Click to collapse
Well I am not sure how you got it to work but the one click method doesn't work on 2.2. There is a manual root method found below with the files you need to do it manually.
http://destdroid.com/showthread.php?11-Droid-X-2.2-Root-Manual-Method
Sent from my DROIDX using XDA App
most likely its in xbin instead of bin; so u have to move it.
1. adb shell
2. system/xbin/su
3. mount -o rw,remount /dev/block/system /system
4. cp /system/xbin/su /system/bin/su
5. chmod 4755 /system/bin/su"
6. ls /system/bin/su" (make sure the results are "/system/bin/su" and NOT "/system/xbin/su" - If you see this, repeat the previous step.)
7.exit
8.exit
9.adb reboot
thanks guys. i rooted it before upgrading actually. just after the upgrade it seemed to have problems. i will try these things and let you know how it works out. thanks again!

[Q] Problems rooting

I'm trying to root my Sprint Hero by following these directions: http://forum.xda-developers.com/showthread.php?t=694572 and when I get to typing in "sh /sdcard/unrevoked" I get the following error message -
$ sh /sdcard/unrevoked
sh /sdcard/unrevoked
Unpacking, please wait...
Unable to chmod /data/DxDrm/unrevoked.13740: No such file or directory
/sdcard/unrevoked: /data/DxDrm/unrevoked.13740: not found
rm failed for /data/DxDrm/unrevoked.13740, No such file or directory
$
Am I missing a step. Please help!!
Can't help you with that particular error, but try http://forum.xda-developers.com/showthread.php?t=804296
That's been proven to work.
That worked, thanks!
Nothing Works
Above solution doesnt work on HTC Hero bu Sprint...
I installed the SDK as suggested..
There is no adb installed part of SDK. Whoever wrote these instructions probably wrote last year.
'adb' is not recognized as an internal or external command.....
In the recent release of Android SDK, adb was moved to the "platform-tools" of your android sdk's installation folder. Check it there and run as instructed... it should work.
I used z4root and it worked fine
Yes z4root still works on the latest software
Sent from my HTC Hero CDMA using XDA App
211655 said:
Above solution doesnt work on HTC Hero bu Sprint...
I installed the SDK as suggested..
There is no adb installed part of SDK. Whoever wrote these instructions probably wrote last year.
'adb' is not recognized as an internal or external command.....
Click to expand...
Click to collapse
Once you have the SDK installed you have to update it. Once you have the update installed instead of going into the /tools directory, you need to go into /platform-tools/ and adb is located there. Other than the directory changes the proceedure is the same. You can also look for Z4root, it is supposed to root the hero, from there you can install rom manager and install clockworkmod recovery.

One click root after update: "We have root, but couldn't push busybox. Not sure why!"

One click root after update: "We have root, but couldn't push busybox. Not sure why!"
I just updated .890 which seemed to go fine with no errors (unfroze all bloat, but did not unroot), but I lost root, as expected.. but when I use Pete's one-click root tool (latest version), it gets to step 3 and gives me the error about not being able to push busybox...!? It says I "have root", but none of my apps recognize it.. I've pulled the battery, rebooted and retried like 10 times... still can't get it to re-root. I've made sure Debugging and Unknown Sources is enabled and tried in Charge Mode and Mass Storage mode... Am I going to have to stock flash this thing and re-update & re-root?
I THINK I have some type of root.. maybe... because Root Explorer will let me mount the System directory as R/W and I can TRY to manipulate files, but if I delete something (like su), it appears to delete successfully, but the file comes back if I refresh the directory.. but I also noticed when I go into the System directory, Root Explorer claims I only have 1MB of free space out of 318.00MB... how did that happen? If I try to run Superuser.apk, it force closes on me.
Any help or ideas are greatly appreciated...
there's an app on the android market that will push busybox if you have root. I'd look into that
edit: have you attempted to run the one-click root again? and if that doesn't work you can try to use the adb method if you're comfortable with it. And make sure that all of your drivers and everything are up-to-date
I have done battery pulls and like a dozen+ re-tries at the 1-click root, always get the same error.. I have been into the ADB shell to try and figure this out and I see the ADB Shell starts out by giving me a # prompt... that means writable/root, right? Any instructions on what I have to do from there?
I will look into that push busybox app, thanks.
http://wiki.rootzwiki.com/index.php/Motorola_Droid_3
This is where all the info about the adb and one-click stuff. The tough part about the adb method is manually pushing su to the (i think) system/xbin folder. Then i just used the app on the marketplace to push busybox. But there's a download link for both of those on the website
Thanks for the links. I think a problem with my ADB is when I reboot it (step 3), I no longer have a # prompt.. it goes back to the $ prompt... the only way I can seem to get the # prompt in ADB is when I use Pete's temporary ADB root... but once I reboot, that goes away. When I try to do step 4, rm /data/local/12m, it says it's a directory and it's not empty and it won't remove it. :\
How do I normally make ADB give me that # prompt so I can write/edit? or am I totally off-base here?..
*edit* I am going to try and do Pete's temp ADB root again and just try steps 18+ and see if that gets me anywhere...
Kraxis said:
Thanks for the links. I think a problem with my ADB is when I reboot it (step 3), I no longer have a # prompt.. it goes back to the $ prompt... the only way I can seem to get the # prompt in ADB is when I use Pete's temporary ADB root... but once I reboot, that goes away. When I try to do step 4, rm /data/local/12m, it says it's a directory and it's not empty and it won't remove it. :\
How do I normally make ADB give me that # prompt so I can write/edit? or am I totally off-base here?..
*edit* I am going to try and do Pete's temp ADB root again and just try steps 18+ and see if that gets me anywhere...
Click to expand...
Click to collapse
After temp ADB root, steps 18 and beyond should do it. You may want to check /system/bin and /system/xbin to remove the old su binaries before pushing the new one. Some folks have one in each location for some reason. Put it in xbin, but if it doesn't work, /system/bin will. Superuser wouldn't recognize xbin for me so I moved it to /system/bin and i'm good since.
Anyone have a thought on the xbin not always working? I think this is the 3rd topic i've seen with this issue, not including myself.
Sent from my DROID3 using XDA App
OK, I got root back! I used steps 18+ for "ADB Method" (after using Pete's temp ADB root) and essentially replaced SU and Superuser.apk, CHMOD'd it rebooted and I had root! Thanks guys!!

HELP!!!! trying Install CWM on zv8

Ok so here it is almost day 2 trying to install CWM on zv8 after using "mt's easiest way to keep root thru zv8'. (Oh and by the way MT your the MAN). Now getting to zv8 was easy, But getting the recovery installed is another issue all together. First started with the AIO bat. file which installs cwm (kudos to MT and djrbliss). And it reads
"system cannot find the path specified'.
SO ok well apparently the computer isnt reading the phone found out the driver has issue shows the error message(on both my laptops).
ok lets try the terminal emulator with
brad6360 said:
1) Download the cwmrecovery.img to your SD. ( I downloaded MT's zip file and then extracted all with root explorer, but you only need the cwmrecovery.img file.)
2) Use root explorer to copy or move it to the /data/local/tmp directory (make sure permissions are set to r/w/exe).
3) Launch terminal emulator and type these commands:
su
mount -orw,remount /dev/block/system /system
mount -orw,remount /dev/block/data /data
dd if=/data/local/tmp/cwmrecovery.img of=/dev/block/mmcblk0p14 bs=4096
rm /data/local/tmp/* 2>/dev/null
4) exit terminal emulator and then reboot.
You can then try the vol down+power button combo upon boot to enter CWM.
Good luck.
Click to expand...
Click to collapse
didn't work and I the local.prop file in the data folder.
Someone PLEASE HELP!!!
(not a noob or expert but I can read and follow directions lol)
Are you sure you still have root level access?
Does adb detect your phone at all?
Still have root access I used root explorer to add the local.prop.
Adb recognizes my phone it shows a serial number under adb devices
Is there a way I can flash cwm in adb?
Sent from my VS910 4G using XDA
Use the newest aio from Mt. It worked for me. The simplest way is to flash the v7.tot then 'JUST' root, create the local.prop file, then ota to v8. Then continue on with Mt's aio to install cwm. Don't worry about having complete root access (cuz I didn't, but had cwm). Flashed broken out and haven't looked back.
--My REVO is Broken, tweaked, SC'd, and TB'd. Just awesome!
Thats where I'm stuck. I'm on zv8, using mt's easiest AIO to update from zv7. The AIO for cwm isn't installing nor through the terminal emulator. Any other suggestions?
Sent from my VS910 4G using XDA
What happens when you go into recovery? Is it the stock recovery? Stock v8 didn't have the option to boot into recovery. Just a thought. When I did it I got a lot of errors, but it took.
--My REVO is Broken, tweaked, SC'd, and TB'd. Just awesome!
mrand1 said:
Thats where I'm stuck. I'm on zv8, using mt's easiest AIO to update from zv7. The AIO for cwm isn't installing nor through the terminal emulator. Any other suggestions?
Sent from my VS910 4G using XDA
Click to expand...
Click to collapse
I have the same problem, Even when i Flash zv7 tot and try old AIO it says
Cannot find specified path
and i am not a noob and have broken out an old revo with mt's help but this new one with pre loaded zv8...No luck yet
had to manually push
I'm glad that I'm not the only one having this issue
Can you use Root Explorer to check and make sure adb is pushing the image file to your phone? Look in this directory: /data/local/tmp/cwmrecovery.img
You could always do this manually using adb. Here's how.
1. Open the ZV8CWMRecovery folder on your PC.
2. Double click the 'Files' folder to go into that directory.
3. Highlight/select and copy the address of your current folder location on your PC. It will look something like this:
Code:
C:\Documents and Settings\username\My Documents\Downloads\ZV8CWMRecovery\Files
4. Click Start>Run>type 'cmd' and hit enter/return to open your command prompt.
5. Type 'cd', hit your spacebar, then paste your address which you copied in step 3 into your command prompt, hit enter/return.
6. You should now be positioned in the folder containing the adb and CWMRecovery files.
7. Type the following to copy the CWMRecovery image to your phone:
Code:
adb devices
adb remount
adb push cwmrecovery.img /data/local/tmp/cwmrecovery.img
adb shell dd if=/data/local/tmp/cwmrecovery.img of=/dev/block/mmcblk0p14 bs=4096
adb shell "rm /data/local/tmp/* 2>/dev/null"
adb shell rm /system/etc/install-recovery.sh
adb shell rm /system/recovery-from-boot.p
adb shell rm /data/local.prop
adb reboot
Phone should reboot. Try and boot into CWMRecovery after it reboots.
idk if I'm not doing something right or wrong. I have usb debugging and internet connection, and I'm getting "remount failed: operation not permitted".
I had the same issue but following these instructions helped me, what finally helped me was typing a wrong command wich gave me a help menu with all the commands, the important one being "adb reboot [Recovery:Bootlaoder]"
adb reboot recovery did the trick, then wiped flashed broken out and sooo happy to be done with it.
after pushing CWM in command prompt of course
I'm also getting "remount failed: operation not permitted" when trying adb remount in the command prompt just as mrand1 apparently did.
I (perhaps noobishly) skipped that step and did adb push cwmrecovery.img /data/local/tmp/cwmrecovery.img but after trying the next step got cannot open for write: Permission denied.
I'm trying to get back to Broken Out 1.1 - when it first came out I successfully downgraded to zv7 by flashing the .tot and then doing the OTA update, but now when I try to do that I can't seem to get the OTA to start downloading. I flashed zv8 tot in order to test the latest root method (which works) I just can't get CWM on there now - I don't seem to have any recovery at all actually. Any help would be appreciated.
slimzim said:
I'm also getting "remount failed: operation not permitted" when trying adb remount in the command prompt just as mrand1 apparently did.
I (perhaps noobishly) skipped that step and did adb push cwmrecovery.img /data/local/tmp/cwmrecovery.img but after trying the next step got cannot open for write: Permission denied.
I'm trying to get back to Broken Out 1.1 - when it first came out I successfully downgraded to zv7 by flashing the .tot and then doing the OTA update, but now when I try to do that I can't seem to get the OTA to start downloading. I flashed zv8 tot in order to test the latest root method (which works) I just can't get CWM on there now - I don't seem to have any recovery at all actually. Any help would be appreciated.
Click to expand...
Click to collapse
I did the same thing, flashed to zv8 tot, was able to root but was unable to flash cwm recovery. I tried manually doing it and running MT's AIO. It's telling me permission denied on all of the steps except the push cwmrecovery.img. It appears I do not have any recovery either. Trying to get to Broken Out! Any help is appreciated, thanks guys!
asauber said:
I tried ... running MT's AIO. It's telling me permission denied on all of the steps except the push cwmrecovery.img.
Click to expand...
Click to collapse
For what it's worth I also tried that with the same results.
I finally got this to work much more easily thanks to a quick talk with mtmichaelson. Here's the method:
1) Get to ZV8 (I got there via LGNPST)
2) Root using the tool found here: http://forum.xda-developers.com/showthread.php?t=1621625
3) Open a Terminal Emulator
4) Type: su
5) Hit enter
6) Type: echo 'ro.kernel.qemu=1' > /data/local.prop
7) Press enter
8) Reboot
9) Use the ZV8CWMRecovery.bat found here: http://forum.xda-developers.com/showthread.php?t=1583023
Good luck!
slimzim said:
I finally got this to work much more easily thanks to a quick talk with mtmichaelson. Here's the method:
1) Get to ZV8 (I got there via LGNPST)
2) Root using the tool found here: http://forum.xda-developers.com/showthread.php?t=1621625
3) Open a Terminal Emulator
4) Type: su
5) Hit enter
6) Type: echo 'ro.kernel.qemu=1' > /data/local.prop
7) Press enter
8) Reboot
9) Use the ZV8CWMRecovery.bat found here: http://forum.xda-developers.com/showthread.php?t=1583023
Good luck!
Click to expand...
Click to collapse
Man, that was too easy!
Thanks for posting this slimzim. This worked straight away for me, I'm installing Broken Out as I type! I'm actually a little glad this happened because now I'm a little more familiar with terminal emulator and what local.prop does. Never had to use it in the past. This is exactly the second phone I've ever rooted and am usually able to just use AIOs.
And of course, thanks to mtmichaelson for chatting with you about it and doing all the hard work in the first place!
slimzim said:
I finally got this to work much more easily thanks to a quick talk with mtmichaelson. Here's the method:
1) Get to ZV8 (I got there via LGNPST)
2) Root using the tool found here: http://forum.xda-developers.com/showthread.php?t=1621625
3) Open a Terminal Emulator
4) Type: su
5) Hit enter
6) Type: echo 'ro.kernel.qemu=1' > /data/local.prop
7) Press enter
8) Reboot
9) Use the ZV8CWMRecovery.bat found here: http://forum.xda-developers.com/showthread.php?t=1583023
Good luck!
Click to expand...
Click to collapse
So far not working...repeating process now...
da_morales said:
So far not working...repeating process now...
Click to expand...
Click to collapse
If you've done all steps exactly it should work. I went through a ton of other "fixes" that didn't work, I believe the key here is when you use the terminal emulator directly on the phone to create local.prop. I was trying to create local.prop in every way but that, and until I did it directly on the phone did I have success.
Good luck!
local.prop missing
I used the Easy ZV8 All in One Rooting Tool, and have no sound at all like a couple of other users. One of the suggestions was to rename the local.prop file in the /data folder to local.prop.bak.
I assume this is the /data folder in the internal folder? When I did the steps for the all in one rooting tool (coming from rooted zv7), there is no local.prop file in my /data folder to rename, yet I still have no audio for ringtones, phone calls, etc. except for the boot up sound on the splash page.
Any ideas why my local.prop file isn't even there? I even tried copying the one from the mtmichelson zip file into there, still no avail. Thanks!
I have the same issue. I used the echo command in term emulator and the local.prop file was there. rebooted and the file is gone. I have root but cannot install cw recovery. I have tried AIO, adb, and terminal emulator but nothing makes it stick. Any help would be greatly appreciated
Rob

Can't root my S5830 2.3.6 - tried everything.

Yesterday I installed Windows XP on my PC, cause I couldn't install phone drivers on 8.1. I downloaded Odin for S5830 and flashed a Polish 2.3.6 ROM (from updato.com) over the existing 2.1. Next I flashed 5.0.2.6 fix CWM. Then I realized, that to root my phone I need to have a stock recovery, so I flashed it and then rooted with root.zip. I ran the phone to look if there's a superuser app and there was, so I flashed the CWM back. When I wanted to upgrade the CWM (to flash custom ROMs) via terminal, I typed 'su' and it said that I don't have root access, so I installed an app to see if I have root and it said, that I don't. I tried everything to root my phone. I flashed the ROM again, did a factory reset. Every time I tried to root, it was like it's rooted but not or it failed to root. What I did wrong?
My guess is that the root.zip didn't install the su binary correctly(E.g. into the wrong path so that the vendor su binary is still called).
To verify that, you could try(from the terminal):
echo $PATH
That should show you a ":" seperated list of paths in which the shell(The thing running in the Terminal) looks for a binary.
You'd now need to go through every path in this list, and check for a su binary. If you find one, run it. For example:
ls /example/path/su
If this finds a file(indicated by it showing the filename, su), run it:
/example/path/su
If you find more than one su binary, chances are that one of them will work. If you don't find any su binary, the root.zip probably wasn't able to remount rw.
If you're a little more advanced, you could try rooting your phone manually(I needed to to this yesterday because I'm on linux):
Download SuperOneClick 2.3. The .zip contains a folder called exploits. These programs initially get you the root permissions. To use them, adb push them to /data/local/tmp (Because you have write and execute permissions there), and execute them. They either directly drop you to a root shell or restart the adbd with root permissions. Either way, you can then remount /system and copy the su binary from the SuperOneClick to your /system/bin and set the correct permissions. I can't really recommend this method unless you know what you're doing though.
Good luck!

Categories

Resources