Database Users

[Q] Help! My Nook is dead?

Hi,
mi n2e only with 1 week and has got frozen in the middle of a book. It doesn't respond. Soft reset doesn't work. Battery was about 50%.
I have disassembled it and try a lot of things, remove battery, connect to supply without battery... but the screen is in the same page of the book. There is no way to turn off screen.
Now with the nook connected to supply the led indicator is off and my computer doesn't detect it. This morning I got the light turned red (charging perhaps???) In this situation when I pushed button to turn off, the red changed to green for 2-3 seconds and then turned red again. And my computer detected it.
But now the light indicator is off again.
This is a gift from a friend in Usa. I live in Spain, so there is no warranty and for this reason I've tried to repair myself.
Any help, please? I'm desperate with it. I can't understand it fails in only 1 week.
Thanks.

> Soft reset doesn't work.
What do you mean by "doesn't work". It happened to me that my touch screen stucked but when I pressed "power off" button for a long time (e.g. 15 s) my nook rebooted and then if was OK.
But in you case whole system is stucked (no menu after pressing "n"), right?

Right. Whole system is out. Anything works... Now when I plug to power, there is no light on (led is off).

Hi Esfinge
Did you find a solution?
Same thing happened to me, I'm in South Africa, so can't take it back to B&N.
Got it brand new, charged it, connected to wi-fi, registered, loaded a book via Caliber (on Mac), switched off wi-fi.
The next time I picked it up it had the message that the unit is switched off and that
you have to power it up by pressing the power button on the back.
Tried removing the battery, did not help at all, also holding power button for 20 sec.
If I plug it into power the light goes green and then orange after a couple of seconds, if I connect it to a computer I can access the files on the nook.

esfinge said:
I have disassembled it and try a lot of things, remove battery, connect to supply without battery... but the screen is in the same page of the book. There is no way to turn off screen.
Click to expand...
Click to collapse
Dude, it's a e-ink screen..
When powered down it still retains its last image, it wont go blank unless told to do so.
JDRZA said:
Hi Esfinge
If I plug it into power the light goes green and then orange after a couple of seconds, if I connect it to a computer I can access the files on the nook.
Click to expand...
Click to collapse
That doesn't make sense, a powered down N2 will not mount the sdcard on your pc when connected via usb.
So if you're able to access the Nook partition while the N2 is still showing its "powered down" screen, you're in some serious trouble, as that would indicate the N2 is powered on and running, but not communicating with the e-Ink screen

So if you're able to access the Nook partition while the N2 is still showing its "powered down" screen, you're in some serious trouble, as that would indicate the N2 is powered on and running, but not communicating with the e-Ink screen [/QUOTE]
This seems to be the case, worked perfectly and then suddenly not, I might be sitting with a 'Friday' model.... anyone know where I can get a new screen?

JDRZA said:
So if you're able to access the Nook partition while the N2 is still showing its "powered down" screen, you're in some serious trouble, as that would indicate the N2 is powered on and running, but not communicating with the e-Ink screen
Click to expand...
Click to collapse
This seems to be the case, worked perfectly and then suddenly not, I might be sitting with a 'Friday' model.... anyone know where I can get a new screen?[/QUOTE]
Screen is black blank, hasnt came back since it first shut off after the first or second reboot on the first try restoring it to 1.4.3. The Screen was working fine before I used it everyday then i wanted to switch roms from phirmod 7.1 to NookieJoyOS it worked but the wifey didnt like it. She wanted her original nook color back. So I went back to original stock rom and then i started having problems. At first i though i had formatted something wrong in cw3.0.2.8. Above I was stating scenarios in threads i was reading on what possibly happened.

dbole said:
This seems to be the case, worked perfectly and then suddenly not, I might be sitting with a 'Friday' model.... anyone know where I can get a new screen?
Click to expand...
Click to collapse
I recently got an NST screen/digitizer for ~$40US on eBay, it took 5minutes to replace it.

[Q] Mt4G won't boot AT ALL

