The follow-up on the "My Note 4 is acting up!" issues.

The follow-up on the "My Note 4 is acting up!" issues. - Galaxy Note 4 General

EXPLANATION THREAD:
TL;DR: There is no TL;DR, I expect anyone who wants to take this seriously to read all of this. If you want to skim, don't bother posting replies.
DISCLAIMER: ANY THING POSTED BELOW WON'T FOR SURE FIX OR EVEN EXTEND YOUR PHONE'S LIFETIME. IT IS NOT FOR SURE THOUGH, IT MAY EVEN SHORTEN YOUR PHONE'S LIFESPAN EVEN SHORTER.
I would like to start out by saying thanks to all the other people with eMMC read issues and their testing to help find out what works and what doesn't works. I can't list you all, but I would like to say thanks anyways.
What is this about? [You may be asking me as you are reading this.]
This is about the issues with Note 4's starting to lag, crash, stutter, and downright refuse to boot.
.
Why bother with the thread, here to rub it in their faces that your phone works?
No. In fact, my phone also has these issues, that's why I bothered researching into it.
Well, then? What's the point?
Be quiet and I will get to that.
Note 4's have started having eMMC issues quite recently, the whole shebang probably started around April of this year. (Not quite sure, just an estimate.) This results in storage lags that are really bad, to the phone crashing entirely, to the phone even failing to boot system, or even read the bootloader. The problem is that this is affecting anyone who owns a Note 4, be it rooted or not rooted, someone who has been on stock the whole time to someone who flashes every other day. There isn't even any signs to look out for before it starts happening, it just happens.
Can I fix it using [XXXXXXX] Rom or Software Fix?
No. At least from what we all have seen, you can't fix this with software, it is a Hardware issue.
But wait, NYiCoN made a thread about how he fixed his issue with software.
Personally, everyone's case can be slightly different, I have tried his method, but it didn't work for me sadly. I am not saying his method doesn't have a chance of working, go ahead and try it if you haven't. I linked his thread just in case. If it works for you, great, rejoice in your working phone, if not, keep reading. I will cover some other things to try.
Some of the causes to the problem that people are thinking of, I have compiled together. I wanted to point some of the more major ones out first. These responses are my testing, not anyone else's.
● Battery being an issue? (People tend to believe this because a battery pull can fix boot issues.)
I have bought multiple batteries off of Amazon from Anker and Samsung, and haven't seen a difference with different batteries.
● Rom being an issue? (I and others, including this thread by forbidinjustice have been observing this.)
I myself have found that a stock rom does improve if not entirely fix all the issues. This may have something to do with the kernel. My recommendation: Try wiping the entire NAND with a re-partition PIT file, a stock image of Marshmallow or Lollipop, your choice, and Nand erase all selected in ODIN, I will explain this process later.
● Kernel being an issue? (Maybe something to do with power management?)
I have found that most eMMC issues happen to me on roms with custom kernels, like CM, or device ports. I have also observed that my eMMC only crashes when it goes from a low-power state to high-power state too quickly. Which would explain why it can crash during doze, or when the phone isn't using the eMMC too heavily.
● SIM and/or SD Card (SD bus doing something to eMMC chip? Not an expert with storage types. Forgive me.)
I haven't found my phone to be any more or less stable with my SD Card and SIM Card both in. This honestly has left me drawing blanks.
There are way more speculations to the problem, but those are the major ones to pay attention to. But now, onto bigger and better things to do just in case your phone hasn't died yet. Things to do first will be on the second post.

THINGS TO DO FIRST:
NOTICE: This post will mainly pertain to those that still have a phone that boots up and works.
This post will cover what you should do first before experimenting or messing around with software fixes.
● Backup your important files, if you don't, YOU WILL LOSE THEM. Do not take that warning lightly.
● Next, this will require that you have a custom recovery, there may be a way to do this within a terminal with root, or something along those lines, but don't count on them.
● You will need to download this Unbrick Creator from this AndroidFileHost link courtesy of hsbadr. Give him thanks at the origin thread here.
● Then, copy the zip to your Note 4 and "install" the zip. This will require TWRP however as it relies on BusyBox commands to backup the bootloader and package it. Your bootloader backup will then be copied to the internal SD on the phone. Proceed to copy it back to your computer and hold onto that image.
● If you have a spare SD, you can go ahead and get Win32DiskImager from here. If you are on Linux or Mac however, you should be able to dd the image file to a Micro SD card. Make sure to unzip it from it's gzip archive though, otherwise it won't write properly. Proceed to write the image file to the SD card, then whenever your phone can't load the bootloader, pop this SD card in and BAM! You can get back into ODIN to reflash the right bootloader.
That was pretty short relative to my first post above. Anyways, things to try will be Post 3.

THINGS TO TRY:
This post will cover what you can consider trying to help alleviate your issues.
NOTICE: WHAT I COVER BELOW IS YOUR RESPONSIBILITY, NOT MINE:
I will try my hardest to give you clear, concise instructions on what to do, but you are responsible for carrying them out, if your phone bricks, makes funny noise, catches on fire, kicks your dog, or even joins ISIS, it isn't my responsibility, so if you brick your device, don't blame me.
● First up, because I feel it is one of the safest methods to try is NYiCoN's method.
This is his method, not mine, I am only paraphrasing it here because I want to keep the post continuous.
● He provides the files you need to download at this Google Drive link here.
● You need to download all the files from that link and hold onto them.
● After downloading files, proceed to put the phone into Download Mode.
● Open the ODIN binary provided in the Google Drive and connect the phone to your PC.
● Click on the CP button to choose the "N910TTMB1COD6_Modem_CP.tar" file.
● Proceed to click on the AP button and choose the "N910TUVU2EPE3_N910TTMB2EPE3_N910TUVU2EPE3_HOME_AP.tar" file.
● Go ahead and click the Start button to begin flashing.
● Once flashing is complete, pull the battery on the phone and immediately go back into Download Mode.
● Click on the CP button and choose the "N910TUVU2EPE3_CP.tar" file.
● Click the start button to begin flashing.
● Once ODIN is finished, pull battery and open Samsung Kies.
● Proceed to perform an Emergency Upgrade in Kies to force phone to EPG2 Stock firmware.
● Once Kies is done, let your phone start up as normal and play around, see if this helped.
● Second thing to try is justforgot's method which involves wiping all the partitions in TWRP each in a row before flashing a rom.
● The only thing I will mention is the eMMC tends to run smoother when all partitions are wiped before flashing, but this also tends to wear out chip worse. I only recommend this if you don't care about life span of phone, or you aren't worried. If you need the phone to last, be weary as this can speed up deterioration of the memory provided the eMMC chip is the problem.
● Last method for right now is something I thought up with the help of maxrfon's logcat output which involved /efs write errors.
● I should point out that this method also adds to deterioration on the storage chip, albeit to a lesser extent, a risk still exists. Also, this only works on TouchWiz roms as on CM roms, TWRP won't let you backup the EFS partition.
● It simply involves backing up /efs at least once and then restoring about 7-10 times, around 2-3 time, it will take up to 2 entire minutes to write 14 megabytes, afterwards restore should be quick again. That should help a little, but it isn't to as great an extent as the upper methods do.
● BONUS!!! World War 3 Atom Bomb method. This was something I mismashed with other methods along with my own knowledge of ODIN. This method will wipe your chip as clean as you can possibly get it without brick. This also has the highest rate of deterioration, be careful, this method is a doozy.
● First, get ahold of PIT files for your device, I won't post links because malhandling these files can be bad. You can get bricked if you aren't careful. SamMobile is a pretty good place to find PIT files.
● Second, get ahold of a stock firmware you want to use, or you can tie this in with NYiCoN's method above for extra chance of a good flash.
● Open ODIN and connect the phone to the PC in Download Mode
● Click the Pit button and chose the PIT file you downloaded.
● Proceed with NYiCoN's Method except checking re-partition and Nand Erase All, during the first flash session.
● Once you are ready to boot, you will be taken to recovery to flash the system image, but after that, you are stuck at the bootloader screen forever. You need to go back into recovery, wait for Installing System Update to pass, then do a factory reset because the Nand Erase removes the data partition. A factory reset recreates this data partition, reboot and you are golden.
Last post will be what you can do to help diagnose the issue further. If you so please.

