Database Info

[.zip] Showudway's Format All

FIXED
Hello I'm here to present my Format all utility.
I know there is already one out but i just got bored and decided to whip one up.
Wipes all the listed file systems Three different times to insure a full wipe.
Wipes the fallowing:
System
Data
Dalvik
Cache
Boot
Bat stats
Flash .zip in recovery before flashing a rom, Enjoy!

Thanks. Will come in handy.
Sent from my PC36100 using XDA Premium App

No problem, tell me how it goes for you

never hurts to have another format all floating around

I like how you think, but mine is prettyfull!

http://forum.xda-developers.com/showpost.php?p=12832127&postcount=17
/thread. Please make sure you check your scripting, spelling, etc before you break someone's phone.

DrRyder said:
http://forum.xda-developers.com/showpost.php?p=12832127&postcount=17
/thread. Please make sure you check your scripting, spelling, etc before you break someone's phone.
Click to expand...
Click to collapse
Posting fixed version now, just ran it on my device.

[Utility] Showudway's Format All

[Completely Recoded!]
[Is made to only work for evo, will not run on any other phone]
Hello I'm here to present my Format all utility.
I know there is already one out but i just got bored and decided to whip one up.
Big Thanks to Calkulin
Wipes all the listed file systems Three different times to insure a full wipe.
Wipes the fallowing:
System
Data
Dalvik
Cache
Boot
Battery Stats
All Temp files
Flash .zip in recovery before flashing a rom, Enjoy!

I'll give this a try soon. Thanks!
Sent from my PC36100 using XDA Premium App

Cool gonna test it out now
Sent from my PC36100 using Tapatalk

Same as all other format all .zips

Thanks guys, tell me your results!

Will this work with the newest cwm and amon?
Tapa tapa tapa

mlin said:
Will this work with the newest cwm and amon?
Tapa tapa tapa
Click to expand...
Click to collapse
Yes it will, I just tested to make sure.

I guess i can use this one as well w the other two
This i like cause it wipes dalvik.. nice nice.
Thanx op!
Sent from my PC36100 using Tapatalk

I don't think this differs at all from Calkulin's format all posted many moons ago.

tzbigworm said:
I don't think this differs at all from Calkulin's format all posted many moons ago.
Click to expand...
Click to collapse
calk's doesn't wipe dalvik

gotshores said:
calk's doesn't wipe dalvik
Click to expand...
Click to collapse
exactly, i think mine is the only one that does

The other difference is this one wipes 3x - saves some time and wear on the evo hw buttons.

I like you work - this is nicer than caulk's if only because it has more messages. Would you mind making one to clear temp files which can be used before upgrading a rom or installing a kernel.

gotshores said:
calk's doesn't wipe dalvik
Click to expand...
Click to collapse
Nor does it work with the newest CWM

mlin said:
Nor does it work with the newest CWM
Click to expand...
Click to collapse
+1 I hate that about Cal's. No need to sweat that now. Thanks.
Sent from my PC36100 using XDA Premium App

I'll most def give it a shot before flashing a new rom.

Ok. This script isn't doing what you're selling bud.
1. It formats the cache, data, boot, and system once.
2. You delete_recursive on the dalvik cache. For some people, like myself, the dalvik cache is in /cache. Not /data.
3. You're using half Edify and half Amend scripting. Your show_progress is the wrong syntax for Edify. So is the rest of your format/delete commands.
4. You have so many spelling mistakes that it looks like a 10 year old whipped this up.
You asked for feedback, here it is. I could write up a better wipe and you've actually motivated me to do it.
Edit: Attached is a quick Format & Wipe that I made. It's an update-script but it's 100% Edify. Someone who's willing try this and let me know if it works. <--- Read below.
Edit 2: I had to modify the script a little bit due to syntax errors, renamed it to updater-script and added an update-binary. I used it before flashing my latest update to my rom and it worked perfect.

and this seems a lot like
http://infectedrom.com/showthread.php/238-Vr_superwipe

