I followed the instructions located at http://androidcentral.us/2014/04/how-to-root-sprint-samsung-galaxy-s5-sm-g900p/ , my Galaxy S5 wouldn't boot. It was stuck on a screen which said "Recovery is not seandroid enforcing".
I found a post elsewhere on the xda-developers forums which suggested re-doing the CF Auto Root step and pulling the battery before the phone reboot, which I successfully pulled off but the phone still would not get past the "Recovery is not seandroid enforcing" screen.
I was able to restore my phone to a usable state using http://forum.xda-developers.com/showthread.php?t=2734322&page=7 and a utility for converting .img files to files suitable for Odin to upload to the phone. However, I'd still like to get the phone rooted.
Can anyone help? Would perhaps loading a standard KitKat kernel first be what's needed? I haven't done any modifications to the phone before this, but I realize that Sprint may have, and I'm wondering if that's what's throwing the process off.
Related
CyanogenMod 12.1 ERROR "KERNEL IS NOT SEANDROID ENFORCING SET WARRANTY BIT: KERNEL"
Hi. I am working on a brand new Samsung SM-G900F i.e. a Samsung Galaxy s5.
I shall explain how I have got where I have got below - which ended up with a rooted, working phone running CyanogenMod 12.1, Android 5.1.1 and with the GAPPS (Google Apps) on it, but the question is simply this: -
"How do I get rid of the error message that appears when I boot at the top left of the screen
KERNEL IS NOT SEANDROID ENFORCING
SET WARRANTY BIT: KERNEL
?"
I have set out the following in detail, in case the sequence of steps I undertook will assist other users, or enable them to recognise whereabouts in the sequence they are experiencing errors.
1) I am in the UK. The phone is a brnd new, boxed Samsung SM-G900F which uses LTE (it says so on the box, whatever LTE is).
2) The phone is not network locked: I bought it from MobilePhonesDirect (a big online retailer here in the UK) but I have a Vodafone (UK) SIM card in it, and it has hitherto worked. I am porting a number across to it such port taking effect today.
3) On the new phone I downloaded an upgrade to Android 5.0. I then encrypted the phone which took less than an hour, but quite a long time nonetheless.
4) This wasn't good enough! I wanted Android 5.1 or Android 5.1.1, so ....
5) I connected the phone to my Windows 10 PC via USB, and I attempted to use Kies. This told me to use a newer product called Smart Switch to communicate with the phone. I installed this and was able to communicate.
6) I used ODIN 3.07 to flash things to the phone. I flashed CF-Auto-Root-klte-kltejv-smg900fq and I successfully rooted the phone. Upon boot it was still running Android 5.0 and it was still encrypted.
7) I flashed ClockWorkMod (CWM) to the phone, this version: g900f-cwm-recovery-6.0.4.7
8) I flashed the following zip files to the phone [TN]-VM12.1-20150327-2.0.0-klte and gapps-5.1.x-20150324-minimal-edition-signed.
9) The phone started to boot, but I got the Cyanogenmod 12.1 "Encryption Unsuccessful" message and it would not get past that.
10) I read up. I had used the wrong Cyanogenmod file, I think. I then discovered that as the phone would not boot I was unable to get any files onto it.
11) I then, from CWM, did a factory reset, wiped the cache, and wiped the Dalvik cache
12) I discovered the wonderful, wonderful ADB feature in CMW. I managed to find a piece of software called fastboot.zip. Eventually I worked out the sequence of commands and the syntax (thanks to a YouTube video which I wished to link to but I cannot find what it was I used last night!).
12) I flashed these two slightly different CyanogenMod 12.1 / GAPPS files to the phone: cm-12.1-20150428-UNOFFICIAL-klte.zip and gapps-lpmr1-20150324-signed.zip.
13) It still had errors. I went back to CWM and I "unmounted" and "formatted" this, that and everything, and I eventually got those two zips to work.
13) The phone now functions effectively, BUT ....
14) I still get the error message
KERNEL IS NOT SEANDROID ENFORCING
SET WARRANTY BIT: KERNEL
The above took me about 4 and a half hours in total, watching YouTube tutorial videos etc etc.
I am very grateful for all of those who share their knowledge. I would love it if someone knew how to get rid of that error message. I read something about it being Samsung Knox. I tried to run a command line command from a terminal emulator on the phone, but I got an error message.
BlameTheMachines
(to quote Duran Duran!)
This error is normal because CM12.1 has unsecured kernel. CM12.1 Kernel doesn't support SEAndroid and is not secured so that's why you are getting this error.
Bruce666 said:
This error is normal because CM12.1 has unsecured kernel. CM12.1 Kernel doesn't support SEAndroid and is not secured so that's why you are getting this error.
Click to expand...
Click to collapse
Many thanks. Would you have any idea how I can work around this? When using CM 12.1 and Android 5.1 on my Galaxy SIII up until yesterday there has been no issue (except the fundamental crash issue on power loss reported in my post today elsewhere on this Forum!).
Any tips would be appreciated, and at least I now know it is CM 12.1 not any of the other permutations and combinations of my set-up. I thought of posting on here: http://forum.cyanogenmod.org/
All the best,
BlameTheMachines
Please help if you can.
I tried to root my phone and I should not have. Now the phone is stuck with the message "Recovery is not seandroid enforcing".
I have Odin installed and the stock ROM (from SamMobile) but my computer won't recognize the phone.
Model is Samsung Galaxy S5 Active - SM-870W.
Any advice is appreciated.
Thnx
erinforrest said:
Please help if you can.
I tried to root my phone and I should not have. Now the phone is stuck with the message "Recovery is not seandroid enforcing".
I have Odin installed and the stock ROM (from SamMobile) but my computer won't recognize the phone.
Model is Samsung Galaxy S5 Active - SM-870W.
Any advice is appreciated.
Thnx
Click to expand...
Click to collapse
have you installed the Samsung driver on your computer?
which file have you downloaded from sammobile?
erinforrest said:
Please help if you can.
I tried to root my phone and I should not have. Now the phone is stuck with the message "Recovery is not seandroid enforcing".
I have Odin installed and the stock ROM (from SamMobile) but my computer won't recognize the phone.
Model is Samsung Galaxy S5 Active - SM-870W.
Any advice is appreciated.
Thnx
Click to expand...
Click to collapse
This problem happens when your installed recovery doesn't match your current firmware version. Like flashing a cf-auto root file of 6.0.1 firmware on a 5.1.1 phone. You have to check if your drivers has been installed properly or not. If you need the data on your phone you can just flash your specific recovery for your firmware. You must extract it from the rom file and convert in into a tar file. I can give you instructions on that. Reply my post if you need further help on this issue.
Update
Thanks Everyone for your responses.
I left my phone off with the battery removed for 24 hours and the error "..not seandroid enforcing" stopped appearing. I was then able to re-flash with the appropriate firmware and problem solved.
So for anyone still struggling, I advise taking the battery out and trying to leave it be for 24 hours. Not sure why that would help but sometimes you just need to step away lol.
Hi Guys,
I have a sm-n910u (note 4) that my brother has attempted to flash. however its now stuck in the reboot loop with error "recovery is not seandroid enforced"
I personally am very new to the whole phone flashing, rooting and modding stuff but very experienced in IT.
I have played around with different roms and oden but cant seem to make it work
I was hoping that someone might be able to guide me in at least getting the factory system back on there.
details are sketchy about what has been done already but i do have the device here.
any help would be awesome.
Thanks in advance
My son no longer uses his Tab 4 8.9 T337T tablet.
I was able to root it using CF Auto Root.
But, the TWRP recovery that was made for it might had messed up the tablet.
It boots up as far as the T-Mobile screen.
I found the T337T firmware to use with ODIN and I can get to download mode and the tablet is recognized by ODIN.
However, when I go to place the files into ODIN, the program goes to eventually a not responding state.
I had encountered a Set Warranty Bit: Kernel issue.
Amy suggestions on how to fix this would be appreciated.
Also, is there any way for me to change the firmware to a wifi-only model firmware?
Looks like I figured it out after trying a half dozen options...
pit file could yuo have it
Bought a Galaxy S7 Edge today from a coworker, SM-G935F, Verizon variant (as far as I know. She bought it brand new and used it on Verizon.) First thing I tried to do was root it using this method -- https://theunlockr.com/root-samsung-galaxy-s7-s7-edge/
(basically used Odin to flash Samsung_G935x_QC_Rooted_BOOT.TAR)
Got a "Pass!" message in Odin, rebooted the phone.
Was greeted with a pretty red-colored message on the top left, "kernel is not Seandroid" followed by a continuous bootloop. Would automatically shut off on its own, etc. Had to boot into recovery to actually power it off. (Still stock recovery, by the way)
Anyway. Googled the error, didn't seem like a big deal with so many results and "Solved" also being prominant. Tried to revert back to the stock firmware and got this in Odin's log:
<ID:0/003> Re-Partition operation failed.
Came across another post suggesting to un-tick the "re-partition" option in Odin, which it already was/is. Now I'm kind of lost on what to do. Came across one thread suggesting that the firmware on my device doesn't match the one that I downloaded which.. I have no idea how to check that given I'm unable to even boot the device. I do recall seeing 2017 briefly when scrolling through the build/kernel section, possibly December 2017 if my memory serves me correctly.
Another thread suggested something about flashing a .pit file.
Does anyone know I how I can get this back up and running? Preferably rooted?
Thanks much in advance!
- D
..