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
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?
My nexus 4 died. Can not boot. No respond but only red flash when plugged in with charger. I already unlocked my phone.
any one can help me?
huangkaiwisdom said:
My nexus 4 died. Can not boot. No respond but only red flash when plugged in with charger. I already unlocked my phone.
any one can help me?
Click to expand...
Click to collapse
Thats the RED light of death. Its a battery problem. Some people have opened their phones and fixed it somehow. I suggest you get a RMA.
Addsome said:
Thats the RED light of death. Its a battery problem. Some people have opened their phones and fixed it somehow. I suggest you get a RMA.
Click to expand...
Click to collapse
Since I already unlocked my phone and flash recovery. Do I still under the warranty?
huangkaiwisdom said:
Since I already unlocked my phone and flash recovery. Do I still under the warranty?
Click to expand...
Click to collapse
Im not 100% sure but since what you did, did not cause the RED led they should fix it. Unless something you did made that happen. When did this happen and how?
Put it on charge overnight. It should boot into recovery.
Addsome said:
Thats the RED light of death. Its a battery problem. Some people have opened their phones and fixed it somehow. I suggest you get a RMA.
Click to expand...
Click to collapse
Addsome said:
Im not 100% sure but since what you did, did not cause the RED led they should fix it. Unless something you did made that happen. When did this happen and how?
Click to expand...
Click to collapse
When I was trying to root my phone, when It on Recovery mod, I left for a while, when I came back, the phone was very hot, and powered off. No response when hit the power button.
calyxim said:
Put it on charge overnight. It should boot into recovery.
Click to expand...
Click to collapse
I tried. Keep in charge overnight. But still only Reg flash light.
huangkaiwisdom said:
When I was trying to root my phone, when It on Recovery mod, I left for a while, when I came back, the phone was very hot, and powered off. No response when hit the power button.
Click to expand...
Click to collapse
Hmm, you might of done something wrong.. Why would you leave it while it was rooting? I dont know what to do. Maybe you did something to the battery. Since you say it was very hot the battery might of overheated and died. Was it hot throughout the phone? Or just the top section. You could always but a battery and replace it yourself.
Addsome said:
Hmm, you might of done something wrong.. Why would you leave it while it was rooting? I dont know what to do. Maybe you did something to the battery. Since you say it was very hot the battery might of overheated and died. Was it hot throughout the phone? Or just the top section. You could always but a battery and replace it yourself.
Click to expand...
Click to collapse
It's just the top section. Maybe I did something wrong. The phone showed the battery logo for one second. But back to Red light then.
Charge it the whole night with another charger, not stock
calanizzle said:
Charge it the whole night with another charger, not stock
Click to expand...
Click to collapse
I will try that. Thanks
I believe some have fixed thier problem by pressing down where the battery connects to phone
Plug it into a USB slot on your computer and repeatedly try and get into recovery. Worked for me when I got the red light. When you do get into recovery leave it there a while to charge.
Sent from my Nexus 4 using Tapatalk 2
Is there any way of avoiding this red light of death issue. I am worried that it will happen on my Nexus
droidmakespwn said:
Plug it into a USB slot on your computer and repeatedly try and get into recovery. Worked for me when I got the red light. When you do get into recovery leave it there a while to charge.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
When plug into USB and connect to computer, it show the battery charge logo for seconds and back to red flash light. And I press volume up + power button, no flash but still Red light. nothing happened.
huangkaiwisdom said:
When plug into USB and connect to computer, it show the battery charge logo for seconds and back to red flash light. And I press volume up + power button, no flash but still Red light. nothing happened.
Click to expand...
Click to collapse
If you have adb access, boot to recovery there.
Sent from my Nexus 4 using Tapatalk 2
droidmakespwn said:
Plug it into a USB slot on your computer and repeatedly try and get into recovery. Worked for me when I got the red light. When you do get into recovery leave it there a while to charge.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I got red light of death and believe me I understand how it feels.
Good news: You can come out of it
1. Plug into wall charger for 1 hour or so. Make sure the wall charger has has at least 5V and 0.7 A, lower than that can not make sufficient charge.
2. After one hour of charging, the red light should go off (It's ok even if its RED light is glowing)
3. take out the charger and press power + Vol Down
4. Holding above two buttons, insert your charging USB to phone
5. The red light should blink and after a while you should be in boot loader.
5.1. If it doesn't do it again (Holding above two buttons, insert your charging USB to phone)
5.2. If you are not getting it after say 15-20 tries, leave it for charge for some more time and then try
6. Once you are in boot loader screen, don't let the screen turn-off, that is every 20-30 secs keep pressing vol button.
7. After 2 mins, chose reboot option and your phone should reboot, you can see zero battery
Bad News: Even though you will come out of RED Light of Death, the battery will become very weak (Very!!) and if again it turns off due to low battery it will go to RED Light of Death again.
If you have warranty and you are rooted, flash Google Firmware when you are in fastboot and claim your Warranty.
Sadly, I am in Singapore and using US set, so I can't do that.
Let me know if it helped.
Please help, when i was flashing awesome beats, at the end of flashing my device's temperature is very high and then it turned off by itself. After that, my device wont turn on when i pressed the power button although my battery shows 50%+ before flashing.
I tried to plug the charge and the white battery charging indicators appeared but then the device went off again after a while. It happens repetitively, white battery charging shows up, and then turned off. When i tried to turn on the device while plugged into charger, a google logo appeared and then turned off. I can access the bootloader when pressing the vol down button while it's charging. Please help me, what's happening with my device? is it because the battery is fully depleted or maybe another issue? Thank you
Sorry for my bad language.
Seems like something went wrong during flashing.Flash the factory rom..it should clear away your problem
SeNt frOm my A\/\/€$♡/\/\€ NoTE 2 using xDa premium app
mannyvinny said:
Seems like something went wrong during flashing.Flash the factory rom..it should clear away your problem
SeNt frOm my A\/\/€$♡/\/\€ NoTE 2 using xDa premium app
Click to expand...
Click to collapse
i've tried to flash the factory image but the problem still there. it wont turn on with charger unplugged, when it plugged, white battery charging indicator shows up, and then turned off with red led blink, after a while it turned on again with white battery charging indicator and again it turned off with red led blink, this happened repetitively. If i put my device in charge for a while, the red led wont blink again when it turned off after the white battery charging indicator, but it still wont boot..
ishall_07 said:
i've tried to flash the factory image but the problem still there. it wont turn on with charger unplugged, when it plugged, white battery charging indicator shows up, and then turned off with red led blink, after a while it turned on again with white battery charging indicator and again it turned off with red led blink, this happened repetitively. If i put my device in charge for a while, the red led wont blink again when it turned off after the white battery charging indicator, but it still wont boot..
Click to expand...
Click to collapse
I too faced somekind of this situation when I flashed Jellybam rom on my GNex..it won't turn on for no reason..random freezing.overheat..I immediately flashed factory image but the problem was still there for about 3-4 days!! ! isn't this weird?? But it automatically got fixed in few days and I still don't know how! So don't worry..:good:
mannyvinny said:
I too faced somekind of this situation when I flashed Jellybam rom on my GNex..it won't turn on for no reason..random freezing.overheat..I immediately flashed factory image but the problem was still there for about 3-4 days!! ! isn't this weird?? But it automatically got fixed in few days and I still don't know how! So don't worry..:good:
Click to expand...
Click to collapse
what did you do in those 3-4 days to your device?
Thanks for the advice
I hope more member will come here and have another solution to my problem :fingers-crossed:
Nothing..was just dreaming a fairy comes and fixes my phone
SeNt frOm my A\/\/€$♡/\/\€ NoTE 2 using xDa premium app
mannyvinny said:
Nothing..was just dreaming a fairy comes and fixes my phone
SeNt frOm my A\/\/€$♡/\/\€ NoTE 2 using xDa premium app
Click to expand...
Click to collapse
haha, i think i'll do the same until there's someone come to me and give me the solution :laugh:
Let it charge for couple hours before doing anything to it. How are you flashing the factory image? I recommend using one of the toolkit to guide you through.
Sent from my Nexus 4 using Tapatalk 4 Beta
Sometimes old school works.
Pull the battery and put it back in after 15 seconds
badboy47 said:
Let it charge for couple hours before doing anything to it. How are you flashing the factory image? I recommend using one of the toolkit to guide you through.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
i'm flashing using fastboot.
nwtspam said:
Sometimes old school works.
Pull the battery and put it back in after 15 seconds
Click to expand...
Click to collapse
I don't have the tools to open it.
Thanks for all of your advices, i think i've already fix my phone since it can boot again and i successfully restore my nandroid backup. I did charge my device using 3rd party charger with 2.0A for a couple minutes and then unplug it and charge using my original charger. and guess what.. it works hhe. Thank you all :good:
Glad its alive again. Next time make sure to feed it well. Don't let the battery die to 0%. Recharge it once u reach 5% to 10%.
Sent from my Nexus 4 using Tapatalk 4 Beta
badboy47 said:
Glad its alive again. Next time make sure to feed it well. Don't let the battery die to 0%. Recharge it once u reach 5% to 10%.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks btw. the weird thing is, when i turned on the device, the battery is the same as just before it turned off. I think the battery is not depleted to 0%, maybe the device is malfunctioning or something.
ishall_07 said:
Thanks btw. the weird thing is, when i turned on the device, the battery is the same as just before it turned off. I think the battery is not depleted to 0%, maybe the device is malfunctioning or something.
Click to expand...
Click to collapse
hmm that is weird. Did you try wiping battery stats? If not, give it a try.
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