I just typed the one I made up. I have no idea what anyone else's format all scripts do. I just know mine isn't going to do it 3 damn times. It deletes /boot, /cache(includes dalvik-cache since that's /cache/dalvik-cache), /data(includes dalvik-cache since that's /data/dalvik-cache), & /system. It then formats boot, cache, data, & system.
That's all. Should work perfect.

DrRyder said:
Ok. This script isn't doing what you're selling bud.
Edit: Attached is a quick Format & Wipe that I made. It's an update-script but it's 100% Edify. Someone who's willing try this and let me know if it works.
Click to expand...
Click to collapse
I fixed it now,tested and it ran perfect with my evo

You are NOT doing a full wipe!

...if you are not formatting /system.
I keep reading on almost every development thread, pages of posts from people stating that they are having all kinds of problems and it is the fault of the rom they flashed. Then after several people try to help out, the poster of the problem will usually state something like, "I DID DO A FULL WIPE DAMMMMMITT!!! I cleared cache, dalvik and EVEN did a factory reset...I even fixed permissions after I flashed...THIS ROM IS JUNK!!!!"
Time and time again, I see that they neglected to format /system. If you don't include this as a part of your "full wipe", you can leave behind remnants of your previous rom, which is most probably going to cause problems.

couldn't have said it better myself. especially when coming from a 2.3.5 rom but should do it for any.

mmapcpro said:
...if you are not formatting /system.
I keep reading on almost every development thread, pages of posts from people stating that they are having all kinds of problems and it is the fault of the rom they flashed. Then after several people try to help out, the poster of the problem will usually state something like, "I DID DO A FULL WIPE DAMMMMMITT!!! I cleared cache, dalvik and EVEN did a factory reset...I even fixed permissions after I flashed...THIS ROM IS JUNK!!!!"
Time and time again, I see that they neglected to format /system. If you don't include this as a part of your "full wipe", you can leave behind remnants of your previous ROM, which is most probably going to cause problems.
Click to expand...
Click to collapse
I have continually recommended this also, but maybe doing it here in a separate thread will get better attention.
I format /system between ALL ROM flashes (only takes a few more SECONDS if you are also wiping davlik and cache).
Per your OP - I have had very few issues as a result. I really think most of the posts on problems that are not know issues in these threads are the direct result of not doing this.
PS - formatting /system does also not always work either. I have not had problems so far with my G2X from not doing a "real full wipe" (fastboot system erase....), but I did a few times when I was crack-flashing nightlies over on the MT4G forum. I could not otherwise get WiFi and/or bluetooth to work at times even after doing a factory reset and formatting /system.

besides the wide data, cache, dalvik and format/system, is it safe or recommended to format anything else when flashing a new rom?

gaww said:
I format /system between ALL ROM flashes (only takes a few more SECONDS if you are also wiping davlik and cache).
Click to expand...
Click to collapse
Um, how? There's no option in CWM. Do you shell in and do an "rm -rf" in the /system directory?
gaww said:
I have not had problems so far with my G2X from not doing a "real full wipe" (fastboot system erase....), but I did a few times when I was crack-flashing nightlies over on the MT4G forum.
Click to expand...
Click to collapse
Is there such a thing as fastboot for Terga2 devices? I thought that was ARM thing (like my old HTC Magic)...? Is there an equivalent tool for the G2x?

lannister80 said:
Um, how? There's no option in CWM. Do you shell in and do an "rm -rf" in the /system directory?
Is there such a thing as fastboot for Terga2 devices? I thought that was ARM thing (like my old HTC Magic)...? Is there an equivalent tool for the G2x?
Click to expand...
Click to collapse
Its under mounts and storage I believe.
Also this whole problem could easily be alleviated by rom makers putting a format /system in there install script like CM does. Not defending dumb asses, just saying it would be helpful for the people less in the know.
Sent from my LG-P999 using xda premium

xsteven77x said:
Its under mounts and storage I believe.
Also this whole problem could easily be alleviated by rom makers putting a format /system in there install script like CM does. Not defending dumb asses, just saying it would be helpful for the people less in the know.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Oh, CM formats /system? Awesome, I only use CM, so I don't have to worry about this issue.

