Via ROM manager, I updated CWR to 3.0.2.4 from 3.0.0.5. And now, for some reason when i boot into recovery, I'm greeted by the bootloader saying that there is no recovery or boot img. I don't have access to a PC right now, and I've tried installing older CWR versions, still no luck. Anyone have an idea?
Sent from my Nexus S using XDA App
MrSvedberg said:
Via ROM manager, I updated CWR to 3.0.2.4 from 3.0.0.5. And now, for some reason when i boot into recovery, I'm greeted by the bootloader saying that there is no recovery or boot img. I don't have access to a PC right now, and I've tried installing older CWR versions, still no luck. Anyone have an idea?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I've had intermittent trouble with ROM Manager properly flashing recoveries. Assuming you have the su binary installed already, you could download the img and then use flash_image from a terminal emulator to flash it manually from the phone itself.
Code:
flash_image recovery /sdcard/recovery.img
flash_image: http://cyanogen-files.carneeki.net/flash_image.zip
CWM: http://mirror1.kanged.net/recoveries/recovery-clockwork-3.0.2.4-crespo.img
Code:
Just flash 3.0.0.5 again and it will be fine.
Sent from my Nexus S using XDA Premium App
One thing that I always have to make sure to do whenever I flash a recovery on the Nexus S via ClockworkMod, is to flash it at least three times. For some reason the first time it never sticks - it takes it quite some time to first download it then try to flash it. The subsequent reflashes are (usually...) fairly quick and don't take longer than a couple of seconds - which is how I know that it's properly flashed them.
So go ahead and flash the newest available recovery for your NS, just do it at least three times.
knytphal said:
One thing that I always have to make sure to do whenever I flash a recovery on the Nexus S via ClockworkMod, is to flash it at least three times. For some reason the first time it never sticks - it takes it quite some time to first download it then try to flash it. The subsequent reflashes are (usually...) fairly quick and don't take longer than a couple of seconds - which is how I know that it's properly flashed them.
So go ahead and flash the newest available recovery for your NS, just do it at least three times.
Click to expand...
Click to collapse
Yup, that did it! Just kept doing it till it worked Thnx!
Sent from my Nexus S using XDA App
Related
I have installed it while in '0.5, and when I go back in, its always gone. Has rom manager been updated for this? Because I think that's they problem. I choose CWR from within rom manager (which is .0.5), and when it reboots I am back in 0.5.
Just wondering if there was an update or a fix/patch I missed.
Sent from my HTC Glacier using XDA App
I don't know what you are doing, so I will just tell you what I have done.
1) Download 3.0.0.6 and save to sd.
2) Flash 3.0.0.5 from within rom manager.
3) reboot into recovery 3.0.0.5.
4) Flash 3.0.0.6 file
5) reboot until rom loaded
6) Once rom loaded reboot again into recovery and should be 3.0.0.6 (do not reflash 3.0.0.5 again, otherwise will see 3.0.0.5 in recovery again)
If that doesn't work, I don't know what to tell you except to use adb.
Sent from my HTC Glacier using XDA App
syntropic said:
I have installed it while in '0.5, and when I go back in, its always gone. Has rom manager been updated for this? Because I think that's they problem. I choose CWR from within rom manager (which is .0.5), and when it reboots I am back in 0.5.
Just wondering if there was an update or a fix/patch I missed.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Sometimes when you flash a new ROM, CWM 3.0.0.6 doesn't stick. When that happens, just downlaod and install a clean CWM recovery file again from here (http://forum.xda-developers.com/showthread.php?t=944681) and follow instructions and 3.0.0.6 should stick.
syntropic said:
I have installed it while in '0.5, and when I go back in, its always gone. Has rom manager been updated for this? Because I think that's they problem. I choose CWR from within rom manager (which is .0.5), and when it reboots I am back in 0.5.
Just wondering if there was an update or a fix/patch I missed.
Click to expand...
Click to collapse
I'm not sure what the other posters mean when they say CWM doesn't "stick". The problem is that 3.0.0.6 is not an officially supported version, and therefore even when it's installed, ROM Manager will continue to say you have 2.5 or 3.0.0.5 installed. Once you've successfully installed 3.0.0.6, don't worry what ROM Manager says about versions. Just boot into recovery and you'll see that 3.0.0.6 is there.
I flashed once and its been there ever since. I dont see y its resetting
Sent from my HTC Glacier using XDA Premium App
charlieb620 said:
I flashed once and its been there ever since. I dont see y its resetting
Click to expand...
Click to collapse
It's not resetting. He just thinks it is since 3.0.0.5 is the latest version supported by ROM Manager.
TeeJay3800 said:
It's not resetting. He just thinks it is since 3.0.0.5 is the latest version supported by ROM Manager.
Click to expand...
Click to collapse
I actually realize that Rom manager merely says 3.0.0.5 and 0.6 is actually "installed". The problem is it doesn't "stick". Even if I boot from recovery not using rom manager, 0.5 is always still there. I am going to download it again and see what happens.
Thx!
Sent from my HTC Glacier using XDA App
Just an FYI for any who had any problems.
Originally, the file I had a link to (and downloaded) was something like clockworkmod-recovery-3.0.0.6.zip (or similar). This apparently is a one shot flash to put you into the 3.0.0.6 recovery while you are already in the 3.0.0.5 recovery. The file that I just downloaded (given above in this thread) actually creates a permanent 0.6 recovery. Just install the file from 0.5 recovery, reboot, and then flash clockworkmod recovery from within rom manager.
At that point, whenever you boot into recovery from RM, it be 3.0.0.6. NOTE: RM will continue to say that you have 3.0.0.5 installed, so ignore that.... 0.6 will be installed.
Sent from my HTC Glacier using XDA App
based on your original post (unless I'm miss reading it) you are flashing the zip file from within recovery, when phone reboots you are going into ROM Manager and flashing CWR which shows as 3.0.0.5 if you use the method in the link "NeverAlwaysEver" posted 3.0.0.6 over writes 3.0.0.5 so it should stick... however I did notice after flashing the newest version of 3.0.0.6 (the one that keeps phone from booting into recovery if plugged in while off) if I selected 3.0.0.5 in ROM Manager it would flash back to 3.0.0.5, I don't know why but that is the only one I have had the same problem you laid out.
One thing I realize is all the posts about these topics can be confusing because it is not always clear whether a poster is starting that they "flashed" cwr, ot merely booted into cwr.
But my problem was solved when I flashed/installed the file from the link by NeverAlwaysEver above when I was in CWR (3.0.0.5). This file is a substitute file which RM uses to flash to a new recovery. So when you flash again from within RM, you are "installing" the 3.0.0.6 recovery. I didn't write RM, so I do not know why it doesn't recognize that 3.0.0.6 is installed and report this as the actual version after you do this, but its a minor issue.
I dint know what zip version you are referring to other than the one in this thread and the "one-shot" one I had (which I got from SoltyPK in some post), but the later one could have utility if you need more than 2 recovery versions (e.g., if for some reason you wanted to have the ability to use the stock recovery (2.5.1.7), cwr 3.0.0.5, and cwr 3.0.0.6., the last one you actually install while in 3.0.0.5, and it thereupon immediately puts you into 3.0.0.6.
Sent from my HTC Glacier using XDA App
syntropic said:
Just an FYI for any who had any problems.
Originally, the file I had a link to (and downloaded) was something like clockworkmod-recovery-3.0.0.6.zip (or similar). This apparently is a one shot flash to put you into the 3.0.0.6 recovery while you are already in the 3.0.0.5 recovery. The file that I just downloaded (given above in this thread) actually creates a permanent 0.6 recovery. Just install the file from 0.5 recovery, reboot, and then flash clockworkmod recovery from within rom manager.
At that point, whenever you boot into recovery from RM, it be 3.0.0.6. NOTE: RM will continue to say that you have 3.0.0.5 installed, so ignore that.... 0.6 will be installed.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Good to know you have it straighten out now hehe I wouldn't mind if you hit thanks button
RavenWulf said:
based on your original post (unless I'm miss reading it) you are flashing the zip file from within recovery, when phone reboots you are going into ROM Manager and flashing CWR which shows as 3.0.0.5 if you use the method in the link "NeverAlwaysEver" posted 3.0.0.6 over writes 3.0.0.5 so it should stick... however I did notice after flashing the newest version of 3.0.0.6 (the one that keeps phone from booting into recovery if plugged in while off) if I selected 3.0.0.5 in ROM Manager it would flash back to 3.0.0.5, I don't know why but that is the only one I have had the same problem you laid out.
Click to expand...
Click to collapse
If you mean CWM 3.0.0.6 off mode charging from this thread (http://forum.xda-developers.com/showthread.php?t=1014554), it says that one is modified from the original CWM 3.0.0.6 and not the newest CWM 3.0.0.6 that TrueBlue_Drew posted (link I gave in previous post). I haven't tried that off mode charging CWM modified from original CWM .6 but maybe that is the reason why it goes back to .5.
I have been trying to get clockwork to work forever on my Vibrant and I finally got it to work.I rooted my phone using super one click method then I installed 3e_recovery installer onto phone.I used Rom Manager to install Clockwork for Samsung Vibrant Galaxy S.Every time I would load onto stock recovery and reinstalled packages 2 times and it would never load into Clockwork recovery (I tried so many different things to get it to work for about a week).So today I used Rom Manager to install Clockwork again but this time I selected Galaxy S Captivate instead of the Galaxy S vibrant(which is the phone I own).I rebooted into recovery and reinstalled packages twice and it finally booted into Clockwork recovery.I just figured there must be other frustrated people having the same issue so I thought this might be helpful to somebody.
matb321 said:
I have been trying to get clockwork to work forever on my Vibrant and I finally got it to work.I rooted my phone using super one click method then I installed 3e_recovery installer onto phone.I used Rom Manager to install Clockwork for Samsung Vibrant Galaxy S.Every time I would load onto stock recovery and reinstalled packages 2 times and it would never load into Clockwork recovery (I tried so many different things to get it to work for about a week).So today I used Rom Manager to install Clockwork again but this time I selected Galaxy S Captivate instead of the Galaxy S vibrant(which is the phone I own).I rebooted into recovery and reinstalled packages twice and it finally booted into Clockwork recovery.I just figured there must be other frustrated people having the same issue so I thought this might be helpful to somebody.
Click to expand...
Click to collapse
Is this reliable or was it just a fluke? I'm trying to get CWM on my new vibrant which has kb5 stock rom.
I used superoneclick to root and install busybox, but I have no clockworkmod.
In ROM manager, I select flash clockworkmod recovery. Select Vibrant. It says something like recovery downloaded. Then does nothing.
So I then select reboot into recovery which takes me to stock recovery. I select reinstall packages a few times and nothing happens except the signature failure each time, so then I end up rebooting from there.
Am I going wrong somewhere? I have searched around a bit but haven't got the solution yet. Thanks.
Wait, are you saying you selected the captivate option in rom manager on your VIBRANT?
via LG G2x
pez321 said:
I used superoneclick to root and install busybox, but I have no clockworkmod.
In ROM manager, I select flash clockworkmod recovery. Select Vibrant. It says something like recovery downloaded. Then does nothing.
So I then select reboot into recovery which takes me to stock recovery. I select reinstall packages a few times and nothing happens except the signature failure each time, so then I end up rebooting from there.
Am I going wrong somewhere? I have searched around a bit but haven't got the solution yet. Thanks.
Click to expand...
Click to collapse
The problem is, the 3e recovery in our 2.2 roms used different signing keys that haven't been cracked like 2e has. So, you need to replace the recovery file with a fixed one, or odin a voodoo kernel and be done.
Bit this is not the thread on where to discus that.
Sent from my SGH-T959 using XDA App
getting clockwork
did you uninstall the old clockwork frist or did it copy over it
What I did is I odin back to stock. Find an app called z4root once you have root download rom manager then install rom from there this is an easier method
Sent from my SGH-T959 using XDA Premium App
I'm trying to get Clockwork Mod installed on my wife's Nexus S via ROM Manager but whenever I reboot into recovery it's just the default recovery.
I had this issue with my Nexus S too and I never resolved it. I was only able to flash via fastboot. This isn't an option on my wife's phone as it's not unlocked and I don't want to wipe everything.
Sent from my Nexus S using XDA
How can you flash cwm without unlocking? I don't think that's possible(correct me if I'm wrong).
Sent from my Nexus S from Tapatalk
ljordan2 said:
How can you flash cwm without unlocking? I don't think that's possible(correct me if I'm wrong).
Sent from my Nexus S from Tapatalk
Click to expand...
Click to collapse
You mean rooting? You're supposed to be able to flash it from within Android if your phone is rooted. OEM unlocking the phone lets you flash things from the bootloader. However, despite that I haven't been able to do it.
I finally gave up. Since the phone is rooted I just backed everything up with Titanium Backup and then OEM unlocked the phone and I'm not restoring from scratch. Not sure I'll ever have an answer to this issue.
Note: If the phone is rooted and you have flash_image, you can use that to flash custom recovery(without bootloader unlocking) 'manually'.
cbstryker said:
I'm trying to get Clockwork Mod installed on my wife's Nexus S via ROM Manager but whenever I reboot into recovery it's just the default recovery.
I had this issue with my Nexus S too and I never resolved it. I was only able to flash via fastboot. This isn't an option on my wife's phone as it's not unlocked and I don't want to wipe everything.
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
I have had the same problem with ROM manager ever since I bought it. What I do is flash the recovery a few times. I'll hit flash recovery, and when it finishes I'll do it like 3 or 4 more times and eventually the recovery will stick.
Sent from my Nexus S using xda premium
To fix this, flash CWM recovery using ROM Manager, and then install root explorer. Using root explorer, rename /system/etc/install-recovery.sh to something else (e.g. /system/etc/install-recovery.sh-RENAMED) and that should make your CWM recovery stick. Otherwise it gets overwritten on each boot by the stock Android recovery.
I actually just learned this over the weekend when I got my new NS and I had to do the same thing. I've previously been a happy SGS i9000 owner for the past 2 years, so the NS is pretty new to me still.
i had the same bug i flash a more oldest vercion of rom manager and cmw and that work for me but im crazy ,there are better methods I just tell my experience
Just flashing using CWM..dont flash using ROM manager...many users have problems flashing from ROM manager..
rhainman said:
To fix this, flash CWM recovery using ROM Manager, and then install root explorer. Using root explorer, rename /system/etc/install-recovery.sh to something else (e.g. /system/etc/install-recovery.sh-RENAMED) and that should make your CWM recovery stick. Otherwise it gets overwritten on each boot by the stock Android recovery.
I actually just learned this over the weekend when I got my new NS and I had to do the same thing. I've previously been a happy SGS i9000 owner for the past 2 years, so the NS is pretty new to me still.
Click to expand...
Click to collapse
This ^
Sent from my Nexus S
So my friend and I last night decided to unlock, root and flash recovery using the nexus 7 toolkit. Everything seemed to work ok, but now we have a major issue. It seems last night he flashed phandroid rom or whatever its called, but didnt wipe, so now he lost clockwork somehow, and the rom just boots and doesnt do anything.
We tried using the toolkit again to push recovery, it says it sent it, but we can only access fast boot. If you hit volume keys to get into recovery mode, and select it, it wont go into clockwork, just tries to boot the rom
Any suggestions?
chugger93 said:
So my friend and I last night decided to unlock, root and flash recovery using the nexus 7 toolkit. Everything seemed to work ok, but now we have a major issue. It seems last night he flashed phandroid rom or whatever its called, but didnt wipe, so now he lost clockwork somehow, and the rom just boots and doesnt do anything.
We tried using the toolkit again to push recovery, it says it sent it, but we can only access fast boot. If you hit volume keys to get into recovery mode, and select it, it wont go into clockwork, just tries to boot the rom
Any suggestions?
Click to expand...
Click to collapse
Do you have the N7 connected to your computer via USB? For some reason it won't boot into recovery if it's not connected via USB, I had this problem when flashing the Paranoid Android rom.
Cmon chugger you have the gnex for god sakes why the hell did you use a toolkit.
Secondly If you can fast boot flash a recovery. And boot into recovery and reflash the ROM.
Sent From My Toro+ via White Tapatalk
Hi,
It seems that I have CWM and recovery installed on my Nexus 4. I was on TWRP previously and switched to CWM, now it seems that it is stucked.
I erased recovery in command prompt and flash it with CWM after installing stock ROM but ROM Manager still detected TWRP. How do I get rid of TWRP?
Zouk18 said:
Hi,
It seems that I have CWM and recovery installed on my Nexus 4. I was on TWRP previously and switched to CWM, now it seems that it is stucked.
I erased recovery in command prompt and flash it with CWM after installing stock ROM but ROM Manager still detected TWRP. How do I get rid of TWRP?
Click to expand...
Click to collapse
try flashing stock recovery via adb
If you reboot into recovery does CWM come up or TWRP? If it's CWM then ignore ROM Manager and continue as normal
ijustzeke said:
try flashing stock recovery via adb
Click to expand...
Click to collapse
So you are suggesting that I erase and flash to stock recovery via adb and then flash custom recovery again?
EddyOS said:
If you reboot into recovery does CWM come up or TWRP? If it's CWM then ignore ROM Manager and continue as normal
Click to expand...
Click to collapse
CWM comes up as the recovery because it's the latest one I flash. I know it might now matter but this really bugs me.
Dunno why you're using ROM Manager anyway, pointless piece of software IMO. Just flash everything manually
Mine was gone when i unrooting the device
Sent from my Nexus 4
EddyOS said:
Dunno why you're using ROM Manager anyway, pointless piece of software IMO. Just flash everything manually
Click to expand...
Click to collapse
I was just checking out the app, don't really use it. That was when I saw two recoveries. I erased and flashed everything via adb previously. Just really wanna know the cause and how to get rid of it.
curtzxion said:
Mine was gone when i unrooting the device
Sent from my Nexus 4
Click to expand...
Click to collapse
Is there a way just to unroot but keep my ROM, kernel and data intact?
Zouk18 said:
I was just checking out the app, don't really use it. That was when I saw two recoveries. I erased and flashed everything via adb previously. Just really wanna know the cause and how to get rid of it.
Is there a way just to unroot but keep my ROM, kernel and data intact?
Click to expand...
Click to collapse
My rom, kernel, and data doesn't change, when i was unrooting the device(as i remember)
Sent from my Nexus 4
That's normal. I have it too. Just choose cwm on recovery already installed and leave it like that.
Sent from my Nexus 4 using xda premium