yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4 XL Guides, News, & Discussion] bradical711:
@madmuthertrucker

Link To Universal Safetynet Fix Thread

You need the "universal safetynet fix" magisk module. XDA thread link is posted above, actual download is hosted on GitHub.

In order to install the "universal safetynet fix" module in magisk though, you'll also need to install the "riru" module. You can find the "riru" module in magisk's repo by searching for "riru". Finally, you'll need to enable magisk hide for Google Play Services, specifically only "com.google.android.gms" & "com.google.android.gms.unstable" need to be ticked. Afterwards, reboot and you should be passing safetynet. Once you're passing safetynet again, don't forget to clear the data for Google Play Store as well and reboot a 2nd time. That'll make sure the Google Play Store certifies your device as "official" in the Play Store after you start passing safetynet again. Optionally, hiding the magaisk manager itself isn't necessary in passing safetynet, but can help you with accessing mobile versions of banking apps, (gpay) etc.
[Google Pixel 4 XL Guides, News, & Discussion] madmuthertrucker:
I followed your instructions to the letter and it worked just fine! No problems. It was almost to easy. I have been over complicating it. I'm following Safetynet Fix thread now. Thanks for the help.
[Google Pixel 4 XL Guides, News, & Discussion] madmuthertrucker:
I'm passing Safetynet and device is certified. But GPay is still fighting me. Did any of you guys get it working?
[Google Pixel 4 XL Guides, News, & Discussion] bradical711:
I can access gpay just fine on A12. I have it installed and just checked myself. I'm passing safety net myself and have the magisk app hidden (renamed). What do you mean by gpay fighting you.? Does it happen when making a purchase or just opening the app on A12.? I had gpay on A11 and it worked fine for me when I used it. Upgraded to 12 via OTA, no change in my setup and I can access it still. I haven't tried to make a purchase with it yet though.
[Google Pixel 4 XL Guides, News, & Discussion] madmuthertrucker:
I did a clean install from A11 to 12. I can sign into GPay but I can't add payment card. If I open wallet it says "Unable to load your payment info". The first time it said this may be because your device is rooted. I selected GPay in MagiskHide. I also renamed Magisk. I cleared cache and storage but I still can't add payment cards. That has always been my test, after clearing storage usually it asks me to re add payment cards. I cleared storage force stop and this is what pops up.

Google Pay can't be used on

this device

Sorry, your device isn't passing Google Pay's security checks. This may be because your device is rooted, or is running an uncertified or custom 0S build.

As a result, Google can't confirm that your device meets Google Pay's security standards.
[Google Pixel 4 XL Guides, News, & Discussion] bradical711:
Interesting... If I go to gpay and open wallet I get no error message. I also tried adding another card and was able to do so with no issue either.... I've never had to add gpay to magisk hide so I know that's not it. You said you were passing safetynet as well as Play Store Certified along with magisk hidden so my last guess would be to ask if you have any variant of Xposed installed (Edxposed or LSposed). I think having Edxposed would trigger gpay since it hooks all apps unless you have specifically excluded gpay itself in Edxposed 'blacklist'. I'm not sure what else it could be though cause you pass all the other checks for gpay. Maybe and I mean maybe, it could be a TWRP folder/leftover magisk files in /sdcard/ ... No idea otherwise if none of those are it though.
[Google Pixel 4 XL Guides, News, & Discussion] madmuthertrucker:
Well now I checked & I'm failing Safetynet. I'm still Play certified. I'm running LSPosed, XPrivacyLua. Just like in the guide. I don't get why I originally passed SafetyNet and now I don't. I'm going to start over with a clean install I guess. I'm running Canary. I'm at a loss.
[Google Pixel 4 XL Guides, News, & Discussion] bradical711:
Hmmm, I double checked my safetynet and I'm still passing with the same setup. I double checked with 'root checker' app and magisk alike. I'm running stable version 23 of magisk along with 9 modules. None of which include the Xposed variants. Maybe try again with the clean install but don't install LSposed/xprivacylua. First work on passing safetynet again with just those 2 modules you need, and then we can go through the process of elimination.
[Google Pixel 4 XL Guides, News, & Discussion] madmuthertrucker:
That's a good idea. I was passing Safetynet with just Riru & Safetynet Fix. Okay I'm going to try it.
[Google Pixel 4 XL Guides, News, & Discussion] madmuthertrucker:
Okay just for giggles I uninstalled LSPosed, XPrivacyLua and I'm passing Safetynet again now. Still not able to add payment to GPay. So you were right about that module being the culprit.
[Google Pixel 4 XL Guides, News, & Discussion] bradical711:
Awesome! I was gonna say it has to be the Xposed variant but didn't wanna call it out without any confirmation first. Now in terms of not being able to add a payment method still, now I'd try clearing the data of gpay again, rebooting, and trying to add a payment method again. I think that should clear up the issue and if not, maybe a complete uninstall/reinstall of gpay if clearing the data and rebooting didn't work.
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
Anyone, who has a rooted Android 12 Pixel 4XL that has

