I ran antutu benchmark and the phone automatically rebooted. I ran it again, and got forced closed. Now It won't boot up. On charging it, the charging symbol appears followed by the red notification led. On booting while charging, I can go uptill the google screen but not further or bootloader mode. Please help!
It is rooted with cwm and faux kernel and Dalvik and Bionic optimized libs
Ibrahim.Rahman said:
I ran antutu benchmark and the phone automatically rebooted. I ran it again, and got forced closed. Now It won't boot up. On charging it, the charging symbol appears followed by the red notification led. On booting while charging, I can go uptill the google screen but not further or bootloader mode. Please help!
It is rooted with cwm and faux kernel and Dalvik and Bionic optimized libs
Click to expand...
Click to collapse
In all honesty, you were probably right there, but you just didn't let it charge enough. I had a rlod the other day, I must've done it good this time because I had to let it charge for almost an hour before it would power back up. I can't remember though, if it actually chargers when the red light is lit, or if you need to unplug it and plug it back in so that it's plugged in with no red light, no power on, or anything. Let it charge while of with the red light on for about 20 mins. Then fiddle with it, unplugging and plugging back in, until you can get it to stay plugged in without powering it up or the red light coming on. Let it charge for about 20 mins like this too. Unplug it. Turn it on. Plug it back in immediately after seeing the google logo, let it finish booting and finish charging and you should be good. I've had around 5 - 7 rlod (mostly all my fault) and this method has worked every single time. I've never opened or rma'd my phone.
username8611 said:
In all honesty, you were probably right there, but you just didn't let it charge enough. I had a rlod the other day, I must've done it good this time because I had to let it charge for almost an hour before it would power back up. I can't remember though, if it actually chargers when the red light is lit, or if you need to unplug it and plug it back in so that it's plugged in with no red light, no power on, or anything. Let it charge while of with the red light on for about 20 mins. Then fiddle with it, unplugging and plugging back in, until you can get it to stay plugged in without powering it up or the red light coming on. Let it charge for about 20 mins like this too. Unplug it. Turn it on. Plug it back in immediately after seeing the google logo, let it finish booting and finish charging and you should be good. I've had around 5 - 7 rlod (mostly all my fault) and this method has worked every single time. I've never opened or rma'd my phone.
Click to expand...
Click to collapse
I'll try this tomorrow as it's 1 30 am here and I have a test tomorrow. Let's hope it works..
Btw I should mention, when I connected it to my pc, i got 'installing device driver' message with 'unidentified device' I mean is the phone already on? (although fastboot devices or adb devices doesn't show anything)
Thanks!
Sheep.... If its instaling drivrr on rlod then 49% of your phone being stuck at QHUSB_DLOAD mode. Good luck
Sent from my Nexus 4 using xda app-developers app
opssemnik said:
Sheep.... If its instaling drivrr on rlod then 49% of your phone being stuck at QHUSB_DLOAD mode. Good luck
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
What's QHUSB_DLOAD mode?
If the phone is completely powered off, your computer shouldn't even know when you plug it in, it shouldn't pop up with any messages at all. What your getting sounds a bit like the message people get when their phone is hard bricked, except reading from your first post, you havent done anything at all to even get close to a hard brick. Try holding your power button for 30 seconds. A real 30 seconds, count it out. When I turn my phone back on from the rlod (after doing all my rlod steps in the previous post), sometimes I have to hold the power button for a god awful long time, it has to be close to a full minute. Your phone might be frozen on some lower level (locked up bootloader maybe?) and might require holding the power button that long as well.
username8611 said:
If the phone is completely powered off, your computer shouldn't even know when you plug it in, it shouldn't pop up with any messages at all. What your getting sounds a bit like the message people get when their phone is hard bricked, except reading from your first post, you havent done anything at all to even get close to a hard brick. Try holding your power button for 30 seconds. A real 30 seconds, count it out. When I turn my phone back on from the rlod (after doing all my rlod steps in the previous post), sometimes I have to hold the power button for a god awful long time, it has to be close to a full minute. Your phone might be frozen on some lower level (locked up bootloader maybe?) and might require holding the power button that long as well.
Click to expand...
Click to collapse
Thanks! I'll do it tomorrow and inform you about any progress..
Goddnight...
Its Mike Download mode for Samsung devices.its trigered by the 2nd bootloader when the 1st onde fails to boot.when on this mode.the nand turns into a pendrive(like) and can be all reformated(re send partition table).but we dont have all the files to do that.
Sent from my Nexus 4 using xda app-developers app
Btw, would leaving it charging for about 5 hours cause any further damage? I mean is it advisable to do so?
opssemnik said:
Its Mike Download mode for Samsung devices.its trigered by the 2nd bootloader when the 1st onde fails to boot.when on this mode.the nand turns into a pendrive(like) and can be all reformated(re send partition table).but we dont have all the files to do that.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Right..
As long is stock charger its ok
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 06:53 PM ---------- Previous post was at 06:51 PM ----------
U can try pressing vol up and down for 1min.then pluging in the charger
Sent from my Nexus 4 using xda app-developers app
username8611 said:
If the phone is completely powered off, your computer shouldn't even know when you plug it in, it shouldn't pop up with any messages at all. What your getting sounds a bit like the message people get when their phone is hard bricked, except reading from your first post, you havent done anything at all to even get close to a hard brick. Try holding your power button for 30 seconds. A real 30 seconds, count it out. When I turn my phone back on from the rlod (after doing all my rlod steps in the previous post), sometimes I have to hold the power button for a god awful long time, it has to be close to a full minute. Your phone might be frozen on some lower level (locked up bootloader maybe?) and might require holding the power button that long as well.
Click to expand...
Click to collapse
So I couldn't sleep. Out of nowhere, idk how I am now in bootloader mode. Should I restart of power off or what?
Ibrahim.Rahman said:
So I couldn't sleep. Out of nowhere, idk how I am now in bootloader mode. Should I restart of power off or what?
Click to expand...
Click to collapse
Wish I had a four letter response. Was this after letting the phone charge? I would power off and let it charge until you wake up. (four letter word was in reference to QLOD and RLOD like the average layperson would know what that means! )
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
Wish I had a four letter response. Was this after letting the phone charge? I would power off and let it charge until you wake up. (four letter word was in reference to QLOD and RLOD like the average layperson would know what that means! )
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
While charging. After selecting power off/Start up/recovery mode/restart bootloader, it again starts getting rlod. it shuts down as soon as I disconnect the cable,
Ibrahim.Rahman said:
While charging. After powering off, it again starts getting rlod. it shuts down as soon as I disconnect the cable,
Click to expand...
Click to collapse
How long did you charge it?
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
How long did you charge it?
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Its somewhere between one and a half hour to 2 hours
Ibrahim.Rahman said:
Its somewhere between one and a half hour to 2 hours
Click to expand...
Click to collapse
I'm thinking a hw or battery issue. It's strange (duh) that after that length of time that it would shutdown after disconnecting the cable.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
I'm thinking a hw or battery issue. It's strange (duh) that after that length of time that it would shutdown after disconnecting the cable.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
I hope I don't have to open it up. Its nearly 3 here so im leaving it charging and will remove it in three hours. Will get back later.
Thanks!
So nothing worked.. I guess the only way left is to open the phone up.. Wanted to avoid doing that at all costs :/
Ibrahim.Rahman said:
So nothing worked.. I guess the only way left is to open the phone up.. Wanted to avoid doing that at all costs :/
Click to expand...
Click to collapse
Well i have been writing about this. In short you have to disconect the battery, and try to boot it again.fist try to hold the volume down when conecting the charger, it will restart bootloader , select to start. f that doesnt work, you have to disconect the battery, and wrtie an factory image ( nexus 4 occam ) . Try to boot the phone first when disconecting the battery, before writing the factory img. GL
Related
Just got my nexus 4, and after it was left in cwm for about 10 minutes (while I was making breakfast) it went to a black screen and now just the red led notification led is flashing whenever plugged in, and on my mac in system profiler it shows "composite device", any suggestions?
Thanks!
nycbjr said:
Just got my nexus 4, and after it was left in cwm for about 10 minutes (while I was making breakfast) it went to a black screen and now just the red led notification led is flashing whenever plugged in, and on my mac in system profiler it shows "composite device", any suggestions?
Thanks!
Click to expand...
Click to collapse
Is your device hot to the touch?
Sent from my Nexus 4 using xda premium
20 second press on power button
No luck
Sent from my HTC One X using xda premium
Don't know if you want to do this, but you can open the phone and disconnect and reconnect the battery connector...
What was your battery level, I know in other devices some times the CPU(s) run at full speed in recovery allowing for quicker flashing this could discharge the battery rapidly. Also a flashing red LED when plugged in normally means the phone is charging but doesn't have enough charge to reliably turn on, leave it plugged in for about 15 minutes and try turning it on again.
Try holding down the VOL + and - keys along with the powerbutton (after turning it off by holding down the power button for an extended time) and see if you can get into fastboot. My friend's Nexus 4 kept bootlooping after he unlocked the bootloader but booted straight to CWM after, not letting it erase userdata first.
Net.silb said:
Don't know if you want to do this, but you can open the phone and disconnect and reconnect the battery connector...
Click to expand...
Click to collapse
I have no problem doing this, the phone seems easy to disassemble, looks alot like a overgrown iPhone 4, 2 screws on the bottom. I just hope its an easy slide, I don;t want to mar it in case I have to exchange it.
jakejm79 said:
What was your battery level, I know in other devices some times the CPU(s) run at full speed in recovery allowing for quicker flashing this could discharge the battery rapidly. Also a flashing red LED when plugged in normally means the phone is charging but doesn't have enough charge to reliably turn on, leave it plugged in for about 15 minutes and try turning it on again.
Click to expand...
Click to collapse
I thought this as well, its been plugged in for at least an hour now.
Oh and now I don't even get the red led!
good times..
I've got the exact same issue. Plugged it in last night to charge and this morning it wouldn't turn on. Plugged and unplugged it and the red LED starts flashing. After a minute or so I'm getting the battery charge animation on the screen - so the red LED is power related. Now to see if it actually charges up and boots.
Hi nycbjr. I have seen a similar issue posted here, but I can't find the thread at the moment, try searching. If I remember correctly then he got it working by holding power, volume keys and then plugging in the charger.
nycbjr said:
I have no problem doing this, the phone seems easy to disassemble, looks alot like a overgrown iPhone 4, 2 screws on the bottom. I just hope its an easy slide, I don;t want to mar it in case I have to exchange it.
I thought this as well, its been plugged in for at least an hour now.
Oh and now I don't even get the red led!
good times..
Click to expand...
Click to collapse
Try a different charger?
Unlucky
Get a Free £5 On a GiffGaff sim
Called google, they are sending me another one advanced replacement, so I can send the bad one back at me leisure.
Good customer service!
Qhsusb_dload
nycbjr said:
Called google, they are sending me another one advanced replacement, so I can send the bad one back at me leisure.
Good customer service!
Click to expand...
Click to collapse
Hi!! I have the exact same problem, unfortunately the phone is bricked! Does anyone know how to fix this? I saw a video on youtube Nexus 4 - JTAG Brick Repair Service
CalogeroIndorato said:
Hi!! I have the exact same problem, unfortunately the phone is bricked! Does anyone know how to fix this? I saw a video on youtube Nexus 4 - JTAG Brick Repair Service
Click to expand...
Click to collapse
If u are fully bricked JTAG is the way to go.
Sent from my Nexus 4 using Xparent BlueTapatalk 2
Here seems to be a similar thread, maybe you'll find help there.
http://forum.xda-developers.com/showthread.php?t=2111947
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?
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
My Nexus 7 2013 wont turn on.I bought it on 4 sep ,no problems till this morning.Last night i left it charging and this morning it wasn't turning on.
My warranty is ****ed up because im using cyanogenmod 10.2. Any suggestions?
Is the problem that i was using charger outputing 0.7A?The stock charger is outputing 1.35A.
Hold the power button for 30 seconds.
...
Username invalid said:
Hold the power button for 30 seconds.
Click to expand...
Click to collapse
Don't work.
unplug it and leave it for around 10 minutes, then plug it back in again, wait a minute and hold down power for 30s until it boots. Should be OK after that.
Don't work
Dav_prime said:
unplug it and leave it for around 10 minutes, then plug it back in again, wait a minute and hold down power for 30s until it boots. Should be OK after that.
Click to expand...
Click to collapse
Don't work :crying:
atheris said:
Is the problem that i was using charger outputing 0.7A?The stock charger is outputing 1.35A.
Click to expand...
Click to collapse
So maybe it is complety uncharged? Why not try again to charge with the stock charger?
ThaiDai said:
So maybe it is complety uncharged? Why not try again to charge with the stock charger?
Click to expand...
Click to collapse
Im doing this right now
atheris said:
Im doing this right now
Click to expand...
Click to collapse
Good luck. But please do not make double posts and post questions in the Q&A forum next time, ok?
Always use the stock charter, and charge it over nigth, I think this solves your Problem.
Plug it for 30 minutes. Then restart.
If not unplug/plug battery by opening back cover.
Maybe battery was disconnected.
Did you try holding volume up + power? I had this happen to me as well and I did that combination while on the charger to get my N7 to turn back on.
Sent from my SPH-L710 using Tapatalk 4
I actually had this problem last night. My battery was at 20% a few days ago... left it idle, went to use it last night and bam, nothing.
Plugged it in for a few minutes and tried to boot, nothing. Left it for about 5 minutes and then just held down the power button until something happened, and finally I managed to get the battery icon to appear. It would stay for a few seconds then the screen would go black. Then it would return. Rinse, repeat. I couldn't even get it to stop doing that. Eventually gave up and just let it charge for another 10 minutes.
Looked at it after that and it was booted. Battery page shows it dropped from 20% to completely dead instantly. Not sure what's up with that.
The whole time I was doing this procedure, the notification light was pulsing in sequences of 5, if that means anything to anyone.
Anyway, tablet is fine this morning.
Ok so yesterday I had my nexus 4 in the charger at 46 percent and i was about to send a tweet when the screen froze. thinking it was a simple crash i pressed the home button and no visual response then it powered off. now whenever i try to power it on nothing happens. i tried pressing the power and volume buttons. whenever i try to turn it on and i plug it in the red light flashes. sometimes it flashes continiously sometimes it is a solid color. so what can i do it wont communicate with the computer. im not sure what the issue is. is it a battery issue or is it impossibly bricked. i already charged it overnight to no avail.
oh and im running stock cm11 with the stock cm kernel. i just installed it the night before.
im planning on just openning it and unplugging and plugging the battery back in. will this work?
Try power button + volume down for 10 seconds and than plug in the power cable. You somehow must try to boot into bootloader.
CCody said:
Try power button + volume down for 10 seconds and than plug in the power cable. You somehow must try to boot into bootloader.
Click to expand...
Click to collapse
it wont work. the red light either flashes red or stays red.
dominiqueovalle said:
it wont work. the red light either flashes red or stays red.
Click to expand...
Click to collapse
How many times did you try that? It may don't work in the first time.
But if you can screw off you phone, that I would suggest to look after the batterie :good:
CCody said:
How many times did you try that? It may don't work in the first time.
But if you can screw off you phone, that I would suggest to look after the batterie :good:
Click to expand...
Click to collapse
do you think it could be bricked tho? the battery wasnt even low
dominiqueovalle said:
do you think it could be bricked tho? the battery wasnt even low
Click to expand...
Click to collapse
It is hard to say, because there are so many reason why your device doesn't boot only left the red LED flashing. One reason could be your batterie which is bricked. Another reason could be a thermal shutdown cause by overheat. And of course there are those little, little software issues that only appear once in five years...
CCody said:
It is hard to say, because there are so many reason why your device doesn't boot only left the red LED flashing. One reason could be your batterie which is bricked. Another reason could be a thermal shutdown cause by overheat. And of course there are those little, little software issues that only appear once in five years...
Click to expand...
Click to collapse
just my luck. but the battery was 46 percent and it wasnt that hot. i hope its not bricked because the computer refuses to detect it
I haven't got any idea what you are taking but i Had the Problem while my phone was loading it just went To Black screen and the red LED was blinking i just let it load and suddenly it worked but also my phone is quit stupid (never buy the huawei ascend g510 its s**t) it somethimes showes 40% and suddenly 1% and it shuts down.:thumbdown: .but i hope this helped you
Sry for my english
Sent from my HUAWEI G510-0100 using XDA Free mobile app