I went out for a while with my battery at 20%, when I came back it had drained out. I put it to charge, but when I tried to switch it back on, it refused to boot. On a normal power button press, it would vibrate 3 times and then the red notification light would start blinking. Same thing with power + volume_up. If I press power + volume_down, it would vibrate 5 times and the green notification light would stay lit. Nothing comes on the screen, whatsoever.
I was rooted with S=off, and was using the Operation Inferno ROM (which I have been using comfortably for the past month or so).
I did try some stuff with ADB, such as using it to reboot into bootloader and recovery (same 3 vibrate + red notification light), pushed the Operation Inferno ROM again to the sdcard and tried to restore the ROM from that location (for which I got adb: unable to open file /sdcard/backup.zip).
I haven't yet gotten around to downloading and installing the factory image some have suggested for the eMMC issue (PD15IMG.ZIP) but I wanted additional opinions considering most people with an eMMC issue have been able to open HBOOT at least.

When the phone doesn't power on, neither ADB nor fastboot will help you. There is no device on the other side, so all your attempts went to the drain, and it was expected. Nothing to do with eMMC issue or anything else. Your phone just doesn't power on.
Put your phone to charge, if the light turns orange - just leave it to charge until it's green, then disconnect and try to power on.
If the light doesn't turn orange, or it doesn't power on even after charging - remove the battery for 10 min, press Power button for 1/2 min, release the button, reinsert the battery, put to charge. And again, let it charge before you try to turn it on.

I did charge it earlier (for about half an hour or so) and the orange light does come, but it didn't boot after that either.
I'll just give it a try by charging it through the night and see.

I think a key thing is to take out your battery for 10 min, as Jack_R1 suggested. Then proceed with the charging.
Sent from my HTC Glacier

Still doesn't work. I dissembled it and kept it like that for quite some time, then put everything back and charged it for hours. Still the same issue happening during boot.

Connect the phone to USB, powered off, see if the PC recognizes "QHSUSB_DLOAD" device. Try to power it on, see if it happens.
If it happens - it means your primary bootloader is screwed, in another words - no repair (actually, repair is theoretically possible, but no guide, no information and no sources exist for MT4G).