To be honest, it's stuff like this that has kept me from flashing a ROM. I've started a procedure doc, filling in details as I read threads. I hadn't seen this one...
Some day I will hopefully have an all-encompassing "this is how you flash a ROM" doc, and I will post it. Unless it already exists?
Then I have to start on a Kernel flash doc...
Just so I can use a stable phone...
I write embedded C for a living, and music is my hobby - I didn't mean for my phone to become a hobby, also. But it is addicting...

mmapcpro said:
...if you are not formatting /system.
I keep reading on almost every development thread, pages of posts from people stating that they are having all kinds of problems and it is the fault of the rom they flashed. Then after several people try to help out, the poster of the problem will usually state something like, "I DID DO A FULL WIPE DAMMMMMITT!!! I cleared cache, dalvik and EVEN did a factory reset...I even fixed permissions after I flashed...THIS ROM IS JUNK!!!!"
Time and time again, I see that they neglected to format /system. If you don't include this as a part of your "full wipe", you can leave behind remnants of your previous rom, which is most probably going to cause problems.
Click to expand...
Click to collapse
+1, I make sure EVERYTHING is wiped before I flash a ROM.

lannister80 said:
Um, how? There's no option in CWM. Do you shell in and do an "rm -rf" in the /system directory?
AS others have now said, it is under mounts and storage. It fortunately is no longer right below format SD Card - a number of people have done so accidentally.
Is there such a thing as fastboot for Terga2 devices? I thought that was ARM thing (like my old HTC Magic)...? Is there an equivalent tool for the G2x?
Click to expand...
Click to collapse
This was done with SDK tools fastboot commands. I have not had to try it yet on a G2x, but I assume it would work - other fastboot commands do.
I usually also added the -w to wipe cache and data at the same time.

lannister80 said:
Is there such a thing as fastboot for Terga2 devices? I thought that was ARM thing (like my old HTC Magic)...? Is there an equivalent tool for the G2x?
Click to expand...
Click to collapse
Tegra stuff does have fastboot, on the O2X and Advent Vega, if you wipe the boot partition and reboot the phone drops to fastboot. I would assume the G2X is the same.
You can flash or boot a recovery, and boot a boot image, although you can't flash a boot image for some reason. That's all I've tried though.

wyldkard said:
besides the wide data, cache, dalvik and format/system, is it safe or recommended to format anything else when flashing a new rom?
Click to expand...
Click to collapse
Yes...the internal SD card. This is an often neglected step and could cause problems (such as boot loops) if not formatted.

Interesting, I've done many ROM flashes using about 5 different types of ROM and not had to do this but I'll bear it in mind.
I just do a data wipe when using different types if ROM and just cache when upgrading the same ROM. Maybe I've been lucky?
Sent from my HTC Desire using Tapatalk

hidden_dragon said:
Yes...the internal SD card. This is an often neglected step and could cause problems (such as boot loops) if not formatted.
Click to expand...
Click to collapse
You erase ALL of your personal data each time? That's thorough for sure, but not really necessary.

leenukes said:
Interesting, I've done many ROM flashes using about 5 different types of ROM and not had to do this but I'll bear it in mind.
I just do a data wipe when using different types if ROM and just cache when upgrading the same ROM. Maybe I've been lucky?
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
I've never had any issues just wiping data/caches when switching roms. But it doesn't hurt to start with as clean a slate as possible.

Oh how I miss Ohsaka's superwipe from my g1 days... I can't be spending all day manually wiping caches, dakviks and formatting systems...
Sent from my LG-P999 using xda premium

BobbyDukes707 said:
Oh how I miss Ohsaka's superwipe from my g1 days... I can't be spending all day manually wiping caches, dakviks and formatting systems...
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
How many times per day do you flash new ROM's - lol ???

leenukes said:
Interesting, I've done many ROM flashes using about 5 different types of ROM and not had to do this but I'll bear it in mind.
I just do a data wipe when using different types if ROM and just cache when upgrading the same ROM. Maybe I've been lucky?
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
You have been lucky - especially in flashing different types of ROMs on the same device
Also, it takes a lot more work to reload data (unless you are using advanced restore) and most flashing issues happen with the system rather than data. I always try to preserve data but clear the system.

