Well this is a bummer. In case folks haven't seen this, Chainfire will be halting all development of root-related products.
Google+ post by
Chainfire - https://plus.google.com/+Chainfire/posts/ZVDG2SnmgM5
Moto G5S Plus XT1806, FrankenROM Oreo, MultiROM, Tapatalk 4.9.5
Thanks for killing all my devices........
This has been known for quite awhile, it's not new news (although the referenced Twitter post is recent). He sold the rights to SuperSU to CCMT quite some time ago. I think SuperSU and his other apps will still be updated, but by CCMT, not him. He long ago stated that he has been looking to distance himself from his projects. I guess he just wants to move on and have a life outside of Android, I can understand his viewpoint.
My only hope is that SuperSU will become open source, it has always been closed source thusfar. We now have flourishing projects like Magisk that are open source and doing well, despite its' issues (the ones I've had with it anyway). There is a lesser known root method called Phh's Superuser that is also open source, though not nearly as popular as Magisk or SuperSU. I think SuperSU would do well to open its' code and let the world contribute to it so that it can be further improved.
I wish @Chainfire the best of luck.
AnonVendetta said:
This has been known for quite awhile, it's not new news (although the referenced Twitter post is recent). He sold the rights to SuperSU to CCMT quite some time ago. I think SuperSU and his other apps will still be updated, but by CCMT, not him. He long ago stated that he has been looking to distance himself from his projects. I guess he just wants to move on and have a life outside of Android, I can understand his viewpoint.
My only hope is that SuperSU will become open source, it has always been closed source thusfar. We now have flourishing projects like Magisk that are open source and doing well, despite its' issues (the ones I've had with it anyway). There is a lesser known root method called Phh's Superuser that is also open source, though not nearly as popular as Magisk or SuperSU. I think SuperSU would do well to open its' code and let the world contribute to it so that it can be further improved.
I wish @Chainfire the best of luck.
Click to expand...
Click to collapse
that's probably the exact opposite of what'll happen. you usually don't buy code to make it open source (Not that I do that, but I don't find the logic in it
As of now Magisk is way better unless you want simple su. I have no intentions on going back to crappy flashable zips for add-ons after using Magisk's module system.
Yeah, I'm sure some money changed hands between Chainfire and CCMT, it's just wishful thinking. I really don't care that much whether the code is open or closed, I'm sure CCMT will keep updating SuperSU even without Chainfire around. Whether Magisk is better is a matter of opinion, I've had numerous issues with it (which I do believe I already discussed with you in another thread). Every time I've used Magisk it has eventually caused problems. I'm a traditionalist, I only need a simple su, one that just works, SuperSU meets that need and has always worked well for me for the most part. Everywhere I read here on XDA, I see people pushing Magisk. I don't care about systemless, passing SafetyNet, hiding root, etc. To me it's all just superfluous extras, for me I'm happy with a reliable root solution that does *ONLY* that, and does it well.
AnonVendetta said:
Yeah, I'm sure some money changed hands between Chainfire and CCMT, it's just wishful thinking. I really don't care that much whether the code is open or closed, I'm sure CCMT will keep updating SuperSU even without Chainfire around. Whether Magisk is better is a matter of opinion, I've had numerous issues with it (which I do believe I already discussed with you in another thread). Every time I've used Magisk it has eventually caused problems. I'm a traditionalist, I only need a simple su, one that just works, SuperSU meets that need and has always worked well for me for the most part. Everywhere I read here on XDA, I see people pushing Magisk. I don't care about systemless, passing SafetyNet, hiding root, etc. To me it's all just superfluous extras, for me I'm happy with a reliable root solution that does *ONLY* that, and does it well.
Click to expand...
Click to collapse
Then maybe phh's superuser?
@Choose an username...: I still use Phh on several devices. But it doesn't work with Oreo on the A7, it can't patch the boot image in TWRP. Also tried with FlashFire. It worked fine on the A7 on Nougat.
Phh is the most reliable and fastest root solution I've tried. But it does have a few downsides. Like no automatic su.d script execution support (although you can set it to do so manually on a per script basis, via a simple command). I like that with SuperSU I can just drop my scripts in a su.d folder and they will be automatically ran at boot.
@phhusson has also stated that work on his project has halted and there will be no updates for the foreseeable future. He even goes as far as recommending Magisk for those that want a frequently updated open source solution. If I knew how to code then maybe I would consider picking up the torch and forking his project. I have beginner level coding experience in a few languages but I'm relatively green.
Another thing I've noticed is that with an Oreo ROM installed, I can't seem to flash certain zip files in TWRP. Like @YashdSaraf's BusyBox. Or other BusyBox zips. Also had trouble with some Viper zips not flashing. And a handful of others. They don't error out, they just hang and never finish flashing. I never had issues flashing zips on older Android versions. I've tried with @jcadduono's official TWRP, and @NFound's unofficial TWRP. I can only conclude that this is related to Oreo. As a workaround I use FlashFire with SuperSU v2.82 SR5, installed in SBIN mode. With this zips flash correctly. I have tested FlashFire with the latest Magisk versions. FlashFire claims to have been successful, but when I reboot back into Android my changes are nowhere to be found. It is as if Magisk deflects the changes away from the system partition and dumps them into a digital black hole. Magisk Manager works fine for flashing Magisk zips but not for others.
Just felt like I had to elaborate a bit more so you understand my reasoning for avoiding Magisk.
Related
Hello,
Is there a way to make SuperSU/SuperUser less slow? I mean, on a virgin rom it's already not so fast, but after you install your apps, it can takes minutes before the pop-up asking for root rights comes, if it comes..!! So is there a way to "fix" that? It's a pain, having to reboot sometimes cause of that!
Thanks.
goja said:
Hello,
Is there a way to make SuperSU/SuperUser less slow? I mean, on a virgin rom it's already not so fast, but after you install your apps, it can takes minutes before the pop-up asking for root rights comes, if it comes..!! So is there a way to "fix" that? It's a pain, having to reboot sometimes cause of that!
Thanks.
Click to expand...
Click to collapse
Set it to automatically grant permissions and turn notifications off, but remember that this is very insecure way so don't install any untrusted apps.
I've thought of that, but i'm not sure it would help : If it waits, let's say 2minutes, for showing pop-up asking for rights, then it would also wait 2minutes before automatically allowing apps...
2 minutes?? It should show immediately, so there is something wrong in your rom. Try to wipe cache and dalvik cache and fix permissions.
Man, this is not in MY ROM, this is in ANY roms... Seems that the more apps installed (=the more process running) the slower it'll be!
I agree. I have the same problem. I'm running CM13 (Marshmallow) on my old S3 i9300, and I flashed SuperSu (beta) for it. It work well, but its slow to grant permissions even when its meant to do so automatically. I've set it to start at boot, but this hasnt done much. Any fixes??
Same problem also here with every rom that I used it. Root in cm roms is almost instant.
same here on a custom cm12.1 rom
What the heck are you guys talking about? 2 minutes?! That is just plain wrong. I won't say impossible, cause you obviously have problems, but I have never seen that behavior you're talking about, and that is absolutely not caused by SuperSU or Superuser. Even my 7 years old HTC HD2 asks for, or grants root in 2 seconds max. Tell your developers to fix their ROMs.
Sent from my HTC One M9 using Tapatalk
Can it be that "Clean Master" or some other memory management software is pushing SuperSU back. Try uninstalling any memory management software.
never had issue having to wait for 2min either and ive rooted almost 50 diffrent phone from ics to lollipop to my current headache oppo mirror 5 still superSU still doing its job
I can confirm this is a real problem, but can also confirm it goes away with tweaking.
On aosp, it's important to disable the native su in dev options.
In anything else, for instance touch wiz, I have learned that system less root is evil, and mount separate name spaces is the devil.
Now, when installing prerooted rom, kernels etc, it's imperative to get your supersu set up prior to installing your root apps...or it will hit the fan....well..that's dramatic. It'll act oddly and you'll never realize what's causing things to be weird.
First and foremost, uncheck mount separate blah blah and reboot. Then, attempt to install supersu to system. If it fails after reboot, twice, then you must return the check mark to mount name spaces and reboot.
Once rebooted, try the "cleanup for reinstallation" and if that succeeds in allowing you to update/reinstall from play store, try to uncheck the mount name spaces again...then attempt the system install again...should work this time...
EDIT the point of all this is to test the app and the connection with the binary. If the app can't control the binary stuff, you'll probably be seeing lag. By doing all the options and checks that tweak the binary, you will have a good supersu environment, and the lag will disappear.
When you finally get supersu to do the things with its binary without crashing, you'll notice no more lag.
Further more, disabling notifications is an ABSOLUTE MUST. From @Chainfire himself, he suggests turning off notifications to get rid of overhead, and he states that logging does not effect it much, and after HUNDREDS of man hours tweaking and fiddling with supersu in every arena, from system less, to autoroot, I could not agree more.
Throw the man some love, respect, and donations, because he's at the front of the pack, hacking the infinite combinations of phones, to couriers, to software, to user intelligence.
His app is rock solid. The billions of other x factors are to blame
2nd edit mount name spaces will cause all sorts of odd things, so I disable that always, as well as notifications.
It's important to note, you'll always have delay for root requests in the first few minutes after boot, as certain things like scripts and even supersu itself might be denying for the first few minutes.
Enabling supersu at boot might help, actually it will help, but I've never needed it after configuring my root environment properly.
When everything fails, I Uninstaller root completely, and either reflash supersu, or my prerooted kernel of choice
3rd edit. Sigh, sorry. I notice my environment is in need of tweaking nearly 100% of the time when I flash a prerooted kernel, then a prerooted rom. Even flashing the kernel again, as is sometimes required for a rom not tailored for my device, will cause things to get out of wack which I notice instantly, when I got supersu lag
check if any other app stopping it.
I always update su binary, set the access to grant and delete su app.
Its d fastest way.
Read rules before posting questions on development forum¡*
Ur thread will b moved immediately.
BatDroid said:
check if any other app stopping it.
I always update su binary, set the access to grant and delete su app.
Its d fastest way.
Read rules before posting questions on development forum�?�¡*
Ur thread will b moved immediately.
Click to expand...
Click to collapse
â?¦
I don't even know how to process this ?¦ try my way first¦
I'd bet anything the speed will be just as fast¦ and i forgot to mention, i always enable full logging? so full logging, no lag?vs no nothing, no app, security etc
loogielv said:
I can confirm this is a real problem, but can also confirm it goes away with tweaking.
On aosp, it's important to disable the native su in dev options.
In anything else, for instance touch wiz, I have learned that system less root is evil, and mount separate name spaces is the devil.
Now, when installing prerooted rom, kernels etc, it's imperative to get your supersu set up prior to installing your root apps...or it will hit the fan....well..that's dramatic. It'll act oddly and you'll never realize what's causing things to be weird.
First and foremost, uncheck mount separate blah blah and reboot. Then, attempt to install supersu to system. If it fails after reboot, twice, then you must return the check mark to mount name spaces and reboot.
Once rebooted, try the "cleanup for reinstallation" and if that succeeds in allowing you to update/reinstall from play store, try to uncheck the mount name spaces again...then attempt the system install again...should work this time...
EDIT the point of all this is to test the app and the connection with the binary. If the app can't control the binary stuff, you'll probably be seeing lag. By doing all the options and checks that tweak the binary, you will have a good supersu environment, and the lag will disappear.
When you finally get supersu to do the things with its binary without crashing, you'll notice no more lag.
Further more, disabling notifications is an ABSOLUTE MUST. From @Chainfire himself, he suggests turning off notifications to get rid of overhead, and he states that logging does not effect it much, and after HUNDREDS of man hours tweaking and fiddling with supersu in every arena, from system less, to autoroot, I could not agree more.
Throw the man some love, respect, and donations, because he's at the front of the pack, hacking the infinite combinations of phones, to couriers, to software, to user intelligence.
His app is rock solid. The billions of other x factors are to blame
2nd edit mount name spaces will cause all sorts of odd things, so I disable that always, as well as notifications.
It's important to note, you'll always have delay for root requests in the first few minutes after boot, as certain things like scripts and even supersu itself might be denying for the first few minutes.
Enabling supersu at boot might help, actually it will help, but I've never needed it after configuring my root environment properly.
When everything fails, I Uninstaller root completely, and either reflash supersu, or my prerooted kernel of choice
3rd edit. Sigh, sorry. I notice my environment is in need of tweaking nearly 100% of the time when I flash a prerooted kernel, then a prerooted rom. Even flashing the kernel again, as is sometimes required for a rom not tailored for my device, will cause things to get out of wack which I notice instantly, when I got supersu lag
Click to expand...
Click to collapse
As he said i have dissabled notifications and worked, Thanks Man
I've had this problem on a Samsung Galaxy J7 (2016). It was because I disabled the encryption of /data. For details on how to solve it see here. I think there are probably other factors that can cause this, so this solution is probably not for everyone. But I would recommend checking your adb logcat to figure out if something is going on in the background that should not.
Since I installed SuperSu 2.79 on my klte on RR (los, android 7.1.1) the device started lagging, not a lot but enough to be annoying.
I decided that I needed a fresh start with my LG v30+ after over a year on Oreo, and figured I would go ahead and wipe everything and install rooted stock pie per this thread (using the TWRP flashable method).
From there, I went ahead and installed the Magisk Modules for Busybox, Riru - Core, and Riru -EdXposed, because I wanted to have a few Xposed modules. I started out with XPrivacyLUA, and GravityBox [P], making TWRP Backups and checking SafetyNet status after each install. Because it kept passing every time, I got complacent, and stopped checking. I installed Buttered Toast Revived, GM Dark Theme Enabler, and MinMInGuard in EdXposed, followed by several apps. I then installed the 4.4.153_haumea_I.base_1.9_3 kernel, and a bunch of more apps.
It was around this time I decided that I should try and set up Google Pay, only for it to complain about the device it was installed on. I went back to Magisk Manager and sure enough I was failing SafetyNet checks on both ctsProfile and basicIntegrity. And because I wasn't checking every step of the way, I don't know what caused it to break. I've tried unloading the various modules but none of them seem to be a smoking gun, as both check continue to fail even when some or all of them are turned off.. It's not the custom kernel is it? and if so, what do I do to to roll back to stock?
I also looked into the Magisk Module, MagiskHide Props Config but the developer of that says it doesn't have much chance of fixing basicIntegrity fails. Also, they don't have a device fingerprint in their database for v30+ Pie yet. So when I have some free time to dedicate to phone tinkering, I'm going to back up what I have now, revert to an earlier backup from before things broke, pull a getprop ro.build.fingerprint, and then restore my backup of the current broken state so I can give it a try anyway. Because I'm stubborn like that.
That is, unless I get easier suggestions to try first. Passing SafetyNet would be a nice to have thing, but I wasn't passing before I did my wipe, and so I won't really miss it if I'm not passing now either.
Try looking through here: https://github.com/ElderDrivers/EdXposed/issues/386
Seems a recent SafetyNet update is halfassedly checking for the edXposed Magisk module and workarounds are hit-and-miss, with no word from the dev(s) if they're working on it or intend to.
Septfox said:
Try looking through here: https://github.com/ElderDrivers/EdXposed/issues/386
Seems a recent SafetyNet update is halfassedly checking for the edXposed Magisk module and workarounds are hit-and-miss, with no word from the dev(s) if they're working on it or intend to.
Click to expand...
Click to collapse
This was it. Blacklisting Google Play, Google Play Services, and Google Services Framework in EdExposed (the suggested workaround) seems to be working for now.
And if anyone's curious, the device fingerprint on my US998 30b is
Code:
lge/joan_nao_us/joan:9/PKQ1.190414.001/192451445de41:user/release-keys
Not that that's changed at any point in my installation process, according to the backups that I've checked. So MagiskHide Props Config wouldn't have been any use, because that wasn't the problem in the first place.
radwolf76 said:
Code:
lge/joan_nao_us/joan:9/PKQ1.190414.001/192451445de41:user/release-keys
Not that that's changed at any point in my installation process, according to the backups that I've checked. So MagiskHide Props Config wouldn't have been any use, because that wasn't the problem in the first place.
Click to expand...
Click to collapse
Well I mean...the device fingerprint is only a contributer to the long list of crap that'll trip Safetynet; Google really, really doesn't want non-compliant devices to use Safetynet apps. The scans have become quite invasive.
All the official ROMs should have compliant fingerprints, anyway.
Thing is...I didn't mean "halfassedly" in a offhand or facetious way; they probably have implemented a check, in an experimental and thus inconsistent way, that only catches the module often enough to be annoying. Or the way they're checking might depend on other things in the environment (looking for signs of its presence rather than the module itself), which would explain why the workaround works on some phones and not others. Try to keep track of any root- or Magisk-requiring changes you make.
I couldn't get a pass when I tried a few days ago, and ultimately couldn't figure out why despite doing the usual stuff and the workaround above. Decided Ingress and PokeGO were more important than GravityBox, which I've done without for years anyway :v
Enjoy being able to pass the checks, but be prepared for it to break at any moment. Google has been annoyingly persistent about patching workarounds, and the workarounds for the patches to workarounds, and so on.
I've had the same problem, although blacklisting Google play, Google services framework, and Google play services didn't help.
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!
Hello I would appreciate some help fixing an issue.
Please excuse my lack of knowlage, I will try to give adequate info. If more info is needed let me know.
I have a Oneplus Nord N10 5G "unlocked" (I believe that means global) Build# BE86AA Model# BE2026 Android ver. 11
The phone has been rooted since October 13-20
I cannot recall the tutorial I followed to root. I do have TWRP and Magisk on the phone. With Magisk 23.0 I passed SafetyNet (I used the built in SafetyNet Checker Via Magisk)
A few days go (Feb/18/22) I updated Magisk(24.1)/App(24.1) Via the Magisk app. I no longer pass SafetyNet (I used Root and SafetyNet Checker from "BetterOpts")
Magisk 24.1 no longer has Magiskhide
Now I cannot play Niantic's game called Ingress.
A message pops up saying "Ingress is not supported on this device configuration"
I had no issue when I had Magisk 23.0 (using magiskhide)
I googled that message and found that Niantic searches for root/rooting apps.
I have messed around with "Magiskhide props config v6.1.2" changing device fingerprint, force basic attestation.
Nothing seemed to help so i Reset all options/settings
I have read many horror stories of people hard bricking or causing more damage by trying to revert/unrooting back to stock.
I think i did a dumb and did not backup anything from Pre-root.
I saw a few posts on reddit/gaming.stackexchange people saying outdated SupperSU caused them to get the message.
I do not have SupperSU.
Another person they deleted a folder called "MAGISKMANAGER" and that solved the message.(this post was back in 2019)
I'm not sure if they unrooted and thats why they deleted the folder.
I couldn't find a folder with that name.
A lot of posts I found all say "Use Magiskhide"
But Magiskhide has been removed from Magisk24.0+
I did a search (using files app) and found Magisk.apk(s)
Magisk_patched
and Magisk-23.0.zip
I'm not sure if should delete these. Not sure if deleting (or moving files to computer) would cause problems on the phone at next reboot.
I am no rooting expert so again please excuse my ignorance. again if more info is needed please let me know and i will answer to my best ability.
Do you recommend a Hide Root App/Mod?
Should I install Xposed Framework via Magisk?
Thank you for your time and advice
Edit:
I am very stupid. I found kdrag0n safetynet-fix from Github.
Downloaded the latest release (2.2.1)
Installed Via Magisk app
Rebooted
Ingress works
I'm thinking of leaving this post up. It might help someone?
If you still need to upgrade to Magisk 24.1 then study at least the start of this thread. Maybe not for now but in the future.
Magisk 23 and lower will not be supported any longer.
Wonderful new week for you !
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
xabu said:
If you still need to upgrade to Magisk 24.1 then study at least the start of this thread. Maybe not for now but in the future.
Magisk 23 and lower will not be supported any longer.
Wonderful new week for you !
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Click to expand...
Click to collapse
I saw that thread right after i made my post.I thought about deleting the post. I'm sure there will be other people who will update without reading beyond "New update" and hopefully this will find them and steer them toward getting their device up and running.
For anyone curious.
Go into magisk settings, use the option to change magisks package name.
Then enable Zygote mode.
Reboot your phone.
Go back into your now renamed magisk app (mine is usually named system because who the hell looks at an app named system and think "this is the malicious code, I know it!")
Open your magisk app, go back into the settings and look for the option that says deny, click it and look for the app you're gonna hide from magisk.
If you're looking to use something like Pokemon go, click it twice so that way Zygote rejects both checks.
Now go be a pokemon master
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.