Google Pay working

. Please, share the instructions. I'll update the OP and list you in the Credits for sharing the solution.
[Google Pixel 4 XL Guides, News, & Discussion] bradical711:
You don't need anything special to get gpay working. I'm on A12 Pixel 4XL currently using gpay with no issue. You simply need to pass safetynet and NOT have ANY Xposed variant installed. As far as I'm aware and confirmed yesterday with @madmuthertrucker, Xposed WILL trip gpay. I'll repost my instructions that I posted yesterday to pass safetynet as that's all that's required to use gpay.
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
Thanks! :)

Pass Safety Net - Updated
[Google Pixel 4 XL Guides, News, & Discussion] madmuthertrucker:
This worked for me. I completely uninstalled GPay. Then reinstalled it. Oddly it didn't work right away. At first I couldn't add a card. But then the next day I opened it and it was asking for a payment card. I tried using it and it's working. Thanks for getting us all sorted out here.
[Google Pixel 4 XL Guides, News, & Discussion] bradical711:
My pleasure, I'm glad you got everything sorted out and working again! I'm happy I could be of help! Enjoy your device and have a great rest of your weekend!
[Google Pixel 4 XL Guides, News, & Discussion] CCTV_11:
not sure what error i got. but missing MagiskHide option in settings
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
That is the new Magisk Canary <beta> 23010. Check this thread for changes and search this thread for information on its use.
[Google Pixel 4 XL Guides, News, & Discussion] madmuthertrucker:
I didn't take the Magisk update. I'm a little confused about it. I wonder if we can hide root from GPay and banking apps.
[Google Pixel 4 XL Guides, News, & Discussion] bradical711:
I'm assuming you mean the canary update for magisk that just popped a few days ago.? If so, long story short is that there's gonna be a lot of semi-big changes with magisk. The first is the removal of "magiskhide" and the introduction of "zygisk". From my understanding thus far, "zygisk" is an alternative to "riru" built natively into magisk ('riru' being the backbone of Xposed). Now from what else I've read on is that installing the new magisk canary breaks the "riru" module because both "zygisk" and "riru" 'fight' each other trying to do the same thing. And because "zygisk" is still in testing, a lot of Xposed modules don't actually run natively on zygisk just yet... Or not perfectly anyway. Now the last major change for the canary was the removal of "magiskhide". In replace of "magiskhide" however, Magisk now has a "deny list". Essentially the "deny list" reverts all changes that magisk and "zygisk" have done to your system back to stock for whatever processes/apps you want. The ONLY similarity is how you would select the processes/apps for "magiskhide" and the "deny list". But again, "Deny list" is NOT the same thing as "magiskhide" and is NOT the "magiskhide" future replacement. That basically sums up my current knowledge of the situation. If you're looking for advice on wether or not to take the update, I'd avoid it unless you want to mess around with your setup again. Most things aren't working as expected with zygisk/deny list etc etc.
[Google Pixel 4 XL Guides, News, & Discussion] madmuthertrucker:
Yes the canary update. I switched to stable. I didn't want to mess with my setup, I just got it going. You have a better understanding of this than I did. I will just wait & hope that somebody comes up with solutions.
[Google Pixel 4 XL Guides, News, & Discussion] flyoffacliff:
Which Magisk build? The latest Stable without MagiskHide?

Is there a specific build that supports both Android 12 and MagiskHide?

Or is it no longer needed?

Thanks
[Google Pixel 4 XL Guides, News, & Discussion] bradical711:
Magisk canary (23010), the latest experimental/bleeding edge version. And current stable magisk (23000) supports A12 already and has magiskhide. Magiskhide is only removed in the canary version (23010) and in the future stable versions going forward. Some form of magiskhide is needed if you want to pass safety net, use banking apps etc. Otherwise completely unnecessary if you don't care and/or circumstances don't fit you. The only other thing that may apply is that I think the current stable magisk (23000) doesn't support pixel 5 on A12 as that phone uses a newer boot image format for A12 that is currently only supported on the new canary version of magisk (23010). In that case, you'd have to use canary to root the pixel 5 on A12.
[Google Pixel 4 XL Guides, News, & Discussion] 73sydney:
Got my 4 XL yesterday

