[TOOL] G2x Nullifier AROMA [UPDATED!] 2 August, fully customizable: Made with AROMA!

Search This thread

Волк

Senior Member
Jan 7, 2012
1,159
548
San Diego
Nexus 9
Google Pixel 6 Pro
Hello,

Here is my no longer new wipe tool, inspired by the G2x Scrubber.

The Nullifier.

This uses a special command in combination with a special file to overwrite the internal partitions with 0's, hence "Null" for 0 and "-ifier" for the fact that it does the action of the root word to something else. It also formats *all* the partitions afterward and *new* checks for, and repairs any errors on them.

6 Oct: This tool is now depreciated and succeded by the G2x AIO wipe tool.

New 2 August:

Updated to 3.1, now fully customizeable by partition. Still haven't gotten around to making status bars, it's going to take a little bit to work out the best implementation.

New 28 July: I've been working on wrapping my head around the infamous AROMA installer and have at least made some progress in understanding it. As alot of people in the past had wanted to have the option to choose which to wipe, and how many times. We're not there yet. Yet. I just wanted to give those interested something new to chew on while I work out how to break it down function by function. Currently I have it made so that you have one installer which allows you to choose between a single and dual wipe.

New 26 March: The Cache Nullifier I edited the script down to just do a single pass Nullification then format and error check. This will work on the G2x, O2x and su660.

26 April update: Changed the commands so that it writes ext4 file system instead of ext3 when it formats and created an error check zip, mostly just because it could prove to be useful. I tried a couple of different sign programs to sign these properly but in testing signature verification fails still.

Minor update 1 March: swapped out the binaries on the 2.0.6 releases so they're the same as the older versions, added an ext4 cache nullifier, and fixed the code on the dual-wipe as I was sober when that one was revised as it had errors which would prevent it from running.

Some brief need to knows:

1. This is a little lengthy process so please bear with it. The longest wipe is on /data which will take about 7 minutes. Obviously, make sure you have plenty of battery life before running it or are charging.

2. You *must not* power off your phone without first installing a new ROM or restoring a nandroid after you use this. See post here:
http://xdaforums.com/showpost.php?p=23998091&postcount=125

3. I will provide help, support, etc., but I am not, nor is anyone else involved with this, responsible for any problems you may have in the extremely unlikely event that you do.

old links:

Depreciated

Direct link to 3.1:

Depreciated

Thanks to da-pharoah for being my main beta tester who stuck with me all the way, even after bricking his phone and getting the progress bar pinned down as best as possible.

Additional thanks to anyone who contributed (you know who you are).
 
Last edited:

Волк

Senior Member
Jan 7, 2012
1,159
548
San Diego
Nexus 9
Google Pixel 6 Pro
Nullifier Q and A:

Q: Will this harm my phone in any way or brick it?
A: No, the incident with Pharaoh's phone was an unexpected problem brought about from the source-file I was using at the time causing CWM and Android to think the phone was encrypted. I no longer use that source-file.

Q: Why not just format everything?
A: Because a format isn't intended to erase data, though, to a degree, does so. This script is intended to and will wipe out the data and leave a clean set of partitions for a ROM to be installed to.

Q: (Submitted by Cargohook) Would it be idiotic or fruitless to run this and then restore a nandroid backup? I mean, would that defeat the purpose?
A: I highly doubt it would be a waste of your time. On an educated hunch, when you restore a nandroid all CWM does is format the partitions then load the data from the nandroid to those partitions; back to square 1 with old data being left behind.

Q: Why don't I get a message about formatting /boot?
A: Because it doesn't format /boot. Why? In testing I found that it doesn't need it. It's all a matter of how Android uses boot.img and how it's copied.

Q: Does this wipe internal or external SD? (added because it keeps getting asked)
A: In a word, no.

Q: Will using this cause nand-failure or make my phone unusable if used too much?
A: In my opinion, no. In other's, yes. By my experience I have never encountered such a problem. To give you a better answer, please see Overground's post on that subject here: http://xdaforums.com/showpost.php?p=25257903&postcount=327
(Thanks for the objective opinion overground)

(More to come as need be)
 
Last edited:

Волк

Senior Member
Jan 7, 2012
1,159
548
San Diego
Nexus 9
Google Pixel 6 Pro
Reserved just in case. (I knew there was a reason for me reserving this)

Changelog for 3.1:
Now you can select one, two or no wipes per partition, a long-requested feature.

