Hey im back to android but I cant get the custom rom to boot. It keeps saying (Kernel is not SEANDROID ENFORCING) and it just stays there. I tried all the kernels from inside the rom(aroma) but non of them boot. I installed the nougat BL and Modem... maybe someone can tell me what im doing wrong. Sorry for my english.
EDIT: okay now with the stock kernel (KERNEL IS NOT SEANDROID ENFORCING) is gone but its still stuck at samsung galaxy s7 edge powered by android screen.
hi,i'm in the same problem.did you find how to solve it?
Kernel is not seandroid solved
After many times trying to install this rom and all the time getting stuck on boot logo and with kernel bla bla bla.i want to say first that other roms installed nice and easy.so in the menu aroma ,when you try to install you have option to install magisk or supersu.everytime i tried was left on magisk but after many many times being not succesfull i choose supersu instead and this time worked .after losing my time with this rom ,also crash and reboot when i tried to call somebody (first time in 10 years) and also the battery consumtion is very bad.20% in 1 1/2 hours.
Related
Hi everyone,
I'm a noob here but I read the guidelines
You're the only who can save me tonight (it's 3 a.m. here and sry for my bad english).
I rooted my Galaxy S4 (international version - Snap 600 - i9505) and I flashed the latest nightly of cyanogenmod. I started my device and, after 4-5 minutes, the rom started. I felt immediately disappointed, it's a pre-alfa version and I installed it just to try it.
So, I decided to install the Pure Google Rom with Android 4.3 (http://forum.xda-developers.com/showthread.php?t=2341026).
I rebooted my device, but for some reasons (I got a small crash, because I failed, removing my battery during the boot animation), my phone is now stucked at the title screen.
I can see just "Samsung Galaxy S4 - GT_i9505" on an infinite black screen. I'm so sad, I wish to solve this problem...
P.S. I tried to reboot in recovery mode: almost the 70% of the times I tried, it failed entering recovery mode. The only time it entered recovery, I wiped everything, but nothing seems to change.
Please help :\
demLong said:
Hi everyone,
I'm a noob here but I read the guidelines
You're the only who can save me tonight (it's 3 a.m. here and sry for my bad english).
I rooted my Galaxy S4 (international version - Snap 600 - i9505) and I flashed the latest nightly of cyanogenmod. I started my device and, after 4-5 minutes, the rom started. I felt immediately disappointed, it's a pre-alfa version and I installed it just to try it.
So, I decided to install the Pure Google Rom with Android 4.3 (http://forum.xda-developers.com/showthread.php?t=2341026).
I rebooted my device, but for some reasons (I got a small crash, because I failed, removing my battery during the boot animation), my phone is now stucked at the title screen.
I can see just "Samsung Galaxy S4 - GT_i9505" on an infinite black screen. I'm so sad, I wish to solve this problem...
P.S. I tried to reboot in recovery mode: almost the 70% of the times I tried, it failed entering recovery mode. The only time it entered recovery, I wiped everything, but nothing seems to change.
Please help :\
Click to expand...
Click to collapse
Usually the international version is i9500 running on Exynos Octa core. Are you sure you loaded the right firmware?
If you have flashed the custom recovery (CWM, Philz, TWRP), you can try to load different firmware (copy to SD card first). Worst case, you can use Odin to flash. Unless it is hardware problem, it is not easy to brick the phone.
Thx
tingtan said:
Usually the international version is i9500 running on Exynos Octa core. Are you sure you loaded the right firmware?
If you have flashed the custom recovery (CWM, Philz, TWRP), you can try to load different firmware (copy to SD card first). Worst case, you can use Odin to flash. Unless it is hardware problem, it is not easy to brick the phone.
Click to expand...
Click to collapse
Thank you, I flashed the philz touch version for i9505 and it works flawlessly. I installed the Google Stock Rom and it's working. I'll update tomorrow if I got crashes or black screens.
Thank you so much tingtan
Hi,
i have serious problems with my S4(i9505):
I rooted it when i got it and have installed various roms so far. The last working one was "liquid smooth".
Then it begann to reboot from time to time and when the problems got worse i decided to reinstall again... now, i think my problems arrived with the 4.4 roms. I installed pacman and tried to boot, it didn't work and i think that's when my bootup sequence changed, now i have a little text in the corner saying "kernel is not seandroid enforcing. Set warranty bit : kernel"
so i thought something must be wrong with the kernel and installed various kernels, hoping to clear that message in the corner. At some point i realized that this only makes my situation worse (s4 reboots directly after booting, while bootin, while finishing up "first boot", it gets stuck in bootloops, etc).
Right now i'm not even sure if i understand the whole concept of kernels and roms anymore... so i decided to ignore the message for now and focus on getting my phone to work... i installed some roms again, some (i think the 4.2'S) seem to work, the 4.3's all crash while booting...
i managed to get liquid smooth back on it again (2.9).
Oh and i tried reinstalling stock kernel but the installation under CWM aborted.
Now i can use basic phone options again, but as soon as i flash gapps(no matter on which rom (Cyanogen, pacman, liquid smooth), the phone won't boot anymore, i re-downloaded the package several times, it's the latest one, so it should be okay...
S4 google edition of course doesn't work at all ...
Anyone an idea, how i can get google apps back ? Or basically just get my phone to work ?
Furthermore : How do i clear the message (kernel is not seandroid enforcing)? My basic goal is to have a working android 4.3 enviroment with gapps...can't be that hard ...
i spent the whole day on that, i have used searchfunction not only on this forum, so sorry if i have missed a thread stating the same problem. Plus: i need someone to talk to
EDIT:
I've installed Stock ROM, now it keeps rebooting at the point where i can set up wlan ...
I rooted my J5 (SM-J500FN) yesterday the first time. Since then I reflashed the CF-Auto-Root file about 5 times because my phone got stuck at the bootup screen (on the top of the screen it said in yellow: Set Warranty Bit : kernel). This was due to Samsung KNOX which I somehow was able to deactivate it. After trying many times I now can restart my phone consistently without any bootloops (the yellow text is still there).
My problem now is that after about 3 minutes runtime root checker doesnt detect my device as rooted. SuperSU writes that my device isnt rooted. After a restart root works again for maximum 5 minutes. Im really puzzled because I never experienced someting like that befor and I have no clue how to solve this...
-Toby
Toby9 said:
I rooted my J5 (SM-J500FN) yesterday the first time. Since then I reflashed the CF-Auto-Root file about 5 times because my phone got stuck at the bootup screen (on the top of the screen it said in yellow: Set Warranty Bit : kernel). This was due to Samsung KNOX which I somehow was able to deactivate it. After trying many times I now can restart my phone consistently without any bootloops (the yellow text is still there).
My problem now is that after about 3 minutes runtime root checker doesnt detect my device as rooted. SuperSU writes that my device isnt rooted. After a restart root works again for maximum 5 minutes. Im really puzzled because I never experienced someting like that befor and I have no clue how to solve this...
-Toby
Click to expand...
Click to collapse
Happened to me too in the summer...
CF-autoroot isn't really good... Try the old method of flashing SuperSU trough a recovery (TWRP). this should work with no bugs, no matter what.
That yellow text above the screen: "Set Warranty Bit: kernel" is all good. It indicates that your device is rooted by indirectly saying that the system has been modified. I think that some repair app in the phone is restoring files after startup which makes you lose root after a couple of minutes. I suggest you try flashing with TWRP (custom recovery).
Thank you both. I flashed the SuperSU zip and now it is working perfectly.
So i i wanted to install a clean rom on my note 3 and got this a message when phone is booting.
thats how it started:
-Installed Odin , then installed TWRP then SuperSu with TWRP.
- Downloaded the LineageOS for note 3 and GAPPS, insalled it and it wasnt stable at all
Had every few minutes restarts with the message "Set warranity bit kernal" at top of the screen.
- Decided to try other rom(MagMa NX s8) , so i download older TWRP for this , installed the rom properly and then reboot
and its got stuck into this message again "Set warranity bit kernal" and didn't boot into the rom at all..
I wanted to try this ROM so hard heh..
- Now im with Resurrection REMIX which is stable and no restarts or bugs, but the message is still there when the phone is booting up.
tried so many things to fix it , could find away tried different kernals, didn't help , tried YouTube guides - none worked for me.
anyone is familiar with this issue?
arlxcvi said:
So i i wanted to install a clean rom on my note 3 and got this a message when phone is booting.
thats how it started:
-Installed Odin , then installed TWRP then SuperSu with TWRP.
- Downloaded the LineageOS for note 3 and GAPPS, insalled it and it wasnt stable at all
Had every few minutes restarts with the message "Set warranity bit kernal" at top of the screen.
- Decided to try other rom(MagMa NX s8) , so i download older TWRP for this , installed the rom properly and then reboot
and its got stuck into this message again "Set warranity bit kernal" and didn't boot into the rom at all..
I wanted to try this ROM so hard heh..
- Now im with Resurrection REMIX which is stable and no restarts or bugs, but the message is still there when the phone is booting up.
tried so many things to fix it , could find away tried different kernals, didn't help , tried YouTube guides - none worked for me.
anyone is familiar with this issue?
Click to expand...
Click to collapse
thats not an issue. Its normal if you had flashed a custom ROM. I am running RRN only for the past 4 months... that message has always been there for long time.
Hello XDA! I recently came into ownership of two Galaxy Tab 4 10.1 WiFi tablets that came factory reset with Android 5.0.2, they are the SM-T530NN variant for education as these came from a school - and I wanted to flash them with LineageOS. I had already rooted and flashed my Nexus 7 with LOS with no issues and really like it, so I figured I would do that too on these Tab 4's.
The problem I am running into is once I install LineageOS and Supersu from TWRP, the tablet reboots and can't get passed the following message:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: Kernel
I've read that this is not an error, and has something to do with the rooting process or possibly the ROM that I used itself, but nonetheless, it just sits at that error and never fully boots, hence why I can't just ignore it. My OS appeared to install with no errors. Other posts that I have researched on this forum concerning that message don't fully provide me with a solution I can replicate. However, I still have access to download mode and TWRP recovery upon boot so all does not appear to be lost.
I started with thisisapoorusernamechoice's guide (which was awesome by the way) for rooting and have kinda gone from there, trying newer version's of TWRP but am still stuck at boot.
Here are the files/versions I have used:
Odin 3.11.1
twrp-3.0.0.9_matisse_20160314-0843.tar (and 3.0.3.0)
lineage-14.1-20170319-UNOFFICIAL-matissewifi
supersu 2.79
Any help would be greatly appreciated.
***UPDATE***
Never saw any replies to this post so I decided to just try a different ROM, went for Bliss 6 to see if it would boot. Sure enough I still get the same message as before but it does boot up and is usable! Some minor things are not working like the camera app crashes upon opening, and the lock screen date and time are all smashed together - but these are minor inconveniences as these tablets will only be used for Plex, not taking pictures. Plus I still have a TWRP backup of the stock ROM should I choose to go back to that.