[Guide] Root Pixel 4 XL with Magisk Android 13

[Homeboy76]

not sure what error i got. but missing MagiskHide option in settings

That is the new Magisk Canary <beta> 23010. Check this thread for changes and search this thread for information on its use.

 

[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.

 

[bradical711]

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.

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.

 

[madmuthertrucker]

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 was the removal of magiskhide. In replace of that 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. "Deny list" is NOT the same as magiskhide although the finer details aren't as clear to me on that part. That basically sums up my current knowledge of the situation. If you're looking for advice on wether or not to take 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.

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.

 

[flyoffacliff]

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.

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

 

[bradical711]

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

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.

 

[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)

 

[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?

 

[madmuthertrucker]

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?

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.

 

[mochamoo]

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.

It is the Google version and have been flashing the generic versions all along. VZ tends to cripple things like esim functionality.

 

[madmuthertrucker]

It is the Google version and have been flashing the generic versions all along. VZ tends to cripple things like esim functionality.

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.

 

[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.

 

[Homeboy76]

Magisk Canary 23001: Click 3 dot Menu => Click app-debug.apk => Click 3 dot Menu above View raw => Click download

 

[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

 

[madmuthertrucker]

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

Did you do a clean install?

 

[docluv01]

Did you do a clean install?

Yes, I did. had to flash back stock boot.img to be able to use phone

 

[Homeboy76]

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

@docluv01 did you use Magisk Canary 23001 to patch the boot image?

 

[docluv01]

@docluv01 did you use Magisk Canary 23001 to patch the boot image?

Hi, yes I tried 23001, 23012, and the latest alpha. Same thing in all instances. Had to reflash stock boot.img every time.

 

[Homeboy76]

Hi, yes I tried 23001, 23012, and the latest alpha. Same thing in all instances. Had to reflash stock boot.img every time.

@docluv01Try this also are you using SafetyNet Fix 211.

If that doesn't fix it, It might be a hardware problem.

 

[docluv01]

@docluv01Try this also are you using SafetyNet Fix 211.

If that doesn't fix it, It might be a hardware problem.

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.