So i flashed back to stock using Odin, took the three updates to fp8, but now when i flash cwm it doesnt take.... always goes back to Android recovery. What am i doing wrong??
Thanks guys for all your continuing support with this device!
You need to boot directly into recovery after odining cwm recovery - there's a script that runs (/system/etc/install-recovery.sh) that overwrites recovery with stock when you boot up - you need to remove/rename/disable that script (either while in recovery or after flashing superuser/supersu so you can have write access to /system after booting, though the latter approach requires you to again odin recovery once you are done) to make the custom recovery "stick". Hope that helps
dwitherell said:
You need to boot directly into recovery after odining cwm recovery - there's a script that runs (/system/etc/install-recovery.sh) that overwrites recovery with stock when you boot up - you need to remove/rename/disable that script (either while in recovery or after flashing superuser/supersu so you can have write access to /system after booting, though the latter approach requires you to again odin recovery once you are done) to make the custom recovery "stick". Hope that helps
Click to expand...
Click to collapse
TOtally worked!! Thank you!
Related
not sure if this is what everyone is already doing, but I was trying to figure out how it might work
stock ota 2.3.1 os
fastboot oem unlock
flashed clockworkmod recovery
boot into recovery nandroid backup stock non-rooted os (just in case )
flash su-2.3.6.1....zip
nandroid backup again
take the boot.img from this nandroid backup and fastboot flash boot
onicrom said:
not sure if this is what everyone is already doing, but I was trying to figure out how it might work
stock ota 2.3.1 os
fastboot oem unlock
flashed clockworkmod recovery
boot into recovery nandroid backup stock non-rooted os (just in case )
flash su-2.3.6.1....zip
nandroid backup again
take the boot.img from this nandroid backup and fastboot flash boot
Click to expand...
Click to collapse
No.
10chars
fastboot oem unlock
flash cwm recovery
nandroid backup
mount /system
flash the su-2361 zip
boot up
rename/delete /etc/recovery.sh (or whatever the exact file is)
download rom manager, flash latest cwm (as of right now it's 3.0.0.5)
reboot to recovery to make sure cwm loads properly and updated.
done.
nxt said:
download rom manager, flash latest cwm (as of right now it's 3.0.0.5)
Click to expand...
Click to collapse
Caution with the 3.0.0.5 latest CWM. I can't get into CWM recovery with that one; I had to downgrade back to 3.0.0.0. The phone just stalls at the Google screen on boot up with it.
Another person's reported the issue in another thread here. I emailed koush, but no response yet.
@nxt, you've tested 3.0.0.5 and it works as expected?
distortedloop said:
Caution with the 3.0.0.5 latest CWM. I can't get into CWM recovery with that one; I had to downgrade back to 3.0.0.0. The phone just stalls at the Google screen on boot up with it.
Another person's reported the issue in another thread here. I emailed koush, but no response yet.
@nxt, you've tested 3.0.0.5 and it works as expected?
Click to expand...
Click to collapse
Not nxt, but I haven't had any issues with 3.0.0.5. Flashing, restoring, or anything at all.
unremarked said:
Not nxt, but I haven't had any issues with 3.0.0.5. Flashing, restoring, or anything at all.
Click to expand...
Click to collapse
Interesting. I wonder what the quirk is on mine and the other guy's. I haven't tried flashing it from fastboot, but selecting reboot to recovery from within ROM Mgr will not load recovery, it just hangs. No issues with 3.0.0.0.
distortedloop said:
Interesting. I wonder what the quirk is on mine and the other guy's. I haven't tried flashing it from fastboot, but selecting reboot to recovery from within ROM Mgr will not load recovery, it just hangs. No issues with 3.0.0.0.
Click to expand...
Click to collapse
Works fine for me normally. I personally don't use rom Manager to do anything though. I manually reboot into recovery and do recovery stuff. I have not tried selecting reboot to recovery via ROM Manager. That might be the issue.
Im trying to flash the Clockwork Recovery mod to my sidekick but every time I boot in recovery I keep getting the stock recovery screen. First of all I rooted my phone using the latest version of SuperOneclick Root. Once the phone was rooted I installed both root explorer and rom manager.
I downloaded the modified binary recovery file and replaced it in system/bin using Root Explorer. I used Rom manager to flash the CWM and it supposedly intalled it (it says version 4.0.0.2). I tried to reboot on recovery but it doesnt boot the CWM recovery screen. I the tried donwloading the CWM and placing the update.zip file in the root of my SD card. I then rebooted into recovery and selecte reintall packages and i get the following:
E: signature verification failed.. installation aborted?
Im guessing its the binary recovery file that's causing the problem but I've tried replacing the file again and it wont work. Anyway, does anyone have any idea whats going on and how I can successfully install the clockwork recovery mod??
Yes that would say that it isn't using the correct modded recovery binary. use my modded oneclickroot script to push the correct recovery and update, and it should work.
http://forum.xda-developers.com/showpost.php?p=15831175&postcount=124
Thank you so much it worked like a charm!! One question, every time I boot in recovery now, it boots in the stock recovery. In order to boot CWM i have to select reinstall packages every time is this normal??
Currently that's normal. I've got the same thing on mine.
sly_fox said:
Thank you so much it worked like a charm!! One question, every time I boot in recovery now, it boots in the stock recovery. In order to boot CWM i have to select reinstall packages every time is this normal??
Click to expand...
Click to collapse
Yes that CWM is a fake flash and doesn't actually replace your stock recovery so you would have to reinstall packages everytime, unless you flash bali kernel which has the red CWM that replaces the stock recovery when you boot into recovery mode
Sent from my SGH-T839 using XDA App
EDIT: sniped by ayoteddy.
That is normal, as that script uses the "fake flash" instead of having CWM built into the kernel.
A fake flash technique uses a modded recovery binary that doesn't check for signature verification, allowing us to boot into CWM from a stock looking recovery, even on a stock kernel.
In order to have recovery boot straight to CWM, you need to have it built into the kernel, which currently only exists on the Bali kernel (as there's no need to build it for another kernel).
I have rooted & unlocked the boot loader on my Nexus S with ICS 4.0.4. I had flashed a custom recovery and had flashed the SU. After re-boot, I found that that the custom recovery had gone and the stock recovery was appearing.
Later I installed ROM Manager and clicked on flash ClockWorkMod recovery. It downloaded & installed. Immediately I could boot in to ClockWorkMod recovery and see all the options. Later I wanted to flash a customer Kernel. When I tried the option in ROM manager to boot in to recovery, it goes in to the stock recovery.
What's wrong? How can I flash a Kernel now. Can I flash using the stock recovery? Why is the phone not saving the ClockWorkMod recovery?
try install cwm throught fastboot first (guide here). The cwm version of the guide is outdated, so make sure to download latest version of cwm.
Delete or rename /system/etc/install-recovery.sh and flash CWM one last time. It'll stick. Each boot, stock ROMs reflash the stock recovery unless you delete/rename that file.
All,
I'm rooted and unlocked. The weirdest thing I'm experiencing is that in both the EZ Recovery and Rom Manager, when I select to reboot into recovery, I'm not booting into ClockworkMod. I'm booting into stock recovery I think. The only time it would boot into ClockwordMod is when I flash touch clockwork mod then it would boot into the correct recovery.
Do I need to flash the Touch ClockworkMod every time I want to boot into recovery? Thats annoying.
Please help.
Thanks!
If you boot into stock recovery by selecting reboot recovery then CWM is simply not installed. Are you selecting the correct option in ez recovery to install the recovery?
I'm good now. I was on stock, but was rooted and unlocked. Like I said, it would work if I flash the recovery, but if I reboot into recovery again without flashing it would go back to stock recovery.
Anyways, I've flashed to CleanRom 4.0 and tested rebooting into recovery and sure enough it went to the ClockworkMod Recovery. So looks like I"m good.
It will do that on stock rom unless a couple of files are modified I believe. Doesn't do it on custom roms.
I flashed CWM in odin,but when i boot up into CWM it boots the stock recovery.Also,do i need to flash the bootloader and radio if coming from 4.1.2? I must be getting old..I did it on my last relay,but i don't remember how.Do i have to flash the bootloader first?
Thanks
The 4.1.2 stock image apparently has code within its start up routine to overwrite a custom recovery if one is detected at boottime. After flashing with ODIN, did you reboot into the system, or did you directly boot into CWM? If you're on 4.1.2 stock, there will be no need to update the bootloader or modem, you're on the latest. Try flashing CWM, and then immediately booting into recovery. You can also delete the files Stock calls to reflash the recovery from the image once you're able to get in via CWM, and utilize adb.
Magamo said:
The 4.1.2 stock image apparently has code within its start up routine to overwrite a custom recovery if one is detected at boottime. After flashing with ODIN, did you reboot into the system, or did you directly boot into CWM? If you're on 4.1.2 stock, there will be no need to update the bootloader or modem, you're on the latest. Try flashing CWM, and then immediately booting into recovery. You can also delete the files Stock calls to reflash the recovery from the image once you're able to get in via CWM, and utilize adb.
Click to expand...
Click to collapse
Yes,i booted into the system,then restarted into CWM...I'll try reflashing,and booting right into recovery and let you know,Thanks for the reply!
Yep,that did it...Got it up and running..Thanks again Magamo..