Originally Posted by crawlgsx
Agreed, very bad.
All I am saying is that it ONLY happened on those 2 botched kernel implementations. It is obviously SOMETHING the Dev's did with the kernel that caused this, seeing how ALL the other roms/versions clearly have not caused this. Since the result was immediate with both of those and many of us have jumped/cwm'ed/etc from MANY different Leaked kernel builds and NOT had that problem.
I am not trying to put them at blame, running any rom/dev is strictly at your own responsibility and risk, just stating that I don't think it is fair to place every leaked rom build in the same category of danger. Is there a risk, certainly, as the dev's could accidentally make said same mistake (I am not even clear if "we" know what causes it?) in a future version. That said I feel pretty confident that if the "final" versions of iMilka's roms were going to cause that issue, it would've happened by now. That is why I wanted to see if anyone had ever been bricked (fried eMMC) from them, and it seems, no.
Its nothing the dev did, it is more the nature of a binary only kernel and probably one of the options enabled/disabled which we will never know for 100% as it is a binary kernel. No sourcecode! Just avoid the leaked kernels and that's it. Entropy had mentioned what he think it could be, but no need to blame it on a dev now.
If you flash it, its all ways your own fault ;)..
Binary kernels from a different device are always considered dirty hacks and dangerous (period) as there is simply no control over them. The dev didn't choose the kernel settings, right? But you choosed to flash..
Sent from my GT-N7000 using xda premium
Samsung Galaxy Nexus