Database Users

officially bricked

I tried to load up the new gingerbread roms from my current one. I downloaded its content and tried to install it via clockwork.
I first deleted system, logo, and cache followed up by a restore format. When trying to download the new rom, I was getting a weird error that was stopping me from completing the full installation. So basically was in a chokehold because I didn't have any backup files or another working rom in the sd at that time. I just restarted the phone and it for a few times was stuck on the M screen, but now its just green led when I plug it into the computer usb. When plugging it into the outlet, it imediately turns on stuck on the M screen and shuts off when unplugging as if the battery isnt charging at all.

Sounds like ur going to have to sbf.
Sent from my DROIDX using XDA App

bigshotrob22 said:
Sounds like ur going to have to sbf.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
thats the problem.. i got the X.340 sbf and the program aswell but I cant get into bootloader mode. is there an alternative way to sbf?

Did u pull the battery for 30 seconds and then hold the volume buttons + power to put it n bootloader
Sent from my DROIDX using XDA App

Could be your battery same thing happened to me try using a friends battery your battery could be dead and it no longer charges
Sent from my DROIDX using XDA App

bigshotrob22 said:
Did u pull the battery for 30 seconds and then hold the volume buttons + power to put it n bootloader
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
bootloader is such a rare occurance for me, i just had it come out but it was flashing low battery. the thing is, im not quite sure if its charging if i have it plugged into the computer. when i have it plugged into an outlet, the M splash screen comes up so i'm worried that draining the power..
edit: now it flickers for a split second, am i supposed to hold on to it til something shows up? been like 1 minute
i dont think bricking phone blows your battery. at least i hope it doesnt, was working fine before.

Plug it in without the battery if a question mark comes up you ned to use another battery cuz it won't charge in boot loader and the boot loader should pop up right away hold power volume down and camera button it takes about three seconds
swyped from my DROIDX using XDA App

well its basically the same thing. when plug into the outlet it shows the m splash screen with or without the battery.
when its plugged into the compuiter however, its just flickers once. when it is done with the battery in, the led is on forever
EDIT: OBSERVATION
when on the wall, it is actually charging, but REALLY slowly because of the fact that the splash screen stays on. found this out because i had it in for30 min and then tried to connect mit to my comp with bootload and it loaded for a few minutes with the low battery flashing.
is version 320 the latest?

Okay. so it isnt charging as I though because its not working at all... problem is, I dont know if it truly is a battery defect. If I were to Buy a new battery, how would i know if it is charging if it doesnt boot and just stays stuck on the M logo screen?
perhaps I should by a battery charger where i take the battery out and charge it through there? because my bootloader always gives me the same low battery.

Do you have any friends with the same phone? There is also a macgyver (spelling?) Method of doing this by cutting the USB cable open and attaching the cable ends to the battery. However I would only do this if you're really desperate

i just really need make complete sure that this phone is INFACT dead battery
when not plug, it doesnt turn on what so ever with a white spark on the led.
when plugged nto outlet the logo shows but i isnt charging because it isnt booting
when plugged into the computer it is a solid green which i think represent a dead or a low battery state(can someone back thisup?)

Your battery is dead, as in drained, but should work fine once you get your phone to a bootable state again. The problem is that, in the state your phone is in, there's no charging capabilities. Bootloader won't do it, neither will sitting at the M logo. So, you just need to find someone with a compatible battery to let you use it to SBF your phone. Then, boot the phone up completely, and let your battery charge to at least 50-60% before trying to install a ROM. Preferably, I'd go with a full charge, just in case you end up in a similar situation again.
This is nothing to freak out over, you'll be fine.. the only problem you have is that your battery has no juice, as confirmed by the low battery warning in the bootloader, when you successfully got it to load.