Changelog for 3.0.5:

1. Obviously this is now AROMA based.

2. The scripting for the progress bar is different due to AROMA, so for now we have no status bar progress. I'm waiting to see if someone can explain what Amarullz means in his explanation since I can't make heads or tails of it. Otherwise all the old functionality is the exact same.

Changelog: (old)

1. Added progress bar.

It's not 100% accurate, but sadly it's impossible to get it 100%, even after tons of testing.

2. Fixed format issue with /cache.

Thanks Overground for showing us a better format command to use
and to my tester/protogee Pharoah, who added the unmount command which made CWM less pissed at me.

3. Added a model check just in case someone doesn't know what they're getting ahold of and turn their phone's internals into something resembeling Chernobyl's Reactor Number Four.

4. Removed unneeded mount command in dual wipe script which was causing problems.


Plans for the future:

Create a menu system so that the user has a choice of what to wipe, and single vs dual wipes, or no wipe at all.
This is coming along well, I decided to keep it more straight-forward versus making a system of menus, so once it's thoroughly tested it'll be released

Hopefully a time-based progress bar is still possible, if not I guess it's time to find someone who likes math to figure out the percentage of each operation.
 
Last edited:

IRASadPanda

Senior Member
Dec 30, 2011
1,751
296
Johns Creek
4. I will provide help, support, etc., but I, nor anyone else involved with this, is responsible for any problems you may have in the extremely unlikely event that you do.
(you know who you are).

You need to change that so that it says "I am not, nor is anyone else involved in this, responsible for any problems....etc."

The way it's worded right now makes it look like you're claiming responsibility, which could get ugly.
 
  • Like
Reactions: r4d14n7

menting

Senior Member
Apr 15, 2011
307
55
i know a regular "format" of a nand flash just breaks the links to the data stored in the cells and doesn't actually overwrite the data, but won't doing this often wear out the flash card
 

BobbyDukes707

Senior Member
May 5, 2009
383
80
Skullcrusher Mtn.
Worked like a freaking charm! Thanks! Start it... let it do its thing, right at the "oh ****, something is wrong" moment it will move on... let it work...

Sent from my LG-P999 using xda premium
 

timothy7732

Senior Member
Jan 20, 2012
186
11
Let it run and it cleaned it all up running way faster you rock!!!!!!"

Sent from my LG-P999 using xda premium
 

