Related
I was just wondering, for those of you people that had the I9000M Internal SD fail can you answer the following (approximately):
how many apps did you have installed?
how much of the internal SD was used?
I'm just trying to figure out why they're dying. I have one myself and I'm not exactly using it to its full capacity. I was wondering if people that used their Internal SD more heavily were the ones that were have problems.
nemethb said:
I was just wondering, for those of you people that had the I9000M Internal SD fail can you answer the following (approximately):
how many apps did you have installed?
how much of the internal SD was used?
I'm just trying to figure out why they're dying. I have one myself and I'm not exactly using it to its full capacity. I was wondering if people that used their Internal SD more heavily were the ones that were have problems.
Click to expand...
Click to collapse
I was using about 4.5 GB on mine with about 110+ apps. I don't think it has anything to do with the amount being used though. More with the flashing of a Froyo firmware, specifically, doing a factory wipe in Recovery Mode of a Froyo ROM. I was able to flash a Froyo ROM successfully and have it boot up properly once before I decided to do a wipe and pretty much screwed up my internal SD.
dawgpound6985 said:
I was using about 4.5 GB on mine with about 110+ apps. I don't think it has anything to do with the amount being used though. More with the flashing of a Froyo firmware, specifically, doing a factory wipe in Recovery Mode of a Froyo ROM. I was able to flash a Froyo ROM successfully and have it boot up properly once before I decided to do a wipe and pretty much screwed up my internal SD.
Click to expand...
Click to collapse
That's the thing though. One person having an issue doesn't which they think resulted from 'this' may not apply to everyone. This is why I'm trying to take a sample and find out what is the biggest culprit (i.e. lag fix, flashing ROMs, amount of storage, etc.).
i believe this is also the cause of my sdcard corruption. ever since i installed froyo, i lost half the sdcard, and now i can't mount it in recovery.
i can't comment yet
still working
have over 400 apps installed
only around 400 MB free in the internal SD everything else consume by Apps and Maps
i keep changing apps frecuently, and installing updates as they appear on Android Market
I was using about 10GB of my internal SD card when I chose to download a Froyo build (JPK). Soon after installing it, I tried plugging it into my computer via Mass Storage mode, and then couldn't get out of it. Eventually the phone went blank, it vibrated a few times, and the only way to get it to do anything was to pull the battery. Once I did that, the internal SD storage was toast.
I was trying quite a few things to get it to recognize the internal storage, but in the end I ended up bricking the phone even more. Now it will bring up the Galaxy S GT-9000 screen, light up the Back/Menu buttons for a few seconds, and then reboot. Download mode and recovery mode are now gone and the only thing I've had it do is go into Forced Upload mode (which as far as I've searched) is pointless for us now.
I have a feeling it's more related to the lagfixes. I had uninstalled the Voodoo one soon after trying it out, but I guess that wasn't enough.
Devhux said:
I was using about 10GB of my internal SD card when I chose to download a Froyo build (JPK). Soon after installing it, I tried plugging it into my computer via Mass Storage mode, and then couldn't get out of it. Eventually the phone went blank, it vibrated a few times, and the only way to get it to do anything was to pull the battery. Once I did that, the internal SD storage was toast.
I was trying quite a few things to get it to recognize the internal storage, but in the end I ended up bricking the phone even more. Now it will bring up the Galaxy S GT-9000 screen, light up the Back/Menu buttons for a few seconds, and then reboot. Download mode and recovery mode are now gone and the only thing I've had it do is go into Forced Upload mode (which as far as I've searched) is pointless for us now.
I have a feeling it's more related to the lagfixes. I had uninstalled the Voodoo one soon after trying it out, but I guess that wasn't enough.
Click to expand...
Click to collapse
Sorry, but what? Let me get this straight, you tried voodoo lag fix, uninstalled immediately, and yet you still believe it is the lagfix that destroyed the SD card? You think that applying the lagfix mod somehow utterly destroys your SD card even though you've used it for an extremely short amount of time? If that's true then most root users would have bricked their vibrants already.
Seriously, that makes no sense. I stand by my theory that there's a bad batch of SD cards that went into the i9000m production. Bad SD batches happen all the time. Not something uncommon. On top of that, all Voodoo lagfix does is change the file system of the SD card. Would your hard drive die if you formatted it from ntfs to fat32? No. This is not mentioning there are quite a few vibrants that have not used lagfix with dead sd cards.
If it was purely a hardware failure of the flash chips, then it would make sense to have the failures occur randomly. As it is right now, most of the failures seem to happen when people flash the newer Froyo builds (or very soon afterwards).
As far as the lagfix is concerned, I'm by no means implying that this is the only cause of the failures, but if something is going wrong in the conversion of file systems (however minute it may be), it is possible for the file system to become corrupted over time.
I don't think we know for sure whether it's a hardware failure or a software one. This is made even more difficult by the fact that we are generally limited in what recovery options are made available (not like a desktop, where I could boot a Linux distro off a USB stick and directly access the file system to troubleshoot). I do realize some have been able to try and get utilities like GParted to run on the phone's internal memory, but it's still not nearly as convenient as running the same utility on a desktop HDD/SSD.
Feel free to disagree with me, but I know once I get my phone back, I won't be installing a lagfix (or a custom build for that matter).
Hmm.. So i9000m's had a bad batch of memory? interesting. I'll remember that when someone comes asking for problems and see if their device is a i9000m , BTW what is the i9000m ? Captivate?
i9000m = Canada Bell Mobility version of Samsung vibrant
i9000 = international version
nemethb said:
That's the thing though. One person having an issue doesn't which they think resulted from 'this' may not apply to everyone. This is why I'm trying to take a sample and find out what is the biggest culprit (i.e. lag fix, flashing ROMs, amount of storage, etc.).
Click to expand...
Click to collapse
I missed this post completely. People are having some MAJOR confirmation bias for WHY the i9000m dying.
Just because you do something, it doesn't always imply causation. There are plenty of vibrants around with dead SDs without ever installing lagfix or froyo. It's purely coincidence, because the SD was going to fail anyway.
Actually, I don't think there is enough evidence to come to any conclusion regardless.. But there is no evidence proving that the lagfix cannot be part of the problem, or no reliable proof. especially since nobody totally understands how the internal hardware works on this phone though. In fact, the "evidence" that wear leveling happens on the hardware controller is based solely on the sentence "computer SSD's do it that way" (ie, no evidence). And a lot of other evidence related to other problems i'm seeing is also based on assumption.
1) First isolate if the problem is faulty hardware or simply a formatting issue..
2) Work out what ROM's and such people were using
3) Work out if they were using a lagfix.
4) CONFIRM that the internal SD is actually dead. Many people here jump to conclusions too quickly.
5) Also, work out if there is an easy way to get "batch numbers".. Maybe it's isolated to a specific hardware batch.
i was on official jh2 rom from bell w/ voodoo lagfix. Never attempted flashing another rom. I noticed one time it crashed so i pulled the battery for an hour and that had fixed the issue (or so i thought). Was working for about a day and it crashed again. Out of desperation i tried flashing other roms like froyo. So the way i see it, its either general faulty hardware or the lagfix...not flashing froyo builds.
My i9000M had never crashed until soon after installing the JPK firmware, and in my case one crash was enough to "break" the SD Card. Again though, the fact it only crashed when I installed Froyo does not mean this was the cause.
Hopefully we can figure it out, because between the 3-button recovery mode issue and this, I'm considering getting another Android device instead.
I have a bell i9000m and I have not had this issue yet. Just curious for people who have. Did your phones have the three button issue as well?
Sent from my GT-I9000M using XDA App
I started thinking the same thing actually. Mine did have the 3 button recovery issue as well, and of course I had patched it (using the official Samsung Canada JH2 re-release).
MaestroSeven said:
I have a bell i9000m and I have not had this issue yet. Just curious for people who have. Did your phones have the three button issue as well?
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
3 button was working on mine. But I have seen reports on here from people with the same issue where 3 button was not working..
Sent from my GT-I9000M using XDA App
3 button was also working on mine. Like the others, JPK booted correctly but I was getting force errors due to me upgrading from Eclair. Then I decided to wipe/factory reset and it was a no go from then on.
I hope we can figure this out. There has to be a way to get to the internal SDCard and repair it properly.
I have the T-Mobile US Vibrant and I noticed some weird problems with my internal storage too. I have only rooted and lagfixed my phone. I noticed it was taking longer and longer to open photos in my gallery and sometimes they don't open at all. Sometimes the phone will not mount as a storage device on my laptop. In the past 4 days, my phone has crashed hard twice. The first time I had to boot into recovery and wipe personal data and download all my apps and set my email accounts again. This morning my phone lost all the contacts from Facebook, Touchdown (Exchange) and Gmail.
This JUST happened to me like, 5 minutes ago. I browse these forums every day and I had never seen any warnings with regards to Froyo screwing up internal sd cards. It seems many of these cases are Froyo related. Now I probably have to take my phone back.
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.
Hello guys! This is my first post after visiting xda developers everyday for the past two weeks so bare with me...
I recently purchased an HTC HD7 from ebay at a very good price. I thought all was well with the free shipping and all...until the phone started restarting after the first day. So I panicked, searched on google and up pops up xda developers forum! It offered alot of solutions to many problems regarding resetting and restarting.
However after extensive research for the past two weeks, I finally recognized that the problem was the 'internal' SD card. The sellers from HK from whom i bought the phone had voided HTC warranty to insert one of their low class, cheap SDHC cards (which explains the reduction in cost) causing it to fail drastically as a phone. I know this happened because of a shiny warranty sticker with a bunch of chinese symbols on it. Updates won't work, factory reset happens on it's own, restarting even when i simply open up the messaging app and of course the infamous "storage card not working" error.
I've decided I cannot and do not want to send back my phone back in exchange for a new one since i will encounter the same problems. I've decided to have them compensate me for any repairs I have to make. So I read an article on xda dev about upgrading memory to 32GB using SanDisk Class 2 SDHC. Problem is, it is quite out of reach in my country so I would like to know a full list of compatible SDHC cards (not necessarily 32 gb). Also, what other hardware problems might be causing the occurances mentioned? I doubt it's a software problem, but say it is, what might be causing it?
Thank you!
cabe0018 said:
Hello guys! This is my first post after visiting xda developers everyday for the past two weeks so bare with me...
I recently purchased an HTC HD7 from ebay at a very good price. I thought all was well with the free shipping and all...until the phone started restarting after the first day. So I panicked, searched on google and up pops up xda developers forum! It offered alot of solutions to many problems regarding resetting and restarting.
However after extensive research for the past two weeks, I finally recognized that the problem was the 'internal' SD card. The sellers from HK from whom i bought the phone had voided HTC warranty to insert one of their low class, cheap SDHC cards (which explains the reduction in cost) causing it to fail drastically as a phone. I know this happened because of a shiny warranty sticker with a bunch of chinese symbols on it. Updates won't work, factory reset happens on it's own, restarting even when i simply open up the messaging app and of course the infamous "storage card not working" error.
I've decided I cannot and do not want to send back my phone back in exchange for a new one since i will encounter the same problems. I've decided to have them compensate me for any repairs I have to make. So I read an article on xda dev about upgrading memory to 32GB using SanDisk Class 2 SDHC. Problem is, it is quite out of reach in my country so I would like to know a full list of compatible SDHC cards (not necessarily 32 gb). Also, what other hardware problems might be causing the occurances mentioned? I doubt it's a software problem, but say it is, what might be causing it?
Thank you!
Click to expand...
Click to collapse
I think your probably right, more than likely it is due to the cheap SD card!
The good thing is that almost all the newer manufactured SDHC cards will work in the HD7, class 2, through 10.
I would recommend at least the 8gb or the 16gb for storage capacity and a class 4 for read/write speeds.
Stay with a better brand like SanDisk or PNY.
Purchace it from someone that has a decent return policy, just incase you get a dud.
Run the CrystalDiskMark 4000mb test on it and post your results in the "upgrade your HTC HD7 memory to 32gb" thread here:
http://forum.xda-developers.com/showthread.php?t=883582
and they will be able to tell you if its a sufficient SD card for the HD7.
Thank you
xdrc45 said:
I think your probably right, more than likely it is due to the cheap SD card!
The good thing is that almost all the newer manufactured SDHC cards will work in the HD7, class 2, through 10.
I would recommend at least the 8gb or the 16gb for storage capacity and a class 4 for read/write speeds.
Stay with a better brand like SanDisk or PNY.
Purchace it from someone that has a decent return policy, just incase you get a dud.
Run the CrystalDiskMark 4000mb test on it and post your results in the "upgrade your HTC HD7 memory to 32gb" thread here:
http://forum.xda-developers.com/showthread.php?t=883582
and they will be able to tell you if its a sufficient SD card for the HD7.
Click to expand...
Click to collapse
Where can I hit the thank you button? I cannot find it :S Also the phone is deteriorating day by day....Now it is out of battery and when i charge it, it goes into a loop of the HTC splash screen and a windows loading screen. It then freezes and repeats. Is there anything else that might be contributing to this? thanks!
cabe0018 said:
Where can I hit the thank you button? I cannot find it :S Also the phone is deteriorating day by day....Now it is out of battery and when i charge it, it goes into a loop of the HTC splash screen and a windows loading screen. It then freezes and repeats. Is there anything else that might be contributing to this? thanks!
Click to expand...
Click to collapse
It's definitely possible and I wouldn't rule out a software issue, but I think the signs are pointing to a non- compliant SD card
The devices OS is reliant on the SD card to store user data and cache, contacts, SMS, emails and apps, without an SD card inserted or having a faulty SD card would cause these operations to crash and cause system errors when powering on the device, this in turn prevents it from operating and the system from loading and cause file system performance issues, device lockup, reset or boot loop.
Are you sure that they even put an SD card in your device? They or the original owner may have removed the SD card and not installed another one. Either way, I would start with putting a new SD card in your device and go from there!
xdrc45 said:
It's definitely possible and I wouldn't rule out a software issue, but I think the signs are pointing to a non- compliant SD card
The devices OS is reliant on the SD card to store user data and cache, contacts, SMS, emails and apps, without an SD card inserted or having a faulty SD card would cause these operations to crash and cause system errors when powering on the device, this in turn prevents it from operating and the system from loading and cause file system performance issues, device lockup, reset or boot loop.
Are you sure that they even put an SD card in your device? They or the original owner may have removed the SD card and not installed another one. Either way, I would start with putting a new SD card in your device and go from there!
Click to expand...
Click to collapse
Yes I am sure they put in an SD card because i removed the back panel and it is clearly visible. One thing I find annoying is that they removed the protective metallic paper used to protect and hold the SDHC in place. Is there a way to use an alternative to this protective paper? I have also noticed the phone does have some on board memory ( 11MB) to be able to run. However there is no place for anything, messages, contacts, even for running applications such as IE! I'm guessing it is some kind of emergency memory? Anyways, my worry is that i feel that metallic strip is somewhat important so I would like to know how to replace it? Your help is very much appreciated!!!
cabe0018 said:
Yes I am sure they put in an SD card because i removed the back panel and it is clearly visible. One thing I find annoying is that they removed the protective metallic paper used to protect and hold the SDHC in place. Is there a way to use an alternative to this protective paper? I have also noticed the phone does have some on board memory ( 11MB) to be able to run. However there is no place for anything, messages, contacts, even for running applications such as IE! I'm guessing it is some kind of emergency memory? Anyways, my worry is that i feel that metallic strip is somewhat important so I would like to know how to replace it? Your help is very much appreciated!!!
Click to expand...
Click to collapse
Glad I can be of help!
It sounds like it's not recognizing the SD card. Can you get the phone running and goto settings, about phone and check to see what it says for storage capacity. It should show, total storage and available storage.
As far as the metalic tape... I know that it's there to help prevent the SD card from coming out of the tray. Because WP7 Mango security locks the card to prevent any data from being removed from the card. So say you removed the card without unlocking it first, there is no way to extract the data from the card or format it with another device. If the HD7 is turned on without the SD card installed the card will no longer work in the device either.
Not a 100% sure if the tape serves any other purpose though. You could cut a piece of duct tape to fit and secure it in place use the good kind like gorilla duct tape.
xdrc45 said:
Glad I can be of help!
It sounds like it's not recognizing the SD card. Can you get the phone running and goto settings, about phone and check to see what it says for storage capacity. It should show, total storage and available storage.
As far as the metalic tape... I know that it's there to help prevent the SD card from coming out of the tray. Because WP7 Mango security locks the card to prevent any data from being removed from the card. So say you removed the card without unlocking it first, there is no way to extract the data from the card or format it with another device. If the HD7 is turned on without the SD card installed the card will no longer work in the device either.
Not a 100% sure if the tape serves any other purpose though. You could cut a piece of duct tape to fit and secure it in place use the good kind like gorilla duct tape.
Click to expand...
Click to collapse
I have successfully inserted a 32Gb SanDisk SDHC Class 4 in my phone just a few hours ago. I performed a hard reset as instructed. When I booted up, the HTC splash screen showed up and it froze. For roughly 5 minutes...I plucked out the battery and again performed a hard reset. This time the device loaded with an error saying: low storage space please free up some space from your device. I tapped 'ok' and all I had was a black screen, although i know the OS booted up because i could hear system sounds, the bottom buttons were responsive and the lcok screen was visible. However when I slide up, no icons are visible except the wifi icon, the battery icon and the sim icon.
I tried loading the bootloader and as far as storage goes it is only recognizing some sort of 64MB partition from an "sd sandisk". Could this be a faulty installation of the OS on the new card? was I supposed to allow the system to take its time to load the software onto the new SD card? I am also unable to obtain the bootloader version etc that would be required to flash an RUU. Help would be appreciated!
cabe0018 said:
I have successfully inserted a 32Gb SanDisk SDHC Class 4 in my phone just a few hours ago. I performed a hard reset as instructed. When I booted up, the HTC splash screen showed up and it froze. For roughly 5 minutes...I plucked out the battery and again performed a hard reset. This time the device loaded with an error saying: low storage space please free up some space from your device. I tapped 'ok' and all I had was a black screen, although i know the OS booted up because i could hear system sounds, the bottom buttons were responsive and the lcok screen was visible. However when I slide up, no icons are visible except the wifi icon, the battery icon and the sim icon.
I tried loading the bootloader and as far as storage goes it is only recognizing some sort of 64MB partition from an "sd sandisk". Could this be a faulty installation of the OS on the new card? was I supposed to allow the system to take its time to load the software onto the new SD card? I am also unable to obtain the bootloader version etc that would be required to flash an RUU. Help would be appreciated!
Click to expand...
Click to collapse
That's strange... The HD7 has an internal (primary) seperate memory for the OS, the SD card is a secondary memory for the device. Technically it's a non removable storage. So once inserted, you hard reset the device and the SD card is formatted and then it becomes a part of the device and it's integrated into the file system.
If you boot into bootloader mode (device off, hold down the volume down button and power the device back on, while continuing to hold down the volume down button) what's all the information on the bootloader screen? I'm wondering if it's bricked. Can you also get into USB host mode? Device off, hold down the volume down button and the camera button and then power back on.
xdrc45 said:
That's strange... The HD7 has an internal (primary) seperate memory for the OS, the SD card is a secondary memory for the device. Technically it's a non removable storage. So once inserted, you hard reset the device and the SD card is formatted and then it becomes a part of the device and it's integrated into the file system.
If you boot into bootloader mode (device off, hold down the volume down button and power the device back on, while continuing to hold down the volume down button) what's all the information on the bootloader screen? I'm wondering if it's bricked. Can you also get into USB host mode? Device off, hold down the volume down button and the camera button and then power back on.
Click to expand...
Click to collapse
The device was not bricked. I inserted another SDHC card I had used for an old MP4. It was an 8GB TEAM SDHC class 2. The device booted up the OS on this card after a formatting and everything worked better than previously. However some restats were still happening. I tried loading the bootloader in an attempt to flash a custom ROM for the device but no USB text was seen on screen although Zune was recognizing the device perfectly. I decided to leave the device as is. Yesterday, I migrated to my grandma's for a week and I have a room where reception is great always full and no interruptions. A curious fact was that the phone did not restart once no matter how much I used it... and I did use it extensively downloading apps for the first 3 hours, constantly chatting on facebook, emails HTC hub and also voice recognition for messaging and searches. It was working 100% great. When I descended down the stairs (my room is on the first floor) and went to the kitchen I recieved a call from my girlfriend. I picked it up and reception was pretty bad, so I told her to message me instead. As I cut I realized the reception bar was zero. After a couple of minutes, the phone restarted for the first time since my stay at grandma's. I came to the inevitable conclusion that the mobile restarts everytime the reception is bad. This conclusion was backed up by working fine in my room and restarting every time I went to a low reception room. It hit me then that my house does have pretty bad reception where I reside most of the times which causes all those restarts. I am almost sure this is the cause of the restarting. However I am not sure what it infers... Regardless I am sending the phone back in exchange for a new one. However I do wish to know if anyone encountered the same problem, what they did to tackle it (besides running around like a madman to find reception), what causes this and if it is a model defect or a rare case. Thank you for your help!
cabe0018 said:
The device was not bricked. I inserted another SDHC card I had used for an old MP4. It was an 8GB TEAM SDHC class 2. The device booted up the OS on this card after a formatting and everything worked better than previously. However some restats were still happening. I tried loading the bootloader in an attempt to flash a custom ROM for the device but no USB text was seen on screen although Zune was recognizing the device perfectly. I decided to leave the device as is. Yesterday, I migrated to my grandma's for a week and I have a room where reception is great always full and no interruptions. A curious fact was that the phone did not restart once no matter how much I used it... and I did use it extensively downloading apps for the first 3 hours, constantly chatting on facebook, emails HTC hub and also voice recognition for messaging and searches. It was working 100% great. When I descended down the stairs (my room is on the first floor) and went to the kitchen I recieved a call from my girlfriend. I picked it up and reception was pretty bad, so I told her to message me instead. As I cut I realized the reception bar was zero. After a couple of minutes, the phone restarted for the first time since my stay at grandma's. I came to the inevitable conclusion that the mobile restarts everytime the reception is bad. This conclusion was backed up by working fine in my room and restarting every time I went to a low reception room. It hit me then that my house does have pretty bad reception where I reside most of the times which causes all those restarts. I am almost sure this is the cause of the restarting. However I am not sure what it infers... Regardless I am sending the phone back in exchange for a new one. However I do wish to know if anyone encountered the same problem, what they did to tackle it (besides running around like a madman to find reception), what causes this and if it is a model defect or a rare case. Thank you for your help!
Click to expand...
Click to collapse
Yeah... If you can exchange it for another one I would!
If in bootloader mode the white section will display "serial" while not plugged in and "USB" while plugged in, if neither of these are present then the device is half/small bricked for sure, even if it's recognized by Zune. That can be fixed with the goldcard/ Y cable method too.
I have heard of some people having issues with restarts when on their network and while roaming outside of their network. One thing you can try is flashing different radio versions until you find one that gives the best signal. Another thing could be the OS build version and firmware version that your device is running on, it may need to be updated.
xdrc45 said:
Yeah... If you can exchange it for another one I would!
If in bootloader mode the white section will display "serial" while not plugged in and "USB" while plugged in, if neither of these are present then the device is half/small bricked for sure, even if it's recognized by Zune. That can be fixed with the goldcard/ Y cable method too.
I have heard of some people having issues with restarts when on their network and while roaming outside of their network. One thing you can try is flashing different radio versions until you find one that gives the best signal. Another thing could be the OS build version and firmware version that your device is running on, it may need to be updated.
Click to expand...
Click to collapse
While I wish to thank you for your constant support and very useful suggestions on the matter, xdrc45, I am going to send the phone back very soon. Chances are I will recieve a replacement in two weeks time. Aside from this, I am sure the seller at HK will send me a phone with similar issues (Cross-fingers he won't), But since I am able to handle some very basic technical issues such as these, and the phone is at a good price (160EUR) I do not wish to refund. I'd much rather tinker with it a little here and there to customize it to my liking, ensure maximum potential of the phone and prevent issues. So my question is this: What steps should I take the minute the phone arrives (assuming they send me an identical copy of the phone they provided)? Do I need to supply myself with any hardware or software to be able to install the phone to function as though I bought it officially from HTC?
In reply to your suggestion on the bootloader: yes, the white section was always empty no matter what...so I'm guessing the phone was slowly dying away anyways. I will definately look further into the goldcard/ y cable.
Thanks!
cabe0018 said:
While I wish to thank you for your constant support and very useful suggestions on the matter, xdrc45, I am going to send the phone back very soon. Chances are I will recieve a replacement in two weeks time. Aside from this, I am sure the seller at HK will send me a phone with similar issues (Cross-fingers he won't), But since I am able to handle some very basic technical issues such as these, and the phone is at a good price (160EUR) I do not wish to refund. I'd much rather tinker with it a little here and there to customize it to my liking, ensure maximum potential of the phone and prevent issues. So my question is this: What steps should I take the minute the phone arrives (assuming they send me an identical copy of the phone they provided)? Do I need to supply myself with any hardware or software to be able to install the phone to function as though I bought it officially from HTC?
In reply to your suggestion on the bootloader: yes, the white section was always empty no matter what...so I'm guessing the phone was slowly dying away anyways. I will definately look further into the goldcard/ y cable.
Thanks!
Click to expand...
Click to collapse
I think that's a good choice and hopefully the next one won't have the same problems for you!
The best thing to do when you get the new one is boot into bootloader mode and check the information, if you want post back all the info from the BL screen or provide a screen shot of it. Also go into settings, about phone, more info and post back all the information from there too. That way we can make sure everything is up to par on the device and functioning like it should and make sure it's not bricked and if it is we'll get it taken care of for you!
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.
So I noticed on Friday every app (Discord/Signal/Twitter/etc) that used WebViewer was crashing and wouldn't open. I traced it down to the Chrome app and disabled the Chrome app on the phone and everything worked. However, I wasn't able to uninstall or install the latest version of Chrome on the phone, even after re-enabling the app. Not a problem I thought, I'll just Restore from a Titanium backup. However when I did it put the phone into a boot loop. Crap, I'll restore from a Nandroid backup. Nope same thing. So I wiped the System/Dalvik/cache and downloaded the full Rom from OnePlus's website and did a fresh Flash. Same thing. If I try to Format the phone all way it freezes on the data and then goes into a dead android state.
Does anyone have any ideas? Preferably I would like to avoid wiping the phone to zero, but if I have to I have to. If it comes to that, does anyone have a good Rom recommendation for just playing games and taking calls?
DarqAnshin said:
If I try to Format the phone all way it freezes on the data and then goes into a dead android state.
Click to expand...
Click to collapse
RIP UFS memory
przemcio510 said:
RIP UFS memory
Click to expand...
Click to collapse
Hmm... I'm really hoping this is not the case. Do you have any suggestions?
DarqAnshin said:
Hmm... I'm really hoping this is not the case. Do you have any suggestions?
Click to expand...
Click to collapse
Suggestions for what?
Unfortunately these signs you described are leading to memory chip failure (sudden death, hang on formatting data).
If you could boot into TWRP, I'd suggest backing data up to your PC, as much as possbile.
You may try your luck with an unbrick tutorial (without or with data wipe).
przemcio510 said:
Suggestions for what?
Unfortunately these signs you described are leading to memory chip failure (sudden death, hang on formatting data).
If you could boot into TWRP, I'd suggest backing data up to your PC, as much as possbile.
You may try your luck with an unbrick tutorial (without or with data wipe).
Click to expand...
Click to collapse
Yeah TWRP isn't an issue. That I can get into and it is my fault that I should have mentioned that I have already tried the unbrick methods.
I guess I was hoping that it really hadn't fallen to a hardware failure and more along the lines of something I did. I'll be honest in saying that I was really hoping there was a bit of knowldege that I was missing or that somebody would just be like "Nope, I've run into this before. Go in and change this flag from 1 to 0 and do this step you overlooked.".
Either way thank you for your time and responses and many thanks for taking time out to respond back to me.
DarqAnshin said:
Yeah TWRP isn't an issue. That I can get into and it is my fault that I should have mentioned that I have already tried the unbrick methods.
I guess I was hoping that it really hadn't fallen to a hardware failure and more along the lines of something I did. I'll be honest in saying that I was really hoping there was a bit of knowldege that I was missing or that somebody would just be like "Nope, I've run into this before. Go in and change this flag from 1 to 0 and do this step you overlooked.".
Either way thank you for your time and responses and many thanks for taking time out to respond back to me.
Click to expand...
Click to collapse
No problem; sorry for your loss, but you know, that's perversity of inanimate objects. I had similar case with my laptop, when SSD died - poof and data is gone
I had the same on my old phone I just got a new sd 32GB and that was all of my extra Money and less than 2 weeks it broke and had to go back to 8gb
Sent from my A460T using XDA Free mobile app