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.
Related
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 ...
Hello, i recently purchased a samsung s5 900w8. I had one before rooted with alliance rom fully customized but i lost it at work in contruction. so i rooted my phone no problem got twrp on it and tried this with philz touch on it no problem. but when i go to install the rom i get ether one or two problems same on both recoverys, also tried different versions for alliance rom. It ether says it installed good i go to reboot and it keeps loop back to recovery when i boot it. Or when it installs and i go to reboot, it says root not detected will you root now (i've selected both options) and it gets stuck at the samsung powered by android logo. I've followed video and article how to's and for this mod and i still am having these problems please help.
tr0nic135 said:
Hello, i recently purchased a samsung s5 900w8. I had one before rooted with alliance rom fully customized but i lost it at work in contruction. so i rooted my phone no problem got twrp on it and tried this with philz touch on it no problem. but when i go to install the rom i get ether one or two problems same on both recoverys, also tried different versions for alliance rom. It ether says it installed good i go to reboot and it keeps loop back to recovery when i boot it. Or when it installs and i go to reboot, it says root not detected will you root now (i've selected both options) and it gets stuck at the samsung powered by android logo. I've followed video and article how to's and for this mod and i still am having these problems please help.
Click to expand...
Click to collapse
I would try installing a different kernel, Adam kernel by wanam works good for me.
http://forum.xda-developers.com/showthread.php?p=55526561
Also I would use ktoonsez latest version of twrp.
http://forum.xda-developers.com/showthread.php?p=53277016
And if all else fails, I would re-download the rom, just in case it is a bad download.
SM-G900W8, 0x1
A recovered flashaholic since Aliance Rom 5.5
First of all, hello all!
I'm a new member here.
So, what's the problem? Well, I recently rooted my Galaxy Tab 4 SM-T530 (WiFi only version) with Kingroot. Then I installed Cyanogenmod from the thread listed at the ROM section. All was working fine up until I decided to flash the GApps.
I chose the newest versions (both Zero and Mini for 6.0) but none of them worked.
Flashing went well. The problem was after booting.
After the first boot, I'd get caught in an endless loop of errors stating that "Unfortunately, Setup Wizard has stopped working". I couldn't do much other than rebooting. But then, I was greeted with yet another problem: it was stuck in a boot loop. Basically, after saying that it "Prepared Google App" and some others, the tab would repeat the process in an infinite loop. I left it for half an hour to do so, but the problem persisted.
Keep in mind the fact that I installed the newest version of Mini GApps package provided from that thread.
If any of you can help me out with this, I'd be very thankful, since this is the same time I install a custom ROM, and I really don't want to come back to the old Samsung ROM
http://forum.xda-developers.com/tab-4/development/rom-slimrom-5-0-1-alpha-0-7-t2963906
This is from where I installed all things needed.
Try again, this time flash both zips at the same time and not doing anything in the middle of both flashes. The usual cause of the same error in my other s3 is booting the ROM up, going back to recovery, then flashing GApps.
I never did anything else. Now I wiped data/dalvik/system/cache, reflashed the ROM and now just finished reflashing both zips in TWRP (first Mini then Zero, can't do them at the same time).
Now, I'm pretty much 'fingers crossed', as this is what an error told me. Pretty much tried to flash the zips without wiping anything/reflashing the ROM. That's why I went for a clean install.
EDIT: it didn't work at all. Still caught in the same "Preparing app x" boot loop. Now I'll let it run for 6 hours and see if not my own impatience is the problem.
EDIT 2: For some reason it took ages to boot up. Now, when I finished booting, I saw that the Play Store, Quick Search Bar and the Google Services weren't working at all. I tried to manually update them, but ended up in an agonizing loop of "Unfortunately, Google Services Framework has stopped" errors. Again, this leads me into thinking that the GApps from that thread aren't working.
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.
Never mind. Solved after a LOT of trial and error.
----
I have a Zenfone ZE552KL in a weird predicament. I was running the Unofficial Lineage OS rom for a while. It initially had a bad bug that made it unusable (couldn't use the keypad while on a call, phone would crash). I finally got around to installing an updated version of the rom which fixed that issue, but then the battery was lasting barely 8 hours (instead of the usual 20+ hours). I decided to give up and go back to stock. I followed some instructions and installed the MM stock rom, went back to stock boot and recovery, then tried to update to stock Nougat, and I can't do that. Every time I try flashing from the SD card in the stock recovery, I get "E: Failed to verify whole-file signature" and the installation aborts. I've tried every fix imaginable (re-downloading, downloading different versions, trying different SD cards, etc), and I just can't get it to work.
So right now my options seem to be use LOS with an 8hr battery life, or use an old buggy MM stock experience.
Can anyone point me in the right direction so I can have something usable? Is there a LOS specific version that doesn't have major battery issues AND has a working phone? Is there anything I can do to get the stock OS back to Nougat?
<sigh>
A
TWRP recovery allows you to toggle "zip verification" when installing roms. Flash TWRP and then flash your Rom while making sure "zip verification" box is unchecked.
I finally made progress today. I was able to flash the stock Nougat FW using TWRP, but only after flashing LOS to it first. I have no idea why. But it works and I'm done playing with it. It's just too buggy and there isn't enough of a dev community for it.