Galaxy Nexus stuck on Google logo boot loop help [GSM] - Samsung Galaxy Nexus

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

Related

Desperate Help Needed!

So I am the proud owner of a shiny, new Galaxy Nexus (GSM). Unlocked the bootloader and installed CWM recovery and was doing great. Today I decided to install the volume fix. Installed the zip through recovery, completed and rebooted. The phone got stuck in a bootloop over and over and over and over and would not boot Android at all. Did a ton of research here and everywhere and, in a panic, I booted into CWM recovery, reset the cache & did a full factory reset. NOW, the phone will not go past the Google bootscreen with the unlock symbol, no matter what I do. AND, I can't even flash the original google image because I can't get in to set USB debugging so my computer won't even recognize the phone (FYI, I'm on a Mac). I am at a complete loss and don't know what to do. If I could only get the computer to recognize the phone I could flash the original google image through Terminal, but alas, I can't. Any ideas? If I can somehow get this phone back up and running I would be eternally grateful. For now, I think I may be SOL. Thanks....
This happened to me, I was not able to solve the issue, even though I could push and pull data to and from the device via ADB. I could still not get past the google logo. I decided to lock the boot loader again and return to the store for a new device.
http://groups.google.com/group/android-building/msg/2cd2b16ed56a7e84
Sent from my Galaxy Nexus using XDA App
hartford said:
So I am the proud owner of a shiny, new Galaxy Nexus (GSM). Unlocked the bootloader and installed CWM recovery and was doing great. Today I decided to install the volume fix. Installed the zip through recovery, completed and rebooted. The phone got stuck in a bootloop over and over and over and over and would not boot Android at all. Did a ton of research here and everywhere and, in a panic, I booted into CWM recovery, reset the cache & did a full factory reset. NOW, the phone will not go past the Google bootscreen with the unlock symbol, no matter what I do. AND, I can't even flash the original google image because I can't get in to set USB debugging so my computer won't even recognize the phone (FYI, I'm on a Mac). I am at a complete loss and don't know what to do. If I could only get the computer to recognize the phone I could flash the original google image through Terminal, but alas, I can't. Any ideas? If I can somehow get this phone back up and running I would be eternally grateful. For now, I think I may be SOL. Thanks....
Click to expand...
Click to collapse
One more post like this in Dev section and you'll be banned for 3 weeks

Help urgent!!!!!!! Gn stuck on google symbol

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.

Bricked phone

Ok so my phone was acting up weird on my jelly bean rom on Verizon Gnex. So I went into clockworkmod and tried to factory reset. It did that but then when i tried to turn the phone on it started bootlooping the google screen. The only thing I can access is Clockworkmod now and when I hit the recovery option I get the Red exclamation Android. So I tried to do the back to stock/unroot in Wugs and that didnt change anything. Then I tried to do the restore stock recovery option but that didnt work. Now I want to return the phone to Verizon but I cant since it's still unlocked. And if i try to unlock it, it wont let me because the debug option isnt turned on and ADB isnt configured now since i restored everything. Any ideas?
hwkfan1 said:
Ok so my phone was acting up weird on my jelly bean rom on Verizon Gnex. So I went into clockworkmod and tried to factory reset. It did that but then when i tried to turn the phone on it started bootlooping the google screen. The only thing I can access is Clockworkmod now and when I hit the recovery option I get the Red exclamation Android. So I tried to do the back to stock/unroot in Wugs and that didnt change anything. Then I tried to do the restore stock recovery option but that didnt work. Now I want to return the phone to Verizon but I cant since it's still unlocked. And if i try to unlock it, it wont let me because the debug option isnt turned on and ADB isnt configured now since i restored everything. Any ideas?
Click to expand...
Click to collapse
1) You need to post questions in the Q&A section, not the General section.
2) Do not use toolkits.
3) If you want to go back to stock, use this.
4) Locking the bootloader has nothing to do with ADB or USB debugging. Have a read here to find out more.
To re lock the bootloader is done through Fastboot and has nothing to do with ADB. The code is 'fastboot oem lock'
Personally, I use toolkits as I'm lazy and don't feel like typing that every time, but I would know how to fix an error so its really up to the user.
http://android.stackexchange.com/questions/21460/what-does-fastboot-oem-lock-do
Sent from my Galaxy Nexus using xda premium
You're phone is not bricked. You moved than likely just agree not sure what you are doing. You're saying that you are in CWM and can't get to recovery. CWM is a custom recovery. It sounds like you are in bootloader and have the stock recovery installed. Get the android sdk and use fastboot to install a custom recovery (like CWM) and then install a rom. Our you can use fastboot to restore to stock using Google factory images (will erase your sdcard partition).

