Related
Ever since I updated to the last OTA I have lost clockworks recovery image. Thus now I am unable to install the latest froyo rom.
I have tried to install the latest clockworks recovery image and Amon_Ra recovery through Rom Manager. Each time it states it is installed but everytime I try to boot up to the recovery image it gives me the following error:
E: Can't open /cache/recovery/command
and it just gives me the Android System Recover <2e>
Any help would be appreciated....
It sounds like you are not rooted.
If you accepted the OTA from Sprint using your system update on your phone, you are no longer rooted and will not have a custom recovery/root permissions. You will be unable to flash any custom recovery/ROMS/delete any sprint apps/Other Root only things until someone comes up with a way to root 2.2.
Have a drink in hopes that a dev will come up with a way to Root 2.2 soon!
I didnt update over the phone
What happened is I installed a rooted verson of 1.47.651.1 but in doing that it got rid of the recovery image... it definetly a rooter version because i can run apps that require root.. such as wife tether titanium back etc...
any other suggestions...
coolguycarlos said:
I didnt update over the phone
What happened is I installed a rooted verson of 1.47.651.1 but in doing that it got rid of the recovery image... it definetly a rooter version because i can run apps that require root.. such as wife tether titanium back etc...
any other suggestions...
Click to expand...
Click to collapse
there's an update.zip around here somewhere that will allow you to boot into an early form of clockwork recovery.
so, assuming that you goofed something, but still have nand unlocked....
find that update.zip. put it and a .zip for a real recovery onto your sdcard. boot into hboot, let it run the update.zip, that will take you to koush's early clockwork recovery. use that recovery to flash a solid recovery.
done.
alternative method would be to use fastboot to erase the recovery partition, then put a new recovery in.
Here is the update.zip...Just extract Recovery.zip....Do this OR/AND what the Senior Member above said and you should be good
timothydonohue said:
there's an update.zip around here somewhere that will allow you to boot into an early form of clockwork recovery.
so, assuming that you goofed something, but still have nand unlocked....
find that update.zip. put it and a .zip for a real recovery onto your sdcard. boot into hboot, let it run the update.zip, that will take you to koush's early clockwork recovery. use that recovery to flash a solid recovery.
done.
alternative method would be to use fastboot to erase the recovery partition, then put a new recovery in.
Click to expand...
Click to collapse
I actually tried the update.zip one already and it doesnt install... it will stated that the signature cant be verified and it will about the installation... havent tried the fastboot approach... I guess I will need to find out how to do that now
so from the looks of it I am screwed... I have hboot .79 if that matters and from the looks of it the rooted rom i installed screwed up my nand unlock.. which is why i think i can install any recovery images... i tried alot of the nand unlock tutorials and most of them I eventually get to a point were i need to write to /data and i cant because permissions are denied... great... oh well i'll keep on trying... any suggestions are appreciated...
If you still have super user, try this...same thing happend to me.
http://forum.xda-developers.com/showthread.php?t=744621&page=4
I'm having a very similar problem also. My Hboot is 0.79.000 too & after trying clockworkmod recovery, a few RUU update attempts, and attempting to change ROMs completely (not in that order) I'm at a loss, no success anywhere. I can't even get in to recovery anymore. It just reverts back to Bootloader menu where my options are Reboot, Reboot Bootloader, or Power down (& I think there is one other option that i tried and sent me back to the aforementioned screen). However, I can still load my pre-existing ROM...
Does anyone have any ideas if there is anything I can do?
TIA
topdawgn8 said:
If you still have super user, try this...same thing happend to me.
http://forum.xda-developers.com/showthread.php?t=744621&page=4
Click to expand...
Click to collapse
I have a question bout this... I seen this before but the sdk that I downloaded for Windows 7 does not have the Su command... any ideas on how I can get it for Windows 7?
Sent from my PC36100 using XDA App
Nevermind I got the Su command to work
Sent from my PC36100 using XDA App
you can erase recovery from rom manager and try to reflash. i would recommend reinstalling rom manager just to make sure it installed correctly. it installed bad on me once and corrupted my recovery trying to update it, reinstalled and installed an old recovery then the newest one and it worked.
Thanks for the suggestions all. I followed the instructions from link you posted using terminal emulator. No such luck, still reading HBOOT 0.79.0000 and running same ROM.
I also tried reinstalling (several times) clockworkmod recovery images and it effects nothing.
Should I try to completely unroot my phone again? If the images i just flashed didn't do it what will?
Im totally at a loss here. ARG!
hit there jtwonbly.......are you also running the stock rooted 1.47.651.1?
Build number 1.47.651.1 CL195459 release-keys
yea same here......and what is it that your trying to do...go back to stock ROM?
I'd like to go to any other ROM. Its as if I'm no longer rooted anymore.
I think I may try to start all over again using NeckFaces old tutorial on unlocking NAND w/o adb. I'm just not sure if that will fix the HBOOT file because I can't get in to Recovery.
OK Guys thanks for all your help but I have been able to get it fixed now!!!
I pretty much had to redo all of Toast Root tutorial and NAND unlock to get it working. Both Part 1 and Part 2 even though I was already running a rooted rom.
The original problem I had is I kept getting told to just try the nand unlock in part 2 but the phone wasnt having it. It wouldnt like the engineering build of the pc36img.zip
So I started from Part 1. Downloaded the rooted rom pc36img.zip and what do you know it finally let me install it. By the time I was done with both parts 1 and 2 I was able to flash a recovery image, get back to hboot .76 and I am now another proud owner of an Evo running a rooted Froyo!!!!
So i am running the stock rom unlocked and rooted. Everything has been working fine until recently.
I wanted to flash a boot animation instead of just copy and paste with root explorer. So i booted into fastboot (volume hold then power). I then selected recovery and my phone shows the android thinking then he's flat on his back with an exclamation point above him. I followed the rootwiki for the gnex to the letter. Any ideas on whats wrong?
Thanks for helping a newb.
No solution from me.. but:
dalumberjack said:
So i am running the stock rom unlocked and rooted. Everything has been working fine until recently.
I wanted to flash a boot animation instead of just copy and paste with root explorer. So i booted into fastboot (volume hold then power). I then selected recovery and my phone shows the android thinking then he's flat on his back with an exclamation point above him. I followed the rootwiki for the gnex to the letter. Any ideas on whats wrong?
Thanks for helping a newb.
Click to expand...
Click to collapse
Afraid I can't help you but I had exactly the same issue. I used flashed the original recovery again and again but kept getting droid flat on it's back with the red exclamation mark. Finaly I decided that I found recovery imporatant enough and decided to flash CWM recovery. That gave me at least recovery back. I would prefer however getting stock recovery back. So if someone has a resolution I would be one happy camper.
Tried to flash it again and it gave me an error in adb saying faiked partition.
Any help is appreciated
Try flashing CWM with Rom Manager.
The android on his back with exclamation point is stock recovery. You have a few options: install ROM manager and flash clockworkmod through it (some people's phones need this done before each flash I think based on root process) or you can change the name of your recovery-from-boot.p file which is a file that causes ICS to revert back to stock recovery, and some have to use root explorer to change the read/write access to get clockwork to stick. I would just use ROM Manager for it. If you ever want stock recovery you can download the factory image file from Google and extract the recovery.img and use fastboot
- copy the recovery.img file to the directory that contains your fastboot utility
- start-up a terminal/command session
- put your phone into fastboot / bootloader mode
- type the following fastboot command to flash the stock recovery:
Code:
fastboot flash recovery recovery.img
At least my problem is solved. The fact that droid with the red exclamation mark is stock left me searching how to get into recovery then. It appears that if you hit Volume up and power shortly when you see that image it loads stock recovery menu.
Two simple questions: I want my GN to be close to stock, haven't flashed custom rom's radio's etc. What I do want is Root and SetCPU (for power saving options during screen off), rootexplorer, Volume+ etcetera working. I've managed to put them all on, now:
If I reflash stock recovery and lock my bootloader: will they keep on working and:
If I get OTA updates: will they keep on working too?
Thanks in advance for any reply...
Diger36 said:
At least my problem is solved. The fact that droid with the red exclamation mark is stock left me searching how to get into recovery then. It appears that if you hit Volume up and power shortly when you see that image it loads stock recovery menu.
Two simple questions: I want my GN to be close to stock, haven't flashed custom rom's radio's etc. What I do want is Root and SetCPU (for power saving options during screen off), rootexplorer, Volume+ etcetera working. I've managed to put them all on, now:
If I reflash stock recovery and lock my bootloader: will they keep on working and:
If I get OTA updates: will they keep on working too?
Thanks in advance for any reply...
Click to expand...
Click to collapse
you can leave your phone unlocked and root with a method such as CF-Root and leave your factory recovery and OTA's will go through and install without issue. Having the bootloader unlocker doesn't effect OTA's at all. There are a some programs that claim they maintain root after OTA but even if they don't you can just re root with a program like CF-Root
joshnichols189 said:
Try flashing CWM with Rom Manager.
Click to expand...
Click to collapse
This. I had the exact same issue when trying to flash anything after I rooted. either flash CWM through rom manager or install CWM permanently if you haven't already. After I installed it I've had no issues.
Is it possible to manually update to 4.04 without installing a custom recovery? I downloaded the file, named it update.zip, put it in the root and rebooted holding down volume +/- and power. I chose to go into recovery and it just presented me with the red triangle with an exclamation point. Is there no stock recovery on these?
The problem you'll run into is that in order to update, the update needs to be in the cache folder, which you cant access without root.
im in same boat... tried this but got nowhere
http://www.androidauthority.com/ver...id-4-0-4-update-unofficially-available-50690/
williamthegoat said:
The problem you'll run into is that in order to update, the update needs to be in the cache folder, which you cant access without root.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=22182181&postcount=1
You can use the toolkit I guess to run a temporary copy of cwm. You might need to have the boot loader unlocked. Be careful if you are tempted to unlock your boot loader. It will wipe the phone of everything including your photos.
bunklung said:
http://forum.xda-developers.com/showpost.php?p=22182181&postcount=1
You can use the toolkit I guess to run a temporary copy of cwm. You might need to have the boot loader unlocked. Be careful if you are tempted to unlock your boot loader. It will wipe the phone of everything including your photos.
Click to expand...
Click to collapse
Will applying the 4.0.4 update relock your bootloader? I know you will have to reroot.
It did not relock my bootloader.
I only had to reroot.
I'm having an issue with my friend's GN,
He suffers from random reboots which automatically restore the phone information to a specific date in the past.
I tried the toolkit, manual root and unlock but no luck.
the bootloader itself relocks itself right after i try the "fastboot reboot-bootloader" command.
I cant flash CWM permanently.
Can this be the recovery partition kicking in? I tried renaming it and I didn't get an error.
I managed to root the device, but then I cant install any programs from the Market, I was trying to get Root Explorer to work to ensure that the recovery is renamed or removed.
Whenever I flash the bootloader to primela03 it goes back primekk15.
Is this a GSM GNex (i9250)?
i9250
To me it sound like you actually never unlocked the bootloader in the first place..
Edit: To be more constructive... I have no idea what "the toolkit" does or how it works.
To unlock your bootloader you boot into it and run "fastboot oem unlock". That's the whole process. I personally don't see the value of a toolkit obscuring that process.
Unlocking your bootloader will cause your phone to factory reset and wipe everything on it. Have you done this? Have your phone asked you to confirm this? Did you click the volume-rockers to "yes" and then confirm with the power-button? And then, did the phone get wiped?
If you cannot answer "yes" to every question asked above, you have not unlocked the bootloader. End of story.
When you boot the phone up there should also be an unlocked lock icon under the Google logo at the bottom of the screen.
This is a wacky situation,
I tried using GNex toolkit 6 (http://forum.xda-developers.com/showthread.php?t=1392310) and it never worked.
"fastboot oem unlock" unlocks the device, but the as soon as I try "fastboot reboot-bootloader" it goes back to it's locked state.
I tried flashing another bootloader right after I unlocked it, but it reverted to the old one after rebooting.
BlindWolf8 said:
When you boot the phone up there should also be an unlocked lock icon under the Google logo at the bottom of the screen.
Click to expand...
Click to collapse
Did that, but as soon as I reboot the lock icon goes away.
aGoGo said:
Did that, but as soon as I reboot the lock icon goes away.
Click to expand...
Click to collapse
Strange
There is a file that will put the stock recovery back when you reboot. I'm not sure what else that file does but maybe that's your problem?
Going from memory, I think the process is unlock via fast boot, flash clockwork recovery, boot into recovery, flash super user, I also removed that recovery file at this stage via adb even though other directions have you do it later with root explorer. And that was it. If you do it the way others wrote it up (using root explorer) you'll have to reflash the recovery again.
Sent from my Galaxy Nexus using Tapatalk 2
DeezNotes said:
There is a file that will put the stock recovery back when you reboot. I'm not sure what else that file does but maybe that's your problem?
Going from memory, I think the process is unlock via fast boot, flash clockwork recovery, boot into recovery, flash super user, I also removed that recovery file at this stage via adb even though other directions have you do it later with root explorer. And that was it. If you do it the way others wrote it up (using root explorer) you'll have to reflash the recovery again.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Here's what I just did:
1- Unlocked the recovery
2- Booted insecure image
3- pushed superuser
4- installed root explorer, ROM Manager via adb
5- in root explorer I deleted recovery-from-boot.p from /system and it came back then tried "adb shell rm /system/recovery-from-boot.p" and it's gone.
6- Tried downloading CWM from ROM manager and the phone reboots whenever it starts download and goes back to stock
rebooted and the damn thing still living in the past!!! even the recovery file is back!
aGoGo said:
Here's what I just did:
1- Unlocked the recovery
2- Booted insecure image
3- pushed superuser
4- installed root explorer via adb
5- deleted recovery-from-boot.p from /system
rebooted and the damn thing still living in the past!!! even the recovery file is back!
Click to expand...
Click to collapse
You have to go back in and re-apply the recovery. That file "recovery-from-boot.p" is like a "reset" file that puts the stock recovery back during the boot process. I suspect it may be re-locking your bootloader too, but this is just a guess.
After you do step 5, repeat steps 1 and 2.
aGoGo said:
Here's what I just did:
1- Unlocked the recovery
2- Booted insecure image
3- pushed superuser
4- installed root explorer via adb
5- deleted recovery-from-boot.p from /system
rebooted and the damn thing still living in the past!!! even the recovery file is back!
Click to expand...
Click to collapse
When you "Unlock the recovery," do you mean you flash a custom recovery or do you mean you unlock the *bootloader*? It's not the same thing.
aGoGo said:
Here's what I just did:
1- Unlocked the recovery
2- Booted insecure image
3- pushed superuser
4- installed root explorer, ROM Manager via adb
5- in root explorer I deleted recovery-from-boot.p from /system and it came back then tried "adb shell rm /system/recovery-from-boot.p" and it's gone.
6- Tried downloading CWM from ROM manager and the phone reboots whenever it starts download and goes back to stock
rebooted and the damn thing still living in the past!!! even the recovery file is back!
Click to expand...
Click to collapse
O_O
the only thing I can think of is a hardware problem is causing the device to do a hard reset every time you boot.
j.go said:
When you "Unlock the recovery," do you mean you flash a custom recovery or do you mean you unlock the *bootloader*? It's not the same thing.
Click to expand...
Click to collapse
I unlock and then flash or sometimes reboot another boot image.
DeezNotes said:
You have to go back in and re-apply the recovery. That file "recovery-from-boot.p" is like a "reset" file that puts the stock recovery back during the boot process. I suspect it may be re-locking your bootloader too, but this is just a guess.
After you do step 5, repeat steps 1 and 2.
Click to expand...
Click to collapse
Did that, the moment I reboot, everything goes back to normal :s
I'm also unable to wipe from the normal system settings, the phone reboots when we try that.
can it be related to this issue? http://www.galaxynexusforum.com/forum/rescue-squad/4093-data-not-wiping-cant-return-stock-3.html
If you have problems doing data wipe/factory reset, it's quite possible that storage is corrupted/failing. It may be whats causing all the random reboots and reverting to old info. Best to bring to a samsung center and make that warranty claim.
I'm not sure what you're doing wrong... but its something.
You shouldn't have to flash another boot loader. I'm not sure what you would gain from that with the phone being a nexus?
Flashing another recovery is necessary for flashing different roms, kernels, mods, root, etc.
If you are indeed flashing a different boot loader, may i ask why?
Sent from my Galaxy Nexus using Tapatalk 2
Don't just delete the file recovery-from-boot.p, as there's one more file that can do bad things. It's called "install-recovery.sh" and is to be found within /system/etc
Theshawty said:
Don't just delete the file recovery-from-boot.p, as there's one more file that can do bad things. It's called "install-recovery.sh" and is to be found within /system/etc
Click to expand...
Click to collapse
Actually, don't delete either file.
Don't touch recovery-from-boot.p at all, and rename the sh.
If you want to be able to install otas in the future, renaming the patch file will break the MD5 check. The file is harmless if the sh file is out of commission.
DeezNotes said:
I'm not sure what you're doing wrong... but its something.
You shouldn't have to flash another boot loader. I'm not sure what you would gain from that with the phone being a nexus?
Flashing another recovery is necessary for flashing different roms, kernels, mods, root, etc.
If you are indeed flashing a different boot loader, may i ask why?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm trying another loader because nothing else works, the phone is stock and running 4.0.2. auto update causes it to crash and reboot.
Hey there
I'm currently working through the below process... on my Verizon CDMA LTE Galaxy Nexus runing 4.0.2 Stock.
http://strifejester.wordpress.com/2012/05/01/imm76k-direct-for-verizon-galaxy-nexus/
Also watched this Video (but he doesn't get the error)
http://www.youtube.com/watch?v=dQ1HuteSnDE
And when i get to the part about running mempodroid as sh I get an error that says the following:
Segmentation fault See the below screen shot.
Does anyone have any advice on how i can get past this? I have restart phone and desktop many times and happens every time. I have the PDAnet drivers installed and everything else adb seems to be working.
Would love some help,thanks in advance. Really want to get this working tonight if possible.
Conty
You are not developing anything
Moved to Q&A
FNM
Sent from my PantechP4100 using xda premium
Why would you temp root? Why not just temp boot to recovery, flash the superuser zip, and then restart. You'll be rooted, and if you don't want CWM installed, since it is only temp flashed, it'll disappear as soon as you restart.
imnuts said:
Why would you temp root? Why not just temp boot to recovery, flash the superuser zip, and then restart. You'll be rooted, and if you don't want CWM installed, since it is only temp flashed, it'll disappear as soon as you restart.
Click to expand...
Click to collapse
I'm just following the process for the 4.0.4 install. How else can i do what i need? I'm quite new to my Nexus, i had a bionic before.
Thanks
Need the temp root to run mempodroid i think, can i do this another way? i honestly don't know
If you are on stock 4.0.2 (ICL53F), download the 4.0.4 OTA update zip that is posted here somewhere and put it on the root of the internal sdcard. Restart your phone into recovery (should be stock recovery) and apply the update. It will verify the system and flash the update if everything checks out.
From there, if you want to be rooted too, download the superuser package from http://androidsu.com/superuser/ and put it on the internal sdcard (location doesn't matter). Use fastboot to temp boot to recovery, you'll need a custom recovery file for this (CWM, CWM Touch, TWRP, etc.). Run fastboot boot <recovery image file> and it will boot into recovery. Select the option to install a zip file, flash the superuser zip you downloaded, then restart and you should be on stock rooted.
imnuts said:
If you are on stock 4.0.2 (ICL53F), download the 4.0.4 OTA update zip that is posted here somewhere and put it on the root of the internal sdcard. Restart your phone into recovery (should be stock recovery) and apply the update. It will verify the system and flash the update if everything checks out.
From there, if you want to be rooted too, download the superuser package from http://androidsu.com/superuser/ and put it on the internal sdcard (location doesn't matter). Use fastboot to temp boot to recovery, you'll need a custom recovery file for this (CWM, CWM Touch, TWRP, etc.). Run fastboot boot <recovery image file> and it will boot into recovery. Select the option to install a zip file, flash the superuser zip you downloaded, then restart and you should be on stock rooted.
Click to expand...
Click to collapse
Which CWM version do i want and will this include the radios if i do it this way, sorry kinda newb at this phone. very different to my bionic.
Thanks so much for your help tho
Eidt
I got into stock recovery and saw the android with the explanation point but when i click Volume up + power i get no menu...
I'm off to bed will check back in the morning and see if you have any ideas, thanks again for the help
Finally got the stock recovery to work, however it only allows flashing from ./cache and i cant get my update.zip to cache without root right?
So decided to just unlock bootloader and then it let me root and push to ./cache and then i flashed the update.zip
All seems to be working now.
Thanks for all the help
I love the fact its so easy to unlock and lock the bootloader. very happy with that lol
is there a way to re root the phone once its on 4.0.4 IMM76K ? as the Galaxy Nexus toolkit stops at IMM30B...
Thanks
Nevermind
Adrynalyne saved the day once again
http://www.droid-life.com/2012/02/06/how-to-root-android-4-0-4-on-the-galaxy-nexus/
Thanks Adrynalyne