Jack_R1 said:
Connect the phone to USB, powered off, see if the PC recognizes "QHSUSB_DLOAD" device. Try to power it on, see if it happens.
If it happens - it means your primary bootloader is screwed, in another words - no repair (actually, repair is theoretically possible, but no guide, no information and no sources exist for MT4G).
Click to expand...
Click to collapse
When its plugged in, its recognised by the ADB (even when powered off), and I can do some basic commands (mentioned in the first post). When I power it on the same thing happens as when it wasn't plugged into USB (ie, the vibration and the blinking LED).
I'm also worried about water damage, since a very tiny amount did come on it as I was sweating profusely. Although the indicators in the battery tray and on the battery itself don't signal damage (they're completely white) I've just decided to try and keep it opened up in a bowl of rice, just in case, until someone is able to come out with some idea.
As I'm in India, taking it to T-Mobile is not an option. If nothing works out, I might take it to HTC and see if they can help out.

my device has just quit workin all together

my att g2 4.2 rooted stock rom worked normally last night, this morning I plugged it into the car charger and it displayed it was charging with 2% charge present. I pressed the power button the boot animation began I set it down and when I picked it back up a few minutes later to use it...well nothing...the charging indicator led wasn't lit and when I pressed the power button LG appeared for only a split second then went black. when I plug it in same thing, LG logo for a brief second then disappears. I haven't done anything recently except xposed modules, no flashing of anything. any ideas? thank you guys

It happened to me (on other devices) when I let them discharged too far. Just allow it to charge awhile then try to hold the power button
for 10-20secs ... The NookHD+ were the worst in this situation (it won't charge sometimes, I had to plug/unplug a few times to initiate a charge, I was almost about to RMA one of them).

something else that's odd
when I plugged my device into my laptop the laptop acted like I just plugged in 12 different things that all needed to have their disk formatted. what is going on? wierd

pollutedmuse said:
when I plugged my device into my laptop the laptop acted like I just plugged in 12 different things that all needed to have their disk formatted. what is going on? wierd
Click to expand...
Click to collapse
try charging the device in offline mode ( turn it off and let it charrge for a while) and then turn it on . mind wouldnt turn on because of very low charge yesterday. doing this helped

update
I let it charge for several hours, nothing...it appears to be in some kind of boot loop. I can't turn it off all the way, I hold the powwer button for tensec or so and the LG will appear for a second then disapear and then the back light stays on. oh ya, when I plugged it in a few hours ago it wouldn't turn on but the red LED was flashing. I'm not sure how long it stayed on, but it was off when i got back to it several hours later. thank you for your time fellas!

If you can get to recovery at all, leaving it on charge in there. Has saved me in a similar situation.

shriom_manerker said:
try charging the device in offline mode ( turn it off and let it charrge for a while) and then turn it on . mind wouldnt turn on because of very low charge yesterday. doing this helped
Click to expand...
Click to collapse
Could have been the power switch that makes the phone short circuit and goes off anytime.
Sent from my LG-D801 using xda app-developers app

Thank you sirs, unfortunately still no good

it sounds like you had the same thing as everyone else yesterday that had twrp installed and the carrier automatically updated the system.
I could not get my phone recognized by the laptop and had to use pdanet drivers, which finally worked, but I still had to dig for the device. then had to flash back to stock. There is a pretty good thread on this topic, already. Search for it in the developer section. Do not skip any steps, such as setting the date back to jan2012 and turning off the internet. go slow and methodically, or you will miss a step and get frustrated.

[Q] Yet another Nook not holding charge and hanging at the boot screen

Google shows me I'm not even remotely alone in my trouble, but with the way tech works every problem is at least a little unique. I'll give a rundown of what I've down and whats happened up to this point.
First, I bought it used from Amazon. Very Good condition from a seller with 99% or whatever satisfaction. I think I've bought from them before, actually. So while this isn't a new device, I know I wasn't scammed. It was also factory reset and I'm assuming it wasn't rooted, though admittedly I have no idea how to check on a Nook.
Second, when it arrived the first thing I did, naturally, was turn it on. Plugged in the Nook to my computer, it booted up just fine, I registered, and loaded one a few ebooks with Calibre. The books opened up, they looked great, we were golden.That was when I noticed the battery indicator in the top didn't have a number on it. It was solid black with a ?. I thought that was weird, so I tried rebooting the device. That was when I was hit with an update, it downloaded and installed then rebooted. Here's when it all went to crap.
Third, I can get into the device. If I hold the power button and wait a bit it takes me to the homescreen where I'm met with a 0% Battery warning saying to plug it in or the device will shut off. Waiting for this message do disappear seems to give me normal access to the device, except the battery indicator is still just ?. This still happens now, after about 10 hours of charging.
Fourth, plugging in the device to anything be it wall charger or computer causes the device to reboot back to the Read Forever screen. Even if the device is completely powered off. It just hangs at the boot screen and goes nowhere. If I hold down the power button, or power + n, all it does is flash the screen to blank and then goes back to the boot screen. If I unplug it and hold down power it goes back to the previous problem.
That's everything I know. I seem to have the proper Nook micro USB cable, but the adapter is a little white Chinese looking thing so I know it's not the official. So I've switched to my Nexus 5's micro USB cable since I know it works and plugged it into my PC. The charging indicator is on, but thanks to my minor colour blindess I'm having a hell of a time deciding if it's orange or green. It's either green, orange, or yellow for sure though. Right now I'm going to go to sleep, let it charge through the night. I've had a similar problem happen to my Nexus 7 where it wouldn't turn on, and a nightlong charge seemed to fix it so who knows, this thread might be useless in the morning.
In the more likely event that it's still very useful, any help would be appreciated. And please try to keep it simple. I'm not new to technology or Android in phone/tablet form and all the associated hairpulling, but this is literally the first time I've ever dealt with an ereader. I'd like to get this solved at home, since I don't have a warranty and the price to ship this thing back to the seller would make this end up costing more than a new one would have since I'm Canadian and the seller isn't.
Thanks in advance.
Edit: After a night of charging, still 0%.

This, unfortunately, is the sign of a factory buggy (for lack of a better word) device. I doubt there's any hope. Sorry about that.
Keep me updated.

I think that there might be software to blame. My Motorola Defy also had that sort of weird battery behaviour after one of factory resets. Since then I have to install a patch written by one of XDA members every time I make a reset. But it works. Unfortunately I have no idea if it can be helpful in this case. (I'm refering to this post: http://forum.xda-developers.com/showpost.php?p=34590229&postcount=1 )
Nonetheless I would seek some slight hope in disconnecting and reconnecting the battery.

Alright, so. Progress report:
I tried the 8 failed boots trick to reset the device back to the original firmware. This brought me back to square one. The device worked, I could load books on to it via USB, and read them. But the battery indicator was just a question mark. Going into the settings revealed that the battery was at 100%, or at least claimed to be. But hey, I could read on it so I figured I was alright.
Now, a couple days later, I just woke up to find it with a new problem. Pressing the little N button to wake it up isn't doing anything. It won't respond to holding the power button down and my computer wont pick it up when it is plugged in. The charging light still comes on but I don't know how much it can be trusted.
I'm going to let it charge for a bit, but I'm beginning to think the battery is just toast.

Shodex said:
Alright, so. Progress report:
I tried the 8 failed boots trick to reset the device back to the original firmware. This brought me back to square one. The device worked, I could load books on to it via USB, and read them. But the battery indicator was just a question mark. Going into the settings revealed that the battery was at 100%, or at least claimed to be. But hey, I could read on it so I figured I was alright.
Now, a couple days later, I just woke up to find it with a new problem. Pressing the little N button to wake it up isn't doing anything. It won't respond to holding the power button down and my computer wont pick it up when it is plugged in. The charging light still comes on but I don't know how much it can be trusted.
I'm going to let it charge for a bit, but I'm beginning to think the battery is just toast.
Click to expand...
Click to collapse
Hi, I just went through something similar 48 hrs ago. The NST is frozen, stuck at reading forever. Before that, the battery icon had a '?', and the device info said battery status was "unavailable". Plugging in to charge had a solid green light.
I read around, and what worked was to open the case, and disconnect the battery. Google said to wait 30 mins, I waited 1. Re plugged in, put it to charge. The LED turned to orange, and 15 mins later, the NST booted. All good now.
Total cost: set of TORX scredrivers (you need a T5).

ghane0 said:
Hi, I just went through something similar 48 hrs ago. The NST is frozen, stuck at reading forever. Before that, the battery icon had a '?', and the device info said battery status was "unavailable". Plugging in to charge had a solid green light.
I read around, and what worked was to open the case, and disconnect the battery. Google said to wait 30 mins, I waited 1. Re plugged in, put it to charge. The LED turned to orange, and 15 mins later, the NST booted. All good now.
Total cost: set of TORX scredrivers (you need a T5).
Click to expand...
Click to collapse
Okay, so. No T5 but I managed it with a teensy weensy flathead. Unlugged the battery, left it that way for about 20 minutes, plugged it back in, then left it to charge. 15 minutes later I came back and viola, it works and the battery is reporting it's remaining juice. Thank you very much, that seems to have done the trick.
You know, this might be the first time I ever managed to have a tech problem solved entirely by a forum.

Shodex said:
Okay, so. No T5 but I managed it with a teensy weensy flathead.
Click to expand...
Click to collapse
You realise that that voids the warranty you get from XDA?
Shodex said:
You know, this might be the first time I ever managed to have a tech problem solved entirely by a forum.
Click to expand...
Click to collapse
I knew the Internet would be useful for something, one day

ghane0 said:
You realise that that voids the warranty you get from XDA?
Click to expand...
Click to collapse
It's a used device, there was never a warranty.

Looks like the problem is fixed. Great! Sorry I was inactive.
Later!

[Q] N4 doesnt turn on. Red Light blinks once.

Hello.
When I try to turn on my N4, I hold power button, and after about 10 seconds Red light blinks (just once, if it's connected to USB that 1 blink last for 3 seconds, if connected to wall, it's just quick 1 blink. If it not connected anywhere there is no action at all, it just stays dead, no blinks, nothing). Same if I try to go in bootloader by holding volume down+power.
This happened after I successfully installed CM12, with no errors. Then I rebooted my phone, and it just stayed black as it is now. Battery was around 25~30% that time, and phone was connected to USB.
Did I bricked my phone totally? I am now trying to charge it up already for 1 hour... but it nothing changes.
I have searched here for similar problems, but couldn't find solution...
Edit: Charging already for 10h+ , still same..
Edit2: I removed battery, reconnected after a while, still same problem.
So I tested it with multimeter, it says 2.6V, but fully charged must be 3.8V. Could this be a problem? I was charging it for whole night.
Edit3: I just got new battery . But it looks the same.. phone doesn't boot up.. same red light blinks once.. so.. its my phone is dead? I can't believe that...
When I connect to PC usb, there are unrecognized deviced called "QHSUSB_DLOAD".

easy fix
Hold down the power button and the volume down button at the same time until phone reboots. If you see the little android no need to worry just let go and wait for your device to reboot on its own. This is not a factory reset it's just like restarting your device. :good:

zelexon said:
Hold down the power button and the volume down button at the same time until phone reboots. If you see the little android no need to worry just let go and wait for your device to reboot on its own. This is not a factory reset it's just like restarting your device. :good:
Click to expand...
Click to collapse
I have tried that many times. Nothing. It's bootloader screen, but I can't get there. Nothing happens. If I keep holding volume down+power it just keep blinking once every ~10 seconds, same if I hold just power button. If phone is not connected to charger, there are no blinks at all.

I removed battery, reconnected after a while, still same problem.
So I tested it with multimeter, it says 2.6V, but fully charged must be 3.8V. Could this be a problem? I was charging it for whole night.

Cracken6 said:
I removed battery, reconnected after a while, still same problem.
So I tested it with multimeter, it says 2.6V, but fully charged must be 3.8V. Could this be a problem? I was charging it for whole night.
Click to expand...
Click to collapse
I had the same problem a year ago, I tried to remove the battery, charging all night, and other solutions that I found online and no one worked.
Finally I found here in XDA a user with the same problem and his solution was charger the phone with a wireless charger, a friend of mine has one and I put the phone to charge and after a few minutes the screen goes on and the phone was charged, then I press power button and the nexus run again.
Hope this works.
Sorry for my bad English, I'm from Spain.
Good luck.
(I bought a wireless charger in case it happen again)

I don't know anyone with wireless charger. I already ordered a new battery, and then I probably will get wireless charger also. Ty.
But this problem is very weird if you think so.. I think it happened because of many aspects together:
1) Battery was already below 30%
2) I pretty regularly charge phone with USB (won't do it again)
3) It was connected to PC USB in same time.
4) I installed CM12 ROM in same time
So main reason I think is USB, that I restarted phone while it was on pretty low battery and with USB connected.. phone restarted and got invalid voltages and couldn't even boot up or charge phone. I also found an article which says, minimum voltage, when phone battery has 0%, it's 3.0V, so I was below that.. it just screwed everything and battery died. Well, I am not sure for 100% that it's battery fault, but I hope so, I really love my N4 and still wanna use it for long time, I hope it's not dead phone, just a dead battery. Lets see! I will update this thread , when I get my new battery (less than month probably).
Sorry, my english is also not perfect. I am from Latvia.

