Until recently, my HD+ has continued to labor on almost flawlessly since converting over to full Android quite some time ago. It is currently running v5.1.1/CM 12.1-20151018 Ovation.
In the last two months it has started to simply not boot up (even while fully charged) unless I plug it in. Even then, it takes several minutes before it boots. I can get it to reboot while unplugged, but if I fully shut it off by holding down the power button, it will not restart unless I plug it in again.
Have had to go to holding the power button down for full shutoff as it also will spontaneously reboot if you select power off from the menu.
As it has not exhibited any issues until now, I am clueless as to what is going on.
I am using it only for viewing photos taken with my digital camera via its sd card, using it for graphic novels, and using the Prestigio ereader for for ebooks with photographs and color plates.
Other than the apps for the graphic novels and Prestigio, I have it totally stripped down and don't even use the wifi connection.
Will be very greatful for any assist with fixing this.
Could it be as simple as refreshing 12.1 or should I go back to 11.1?
PS: Appears to be related to having the sd card inserted or not. Will start with card out when it won't with it in. Cannot reboot into TWRP.
PPS: It was definitely the sd card used to configure the Nook. Replaced it with a clean one and (almost) all of the problems disappeared.
Still does a spontaneous reboot if I use the software "Power Off" from the menu once the power button is pushed.
If I hold the power button it will fully turn off and not reboot. and then starts normally.
For the limited use I have configured it for, I should leave "well enough" alone at this point.
Any ideas as to the spontaneous restarts???
It still has one of the best screens around!!!
Thanks in advance.
Related
Having an odd issue with my Nook (rooted with Auto-Nooker).
When I power it off, I cannot seem to power it back on with the power button, unless I plug the USB cable in first. Any ideas? Is this normal? Thanks.
I had problems the first couple of power ups, then is started acting normal.
I just got ny nook last night and when i tried to wake it up this morning i had to plug it in. I hope it fixes itself soon.
Sent from my NOOKcolor using the xda app
Silly question perhaps, but a few people have forgotten... Did you remove the SD card with the Auto Nooter image and reformat it? Otherwise it will boot into that every time you try to turn it on.
peiziyu said:
Silly question perhaps, but a few people have forgotten... Did you remove the SD card with the Auto Nooter image and reformat it? Otherwise it will boot into that every time you try to turn it on.
Click to expand...
Click to collapse
This was my problem as well until I did what you said. Thanks for the reminder!
I was having the same issue in the beginning. Even without the sd card inserted, I'd have that issue. It seems to be fine now, though.
Are we supposed to see the Nook color custom boot animation with the little android guy on the bottom right, though? I thought it was just part of the rooting/setup.
sano614 said:
I was having the same issue in the beginning. Even without the sd card inserted, I'd have that issue. It seems to be fine now, though.
Are we supposed to see the Nook color custom boot animation with the little android guy on the bottom right, though? I thought it was just part of the rooting/setup.
Click to expand...
Click to collapse
Everytime I have rebooted I have seen that boot screen, so it should be normal
I have taken my card out and reformatted it. My issue is more so when i leave my nook alone for a long period of time and it is just sitting in sleep mode. I have to hold the power button to get it to come back on(it reboots).
Sent from my NOOKcolor using the xda app
I think that is intended, pretty sure you had to push the power button for a second or two stock as well... reduce accidental power ons?
Seems odd, but I found a way to start up my Nook Color without having to plug in the USB. If I press and hold the Home button for a few second, then press the power button, it'll come on.
The custom logo is a standard part of the rooting process. If you don't like it, you can revert to the standard by moving or renaming /data/local/bootanimation.zip
I recently tried booting using what turned out to be a bad SD card image. At the time it got as far as the ANDROID block letters on the edge of the screen. I took the SD card out but then realized I had no way to reboot it: the power button did nothing and I couldn't pull the battery like on my Droid. At first the only option I could see was to wait a day or two until the battery ran down. Now, I know nothing about adb except what I did to get the market added to froyo but I did remember that it ended with an adb reboot command. I tried that, my NC rebooted and all is good.
So I'm wondering what options exist when the device doesn't boot?
- adb reboot (may not respond and probably of little use if EMMC boot is bad)
- ???
Make a bootable sdcard with CWR on it. Then no matter what state the device is in if you put the bootable sdcard in the device and power on it will boot into CWR so you can do whatever is needed to get yourself back up and running again in short order
But what if the device is already on like in my case? Other than adb reboot (which may or may not work) there's no way to force a reboot, or is there?
FYI you can always turn the device off no matter what. Just hold the power key for about 10 - 15 secs and no matter what states you are sitting at it will force it to power down. Just like a comp when you hold the power key down for an extended amount of time it will in fact power off.
On another note depending on what recovery you have on the device if it does get stuck and you force it to power down like I just mention you can boot into ( CWR ) recovery mode and from in there there is a reboot option also. Again tho that would only work if you have CWR installed on the internal memory.
I did hold the power button down for fairly long time. Apparently it wasn't long enough.
I just have the rooted stock 2.1 internally. Don't know what, if any, recovery that gives me.
So much to learn, so little time...
lol.... I hear ya there. Been messing with Android phones for ages now but a new learning curve when it comes to the Nook with so many different options we have to choose from. BTW I have had it to where I had to hold the power key down for over 30secs to get it to power down just so you know. If you run into the issue again for sure just keep holding it and it will power down at some point.
Good to know. Thanks.
Hi all,
I bought a Nook HD+ around a year ago, and installed CM11 and CWM recovery on it. Everything worked fine until coming back from a trip in June, when I noticed that the power button required several tries to power on the device. I thought nothing of it until I came home and found that it wouldn't turn on at all, having tried all the button combinations and power cycles suggested in these forums. Now here's the strange part: I believe the internal eMMC may be corrupted because a) there's no battery icon when plugging it in. and b) when trying to turn it on, the screen is clearly on for a couple of seconds. It turns grayish and I can see the edges of backlighting, but there's nothing on it. Also, it won't boot from microSD or show anything on the screen at all. So, I have two questions: 1) What is the cause of this problem, e.g. broken screen or bad memory, and 2) What can I do to fix this? The tablet is just out of warranty, but I do live relatively close to a B&N store.
Thanks in advance,
sgamer395
HI,
I've had a Nook HD+ for less than a week, and I seem to have turned it into a brick last night. I booted with a AFN card (dual boot) and it booted ok, and I loaded up a kindle app, and a file manager app. I had the charge cable hooked to my computer's USB, and the PC screen showed my device and 2 folders, which I believe were the internal memory and the 32 GB card with the AFN software. I dragged file onto one of the folders and immediately the Nook's screen went dark. Nothing I could do, with the 32 GB card inserted or removed, would have any effect on the Nook. I"ve been pressing the on switch for >> 30-60 seconds, and also tried it with the N key held down and with the volume keys (both and singular keys) held down. The tablet will not do ANYTHING. When I first push in the data/charging cable in, there is a little LED next to it. It will turn green for about 5 seconds, and then it will turn orange for about 5 seconds-that is all. Nothing else happens.
Is there anything I can do to fix this thing?
Thank you for any info.
I think the Nook HD+ would have been all I needed-I mostly just read books. Sometimes I go to Starbucks, and browse the web, that's mostly about it. But I have all formats of books, EPUB, PDF, Kindle, DJVU, mostly and the Nook wouldn't 'take' the Kindle app obviously, so I thought this (turning it into full android) would be good.
If I get another android, what's good and cheap? I'd prefer
I'd let it charge for a day.
I have a Xiaomi Redmi Note 4X, which I started using around March. Lately, I have been facing an issue which has left me troubled a lot. My Note 4X seems to be in a bootloop.
Around two weeks ago, I was casually using my phone in college. I had put around 25 apps on download from Google playstore. Alongside, whatsapp was running. I usually take pics of my lectures, so when the teacher had written on the board, and was about to erase, I quickly attempted to go to the home screen, by clicking the home button ( middle button), so I could launch the camera app, and take the pic. But, the phone didn't go to the home screen, and stayed at the app being used. However clicking on the recent apps (the left button), the two running apps showed. However, as I didn't have much time, I did what came in my mind. Reboot the phone. Unfortunately, as soon as it booted back, the screen remained black.
Its been like this for two weeks now. Whenever I turn it on, It will show the Mi logo, then the Android logo simultaneously below it ( Like usual when it boots), but after that, the screen goes black. Touching the three buttons at the bottom of the phone make the back-lit underneath light up along with a vibration(Like usual). Clicking the touchscreen gives a vibration. If a sim card is put inside, and a call made to the inserted sim card's phone number, the phone starts ringing as usual, however, still with a black screen. Another major issue I experience other than the black screen, is that the top right of the phone becomes really really hot as time progresses( within minutes)(This never happened before), and the battery drains really fast too. I get freaked out because of this( I think it might explode or catch fire), so I quickly turn off the device, after some tinkering.
I have been trying to find a solution since the past two weeks. Hard pressing the Volume Up+ Start button takes me into MiRecovery 3.0, which offers 3 options, 1.Reboot, 2. Wipe Data, 3. Connect To MiSuite. Going into 2 gives the option " Wipe All data" only, and 3 is seemingly useless the MiSuite doesn't support new versions of Android. Hard pressing the Volume Down+Start button takes me to FastBoot. It should be noted, that in both MiRecovery 3.0, and Fastboot, the phone doesn't warm up really fast, as it does when booted normally, and rather remains cool even if left for quite sometime in these modes (approx 30 minutes atleast).
The main thing I'm trying to achieve is to backup the data on my phone, mainly the photos (lecture notes), and whatsapp data. The rest of the app-data isn't that much important, albeit if also savable, it would be a bonus.
I haven't tried flashing any ROMs, recovery, or anything else, as I'm afraid the data may be erased, and as I have never done anything like this before. Also, my phone isn't rooted, as I didn't feel the need for it to be.
Help is highly appreciated. I hope to be able to safely extract my data, and be able to start using my phone again.
Thanks to advance to all those who reply.
Guys?
:/
Try Redmi NOTE 4X forum.
I Have the same problem,
I Have the same problem, did you solve the issue?