did you select to reveal system apps and also hide the google play services and related stuff?New to the safetynet stuff and hiding magisk but i have followed the instructions and when i do a safteynet check it says i pass but google pay is still non-functional it states it is "unable to load your payment info" does anyone have any ideas? i am on the January update with the canary magisk and p6pro
I didn't need a particular version. Set up the fingerprint with the Chase app while running the stock, unrooted kernel (boot.img). Then put the custom and/or rooted kernel back on the phone and it'll keep working as long as you're following all the steps in the OP as well.
What is kernel that your using and how do you like it?I didn't need a particular version. Set up the fingerprint with the Chase app while running the stock, unrooted kernel (boot.img). Then put the custom and/or rooted kernel back on the phone and it'll keep working as long as you're following all the steps in the OP as well.
I already had the Chase app working (without fingerprint) before updating to the January update via the full factory image (without wiping), so while I was flashing, I boot the phone once fully stock (I do that anyway, just to make sure there's no problem yet), set the fingerprint reader up in the Chase app, then I flashed the newly Magisk'd boot.img from the January update.
Once my custom kernel of choice was updated for January, I flashed it as well. Everything still works.
That's not really the subject of this thread. I like it quite well but I tend to not experiment much - I try something and I like it so I stick with it unless there's some really strong reason to try something else, so I've only flashed a couple. I hope you understand, I'm not going to make comparisons between them. There are four very fine choices here and I don't think you'll go wrong with any of them. If you have any trouble finding them, click on the Development Quick Filter up above the list of threads in this section and Control-F and type kernel, and you'll easily see the ones that are available.
Perhaps you should post this in the OnePlus 7T Pro thread given this is a Pixel 6 Pro thread for how to pass SafetyNet? There are also several existing guides on how to root, unroot and update via OTA (when rooted) for the Pixel 6 Pro and there are some differences to that of the OnePlus 7T Pro. For example, when updating to the April build via "Install to Inactive Slot" method, Canary Magisk 24306 is required. This is a Pixel 6 series distinction. You also mention TWRP and there isn't a TWRP for the Pixel 6 series. Just a couple of examples.While learning about my new OnePlus 7T Pro and spending countless hours to root it, I created a GitHub repo showing how to root, unroot, and update OTA (when rooted):
Maybe it can help someone else
You re-enabled the relevant Magisk Modules (if you disabled them before updating)? Try rebooting again?
Probably just @Pekempy's personal choice. You *can* use and do those things. I choose not to.
I would chalk it up to coincidence, nothing more, but who knows.
Down grade to beta from canary, patch root, upgrade to canary patch root. This worked for me
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot boot magisk_patched-230xx_xxxxx.img
fastboot flash boot magisk_patched-230xx_xxxxx.img
fastboot --disable-verity --disable-verification update image-raven-xxxxxxxxxxxx.zip --skip-reboot
fastboot reboot-bootloader ping -n 5 127.0.0.1 >nul fastboot flash boot --slot=all magisk_patched-23xxx_xxxxx.img fastboot reboot
The below was emailed to me by KLWP developers after I raised I couldn't install it. It's worked for me for getting apps like Netflix to show.
"This may have something to do with the new copy protection Google introduced with the new signing method. This happens if the Play Store falsely detects that something was tampered with on the device. To get around this, you can try to clear Google Play Store's app data."
Use an older version of that app (version 4.234) to get the fingerprint setup and working.
1. Remove your current Chase bank app.
2. Install the older version mentioned.
3. Add it to the magisk deny list.
4. Setup your fingerprint.
Once you've done that, you can update the app in the Play Store to the latest version and the fingerprint will still work
I was following these:
Note the writing "If you flash the images in bootloader, you will have to wipe." This has been my experience as well.
Maybe here? Haven't tried yet. http://www.oldversion.com/android/com-chase-sig-android/
There's also https://apkeureka.com/apk/com.chase.sig.android/
Found using this search: https://www.google.com/search?q=chase+bank+apk+old+version&sxsrf=AOaemvLfTz7WOH6Um3eIfpWRliMBVMz2Kw:1637594539550&ei=q7WbYczzIJWPtAbtxKmYBg&ved=0ahUKEwiM9cKGo6z0AhWVB80KHW1iCmMQ4dUDCA4&uact=5&oq=chase+bank+apk+old+version&gs_lcp=Cgdnd3Mtd2l6EAMyCAghEBYQHRAeOgcIABBHELADOg0ILhDHARCjAhCwAxBDOgcIABCwAxBDOgUIABCABDoICAAQFhAKEB46BggAEBYQHkoECEEYAFDaCFinEmDZE2gBcAJ4AIABuwGIAc4KkgEDNi42mAEAoAEByAEKwAEB&sclient=gws-wiz
I kinda hate to download banking apps from random websites, however.
The newest version (still older than what I had from the Play Store) on the second site, chase-mobile_v4.252_apkeureka.com - 20211007 fingerprint still wouldn't enable.
The oldest version on the second site, chase-mobile_v4.171_apkeureka.com - 20201211 wouldn't let me sign in without updating.
I'll try one somewhere in the middle. Trial and error is a pain, though. Install, deny in Magisk, log in, 2FA, Settings, Fingerprint, denied. Wipe Cache and Storage, uninstall, repeat.
chase-mobile_v4.220_apkeureka.com - 20200702 - wouldn't let me sign in without update
chase-mobile_v4.231_apkeureka.com - 20200805 - wouldn't let me sign in without update
chase-mobile_v4.234_apkeureka.com - 20200817 - wouldn't let me sign in without update
And that's all she wrote for now. 10/07 is the only one on the site newer than 8/17, 8/17 requires update before trying to sign in, and 10/07 still has the problem where I couldn't enable fingerprints. I don't have the Chase app still installed on some previous rooted phone (with an old version) to restore app data from.
By the way, I notice all these APKs are much bigger than what the Play Store reports is the current app's size, but maybe there's a technical reason for that. I hope.
Thanks for posting. Last night I had the forked Alpha version of Magisk installed with RIRU and the public release of USNF 2.1. Passed Safetynet and everyting was working well, but decided I'd feel better using the latest non-forked Zygisk compatible Magisk 23011No worries, we're all adults here trying to keep up with Google's changes after all
With USNF, DenyList doesn't need to be enabled for Play Services. This prevents any breaking of Play Services. What I did was:
- Latest Magisk Canary
- Enabled Zygisk but keep DenyList turned off
- Flash the USNF module
- Reboot system and verify if Zygisk is shown as "Yes" in Magisk Manager
- Enable DenyList and select my bank apps
- Hid Magisk Manager by repacking it with a different name
Tested for SN and it passed. Netflix works. Banking apps mostly work with the exception of one which is worked-around by temporarily uninstalling only Magisk Manager. After I'm done with that bank app, a reboot brings back Magisk Manager.
Unfortunately, since I'm traveling, GPay isn't available here so I can't test it but it should work just fine. If you've a specific app you want me to test, link it and I'll post a screenshot.
I'll update my guides in a bit, but just for you...this will be the Cliff Notes version, so if you need more detailed instructions, you'll have to wait a bit...@Anonshe or @V0latyle, you guys are doing a great job so far! I appreciate your dedication!
I have my P6P sitting in its box for now, only unlocked the bootloader. Would any of you be so kind to write an idiot-proof guide to permanently root the P6P? I feel like information is all over the place in the P6P section...
fastboot flash unlock
flash vbmeta --disable-verity --disable-verificaiton --slot=all vbmeta.img
fastboot flash boot magisk_patched-23xxx_xxxxx.img