ROM may flash stock recovery on boot - Nexus S Q&A, Help & Troubleshooting

Flash CMW Recovery 6.0.1.0
ROM may flash stock recovery on boot Fix
I chose YES, how to restore the stock Recovery?

assuming you are on jellybean
with this CWM- stock-recovery-JB-4.1.1.zip
or fastboot only recovery.img extracted from zip JB factory image

Related

[Q] Nexus S ICS 4.0.4 & ROM Manager

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.

[Q] Couldn't find this one either...

Does TWRP recovery for the One S (S4) T-Mo require me to flash a seperate boot.img when I flash a rom, say Trickdroid v8.0? I want to flash either CM10 or Trickdroid but I'm not sure if TWRP will automatically access the boot.img in the ROM.zip. Any help would be greatly appreciated:fingers-crossed:
try just flashing the .zip and if it doesn't work then boot back into recovery and wipe then boot into bootloader -> fastboot, extract the files from the .zip on your computer, then flash the boot.img manually through fastboot, then boot into recovery and install the .zip. trial and error. it's how we learn
p.s. i know that cwm recovery automatically flashes the boot.img but twrp might not

[Q] CM10 to sense help!

Ok so I flashed the cm10 rom today and used CMD to add the boot.img for cm10 but now I want to go back to Viperrom. I flashed the original boot.img using cmd again but I got stuck in a boot loop (kind of) what I mean by that is that if I flash cm10 from the recovery It works fine but I can't flash any other rom without triggering the bootloop so how do I fix this? I can still access both the bootloader and the recovery and I don't want to go back to stock, just to ics roms. Thank you!
Just clear system, cache and userdata and flash viper ROM in recovery, reboot to bootloader then flash the boot.img from the viper ROM zip file.
Generally you get bootloops and such when on the wrong boot.img.
frdd said:
Just clear system, cache and userdata and flash viper ROM in recovery, reboot to bootloader then flash the boot.img from the viper ROM zip file.
Generally you get bootloops and such when on the wrong boot.img.
Click to expand...
Click to collapse
Thanks, so do you have to flash the img of every rom you want to use?

Question on updating to CM-10.2 from stock 4.1.2

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..

Cannot update bootloader

I am currently using bootloader 10.4.4.25 and cannot install the latest cm 11
And I am using CWR 6.0.4
Can anyone advise how can I update the bootloader so I can install cm11?
Thanks
Download the latest Asus firmware, unzip the file once resulting in another zip.
Copy that zip to your tabet and flash it in CWM (that you have everything you care about backed up off the tablet goes without saying, right?). That will get you onto the latest bootloader but also wipe your custom recovery.
Boot into fastboot, flash a CM11 compatible recovery.
Reboot
Boot into recovery, do a factory wipe and then flash the rom.
Thanks for the advise. I am downoading the latest firmware from ASUS website and will install it.
I am not sure how to flash a CM11 compatible recovery from fastboot. Can you give more details please? Shoudl I follow the root instruction from the ROM post and re-root the machine again?
Thanks in advance
berndblb said:
Download the latest Asus firmware, unzip the file once resulting in another zip.
Copy that zip to your tabet and flash it in CWM (that you have everything you care about backed up off the tablet goes without saying, right?). That will get you onto the latest bootloader but also wipe your custom recovery.
Boot into fastboot, flash a CM11 compatible recovery.
Reboot
Boot into recovery, do a factory wipe and then flash the rom.
Click to expand...
Click to collapse

Categories

Resources