[SOLVED] (HD) Stock runs perfectly but CM ROMs are now causing havoc - Nook HD, HD+ Q&A, Help & Troubleshooting

Wow. This just gets weirder and worse(r). We've been running first CM 11 and then CM 12.1 on this HD for awhile and all was fine. Suddenly the battery indicator became wonky, dropping from 50-ish% to 1%, precipitating a shutdown unless the tablet was immediately plugged in. Then suddenly the battery indicator would return to normal and you could unplug the tablet.
Next, after running a backup on the CM 12.1 ROM the tablet started crashing during boot (the cyan android phase) UNLESS it was plugged in to the power supply (USB to computer is not sufficient). This, despite a good charge level on the battery. After a minute or so when the boot was complete, you could unplug the tablet and go on your way.
Today the screen flashing began. Makes the tablet completely unusable. Sometimes you can calm it down for awhile by connecting via USB to computer, sometimes not. This thing is freaking me out. I just recently took the tablet all the way back to stock and resintalled CM 12.1 from scratch, including building a new SD card from new files. Before someone asks, it's a class 4 card. I've always been fine with Class 10 or UHD cards when working with my Nook Tablet, but for some reason I decided to play it "safe" with the HD and hunted around for a lower class. Maybe a mistake?
Finally I took the tablet back to stock again today, completed the sign-in process to the old B&N account and everything is fine. No screen flashing, no funny business with the battery indicator, no problem booting without the power cable.
I just ordered a "new" (out of box) replacement for the tablet on ebay, but it doesn't seem like this is an actual hardware issue.
What scares me now is a potential repeat of this process with the new tablet. I've never had any experiences like this with my old Nook Tablet. I'm at a complete loss.
Help!
Edit: OK, we seem to have tracked down the general source of the screen flashing. The backup we have been restoring is from July 2017 so quite a few apps want updating. We noticed things would be fine for awhile and then the flashing would start. At one point "Unfortunately Google Play Services has stopped" kept popping up. I began to suspect either a bad or incompatible update was messing with the system. So...we did another restore of the same backup but immediately turned off auto-updates from the PlayStore. Three days later and no display flashing. One small victory.
Could the shutdown during the boot animation be caused by a corrupted file? I don't see how since it boots OK when plugged in, just not on battery, but I'm willing to pursue any possibility.
Edit.Edit: Well, well.... We got a "new" open-box HD from ebay and I started working on it. I noticed in making new SD cards that one I had been working with was not properly set to 0x0C FAT32 LBA. I fixed that. This time the tablet will boot into the OS without being plugged in! Yay! Still have to test that on the old one after I finish building a duplicate system.
I'm restoring apps and everything is fine until suddenly the flashing starts up again. But now I know when it did. The offender seems to be the 0.15 version of Lithium Epub reader. I managed to uninstall that via ADB (with screen flashing you can't do much with the tablet except ADB). Voila, no more screen flashing. I found a copy of version 0.13 and installed that. No flashing screen. Needless to say I've set the app to not auto-update.
Edit.Edit.Edit: Well, $40 later we now have a second Nook HD and both are running fine. Hard to imagine that the goof that somehow happened to the SD card would manifest as only being able to complete boot when plugged in, but that must be it. Returning to stock (tried that...) and reflashing with the newly prepared SD card did the trick. Moral: sweat the small stuff.

Related

[Q] Strange reset from CM7 to Nook 1.2???

OK, here's the situation:
Nook Color running CM7 7.0.3 from SD card. Been running this since May without problems.
Last night I plugged in the Nook to charge and turned off the screen.
This morning I unplugged the charger from the Nook and it chirped. Never heard that before. I turned on the screen and it was at the out-of-the-box Nook lock screen. I swiped to unlock and found that overnight my Nook had somehow reset itself back to 1.2 of the Nook OS. I looked at the SD card contents and nothing was here.
I powered off completely, then back on, and all was well, back into CM7 from the SD card.
Any idea what caused this? I don't remember seeing any issues like this since I started following these forums in May.
Thanks in advance for any suggestions.
Steve
By "reset itself to back to 1.2," do you mean you had 1.3 installed and somewhat personalized previously, or just that it unexpectedly booted into stock instead of CM7?
I have no clue what happened either way--I'm just not sure what you're describing. If you were running CM7 from SD, stock was always still there, and some power irregularity caused your NC to shut down unexpectedly, and apparently fail to boot from SD, causing it to boot from stock on the internal storage instead.
Additionally, something may have triggered a factory-reset, but in that case it would have walked you through set-up again, and you said it took you straight to the lockscreen.

Nook Freezing at 99% on start up

My nook was running fine as of 30 minutes ago. I turned it off when I left to go up to my college class. When i got up here, i turned my nook back on to check my email and it is freezing at 99% on boot, I took the sd card out (just a normal 16 gb card with movies on it) and it still does the same thing...is there a way to fix/diagnose this without having to reformat the whole thing? I can sill enter the factory reset, but i would really not want to. I saw something abou another user having a similar issue, but I cant find it now.
This is on a rooted stock (latest version from B&N) HD+
At first i thought it was heat issues due o it being 90+ degrees up here, but im in he classroom atm and its sill having the problem.
EDIT:seems like something happened to where It reset itself when i plugged it into my computer at home...*not to self, make titanium backup, backup to ext_sdcard and NOT sdcard* not that i lost anything thankfully lol
im guessing something messed with the /system...but only thing i downloaded today was Ravensword, Fast Reboot(1st two from play store), and BT Controller 1.4 (outside source) (Most likely this)

[Q] Screen Issues?