raziel36 said:
Your battery is dead, as in drained, but should work fine once you get your phone to a bootable state again. The problem is that, in the state your phone is in, there's no charging capabilities. Bootloader won't do it, neither will sitting at the M logo. So, you just need to find someone with a compatible battery to let you use it to SBF your phone. Then, boot the phone up completely, and let your battery charge to at least 50-60% before trying to install a ROM. Preferably, I'd go with a full charge, just in case you end up in a similar situation again.
This is nothing to freak out over, you'll be fine.. the only problem you have is that your battery has no juice, as confirmed by the low battery warning in the bootloader, when you successfully got it to load.
Click to expand...
Click to collapse
thanks for the reassuring comment, however, i think i need to bootload.
i accidently did the partition hat formats everything.. cant recall if it was under clockwork because it didnt have the same interface, i was all light blue text with an ok button on the left corner. Anyway, i've completely destroyed the phone as in no roms no factory.
can I possibly get a dock to charge this battery and then get into bootloader for an sbf session
? Even if I did have battery, im pretty sure i just hover at the logo screen

jinho11050 said:
thanks for the reassuring comment, however, i think i need to bootload.
i accidently did the partition hat formats everything.. cant recall if it was under clockwork because it didnt have the same interface, i was all light blue text with an ok button on the left corner. Anyway, i've completely destroyed the phone as in no roms no factory.
can I possibly get a dock to charge this battery and then get into bootloader for an sbf session
? Even if I did have battery, im pretty sure i just hover at the logo screen
Click to expand...
Click to collapse
There's a usb trick u can try. Google it.
Sent from my DROIDX using XDA App

