Im running Resurrection Remix Oreo, and get the warning message "SElinux is not enforcing, your security has been weakened" What exactly does this mean, should I be worried and what can I do about it?
Åttavantar said:
Im running Resurrection Remix Oreo, and get the warning message "SElinux is not enforcing, your security has been weakened" What exactly does this mean, should I be worried and what can I do about it?
Click to expand...
Click to collapse
Selinux just determines what processes can access certain resources on the phone. There's nothing you can do about it as the rom must be compiled with selinux enforcing. Also, there isn't much to worry about.
Im also facing the same issue, how can i fix it, is there any problem with it?
Nithish natla said:
Im also facing the same issue, how can i fix it, is there any problem with it?
Click to expand...
Click to collapse
There is no problems with it. But if you want enforcing then try other ROMs. I think when all the bugs are fixed , selinux will be made enforcing.
Related
My phone is only rooted, I have ignored the security updates since I got it thinking I might loose my root. Is this the case or will it still be rooted and do I need these updates anyway? Also, anyone know of a good rom for the att version that wont kill the battery and has a better camera than the stock one. I sure miss my s3 camera app that was in one of the carbon roms I had on it it was awesome. btw the phone was towel rooted.
ignores it because it has to do with Knox, disable it is better from settings / security
G900H power by Genezis
george0884 said:
ignores it because it has to do with Knox, disable it is better from settings / security
G900H power by Genezis
Click to expand...
Click to collapse
That was kind of what I thought, thanks
for the response
So while rooted if Knox is removed or disabled one can still get Samsung Security Updates to install properly?
tyreman1 said:
So while rooted if Knox is removed or disabled one can still get Samsung Security Updates to install properly?
Click to expand...
Click to collapse
I don't think Knox can be disabled or removed without issues. Novice level answer though.
My 6P is no longer picking up any networks over wifi - the scan list is empty. I have several other devices in the same location that are successfully picking up and connecting to wifi however.
I have ElementalX Kernel 1.19. Marshmallow 6.0.1, Patchlevel June 1 2016.
Can anyone advise on how to proceed with diagnosing and resolving this please?
EDIT: FOUND MY ISSUE, apologies for the lame post.
FYI for those who like me occasionally post before searching in a frantic panic, the issue here was I'd upgraded to 1.19 EX Kernel before going to Patchlevel July 2016.
Yeah, got caught by the same thing. Seems that flar was aware of the issue yet the EXKM still prompts you to download regardless of patch level. You would think that for a known issue the patch level would be checked first.
i have seem issus , but i cant fix it .
colud u plz expline to me how ?
GroovyGeek said:
Yeah, got caught by the same thing. Seems that flar was aware of the issue yet the EXKM still prompts you to download regardless of patch level. You would think that for a known issue the patch level would be checked first.
Click to expand...
Click to collapse
The updater doesn't have that level of granularity. Patch level didn't even exist when I built it.
i am a little confused as i can't realy see a solution on this .. i tried different roms with no success .. i get stuck on Searching for Wi-Fi networks ... please tell me how do i get this going (work)
brangelina said:
i am a little confused as i can't realy see a solution on this .. i tried different roms with no success .. i get stuck on Searching for Wi-Fi networks ... please tell me how do i get this going (work)
Click to expand...
Click to collapse
When you flash July needed roms, have you installed the July Vendor.img as well? If not, download the factory image from Google and pull the img from within the zip. TWRP 3.0 can flash these.
Sent from my Nexus 5X using Tapatalk
I'm not rooted but I can't launch s health on the final version of Nougat that my phone updated to today. (Xxu1dplt)
It says about a Knox warning and device compromised?
It's running stock though! Anyone else with the same issue?
Have you ever rooted before and then unrooted? Sorry if stupid question
Sent from my SM-G935F using XDA-Developers Legacy app
Once knox is tripped, game over even if you unroot.
jadaress1 said:
Have you ever rooted before and then unrooted? Sorry if stupid question
Sent from my SM-G935F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Nope. I assumed s health didn't work in earlier beta due to being beta.
I've never rooted this phone. Only thing I did was install beta by applying in the beta app.
Try uninstall and re-install again s-health
Go to download mode by switching off the device then hold Power + Volume Down + Home
Does it say Warranty void: 1?
CuBz90 said:
Go to download mode by switching off the device then hold Power + Volume Down + Home
Does it say Warranty void: 1?
Click to expand...
Click to collapse
It wasn't but it is now. Seems somehow during the beta it has tripped it. I contacted samsung and they're not interested.
It doesn't matter now as i've bit the bullet and installed twrp+renovate edge rom. Ironically renovate edge is running better than the official rom did with better doze despite having all the same apps installed. And s-health works fine on it.
Not sure what samsung are trying to prove by crippling people running the official ROM.
f1ux said:
It wasn't but it is now. Seems somehow during the beta it has tripped it. I contacted samsung and they're not interested.
It doesn't matter now as i've bit the bullet and installed twrp+renovate edge rom. Ironically renovate edge is running better than the official rom did with better doze despite having all the same apps installed. And s-health works fine on it.
Not sure what samsung are trying to prove by crippling people running the official ROM.
Click to expand...
Click to collapse
Ye if Knox has tripped, Samsung will have nothing to do with it, even if it's their fault, they just don't want to hear about it.
f1ux said:
It wasn't but it is now. Seems somehow during the beta it has tripped it. I contacted samsung and they're not interested.
It doesn't matter now as i've bit the bullet and installed twrp+renovate edge rom. Ironically renovate edge is running better than the official rom did with better doze despite having all the same apps installed. And s-health works fine on it.
Not sure what samsung are trying to prove by crippling people running the official ROM.
Click to expand...
Click to collapse
If what you want is to use SHealth on stock nougat with a knox tripped phone, I can give you a working solution with one caveat.
If you were already a beta tester you need to Odin back to BTU mm (or whatever CSC version you used to join the beta) and setup your phone normally. Make sure you also open SHealth. After, if you have not received a notification to update, go to settings and manually search for updates. Depending on which version of marshmallow you went back to, you might receive one update to the latest 6.0.1 available and after that, you will again be prompted to update, this time to 7.0. If you follow these steps, SHealth will work, even with knox tripped, but, if you manually reset the phone. SHealth will be blocked once again.
I know it seems a little complicated, but it's really not that hard.
Hope this helps.
f1ux said:
Nope. I assumed s health didn't work in earlier beta due to being beta.
I've never rooted this phone. Only thing I did was install beta by applying in the beta app.
Click to expand...
Click to collapse
This is weird . There's no way Knox is tripped without you doing anything like flashing TWRP.
joejoe23 said:
This is weird . There's no way Knox is tripped without you doing anything like flashing TWRP.
Click to expand...
Click to collapse
people lie. the dindu nuffins
joejoe23 said:
This is weird . There's no way Knox is tripped without you doing anything like flashing TWRP.
Click to expand...
Click to collapse
yes, i've been flashing my phone for around 10times with official binaries and never tripped knox. I flashed BTU(from INS) and updated to N, s health working fine here
Ive had the same problem, after flashing the official UK Rom. Knox is not triggered but shealth refused to work.
I reflashed the rom using every file incl. CSC and now everything works like it should.
1stlynx said:
Ive had the same problem, after flashing the official UK Rom. Knox is not triggered but shealth refused to work.
I reflashed the rom using every file incl. CSC and now everything works like it should.
Click to expand...
Click to collapse
I am quite new at this, so you basically did this in Odin?
.... can't post link to picture
You add in Odin: BL, AP, CP and CSC ?
I have the same problem in Shealth, and i would really like to stick with warrenty (Currently in the dawnload mode is still 0). And with Shealth compromised, My Knox app doesn't works as well.
Punisher159 said:
I am quite new at this, so you basically did this in Odin?
.... can't post link to picture
You add in Odin: BL, AP, CP and CSC ?
I have the same problem in Shealth, and i would really like to stick with warrenty (Currently in the dawnload mode is still 0). And with Shealth compromised, My Knox app doesn't works as well.
Click to expand...
Click to collapse
Hi,
i used this guide :
https://www.sammobile.com/forum/showthread.php?t=30800
dont know if i am allowed to post the link.
i did step 3.
Way to make shealth working on tripped but stock devices:
Install marshmallow with odin
Run shealth for it to start collecting user data
Update to nougat without wiping device
profit
kartonick said:
Way to make shealth working on tripped but stock devices:
Install marshmallow with odin
Run shealth for it to start collecting user data
Update to nougat without wiping device
profit
Click to expand...
Click to collapse
i have tried that but i wont count steps. so its of no use. when updated it... stopped working completely
poncespr said:
If what you want is to use SHealth on stock nougat with a knox tripped phone, I can give you a working solution with one caveat.
If you were already a beta tester you need to Odin back to BTU mm (or whatever CSC version you used to join the beta) and setup your phone normally. Make sure you also open SHealth. After, if you have not received a notification to update, go to settings and manually search for updates. Depending on which version of marshmallow you went back to, you might receive one update to the latest 6.0.1 available and after that, you will again be prompted to update, this time to 7.0. If you follow these steps, SHealth will work, even with knox tripped, but, if you manually reset the phone. SHealth will be blocked once again.
I know it seems a little complicated, but it's really not that hard.
Hope this helps.
Click to expand...
Click to collapse
Hello,
I am interested with the first solution. Can you please give me more detail how to proced ? Thank you in advance
does samsung pay works with u? i bought a second hand uk handset without having any knowledge of knox which was tripped. though i got it to work following a post here, samsung pay doesnot work evenon stock firmware.
elkhalifi said:
Hello,
I am interested with the first solution. Can you please give me more detail how to proced ? Thank you in advance
Click to expand...
Click to collapse
Thank you poncespr, your solution woked for me.
I am able to launch SHealth again
Safetynet is really becoming widely used in apps such as Netflix and Banking apps and while other devices pass safetynet through magisk easily, our devices could not. At best case scenario only the basic integrity check passes. Now, there is a kernel patch made by sultanxda to bypass the safetynet check on our kernels. Would it be worth it if someone recompiles Anykernel with the safetynet patch?
Lightracer said:
Safetynet is really becoming widely used in apps such as Netflix and Banking apps and while other devices pass safetynet through magisk easily, our devices could not. At best case scenario only the basic integrity check passes. Now, there is a kernel patch made by sultanxda to bypass the safetynet check on our kernels. Would it be worth it if someone recompiles Anykernel with the safetynet patch?
Click to expand...
Click to collapse
you should ask Android-andi directly, when he gets back his LG device
Disabling a security feature sounds stupid if i care about rom security all the time... Beside that i am not even sure if we would ever need that mentioned kernel patch.
ninestarkoko said:
you should ask Android-andi directly, when he gets back his LG device
Click to expand...
Click to collapse
Andi's AnyKernel thread mentions "No Feature Requests" so I don't really want to donate
$$$ to a charity because I'm broke
Android-Andi said:
Disabling a security feature sounds stupid if i care about rom security all the time... Beides that i am not even sure if we would ever need that mentiones kernel patch.
Click to expand...
Click to collapse
Maybe you're right, posts about that kernel patch dates back to October 2016 and I can't find any threads for it
Lightracer said:
Safetynet is really becoming widely used in apps such as Netflix and Banking apps and while other devices pass safetynet through magisk easily, our devices could not. At best case scenario only the basic integrity check passes. Now, there is a kernel patch made by sultanxda to bypass the safetynet check on our kernels. Would it be worth it if someone recompiles Anykernel with the safetynet patch?
Click to expand...
Click to collapse
i applied this patch on a non-public test build of rr 5.7.4. this patch dont solve the problem for now, because hide magisk is not working properly with our tab.
smart-t78 said:
i applied this patch on a non-public test build of rr 5.7.4. this patch dont solve the problem for now, because hide magisk is not working properly with our tab.
Click to expand...
Click to collapse
Oh, is the problem found yet or is it still a mystery?
Lightracer said:
Oh, is the problem found yet or is it still a mystery?
Click to expand...
Click to collapse
its still a mystery.
i worked on a rr version with inbuilt magisk some weeks ago. root works without problems but hide magisk dont do his job. so it doesnt matter if the patch applied or not. cts profile check fails.
This tablet P3110 used to do Netflix just fine... What was the last Netflix version before the switch? And is that version still working for Netflix viewing or is it blocked too?
ONLY FOR INFO
https://www.lineageos.org/Safetynet/
Just an small update: we don't need this freaking kernel workarounds other devices need because of the bootloader.
Latest slim6 and omni6 by me, also latest official lineage pass safetynet out of the box (not sure if lineage needs magisk to hide su, slim6 and omni6 are "user" builds and don't even allow adb root access)
I just bought one of the Oral B 8000 toothbrushes and apparently there is an issue in Android 7.0 which won't allow the toothbrush to pair over bluetooth with the phone app. I was curious if anyone else had come across this issue and gotten it resolved. The issue is known to Oral B but right now the only fix is to upgrade to Android 7.1 and I would like to stay on stock firmware because it's nice and stable. I am rooted and bootloader unlocked so if absolutely necessary I can change roms but I was hoping someone might know of a fix. Was also curious if the latest phone update might have fixed it even though it didn't change the Android version number.
pwnerman said:
I just bought one of the Oral B 8000 toothbrushes and apparently there is an issue in Android 7.0 which won't allow the toothbrush to pair over bluetooth with the phone app. I was curious if anyone else had come across this issue and gotten it resolved. The issue is known to Oral B but right now the only fix is to upgrade to Android 7.1 and I would like to stay on stock firmware because it's nice and stable. I am rooted and bootloader unlocked so if absolutely necessary I can change roms but I was hoping someone might know of a fix. Was also curious if the latest phone update might have fixed it even though it didn't change the Android version number.
Click to expand...
Click to collapse
an Android controlled toothbrush? is it april 1st? How does that work?
blue"tooth" LOL
You listen to music via vibration of your teeth.
railfan-eric said:
an Android controlled toothbrush? is it april 1st? How does that work?
Click to expand...
Click to collapse
it syncs with bluetooth and your phone camera to see what stops you are missing and over brushing. even without all that functionality and just as a dumb toothbrush it really is worth it
Same problem with LG G5 with 7.0. Did you find any solution?
Oral-B not starting on rooted devices
Hi,
Has anyone managed to use the Oral-B app on a rooted android? I am on Oreo with Xposed, and despite adding the app to Rootcloak config, it will detect the root.
I've read on the app comments that uninstalling supersu makes the app work, so it may be that Rootcloak default config is missing some keywords/commands?
jbd7 said:
Hi,
Has anyone managed to use the Oral-B app on a rooted android? I am on Oreo with Xposed, and despite adding the app to Rootcloak config, it will detect the root.
I've read on the app comments that uninstalling supersu makes the app work, so it may be that Rootcloak default config is missing some keywords/commands?
Click to expand...
Click to collapse
hi. did you find a solution? rootcloack didnt help me...
Ugo10 said:
hi. did you find a solution? rootcloack didnt help me...
Click to expand...
Click to collapse
Yes, it's working for me now. I have actually two solutions.
- I moved from superSU to Magisk. I still don't pass SafetyNet as I'm using gravity box. Now I'm with Oral-B app 6.0.1 and it starts and works correctly.
- at some point, while still with superSU, I downgraded the app with an apk of a previous version found online. The v5.2.3 doesn't seem to have SafetyNet implemented and it has the same features anyway. Remember to disable "auto update" in Google play to remain on that version.
jbd7 said:
Yes, it's working for me now. I have actually two solutions.
- I moved from superSU to Magisk. I still don't pass SafetyNet as I'm using gravity box. Now I'm with Oral-B app 6.0.1 and it starts and works correctly.
- at some point, while still with superSU, I downgraded the app with an apk of a previous version found online. The v5.2.3 doesn't seem to have SafetyNet implemented and it has the same features anyway. Remember to disable "auto update" in Google play to remain on that version.
Click to expand...
Click to collapse
it's perfect! thx!