fwiw, im still using vvb2060's Alpha 31, same as i have been for my Pixel 2XL

You dont have to use any current version of magisk...theres currently the "official" and 2 forks going (on Telegram and referred to here in the Magisk threads) and with each release theyre up and down. I dont test every build of these 3 builds these days, dont have the time, but i keep involved and test where i can.

For certainty i use the older alpha 31 (attached), you can use MagiskHide as always

Apha 31 and Universal SafetyNet Fix 2.1.1 are all thats needed to pass SafetyNet, i just use Riru and Riru-Momohider for my banking app...Riru-Momohider (i have my own mod of the installer (also attached) that sets all config switches here (dont use this with the newer magisks) automatically instead of manually - i got tired of doing it manually as a frequent ROM tester on my Pixel 2XL) NOTE: The Riru-MomoHider mod is only recommended for old Magisk and Magisk Alpha to 31...beyond this it may result in failures/worse as not all the 4 switches are supported on later Magisk or Magisk Alpha at this time (or perhaps ever)
[Google Pixel 4 XL Guides, News, & Discussion] mochamoo:
I purchased my phone direct from Google but am using it on Verizon. I see that there iare separate versions. One specifically for Verizon. I'm suspicious of that one... Is there any reason that I *have* to use the VZ one for A12?
[Google Pixel 4 XL Guides, News, & Discussion] madmuthertrucker:
I'm in the same boat as you. What version did you buy? Did you buy the VZ one? If not then no don't use it.
[Google Pixel 4 XL Guides, News, & Discussion] mochamoo:
It is the Google version and have been flashing the generic versions all along. VZ tends to cripple things like esim functionality.
[Google Pixel 4 XL Guides, News, & Discussion] madmuthertrucker:
I would be afraid to install the VZ version. It's probably full of bloatware. I worry that it might lock my bootloader. I'm running A12 non VZ version on their network.
[Google Pixel 4 XL Guides, News, & Discussion] mochamoo:
All went well without wiping. Was prepared to if I had to. Note: face unlock doesn't work if you have camera access blocked. :)
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
Magisk Canary 23001: Click 3 dot Menu => Click app-debug.apk => Click 3 dot Menu above View raw => Click download
[Google Pixel 4 XL Guides, News, & Discussion] docluv01:
Hi Team, so I updated my 4 xl to android 12, installed the latest alpha Magisk, patched the boot.img. Flashed the patched boot.img, and when I boot the phone, the touchscreen is non responsive. :( not sure hot to resolve
[Google Pixel 4 XL Guides, News, & Discussion] madmuthertrucker:
Did you do a clean install?
[Google Pixel 4 XL Guides, News, & Discussion] docluv01:
Yes, I did. had to flash back stock boot.img to be able to use phone
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
@docluv01 did you use Magisk Canary 23001 to patch the boot image?
[Google Pixel 4 XL Guides, News, & Discussion] docluv01:
Hi, yes I tried 23001, 23012, and the latest alpha. Same thing in all instances. Had to reflash stock boot.img every time.
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
@docluv01Try this also are you using SafetyNet Fix 211.

If that doesn't fix it, It might be a hardware problem.
[Google Pixel 4 XL Guides, News, & Discussion] docluv01:
Thanks, I don't believe this to be the issue. with stock boot.img everything works fine. Its only when I flash a patched magisk boot.img.
[Google Pixel 4 XL Guides, News, & Discussion] bradical711:
What device do you have.? (EDIT NVM, I seen it's a 4 XL). Anyways since your device isn't a pixel 5a 5g or newer, you don't need alpha/canary magisk to root A12. I'm using the 4 XL rn with stable magisk (23000) on A12 November security patch. Try stable magisk since you're not on a pixel 5a or newer and report back. I also did an OTA from A11 to 12 without any issue. Same modules for me etc so it might be a magisk canary/alpha issue.
[Google Pixel 4 XL Guides, News, & Discussion] docluv01:
Thanks, I just tried it, and same thing. touchscreen is not responsive.

Looks Like im the only one with this problem :(
[Google Pixel 4 XL Guides, News, & Discussion] docluv01:
OK UPDATE: I simply redid android 12 (removed -w) and repplied the patched boot.img, and seems it took now. WHEW!!! Thanks!
[Google Pixel 4 XL Guides, News, & Discussion] loonix:
I am still on September update and looking to upgrade to Android 12 via a clean install. What are some good ways to do a backup of the apps+data+settings that folks are following? I am trying to avoid anything using the cloud/paid softwares. Had used Titanium Backup when I went from Android 10 to Android 11, so that is one option but looking for some other recommendations.

Thanks.
[Google Pixel 4 XL Guides, News, & Discussion] 73sydney:
Migrate - its in my signature for a reason.

Its free, it works

Here is how i use it, its worked out to be the easiest way for me, across probably 100 ROM flashes by now, from 9 to 10 to 11 to 12 :) It will warn you it hasnt been tested on 12 when you go to restore, but it works 100% fine

https://xdaforums.com/t/app-root-5-...stom-rom-migration-tool.3862763/post-85862285

Note: please never mention that awful piece of crud Titanium Backup ever again in my presence :)
[Google Pixel 4 XL Guides, News, & Discussion] loonix:
I am glad I asked for current recommendations ! Thanks for the suggestion. I am going to follow your guide but just posting it here in case others also find the big thread linked in your signature a little daunting.

https://xdaforums.com/t/keeping-watch-connection-and-samsung-pay-across-roms.4274429/

I think for us in P4XL, since we don't have TWRP we will need all the three apps -> Main, Flasher and Helper.
[Google Pixel 4 XL Guides, News, & Discussion] smithilberry:
FYI, I have my Pixel 4 XL (Google Store/Unlocked version) on Nov 2021 patch without any issues

(using Magisk 23.0, passing SafteyNet, & GPay working)

All I did is the "regular method" of updating, which I define as...

1. download factory image and remove -w from flash-all

2. extract boot img from zip

3. move boot img to phone and patch with magisk manager (Magisk 23.0)

4. move magisk boot img to PC

5. flash update Code: flash-all

6. flash magisk Code: fastboot flash boot magisk_patched.img

7. reboot and enjoy

Oh, and modules I have installed for Magisk are:

Busbox 1.34.1

Riru v26.1.3

Universal SafetyNet Fix 2.1.1
[Google Pixel 4 XL Guides, News, & Discussion] loonix:
I have been doing the exact same steps until September update. From October I think it is now Android 12 and I just want to do a clean install(without removing -w). If you updated in October then this is exactly what I would follow too.
[Google Pixel 4 XL Guides, News, & Discussion] loonix:
Update: I have P6 Pro coming soon so decided to go skip clean upgrade to Android 12 as I didn't want to go through too much trouble in case it arises. I did backup via the Migrate app just in case however (flash method selected during backup, not TWRP)

Ended up dirty flashing from September Android 11 update to November Android 12 upgrade. Everything appears to be running fine after an hour of use.

Also forgot to mention that while I do follow the same steps as @smithilberry , I always have added a reboot between step 5 and 6. In the past I had a bootloop one time when not doing this step and it forever changed my update method.

Essentially

1. download factory image and remove -w from flash-all

2. extract boot img from zip

3. move boot img to phone and patch with magisk manager (Magisk 23.0)

4. move magisk boot img to PC

5. flash update Code: flash-all

6. REBOOT -> Let the system update finish after you are logged in one time without root.

7. flash magisk Code(Reboot to bootloader first after 6 completes) : fastboot flash boot magisk_patched.img

8. reboot and enjoy
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
One, there is a Google Pixel 6 Pro | XDA forum that could benefit from your Pixel 6 Pro experiences.

Two, that factory image flashing procedure is in the OP, #4 'keep data' :)
[Google Pixel 4 XL Guides, News, & Discussion] loonix:
I understand :) Just wanted to give a datapoint where a dirty upgrade also has gone through fine (after making sure backups are in place just in case). I am very much a proponent of clean major version upgrades in the past. Your sticky has been the backbone for last couple of years of upgrades and I am very thankful. Sorry if that is not stated explicitly. It is implied, just not stated verbose.

