I have been trying to get my rooted Galaxy Nexus to load the CWM Touch recovery image, and I just can't seem to get it to stick. I originally just tried to install the basic non-touch version from Rom Manager. When it rebooted, I got the red ! and a dead robot. So I booted into fast boot, and flashed the touch recovery. After flashing if I go straight to recovery, I do get the CWM recovery and can backup. My problem is that if I the reboot the phone, I can never get back to it again. I always end up at the red ! and a dead robot.
I read on another thread to rename the file "/recovery-from-boot.p" to "recovery-from-boot.p-bak" and that it might require reflashing the image. I moved this file and re-named it, reflashed, booted into android. Then powered off and booted into recover mode, just to see the red ! again.
It seems that when I first flash I can go into it, but anytime after that it just dies. Anyone have a deeper knowledge of what is going on here and care to point me in the right direction? I could probably just go ahead and flash a new image to the phone but I don't feel good doing that while the recovery image seems to need re-imaging every time.
Hi there,
You're correct, you need to rename/delete that file to make cwm stick on the nexus.
If you reboot the phone before removing that file, the file will update your settings to point to the old recovery instead of cwm.
Since you've just renamed it, reinstalling cwm should do the trick.
You're renaming the wrong file. You need to rename or delete install-recovery.sh from system/ect
Related
I have a rooted TMo Vibrant running 2.1. I want to install a custom ROM and have the paid version of ROM mgr installed. I have downloaded the new ROM and I also have a (separate) zip of a different ROM on the SD card. The beginning steps of the installation go smoothly. But when I get to the point where ROM mgr says "Do you want to go into recovery mode to continue installation?" and I Select YES, the phone reboots into NORMAL mode and the installation ends. Same thing happens if I try to install manually from the SD card. I scroll down and select "install zip ...". Then the next screen that pops up has "reboot", " delete data", "reinstall packages", etc . I have tried all those options. But ultimately I end up back at the point where the only option I haven't chosen is "reboot system now". When I select reboot, the phone reboots in normal mode again. What am I doing wrong?
Not sure if this is your problem, but sounds like you need clockwork mod recovery update.zip on your phone.
Here is the trick though, when you get into normal recovery, sometimes you have to apply the cwm recovery update.zip TWICE to get into cwm recovery.
Boot up phone into stock recovery
apply the cwm recovery update.zip
phone reboots into stock recovery again
apply the cwm recovery update.zip again.
Hope that helps.
I would suggest doing this.
First and foremost make a nandroid backup, you can use cwm to do this. place a copy of the backup on your computer.
Backup your /efs folder which contains your nv_data.bin and imei information. You loose this you are f*cked.
Get the cwm recovery update.zip and put it on your internal sd root. If you have multiple update.zip files, just delete them all, just make sure the cwm recovery update.zip is there.
Also place the zip file of the rom onto your internal sd root also.
Disable voodoo lagfix if you have that installed.
Odin back to stock jfd 2.1. When finished next..
Apply cwm recovery update, apply TWICE to get into cwm recovery.
Then you can go into cwm recovery and select the zip of the rom you want to flash.
Follow all install directions of the ROM developer, they may want you to be on 2.2 first, which would mean odin to stock jfd 2.1, flash stock 2.2, then install whatever rom you are trying to.
That is how I do it.
I have a question about Clockwork recovery and this phone. Above you say that if any .zips are on internal sd to delete them and leave CWR on there only. I have this. Then if we want to go into the CWR we have to apply the update.zip twice. I do this also. Why can't we just replace the stock recovery with the Clockwork one and bypass the having to reinstall the packages twice. Maybe an sh init_hijack or something like that. I have been trying to find where the stock recovery "lives" to no avail. If you know where it is, then I can work on this and post the results.
Seems reasonable that if we replace the stock files with the CWR files and hijack the rocvery at boot it should work to boot right into CWR directly.
Woodrube said:
I have a question about Clockwork recovery and this phone. Above you say that if any .zips are on internal sd to delete them and leave CWR on there only. I have this. Then if we want to go into the CWR we have to apply the update.zip twice. I do this also. Why can't we just replace the stock recovery with the Clockwork one and bypass the having to reinstall the packages twice. Maybe an sh init_hijack or something like that. I have been trying to find where the stock recovery "lives" to no avail. If you know where it is, then I can work on this and post the results.
Seems reasonable that if we replace the stock files with the CWR files and hijack the rocvery at boot it should work to boot right into CWR directly.
Click to expand...
Click to collapse
Well with MiUi and CM it goes directly into clockwork mod recovery. I guess that's the stock recovery on MiUi and CM.
For me, only on 2.1 and 2.2 roms did I have to apply cwm recovery.zip twice.
SamsungVibrant said:
Well with MiUi and CM it goes directly into clockwork mod recovery. I guess that's the stock recovery on MiUi and CM.
For me, only on 2.1 and 2.2 roms did I have to apply cwm recovery.zip twice.
Click to expand...
Click to collapse
I have not used either for this phone but have with other phones and I think that it is b/c they reworked the services and framework.jars into an expanded power menu. I will see it that hack works on this one, so it will be easier on 2.1 and 2.2 for "relative" noobs. I have done it once for another phone and then my computer crashed (not issue related). I'll let you know what I find out this weekend b/c it'll take some time to get the pathways correct.
I appreciate you quick replies and have taken the first part of the advice and tried to backup everything (Which I thought I did using CWM). Just to be safe I have now installed Root Explorer and will back up everything this evening. Can't do more right now. Need to get back to work. Wayne
That did it. I now have my new ROM installed and a back-up of my efs file (which I mistakenly thought was included in my Nandroid back-up). BTW my nandroid, back-up produced by CWM doesn't include a boot image (or at least there is no image called "boot"). I thought there should be a boot image. In any case, I'm finally over the problem I've been trying for days to overcome. Thanks sooooo much. Wayne
I've tried flashing over and over, and keep getting stuck at the white HTC splash screen after flashing cm7!?!
I've tried flashing through RM and manually.
What I've done:
Downloaded MR2.5 Radio, renamed to PG05IMG.zip, put on root of sd, reboot to recovery, updated it. Booted into my current rom (Gingeritis 3D) and had a signal and everything. So I renamed the PG05IMG to MR2.5-PG05IMG.zip.
So I rebooted into Recovery, did factory reset, wiped dalvik cache, cache partition, and then went to install zip from sd, and went to the Zoom kernel I had downloaded (which I was told works with CM7),
I then did the same thing with the CM7 update rom image which is: update-cm-7.1.1-Thunderbolt-signed.zip
(I have it in a folder called ROMs, is that ok? or does it need to be on the root while flashing?)
I then reboot, and it doesnt ever get past the white HTC splash screen.
I've done it 3 times, making sure everything is wiped, etc and still get the same thing.
What am I doing wrong?
Can someone give me a link to a CM7/Kernel/radio combo they KNOW works???
I don't know what else to try.
I've Googled it, and found lots of people with the same issue, but find no solutions....
I had been doing everything right, but it seems Clockwork Mod Recovery was corrupt or something.
What I did:
I restored back to my last backup.
Opened Rom Manager
Click "Flash Clockwork Mod Recovery" (the top one, even if it says your up to date)
after it flashes CWM successfully, either download and flash a rom from Rom Manager, or do it manually as I did.
And after the flash, I rebooted, and it went right to the CM7 boot animation, and loaded perfectly.
If you were like me and searched google, and found lots of posts with the same issue, but no solutions. So I hope this helps others.
Thanks for all the help guys!
(goes to show sometimes you just gotta try anything and everything)
Did you flash the radio in recovery? Nooooo thats not how you do it. Rename it to PG05IMG.zip and place it on the root of your sd card. Turn your phone off. And then turn it back on by holding power and volume down at the same time. it will take you to the bootloader and it will ask you if you want flash the radio. I think that might help
Sent from my HTC Mecha using Tapatalk
Hey guys,
I have a 16gb Nook Tablet that I rooted using Albert's bootable zip. I installed CWM via the recovery flasher included in the root pack and then proceeded to install a rom. When I went to boot in to CWM using just the sytem itself, the screen stays on the white screen with the box and it jumps around(looks like top of box is broken but it isn't). I have a bootable recovery sd that allows me to go in to CWM but i am getting E: can't open /cache/recovery/last.log
I've tried reinstalling the ROM and it gets to the boot screen and then starts jumping too.
Has anyone had success with fixing this issue?
That sounds like very strange behavior, it sounds like you might have an issue with CWM on the device itself. In fact, after you apply the root and everything you shouldn't need to be back in CWM again unless something goes wrong.
Can you boot the tablet into the normal OS, or does it only try and go to CWM?
It only goes in to CWM. I should be able to use fastboot from CWM right?
I don't know to be honest. If you can't boot into anything else, I'd go back tot he start. I know there is a thread around here that you can actually use CWM to restore back to 1.4.2 stock, then you can re-root from there.
I think I may have it, but I'd have to look.
http://forum.xda-developers.com/showthread.php?t=1663836
Here bro. This should bring you back to full 1.4.2.
I tried to install CWM recovery by flashing the zip file in TWRP. It seemed to have flashed fine, but I cannot get into recovery now. When I try, the screen "flashes" and "flickers" a few times before going black. I've used odin to install the .tar file that I originally used to root the device and in goes through the process just fine. However, when I pull the battery and try to go into android stock recovery, it does the same thing ("flashes & flickers and then goes black"). When I try to boot the phone as normal (not into recovery) it boot loops between the blue samsung swirl and the verizon 4g logo.
I was on cleanrom 4.7 if that helps at all. I would greatly appreciate anyones assistance concerning this matter.
Edit: Found a .tar file for TWRP and was able to load it through ODIN. Once into TWRP I was able to restore a backup I made earlier today. Thought I would edit the post in case someone ran across the same problem.
Romans8vs1 said:
I tried to install CWM recovery by flashing the zip file in TWRP. It seemed to have flashed fine, but I cannot get into recovery now. When I try, the screen "flashes" and "flickers" a few times before going black. I've used odin to install the .tar file that I originally used to root the device and in goes through the process just fine. However, when I pull the battery and try to go into android stock recovery, it does the same thing ("flashes & flickers and then goes black"). When I try to boot the phone as normal (not into recovery) it boot loops between the blue samsung swirl and the verizon 4g logo.
I was on cleanrom 4.7 if that helps at all. I would greatly appreciate anyones assistance concerning this matter.
Edit: Found a .tar file for TWRP and was able to load it through ODIN. Once into TWRP I was able to restore a backup I made earlier today. Thought I would edit the post in case someone ran across the same problem.
Click to expand...
Click to collapse
My first time through a bootloop I ran into the same issue and had the same fix.
Just got back into ROMs again, but made a few mistakes.
I was attempting to install Cyanogenmod
Got the Boot.img file to work, however I realized I didn't add the files to install the ROM, into the SD folder.
(Went into the "install" option on TWRP, but there are no files to install at all)
Now my phone just boots up to the splash logo, and stays there. Any way to fix it?
Note: Already tried RUU, I get the version error like everyone else. I don't know what else to do.
akim33 said:
Just got back into ROMs again, but made a few mistakes.
I was attempting to install Cyanogenmod
Got the Boot.img file to work, however I realized I didn't add the files to install the ROM, into the SD folder.
(Went into the "install" option on TWRP, but there are no files to install at all)
Now my phone just boots up to the splash logo, and stays there. Any way to fix it?
Note: Already tried RUU, I get the version error like everyone else. I don't know what else to do.
Click to expand...
Click to collapse
Create a folder "0" on the sd card and put the file in there. You can also side load in recovery it just takes forever to transfer the ROM.
TheRealDeadApe said:
Create a folder "0" on the sd card and put the file in there. You can also side load in recovery it just takes forever to transfer the ROM.
Click to expand...
Click to collapse
Thank you for the side load recovery. That managed to work, however I encountered another problem.
I am now stuck on the cyanogen 10.1.3 screen, same deal as before.
I've tried everything to solve this:
Deleted cache, factory reset
Made sure I had correct kernal
Etc.
Please, really need to use my phone. Thank you for the help.
Extract the kernel (boot.img) from the ROM file and flash it from your pc using fastboot. Rom doesn't boot is typically due to wrong kernel, maybe it failed to flash from recovery. You are s-off, correct?