and how not to do this by accident ?
I managed to reproduce this issue after clearing my "Personal pages service" data, it resets the private key on the service level only, and somehow the password stay incorrect while calling "mount_privatemode 1000 /mnt/shell/privatemode /storage/Private" even if i force the regeneration of the private and backup key!
Disabling secure storage let you bypass its checks but it fails now on the Knox container level "com.sec.knox.container.util.EnterprisePartitionMa nager.mountPrivateMode", there no way to reset the password, obviously it requires the old one, so i don't see what we can do at this level .
I also had this issue until some minutes ago.
Honestly I don't know why but before rooting and installing xposed, I think I cleared the PersonalPage service data...I ended up in an unusable PrivateMode like other users on this thread but even worse, for me, the impossibility of removing my fingerprint reading since I was using the fingerprint unlock method with PrivateMode.
I am investigating from 1hour and, as you said, there is something strange with the FsKeyBackup string. The 'getPrivateFsKeyBackup()' method always return null and the entire management of this second key seems to be left to com.sec.knox.container.
I found 'privatemode_edk_1000' under '/data/system/users' and guess what. By deleting this file (to force its creation again) the backup key is handled correctly, getPrivateFsKeyBackup() does not return null anymore and PrivateMode works again.
*For users which have some files in PrivateMode: this procedure will reinitialize PrivateMode thus all your private data will be destroyed.
I am testing all this stuff on a Note4 N910F
I was not planning to buy a GalaxyS5, but i was lucky to get one as gift this weekend.
One of the issues i noticed on the past two days was the SHealth incompatibility with Xposed (described on this thread), somehow if you are using Xposed framework, Secure storage will fails to process and save data, which leads to Sensor service hangs
This module bypass the secure storage checks on SHealth and Private mode services, and will let you load the SHealth App with no hangs and activate Private mode on Rooted Samsung devices running Xposed framework.
I did just the basic tests for SHealth because i don't use this App anyway, it's not easy to play football with a device on my hands/pocket .
|samsung, secure storage, security, shealth, xposed|
|Thread Tools||Search this Thread|