I've now flashed the recovery using both rom manager and fastboot 4 times, and each time it works fine the very first time after, but then the 2nd and succeeding times after lead to the little android and then the triangle and exclamation point. This is with the latest clockwork 3.1.0.1 on a Nexus S 4G. I have no idea what the problem could be and I'm hella frustrated.
Thanks for any help you can provide in advance.
http://forum.xda-developers.com/showthread.php?t=856999
Trying this, will update with results after I just try flashing cyanogen.
EDIT: UPDATE problem solved after flashing cyanogen. Sorry for taking up extra space. Here's the fix incase others were searching.
-Flash recovery
-Enter recovery while it's still working, nandroid backup, wipe, flash cyanogen.
-Done
If that doesn't work use the commands from that link.
The problem is solved cause CM fixed it for you.
If you don't have a ROM fixing it for you (eg stock Android), you need to rename the install-recovery.sh inside /system/etc to something else to make a recovery stick through reboots. Renaming system data requires root/super user.
The order would be:
Flash recovery
Flash su.zip
Boot into Android
Use a root explorer (eg Super Manager or Root explorer) to rename the file above
Flash recovery again
Related
hey i rooted my nexus s and installed clockworkmod 3.0.0.0
i have installed rommanager 3.0.0.2
when i open the rommanager it says that there is a update to version 3.0.0.5
i tap on install after a wile it says that is installed correct
BUT
when i boot into recovery ... it dont work ... i boot the nexus s again an step back to clockwork 3.0.0.0 an i can boot to the recovery ...
so what is wrong?????
thx
footballpics.info said:
hey i rooted my nexus s and installed clockworkmod 3.0.0.0
i have installed rommanager 3.0.0.2
when i open the rommanager it says that there is a update to version 3.0.0.5
i tap on install after a wile it says that is installed correct
BUT
when i boot into recovery ... it dont work ... i boot the nexus s again an step back to clockwork 3.0.0.0 an i can boot to the recovery ...
so what is wrong?????
thx
Click to expand...
Click to collapse
you may just have to install CWM manually like you first did
ok ok ... i will do that ... thx for the hint
BUT
what for is the updatefunction in the rommanager then if it is not working???
slowz3r said:
you may just have to install CWM manually like you first did
Click to expand...
Click to collapse
You could probably flash it from fastboot, but the OP is correct, the 3.0.0.5 update "breaks" ROM Mgr and CWM.
With 3.0.0.0 you can open ROM Mgr, then select Reboot To Recovery, and the phone will quickly reboot into CWM recovery.
Upgrade to 3.0.0.5 and when you select Reboot To Recovery, the phone gets stuck on the white Google on black background screen. A battery pull is required.
Downgrade to 3.0.0.0 and the expected behavior returns.
Seems to be a bug to me with 3.0.0.5. Need to let koush know.
To the original poster, you're aware that if you're on Android 2.3.1 that any fresh normal boot of the phone restores the stock recovery to the device unless you remove/rename the appropriate script in the /etc folder, right?
i have Android 2.3.1
which file i have to remove/reneame in dhe "/etc" folder?
is this different to the way to update the clockwork as on the HTC Desire?
thx
footballpics.info said:
i have Android 2.3.1
which file i have to remove/reneame in dhe "/etc" folder?
is this different to the way to update the clockwork as on the HTC Desire?
thx
Click to expand...
Click to collapse
/etc/install-recovery.sh
Be aware there are some who think it's risky. I'd advise reading this thread before proceeding, at least the last few pages of it.
I'd also be leary of messing with the recovery until you're sure you're able to get into at least CWM to make fixes if needed (e.g., have CWM 3.0.0.0 working).
Also, I just went to the Market, found Rom Manager (Premium) and scrolled down to the email the author link and sent a bug report. I'm not encouraging spamming him with complaints, but those anxious for a fix might want to report the bug as well if they have it.
i installed Clockwork again from: http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html (Nexus S 3.0.0.5)
an installed it manualy with: fastboot flash recovery recovery.img
after taht i loaded the recovery and it told me that i have 3.0.0.5
rommanager told me i have 3.0.0.0 and there is a update for me *g*
but when i tryed to reboot an go to the recovery again its not possible ... i got an error and had to hardboot - its possible to load android ...
so now ... whats the problem ... i downloaded the right CW and installed it like i did 1st. time ...
i read the link you gave me - found that:
Originally Posted by Luxferro
well in order to prevent your recovery from returning to stock, you need to use root explorer, or another method to rename the following file:
/etc/install-recovery.sh
rename it to something like install-recovery.sh.old
now when you phone boots, it won't be able to run that script to replace your recovery.
That's all there is to it. It's that simple. Root explorer is a file explorer with root access. When you browse to the file, click the button to enable read-write access in root explorer, and then long press on the filename and rename it.
...............................................
when i have 3.0.0.0 as recovery and i reboot and then reboot to recovery anything is working i kan go to the recovery menue - i have root rights and i can install what i want .. so what is set back with this "bootscript"?
for me everything sounds a little bit wierd ... i am sorry ...
thx
flo
My 3.0.0.5 recovery wasn't there as well. I reflashed it in Rom Manager, and then it worked.
Rom Manager had a problem on Droid 1, where you had to flash the recovery a couple times. I'm hoping that bug doesn't apply to Nexus S as well.
so now its not possible to boot into the recovery ... its 3.0.0.0 or 3.0.0.5 ...
ok i renamed this /etc/install-recovery.sh to /etc/install-recovery.sh.sav now the update seems to work ...
I was running 3.0.1 unlocked/rooted, Tiamat's 1.4.1 kernel. I followed the steps to update to 3.1 from here, and had no issues what so ever. This was earlier this week, and today I was going to run fix permissions in recovery. I used Quick Boot (also tried Reboot to Recovery in ROM Manager) to boot to recovery, and I got to the Android with the exclamation point...
I tried sending the modified 3.0.2.8 recovery listed in the Dev Forums using fastboot commands, and everything went smooth with no errors, but still got the Android/exclamation point.
I tried reflashing recovery via ROM Manager, and it wouldn't pop up anything, so I uninstalled/reinstalled, and the flash of recovery worked. Boom! Recovery is back! So I can do what I need (run fix permissions), and rebooted the device.
I try to reboot into Recovery again, back to Android with exclamation point. Any thoughts here as to why I must do this, and thoughts to what I can try to make Recovery "stay"?
Thanks!
RMarkwald said:
I was running 3.0.1 unlocked/rooted, Tiamat's 1.4.1 kernel. I followed the steps to update to 3.1 from here, and had no issues what so ever. This was earlier this week, and today I was going to run fix permissions in recovery. I used Quick Boot (also tried Reboot to Recovery in ROM Manager) to boot to recovery, and I got to the Android with the exclamation point...
I tried sending the modified 3.0.2.8 recovery listed in the Dev Forums using fastboot commands, and everything went smooth with no errors, but still got the Android/exclamation point.
I tried reflashing recovery via ROM Manager, and it wouldn't pop up anything, so I uninstalled/reinstalled, and the flash of recovery worked. Boom! Recovery is back! So I can do what I need (run fix permissions), and rebooted the device.
I try to reboot into Recovery again, back to Android with exclamation point. Any thoughts here as to why I must do this, and thoughts to what I can try to make Recovery "stay"?
Reflash cmw afterward and it should stay.
Thanks!
Click to expand...
Click to collapse
Use your computer to do this:
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
or alternately, you can use a root file manager such as root explorer to remove the files (I personally just renamed mine so they wouldn't be recognized. I don't like burning bridges).
Re-flash cmw afterward and it should stay.
Thanks! That worked, you the man! I renamed them as well, as I don't want to burn bridges either.
9020 – Eur model. Was 2.3.3, but upgraded to 2.3.4 after one day.
I followed the Unlockr guide, and followed the following, before deviating!!Can someone help me recover from this recover from this?
Bootloader successfully unlocked
Then it all went pear shaped!!
IV. Flash a Custom Recovery Image
1. Download the custom recovery image and save it to your computer: DONE
ClockworkMod Recovery for Nexus S
2. Copy the recovery.img file inside the tools folder of the sdk (so it is in the same folder as fastboot.exe) DONE
3. Then in the command prompt that should still be open, type the following with hitting enter at the end of
each line:
fastboot flash recovery recovery.img DONE
This is where for some insane reason (moment of madness) I deviated and don’t know how to get out of it. I rebooted and it went into clockwork mod. I couldn’t get out of it so I thought I would flash a backed up nanroid rom (2.3.1) which I down loaded. Big mistake, as it boots then freezes after 1minute.
I then booted into recovery (clockwork mod) and wiped cache, and pretty much everything else. Now the phone hangs on the google start page, recovery (clockwork mod) says there’s misc missing, cache missing etc....Cant flash any new rom. Can get to recovery but that’s about it.
I need some help to fix it!
mittu1 said:
9020 – Eur model. Was 2.3.3, but upgraded to 2.3.4 after one day.
I followed the Unlockr guide, and followed the following, before deviating!!Can someone help me recover from this recover from this?
Bootloader successfully unlocked
Then it all went pear shaped!!
IV. Flash a Custom Recovery Image
1. Download the custom recovery image and save it to your computer: DONE
ClockworkMod Recovery for Nexus S
2. Copy the recovery.img file inside the tools folder of the sdk (so it is in the same folder as fastboot.exe) DONE
3. Then in the command prompt that should still be open, type the following with hitting enter at the end of
each line:
fastboot flash recovery recovery.img DONE
This is where for some insane reason (moment of madness) I deviated and don’t know how to get out of it. I rebooted and it went into clockwork mod. I couldn’t get out of it so I thought I would flash a backed up nanroid rom (2.3.1) which I down loaded. Big mistake, as it boots then freezes after 1minute.
I then booted into recovery (clockwork mod) and wiped cache, and pretty much everything else. Now the phone hangs on the google start page, recovery (clockwork mod) says there’s misc missing, cache missing etc....Cant flash any new rom. Can get to recovery but that’s about it.
I need some help to fix it!
Click to expand...
Click to collapse
If you have recovery, then you are fine. Just flash a rom. Flash the stock rom if you want. Any rom. Then you should be fine.
Sorted!! The solution was found here:
http://forum.xda-developers.com/archive/index.php/t-992114.html
New ROM up and running, no issues so far.
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).
Hi guys!
Yesterday I successfully rooted my NS (it is a European SLCD model with stock 2.3.6 on it) following the newest guide on nexusshacks.com. So I ended up with TWRP recovery.
Then I thought the easiest to install CM is via Rom Manager. Therefore I had to change recovery for CWM. (I flashed the latest one.)
And here comes my question: why am I unable to flash CM?
First I tried it in Rom Manager, after wiping everything and rebooting system nothing happens, except for a big yellow exclamation mark.
Then I downloaded the proper CM myself and I tried to do the whole process manually in recovery menu. After wiping and choosing update from SD card I get a message like the process is aborted.
I also tried with an older CWM and with other ROM.
Any suggestions?
Thanks a lot
Sent from my Nexus S using XDA App
Boot into bootloader, then flash recovery via fastboot.
fastboot flash recovery recovery.img
stock firmware will rewrite your recovery after each boot. flash recovery then flash this right after.
Follow what SEAN SAys..............He is a Master in all these , and he helped me with details to root, flash cwm, make it sticky and flash custom ROMS.
It took me 5 minutes to do all those , and Now I am switching Roms like I switch my underwears every day twice.
I must say, Sean has the best possible way which is like a finger click.