[Galaxy Note GT-N7000 General] Entropy512:
No, no no NO - STOP talking about root. It COMPLETELY invalidates the test case in Samsung's eyes (even though it is totally irrelevant)

No, it doesn't have jack **** to do with rooting. It happens during a wipe in recovery. The recovery binary is in the initramfs, which is packaged with the kernel - All of the prerequisites for danger are fundamental aspects of the device that can't be changed (the eMMC model and fwrev) or are entirely located within the kernel image (either the kernel itself or the initrams).

What is in /system is completely and totally irrelevant - rooted or not, it just doesn't matter. Period.

Yup. The sample size of people who wipe in stock recovery is small to begin with - people running bone stock just don't wipe often. In addition, people who damage after wiping on bone stock are just going to go get warranty service, they're not going to come here.

You, sir, are an idiot. You are sitting here claiming that it has something to do with rooting or customization when all of the technical data collected over the past 2-3 weeks says otherwise. You are apparently completely and totally uneducated as to the nature of this problem and what causes it.

1) We have code review of Samsung's kernel showing that it passes ERASE commands to the eMMC chip if the recovery asks it to

2) We have documentation from a Google engineer that the eMMC chip and fwrev present in nearly every shipped N7000 is a fwrev that is documented as having a problem where it can't reliably handle ERASE commands. Google themselves encountered the bug during Galaxy Nexus development (and forced Samsung to upgrade the firmware in GNex devices)

3) On the previous page, I established the third and final component - Stock recovery attempts to issue ERASE commands during a wipe, which WILL reach the eMMC chip if the kernel doesn't block it.

While Samsung claims they can't reproduce the bug - Sprint can. http://xdaforums.com/showthread.php?p=26465085#post26465085

(I commend Sprint for acknowledging the bug and working on deploying a fix.)

While I realize the technical description of this issue may be difficult for some people (including, obviously, yourself) to understand - if you don't understand it, shut the hell up and stay silent, don't go around spouting completely untrue and baseless bull**** which is completely and totally wrong.

Put your money where your mouth is. If you seriously and truly believe that Samsung's stock ICS releases for this device are safe despite all of the evidence that says otherwise:

Verify that your eMMC chip is VYL00M, KYL00M, or MAG4FA fwrev 0x19 - nearly all devices shipped are in this configuration, but if you happen to have a rare device that isn't one of these, the test is invalid

Install bone stock XXLPY. Use it a bit - install some apps, go through the setup process so /data has some content in it.

Then enter stock recovery and do a wipe data/factory reset

Since the issue is intermittent (as documented by Mr. Sumrall himself), repeat this 20-30 times (Including making sure that /data is not empty - ERASE commands on an already-erased partition might be safe.)

Do it, or shut up and stop claiming that XXLPY is safe if it hasn't been customized - BECAUSE IT IS NOT SAFE.