You just double-click in windows, boot your phone to ODIN DL mode, and press Start.

No need to flash GB-based kernel/recovery just to do wipe data/factory reset then flash back to ICS-based kernel.

To be clear, the purpose is to have a "safe" replacement for wipe data/factory reset (recovery option) until we get the "fixed" kernels. It will wipe /cache and /data only, which is what wipe data/factory reset does. It will NOT wipe /system nor will it wipe your kernel.

In case people are not aware, there is a bug in the EMMC firmware (likely wear-level code) where if you issue an mmc_erase() it may result in a lockup/superbrick(). The reason it doesn't happen in GB is because GB doesn't use mmc_erase(). In ICS they added mmc_erase() into the code path initiated from make_ext4fs(). This is used by wipe data/factory reset in Recovery which is why we sometimes see the lockup/superbrick. Given that the problem is likely in the wear-level EMMC firmware code, it may not get triggered all the time even if mmc_erase() is called, but we are at risk whenever it is called.

As usual, you should be careful when flashing anything. I've been using this for 2 weeks now to test releases and haven't had any issues.

Q1 - Will this completely wipe all data, even from internal storage? How do I get my phone to go back to having only the basic folder/files needed to run?

Here is the reason I ask. I'm currently running Team Rogue Recovery. I just selected the Calkulin's Format All for E4gt.zip and ran it. It said it wiped a number of directories. After it ran, I then selected the Wipe > Factory Reset option. It said it wiped a number of directories.

However, when I go back and say "Choose .zip from Internal Storage", I see all these directories that were created by apps I installed that I thought would have been wiped. For example, I see a directory for BeWeather, CameraZoom, GoLauncher, GoLocker, etc. If I did a factory reset, shouldn't all those directories disappear from the internal storage?

Q2 - Assuming the answer to Q1 is yes, then based on the instructions provided, if I were to use this utility, it would clear out the data, but it would not remove the kernel. So could I use this utility while having a GB (EL29) kernel installed, and then flash a GB ROM?

Q1 - Will this completely wipe all data, even from internal storage? How do I get my phone to go back to having only the basic folder/files needed to run?

Here is the reason I ask. I'm currently running Team Rogue Recovery. I just selected the Calkulin's Format All for E4gt.zip and ran it. It said it wiped a number of directories. After it ran, I then selected the Wipe > Factory Reset option. It said it wiped a number of directories.

However, when I go back and say "Choose .zip from Internal Storage", I see all these directories that were created by apps I installed that I thought would have been wiped. For example, I see a directory for BeWeather, CameraZoom, GoLauncher, GoLocker, etc. If I did a factory reset, shouldn't all those directories disappear from the internal storage?

Q2 - Assuming the answer to Q1 is yes, then based on the instructions provided, if I were to use this utility, it would clear out the data, but it would not remove the kernel. So could I use this utility while having a GB (EL29) kernel installed, and then flash a GB ROM?

The purpose of this utility is to simulate the wipe data/factory reset option in Recovery using ODIN. The reason I put it together is there is a change in the ICS kernel where wipe data/factory reset does an mmc_erase(). This in turns triggers a bug in the EMMC firmware which could lead to your phone superbricking.

Wipe data/factory reset in Recovery will reset /cache and /data. It won't touch your SD card. This utility does the same, but does it in a safe manner that won't trigger the EMMC lockup/superbrick situation.

Don't expect stuff in /system (ie your ROM) to be reset nor your kernel. That is not the purpose of Wipe data/factory reset in Recovery. Its purpose is to get rid of your Android user data so you start from scratch.

If you are using a GB-based kernel/recovery, you don't need this. Your kernel/recovery doesn't issue an mmc_erase() thus are safe from the EMMC lockup/superbrick.

XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality.Are you a developer?