END POST:
Due to the thread not being that popular, I have decided to remove the post explaining about what you can do if you wish to help. That and some people believe this thread was useless, it probably is, due to this being a hardware bug (most likely). I guess that the only advice I can give you now is that if none of the above worked. You will have to buy a new phone or find a way to fix this one. I will keep the thank you message below as I still thank those who took the time to read it. This thread was made to be a one stop learn 'em session about the NAND chip issue, and if it could be stickied, I would appreciate it. Other wise, the thread is useless as of now and it can be closed.
As always, if you read through all of this, I thank YOU. Even if you don't contribute anything, I thank you for bothering to read this, which shows that it meant SOMETHING. If I sounded bossy, forceful, mean, rude, strict, or even harsh, I was only trying to express seriousness on the subject, don't take me as leader of the Note 4 crash bug or anything like that, I am just a guy with a bugged phone like you probably are who is trying to fix it.

No need to write a book. The emmc issue is the nand chip dying a slow death. Its a ticking time bomb and will have to be fixed. Just accept it

ciscostud said:
No need to write a book. The emmc issue is the nand chip dying a slow death. Its a ticking time bomb and will have to be fixed. Just accept it
Click to expand...
Click to collapse
No need to sound so negative. The eMMC issue may just be a slow failure, it may be just a ticking time bomb, but you can't blame people for trying to extend the time on that bomb, like me. Even if it has to be a hardware fix, that is all-in-all a cheaper solution than a new phone entirely. This thread can also serve the purpose of ensuring it's the storage chip failing. Plus, I already HAVE accepted the eMMC failing being an outcome, the first post went over your chances of fixing it with software and I said they were possibly was NO chance of fixing it with software. The post covering things to try is LITERALLY called THINGS TO TRY: This thread also hopes to achieve educating people in the fact that their hardware may not have failed, and it was a software issue. And if I helped even one person, it would of been worth it.
Besides, the thread name doesn't say "LAST BIT OF FALSE HOPE FOR DELUSIONAL NOTE 4 OWNERS IN DENIAL." It says it is a follow up to all of the Note 4 issue threads.

I will summarize.... If you're getting the emmc error, no amount of tinkering, flashing or battery changes will fix it. The more you use your phone the worse it will get.
Backup your phone while it still works and make a plan to replace your mainboard or get a new one phone.

ciscostud said:
I will summarize.... If you're getting the emmc error, no amount of tinkering, flashing or battery changes will fix it. The more you use your phone the worse it will get.
Backup your phone while it still works and make a plan to replace your mainboard or get a new one phone.
Click to expand...
Click to collapse
I understand what you mean about the inevitable hardware failure with this error, and I am not trying to tell people that flashing, tinkering, or battery changes WILL fix it. I am only stating that you might be able to fix it or extend the phone's lifetime. Because plenty of people, including myself, can't afford to get a new phone off the bat. You also can't trust mainboards as they can come from other used phones and can have the same issues. This thread may just be a bunch of myths that don't help, but there is real experiences behind them. People who want to try will try this, if it helps is up to them. I understand it is hardware and you aren't saying anything new by pointing it out. But this is meant to help people who have this phone and need/want to try anything to get it in working shape, even if just for an extra day.
But for record's sake, I will add a disclaimer.

Related

What are the Cons of rooting your phone?

I read the wiki but it only tells you "Why you should" root your phone. Obviously Google removed root from the latest firmware for a reason. If its for security reasons, how can you be "safe" with a rooted phone? Can you still download paid apps from the App store with a rooted phone? How well does the Apps on the SD card work? The main reason I would want to root my phone is for the SD card app feature. The G1 space sucks ass and its constantly telling me I am low on space.

When you root your phone, it automatically installs an app called "SuperUser" (assuming you're using one of JesusFreke's builds). SuperUser allows you to control which applications have root privileges.
Also, Google probably removed root because of stuff like the fact that it enables you to copy protected apps and the like... and even if they didn't know at the time, they probably knew that it would happen

