• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

GS2ROMNuke/GS2ROMWipe Scripts

Good stuff Hawker. Probably the only question I can ask is; what does removing .android_secure do?
 
It gets removed in a factory reset. It was the only thing the Nuke script didnt do, so its an easy way to do a factory reset AND format /system (not done by a factory reset)

As for what its for, your new ROM may (or may not) move certain apps from its internal system storage into this folder. Its just clearing these old apps ready for your new rom
 
For those who have downloaded 1.1, download it again as there was a missing character in the script that was causing it to end without wiping.
Sorry
 
Hawker said:
For those who have downloaded 1.1, download it again as there was a missing character in the script that was causing it to end without wiping.
Sorry
Click to expand...

:hahaha: Typical... just can't get the staff these days!

(Shotty paid me to write that!)








Cheers old NUKER! :cheers:
 
GS2ROMNuke v1.2 is now up.

This version also clears android application data areas from the SD card.

/sdcard/Android/data
/sdcard/data

This is done so when you install your applications back onto your fully wiped new ROM, the applications have a clean start, so avoiding possible hangups from your previous firmware/OS version.
 
Quick question, regarding the 4.0.4 brick.
Does this cleaner use the stock recovery or CWM recovery to do the wipes?
Thanks.
 
It makes calls to the bundled GB binary file.

Anyway, as far as I know, if you have CWM recovery in your kernel installation, your stock recovery will be wiped so it would be impossible to make calls to the stock recovery. (and vice versa if you have a stock kernel).

And on a double whammy note, whichever recovery you have, it makes calls to the installed kernel to do its wipes (hence the origins of the brick bug with affected kernels), so its irrelevant if you have stock recovery or CWM recovery.

Its the kernel you have, not the recovery program, that determines the brick bug. The recovery program is just the interface that causes the bug to occur.
 
Thanks for your prompt reply.

It has been determined (in XDA and other forums) that the risk of bricking a Galaxy S2 with official 4.0.4 firmware and stock kernel is by making a data wipe with CWM recovery.

I flash a temporal CWM recovery (from stock recovery) to use your script, without changing the kernel. By doing so, will it use the stock recovery or the temporal CWM to do the wipes?

Thanks again. :)
 
Yes, the brick occurs in a wipe in CWM Recovery, but the problem lies in the underlying kernel, and not in CWM Recovery itself. CWM makes calls to the kernel to perform the wipe and the kernel bricks your device.

Bottom line is, if you are on, or are intending to go onto 4.0.4, flash Siyah via Odin ASAP and you can CWM wipe to your heart's content.

Using this script on 4.0.4 when still on a stock kernel shouldn't cause the brick bug as it uses a GB binary, but my testicles are not big enough to test this out for certain. :)
 
Hawker said:
my testicles are not big enough to test this out for certain. :)
Click to expand...

Not what I heard

1331575709_0.jpg
 
You must log in or register to reply here.
Back
Top Bottom