Need help changing recovery image. - myTouch 3G, Magic General

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

Related

Help on how to switch Recovery img.

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

mytouch 1.2 recovery broken

On test seven, went to flash Amun ras new recovery, didn't know that flashing a recovery is broken in this so now I am stuck with a broken recovery. I tried flashing it via adb shell didn't work, you guys have any suggestions?
Flash the 2010 Engineering SPL, flash recovery, then revert to stock SPL.
Flash via Terminal Emulator. I had to do the same thing.
Guess ill do yhat. I was hoping there was another way cuz i do not like flashing an spl via anything but fastboot lol.
C0dy said:
Flash the 2010 Engineering SPL, flash recovery, then revert to stock SPL.
Click to expand...
Click to collapse
I have the similar problem, i can't access the recovery, i can use the phone, or in the computer (adb) but i don't know how i can flash this without access to the recovery.
p10l1n said:
I have the similar problem, i can't access the recovery, i can use the phone, or in the computer (adb) but i don't know how i can flash this without access to the recovery.
Click to expand...
Click to collapse
Download Terminal Emulator if you don't already have it.
Then follow these steps.
Code:
Copy recovery-RA-sapphire-v1.7.0G.img to the root of your sdcard
start the terminal app
#flash_image recovery /sdcard/recovery-RA-sapphire-v1.7.0G.img
Flashing recoveries is broken in t7 so that wont wrk. What i wanna know is if fladhing an spl via terminal is.
knny1491 said:
On test seven, went to flash Amun ras new recovery, didn't know that flashing a recovery is broken in this so now I am stuck with a broken recovery. I tried flashing it via adb shell didn't work, you guys have any suggestions?
Click to expand...
Click to collapse
Do you have any access via fastboot? You could do a nandroid restore via fastboot then flash a recovery img... if not flashing an spl via goldcard method would work to let you fastboot flash a rom and recovery image.. perhaps..
I of course could be way off but I'm trying to help you brain storm.
What are the commands to nand restore via fastboot?
depends if you've done a backup via the recovery tool or the fastbooter.
If you did it on your recovery screen and it saved to the sd card you'll need to copy these files from the NAND folder in your sd card
Code:
data.img
system.img
boot.img
saved then in the /tools area of where ever you set up AndroidSDK. in my case it's /AndroidSDK/Tools/ (might be different for you)
Once that's done flashing codes are below. if you did NAND via fastbooter just use these codes.
Code:
fastboot devices (make sure it sees you)
fastboot flash system system.img
it will say Sending, then writing and say OKAY if it was successful
then type
fastboot flash userdata data.img
wait for the second OKAY and type
fastboot flash boot boot.img
wait for the second OKAY and type
fastboot reboot
Hopefully that works for you.
Ah okay that was simple, idk why I didn't think of it. I'm setting up sdk on my buddies laptop right now n then I'm going to get this thing breathin correctly again.
knny1491 said:
Ah okay that was simple, idk why I didn't think of it. I'm setting up sdk on my buddies laptop right now n then I'm going to get this thing breathin correctly again.
Click to expand...
Click to collapse
me too, hope it works out for you. if it doesn't I'll keep brain storming with you.
I'm just REALLY trying not to go throguh the root process again lol, I think I'm just going to adb shell the SPL and then fastboot the recovery given its the easiest way I can think of.
I also just thought of the idea that you could simply do
Code:
fastboot erase recovery
fastboot flash recovery (recoverynamehere)
I need to flash the ENG spl first, which I am doing right now lol.
What is the appropriate command for flashing the spl? I did this:
adb shell
mount /sdcard
cd /sdcard/
flash_image hboot hboot.img
and via terminal:
su
flash_image hboot /sdcard/hboot.img
It said it couldn't find the hboot partition, my guess is I need to figure out what the correct partition name is.
Anybody know the command?
Heellllloo? Lol need some help here
Anyone got anything?
Fixed
-------------------------------------
Sent via the XDA Tapatalk App