jinho11050 said:
thanks for the reassuring comment, however, i think i need to bootload.
i accidently did the partition hat formats everything.. cant recall if it was under clockwork because it didnt have the same interface, i was all light blue text with an ok button on the left corner. Anyway, i've completely destroyed the phone as in no roms no factory.
can I possibly get a dock to charge this battery and then get into bootloader for an sbf session
? Even if I did have battery, im pretty sure i just hover at the logo screen
Click to expand...
Click to collapse
You definitely need to use the bootloader, and I was implying that in the first reply(SBF'ing requires going into the bootloader). If you had a stand-alone battery charging cradle/dock, that should do the trick. Just make sure to let the battery charge sufficiently. I've successfully gotten an SBF completed, starting with only 30% battery. SBF takes about 7 minutes on my laptop(not that I've timed it, but I usually light up a smoke when I start the process lol). So, as long as the battery is charged enough to no longer give the "Low Battery" warning in the bootloader, you should be fine.

You got your usb cable and put the ends where the battery goes that's how I got mine working try it
Sent from my DROIDX using XDA App

froyli said:
You got your usb cable and put the ends where the battery goes that's how I got mine working try it
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
al the tips or just red for pos and black for neg

Positive and negative google it before you do it
Sent from my DROIDX using XDA App

okay im having another issue with bootloader.. the program detecs it but i canot start the process.. am i missing something?
EDIT: finally got sbf working after renaming it.
All my threads have been in a form of technique difficulty question and the answer I get from the community were VERY helpful. thank you everyone

jinho11050 said:
okay im having another issue with bootloader.. the program detecs it but i canot start the process.. am i missing something?
EDIT: finally got sbf working after renaming it.
All my threads have been in a form of technique difficulty question and the answer I get from the community were VERY helpful. thank you everyone
Click to expand...
Click to collapse
Glad you got it working! Nearly everyone on here has needed help, at one point or another, and that's what makes Android so great... the community.
Sent from my DROIDX using XDA App

Nexus just died!

Hi.
My N7 just died a few minutes ago. I was using it fine with about 25% battery left. All of a sudden a 'please connect to a charger' symbol flashed up then froze. Next thing that happened was the screen went black and little sparky white dots starting flashing all over the screen. I have connected it to a charger and held the power button for 15 seconds and its starts booting again, but as soon as I get into the os the screen briefly corrupts and blacks out.
Here is a video.
http://www.youtube.com/watch?v=lN_oDlaKVkQ
Is there anyway to do a hard reset via the volume rocker and power button?? I have managed to get into the boot loader but there are no options. It will not power on without connecting to a charger.
Everything is at stock.
Looks like another call to Google.

Warren_Orange said:
Hi.
My N7 just died a few minutes ago. I was using it fine with about 25% battery left. All of a sudden a 'please connect to a charger' symbol flashed up then froze. Next thing that happened was the screen went black and little sparky white dots starting flashing all over the screen. I have connected it to a charger and held the power button for 15 seconds and its starts booting again, but as soon as I get into the os the screen briefly corrupts and blacks out.
Here is a video.
http://www.youtube.com/watch?v=QiXdDyDHs0Y
Is there anyway to do a hard reset via the volume rocker and power button?? I have managed to get into the boot loader but there are no options. It will not power on without connecting to a charger.
Looks like another call to Google.
Click to expand...
Click to collapse
You need to change the settings on the youtube video. When I click on the link, it says that the video is private.

Are you rooted and unlocked ???
Sent from my Nexus 7 using Xparent Cyan Tapatalk 2

Oops sorry just changed it now.
I can get into the boot loader but pressing the volume button down doesn't move it to recovery mode.
I think it is well and truly stuffed.

Looks like a victim of fsync being turned off.. Sudden power lose, data wasn't written completely, reboots, hits the corrupt data and poof.
Reflash a rom and you should be good to go.

ANDR0lD said:
Are you rooted and unlocked ???
Sent from my Nexus 7 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
No. Everything is stock.

Warren_Orange said:
No. Everything is stock.
Click to expand...
Click to collapse
Hmmm... was USB debugging on in your settings before this happened?
Sent from my Nexus 7 using Xparent Cyan Tapatalk 2

let it charge for a bit then try booting it

ANDR0lD said:
Hmmm... was USB debugging on in your settings before this happened?
Sent from my Nexus 7 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
99% sure it was not selected.
simms22 said:
let it charge for a bit then try booting it
Click to expand...
Click to collapse
Ok will do. I noticed after my last reset battery said 0%. Whereas 5 minutes previous during another boot attempt it said 28%, which is the amount it died on.

Warren_Orange said:
99% sure it was not selected.
Ok will do. I noticed after my last reset battery said 0%. Whereas 5 minutes previous during another boot attempt it said 28%, which is the amount it died on.
Click to expand...
Click to collapse
Maybe it was on the verge of being dead but your battery level was not being shown properly.

airmaxx23 said:
Maybe it was on the verge of being dead but your battery level was not being shown properly.
Click to expand...
Click to collapse
So even if the N7 is attached to the charger would it still flip out after loading android?
I really hope its just a dead battery but I'm not hopeful.

Same thing happened to me and i fixed it(Mine was dying at %15). I did some random things and I'm not sure about every step is necessary. Here is what I did:
1) Erase system data and cache partition using fastboot
2) Flash stock rom using fastboot
3) Charge it for 2-3 hours more when battery gets %100
4) Factory data reset
5) Use it until battery gets %1
6) Charge it again and wait 1-2 hours more when it gets %100
7) Done

Restore the factory image from fastboot. You might also consider flashing a custom recovery long enough to wipe your battery stats. I had this happen on a completely stock LG Marquee, once. Exact same situation, too.

Hi all.
Well I left it to charge for about two hours and then reset it (15 seconds power button). All the screen had a white halo around the edge, but it did stay on and not corrupt. I have added a video to show the effect.
http://www.youtube.com/watch?v=0_NKFsF1xw0
So I left the N7 for a bit and it started to get better. So I left it a bit longer and it got a little bit better. Better but not good - all the screen has bad image burn, it is getting better though. Now the image burn is disappearing and it is 80% back to normal. The left side of the screen is worse though. It is also charging very slowly. I left it charged for two hours and its only on 40%.

Looks like possibly a hardware problem... I have not seen anything like that before. I'd see about warranty through ASUS on that one. Especially if its still 100% stock.
Sent from my Nexus 7 using XDA Premium App

I think I'm bricked?

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?

Battery drain while tablet is turned OFF

