my magic is TIM's G2
the rom is myhero 2.0.5 but the recovery is too old, so i want to flash the recovery to Amon's recovery 1.5.2.
but when i flash_image recovery /sdcard/recovery.img
some error type. all is "out of memory". then i open the phone, i can't into the recovery.
it's so bay. now i can flash 1.2.3H into my Magic, i want flash 1.5.2, help please.
It won't work if you only type that. I assume you're using a terminal emulator. I'm pretty sure you only forgot the mount command, but I'll go trough everything to be sure.
All you need to to is to flash the recovery image again. As you're having MyHero, I assume you're having a 32A. Therefore, make sure you have the recovery-RA-sapphire-v1.5.2H.img, not the recovery-RA-sapphire-v1.5.2G.img.
Copy the file to the root of your SD, no need to rename it.
Open up your terminal emulator, and type:
Code:
su
You should get a root request, accept it. Then type in:
Code:
mount -a
Don't worry if you're getting errors here, that's normal. Lastly, type in the following.
Code:
flash_image recovery /sdcard/recovery-RA-sapphire-v1.5.2H.img
It's just normal to get errors here too. Or, at least I do.
Start your phone in recovery, and it should work.
tks
i will try later
Related
I flashed with the latest cyanogen on a 32A in CM's recovery image, i had the patch for the kernel (take it from 32B to 32A) but i didnt get to apply it yet.
when i rebooted my phone it hangs on the Rogers screen, i can get to fastboot and recovery mode (stock recovery mode). I made a nandroid backup (before the flash) but i cant get to it from the recovery mode menu, and when i connect the fastboot usb, my sd card doesnt show up on my computer. so i cant run the fastboot command to load the recovery image...
is there anything i can do?
some more information:
when i go into recovery mode, the "removable disk" shows up in my computer, but clicking on it just says "please insert a disc into drive..." which leads me to believe it is not mounted, any way to do this from recovery?
It'll never boot when you haven't installed the 32A patch.
And that means that you'll never be able to mount the SD card to have it show up in Windows. You can use adb to push the update.zip file to your SD card while in Recovery mode.
(You'll need the Android SDK installed for this)
Start up your phone in Recovery mode using the Power+Home buttons.
Once in recovery, wait for Windows to detect the phone (about 30 seconds).
Copy the 32A patch to your Android SDK tools folder, then run:
Code:
adb push <filename for your 32A patch>.zip /sdcard/update.zip
This will push your 32A patch to your SD card as update.zip.
Then apply update.zip through your Recovery environment.
A note to you... Before running the adb push, try running:
Code:
adb shell
mount /sdcard
exit
adb push <filename for your 32A patch>.zip /sdcard/update.zip
This will make sure that your SD card is properly mounted before copying the file to it.
To check that the file is there before trying to update, run this from your Command Prompt.
Code:
adb shell
cd /sdcard
ls | grep update.zip
You should see update.zip listed there.
After you've applied the 32A patch zip file through your Recovery environment, reboot your phone.
Should work now...
If you haven't installed the Amon_RA Recovery yet, it would be a good idea. It lets you save and update zip file to the root of your SD card without renaming it to update.zip first. You can apply any update zip file as an update.
thanks for the reply,
when i type adb shell i get:
"error: device not found"
typing adb devices also yields that the device is not listed
but windows does make the noise notifying that a device is connected, and the Removable disc still comes up in my computer
when i go into Device Manager, under disc drives it shows up as
HTC Android Phone Usb Device when the phone is in recovery
and if this makes any difference, press home+power again and look at the options in recovery the bottom says "E:Can't open /cache/recovery/command"
it worked in fastboot/recovery before, but that was when i had USB debugging selected and before i flashed CM i wiped. could this be the reason why im not able to access the phone with adb in recovery/fastboot?
for some reason i was able to fastboot into cm's recovery image and then the device was listed in adb, i followed your instructions and applied the patch, the phone booted up!
thank you!!!!! phew, that was a close one
zeotrope said:
for some reason i was able to fastboot into cm's recovery image and then the device was listed in adb, i followed your instructions and applied the patch, the phone booted up!
thank you!!!!! phew, that was a close one
Click to expand...
Click to collapse
The CM recovery works great but without a hardware keyboard it's not entirely functional.
I'd recommend flashing Amon_Ra recovery and using that. Read the directions carefully though. Make sure you use the right one for your phone.
got amon-ra's recovery permanently flashed on there, thanks again for your help
Well I need help. Last week when verizon was having probelms with service my friend thought that it was his phone. He got to messing with **** and now he cant load any roms. Im hoping someone can help. When he boots into recovery mood he no longer has the option to flash zip from sd. Also Nand backup is now missing so he can not backup to a restore point. the only options he has is flash update reboot wipe cache and factory reset. I have heard of people losing root but with that would you even be able to boot by pressing power and the volume up key... he wont leave me alone about fixing his problem so any info someone could shed on the situation I would really appreciate... Thanks
leech2082 said:
Well I need help. Last week when verizon was having probelms with service my friend thought that it was his phone. He got to messing with **** and now he cant load any roms. Im hoping someone can help. When he boots into recovery mood he no longer has the option to flash zip from sd. Also Nand backup is now missing so he can not backup to a restore point. the only options he has is flash update reboot wipe cache and factory reset. I have heard of people losing root but with that would you even be able to boot by pressing power and the volume up key... he wont leave me alone about fixing his problem so any info someone could shed on the situation I would really appreciate... Thanks
Click to expand...
Click to collapse
Just redo Amons recovery. That should fix it.
Follow these steps: (Also found in Sticky section)
III: Flashing a Custom Recovery
Flashing a custom recovery will make your life easier when flashing ROMs in the future.
1. Download this file: Recovery.zip
2. Extract file contents to your \tools\ directory of your Android SDK.
3. Open up a command prompt and go to your tools directory, and execute these commands:
* adb shell mount -o rw,remount /dev/block/mtdblock3 /system
* adb push recovery.img /sdcard
* adb push flash_image /system/bin
* adb shell chmod 755 /system/bin/flash_image
* adb shell flash_image recovery /sdcard/recovery.img
4. Success! You now have a recovery partition installed on your phone. You can access it by running "adb shell reboot recovery" or by powering off your phone, holding "Volume Up + Power On"
Once you do this...power down... then volume up + end = recovery..
The behavior of the recovery boot that you are describing is an HTC recovery; it is not Amon_RA. Amon_RA didn't change, it got replaced.
That strongly suggests that "your friend" re-flashed an HTC ROM onto the phone, probably using a HBOOT method (using a "PB00IMG.ZIP" file).
droidkevlar said:
Just redo Amons recovery. That should fix it.
Click to expand...
Click to collapse
droidkevlar assumes here that what got flashed was the HTC Root PB00IMG.ZIP file.
For the sake of "your friend who won't leave you alone", I hope droidkevlar is correct; otherwise your friend has joined the leak club.
Good luck,
bftb0
vash8806 said:
* adb shell mount -o rw,remount /dev/block/mtdblock3 /system
* adb push recovery.img /sdcard
* adb push flash_image /system/bin
* adb shell chmod 755 /system/bin/flash_image
* adb shell flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
or you could do it from the PC with a single command. Put the phone into FASTBOOT mode (power on phone holding down both Send+End/Power), and then
Code:
fastboot flash recovery recovery-RA-eris-v1.6.2.img
The md5sum of Amon_RA v1.6.2 for the Eris is e3932991f097993602af3c7a4b61a4f8
You can check to see if fastboot is communicating with the phone by using the command "fastboot devices". (Note that if running fastboot from Linux, fastboot needs to be run as root to access the USB device).
bftb0
sending my phone back into google, have frf91 back. need to remove clockworkmod now and install the stock recovery. googled it but no help with the current frf91, unless you can use the original shipping recovery image with it? also do you think clockworkmod might cause any concerns when they receive it if i cant figure it out? bootloader is not unlocked.
So, for some reason, I couldn't find a guide on xda...I know I saw one here...
Anyways, here you go:
http://androidspin.com/2010/05/06/guide-unrooting-your-nexus-one-its-like-it-never-happened-almost/
is there an easier way to do this if you used Rom Manager?
Nope, I don't think it's possible to flash a recovery with a recovery...(edit: there is no option in Rom Manager to select a specific recovery.img)
You might be able to do use the flash_image binary.
If you have adb setup, use: (you must have the recovery.img in the root of your sd card)
Code:
adb shell
su
flash_image recovery /sdcard/recovery.img
Is that true for the paid Rom Manager version as well?
wdfowty said:
Nope, I don't think it's possible to flash a recovery with a recovery...(edit: there is no option in Rom Manager to select a specific recovery.img)
You might be able to do use the flash_image binary.
If you have adb setup, use: (you must have the recovery.img in the root of your sd card)
Code:
adb shell
su
flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
I second this. This is how i got the stock recovery back onto my device.
im not familiar with adb setup, is it hard to install/use? im getting frustrated trying to get it back to stock. do you think htc will care i have clockwork mod as my recovery? bootloader isnt unlocked.
futango said:
I second this. This is how i got the stock recovery back onto my device.
Click to expand...
Click to collapse
everytime i hit adb shell a # comes up with the line next and su command isnt working
bobbbyjuice said:
everytime i hit adb shell a # comes up with the line next and su command isnt working
Click to expand...
Click to collapse
That mean your machine not yet rooted, go to the wiki page, or search 1-click rooted, that is a post link on wiki page, title is something like root without unlocking, details instructions on and shell
thanks i just 1 click rooted real quick. i have the recovery file on my sd card but now it says not found. its recovery.img like it asks for.
bobbbyjuice said:
thanks i just 1 click rooted real quick. i have the recovery file on my sd card but now it says not found. its recovery.img like it asks for.
Click to expand...
Click to collapse
Why are you trying to get rid of clockwork when you weren't rooted and couldt have installed it in the first place.
booted into recovery and found out one of my previous attempts must have worked because i have the stock recovery back now. thanks for all the help guys!
YES YOU NEED TO READ THIS WHOLE POST, PROB MORE THEN ONCE TO MAKE SURE YOU GOT IT. YES I KNOW HOW LONG IT IS, I TYPED IT!
the reason i call it a semi-brick is because a true brick can bot be recovered with out opening the case.
first go here and read this for info: http://forum.xda-developers.com/showthread.php?t=838484
now since your here im going to assume that its too late.
*things you will need.
copy of cwm recovery. get it here (the manual install link): http://forum.xda-developers.com/showpost.php?p=9145724&postcount=28
adb installed and working.
a known good rom, or nandroid backup. here is one: http://forum.xda-developers.com/showthread.php?t=836042 (use odex one)
a wpthis.ko for YOUR specfic kernel (run (adb shell cat /proc/version) that will tell you what kernel you have)
*first thing we need to know is, are you s-off or s-on now?
if your s-off just boot into clockwork mod recovery, wipe the phone and flash a known good rom and be done with it. if you dont have cwm recovery installed. boot into fastboot (vol down+power) you must have the sdk/adb installed and working, and type fastboot flash recovery LocationOfRecovery.img (where LocationOfRecovery.img= where you have the recovery, ie c:\android\recovery.img). once thats installed follow instructions above.
*if you are s-on:
will the phone boot into android? if so your not bad off.
if you want to unroot to return the phone, follow the unroot thread here: http://forum.xda-developers.com/showthread.php?t=835971
if you dont want to unroot then you have a couple of different options. if you have cwm recovery still installed, just follow instructions above and flash a known good rom. ive been told that boot.img (kernel) wont flash if you are s-on. the way to fix this (temporarily) is boot into recovery, but before you flash run these commands:
(put wpthis.ko in sdk folder)
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
then proceed to flash the rom. once booted into android skip down to, "now to get back to s-off"
*if you have stock or eng-recovery installed.
will the phone attempt to boot android at all? where is it stuck at?
a good min after it starts to try to boot, type these commands:
adb remount
adb shell
if you can get in shell then theres still hope. back out shell for a second and start here:
put the cwm recovery.img and wpthis.ko in your sdk folder
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb push recovery.img /data/local/recovery.img
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
# dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21 (now wait a min or 2 to give it time to finish)
#sync (give it another min or to just to be safe)
#reboot recovery
at this point you should be in cwm recovery. follow instructions above for flashing with s-on.
*if you cannot get into shell while booting, but have eng-recovery installed, there might be some options.(however this is all theory)
boot into recovery-
if you are on linux using adb, you can try taking sh from /system/bin folder of any custom rom, chmod 0755 it, then push it to /system/bin and adb shell might work.
windows-
boot into recovery.
a system.img compatible with your installed kernel pushed may work. put the system.img into the sdk folder.
adb push system.img /data/block/mmcblk0p25
then reboot and see where you are. if that dont work, grab the modified miscnew.img here: http://www.4shared.com/file/pUPfrGi-/mmcblk0p17.html
rename it misc.img put it in sdk folder and
adb push misc.img /dev/block/mmcblk0p17
then reboot into bootloader with PC10IMG.zip on root of sdcard and it should run though. if it does your fully stock and get to start all over again.
*if you cannot get into shell, and you have stock recovery, im sorry your pretty screwed. as of right now the only thing thats gonna bring it back is a full img/update signed from htc thats equal to or higher then the version currently on the phone. (well and jtag of course)
*well now you've done one of the steps above. your booted into android, you have perm root, and cwm recovery installed, just still s-on. dont worry your almost there!
first take that wpthis.ko for you kernel and push it, and the eng hboot.
adb push wpthis.ko /data/local/
adb push hboot-eng.img /data/local
then from adb shell, or terminal root prompt:
# insmod /data/local/wpthis.ko (again you should get the function not implemented error)
NOW REMEMBER THIS NEXT STEP COULD MEAN DEATH FOR YOU G2 IF TYPED WRONG, AND AFTER ALL THIS HARD WORK!
# dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
wait a few mins to be sure its done.
# sync
wait a few more just cause.
reboot, you should now be s-off, cwm recovery installed, and free to do whatever you want. just dont go screwing it up again
* as new methods are discovered, or ones here are proven wrong, i will update as necessary. as of the writing post, 2 devices that i know of have been saved!
good luck!
wpthis.ko for bacon bits.03 kernel: http://www.4shared.com/file/OAcd1bix/wpthis-263221-cyanogenmod.html
first off, let me say i'm a total n00b
trying to flash_image recovery to clockwork 2.5.1.2
downloaded recovery-clockwork-2.5.1.2-glacier.img (renamed to recovery.img) and put it on the root of the sdcard
launch terminal emulator (from market)
type su [enter]
type: flash_image recovery /sdcard/recovery.img [enter]
keep getting flash_image: not found
i've also tried ROM Manager and Flash ClockworkMod Recovery
it shows current recovery as ClockworkMod 2.5.1.2
but when i reboot into recovery, i keep getting the triangle !
perm. rooted with Visionary
obviously i'm doing something wrong. do i need to have S=off in order for this to work?
thanks in advanced
Close - S=off
I flashed via this method you need to download flash_image and put it in /system/bin
A more helpful response can be found here:
http://forum.xda-developers.com/showthread.php?t=918275
smellmyfingers said:
perm. rooted with Visionary
obviously i'm doing something wrong. do i need to have S=off in order for this to work?
thanks in advanced
Click to expand...
Click to collapse
Yes you have to have s=off.
The security protocol is flashing the stock recovery image back onto the phone.