ROB281
Well-Known Member
yes this is with the latest version, it happened with an older version as well
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
yes this is with the latest version, it happened with an older version as well
KitsapAndroid
Android Enthusiast
I've gotten it once or twice. I think it only pops up when the phone goes into roaming. Not really to sure though. I just ignore it. Hopefully it's not a billing problem for me down the line. I suspect it won't be though.
It's not just you. I think many others are having that same issue.
Did you use this one ClockworkMod Recovery 3.0.0.5 - xda-developers
It seems like you have the right version. I flashed it through rom manager with no problems. Its on the wiki page. Just make sure you place the recovery you download and rename in the same folder where the ". Xxx" is
As mentioned before CWM 2.5 works just fine, I would wait until 3.0 is more stable as it seems many are having different issues with it, if you absolutely want to flash the 3.0 and phone is not taking it via TE, then either you have an older version of TE, or you will have to force it from ABD 
LBPHeretic
Android Expert
Yeah, I think I am just going to stick with ClockworkMod Recovery 2.5.0.1 for now. I still do not understand why Terminal Emulator will not flash it though, but it is not a huge deal because I can just use ROM Manager like DonB said. Is it possible that using Z4Root to root my handset is the reason why Terminal Emulator will not recognize the flash_image command? Maybe I need to install BusyBox, though I thought that was installed when one rooted?
EDIT: Nevermind, I think I see the problem. My ROM does not have the flash_image utility installed, which is why Terminal Emulator cannot use it. How would I know if BusyBox is installed though, because I thought Z4Root said it installs it when you root?
EDIT: Nevermind, I think I see the problem. My ROM does not have the flash_image utility installed, which is why Terminal Emulator cannot use it. How would I know if BusyBox is installed though, because I thought Z4Root said it installs it when you root?
andygu3
Android Expert
You can use TB to install busybox
LBPHeretic
Android Expert
How would I do that? I saw some BusyBox installer in the Android Market, but was not sure if it was good.
I think ultimately, once I flash to a different ROM it will not matter anyway. BusyBox and flash_image are surely already included in custom ROMs, at least they have been in my experience. I was just mistaken to think flash_image was on the stock ROM by default, I guess. Where would I look to see if BusyBox is installed on my stock ROM after Z4Root, so I can flash back to it and check later?
andygu3
Android Expert
The busybox installer in TB is in the 'Problems' part of the main screen in TB
Squiggy
Android Enthusiast
I haven't had any issues at all since flashing it a few days ago. Best ROM I've ever installed. Changes the phone - for the better - completely.
MahaloCat
Android Expert
Use method 2 - Aosps Build Remove the Flash_Image code.
You can Add it...But its a pain in the ass.
You can also flash back to a CM6 rom - Flash_image is enabled there.
Method 2 is easiest IMO
LBPHeretic
Android Expert
Yeah, you are probably right. I did not realize that AOSP removed the flash_image binary and that is a shame.
I actually found a guide to put the flash_image binary back into the system directory using Terminal Emulator which looked pretty straight forward here: [GUIDE] Flash any recovery easily on the phone using flash_image - xda-developers . I just wondered if that would work for our Sprint HTC Hero handsets. I have no problem with using a command line.
LBPHeretic
Android Expert
Yeah, I might, but really it was just a "for my information" type of thing. I do not mind flashing to CyanogenMod ROMs to flash new recoveries or just use the ROM Manager method.
It is not like one has to flash a new recovery that often anyway. I just like to have the information and I appreciate your insight on this.