Hi. I'm just flashed this rom: http://forum.xda-developers.com/tab-4/development/rom-cyanogenmod-12-1-t3097152 and then flash moonbutt's testing kernel, then i got a "Kernel is not seandroid enforcing" error, so i can't boot to system. Please help me to install this rom, my device is sm-t331.
Sorry about my bad English
Thanks.
longhai18 said:
Hi. I'm just flashed this rom: http://forum.xda-developers.com/tab-4/development/rom-cyanogenmod-12-1-t3097152 and then flash moonbutt's testing kernel, then i got a "Kernel is not seandroid enforcing" error, so i can't boot to system. Please help me to install this rom, my device is sm-t331.
Sorry about my bad English
Thanks.
Click to expand...
Click to collapse
"Kernel is not seandroid enforcing" is not an error, that's just the tablet's way of letting you know there's a custom rom installed every time you boot. Every custom rom I've (successfully) installed, I've seen this message on boot.
When you say you can't boot to system, are you letting it try, or do you just power down whenever you see the message? Because the message is not part of the problem.
thisisapoorusernamechoice said:
"Kernel is not seandroid enforcing" is not an error, that's just the tablet's way of letting you know there's a custom rom installed every time you boot. Every custom rom I've (successfully) installed, I've seen this message on boot.
When you say you can't boot to system, are you letting it try, or do you just power down whenever you see the message? Because the message is not part of the problem.
Click to expand...
Click to collapse
I said clearly that i can't boot to system anyway. You mean i have to wait? Yes, i wait, wait and wait but the message still hang on the screen, maybe forever )
Related
Hi everyone!
I've flashed the latest (6.0.0.8) CWM on my L7 using ROM Manager which seemed to go well.
When I try booting into recovery I get the
"Secure booting Error! Cause: boot certification verify" error.
Since regular booting works I've tried to flash it again several times using ROM Manager but to no avail.
Has any of you experienced this issue before?
Googling doesn't seem to help.
Using stock ROM, device rooted using this method.
nexessive said:
Hi everyone!
I've flashed the latest (6.0.0.8) CWM on my L7 using ROM Manager which seemed to go well.
When I try booting into recovery I get the
"Secure booting Error! Cause: boot certification verify" error.
Since regular booting works I've tried to flash it again several times using ROM Manager but to no avail.
Has any of you experienced this issue before?
Googling doesn't seem to help.
Using stock ROM, device rooted using this method.
Click to expand...
Click to collapse
you have your bootloader unlocked?
Sabyn said:
you have your bootloader unlocked?
Click to expand...
Click to collapse
Hi, I somehow missed the thing that LG devices have a locked bootloader.
Thanks for pointing this out.
I unlocked the bootloader using this method.
Nonetheless, problem persists (after reflashing recovery)
Never mind, I figured this out.
Thanks guys you rock.
I tried to install the CWM Recovery using Odin. Device gets stuck in BootLoop with......
1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)
Cant Boot in download mode
It isnt recognized by the pc, odin or kies
Havet find a clear answer in previous posts. Any help?
luisjo2k said:
I tried to install the CWM Recovery using Odin. Device gets stuck in BootLoop with......
1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)
Cant Boot in download mode
It isnt recognized by the pc, odin or kies
Havet find a clear answer in previous posts. Any help?
Click to expand...
Click to collapse
I am in this situation right now as well after flashing CWM recovery via ODIN. Hopefully someone has an answer. Did you find anything?
Try to overwrite your recovery with Philz Touch. It's working perfect for G900 variants so far:
Philz Touch Recovery Download
babygau said:
Try to overwrite your recovery with Philz Touch. It's working perfect for G900 variants so
Click to expand...
Click to collapse
I was finally able to get the phone into download mode by pulling the battery so I just pushed TWRP to it to fix the CWM issues. I'll check out Philz Touch as well though. Thanks.
knoxrents said:
I was finally able to get the phone into download mode by pulling the battery so I just pushed TWRP to it to fix the CWM issues. I'll check out Philz Touch as well though. Thanks.
Click to expand...
Click to collapse
Great!
IMO, Philz Touch is more beatiful and more functional than TWRP
Hi guys - I had this same issue today. I'd also installed CWM and tried to go into recovery mode via ROM Manager when it happened.
Looked around and after finding this thread I managed to flash with Philz Touch and got it to boot. Managed to get it into recovery mode and run this new Philz Touch version of CWM and do a backup. However just before it got into CWM it still came up with:
1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)
Then loaded into CWM whereas before flashing Philz it was just looping. Is there a way I can stop it from coming up with this?
jeemer said:
Hi guys - I had this same issue today. I'd also installed CWM and tried to go into recovery mode via ROM Manager when it happened.
Looked around and after finding this thread I managed to flash with Philz Touch and got it to boot. Managed to get it into recovery mode and run this new Philz Touch version of CWM and do a backup. However just before it got into CWM it still came up with:
1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)
Then loaded into CWM whereas before flashing Philz it was just looping. Is there a way I can stop it from coming up with this?
Click to expand...
Click to collapse
I'm using TWRP and the same thing comes up. It only comes up for a few seconds so I just don't worry about it. With CWM recovery, it was locked on that screen.
knoxrents said:
I was finally able to get the phone into download mode by pulling the battery so I just pushed TWRP to it to fix the CWM issues. I'll check out Philz Touch as well though. Thanks.
Click to expand...
Click to collapse
I have the same problem but when I pull the battery, then reinstall it I get the same result, I need help in a major way this is a brand new company phone
Noebody said:
I have the same problem but when I pull the battery, then reinstall it I get the same result, I need help in a major way this is a brand new company phone
Click to expand...
Click to collapse
I fixed it!!!
..
S5 set warranty bit recovery (G900i)
I know that philz recovery is best solutino but when I am going to download philz it's giving this error:
Hello,
Unfortunately, as of this time, the main portions of goo.im have been disabled. Due to a finance issue, our CDN account has been suspended, and all files stored on it are effectively non-accessible. Due to some RL issues on my(Alexander)'s part, once goo started actively losing money 6 months ago, I had changed jobs a bit to help support goo. Unfortunately, this wasn't enough combined with some other issues that crept up on me. Due to this, I'm formally shutting down Goo. There is an offer in to take over the files and hosting from a generous sponsor, however, until the financial issues are sorted out, they are unable to adsorb Goo. It's been my pleasure to serve files for you all for the past couple of years, and I wish everyone good luck into the future.
-- Snipa/Alexander Blair
If you have picked up a sponor account within the last two months, please reach out to us if you'd like a refund. It may take some time, but we'll do our best to get these processed and sent out. -- Thanks for everyone who's supported us over the years.
Noebody said:
I fixed it!!!
Click to expand...
Click to collapse
How? Same problem here.
jdrch said:
How? Same problem here.
Click to expand...
Click to collapse
I just saw this, and honestly I don't remember. Remind me what's happening and maybe it'll jog my memory
Hello all, long time lurker, first time poster
I was wondering if there is currently a way to get a custom recovery on my phone without the use of a computer. I was able to root my phone using towel root, and first thing I did was install Rom Manager and start to make a nandroid backup until I got:
" RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery"
So I went into download mode, hit cancel and was able to boot into android but to this day I am unable to get into recovery, stock or custom. Due to my current complicated situation I do not have access to a computer and was hoping there was a work around to allow me to implement a custom recovery without a pc. I want to be able to make a nandroid backup, flash zips into the OS, and possibly experiment with other roms... I have tried looking into this myself but the only thing I came up with us an app called "Flashing Tool", though I don't know whether that will allow me to do what I want it to. Oh, and I don't care about Knox being flagged by the way.
So ladies and gentlemen of the Xda community, I beg for your assistance and would greatly appreciate any answers you can give me.
My phone is a T-Mobile Note 3, rooted stock Kit Kat rom, any other info needed just let me know.
Brooklynyte said:
Hello all, long time lurker, first time poster
I was wondering if there is currently a way to get a custom recovery on my phone without the use of a computer. I was able to root my phone using towel root, and first thing I did was install Rom Manager and start to make a nandroid backup until I got:
" RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery"
Click to expand...
Click to collapse
That is the standard message while recovery is booting. How long did you wait?
FeralFire said:
That is the standard message while recovery is booting. How long did you wait?
Click to expand...
Click to collapse
After that message it just restarts into a boot loop showing that message over and over until I pull the battery, boot into download mode and then hit cancel so the phone boots up normally. Currently I do not have a recovery menu at all, not stock, and not custom.
Brooklynyte said:
After that message it just restarts into a boot loop showing that message over and over until I pull the battery, boot into download mode and then hit cancel so the phone boots up normally. Currently I do not have a recovery menu at all, not stock, and not custom.
Click to expand...
Click to collapse
Ok, try mobile odin.
FeralFire said:
Ok, try mobile odin.
Click to expand...
Click to collapse
Ok, installed Mobile Odin, first thing it said was to make sure I have the proper boot loader or it could result in a soft brick. Now it shows me the different partitions, one of them being "recovery"... Now what file exactly should I be using? Do I flash it to that partition or do I just use the" Open file" option? Can you guide me through it at all? I appreciate all your help thus far!
Edit: I believe I found the correct file to flash... Please correct me if I'm wrong but being that I have the T-Mobile version of the Note 3, my boot loader should not be locked right? So I should be able to flash this file *n9005-cwm-recovery-6.0.4.7-kk(0125).tar* using mobile odin, and all should be good, right? I would post the link but I'm a new user and cant... But this is the description of the file: SM-N9005/SM-N900T/SM-N900P Qualcomm Note 3 – CWM Recovery -*Download*-*Credits*(Also works for T-Mobile/Sprint)
Brooklynyte said:
Ok, installed Mobile Odin, first thing it said was to make sure I have the proper boot loader or it could result in a soft brick. Now it shows me the different partitions, one of them being "recovery"... Now what file exactly should I be using? Do I flash it to that partition or do I just use the" Open file" option? Can you guide me through it at all? I appreciate all your help thus far!
Click to expand...
Click to collapse
I have never personally used Mobile Odin, but you need to flash the recovery's tar file in the software.
FeralFire said:
I have never personally used Mobile Odin, but you need to flash the recovery's tar file in the software.
Click to expand...
Click to collapse
You my dear friend, have my everlasting gratitude! I now have a working cwm recovery! Maybe I should make a quick guide to show how to root and flash custom recovery without a computer... Lord knows I could have used a guide like that. Thank you Feral....
Brooklynyte said:
You my dear friend, have my everlasting gratitude! I now have a working cwm recovery! Maybe I should make a quick guide to show how to root and flash custom recovery without a computer... Lord knows I could have used a guide like that. Thank you Feral....
Click to expand...
Click to collapse
Just press the thanks button.
And you are welcome.
Greetings,
S5, Verizon. Was previously running 4.4.4, Stock rooted.
I upgraded to Lollipop Stock rooted. But I do not have a custom recovery.
I grabbed TWRP and it failed, "Secure Magiccode check failed : recovery"
I did a bit of digging, and Verizon's Samsung's GS5 is not on their list of devices.
I checked clockwordmod, they do not list it either.
Am I missing something? I installed Safestrap previously, to install lollipop. However, that does not work with Lollipop, so I've read.
Any suggestions for a custom recovery?
If you're rooted, try this
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en_GB
It's what I use
Nice thought. I grabbed that and installed it. Unfortunately, it didn't work. My phone is now stuck with "Recovery is not seandroid encorcing."
And it's continually trying to boot into recovery.
Research time.
Can you boot into recovery using Vol Up, Home & power?
I think that message is normal, as it's not stock recovery
*Detection* said:
Can you boot into recovery using Vol Up, Home & power?
I think that message is normal, as it's not stock recovery
Click to expand...
Click to collapse
Nope. I get the nice blue "Booting recovery" (or whatever), then the message above.
Then "Start up Failed" blah blah.
Might have to flash a stock ROM back on this to get it booted. I'm still reading up on it.
Thanks for your tips!
jagauthier said:
Nope. I get the nice blue "Booting recovery" (or whatever), then the message above.
Then "Start up Failed" blah blah.
Might have to flash a stock ROM back on this to get it booted. I'm still reading up on it.
Thanks for your tips!
Click to expand...
Click to collapse
I was able to reflash "G900V_OA8_Stock_Partitions.tar.md5", and this rebuilt the recovery partition.
So, I'm functional, but no custom recovery.
Tried using the TWRP manager to flash recovery again since rebuilding recovery?
*Detection* said:
Tried using the TWRP manager to flash recovery again since rebuilding recovery?
Click to expand...
Click to collapse
No, this is where I was before. Doing it again will almost undoubtedly result in the same issue.
Aren't Version S5s all bootloader locked?
*Detection* said:
Aren't Version S5s all bootloader locked?
Click to expand...
Click to collapse
I am not that well versed. I just wanted to install a custom recovery
I was rooted with Kitkat, and installed Safestrap. I booted into that to upgrade to Lollipop.
It's not that big of deal. I was hoping for a simple solution.
*Detection* said:
Aren't Version S5s all bootloader locked?
Click to expand...
Click to collapse
Yeah NO TWRP. If one does manage to replace stock recovery w twrp, a message pops up letting you know its a unauthorized Verizon....... Please go to nearest VZW store.
---------- Post added at 05:16 PM ---------- Previous post was at 05:15 PM ----------
Go Dev Edition if you want TWRP.
Am trying to flash TWRP to my (SM-G935F) S7 Edge Nougat 7.0
No matter which TWRB of the 11 versions i flash it does not work
Either give me a Total RED SCREEN (The last 3 or 4 versions) or give me Recovery is not Seandroid Enforcing (Older Versions) and freeze
Am using the latest Odin v3.12
I don't know what to do please help
koshac4 said:
Am trying to flash TWRP to my (SM-G935F) S7 Edge Nougat 7.0
No matter which TWRB of the 11 versions i flash it does not work
Either give me a Total RED SCREEN (The last 3 or 4 versions) or give me Recovery is not Seandroid Enforcing (Older Versions) and freeze
Am using the latest Odin v3.12
I don't know what to do please help
Click to expand...
Click to collapse
Hello,these are my steps for obtaining TWRP.First i use cf-root and then download TWRP official app,from there you will have option to flash latest image 3.2.1.-1.Try that if you want.good luck
darksx said:
Hello,these are my steps for obtaining TWRP.First i use cf-root and then download TWRP official app,from there you will have option to flash latest image 3.2.1.-1.Try that if you want.good luck
Click to expand...
Click to collapse
hey man
i have done that
i obtained the 11 version of TWRB and tried to flash all of them from the official website but it gives me RED screen on the last 6 versions and the error message above on 2 versions and the rest the screen just freeze
What do u mean by using CF-ROOT!?
koshac4 said:
hey man
i have done that
i obtained the 11 version of TWRB and tried to flash all of them from the official website but it gives me RED screen on the last 6 versions and the error message above on 2 versions and the rest the screen just freeze
What do u mean by using CF-ROOT!?
Click to expand...
Click to collapse
As i described as above i usually use the second method.So i first root my device with cf-root package,you will find that in firmware.mobi,and then i flash twrp image with Twrp app itself or you can flash it with flashify.But in your case i don't know what's wrong.Are you using correct twrp version.
darksx said:
As i described as above i usually use the second method.So i first root my device with cf-root package,you will find that in firmware.mobi,and then i flash twrp image with Twrp app itself or you can flash it with flashify.But in your case i don't know what's wrong.Are you using correct twrp version.
Click to expand...
Click to collapse
See am not 100% which is the right TWRP version but i tried them all and no use
Yesterday it took me 6 hours to figure out the stock and flash it back to normal and now idk how to do it
I need like exact numbers and figuers and name for the versions as i tried the thread on xda but the TWRB couldn't be loaded from the boot to start with
Can u help!?
koshac4 said:
See am not 100% which is the right TWRP version but i tried them all and no use
Yesterday it took me 6 hours to figure out the stock and flash it back to normal and now idk how to do it
I need like exact numbers and figuers and name for the versions as i tried the thread on xda but the TWRB couldn't be loaded from the boot to start with
Can u help!?
Click to expand...
Click to collapse
If you have SM-G935F and i see you have but check again just to on the safe side here is the link for recovery
https://eu.dl.twrp.me/hero2lte/ .Did you flash that version.
darksx said:
If you have SM-G935F and i see you have but check again just to on the safe side here is the link for recovery
https://eu.dl.twrp.me/hero2lte/ .Did you flash that version.
Click to expand...
Click to collapse
Every single one of them
koshac4 said:
Every single one of them
Click to expand...
Click to collapse
This is really strange,yesterday i have rooted and flashed twrp without any problems.Did you maybe ticked option OEM unlock in developers option.
darksx said:
This is really strange,yesterday i have rooted and flashed twrp without any problems.
Click to expand...
Click to collapse
Which version of them though!?
I tried all the 11
The leatest 5 or 6 gives me a red screen and older ones freeze or recovery is not seandroid enforcing and also freezez
koshac4 said:
Which version of them though!?
I tried all the 11
The leatest 5 or 6 gives me a red screen and older ones freeze or recovery is not seandroid enforcing and also freezez
Click to expand...
Click to collapse
I always flash the latest,so in this case 3.2.1-1
darksx said:
I always flash the latest,so in this case 3.2.1-1
Click to expand...
Click to collapse
Nop just a very red screen that not making u able to do anything then i restart back again to download mode
I have the same problem,
My red screen problem,
I had to use odin v3.16 and old twrp version twrp-3.1.1-0-hero2lte.img.tar because of een red screen after booting with the newest odin and twrp.
After installing this old twrp, I could install, within twrp, the new image twrp-3.2.3-0-hero2lte.img, which I put already put on the sd card.