Database Users

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?

[Q] Is my phone bricked or is it a simple battery issue?

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

Took a picture with flashlight on, now hard bricked

this could have just been bad luck but now it looks like im sending my phone back to huawei AGAIN.
Long story short, i JUST got the phone back from getting a battery replacement a week ago and every thing was great. Finally could go from 100%-0 with no issues. I was looking for a serial number on a router and with the flashlight turned on i went to take a picture. Screen froze and started to boot loop. I did manage to get back into TWRP after the first boot so i decided id wipe everything and restore my Rom seeing as i had just backed up yesterday and wouldn't miss much. It got me to the "please lock your bootloader bla bla bla" screen and went black. No google screen or anything. Now its just dead. plugged it into a charger. Nothing. Plugged it into the computer. Nothing. Hold down power for 20 seconds. Nothing. Hold volume down and power. Noooppee.
So yea, either im an idiot for trying to take a pic with the flashlight on or im having a bad run with this phone lately. Maybe both. idk. i love this phone but this is getting ridiculous.

Wickidmasshole said:
this could have just been bad luck but now it looks like im sending my phone back to huawei AGAIN.
Long story short, i JUST got the phone back from getting a battery replacement a week ago and every thing was great. Finally could go from 100%-0 with no issues. I was looking for a serial number on a router and with the flashlight turned on i went to take a picture. Screen froze and started to boot loop. I did manage to get back into TWRP after the first boot so i decided id wipe everything and restore my Rom seeing as i had just backed up yesterday and wouldn't miss much. It got me to the "please lock your bootloader bla bla bla" screen and went black. No google screen or anything. Now its just dead. plugged it into a charger. Nothing. Plugged it into the computer. Nothing. Hold down power for 20 seconds. Nothing. Hold volume down and power. Noooppee.
So yea, either im an idiot for trying to take a pic with the flashlight on or im having a bad run with this phone lately. Maybe both. idk. i love this phone but this is getting ridiculous.
Click to expand...
Click to collapse
I've taken pics with the flashlight on several times on mm and nougat. I've never had any issues from it. If you can still get into TWRP maybe try to load factory image. If you aren't even getting to to google splash screen it's almost like you don't have an os installed.
Nevermind. Just reread what you wrote and saw that it won't boot at all.

murphyjasonc said:
I've taken pics with the flashlight on several times on mm and nougat. I've never had any issues from it. If you can still get into TWRP maybe try to load factory image. If you aren't even getting to to google splash screen it's almost like you don't have an os installed.
Click to expand...
Click to collapse
I was planning on doing that if it boot looped off the restore but this thing is a paper weight right now. no lights no vibrate and nothing is waking it up. charger or computer. second RMA in a month here we come.

Wickidmasshole said:
I was planning on doing that if it boot looped off the restore but this thing is a paper weight right now. no lights no vibrate and nothing is waking it up. charger or computer. second RMA in a month here we come.
Click to expand...
Click to collapse
I'm having the battery drain issue with my 6P. Google said they will send an RMA even though I'm out of warranty. I've just got to tell them to send it. Haven't done it yet because I'm halfway scared of getting a device that has worse problems. At least now I know 15% battery actually means 0. Other than that it's in perfect condition. After your experience I may just keep my phone and try replacing the battery myself.

its funny because i bought directly from huawei in November of 2016 and before i sent it in it told me i was under warranty until Jan 26 2017. now i just checked and im under warrenty until 4-3-17. so maybe they dont even trust their own work and extended my warranty lol
if i didnt have a back up phone id be way more pissed off about this.

Wickidmasshole said:
I was planning on doing that if it boot looped off the restore but this thing is a paper weight right now. no lights no vibrate and nothing is waking it up. charger or computer. second RMA in a month here we come.
Click to expand...
Click to collapse
There is another thread where ppl are able to regain access the dead phone by holding the power button down for an extended time. Some say a minute and a half, others several minutes but their phones were coming back on and fully functioning afterwards. If you can get back into recovery why not try a factory reset before restoring your backup.

v12xke said:
There is another thread where ppl are able to regain access the dead phone by holding the power button down for an extended time. Some say a minute and a half, others several minutes but their phones were coming back on and fully functioning afterwards. If you can get back into recovery why not try a factory reset before restoring your backup.
Click to expand...
Click to collapse
i only got back into recover off of the very first bootloop now i cant get it to turn on at all. tried out your long power hold tip but nothing still.
what makes me think its really deadzo is if i plug it into a wall charger i dont even get the red charging light anymore

Wickidmasshole said:
i only got back into recover off of the very first bootloop now i cant get it to turn on at all. tried out your long power hold tip but nothing still.
what makes me think its really deadzo is if i plug it into a wall charger i dont even get the red charging light anymore
Click to expand...
Click to collapse
Some people have reported that plugging the phone into a wall outlet for an extended period of time (sometimes 24 hours or more) brings the red notification light back and then you can power on again

Is my phone a bricked lost cause?

