Develop Bugs

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

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

Can't restore or even lock bootloader... Bricked?

I've been lurking for quite some time and haven't been able to find a solution for my issue. Here's what happened:
I cracked the screen on my Galaxy Nexus and got an insurance replacement. I then used ClockworkMod Recovery to copy over from my old device to my new device. All was good for about 12 hours when the new device started boot looping with the flashy color animation screen. I figured that might have been something I did, so I tried doing a factory reset and the like with ClockworkMod Recovery and managed to totally mess the phone. After trying to do a factory reset, the phone wouldn't boot up at all anymore -- I just get the dreaded red triangle with exclamation point. I tried formatting all the partitions with ClockworkMod (which was a bad idea). Ever since then, I've been stuck. I've spent several days so far trying to get this thing working. I have to note that Odin and fastboot modes work perfectly fine.
Among things I've tried unsuccessfully:
Flash to stock using Odin
--Odin says everything is fine, when I flash with a stock ROM that I downloaded. Upon reboot, nothing is any better and I still get the red triangle/exclamation point.
--When I try to use the tar files that ClockworkMod generated, Odin crashes immediately.
Push custom ROMs to /sdcard/ using adb while booted into ClockworkMod in hopes of getting the system to boot.
--This never works successfully. Sometimes I get no error but can't find the zip file. Other times I'll get an I/O error, or even a read-only error. The original backup is giving me checksum errors.
Flash factory ROMs using fastboot.
--I always get the red triangle/exclamation point.
Restore and flash with WUG's toolkit.
--Same thing as when I try to use fastboot. It seems that flashing the device goes fine, but the device will still not boot.
After every time I've flashed the device, whether using Odin or fastboot, I've tried doing a factory reset by pressing power+vol up+vol down and then selecting factory reset. This hasn't made any difference.
I'm about to give up on it and send the device back to the nameless insurance company, but I would like to lock the bootloader first. I can't even seem to lock the bootloader! In fastboot, I type the usual 'fastboot oem lock', and the device reports that it is locked, but after rebooting, the device always reverts back to having an unlocked bootloader.
Have I missed anything? Any thoughts? I'm lost.

Fyi, the red exclamation point is the stock recovery screen.
Try following the instructions in the "flash" link in my sig.
Sent from my Galaxy Nexus using Tapatalk 2

As well, issue the following commands when in fastboot:
Fastboot erase system
Fastboot erase userdata <- this will wipe by the way, including/sdcard
Fastboot erase boot
Fastboot erase recovery
Fastboot erase cache
And then flash the images in fastboot.
Sent from my Galaxy Nexus using Tapatalk 2

Thanks a ton for the helpful info -- I hadn't tried flashing userdata and system using that method before, and your write-up was definitely one of the more helpful I've seen.
Unfortunately, it doesn't seem to have helped. I used the factory 4.0.2 mysid/toro image on the link you provided. While flashing, the system seems to work absolutely fine, but it just reboots into recovery at the end.
I followed your instructions twice, including erasing the partitions. Also, after each try, I've tried doing a factory reset from recovery and then rebooting (after trying to boot a couple times), though none of this helped.

enginerrd said:
Thanks a ton for the helpful info -- I hadn't tried flashing userdata and system using that method before, and your write-up was definitely one of the more helpful I've seen.
Unfortunately, it doesn't seem to have helped. I used the factory 4.0.2 mysid/toro image on the link you provided. While flashing, the system seems to work absolutely fine, but it just reboots into recovery at the end.
I followed your instructions twice, including erasing the partitions. Also, after each try, I've tried doing a factory reset from recovery and then rebooting (after trying to boot a couple times), though none of this helped.
Click to expand...
Click to collapse
If you've flashed the system, userdata and boot images using fastboot, and you are still not able to boot into Android, I can only suspect that you have either a corrupt bootloader or a hardware issue.
And if odin does not work, then unfortunately I would suspect that there is a hardware issue.

