Revert "Added Samsung eMMC wear leveling data corruption bug patch to live patches"

This reverts commit 19637645568788f029210ff41879643b6ddfcd88.

Reson for revert: no Exynos 4 device carries any of the eMMCs affected by this bug.

Lanchon: do you know of any reason why the wear leveling bug patch is not included in the 4210/4x12 kernels?

Entropy512: It's easy - no 4210 or 4412 device ever had fwrev 0x25.  While according to Ken Sumrall, 0x19 is
affected by the bug - the patch that has been provided will ONLY patch 0x25 chips on bootup.  Also despite
Ken saying 0x19 was supposedly affected by the bug, of all the various bad behaviors I've seen reported for
the 4210 family, the 32kb-of-zeros bug is not one I've ever seen a report of occuring.

So there's no point of including it.  It will do absolutely nothing since it only patches a chip no device
that runs this kernel has.

Lanchon: yes i know the patch is version specific, and that fwrev 0x19 supposedly has the WL bug on top of
brickbug. in fact, since its a simple mod to the eMMC firmware, i thought of reading the patched code area
on both 0x25 and 0x19 and if identical...... maybe..... apply the patch to 0x19 too. but i deem it too risky.
i would need a lost imei crack display unit with 0x19 to test.

how is it that you know for sure no exynos 4 device ever had fwrev 0x25?

Entropy512: During the Superbrick fiasco we did a lot of monitoring of what chips/fwrevs showed up in
people's devices.  We never saw anyone with an 0x25.

Samsung kept on putting 0x19 chips into devices long after 0x25 was available AND after they knew about the
issue.  When they finally stopped using fwrev 0x19 chips, a completely different model number showed up.
I forget what it was, but it wasn't MAG4FA or VYL00M.  (I don't think we ever saw KYL00M in any 4210 device.)