Way to exaggerate...the entire process takes about a minute and a half, lol.
Sent from my LG-P999 using xda premium

BULL****, my mom told me to fold the toilet paper 4-6 times and wipe from my turkey neck outward toward my crack.
NEVER TOWARD THE TURKEY NECK, NEVER..

[TOOL] G2X Cleanup Batch *** WARNING *** WILL FORMAT INTERNAL SD

If you are going to flash and ICS ROM after this tool please make sure to first install a GB then ICS otherwise your SD card will not be accessible. I am trying to find a fix but it has been illusive. This statement will be removed once a fix has been found and OP updated.
Now with CWM Touch!
This method uses NVFLASH to recreate all partitions and formats them, thereby getting rid of the file allocation pointers and hence renders data inaccessible without effort.
Note: I have never seen a file come back to life or its data affect other files without effort on the users part or a temporary glitch once the partitions and pointers have been overwritten. Please post a reply with evidence if you have seen it.
Benefits:
The contents of the zip file can be used to super clean G2X before a new ROM flash. This tool recreates all the partitions in the phone so wipes the pointers to all files (everything). The method it employes has existed from before. The files here will stop short of pushing a ROM, so that you can push your favorite ROM.
Prerequisites:
G2X (Will not work on O2X due to different partition table)
Desire to have a clean install of your favorite ROM
Backup your data
*** WARNING ***​
This tool will wipe both phone internal memory and internal SD card. External SD card content is safe.
Don't say you haven't been warned!
What to do:
Download the attached Zip file.
Take out the battery (assuming you have backed up your data on external SD card, computer or elsewhere), connect the device via USB while holding VOL+ and VOL- together. Don't let go of the volume buttons until the device is recognized.
(I typically leave Device Manager open to see when it shows up in the list under "USB Controllers").
Launch flash.bat, sit back and wait until the process finishes (generally a good idea to open a command prompt, CD to the directory and then run the file).
Unplug, put battery in, reboot into CWM recovery (pushed by this tool) by holding VOL- first, then pressing and holding POWER).
Flash your favorite ROM.
Enjoy!
I made this package because I could not get the bluetooth to work with G2x GB 2.3.3 (and below). The issue was a disconnect problem where both the phone and headset would still think they were connected but in audio would not be routed for a call or media. After this procedure my phone has not had an issue for almost 3 weeks now. I have tried it with two ROMs and 3 different headsets without any issues.
I guess I will not toss this phone after all .
Putting it out there in the hope that it may help others solve some of their issues as well. I suspect bad data stays in places not touched by other methods.
Your comments are most welcome.
[Update]
Klathmon has made an newer version with CWM 5.0.2.8. RP by Klathmon can be found here:
http://forum.xda-developers.com/showpost.php?p=24768294&postcount=66
I have tested the windows version but linux one is untested. Use at your own risk.
[Update]
Now with CWM Touch!
Thanks to everyone who has contributed on this thread with a drive to positive change! You work/comments/suggestions are very much appreciated.
References:
http://forum.xda-developers.com/showthread.php?t=1248644. This link was the inspiration for the current work.
Link to CWM Touch development thread. I took the image posted there: http://rootzwiki.com/topic/22984-recovery-touch-enabled-cwm-5813/
[EDIT] The zip file should be fixed now. Darn work machine does something to the upload.

was just about to flash the new hellfire rom and saw this tool! will try it out and see how things go
edit: yeah corrupt zip on my end too.

The zip file seems to be corrupt. Could you re-upload plz

worked great on my end, no problems.

khanggle said:
worked great on my end, no problems.
Click to expand...
Click to collapse
The real test is how stable your ROM would stay with this method to wipe than any of the other methods.
I guess only time will tell .

wow this method really blaze hellfire much thanks to your( you) & (rom dev)

Ohh I like this. Thank you for sharing .
This thing is faster than nullifier, and I especially like how you don't need to be in CWM to use it. It just seems like doing it in "update mode" would allow better manipulation of the phone's internals.