I was using my Nexus 7 til it hit about 15% and the battery alert came out. I turned it off, plugged into the charger and left it there overnight. The following night I took it out of my pouch only to realise that its very warm. I had to press on the power button for a good 10 seconds before it turned on, and when it booted up the battery had only 5% remaining, even though it was fully charged (I checked to make sure it was 100%) and was left OFF the entire day.
I encountered this before but thought I solved the issue after wiping the device and flashing CleanROM 3.0 without any custom kernels or tweaks. Looks like the issue is back, any idea what might be wrong? I hope it has nothing to do with the physical battery itself because that would be a pain. Other than this, the day to day battery life of the tablet and stability is pretty good.

BUMP
No one really? Im sure there are people who experienced this before.

My wife's phone does something very similar. Crashes, heats up and when she gets it back on the battery has taken an absolute hammering. Luckily it occurs only rarely and it appears that there are no long term consequences.
Cheers Danny

toidimaet said:
My wife's phone does something very similar. Crashes, heats up and when she gets it back on the battery has taken an absolute hammering. Luckily it occurs only rarely and it appears that there are no long term consequences.
Cheers Danny
Click to expand...
Click to collapse
What phone is she using? Is it rooted?
Anyway I think i figured out why, i happened to notice it by chance. After full charge, i plug it out and notice the screen is actually turned on even though the device isnt! The screen is just showing a plain blank screen, but you can tell its turned on, by looking at an angle. I had to manually force a shut down by holding the power button before it goes off, then the tablet automatically switches on. It seems that it only happens when i charge the tablet while its switched off, I wonder if it has anything to do with the bootloader (Im on 4.2.1) or the charger itself.

Galaxy s2 rooted, does not appear to be rom or kernel specific as it occurs with different combinations. Anyway good news you have at least identified the problem.
Cheers Danny

Sounds like it never charged. Why turn it off to charge it? Airplane mode is just as good.

toidimaet said:
Galaxy s2 rooted, does not appear to be rom or kernel specific as it occurs with different combinations. Anyway good news you have at least identified the problem.
Cheers Danny
Click to expand...
Click to collapse
If thats the case have you tried re-calibrating the battery? Sounds like its pretty messed up, thats what i'd do.
jefferson9 said:
Sounds like it never charged. Why turn it off to charge it? Airplane mode is just as good.
Click to expand...
Click to collapse
It did charge because when i turned it back on it showed as 95%, the first 5% was drained because the screen was left "on" the whole time. I am beginning to suspect it is the case I use with the tablet. Its similar to those smart cases on the iPad where the screen auto ons/off when you flip or close the cover. I notice that even during the process of shutting the tablet down the flap still affects the screen off/on when i close it. A potential way of screwing up stuff. Next time I charge it turned off, I'll try removing the case entirely and see what happens.

Alright this time I turned the tablet off and left it to charge over night WITHOUT the casing and now it's working fine. No screen on or any heat whatsoever.
Sent from my non-Apple device via XDA App

cr0wnest said:
Alright this time I turned the tablet off and left it to charge over night WITHOUT the casing and now it's working fine. No screen on or any heat whatsoever.
Sent from my non-Apple device via XDA App
Click to expand...
Click to collapse
Why are you turning it off to charge? Just plug it in and be done with it. I never turn any of my devices off - the only time my S2 has been off is to reboot to flash a new ROM. Never have any charging issues.
T
Sent from my Nexus 7 using Tapatalk 2

tedkunich said:
Why are you turning it off to charge? Just plug it in and be done with it. I never turn any of my devices off - the only time my S2 has been off is to reboot to flash a new ROM. Never have any charging issues.
T
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Its just a habit i guess, and i always have the mentality that it makes a difference charging it while off
And its also good to reboot your phone once in a while, I usually do it once every 24 hours of use. Y'know, to flush out the RAM and OS so it can start anew. :highfive:

black screen after sleep

Hi,
my n10 works great except the odd time when I try to wake it up and it's completely non-responsive, just showing me a black screen.
I'm unlocked , and rooted, running CleanRom. Is this device related or rom?
Cheers

pinn___________ said:
Hi,
my n10 works great except the odd time when I try to wake it up and it's completely non-responsive, just showing me a black screen.
I'm unlocked , and rooted, running CleanRom. Is this device related or rom?
Cheers
Click to expand...
Click to collapse
¿Are you using a kernel that supports hotplugging of the second core?.