Superuser protects your phone by allowing programs you give permission to that use root. I can still see paid apps in the Market (I haven't bought any yet, but I will). I didn't move my apps onto my SD card because Paragon Partition Manager froze during the partitioning and I had to reinstall Vista .
The only con is that you have to wait for JF's updates

I believe I also read here that rooting your phone voids your warrenty, so if you have a problem with it make sure you switch back to the official firmware before sending it in

androidmonkey said:
I read the wiki but it only tells you "Why you should" root your phone. Obviously Google removed root from the latest firmware for a reason. If its for security reasons, how can you be "safe" with a rooted phone? Can you still download paid apps from the App store with a rooted phone? How well does the Apps on the SD card work? The main reason I would want to root my phone is for the SD card app feature. The G1 space sucks ass and its constantly telling me I am low on space.
Click to expand...
Click to collapse
I'll try to answer your questions the best I can:
-I don't work for Google so be advised this IS pure speculation on my part. With that said, I think they removed root access for the masses to avoid the possibility of folks having their Android handsets compromised by malicious apps.
Though, having root doesn't necessarily mean this WILL happen to you.
So long as you have common sense, and know better to install apps from questionable sources, you'll be fine. Additionally, the JesusFreke firmwares have a "SuperUser Whitelist" app that will ask for escalated privileges whenever a process requires root.
This is provided as another layer of security.
So to say it again, do not allow apps/processes to run unless you KNOW EXACTLY WHAT THEY DO. Follow that and you won't have any problems.
-Market apps can be installed and used without issue. I have dozens apps installed (and yes, a few paid apps as well) and have had ZERO issues with them. Matter of fact, if you look through the market, you'll see several cool apps that require root (Task Manager, WiFi Tether, etc).
-Far as installing and running apps from the sdcard, I'll defer to someone else because I haven't done it myself. I prefer to wait until an easier, or official method becomes available. Though, I have moved the various caches (Web, Maps, Market, etc) to the sdcard without issue.
That helps to conserve space with the internal memory.
Hopefully that helps you.

Thanks for all the replies. So is it safe to say that if I only install apps from the Android Market I should be safe? Can programs on the Android Market be malicious? Hopefully Google is monitoring the applications for malicious code.
So, what is the "best" guide to use for rooting a RC33 phone?

programs on the market could possibly be malicious, read reviews, i found a game that said it needed the internet, gps, and some other stuff in order to work, but yet the app never used any of those features in the actual gameplay, thus i removed it and reported it as malicious because i frankly don't feel that it should need access to things it isn't gonna use. a general rule is that if a single person said it was malicious then don't install it, and never be the first to install an app. let someone else break their phone first

The only con for rooting your phone is that people who don't know any better usually end up bricking it. "oooh root yay! i don't know what it duz bat it sounds cool! oh no! i brcked it halp plz"

And you can still unbrick your phone pretty easily.

IzzeLing said:
The only con for rooting your phone is that people who don't know any better usually end up bricking it. "oooh root yay! i don't know what it duz bat it sounds cool! oh no! i brcked it halp plz"
Click to expand...
Click to collapse
lol, your quote can be used on a LOL Cat.

i wouldnt say that waiting for the updates is technically waiting, when you have a rooted phone...
at least for me, i must have been on the bottom of t-mobile's randomized IMEI list when it came to updates.. I used to see people all around me have updates for weeks before me. Coincidentally i was the first to have mine... but the updates are released right from the google site, plus the wait time for JF and others to work their magic.
cant complain with a rooted phone, if anyone is skeptical about it... you CAN reverse the process

the.snks said:
-Far as installing and running apps from the sdcard, I'll defer to someone else because I haven't done it myself. I prefer to wait until an easier, or official method becomes available. Though, I have moved the various caches (Web, Maps, Market, etc) to the sdcard without issue.
Click to expand...
Click to collapse
I've moved my apps and caches to the sdcard and now I never have to worry about running low on space.
I followed one of the tutorials about moving the apps, but when paid apps came out, I had some problems. The solution was to move not only the "app" directory but also the "app-private" directory to the sdcard. Once I did that, everything was fine. I am able to install both free and paid apps with no problems. I'm very glad I did it -- no regrets.
I have an 8gb sdcard and I partitioned 1gb to apps and caches (ext2 format) and 7gb to data (fat32 format).

unknown.soul said:
Superuser protects your phone by allowing programs you give permission to that use root. I can still see paid apps in the Market (I haven't bought any yet, but I will). I didn't move my apps onto my SD card because Paragon Partition Manager froze during the partitioning and I had to reinstall Vista .
The only con is that you have to wait for JF's updates
Click to expand...
Click to collapse
Rooting may be safe to people like you all, but rooting is definitely the downside of android. Sd card blank and file recognition errors are the opposition to what android has made. I will not root my phone again because of the unexpected long term damage this has caused to my phone. I will tell my friends not to root their phone unless they want to turn their android to ruins. These kind of problems happen for absolutely no reason at all.

ri123 said:
Rooting may be safe to people like you all, but rooting is definitely the downside of android. Sd card blank and file recognition errors are the opposition to what android has made. I will not root my phone again because of the unexpected long term damage this has caused to my phone. I will tell my friends not to root their phone unless they want to turn their android to ruins. These kind of problems happen for absolutely no reason at all.
Click to expand...
Click to collapse
I disagree with the statement "downside". Android is about open source and customization. The downside to root is that you need to spend a bit of extra time playing with your phone when it doesn't end up going the way you planned or there are bugs in a new Rom. Other than the extra time on the phone, I have not run into a downside. I have not looked back since I rooted.
Sent from my Kang Banged Dinc2

ri123 said:
Rooting may be safe to people like you all, but rooting is definitely the downside of android. Sd card blank and file recognition errors are the opposition to what android has made. I will not root my phone again because of the unexpected long term damage this has caused to my phone. I will tell my friends not to root their phone unless they want to turn their android to ruins. These kind of problems happen for absolutely no reason at all.
Click to expand...
Click to collapse
I 100% disagree with this statment. having a rooted phone in itself will not cause any errors. even the process of rooting won't brick a phone or cause problems (so long as you understand what you are doing). although there is the way out in right field chance of something going even if everything is done right (very hard to brick a phone if you truley know what you are doing and are sober at the time)
android has always been and (hopefully) always will be open source. the android code it self in pure aosp is in fact rooted. it is the carriers and cell phone makers and such that lock the bootloader and deny privalage. as any linux user knows it is easily possible to damage you phone/pc/etc if you don't know what you are doing, but having root privalage in itself causes no harm - only to the novice.
this stament of unexpected long term damaged caused by root is false, it was caused by someone not knowing what they were doing and shouldn't have root privalages in the first place.
*excuse my spelling errors as rooting a phone doesn't improve my gramar/spelling*
Sent from my HTC Vision using xda premium

demkantor said:
I 100% disagree with this statment. having a rooted phone in itself will not cause any errors. even the process of rooting won't brick a phone or cause problems (so long as you understand what you are doing). although there is the way out in right field chance of something going even if everything is done right (very hard to brick a phone if you truley know what you are doing and are sober at the time)
android has always been and (hopefully) always will be open source. the android code it self in pure aosp is in fact rooted. it is the carriers and cell phone makers and such that lock the bootloader and deny privalage. as any linux user knows it is easily possible to damage you phone/pc/etc if you don't know what you are doing, but having root privalage in itself causes no harm - only to the novice.
this stament of unexpected long term damaged caused by root is false, it was caused by someone not knowing what they were doing and shouldn't have root privalages in the first place.
*excuse my spelling errors as rooting a phone doesn't improve my gramar/spelling*
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
To prevent factory reset bricking I had to move to a different Rom. I knew what I was doing. I returned to stock Rom and factory reset, and every zip I downloaded from my computer could not be recognised properly by my phone.
I know that android is based on pure root, but who should I blame if something goes wrong with my phone? Every rooted phone becomes faulty, why should I pay extra just because I can't download anymore roms?
Think about the random percentage of people that have had their phones bricked just because of rooting problems. I am one of them.
Your statement "only to the novice" is something I disagree with.
I remember when I read a thread about someone's Samsung Vibrant getting hard bricked all of a sudden! Or when I read a Sony Ericsson touchscreen refusing to work after light debugging. These people will most likely be paying for their android phones.
In a way, I do not completely disagree with you. In a way I believe that Android should start believing in its roots.
For the moment, I do not know who to blame for the mess my phone is in. I didn't do things wrong on purpose. So maybe it is better not to root. Maybe it is more advisable to complain to the creator of your phone if there is not "enough", or if there is too much bloatware. Maybe Android should be fixing my HTC! I need to stop all this unnecessary refusal from happening on my android. This is why I find the essence of rooting initially bad. When there is no limits, something can go wrong.
Please may I let you know that my touchscreen is mostly unresponsive. I will be surprised if I have got all of my spelling correct! If I still had the advantage of the warranty, I would be sending my phone straight to HTC to get repaired.
Sent from an unusually unresponsive touchscreen on my HTC Explorer A310e using xda app-developers app

ri123 said:
To prevent factory reset bricking I had to move to a different Rom. I knew what I was doing. I returned to stock Rom and factory reset, and every zip I downloaded from my computer could not be recognised properly by my phone.
I know that android is based on pure root, but who should I blame if something goes wrong with my phone? Every rooted phone becomes faulty, why should I pay extra just because I can't download anymore roms?
Think about the random percentage of people that have had their phones bricked just because of rooting problems. I am one of them.
I remember when I read a thread about someone's Samsung Vibrant getting hard bricked all of a sudden! Or when I read a Sony Ericsson touchscreen refusing to work after light debugging.
In a way, I do not completely disagree with you. In a way I believe that Android should start believing in its roots.
For the moment, I do not know who to blame for the mess my phone is in. I didn't do things wrong on purpose. So maybe it is better not to root. Maybe it is more advisable to complain to the creator of your phone if there is not "enough", or if there is too much bloatware. Maybe Android should be fixing my HTC! I need to stop all this unnecessary refusal from happening on my android. This is why I find the essence of rooting initially bad. When there is no limits, something can go wrong.
Sent from an unusually unresponsive touchscreen on my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse
I'm not trying to sound rude here but the only blame is to ones self if YOU screw up your phone.
yes you can blame a phone company when the hardware fails from normal use, or your cell phone carrier for adding useless apps. or well blame android for creating an operating system that at its heart allows one to have full access to every part of it.
android doesn't write the radio, android doesn't write the bootloader, they are not firmware or hardware only os. they also are not responsible for a bad rom.
I will say again the act of rooting your phone in itself causes no damage, only when you do something wrong during this process is it possible to brick your phone, and as for the percentage of people who did brick there phone 99.99% of them messed up, that means their own fault.
.01% had a major power surge while phone was updating via fastboot and their computer only coppied a portion of the firmware to the phone and then the dog kicked over the phone knooking the battery out leaving no bootoader... or whatever, it is hard to do this wrong
and again having a rooted phone will intself not brake hardware, not damage firmware, will not cause a single issue
the missue of having root, or the improper method of obtaining root is the only problem, and people who don't know what they are doing (fully understand) well just shouldn't root, or should learn to except blame at the very least...
done with my ranting, good day...
Sent from my HTC Vision using xda premium

demkantor said:
I'm not trying to sound rude here but the only blame is to ones self if YOU screw up your phone.
yes you can blame a phone company when the hardware fails from normal use, or your cell phone carrier for adding useless apps. or well blame android for creating an operating system that at its heart allows one to have full access to every part of it.
android doesn't write the radio, android doesn't write the bootloader, they are not firmware or hardware only os. they also are not responsible for a bad rom.
I will say again the act of rooting your phone in itself causes no damage, only when you do something wrong during this process is it possible to brick your phone, and as for the percentage of people who did brick there phone 99.99% of them messed up, that means their own fault.
.01% had a major power surge while phone was updating via fastboot and their computer only coppied a portion of the firmware to the phone and then the dog kicked over the phone knooking the battery out leaving no bootoader... or whatever, it is hard to do this wrong
and again having a rooted phone will intself not brake hardware, not damage firmware, will not cause a single issue
the missue of having root, or the improper method of obtaining root is the only problem, and people who don't know what they are doing (fully understand) well just shouldn't root, or should learn to except blame at the very least...
done with my ranting, good day...
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
As I have said,one of the problems with rooting is that people have to move off their Rom in case of factory reset bricking.
0.1% have got the limited service error or the bad zip file error with their phone practically in a trap.
Much more than 0.1% have the sdcard blank error
I understand root enough to install roms and unroot my phone.
I did not do this on purpose, I just installed stock Rom and factory reset and my phone did not work as it intended to.
This is why I shall, in the future, ACCEPT things and rant about my rooting experience to those people who would unconsciously root. More ranting is needed.
Sent from my HTC Explorer A310e using xda app-developers app

ri123 said:
As I have said,one of the problems with rooting is that people have to move off their Rom in case of factory reset bricking.
0.1% have got the limited service error or the bad zip file error with their phone practically in a trap.
Much more than 0.1% have the sdcard blank error
I understand root enough to install roms and unroot my phone.
I did not do this on purpose, I just installed stock Rom and factory reset and my phone did not work as it intended to.
This is why I shall, in the future, ACCEPT things and rant about my rooting experience to those people who would unconsciously root. More ranting is needed.
Sent from my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse
whenever you flash something to your phone expecially firmware you should check the md5sum, its a given and those 0.1% would not have a brick due to a curropt download if they did this so again not the fault of root
having root access WILL NOT cause your sd card slot to quit working, this just has no merrit, having root has just doesn't break hardware in itself, it just doesn't
depending on the phone and how you rooted and if you have an unlocked boot loader and loads of other question need to be figured out before you flash a stock rom, especially from bootloader (if the rom is packaged with a radio, hboot, recovery etc)
once you have true soff you can flash almost anything, including things that shouldn't be flashed. have a security flag is good for this exact purpose, to keep people from flashing what they shouldn't - yes this is how most people brick their phone, they don't fully understand.
and I'm not saying you stupid by I do agree it doesn't take a genius to flash a rom, but knowing the steps that someone has written down is diffrent then undertanding why it works
listen I know you said more ranting is neccessary, but it isn't, the fact is you figured out how to have fun with your phone by following some steps you read in a forum somewhere or watched a youtube video, that's great fun, I know I love it to.
but you didn't bother to figure out why it works or what to do/not to do, because you didn't you made a mistake, it happens, no one thinks less of you.
now you should learn from your mistake and learn to accept blame for making this make, no one told you to do what you did, and you didn't take the time to find out the repercutions of what you were about to do before you damaged your phone.
again root privalages in itself CAN'T harm your phone it just enables you to make a mistake as you have lost some security against it, just as owning a gun won't make you shoot someone but gives you the ability to do so (exuse my analogy as I know it is not apples to apples)
**** happens, get on with your life, no need to rant, no one thinks less of you, learn from mistakes, accept blame when you should... and as always exuse my speeling/grammar errors as root in it self won't make me smarter either
good night
Sent from my HTC Vision using xda premium

demkantor said:
whenever you flash something to your phone expecially firmware you should check the md5sum, its a given and those 0.1% would not have a brick due to a curropt download if they did this so again not the fault of root
having root access WILL NOT cause your sd card slot to quit working, this just has no merrit, having root has just doesn't break hardware in itself, it just doesn't
depending on the phone and how you rooted and if you have an unlocked boot loader and loads of other question need to be figured out before you flash a stock rom, especially from bootloader (if the rom is packaged with a radio, hboot, recovery etc)
once you have true soff you can flash almost anything, including things that shouldn't be flashed. have a security flag is good for this exact purpose, to keep people from flashing what they shouldn't - yes this is how most people brick their phone, they don't fully understand.
and I'm not saying you stupid by I do agree it doesn't take a genius to flash a rom, but knowing the steps that someone has written down is diffrent then undertanding why it works
listen I know you said more ranting is neccessary, but it isn't, the fact is you figured out how to have fun with your phone by following some steps you read in a forum somewhere or watched a youtube video, that's great fun, I know I love it to.
but you didn't bother to figure out why it works or what to do/not to do, because you didn't you made a mistake, it happens, no one thinks less of you.
now you should learn from your mistake and learn to accept blame for making this make, no one told you to do what you did, and you didn't take the time to find out the repercutions of what you were about to do before you damaged your phone.
again root privalages in itself CAN'T harm your phone it just enables you to make a mistake as you have lost some security against it, just as owning a gun won't make you shoot someone but gives you the ability to do so (exuse my analogy as I know it is not apples to apples)
**** happens, get on with your life, no need to rant, no one thinks less of you, learn from mistakes, accept blame when you should... and as always exuse my speeling/grammar errors as root in it self won't make me smarter either
good night
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Thanks for the reply.
I feel more people should know the repercussions and 'cons' of rooting so I thought of involving my situation as it could affect someone's choice of rooting.
What is a security flag? My phone is s on and yet it does not work.
Also, what is 'true soff'?
Sent from my HTC Explorer A310e using xda app-developers app

For developers. Root Info. Hope this helps

Hey,
I have been trying to root since the minute the process was let out publicly with no luck, until this morning. I have been through each thread over and over and finally found several things that made it work. After completing the task and going back over everything I tried. I found out the following and I would bet good money it will work for any one.
1. I left my phone plugged in the whole time. No usb cord inserting
2. I had it set to disk mode under pc connection in settings.
3. I used the 2gb card from verizon. Did not erase it. Don't know how it was formatted and don't believe it matters.
4. Made sure the HTC driver was working. This was done by having phone plugged in while in normal operating mode. To verify this once you hear the usb sounds in the command window at the C:/whatever/tools prompt type adb devices. It should come up with a serial number or such.
5. This will sound odd, but several of the methods talk about the screen flicker and not many talk about a sound the phone makes when it loads the sd card. That sound is real and audible if you put the phone to your ear. try it when you turn your phone on. You can hear it. That sound is the key. Try it by starting your phone normally and put it up to your ear. You will hear it.
6. Ok, if your phone is recognized by adb and you can hear the sound you have all you need. Make sure you have the necessay files downloaded to your tools folder.
7. With your phone in normal operating mode, shut it down. You need access to your battery and your sd card so the back needs to be off.
8. Pull the battery and unclick your sd card, hold Vol- and power. The phone will start and try to load the bootloader and leave you at the screen where you can select recovery.
9. Start Loop.bat
10. Press Vol - to select recovery and press power. move the phone close to your ear with your thumbnail on the sd card. When you hear that sound, immediately click in your sd card. The phone will goto the black triangle screen. The phone will then go through it's usb detection and when you hear the connected sound, you will get the error message. This may take 15-30 seconds. It took me 2 tries the first time, but now I have gotten it everytime I have tried since.
11. type in adb devices to verify that your in recovery.
12. Use your favorite method from here. The xda method is the one I used. Everything works fine. Wireless directly to my IPAD.
I think if I made a spread sheet of all the methods, sd cards and timings, we would find out that this is usually the thing that works. You can use the clock method, but I guarantee the right time collates with the cricket sound which collates with the screen flicker.
Anyone else smart that cares to look at this may be able to figure a way to streamline it even more.
Rod

sorry buddy but this old news we all knew about the audible sound, most people tried clicking in the sd card at that point, others tried plugging in usb at that point, buts we all knew about the sound and tried different methods to get it to work. personally i tried your method and it didnt work before i actually rooted. the method i used, envolved a linux live usb flash drive, linux live sd card formatted, and the tail messages, worked everytime the first time, if i missed the first time i had to restart the entire process. atleast now you are rooted

Jesus, everyone has a method that works for "everyone".
Apparently "Search" is broken?

aaronjb said:
Jesus, everyone has a method that works for "everyone".
Click to expand...
Click to collapse
I hear what you're saying, but we shouldn't stifle discussion that could lead to a more reproducible method, either. Maybe this doesn't warrant a new thread, but whatever.
Anyway, I had tried several of the other methods before, maybe 20-30 times, but nothing worked. I tried to time it with the click sound a couple times before, and it didn't work, but I thought I'd give it another try, since OP mentioned he got it to work with the stock 2GB SanDisk card, and that's all I have.
This time, I got it on the second attempt. My reflexes were a little slow, so it was probably more like a half-second after the click sound that I managed to click in the SD card. I haven't attempted to get back yet, so I don't know how repeatable it is.
One thing that may or may not be worth trying for others is that right before I got it, I uninstalled HTC sync, installed the bootloader drivers from the unrevoked site (can't post URL since I'm a noob).
Then uninstalled them (check "delete drivers" when doing so they won't auto-reinstall), reinstalled HTC sync, and finally reinstalled the bootloader drivers. I did the last reinstall because the device wasn't showing up when the phone was in the bootloader menu w/just HTC sync. It's unclear if any of this made a difference, or if I just got lucky with my timing this time.
When I was booting into recovery and pushed in the SD card, very shortly afterwards, I got a balloon in the bottom right that said it was installing the drivers (again? is that expected?). After that, rewt!

Oh lord, if I never saw another one if these threads, I could die a happy man. They're about as useful as alchemy, phrenology, perpetual motion machines, astrology, cold fusion, x-ray specs, etc etc ...
Sent from my Hal90000 using XDA App

The question begs:
If it bothers you so much, why the heck did you read it? Nobody makes you read these particular threads.

adrynalyne said:
The question begs:
If it bothers you so much, why the heck did you read it? Nobody makes you read these particular threads.
Click to expand...
Click to collapse
Because the title is so vague that you don't know it's YARMTISWWFE (Yet Another Root Method That I'm Sure Will Work For Everybody) thread until you read it?

If you couldn't figure out the post content by this time:
I have been trying to root since
Click to expand...
Click to collapse
Then some folks here might want to get tested for some learning disabilities. Don't even have to finish the first sentence to figure out what this thread was about.

To become rooted, do you have wipe your phone and sd card?

No, you definitely do not need to do that.

adrynalyne said:
The question begs:
If it bothers you so much, why the heck did you read it? Nobody makes you read these particular threads.
Click to expand...
Click to collapse
I wanted to see who was pretentious enough to think that their hare-brained scheme for rooting needed a new post, why they thought their experience could possible impact developing for the Inc, or what could possibly justify tacking "for devs" on the title of their post--as if they succeeded in making a secret club of a thread by doing so.
If he/she really wanted to help devs, they might have PM'd the guys involved with Unrevoked first, or joined their IRC channel, rather than clogging up the forum with another rooting thread. Honestly, there's enough going on now to think of others' purposes here before your "eureka" moment. Too bad I had to bump this thread just to respond.

Why be so mean? The more discussion on obtaining root the better I would think. Maybe this topic was not helpful but another one someday might and if people like the rude folks bashing the OP in this thread make others afraid to post then we might never get a reproducible method.
The sooner we get a reproducible method the better, because that means more folks to test and a wider user base for ROMs. I dont think a developer would spend too much time on a ROM for a device that they do not own and feel only a handful of people would have access to.

Oozura said:
Why be so mean? The more discussion on obtaining root the better I would think. Maybe this topic was not helpful but another one someday might and if people like the rude folks bashing the OP in this thread make others afraid to post then we might never get a reproducible method.
Click to expand...
Click to collapse
You call it mean, I call it strongly discouraging more speculation on a topic that already has a dozen or more threads going. As you can see by the proliferation of more advanced thread recently, most have moved on from trying to root, which common sense would tell one is caused by most having figured it out.

Maybe everyone has figured it out, maybe not. I imagine if you started a thread and asked who was still trying you would get several folks respond that they were. Nothing indicative of the entire population but just saying.
Edit: I just saw your avatar and then your use of such excellent gramar and vocabulary above. Did you make your own lingwo(sp) robot?

This thread has turned into a flame fest against the OP (since pretty much the beginning of it). Thread closed.

[Q] Things I want to know about flashing and more!

A lot of things are never explained. Its really easy to just flash a ROM but there is a lot more to the process that could help.
I have soo many questions its ridiculous.. Why not ask them all at once? Im not dumb, I would like to see someone find complete information on any of these things..
1. Nobody ever explained what we can do with Clockwork Recovery, I know that I can restore previous ROMS with it but what else? Could I easily just flash back to my original 2.1 out of the box modded phone ROM even though I am on 2.2 now?
2. When I flash these ROMS, should I be doing like a format of the internal SD card to make it all fresh and what not?
3. What about App2SD? Thought sounded way cool when I first heard about it. How can I get that working? Couldn't I just use that and never have to backup my apps between ROMS anymore? Maybe I don't get it but theres no info on it either.
4. What is Nandroid? Sounds cool.
5. What would be the best way to back everything up between flashes?
At the moment, I just use TB to back up my important apps and then restore them + data afterwards. And for contacts and stuff I just uses Google sync, easy enough. It seems pointless to back up though because the Titanium Backup folder still remains after flashing, why do things still remain? Is this a good thing?
6. What the heck is kernel swapping and more specifically, what does it do? I have a general idea what a kernel is but feel free to explain!
7. Anything else about the finesses of flashing would be awesome to read about. This is all that comes to mind but yeah, feel free to really lay on the details.
I don't really care how ridiculous this seems, its a forum. More specifically, the Q&A section. Any help would be awesome!
[Edit] Ha, go figure. No replies. Was worth a try.

Those are all very good questions.
I agree with you that so far there is not a good central repository of information to explain all this that I know of.
I recently flashed to Cognition 9.1 after reading bajillions of threads to try and piece together the proper procedure. You see people making suggestions left and right, but half the time they conflict with each other, and the other half are stated in terms that only someone that already knows how to do it would understand.
There are two wikis and a couple guides out there with good information, but they tend to be grander in scale. "How to make your Captivate take over the world" articles are great and useful. But it's very difficult to find information on the small specific bits contained in those guides.
To understand all those little bits requires lots of googling and taking notes. I can't tell you how many e-mails I've sent myself from work containing little snippets of "do this", "try this", "how to..." that I've slowly come across after scouring these forums for hours on end.
That's not to say I don't appreciate all the info given from the users here. I'm just saying it'll be nice when all that knowledge gets pooled into one central location like one of the wikis rather than scattered sentence by sentence amid thousands of pages of posts.
And the next response to me from some snarky person will undoubtedly be "Well if you want the wiki to have that info then do it yourself!". My response then would be, "I don't know that information which is why I'm saying it would be nice if..."
The next snarky response to expect would be "If you want to know stuff then search the forums you newb. That's how *I* did it!" And my response to that would be, "And wouldn't you have been incredibly overjoyed to have NOT spent hours of your free time trying to piece together knowledge out there? And why the heck didn't you then post a straight-forward guide of simple steps on how to do it. And why the heck aren't you being a good person and helping me out now rather than being snarky and telling me to figure it out myself??"
So here's my answers to your questions which won't be very good but maybe if enough of us clueless people discuss this kind of stuff we can start to hash out more specifics.
1. Clockwork Recovery? I really don't know. I've read so many cryptic discussions about Clockwork that I can't tell you what it does. I know it can be used in flashing ROMs, but in following the Cognition line it's easier to use the Odin One Click method.
The name of it however makes it seem like its purpose is to recover from something to something. I'd assume that means you can recover our phone to stock if we have problems, but I bet that assumption is wrong.
2. Flash internal SD when updating ROM? Funny story that... I found this thread because I was doing a search on that very thing. I have seen mentioned in a couple places people saying you should do it. However in most "How to flash a ROM" discussions I've read they don't have formatting the internal SD as part of the scenario. And nowhere (yet..) can I find instruction on how to do it properly. I'm assuming I shouldn't just hook it up in USB mode to my computer and having my computer run a format on it. So I won't.
I know that the Odin tool does a "Master Clear" which I assumed would wipe the internal SD. But when I look at my internal SD it still has all sorts of stuff on it from before still. So evidently to "Master Clear", which is suggested in many "How to flash a ROM" guides, doesn't format the internal SD but "clears" some other mystical information.
3. App2SD. Well when I look up App2SD at Appbrain the description says, "helps you to move apps to either external or internal storage thru' the system Settings." Ok... great... So if I have apps installed (which default to internal SD) then I should be able to run this to move those apps to my external SD.
What happens when I flash a new ROM though like you said? The apps are on my external SD, but can I instantly use the apps on the fresh ROM or do I have to use App2SD again to move them to internal SD or what?
4. Nandroid! It does sound cool doesn't it? In most "How to flash ROM" guides and just about every other guide people say "Make sure to make a Nandroid backup before proceeding". Ok, doing a search on Nandroid I find this in the G1 forums:
"* What is Nandroid Backup v2.0?
Nandroid Backup is a set of tools and a script that will enable anyone who has root on their G1 and has the engineering/dev spl bootloader [1] (or has a dev phone) + a recovery image with busybox and adbd running as root [2] to make full system backups. These can then be restored using the fastboot [3] commandline tool and your phone in SPL/bootloader mode (hold camera + power)."
Uh.. say what? Ok I get what its end result is. It backs up my system. But what's this engineering/dev spl bootloader? I remember from WinMo that a bootloader booted the phone into a state where you could load a ROM onto it. Doesn't seem to fit exactly in this context.
I don't think I have a dev phone and I know I don't have any sort of recovery image. Busybox I recognize because Titanium Backup makes you install it. Don't know what it is though. And "adbd" has to do with running the Android developer kit or terminal or something which allows you to interact directly with Android on your phone I think. I couldn't get it to work on my computer so haven't been able to play with it.
So yeah, when everyone one says "Make a Nandroid backup" like it's the most simple thing in the world that every newborn baby is born with instant knowledge of doing... I must be missing something...
5. Backup between flashes. Well, from all the discussions I've read it sounds like you're supposed to use Clockwork Recovery or Nandroid or maybe both. Possibly you're also supposed to hunt down an ostrich and ride it to your local gas station to pick up a pack of bubble gum and donate it to your local charity of choice in order to get it to work.
Titanium Backup appears to backup your Apps so you can then install them again (I wonder if using App2SD affects that?). You can also back up system stuff, but everyone says not to do that. I assume that means it backs up various system files that would just mess up your new ROM if you restored them.
6. Kernel swapping. I know in general computing terms a Kernel is the very core of an operating system. Since there's swapping going on I assume there are different versions of the Android kernel out there and each one must have something different about them or there wouldn't be any swapping going on. As to what those differences are I couldn't tell you. Personally I'm going to stick with premade bundles like Cognition. That way I don't have to worry about kernel swapping and sacrificing chickens since some awesome genius (like DesignGears) has already done all that. Minus the chicken sacrifice possibly.
7. Flashing finesse. Like I said I've recently flashed from stock to Cognition 9.1 and everything seems to work (except my battery seems to be draining faster, even though I flashed from 100% charge, and did "Master Clear". So next step will be clearing the battery stat file which is another thing I need to research and doing another full charging cycle to see if that helps).
I scoured the forums before doing the flash looking for the proper steps and I finally came upon a post from someone that actually listed each step very clearly on how to do it properly. Huzzah!
Here's what KewlRobD posted:
"- I was running 2.1.7 so I disabled voodoo lagfix
- I powered off my phone and waited for it to reach 100% battery
- I removed my SIM card
- I then used ODIN to flash back to JF6
- I then used ODIN to Master Clear
- I then used ODIN to flash Beta9
- I then used ODIN to Master Clear again.
- I then put my SIM back into my phone and began customizing"
How many hours did I spend reading thread after thread to slowly piece parts of this together into some confused possible instruction list?? Well here you go, KewlRobD was very awesome and actually listed very clearly the steps to take.
The disabling lagfix part he mentions didn't apply since I was on stock and never applied a lagfix. However this is something else I'll have to research if I decide to flash to a new ROM because all "How to..." guides tell you to disable lagfix. Because again, all newborns pop out of the womb with instant knowledge on the disabling of the lagfixes.
Now the only thing he didn't mention was formatting the internal SD, nor did he mention anything about recalibrating the battery, clearing the battery stats file, bump charging etc. (besides saying to charge to 100% first)
So I'm still searching for the formatting of the internal SD information, and I remember reading somewhere about clearing the battery. I think I actually e-mailed it to myself. Yep, here's what Demented71 says about clearing the battery:
"As far as the battery, I would:
Charge your phone while it's on to 100%
Turn it off and charge to 100%
Turn it on and let it fully boot and turn it off again, charging to 100%
Then, when you unplug it, put it into recovery mode first, use CWR (the green recovery) to 'wipe battery stats' in it's advanced menu.
Then use your phone completely until it won't turn on, trying not to connect it via USB or wall charger.
When charging it up after that for the first time, try and leave it off and charge it to 100%, but let it sit for a few hours past 100%, and then use it normally. It's best to do this when your sleeping if you don't need your phone during that time. Another option is to buy the 2x battery+charger from eBay. Works great to always have a full battery."
Again, very helpful post with nice clear instructions instead of "Ur battery sux? Then reset it... duh!" However, there's one spot in there where he says to use CWR. I can only assume that means Clockwork Recovery. KHAAAAAAAAAN!! So in the end I need to do more research to figure out what exactly CWR is and how it works. *sigh*

Clockwork Recovery is a very useful tool. With it you can do many system type things before the os proper (android) is loaded.
You can install "mods" which are modifications to the system, such as zmod, or replacing your battery icon. They are given to you in zip files that have the instructions in place as scripts and such that install the mod for you. No creeping around your internal file system wondering what goes where and I hope I get it right.
You can install roms the same way.
A nandroid back up is the backup (for us) that clockwork recovery provides. If you do a rom manager or clockwork backup, you just did a nandroid backup. It lets you rollback to a point of your chosing as long as you can root your phone and install rom manager.
rom manager downloads the clockwork recovery app to your phone. As long as it's the most recent version you can move the update.zip it puts on your phone to your computer, and then you can put it on your sdcard anytime you want. Once it's there, reboot into recovery, select reinstall packages, and you should be in the clockwork recovery program.
From there you can create or restore a backup, install a mod, or rom from sdcard and quite a few utiliy scripts like formating your sd, removing battery stats, and the like. Careful. Some of this will wipe your data and leave you without apps and such. Like new.
Titanium Backup is your friend. A nandroid backup is a fallback spot, or a relatively easy way to switch back and forth between roms, sort of. If you flash a new rom you don't want to do that. Titanium Backup allows you to backup all your apps and thier data. If you pay for it, and you'll want to, it allows you to do it all as a batch operation, instead of one app at a time.
While it's beyond my time constraint's AND expertise level to answer all your questions, I hope these helped some?
Edit: Before messing with this it's a good idea to be sure you can do the button combinations to get into recovery and/or download modes. DesignGears has a thread in development that explains this and offers a fix if you can't do it. Will help keep/get you out of reboot loops if something goes fubar.
Recovery: From power off, hold both volume buttons down and push power. Hold all three until you see the at&t white screen. Hold for a second or so then release the power button while still holding the volumes. You should boot into recover there. Blue text with some choices. Move with volume up and down, choose with power.
Download: From power off, hold both volume buttons and plug in your usb cable. You should get a big yellow graphic with "Don't turn target off." That's download mode. (If you are planning to use odin or odin one click then have that program running on your computer when you do this.
(Just in case ya didn't know. Don't mean to talk down to anyone.)

Awesome response, Sulphur4724. Thank you very much.
I had no clue Clockwork Recovery was capable of doing so much stuff. I'll definitely have to check it out now.
And that answers our question on how to format the internal SD. Now we just need to find out under what circumstances it's a good idea to do so.
Along the same lines I've also heard people mentioning repartitioning the SD. I'm assuming that's only to do with the various lag fixes out there?
And thanks for clearing up the Nandroid inquiry. I always thought when people said "Make a Nandroid backup..." that they were referring to a program called Nandroid. No wonder I couldn't find an app called that!
So to simplify a little:
1. What can I do with Clockword Recovery (CWR)?
CWR backs up your ROM to an update.zip file that you can store elsewhere in case you want to restore your ROM to saved state. It also allows you to install modifications to Android such as a new battery icon. And finally, it allows you to run system utilities such as formatting the SDCard, or clearing the battery stats. CWR also works in conjunction with an App called "Rom Manager" to perform some operations.
2. Should I format the internal SD when installing new ROMs?
Not sure yet. But in order to actually DO the formatting you would use Clockwork Recovery.
3. What is App2SD and how do I use it?
Not sure yet. The description sounds simple. Move apps to the external SD card. But earching the interwebs for information is giving descriptions involving repartitioning the system into 2 partitions, flashing things, running adb commands, etc. Maybe all that information is old and it's now a simple process? We need more info.
4. What is Nandroid and how do I do it?
Nandroid is basically backing up your ROM so you can use it to restore later. To do this you use Clockwork Recovery. See question 1.
5. What's the best way to back up everything between flashing ROMs?
Using Rom Manager and Clockwork Recovery you can make a backup (Nandroid) of your current ROM. See questions 1 and 4.
In order to back up applications you will want to use an app called Titanium Backup (often referred to as TiBu). With TiBu you can make backup copies of any apps you want. Along with that you can tell it to back up any data for those apps (which would be game saves, app settings, etc.). You can also back up system files and data, but this can often lead to ROM issues if you replace a new ROMs files with old backup files so do your research and be careful.
-----
Besides the formatting internal SD and App2SD questions, does that all sound right so far?
Does anyone know if all this is universal Android stuff, or if it only pertains to the Captivate?
By the way, thanks for asking these questions, Shival!

And that answers our question on how to format the internal SD. Now we just need to find out under what circumstances it's a good idea to do so.
Click to expand...
Click to collapse
You can also format the SD card by settings/sdcard and phone storage.
Along the same lines I've also heard people mentioning repartitioning the SD. I'm assuming that's only to do with the various lag fixes out there?
Click to expand...
Click to collapse
Lagfixes will take care of themselves. I'm not real sure how this works, tho I always do it and it ain't hosed me yet. From my days as a computer geek I seem to remember that when you make a partition you should make the blocks, where stuff actually gets written, as small as possible. When a file is written to a file system it is written to these blocks. On the last one it uses, if it doesn't fill it up that space is wasted. So smaller blocks = smaller waste = more free space. Not really expert about this (hell, about any of this) so someone else may be able to clarify better, but it's workin' for me so far.
And thanks for clearing up the Nandroid inquiry. I always thought when people said "Make a Nandroid backup..." that they were referring to a program called Nandroid. No wonder I couldn't find an app called that!
Click to expand...
Click to collapse
I spent a while lookin' for it too.
CWR backs up your ROM to an update.zip file that you can store elsewhere in case you want to restore your ROM to saved state
Click to expand...
Click to collapse
An update.zip is a stored mod or rom before it's applied to your phone. Made by the developer with install scripts and such to automate the process. The actual backups you can find and inspect under clockworkmod/backup on your sdcard once you've run a backup. They are saved as img files that can be written back to your phone if you have an issue you can't recover from using cwm. But they are NOT the update.zip files. Those are the android format for installing stuff from recovery.
2. Should I format the internal SD when installing new ROMs?
Click to expand...
Click to collapse
The jury is out on this. Some guys swear by it, some guys say "nah." What it will do is wipe all YOUR data and stuff off the phone, leaving it with just the OS ROM as created by the dev. cwm can do it, or you can do it from settings/sdcard and phone storage.
3. What is App2SD and how do I use it?
Click to expand...
Click to collapse
Most phones have a finite amount of storage that the system can use. Most of them have a relatively small amount actually. As cappy owners we have a whopping 2 gb of that storage. But the other guys usually have considerably less. Applications get written to that space and it quickly runs out on other platforms. so app2sd moves apps to the external sd. Or the internal for us, since our total storage is 20 gb. (i think.) The unreserved space is formatted by the phone to look like an external SD card to the phone. anyway, it's not as big an issue for us as 2gb is a LOT of space that will take a while to fill up.
You can also back up system files and data, but this can often lead to ROM issues if you replace a new ROMs files with old backup files so do your research and be careful.
Click to expand...
Click to collapse
For backups this is fine. If you flash a new rom do NOT restore system settings from an older backup. It will restore stuff that may not work with what your flashing and will gum it all up but good. FC hell. You are pretty safe restoring apps+data as that just restores the apps data itself and doesn't overwrite any system files.
-----
Does anyone know if all this is universal Android stuff, or if it only pertains to the Captivate?
Click to expand...
Click to collapse
I dunno! This is my first android phone!

Sulphur4724 said:
You can also format the SD card by settings/sdcard and phone storage.
Click to expand...
Click to collapse
Ah cool, thanks!
From my days as a computer geek I seem to remember that when you make a partition you should make the blocks, where stuff actually gets written, as small as possible. When a file is written to a file system it is written to these blocks. On the last one it uses, if it doesn't fill it up that space is wasted. So smaller blocks = smaller waste = more free space. Not really expert about this (hell, about any of this) so someone else may be able to clarify better, but it's workin' for me so far.
Click to expand...
Click to collapse
Yeah if I remember correctly small blocks mean less space wasted, but it also means more I/O which slows performance. And bigger blocks mean more potentially wasted space but faster performance since there is less I/O going on because you're writing bigger amounts of data at once rather than a bunch of tiny writes. In today's computers where space is cheap you want to make bigger blocks to enhance performance. Not sure what's suggested for NAND. And my memory could be faulty on all that, but that's what I remember from back in the day of tiny hard-drives.
An update.zip is a stored mod or rom before it's applied to your phone. Made by the developer with install scripts and such to automate the process. The actual backups you can find and inspect under clockworkmod/backup on your sdcard once you've run a backup. They are saved as img files that can be written back to your phone if you have an issue you can't recover from using cwm. But they are NOT the update.zip files. Those are the android format for installing stuff from recovery.
Click to expand...
Click to collapse
Ahhh, ok. So update.zip is literally the file Android uses to make updates with whether it's a mod or ROM. The backed up ROM then will be a .img file?

Yeah if I remember correctly small blocks mean less space wasted, but it also means more I/O which slows performance. And bigger blocks mean more potentially wasted space but faster performance since there is less I/O going on because you're writing bigger amounts of data at once rather than a bunch of tiny writes. In today's computers where space is cheap you want to make bigger blocks to enhance performance. Not sure what's suggested for NAND. And my memory could be faulty on all that, but that's what I remember from back in the day of tiny hard-drives.
Click to expand...
Click to collapse
Never thought of it like that, touche'. Now I gotta try changing sizes.
Ahhh, ok. So update.zip is literally the file Android uses to make updates with whether it's a mod or ROM. The backed up ROM then will be a .img file?
Click to expand...
Click to collapse
Roger that. Now ya got it.

WOW!
This thread RULES! Sulphur4724 and sschrupp, many thanks, I learned a lot. If I have the time this weekend I'll try to edit this information into a backup / memory FAQ, if you think that would be useful.
sschrupp check out this guide if you haven't seen it before, it's pretty idiot proof; I had no trouble and I am an android n00b.
edit: nevermind the forum isn't letting me post links because I'm new here. It's a great guide though, so if you want, go to the website android police, and under the guides tab, read the guide called "complete guide how to fully back up and restore your android phone using nandroid backup and clockworkmod rom manager"

Glad I could help. I'd let this stand a few days and see if there are any corrections. I'm going by what I know which may or may not be 100% correct. I came to this phone from a Blackberry. Everything I'm trying to pass on I learned from reading the cognition thread and branching from there. Yes. All of it! Even before the 4k post cleansing it got a while back.
But see I can't code, and I wanna participate. So I'm doing what I can to be part of this community and if it takes some weight off the guys that DO code... well that's full of win.
/shrug

Sulphur4724 said:
But see I can't code, and I wanna participate. So I'm doing what I can to be part of this community and if it takes some weight off the guys that DO code... well that's full of win.
Click to expand...
Click to collapse
Yeah that's how I see it too. Also I almost always buy the pay version of apps that really help me that independent devs here on XDA write.

Why does ROM manager run after startup? Is it okay if I disable this through autostarts? I don't run pre-scheduled backups so I can't think of any reason for it to be running in the background all of the time.

This thread is epic!
So worth it =]
I really hate that the phones storage is called internal SD, I get soo confused reading thing that say "do something to the SD" I am like, WHICH ONE!? and then I explode.
I tried to install a lagfix on a Cognition ROM once, it failed. Did it right after flashing, created the file system then I tried to do the lagfix and it failed. I never tried again. Don't know if its worth it anyways.
Battery has been a super drain! It is incredibly hard for me, a light user who is mildly OC, to let the battery get below 80% and yet, within ten minutes off the charger it starts going down lol. I keep it clean and everything, nothing is running and I always disable background data. I probably do need to redo the battery bin file. Wish I had time, either at work or I am in class.
Phone runs fine I think so I guess I'll just forget formating the internal SD. Maybe I'll try it someday though. I'd imagine the device would clog up eventually.
I just wish I was smart enough to make use of some of the more advanced facets of Android.
I guess there are just too many devices and technology moves so fast that its almost impossible to make a guide. Searching for the info is sort of fun and I do try.
I love it when you are searching for something specific but you learn so much more along the way and I, usually forget what I was searching for in the first place.
This CyanogenMod thing sounds cool. I want it, when its finished, I know barely anything about it though.
I cannot keep up at all with the Cognition releases. I barely know what the changelogs are even talking about when I do lol.
Do our phones work more efficiently with a linux distribution? I just use my Windows Vista partition mainly but I have Ubuntu. Screw windows 7, I am sticking with Vista lol. I'd imagine it would be super hard to find the same tools we use to mod our phones via windows, for Linux.

Komodo Rogue said:
Why does ROM manager run after startup? Is it okay if I disable this through autostarts? I don't run pre-scheduled backups so I can't think of any reason for it to be running in the background all of the time.
Click to expand...
Click to collapse
Be careful in your thinking. Just because an app is loaded in memory does not mean it is actually doing anything. This is not windows with hundreds of processes going on. Android actually prefers to have things in memory to make accessing them faster and consuming LESS battery power as a result of not having to load them every time you want to access them. Each activity is assigned a number corresponding to its priority which determines what gets kicked out when you want to load something that is not already present and more memory is needed than what is available.
You can see this in action by utilizing a system monitor that tracks cpu activity for each process. Most apps that are in memory use ZERO cpu time unless/until you open them. For the ones that do, such as an email app, they will only use cpu time when retrieving messages which takes little energy. If you endlessly kill these with a task manager, you willuse MORE battery as a result of these having to be reloaded by the os instead of accessing them from ram, not to mention the battery drain caused by the task killer constantly polling to see what is in memory.
Sent telepathically using vulcan mind meld app.

newter55 said:
Be careful in your thinking. Just because an app is loaded in memory does not mean it is actually doing anything. This is not windows with hundreds of processes going on. Android actually prefers to have things in memory to make accessing them faster and consuming LESS battery power as a result of not having to load them every time you want to access them. Each activity is assigned a number corresponding to its priority which determines what gets kicked out when you want to load something that is not already present and more memory is needed than what is available.
You can see this in action by utilizing a system monitor that tracks cpu activity for each process. Most apps that are in memory use ZERO cpu time unless/until you open them. For the ones that do, such as an email app, they will only use cpu time when retrieving messages which takes little energy. If you endlessly kill these with a task manager, you willuse MORE battery as a result of these having to be reloaded by the os instead of accessing them from ram, not to mention the battery drain caused by the task killer constantly polling to see what is in memory.
Sent telepathically using vulcan mind meld app.
Click to expand...
Click to collapse
Thanks for the response, that's helpful information to know. I don't use a task killer but I DO have quite a bit of apps disabled at boot through the app "autostarts" that I am going to turn back on now. Quickoffice comes to mind as an example; I use that maybe two or three times a week so I didn't see why I should have it "running" all of the time, but now I'm going to re-enable it.
Nevertheless, the only time I see myself using ROM Manager is before a system flash... and sadly if you read the thread I wrote about flashing to a new ROM, it turns out I may NEVER be flashing a new ROM. So in THIS case, shouldn't I just disable it from startup?

I tried to install a lagfix on a Cognition ROM once, it failed. Did it right after flashing, created the file system then I tried to do the lagfix and it failed. I never tried again. Don't know if its worth it anyways.
Click to expand...
Click to collapse
The answer to this is... sometimes. The phone can get pretty laggy if there are a lot of os writes and reads. A lagfix helps out with this. It depends on your patience and how fast/cool you want to be. (I do it just for the geek factor! RAWR!)
Battery has been a super drain! It is incredibly hard for me, a light user who is mildly OC, to let the battery get below 80% and yet, within ten minutes off the charger it starts going down lol. I keep it clean and everything, nothing is running and I always disable background data. I probably do need to redo the battery bin file. Wish I had time, either at work or I am in class.
Click to expand...
Click to collapse
I have tried every thing I could find/read/think of and my battery life still sux. Why? It's not a phone, it's an ENTERTAINMENT CENTER! Seriously, the Amoled screen on this puppy is pretty as hell but it's also hell on a battery. When it's open, it's eating energy as fast as it can put it away. My philosophy after hours and hours of trying to figure this out is this: Enjoy the phone and keep a charger handy. Try this tho, next time you flash something rom wise pull your sim card. DG says that when the modem.bin file flashes with it in it can cause it to keep the modem open all the time causing massive battery drain. I tried this last flash and it does seem to make a difference. /shrug
Phone runs fine I think so I guess I'll just forget formating the internal SD. Maybe I'll try it someday though. I'd imagine the device would clog up eventually.
Click to expand...
Click to collapse
I haven't done a master clear or format in several flashes and I've had no ill effects. I can imagine a point down the road where issues may ensue, but not recently.
I just wish I was smart enough to make use of some of the more advanced facets of Android.
Click to expand...
Click to collapse
Don't we all!
I guess there are just too many devices and technology moves so fast that its almost impossible to make a guide. Searching for the info is sort of fun and I do try.
Click to expand...
Click to collapse
There are some guys trying, they just aren't advertising well!
This CyanogenMod thing sounds cool. I want it, when its finished, I know barely anything about it though.
Click to expand...
Click to collapse
CDE is about as close to CyanogenMod as we have right now. Want a sneak peak? There's your huckleberry.
Do our phones work more efficiently with a linux distribution? I just use my Windows Vista partition mainly but I have Ubuntu. Screw windows 7, I am sticking with Vista lol. I'd imagine it would be super hard to find the same tools we use to mod our phones via windows, for Linux.
Click to expand...
Click to collapse
If you are coding or plan on coding i'd say yes. If not? nah. winders works just fine. Or as fine as it ever works.

TWRP, eMMC errors, and a lot of questions...

So I have one great Note 4 that runs fine. A second Note 4, given to me appearing to be a paper weight, has been with some effort rescusitated. But no, the eMMC errors have not gone totally.
This "bad" phone, however, is allowing me to fully exercise some of my curiosity. And in the process, no matter what happens, I hope I can get a few more answers about things. I know about the little app that keeps the phone from going to sleep and stablizes it... that works on the phone unless it gets turned off. And then the whole cycle of trying to start it again (the freezer trick, the holding of buttons, the pulling of the battery... sigh).
My latest gambit has been to go into TWRP and reformat /system /data and /cache (the only directories where I'm allowed to do so) to f2fs. In fact, just to really wipe this baby as clean as I possibly could, I reformatted them back to ext4, then back again to f2fs. I then installed a custom rom (the official CM 14.1). It appears to have installed over the top of the f2fs without trouble.
But of course I am freewheeling it here. I do not know very much about what is going on down inside there.
My questions:
1. What "hidden" directories are there that TWRP isn't showing me? Is there any possibility that if I could reformat them (and not destroy the phone) it might help with the eMMC errors? How would I do that if I in fact can?
2. When I reformat the directories from one format to another, am I actually wiping them or not? (I've read long pages about people suggesting that Android phones are terribly hard to actually wipe all data off.)
3. Is there any other possible cause for the eMMC errors than bad physical memory? I understand that bad memory chip *is* one obvious cause... but are there other causes that could in fact kick up an eMMC error that isn't really about the memory chip?
I'll post any other questions if and when I think of them. Worst happens, I mess this phone up so bad it won't reboot at all. I'm not too worried about that.
All thoughts welcome. I can experiment without caring too much.

I have read elsewhere that the problem could be caused by having a micro sd inserted in the phone.

Intensivefire said:
I have read elsewhere that the problem could be caused by having a micro sd inserted in the phone.
Click to expand...
Click to collapse
Yes, I've read that also. Tried all sorts of experiments with and without micro-sd card inserted. Using a Wake Lock app from playstore (set on mid-range) allows the phone to do and be nicely. But shut it off and I have to freeze it for 5 min before it will restart. So... hopefully the Chinese mb card I bought today will actually work. Providing I can in fact open the phone without busting it. (There's some good clues on youtube which is nice.)

shonkin said:
Yes, I've read that also. Tried all sorts of experiments with and without micro-sd card inserted. Using a Wake Lock app from playstore (set on mid-range) allows the phone to do and be nicely. But shut it off and I have to freeze it for 5 min before it will restart. So... hopefully the Chinese mb card I bought today will actually work. Providing I can in fact open the phone without busting it. (There's some good clues on youtube which is nice.)
Click to expand...
Click to collapse
emmc errors on note 4 is well known hardware failure , its time for you to replace emmc chip or system board

zfk110 said:
emmc errors on note 4 is well known hardware failure , its time for you to replace emmc chip or system board
Click to expand...
Click to collapse
Yes, I said that in my first post. My point was that it is possible other causes for the error message just might exist. But all that is moot now... I did in fact order a new motherboard. But in the meantime, when I went to dissect the phone according to instructions on youtube, I found out too late that the author of said instructions was fairly clueless as far as a successful end result. The phone is dead, dead, dead. Lucky for me, it wasn't my main Note 4, which is just fine.

Here is a 100% hardware fix for this issue that anyone can do with no tools or specia
Here is a 100% hardware fix for this issue that anyone can do with no tools or special equipment.
It really works. Give it a try. ?
https://youtu.be/jLPHWtb0StI

Misreporting Battery?

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.

Database Develop

welcome