Database Develop

[Q] script for wiping tablet for a real clean install

Hello,
I was wondering if such a thing as described in subject exists.
I am looking for something which wipes everything but the CWM bootloader and the sd card directory.

The option is already there in cwr
Sent from my Sensation using xda premium

Is it cenwesi? I know the wiping section, but for instance there's no option to format or resize the /recovery partition for example.

goenieg said:
Is it cenwesi? I know the wiping section, but for instance there's no option to format or resize the /recovery partition for example.
Click to expand...
Click to collapse
if you format the recovery you would lose CWM. A data wipe should be suffient, if not plug it into a computer and delete everything on the "sdcard"

bdfull3r said:
if you format the recovery you would lose CWM. A data wipe should be suffient, if not plug it into a computer and delete everything on the "sdcard"
Click to expand...
Click to collapse
thanks, I now have 13 Gb available, is the rest taken by the recovery partition? is resizing an option?
(pls forgive me for being ignorant

I think the devs would have to put a wipe script in their ROMs so the user doesn't have to do it manually. At least that's what the devs at my smartphone's forum (Vibrant) do. Albeit, sometimes it is best to do some manual cleaning, and TWICE at it (the system isn't infallible).

What can I wipe to be "squeaky clean"?

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

[Q] encryption unsuccessful?