Top Liked Posts

  • There are no posts matching your filters.
  • 60
    Hello,

    Here is my no longer new wipe tool, inspired by the G2x Scrubber.

    The Nullifier.

    This uses a special command in combination with a special file to overwrite the internal partitions with 0's, hence "Null" for 0 and "-ifier" for the fact that it does the action of the root word to something else. It also formats *all* the partitions afterward and *new* checks for, and repairs any errors on them.

    6 Oct: This tool is now depreciated and succeded by the G2x AIO wipe tool.

    New 2 August:

    Updated to 3.1, now fully customizeable by partition. Still haven't gotten around to making status bars, it's going to take a little bit to work out the best implementation.

    New 28 July: I've been working on wrapping my head around the infamous AROMA installer and have at least made some progress in understanding it. As alot of people in the past had wanted to have the option to choose which to wipe, and how many times. We're not there yet. Yet. I just wanted to give those interested something new to chew on while I work out how to break it down function by function. Currently I have it made so that you have one installer which allows you to choose between a single and dual wipe.

    New 26 March: The Cache Nullifier I edited the script down to just do a single pass Nullification then format and error check. This will work on the G2x, O2x and su660.

    26 April update: Changed the commands so that it writes ext4 file system instead of ext3 when it formats and created an error check zip, mostly just because it could prove to be useful. I tried a couple of different sign programs to sign these properly but in testing signature verification fails still.

    Minor update 1 March: swapped out the binaries on the 2.0.6 releases so they're the same as the older versions, added an ext4 cache nullifier, and fixed the code on the dual-wipe as I was sober when that one was revised as it had errors which would prevent it from running.

    Some brief need to knows:

    1. This is a little lengthy process so please bear with it. The longest wipe is on /data which will take about 7 minutes. Obviously, make sure you have plenty of battery life before running it or are charging.

    2. You *must not* power off your phone without first installing a new ROM or restoring a nandroid after you use this. See post here:
    http://xdaforums.com/showpost.php?p=23998091&postcount=125

    3. I will provide help, support, etc., but I am not, nor is anyone else involved with this, responsible for any problems you may have in the extremely unlikely event that you do.

    old links:

    Depreciated

    Direct link to 3.1:

    Depreciated

    Thanks to da-pharoah for being my main beta tester who stuck with me all the way, even after bricking his phone and getting the progress bar pinned down as best as possible.

    Additional thanks to anyone who contributed (you know who you are).
    11
    Nullifier Q and A:

    Q: Will this harm my phone in any way or brick it?
    A: No, the incident with Pharaoh's phone was an unexpected problem brought about from the source-file I was using at the time causing CWM and Android to think the phone was encrypted. I no longer use that source-file.

    Q: Why not just format everything?
    A: Because a format isn't intended to erase data, though, to a degree, does so. This script is intended to and will wipe out the data and leave a clean set of partitions for a ROM to be installed to.

    Q: (Submitted by Cargohook) Would it be idiotic or fruitless to run this and then restore a nandroid backup? I mean, would that defeat the purpose?
    A: I highly doubt it would be a waste of your time. On an educated hunch, when you restore a nandroid all CWM does is format the partitions then load the data from the nandroid to those partitions; back to square 1 with old data being left behind.

    Q: Why don't I get a message about formatting /boot?
    A: Because it doesn't format /boot. Why? In testing I found that it doesn't need it. It's all a matter of how Android uses boot.img and how it's copied.

    Q: Does this wipe internal or external SD? (added because it keeps getting asked)
    A: In a word, no.

    Q: Will using this cause nand-failure or make my phone unusable if used too much?
    A: In my opinion, no. In other's, yes. By my experience I have never encountered such a problem. To give you a better answer, please see Overground's post on that subject here: http://xdaforums.com/showpost.php?p=25257903&postcount=327
    (Thanks for the objective opinion overground)

    (More to come as need be)
    8
    Reserved just in case. (I knew there was a reason for me reserving this)

    Changelog for 3.1:
    Now you can select one, two or no wipes per partition, a long-requested feature.

    Changelog for 3.0.5:

    1. Obviously this is now AROMA based.

    2. The scripting for the progress bar is different due to AROMA, so for now we have no status bar progress. I'm waiting to see if someone can explain what Amarullz means in his explanation since I can't make heads or tails of it. Otherwise all the old functionality is the exact same.

    Changelog: (old)

    1. Added progress bar.

    It's not 100% accurate, but sadly it's impossible to get it 100%, even after tons of testing.

    2. Fixed format issue with /cache.

    Thanks Overground for showing us a better format command to use
    and to my tester/protogee Pharoah, who added the unmount command which made CWM less pissed at me.

    3. Added a model check just in case someone doesn't know what they're getting ahold of and turn their phone's internals into something resembeling Chernobyl's Reactor Number Four.

    4. Removed unneeded mount command in dual wipe script which was causing problems.


    Plans for the future:

    Create a menu system so that the user has a choice of what to wipe, and single vs dual wipes, or no wipe at all.
    This is coming along well, I decided to keep it more straight-forward versus making a system of menus, so once it's thoroughly tested it'll be released

    Hopefully a time-based progress bar is still possible, if not I guess it's time to find someone who likes math to figure out the percentage of each operation.
    8
    I understand it is hard when someone questions or says something about your work when your very passionate about what you do. i say take a deep breath and relax if you don't like it don't use it if you like it use it it is a simple concept i use this all the time and have never ever ever had a problem unless i have forgotten to flash something aka human error lets all play nice and appreciate the hard work volk has put in to this


    have a great day

    John C Craig
    x0xhellx0x
    6
    Ok. I've read over the last few pages and I see both sides of the debate.
    IMO, both arguments hold some validity.

    I have personally used this tool with no ill effects, and my phone seemed to run better after having used it (I have no hard data to provide to substantiate this).

    That being said, I would advise users of 3 things.

    1. (Obviously) Use at your own risk.
    2. Overuse of the tool could (but is not proven to) be detrimental to the device.
    3. Read and use common sense when making the decision to use this (or any other) experimental tool.

    Everyone's arguments have been heard and made, and I have not removed any pertinent posts as I believe them to help inform the end user of their ultimate decision.

    Please keep this discussion on-topic and civil as I will not hesitate to exercise my powers on those who attempt to further derail the thread.

    Thank you for your cooperation.