hI guys. I'm having a bit of trouble with my SM-G925I S6 edge here!
I had successfully rooted my phone. Successfully flashed TWRP recovery. But then when I flashed a ROM "CM 13" on it, my phone got stuck on the bootup screen, with the massage/error "kernel is not seandroid enforcing". I've been trying to fix it, but nothing worked.
I've tried flashing the stock firmware, re-flashing the ROM, re-flashing the TWRP recovery. Does anyone have any solution for this problem, or is my phone bricked?
T-w4yn3 said:
hI guys. I'm having a bit of trouble with my SM-G925I S6 edge here!
I had successfully rooted my phone. Successfully flashed TWRP recovery. But then when I flashed a ROM "CM 13" on it, my phone got stuck on the bootup screen, with the massage/error "kernel is not seandroid enforcing". I've been trying to fix it, but nothing worked.
I've tried flashing the stock firmware, re-flashing the ROM, re-flashing the TWRP recovery. Does anyone have any solution for this problem, or is my phone bricked?
Click to expand...
Click to collapse
Flash stock rom, flash twrp then flash custom kernel if you still get the error. But a stock rom flash should fix it as it flashing the whole thing to stock including kernel and recovery.
---------- Post added at 05:58 PM ---------- Previous post was at 05:56 PM ----------
callumbr1 said:
Flash stock rom, flash twrp then flash custom kernel if you still get the error. But a stock rom flash should fix it as it flashing the whole thing to stock including kernel and recovery.
Click to expand...
Click to collapse
Does the phone not boot up at all?
Related
Hello,
I have been trying to flash TWRP to my SM-G925F and whenever I boot it says: "Recovery is not SEAndroid enforcing." (If this happens I just flash the stock recovery back and it works)
Is there a way to turn off "SEAndroid" or am I flashing the wrong version of TWRP onto my phone?
Please reply quickly because I would really like TWRP!
NH-Gaming said:
Hello,
I have been trying to flash TWRP to my SM-G925F and whenever I boot it says: "Recovery is not SEAndroid enforcing." (If this happens I just flash the stock recovery back and it works)
Is there a way to turn off "SEAndroid" or am I flashing the wrong version of TWRP onto my phone?
Please reply quickly because I would really like TWRP!
Click to expand...
Click to collapse
As far as I remember, flashing a custom recovery gives you that message. It's been like that for years which points me to the fact you're either new to Samsung or new to flashing a custom recovery on a Samsung
NH-Gaming said:
Hello,
I have been trying to flash TWRP to my SM-G925F and whenever I boot it says: "Recovery is not SEAndroid enforcing." (If this happens I just flash the stock recovery back and it works)
Is there a way to turn off "SEAndroid" or am I flashing the wrong version of TWRP onto my phone?
Please reply quickly because I would really like TWRP!
Click to expand...
Click to collapse
normal..which version you tried..
here is the guide
http://forum.xda-developers.com/showthread.php?t=3144866
Hello, I am using the 2.8.7.1-zeroflte TWRP recovery for the normal S6 not the S6 edge, would that be the problem?
not if it work..that sentence is normal..as it's because of the system write protection / security from 5.1.1 you have to live with that
It's not as intrusive as In past devices eg note series that I have rooted. And it sure doesn't effect functionality. You'll be looking more at the home screen than a reboot screen (unless your a dev lol )
I am having the issue with my phone.... I rooted phone with a 5.0.1 recovery on 5.1.1 rom. Now its stuck in a loop at SAMSUNG Galaxy S6 Edge
Logo. With Recovery is not SEANDROID ENFORCING. Any one please help.
having the same problem! trying to install twrp 2.8.7.1 on my s6 flat g920I, with 5.1.1 stock! installing through odin, when i enter twrp get this message, and after reboot im stucked on a loop
CellularGeek said:
I am having the issue with my phone.... I rooted phone with a 5.0.1 recovery on 5.1.1 rom. Now its stuck in a loop at SAMSUNG Galaxy S6 Edge
Logo. With Recovery is not SEANDROID ENFORCING. Any one please help.
Click to expand...
Click to collapse
Deepblackk said:
having the same problem! trying to install twrp 2.8.7.1 on my s6 flat g920I, with 5.1.1 stock! installing through odin, when i enter twrp get this message, and after reboot im stucked on a loop
Click to expand...
Click to collapse
why you do so..? and not making it as i wrote in the thread
http://forum.xda-developers.com/showthread.php?t=3144866
Alex-V said:
why you do so..? and not making it as i wrote in the thread
http://forum.xda-developers.com/showthread.php?t=3144866
Click to expand...
Click to collapse
Sorry I posted here before I finding the other thread.
How I can repair my smartphone if I already made it or it isn't solved? Please help
Hi All
Need an urgent help. While trying to root my S6 edge,India version! I think, I have bricked my phone. Its stuck on 'recovery is not seandroid enforcing'. Its only getting into the Download mode. But I have tried everything so far on the internet and no luck in fixing it. My variant version is - SM-G925I and the firmware was G925IDVU3DOK9.
Can anyone please help me with the steps to fix this issue!
Appreciate the help.
PS: Attaching the screenshot with the 'About the phone' details. Please let me know, if you need anything from my side.
Regards
Deeptiman
im trying to get my bricked s6 edge back to stock and just up an running again sm-g925f
was given to me in bricked state by my 16 year old cousin whom im trying to fix it for...
not sure if its rooted or what firmware it has on it now...
tried allsorts last 6 days, all new stock firmwares from sammmobile etc.
tried twrp etc
not sure what to do or where im going wrong.
odin wont flash any firmware file?? just gives fail after passing md5 part
I'm stuck having this problem ever since i Flash Stock Firmware 5.1.1 on my SM-G925I
Previously, i was running on Stock Firmware 5.0.2 with Root without any Custom Rom. What i did was... I just Flashed the new Firmware i've downloaded from SamM0bile. Done! So next i just try to Root my phone again using the AndroidRootz method (which i did for my 5.0.2 Firmware) & while trying to get into Recovery Mode i get this error.
I click on my SuperSU app which was already installed on previous Root it does nothing, then i check for a Software Update it says my Device is modified.
I have this feeling is related to the TWRP.tar file i Flashed.
PLEASE HELP.....
As soon as you put on that custom recovery you will get that error on 5.1.1, I get that everytime I boot my phone with a custom rom.
dwarfer66 said:
As soon as you put on that custom recovery you will get that error on 5.1.1, I get that everytime I boot my phone with a custom rom.
Click to expand...
Click to collapse
Any remedy??
No mate, thats Samsungs way of punishing us users of custom roms!
Does anyone know of a system to root the new samsung marshmallow 6.0.1
i've tried the system with 2 bootloaders,
i've tried carhdrom and the samsung themes in settings is gone and i can't get to root,
so i installed the new marshmallow that samsung just posted but i can't root it with whatever old suggestions
can anyone help please
much appreciated,
sincerely
I'm also struggling.
I've flashed stock 6.0.1 (from 51.1.) and tried to flash TWRP but I get the 'Recovery is not seandroid enforcing'.
Help!
seandroid
this only means you don't have a stock samsung rom and possibly you knocked knox for service, if that keeps up at nite.
i've installed criscross new marshmallow but i lost the samsung themes option in setting,
it has a huge stock of very nice themes for free.
have a hunch that because the rom is very fresh no one has come up with a solution
let me know if you succeed.
good luck
yonster said:
I'm also struggling.
I've flashed stock 6.0.1 (from 51.1.) and tried to flash TWRP but I get the 'Recovery is not seandroid enforcing'.
Help!
Click to expand...
Click to collapse
exlaval said:
this only means you don't have a stock samsung rom and possibly you knocked knox for service, if that keeps up at nite.
Click to expand...
Click to collapse
It's a stock Samsung rom. Getting the message doesn't bother me and neither does tripping knox, but it bothers me that rather than booting into recovery I get the 'Recovery is not seandroid enforcing' and nothing else. I have to boot into download mode and get back the phone back from there.
Download space-x kernel and supersu2.67.apk from
Here -
https://drive.google.com/folderview...sharing&tid=0B40ItdHKfkyQOWRXazlJU1ZoV00#list
Now flash space-x kernel from odin .
Wait for ur mobile to boot (takes time!)
When boot finished install supersu2.67.APK.
Enjoy.....
ahamed.rafi135 said:
Download space-x kernel and supersu2.67.apk from
Here -
https://drive.google.com/folderview...sharing&tid=0B40ItdHKfkyQOWRXazlJU1ZoV00#list
Now flash space-x kernel from odin .
Wait for ur mobile to boot (takes time!)
When boot finished install supersu2.67.APK.
Enjoy.....
Click to expand...
Click to collapse
Thanks.
Do I need to flash to boot.img file too? At which point?
Thanks again - appreciate it.
Your welcome....
No not required only flash the tar file ignore the boot.img.....
It worked for me..
Hope it helps..
Is it tripping Knox?
Obvio....
SM G925F???
Hi there will this root method work for the international SM-G925F version?
Greetings Dudes / Dudettes
So I have the kernel flashed and SuperSU installed but still I get "Recovery is not seandroid enforcing" when trying to boot TWRP..also tried Philz same no dicee :< = no custom roms right ?
How can I fix this apart from flashing an older rom....
EDIT:
If somebody else is stuck in the future google OLD_BL_TWRP_2.8.7.2.tar it gave me a working recovery :>
EDIT2:
What appeared to be working was all nice and all but then the current stock marshmallow rom would not boot up.
according to the guys at twrp site, they do not have as yet a formal twrp version for marshmallow for the g925f
i tried just about every version out there none worked
what i want to know is how do i flash a custom rom WITHOUT TWRP - ?
I download the system update for OnePlus x oxygen os 2.2.1. But when I reboot it for installation, there's a message "installation failed". What's wrong with the file? It seems to download everything properly. But error occurs during installation.
Is it rooted? Which recovery r u using? Twrp or stock?
Not rooted
itsmelutfor said:
Is it rooted? Which recovery r u using? Twrp or stock?
Click to expand...
Click to collapse
What have you already modded in the original installation? If your system was stock the update wouldn't fail. Please be more specific so people can help you. If you've kingrooted or flashed twrp, the update will fail...
I don't know about the OP, but I had the same issue when I tried to OTA to OOS 2.2.1. I applied all my hacks through TWRP but always booting TWRP by ADB and never flashing TWRP to the phone. So, I have unlocked bootloader, Developer settings, stock recovery, Boeffla, CameraHAL. With this, OOS 2.2.1 OTA gave me "installation failed". Shouldn't it have worked since I was still in stock recovery?
Thinking it could be the kernel I then tried to restore the original kernel by going to a TWRP backup I made immediately before flashing Boeffla, and restoring boot.img. To my surprise, I then lost all Wi-Fi functionality.
In the end, I downloaded the full OOS 2.2.1 ROM from OnePlus and dirty-flashed it, stacking it before the newest versions of Boeffla and CameraHAL. Phone is working OK, no bugs noticed so far.
I still haven't flashed TWRP nor rooted the phone. In my configuration, what's stopping OTA from working? It would be nice to have OOS3 OTA, since I still don't trust the backups I'm making.
Sent from my ONE E1003 using XDA Labs
TiagoJSilva said:
I don't know about the OP, but I had the same issue when I tried to OTA to OOS 2.2.1. I applied all my hacks through TWRP but always booting TWRP by ADB and never flashing TWRP to the phone. So, I have unlocked bootloader, Developer settings, stock recovery, Boeffla, CameraHAL. With this, OOS 2.2.1 OTA gave me "installation failed". Shouldn't it have worked since I was still in stock recovery?
Thinking it could be the kernel I then tried to restore the original kernel by going to a TWRP backup I made immediately before flashing Boeffla, and restoring boot.img. To my surprise, I then lost all Wi-Fi functionality.
In the end, I downloaded the full OOS 2.2.1 ROM from OnePlus and dirty-flashed it, stacking it before the newest versions of Boeffla and CameraHAL. Phone is working OK, no bugs noticed so far.
I still haven't flashed TWRP nor rooted the phone. In my configuration, what's stopping OTA from working? It would be nice to have OOS3 OTA, since I still don't trust the backups I'm making.
Sent from my ONE E1003 using XDA Labs
Click to expand...
Click to collapse
If you modify even a single bit in stock rom and revert back, updates are definitely going to fail.
The only solution to receive OTAs is flashing stock recovery with stock rom with locked bootloader.
Or you can manually flash OTAs using TWRP.
I made several backups of my stock rom before testing mods, but when I restored and tried to perform OTAs, it always failed while installing.
prabhat.singh.836 said:
If you modify even a single bit in stock rom and revert back, updates are definitely going to fail.
The only solution to receive OTAs is flashing stock recovery with stock rom with locked bootloader.
Or you can manually flash OTAs using TWRP.
I made several backups of my stock rom before testing mods, but when I restored and tried to perform OTAs, it always failed while installing.
Click to expand...
Click to collapse
You just need to wipe cache from the stock recovery in order to install the ota updates , customer care babe told me
---------- Post added at 03:44 AM ---------- Previous post was at 03:43 AM ----------
Hello guys, I unlocked my bootloader...now would I get the ota updates? It's not rooted and on stock ROM.
If no then please tell me how to revert back to locked bootloader.
TiagoJSilva said:
I don't know about the OP, but I had the same issue when I tried to OTA to OOS 2.2.1. I applied all my hacks through TWRP but always booting TWRP by ADB and never flashing TWRP to the phone. So, I have unlocked bootloader, Developer settings, stock recovery, Boeffla, CameraHAL. With this, OOS 2.2.1 OTA gave me "installation failed". Shouldn't it have worked since I was still in stock recovery?
Thinking it could be the kernel I then tried to restore the original kernel by going to a TWRP backup I made immediately before flashing Boeffla, and restoring boot.img. To my surprise, I then lost all Wi-Fi functionality.
In the end, I downloaded the full OOS 2.2.1 ROM from OnePlus and dirty-flashed it, stacking it before the newest versions of Boeffla and CameraHAL. Phone is working OK, no bugs noticed so far.
I still haven't flashed TWRP nor rooted the phone. In my configuration, what's stopping OTA from working? It would be nice to have OOS3 OTA, since I still don't trust the backups I'm making.
Sent from my ONE E1003 using XDA Labs
Click to expand...
Click to collapse
swatidixit710 said:
I download the system update for OnePlus x oxygen os 2.2.1. But when I reboot it for installation, there's a message "installation failed". What's wrong with the file? It seems to download everything properly. But error occurs during installation.
Click to expand...
Click to collapse
deathaddder said:
You just need to wipe cache from the stock recovery in order to install the ota updates , customer care babe told me
---------- Post added at 03:44 AM ---------- Previous post was at 03:43 AM ----------
Hello guys, I unlocked my bootloader...now would I get the ota updates? It's not rooted and on stock ROM.
If no then please tell me how to revert back to locked bootloader.
Click to expand...
Click to collapse
I have tried wipe cache method and doesn't works at all if you have rooted your phone and unrooted back.
And the OTA should work even with unlocked bootloader, if you have not rooted your phone before.
If you want to lock your bootloader again, just follow these steps,
1. Goto Settings -> Developer options
2. OEM unlocking -> turn it off
Error in installation of OxygenOS2.2.1
Having same issue, I doubt why it is not getting installed. Not rooted and not even touchted the kernel. Is it a bug or it requires a flash ?
Ankit_Lal said:
Having same issue, I doubt why it is not getting installed. Not rooted and not even touchted the kernel. Is it a bug or it requires a flash ?
Click to expand...
Click to collapse
Did you try to flash the full rom zip here?
http://downloads.oneplus.net/2016-04-20/opx/OnePlus_X_OxygenOS_2.2.1-X/
Cannot update to Oxygen OS 2.2.1
Yup ! I tried the same but it fails repetedly
Is there anyone who is facing the same issue ?
Ankit_Lal said:
Yup ! I tried the same but it fails repetedly
Is there anyone who is facing the same issue ?
Click to expand...
Click to collapse
I have the same problem. Brand new phone, out of box, Oxygen version 2.1.0.
I've just unlocked the bootload and flashed TWRP on to my moto G4 plus and went to flash magisk after to get root. After i flashed it I rebooted my phone but it wouldn't boot into the system and wouldn't even show the boot animation. I tried to use the Stock recovery I made after putting TWRP on my phone but it kept on saying error 255. This lead me to sideload lineage OS onto the phone which work. However when I tried to boot into android it did the same thing again. I have a feeling that something is wrong with the /boot partition as when i go to recover using my stock img there is only a system box.
Any help is appreciated
Welcome to XDA,
and did you try reflashing stock firmware?
That will always work.
Hello there. I'm having a major issue with flashing magisk right now. So all was fine. Then today, I flashed OxygenOS open beta 19 on my OnePlus 5T. I then tried flashing Magisk. What's really weird is it boots, but as soon as it does, I get a split second of enter pin, before my phone just says shutting down before it does just that. I've tried the uninstaller then reinstalling it with no luck. I'd really like to stay rooted without wiping data, but I can live without root. Does anyone know how I could fix this problem? Thanks so much in advance.
---------- Post added at 09:12 PM ---------- Previous post was at 09:10 PM ----------
Oh very sorry, I mean open beta 29.