So, I figured I'd set up the scenario first in hopes to help make this understood:
1. Got the device
2. Booted/Updated to 5.0
3. Rooted using CF Autoroot
4. Remained on Stock 5.0 + Root (Stock bootloader/recovery)
- 1st "OFFICIAL" ROM came out so like the gentle flash'aholic I am, I rushed and downloaded [ROM][Unofficial][5.0.2][alpha/wip] Resurrection Remix v5.2.6[victara]
1. I installed TWRP via the Google Play App, (I think i was on 2.8.3.0)
2. Rebooted into TWRP, and did a FULL BACKUP (saved locally)
3. Formatted Davlik, System, Data, Internal Storage, Cache
4. Rebooted into TWRP, pushed the ROM files ([ROM][Unofficial][5.0.2][alpha/wip] Resurrection Remix v5.2.6[victara])
5. Flashed the ROM, GAPPS, SuperSU, Rebooted.
After about a minute of booting into the new ROM (new red loading animation) I started to get "encryption unsuccessful", and the only option was to factory reset phone, after which nothing happened, my guess was because of the custom recovery.
What was my error, and how do I prevent this from happening again?
My thinking is that wiping the Cache/System/Data/Internal/Davlik partitions somehow messed up some function someplace?
To fix it I took steps in this thread (http://forum.xda-developers.com/moto-x-2014/help/lollipop-update-failing-how-troubleshoot-t2961633) - thanks @randyklein
-Download "Official 4.4.4 Full Restore Images" from http://www.graffixnyc.com/motox.php# and extract. Move recovery.img, boot.img, and system.img into adb folder
-Boot into fastboot, plug in USB
-Using mfastboot v2, run the following commands:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
How do I avoid this in the future if I decide to try a custom ROM/Recovery again?

Same problem...

Format data in twrp to fix encryption error

CWick4141 said:
Format data in twrp to fix encryption error
Click to expand...
Click to collapse
will i lose my twrp backup ?

marquesini said:
will i lose my twrp backup ?
Click to expand...
Click to collapse
Data partition just stores your apps (if not pre-loaded into system partition via ROM), and any data associated with them, so it leaves the Internal SD Card partition alone.
What concerns me is that I already wiped data, and I think I formatted the data partition as well, and still had the issue.
I'll have to try again soon.

I did a full wipe and then formated the data, then installed the ROM,gaaps,and supersu beta.
Got it working with root.

Shemploo said:
Data partition just stores your apps (if not pre-loaded into system partition via ROM), and any data associated with them, so it leaves the Internal SD Card partition alone.
What concerns me is that I already wiped data, and I think I formatted the data partition as well, and still had the issue.
I'll have to try again soon.
Click to expand...
Click to collapse
Formatting data in twrp is not the same as wiping data

CWick4141 said:
Formatting data in twrp is not the same as wiping data
Click to expand...
Click to collapse
True, that is why I said in above post that I think I formatted it as well, but being as I'm not certain I'll have to do it again to be sure.

Shemploo said:
True, that is why I said in above post that I think I formatted it as well, but being as I'm not certain I'll have to do it again to be sure.
Click to expand...
Click to collapse
You would know if you formatted data since it erases everything including internal storage

CWick4141 said:
You would know if you formatted data since it erases everything including internal storage
Click to expand...
Click to collapse
Alright, I booted TWRP, and clicked "Data" then "Repair/Change File System" it's currently showing f2fs, my format options are EXT2, EXT3, EXT4, FAT.
I think I want EXT4 right?
UPDATE: I tried EXT4 as every partition seems to use it, and from past experience, and It's working!.
Thank you for nudging me in the right direction.

edit: wrong thread

USERDATA erase...

Long story short... My USB port is dead on my Nexus 6. I flash everything in TWRP such as roms, kernels and modems (YAY for the ability to do so). I am wanting to wipe everything in my phone to start fresh. Let's say I did a factory reset to the phone (wiped everything except userdata), got my rom to boot and then went into recovery to wipe my userdata partition only, would my phone go ahead and rebuild the partition on successful boot?
Thank you in advance!

thawte said:
...Let's say I did a factory reset to the phone (wiped everything except userdata), got my rom to boot and then went into recovery to wipe my userdata....
Click to expand...
Click to collapse
Wiping a partition in twrp will show a.o. the message 'formatting...'. The partition is already build but empty.

NLBeev said:
Wiping a partition in twrp will show a.o. the message 'formatting...'. The partition is already build but empty.
Click to expand...
Click to collapse
Ah gotcha. Also the rom will still boot with empty USERDATA? Just making sure it does not have important files for boot...

thawte said:
Ah gotcha. Also the rom will still boot with empty USERDATA? Just making sure it does not have important files for boot...
Click to expand...
Click to collapse
Wiping data in recovery shouldn't affect the system or booting.
But, personally, I'd take a full nandroid backup before anything. If you can't plug in to a pc and use fastboot to fix anything serious, you should be playing it very safe. :good:

Darth said:
Wiping data in recovery shouldn't affect the system or booting.
But, personally, I'd take a full nandroid backup before anything. If you can't plug in to a pc and use fastboot to fix anything serious, you should be playing it very safe. :good:
Click to expand...
Click to collapse
Doesn't the nandroid backup store to userdata?
Sent from my Nexus 6 using Tapatalk

thawte said:
Doesn't the nandroid backup store to userdata?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Data in recovery and userdata aren't the same. There's no "userdata" in twrp. (unless the newest twrp has changed?)
Userdata is apps, data and internal SD storage. You use fastboot typically to erase userdata.
You use twrp to erase data, and internal storage, separately.
Edit: and yes, it does store to userdata. But you can't erase userdata without a PC. Just erase data in twrp, and leave internal storage alone.
Or wipe it all, but without access to a PC, you could not fix the phone if anything goes wrong. That's why I'd keep a full nandroid backup on the device.

Xiaomi Mi A2 (jasmine) can I update stock ROM via TWRP

Good Morning, I want to upgrade brother device to new version of android (because he can`t install security updates for unknow reasons), but I affraid that he loose all apps and settings (he is a firefighter and have app from firefighter station which signals dangerous traffic etc.) So my question is can I update downloaded stock ROM via TWRP (adb sideload) without fears that he loose everything?

iHusky said:
Good Morning, I want to upgrade brother device to new version of android (because he can`t install security updates for unknow reasons), but I affraid that he loose all apps and settings (he is a firefighter and have app from firefighter station which signals dangerous traffic etc.) So my question is can I update downloaded stock ROM via TWRP (adb sideload) without fears that he loose everything?
Click to expand...
Click to collapse
The only thing that will take your fear, is a backup of all important partitions (boot, system, data, vendor, efs, persist), stored externally, plus a copy of the internal storage content, also stored externally.
With that you should be able to restore everything to the exact point it is at right now, so you'll really need to mess up hard to not come out of basically any situation with those partitions saved.
As for your inital question:
Why don't you just update via ota if you wanna stay on stock?

Phil_Smith said:
The only thing that will take your fear, is a backup of all important partitions (boot, system, data, vendor, efs, persist), stored externally, plus a copy of the internal storage content, also stored externally.
With that you should be able to restore everything to the exact point it is at right now, so you'll really need to mess up hard to not come out of basically any situation with those partitions saved.
As for your inital question:
Why don't you just update via ota if you wanna stay on stock?
Click to expand...
Click to collapse
Because, brother have error, while try install security updates, but he have from March this year
And this is not possible to make update, because after click backup (Data partition) I get error "cannot create data/media/0/TWRP

iHusky said:
Because, brother have error, while try install security updates, but he have from March this year
And this is not possible to make update, because after click backup (Data partition) I get error "cannot create data/media/0/TWRP
Click to expand...
Click to collapse
Okay, so maybe first copying internal storage content to your PC and backup important apps would be sufficient then.
For apps you can use Titanium Backup (good, but makes troubles on android 10 at the moment), Swift Backup (recommend by many others) and more.
These backup solutions save apps and app data on your phone, so copy that to an external place, or you might lose them if you need to format data (which I'll suggest).
After your "backups" are made, I would wipe every partition in each slot, which you can also achieve with a "fastboot -w", and then also format data - the one where you need to type "yes" (which will also erase all internal storage content, but most probably will also solve your troubles).
From here there are tools like miflash or fastboot images to reflash stock (inform yourself about them, before you start all that!).
Be sure to flash the latest one right away, so you won't be in the need of "dirty" updates immediately again.
Afterwards, you can copy back the internal storage content and the folder of the backup app, and restore the previously saved apps.

Phil_Smith said:
Okay, so maybe first copying internal storage content to your PC and backup important apps would be sufficient then.
For apps you can use Titanium Backup (good, but makes troubles on android 10 at the moment), Swift Backup (recommend by many others) and more.
These backup solutions save apps and app data on your phone, so copy that to an external place, or you might lose them if you need to format data (which I'll suggest).
After your "backups" are made, I would wipe every partition in each slot, which you can also achieve with a "fastboot -w", and then also format data - the one where you need to type "yes" (which will also erase all internal storage content, but most probably will also solve your troubles).
From here there are tools like miflash or fastboot images to reflash stock (inform yourself about them, before you start all that!).
Be sure to flash the latest one right away, so you won't be in the need of "dirty" updates immediately again.
Afterwards, you can copy back the internal storage content and the folder of the backup app, and restore the previously saved apps.
Click to expand...
Click to collapse
I tried MiFlash, but without wipe anything, and it don`t upgrade version of system
But if I must, flash 2 slots A/B using MiFlash or one slot (A) is for system?

You can just download the zip file with version u want from the site below and flash it via TWRP making cache and dalvik cache wipes and changing slots at the end.
https://mifirm.net/model/jasmine.ttt#zip-mif

pfss said:
You can just download the zip file with version u want from the site below and flash it via TWRP making cache and dalvik cache wipes and changing slots at the end.
https://mifirm.net/model/jasmine.ttt#zip-mif
Click to expand...
Click to collapse
So, I don't need
to flash second slot?

iHusky said:
So, I don't need
to flash second slot?
Click to expand...
Click to collapse
Just if u want. It's not necessary.
In october I updated mine this way but forgot to change the slot before rebooting to the system and realized that was in the old Android version. I just went to TWRP again and changed slot. After rebooting, the phone was in the updated Android One.

pfss said:
Just if u want. It's not necessary.
In october I updated mine this way but forgot to change the slot before rebooting to the system and realized that was in the old Android version. I just went to TWRP again and changed slot. After rebooting, the phone was in the updated Android One.
Click to expand...
Click to collapse
I tried using fastboot and MiFlash but after all it stuck on bootloader

iHusky said:
I tried using fastboot and MiFlash but after all it stuck on bootloader
Click to expand...
Click to collapse
I just updated mine to November patch downloaded from here: https://mifirm.net/downloadzip/4197
I entered fastboot mode, executed
Code:
fastboot boot my_twrp_image_file.img
In TWRP made de wipes, flashed the ROM, changed slot and rebooted phone. It looks like it's normal.