Develop Bugs

[Q] Cannot boot phone, vibrates 7 times, no LED

Hey,
I'm worried that my phone is bricked, but would like to hear if there are some options of reviving my phone without sending it to repairs.
I was in ClockworkMod Recovery as I wanted to update my ROM from oxygen-v.2.0-RC7 to the latest version.
I had wiped all data and dalvik cache and was in the middle of installing the .zip when my battery popped out (don't ask how).
Now my phone won't boot up at all. When connected to a charger it vibrates 7 times, but the LED is not on and I cannot boot it, even when trying Power+Vol. button.
Am I screwed? Or is there a way to save it?

Nevermind! It suddenly decided to boot up into Recovery on one of my attempts and I managed to restore my old settings.
It seems it just needed some time.
Mods are welcome to delete this thread.

[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/

Strange issue, need a little help.

I was on my phone, checking XDA, reading news and so forth. I put the phone down to grab some dinner. When I got back after eating I picked up my phone and it was unresponsive.
I held down the power button for a while and nothing.
I did a battery pull and I was able to boot to the Google splash screen with the unlock symbol. Unfortunately it just hung there.
I pulled the battery again, this time I booted in fastboot, then recovery. The clockworkmod recovery main menu came up in recovery, but when trying to do a restore or anything… The blue menu would disappear and not come back. I can get to recovery, but I am unable to do anything with it.
Last night I flashed to AOKP B26 from AOKP B25. I wiped cache and dalvik. I did not do a full wipe, but according to the dev you do not need to. This morning I flashed Morphic’s kernel TNP138-RD-FUV. I used this kernel on B25 with no issues for several days as well. I wiped cache and dalvik before flashing the kernel as well. CPU was set to the default 1190 and default voltages, with the on demand governor.
It is weird that I didn’t have any issues until hours later and the phone wasn’t even in use. It is as if it wiped itself. I am wondering how and why.
At this point I am going to do a full factory ODIN restore. I don’t think there are any other options.
EDIT, as posted below:
I was getting ready to do the ODIN restore when for the heck of it I decided to let it boot normally one last time. What do I have to lose.
I booted to the Google splash screen and set it down. I got a drink and took out the trash. When I came back I noticed it was at the boot animation! It sat at the boot animation for another couple of minutes but 10 minutes after pressing the power button I was booted up.
I let it sit for another 10 before I played with it. But now its like nothing ever happened. And it boots regularly now. I even booted into recovery and it is functioning as normal.
Any ideas what happened?

Dakota0206 said:
I was on my phone, checking XDA, reading news and so forth. I put the phone down to grab some dinner. When I got back after eating I picked up my phone and it was unresponsive.
I held down the power button for a while and nothing.
I did a battery pull and I was able to boot to the Google splash screen with the unlock symbol. Unfortunately it just hung there.
I pulled the battery again, this time I booted in fastboot, then recovery. The clockworkmod recovery main menu came up in recovery, but when trying to do a restore or anything… The blue menu would disappear and not come back. I can get to recovery, but I am unable to do anything with it.
Last night I flashed to AOKP B26 from AOKP B25. I wiped cache and dalvik. I did not do a full wipe, but according to the dev you do not need to. This morning I flashed Morphic’s kernel TNP138-RD-FUV. I used this kernel on B25 with no issues for several days as well. I wiped cache and dalvik before flashing the kernel as well. CPU was set to the default 1190 and default voltages, with the on demand governor.
It is weird that I didn’t have any issues until hours later and the phone wasn’t even in use. It is as if it wiped itself. I am wondering how and why.
At this point I am going to do a full factory ODIN restore. I don’t think there are any other options.
Click to expand...
Click to collapse
In cwm is there a 'go back' option at the bottom? If not scroll up and down a few times passing from bottom to top (looping) until it says like back button activated. If back is not active power button makes screen go off and on and does not select.
This is if you are not using touch enabled cwm.
Sent from my Galaxy Nexus using Tapatalk

if you can get into cwm then try fastboot and flash the factory images from the boot screen

_Dennis_ said:
In cwm is there a 'go back' option at the bottom? If not scroll up and down a few times passing from bottom to top (looping) until it says like back button activated. If back is not active power button makes screen go off and on and does not select.
This is if you are not using touch enabled cwm.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I am not using the touch enabled. I know that if you cycle through the menu too much it will disable the select button, but if you keep cycling it will enable it. This isn't that.
The screen is on, I can see the clockworkmod recovery & version in the middle of the screen. Just the ICS blue menu disappears completely. no go back or anything. just a black screen with the clockworkmod info in the middle. It is as if its thinking but it just hangs.

id suggest you try to use ADB from recovery to try and at least pull the sdcard files first of all
second id try to flash another recovery from fastboot then boot to recovery and flash a rom or restore backup
if the above doesnt work then factory image from fastboot is it

I was getting ready to do the ODIN recovery when for the heck of it I decided to let it boot normally one last time. What do I have to lose.
I booted to the Google splash screen and set it down. I got a drink and took out the trash. When I came back I noticed it was at the boot animation! It sat at the boot animation for another couple of minutes but 10 minutes after pressing the power button I was booted up.
I let it sit for another 10 before I played with it. But now its like nothing ever happened. And it boots regularly now.
Any ideas what happened?
Sent from my Samsung Galaxy Nexus - Verizon 4G LTE.

Google Nexus GSM stuck on google boot loop

My nexus is stuck on the google boot loop since this morning, i am on stock firmware no root or no nothing, can someone suggest me how can i fix this issue. i have mac and does not have access to any windows machine so i will be greatful if the suggestions will be accordingly for mac

switch off your phone . if you cant switch off the phone then take the battery out and put it back in. Press the volume up and down key along with the power key . this will take you into the bootloader. press the volume down button and navigate to the recovery section. press the power button . this will take you to the default recovery on your phone.
At that time you will see an android robot with an exclamation mark. press the volume up and down key along with the power once again. you should now see the option to update your phone , wipe/reset options. wipe the phone and reboot it . you should be ok after that.
I had the same problem with my gsm gnexus.

Hopefully factory reset using recovery works as krunal1981 suggested. If it doesn't then you will have to use Odin or Heimdall for Mac and preform a full restore. If you have a warranty and the first doesn't work, take it back to Verizon and tell them that your phone isn't booting anymore and they'll replace it.

krunal1981 said:
switch off your phone . if you cant switch off the phone then take the battery out and put it back in. Press the volume up and down key along with the power key . this will take you into the bootloader. press the volume down button and navigate to the recovery section. press the power button . this will take you to the default recovery on your phone.
At that time you will see an android robot with an exclamation mark. press the volume up and down key along with the power once again. you should now see the option to update your phone , wipe/reset options. wipe the phone and reboot it . you should be ok after that.
I had the same problem with my gsm gnexus.
Click to expand...
Click to collapse
Thanks Much this solved all my problems with the phone as of now, wonder what caused the phone to go in that ever ending loop

Question: Did wiping from stock recovery also erase your internal storage (/sdcard) or not?
Anyway - I have had this problem too, and all I can say is: A full wipe fixes it but only temporarily. It will happen again most likely. I believe it is a hardware problem with the internal memory. Next time it happens you should seek a warranty replacement.

when i do this all i get is the droid robot with an exclamation mark. my phone seems to go crazy at moments just keeps power cycling and gets soooooo hot and verizon just keeps trying to give my refurbed ones doing the same thing
galaxy nexus stock

Yes.. resetting the phone from the stock recovery erases everything
---------- Post added at 08:37 AM ---------- Previous post was at 08:36 AM ----------
when you get the android with an exclamation mark , press all the hardware buttons on your phone i.e volume up , volume down and the power button. this will take you to the stock recovery .

Phone just did this last night, it was on my desk and I saw it reboot to the google logo after which it would continually random reboot.
Did a factory wipe/reset, fixed temporarily, but within minutes, begins to do it again. No sim card in, etc.
Curious if there's been any more progress on this.

sphish said:
Phone just did this last night, it was on my desk and I saw it reboot to the google logo after which it would continually random reboot.
Did a factory wipe/reset, fixed temporarily, but within minutes, begins to do it again. No sim card in, etc.
Curious if there's been any more progress on this.
Click to expand...
Click to collapse
It's a hardware defect. The only permanent fix is a warranty replacement.
Fortunately the units with this defect seem to manifest it within the first few months so that the owner can figure it out and get a swap.

So, a bit more information here. I'll get to the result at the end.
I did the factory reset from recovery, that would allow the phone to boot and stay on for a few minutes, I found, after which it would go into boot loops again.
Once the phone was on, I had USB debugging on, and was looking at the phone files when I noticed that folders that were originally on the phone from before the wipe @ recovery would begin to appear, one by one. Complete with all the original files that I had before the factory reset. Once I noticed this, I performed a full wipe from the phone OS (Settings -> Backup & Reset -> Factory Data Reset).
This actually wiped everything, 100%. Made sure not to restore all apps from my google account, either, and guess what, more than 24 hours of not a single reboot. Heavy use for those 24 hours, as well. Been stressing the phone HARD.
Near as I can tell, there was some file or app that for whatever reason probably went rogue and was causing the phone to encounter something which I can only relate as being similar to a core dump/BSOD if you were on linux/windows. I don't study phone OS culture enough (I'm an auto service technician by trade) and haven't compiled a Linux box in over 10 years, so I'm a bit rusty on it, but it honestly doesn't surprise me that this is a definite possibility given all the different hardware configurations and all the different apps that are out there that are expected to work on everything.
So, there you have it, my experience, my fix, and what worked for me (so far). I'll keep everyone posted if I notice any random reboots or any future reboot loops.

I believe it's a hardware level defect with the eMMC. It keeps working fine again until it attempts to write some important file to that exact sector of the internal memory. Then it corrupts again and back to the boot loop.
When I had a defective unit, the longest it'd last before looping again was 20 days. Sometimes as few as five hours. If it spontaneously starts looping again - it's a hardware problem and there's no fix. You need a replacement.
Sent from my Galaxy Nexus using Tapatalk 2

So, here's an update on the situation with my phone.
The update, is that there is no situation. The phone is operating perfectly fine. Had it's OTA update to Jelly Bean a couple/few weeks back now, and is still running smoothly. Moderate to heavy data/wifi usage (past 10 days has seen 700mb wifi traffic, 1.2gb 3G/HSPA traffic) and phone hasn't been rebooted in over 300 hours.
I'll give periodic updates every month or so.

HOX Won't Boot

I need a bit of help with a stock HTC One X. As of this morning it won't boot up. I have made no changes to the ROM, everything is stock.
Tried entering the recovery panel and turning fastboot on then restarting but every time the system stops at the "HTC One" page after making a startup sound. Sometimes the screen will go black and hitting the volume keys will bring up the volume changer but that is it.
There was no warning of an OTA update or anything like that.
When charging the screen stays on and dims, but stays on the "HTC One" screen.

Factory reset HOX and it booted, but next day same issues. This is 3 times I've had to factory reset now.
Every time I restart or cold boot it freezes on the "One X" screen.

This exact same thing has just happened to me! Just 10 minutes ago
I have no idea what to do.
I have not attempted root or anything like that everything is stock (Optus from allphones).
All I did was restart and now I cannot get into the phone.
I can get to those options (fastboot) by holding down the volume down button and the power button but restarting it or powering it off there does not help.
I havn't tried a factory reset yet as I'm scared about loosing all my data.
Can someone please help!
Please please
I'm suprised someone else is having the exact same issue what the hell is happening

Have you tried using the Recovery option from the Bootloader?

Yeah I tried that.
It didn't do anything. I've since done a factory reset. That worked but I've now lost everything
Now that's it's allw whiped I figure I might as well root it and install android revolution. I hope it's just a software thing and this will fix it.

Pyrope said:
Yeah I tried that.
It didn't do anything. I've since done a factory reset. That worked but I've now lost everything
Now that's it's allw whiped I figure I might as well root it and install android revolution. I hope it's just a software thing and this will fix it.
Click to expand...
Click to collapse
Fair enough, if you're thinking of Rooting and installing ARHD etc then feel free to use my Guide : The Stock to Custom ROM Awesomeness guide
It'll take you from Stock to having ARHD on your phone ok
(Shameless plug)
http://forum.xda-developers.com/showthread.php?p=30471180#post30471180

Took it into HTC last night and had the firmware flashed. No problems now... 12 hours with numerous restarts just to make sure.
It looks like it was a corruption in the software. I noticed HTC turned off the fast boot option before giving the phone back to me. Took 30 minutes in total.

If it happens again, try to hold the power button and the "Homepage" button at the same time. You should see a grey box saying "Continue holding to restart".
Thats a full restart rather than a shell restart.
That may help.