I was running a standard OS, no root/custom/anything (mostly because I couldn't find a compatible hack). Anyway, I had my phone running happily for ~2+ years, no trouble at all, but few days ago I left it charging for 2-3 days (it powered down due to lower power before that). I've done it before several times, but when I tried turning it on, it was stuck on Samsung logo (white on black). I restarted, it was stuck a bit further on the colored startup animation. Third time, stuck on the logo again. I turned it off, but it was a bit warm after 10 or so minutes. I tried charging it - it showed the usual green battery charging from 80% or so. I took the battery out, pressed the power button for a minute for some hard reset, but the battery back in, and from that point on it seems I have a brick. No reaction to power button, no reaction to charging. Power+Home+VolUp produce no reaction, either.
Is there anything I can try, or should I just give up?

Factory reset ??
Flash stock rom via Odin ??
Sent from my SM-N930F using XDA-Developers Legacy app

piokon said:
I was running a standard OS, no root/custom/anything (mostly because I couldn't find a compatible hack). Anyway, I had my phone running happily for ~2+ years, no trouble at all, but few days ago I left it charging for 2-3 days (it powered down due to lower power before that). I've done it before several times, but when I tried turning it on, it was stuck on Samsung logo (white on black). I restarted, it was stuck a bit further on the colored startup animation. Third time, stuck on the logo again. I turned it off, but it was a bit warm after 10 or so minutes. I tried charging it - it showed the usual green battery charging from 80% or so. I took the battery out, pressed the power button for a minute for some hard reset, but the battery back in, and from that point on it seems I have a brick. No reaction to power button, no reaction to charging. Power+Home+VolUp produce no reaction, either.
Is there anything I can try, or should I just give up?
Click to expand...
Click to collapse
The only answer I can think of is that your battery is dead. I would try to use another battery before getting to the conclusion that your phone is completely bricked. Or just let the battery out of your phone for a couple of days and try again later.

JJEgan said:
Factory reset ??
Flash stock rom via Odin ??
Sent from my SM-N930F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Can't do either since the phone is not turning on.

ShaDisNX255 said:
The only answer I can think of is that your battery is dead. I would try to use another battery before getting to the conclusion that your phone is completely bricked. Or just let the battery out of your phone for a couple of days and try again later.
Click to expand...
Click to collapse
Tried a new battery, the phone still won't turn on. No lights, no charging screen, no activity.

piokon said:
Tried a new battery, the phone still won't turn on. No lights, no charging screen, no activity.
Click to expand...
Click to collapse
Must have fried something. The only thing I would check now is to connect it to a PC with a USB cable and see if the PC detects something, ANYTHING. If it makes sounds that something has been connected to it. I remember when I hard bricked my phone, it did not turn on at all but my PC still sort of detected it. I guess that is the only thing left to try to give you a definite answer

Hard Brick - Phone Not Turning On

Hye,
I was just updating the ROM which is Nitrogen OS. And then i'm flashing the Flash kernel but it stuck for a quite long time. So im pressing Power button + Volume down to reboot into recovery.
And then the phone is not turning on again.
I'd tried to charge the phone using OEM / after market charger / pc and no LED turning on. On the pc , there is no device detected on the Device Manager.
Is there any possible way to reboot into recovery ?
Thanks for helping.

have you tried adb commands?

Shod20 said:
have you tried adb commands?
Click to expand...
Click to collapse
How to use adb command if my phone not detected on pc ?
Literally on Nexus Root Toolkit didn't found my device

keep pressing the power button for more than 60 seconds

csjneek said:
keep pressing the power button for more than 60 seconds
Click to expand...
Click to collapse
Nah , didn't work for me. Pressing like 10 minutes already.

masbz said:
Nah , didn't work for me. Pressing like 10 minutes already.
Click to expand...
Click to collapse
Leave it on the original USB-C charger overnight or several hours until the front led light comes on. Then do the 2 minute power only button. If it doesn't power on within 2 minutes, it's not going to. The bad part really is that even if you put a new battery in it, it may not fix it. How was the phone behaving before? Any of these.... getting hot, bad SOT, turning off below a certain battery %, not charging fully to 100%? If your battery was acting up recently you could try a battery. If the battery was strong and it just happened out of the blue, likely the phone (MB) is toast. Is there a Huawei service center in KL? Semoga berjaya.

v12xke said:
Leave it on the original USB-C charger overnight or several hours until the front led light comes on. Then do the 2 minute power only button. If it doesn't power on within 2 minutes, it's not going to. The bad part really is that even if you put a new battery in it, it may not fix it. How was the phone behaving before? Any of these.... getting hot, bad SOT, turning off below a certain battery %, not charging fully to 100%? If your battery was acting up recently you could try a battery. If the battery was strong and it just happened out of the blue, likely the phone (MB) is toast. Is there a Huawei service center in KL? Semoga berjaya.
Click to expand...
Click to collapse
I recently flash the new Nitrogen ROM and after successful flashing , went back to recovery to unroot with SuperSU. During flashing, it was stuck and had to hard reset it and this was happen.
Nothing unexpected behavior at all, the battery kinda mess up since i'm a heavy user. SoT for 2-4 hours. I'm contacting the sc but right now we have Chinese New Year eve. Therefore , they'll closed it till Monday.
And for the bad luck, my warranty was expired on 27/1/2017. Kinda sad for me. Hopefully , they'll make an exception for this situation.
Btw thanks for that good luck. Appreciate that.