I have recently rooted my S21, and it works perfectly except for apps such as Paypal having issues around the use of fingerprints.
I can unlock the phone with fingerprints, but every app with the ability to read fingerprints fails. Is this happening for anyone else, and does anyone have any tips?
you needed to backup the DRM keys or use hacked kernal .img
i dont know if there is workaround yet for the S21 series
some app can hack this, but its ilegal AFAIK
also netflix and similar apps might not work well or at all for you
I seem to have fixed the issue. I traced it down to being related to the safety-net magisk module I had flashed. It turns out there seem to be known issues with it, and have been resolved in a test release (version 2.0 I believe)
Pisaman2 where did you get ver 2.0 from plz. Also did you have to use magisk props to change fingerprint like before? Or can you just install ver 2.0 and it will work without issues.
Related
I have yet to get the FP Nav to properly work (or work at all) in either weekly.
I installed weekly 6 with a fresh install and it worked until I restored my apps with Titanium.
Any ideas as to apps that would prevent this from working?
I have tried DPAD, Trackball, and Mouse. and NAV Enable IS set to Enable.
3 day bump 10char
Don't restore random stuff with Titanium and you'll be fine. Just restore the apps you got from the market or sideloaded.
Hmm. I just tried to enable FP nav on weekly #6 (I had it disabled since right after install) and it wouldn't work. Moreover, the FP reader, which had been working, now doesn't work either (I get "Enroll Not Successful"). I'm sure I installed/updated an app or two in the interim, but just through the Market--I did not restore anything via Titanium.
Ah well, I don't completely trust the FP reader anyway, although when it was working it worked pretty well. If there's a way to get it working again without reflashing CM7 I'd be interested. I tried to find the settings discussed in the following thread:
forum.xda-developers.com/showthread.php?t=977600
. . . but there is no "com.motorola.android.providers.settings" directory in /data/data. I guess those settings might be for stock roms, not CM7?
I had a lot of random reboots with FP in weekly #6 so I ended up disabling it and deleting the apks associated with it just to be sure it wouldn't reboot.
I deleted the following apks and I haven't had any random reboots since then.
Atrix Settings 1.0
Fingerprint sensor
com.cyanogenmod.truemobileaudio
Hey Guys,
so i have some questions i need answers for before i just go in and try to update my modded S9 to Android 9
My Setup:
Galaxy S9 SM-G960F Exynos
Messed up my ROM once and had no backup so i installed a stock one from SamMobile or something.
Edit: forgot to mention that i'm from germany. i think there are some region specific FWs so keep that in mind.. im not sure which specific ROM i installed but it should be a stock rom with correct region and model number.
TWRP installed.
Magisk v17.3 with Manager v6.1.0 installed with following modules{
Systemless Hosts,
YouTube Vanced v13.34.50(b01.25.00)
}.
I have bxActions installed and mapped my bx button to 4 actions{
NavBar->Back,
NavBar->TaskManager,
NavBar->Home,
Google Assistant
}.
i modified my build.prop so my NavBar isnt visible for more screen real estate (thats why my bx button has these mappings).
I applied some black and red theme for GBoard and overall system Theme (status bar and whatever... settings menu and stuff).
Im also using AdAway (thats why i have the Systemless Hosts module installed in magisk).
SafetyNet is no Problem. i can use all apps i heard i could have problems with when magisk not properly installed{
Pokemon GO,
Snapchat,
Google Pay (although it doesnt work correct recently... might be a problem with my PayPal tho),
Banking App etc..
}.
I also started app dev with flutter with it via USB-Debugging if thats somehow important to know.
My Questions:
Since im not able to Update via OTA.. how can i update to android 9 safely without messing up my setup?
What does work after the Update and what doesnt? TWRP ****ed up? build.pro mod gone? magisk?
Is it even worth it to update?
oh and while we are at it: since knox is tripped some features like secure folder etc dont work. any alternatives for something like a password secured folder or similar?
Thanks for your help
I test app builds for (a little) income. The app I use to test builds is called UserTesting. The app records my screen during while I test builds.
Since rooting my phone, I've been unable to successfully complete a test. I accept a test, start the screen recorder, and then I get a notification: "Your test has been cancelled." I believe this is related to rooting, since I never had this problem before.
I've tried to fix it using:
Magisk Hide
Magisk Hide Props Config > Changing the fingerprint of my phone
By using those solutions, I've been able to run my banking apps. But I still can't get UserTesting working.
Theories:
Even though I've blocked UserTesting from seeing that my phone is rooted, maybe it still manages to do it via the screen recorder? Could that be?
My phone runs Android 10, but the fingerprint I chose was Android 9, because that was the latest available in Props. Could that be causing problems?
Does anyone know why this app isn't working and how I can fix it? Thank you.
My specs:
Sony Xperia XZ1 Compact
Running LineageOS 17.1 Unofficial 1.6
Magisk 20.4 (20400)
[Please let me know if this should be posted elsewhere, somewhere more targeted at rooted phones wherever that might be.]
I have an SM-G998U, bootloader unlocked and rooted with Magisk. (Official ROM still.) I'm experiencing some odd behavior with biometrics; for example...
LastPass reports a "change in biometrics" and is requiring both my master password AND my fingerprint; earlier editions on a different device (LG V20, likewise rooted) would only complain about being installed on a rooted device but would otherwise operate normally (current version on this phone makes no such complaint);
My medical records app refuses to let me use biometrics at all;
My banking app happily lets me use my fingerprint as if nothing is amiss.
I don't know much about how biometrics work on the S21, or how Samsung may have tried to harden them (e.g. via Knox). I don't mind tinkering and I don't mind risking the phone; does anyone have any thoughts (or knowledge) as to what I might try to make the complaining apps work more like nothing is unusual? (Note: MagiskHide and Storage Isolation (arm version) do not seem to help in the examples above.)
dwkindig said:
[Please let me know if this should be posted elsewhere, somewhere more targeted at rooted phones wherever that might be.]
I have an SM-G998U, bootloader unlocked and rooted with Magisk. (Official ROM still.) I'm experiencing some odd behavior with biometrics; for example...
LastPass reports a "change in biometrics" and is requiring both my master password AND my fingerprint; earlier editions on a different device (LG V20, likewise rooted) would only complain about being installed on a rooted device but would otherwise operate normally (current version on this phone makes no such complaint);
My medical records app refuses to let me use biometrics at all;
My banking app happily lets me use my fingerprint as if nothing is amiss.
I don't know much about how biometrics work on the S21, or how Samsung may have tried to harden them (e.g. via Knox). I don't mind tinkering and I don't mind risking the phone; does anyone have any thoughts (or knowledge) as to what I might try to make the complaining apps work more like nothing is unusual? (Note: MagiskHide and Storage Isolation (arm version) do not seem to help in the examples above.)
Click to expand...
Click to collapse
AFAIK rooting (triggering KNOX) or unlocking will not (directly) break biometric features.
Maybe it's just an issue with a few apps that refuse to work properly.
MagiskHide would have been my first try too. Check for Magisk updates. Hopefully the hiding will be optimized ... so that your apps can no longer recognize root.
Backstory: So got my daughter a bluetooth enabled toothbrush named in title, and loaded up the app for it:
Philips Sonicare For Kids - Apps on Google Play
Transform brush time into fun time!
play.google.com
Running on a OnePlus 6, Android 10 stock firmware other than bootloader unlocked, Magisk installed. Start it up, whines it is rooted and refuses to run. Sputter some colorful language, add app to Magisk Hide, restart, poof, works great.
Now daughter likes it, and don't want to give her my phone twice a day... so open the drawer and pull out an older phone, LG G6. Old firmware, prob full of security issues, figure I'll install LineageOS on it. OK, great, get through all that, shiny running system... repeat app install... and ugh... "t3h r00t3d phone!".
This time, Magisk Hide isn't "fixing" the problem, and I am curious what the difference is... same app version on both phones. Safetynet check passes on both phones. The only real differences I can cite are (1) Android 11 OS base and (2) Roar Gapps MiniMe build (vs full Gapp suite on stock OnePlus rom). At this point, there aren't other apps on the device (e.g. SuperSU or similar usual suspect).
Any suggestions on what is different that an app could check and call out a rooted phone?
Answering my own post, in case anyone searches this and finds it helpful...
Turns out this app appears to blacklist Lineage OS.
Reflashed clean, OS only... fail. (No root or safetynet at this point)
Added somewhat normal Gapps, now with working safetynet... fail.
Didn't need to install Magisk at this point.
Lets test the theory... grab another OS image at random, flash it (still no Gapps, Magisk, SN)... success!
Install Magisk, still success!