You are advising people to stay away from Samsung ROMS, are you sure this is correct?
Is this issue not a Kernel issue, therefore the ROM is of no consequence, but the kernel/recovery is what is really responsible for the issue
As far as my understanding goes, and from reading in the relevant thread that is dealing with this issue, ROMS were never discussed, Kernels were, you can use any ROM you like, the fix is at a kernel level
On another note, since Chainfire was able to release this tool that can check if your hardware is the one affected, is it at all possible to release a tool that can check to see if the kernel you are running has the dangerous code disabled???
Or just flash last GB and stay on it and don't worry about flashing ICS.
---------- Post added at 04:08 PM ---------- Previous post was at 04:07 PM ----------
CM9 ROMs and kernels are SAFE. You do not have to stop flashing the nightlies. The Samsung official and leaked ROMs and kernels are the faulty ones. Franco and Speedmod kernels are safe as well.
---------- Post added at 04:10 PM ---------- Previous post was at 04:08 PM ----------
The emmc bug is on the official and leaked Samsung ROMs and kernels. On the Note, CM9 is safe. I'm not sure which ROMs are safe for SII but I'm sure CM9 is one of them. Avoid wiping data on the Samsung ROMs, or in my opinion, avoid Samsung ROMs entirely.
I'm saying avoid Samsung roms, absolutely. Yes, it is only the Samsung kernel. But, it is easier to just avoid the entire Samsung official ROMs for noobs.
The franco and speedmod kernels are stock (kinda) and they just disabled the MMC_Cap_erase code. So, they are pretty safe. If you HAVE to run a Samsung rom, you can flash one of these kernels. I was just making it easier on users.
|Thread Tools||Search this Thread|