[Galaxy S III Q&A, Help & Troubleshooting] KeesStolk:
Just a noob sharing some thoughts, hope it can help some other noobs like me.

A no wipe in my book:

Here is how i do a no wipe.

In recovery, mount and storage and choose format system.

Go back and wipe Cache and Dalvik

Install / flash the rom.

A full wipe in my book:

Into recovery, mount and storage and format system, data and cache.

Go back, wipe/ reset data, cache and dalvik.

Install/flash rom

Format of the internal SD:

Here is what i do:

Make a app backup with TB to my external sd

Make a nandroid to my external sd

Make sure i also have a efs backup on my external sd

I only save mods, roms on my internal sd in my download map and this map i move to my external sd.

Then i reboot to recovery.

Mount and storage and format internal sd.

And to be save and have it nice a clean, also format system, data and cache and because i am not only a flashohalic but also a cleanohalic, i then wipe/reset factory reset, cache and dalvik.

Probably a big overkill, but he, done it several times it works for my and it only cause a few seconds.

Then i reboot, skip the setup/registration, move my download map back to my internal sd (don't like flashing from external sd).

Back in cwm, again a full wipe which includes the formats data, system and cache.

Then flash the rom and setting it up.

This way, you have a nice clean fresh S3, but and this is a big BUT.

Backup, backup backup and don't forget a efs backup to your external sd and pc.

Don't think lightly about those backups, when imei is broken and you don't have a backup, your a done, only thing left is a visit to Samsung.

Good luck when you are going for it.

And i know, Aroma installer is also doing some automatic wiping, but i am just a bit old fashion and like to do some stuff manually.

Bootloader.

As you all know, the new bootloader can be a pain in the ass.

But, i am still not sure that Samsung only released the new bootloader just to discourages us to flash custom stuff.

So, if you like flashing stuff and you are on the new bootloader like me, just remember when you entered recovery and you are done flashing stuff, use Triangle Away from Chainfire,

But, for some, like on my wifes phone, the latest version works without problem, but on my S3, i need to use the older version, 2.37, why, don't have a glue.

Not all S3 are the same, although have the same name and using the same chipsets. :)

But you can also use the old bootloaders, with does, you just have to run Triangle Away just once, when entering recovery, it will not count.

Your own choose.

About Sudden Death.

A lot of threads are open for this.

My 5 cents:

I have the "sudden Death" chips VTU00M chip with 0xf1 on both our phones.

Mine is running since 27 may 2012 without problems, still fast and smooth.

The other is up and running since 31 Augustus 2012 and also still fast and smooth.

Both have been rooted from day one, the only thing i do, is turning the devices off completely for a few minutes 4 to 5 times a week.

Old habit to clear memory, anyway, gives me time to do a good cleaning of my screen.

Here is the code to check your revision and to see from which day you are running your S3 *#12580*369#

Further more, AndreiLux found i string in the ELLA kernels released by Samsung that looks like that it solves the sudden death issue.

So, if indeed if fixes this issue, then off course the latest kernels releases from Sammy has also the fix and not just the custom kernels.

As far as i know, all the custom kernels has the fixes integrated this string by now, but i myself like the stock kernels, Indie puts in the Omega Roms.

Phil3759 has also made a repack of recovery based on CWM touch 6.0.2.7 to get it all safe.

More to come in the future, because i am learning everyday here on XDA and like to share and help others.

Edit, here is quote from AndreiLux about the new bootloader:

http://xdaforums.com/showpost.php?p=37163086&postcount=1298

Do I need any particular Bootloader? No - There is no evidence to suggest this fixes anything

Apparently that's wrong, download mode on the device uses a microkernel from inside the bootloader instead of the full blown Linux kernel. When flashing something via Odin in download mode you'd be using the bootloader's MMC driver and thus be at risk.

All-day users are still safe via recovery and live kernel, but are not advised to flash things in download mode with an older bootloader. This also explains why they updated the bootloader in LLA. The security checks are a mere update to bring it up with what the 9305 and Note 2 users already have in terms of not able to get rid of the exclamation mark.

Personal note:

Maybe i am seeing this wrong, to much thinking in terms of home computers, but here is some thoughts regarding above.

From cold, turned off device,.

Turning the device on, micro kernel inside the bootloader kicks in to send information how to start the device correctly.

If it works this way and you are on the old bootloader, then every time you start the device with the old bootloader, you are at risk?

Some useful links:

My struggle with TA

Omega roms S3

Chris_84 Faq

Triangle Away

http://www.chainfire.eu/articles/118/Triangle_Away_vs_Samsung/

Old bootloader

Philz recovery

https://www.google.nl/search?q=andr...s=org.mozilla:en-US:official&client=firefox-a

https://play.google.com/store/apps/details?id=com.electricsheep.asi&hl=nl

https://play.google.com/store/apps/...sIm5ldC52aW5hZ3JlLmFuZHJvaWQuZW1tY19jaGVjayJd