Tried to enable private mode on my s5 and it started failing. I was rooted and had posed. Reset the pose settings to stock, still didn't work. Unrooted phone in supersu, and uninstalled all the apps i had that were root apps. Still nothing. Multiple reboots, a battery pull, nothing happening. Can anyone suggest me anything outside of a factory reset.
Restoring a backup from before you had rooted it?
You haven't provided any meaningful amount of information in aid of narrowing this down.
Which means that people can only make wild guesses.
What is your Knox status?
What root method did you use?
Did you install Xposed framework or use a custom ROM that includes Xposed?
Did you edit build.prop or use a custom ROM that has modified that file?
Have you frozen any system apps e.g. with Greenify or Titanium?
Post a screen shot of your "About Device" screen in the Settings menu
.
Is there a way to get private mode working after root without xposed ? i've already tried to change the build prop ro.security.storage to false but doesn't worked.
I want to back to stock + root without any another modifications, like xposed, but i use a lot the private mode.. can anyone help me ? thanks.
Personally I had a strange result.
Xposed completely froze my phone, but before it did I too lost private mode.
The first thing I did after rooting was a nand backup, and restoring this after the xposed problem fixed everything. Both privacy mode and S-Health worked perfectly.
I have no idea why, but I have updated my rom since and everything still works.
Sent from my SM-N910F
Install Wanam xposed kit to disable S-health secure server. It can't function properly when xposed is installed
Sent fra min SM-N910F via Tapatalk
If you have the security feature Secure startup enabled, which requires you to enter your password/pin/pattern before your phone boots up, sRGB mode will reset every time. After turning secure start-up off, sRGB mode will stick and you won't need to re-enable it after every reboot. You can disable/enable this feature by going into security and resetting your password
Thanks for the tip, seems to work :good:
Any idea why I can't disable the secure startup feature? I've tried turning password on/off repeatedly, and it never gives me that option again.
amirfk12 said:
Any idea why I can't disable the secure startup feature? I've tried turning password on/off repeatedly, and it never gives me that option again.
Click to expand...
Click to collapse
You need to change it to another security type. For example if you have a PIN change it to pattern and back or vice versa
tried that. didn't work. any other ideas?
I never set secure startup and mine reset every reboot. Since I reboot every day.
Sent from my Nexus 6P using XDA Free mobile app
I can't turn off the secure reset feature as well. I tried changing from pattern to pin to password and still no dice. I even factory reset to see if that would help and it didn't. Maybe a bug that will get fixed in a future update.
Sent from my Nexus 6P using Tapatalk
Can not remove the secure startup
uknowme4me said:
I can't turn off the secure reset feature as well. I tried changing from pattern to pin to password and still no dice. I even factory reset to see if that would help and it didn't. Maybe a bug that will get fixed in a future update.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Did you factory reset through recovery mode or through backup and reset setting?
I did it through both. I just got my 64gb frost 6P yesterday and it does the same exact thing. I'm thinking a software bug.
Sent from my Nexus 6P using Tapatalk
uknowme4me said:
I did it through both. I just got my 64gb frost 6P yesterday and it does the same exact thing. I'm thinking a software bug.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
yeah, was chatting with Google CS....wiped cache, didn't work and so they suggested factory reset. if it didn't work for you, i don't think i'm going to do it
My 6P requires patern before boot up and sRGB does not reset by itself.
Sent from my Nexus 6P using Tapatalk
That did the trick! Thank you!
For those of you still having issues, here are the steps: Settings > Security > Screen Lock (top option on this page) > confirm your password/pattern/etc. > choose a new one (can be the same as before) > THEN you choose the "Secure Start-up" yes or no. CHOOSE " No Thanks" ...Problem solved. Well, for me at least.
Absolutely 100% stock
Non rooted
Build number MDB08K
enhancedcollagen said:
If you have the security feature Secure startup enabled, which requires you to enter your password/pin/pattern before your phone boots up, sRGB mode will reset every time. After turning secure start-up off, sRGB mode will stick and you won't need to re-enable it after every reboot. You can disable/enable this feature by going into security and resetting your password
Click to expand...
Click to collapse
if you disable Secure startup doesn't that make device encryption useless?
I'm having this issue too with my Nexus 6p running Nougat. I'm unable to turn off secure startup. I've tried a factory reset through recovery and that didn't help. I wonder if it's some kind of issue with the OTA. I wish they would hurry up and make the factory image available so I could try flashing it to see if that somehow fixes it. The odd thing is that while running marshmallow I had secure startup in place, but sRGB stuck during a restart. I'm also wondering if decrypting would resolve the issue since that would basically disable secure startup, but I'm reluctant to do that because I'm getting tired of setting up my phone again and again. The other reason I'm reluctant is because my phone was decrypted until I pushed the nougat OTA. If I'm going to go to the trouble of decrypting my phone just to have another OTA encrypt it in the future, I'd rather not bother. Does anyone know whether flashing factory image (not necessarily an OTA) always encrypts the device? (Sorry for my wordiness)
chaddesch said:
I'm having this issue too with my Nexus 6p running Nougat. I'm unable to turn off secure startup. I've tried a factory reset through recovery and that didn't help. I wonder if it's some kind of issue with the OTA. I wish they would hurry up and make the factory image available so I could try flashing it to see if that somehow fixes it. The odd thing is that while running marshmallow I had secure startup in place, but sRGB stuck during a restart. I'm also wondering if decrypting would resolve the issue since that would basically disable secure startup, but I'm reluctant to do that because I'm getting tired of setting up my phone again and again. The other reason I'm reluctant is because my phone was decrypted until I pushed the nougat OTA. If I'm going to go to the trouble of decrypting my phone just to have another OTA encrypt it in the future, I'd rather not bother. Does anyone know whether flashing factory image (not necessarily an OTA) always encrypts the device? (Sorry for my wordiness)
Click to expand...
Click to collapse
Yes. Every OTA will force encryption due to the "forceencrypt" flag in the boot.img. Flashing SuperSU, modified boot.img, or custom kernel will turn that off and keep you decrypted, if you are decrypted.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Yes. Every OTA will force encryption due to the "forceencrypt" flag in the boot.img. Flashing SuperSU, modified boot.img, or custom kernel will turn that off and keep you decrypted, if you are decrypted.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks for the quick reply, SlimSnoopOS. Can I infer that as long as I'm not flashing an OTA and just the system image from the factory image (not the boot image) then it won't screw with the decryption?
chaddesch said:
Thanks for the quick reply, SlimSnoopOS. Can I infer that as long as I'm not flashing an OTA and just the system image from the factory image (not the boot image) then it won't screw with the decryption?
Click to expand...
Click to collapse
It won't but there's nothing wrong with ADB Sideload the OTA zip or manually flashing boot, system and vendor. Just make sure to go directly into TWRP (do not boot into the rom) and flash superuser/custom kernel before booting up to stay decrypted. I've manually installed each OTA and kept decrypted doing those steps.
Sent from my Nexus 5X using Tapatalk
when i use my otg with anything it says charging connected device. when i go to change the setting itll act like it switches then a sec later its back to charging....why is this? a week ago i was using my ps4 controller just fine wired with the otg mow i cant do anything with it, not even in twrp either...any help to fix this would be great!
Same problem here!
Stock rom, not rooted!
/System is encryption , have same without TWRP after TWRP wipe data after work fine
dayl1ght said:
/System is encryption , have same without TWRP after TWRP wipe data after work fine
Click to expand...
Click to collapse
Is there any solution for this without rooting the device?
I don't want to root it, because I use some apps, which are crashes when my device is rooted!
Samsung Costumer Service told me to do a factory reset....pff...
Artemon9 said:
Is there any solution for this without rooting the device?
I don't want to root it, because I use some apps, which are crashes when my device is rooted!
Samsung Costumer Service told me to do a factory reset....pff...
Click to expand...
Click to collapse
you can use Magisk to hide root and fake Knox 0x0 as unroot but device have root.
The ROM development is blooming, and I love that Kudos tp all developers!
However, I am using a mobile banking app that firmly requires me to have my SELinux state as Enforcing, but every ROM still has to be Permissive in order to work properly. When I change it to enforcing by an app, FP sensor and lock screen, button backlights and many other doesn't work.
Can some dev tell me why is this? can we have a ROM that has SELinux enforcing in the near future? If we can't, is there a way to fool an app into thinking that I have Enforcing mode?
Thanks in advance!!
You can use magisk to enable this via an module you find for download.
But this will disable the fingerprint reader. (at least on the RR rom it happend so.)
You have to live with stock til it's fixed