Related
I bought a Nexus 7 a couple of weeks ago and decided to root it a week later. I used the Nexus Root Kit to unlock and root. The rom is stock though. Now I notice that sometimes if I turn it off, it won't turn back on with just pressing the power button and it won't charge either. I manage to get it on again by pressing the power button along with the up/down volume buttons. Has my rooting screwed it up?
I have the same problem, but never know what is exactly happening to my nexus 7.
U need to wipe it and flash cm or something ...it needs a nice wiping in any case
Sent from my Nexus 7 using xda app-developers app
Hi, i dont think that the root is something to do with the turn on issue because i have mine rooted and i dont have Any problem.
Enviado desde mi Nexus 7 usando XDA Premium HD app
Mine is not rooted and it just did this today, shut all the way down and was it would not even show the charge symbol, I plugged it into the wall charger and it had a "fuzzy TV" look to it, which worried me, so I unplugged it and plugged it back in a few times until that 'fuzzy TV' look went away and it was all dark. Then I held the power button along with pushing the up and down arrows, and finally one of the combinations worked and it turned on to the power charge screen.
Im thinking it went so far completely dead that it just needed to be plugged in for a little while but I see that others are having the same issue. I wish we could know more as to why this has happened.
I thought I'd clean up the OP for folks who got here with similar issues as me since it seems more common than we'd like.
Scenario:
Phone does not turn on without the charger or USB plugged in.
When plugged in, it boot loops at the Google logo (i.e. turns off at the logo, and reboots) and gives what is beginning to be referred to as the the 'red LED of death'--where the LED just blinks read.
The bootloader is accessible when plugged in. But trying to boot into recovery causes a loop. If you try to enter recovery, the phone has to turn off then boot back into recovery. But turning off means that when it turns on it will loop at the Google logo. So, booting into recovery is NOT an option.
Download mode is also accessible when plugged in.
Since the bootloader is accessible, it is possible to flash the factory image to the phone, however, doing so does not resolve the boot loop, nor does it allow the phone to turn on without being plugged in.
Fixes which have worked for some people
Instructions in this post worked for a couple people. NOTE: you have to be able to get into the bootloader for this to work.
One person who left it in download mode plugged into the PC (which was off) overnight, and somehow the problem was resolved. Thread here.
Here's a post in this thread from a user who was able to get it booting up again by leaving it on the charger for a bit.
You fool.
abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
Tape the power button down so it goes into a power cycle. Leave it until the battery is totally dead. Then plug it into the wall outlet, let it fully charge. Then try turning it on.
Sent from my Nexus 4 using xda premium
Your computer only detects it briefly? perhaps it'll detect it if you boot into Bootloader mode (not sure if you were able to from reading the OP)
Press and hold volume down, volume up, and power until the device boots. If you successfully enter Bootloader mode you can find steps on how to return to stock here: http://forum.xda-developers.com/showthread.php?t=2010312
overhauling said:
Your computer only detects it briefly? perhaps it'll detect it if you boot into Bootloader mode (not sure if you were able to from reading the OP)
Press and hold volume down, volume up, and power until the device boots. If you successfully enter Bootloader mode you can find steps on how to return to stock here: [/QUOTE]
Yeah, it would be nice if...en if I get into the bootloader for a second.
Click to expand...
Click to collapse
abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
i am on the same boat. i already contacted CSR anh they will send me a new one. after flash new kernel and start antutu, the n4 crashed and completely dead.
I'm pretty sure the battery with the lightning bolt means its charging.
Sent from my Nexus 4 using Tapatalk 2
ntt1409 said:
i am on the same boat. i already contacted CSR anh they will send me a new one. after flash new kernel and start antutu, the n4 crashed and completely dead.
Click to expand...
Click to collapse
Omg.. you don't need a replacement. Stop trying to load roms and kernals if you do not know how.
sent via xda premium with nexus 7
Ulver said:
I'm pretty sure the battery with the lightning bolt means its charging.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, but it's already full charged. Even if I leave it on the charger for a while, it still doesn't start up
KonstantinKeller said:
Tape the power button down so it goes into a power cycle. Leave it until the battery is totally dead. Then plug it into the wall outlet, let it fully charge. Then try turning it on.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I would say try this to drain the battery. Then charge it and see what happens.
So how exactly did the phone brick? Just so everyone here knows what not to do. Is it the kernel that caused it since its still in experimental stages?
Sent from my Nexus 4 using xda premium
abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
Have you tried reflashibg or using your nan droid back up from the recovery console?
Just because our won't not does not mean it is bricked.
It is really ticking me of that many people do not even have our phones and you are exchanging because of ignorance. Surely all these exchanges must impact stock. I know they keep extras but how many?
Stop messing with things you know nothing about until you at least learn..
sent via xda premium with nexus 7
abnormalreply said:
Yeah, it would be nice if I could get into the bootloader :/
But as I mentioned, it 'thinks' the battery is dead so it just keeps turning on and off even if I get into the bootloader for a second.
Click to expand...
Click to collapse
That's the point. It'll turn on and off until the battery is ACTUALLY dead. Then, charge it fully, and try to start it.
Dude this happened to me last night! Same ROM kernel combo! And fired up an tutu after ocing point is this should not be happening just made a thread and seen this here! Freaky! I'm telling u people beware something is up for sure been doing this a long time never seen this before
First if you have an unlocked bootloader, your replacement won't be free. As soon as Google gets it and realizes it's unlocked they will charge you full price for your replacement.
Second, Nexus devices are next to impossible to brick. There is probably a way to reset the device. I would try first unplug the device from your computer or charger and try holding the power button for a full 15-20 seconds. Then try booting into bootloader or recovery. If that doesn't work, try holding volume up and power for 15-20 seconds. If that doesn't work, try volume down and power for 15-20 seconds. And if that one doesn't work try holding all 3 down for 15-20 seconds. This sounds like a problem that would more than likely be fixed by removing the battery and rebooting. Since this doesn't have a removable battery there has to be a built in 'hard reset' that will power cycle the phone.
I am willing to bet there is a way to get this working. I guarantee if I had it here in front of me I could.
Also, like someone else has said before, if you are a not good at diagnosing problems, troubleshooting problems, fixing this kind of stuff on your own and adb/fastboot, it makes no sense to be using experimental software on your device. Especially if you plan on pushing its boundaries by overclocking and running benchmark software. If I were you, after you get this straightened out, wait a while until stuff is more ppolished and tested better.
So, by sheer luck, I was able to get into the bootloader and have it stay on. I was then able to use the toolkit (option 9) to flash the google factory stock image. This completed successfully, and I was also able to re-lock the bootloader, but I still have the same problem as I did before: battery charging icon and constant reboot. So, it's completely stock now and the issue is still there. Would it be reasonable to assume that the issue isn't software and I somehow got a hardware failure?
Yo hold power down then plug USB in then right after hold all three button .like after u plus in USB while holding power button then at same time hold volume buttons also this is how I got into download mode.....but.....phone was not detected and comp SD there was a driver failure. But yes dude phone was charged. And I had same exact combo as u I mean same exact. This is why it is freaky. Aokp was fine all day then when I flashed faux test kernel and fired up antutu I just had a flash then nothing. Not blaming anyone of course it was me who chose to flash after all this is custom software and I love these guys work just wish I knew what did it ....like what actually did it
Richieboy67 said:
Omg.. you don't need a replacement. Stop trying to load roms and kernals if you do not know how.
sent via xda premium with nexus 7
Click to expand...
Click to collapse
Seriously... thousands of people waiting for the phone to become available, and people who deserve to have their phone bricked are getting 2nds for free.
abnormalreply said:
So, by sheer luck, I was able to get into the bootloader and have it stay on. I was then able to use the toolkit (option 9) to flash the google factory stock image. This completed successfully, and I was also able to re-lock the bootloader, but I still have the same problem as I did before: battery charging icon and constant reboot. So, it's completely stock now and the issue is still there. Would it be reasonable to assume that the issue isn't software and I somehow got a hardware failure?
Click to expand...
Click to collapse
I was able to do the same thing but it would vibrate then see Google for a sec then nothing and back to a blinking red light....dude this is crazy I can't. Believe this happened to another person the same exact way
dammit. And I was just going to try this combo. Guess that's gonna be a no go.
Last ditch effort is to unscrew the two t5 screws at the bottom and do a real battery pull. Probably wont work, but what do you have to lose?
hey guys out there i really need your help,
my nexus 10 doesn't boot anymore, and i dont mean something like getting stuck at the bootscreen, in doesnt respond in any way, no matter how long i'm pressing the power button.
display still works because when its plugged in and i press the power button it shows me the battery which is completely white, that does mean that it is fully charged, or? unfortunately that is the only vital sign i can get...
im running cm 0301 nightly with stock kernel, just turned it off this morning and now this
did anyone experiece the same and could help me?
thanks in advance
gilbus said:
hey guys out there i really need your help,
my nexus 10 doesn't boot anymore, and i dont mean something like getting stuck at the bootscreen, in doesnt respond in any way, no matter how long i'm pressing the power button.
display still works because when its plugged in and i press the power button it shows me the battery which is completely white, that does mean that it is fully charged, or? unfortunately that is the only vital sign i can get...
im running cm 0301 nightly with stock kernel, just turned it off this morning and now this
did anyone experiece the same and could help me?
thanks in advance
Click to expand...
Click to collapse
2 possible solutions, first is the easiest.
1. While it's plugged in to charger and the battery is showing hold in power and up/down volume buttons together for about 5 seconds after battery disappears and release power while continuing to hold up/down volume until recovery comes up.
If your warranty has expired then try second option
2. Open it up and disconnect battery, hold power for 10 second then reconnect and power up.
AW: [Q] Nexus 10 doesn't boot anymore
Hmm, first solution doesn't work, but it once vibrated and the screen blinked for a short moment when I plugged it in after some time, unfortunately I can't reproduce it :/
I already rooted so I might have no warranty at all anymore but if it is a hardware bug they have to repair, or?
I bought it last December.
At least my friend got his rooted i9300 replaced without any cost when it got sudden death.
Actually don't know what to do now :/
Sent from my GT-I9300 using xda app-developers app
AW: [Q] Nexus 10 doesn't boot anymore
OMG, I knew that charging does take long, but it needed 3 hours to get enough juice just to boot up
It did boot, but shows 0 percent battery ^^
I'm gonna charge it the whole night without shutting it down, let's wait until for tomorrow
Nevertheless thank you for your advices
Sent from my GT-I9300 using xda app-developers app
gilbus said:
Hmm, first solution doesn't work, but it once vibrated and the screen blinked for a short moment when I plugged it in after some time, unfortunately I can't reproduce it :/
I already rooted so I might have no warranty at all anymore but if it is a hardware bug they have to repair, or?
I bought it last December.
At least my friend got his rooted i9300 replaced without any cost when it got sudden death.
Actually don't know what to do now :/
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Just send over if all solution not working, don't talk anything on root.
Sometimes they don't care, or don't know.
At least I had send for repair for Nexus One & S III before, and both was root.
AW: [Q] Nexus 10 doesn't boot anymore
Well, it does work now again but only shows 5% battery after 6 hours charging with wall.
Gonna send it in nevertheless, if they ask for root I'll just flash stock and send it
Sent from my GT-I9300 using xda app-developers app
I placed my nexus 10 on charging yesterday, and after a while (2-4 hours later) when i came back, i found the device to be turned off, I tried the power button in all the combination with volume buttons, but still no luck (even held the power button for 3mins) I searched online, and couldnt find any help on other forums. Some said to keep it on charging overnight and then try powering it up. But still no luck.
I dont get any notification when i connect it to charger, although when i press the power button while connected the screen lights up, and battery charging sign shows up.
Any help would be greatly appreciated.
epicbearman said:
I placed my nexus 10 on charging yesterday, and after a while (2-4 hours later) when i came back, i found the device to be turned off, I tried the power button in all the combination with volume buttons, but still no luck (even held the power button for 3mins) I searched online, and couldnt find any help on other forums. Some said to keep it on charging overnight and then try powering it up. But still no luck.
I dont get any notification when i connect it to charger, although when i press the power button while connected the screen lights up, and battery charging sign shows up.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
So you cannot even get to the recovery?
You ether over charged it (very unlikely to happen) or you have a faulty N10.
Sent from my Nexus 4
andyabc said:
So you cannot even get to the recovery?
You ether over charged it (very unlikely to happen) or you have a faulty N10.
Sent from my Nexus 4
Click to expand...
Click to collapse
No, can't even get to recovery. But i have been using the device for over two months now, nothing like this ever happened. What about the charging sign when i press the power button. It might be some kind of a sleep mode or something, no?
epicbearman said:
No, can't even get to recovery. But i have been using the device for over two months now, nothing like this ever happened. What about the charging sign when i press the power button. It might be some kind of a sleep mode or something, no?
Click to expand...
Click to collapse
Could be a bootloader corruption, software issue, hardware issue or some part of the hardware "thinks" that it is still on when it is not causing it to not switch on.
Have you noticed any issues before it just came off like extreme overheating?
Sent from my Nexus 4
andyabc said:
Could be a bootloader corruption, software issue, hardware issue or some part of the hardware "thinks" that it is still on when it is not causing it to not switch on.
Have you noticed any issues before it just came off like extreme overheating?
Sent from my Nexus 4
Click to expand...
Click to collapse
Well, yes the tablet was getting overheated after a long session of hd videos, or games, but that use to happen all the times.
I believe this is normally called a "Sleep of Death" or sometimes "screen off death". Hold power + vol up + vol down at the same time for 5 seconds and you should boot into fastboot. From there hit the power button to turn the tablet on. Then go about finding a better ROM/kernel combo that doesnt give you this problem.
EniGmA1987 said:
I believe this is normally called a "Sleep of Death" or sometimes "screen off death". Hold power + vol up + vol down at the same time for 5 seconds and you should boot into the bootloader. From there hit the power button to turn the tablet on. Then go about finding a better ROM/kernel combo that doesnt give you this problem.
Click to expand...
Click to collapse
Like i said, its not working i tried using that combination, it wouldnt budge. Screen wont even turn on.
EniGmA1987 said:
I believe this is normally called a "Sleep of Death" or sometimes "screen off death". Hold power + vol up + vol down at the same time for 5 seconds and you should boot into the bootloader. From there hit the power button to turn the tablet on. Then go about finding a better ROM/kernel combo that doesnt give you this problem.
Click to expand...
Click to collapse
You just need to press power and volume down to enter the bootloader.
Sent from my Nexus 4
---------- Post added at 11:35 PM ---------- Previous post was at 11:34 PM ----------
epicbearman said:
Like i said, its not working i tried using that combination, it wouldnt budge. Screen wont even turn on.
Click to expand...
Click to collapse
Try press and holding the power button for around 10 seconds and then try powering it up again.
Sent from my Nexus 4
Are you using the charger/cable that came with your device?
Its working.
Weird how it was taking any input from the power button though. I kept the tablet on charging over night and i tried turning it on in the morning and it worked.
Thank you all.
epicbearman said:
Its working.
Weird how it was taking any input from the power button though. I kept the tablet on charging over night and i tried turning it on in the morning and it worked.
Click to expand...
Click to collapse
I've had my Nexus 10 for less than a week, and this morning I encountered this problem. I was working on setting up syncing through an app called FolderSync and SugarSync. Syncing of one of the folders seemed to go into a loop. The device locked up completely a couple times. I got the process running again and left it running while I went for a workout. When I came back no way could I get it turned on.
I had tried all the things suggested here before checking here for help. I'll try your "solution" of leaving the device on charge overnight. If I can't get it going tomorrow morning I'll return it to Staples, where I bought it.
I have an iPad and have never encountered anything even close to these problems. Bought the Nexus 10 specifically to run the Vim Touch app for Android. The only Vim app for the iPad is horribly crippled.
Sounds like this thread pretty much exhausted the possibilities by the time epicbearman discovered his "solution," but if by chance anyone has any further suggestions I would be grateful.
Thanks,
Eric Weir
I had the exact problem as the OP and none of my chargers worked. I then googled and found someone that said to try to charge via their PC USB instead of the wall charger. I left it plugged into the USB for a couple of hours and the charge went to 4% ( so it must have been very dead ) and all is well.
I charged it via the usb charger, and connected it to my pc overnight. Try doing that.
Take off the back and disconnect the battery and reconnect it
Sent from my Nexus 4 @1.67 GHz on Stock 4.2.2
IRX120 said:
Take off the back and disconnect the battery and reconnect it
Click to expand...
Click to collapse
Thanks. If I'd gotten this in time, I suspect it would've worked. But when I couldn't get it started after trying everything else and leaving it on charge overnight, I returned it to Staples.
Will order a Nexus 7 from Google. If I can get Vim Touch running successfully---my reason for wanting an Android tablet---and I find the screen to small for heavy writing---I want to get by with a soft keyboard---I'll order another 10 and give the 7 to my daughter.
Thanks again,
Eric Weir
Hacking noob here. As in never. Sorry if this is "yet another annoying noob" issue.
I just got an N7 today and I'm having boot issues. I was able to use the device initially, I got it setup and it charged to 100% earlier. Then I did my first shutdown in order to investigate the bootloader. Since then it has been difficult to get it to power on.
The device is brand new, stock, and nothing done to it, other than user setup, and USB Debugging has been enabled. And I haven't dropped it or gotten it wet or dusty or anything fail you might be thinking of. No crazy apps, not rooting ,etc.
Reading up, it sounds like I need to power off the device, then simultaneously press Vol Up, Vol Down and Power (for some amount of time) in order to get into the bootloader /recovery menu.
This does not happen. Nothing happens.
So I tried to power the device back on. It doesn't.
I plug in the USB cable and I don't see the charging icon appear.
I notice a possible discoloration near the usb port, which could simply be the spot where the notification led is, but there is a visible "spot" that can be seen there. Wondering if this is an indicated that something is fried?
After messing around with cables and random button pressing I have gotten it to boot a couple of times, and seen the charge icon a couple of times, but I'm starting to suspect that this device is effectively DOA. Its been charged sufficiently (>60%) ever since I got it.
1. Anyone have any advice on this? I have no plans to wipe the device, I wanted to actually investigate sideloading the OTA. Answer - Ignore this.
2. Am I missing something? Is there a different/specific order of operations to start it? Answer - Bobos will fail.
3. Does it matter if USB power is connected while trying any of this? I've tried 3 different sources. And none provide a consistent state. Answer - No.
4. Can anyone else confirm this "discoloration" is visible at this spot? (halfway between the bottom center and the display area) Answer - Its just the notification led.
UPDATE: Turns out that pressing all 3 buttons causes a portal to another planet to open over Manhattan. Do not do this.
Instead simply press Power + VolDown to get to the bootloader.
I expect you have a defective device. However, you might just be doing weird things with your buttons.
To get to the bootloader, you just need to hold down the power button and volume down button. You don't need to have the microUSB cord plugged in.
For simply booting up the system: there have been times when I've had to hold the power button down for a while in order to get the device to boot up.
Sent from my Nexus 6 using Tapatalk 4
You need to hold the power button down a few seconds to turn on.
Boot loader is Power+VolDown
The discoloration is the notification led.
Thanks for the replies! I was able to finally get into the bootloader menu by following xdhall's instructions. And from there, into Recovery. Since using this method I'm not having any power on issues. It may be a "bug" in how it registers button presses, because it definitely isn't acceptable to have my experience occur (no usb charge, etc)
On to trying to update to 4.4 via the OTA recovery method. Google can't stop me now.
Thanks to sfhub for speaking to the discoloration. I really wasn't sure if I saw it before this issue started. Better to panic and ask, then assume and fail.
Oh yeah, don't press down all 3 buttons for 10 seconds from power off, it does wierd things.
I have issues getting it to power on once in a while too. Have to leave it for a while or put it on charge for a while and then the power button works.
Sent from my Nexus 7 (2013)
I was just about to ask a similar question. Many thanks to zenrage for doing the work for me.
Sent from my SPH-L710 using XDA Premium 4 mobile app
BreakShadow said:
I have issues getting it to power on once in a while too. Have to leave it for a while or put it on charge for a while and then the power button works.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
If you get the blinking LEDs, that is because the power is drained too low.
No blinking LED,just doesn't boot always at any battery level whatsoever. No issues with the buttons, they work fine when on. Untouched and locked system.
Sent from my Nexus 7 (2013)
BreakShadow said:
I have issues getting it to power on once in a while too. Have to leave it for a while or put it on charge for a while and then the power button works.
Click to expand...
Click to collapse
I had that too...returned it.
It was totally random...and would shut down by itself at random even though I charged it recently. I think it's an issue w/ the battery level sensor because to get it to boot, I'd have to plug it in for 15min, then power it up...
My old N7 2012 never had that quirk
I'm glad you were able to solve your problem with your nexus 7! I hope you enjoy it!
Sent from my Nexus 5 using xda app-developers app