As we know, the Nook Color's SD slot will always take first boot priority. I'm in a situation where even booting via SD through known methods are not working.
The purpose of this thread is to:
1) Share with others who are in this similar situation, on methods which may result in the recovery of their own devices
2) Keep this discussion healthy so one day, I will be able to restore my own bricked device which I'm still striving hard to.
Click to expand...
Click to collapse
IMPORTANT: If you have a bricked device I need to emphasize on searching and reading very carefully what others have shared here in both General and in Development. This is a fundamental requirement, as with the ability to follow instructions and not panic by creating unnecessary threads. This will only make things harder to find, so thank you in advance for not doing that.
There are many useful guides out there, some of which the most helpful are:
Nook Color Restore to stock by samuelhalff
Dummies Guide to Fixing 'My Nook Won't Boot' by RileyGrant
Stock 1.1.0 Clockwork Recovery Image by brianf21
Nook 1.01 stock dd images by shad0wf0x
[RECOVERY] Monster RootPack 0.7 / Clockwork Recovery 3.0.0.5 SD by thecubed
Click to expand...
Click to collapse
Anyway, in severe bricking cases where hardware is not at fault, many of the solutions to restore the NC begins with either:
1) Booting to CWR-SD via uSD
2) Booting to a rom i.e. Nookie Froyo via uSD
3) Having ADB access, if available
Till date I am not sure why the SD-loaded programs do not work for me, and here are the symptoms:
1) Without SD inserted, the standard BN splash appears, 'Welcome to the Future of Reading', then gets stuck there till powered down. Needless to say, the 8-times reset method doesn't work.
2) With SD inserted, the 'LOADING' screen will splash, then screen blacks out with device still powered on . You will know that the device is still running as you need to hold power down for around 20 secs before you're able to power it back up again. I call this the 'Black Screen of Death'.
Click to expand...
Click to collapse
To get your device up and running, try the following:
0) Do not panic. As long there's no hardware failure there will always be a solution. Look at me, thing's still a damn brick and yet here I am, still hopeful
1) Perform a search, read the useful threads created by the above members first. This thread is related only to failed SD-booting.
Once you've done that, prepare your recovery options with these in mind. The elimination process is part and parcel of problem-solving. In no particular order:
2) Sometimes, try powering on your device by connecting the USB cable from your PC or A/C source, instead of using the Power button.
3) Use only the original USB cable that came with your device.
4) Use the back USB ports of your PC, instead of the fronts as they may provide more consistent power and connection to your device. Try to avoid using USB hubs as they may not distribute the required power equally/properly.
5) Try switching to different USB ports, some may be hardware-gimped due to wear-and-tear.
6) Try to attempt the recovery on another Win, Mac or Linux computer. At least eliminate further possibilities of environmental hardware error.
7) Try charging the battery full.
8) Or, try discharging the battery completely, by leaving the device in BSOD state overnight until you get a message saying your device can't boot due to insufficient power when switched on. Once you are in this state, keep booting the device up until the screen does not appear. Then, recharge it back to full to see if the OS returns to stock (I am sceptical of this, but this was what others advised).
9) Try different SD cards. The device could be picky. Variety should be by class-type, brand, SDHC or non-SDHC. It's been discussed that faster cards perform better, as with more reknowned brands. Also, 16GB cards reportedly do not run Froyo (do read more by searching).
10) When loading anything via SD (CWR, roms), try different button combinations i.e. power + n + up, power + n, etc.
11) And/or, hold power for various timed-presses i.e. >30 / 45 / 60 seconds. Some members report CWR booting up after these periods, or even longer.
Note: funnily I tried holding power + n + up for > 60 seconds and the 'LOADING' screen just stays frozen. Still doesn't work, and I didn't get any ADB access.
12) Try formatting the card completely with native Win/Linux tools, EASEUS Partition Master or SDFormatter before each burn.
13) Try using both Win32DiskImager and WinImage, or dd-ing in Linux (search for more instructions). If you have Linux, you can check to see if the SD's /boot partition is indeed bootable or not.
14) For ADB access, try to unregister your hardware (go to Start > Run > devmgmt.msc), then unplug-replug device to have your PC detect it again. If a device with VID of 2080 shows up, that's the NC. You should know what this means, by now. If not, read more here.
15) Try different SD card readers, especially when experiencing failure on multiple computers. As opposed to multi-adapters i.e. 6-in-1s, try dedicated microSD readers like this one. Do not use those microSD-to-normalSD converters (usually packed together in the same shipping plastic as your card) just because you only have a reader that reads regular SD cards, they tend to fail a lot.
16) At your own risk, try cleaning the contact points on your SD cards (if you must, use cleaning alcohol and a cottom swap/q-tip - do not use water), to free them of dirt and invisible grime. If you have multiple SDs, try cleaning the least expensive ones first. Don't forget to leave them to dry completely before insertion into the NC. Credit to bonobomidwest, read his experience here.
Click to expand...
Click to collapse
17) Use Nooter 0.2 (recommendation from thecubed):
Here's my recommendation: use the stock charger cable (the one with the light-up N in it) when you try Nooter 0.2.
If the light goes from orange to green (or something like that) that means Nooter is booted and working.
My new thought: some file in /rom is missing, which controls the backlight and lcd controller. I can't prove this, but it seems logical haha.
All you need to do is get Nooter 0.2 booted and ssh'd in and you'll be able to dd over a complete 1.0.1 backup.
rawfish: I use Ubuntu, so sorry if I'm not able to provide instructions for Windows
Type:
Code:
sudo ifconfig usb0 192.168.2.1
Then:
Code:
ssh [email protected]
And you should be able to follow the directions for restoring on the wiki... either that or check around on IRC, if you tell them that you've got ssh access and you just need to restore your device, they'll help you out if I'm not around..
rawfish: I typed 'dmesg' in shell to see if the NC connected as a usb-ethernet device, and it doesn't show. If it does for you, then you should have progress and should ask around in IRC.
Click to expand...
Click to collapse
All these did not work for me, but hope this is useful to some. I've read testimonies from everyone that this is an unbrickable device, and I certainly hope it's true, and for a kind soul to help suggest more solutions. As I'm overseas, do you think I should call BN up to see if I can arrange to send my device back for fixing/replacement? It's been a month since purchase, and 3 weeks of failed restore attempts.
Disclaimer: I am not responsible if any of these methods get you in deeper trouble. Attempt at your own risk. Credit goes to thecube aka IOMonster, and the #nookcolor channel on irc.freenode.net. Thank you to everyone who created the recovery guides too.
This space reserved.
You sure you just don't have crap or badly burned SD cards? Sounds pretty much what happens if you boot s really slow/junk SD or burn it badly.
khaytsus said:
You sure you just don't have crap or badly burned SD cards? Sounds pretty much what happens if you boot s really slow/junk SD or burn it badly.
Click to expand...
Click to collapse
I tried on 6 different SD cards:
1. Transcend 8GB Class 6
2. Transcend 4GB Class 2
3. Wintec 16GB Class 10
4. Sandisk 4GB Class 4
5. Sandisk 2GB non-SDHC
6. Sandisk 256MB
I've burned stuffs like Autonooter and Honeycomb on these before, and they worked fine.
rawfish said:
I tried on 6 different SD cards:
1. Transcend 8GB Class 6
2. Transcend 4GB Class 2
3. Wintec 16GB Class 10
4. Sandisk 4GB Class 4
5. Sandisk 2GB non-SDHC
6. Sandisk 256MB
I've burned stuffs like Autonooter and Honeycomb on these before, and they worked fine.
Click to expand...
Click to collapse
First of all - great job in pulling all the resources into one place (it's small consolation, but i think you've just helped a whole load of people )
Second, i apologise if I'm telling you stuff that's obvious, but in helping out on these forums often it's the LOGIC of troubleshooting rather than the particulars of the problem that are important... In other words, only vary one thing at a time, and ALWAYS swap out every piece of hardware involved at each stage... if you always rely on one piece of hardware this might be the weak link... so have you tried a different SD drive or adapter? and have you tried burning from a different computer?
Now, I'm not being insulting, because I had a virtually identical problem with my first froyo - it just wouldn't boot (as you describe) despite multiple burns, different cards, all of the standard formatting tricks etc. It wouldn't work in multiple computers - the common element being the SD/microSD adapter. It never occurred to me that such an electrically simple part could be at fault, but you bet it was - in fact i would say in my experience these things consistently fail! (I spent a day kickign myself, because we know ho unreliable they are from using them in other devices). They also all look alike so it's hard to keep track of which one you are dealing with They also fail unexpectedly, so if you used an adapter before there's no guarantee it's working now...
Sooo... Have you tried a dedicated microSD reader (rather than a simple adapter)? I now carry one with me everywhere (it doubles as the world's smallest thumb drive too)
http://www.amazon.com/gp/product/B002HGFKR8
Also bear in mind that froyo appears not to work on 16gb cards (i see you tried one)
Also, from my experience with other devices these cards are very sensitive to dirt and oil on the contacts. Certainly with enough frustrated handling you can get enough finger-grease on them to have them fail. Also they seem to be much less tolerant when writing than reading. I have NO idea how you would go about cleaning out the slot in the NC (and as someone who has ruined at least one DVD drive by blowing canned air where you shouldn't I'm not going to advocate for that). I have resurrected 'dead' SD cards before by cleaning the contacts with rubbing alcohol and a q-tip (on the card's contacts) - but again do so with great care (at your own risk!!!) and with your cheapest card, and make sure it si completely dry before you put it in the NC.
I have been generally a little scared that all this plugging and unplugging of the microSD might hurt the NC, so i have done everything i can to avoid that...
I am sure you can find someone local to you willing to help fix your boot issue but I assure you, its damn near impossible to brick a nook without physical damage.
@bonobomidwest:
No offence taken at all, in fact I am very appreciative of your contribution. I forgot to add the fact that I tried on 2 different card readers, plus indeed tried to clean the slot via an air duster VERY GENTLY as a last effort resort (I would not recommend this, it may cause permanent hardware damage). Once I'm free I'll go get a new SD reader (reads uSD only) and a new uSD which I haven't tried before. I'll try cleaning the contact points too.
*Thanks - I've added more checklists to the OP
@combustiblemonkey:
Thanks for the assurance.
I convinced my friend to buy a nook, rooted it for him, and was bricked within 2 days. Here is how I fixed it
EDIT: I tried to post a link, but was unable. If you go to theunlockr(dot)com and search for how to restore nook color to stock, there is a detailed article.
This took me almost 2 days of reboots, black screens, and freezing. I would get into CWR, and it would freeze. Had to reboot, got the black screen of death. Literally, a couple hundred reboots before it said that the OS has successfully installed, and of course, it froze again. Many more reboots, and it was finally at stock. I figure getting it back to stock was enough to return it.
Dr-Rockso said:
I convinced my friend to buy a nook, rooted it for him, and was bricked within 2 days. Here is how I fixed it
EDIT: I tried to post a link, but was unable. If you go to theunlockr(dot)com and search for how to restore nook color to stock, there is a detailed article.
This took me almost 2 days of reboots, black screens, and freezing. I would get into CWR, and it would freeze. Had to reboot, got the black screen of death. Literally, a couple hundred reboots before it said that the OS has successfully installed, and of course, it froze again. Many more reboots, and it was finally at stock. I figure getting it back to stock was enough to return it.
Click to expand...
Click to collapse
Thanks, this is the direct link:
http://theunlockr.com/2011/02/14/how-to-restore-the-nook-color-to-stock
All instructions were taken from XDA, plus no guarantee it's the most updated
Moving on, great to hear you've gotten it back to stock. Man, you've got GREAT patience, a couple hundred reboots?
1) Was the SD inserted in or not? Curious about the OS successfully installed message, which is the result of 8x unsuccessful reboots without SD inserted.
2) Could you also provide a more detailed account on what you did? Looking forward to hear - thanks.
Hi rawfish
I also have this issue and have been trying many things. My nook did boot nooter 0.2 (the light went green) but I couldn't get Win 7 or Ubuntu to connect to it. My screen never changes at all, no backlight even. Seems this may be a larger issue than most believe it to be, especially for people like us who don't live in the US.
chrysilis said:
Hi rawfish
I also have this issue and have been trying many things. My nook did boot nooter 0.2 (the light went green) but I couldn't get Win 7 or Ubuntu to connect to it. My screen never changes at all, no backlight even. Seems this may be a larger issue than most believe it to be, especially for people like us who don't live in the US.
Click to expand...
Click to collapse
If you can find a friend or person in your area having the same device, you can try to see if an SD you burned work on theirs. If it works on theirs, it's possible that your SD slot is defective - but then comes the question of it being in working condition before the bricking happened, right?
I still think mine's recoverable, as with yours. Could be a bad SD or reader, or bad contacts. I'm going to try out using another reader plus purchase an el-cheapo branded SD. I'm also going to try formatting it via another PC in a linux environment and messing around with the partitions.
I understand the trouble you may have taken to get the device - and this happens. All the best mate, and do cheer up, don't give up.
rawfish said:
Thanks, this is the direct link:
All instructions were taken from XDA, plus no guarantee it's the most updated
Moving on, great to hear you've gotten it back to stock. Man, you've got GREAT patience, a couple hundred reboots?
1) Was the SD inserted in or not? Curious about the OS successfully installed message, which is the result of 8x unsuccessful reboots without SD inserted.
2) Could you also provide a more detailed account on what you did? Looking forward to hear - thanks.
Click to expand...
Click to collapse
When I finally got it to work, the SD card was installed with the 1.0.1 stock OS on it, and CWR. The problem was that that (+) and (-) would only occasionally work. And if they did, it would usually freeze. I would be able to format system, but it would freeze if I tried to format data. Powered off, and I would get the black screen of death (BSoD). Once this happened, I would plug it into my computer so that I could hear the chime indicating a new device was plugged in. I found that ejecting the SD and then rebooting would sometimes help get rid of the BSoD. Then another power down, plug in the SD, and start again. Also, holding the N, +, and Power would sometimes help in launching CWR. I would usually have to hold for 60 seconds, but it would finally launch. It seemed like the nook was trying to run a process that slowing it down and causing it to freeze, but I couldn't figure out what it was. If I would wait an hour, it would boot CWR and allow me to format system and data, but then it would freeze when I would try to install the zip.
The successful install message was in CWR. It said Install From SD Card Complete, or something like that. After that, I still had to do the 8 reboots. It would load up the stock welcome screen and freeze. 8 reboots later, I got the video lady. Good enough to return it to the store.
It really was just persistence. It would usually take an hour of reboots before I was able to try to install the zip, and it probably failed on me 15+ times. The status bar would get half way, and freeze. Then I had to begin again. If it had been my nook instead of my friends, I probably would have given up. I wish I could be more specific, but unfortunately I am new to all of this. My nook rooted just fine, and fixing his is really my only experience with CWR. I just kept going until it worked.
Good luck! It is a pain in the ass, but it can happen.
rawfish said:
If you can find a friend or person in your area having the same device, you can try to see if an SD you burned work on theirs. If it works on theirs, it's possible that your SD slot is defective - but then comes the question of it being in working condition before the bricking happened, right?
I still think mine's recoverable, as with yours. Could be a bad SD or reader, or bad contacts. I'm going to try out using another reader plus purchase an el-cheapo branded SD. I'm also going to try formatting it via another PC in a linux environment and messing around with the partitions.
I understand the trouble you may have taken to get the device - and this happens. All the best mate, and do cheer up, don't give up.
Click to expand...
Click to collapse
My wife has one as well so am able to test using that and the SD works fine in hers. The whole screen not turning on thing is weird though, does your screen turn on?
We bought them when on honeymoon in America so didn't have to pay a shipper or anything
Deleting the partitions manually with Gparted and using dd to burn the SDs and making sure the correct partitions are bootable doesn't seem to work. Last night I retried a lot of the previously attempted options, with no results.
It's weird to think that a working SD slot and a slew of cards will suddenly malfunction, but for now that seems like the most plausible reason why my NC can't boot anything off SD.
To think back how it all started, the device suddenly rebooted from HC preview v0.4 to stock BN 1.01 (rooted + installed CWR on eMMC) while the SD is inserted, then upon another reboot it simply stays dead, this gives me reason to believe that the internal boot partition is corrupted, and SD slot nuked hardware-wise.
Hmmm, really hoping to find someone else who has the same device, in my area.
Right now I am at the Black Screen of Death as well...
I think Barnes should refund me, but I am willing to do some tests for the good of society.
Steelfan555 said:
Right now I am at the Black Screen of Death as well...
I think Barnes should refund me, but I am willing to do some tests for the good of society.
Click to expand...
Click to collapse
Sorry to hear that, and don't give up! Hope you took a look at the other threads, and this little pseudo checklist I made in the OP. Do share the outcome
Thank you Rawfish. The first option, the Dummies Guide to Fixing 'My Nook won't boot'
was what I needed to get started on the right track again. Though I'm not sure anyone wants to know how I ended up here, I'm grateful to those that put in the time and effort to find any of these solutions.
Thank you!
FroztIkon said:
Thank you Rawfish. The first option, the Dummies Guide to Fixing 'My Nook won't boot'
was what I needed to get started on the right track again. Though I'm not sure anyone wants to know how I ended up here, I'm grateful to those that put in the time and effort to find any of these solutions.
Thank you!
Click to expand...
Click to collapse
Update:
Ok, so after running through it, I ended up getting stuck on the boot screen that shows N. If I powered off, it would restart and get stuck at that screen. I tried the 8 shutdowns (it installed new software), but afterwards, it was still stuck. So, I tried another method I found on the forums. I powered off holding the N button and power, which caused it to boot back up and do a factory reset. I now have a factory fresh Nook.
Okay, it's been a while since I kept this thread updated - I contacted BN and had the device sent back, apparently the SD slot failed so they sent me a new one. I'm just wondering if it's sheer concidence that it happened, as I was tinkering with Nookie Honey preview v0.4, when the hardware suddenly failed.
Oh well, I guess the NC still remains as a 99.99% unbrickable device - with the 0.01% being related to the ambiguous root cause to my case.
I now have 2 NCs (one from the RMA process, another one from the $199 eBay deal.
A couple of days ago my dad got my sister and me nook colors. I installed honeycomb which ran off the sd card on both and rooted both. I was tired of not having YouTube flash and many other apps so I tried out froyo and cm7. After about 50 unsuccessful installs I have decided I must have a hardware problem because they will run on my sisters nook.
The problem is that after the install, it boots off the sd card and loads android completely but when it asks to complete with setup wizard or
Default action it freezes up for a second and shuts off. After I boot again it just says "Powering Down."
I don't know if I should try a native install or go return this one. I already restored it completely to factory conditions so they won't be able to tell. I have searched everywhere and cannot find this anywhere else (problem or solution).
I just find it so strange how it works on the other nook color but not mine. Even setting it up on hers and moving it to mine produces the same issue. I probably will return it unless someone can help me but I'm more curious to what the problem is than how to fix it, since I can simply go get a new one.
Any help is appreciated!
****bump****
Thats certainly a new one. I only have one nook so ive never tried them side by side. Ive never been able too successfully boot off an sd card and have it stable. I eventually just decided to go to cm7 internal and never looked back. I wonder if theres something different in the nook in how it reads from the sd card.
are you overclocking the image? or running it stock?
you said you set it up on your sisters nook then move it to yours and you have problems. did you try taking her good, working build and moving that sd card to your nook and seeing if the problems go away. Ive read alot about sd cards and different quality's of cards. maybe theres something up with the sd card you have.
I have problems no matter what. If i put it on hers to setup, it still has the problem. If i set it up on mine, still has the problem. I just tried phiremod v6.1 and it also had the problem (i expected this because it is still cm7). I probably will return it but i wish they would just update these things to android 2.2/2.3 and maybe even full honeycomb when it comes out and save all of us from these issues.
The image is the normal one. I have tried installing directly to the sd, using the "SD CARD TEMPLATE" files that you install and then boot from to install cm7, etc.
They all work on the other nook but mine is being stubborn for some reason.
I am at the airport getting ready to fly home and i might try installing it internally tomorrow. I just don't want to have this problem again and have to spend a bunch of time reinstalling the stock rom to return it.
I completely understand your frustration, especially since you have 2 and are not seeing the same thing on both. Are you experiencing any other problems with the device. based on what your telling me i would have to assume there is something wrong with the sd card slot.
but if you forget about your sisters nook for a min, what you are describing is exactly what i experienced on my nook. that's why i went for internal. I started with the dual boot, but found that i stopped using the stock rom pretty quickly, and with the slow ports of cm7 to dual boot, i just scrapped dual booting all together, and now im full cm7 and its great.
john10101 said:
I completely understand your frustration, especially since you have 2 and are not seeing the same thing on both. Are you experiencing any other problems with the device. based on what your telling me i would have to assume there is something wrong with the sd card slot.
but if you forget about your sisters nook for a min, what you are describing is exactly what i experienced on my nook. that's why i went for internal. I started with the dual boot, but found that i stopped using the stock rom pretty quickly, and with the slow ports of cm7 to dual boot, i just scrapped dual booting all together, and now im full cm7 and its great.
Click to expand...
Click to collapse
I tried the internal install, but it is doing the same thing. I am recovering the stock image right now. Thanks for the help, but I am just going to take it back and get a new one and not root it or anything and just install it to the sd card.
I have the same problem too.
Holler y'all, I'm hoping you might be able to lend me a hand with these here droid troubles, you see I was fiddling with my Streak and I seem to have broken something kinda important. My droid now tells me my internal storage has a total space of 0.00B on which 2.15GB of applications are installed, contradiction I know. What's kinda weirdypants is that I seem to be able to install new apps fine, but when I try to use the camera I get the "Please insert an SD card before using the camera" nonsense. I should probably note that I also have an external SD plopped into the slot. So there's actually two SD cards, why the camera doesn't see either I ain't got a scoob.
So how did I get here? Well... I had been using that CM10.1 rom, which was quite shexy and all, but the lack of camera and the constant crashing that required a reset made it too unreliable for my use. I decided to downgrade back to Honeycomb and everything seemed to point towards StreakDroid-HD7-R8, but things went a little sideways and I ended up in a boot loop. Perhaps I shouldn't be fiddling with things when I'm so shleepy. Anyways I got my paws on a stock rom and managed to install it with fastboot and recovery. Everything looked fine and I went ahead with setting it up and installing apps, until I got errors about the SD not having enough space to install some apps when it really should've had plenty. I rooted it, tried clearing caches, formatted it, but there was no change except for me having to install all my apps again. Oh yeah, I couldn't backup in Titanium either. So here I am.
Perhaps the SD is dying, perhaps I corrupted it with my fiddling, maybe it's something to do with the partitioning, maybe it's something else? If anyone has any ideas or suggestions, please share.
Also, if the SD is to be retired, is there anyway of redirecting apps which would normally use the internal SD use the external instead, for example the camera app?
Thanks in advance.
That is becuase CM10.1 changes the partition tables.
Does not anyone read around here? There is like 10 people who have posted the exact same thing.
You need to restore to Android 2.2 and then upgrade from there.
giveen said:
That is becuase CM10.1 changes the partition tables.
Does not anyone read around here? There is like 10 people who have posted the exact same thing.
You need to restore to Android 2.2 and then upgrade from there.
Click to expand...
Click to collapse
Offt, that was a tad fiesty. My apologies hombre, I do read and I've ready plenty on this forum, but I guess I haven't read the right threads, perhaps I didn't know the right combination of words to search for. Slap me with a wet fish and shower me in stale coco pops - I am a daftie! You're a mighty fellow, so I shant be cheeky, you've spent a great deal of time making the streak more awesome for all of us, which I do appreciate greatly. Thank you.
Now when you say restore to Android 2.2, are we talking stock ROM here? And do I have to do anything special beforehand or is it just a case of plopping the ROM on my SD and restoring? Thanks kindly for your help captain.
You need to grab the NVFlash pack to restore to Android 2.2, which will also restore the Dell crappy partition tables.
Look at TheManii's DevHost page, he should have it.
Partition tables had to be changed as Dell did not correctly do Android, resulting in the sdcard daemon being broken, so they created something called like "oem_sdcard". If they had just done it right the first time, we would be in this predicament.
Oh and anytime you need to be slapped by fishes, I'm more than glad to. If you had merely scanned the General section, before you posted, you would have seen at least, three threads, where people were having the same problem, and where each time I already stated the exact same thing that you needed to do.
I'll take the slap. I think I spent most of my time in the Dev section, yet I post here in General, you see, that is why I am daftie! My internal compass is corrupted.
Many thanks for the help and info, perhaps someone should slap Dell with a fish? Anyways I best go correct my wrongs now.
I have read many threads and I have the same problem. However, I already used nvflash to repartition my Dell and revert back to 2.2.2. I then updated back to Honeycomb 3.2 and I still have this issue. I ran it a couple times... repartition and restore back to 2.2.2 but still no luck. Any thoughts? Sorry to respond to such an old thread, just fishing for any ideas.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
xcover2 Same issue
I am facing same issue with my xcover2 , any solutions ?
I recently switched over from CM10.1 to LN14.1 and have been getting misreported battery (it worked fine previously) Specifically, it will drop 15-20% every 10 minutes or so, and stay at 1% for several hours (I've recorded up to ten hours).
What I've tried to fix the issue:
Draining to 0% and recharging to 100% (i.e. manual calibration listed on XDA) on LN14 builds
Battery Calibration Apps recommended on XDA
Flashing down to stock ROM, factory resetting, and re-flashing 14.1 (I read this could restore a battery file that has been affected by repeated flashing of ROMs.)
Flashing back down to CM10.1 and CM10.2 (also tried CM11 and CM12 builds) that I used previously
Wiping DALVIK/Cache between each install
Battery Monitoring Apps (Rooted)
Battery saving/hibernation apps
Adjusting nearly every power consumption option (screen brightness, WiFi, etc.)
The behavior has been the same switching between any ROM of CM, LN, Stock/Factory Reset from the point that I first upgraded from CM10 to LN14.
I don't think it's a lack a capacity and it has to do with misreporting.
I haven't tried recalibrating/draining on CM10 or stock, but I don't know if that would be pointless since I've attempted it three times on LN14 with no success. Also, I don't know if the process causes battery issues long-term. Right now, I'm looking to see if TWRP reports the same battery level as LN14. Last night, I was at 1% for 10 hours or so, including ~3 hours of video trying to discharge.
Anyone have any tips on where to look next? Is this just an issue with LN on HD+ in general? Thanks in advance for any help.
Probably one of your sources of information is this post: https://forum.xda-developers.com/nook-hd/help/nook-hd-battery-issue-custom-rom-fixes-t3389721
We suffered through this issue with an HD for quite awhile and tried all the stuff you mention. It may be that the return to stock/factory reset actually worked but it may also be that we discovered that somehow the SD card we were using for flashing (and which we had remade at some point) had not been properly configured as 0x0c and was instead 0x0b. This eventually led to a tablet that would only boot when plugged in and allowed to sit for a minute before being unplugged. We never got to the battery misbehaving issue at that point because of the panic that ensued over what the %#W% was going on!
Anyway.....once the card was made properly, we started from stock/factory reset (including actually re-registering the tablet with B&N, etc.) and then flashed the CM ROMs. Everything is now fine.
Whew.
nmyshkin said:
Probably one of your sources of information is this post: https://forum.xda-developers.com/nook-hd/help/nook-hd-battery-issue-custom-rom-fixes-t3389721
We suffered through this issue with an HD for quite awhile and tried all the stuff you mention. It may be that the return to stock/factory reset actually worked but it may also be that we discovered that somehow the SD card we were using for flashing (and which we had remade at some point) had not been properly configured as 0x0c and was instead 0x0b. This eventually led to a tablet that would only boot when plugged in and allowed to sit for a minute before being unplugged. We never got to the battery misbehaving issue at that point because of the panic that ensued over what the %#W% was going on!
Anyway.....once the card was made properly, we started from stock/factory reset (including actually re-registering the tablet with B&N, etc.) and then flashed the CM ROMs. Everything is now fine.
Whew.
Click to expand...
Click to collapse
I checked my SD card and the Partition ID is 0x0b. However, my tablet doesn't have the behavior you described regarding the need to be plugged in to boot.
Are you indicating that it would be worth flashing back down to 2.1.0 Stock ROM/Factory Reset with a 0x0c card, and Registering to attempt to resolve the issue? Would I be required to remain on stock for a period of time or can I re-flash to LN immediately? Thanks in advance for you help, the Partition ID type is news to me.
theleagueofstream said:
I checked my SD card and the Partition ID is 0x0b. However, my tablet doesn't have the behavior you described regarding the need to be plugged in to boot.
Are you indicating that it would be worth flashing back down to 2.1.0 Stock ROM/Factory Reset with a 0x0c card, and Registering to attempt to resolve the issue? Would I be required to remain on stock for a period of time or can I re-flash to LN immediately? Thanks in advance for you help, the Partition ID type is news to me.
Click to expand...
Click to collapse
I'm no expert so my information is anecdotal. I'd never seen the weird behavior like on the HD tablet in all my work with an old Nook Tablet. And I can't pinpoint the battery reporting issue vs. the improper remake of the card. All I know is that at some point I thought there must be something wrong somewhere and decided to make a completely new card. Then the "fun" really began.
The actual correct Partition ID type is 0x0C FAT32 LBA (as shown by Minitool Partition Wizard). This is documented in all (most?) of the instructions for preparing SD cards. I just got sloppy, I guess. It's still difficult to believe that this change made the difference but it did for me, at least in terms of boot. I do think the return to stock is a good idea. It may not be necessary to register (we already had an account from the old days of running stock), but I would do the factory reset and let it sit awhile as the OP suggested (maybe 15 min?). As he said, what's a few minutes if it will save you endless headaches? What do you have to lose?
When I (carefully) prepared my new SD card I used the files provided by @belfastraven, substituting the old version of CWM needed to reflash stock for the one he had. This gave me SD-based TWRP (two different versions) as well as the old CWM. For the life of me I can't relocate that post, but I expect other card recipes will work.
Edit: here we go: https://forum.xda-developers.com/showpost.php?p=66086179&postcount=10
nmyshkin said:
I'm no expert so my information is anecdotal. I'd never seen the weird behavior like on the HD tablet in all my work with an old Nook Tablet. And I can't pinpoint the battery reporting issue vs. the improper remake of the card. All I know is that at some point I thought there must be something wrong somewhere and decided to make a completely new card. Then the "fun" really began.
The actual correct Partition ID type is 0x0C FAT32 LBA (as shown by Minitool Partition Wizard). This is documented in all (most?) of the instructions for preparing SD cards. I just got sloppy, I guess. It's still difficult to believe that this change made the difference but it did for me, at least in terms of boot. I do think the return to stock is a good idea. It may not be necessary to register (we already had an account from the old days of running stock), but I would do the factory reset and let it sit awhile as the OP suggested (maybe 15 min?). As he said, what's a few minutes if it will save you endless headaches? What do you have to lose?
When I (carefully) prepared my new SD card I used the files provided by @belfastraven, substituting the old version of CWM needed to reflash stock for the one he had. This gave me SD-based TWRP (two different versions) as well as the old CWM. For the life of me I can't relocate that post, but I expect other card recipes will work.
Edit: here we go: https://forum.xda-developers.com/showpost.php?p=66086179&postcount=10
Click to expand...
Click to collapse
I just flashed down to stock, factory reset and reinstalled 14.1 I set the SD to 0x0C FAT32 LBA. I didn't wait 15 minutes after installing the stock though, just a few minutes (I missed this step and hopefully it doesn't make all the difference.) I'll report the results on usage.
I flashed down to stock with NookHDplus-bootable-CWM-6028-for-stock-BOOTFILES-r4-(05.15.13) posted in a CM10 thread though.
The early indication is that the issue is still the same. I think I'm fighting a losing battle and I'll have to look into replacing the battery or making a regular habit of keeping the tablet plugged in.
theleagueofstream said:
to open the device and/or replace the battery, but it doesn't seem like the device is made for it.
Click to expand...
Click to collapse
Like most Android devices, not it's not made to be opened up.
But it's doable with care. If you search you can find instructions and videos.
But, 1, I'm non convinced it's a bad battery. You get too much runtime at 1%
And 2, not sure of any good options for replacement batteries. That's why my wife's HD+ doesn't gave a new battery.
ST Dog said:
Like most Android devices, not it's not made to be opened up.
But it's doable with care. If you search you can find instructions and videos.
But, 1, I'm non convinced it's a bad battery. You get too much runtime at 1%
And 2, not sure of any good options for replacement batteries. That's why my wife's HD+ doesn't gave a new battery.
Click to expand...
Click to collapse
I'm considering opening it just for the sake of seeing if there's a bad connection, but I've seen people damaging the case, etc. I agree with your sentiment that the capacity doesn't indicate it's a bad battery. Regardless, I'm grateful for everyone's help here so far.
theleagueofstream said:
but I've seen people damaging the case, etc.
Click to expand...
Click to collapse
Some people just shouldn't work on finiky stuff. I;ve seen people screw up lots of things because they rushed.
Phones and tablets just require time and patience.
ST Dog said:
Some people just shouldn't work on finiky stuff. I;ve seen people screw up lots of things because they rushed.
Phones and tablets just require time and patience.
Click to expand...
Click to collapse
I'm assuming you've opened a few, so do you recommend a special set of tools? Or is a guitar pick and appropriate screwdriver enough?
theleagueofstream said:
I'm assuming you've opened a few, so do you recommend a special set of tools? Or is a guitar pick and appropriate screwdriver enough?
Click to expand...
Click to collapse
Not sure on these.
I've got a few plastic spludgers that have been handy with other devices.
This one makes it look easy, but the tape on the bezel is missing.
https://youtu.be/1muVOrhORq8
Also they don't even tape the replacement battery to the back so it might shift around in the case.
This is more like what you'll encounter.
https://youtu.be/HpVrds3g-M8
Note all the double sided tape. You'll want to preserve it replace it.
ST Dog said:
Not sure on these.
I've got a few plastic spludgers that have been handy with other devices.
This one makes it look easy, but the tape on the bezel is missing.
https://youtu.be/1muVOrhORq8
Also they don't even tape the replacement battery to the back so it might shift around in the case.
This is more like what you'll encounter.
https://youtu.be/HpVrds3g-M8
Note all the double sided tape. You'll want to preserve it replace it.
Click to expand...
Click to collapse
Do you have any suggestions for a replacement brand?
I found:
https://www.amazon.com/TLP-040-Li-P...d=1510605819&sr=1-4&keywords=nook+hd++battery
but I thought someone with better experience could make a suggestion.
theleagueofstream said:
Do you have any suggestions for a replacement brand?
Click to expand...
Click to collapse
As I said earlier, no. I'm not confident any of them are any good.
Someone posted a link to the one they got in the other thread.