Hi, as i already wrote some posts with unbootable versions after the beta4 (including CM nightlys too, of Android 4.3)
I flashed some different Kernel,
both are good Kernel. With both Kernel i get the same issue as with updating my beta4 slimrom, it boots FIRST time, then after a reboot it stucks on Galaxy S3 boot screen (Kernel Problem)
I flash the kernel on the beta4 slimrom of course. One thing i noticed is, the Kernel of the beta4 slimrom is 3.0.80+ autobuild@slimautobuild#1 and with SELinux-Status Deactivated
Every update since then if slimrom has SELinux-Status Moderate
. Also the 2 Kernel is tested have both SELinux-Status Moderate
I have also found some people having kind of same problems with their Galaxy S2 for example. They stuck on Device Boot screen/ Black screen (bootloop?!).
I tried different CM nightlys aswell, no luck, i can restore a backup of the very early nightlys, that works. But every other nightly later doesn't boot.
Im pretty sure that it has something to do with this SELinux-Status
and/or the Bootloader maybe?
But i don't understand why none wants to talk about it?
Im curious what will happen when Samsung releases their 4.3 version for the Galaxy S3, or when 4.3.x or 4.4 come out.
To bad i may have to wait until that and im stuck with 4.2.2 or beta4. :(
My Bootloader is: XXEMG4
btw. I also reflashed latest samsung stock rom etc. everything stock. And tried to install slimrom or CM after that etc. no luck, it just doesn't boot. beta4 works tho, as already said before. I find it very funny and annoying at the same time, lol.
Okay... i now flashed latest Weekly with 4.3.1 AND the Kernel of Goodyhttp://forum.xda-developers.com/showthread.php?t=2270158
Based on Siyah Kernel. Point is, SELinux is OFF in this Kernel. And oh wonder, i can boot any version now of Slimroms or CM etc. so, reason why my GS3 didn't want to boot past the Kernel (Galaxy S3 boot screen) has to do with the fact that other Kernel have SELinux "ON".
Thats why slimbean beta4 kernel booted, there SELinux was also "OFF".
And i have to say, that sucks if i have to search for custom Kernel all the time to even be able to run any version of a custom rom. Why is this crap even activated if gives serious problems to some users? I don't get it.
greetings and thanks for help