Looking forward to retiring P4XL and hopping on the P6 Pro forum soon.
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
Must reads:

Post in thread '[KERNEL] CleanSlate R2.7.13/S3.7.13 |S2S|Gamma|KCal|AdBlock|VIB|WrGrd [Nov 6]' https://xdaforums.com/t/kernel-clea...adblock-vib-wrgrd-nov-6.4027435/post-85973909
[Google Pixel 4 XL Guides, News, & Discussion] loonix:
For those on latest Canary 23014 (Zygisk with GPay added to deny list),to pass safetynet and enable contactless payments

1) Clear data for both GPay and Google Play Services. Unfortunately this also meant adding cards back in GPay app (basically reverify already added cards in your GPay profile)

2) Apply SafetyNet fix 2.2.0 (latest).

On the bright side no longer need Riru, Riru core, LSPosed etc. etc. Just SNF 2.2.0 + Systemless hosts like old times.
[Google Pixel 4 XL Guides, News, & Discussion] crypt0kiddie:
For the love of God Android 12 was painful.

I tried, I really tried. I kept having Windows Millennium Edition flashbacks the user experience was SO BAD!

Waiting for my phone to boot back into Windows 98 SE, er I mean Android 11 now.
[Google Pixel 4 XL Guides, News, & Discussion] kb5rir:
Worked Perfect Thanks soooo Much
[Google Pixel 4 XL Guides, News, & Discussion] madmuthertrucker:
Well I just re rooted the update with Magisk 23.0, Riru, and USNF 2.1.1. I figured it's not broke maybe I shouldn't fix it. It won't work forever, I suppose, I will have to get Zygist and join the future. Next time.
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
Suggestion: Update USNF to 2.1.2 Magisk Hide will still work.
[Google Pixel 4 XL Guides, News, & Discussion] Op1_2:
error: cannot open 'magisk_patched-23016_XmpRD.img'. Any idea why i keep getting this error? nevermind i figured it out.
[Google Pixel 4 XL Guides, News, & Discussion] Op1_2:
awesome guide thanks
[Google Pixel 4 XL Guides, News, & Discussion] Douak:
Thanks.

