Sup guys, can someone show me how to change a recovery img via 1click root method? Right now I'm using Cyanogens 1.4 which is great but would like to upgrade to the new Amon RA's img. Any help would be appreciated.
TTT back up
Using ADB...
from the command prompt...
where you see recovery.img just type in the file name that you have in plasce of it....
adb remount
adb push recovery.img /sdcard/recovery.img
adb shell flash_image recovery /sdcard/recovery.img
adb shell reboot recovery
Related
Okay so I used the one click method to root my phone. Currently I am running the cyan 4.0.2 with the cyan 1.4 recovery. I also upgraded my spl to 1.33.2005. My question is how can I go about changing my cyan 1.4 recovery to the updated amon rav1.2.1?
how to use the android software developer kit to
http://forum.xda-developers.com/showthread.php?t=502010
directions are in the thread for the recovery image in question on how to apply after you get the sdk set up
http://forum.xda-developers.com/showthread.php?t=530492
You don't need SDK to flash new recovery image. This is what I did:
Download the recovery image, copy it to the root folder of the SDcard and rename it to recovery.img
Open Terminal:
Code:
su
flash_image recovery /sdcard/recovery.img
Done.
Thanks. Your way seems easier. Ill try that first. Thanks for your help.
tengtengvn said:
You don't need SDK to flash new recovery image. This is what I did:
Download the recovery image, copy it to the root folder of the SDcard and rename it to recovery.img
Open Terminal:
Code:
su
flash_image recovery /sdcard/recovery.img
Done.
Click to expand...
Click to collapse
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
hi,
one of our members in and-roid.ir is facing a strange problem... his phone is s-off and recovery v.3 was flashed.
he was installing a rom and suddenly there was an error in the installation... he tried to enter recovery and restore a back up but when trying to enter recovery from bootloader instead of entering recovery mode it will enter fastboot mode...
he flashed recovery again but no luck...
suddenly when usb was plugged he entered recovery mode... he tried again with usb unplugged and couldn't enter recovery mode...
so after entering recovery mode with usb plugged memory card won't mount... he tried to manually mount it and still no luck...
any ideas what's the problem?and how to trouble shoot it?
any clues at all?
Reflash the misc partition. (you can see how to do this in the root HBOOT 1.00 thread) Or you can boot into recovery...
Go to fastboot
put the custom-recovery.img in your android-sdk/tools folder
fastboot boot (drag and drop recovery.img into cmd or terminal) press enter
so i have to do following commands? correct?
Code:
adb shell
su
...you should have root privileges now (showing #). Next thing is backing up misc partition and replacing it with one from hack4legend-v5.zip. Extract this zip somewhere and fire another command promt there. Now you should upload flash_image binary and misc1-2.img:
Code:
adb push flash_image /data/local/
adb push misc1-2.img /data/local/
...switch back to 1st command prompt and change permission of flash_image_binary:
Code:
chmod 755 /data/local/flash_image
...and backup your current misc partition:
Code:
cat /dev/mtd/mtd0 > /sdcard/misc_backup.img
Now flash misc1-2.img:
Code:
/data/local/flash_image misc /data/local/misc1-2.img
exit
Click to expand...
Click to collapse
I believe so yes
Hi i made this lok version of cwm touch recovery img so you can now flash it using loki
this recovery is not auto loki so you will need to flash loki_doki.zip
to roms without loki installed
Download the files below
extract cwmtouchlok.zip
use the following adb shell/terminal commands to flash using loki
Code:
adb push recovery.lok /data/local/tmp/
adb push loki_flash /data/local/tmp/
adb shell
su
chmod 755 /data/local/tmp/loki_flash
/data/local/tmp/loki_flash recovery /data/local/tmp/recovery.lok
once done you will have successfully installed CWM Touch Recovery on your AT&T Galaxy S4
loki over CMW
nelson1345 said:
Hi i made this lok version of cwm touch recovery img so you can now flash it using loki
this recovery is not auto loki so you will need to flash loki_doki.zip
to roms without loki installed
Download the files below
extract cwmtouchlok.zip
use the following adb shell/terminal commands to flash using loki
Code:
adb push recovery.lok /data/local/tmp/
adb push loki_flash /data/local/tmp/
adb shell
su
chmod 755 /data/local/tmp/loki_flash
/data/local/tmp/loki_flash recovery /data/local/tmp/recovery.lok
once done you will have successfully installed CWM Touch Recovery on your AT&T Galaxy S4
Click to expand...
Click to collapse
My device is i377, rooted and with CMW 6.0.3.2. Do I need Loki? will it (safely) install over CWM?
Be gentle with this 74 yr noobie:>)) (also speak slowly. thanks
Hey!
I have tried installing cwm after doing towelroot. I am using terminal and used the command:
Code:
flash_image recovery /sdcard/recovery.img
but it ends up doing nothing. I have the proper binaries and I did chmod 777 so the command should work. But when I do:
Code:
reboot recovery
I boot into Android recovery 3e. Also after executing the command should I get any output or should it go straight to next line? Any help would be appreciated.
We have a locked bootloader which really prevents the us from replacing the stock kernel and recovery. The only working recovery we have is safestrap. Read more on the all things AT&T thread.
Sent from my SGH-I337 running GPE using Tapatalk
Oh wow can't believe i forgot that.