Originally Posted by Entropy512
Almost surely - you'd have an even bigger chunk of the eMMC blown out.
I think eventually you'll pretty much lose the entire chip, or hit the bootloaders.
I was originally certain that this bug couldn't affect Galaxy S1 devices, but I realized they have hybrid storage - oneNAND/moviNAND for boot and /system and a few other partitions, but eMMC for /data and /sdcard - On those devices, wiping /data is starting to appear to trigger a bug that corrupts the partition table itself, rendering the entire chip unusable. (The Encryption Unavailable situation on those devices) - Currently this involves a lot of speculation though, far less is known about the EU situation on those devices, but it is starting to seem like it might be related.
Well now... that would definitely change the scope of the problem if true. Has anyone tried this on the i9001 as it does have the MAG4FA? I've been trying to find any test cases on XDA but haven't seen anything yet.
Anyhow from what you're posting it seems there is still progress being made albeit slow.
An "EU situation" has me going here:
Note in 4.5 the introduction of a "Discard" feature:
– A variant of the TRIM command that is more memory technology friendly
Is it possible that 0x19 was based on 4.4 standards but not fully compliant and 0x25 may be fully 4.5 compliant (meaning it can use the discard but not secure erase/trim?)
Again, know this is your field more than it is mine and that you might not be able to respond in public... but might be worth asking them the difference for the change.