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 ...
Related
Hi guys,
For the last 2 nights I´ve been trying to get a CG Mod 6.1 on my HTC Magic 32B.
I have rooted it with onclick-root method and tried a bunch of things like ROM Manager and flashing via fastboot (brings up "remote not allow" error). Nothing worked out.
Here are the facts:
HTC Magic with OTA upgrade to 2.2.1
hboot: 1.33.0013
radio: 2.22.28.25
Rooted with Oneclick method
Do I need a goldcard? How do I do that? What hboot Version do I need? What Radio do I need? What do I have to do first?
Are you certain the Root took? Are you seeing the Superuser icon in your app drawer?
When you were using Rom Manager did you flash, or attempt to flash a custom recovery, and if so did it install ok?
What happened when you tried to flash a ROM using Rom Manager?
I'm sure we'll get to the bottom of this
Yes, rooting has worked...Icon is there everything looks fine.
With the Rom Manager i tried to install "update-cm-6.1.0-DS-2708port_S" aswell as the "update-cm-6.1.0-DS-signed". Both did not work.
I still can boot to my standard OTA 2.2.1
Try wiping your phone in recovery and then install the rom
hang on a minute...
it sounds like you haven't installed a custom recovery before trying to flash the rom. Can you clarify...have you actually done this yet?
The process should go root/recovery/nandroid backup/rom in that order.
yeah you re right...i dont have a custom recovery
i just tried to load "recovery-RA-sapphire-v1.7.0G.img" on the console
su
# flash_image recovery /sdcard/recovery.img
does not work, i get: flash_image: not found
USB debugging is enabelde
3rd party software is enabeled
is there another way to get flash the recovery ?
Rom Manager!
At the top you should have the option to flash clockworkmod recovery. Select that; it will run and then the phone should reboot. I usually do it again to confirm. If it installed correctly the first time you'll get a pop up saying that it is installed.
If all goes to plan select 'backup current rom' from within Rom Manager. This is a nandroid backup and can be re-installed from recovery any time you wish to return to stock.
NOW you are free to install a custom ROM of your choice
Post back if you encounter any issues.
I have tried that. It flashes, gives my a popup that it installed correctly.
But it does not reboot.
When i choose restart in recovery mode it boots up the phone an gets stuck on the vodafone logo. BatteryOut reboot and i am back at the good old 2.2.1 OTA
do i have to wait long?!? cant be, right? do i need to hold down any buttons?
If you try the backup option now you'll soon find out if the recovery did indeed install ok. (it won't backup if the recovery isn't installed)
i restarted...flashed the recovery again. got popup confirmation. then chose backup rom and got stuck at the vodafone logo
You must be pretty frustrated by now. It might be time to start asking for more help in the dev section of the Magic forum HERE.
I hope that somebody has the answer!
Thanks for your help...i ll see if someone else has any ideas.
roodee said:
yeah you re right...i dont have a custom recovery
i just tried to load "recovery-RA-sapphire-v1.7.0G.img" on the console
su
# flash_image recovery /sdcard/recovery.img
does not work, i get: flash_image: not found
USB debugging is enabelde
3rd party software is enabeled
is there another way to get flash the recovery ?
Click to expand...
Click to collapse
Are you are aware that the command you need to type will be
flash_image recovery /sdcard/recovery-RA-sapphire-v1.7.0G.img
The command points to the exact file name on your sd card so if you just wrote flash_image recovery /sdcard/recovery.img and the recovery file was not called "recovery.img" it would not know what to look for.
I'm not sure if this is what you have or whether you just copied and pasted from a guide, but I just thought I'd put it out there in case that is the case.
Hope this helps.
I just finished rooting my wifes phone and had Rom Manager installed CWM yet when I reboot into recovery it starts 3e instead. I also downloaded SGS Tools but dont see a way in there to set the recovery to reboot into.
kevria said:
I just finished rooting my wifes phone and had Rom Manager installed CWM yet when I reboot into recovery it starts 3e instead. I also downloaded SGS Tools but dont see a way in there to set the recovery to reboot into.
Click to expand...
Click to collapse
'
You need to install the modded 3e and then cwm recovery.
As per this thread http://forum.xda-developers.com/showthread.php?t=909213 thanks.
kevria said:
As per this thread http://forum.xda-developers.com/showthread.php?t=909213 thanks.
Click to expand...
Click to collapse
I was able to install the hacked 3e recovery but when I go through Rom Manager and tell it to Flash CWM it says it does (tried it three times) yet when I reboot into recovery it still comes up as the 3e hacked.
I figured it out. The flashing was creating an update.zip that then had to be installed. All set with CWM.
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'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
hi there
when i try to install the new recovery with:
1.: Rommanager it makes the update but i cant boot into recovery
2.: i tryed to install it with: "flash_image recovery /sdcard/name-of-recovery.img"
but both ways are not working ..
so what to do?
thx
flo
There is now 5.0.1.0 update posted on koush's page (Google Nexus S):
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.1.0-crespo.img
Click to expand...
Click to collapse
You can open Android Terminal app and type the following commands:
su
flash_image recovery /sdcard/recovery-clockwork-5.0.0.0-crespo.img
reboot recovery
Click to expand...
Click to collapse
I was able to update via ROM Manager successfully though (it will take quite awhile to switch from Google logo to boot animation on your first reboot).
i allready tryed that terminal thing .. last time it worked (3.0.0.5 to 3.0.2.4) but this time .. no chance ..
the update with rom manager dindnt work on my Nexus S anyways .. i dont know why ..
i tryed that with different roms ..
i had such a problem on my Desire like a year ago and than i had to delete a file .. i cant remember but is it possible that i have to delete the file here too?
thx
flo
ok .. in this Thread:
http://forum.xda-developers.com/showthread.php?t=1039584&page=5
i found this:
"anyone having issues with recovery flashing open rom manager and press menu and go to settings. now check erase recovery. this will wipe the recovery partition prior to flashing. this makes the recovery img flash correctly 99% of the time. if not on the main page in rom manager press menu and clear your download cache. this will remove all the files and folders inside /sdcard/clockworkmod/ so you will los e any roms downloaded. then click to flash the recovery again. it will redownload the recovery and reflash. you should still keep the erase option in settings checked. if it still does not flash correctly try flashign twice in a row. if that doesnt work fastboot erase recovery . and fastboot flash recovery \path\to\recovery\here.img"
delete recovery BEFOR flashing a new is working here ...
Flash_image gui by Joeykrim will work great for you
I did an update to v5 and couldn't boot into recovery too, but that was because i did it by the usual hardware buttons Power + VolumeUp.
Then by accident, i was able to boot into recovery, and that is by the "Reboot into Recovery" menu in ROM Manager itself.
Have you tried this method of rebooting yet?
the new cwm flashed fine for me no issues.
I can no longer reboot into recovery after updating to CWM5.01. Tried using rom manager and terminal emulator with no luck. Also tried reverting back to my old recovery and still nothing. The above steps posted didn't work either. Someone please help. I can't restore any backups because I can't boot into recovery.
Edit: Working and fixed by pushing it through adb