I know this is very basic, but I rooted the phone and now have to put clockwork on the phone. so the question is, do i use the one click clockwork thing?
what about the rom manager version, can you flash that with a rooted system through normal recovery? or is it like no matter what I need 1 click clockwork on the phone before putting on a kernal that will have clockwork in it?
robl45 said:
I know this is very basic, but I rooted the phone and now have to put clockwork on the phone. so the question is, do i use the one click clockwork thing?
what about the rom manager version, can you flash that with a rooted system through normal recovery? or is it like no matter what I need 1 click clockwork on the phone before putting on a kernal that will have clockwork in it?
Click to expand...
Click to collapse
As of last night there is a shortcut now available.
Koush said:
Note, using reboot recovery or adb reboot recovery will take you to a "stock" recovery. Simply apply the update.zip on your SD card and clockworkmod will start up. (This method is better known as fakeflash)
Starting up recovery through ROM Manager will take you directly into clockworkmod.
Click to expand...
Click to collapse
Go to this thread and download the .zip of the ClockworkMod kernel. Rename the file "update.zip" and place it at the root of your SD card. Reboot into stock recovery by turning off the phone and then hold volume down/camera/power. There should be an option to install update.zip - do that. Now you can reboot the phone and you should have the ClockworkMod kernel installed. Go to the market and download ROM Manager. Open it up and select Flash ClockworkMod Recovery. After the file is downloaded select Reboot into Recovery. Your phone should reboot and automatically install Clockwork. Done.
From my understanding the .zip is signed so this should work, although I used a different method as I already had the old Clockwork Recovery installed when I installed the ClockworkMod kernel.
I think that you need either a custom recovery or use redbend ua to flash- the true stock recovery will not work as it is not signed by samsung etc
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 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.
I have just rooted my phone recently on my Droid X using Z4root and it worked fine. Then I backed up my phone using Titanium Backup, which also worked fine also. Then I installed ROM Manager and then flashed ClockworkMod Recovery within ROM Manager. When I click on Backup Current ROM the phone reboots fully without going into recovery. So I open ROM Manager and click "Manage and Restore Backups" and there is no file there.
I tried clicking "Reboot into Recovery" to see if I could select it there and the phone just reboots back to android without going into recovery. So then I turned off my phone and held down the home+power to go into recovery which works. When I'm there it doesn't have an option to backup my ROM. I don't want to flash this ROM I want to try until I can backup my current stock ROM, in case something goes wrong.
When at the blue recovery screen I notice at the bottom in yellow a message is displayed "E: Can't open /cache/recovery/command. Wondering if this is my issue. I also notice in recovery it gives me an option to "apply sdcard:update.zip" but I don't see an update.zip on my sd card, so I'm not sure if I should select this before being able to backup my stock ROM. I'm afraid to flash the ROM before knowing this current problem. Can anyone help me with this issue? I am new to the whole root and ROM hacks, but have been researching in depth and taking all precautions so I'm trying hard not to brick my phone. Thanx in advance.
First off update.zip is just an update.zip package. Could be anything thats an update and can be flashed. Yeah...not sure why rom manager doesnt work for you but all the same your better off doing it from recovery anyway. You can make backups in recovery you don't need rom manager just use rom manager to manage your backups it will see them no matter what! It will allow you to rename them as well so they are easily identifiable also. If your rom manager works youll be able to name the backup before hand! If you ask me rom manager doesnt update the roms fast enough anyway they are usually like 2 days behind! Good tool either way but not so good at replacing roms as recovery does a better job. I have never had one problem using recovery but I've had a problem every time I try to flash a rom using rom manager!
Okay I figured out that the ClockworkMod Recovery must not have flashed properly or something bc I was just at the dev's site and the picture of the recovery is different than mine bc it's green and has many more options to choose from. Plus it says ClockworkMod Recovery on the recovery screen and mine doesn't. It's blue and says android recovery at the top. When I open the ROM Manager it says that I have the ClockworkMod Recovery but I don't. I even tried reflashing but it didn't work either. So how do I get the ClockworkMod Recovery to flash correctly?
I am having same problem but I just use bootstaper and it works fine
I tried downloading the bootstrap from the creator of ClockworkMod Recovery but the link seems to be broken. What bootstrap are u using?
I found the bootstrap for the Droid X on the market and that fixed the issue I was having. Wish I would have known from all the other posts/articles I read that it was a requirement for the Droid X to have the bootstrap to run recovery
How does the fake flash with CWM via Rom Manger work? Is it like the flash that's used with the Vibrant, where it's just an update.zip that's temp installed when booting into recovery? Or is it something different?
aczarney said:
How does the fake flash with CWM via Rom Manger work? Is it like the flash that's used with the Vibrant, where it's just an update.zip that's temp installed when booting into recovery? Or is it something different?
Click to expand...
Click to collapse
Yes, it puts the update.zip onto the sdcard. If you get stuck in a bootloop, there is no way to recover other than doing a factory reset if you flash the recovery this way.
On the other hand, if you flash CWR through NVFlash, if you get into a bootloop, you can press Vol - and Power to access the recovery.
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).