I was playing when it happened to me. The phone was very very hot and the battery was around 70%. When I put in the wireless charged and I can reboot the phone the battery was at 65%, so it had charge but the phone won't boot.
I charge my phone almost every day, sometimes with AC, others with USB (plugging to PC) or wireless that depends of my needs
I hope you can fix it. Good luck.

Btw. Do you know if battery charges with wireless charger, if it's removed from the phone?

Don't think it does, since the receiving coils for wireless charging are located just behind the glass back.

Flipz77 said:
Don't think it does, since the receiving coils for wireless charging are located just behind the glass back.
Click to expand...
Click to collapse
The battery will charge with a NCF Charger
Major Issue Google
This "Nexus SOD" issue is showing up on many sites across the Internet. I have multiple "Nexus" devices including 2 Nexus 4, 1 Nexus 5, 2 "Nexus 7 2013". It suddenly started out of the blue with one of my Nexus 4 phones. Symptoms included rapid battery discharge. I am using Lollipop 5.1 on all devices. There are many claims as to the cause, Hardware Motherboard, Power Button etc. Others claim it is "Software Related" or App Related. The problem effects Nexus 4 and Nexus 5 phones. I have ordered a new motherboard for my nexus 4 device and see if that makes a difference.
This problem should warrant a "Major Android Lollipop Crisis Team" by Google to investigate the cause and let us know what it is and what Google is doing to solve the problem before moving to announce "Android M". This issue needs to brought up and actively pursued at the upcoming "Google I/O Conference" by the strong Android Developers Groups to press for "Formal Action"