This sounds like what happened to my phone as well. Someone else had it happen too. That's 3 nexus's in a week. Mine didn't even last 2 months.
I have a thread about mine and another user posted another thread a day or 2 ago. Mine boots into the system but is not erasable, not writable. Can't lock my boot loader. I've tried odin, adb, everything possible. I wish we could start a lawsuit because Samsung won't help me. I'm in the US and it's a gsm nexus that was purchased before the play store sold it. USA wont accept an international phone and UK Samsung won't take a phone from overseas. Basically they said I'm sh*t outta luck.

Thanks again for the help. I'm going to bite the bullet and just call the insurance company and try to send it back as a defective device. Hopefully they don't rake me over the coals.
I'll post back with an update as to how that goes.

You guys need to learn how to use fastboot and adb commands correctly to restore google's stock images.
Stop realying on toolkits thinking it will help you.
Also learning that the Red Exclamation Android is stock recovery!
Press the Power and Vol Up button will get you the stock recovery menu options to come up!
Not to be mean, BUT I hope the insurance company denies you, you totally screwed up the phone yourself.

I did not screw my phone up myself. My phone was never even rooted. I know very well how to issue adb commands and install images. Learn what you are talking about before you jump onto people or come across as a total di*khead

Alright, replacement phone is on the way. Thanks again for the help. I tend to think it is a hardware issue because of how the issue originally presented itself, but I'm still pretty new to the Android platform. It seemed to me that a watchdog timer was timing out or something similar.
Perhaps this will be the push I needed to start developing Android hardware/software... I'm all about embedded systems and would like to move beyond basic ucontrollers.

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.

[Q] Need Help, GNex Went Mad. Can't Boot up.

