Android
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
Fucking DRM.
This happens because "normie" Android devices has a proprietary shit called SafeNet Attestation API
SafetyNet is the old thing. It's all about Play Integrity now. Magisk & friends have already moved on to a new method of fingerprint spoofing.
This is the correct take.
More and more every day, I wish the Firefox Phone had survived.
Firefox had a phone? I wish Firefox would try again.
They did. It was a project initially called "Boot to Gecko," about a decade ago; and the idea was to make a Linux kernel OS so lightweight that you were running web apps as close to bare metal as possible. There were intended to be no binary apps, only web apps running on open standards; though that didn't necessarily carry through as originally intended.
I agree. I think it was before its time and would be a real boon today.
I can't remember much about it but I seem to remember that the actual hardware itself was very entry level which was part of the problem. It really would have done better to appeal to enthusiasts.
I get that it was marketed at third world countries, but I still think they would have done better had they had a western version with more up-to-date specs as well, if only to get the kind of market share that would encourage app developers.
It kinda did survive. KaiOS is forked from Firefox OS, though it's more designed for Kinda-Smart feature phones in developing countries.
Just FYI, rootkit malware does exist for phones
Did you unlock your bootloader? Some apps just scan for Google Play SafetyNet or in some other way to check whether you unlocked your bootloader or rooted and if they think you do they will vaguely state you are rooted.
Other's concern about your phone being infected are justified and I recommend you to try whether a dedicated root checking app thinks your phone is rooted. These usually don't lie.
Regarding your rooting situation I always rooted the lazy way. Renamed magisk.apk
to magisk.zip
, flashed it and it always worked for me. But I rooted only 2 phones in my life really and this is not the recommended method by magisk developer.
Does that really work? Because if that works and I can't find an image file, that's the only way. I can still factory reset it after it messes up my device, right?
Uodate: no, it doesn't
Device platform: arm64-v8a
- Installing: 27.0 (27000)
- Processing zip file ! No boot image found ! Process error ! Installation failed
Did you flash a custom ROM? Maybe it will work with a custom ROM.
EDIT: Your phone uses Mediatek processor, so it's not going to be well supported. I recommend you to stick to locked bootloader and just live with the phone as it is.
I've had a banking app think my phone was rooted before. Had to basically switch banks.
Lineage OS user here, my banking app got an update a while ago that stopped trusting my finger scanner because I'm rooted. Luckily it still allows passwords or else that would be a deal breaker.
*Edit, now that I think about it I'm not even rooted, just an unlocked boot loader.
Adjacent topic... Do you use a credit union? Because fuuuuuuck banks.
My bank just merged with another and released a new app. Immediately when trying to log in it said that the app can't be used with developer mode enabled.
With developer mode enabled? I have that enabled, although my error message is about root. With a degoogled stock ROM, you have to have adb to backup system data, it's crazy your bank was blocking that.
Credit unions are better but that doesnt mean their app will work on a rooted device
Source: My credit Union app doesnt work on my rooted devices 🙃
Is your system software fully updated?
Are you running a Beta version of the system software?
But Android is open source! Oh, until you actually do any fucking thing with it. Be gone, Google.
maybe a stupid question: But doesn't android sandbox every app? If every app is running in a sandbox, it shouldn't be too hard to pretend your phone isn't rooted.
If they check for a specific version number, like @RagingRobot mentioned, it also shouldn't be a problem. Just set that specific sandbox to return whatever version you want.
I am aware that 'just configure the sandbox' is not really an accessible solution. But a sandbox-config-master would be a great app for rooted phones.
Well apparently rooted phones can pretend to apps they're not rooted. Problem is, my phone isn't actually rooted.
Turn developer options off.
Do it, my local government app at least had the decency to explain it was the developer mode being on and not root.
This happened to me once when I updated Android. The bank software had a check for a specific version and my version was higher so it thought I was running something weird. I had to wait for the bank to update the app to support the newest android version
I have too many gripes with banks and how they handle digital interactions.
They're a bunch of dinosaurs, both in what they support and how they support it. They're also in a position where they feel like they can do what they want and you just have to suck it up.
And for the most part, they're right, because all the banks are equally bad. A nontrivial number of the apps are just chrome running in an app window, security is a joke, they make you sign in with your card number which is plainly visible to anyone with eyes that is within a few meters of your card anytime you have it out of your wallet, they restrict your password so you can't use special characters or have it be long enough to actually provide real security, and they limit your 2FA options to SMS. Everything is terrible.
Even when you go into the bank or use the ATM, access is restricted by a fucking FOUR DIGIT NUMERICAL PIN and if you can even use a longer pin code, they don't tell you that and most systems assume your pin is four numbers and won't let you enter any more than that.
God forbid you lose your card, good luck going through the gauntlet of outdated information the bank is going to ask about for you to prove you are who you say you are.
They're all the fucking same and it infuriates me.
Install TB Checker and use the various detection modes to figure out what the bank app might be picking up on.
They check for a lot of (dumb) things instead of just checking for Play Integrity like they're supposed to. For example it might be detecting an app that could be using root, even if it's not, and assume that means you must be rooted, even though you're not. 🤷
Wasn't there talk about Google deprecating SafetyNet? If this has already happened and your banking app is still relying on it, it could lead to a fslse positive on the root check I believe.
Had the same problem with my banking app. Fortunately, mine was solved with a reboot.
-
Install Kitsune Mask (just like Magisk install) https://huskydg.github.io/magisk-files/
-
Install PIF Next. It will automatically download new device fingerprints as Google bans old ones https://github.com/daboynb/PlayIntegrityNEXT
-
Google, banks, Microsoft, whoever else is aggressively checking for root. Please consider to eat my entire asshole. Thank you.
Edit: nvm I'm bad at reading, I missed that you couldn't even root your phone.