Works for me with Magisk 23 🙂
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
:) I hope you all have a Joyful Holiday season with your family and loves ones. :)

~ ~ ~ Stay safe ~ ~ ~​
[Google Pixel 4 XL Guides, News, & Discussion] dogeen:
First "oh no did I brick my device?" post of the year!

I was on Android 11 with an unlocked bootloader, magisk root on the stock rom, and tried doing a clean install, without the "Magisk Restore Images" step, because Magisk hadn't backed them up, and found myself with a device that doesn't have WIFI or mobile. Luckily, I had a backup of my persist.img, but my phone doesn't appear to like that persist.img anymore.

Note: I had modified my modemst1 because my device is from US and the Turkish government wanted me to pay ~$300 to not block it, so I changed my IMEI for the Turkish line to the IMEI of an old phone that belonged to a relative, and kept my US line with the original IMEI.

Here is what I tried:

- Right when Android 12 booted for the first time, mobile was gone, but WIFI was just flaky. It listed the networks and even started downloading my backup. That was followed by a boot loop, which may have been because of a button issue. I followed the instructions for flashing boot.img with --slot all. Again, WIFI was only flaky but after a few reboots it was gone entirely.

- Reflashed the stock 12 several times, didn't help.

- Reflashed the stock 11 version I was on, didn't help.

- fastboot erase/flash persist consistently fails with "Not allowed to flash" and "Not allowed to persist" even when I have root. This is very strange.

- dd if=<persist.img path> of=/dev/block/sda2 - seems to work but doesn't fix anything. Attempting to turn on the WIFI makes the UI unresponsive.

- Installed TWERP hoping it would provide a way to flash the persist.img but didn't really help. But it showed the persist partition size to be 0 bytes, which was a very interesting finding, confirming the persist partition corruption.

3 questions:

- Am I not flashing my persist.img correctly? If so, why not? I had backed it up with dd.

- I am guessing I might have to start looking for a Pixel 4XL persist.img, but where do I look for that? I am guessing all Pixel 4XLs have the same but the stock image downloads don't come with the persist.img for some reason.

- Is there anything else I should do?
[Google Pixel 4 XL Guides, News, & Discussion] madmuthertrucker:
Are you guys getting GPay working? I installed the Jan update and switched to magisk canary with safety net 2.2.1. I passed safety net, device is certified, banking apps all good. I denied Play store, Gpay, and Play Services. I noticed that Play services unchecks after reboot. Where am I going wrong? I'm not finding any recent info.
[Google Pixel 4 XL Guides, News, & Discussion] madmuthertrucker:
I got GPay working! Here is how.

Clear the cache and data for Google Play services, Google Play Store, and GPay. After which, I removed and reinstalled Google Pay and then added the payment method back in.

I had done this originally but not the uninstall & reinstall. That's what did it.
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
Update!

Magisk Canary 23017
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
Update

Magisk Canary 23018
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
Update

Magisk Canary 23019
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
UPDATES!

Magisk 24.1 Beta App

Magisk Canary 24101