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.
Related
I was wondering if I was missing a post. I still get random Cyanogen Shut downs. I am using 4.2.13 after a wipe and still experience random shutdowns.
The phone just goes dark and I have to power it up again.
I have read some people attribute it to locked home screen and some people while using locale.
It is quite frustrating and I was wanting to know... if there isn't a fix, what Rom should I port back to. I need to clear this up because it gets aggravating missing calls.
Give superD 1.2 a try or even dwangs ROM they both are very speedy and well stable
Try re-flashing the rom, or you can try another rom as you said...i recommend Super D or WG Build....i myself use WG Build
You might be running out of system space.
Go to console:
$ su
# df
Check the Available next to /system. 28mb should be normal, but you could always apply the 10mb ramhack. Go with CFS for stability.
Can you recreate the scenario by which the phone will reboot on it's own and get a logcat?
No I cannot recreate it, it is very random. Afterwards I cannot logcat. I have tried wipe and reinstall of alot of his roms, all of them do the same thing.
I was hoping there was a fix because it is his rom I prefer.
I guess I will try another rom and maybe the problem will resolve itself.
Brutal-Force said:
No I cannot recreate it, it is very random. Afterwards I cannot logcat. I have tried wipe and reinstall of alot of his roms, all of them do the same thing.
I was hoping there was a fix because it is his rom I prefer.
I guess I will try another rom and maybe the problem will resolve itself.
Click to expand...
Click to collapse
Try Enoms rom if you tried Super D and WG-Build Y-2.6 with no success.
The problem you have is definitely weird.
I also suggest updating your Radio, Spl and RA Dream to the latest versions.
If possible try another microSD card preferably Class 6 to see if that fixes your problem.
I've been experiencing this same thing with random shut downs. I am running 4.2.13 also.
I have tried a wipe and re-install but the problem still exists.
There doesn't seem to be any rhyme or reason to it. The only thing I can say is that it always happens after the phone has been idle and when I go to pick it up it's powered down and I then need to power it back up.
It is very frustrating becuase you're never fully aware that the phone is off until you go to use it. I don't know if it's the ROM or some program that I've installed. I've been uninstalling all recent programs but so far the problem still exists. Perhaps I'll try one of the other recommended roms.
I have tried the stock rom and Dwangs rom, so I doubt its the ROM. Also I installed minimal applications and it still happens.
Its a toss-up between battery and phone. Although my battery is an extended battery, it can happen even when the battery is at 80%+ charge.
I called T-mo and they are going to swap out my phone. When I get it I will run the stock rom for a couple days with my Extended Battery. If it continues, I will put the stock battery back in it. Then I will go back and root it. If the problem comes back, then it has to be the rom.
Brutal-Force,
I'll eagerly wait your results. Unfortunately I purchased my G1 off of ebay a year ago so if it is the phone I'm out of luck.
Out of curiosity do you use Nitrodesk Touch down for Exchange? I've had some reboots right in the middle of synchronizing my email with this program.
Thanks
No I do not. As a matter of fact, I had uninstalled almost everything in an attempt to track down the culprit.
I really do think its gonna end up being the battery. Since the phone is not an option for you, I would recommend trying out a cheap 10 dollar battery off the internet. While I can't imagine why a charged battery would do this, I have noticed by looking at a friends G1 that the phone interprets batteries in different ways. In his phone his battery never showed below 90% even though after 10 hours it would run out of battery. As soon as he put in on the charger it showed 90%.
I to had purchased one of the extended batteries shortly after purchasing the phone. It has worked fine for just about a year but perhaps it is beginning to have problems. I'll dig out the original stock battery later today and try that for a day or so and see what happens.
Thanks
I have the same problem. My phone randomly restarts. It's more of an annoyance rather than a big problem, especially since it's almost always a restart and not a shutdown. If you guys do indeed find out it's the battery do post your findings here!
Thanks
I have exactly the same symptoms. Though before I saw this post I was attributing it to the fact that I have recently dropped my phone.
I also have a spare battery (I'm using Andida instead of original now), so I'll test to see if that happens with the original too.
Hmmm..
OK so i take out my extended battery and put in the original battery and plug it in to charge since it's on the low side. The phone immediately reboots and continues to do so indefinitely.
As soon as the home screen comes up it reboots.
So I put my extended battery back in and same thing. Now I'm not sure what to think so I've backed up my SD card and performed a complete wipe and am installing a completely different ROM.
I'm hoping it was the ROM or some program and not the phone.
I'll get back later.
rckeystone said:
Hmmm..
OK so i take out my extended battery and put in the original battery and plug it in to charge since it's on the low side. The phone immediately reboots and continues to do so indefinitely.
As soon as the home screen comes up it reboots.
So I put my extended battery back in and same thing. Now I'm not sure what to think so I've backed up my SD card and performed a complete wipe and am installing a completely different ROM.
I'm hoping it was the ROM or some program and not the phone.
I'll get back later.
Click to expand...
Click to collapse
Its good that you guys are investigating the cause of this issue. I too admitingly started using CM when I first rooted my phone. I too had issues and FCs so changing the Rom was the first thing that came to my mind.
You never know maybe its the battery (see the 1700 battery thread on the many problems Andidas has had with their G1 extended batteries)
In the end I am hopeful that you find a solution and have found out sometimes its as easy as changing Roms to fix many complaints/issues you might have.
This is what I've experienced so far.
I did a full wipe of my phone yesterday and installed the AOSP ROM (went away from cyanogen) and I have installed most of my programs. So far all is great. I've had no reboots or any other issues. Since yesterday I have been using my extended battery so I know the battery is OK.
I can't say for sure what was causing my issue. I had been using cyanogen's ROM for quite some time so I don't have a reason to think it was the ROM unless it was one of the current updates.
Perhaps I just had a collection of issues that came to a head and it was time to clean the phone and start over.
Same Problem
Hi, First post here. Great site by the way.
I am having the same problem as you are. Cyanogen, manup's 2.1 (1.5) and the "official tmobile 1.6" rom would frequently reboot or shut off on me. I tried three different sd cards and completely wiped my phone everytime i went between these roms. After much frustration I unrooted my phone last week and went to stock 1.6. It was working perfectly fine but the terrible battery life convinced me to try rooting my g1 again. After going through all the steps the same symptoms came back. So in order to be able to use my phone I went back to the stock unrooted rom. I also would like to mention that before these symptoms came up I had my phone rooted since may 2009. I also tried various SPL's and recoverys while trying to resolve my problem. Thanks
Random reboots are the reason why I don't run CM roms for any length of time anymore. I do load them from time to time to check it out and what not, but more often than not, I always find myself back on a Dwang rom.
My new G1 should be arriving tomorrow, but it has been 2-3 days now with the original battery. No shut downs. While it will be nice to have a new phone (although my phone is unblemished) it will suck to have to re-root it. I am pretty certain its the battery.
I will recheck when I get my new phone set up, I will put the extended battery back in it. I am still pretty certain it is the battery though.
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.
Hey everyone I'm new to this forum. After I updated my bionic to ICS last week I have had nothing but problems. The phone constantly reboots itself. It might stay on for 5 seconds or 3 hours. I was wondering if there is anyway to go back to Gingerbread or a way to install a rom that will work. Any help would be greatly appreciated.
There's no going back to GB. Have you done a Factory Reset since getting ICS? If not, do that first thing.
Sir_Eagle said:
There's no going back to GB. Have you done a Factory Reset since getting ICS? If not, do that first thing.
Click to expand...
Click to collapse
I have reset it 3 times. Still reboots all the time. I tried taking out the microSD card doesn't help either.
I worked in an environment with nearly 20 Bionics, and I've seen it twice. Believe it or not, it was the battery. No idea why, but in both cases I replaced the batteries and the issue was completely resolved. The issue only came up after the ICS update. And, in both cases they were extended batteries, tho I'm not sure if that matters.
stevendbrady said:
I worked in an environment with nearly 20 Bionics, and I've seen it twice. Believe it or not, it was the battery. No idea why, but in both cases I replaced the batteries and the issue was completely resolved. The issue only came up after the ICS update. And, in both cases they were extended batteries, tho I'm not sure if that matters.
Click to expand...
Click to collapse
I should be getting a new battery in the mail tomorrow. I will let you know what happens. Thanks for the help.
Ha, it's been a month, but did it work? Or did you get it working otherwise?
I experience the same issue.
I RSD Lite and FZX my phone back to stock and it seems to work for another 5 days or so. I've tried to nandroid a backup when it's good then restore it when it goes nutty but that doesn't help. I've flashed the FZX image, then used Safestrap to flash a CM-based ROM in Slot1, but when the stock goes TU, so does the other.... and vice versa.
I haven't tried batteries.
I just got this phone in the mail yesterday off of e**y and it has been rebooting all the time too. Not consistently though but enough to make it aggravating. I just got it rooted and somehow was able to get safestrap3 on it. Went into the twrp recovery and wiped cache and dalvik and rebooted from there. So far ok but it has only been about 10 minutes since I did that. I have already done 3 factory resets and even wiped cache in stock recovery. I used my X2 to record the craziness of this phone doing it's own thing but with the guy above talking about the battery maybe being faulty I might have to try that because the phone has at 0% when I got it and I don't know how long it was dead for. Does not being charged for a long time ruin a battery?
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!
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.