[Q] Unable to fix bootloop - even tried STOCK flash in fastboot. No luck.

Hey guys,
Long time lurker, ROM user since the Galaxy S days.
Weird, intractable bootloop problem here. Gets to boot animation sometimes gets to the "upgrading android" screen, then bootloops in a few seconds after upgrading a few apps. Usually bootloops during the boot animation (doesn't matter what ROM or Stock ROM I try). Ocassionally gets to my "SIM PIN" screen, then reboots before I have a chance to enter anything.
Normal State have Cyanogenmod and Franco Kernel running buttery smooth. (CM10.1M3 Snapshot + Franco 376 when problem started)
Problem Started When I tried to update CM to the new RC1 from the Cyanogenmod upgrade button in "settings". I had SuperSU installed overtop the built-in superuser. Everything was working fine.
What I have tried:
Have latest CWM: Have flashed, reflashed, wiped and re-wiped everything imaginable through CWM. All Caches, system sdcard, you name it, if it's an option in CWM I have tried formatting or wiping it and reflashing a ROM.
ROMs I have tried - CM10.1M3 Snapshot, CM10.1RC1 CM10.1RC2, ParanoidAndroid 3.5+ (Latest), Bigxie Maguro Latest.
Finally I got fed up and decided to go back to STOCK, unrooted, unlocked using fastboot.
I did:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader magurobootloader.img
> fastboot reboot-bootloader
> fastboot flash radio radioxxlj1.img
> fastboot reboot-bootloader
> fastboot -w update image-maguro-jdq39.zip
And after booting back into the STOCK google recovery (man I haven't seen that screen in AGES) and resetting factory clearing cache. Low and behold -
STILL BOOT LOOPS!!!! What the hell!?!
I'm at my wits end. Any suggestions would be great. What am I forgetting here?! I am absolutely desperate.
What is in the update image and where did you get it? I'd flash everything manually, skip the update command.
bodh said:
What is in the update image and where did you get it? I'd flash everything manually, skip the update command.
Click to expand...
Click to collapse
Ok good idea, I'll try. The update image was the stock image from google (can't post link - low post count) I just didn't remember the filenames when I was making the original post - but they are the official STOCK images - for the radio, the bootloader and the ROM.
Vihsadas said:
Ok good idea, I'll try. The update image was the stock image from google (can't post link - low post count) I just didn't remember the filenames when I was making the original post - but they are the official STOCK images - for the radio, the bootloader and the ROM.
Click to expand...
Click to collapse
Okay I tried flashing boot, system, userdata, and recovery manually with fastboot flash and after that I STILL get the rebootloop from google logo to boot animation to google logo. So weird.
Any other ideas?
Vihsadas said:
Okay I tried flashing boot, system, userdata, and recovery manually with fastboot flash and after that I STILL get the rebootloop from google logo to boot animation to google logo. So weird.
Any other ideas?
Click to expand...
Click to collapse
So decided to try TWRP just to see...well I dunno.
Interstingly enough when I got to hit "reboot" in TWRP it says "OS not installed!!" which is weird because I basically flashed the stock everything 4.2.2 (bootloader recovery, system, boot, everything) from fastboot. Then JUST flashed the TWRP recovery.
I really don't know what to make of this. I just tried keeping the battery out for like 2 minutes, then going back into fastboot and manually flashing:
bootloader
boot
radio
recovery
system
userdata
relocked bootloader
of the STOCK google maguro 4.2.2 (MD5 sum is good. It checked out)
And I still get a continuous reboot loop that doesn't even get past the "X" animation screen. Very ocassionally (1/10) it does get past that screen and I get to the screen where you choose your language, but right when I choose my language, the phone reboots and then continues the loop.
Honestly...Unless someone has another idea, I think I'm going to get another phone tomorrow and pray I'm under warranty. I hate to do it, because I've never had to do that before through all my flashing/ROM adventures...but I don't know what else to do. I've been using sideload for everything (except of course the fastboot flashing back to stock), but I doubt that has anything to do with it...I dunno crap.
anyone have any words of advice?
One thing I thought i might work was redoing the partition table in Odin. So I tried this method:
http://forum.xda-developers.com/showthread.php?t=2065470 (Thanks to Samersh72)
ODIN worked perfectly, download mode worked well, installed fine, and...
still bootloops!
Sometimes gets to "updating android" does a few apps, then bootloops. Once got to the screen where I select language, and before I could select anything - bootloop!
Do you guys think this is hardware? Right now I've installed stock 4.2.2 through ODIN and locked the bootloader in anticipation of returning the phone...
give a try to omap flash
Good Luck
samersh72 said:
give a try to omap flash
Good Luck
Click to expand...
Click to collapse
I looked into the OMAP flash method - that's some hardcore stuff. It looks like it's more for phones that can't access recovery, or hard seemingly bootbricked. I can actually do all of those things with my phone - I can write a new recovery no problem, I have fastboot access (Works well), I can even seemingly install ROMs - for instance the cyanogenmod boot animation plays fine - but everything boot loops.
I'm a bit worried to try OMAP Flash because it seems from the thread that some people are having their IMEI numbers erased or set to generic and I don't want that to happen since I'm actually still under warranty right now...
Do you think it's worth it to try?
Vihsadas said:
I looked into the OMAP flash method - that's some hardcore stuff. It looks like it's more for phones that can't access recovery, or hard seemingly bootbricked. I can actually do all of those things with my phone - I can write a new recovery no problem, I have fastboot access (Works well), I can even seemingly install ROMs - for instance the cyanogenmod boot animation plays fine - but everything boot loops.
I'm a bit worried to try OMAP Flash because it seems from the thread that some people are having their IMEI numbers erased or set to generic and I don't want that to happen since I'm actually still under warranty right now...
Do you think it's worth it to try?
Click to expand...
Click to collapse
you tried almost everything.... still on warranty:good:, everything is stock, so what are you waiting for, take it to service center
samersh72 said:
you tried almost everything.... still on warranty:good:, everything is stock, so what are you waiting for, take it to service center
Click to expand...
Click to collapse
Yeah you're right. OK done.
While I agree that the safest route is to return the device to warranty, omapflash is a tool which communicates with omap chip before even fastboot/bootloader is installed.
Have you tried viewing logcat/dmesg while device is booting to see why and/or its bootlooping?
Sent from my Nexus
bk201doesntexist said:
While I agree that the safest route is to return the device to warranty, omapflash is a tool which communicates with omap chip before even fastboot/bootloader is installed.
Have you tried viewing logcat/dmesg while device is booting to see why and/or its bootlooping?
Sent from my Nexus
Click to expand...
Click to collapse
I can't seem to get at logcat from this state. even if I try adb -d logcat or something similar it doesn't work. It doesn't pick up the log from the boot. Is it because USB debugging is disabled by default on the stock OS?
Vihsadas said:
I can't seem to get at logcat from this state. even if I try adb -d logcat or something similar it doesn't work. It doesn't pick up the log from the boot. Is it because USB debugging is disabled by default on the stock OS?
Click to expand...
Click to collapse
Yes, but There's a build.prop property that enables ADB debugging.. Since you have access to a custom recovery, you can mount /system rw and make your changes there.
Sent from my Nexus
Similar issue
Hey guys,
I am having a similar issue with my Nexus. It is running Phandroid 3 and one day just locked up, rebooted, and shortly after reboot (15-30 sec. after the OS loads) it freezes. I can still boot into CWM recovery and into fastboot mode, and have tried to flash it with the stock rom and bootloader. I also tried an OMAP flash, but that did not change anything as well. The odd thing is that when I try to flash a new rom (I have tried stock and other custom roms) it flashes as if everything is fine, but when I reboot it still has the phandroid rom on it. Another odd note is that when phandroid boots it notifies me that I have an incoming text message, but I removed the SIM card over a month ago. I have been struggling with this and would love any thoughts or opinions anyone has to offer. Thanks a lot!
lsal25 said:
Hey guys,
I am having a similar issue with my Nexus. It is running Phandroid 3 and one day just locked up, rebooted, and shortly after reboot (15-30 sec. after the OS loads) it freezes. I can still boot into CWM recovery and into fastboot mode, and have tried to flash it with the stock rom and bootloader. I also tried an OMAP flash, but that did not change anything as well. The odd thing is that when I try to flash a new rom (I have tried stock and other custom roms) it flashes as if everything is fine, but when I reboot it still has the phandroid rom on it. Another odd note is that when phandroid boots it notifies me that I have an incoming text message, but I removed the SIM card over a month ago. I have been struggling with this and would love any thoughts or opinions anyone has to offer. Thanks a lot!
Click to expand...
Click to collapse
I dont know if you already did but try to wipe /system also and then flash a ROM.
Sent from my Galaxy Nexus using XDA Premium HD app

