I picked up the Galaxy Nexus from Verizon yesterday and attempted the unlocking and rooting procedure on droid-life.com. It looked like it was working, but now I can not get into recovery. When I try, I end up stuck on the screen with Andy and a red yield sign. I can get into the bootloader and run fastboot from my computer. The phone does still boot up completely.
I've seen posts about using Terminal Emulator and flash_image to restore the recovery, but Terminal Emulator says it can't find su. So something must have failed with the rooting.
Is there any information I can gather to help with this? Any help would be greatly appreciated. I'm out of ideas. My only other rooting experience was on my OG nearly two years ago and it went flawlessly.
Download the image in this thread and flash via fastboot. Make sure to delete /system/reboot-from-recovery.p afterwards.
Android screen with red exclamation point is the stock recovery image. Press power and either up or down volume to get into the recovery.
But yes, you'd want to flash clockwork mod like the guy above me said. Also rename or delete that file he wrote, otherwise on every boot, your recovery will go back to stock recovery.
Sent from my Galaxy Nexus
Oh. I hadn't found any documentation on the stock recovery so when I saw Andy open with a red yield and exclamation sign, I assumed it was bad. Thanks for the help!
EDIT: Got it thanks.
Related
I was running calkulin's rom on my evo but I decided to give cyanogen a run for its money. I was successful in installing cyanogen 6.1, and when i went to go install the addons, they didn't install properly for whatever reason. I went back into recovery mode and did a wipe of the device and went to install a fresh install of culkulin .. but instead of selecting the item "install zip from sd card" i selected "install update.zip" even though I didn't have an update.zip on my device.
After it tried to do that, it asked me if i wanted to reboot, i selected yes, and now i can't get into recovery mode. I can get into fastboot, but when i try and select recovery, it goes to the white HTC EVO 4G screen, then it goes to the screen with the phone, a red triangle with the exclamation point. If i press vol up + power, it brings up the menu to install from update.zip, wipe cache, wipe data, and reboot. I've selected all the options, i'm LOST.
i'm on a 2010 macbook pro .. I have windows 7 installed via VMware but it doesn't want to recognize my phone.
I was able to install adb on my mac, but it still can't recognize the phone. Any help is much appreciated, i don't want a $300 paper weight. Thanks!
Somehow your recovery might have been overwritten. Download a recovery image, go into fastboot and run the following command:
fastboot flash recovery recovery.img
Where recovery.img equals the filename of the recovery image.
Amon_RA has a PC36IMG.zip of his recovery so you don't have to use command prompt at all, just go to bootloader and flash.
http://forum.xda-developers.com/showthread.php?t=705026
i don't have a way to access the commands via terminal or dos to my phone. my computer can't recognize my device .. i'd prefer to do this via OSX because W7 via vmware isn't stable on my machine.
where can i download a custom image .. i may be able to run it via unrevoked, but when i run unrevoked, it gives me the error Device "- exec'/system/bin/sh' failed: No such file or directory (2) -" is not supported at this time.
Sounds like recovery is corrupted, download pc36000.img fkr amon_ra 2.2.1, put it into your root folder of sd card and give it go from fastboot.
I am typing name of recovery from my memory, so it can be wrong.
I read other posts about typing fastboot recovery installation commands, but you have said your adb is not working, so give this a try.
Sent from my PC36100 using XDA App
I'm not sure how to get adb running on the mac but it should be fairly easy. I'd read up on getting your phone connected with adb/fastboot then get the custom recovery img file.
Then you'll do:
fastboot flash recovery recovery.img
(I'm not sure if amon has a readily available image file but you can get the img file for clockworkmod for the evo here: http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
Just click the evo link, copy it to your fastboot folder and rename it to recovery.img just to make it easier.
Edit, if you have an sdcard apater (or maybe put the card in a digital camera or something so you can access it) you can put this PC36IMG.zip file on it: http://www.mediafire.com/file/s3vsgfwcz5po8hs/PC36IMG.zip
then boot your phone with boot loader, it'll scan the file and hit volume up to apply the update.
Had issue yesterday, my phone would boot directly to fastboot. My issue was a corrupted SD card. I bought a new one and it did the same thing but was able to reformat and it works! Never had this issue until i start pushing dalvich cache to SD. Anyhow check your SD card, try another on see if you can boot a zip from fast boot.
i tried that and it works perfectly! I was able to get a custom rom loaded onto my device and boot up, then i re-ran unrevoked so i could get that custom recovery so i could reload one of my past back ups.
Worked like a charm!
dizzle247 said:
i tried that and it works perfectly! I was able to get a custom rom loaded onto my device and boot up, then i re-ran unrevoked so i could get that custom recovery so i could reload one of my past back ups.
Worked like a charm!
Click to expand...
Click to collapse
Glad to hear. Disaster averted
dizzle247 said:
i tried that and it works perfectly! I was able to get a custom rom loaded onto my device and boot up, then i re-ran unrevoked so i could get that custom recovery so i could reload one of my past back ups.
Worked like a charm!
Click to expand...
Click to collapse
He never said what worked. I am having the same issue and would like to know what worked.
Im actually stuck on the htc evo screen. I can access fastboot as well. Where do i go from there.
I'm having almost the exact same problem as dizzle247. I've tried to flash PC36.img and tried using a new recovery.img but it keeps on sending back to the beginning. I don't know if the fact that my phone is set to S-on has anything to do with it but if I try to switch it off it fails.
Please help
The same thing happened with my phone. How did you end up solving the problem?
If you're in that situation, gona have to run an RUU.
Any solution yet?
How would you run RUU when the phone doesn't boot?
I am having same issue.
I can access fastboot.
I can load a pc36img.zip from my root SD.
I can not access recovery.
Re-flashed amon multiple times, no change.
If I try to go into recovery, it just shows white evo 4g screen.
If I try to regular boot, just shows whit evo 4g screen.
Any thoughts?
GrooGrux said:
Any solution yet?
How would you run RUU when the phone doesn't boot?
I am having same issue.
I can access fastboot.
I can load a pc36img.zip from my root SD.
I can not access recovery.
Re-flashed amon multiple times, no change.
If I try to go into recovery, it just shows white evo 4g screen.
If I try to regular boot, just shows whit evo 4g screen.
Any thoughts?
Click to expand...
Click to collapse
Unfortunately, most people that had this problem were never able to get out of it. It happened mainly on AOSP based roms. I'm typing in past tense because it was a fairly common problem a few months ago, haven't heard much about it since.
You can try running an RUU. If it doesn't work and you have insurance, you may need to take it in and eat the $100 deductible.
Some people were flashing radios through hboot and pulling the battery until the device wouldn't even turn on, then taking it in.
However you want to handle it is up to you. I wish that someone had found a solution, but I'd try everything you can find before taking it in. Every phone is different, something may work for yours.
Sent from my PC36100 using Tapatalk
hmmm, can any1 shed some light as to WHAT worked? other ppl have same problem, it would help if they stated the actual solution lol.
tooill said:
hmmm, can any1 shed some light as to WHAT worked? other ppl have same problem, it would help if they stated the actual solution lol.
Click to expand...
Click to collapse
There is no solution most of the people that have had this happen got a replacement
Sent from my PC36100 using XDA App
ugh >.<, i wanna fix mines and sell it, i cant replace it.. i bought it and had it flashed for boost, but now it has that problem so idk what to do with it..
Same problem need help evo4g
GrooGrux said:
Any solution yet?
How would you run RUU when the phone doesn't boot?
I am having same issue.
I can access fastboot.
I can load a pc36img.zip from my root SD.
I can not access recovery.
Re-flashed amon multiple times, no change.
If I try to go into recovery, it just shows white evo 4g screen.
If I try to regular boot, just shows whit evo 4g screen.
Any thoughts?
Click to expand...
Click to collapse
I'm having the same issue need some help
I am running the stock rom without root and unlock and I got the 4.0.2 OTA update 3 days ago. Today when I do the pattern unlock my phone froze and reboot. Now I cannot get pass the Google logo boot screen.
I am able to get into the recovery mode but I don't want to do a factory restore as I don't have anything backup yet.
Is there any solution to this boot loop problem? I am surprise that I am getting this problem as I am running the stock rom without any root / mod.
If there is no solution to this, is there any way I can backup my phone before doing the factory restore?
Many thanks!
You can back up via adb. Try searching in the General threads, since there's a long topic on this...
Good luck!
Thanks, I do find information about backup, but I can't find anything regarding the bootloop...
When i got stuck at the Google screen with a bootloop i booted into the bootloader/fastboot screen with vol up+down power and i redid the one click all process and it basically rewiped my device and put it back to working again with unlocked bootloader rooted etc....
All you have to remember is what build number you have and let the toolkit work its magic.
tigersgt said:
Thanks, I do find information about backup, but I can't find anything regarding the bootloop...
Click to expand...
Click to collapse
Sorry, forgot to mention. You're probably gonna have to wipe via recovery - which is why I pointed you to a back up...
danger-rat said:
Sorry, forgot to mention. You're probably gonna have to wipe via recovery - which is why I pointed you to a back up...
Click to expand...
Click to collapse
I can't find a way to backup without going into Android. I can only go to Fastboot Mode.
Anyone know how to backup the file using abd without getting into android?
Why did make 2 threads about this. Unlock the boot loader and use adb to flash your stock. Image files. You will loose all data unfortunately but I think that's the only way to fix it.
Sent from my Galaxy Nexus using xda premium
Ok I'm stuck with the same problem now. I wanted to flash a ROM, so I downloaded AOKP, flashed it and rebooted and the phone refuses to boot past the Google logo and keeps rebooting again and again. I am able to get into the recovery. I have flashed the ROM several times and its still the same. I have done a complete wipe as well. Still no go.
Fastboot command doesnt work in the bootloader either. I have made sure the drivers are installed, still there is nothing when I type fastboot devices. If I type any fastboot command it just says <waiting for device> or something like that.
Any other suggestions? :-s
Hi guys,
I just bought my One X today. Since it is my first android i am quite noob in all the issues regarding flashing/rooting.
I already unlocked the bootloader, install the clock recovery and then when I try to flash the new rom, i forgot not to extract the zip file so things start to mess up.
Now I am stuck at the HTC boot up screen. I have tried all the methods at:
http://forum.xda-developers.com/wik...very_-_what_to_do_in_the_event_of_a_bad_flash
Click to expand...
Click to collapse
but it doesn't work.
The problem is that when i type a command into cmd it keep showing waiting for device
So I don't know what to do now. I really appreciate your help if you could provide step by step.
Thank you so much
OK so as a noob you thought you'd try too root your 1st android phone after having it just one day??? oops! Lesson learned, next time read up loads first and maybe get used to the phone first before trying too root it. Anyway. . .
After installing Clockworkmod did you (as instructed in all the manuals I have read!) do a backup? If so just remove the usb, turn your phone off and go to the cwm boot menu and select restore. Fixed
recovery?
i see you have flashed recovery..
can you get to it??
Press POWER + VOL DOWN until it reboots and keep holding until u get to HBOOT..
from there select recovery and see if that shows up..
if you can get to Recovery, then you can either flash a CUSTOM ROM, or go back to STOCK recovery and then run RUU (a program provided by HTC that will restore you phone to stock) but you also have to relock the boot loader..
based on your choice more info may be required to help you
My best guess is that you have a messed up kernel...
So I was trying to put JB on my GN using this:
pcworld.idg.com.au/article/429778/how_update_your_galaxy_nexus_jelly_bean/[/url]
I reached to apoint where i had 4.04 yakju, but when I put the file to get JB, It said error and aborted, i went to wipe data and reboot, wipe data worked fine, reboot led me to the google home screen and is stuck there.
I can access fastboot. Recovery mode takes me to that android with the danger sign, doing another reset doesnt work, clicking reboot doesnt work.
I'm pretty nooby at this. I read a few other forums and they said something about flashing a new rom or something but I don't understand.
Please help! The phone isn't mine! Need help ASAP before owner finds out I messed up their phone, thanks!
If you can access fastboot and your bootloader is unlocked just flash a stock system image.
These are the reasons people shouldn't just one click everything they do. If you understood how fastboot worked you would be golden.
Reflash recovery. Then mount USB storage and then get a ROM on there and flash it.
Sent from my Galaxy Nexus using xda app-developers app
xjman said:
If you can access fastboot and your bootloader is unlocked just flash a stock system image.
These are the reasons people should just one click everything they do. If you understood how fastboot worked you would be golden.
Click to expand...
Click to collapse
The site I went to dumbed down everything, and all i had to do was input numbers into some program. I double checked what a fastboot was. I definitely don't know how to work that. I mixed up the fastboot with the bootloader...
how do i reflash recovery and get a rom on there? I know this is asking alot....sorry
My bootloader is unlocked but im not rooted. I will (figure out how to) root if needed.
Open up a terminal on your computer use fastboot to flash the recovery image.
Since you didn't take the time learn what you were doing to begin with, I would take the time now to go read. The answers are easily found with google, or searching this site.
Roughly, install adb and fastboot on your computer, load drivers for your phone, download the proper recovery and put it in the fastboot directory on your pc, plug in the phone boot to the bootloader
open term
./fastboot oem unlock
./fastboot flash recovery <nameofrecoveryimage>
I reached the fastboot part, but when i type in "fastboot flash recovery (file name) it says it cannot load file name...
What is the proper file that I should use? Running 4.04 YAKJU looking to just recover the phone back or switch to jelly bean, whichever is easier. (jelly bean if they are both the same)
okay okay okay, i think im almost there...got a rom and extraced it, i know how 4 files:
Boot 4,148KB
Recovery 4,478 KB
System 316,112 KB
Userdata 137,555 KB
Which one do I put for fastboot oem recovery (fileimagename)
Thanks
Stuck on Google screen
Background: GN is unclocked and rooted. I've had quite a few devices and have rooted them all and run custom ROMs. I am fairly familiar with all of the tools needed, but by no means an expert. I have the Android SDK with adb and fastboot installed on my Win 7 x64 machine as well as the samsung drivers. I loaded a Jelly Bean ROM the day after it was announced at Google I/O and ran it for awhile before I started having touchscreen issues. I removed the battery and restarted the phone and had no problems for about a week or so.
Problem: I started having touchscreen problems again, but figured it was perhaps due to the early version of JB that was ported over from the GSM version (I believe). I tried a few other versions that were released later and they would work for a few days and then the touchscreen issue would pop up again. At this point I started thinking it might be a hardware problem because if I twisted the phone (weird, but it worked) the touchscreen would respond. I flashed another version of the Jelly Belly ROM yesterday (//rootzwiki.com/topic/28677-rom-jelly-belly-v33-07122012-jellybean-411-pure-aosp-its-all-about-speed/") to see if it would work by chance. Unfortunately, I still encountered the touchscreen problem. After rebooting a few times my GN started bootlooping and would not load into Android.
Actions: At this point I tried to recover from a backup, but much to my dismay it failed (don't remember exact error). I tried a few other backups with no luck. I tried reflashing another ROM, no luck. Then I started seeing some errors when booting into recovery (E: can't mount cache/recovery/log. Around this time I also noticed I was getting errors with sdcard. I decided to take the phone back to stock using the verizon ICL53F factory image. I tried via numerous toolkits (Odin, Galaxy Nexus Toolkit and directly from fastboot) and have been unsuccessful. I've searched every forum and have literally tried everything I with no luck. I can flash new recoveries, but it doesn't solve my problem. Right now phone is back to stock with stock recovery and just bootloops at the Google screen.
I assume my phone is completely hosed, but am hoping someone might know something I don't and might be able to help me restore this phone.
Edit: I tried flashing an imm76k factory image via fastboot and was finally able to get in. I must have had a bad icl53f factory image...close call.
Please don't refer me to any more threads or forums........
I'm sure this has been done and done and talked about but I've been reading the **** out of forums and comments for a few hours now and trying to unroot my Sprint LG G2.
I had it running stock like a champ. rooted it. worked great. then I was attempting to flash lollipop and it required a recovery update (No Problem) I downloaded the correct files and bam! it says your phone is not rooted this requires a root (or something like that) I was already rooted SuperSU installed and root checker said I was fine. so what the hell I swipe to root while inside recovery and it goes to some black screen with tiny text saying fastboot: processing commands and won't leave the screen. I tried booting into recovery and same thing happens. Tried to reboot normal and I'm stuck on the LG logo with my led flashing between blue and green slowly. I CAN boot into download mode and I'm following this
http://pastebin.com/WTm1xFXz
and this
http://forum.xda-developers.com/showthread.php?t=2687929
to unbrick but having this error "Failed PreviousLoad()
Did I not get the right .dll file? I doubt it cause I only saw one...or is it the wrong .tot file? there was 3 or so
http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware
Please help!
When i'm in download mode the phone does say I am rooted. is there a way to just re-flash recovery and restore from my backups I did before all this? if I have to wipe this thing clean and start over I don't really mind I just need to get my phone back haha this is the first time this has ever happened to me and I consider myself tech savvy so idk what I did here (except re rooting in recovery like an idiot) thanks so much!
First question, is the download mode you see with a small status bar or the big one?
If you have the big one, download mode should work. The f flash software will verify the tot file. If that goes through you should be golden.
When it asked you in TWRP to root, that is a message telling you system or ROM file did not take.
If you want cm12, use zv8 tot. Root, auto-rec, update TWRP with blastgator bumped TWRP 2.5.1. Flash cm ROM or aosp, then gapps. And go