So the title says it all. I'm looking to clean house a bit and just delete everything on the internal memory and install something from the sdcard. I normally just do a factory reset and wipe caches but there's remnants of passed ROM installations and general clutter that still linger. I saw the options to format emmc but chickened out before doing it. Will this do as I describe or is it something else entirely?
Thanks in advance!
Sent from my Nook HD+ using xda app-developers app
Just did that recently on the Nook and have done that multiple times on other tablets. But I normally have an externalSD hooked up (with all the files I need).
Once I formatted the whole nine yards and was in a panic until I realized I could take out the microSD over to the PC to get the files back on, plugged it back and
reboot the recovery to get back.
That's pretty much what I was hoping would happen. I'd just have my new ROM and gapps on the sdcard and flash from that in recovery after formatting everything on internal memory.
Groovy, thanks.
Sent from my Nook HD+ using xda app-developers app
JeauxAdam said:
That's pretty much what I was hoping would happen. I'd just have my new ROM and gapps on the sdcard and flash from that in recovery after formatting everything on internal memory.
Groovy, thanks.
Sent from my Nook HD+ using xda app-developers app
Click to expand...
Click to collapse
If you are installing a new ROM on emmc, you do not need to format /system with CWM, the zip does that for you. The only thing you want to do in CWM is wipe data/factory reset. That formats /data, /cache and clears the dalvik cache for you. It will leave your internal media files intact. Be very careful with formatting anything else. It can brick your device.
Sent from my Nook HD+ running CM10.1 on emmc.
Hello guys, my booting problem is bit different from most booting issues. The only rom that works for me was CM11 when i first flashed is after installing 2nd bootloader. I made a backup of it. Now when I try to install other roms( some i port, some i download like kinology and CandyKat) none of them go past the boot animation. They get to the boot animation fine, but they won't boot past it. I give it like 45-90 minutes and it still doesnt boot, so I just turn off the KFHD by holding power button and restore cm11 through twrp. Anyone know a solution?
Might be some selinux xattribs causing issues, might wipe internal storage to fix, I heard twrp 2.7 has better selinux support, if an internal storage wipe doesn't do it I would try a command that wipes internal storage over a adb shell in twrp in such a way that wipes xattribs.
Make sure if you try this to backup your twrp backup first and anything on sdcard you don't want to lose.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Might be some selinux xattribs causing issues, might wipe internal storage to fix, I heard twrp 2.7 has better she Linux support, if an internal storage wipe doesn't do it I would try a command that wipes internal storage over a adb shell in twrp in such a way that wipes xattribs.
Make sure if you try this to backup your twrp backup first and anything on sdcard you don't want to lose.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
How would I do this? Clarify please? Thank you a lot!:good:
If you don't already have twrp 2.7 flashed then flash it, then go into twrp and hit wipe and hit advanced and choose internal storage and see if it fixes it. If that doesnt do the trick post back and i'll send you the command you will wanna try next.
As to backing up your twrp backups, just copy and paste the twrp folder off the kindles sdcard.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
If you don't already have twrp 2.7 flashed then flash it, then go into twrp and hit wipe and hit advanced and choose internal storage and see if it fixes it. If that doesnt do the trick post back and i'll send you the command you will wanna try next.
As to backing up your twrp backups, just copy and paste the twrp folder off the kindles sdcard.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thanks! I'll try it as soon as I get home.
Question: I want to wipe everything from my HD+ and start completely fresh. What is safe to wipe and how do I do it in TWPR or CWM? A "factory reset" isn't good enough. It leaves old data around. But I've read too many stories about bricking a device by formatting /data using CWM.
Background: I've been running CM 10.2.1 for a few weeks now. Given what Jon Lee posted about Google and security, I thought I'd try a clean install of CM 10.2.1 without installing gapps, just to see what that's like. (And what services don't run.)
So I did the usual "factory reset" from TWRP and reinstalled CM 10.2.1. To my surprise, when I booted, the latest version of Google Play was still showing on the launcher!
I had used Link2SD to integrate the latest version of Google Play with the OEM system app. So apparently, that this was not wiped. And of course, internal media data is not wiped (not by TWRP, anyway) in a factory reset. But I thought /system was.
The TWRP FAQ has a page about wiping. It says
Depending on your device and its configuration, you may have options for wiping internal storage, external storage, sd-ext, android_secure, and/or an option for formatting data. There's almost no reason that you would ever need to use these items. These options are there for convenience. For instance, if you're getting ready to sell your device, then it's a good idea to wipe everything on the device so that the new owner doesn't get your private data.
Click to expand...
Click to collapse
But they don't tell you which to select.
TWRP makes it confusing by offering to 1) wipe data, 2) internal storage, 3) SDcard or 4) SDcard data in Advanced Wipe. Which is it for wiping your media stuff?
From what I've read, "internal storage" should be the same as "SDcard." So why both? And how is "SDcard data" distinct from those two?
To make matters worse, in the Nook I thought there was an additional element of confusion because the Nook doesn't call the internal SDcard memory what everyone else calls it.
So let's say I am selling my HD+. Would I select all of the above and still be able to install a ROM clean?
Or would I brick?
I know that on a desk top computer if you want to start bare metal, you format the hard drive, wiping everything, and install onto that. But judging from what Succulent wrote in his blog about recovering from an EMMC crash, you can't start totally clean with Android. Apparently, Android needs some preexisting files on the "drive" in order to install. (Like the devconf folder, which contains your MAC and your serial number.)
[Am I understanding him correctly? He was talking about recovering from a tablet wrecked by the EMMC brick bug. Perhaps no /data partition at all, as he offers a script to rebuild/expand that partition?]
I have read stories of people bricking their tablets by formatting /data from CWM. I don't understand why that should brick it. Why couldn't you boot into recovery? How can the /data partition affect the /recovery partition?
So - has anybody done a complete wipe on their Nook HD+? Please explain, for those of us who are obsessive compulsive, exactly how you do it.
To wipe your device with CWM go to mounts and storage and format /system, /cache and 'data and datamedia'. A normal factory reset only wipes /cache and the portion of /data that does not hold your media files. It does not wipe /system. Usually the ROM install does that, but the install script has a feature that saves gapps if you are installing the same version of the ROM (eg, CM11 over CM11). So to get rid of everything, including media files and gapps, do what I said in the first sentence. Of course after formatting /system you must put a ROM back on it for it to boot.
And it is not /data formatting that is the brick problem, it is formatting the /bootdata partition. They are different things. Don't format that.
And succulent was talking about /rom partition which is different yet that needs to be left alone. That is where the devconf folder is. It contains things you need to keep.
If you want to understand the partition structure of the HD/HD+ go to my HD/HD+ Tips thread linked in my signature and read item 16.
And please read my PM to you about removing those assert removal instructions from my dummies thread.
Sent from my BN NookHD+ using XDA Premium HD app
Best Answer
leapinlar said:
To wipe your device with CWM go to mounts and storage and format /system, /cache and 'data and datamedia'. A normal factory reset only wipes /cache and the portion of /data that does not hold your media files. It does not wipe /system. Usually the ROM install does that, but the install script has a feature that saves gapps if you are installing the same version of the ROM (eg, CM11 over CM11). So to get rid of everything, including media files and gapps, do what I said in the first sentence. Of course after formatting /system you must put a ROM back on it for it to boot.
Click to expand...
Click to collapse
Thanks for the thorough answer. And explanations. I always find it easier to remember something when I understand the reason for it. So I didn't know before that the install scripts keep gapps.(But that's what I was deducing.)
I know to stay away from /rom and /boot. Hopefully, TWRP would not let one format those in their numerous choices for Advanced Wipe.
From what you've written before in one of your other threads, I know that you're not a fan of TWRP. So I still don't know what the similar commands are in TWRP for a total clean. But for now I can delete /system in TWRP and do the reinstall without gapps. When I'm ready for a total wipe, I'll revert to CWM.
Can we trade /factory for /swap?
leapinlar said:
If you want to understand the partition structure of the HD/HD+ go to my HD/HD+ Tips thread linked in my signature and read item 16.
Click to expand...
Click to collapse
Read it. (And made an image of my factory partition. And then moved it to my extSDcard for safer keeping.)
So, the Nook HD+ partition structure is a bit different from the stock Android partition stuff I had found on the web.
So, for those of us running a custom ROM, I presume the factory image doesn't do us much good anymore. Will the HD+ automagically restore after 8 failed boots?
If not (or even if it will), is there a way to take that 448MB in the /factory image partition and use them for, say, a /swap partition instead? I think an xda developer is doing something like this for the Galaxy Tab 2, where he's using some memory that Samsung uses for animations and uses them for ZRam instead. Since I've backed up the factory image, and since I already have your factory 2.0.2 ROM, I really don't need the image any more. Seems like wasted space.
PMikeP said:
Read it. (And made an image of my factory partition. And then moved it to my extSDcard for safer keeping.)
So, the Nook HD+ partition structure is a bit different from the stock Android partition stuff I had found on the web.
So, for those of us running a custom ROM, I presume the factory image doesn't do us much good anymore. Will the HD+ automagically restore after 8 failed boots?
If not (or even if it will), is there a way to take that 448MB in the /factory image partition and use them for, say, a /swap partition instead? I think an xda developer is doing something like this for the Galaxy Tab 2, where he's using some memory that Samsung uses for animations and uses them for ZRam instead. Since I've backed up the factory image, and since I already have your factory 2.0.2 ROM, I really don't need the image any more. Seems like wasted space.
Click to expand...
Click to collapse
You can play with the partitions all you want. Just don't ask me to help you fix it. You don't seem to heed my warnings anyway.
But other users be warned that factory partition has vital backup information there (it has more than just the factory zip there) and if you lose it, your device is as good as a paperweight. That is why I recommended all users back that partition up. Not for the factory zip, but for the backup files there. The device has other safety backup routines other than just restoring the stock ROM. An example is, I told you and succulent told you that devconf has vital files all ROMs need in /rom. Well, /factory has a backup of /rom there and if the device discovers /rom is messed up, it tries to repair itself. No /factory and no repair. Paperweight!
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
You can play with the partitions all you want. Just don't ask me to help you fix it. You don't seem to heed my warnings anyway.
But other users be warned that factory partition has vital backup information there (it has more than just the factory zip there) and if you lose it, your device is as good as a paperweight. That is why I recommended all users back that partition up. Not for the factory zip, but for the backup files there. The device has other safety backup routines other than just restoring the stock ROM. An example is, I told you and succulent told you that devconf has vital files all ROMs need in /rom. Well, /factory has a backup of /rom there and if the device discovers /rom is messed up, it tries to repair itself. No /factory and no repair. Paperweight!
Click to expand...
Click to collapse
Thanks for the quick response.
I am sorry that I seem to have gotten on your bad side. I did what you asked and moved my previous comment out of your thread. And I warned everyone that you don't think it's a good procedure.
And I did heed your warning. I made a backup of the factory partition and even moved the copy to my ext SD card for safer keeping. Especially since we were talking about wiping the sdcard. (Unless you're trying to say that storing the /factory img on the ext SD card is a bad idea because I won't be able to get it back to the internal SDcard if/when I need it.)
As for the devconf files, they're in the /rom partition. I don't understand how using the /factory partition for a /swap is going to ruin the /rom partition.
From what you're saying, the HD+ still has a "safety routine" built in, even when running custom recovery and a custom ROM? Does that mean that its safety routine is hard coded somewhere? Or part of the /rom code itself? How does the HD+ know to look in /factory when its running a non-factory OS? Does CM tell it to do that?
You're the expert. I'm just guessing here. If the /factory partition were used as a /swap, and if the system turned into a paperweight because it needed the /factory image later someday, then couldn't one go into recovery and copy the /factory partition back over, per your instructions? As a minimum, couldn't one use succulent's emmc recovery procedure to get back to factory status?
I'd be willing to trade that off for more performance.
How does one know when the HD+ goes into this safety routine? Does it tell you? Or is it transparent to the user? It would be interesting to know how often that happens. Does the safety routine then repair the /rom partition once booted if it detects a problem in /rom?
PMikeP said:
Thanks for the quick response.
I am sorry that I seem to have gotten on your bad side. I did what you asked and moved my previous comment out of your thread. And I warned everyone that you don't think it's a good procedure.
And I did heed your warning. I made a backup of the factory partition and even moved the copy to my ext SD card for safer keeping. Especially since we were talking about wiping the sdcard. (Unless you're trying to say that storing the /factory img on the ext SD card is a bad idea because I won't be able to get it back to the internal SDcard if/when I need it.)
As for the devconf files, they're in the /rom partition. I don't understand how using the /factory partition for a /swap is going to ruin the /rom partition.
From what you're saying, the HD+ still has a "safety routine" built in, even when running custom recovery and a custom ROM? Does that mean that its safety routine is hard coded somewhere? Or part of the /rom code itself? How does the HD+ know to look in /factory when its running a non-factory OS? Does CM tell it to do that?
You're the expert. I'm just guessing here. If the /factory partition were used as a /swap, and if the system turned into a paperweight because it needed the /factory image later someday, then couldn't one go into recovery and copy the /factory partition back over, per your instructions? As a minimum, couldn't one use succulent's emmc recovery procedure to get back to factory status?
I'd be willing to trade that off for more performance.
How does one know when the HD+ goes into this safety routine? Does it tell you? Or is it transparent to the user? It would be interesting to know how often that happens. Does the safety routine then repair the /rom partition once booted if it detects a problem in /rom?
Click to expand...
Click to collapse
If you want to know more how the automatic repairs work, go to my Nook Color Tips thread linked in my signature and read item A12. The partition numbers are different but the repair process works exactly the same way on the HD/HD+, including the need for stock recovery to be installed. There are two ways to get your device automatically repaired if you have CM and CWM/TWRP recovery installed on internal memory. One is to flash stock recovery back per my item 5 in my HD/HD+ CWM thread, and the second is to flash the plain stock zip from item 6 there. That puts stock recovery back. Then it can repair /rom if need be.
And there is no real drawback of removing the factory.zip file from /factory partition since it is basically the same as a plain stock zip I have published. But the other files there are vital and should not be touched.
You got on my bad side by publishing that assert removal procedure on the help forum after I asked you to remove it from my thread. I don't want to make it easy for any user to do that as I consider it dangerous for noobs to do. See my response to your posting of that procedure.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
You got on my bad side by publishing that assert removal procedure on the help forum after I asked you to remove it from my thread. I don't want to make it easy for any user to do that as I consider it dangerous for noobs to do.
Click to expand...
Click to collapse
Thanks for letting me know. Later last night, I saw a post of yours on the Nook Color (I think it was) where you thought that anyone who would remove the updater-script safety check was an "idiot."
Okay, so I'm an idiot. But I am free to be an idiot and start my own thread in the Help forum, right? Just as you are free to respond there as you did. That's what makes the forum go 'round.
PMikeP said:
Thanks for letting me know. Later last night, I saw a post of yours on the Nook Color (I think it was) where you thought that anyone who would remove the updater-script safety check was an "idiot."
Okay, so I'm an idiot. But it's my right to be an idiot and my right to start my own thread in the Help forum, right? Just as it's your right to respond there as you did. That's what makes the forum go 'round.
Click to expand...
Click to collapse
As I recall, I did not say the person that removed the assert was an idiot, it was the person who recommended it that I said was an idiot. The user was a noob and knew no better. He was trying to flash a Nook Tablet ROM to his Nook Color and the assert kept failing (doing what it was designed to do). The idiot was the one that told him just to remove the assert. He did that and bricked his Nook Color.
Sent from my BN NookHD+ using XDA Premium HD app
I wanted to update my sister's Nook HD+ to CM11. I don't have an SD card big enough to do a nandroid backup, so I tried to back up to the internal SD card. It was working fine, then it said "backup of /data failed". I thought this was because the internal SD card ran out of space. When I tried to reboot, it found that it's stuck in a bootloop. It goes to the nook screen, then the Cyanoboot screen, then starts loading Cyanogenmod like normal. The boot animation plays then freezes, and the device reboots. I've tried clearing the cache and dalvik cache and it gets a little farther, but it's still in a bootloop. Please help! I would like to avoid doing a factory reset if at all possible.
If internal space was maxed out, would a factory reset even work any better?
If only booting is corrupted, you should just be able to simply dirty flash the same rom build or newer to fix without losing anything.
I don't know where nandroid backups are made internally but if they are accessible via usb on a pc, then you could just delete those files. If it is indeed full storage. And then dirty flash the build again if needed.
There's probably some other ways to go as well.
After holding my phone in my hands and watching Andy the android on my screen with an "Erasing..." caption below him, I cried.
I have attempted to use Undeleter to recover files, but it returned nothing of use, only a few minor files. After the format, and then the utilization of TRIM (I assume), is data recovery possible? I am currently without Busybox, which does makes this a bit more complicated, but I am trying to get the partition dumped so that I can mount it on my PC.
Does anyone have any other ideas or suggestions?
Device: Droid Turbo
Not recoverable. That is the point of the system wipe... Sorry.
JasonJoel said:
Not recoverable. That is the point of the system wipe... Sorry.
Click to expand...
Click to collapse
I was doubting that Android did some crazy multi-write wipe on your device when you format it, but I could be wrong. Just because it's a system format doesn't mean it's not recoverable. You can recover almost anything from a disk that is simply formatted.