Flash "Temporary" CWR, becomes Permanent? - Samsung Galaxy Nexus

After following Droid-Life.com's guide on unlocking the bootloader, and then rooting the phone, after installing Rom Manager and flashing CWR through the manager, the recovery truly becomes permanent.
This causes problems because if I try to install an OTA update I get the red error because I'm not running stock recovery.
I guess my question is, is there a stock recovery.img that I'm able to flash through fastboot in order to get rid of CWR and get back stock recovery? Thanks!

If you can't follow my train of thought: When I want to root, I need to install SU.zip through CWR
push su.zip thru adb to phone > flash CWR "temporarily" > install su.zip > reboot
But the problem is, the next time I try rebooting to recovery, I get CWR, not stock recovery like I wanted. And that stock-recovery.p file is still on my phone and alive.

http://forum.xda-developers.com/showthread.php?t=1399879

Shortly after posting, I just answered my own question. I downloaded the stock images from Google, found the recovery.img image in there, simply flashed with ADB and worked great. Thanks for your attention

Related

Recovery and Flash_Image not working

I rooted my phone and was able to access Clockwork, but since then I have not been able to boot into recovery. I have gone through many troubleshooting steps including trying to use Rom Manager by clockworkmod to flash a new recovery, trying to go through to root process again and trying to use terminal and adb to flash a recovery. When I try flash_image, it says "flash_image: not found". Rom manager won't boot into recovery. My phone sticks at the exclamation screen when I try to manually boot into recovery. I can't use update.zip because that requires that you have the ability to user recovery. I haven't been able to find any other way to flash a recovery mod onto my system. Is there any way that I can just get the files that are supposed to be installed on the phone and the locations they are supposed to go to so I can just flash them one at a time? Or does anyone have another possible solution?
ESPRDIAG.zip
ESPRDIAG.nbh
ESPRIMG.zip
ESPRIMG.nbh
All those files are showing as missing when I start bootloader.
I think you need to re-root your device if not first. If it is rooted whatever rom you have selected to install needs to be in the root directory of your sdcard. Again before you can flash any rom you need to be rooted and have access to clockwork.
I hope that helps if not try this
http://forum.xda-developers.com/showthread.php?t=702973&page=103
Go through the root process again to get back to clockwork to flash a new ROM. Or follow the process to flash the engineering rom, which will save you from having to do all of that to get back in to clockwork recovery each time.
Finally got it to work, but is there any way that I can get it to go into Clockwork every time I boot into recovery without having to flash it again?
Flashing the engineering rom will enable you to leave update.zip on the root of your sdcard and just flash update.zip eachtime you get to recovery to get into clockwork. Or if you have flashed eng build you can start using rom manager to boot into clockwork recovery. Afaik that's the only way to boot into clockwork.
SySfS

[Q] Need Help with Recovery!!

I have succesfully root my girlfriends slide and gained s-off thru Aplha . but i tried to flash cwm 2.5 thru fastboot like an idiot thinking this was the proper way of permanently flashing new recovery and now cannot get into recovery neither factory with triangle or cwm. How do i fix this or will i have to unroot bascially and start over to get the recovery .img again? Also, who can help with permanently flashing cw recovery so that i do not have to use the update.zip method.?
poor2rican1 said:
I have succesfully root my girlfriends slide and gained s-off thru Aplha . but i tried to flash cwm 2.5 thru fastboot like an idiot thinking this was the proper way of permanently flashing new recovery and now cannot get into recovery neither factory with triangle or cwm. How do i fix this or will i have to unroot bascially and start over to get the recovery .img again? Also, who can help with permanently flashing cw recovery so that i do not have to use the update.zip method.?
Click to expand...
Click to collapse
Did you try to fastboot flash the update.zip? That's not good, you should've flashed the cw2.5 .img file. No, you don't have to reroot or res-off, but download the .img file for the latest clockwork recovery on koush's website, for our device. Then, on your computer, while in fastboot mode and plugged into usb, type
fastboot flash recovery filename.img
obviously replacing filename.img with the actual file name/location.

Frustrated!

