Hi i read around and seen many different suggestions on this but was wondering if there was a clearly outlined step by step for this phone factory unlocked but carrier is Telus Canada SGH-I337M
I have factory reset the phone with oden after putting cyanogen-mod on it and now i have no sound, no wifi, and when i try to make calls it freezes the phone
I also have the "kernel not seandroid enforcing set warranty bit: kernel
I have tried various different methods listed on this site and others all to no avail and now i am frustrated and confused lol
Is there a step by step to make this all work again or have i coma-toasted my phone and should chuck it in the river?
thanks alot for any tips greatly appreciated
Hello People
Looking for some help.
I have recently installed CM11 on my galaxy note 3. its is a great ROM works great and has some brilliant features compared to the samsung bloated stock ROM I had.
I have just had an update show up on my phone so I clicked to download it. once downloaded it had the icon for install which I did.
After that it has just gone in to bootloop and will not even boot into recovery its saying
recovery booting........
recovery is not seandroid enforcing
set warranty bit: recovery
an that is it. it just keeps turning itself off and on.
I cannot get it to boot into recovery or download mode or anything.
Please help I am desperate. I am moving to australia from the UK on monday and really need my phone.
Many thanks in advance for any help
Glen
crookers13 said:
Hello People
Looking for some help.
I have recently installed CM11 on my galaxy note 3. its is a great ROM works great and has some brilliant features compared to the samsung bloated stock ROM I had.
I have just had an update show up on my phone so I clicked to download it. once downloaded it had the icon for install which I did.
After that it has just gone in to bootloop and will not even boot into recovery its saying
recovery booting........
recovery is not seandroid enforcing
set warranty bit: recovery
an that is it. it just keeps turning itself off and on.
I cannot get it to boot into recovery or download mode or anything.
Please help I am desperate. I am moving to australia from the UK on monday and really need my phone.
Many thanks in advance for any help
Glen
Click to expand...
Click to collapse
Bump.. I have the same bootloop issue after upgrading cyanogen i also am unable to use ODIN to get back to stock any suggestions?
Thanks in advance
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.
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
Hi, I need your help guys, this is the problem:
I have a Samsung Galaxy S6 EDGE+ with Android 6.0.1 Marshmallow and the model is SM-G928F. No problem here.
So I decided to flash twrp with Odin, all correctly, version, compatibility, etc.
I plugged the phone in download mode, and flashed the twrp. All seems to be fine.
BUT just after that, when the phone is rebooting, it appears a message in red: "recovery is not seandroid enforcing" and i can't pass to recovery mode. The only way to fix it is flashing the stock firmware. So I can't install any custom recovery and I don't know how to fix that problem and I need the custom recovery as soon as possible. If anyone know the solution, please ask me. Thanks :fingers-crossed:
That is a common problem.The cause is that you dont have an mm compatible twrp.Use this http://forum.xda-developers.com/s6-...ecovery-official-twrp-galaxy-s6-edge-t3354492 Also dont forget that the first thing you must do is flash a kernel
@ÆROMIND - It's possible @Rainbow_Dash is correct, but if you did as you said and had checked version, compatibility etc, try this first:
After installing TWRP, as soon as the screen goes dark when rebooting - and you have to be quick - hit the volume up/power/home buttons simultaneously and keep them pressed. You should reboot into recovery.
I had the same problem, this worked. The "recovery is not seandroid enforcing" is normal btw.
B3311 said:
@ÆROMIND - It's possible @Rainbow_Dash is correct, but if you did as you said and had checked version, compatibility etc, try this first:
After installing TWRP, as soon as the screen goes dark when rebooting - and you have to be quick - hit the volume up/power/home buttons simultaneously and keep them pressed. You should reboot into recovery.
I had the same problem, this worked. The "recovery is not seandroid enforcing" is normal btw.
Click to expand...
Click to collapse
Thanks very much for the support, I will try it.
I'll let you know if it's work, thanks!
ÆROMIND said:
Thanks very much for the support, I will try it.
I'll let you know if it's work, thanks!
Click to expand...
Click to collapse
But just a question:
@Rainbow_Dash Said to me that I need to flash a custom kernel, maybe he have reason because I'm using the Marshmallow stock firmware, and it have more security. Perhaps that's is the problem. In that case, will I need to flash a kernel? Anyway, I don't want it, because customs kernel usually have problems with battery and a few more like wi-fi spontaneous disconnections.
ÆROMIND said:
But just a question:
@Rainbow_Dash Said to me that I need to flash a custom kernel, maybe he have reason because I'm using the Marshmallow stock firmware, and it have more security. Perhaps that's is the problem. In that case, will I need to flash a kernel? Anyway, I don't want it, because customs kernel usually have problems with battery and a few more like wi-fi spontaneous disconnections.
Click to expand...
Click to collapse
I wont lie on 100% stock roms costum kernels are often a terrible idea resulting in what you mentioned.But if you use a good costum rom (like audax plus my tw favourite) that will not be a problem and many times resulting in a better experience and battery life etc
@ÆROMIND - did you solve it?
Why can't I just flash one with Odin? As other mobile holders could do. What's the problem with the Samsung Galaxy s6 Edge + ? I mean I tried everything what's in this post but it is hanging on RECOVERY IS NOT SEANDROID ENFORCING. I've just flashed the stock rom with Odin. But I got an enormous battery drain caused by Android OS and everyone is saying the only solution is rooting your phone. I got a Samsung Galaxy s6 Edge + (928F PDA G928FXXS2BPE2
CSC G928FPHN2BPB6)
S6EdgePlus928FUser said:
Why can't I just flash one with Odin? As other mobile holders could do. What's the problem with the Samsung Galaxy s6 Edge + ? I mean I tried everything what's in this post but it is hanging on RECOVERY IS NOT SEANDROID ENFORCING. I've just flashed the stock rom with Odin. But I got an enormous battery drain caused by Android OS and everyone is saying the only solution is rooting your phone. I got a Samsung Galaxy s6 Edge + (928F PDA G928FXXS2BPE2
CSC G928FPHN2BPB6)
Click to expand...
Click to collapse
Because you can try every twrp if you want even if its listed working for edge plus.If it is not compatible with mm bootloader it wil hang at seandroid enforcing which is why you must get the one i linked up there.If you have lolipop flash whatever you want.
S6EdgePlus928FUser said:
Why can't I just flash one with Odin? As other mobile holders could do. What's the problem with the Samsung Galaxy s6 Edge + ? I mean I tried everything what's in this post but it is hanging on RECOVERY IS NOT SEANDROID ENFORCING. I've just flashed the stock rom with Odin. But I got an enormous battery drain caused by Android OS and everyone is saying the only solution is rooting your phone. I got a Samsung Galaxy s6 Edge + (928F PDA G928FXXS2BPE2
CSC G928FPHN2BPB6)
Click to expand...
Click to collapse
Alot of people (including me) have had the same problem. Strange thing is 3.0.0 worked just fine. The probs started when I updated to 3.0.2. After that I haven't been able to install ANY of the previous versions. Then I saw that someone was using the version for note 5 noblelte. So I tried and it worked like clockwork.. I'm on G928F with the latest bootloader from Sammy.
B3311 said:
@ÆROMIND - did you solve it?
Click to expand...
Click to collapse
I didn't, basically because i was waiting for a reply, but nothing. The reason that i didn't try to solve the problem, it's because i don't really know what will happen to my S6 (and this was so annoying cause i flashed stock firmware to fix the ''recovery is not seandroid enforcing'' like 6 times, and as you can understand , I didn't want to do it again), and probably nothing good would come out.
Anyways, i will not leave this thread, so keep leaving comments to solve this problem in community. Thanks to all
ÆROMIND said:
I didn't, basically because i was waiting for a reply, but nothing. The reason that i didn't try to solve the problem, it's because i don't really know what will happen to my S6 (and this was so annoying cause i flashed stock firmware to fix the ''recovery is not seandroid enforcing'' like 6 times, and as you can understand , I didn't want to do it again), and probably nothing good would come out.
Anyways, i will not leave this thread, so keep leaving comments to solve this problem in community. Thanks to all
Click to expand...
Click to collapse
I (as many others) had your problems. Me (and others) solved it by installing 3.0.2-1 for note 5 noblelte. Works perfect.
I'm on a G928F Latest firmware.
thools60 said:
I (as many others) had your problems. Me (and others) solved it by installing 3.0.2-1 for note 5 noblelte. Works perfect.
I'm on a G928F Latest firmware.
Click to expand...
Click to collapse
Are you sure? Okey, as you say it works, I'm going to try it, if that solve the problem, you will helped me so much!!
B3311 said:
@ÆROMIND - It's possible @Rainbow_Dash is correct, but if you did as you said and had checked version, compatibility etc, try this first:
After installing TWRP, as soon as the screen goes dark when rebooting - and you have to be quick - hit the volume up/power/home buttons simultaneously and keep them pressed. You should reboot into recovery.
I had the same problem, this worked. The "recovery is not seandroid enforcing" is normal btw.
Click to expand...
Click to collapse
Awesome! I was having problem into going into twrp on a Galaxy s6 and this fixed it! =D