[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.
Related
Forgive my ignorance, but ive never used android before and expecting my phone delivered tomorrow (htc hero! )
As i understand it, the android app store signs the apps similar to iphones itunes store to prevent piracy and malware.
Is this correct?
Ive read about how one can "root" the device by loading a image file thru the bootloader over usb, but i wonder, is there a sudo command or similar to temporarily enable root access and later return to default state?
I suppose i could flash it with the root image, install the app and then flash back the default os image, but that feels pretty awkward procedure and would probably raise a bunch of new problems as how the default os would launch the app installed under another os.
I was hoping to start tinkering with programming, but im unsure if i can "throw in the app" and expect it to work..?
After using mac´s for over 20 years ive become too used to stuff just working right out of the box, so i dont feel like experimenting on my own...
There is an option in the settings that lets you install unsigned apps, so no rooting required.
xarvox said:
As i understand it, the android app store signs the apps similar to iphones itunes store to prevent piracy and malware.
Is this correct?
Click to expand...
Click to collapse
Not exactly! Many paid apps are copy protected, but most of the free ones are not. Unlike the iPhone, where you can only install "unauthorized" apps if you jail break the device, Android allows you to install and run applications from a variety of sources on a stock device.
In essence, you do not need to root the device to develop for it, but there are certain things that applications can only be done on a rooted device (for example, receiving a file via Bluetooth, WiFi tethering etc).
I was hoping to start tinkering with programming, but im unsure if i can "throw in the app" and expect it to work..?
Click to expand...
Click to collapse
Well, programming errors aside ( ), and as long as you don't need to do anything that requires root privileges, yes you can. You should bear in mind that the *vast* majority of Android devices will not have been rooted, and therefore the vast majority of available applications do not require rooted phones.
Personally, I expect that later Android builds will remove many of the restrictions that require applications to have root access, so that they can function without requiring a device to be rooted.
Regards,
Dave
Ive found a app that would tether my laptop (mac) over wifi, but requires me to root the device.
Is there a way to temporarily do this, install the app and make the neccisary changes and then switch back to default state?
I don't believe so.
As far as I'm aware, the application requires the elevated privileges when it runs as opposed to just configuration changes. I don't think that even a setuid would help, since I believe the app expects to find and use su/sudo.
Regards,
Dave
Fact: 99% of mobile viruses are for Android.
In general it is never wise in a *nix environment to be root.
See this: http://www.howtogeek.com/132115/the-case-against-root-why-android-devices-dont-come-rooted/
So if I have an older Android device (the Defy+ in particular) I have the option of either root it and try the later CyanogenMod or not to root and stay with Gingerbread forever?
Is there a way that after I installed Cyanogenmod I somehow de-root or un-root the device for safety? I am not that technical; I guess it's not possible; so it remains more like a philosophical question. Not only about the Defy+ in particular but in general.
Un-rooting can depend on the device and the method used to root it.
Of course, you could always just delete your superuser app, or use an app encrypter to require a password to use it. I wouldn't bother though. The benefits of root are too good to pass up if you've already taken that leap. Back-ups, ad blocking, Xposed tweaks, etc.
Doing stupid stuff with a rooted phone can certainly ruin it. The solution is not to do stupid stuff. The best way to keep your device safe is to just use your head. If you want to clean up bloatware, use Clean Master or a similar app that lets you know whether uninstalling something will affect your phone. Only side-load apps from sources you (and other people) trust. Do you research before doing anything that cause a problem. If you don't know, ask here.
That "Fact" you have is absolutely pulled straight out of someone's @$$. Viruses - no. Malware - yes. Don't install shady apps from unknown developers and "99%" of the problems won't even be an issue. And you can run a custom rom without root, such as Cyanogenmod. All root is is enabling admin access of your phone. You can even enable and disable as needed. When you have a superuser app, it controls the root permissions of the phone and you have the option of denying root, allowing root once, to request in a certain time frame, or to run it always.
Ok, So i got the new updates from Google Wallet to the new Google Wallet and Android Pay.
When I attempted to setup Android Pay, I received the error that my device couldn't be "verified as being compatible."
A little browsing turned up some information that Android Pay doesn't like rooted devices, and even gave a couple of solutions.
1. Disable Superuser access if your Superuser app has the capability.
2. If option one isn't possible, then go back to stock, activate, and re-root.
This fix will NOT work for everyone, but since it is a simple setting change, it can't hurt to try this before looking into more 'drastic' measures. This will most likely only work on rooted stock ROMS.
I know that I use Chainfire's SuperSU app, and it has the ability to be disabled so the operator does not has superuser access until it is re-enabled. Simply go to your SuperSU app, go into the "Settings," and uncheck the "Enable Superuser." Different versions and other apps may be a little different, but principle should remain the same if it is an option.
After disabling SuperSU, open Android Pay and complete your initial setup. Once completed, return to the SuperSU app and re-enable Superuser access. The Android Pay app has continued working since then for me.
Based on information given by 'rbeavers,'
https://koz.io/inside-safetynet/
Guess I'm screwed
Click to expand...
Click to collapse
it appears rooted stock ROMs will probably work if you disable superuser (no guarantee though). Custom and ported ROMs most likely will never work unless the devs figure out a workaround. I would also imagine a otherwise stock ROM running a custom kernel wouldn't work either based on rbeavers' link.
Another note, I've integrated updated system apps and certain other apps into the system partition, so that probably won't matter if anyone is curious about that. (Could be different for other people though.)
Original Posting:
Just got the new Android Pay. I received an error that my device couldn't be verified as being compatible. Found some where else that it doesn't like rooted devices . Fix with SuperSU is easy. Go to SuperSU, touch Settings, and uncheck Enable superuser. Setup Android Pay, then re enable it, and so far, it's working for me.
Click to expand...
Click to collapse
Tried it didn't work for me "turned off " SU. My bank isn't on the "list". So that might be it?
Maybe? I didn't think Android Pay used the bank account, only Wallet does. Pay requires you to link your debit or credit card. Both apps automatically pulled my information, so I didn't have to dig into that very much.
Another thing my ROM is otherwise stock.
I've also read that Android Pay just doesn't like some ROMs, so users on custom or ported ROMs and a few devices in general are probably going to be left out in the cold... unfortunately.
Hopefully someone with more knowledge of the Android system can help us out here soon.
https://koz.io/inside-safetynet/
Guess I'm screwed?
Interesting read. Thanks for sharing
So, rooted stock ROMs will probably work if you disable superuser (no guarantee though). Custom and ported ROMs most likely will never work unless the devs figure out a workaround. I would also imagine a otherwise stock ROM running a custom kernel wouldn't work either based on your link.
Another note, I've integrated updated system apps and certain other apps into the system partition, so that shouldn't matter if anyone is curious about that.
Hey team,
Long time forum creeper and general tech hacker / fiddler. I don't generally post on forums but I'm hoping to nab some suggestions. Done a fair lot of looking already, but either turning up stones / outdated info / things that just aren't applicable to me.
Been looking to get Snapchat (and other stubborn apps similar) logged in on my device, honestly I don't even really use it and it's turned into more of a challenge getting it to run at this point because instead of thinking if I should I'm fixated more with the idea of proving that I could.
The phone is rooted, yes I know I could un-root it, stock rom, blah blah, but where is the fun in that?
Anywho the setup is as follows.
Galaxy S10+ SM-975F (Exynos)
Lineage OS 17.1 (Custom rom found here)
I have TWRP in as a recovery, phone is rooted with Magisk and it runs MicroG.
I have signature spoofing working with EdXposed (FakeGapps) and funnily enough I pass SafetyNet (lol I know, wassup google)
(HiddenCore for Xposed helps with this for those who seem to be struggling with newer devices)(Google is your friend "sometimes")
Now, I've done the obvious and sorted out Magisk hide, I've also tried RootCloak for Xposed with no success, again done the obvious install / reinstall / clear app data storage etc etc.
Does anyone have any ideas about what further detection methods they are employing? You'd think hiding root and passing SafetyNet would do it, but noooooo.
NB: In before It's some silly app I've left installed it doesn't like.
Your suggestions would be greatly appreciated!
deusxanthus said:
Hey team,
Long time forum creeper and general tech hacker / fiddler. I don't generally post on forums but I'm hoping to nab some suggestions. Done a fair lot of looking already, but either turning up stones / outdated info / things that just aren't applicable to me.
Been looking to get Snapchat (and other stubborn apps similar) logged in on my device, honestly I don't even really use it and it's turned into more of a challenge getting it to run at this point because instead of thinking if I should I'm fixated more with the idea of proving that I could.
The phone is rooted, yes I know I could un-root it, stock rom, blah blah, but where is the fun in that?
Anywho the setup is as follows.
Galaxy S10+ SM-975F (Exynos)
Lineage OS 17.1 (Custom rom found here)
I have TWRP in as a recovery, phone is rooted with Magisk and it runs MicroG.
I have signature spoofing working with EdXposed (FakeGapps) and funnily enough I pass SafetyNet (lol I know, wassup google)
(HiddenCore for Xposed helps with this for those who seem to be struggling with newer devices)(Google is your friend "sometimes")
Now, I've done the obvious and sorted out Magisk hide, I've also tried RootCloak for Xposed with no success, again done the obvious install / reinstall / clear app data storage etc etc.
Does anyone have any ideas about what further detection methods they are employing? You'd think hiding root and passing SafetyNet would do it, but noooooo.
NB: In before It's some silly app I've left installed it doesn't like.
Your suggestions would be greatly appreciated!
Click to expand...
Click to collapse
Sorry for double post, I've spent time podding and poking with some code and packaged something that seems to be working!
I'll keep testing it and come back
deusxanthus said:
Hey team,
Long time forum creeper and general tech hacker / fiddler. I don't generally post on forums but I'm hoping to nab some suggestions. Done a fair lot of looking already, but either turning up stones / outdated info / things that just aren't applicable to me.
Been looking to get Snapchat (and other stubborn apps similar) logged in on my device, honestly I don't even really use it and it's turned into more of a challenge getting it to run at this point because instead of thinking if I should I'm fixated more with the idea of proving that I could.
The phone is rooted, yes I know I could un-root it, stock rom, blah blah, but where is the fun in that?
Anywho the setup is as follows.
Galaxy S10+ SM-975F (Exynos)
Lineage OS 17.1 (Custom rom found here)
I have TWRP in as a recovery, phone is rooted with Magisk and it runs MicroG.
I have signature spoofing working with EdXposed (FakeGapps) and funnily enough I pass SafetyNet (lol I know, wassup google)
(HiddenCore for Xposed helps with this for those who seem to be struggling with newer devices)(Google is your friend "sometimes")
Now, I've done the obvious and sorted out Magisk hide, I've also tried RootCloak for Xposed with no success, again done the obvious install / reinstall / clear app data storage etc etc.
Does anyone have any ideas about what further detection methods they are employing? You'd think hiding root and passing SafetyNet would do it, but noooooo.
NB: In before It's some silly app I've left installed it doesn't like.
Your suggestions would be greatly appreciated!
Click to expand...
Click to collapse
Are you able to help me unlock a permanently locked Snapchat?
I have never used a Pixel phone, but I am strongly considering a Pixel 6 now. I want to root the phone using Magisk **and** I want to successfully hide root. Furthermore, I want to be able to install some modules in an Xposed-like framework such as LSPosed, and I want the existence of that XPosed-like framework also to be hidden. Ever since Android 11, it's been complicated and confusing to figure out how to accomplish all of this in a reliable manner, given the latest changing versions of Magisk and given the various root-hiding mechanisms that are now offered, and which are also now still in development.
There is a huge amount of information about this general topic in the following threads ...
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/page-2689#post-87696219
https://forum.xda-developers.com/t/discussion-magisk-the-age-of-zygisk.4393877/
https://forum.xda-developers.com/t/...r-unofficial-third-party-magisk-fork.4460555/
https://forum.xda-developers.com/t/lsposed-xposed-framework-8-1-13-0-simple-magisk-module.4228973/
... however, there are collectively more than 50,000 messages in this group of threads, and for me, this fits into the category of "Too Much Information", especialy given that much of this info is contradictory, with different people reporting success and others reporting failure, and different people reporting slightly different versions of the same procedures.
The reason I'm posting here is that I'm wondering of anyone has successfully accomplished what I'm trying to do with a Pixel 6 under Android 11 or Android 12, and if so, whether that person (or people) might be willing to share a straightforward, step-by-step, cookbook-like set of instructions about how to accomplish all of this from beginning to end.
By "beginning to end", I mean to start with a brand new locked Pixel 6 and to install all of the software and features that I described above, with the end result being a reliably rooted Pixel 6 (with root reliably hidden) running some sort of XPosed-like framework under Android 11 or Android 12, and which can be consistently rebooted with no boot loops.
If that is considered off-topic here, I'm glad to take this into private chat.
Thank you very much in advance for any help that you might be able to offer.
What he said, but instead of android 11 or 12, give me one for 13 please.
Oh! I somehow overlooked the following thread when I first came here:
https://forum.xda-developers.com/t/...nlock-bootloader-pass-safetynet-more.4388733/
It covers a lot of the information I'm looking for.
I will soon dig into that thread in more detail, and if it indeed ends up explaining everything that I want to learn, then I will abandon this current thread.
But for the moment, I'll keep this thread alive.
I can confirm my rooted Pixel 6 running 13 passes SafetyNet check and is certified in the Play app following those instructions. However, Google is not using SafetyNet to check for an unlocked bootloader in their apps anymore. GPay complains about device security and there are some apps that I can't download. Netflix, Hulu. Other than GApp and having to sideload Netflix, I don't have any issues.
Here's a thread about the new security check.
https://forum.xda-developers.com/t/discussion-play-integrity-api.4479337/
anyone having issues with some apps detecting root even after magiskhide should try the shamiko module. helped me
few stupid questions regarding rooting my pixel 6 .....
1) its new unlocked phone, should i have the new SIM in phone when rooting, does it matter ?
ok to put it when its done ?
same question for being signed into Google account when rooting, does it even matter, either way ?
2) is there a way to get the pixel phone transfer to show back up, or a way to access it ?
Its very easy for me to transfer all backed up data from my current Pixel 3 that way...
3) can I still run my banking & crypto apps once rooted ? I have read conflicting reports on this... elsewhere that is.
Thank y'all for the awesome information ya provide on here, and Thank You in advance if you have any input for me rooting...
Its amazing how far along we've come along since my bag phone
kengel1969 said:
few stupid questions regarding rooting my pixel 6 .....
1) its new unlocked phone, should i have the new SIM in phone when rooting, does it matter ?
ok to put it when its done ?
same question for being signed into Google account when rooting, does it even matter, either way ?
2) is there a way to get the pixel phone transfer to show back up, or a way to access it ?
Its very easy for me to transfer all backed up data from my current Pixel 3 that way...
3) can I still run my banking & crypto apps once rooted ? I have read conflicting reports on this... elsewhere that is.
Thank y'all for the awesome information ya provide on here, and Thank You in advance if you have any input for me rooting...
Its amazing how far along we've come along since my bag phone
Click to expand...
Click to collapse
1. No, yes, no
2. Yes, kind of
3. Yes with safetynet module and magisk deny list, and sometimes magisk props.
Read @Volatyle's and @Homeboy76's guides. Great info in both.
It would be better if you explained what your end result is. Hiding root can be very difficult; depending on the app requirements, simply having an unlocked bootloader can be enough, because an unlocked device will always fail hardware backed attestation.
If you're simply trying to get apps like Google Pay to work, you should need to do nothing more than install Displax's modded USNF module, and enforce DenyList on the Play Store and Play Protect service.
If on the other hand you're trying to use apps that specifically detect the presence of Magisk, then you may need to hide the Magisk app. As far as hiding the presence of root itself, I am unsure as to whether any app without root privileges can detect whether an SU binary is installed. Someone like @pndwal would know better than I would.