Develop Bugs

[Q] HELP!! New stock nexus ui crashed, stuck at boot animation

Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.

This is the hspa version.

svntsvn said:
Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
Click to expand...
Click to collapse
The android icon you're referring to sounds like the stock recovery. In order to flash a ROM (even stock) from recovery mode, you'll need to load a custom recovery. This requires the device to be unlocked.
Not very often a stock setup needs to be restored. Generally, with the stock setup, only the /data partition is wiped (revert to factory default) and the issues are cleared. Not sure why a stock setup would need to be restore.
If you're still going to pursue reloading the system, without access to the normal android mode, the best route will be using fastboot. This can be done on a mac and the fastboot commands should be the same.
Hope that helps get a start!

This happened me earlier. I was able to factory reset it, which, unfortunately really annoyed me because I hadn't saved a backup..
Before the "Google" logo shows up, press and hold the power button and the volume up and down buttons.
Then go into recovery mode using the volume buttons.
When it reboots, you get that Droid with the hazard sign (which I know you're at, but just for the sake of others who need help) all you have to do is hold down the power button and WHILE it's held, press the volume up or down button and move to "Factory Reset". When you hold down the power button and press the volume rocker, a little menu will appear. It should only take a few minutes then.
Hope this helps. Apparently this is a WiFi issue. I'll definitely be keeping backups as of now..

I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.

svntsvn said:
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
Click to expand...
Click to collapse
I had the exact same problem happen last night with UI crashing and then the getting stuck at the boot animation. I was desperately searching online, looking to find a solution that didn't involve rebooting to factory setting and came across this post and did exactly what you did and it WORKED, very strange, I really wanna know what caused that!!!!

I've had the same problem with my Galaxy Nexus. I received it on December 21st, with stock 4.0.1 build. No root or unlock attempt at any time. On January 2nd I experienced this problems (UI process crash, screen not responding, reboot and stuck in boot animation).
The only solution was to do a factory reset and start over.
On January 10th same problem, same solution. Second factory reset.
I got the 4.0.2 OTA just two days after that. I thought that would resolve the problem. The phone seemed more stable, with less FC's and no trace of the UI crash. Indeed it lasted long...
Exactly until January 24th when I picked up the phone and seemed in the sleep of dead. Removed the battery, restarted the phone... and stuck in the boot animation.
Do you have any advice? Should I return the phone? Aside from those specific problems I am quite happy with the SGN and Android 4 in general. And I use it quite a lot (I have a very long train commute) without other problems.

Again...
It happened again!!
I don't know what to do anymore, this is not a usable phone when I have to reinstall and reconfigure every 3 weeks.

I may have found the problem
Well, not me exactly, but this bug report seems to fit the problem and the charging workaround. Seems to be a problem the file used to store the battery stats and draw the charge graph.
It also fits my usage (I try not to charge it up until 100%).
I can't post links to the forum, the issue is id number 24518 which you can find in code.google.com/p/android/

Galaxy nexus keeps rebooting

I have a stock GN, not rooted yet. Today my phone automatically shut off and now it starts back up, google logo shows up and all those colors come on for couple of seconds and then the phone reboots itself.
I can press both volume up+volume down + power button and get into a menu which gives me the options of Start, Restart bootloader, recovery mode, and power off. I choose recovery mode but then it goes on to an android sign with exclamation mark. After that I can't seem to get anywhere. I have tried volume up +power, volume down+power, and volume up+down+power but nothing seems to work. It just keeps on rebooting it self.
Any solutions to this problem??

There are two possibilities:
1) Software problem. Since you were stock, this is unlikely.
2) Hardware problem. This is more likely, in my opinion.
If you want to eliminate 1) as a possibility, you can try this:
1. Download the GNex Toolkit here
2. Install it & get the drivers working on your computer (if you haven't already)
3. Unlock the bootloader by selecting Option 3 (it'll wipe your phone)
4. Flash factory stock rom by selecting option 8
5. Try it. If it works, congratulations. (if you want to re-lock your bootloader, use option 11)
If this doesn't work, relock your bootloader and send it in for warrantee. (most likely a hardware problem)

....

FredFS456 said:
There are two possibilities:
1) Software problem. Since you were stock, this is unlikely.
2) Hardware problem. This is more likely, in my opinion.
If you want to eliminate 1) as a possibility, you can try this:
1. Download the GNex Toolkit here
2. Install it & get the drivers working on your computer (if you haven't already)
3. Unlock the bootloader by selecting Option 3 (it'll wipe your phone)
4. Flash factory stock rom by selecting option 8
5. Try it. If it works, congratulations. (if you want to re-lock your bootloader, use option 11)
If this doesn't work, relock your bootloader and send it in for warrantee. (most likely a hardware problem)
Click to expand...
Click to collapse
So, I did the above method and after flashing the factory stock rom it won't start up anymore. It doesn't respond to anything at all. It seems I've bricked it
Is there any way to unrbick it now? I'm assuming I can't send it in for warranty either now if it's semi bricked. Unless it's been completely bricked which means there is still a chance of getting a replacement phone.

I have the same prob on rooted SGN
This morning I switched off the airplane mode to be available, system crashed and restarted. And then still the same again - booting / android logo / restart again.. /./. I am using Android Revolution HD 2.1.5, for last month with no problems.
I tried to boot into recovery, then wipe the cache and reflash rom and radio from sd, it is still the same. I can see all the files on my int. sd with no probs.
Please help.

I'm thinking it might be a hardware issue, but I'll wait for another member's opinion before confirming.

Solved!!!
That's what I thought - HW prob, but it seems that luck is on my side, I hope. It helped to get back on stock but with total deletion including int partition
Anyway thanks for support.

630263 said:
That's what I thought - HW prob, but it seems that luck is on my side, I hope. It helped to get back on stock but with total deletion including int partition
Anyway thanks for support.
Click to expand...
Click to collapse
Was your phone rooted or bootloader unlocked before the problem occurred?
Anyways I've sent in my phone for warranty, hopefully samsung will fix it.

So my phone company called me today and apparently Samsung told them that it's corrosion(?) problem. When I asked exactly what does that mean they said it's moisture damage or physical damage that probably caused it. But I'm confused how could my phone possibly get moisture damage inside an otter box. I know how delegate these devices are and I know how to take care of them.
Anyhow it'll be $90 to fix it. I had no other option so I asked them to go ahead with the repairs. So frustrated with Samsung to be honest. I never dropped my phone once, never had any water damage, phone was always inside the defender case. And I still have to pay them for fixing my phone even though it's not my fault.

That's quite worrying, I just started having boot loop problems today. I've had the phone since Feb 29th and not had a problem with it yet, but today it started boot looping. I went into recovery and did a factory reset, was alright for a couple of hours then it crashed, started bootlooping again. Running stock 4.0.2 unrooted, I'm wondering if flashing 4.0.4 might help.

I'm in the same boat.... unrooting stock 4.0.1 firmware - canadian version from Negri.
April 23rd my phone crashed and started boot looping. Google logo - reboot - Google logo - reboot
Factory reset worked. I installed less apps than I had before figuring perhaps an app was corrupting something.
Yesterday - it happened again. Phone crashed. Boot loop. Factory Reset worked. Installed even fewer apps.
We'll see what happens this time around. I am hoping it is just a software thing. Hoping 4.0.4 gets pushed soon too.....

I've been having the same issue, plus sometimes my home screen it would lock up and wouldn't let me do anything, so I did a battery pull and it would boot loop for a half hour.
After the 3rd time I just took it to my Verizon wireless store, and showed them the situation and they couldn't figure it out, so their sending me a replacement, which I'm not looking forward too, don't want a semi-used phone....
Via Galaxy Nexus [LTE]

Rebooting Issue Solved.
I was also a troubled Samsung Galaxy Nexus user and my phone kept restarting more than half a dozen times everyday. Most of the times when I switched between two or more applications, or when it was simply idle on my desk.
However, I found a solution (at least in my case). All I did was root my phone, install cwm recovery, and flash a custom rom after wiping cache and factory resetting the phone, It's been about 5 to 6 hours now since I flashed the custom rom and I haven't had a single reboot or hang since.
Others who face this problem, please give it a shot, who knows? You might save your Galaxy Nexus instead of sending it back to get a replacement or spend some money on it for repairs which aren't even required in the first place.

I also had this problem unrooted. I had to give it to Samsung for the warranty
Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz

I got my nexus yesterday, almost immediately after first start it start to install JB from OTA.
I did buy 2000mAh samsung original battery and started straight with it. not even testing with 1750mAh bat.
after installing JB and needed softwares, it started to randomly reboot.
it rebooted even it was just in my pocket.
sometimes when I did do something, display freezed and after about 5sec it rebooted.
Now I did changed to original 1750mAh, and it havent boot at all couple hours, even I did play angrybirds space.
I wont dare to root it before I am very sure problem is with 2000mah battery.

2stardiver said:
I got my nexus yesterday, almost immediately after first start it start to install JB from OTA.
I did buy 2000mAh samsung original battery and started straight with it. not even testing with 1750mAh bat.
after installing JB and needed softwares, it started to randomly reboot.
it rebooted even it was just in my pocket.
sometimes when I did do something, display freezed and after about 5sec it rebooted.
Now I did changed to original 1750mAh, and it havent boot at all couple hours, even I did play angrybirds space.
I wont dare to root it before I am very sure problem is with 2000mah battery.
Click to expand...
Click to collapse
I could be wrong, but have you tried to clean the pin on the battery? Seems like battery and the phone isn't contracting too well
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz

Little update, phone did continue rebooting with original 1750mAh battery also.
I did also reset with recovery mode, and after that it did also reboot one time.
like it uses all memory/cpu and when nothing to do reboot (like windows )
I also did flash stock rom with toolkit but no help.
I will test rooting phone and flash another rom, or is it useless ?

after using couple days, not yet rooted.
Phone works and wont reboot even in heavy stress. but sometimes it just reboots by own not a single program in task list.
might reboot right after previous reboot or take hours to reboot.
stupid phone

I have been done some research.
I did one more time reflash google stock with rootkit, and forgot lock phone, it was almost 3 hours by own in wifi, no reboots at all.
when I noticed that I forgot to lock it I rooted whole phone and installed paranoid android 2.13 with CWM.
Now Ive been using 2 hours without any reboot, installing software, setting things up and using apps.
I dont understand at all:silly:
edit: noup, yesterday evening one almost reboot, paranoid android did reset itself but didnt even reset uptime. so I didnt count that normal reboot.
but after wake up this morning, it did reboot once when I put in my pocket, another just lying on table, once activating bluetooth in my car.
going to send it back to seller.

I have a similar issue, although not quite the same. Last night my phone started boot looping - it managed to boot up to the lock screen, and I can use it for about a minute before it dies and then reboots. This continues again and again (I have to pull the battery to quit it).
I have stock JB on my GSM GN, but rooted with an unlocked bootloader / CWM. I restored my old CWM backup, and had the same issue. I also wiped the cache and the dalvik just to see if that helped, but I had the same issue. I then tried to do a factory reset in CWM, but after I did that the boot loop just got to the nexus logo and died, entering a new (slightly shorter) boot loop. I went back into recovery and reflashed my CWM backup, and that at least got me back to booting into android.
I can't understand what's going on - could it be a hardware issue if it will happily stay alive in recovery, but dies after 1-2mins of android?
Thanks for your help. If it is hardware then I hope I can reflash the stock recovery / bootloader and unroot through recovery... the phone doesn't stay on long enough to do it when it's booted into full android!

Stuck on Boot.... any ideas?

I hate to ask, but I have to. I'm really stuck with my phone. It will boot but sticks on the Samsung Galaxy S II screen. I am able to get into recovery, but upon a data wipe, it hangs on the same screen on first boot. I am able to get into download mode and flashed EL26 repacked via ODIN, and upon reboot, it just hangs on the same boot screen.
Now some background...
About a few weeks ago, I started having crazy battery problems. Then, a few days ago, my phone would reboot anytime I did anything to it, turn the screen on, it'd reboot sometimes, or make a call, it'd reboot, text, it'd reboot. Basically, non stop constant reboots. I assumed it was just a jacked up battery, because I had no problems with the CM10 alpha I'd been running for the past two months, and now all this. I bought and overnighted a new battery and upon trying it out, I still had the same problems. Then, last night, from bed, I mobile odin'd el26 repacked as it was the only thing I currently had on my SD card, upon reboot, it stuck on boot screen and that's pretty much it since then.
Any ideas? Again, I can get to download mode and recovery, but even flashing, even a clean wipe, it just hangs on the screen on boot.

Since you mobile odined el26 kernel and you are coming from Jelly Bean it won't boot because you need a JB kernel to boot jelly bean.. And an ICS kernel to boot an ICS kernel..
With that said, to avoid any crazy scenarios, I would just grab a One Click Odin(any one will do) ... Boot into download mode.. Connect to PC and go from there to be safe
-TeaM VeNuM Like A Boss

try going into download mode and using one-click odin to go to el29 or 26

Jesus I'm dumb. I remember reading that a few months back. I forgot the el26 was just the kernel and you had to flash to it and then flash your new rom immediately. Thanks.
Any ideas on the crazy reboots?

try a different rom..or maybe ur battery is not being held in tight by ur phone or something..try sticking a piece of paper in there

supersaeed said:
try a different rom..or maybe ur battery is not being held in tight by ur phone or something..try sticking a piece of paper in there
Click to expand...
Click to collapse
Ok got it booting into EL29 and still having reboot problems. I'm thinking it's a power button issue or something. Sometimes when I press it to turn the screen off, it pops up the power menu, and sometimes it just reboots then.
I went ahead and dropped the $100 on a refurb through Assurion bc I need my phone for work and can't keep delaying it.

Note 2 boot load loop fix - cause System Memory full

Hi everyone. This is the first time ive posted anything on here. I will try to fully describe my problem that i really need help to fix.
My wife got my old Note 2 is rooted and she got my
Dad's old unrooted Note 2. After deciding that she didnt want a rooted phone she decided to use my father's unrooted phone. Due to apps updating and the internal memory getting full she ingored the warning message not really realising the outcome. The phone eventually shut itself down and is stuck on the Samsung logo (boot loop). So i gave her my old rooted phone back because she said that it just died. The same happened to the rooted phone too.
I asked before what she did and i was told nothing it just died. So i had nothing to go on. It wasn't until a week later when I tried to sort the problem out she said the System Memory was getting full and a message came up warning of this. So now I believe the problem is that the on board memory has got full and the phone seized. Much like what happens to a PC when the main hard drive gets full!
When i attempt to boot the phone up the Samsung logo show and stays on, never booting up. This happens with both phones. When i hold the Home key, Power button and Up volume switch. The phone loads the first Part of the boot up and at the moment it goes to the system screen it goes blank for a split second and back to the start of the boot. No matter how many times i try it fails. So I can't Factory reset or erase anything because i can get to it that screen.
So I try something else. I press the Home button, Power button and the Down on the volume to access the Download mode. This works fine. So i used Odin to try to put Rom onto the phone hoping this will solve the problem. Both phones connects to Odin alright and I can set up ready to load a rom onto it, however when i press start on Odmin to do its job everthing starts ok but then it goes red with a Failed error message. This happens when i try this on both phones, I seem to be stuck no knowing what to do. I have tried using all the ports on my laptop (window 7) and that makes no difference. The same happens on both devices.
I think i need to clear the memory somehow but have no idea how to do it when i can only access Download mode. I would be very grateful for any help on this but if all else fail I will try to build up static on a ballon and see if putting the near will wipe the memory, lol. Only joking. Im desperate to sort this out.
Any ideas?

try to flash twrp with Odin and download mode. Then enter recovery, connect it to PC and make some space.
But I really doubt it, apps won't install even when you have 500Mb free, so I think it might be hardware problem

Nexus 5X stuck at Google Screen. Won't boot stock recovery.

I was just using my phone like normal today opening up the transit app at the bus stop and it randomly froze and restarted. After that, it only shows the initial Google screen and just keeps bootlooping, but never even gets to the part where the OS is loading (with the google animation). It was just on stock 6.0.1, MTC20K I think. Was not rooted. Bootloader was/is unlocked. Secure boot was/is enabled. It won't even go into stock recovery (when I select recovery it immediately goes back to the Google screen and continues as if I had never selected recovery). I have tried manually flashing each piece of the latest factory 7.0.0 build (NRD90S), but even though fastboot says everything was successful, nothing seems to have changed. Any ideas on how to fix this?

Same thing just happened to me. I have no root or anything but it will not boot the OS. I hope there is a fix for the problem because I really want to use the phone.

Same thing just happened to me.
Click to expand...
Click to collapse
No recovery for you either?

What was the latest Build you had when it was working fine?

To get into the recovery plug the phone into your computer. Go into fastboot (vol down + power) and select the power off option. When it turns off or goes to the charging screen, hold volume up + power to boot to download mode. Once in download mode, turn the phone off by holding vol down + power, then go back into fastboot and you should be able to now access recovery mode. This is what I did, and then flashed back to 6.0.1 and it runs fine now. No Idea why going into download mode allows you to then access recovery and get one clean boot, but it does

Druas said:
I was just using my phone like normal today opening up the transit app at the bus stop and it randomly froze and restarted. After that, it only shows the initial Google screen and just keeps bootlooping, but never even gets to the part where the OS is loading (with the google animation). It was just on stock 6.0.1, MTC20K I think. Was not rooted. Bootloader was/is unlocked. Secure boot was/is enabled. It won't even go into stock recovery (when I select recovery it immediately goes back to the Google screen and continues as if I had never selected recovery). I have tried manually flashing each piece of the latest factory 7.0.0 build (NRD90S), but even though fastboot says everything was successful, nothing seems to have changed. Any ideas on how to fix this?
Click to expand...
Click to collapse
Had the same thing happen - Now typing to you from my warranty replacement. Only option.

blackpaw78 said:
To get into the recovery plug the phone into your computer. Go into fastboot (vol down + power) and select the power off option. When it turns off or goes to the charging screen, hold volume up + power to boot to download mode. Once in download mode, turn the phone off by holding vol down + power, then go back into fastboot and you should be able to now access recovery mode. This is what I did, and then flashed back to 6.0.1 and it runs fine now. No Idea why going into download mode allows you to then access recovery and get one clean boot, but it does
Click to expand...
Click to collapse
Surprisingly, this worked. I forgot about download mode being an option. I also am not sure why this worked.
Edit: The phone boots, but is still randomly rebooting rather often. Not sure why, as everything was wiped and it should have been a fresh install of everything.
Another Edit: Back to boot looping/not getting to the Android loading screen. I didn't do anything other than let it download my apps. Maybe it is a hardware problem after all because it did successfully boot into Android a couple times.

This seems to be a common problem which I have, too. Looks like a whole series of devices had these issues. Currently LG is unable to repair my device because auf missing spare parts they say. So after effortless 3 weeks they will send my unrepaired device back to me with a letter for my dealer to get back my money.
Nice quality and service, LG - NOT!

Janny82 said:
This seems to be a common problem which I have, too. Looks like a whole series of devices had these issues. Currently LG is unable to repair my device because auf missing spare parts they say. So after effortless 3 weeks they will send my unrepaired device back to me with a letter for my dealer to get back my money.
Nice quality and service, LG - NOT!
Click to expand...
Click to collapse
That is actually pretty good outcome. Pixel phone is coming out soon.

Just had this happen today. Streaming music over Bluetooth and using another app, then tried switching tracks in Google Play Music and the app froze. Phone was unresponsive with app on the screen, then screen went off and wouldn't power on.
I finally got it on by holding down power for 30 seconds, but kept boot-looping to Google boot screen. I was able to get into fastboot mode and wipe everything and install the factory image. Still doing the same thing!
Just got off phone with Google. Told the rep everything I had tried and she is working on a replacement order. Supposed to call me back after chatting with higher level support. I wish they would just send me a new Pixel phone, or the 6P at least!

Ive had the same issue, where I just couldnt get passed the Google screen, the only solution for me to get back on to my phone was to let it happen until the battery died. After i let the battery die i turned it back on normally and connected it to my charger, it hasnt turned off since but im sure it will sooner or later
Edit: Issue is still happening but the only way for me to turn it back on is because the battery dies

This just happened to my and my wifes phones...all within a week of each other. I sent my wife's in about a week and a half ago to LG for warranty service. I am hoping that they are able to fix it...it is still in the 'repair' phase. I am trying to decide whether or not I want to send my phone in (which just died yesterday) before or after LG figures out what is going on with my wifes. In both cases, the phones were running fine and just shut down by themselves. The battery was not dead. Each time, the phone will boot to the Google screen, but then immediate shut down. I can get in to recovery and do actions within there, so I do not believe it to be a battery issue. However, as soon as you attempt to boot the phone, it will die.

Were you guys using stock setups or custom ones?
Sent from my Nexus 5X using Tapatalk

Its a 'known' issue. Google has confirmed there is an issue. Only solution appears to be a warranty replacement.
https://productforums.google.com/forum/#!topic/nexus/r29mtzLFS0g;context-place=topicsearchin/nexus/nexus$205x$20bootloop
---------- Post added at 10:22 AM ---------- Previous post was at 10:21 AM ----------
Psychofrantics said:
Were you guys using stock setups or custom ones?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
on both phones, bone stock. Only difference was I was running the beta before getting the stock OTA and my wife's was full stock and received the stock OTA.

I'm having the exact same problem here. Running Android 6.0.1, rooted. Phone suddenly turned off and won't start past the "Google" screen, except for once when it booted fully then immediately shut down, and three times when it loaded the boot animation and shut down. Bootloader is unlocked and TWRP recovery is installed. I can access fastboot but not recovery. I've tried the suggestion of booting into download mode then recovery again, but that didn't work. I have NOT tried updating to Android 7 yet, so this isn't the same boot loop issue faced by some other users. I don't want to try flashing stock yet and lose my data because I have a ton of Tasker profiles and tasks that I haven't backed up in months and I don't want to risk losing them! Serves me right...
Any suggestions?

Same HERE !!!!

the samed for me, and still now i can't light it up

sagshar said:
I'm having the exact same problem here. Running Android 6.0.1, rooted. Phone suddenly turned off and won't start past the "Google" screen, except for once when it booted fully then immediately shut down, and three times when it loaded the boot animation and shut down. Bootloader is unlocked and TWRP recovery is installed. I can access fastboot but not recovery. I've tried the suggestion of booting into download mode then recovery again, but that didn't work. I have NOT tried updating to Android 7 yet, so this isn't the same boot loop issue faced by some other users. I don't want to try flashing stock yet and lose my data because I have a ton of Tasker profiles and tasks that I haven't backed up in months and I don't want to risk losing them! Serves me right...
Any suggestions?
Click to expand...
Click to collapse
In my opinion your EMMC probably died, but you can try reflashing factory images to see if it is some other problem.
I would only try LGUP as a last resort because it will set Allow OEM unlocking to false and lock your bootloader, making further experimentation difficult.
BTW IMO the Android 7 bootloop probably isn't related to Android 7. I think they are just saying hardware problem (EMMC failure) that happens to show up more frequently when you have large updates of OS.
The way Google worded it, it made it seem like Android 7 is killing some hardware because of some incompatibility with just some isolated hardware builds.
I would suggest you let it keep booting and flash some factory images and sometimes EMMC will come back briefly and boot. If it does, immediately backup as much as you can before doing anything else.

Same deal for me and they are sending a replacement. This is a MAJOR blackeye!

Is your phone under warranty then? I am having the same problem as everyone on here. I've tried everything. I bought the phone just over a year ago though, so am a little concerned Google will turn around and tell me it's not their problem... Even though this is clearly a fault!