charging method
Cracken6 said:
I have tried that many times. Nothing. It's bootloader screen, but I can't get there. Nothing happens. If I keep holding volume down+power it just keep blinking once every ~10 seconds, same if I hold just power button. If phone is not connected to charger, there are no blinks at all.
Click to expand...
Click to collapse
I had this problem a long time ago and my fix worked for me after doing a little research it seems like this is a case called battery total discharge. The fix was simply to charge your phone using the wall adapter that came with your phone (I still use my old apple cube wall thing) and to wait for the red light to appear then wait about ten minutes before trying to reboot.

I just got new battery . But it looks the same.. phone doesn't boot up.. same red light blinks once.. so.. its my phone is dead? I can't believe that...
When I connect to PC usb, there are unrecognized deviced called "QHSUSB_DLOAD".

Maybe this video will help you: Oh I´m not allowed to post links until now.
Just search for: - Nexus 4 "red light of death" fix - at youtube.
Hope it will help

AndRe5575 said:
Maybe this video will help you: Oh I´m not allowed to post links until now.
Just search for: - Nexus 4 "red light of death" fix - at youtube.
Hope it will help
Click to expand...
Click to collapse
I have checked all kind of videos there. Also that one. Most of these cases are related to battery, but it seems in my case it isn't. I just searched for QHSUSB_DLOAD unrecognized device, all posts says it means phone is bricked... But cmon, how? I installed CM12, successfully, without any errors, then just restarted phone, and its dead...

Cracken6 said:
I have checked all kind of videos there. Also that one. Most of these cases are related to battery, but it seems in my case it isn't. I just searched for QHSUSB_DLOAD unrecognized device, all posts says it means phone is bricked... But cmon, how? I installed CM12, successfully, without any errors, then just restarted phone, and its dead...
Click to expand...
Click to collapse
Did u try booting the phone without battery by connecting to wall charger and what about flashing stock ROM via PC
Also check that the power button works
This case should be solved

as9333 said:
Did u try booting the phone without battery by connecting to wall charger and what about flashing stock ROM via PC
Also check that the power button works
This case should be solved
Click to expand...
Click to collapse
Just tried booting without battery, and connecting to wall. Same - red light blinks once, after I hold Power button or Power+Volume down for about 15 seconds. If I keep buttons pressed, it just repeats every ~15 seconds.
Power buttons works fine.
After I checked that Device manager thing in google.. it looks very bad.. phone is dead.. probably need to change motherboard. I am just shocked, how this could happen... I didn't receive any errors during CM12 installation. Phone just instantly died after restart.