Hello.
This is my girlfriend's Galaxy Nexus SC-04D(NTT Docomo).
This is the 7th SC-04D that I've played around with.
So I did the usual stuff.
Unlocked bootloader, rooted it, sim-unlocked the phone, installed AOKP and all went well.
While finding some apps at the Play Store, the phone suddenly hanged.
Then the display dimmed and some weird lines appeared.
So I forced shutdown the phone.
After that, phone won't reboot.
I can enter bootloader and download mode.
But, recovery is gone.
I can not flash a custom recovery as well, but I can enter it temporarily using the GNex toolkit.
Attempting to clear cache or factory reset was futile, everything is not mounted, and won't allow me to do so using cwm.
As I can enter download mode, I also tried flashing stock google image, but odin crashes when flashing it.
I also tried OMAP flashing, but gets stuck at:
» Sending data (131072 bytes) ::::::::::.......... [65536]
Can anyone help me on this?
I really have no idea what caused this as well.
As I mentioned, this is the 7th GNex(mine and friends') that I've played around with.
And has always been customizing since my Galaxy S days.
I'd appreciate anybody's help

Here's another weird thing.
I used the GNex Toolkit to relock the bootloader.
Operation is successful.
However, after restart, fastboot status goes back to UNLOCKED.

lemmy_0 said:
Here's another weird thing.
I used the GNex Toolkit to relock the bootloader.
Operation is successful.
However, after restart, fastboot status goes back to UNLOCKED.
Click to expand...
Click to collapse
Don't trust toolkits, read the stickies and do the whole thing manually.
Swype'ed on my CM10 Galaxy Nexus

hi thanks for the reply.
I did it manually as well.
even flashed a boot and radio image with it.
however, after reboot, it goes back to having no boot or recovery image, baseband is unknown and bootloader unlocked.

Your problem is like this? img843.imageshack.us/img843/8599/img0068ar.jpg
The my too

nope, mine can't boot

Question Fastboot boot loop?

Must be rusty in my old age, but I dont remember having any of these issues back with my previous android phones... the 11 is my first new one since the 6T though.
Whats my situation:
Phone boots into fastboot, attempts to boot to recovery, or continue, or restart all end back at fastboot. Can issue fastboot commands, but all roads seem to lead back to fastboot.
How I got here:
When I first got my phone, I unlocked the bootloader via fastboot command, but for some reason my phone wouldn't let me set a pin. Be it numeric, alphanumeric, or pattern, it would never let me confirm after putting it in the second time, and consequently I couldn't register a fingerprint or face scan. Reddit suggested that this sometimes happens after bootloader unlock but can be resolved by re locking and unlocking again... ok fair enough, haven't done much yet, whats another factory wipe.
fastboot flashing lock command - finished, boots straight back to bootloader
fastboot flashing unlock command - finished, ok time to try booting through to see if it fixed the problem... stuck in fastboot.
I'm rusty enough to want to stop here and seek guidance before I further brick my phone. I have fastboot access so in theory I should be able to flash an image from here? Any guidance would be appreciated. I'll admit I've fallen off the scene hard (new baby, job etc) and perhaps I should have just left my phone locked... but habits die hard eh?

You can only flash the full rom /images with unlocked bootloader
With locked bl you becomes the messages
Flashing on locked states not allowed

did you flash a patched init_boot.img after your first unlock?

benhc911 said:
Must be rusty in my old age, but I dont remember having any of these issues back with my previous android phones... the 11 is my first new one since the 6T though.
Whats my situation:
Phone boots into fastboot, attempts to boot to recovery, or continue, or restart all end back at fastboot. Can issue fastboot commands, but all roads seem to lead back to fastboot.
How I got here:
When I first got my phone, I unlocked the bootloader via fastboot command, but for some reason my phone wouldn't let me set a pin. Be it numeric, alphanumeric, or pattern, it would never let me confirm after putting it in the second time, and consequently I couldn't register a fingerprint or face scan. Reddit suggested that this sometimes happens after bootloader unlock but can be resolved by re locking and unlocking again... ok fair enough, haven't done much yet, whats another factory wipe.
fastboot flashing lock command - finished, boots straight back to bootloader
fastboot flashing unlock command - finished, ok time to try booting through to see if it fixed the problem... stuck in fastboot.
I'm rusty enough to want to stop here and seek guidance before I further brick my phone. I have fastboot access so in theory I should be able to flash an image from here? Any guidance would be appreciated. I'll admit I've fallen off the scene hard (new baby, job etc) and perhaps I should have just left my phone locked... but habits die hard eh?
Click to expand...
Click to collapse
You need to re-unlock the bootloader in the original china ROM!
I can help you if you get stuck on this issue ! pm me! !

I did indeed reunlock the bootloader. I imagine the issue possibly when I was attempting to root by patching a boot img with magisk and flashing that... Although after doing that my phone seemed to operate fine.
Regardless I reflashed the original, and it seemed to still bootloop into fast boot.
I tried relocking the bootloader, going to recovery, etc. After some degree of insanity doing seemingly the same thing I got to stock recovery, and then back to bootloader then back to recovery, then it flashed me writing in Chinese and it booted normally.
Since then I've rebooted my phone with no issue.
Not sure what exactly happened to make it conditionally work/not work... But given the time I wasted on it and the infant I'm having strong second thoughts about bothering with an unlocked bootloader. I'm clearly not in my element anymore as my confidence of which files to flash and commands to do so was very low (hence the post). My initial suspicion was "I have fast boot I can just flash original rom and I'm back to square one at least" but was too "afraid" to proceed and brick my new phone.
To expand on the "why bother with unlocked bootloader", I feel like it's been 3 phones since I truly took advantage of unlocking my bootloader. Perhaps I need to read more about the current state to see if there is a value proposition for me, or if I'm just creating more work (to then root, magisk, TWRP, safetynet, windvine etc)

Same happened to me,
Possible solution:
I used fastboot enhance to flash the payload.bin all over again, after it finished it rebooted into fastbootd automatically, then I falshed the same payload.bin into fastbootd as well then it rebooted into system smoothly.