flash_image recovery help

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.

[Q] MT3G bad recovery flash, stuck

Hi,
I have a mt3g, TMobile. CyanogenMod 6.1.0, ClockWork recovery. Used ROM Managed to flash Amon Ra recovery, since I needed to re-calibrate the battery. It asked me to pick phone model, picked Ion/MyTouch 3G. After reboot:
- Stuck on splash screen if I try to go to recovery
- When booted up - a bunch of force closures, keeps playing a ringtone over and over and...
Everything I tried to do through ROM Manager didn't help.
Any help is appreciated.
Thanks.
truss said:
Hi,
I have a mt3g, TMobile. CyanogenMod 6.1.0, ClockWork recovery. Used ROM Managed to flash Amon Ra recovery, since I needed to re-calibrate the battery. It asked me to pick phone model, picked Ion/MyTouch 3G. After reboot:
- Stuck on splash screen if I try to go to recovery
- When booted up - a bunch of force closures, keeps playing a ringtone over and over and...
Everything I tried to do through ROM Manager didn't help.
Any help is appreciated.
Thanks.
Click to expand...
Click to collapse
Do you still have root? If you can get into ROM manager, reflash clockwork recovery, then wipe cache, dalvik, and run a fix permissions. That should get you back up and running long enough to try again to flash amon ra.
Not sure if the oem spl will let you fastboot flash a new recovery but that's your most reliable bet.
It sounds like it might be time to do a full wipe and reflash anyway. Have you heard of Ohsaka's SuperWipe?
I tried reflashing Clockwork through ROM Manager. It says "root granted", "clockwork flashed" immediately. When I try to boot into recovery - I get stuck on green MyTouch screen forever. Battery pull is the only way out.
I guess the problem is that I cannot get to any recovery anymore. Any ideas?
Do you have fastboot. If so you can flash recovery from there.
kodjo said:
Do you have fastboot. If so you can flash recovery from there.
Click to expand...
Click to collapse
Can I do that through adb shell? I don't think I built fastboot.
truss said:
Can I do that through adb shell? I don't think I built fastboot.
Click to expand...
Click to collapse
Fastboot is a different mode. Boot into hboot (vol down + power I think) and then select fasboot from the menu. Then plug into computer. From a command prompt type:
fastboot flash recovery recovery.img
The recovery needs to be in your tools or platform-tools folder and named recovery.img for this to work. Otherwise it would be fastboot flash recovery c:\path\to\recoveryfilename.img. Make sense?
Link to Amon_Ra Recovery 1.7 for MT3G 32B. http://www.filefactory.com/file/caa48b0/n/recovery-RA-sapphire-v1.7.0G-cyan.img
Otherwise keep trying with ROM Manager. Might take a few attempts to get recovery to stick, even temporarily. It did for me. Flash once then flash again. There's also an option in ROM Manager settings to erase recovery prior to flashing. Check that and see if it helps.
Phateless said:
Fastboot is a different mode. Boot into hboot (vol down + power I think) and then select fasboot from the menu. Then plug into computer. From a command prompt type:
fastboot flash recovery recovery.img
The recovery needs to be in your tools or platform-tools folder and named recovery.img for this to work. Otherwise it would be fastboot flash recovery c:\path\to\recoveryfilename.img. Make sense?
Link to Amon_Ra Recovery 1.7 for MT3G 32B.
Otherwise keep trying with ROM Manager. Might take a few attempts to get recovery to stick, even temporarily. It did for me. Flash once then flash again. There's also an option in ROM Manager settings to erase recovery prior to flashing. Check that and see if it helps.
Click to expand...
Click to collapse
I appreciate your help.
When I try to flash recovery.img, I get this: error: cannot load `recovery.img`
When I try running fastboot with absolute path, I get: FAILED (remote: not allow). Is there a way to fix this?
Tried flashing through ROM Manager many times - no result.
truss said:
I appreciate your help.
When I try to flash recovery.img, I get this: error: cannot load `recovery.img`
When I try running fastboot with absolute path, I get: FAILED (remote: not allow). Is there a way to fix this?
Tried flashing through ROM Manager many times - no result.
Click to expand...
Click to collapse
Interesting... Where are you trying to flash recovery.img and getting that error? What method are you using? Are you sure you have the path to recovery.img correct?
As for fastboot, you need an S-OFF/engineering spl so I guess that's out.
What happens if you use Terminal Emulator?
su
flash_image recovery sdcard/recovery.img
Does that work? Keep at it, you have root so not all is lost. Eventually you will get there.
EDIT - make sure you rename the recovery to "recovery.img" and leave it on the root of your sdcard for my italicized instructions above to work. What ROM are you running? If flash_image doesn't work I need to know which version of the binary to give you.
Phateless said:
Interesting... Where are you trying to flash recovery.img and getting that error? What method are you using? Are you sure you have the path to recovery.img correct?
As for fastboot, you need an S-OFF/engineering spl so I guess that's out.
What happens if you use Terminal Emulator?
su
flash_image recovery sdcard/recovery.img
Does that work? Keep at it, you have root so not all is lost. Eventually you will get there.
EDIT - make sure you rename the recovery to "recovery.img" and leave it on the root of your sdcard for my italicized instructions above to work. What ROM are you running? If flash_image doesn't work I need to know which version of the binary to give you.
Click to expand...
Click to collapse
Thank you very much.
Running flash_image recovery command using adb shell a few times did the trick. I was able to boot to Amon RA recovery, wipe and flash CyanogenMod 6.1.0.
truss said:
Thank you very much.
Running flash_image recovery command using adb shell a few times did the trick. I was able to boot to Amon RA recovery, wipe and flash CyanogenMod 6.1.0.
Click to expand...
Click to collapse
Nice! Glad you got it sorted out.

