Before I Rooted my GT-I9500 the SELinux status was official, now when I rooted it SELinux became Permissive, now I want to restore it to official, I tried to, 1. unroot, 2. flush new Firmware 3. reset it to factory settings. but it does not help. Please can someone explain me what is SELinux and how can I restore it to official...
waranty92 said:
Before I Rooted my GT-I9500 the SELinux status was official, now when I rooted it SELinux became Permissive, now I want to restore it to official, I tried to, 1. unroot, 2. flush new Firmware 3. reset it to factory settings. but it does not help. Please can someone explain me what is SELinux and how can I restore it to official...
Click to expand...
Click to collapse
Pleasy don't mix SELinux Status with Device or Firmware Status.
SELinux can be permissive or envorcing (since the latest MGG or MHx Firmwares)
The device status can be official or custom.
If you wan't SELinux Status envorcing and device status official, flash a ODIN Firmware and do a full wipe and never do any customications again.
Alex
I don`t mix it was official 100% and when I do exactly as you told i have my device status official and SELinux status permissive
Related
I have rooted my new Sprint Galaxy S5 and have quarantined all the Knox apps without tripping the knox flag. I have researched setting selinux to permissive on the Sprint Galaxy S5 with the stock kernel and there seems to be no way of doing it short of flashing a different kernel.
Can a selinux permissive kernel be flashed to a stock 4.4.2 rom without tripping the knox flag?
If the kernel is odin flashable, then it should be ok. The knox flag is tripped when a custom recovery is installed.
Thanks for the info. There seems to be no selinux permissive Odin flashable kernels for 4.4.2 for the Sprint Galaxy S5(unless I missed something during my searching). Also, there seems to be no way to set selinux permissive without tripping the knox flag.
Here is a discussion on this: http://forum.xda-developers.com/showthread.php?t=2765353
And: http://forum.xda-developers.com/ver...ipt-permissive-selinux-stock-kernels-t2854364
From chainfire: http://su.chainfire.eu/#selinux-contexts-init-shell
Hello, I need to disable Selinux (SEANDROID) many apps that i have not working i have 0x0 flag Custom Recovery, Rooted,Xposed Installed, I tryed all tutorials but none of them work, Enforcing Restarts when it was permissive apps wasn't crashing like App Name Has Stopped or Selinux need to be set to permissive for this app to work i need help with disabling SELINUX Now i get while booting to recovery "Recovery Is Not Seandroid Enforcing" how can i disable Selinux? Samsung Galaxy Grand Prime SM-G531F Lollipop 5.1.1
TheSMGCraft said:
Hello, I need to disable Selinux (SEANDROID) many apps that i have not working i have 0x0 flag Custom Recovery, Rooted,Xposed Installed, I tryed all tutorials but none of them work, Enforcing Restarts when it was permissive apps wasn't crashing like App Name Has Stopped or Selinux need to be set to permissive for this app to work i need help with disabling SELINUX Now i get while booting to recovery "Recovery Is Not Seandroid Enforcing" how can i disable Selinux? Samsung Galaxy Grand Prime SM-G531F Lollipop 5.1.1
Click to expand...
Click to collapse
it has to be done in the kernel aka boot.img. im not a kernel dev, so you will probably get the best results by looking around the forums for a kernel dev and pm ing them
toolhas4degrees said:
it has to be done in the kernel aka boot.img. im not a kernel dev, so you will probably get the best results by looking around the forums for a kernel dev and pm ing them
Click to expand...
Click to collapse
well thats bad, selinux keeps changing to permissive... i really need boot.img modded? i created my own Custom Firmware and flashed it, it doesn't flagged/tripped knox warrenty void upload here boot.img?
i found in root directory /SYS/FS/SELINUX some files like policy,disable,access,enforce Many files give's access denied or Re-Create's Disable file set to 1 Re-creates same with enforce change to 0 inside re-creates
i'm sick of this selinux ! ! help
Custom Kernel
toolhas4degrees said:
it has to be done in the kernel aka boot.img. im not a kernel dev, so you will probably get the best results by looking around the forums for a kernel dev and pm ing them
Click to expand...
Click to collapse
I Made with DadziokPL Custom Kernel with selinux permissive
***THREAD CLOSED!***
I have Samsung S5 G900f recently updated to marshmallow and this SE status enforcing is not letting me do anything neither can do any modification via framework unable to add any rom via twrp i saw many post but was unable to find any solution plzz guide me coz i want to install alliance rom.
When installing via twrp my mob is just restarting but no rom are getting installed same for cwm.
Supersu is providing root but i am unable to do any modification in my system plz provide me solution for this prob.
simms22 said:
change your selinux to permissive. google an app for it..
Click to expand...
Click to collapse
Yeah tried that Se linux mode changer but still facing problem in installing custom rom or any changes to system files
sk.shehbaz said:
Yeah tried that Se linux mode changer but still facing problem in installing custom rom or any changes to system files
Click to expand...
Click to collapse
What kernel are you running ? On samsung with MM you need a permissive kernel to change selinux from enforcing it can't be done with an app. Try flashing a permissive kernel and you should be ok
Good Luck
Sawdoctor
Me and another D6616 user are having problems passing Google SafetyNet. Though we did root and have a custom recovery, we have since unrooted. Anyone else with this issue? Factory reset didn't help, though didn't try a full device reset Sony PC Companion.
Same D6603.
- Old SafetyNet:
+ Back to 4.4 and root with giefroot_v3, then unroot => Passed SafetyNet.
+ Make a deodexed 6.0.1 ROM, WITHOUT ROOT AND RECOVERY. => Passed SafetyNet
- Latest SafetyNet Update ( Today).
+ Back to 4.4 and root with giefroot_v3, then unroot => Passed SafetyNet.
+ Make a deodexed 6.0.1 ROM, WITHOUT ROOT AND RECOVERY. => NOT Passed SafetyNet (CTS failed).
This deodexed 6.0.1 ROM have to install byeselinux.sh and installmount.sh script. Without this script, phone can boot, but stuck at Setup wizard screen, no network too. Any idea about this problem @shoey63 . Thanks
ReadReadz said:
Same D6603.
- Old SafetyNet:
+ Back to 4.4 and root with giefroot_v3, then unroot => Passed SafetyNet.
+ Make a deodexed 6.0.1 ROM, WITHOUT ROOT AND RECOVERY. => Passed SafetyNet
- Latest SafetyNet Update ( Today).
+ Back to 4.4 and root with giefroot_v3, then unroot => Passed SafetyNet.
+ Make a deodexed 6.0.1 ROM, WITHOUT ROOT AND RECOVERY. => NOT Passed SafetyNet (CTS failed).
This deodexed 6.0.1 ROM have to install byeselinux.sh and installmount.sh script. Without this script, phone can boot, but stuck at Setup wizard screen, no network too. Any idea about this problem @shoey63 . Thanks
Click to expand...
Click to collapse
byeselinux.sh sets kernel to permissive. This is *probably* why SafetyNet fails. No idea about why "stuck at Setup wizard screen, no network too."
shoey63 said:
byeselinux.sh sets kernel to permissive. This is *probably* why SafetyNet fails. No idea about why "stuck at Setup wizard screen, no network too."
Click to expand...
Click to collapse
I will try a deodexed ROM without byeselinux (and root).
Hello Guys
I want to tell how to bypass RMM state: prenormal to install TWRP
Also this will resolve "Only official binaries are allowed"
Disclaimer:
I am NOT responsible for any damage done if you use my guide.
It worked for me 100% and should normally work for everybody!
Feel free to share to anyone else or to embed if you want.
-------------------------------------------------
1. Download latest Stock base via SamFirm
2. Install latest Stock base via Odin Odin v3.13.1 direct download
3. Boot into system
4. Skip the setup
5. Activate Developer settings
6. search and turn of automatic system update
7. Go to time settings and deactivate automatic time
8. Turn back the day for more than 7 days. ( I have turned to the 20th Dec 2018)
9. Search for Software update -> Don't install update
10. Look if latest time searched for updates is the date which you have set. (for me 20th Dec 2018)
11. Reboot your device
12. go into the time settings and reactivate the automatic time
13. Search again for software update - > Still don't install
14. Go to Developer settings
15. deactivate OEM Unlock and reactivate
16. Go to download mode and you will don't see RMM state anymore
18. install TWRP by odin
19. boot into TWRP
20. format data
21. reboot recovery
22. flash verity.zip // found on https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
23. Et voilà! You got completely functional TWRP on your device with Pie Bootloader
24. Flash your preferred Rom!
-------------------------------------------------
Thanks to:
zxz0O0 for SamFirm
Have Fun
this verity.zip is necessary? or can I flash another rom right after install twrp?
edit: by "update.zip" you mean the PIE Beta?
LucasBernardesLopes said:
this verity.zip is necessary? or can I flash another rom right after install twrp?
edit: by "update.zip" you mean the PIE Beta?
Click to expand...
Click to collapse
It decrypt the Userdata.
Yes i mean the Pie Beta.
It works perfect, I was worried because I could not find a solution, very good guide thank you very much
Laiyox said:
Hello Guys
-------------------------------------------------
1. Download CRL3 via Samfirm SamFirm Download from mega.nz
2. Install CRL3 via Odin Odin v3.13.1 direct download
3. Boot Stock CRL3 after install with Odin
Click to expand...
Click to collapse
Hi, I have nonroot CRLB. Is it neccessery to downgreade ?
tomaasz said:
Hi, I have nonroot CRLB. Is it neccessery to downgreade ?
Click to expand...
Click to collapse
I don't really know. The Beta was published while CRL3. So i think it is needed, but you can try. If it dont work you just can reflash CRL3 via Odin
tomaasz said:
Hi, I have nonroot CRLB. Is it neccessery to downgreade ?
Click to expand...
Click to collapse
Following this thread you should be on CRL3.
https://forum.xda-developers.com/galaxy-s8/how-to/s8-exynos-pie-oneui-beta-official-t3890376
do we have to flash twrp after every pie beta update?
How to root s8plus 9.0 one ui
I need help root android 9.0 one ui s8plus ??
i followed everything 9.0 Pie beta also done but after format wipe OEM is gone.
actually i want to root my G955F but its showing error becous RMM status is Prenormal so i cant root my S8 plus
please guide me how to root after beta pie 9.0?
Thx.
talhagsm said:
i followed everything 9.0 Pie beta also done but after format wipe OEM is gone.
actually i want to root my G955F but its showing error becous RMM status is Prenormal so i cant root my S8 plus
please guide me how to root after beta pie 9.0?
Thx.
Click to expand...
Click to collapse
I have just written a new thread with a new method to bypass it:
https://forum.xda-developers.com/galaxy-s8/how-to/guide-skipping-kg-prenormal-oneui-t3911862
How to install the crlb via odin
When I do this on Pie, the OEM Unlock toggle in Dev Options shows up. When I toggle it, it shows the following in download mode:
RMM STATE: Prenormal
KG STATE: Checking
FRP LOCK: OFF
OEM LOCK: OFF
And I am unable to flash TWRP or any custom binaries.
So I downgraded to Oreo, and followed the exact same steps as outlined and now I cannot get the OEM toggle to show up! And of course it says Prenormal in download... but not KG State.
RMM STATE: Prenormal
FRP LOCK: OFF
OEM LOCK: ON
WTF am I doing wrong??
kgr said:
When I do this on Pie, the OEM Unlock toggle in Dev Options shows up. When I toggle it, it shows the following in download mode:
RMM STATE: Prenormal
KG STATE: Checking
FRP LOCK: OFF
OEM LOCK: OFF
And I am unable to flash TWRP or any custom binaries.
So I downgraded to Oreo, and followed the exact same steps as outlined and now I cannot get the OEM toggle to show up! And of course it says Prenormal in download... but not KG State.
RMM STATE: Prenormal
FRP LOCK: OFF
OEM LOCK: ON
WTF am I doing wrong??
Click to expand...
Click to collapse
Did you did everything step by step?
If you miss any step it won't work
Laiyox said:
Did you did everything step by step?
If you miss any step it won't work
Click to expand...
Click to collapse
Yep absolutely followed the directions exactly. In the end I just wanted the 7 days
kgr said:
Yep absolutely followed the directions exactly. In the end I just wanted the 7 days
Click to expand...
Click to collapse
Also used latest Base?
I didn't update the thread to official Pie
can I still flash without root?
I have a J337VPP galaxy J3 running on android oreo 8.0.0 and the hardware version is J337v.04. it is non-rooted. Would I be able to do your steps without root? it has to be able to be done without root since the only way to root is by unlocking the bootloader using the OEM unlock (which I can't do because of this stupid RMM prenormal Samsung decided to create). Thanks! been trying to root different phone of mine for years to take complete control over annoying system apps! (atleast I already have Package Disabler Pro) Thanks again. Hope I can have help. I've heard of going to download mode and seting the date before RMM prenormal. I think I am good with tech but new to this RMM stuff.
---------- Post added at 12:18 AM ---------- Previous post was at 12:01 AM ----------
Turns out RMM state prenormal isn't in download mode/odin. Weird... maybe J3 doesn't support oem unlock
just tried this on SM-G950F (Galaxy S8), RMM state is still prenormal and I can't flash TWRP. I did have the oem unlock option available before doing this though, and had turned it on, but I'm on android 9 which might make a difference
hiden oem option
Laiyox said:
Hello Guys
I want to tell how to bypass RMM state: prenormal to install TWRP
Also this will resolve "Only official binaries are allowed"
Disclaimer:
I am NOT responsible for any damage done if you use my guide.
It worked for me 100% and should normally work for everybody!
Feel free to share to anyone else or to embed if you want.
-------------------------------------------------
1. Download latest Stock base via SamFirm
2. Install latest Stock base via Odin Odin v3.13.1 direct download
3. Boot into system
4. Skip the setup
5. Activate Developer settings
6. search and turn of automatic system update
7. Go to time settings and deactivate automatic time
8. Turn back the day for more than 7 days. ( I have turned to the 20th Dec 2018)
9. Search for Software update -> Don't install update
10. Look if latest time searched for updates is the date which you have set. (for me 20th Dec 2018)
11. Reboot your device
12. go into the time settings and reactivate the automatic time
13. Search again for software update - > Still don't install
14. Go to Developer settings
15. deactivate OEM Unlock and reactivate
16. Go to download mode and you will don't see RMM state anymore
18. install TWRP by odin
19. boot into TWRP
20. format data
21. reboot recovery
22. flash verity.zip // found on https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
23. Et voilà! You got completely functional TWRP on your device with Pie Bootloader
24. Flash your preferred Rom!
-------------------------------------------------
Thanks to:
zxz0O0 for SamFirm
Have Fun
Click to expand...
Click to collapse
when i do deactivate oem option ask for factory reset when i do then thereh is no oem option ?
Hi guys, i have a problem with my S8 (SM-G950F), I want to flash twrp and a custom rom but I can't flash twrp because i have last update (1 september 2019), someone can help me? When I flash the twrp from odin I have FAIL ever, how can i fix kg state prenormal? I used adb and fastboot, i used odin, odin patched-b, princecomsy odin but I can't flash it. I used linux ubuntu 19 with Heimdall flash but it's the same. Thanks in advance.