I'm on stock kernel

Shows a black screen but is on, or is actually off?

bigmatty said:
Shows a black screen but is on, or is actually off?
Click to expand...
Click to collapse
Device is on - as I said it's not waking from sleep with the power button.

Confirm.
Strange thing - sometimes notification LED blinking.

How are you guys determining its on?
I had a defective N10 and experienced similar things. Another user taught me a trick: When you see the led flash but can't turn on the screen try plugging in a charger - if the battery charge icon appears, its not actually "on"...

bigmatty said:
How are you guys determining its on?
I had a defective N10 and experienced similar things. Another user taught me a trick: When you see the led flash but can't turn on the screen try plugging in a charger - if the battery charge icon appears, its not actually "on"...
Click to expand...
Click to collapse
Charger already plugged. No reaction on plug or unplug. No unlock, no root. Comletelly stock.

noahhomsky said:
Charger already plugged. No reaction on plug or unplug. No unlock, no root. Comletelly stock.
Click to expand...
Click to collapse
Dang. Or actually maybe good. I'm not sure which would be the preferable one...

bigmatty said:
How are you guys determining its on?
I had a defective N10 and experienced similar things. Another user taught me a trick: When you see the led flash but can't turn on the screen try plugging in a charger - if the battery charge icon appears, its not actually "on"...
Click to expand...
Click to collapse
Hadn't switched device off and was on full battery too. I'll try your suggestion though.
How long did your rma take btw?
Sent from my Nexus 10 using xda app-developers app

pinn___________ said:
Hadn't switched device off and was on full battery too. I'll try your suggestion though.
How long did your rma take btw?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
My RMA experience was pretty good. It was a Thursday afternoon I phoned Google, and had the second device the following Tuesday. Although I don't like that they put a charge hold on your credit card for another $500 which isn't the fastest to come off, the benefits outweigh that single negative. You don't have to pay for shipping, youre never without a device, for a while you have two devices so you can compare (if needed), shippings decently quick.

pinn___________ said:
Hadn't switched device off and was on full battery too. I'll try your suggestion though.
How long did your rma take btw?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
This "black screen of death" has just happened on my Nexus 10. My device is unlocked, rooted, with CWM and CM10.1 and stock kernel. EDIT: the battery was full (~80%)
I was using Perfect Viewer and the screen suddenly went black. I've tried holding the power button alone and with the volume buttons pressed for up to 1 minute and nothing. Tried to do the same while charging and while connected to a computer. I also tried to connect the USB cable while holding the power button. Nothing worked so far.
Is there any way to send commands such as "reboot' or "shutdown" while connected to a computer? (something like the way fastboot works on linux)
Maybe removing the battery might work, what you guys think?

flyhunter said:
Is there any way to send commands such as "reboot' or "shutdown" while connected to a computer? (something like the way fastboot works on linux)
Click to expand...
Click to collapse
"adb reboot" is what you're looking for.

flyhunter said:
This "black screen of death" has just happened on my Nexus 10. My device is unlocked, rooted, with CWM and CM10.1 and stock kernel. EDIT: the battery was full (~80%)
I was using Perfect Viewer and the screen suddenly went black. I've tried holding the power button alone and with the volume buttons pressed for up to 1 minute and nothing. Tried to do the same while charging and while connected to a computer. I also tried to connect the USB cable while holding the power button. Nothing worked so far.
Is there any way to send commands such as "reboot' or "shutdown" while connected to a computer? (something like the way fastboot works on linux)
Maybe removing the battery might work, what you guys think?
Click to expand...
Click to collapse
I just held the power button for about 30 secs and then it rebooted fine. Maybe a different issue then

I've had the same issue this morning on a 4 day old nexus 10. Its actually the 3rd time this had happened. Stock os and 2 accounts setup.
I'm also getting random scan lines on display.
Gonna RMA mine. Can you only call Google or can you rma online?

You can call or email them. Good luck!