I have a N910T which I've flashed TWRP 3.0.2.0 to via odin.
I can get into recovery fine and install roms, they all seem to extract and install correctly but I get put into a bootloop upon reboot.
I do get;
"KERNEL IS NOT SEANDROID ENFORCING"
"SET WARRANTY BIT: KERNEL"
but from reading that doesn't matter much, generally.
I'm really stuck at the moment. I've tried the various Aroma based installers for a few roms and all do the same.
Flashing stock via odin works fine though, so I know the phone itself is good.
Any ideas what could be causing the bootloops?
Related
When I try to flash CF-Auto-Root, my phone goes into a recovery boot loop and It just says:
"Kernel Is Not Seandroid Enforcing
Set Warranty Bit: Kernel"
Then it reboots, and goes to that page again, and so on. I reflashed stock 4.4 and tried rooting again, but with no success.
Any help please would be appreciated!
If it helps, my phone is a Rogers Canadian Variant SM-900W8.
3teenth said:
When I try to flash CF-Auto-Root, my phone goes into a recovery boot loop and It just says:
"Kernel Is Not Seandroid Enforcing
Set Warranty Bit: Kernel"
Then it reboots, and goes to that page again, and so on. I reflashed stock 4.4 and tried rooting again, but with no success.
Any help please would be appreciated!
If it helps, my phone is a Rogers Canadian Variant SM-900W8.
Click to expand...
Click to collapse
this link could be help you:http://forum.xda-developers.com/showthread.php?t=2614772
For anyone who has this issue, I found a solution. In the CF-Auto-Root thread, download and flash the "CF-Auto-Root-hlte-hltexx-smn9005.zip" instead of the one made for your carrier as the stock recovery image in that one is actually updated for 4.4. It worked flawlessly for my phone.
I found a few of these topics but cant seem to find a solution.
1. I flashed CF-Auto-Root-klte-kltexx-smg900f using odin 3.09
2. Then flashed philz_touch_6.26.1-klte.tar using odin 3.09
3. From there booted into philz i whiped to clear for new ROM and installed http://forum.xda-developers.com/showthread.php?t=2741302 from my ExtSD
Now after this it goes into a bootloop telling me
"Kernel is not seandroid enforcing
Set warranty bit : kernel"
I then found out from there topics i had something to do with Knox, so i then flashed "Nordic_countries_G900FXXU1ANE4_G900FNEE1ANF1_NEE" using Odin 3.09.
And it boots fine, but since i want a new ROM and didn't find out what did it, it happens every time i try flash the custom ROM.
I got a Samsung SM-G900F.
What am i missing?
Kiggerbare said:
I found a few of these topics but cant seem to find a solution.
1. I flashed CF-Auto-Root-klte-kltexx-smg900f using odin 3.09
2. Then flashed philz_touch_6.26.1-klte.tar using odin 3.09
3. From there booted into philz i whiped to clear for new ROM and installed http://forum.xda-developers.com/showthread.php?t=2741302 from my ExtSD
Now after this it goes into a bootloop telling me
"Kernel is not seandroid enforcing
Set warranty bit : kernel"
I then found out from there topics i had something to do with Knox, so i then flashed "Nordic_countries_G900FXXU1ANE4_G900FNEE1ANF1_NEE" using Odin 3.09.
And it boots fine, but since i want a new ROM and didn't find out what did it, it happens every time i try flash the custom ROM.
I got a Samsung SM-G900F.
What am i missing?
Click to expand...
Click to collapse
First root a stock ROM and be sure SU is installed and on that same ROM run SU, then you should be able to disable KNOX, after that you can go and use custom ROMs.
For good step by step instructions go here:
http://galaxys5root.com/galaxy-s5-root/how-to-root-galaxy-s5/
Hi everyone!
So I was a complete fool and with my (rooted) galaxy s4 running 4.4.4 (or 4.4.2) kitkat I downloaded the Lolipop update for my Bell SGH-1337m.
I used an Xda module to change my status from "custom" to something along the lines of "stock" and was then able to download the lolipop update. I should mention that i had clockworkmod installed on this phone, but before the update I had also unchecked all my xposed modules. So then I went to update...
now whenever I try to boot I get "Recovery is not seandroid enforcing" with another message "set warrenty bit: recovery". These two messages also appear even after I boot into recovery (just with "Recovery Booting..." text coming first followed by the rest)
I have attempted flashing multiple ROMS through Odin, as well as a stock recovery file. I am still stuck at this boot process.
Any help would be greatly appreciated as I'm in a new city and need my phone to get around... yeah... I screwed myself :laugh:
"Recovery is not SEAndroid Enforcing" is normal. All that's telling you is that the custom recovery is still installed. With a custom kernel, the message would be "Kernel is not SEAndroid Enforcing" and would appear on the S4 splash screen.
Have you attempted to flash the ROM via Odin with a .PIT file for the I337M? If not, you should find one over in the forums where this should have been posted, http://forum.xda-developers.com/galaxy-s4-att . Fortunately, in the international S4 forums here, the question is general enough that we should be able to help you anyway.
The .PIT file provides Odin with the correct partition information for your S4, which can ensure the ROM gets installed properly.
Strephon Alkhalikoi said:
"Recovery is not SEAndroid Enforcing" is normal. All that's telling you is that the custom recovery is still installed. With a custom kernel, the message would be "Kernel is not SEAndroid Enforcing" and would appear on the S4 splash screen.
Have you attempted to flash the ROM via Odin with a .PIT file for the I337M? If not, you should find one over in the forums where this should have been posted, http://forum.xda-developers.com/galaxy-s4-att . Fortunately, in the international S4 forums here, the question is general enough that we should be able to help you anyway.
The .PIT file provides Odin with the correct partition information for your S4, which can ensure the ROM gets installed properly.
Click to expand...
Click to collapse
OK great! Hopefully I'll find the answer for a .PIT file in terms of setting it up with Odin, I suppose it has something to do with the "re-partition" option in odin, but I'm not doing ANYTHING without a tutorial first
I'll get back to you after I've tried it with a SGH-1337M .PIT file, hopefully I can find one... (Canadian S4 variant, same hardware as AT&T but just the M is different)
You are correct in that it has to do with the re-partition option in Odin. You should have an option to browse to the .PIT file, so Odin knows where to find it. Once Odin sees the file, check "re-partition", and then flash a stock ROM.
I have rooted my samsung note 4 sm-n910f but i have got to the point that it boots up fully but on boot up i get recovery is not seandroid enforced and when i try to use supersu the binary install fails any help would great please
thanks
The "Recovery is not SEAndroid enforced" isn't any big deal, it is a part of KNOX. It is just a proof that you have compromised the device, since you have a "custom" recovery. Now for the root part, you actually need to flash a custom kernel which can be found in the development section of your device (Snapdragon). I recommend you get a modified stock kernel, just like I use, but I am on C variant. Make sure you backup your very stock Kernel which is "boot". Flash the modified kernel through recovery, then install SuperSU. Also, you will start seeing "Kernel is not SEAndroid enforced", since you have flashed a custom kernel, but again it is no big deal.
If it helped you, please hit the thanks button.
Hi, I tried to install a custom recovery with odin. On the odin panel it said "SUCCESS" but as far as I can see, it is not a success.
Now it's bricked and I don't know what to do. I can't take out the battery. I have my stock ROM ready.
alKS9992 said:
Hi, I tried to install a custom recovery with odin. On the odin panel it said "SUCCESS" but as far as I can see, it is not a success.
Now it's bricked and I don't know what to do. I can't take out the battery. I have my stock ROM ready.
Click to expand...
Click to collapse
Put it back in download mode and flash the stock firmware.