so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)

dodgefan67 said:
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
Click to expand...
Click to collapse
He states in OP that it doesn't write anything, therefor doesn't "nullify". It formats and partitions.

dodgefan67 said:
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
Click to expand...
Click to collapse
Actually you are right. Deleting, recreating and formatting partitions does not get did of the 1s and 0s, so in that sense the data is still there. However the pointers are gone, and hence even though the data is still there it can't be accessed without effort.
What do you think the nand has on it when the device is shipped... I can assure you its not ask zeroes!
Sent from my LG-P999 using XDA

mansa_noob said:
Actually you are right. Deleting, recreating and formatting partitions does not get did of the 1s and 0s, so in that sense the data is still there. However the pointers are gone, and hence even though the data is still there it can't be accessed without effort.
What do you think the nand has on it when the device is shipped... I can assure you its not ask zeroes!
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Well no, it has a next to worthless version of android Also, the point he was trying to get across is that it would be better for you to present the script for what it is and not try to compare it to other scripts that do something entirely different. You do kind of imply that you accomplish the same thing as the Nullifier script and more, when in fact you simply do something different.
Some may and probably will prefer your script, at least for specific purposes, while others will prefer the Nullifier script.

MWBehr said:
Well no, it has a next to worthless version of android Also, the point he was trying to get across is that it would be better for you to present the script for what it is and not try to compare it to other scripts that do something entirely different. You do kind of imply that you accomplish the same thing as the Nullifier script and more, when in fact you simply do something different.
Some may and probably will prefer your script, at least for specific purposes, while others will prefer the Nullifier script.
Click to expand...
Click to collapse
Done. OP updated to reflect. Thanks for clarifying that. It was not my intention to state that this tool does anything any other does, or does not.
I think we are all trying to do the same thing... get rid of the issues when swapping ROMs like _____. I can't seem to think of a good analogy here .

thanks for clarifying the OP, that makes much more sense
and no i wasnt trying to say you were reinenting the wheel, just trying to understand what your tool is actually doing
and also i do understand that it would take effort to get data off any type of storage device once the partition has been erased. i deal with wiping hard drives in a data center all the time. we use a DOD wipe tool that writes 1s and 0s over a drive a minimum of three full times to eradicate the data
but with this tool doing it outside of CWM, it sounds like it may do a better job of it
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?

dodgefan67 said:
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
Click to expand...
Click to collapse
There is no need to push CWM 5.02. As I said in the OP it is a mod of the script found in the reference. In that script it was pushing default recovery. Since the recovery partition is being overwritten as well you will loose existing one and you need a recovery to be able to push a new ROM. Hence the need to push recovery (instead of using super one click).
As long as the recovery is not bigger than the partition that holds it we should be able to push a newer version. However I can't leave it empty or people will look for me with a shotgun (myself included ).

dodgefan67 said:
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
Click to expand...
Click to collapse
I was thinking the same thing but seems easy enough .. add the cwm img to the dir and edit the .cfg file. Hopefully that should get the new CWM flashed

So would it be benefitial or pointless to nullify to clear the data then run this script for a... super clean?
Sent from my LG-P999 using XDA

mansa_noob said:
There is no need to push CWM 5.02. As I said in the OP it is a mod of the script found in the reference. In that script it was pushing default recovery. Since the recovery partition is being overwritten as well you will loose existing one and you need a recovery to be able to push a new ROM. Hence the need to push recovery (instead of using super one click).
As long as the recovery is not bigger than the partition that holds it we should be able to push a newer version. However I can't leave it empty or people will look for me with a shotgun (myself included ).
Click to expand...
Click to collapse
ahhhhhh now i understand. my eyes have been opened LOL
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
PL0X_Kleiner said:
So would it be benefitial or pointless to nullify to clear the data then run this script for a... super clean?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
i think it would be pointless unless you are super paranoid

dodgefan67 said:
ahhhhhh now i understand. my eyes have been opened LOL
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
i think it would be pointless unless you are super paranoid
Click to expand...
Click to collapse
Nobody is twisting any arms here... Use it if you want to, don't if you don't want to.
I saw benefit so posted so that others may benefit as well.
Sent from my LG-P999 using XDA