Root OnePlus 2 with TWRP or OTA stock ?

Hi,
I've got a new OnePlus 2 phone.
Do i really have to flash TWRP in order to root my phone using SU tool ? or i can stay with the OnePlus 2 original stock ?
What are the advantages of TWRP?
Best,
Jonathan
rose10 said:
Hi,
I've got a new OnePlus 2 phone.
Do i really have to flash TWRP in order to root my phone using SU tool ? or i can stay with the OnePlus 2 original stock ?
What are the advantages of TWRP?
Best,
Jonathan
Click to expand...
Click to collapse
You can either FLASH TWRP recovery or BOOT into it: the difference is that when you boot into TWRP, it's temporary, which means when you've done your stuff and you reboot into the system, stock recovery will be present. To do so, boot into bootloader:
Code:
adb reboot-bootloader
and instead of:
Code:
fastboot flash recovery recovery.img
which FLASH the recovery, do:
Code:
fastboot boot recovery.img
which lets BOOT into TWRP.
Then you'll be able to flash SuperSu.V.Xx.zip beforehand pushed into your device.
Benefit of TWRP?
Full backup / restore, change file format, flash zip files, etc, etc.
For the OTA, you can still flash them, but you'll have to flash the stock ROM then the incremental zip if you FLASH TWRP or the full OTA update zip file from here.
Hi again,
After rooting my device....i can't copy a sound file to my /system/media/audio/ui..... How can i change the library permission ?
rose10 said:
Hi again,
After rooting my device....i can't copy a sound file to my /system/media/audio/ui..... How can i change the library permission ?
Click to expand...
Click to collapse
Which method? ADB shell? With an app?
If you use ADB shell / Terminal Emulator, you need to mount it into Read-Write mode.
To do so:
(
If you use ADB
Code:
adb shell
)
Code:
su
Code:
mount -o remount,rw /system
Then you can move your file.
Or if you use an app (ES File Explorer for example), you need to enable Root Mode: swipe from left, scroll down and activate "Root Explorer" case.
A thanks is always appreciated.

Categories

Resources