Alright I have a problem. I bought a used G2 which had already been rooted. I installed CM7 on it and it worked fine except for wi-fi (little did I know the awful path this was about to send me down). I thought this might be because I was using Recovery 2.5, so I switched to recovery 3.0 and flashed CM7 again, same problem. I found out you have to reboot the phone after your first boot to get wifi working a lot of time so that was my fault, I should have researched that more thoroughly from the beginning and I would have avoided this whole ordeal. Anyway after this I wanted to downgrade to Recovery 2.5 again because there are a lot of zips that can't be installed through recovery with 3.0. So I tried to do that and couldn't, I looked around and found that was probably because I didn't have eng s-off which I didn't, I had s-off but not engineering.
So I tried getting that working, this took forever because I couldn't figure out if I was supposed to use the OTA or preOTA.ko file. I discovered my phone was post OTA so I tried using that file and didn't receive the correct error message (Function not implemented), but instead some other error. After researching this and trying to find out why that could be or what exactly the OTA part of it does without a definitive answer I decided to go ahead and run the terminal command for eng s-off anyway feeling relatively safe. This succeeded and I was happy that I'd finally figured everything out! Wrong. I had eng s-off. Also I was able to downgrade the recovery again through terminal, however after doing this and trying to boot into recovery it would just stay at the white HTC symbol. Fine, maybe I can't downgrade to 2.5 after installing CM7. So I upgraded Recovery back to 3.0 and used it to install CM6.1.
After doing this I went into ROM manager and dropped myself back down to recovery 2.5.1.3. Now whenever I try to reboot into recovery I immediately get taken to fastboot. I've tried searching for any others having problems like this without success and I'm extremely frustrated. I tried using different versions of recovery 2.0, I tried updating to recovery 3.0 all without any success, still just boots into fastboot if I try to get into recovery. Please tell me someone knows what my issue could be and how I can fix it, meanwhile I'll continue trying to work it out and let you know if I do. Thankyou.
EDIT: It appears for whatever reason rom manager may actually not be flashing a recovery, if someone could post the 2.5.1.3 recovery.img that would be wonderful
I dont know if you have Andriod SDK set up and if you know how to use Fastboot, but since you have an ENG. Hboot you can use fastboot to flash a new recovery image onto your phone, you can download the CWM Recovery 3.0.0.5 .Img from HERE. Place the new recovery image into the same folder your Fastboot.exe file is and run this command:
Code:
fastboot flash recovery <name of recovery.img>
There is also a way to flash a new recovery using flash_image method from you phone, so you can download a new recovery from the link above and use this method to flash it.
2.5.1.3 recovery is obsolete, the new 3.0.0.5 recovery supports all roms 2.2. and 2.3.
joemm said:
I dont know if you have Andriod SDK set up and if you know how to use Fastboot, but since you have an ENG. Hboot you can use fastboot to flash a new recovery image onto your phone, you can download the CWM Recovery 3.0.0.5 .Img from HERE. Place the new recovery image into the same folder your Fastboot.exe file is and run this command:
Code:
fastboot flash recovery <name of recovery.img>
There is also a way to flash a new recovery using flash_image method from you phone, so you can download a new recovery from the link above and use this method to flash it.
2.5.1.3 recovery is obsolete, the new 3.0.0.5 recovery supports all roms 2.2. and 2.3.
Click to expand...
Click to collapse
Thanks, yes I know how to use fastboot, and I did install the 3.0.0.5 recovery earlier, the problem with recovery 3 is that a lot of older zips don't support it and I'd really like that functionality. Any idea on where I might be able to find the older recovery? Thanks in advance
I have a copy of the 2.5.1.3 recovery, I put it in my dropbox for you:
http://dl.dropbox.com/u/17831112/recovery.img
Heres a MD5 checksum for it:
0C9C47FC09460DB17EC4BDA5F4F97A12
Update for anyone else frustrated by this, I found a tool that will attempt to update your zip to the new edify format. I've tried it on a couple zips so far and it worked both times, they just added support for the G2. Here's the link
http://forum.xda-developers.com/showthread.php?t=903598

Recovery image would't update/install.

Hi everyone,
I've done a LOT of reading/searching, but since I can't find sulution decided someone could help.
Just to avoid future questions:
>My Desire is rooted.
>I tried using fastboot (Error: - not allowed)
>I tried using adb (I get an error that /system/bin/sh cannot be found).
>I tried Unreavoked3, but since the phone is rooted, the recovery doesn't isntall.
>I tried ROM Manager. It says the recovery is up to date, but when you boot it, it is stock.
>I'm using original USB cable supplied with the phone.
The only way I get into CWM recovery is flashing update.zip on my sdcard (fakeflash?).
My question are:
1. Why i cant access shell via adb?
2. How should i flash recovery?
Thank You in advance.
So if you turn the phone on whilst holding the volume down button and then select Recovery it doesn't boot into the custom Recovery?
No, it boots into stock recovery.
I just use the Android Flasher Utility (here). Really quick and painless, but you need s-off though.
I'm quite curious, how are you rooted without a custom recovery?
Maybe I don't get it, I bought the phone about a year ago and rooted using unreavoked utility. The recovery I get to gives me 4 options. Text is in blue colour, reboot, apply update.zip and wipe options. What I do, is apply update.zip so i get into CMW recovery.
If you rooted with unrEVOked it flashes CWM. If you've never had that you're not rooted
I'd go back to 100% stock with an RUU suitable for your phone and then root again
EDIT: You weren't rooted and then accepted an OTA update did you?
I think I didn't. So if I:
1. Do a nandroid backup now, I have custom rom installed.
2. Then go back to stock RUU.
3. Root the phone.
Can I do a nandroid restore so I don't have to install everything back again?
EDIT: But I have Superuser app, and if I enter Terminal, type "su" I get root privileges. How can I not be rooted?

[Q] I can't update via OTA

Hello everyone
I want to update mi htc one via OTA but when the phone reboots enter to teamwin recovery i want to know how to updateit my firmware version is 1.12.599.20
Thank you and sorry for my bad english​
daga2448 said:
when the phone reboots enter to teamwin recovery​
Click to expand...
Click to collapse
Enough said. You need stock recovery to do OTA.
Try to locate OTA file and flash it manually
BerndM14 said:
Enough said. You need stock recovery to do OTA.
Click to expand...
Click to collapse
how do i install stock recovery without lossing root??
daga2448 said:
how do i install stock recovery without lossing root??
Click to expand...
Click to collapse
You won't lose root if you have stock recovery.
Do you even have a stock recovery? If so, just place it inside the adb folder, open the command prompt change directory to adb folder, boot into bootloader mode and type fastboot flash recovery name_of_recovery.img The same way you probably got custom recovery onto the device.
Won't lose root because of stock recovery. You'll lose root because of the OTA though, but even then it's easy enough to regain root. You can then either flash back the custom recovery OR boot the custom recovery. I'd suggesting booting the custom recovery that way you can make a nandroid backup of the updated system before you flash anything again.
fastboot boot custom_recovery_name.img If you're using TWRP then it probably won't make a backup of the stock recovery, CWM/Philz will work better for the nandroid. After you made a backup(If you choose to make a backup, again strongly suggested) then you can flash a custom recovery again.
Was it really necessary to post in a massive font?

Categories

Resources