I did a search and couldn't find any other topics covering the same issues I'm having, both here and a general Google search. I also called my mother, and she did indeed say I was special.
Anyway, bought a Nook HD+ two weeks ago and left everything stock for a few days before using Bokbokan's Hybrid SD/EMMC. Everything worked great and enjoyed it for a full week until my Nook started freezing and getting an odd ghosting and slow refresh on the screen.
Figured it was a rom issue so I removed the SD but even when powering it back on the screen had the same effect. And it continued into the stock rom. I de-registered and returned to stock and still had the same issue. Washed out screen, slow refresh, slight flickering an odd randomish burning which held even when the device was powered off and left off for hours. Used the HDMI adapter to see what happened and the output to the TV was fine, making me think I just had a defective screen.
So I returned it for a new one. Followed the same path. Stock a few days, then hybrid install (with the newer Bokbokan rom). Ran great for another few days until I had the screen freeze on me. Not ghosting like I had before, just lines like a disconnected ribbon cable. I reset a few times though and everything was fine. The next day it did it again but took removing the SD card and hard resetting into stock to get it to fix the screen. Then a few hours later I could only get it to boot into the stock rom with a normal screen(CM10 would always have lines and be unusable before it even started booting) , but would go out after 30 seconds. Booted into CWM from the SD card and the screen was fine so I did a factory wipe and left out the SD and booted into stock. De-registered before the screen went out and started over. Started re-registering it and the screen would start going out after the 30 seconds but then snap back to normal after another ten or on a new screen. Once it finished setting up my BN account I reset and... now it seems to be running normal... Left it sit like this for a few hours (checking it every few minutes) and I haven't had a single issue.
This seems to me to be something I'm messing up. I can't see having two defects like that in a row, when I know other people who bought the same week/store from me and haven't had any issues (also running the same Bokbokan rom). And the fact that it seems to fix itself the longer it sits in stock. I haven't dropped it. There has to be something I'm not thinking of that's causing the issues. But I'm completely out of ideas.
Is this maybe some kind of new anti-rooting thing by B&N? Does someone have a voodoo doll of my Nook? My SD card have some type of bacterial infection? Maybe a full blood moon overhead? An allergic reaction to my screen protectors?
Any ideas?
Do you have some big magnetic source or other device in your house that could be effecting your HD+? Just grasping for straws. Never heard of this before.
You might try verygreen's NEW SD scheme and see if you get the same thing.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Do you have some big magnetic source or other device in your house that could be effecting your HD+? Just grasping for straws. Never heard of this before.
You might try verygreen's NEW SD scheme and see if you get the same thing.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
My case does have a magnet in it, but this started before I got this new case.
But the way the screen looks is the way a screen looks like when it needs degaussing... But wouldn't explain why it only clears up after running a fresh stock rom for a bit.
Which has me thinking now it is something wrong with my rom. Even though both Nooks used different roms. I shall try using verygreens and see what kind of results I get.
I hate problems like this. =p
I'll report back in a bit!

Bricked Nook HD

Hello;
Sorry to bother anyone and thank you for taking the time to create this site. I have a Nook HD "Humming Bird" and recently Installed CM11 on it. The other day the Tablet's battery went completely dead and I was able to get it charging again the next day, Upon turning it on the tablet turned on and just Displayed the Nook logo on the front, I have tried recreating the Bootable SD cards and even reverting it back to stock Roms, the tablet act as tho everything is completing successfully but the I restart it, nothing happens it just stays on the nook screen.
I'm really running out of idea's it was working fine and I have flashed this as well as about 4 or 5 different phone. I have seen other forums stating that I need to revert back to stock recovery, rom and each attempt I haven't been successful phone show it installing it complete's it with no errors but then when I turn it on nothing happens.
The only thing that I have noticed during the flashes is that it says something Offset5124 (I don't know if these are correct) and I think a message pulls up
Installing Boot... Installing Boot... Installing Boot...
Any help would be awesome and thank you very much

Nook auto shut off after factory flash and reset.

I recently decided to go back to complete stock. I wanted to see how a factory stock rom would deal with the battery issues and others I've had. That's where the problems really began. I followed the instructions in a current thread. I used this thread years ago to root my nook without a problem. My Nook HD+ this time would not boot from any SD card. It did not matter what image I used or what method from the mentioned thread. The SD cards are good though. I stupidly did a factory wipe/reset in CWM, mostly because I had tried everything else. I knew not to do it, but I had tried everything! My Nook would stay on the Caynoboot after this. I finally got a flash to work using the old method and CWM 6028, but this time it hung on the Nook screen. After fighting this for a while, I finally got the stock recovery and stock rom to flash. Great, it's working again as it should. The problem I have now is if I leave it alone for a bit the Nook will shut off. I can power it back on, but sometimes it takes a couple of tries. I tried to charge it this morning when the battery went down to 6%, but I could not use my Nook charger. It would shut off or start to boot past the Nook screen and then shutoff. I'm typing this now and my Nook is charging fine through my computer. Has anyone experienced the auto shutoff when leaving it alone? It's totally annoying, but it functions fine other than that. All of these problems came to life after going back to stock root. Personally, I don't feel like starting over again. I'm to nervous that something will go wrong.
My thought is this relates to all the known battery problems the Nook has. CM might eliminated some of the obvious though. Mine started 3 months after I bought it years ago. It was part of the reason I went to CM10 at the time. I thought maybe the factory rom was the issue. Do you guys think the auto shutoff and normal charging method issues are battery related? I don't think it's a hardware issue. It could be the way the rom was finally flashed, but I would expect more problems other than the above. One thing the factory rom did fix was the Nook shutting off on almost any flash video. It was always random, but this has not happened since going back to stock.

Categories

Resources