Android 11 Beta 2 Stuck! HELP

Hey! Need a little help. I updated to Android 11 Beta 2. Now my phone is stuck on a boot loop. A li'l different though, phone boots up normally and stays on the lockscreen and alive. Can receive calls. But once I unlock with the pattern it shows ' Phone is starting' works for a good 2 seconds and then ends up on infinite bootloop until I Power down. How do I access my files on PC ? If I can get just few files out of it then maybe I can perform a factory reset . Please HELP!
kkrazzyyguy said:
Hey! Need a little help. I updated to Android 11 Beta 2. Now my phone is stuck on a boot loop. A li'l different though, phone boots up normally and stays on the lockscreen and alive. Can receive calls. But once I unlock with the pattern it shows ' Phone is starting' works for a good 2 seconds and then ends up on infinite bootloop until I Power down. How do I access my files on PC ? If I can get just few files out of it then maybe I can perform a factory reset . Please HELP!
Click to expand...
Click to collapse
some older app is causing the loop you mayneed to factory reset through recovery or flash factory images to ur devices ,( please backup your all data and i will advice you to remove the screen lock if possible as it may cause issues after flashing older or newer images
That's what I am asking. How do I backup?
kkrazzyyguy said:
That's what I am asking. How do I backup?
Click to expand...
Click to collapse
I use this tool in my computer to update my phone.
Make sure to follow and read the instructions.
Since you're phone is in boot loop, put your phone in into bootloader
https://flash.android.com/welcome?continue=/custom
Facing the same trouble, did it help?
Hi, I finally managed to solve this!! Was able to get the phone working with data intact.
So I got exactly the same problem yesterday and was looking around for a solution when I bumped on this thread, the solution suggested to use Android Flash Tool can work only if the bootloader is already unlocked, USB debugging is on and you edit the flash.bat file to remove -w from the command line, which would not work in my case since my bootloader is locked and unlocking through ADB would wipe all data
So the only good solution is to do an OTA UPDATE USING ADB SIDELOAD, I just downloaded the OTA file, connected the phone to computer, booted into recovery and used ADB to sideload the OTA and boom, the phone is its pristine self again, with ALL DATA intact

Categories

Resources