I was trying to do this by copying the img over from the computer on to the SD card. when i boot in to the recovery menu, i select consol and type in what it says on the website
"Copy recovery-RA-dream-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
select console from the menu
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-dream-v1.6.2.img"
But everytime i do this i get an error. here is the error
"error reading /sdcard/recovery/recovery-RA-dream-v1.6.2.img header: input/output error"
Are you trying to flash the stock one, or one with the carebear images? If so, remove the green or pink or blue from the title and flash again.
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
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
Hi everyone, I have a little problem i don't know why my magic doesn't want to enter in recovery mode (boot while holding HOME)
I do it before, but now doesn't want it
Can somebody tell me why or want i can do?
tnks a lot
Your probably going to have to reflash the recovery. Can you still get into fastboot (back+power)?
tnks for answer and you have right
I do this and i can enter again in recovery mode
Code:
Copy recovery-RA-dream-v1.7.0.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your G1 via usb to your pc/mac/...
adb shell
#mount -a (this can give back an error if you don't have an ext partition, don't worry about it and just proceed)
#flash_image recovery /sdcard/recovery-RA-dream-v1.7.0.img
tnks a lote
Hey all,
Hopefuly someone can help me otherwise i'm going to have to take this phone back to the o2 shop where I got it from.
I have a Nexus S, was looking at custom roms the other night and decieded to unlock and root it and flash the CyW7 rom onto it.....after a couple hours of playing with the new software I decieded it wasn't for me so flashed the device back to stock 2.3.1 software.
2.3.1 loaded fine and I installed the 2.3.2 update before rooting it so I could install adblock.
Got it all working fine, setup a security PIN (8 digits) and went to bed.
Woke up this morning and found the phone was not accepting the PIN, ive tried rebooting, trying the PIN in different varations incase I setup a wrong PIN in the first place......still no luck
So, i've looked into reflashing the device with stock 2.3.1 software again but USB debug mode isn't on and I can't install the USB drivers in Fastboot mode (says no compatible driver found for my hardware error)
How do I move forward here? Is there anything I can do to fix it?
Thanks a billion for anyone who gives me advice....
Boot into recovery and factory reset.
Boot recovery took me to a error screen where I had to take battery out to reset it.
I've managed to get the USB drivers to work now, and flashed the clockwordmod recovery image, then reset the phone.
Can I just confirm;
Is this the correct proceedure for the Nexus S to stop the Clockwordmod recovery from been removed.
1. Download the custom recovery image and save it to your computer
2. Copy the recovery.img file inside the tools folder of the sdk (so it is in the same folder as fastboot.exe)
3. Then in the command prompt that should still be open, type the following with hitting enter at the end of each line:</p><p>fastboot flash recovery recovery.img
4. Once it is flashed, leave the phone in plugged in and in fastboot mode.
6. Root the Phone
7. In fastboot mode, select Recovery using the volume buttons and power button and wait for it to boot into recovery mode.
8. Download the Superuser flashable zip file and save it to your computer.
9. Once in recovery mode, select Mounts and Storage then select Mount USB Storage so we can transfer files to the sd while it is in recovery mode.
10. Copy the Superuser.zip file to the root of your internal storage (do NOT extract it, do NOT put it in any folders, just on the phones storage itself).
11. Select Unmount on the phone.
12. Select Mount System, then select Go Back to get back to the main menu.
13. Then scroll to flash zip from sdcard and then choose zip from sd card and select the superuser.zip file and wait for it to finish flashing.
14. Once it is done, select Go Back then Reboot System and wait for the phone to reboot.
15. Stop the Phone from Uninstalling the Custom Recovery Image
16. Once the phone is booted up, plug it in via USB cable and do NOT mount the storage.
17. Open a command prompt on the computer and type the following with hitting enter at the end of each line:
adb shell
cd etc
mount -o rw,remount /dev/block/mtdblock3 /system
mv install-recovery.sh install-recovery-no.sh.
18. Turn off the phone and turn it back on by holding down Volume Up and Power to get into fastboot mode.
19. Plug the phone in via USB cable while in fastboot mode and open the command prompt again and type the following with hitting enter at the end of each line:
cd c:\androidsdk\tools\
adb reboot bootloader
fastboot flash recovery recovery.img
Hello all,
I unlocked and rooted 4.4.1 with the stock ROM.
I saw the new update 4.4.2 and booted into recovery, did adb sideload for the update and everything rebooted.
I seem to have lost Root?
When I open Super SU I get the message:
There is no SU binary installed and SuperSU cannot install it. This is a Problem!
If you just upgraded to Android 4.3, you need to manually reroot - consult...
I go through the following process:
Obtaining Root Access and Custom Recovery:
Turn on USB Debugging.
To do so; you must first go to Settings>About>Build Number and click seven times.
The actual setting can then be found in Settings>Developer Options>USB Debugging
Download the following:
SuperSU (CWM .zip)
CWM (Pick the version for your device)
Place the recovery-clockwork-VERSIONNUMBER-mako.img file into your C:\android-sdk-windows\platform-tools folder.
Put the SuperSU.zip on your phone.
Open another Command Prompt if it isn't still open. (Navigate to C:\android-sdk-windows\platform-tools and shift + right click. Select "Open Command Window Here.")
With your phone plugged in type:
Code:
adb reboot bootloader(Hit Enter)
And wait for your phone to boot into the android again.
Now type:
Code:
fastboot flash recovery IMAGENAME.img
(Change the file name to the correct file name and Hit Enter)
Once that is finished: select the "Recovery Mode" option again on your phone.
You should get a new recovery menu here. Select "install zip from sd card" and "choose zip from sd card."
Find the SuperSU.zip that you transferred earlier and select "Yes" to installing.
Navigate back to "Reboot" and reboot your phone.
You're now rooted!
However, ClockworkMod Recovery won't continue to load after this.
To fix this, find "Rom Manager" from the market. (The free version is fine.) Use the "Flash ClockworkMod Recovery" option.
In Rom Manager, when I try to re-install recovery I get: "An Error occured while flashing your recovery"
Help please!
-Jason
I fixed it. I had to reflash the SU.zip from within recovery.
-J
Long story short. When you flash a ota file you loose root. It resets the permissions on /system
Just download the latest su. Zip and put it on your phone.
Get the custom recovery of your choice in. Img form and flash or just boot it up with fastboot and flash the su. Zip.
It's that simple
---------- Post added at 07:06 AM ---------- Previous post was at 07:04 AM ----------
Damn it. I read everything but I fixed it part. Thought it was a sig which I don't ever read.