So these were my scenarios so far:Dont worry, i took a holiday from Samsung to avoid the nonsense for years, but then Google stopped making decent Pixel phones, so ive unfortunately been back in the fold for about a year now...it hasnt been happy times for me
I do know how to remove the encryption on an S20+ 5G at least, and in fact, using info from an old post on here, i now actually have created a .tar file that i can flash alongside the stock Samsung ROM to automatically install TWRP at ROM flash time, reboot to it (no needing to nail the vulcan death grip of special keys at the right time in boot process), format /data and immediately disable encryption and then reboot to system to start for 1st time setup, automatically like magic.... i will share it at some point soon for my other S20+ 5G brethren.
I dont know off the top of my head much about the S22 but will look into the threads later today to see what the situation is there for installing TWRP and whether theres a "multi disabler" (as its generally called) zip that does the encryption disabling, for most Samsung devices there is...or you could have a scrounge before i do ....
As mentioned disabling encryption can be a pain in the butt, as you have to create a .tar file with TWRP recovery img in it, flash it alongside the stock ROM (with auto reboot off in ODIN), then (with cable plugged in, otherwise you stand NO chance of getting into it) reboot into the newly written TWRP (if you miss it you will have to reflash the TWRP .tar, because booting to system will overwrite TWRP with stick recovery), then format /data and then flash the multi disabler zip. Almost no one gets this stupid procedure right first go...sometimes even i botch it and ive done it since S2 days...hence why when i found this automated method i refer to above, i spent some time updating the contents of it
Ill look later for the S22 procedures/files, in about 8 hours
As @Dante63 alluded to, theres a magisk module you can try, available from the Releases page of my repo here:
GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted devicesRemoves "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted devices - GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" from ro.s...github.com
Im testing a (lightly) debloated stock ROM based ROM at the moment, and dont even need that module - a quick grep of the file i alter reveals that the key type my module removes is in effect, but my SHealth works fine, so id love to know what the ROM dev has removed to make this work, he does mention removing parts of knox....im planning to ask to see if i can apply it via magisk....
<*>Knox partially removed and ROM light debloated</*>
<*>Removed dm-verity, automatic encryption, proca & vaultkeeper services</*>
in the meantime, on this ROM:
grep "ro.security.keystore.keytype" /vendor/build.prop
-Stock ROM, stock recovery, no root: SHM works, SH does not work
-Stock ROM, stock recovery, root: SHM does not work, SH does work (shamiko+sakv2) -> not running samsung official software message
-Stock ROM, stock recovery, root: SHMmod does not work, SH does work (shamiko+sakv2) -> not running samsung official software message
-Stock ROM, TWRP, no root: SHM does not work, SH does not work -> not running samsung official software message
-Stock ROM, TWRP, root: SHM does not work, SH does work (shamiko+sakv2) -> not running samsung official software message
-Stock ROM, TWRP, root: SHMmod does not work, SH does work (shamiko+sakv2) -> not running samsung official software message
Locked BL, everything stock:
No "not running samsung official software" message and no "unlocked bootloader message"
Samsung Health still does not work, SHM works.
Whatever the case is, I either get SHM to work or SH, not both. Whenever the red "official software" message is displayed (root), SHM does not work, while SH does not work without root (shamiko+sakv2).
As for the TWRP tar files. There are in fact TWRP and vbmeta files with a multidisabler for my model, but apart from installing TWRP, it does nothing to encryption. Well it says it disabled encryption, but nothing really happens.
This has to be by far my worst and most time consuming experience in the mobile world since I got my first device in the late 90s. I'd say some things about the MD's/VP's who enforced those policies, but I'd get banned...so I'll leave them to your immagination.
Thank you all for your time