Database Develop

Clockworkmod recovery not booting after a full system boot

Can anyone give me a explanation why after installing rom manager and the clockworkmod recovery i can imediatly boot into recovery, but after doing a normal system boot and try again do boot into recovery (through rom manager or even manualy pressing power + vol down) i can´t??? It stops at a black screen with a white exclamation triangle and a android icon. If i go through flashing the recovery again (in rom manager) and after that i press "reboot into recovery" it works well. But thats the only time i can. Meannig: i have to flash the clockworkmod recovery every time i want to go there. Is this normal? Is it rom manager? clockworkmod recovery? or the Android OS? I´m on a rooted Nexus with a unlock bootloader (androidroot) running stock froyo. What can i do to make the clockworkmod recovery stick?
I´m a newby in flashing roms, and i would love to try a modified rom. But for that to happen i need to have full trust in the apps i´m using to do that. Until now i can´t say that i feel confident to go through with the flashing process. Any help would be much apreciated.
SOUSAFRUI @ NEXUS ONE

I also have the same problem with AmonRA Recovery. After a long search for the answer thru google search, I found out that Custom Recovery won't stick with the Stock ROM. You need to flash your N1 with a custom ROM then only the Custom recovery will work. If you do a nandroid restore back to the stock rom, the custom recovery will disappear again. You need to reflash the custom recovery again to get you back to the custom recovery screen for flashing custom ROM.

Thank you for the quick answer
SOUSAFRUI @ NEXUS ONE

taksei said:
I also have the same problem with AmonRA Recovery. After a long search for the answer thru google search, I found out that Custom Recovery won't stick with the Stock ROM. You need to flash your N1 with a custom ROM then only the Custom recovery will work. If you do a nandroid restore back to the stock rom, the custom recovery will disappear again. You need to reflash the custom recovery again to get you back to the custom recovery screen for flashing custom ROM.
Click to expand...
Click to collapse
same problem with stock frg83
thank you taksei
EDIT: found how to disable:
mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
Click to expand...
Click to collapse

If you would read the recovery installation instructions in Wiki, you'd notice the instructions for removal of those 2 files, that rewrite the recovery on system boot.

[Q] I have a delema!I dont know what to do! I Need Help!

I have nexus one. This is my story. I had rooted my phone using universial android. I installed cyanogen mod and was a very happy user until I saw the MIUI Rom and then I flashed that. Then I saw that it was to unstable so I restored to a backup I made of cyanogen. After I started using cyanogen mod again it was very unstable and had random reboots and lots of force closes. So I just decided I was done with the rooting business so I was gonna use a passimg. Acsently I flashed the Korean passimg and I can't flash any of the other ones(except the frg33one because i cant update to frg83 after and lose root) So on the Korean Rom I rooted and installed clockworkmod. Then I noticed I couldn't install any custom rom(i tried CM6, CM6RC3,MIUI)and I kept getting errors.So while I was in clockwordmod restored one of my old stockrom backups before i had flashed any roms and it worked. But still when went to go and try and flash a rom it still gave me errors. But the most ANNNOYING thing of all is i would flash clockwordmod in rommanager than i would touch reboot to recovery. It worked. I got into clockwordmod but then when i would try and go back again a second time it wouldn't be there. It would be the stock android recovery and even when i would go to recovery though the bootloader it would still be stock recovery. I dont know what to do. As i said my bootloader isnt unlocked because i dont want to void my warrenty. my inital plan was if i ever needed to return this ting i could just i could just run a passimg and restore to to stock everything and there would be no traces. If i have to return my phone it would have to be last resort because I live in Canada and I would have to play ridiculous duties and taxes on it. Now i just want to make sure im able to install gingerbread on when it comes out. Also i forgot to mention that everytime i try to update my phone to 2.2.1 it always fails even though im on stock recovery(although even when i go into recovery and it is the stock recovery rommanager still says im running clockwordmod) PLEASE HELP!!!
ps. Im only 13 but i consider myself to be pretty techsmart for 13. I wouldnt mind using cmd/terminal and im running ubuntu 10.10 on my laptop.

ajam100 said:
I have nexus one. This is my story. I had rooted my phone using universial android. I installed cyanogen mod and was a very happy user until I saw the MIUI Rom and then I flashed that. Then I saw that it was to unstable so I restored to a backup I made of cyanogen. After I started using cyanogen mod again it was very unstable and had random reboots and lots of force closes. So I just decided I was done with the rooting business so I was gonna use a passimg. Acsently I flashed the Korean passimg and I can't flash any of the other ones(except the frg33one because i cant update to frg83 after and lose root) So on the Korean Rom I rooted and installed clockworkmod. Then I noticed I couldn't install any custom rom(i tried CM6, CM6RC3,MIUI)and I kept getting errors.So while I was in clockwordmod restored one of my old stockrom backups before i had flashed any roms and it worked. But still when went to go and try and flash a rom it still gave me errors. But the most ANNNOYING thing of all is i would flash clockwordmod in rommanager than i would touch reboot to recovery. It worked. I got into clockwordmod but then when i would try and go back again a second time it wouldn't be there. It would be the stock android recovery and even when i would go to recovery though the bootloader it would still be stock recovery. I dont know what to do. As i said my bootloader isnt unlocked because i dont want to void my warrenty. my inital plan was if i ever needed to return this ting i could just i could just run a passimg and restore to to stock everything and there would be no traces. If i have to return my phone it would have to be last resort because I live in Canada and I would have to play ridiculous duties and taxes on it. Now i just want to make sure im able to install gingerbread on when it comes out. Also i forgot to mention that everytime i try to update my phone to 2.2.1 it always fails even though im on stock recovery(although even when i go into recovery and it is the stock recovery rommanager still says im running clockwordmod) PLEASE HELP!!!
ps. Im only 13 but i consider myself to be pretty techsmart for 13. I wouldnt mind using cmd/terminal and im running ubuntu 10.10 on my laptop.
Click to expand...
Click to collapse
If you installed the original passimg then you'll have 2 files you'll want to remove if you don't want the stock recovery to keep flashing back when you reboot
Remount /system rw and remove:
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
Remove those, flash your custom recovery and you should be good to go.
With respect to the errors: Clear out the cache and dalvik-cache. Wipe and install your rom of choice, be it a stock repack, CM6, Enom etc.
With Amon's latest recovery *1.8.0.1 you can flash both signed (google) and signed (test) packages, so the official update will flash as well as a repack. If you flash the official 2.2.1 remember to pull remove those 2 files again or it will blow away your custom recovery on reboot.

