Database Info

cant load recovery

Hey guys..
I just today rooted my lovely Nexus S, 9023 or what its called (non branded or nothing)
But i cant load recovery.. went fine when i rooted it, but now that i want to load an custom rom it fails.. i followed this guide to root: http://forum.xda-developers.com/showthread.php?t=883032
Anyone have some ideas??
I just get a android logo and triangle + ! in it.. as error.. (
Best regrads
n0ta

Just tested with ROM Mananger, it can backup just fine.. as soon i choose a ROM to install it loads recovery and fails, just like when you do it manually.

n0ta said:
Just tested with ROM Mananger, it can backup just fine.. as soon i choose a ROM to install it loads recovery and fails, just like when you do it manually.
Click to expand...
Click to collapse
Sounds like stock recovery installed itself. If you are rooted remove/rename /etc/install-recovery.sh then reflash cwm manually or through rom manager.
Sent from my Nexus S 4G using XDA Premium App

I have had this happen on my NS4G. I know they are a little different, but it seems like you are having the same thing happen that I did and to solve it, I open Windows command prompt(or terminal depending on you OS) and fastboot flash recovery (insert recovery.img name here) and reflashed the recovery partition with clockwork. Very easy fix. Just make sure you boot straight into recovery after flashing and flash the Rom you want to flash before booting back into stock(also make a nandroid before that). After that you shouldn't have any more problems unless you unroot. There must be a small glitch somewhere when flashing the clockwork doesn't fully erase stock recovery partition.

krohnjw said:
Sounds like stock recovery installed itself. If you are rooted remove/rename /etc/install-recovery.sh then reflash cwm manually or through rom manager.
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
Works now thanks all to both of you.

n0ta said:
Works now thanks all to both of you.
Click to expand...
Click to collapse
Pretty common lately...Android for Nexus S recovers its recovery if it is changes...
"You dawg, we heard you like recovering your recoveries, so we made recovery recover in recovery." and all that...

bender_123 said:
Pretty common lately...Android for Nexus S recovers its recovery if it is changes...
"You dawg, we heard you like recovering your recoveries, so we made recovery recover in recovery." and all that...
Click to expand...
Click to collapse
The Nexus one did the same thing. Most OTAs verify / replace this file. It's easy enough to deal with if you're unlocked and rooted.
Sent from my Nexus S 4G using XDA Premium App

This is about the third or fourth time this question has come up over the past week...

bender_123 said:
This is about the third or fourth time this question has come up over the past week...
Click to expand...
Click to collapse
I assure you it won't be the last.
Sent from my Nexus S 4G using XDA Premium App

[Q] download mode not working...

I tried searching, but the search is down?
I have spent several hours looking.
I used odin (phone went into download mode without issue) to put my phone back to stock so I could get the ota update.
Went back into download mode with Odin to install CWM, this "passed" and after a restart my phone went into samsung recovery, not CWM.
Now my phone will not go into download mode? I tried different cable, ports, etc.
any help?

so what is it doing since it's not going into download mode.

it wouldn't do anything, I finally reinstalled the drivers and after holding down the power and volume - let go... nothing! push the volume - twice and it went into download mode. Odin recognizes it and goes through the motion, but the phone has a AX_timeout in red at the top left corner of the screen?
Odin continues and say's passed, but when I try to reboot into CWM it hangs on the samsung logo.
It will not boot into recovery, but it will start the phone and everything seems to work.
im using odin 1.83 / windows 7 64bit.

Remove the battery, put the phone in download mode, put the battery back in, and flash CWM. Before you fully boot the OS, flash a custom kernel. If you don't flash a custom kernel, the default kernel will overwrite CWM with the default recovery.

Morrisme said:
it wouldn't do anything, I finally reinstalled the drivers and after holding down the power and volume - let go... nothing! push the volume - twice and it went into download mode. Odin recognizes it and goes through the motion, but the phone has a AX_timeout in red at the top left corner of the screen?
Odin continues and say's passed, but when I try to reboot into CWM it hangs on the samsung logo.
It will not boot into recovery, but it will start the phone and everything seems to work.
im using odin 1.83 / windows 7 64bit.
Click to expand...
Click to collapse
I would try using odin v1.82... My experience with this tool has told me that our charge doesnt always "play nice" with other versions... Also try redownloading the latest CWM, you could of had a bad download.
Sent from my SCH-I510 using XDA

Cilraaz said:
Remove the battery, put the phone in download mode, put the battery back in, and flash CWM. Before you fully boot the OS, flash a custom kernel. If you don't flash a custom kernel, the default kernel will overwrite CWM with the default recovery.
Click to expand...
Click to collapse
Also in my experience I have had CWM recovery with the stock kernel... So something seems funny, stock kernel must not always overwrite custom cwm... Hmmmm. Who can help us here....????
Sent from my SCH-I510 using XDA

stebomurkn420 said:
Also in my experience I have had CWM recovery with the stock kernel... So something seems funny, stock kernel must not always overwrite custom cwm... Hmmmm. Who can help us here....????
Sent from my SCH-I510 using XDA
Click to expand...
Click to collapse
If you happen to flash a ROM that doesn't include the script that the kernel calls for the overwrite, then you could have ended up with CWM on a stock kernel.

stebomurkn420 said:
Also in my experience I have had CWM recovery with the stock kernel... So something seems funny, stock kernel must not always overwrite custom cwm... Hmmmm. Who can help us here....????
Sent from my SCH-I510 using XDA
Click to expand...
Click to collapse
There's a script, can't remember where it's at, that is run at boot to replace the recovery. If that script is not there, it doesn't get replaced. All custom roms have it removed.

shrike1978 said:
There's a script, can't remember where it's at, that is run at boot to replace the recovery. If that script is not there, it doesn't get replaced. All custom roms have it removed.
Click to expand...
Click to collapse
/system/etc/install-recovery.sh

Hmmm... So your saying there basically wasnt a way for me to have cwm with stock rom/kernel with root... I could have swore I had that setup at some point...
Sent from my SCH-I510 using XDA

stebomurkn420 said:
Hmmm... So your saying there basically wasnt a way for me to have cwm with stock rom/kernel with root... I could have swore I had that setup at some point...
Sent from my SCH-I510 using XDA
Click to expand...
Click to collapse
There is, root, boot up, delete the script power off, re root and you're good
Sent from my DROID RAZR using xda app-developers app

stebomurkn420 said:
Hmmm... So your saying there basically wasnt a way for me to have cwm with stock rom/kernel with root... I could have swore I had that setup at some point...
Sent from my SCH-I510 using XDA
Click to expand...
Click to collapse
There is. You can download the Superuser CWM to your phone, flash CWM, boot immediately to CWM (don't let it boot normally), flash Superuser, and reboot.
At that point, if you desire, you can delete /system/etc/install-recovery.sh and reflash CWM if you want to keep it.

shrike1978 said:
There is. You can download the Superuser CWM to your phone, flash CWM, boot immediately to CWM (don't let it boot normally), flash Superuser, and reboot.
At that point, if you desire, you can delete /system/etc/install-recovery.sh and reflash CWM if you want to keep it.
Click to expand...
Click to collapse
You think this would work on the nexus... Seems its kind of a universal method...?
Sent from my SCH-I510 using XDA

[HELP] Why is EZ Recovery not working

Ok so I'm stock rooted and I want to install CWM 6.0.1.0, so I downloaded Ez Recovery from the market and also the apk from the original post here on XDA. But it will not install CWM. I tried all the options. Recovery, Hybrid, and Stock, but when I flash them and it says it was installed successfully I press reboot it takes me to stock recovery every time.
Whats the problem???
Is it possible someone could provide me with a link to the recovery img file or tell me how to fix this problem?
Thanks

This may be obvious, but are you selecting reboot recovery from ez app menu?

Yes, when I flash my recovery I press reboot

Have you run the superuser app initially? I had similar behavior in which it said it flashed but still had stock recovery. The initial run of superuser got things going and when I ran ez recovery again it asked for root permissions and worked as expected...
Sent from my SCH-I535 using Tapatalk 2

I saw you post this in beans thread but I didn't have a fix but then I remembered how I fixed this on my phone. Uninstall ez recovery and reinstall from market. There was a problem with the version numbers or something and this fixed that problem for me
Sent from my SCH-I535 using xda app-developers app

codertimt said:
Have you run the superuser app initially? I had similar behavior in which it said it flashed but still had stock recovery. The initial run of superuser got things going and when I ran ez recovery again it asked for root permissions and worked as expected...
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I was having the same issue as the OP and your advice did it for me! I went back to stock about 2 days ago and I was already getting bored with it.

codertimt said:
Have you run the superuser app initially? I had similar behavior in which it said it flashed but still had stock recovery. The initial run of superuser got things going and when I ran ez recovery again it asked for root permissions and worked as expected...
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Yep, that did it. Thanks.

RAYOCOM said:
Yep, that did it. Thanks.
Click to expand...
Click to collapse
Wondering if any of you guys have had the problem where it flashes the recovery successfully and you can reboot in CWM / TWRP just fine. Then once you get back into the system and try reboot recovery again, it goes straight to the stock recovery.
Is this normal? Do I have to flash the recover everytime?

There is something you need to do in recovery to make it persist, some option you need to select. I'm still not clear on what it is, because its been a long time since I used CWM. I hope someone will chime in with exactly what needs to be done to make it stick so I can be clear on it as well.

apacseven said:
There is something you need to do in recovery to make it persist, some option you need to select. I'm still not clear on what it is, because its been a long time since I used CWM. I hope someone will chime in with exactly what needs to be done to make it stick so I can be clear on it as well.
Click to expand...
Click to collapse
When you select reboot, it will tell you that it is reverting back to stock recovery unless you fix it. You scroll down and select yes and you are good to go.
Sent from my SCH-I535 using xda premium

This happened to me as well when I first rooted. I had to reboot a few times until the proper recovery booted. Now that I have flashed a Rom, CWM recovery boots properly every time.
----
I typed this with my thumbs.

Flashing roms with rom manager successfully

The first time I flashed a from I used NVFlash but after that I used rom manager to boot into recovery when I was on gb now I'm running ics and I just hold down the power button click reboot>recovery and flash rooms from there and it works is this normal? Cuz I heard ur suppose to ALWAYS use nvflash
Sent from my LG-P999 using xda app-developers app

Laxshanth said:
The first time I flashed a from I used NVFlash but after that I used rom manager to boot into recovery when I was on gb now I'm running ics and I just hold down the power button click reboot>recovery and flash rooms from there and it works is this normal? Cuz I heard ur suppose to ALWAYS use nvflash
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
So which is it? If you're always doing Power button > Reboot > Recovery you are booting into the NvFlash'd CWM recovery not ROM Manager

xBkKx said:
So which is it? If you're always doing Power button > Reboot > Recovery you are booting into the NvFlash'd CWM recovery not ROM Manager
Click to expand...
Click to collapse
Ohh ok thanks makes sense but what about when I use to be on gb I use to use rom manager
Sent from my LG-P999 using xda app-developers app

You can also use ROM manager to boot to recovery, the reason people advise against using the app altogether is because the fake flashing that ROM manager does.
ROM manager will boot into nvflash recovery successfully as long as you never flashed the fake recovery via ROM manager.
So again, if you never flashed via ROM manager, then holding power>reboot recovery = going to ROM manager and booting to recovery.

buru898 said:
You can also use ROM manager to boot to recovery, the reason people advise against using the app altogether is because the fake flashing that ROM manager does.
ROM manager will boot into nvflash recovery successfully as long as you never flashed the fake recovery via ROM manager.
So again, if you never flashed via ROM manager, then holding power>reboot recovery = going to ROM manager and booting to recovery.
Click to expand...
Click to collapse
Okayy that's why it works lol thanks alot!
Sent from my LG-P999 using xda app-developers app

Not that it matters, but I have always flashed both recoveries. It's not that Rom Manager "fake" flashes it, it isn't flashed on a persistent partition that can be reached via button combo. I use Rom Manager and it's "fake" recovery mostly for nandroids. In reality, there's literally 2 separate recoveries, albeit, one is worthless in any "no boot" situation. Other than that, it's fine to flash roms and what not, just always have both, never just R M.
[email protected]

mustangtim49 said:
Not that it matters, but I have always flashed both recoveries. It's not that Rom Manager "fake" flashes it, it isn't flashed on a persistent partition that can be reached via button combo. I use Rom Manager and it's "fake" recovery mostly for nandroids. In reality, there's literally 2 separate recoveries, albeit, one is worthless in any "no boot" situation. Other than that, it's fine to flash roms and what not, just always have both, never just R M.
[email protected]
Click to expand...
Click to collapse
Before I'm pretty sure I downloaded a rom and it didn't have rom manager so I downloaded it from the play store and went into recovery through that and flashed a rom? Or is that normal?
Sent from my LG-P999 using xda app-developers app

That's fine, what we're all trying to explain is that if you mess up and your phone won't boot normally, you won't be able to recover it with the Rom Manager recovery since it is only accessible through a working a ROM. This is why we Nvflash it on a persistent partition that can be accessed regardless if you have a working rom or not. There's no difference between the two recoveries, only where they are flashed.
[email protected]

buru898 said:
You can also use ROM manager to boot to recovery, the reason people advise against using the app altogether is because the fake flashing that ROM manager does.
ROM manager will boot into nvflash recovery successfully as long as you never flashed the fake recovery via ROM manager.
So again, if you never flashed via ROM manager, then holding power>reboot recovery = going to ROM manager and booting to recovery.
Click to expand...
Click to collapse
I agree. ROM Manager which should be named ROM Mangler has seriously messed up phones causing its victims many hours of panic and grief. Stay away from it.

Kinda off topic but if rom manager is so bad why is it included with custom roms? One of the first things i do is uninstall it with titanium backup
Sent from my LG-P999 using xda app-developers app

bamathafan said:
Kinda off topic but if rom manager is so bad why is it included with custom roms? One of the first things i do is uninstall it with titanium backup
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
Because it can be used to boot into Recovery, and it is useful for the purpose of organizing backups
Sent from my LG-P999 using xda premium

fail to flash clock work mod need help

so i went to this thread http://forum.xda-developers.com/showthread.php?t=2046439 to try to root my phone.
after going through the steps clock work recovery is not there im stuck with the default android one,
odin tells me im useing custom binary 2 every thing shows i did the first part correctly.
but yet i dont have the cwr mode when i restart with volume up + home + power
all help is appreciated
james
additional info
just restarted and saw os is at 4.0.4
my end goal is being able to use my galaxy s3 (from usa on verzion networkd) on the doco mo network in japan by useing there sim card

srgjames said:
so i went to this thread http://forum.xda-developers.com/showthread.php?t=2046439 to try to root my phone.
after going through the steps clock work recovery is not there im stuck with the default android one,
odin tells me im useing custom binary 2 every thing shows i did the first part correctly.
but yet i dont have the cwr mode when i restart with volume up + home + power
all help is appreciated
james
Click to expand...
Click to collapse
i am stuck at the same thing. it keeps going to the stock recovery area not cwm

If you achieved root then why not just download ROM manager (play store) and flash CWM through the app or if you want TWRP instead which I recommend the get the goo app from the play store and flash TWRP through that app in the same manner.
Sent from my SCH-I535 using xda app-developers app

WettbackMartyr said:
If you achieved root then why not just download ROM manager (play store) and flash CWM through the app or if you want TWRP instead which I recommend the get the goo app from the play store and flash TWRP through that app in the same manner.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
im doing the phone rebel root method and i done the steps in odin but when i go to install the last step of the root it needs cwm and my s3 will not go into cwm. i even installed cwm twice now

Are you making sure to boot straight into cwm from Odin?

tallgrasshawk said:
Are you making sure to boot straight into cwm from Odin?
Click to expand...
Click to collapse
im sorry not sure i know how to do that one. i flashed the vralec file and the cwm part but once that is down it says to boot into cwm recovery and my s3 wont let m do that part
i have done it before then i soft bricked my phone so im rerooting it and im stuck trying to get the last step installed

WettbackMartyr said:
If you achieved root then why not just download ROM manager (play store) and flash CWM through the app or if you want TWRP instead which I recommend the get the goo app from the play store and flash TWRP through that app in the same manner.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
EZ Recovery works well too...
Sent from my Eclipsed Galaxy SIII

Yes forgot about that one. Thanks! :thumbup:
Sent from my Liquidy SuperNexus using xda-developers app