Ok so question, why are you killing all the data on your internal SD card? Why not just the individual partitions that the phone uses? Your destroying data that don't need to be destroyed before flashing a rom...
Sent from my LG-P999 using xda premium

It does not have to be destroyed. I just haven't had a chance to test without recreating emmc yet.
Next step. Likely tomorrow. Would like to test before release.
Sent from my LG-P999 using XDA
[edit] BTW, I do want to restate that there is some data that needs to be destroyed which is not being taken care of by other methods. I don't believe it is in the emmc, but rather it resides in one of the other partitions. Most methods out there are only working in the /data, /system and /cache domain.
My original problem (bluetooth disconnect) which happens to be a problem for some in the community even now was only completely fixed by this method.

[GUIDE] Flashing ROMs correctly, every time

***original post copied verbatim******************************************************************
So I was rummaging around the dev section, QA, so forth. And I have seen numerous threads, questions, posts, where people have had issues with ROMs or just general left field issues that were resolved by going back to square 1 doing a fresh clean install of "rom.zip..
My goal with this thread is to contribute some insight and experience with customizing android devices in the way we all do... at square one, clicking the download button.... we also do not have a thread dedicated to this one subject alone, so here it is. I feel stickying this thread would be extremely useful, as so many people could see it right from the get-go and get valuable information from it.
Just getting right into it, I will say this, I have flashed (I'm sure) damn near 1,000 ROMs to various devices. Mine. Friends. Etc. And never once have I installed a corrupt zip file to these devices. This should never happen, and among other important details to any installation of a ROM, this one is the most important...
VERIFY THAT YOUR DOWNLOADS ARE GOOD!
How do you do this??? Well I will show you... it is with this handy little app called md5 checker from the play store. EVERY. SINGLE. ONE OF US.... should have this app, guys (and gals, because I know you are out there it is a free app. No excuses
What is an MD5 checksum? Trusty link to get the gist of it.. http://www.fastsum.com/support/md5-checksum-utility-faq/md5-checksum.php
Making this simple - I will break this down into steps. Follow this meticulously and 99.9% of the time you will not have an issue or be one of the random bugs popping up when everyone else seems fine.
1. Download md5 checker.
2. Download all zip files needed for your ROM. (whether you do this from your mobile device or a desktop/laptop it doesn't matter, because you WILL verify the file AFTER you have transferred it to where it needs to be allocated - your device). Basically, download it, transfer it.
3. Open md5 checker, the app is pretty easy to use. Much like a file explorer in its layout with the obvious differences.
4. Retrieve md5 for your zip files.
5. Verify them with ROM developer, or others using that particular ROM. Any discrepancies - back to step 2.
6. All is well? Boot to recovery.
7. Wipe data 3 times (you don't need to wipe dalvik cache, that directory is found in the data partition - wiping data = wiping dalvik cache)
8. Wipe cache 3 times (this sometimes does not need to be done either depending on whether or not your recovery wipes cache with data.. most recoveries will spit out some text during the wiping phase letting you know the details of the process and you'll see see something like this when wiping data)..
"Wiping /data...
"Wiping /cache
If you see cache being wiped, you are good. No need to manually wipe cache.
9. Format your system partition through recovery 3 times
10. Install your ROM. Reboot. Let it sit for a minute or two, reboot it again. If you are not installing a custom kernel, stop here. You are done, and winning.
11. Reboot to recovery, wipe cache partition 3 times AND dalvik cache. They are both there as options, for this reason - the goodies we install after a full ROM install.
12. Flash kernel zip. Reboot. Let it sit for a minute or two, reboot it again. You are done, and winning.
Interesting fact about all the ROMs I have installed over the years, NOT ONCE, have I ever installed something corrupted, and every issue/bug I have ever had with a ROM was a known issue. This also doesn't mean your particular device is always going to be able to run for weeks on end without needing a quick reboot. Sometimes its good to do the dishes, I get that. But my disclaimer here is for all to note, if you follow these steps meticulously, you will ALWAYS be able to say to yourself with confidence "nope, did it right, there is something else going on here." And thus you will be a greater problem solver and contributor to the community as a whole every single time you pose a thought or question regarding any problems you are having.
"Do it right once, instead of doin it wrong twice before doing it right."
We are nothing useful without useful information. Useful information = posting in a thread in this tone...
"Hey, installed ROM correctly/thoroughly, verified downloads, XXX is buggy blah blah etc etc... can somebody else here verify if they are or aren't having this issue? Thanks!"
Based on people's response you'll know if it is just you or a legitimate issue, in which case, you brought it to the attention of us all, and the dev(s), and you have now been very useful.
What you don't want to do is this....
"My phone keeps rebooting!!! Haaaalp"
The reason why you shouldn't post like that is because you will ALWAYS get a sour response or people will just ignore you. Or, they will reply with questions you should have already asked yourself... "did you verify your downloads were good??? Did you do a clean and thorough install???"
Long post, but I hope somebody will find it useful and utilize it. It will increase your experience with your android device in a positive way, as it has for me. Cheers

Ah yes i get random freeze screen with some ROM installer

why not format every partition 3 times (idk how recovery looks at this device, im used to 4ext on the HTC sensation) and the wipe data to set al parations right again and install the rom? even why wiping 3 times instead of 1?

Very nice guide. Extremely helpful for beginners
Sent from my GT-N7100 using xda premium

And please have to say that use a wipe script it's such a kind of blasfemy ...

Alienator9191 said:
why not format every partition 3 times (idk how recovery looks at this device, im used to 4ext on the HTC sensation) and the wipe data to set al parations right again and install the rom? even why wiping 3 times instead of 1?
Click to expand...
Click to collapse
agreed
since nand ram has its life time of cycle. wiping the nand for more than needed is some kind of suicide mission to your droid....

I disagree. If you are the type that flashes a ROM 5 times a day then yes that might be a factor.... might be. Each android device I have owned I have flashed a ROM/kernel to it literally thousands of times and nothing was ever damaged because of scrubbing the disk too much and flashing to it too much. Sorry, but misinformed about just how robust these disks are.

It needs to a must read for noobs
Sent from my GT-N7100 using xda premium

Most definitely, wiping 3 times is completely unnecessary. Only 1 time is enough for the NAND to perform the wipe commands. Not only that, but also you're wearing out the flash drive by wiping so much, even though you flash a lot. Another reason to only wipe once.

First of all thz for this step-by-step guide, for newbie is useful.
Phistachio said:
Most definitely, wiping 3 times is completely unnecessary. Only 1 time is enough for the NAND to perform the wipe commands. Not only that, but also you're wearing out the flash drive by wiping so much, even though you flash a lot. Another reason to only wipe once.
Click to expand...
Click to collapse
I agree, why repeat 3 time the same wipe command, when 1 time is enough for wipe data from NAND...
unless there is an hidden reason, I don't see a good reason to do that! :cyclops:

zenzip said:
First of all thz for this step-by-step guide, for newbie is useful.
I agree, why to repeat 3 time the same wipe command, when 1 time is enough for wipe data from NAND ?
unless there is an hidden reason, I don't see a good reason to do that! :cyclops:
Click to expand...
Click to collapse
1 wipe is more than enough
plus this thread should be in general section

I never face any problem with these steps (surely more then 100 flashing)
1.Downoad and flash ROM with Odin (odin doesn't check md5??)
2.Reboot, nevermind if stuck
3.Reboot to recovery, wipe cache and data.
Thats it.
If your counter is already raised, first make sure you have stock kernel and recovery
Reset counter
Start from step 1 above.

**knock knock knock**
Leonard
**knock knock knock**
Leonard
**knock knock knock**
Leonard

BullHorn7 said:
**knock knock knock**
Leonard
**knock knock knock**
Leonard
**knock knock knock**
Leonard
Click to expand...
Click to collapse
Lol... this is Sheldon wiping style...
Inviato dal mio GT-N7100 con Tapatalk 2