[Q] rooting, recovery, custom ROM

Hi out there,
A friend of mine has got a milestone (gsm) and problems with flashing recovery and custom rom.
he says he has got root, but when he tries to flash recovery it says "no root rights" (via root console with su). moreover, his recovery is a .zip and not a .img which i was used to (am a htc hero owner). through not having custom recovery, he cant install custom roms, seems like no root on boot.
anyone can help? as the procedure on htc hero seems to be completely different i cant help him, will give him this link so he can see
thank you,
SummonerOfDeath

http://forum.xda-developers.com/showthread.php?t=983516
You have everything you need to know. Just ask your friend to go thru.
Sent from my Milestone using Tapatalk

Can't access recovery

Hi there, after rooting my phone with the "DoomLord's via Zergrush Exploit" , and after installing rom manager and flashing clockworkmod. I just can't access it.
If I load into the bootloader and click recovery, I get an image with a ! sign and a picture of an android, the same happens when I load recovery through rom manager. I have flashed the recovery twice now and my phone's just not having it. My phone works no problem, I just dont understand it
All I want to do is to make a backup and install a custom rom
Am I doing somthing wrong?
(Yes, my bootloader is locked BTW)

Very simple - you didn't flash the recovery properly, so you're getting to stock recovery.

Yup like Jack_R1 stated, the flash didn't stick or you didn't do it right.
Open Rom Manager, at the top it will tell you what recovery you have.
Does it show anything?
You could also try adb if you have that setup
http://wiki.cyanogenmod.com/wiki/Nexus_One:_Full_Update_Guide#Installing_a_Custom_Recovery_Image
You could even install it via terminal on your phone
Heck try this recovery, it's good
http://forum.xda-developers.com/showthread.php?t=1291970

Try THIS. Install the application and it will install the best recovery

Rom manager tells me that i have clockworkmod 5.0.2.0
I'll try installing the recovery through terminal when i get back to my pc
Sent from my Nexus One using XDA App
EDIT: Having seen the other recovery you've stated, i'll try and install that.
Also, does it matter about which version of android i'm running? could that result of a bad install of the recovery through clockworkmod?
Its 2.3.4 stock rom if anyone's intrested
FINAL EDIT:
Thank you!
4EXT flashed perfectly, after using the app to reboot into the bootloader, it loaded up that. Many thanks!

Trying to install 4.4 Rom, falling at every hurdle.

Hi There,
Just wondering if anyone had any ideas why my phone refuses to co-operate!
Basically, after getting bored of the stock rom when I first got my phone, I somehow managed to install a CM based rom. That worked, but I got bored of the fact that the camera never seemed to work right, and some apps didn't work/ were graphically buggy. Assuming it was just a badly ported graphics driver or whatever, I found a way, using FlashTool, to revert to the stock rom (C6603_10.3.1.A.0.244_Generic UK to be precise). I wasn't sure exactly what it did, but it was back how it used to be. sorted.
So, since kitkat made it's way to the XZ, I thought I'd try one of those roms, being the curious bugger that I am. The process I ended up going with eventually was:
>Downgrading Kernel to a lower version because the root explot wouldn't work on 10.3.1.A.0.244
>Rooting using "DooMLoRD_Easy-Rooting-Toolkit_v18"
>Upgrading kernel to one that would accept a recovery
>Installing TWRP
>Booting into recovery, CWM appeared instead. Strange, I thought. Oddly, mount USB wouldn't work at all, so I had to boot the phone back up to transfer the kitkat rom over
>Trying to flash the rom gave me an error number 7
>Boot Loop, at which point I just flashed 10.3.1.A.0.244 again.
I've tried this twice now, first with DooM Kernel, and then once with a different one. Neither CWM or TWRP have worked properly. Any help? Or am I just cursed?
Cheers

Tried this again, did literally everything I could think of and still no dice. Help? Have I somehow forced my phone to be on stock software forever?

If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk

eryen said:
If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Hey, thanks for your reply!
I had unlocked the bootloader when I first got the phone and just assumed it would be permanent. Would flashing it back to stock firmware re-lock the bootloader?
But yes, assuming my boot loader is still unlocked ( I have tried to check and it doesn't seem to be locked) I have been through those steps basically. I am fine to flash a kernel with a recovery but the recovery never works properly/ at all. I can root the phone no problem though.

Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app

shoey63 said:
Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone

SuburbanKnight said:
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone
Click to expand...
Click to collapse
You're not actually going to boot into your current rom after flashing the kernel.
Flash the kernel via fastboot, then boot into recovery and flash the rom.
All this should be covered in the installation instructions of whatever rom you're trying to flash in any case....
Sent from my C6603 using Tapatalk

Well, that seems to have done it! Thanks very much for your help.
So, I guess the moral here is that if you're on stock and need a recovery to flash a new ROM, always use the boot.img from the ROM you'll be using.
Thanks again - I'd never seen that said before but quite possibly I wasn't paying attention!