yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4a Guides, News, & Discussion] frank93:
works for me, yes. pixel 4a, magisk 24. note that magisk "internal update" crashed for me, i suppose it had something to do with the "hide app" mechanism (the feature where magisk app renames/disguises itself), but after a "clean" uninstall of v23 and then installing v24 (apk), the magisk-update to v24 was offered. running smoothly since the last few hours now.

haven’t tried zygisk yet though, still "classic" mode. :)
[Google Pixel 4a Guides, News, & Discussion] stereo007:
Also Safetynet? I don't have that at all in the version? I can not get GPay to run in v24.
[Google Pixel 4a Guides, News, & Discussion] frank93:
ah, no idea about that, sorry, i don’t care that much for gpay or anything. don’t even have/use a safety net checker as of now, i’m afraid.
[Google Pixel 4a Guides, News, & Discussion] stereo007:
v24 + v2.2.1 (Zygisk) = SafetyNet Passed
[Google Pixel 4a Guides, News, & Discussion] noimjosh:
Has anyone had success rooting after applying the January 2022 Android 12 security patch (BUILD SQ1A.220105.002)?

I've tried Magisk 23.0, Magisk 24.0, Magisk 24.1 and the latest two versions of Magisk Canary and my phone won't boot with the patched image.
[Google Pixel 4a Guides, News, & Discussion] stereo007:
Yes it works for me on SQ1A.220105.002 with v24, without any problems.
[Google Pixel 4a Guides, News, & Discussion] a1291762:
Are you creating that patched image yourself? ie. Upload the boot.img to the phone, use magisk to patch the image, download the patched image and then use fastboot to flash or boot the patched image.

I fastboot boot the image and then get Magisk to install (direct) rather than using fastboot to flash but it shouldn't be any different in theory.

I was running Magisk 23 when the Jan patch came out and it was fine. I was just prompted to upgrade to 24.1 and it's still fine.
[Google Pixel 4a Guides, News, & Discussion] noimjosh:
I am patching myself, but I can't seem to get it to work. I probably will have to do a data wipe and try again, I'm just not ready to do that yet
[Google Pixel 4a Guides, News, & Discussion] a1291762:
Oh, There's maybe a conflicting module?

Try to disable them all before upgrade or do the safe mode thing... Might help?

I ran into this problem when upgrading to Android 11 but I don't use many modules these days.
[Google Pixel 4a Guides, News, & Discussion] noimjosh:
I've already upgraded to Android 12

After installing the patched boot.img, my 4a sits on the G screen with the loading bar below it. It is accessible via ADB, and I have run

magisk --remove-modules

I also couldn't get the phone to boot into safe mode 🙁

It's boots just fine using the unpatched boot.img
[Google Pixel 4a Guides, News, & Discussion] Vedarshi:
I have the same issue since the Jan build. Lost root with OTA and unable to boot into the patched magisk image - the screen is stuck at the loading bar.

I've tried flashing with dm-verity disabled, lock/unlock bootloader, wiped phone and reinstalled but it doesn't seem to work.

But here's a peculiar issue -

If I fastboot boot into the patched image, it is stuck but fixed with a reboot. If I 'fastboot flash boot', I cannot boot into the phone even after re-flashing original boot image. I have to flash all partitions again. Not sure why this is occurring
[Google Pixel 4a Guides, News, & Discussion] ParoxysmX:
So I have a bit of a weird problem, I don't seem to be able to either flash the patched boot.img or boot it directly as some have suggested. I'm on android 12, build SQ1A.220205.002, Feb 2022. So I downloaded the factory boot.img, patched it with the latest Magisk (v24 at the time of writing this) and tried to flash my patched image but the error is

FAILED (remote: 'Failed to write to partition Bad Buffer Size')

Now I notice the partition size is 62 megabytes approximately and the patched boot img is about 98. But weirdly the factory one is the same size. So in theory I couldn't even flash the factory. When trying to boot the patched image directly, it says

(bootloader) boot.img missing cmdline or OS version
FAILED (remote: 'Error verifiying the received boot.img: Volume Corrupt')

Which is bizarre. I tried resizing partitions but the command fails on the remote end. Any ideas?

edit: i was using the boot img for the wrong type of Pixel...bozo
[Google Pixel 4a Guides, News, & Discussion] cmstlist:
So I've been super lazy and haven't even upgraded to Android 12 yet. And now I have Magisk asking me to update to 24.1 which is the version that eliminates MagiskHide. So maybe someone can summarize for me: What is the "new and correct" way to install Magisk and whatever additional tools are required to get SafetyNet passing, Google Pay working, etc?
[Google Pixel 4a Guides, News, & Discussion] Lada333:
Hey guys!

I've read through the last few pages of this thread, however I'd like to ask a few questions to clarify things.

I have a Pixel 4a (bought from Google Store, so it's unlocked) running Android 12 (SQ1A.220205.002). Never been rooted, never had a custom rom flashed.

Is rooting as simple as downloading the latest factory image from developers.google.com to my phone, using the Magisk app to patch the image, then copying the image to my PC and then using ADB to flash the patched image?

I've never had a device that had A/B side patches. Would I need to install the patched/rooted system image twice, essentially, to always have root? Or is that something I needn't worry about?

Is there a way to make a backup of my current system image? As in, if trying to boot the patched image fails (ie. bootloop), can I just go "back" to how it was before? Or could I just flash the un-patched/stock factory image? Is that "guaranteed" to work?

If I manage to softbrick my device, is there a way to get it back? I had a OnePlus 3T before this phone, I remember using an "unbrick tool" once when I bricked it -- does anything similar exist for the Pixel 4a?

Does the Universal SafetyNet Fix work for Google Pay and banking apps (I'm aware that not all banking apps are built the same way, so it might work for some, and might not for others. I'd just like to know if it works for most, or not at all)?

Is there anything to beware of? Any major annoyances, dealbreakers, etc? I used to daily my 3T, and back than I had more time on my hand (so that when something broke, it wasn't a big deal to lose data, flash stuff again, start from scratch), unfortunately that's not the case anymore. I need my phone to be as reliable as possible. Basically my main reason for rooting would be to have access to Advanced Charging Controller. Is it worth the hassle?

Apologies for the long post, and thank you for your answers in advance.

Cheers!
[Google Pixel 4a Guides, News, & Discussion] beeshyams:
1. Yes

2. Don't bother about A/B

3 & 4.You can always flash the OTA update or factory image to get out of mess. Unless you did something really weird, it should work

5. Yes

6. Nothing to worry. I've been using Acc for long

Edit : monthly updates require you to root (step 1). Seamless update to inactive slot is long dead
[Google Pixel 4a Guides, News, & Discussion] Lada333:
Meaning that if I apply an OTA, I'll lose root? So, again, I'll have to manually patch the latest factory image and then flash it? That would count as a "dirty flash," so there's no need to wipe all data, and set everything up from scratch, correct?

Also, what do you mean by "Seamless update to inactive slot is long dead"?
[Google Pixel 4a Guides, News, & Discussion] beeshyams:
Yes to first paragraph

Second Para-only to reiterate that you can't use the old Magisk method of retaining root while applying OTA
[Google Pixel 4a Guides, News, & Discussion] Lada333:
What was the old Magisk method?

Also, one last question: if I wanted to go back to "factory settings," I just flash a factory image, lock the bootloader, and, as far as my device is concerned, it has never been tinkered with?
[Google Pixel 4a Guides, News, & Discussion] beeshyams:
Old method, you can Google it. No point in describing what doesn't work

Yes to the second part, though I didn't try as I want root always. Factory image flashing locks the boot loader too.
[Google Pixel 4a Guides, News, & Discussion] DiamondJohn:
@Lada333 To be clear, you use fastboot to flash the rooted boot image, not adb.
[Google Pixel 4a Guides, News, & Discussion] Lada333:
Yeah, sorry, for some reason I categorize everything in my mind as being "part of adb." I know it's not 100% technically correct though :x
[Google Pixel 4a Guides, News, & Discussion] mikkoc:
Has anyone been able to get banking apps to work with the latest Magisk 24.2 + zygisk + SafetyNet Fix 2.2.1?

I manage to pass all the checks with YASNAC, forcing BASIC evaluation and spoofing a Nexus 6P device.

Added all the apps in the Magisk DenyList, and Enforce DenyList enabled. Yet, all my banking apps detect root.
[Google Pixel 4a Guides, News, & Discussion] Lada333:
I use Magisk Canary (24201) with SafetyNet Fix v2.2.1. I also have Zygisk enabled, DenyList enforced (banking apps added to the DenyList, of course), and it works for me.

Have you renamed your Magisk app? Some apps gave me an error, saying I'm rooted, even when I wasn't, but I had the Magisk app installed. I assume they also check for specific package names that could indicate that your device might be rooted?

I have my Magisk Manager renamed to mSettings, no apps have detected root so far.
[Google Pixel 4a Guides, News, & Discussion] mikkoc:
Ok that worked for one app, but not for the other (HSBC). Oh well, that's OK, I can live with it. Thanks
[Google Pixel 4a Guides, News, & Discussion] XDAUser1234:
Anyone manage to successfully boot the patched magisk boot image? I was able to flash android 12 without issues, update my Magisk Canary, move the boot image to my device, patch the image, move back to PC, and fastboot flash boot patched.img -- cool beans. But then just cycle cycle cycle cycle cycle on the google logo without booting fully up. whats curious (to me) is it does boot up enough, because my WhatsApp on my PC begins to work again as if my Pixel is back on, but it is stitll just on the Google logo. Reflashing the original boot.img brings it right back up.

Any workarounds?
[Google Pixel 4a Guides, News, & Discussion] Lada333:
What command did you use to flash the patched boot image?

Was it "fastboot flash boot boot.img"? If so, could you try flashing it with "fastboot flash --slot all boot boot.img"?
[Google Pixel 4a Guides, News, & Discussion] XDAUser1234:
originally was using "fastboot flash boot patched_file.img" , then "fastboot reboot". No dice, and then fastboot flash boot boot.img to get back to normal....

just tried the above with --slot all, and it did send both options with that. Send and Write to both slot a, and slot b.....then reboot and same issue, just the Google Icon and the scrolling line scrolling on and on. I remember a while back that this was EXPECTED (to take forever) and to just let it go.... so tried that, and after watching it for over 30 mins I flashed back the regular boot.img, still no luck. Hmm.
[Google Pixel 4a Guides, News, & Discussion] beflythis:
hello fellow sunfish folk... I am an oldschool android power user who's just picked up a pixel 4a and doing the due diligence and enjoying stock rom before going wrist deep.

coming from suzuran family (sony xperia devices), I've dealt with compromised camera on custom ROMs for far too many years... nice to see older issues / manufacturer proprietary issues are becoming less and less of a blocker as time passes.

that said, from what I am reading here and what I am seeing on youtube vids... there seems to be a blocker on latest magisk with working finance/gov apps (that don't like root) and ability to take OTA updates with root... this is what I'm seeing:

1) older magisk required to take OTA updates (device signature workaround from what I can learn here)

2) newer magisk required to use trusted apps that block on a rooted device

so does that mean there is currently no solution to be able to take OTA updates if you wish, remain rooted, AND ALSO use trusted apps? am I reading that correctly? Not a huge issue for my use case, but simply trying to understand the lay of the landscape before I start unlocking, rooting, flashing.

Second question - seeing some nice kernel dev work on these boards (woohoo!!!). Is there a hard rule of thumb about which kernels work with which roms? Fully open compat? Listed on a per-kernel basis? Apologies for the basic question that may have an obvious answer. Is there a yet established "gold standard" with a preferred combo of aftermarket kernel + custom ROM? Any recos?

coming from Sony DRM with camera issues (amazing camera if stock, ROM wipes DRM keys which compromises camera forever thereafter) - are there any similar issues with pixel roms or any forewarnings folks may have for me prior to unlocking/rooting/flashing? NGL looks like phones and platforms are getting safer and safer, easier to mod and less penalizing [nice thing]. Hoping that is correct.

Thanks in advance and what a snazzy device. happy to be a sunfish bro.
[Google Pixel 4a Guides, News, & Discussion] a1291762:
If you can't get someone else's patched boot image to work, you can make your own.

Download the factory image that matches the version you are running. Extract it, and the embedded zip to get the boot.img. Send that to the device and use Magisk to patch it. Send it back to the PC and use fastboot to flash it (or get fastboot to boot it, then use Magisk to patch boot directly).
[Google Pixel 4a Guides, News, & Discussion] XDAUser1234:
Yes, just confirming that is indeed the process I was using :-) Moved the boot.img to my Pixel, use the updated Magisk Canary to patch it, move it back to to my PC, then fastboot flash it. No dice. Did someone post a patched imaage? If so, I missed it and will look back. That was actually the only way I managed to get it to work a few versions ago - self patching just would not take.

Also - realizing perhaps I am just using incompatible versions. Took the March 2022 update and have the latest magisk.
[Google Pixel 4a Guides, News, & Discussion] a1291762:
Maybe you have Magisk modules that are the problem? I've only seen that for major upgrades but 🤷 could try disabling all modules, upgrade, and then enable one at a time?

I've only used regular Magisk not canary or anything. But I also don't try to hide root or pass safetynet so regular Magisk is enough.

People used to post patched boot images. Not sure if there's a posted image for march.
[Google Pixel 4a Guides, News, & Discussion] acspdx:
I bought a refurbished unlocked Pixel 4a from Amazon and wanted to root it, but the "OEM Unlocking" toggle was greyed out. I did a factory reset and tried again, but it still didn't work. I even tried booting up with my existing phone's SIM card... still no luck.

Does this mean the one I was sent is in fact a Verizon version whose bootloader cannot be unlocked? If so, is there any way to tell whether you're getting a Verizon one, or is it just the luck of the draw?

EDIT: I chatted with Google's support, and they were able to confirm — via the IMEI — that it was indeed a Verizon-tainted model. I'm sending it back to the Amazon seller, and I ordered one on eBay that has "unlocked bootloader" in the item description.
[Google Pixel 4a Guides, News, & Discussion] acspdx:
Replacement 4a has been rooted. I even figured out how to make my own Magisk module to replace the obnoxious thumping touch sound with something more unobtrusive.
[Google Pixel 4a Guides, News, & Discussion] andrewblake:
I got a 4A, rooted, installed Magisk, etc, everything worked perfectly.

Thank you so much for providing this information and the tools.
[Google Pixel 4a Guides, News, & Discussion] beflythis:
Did you get answers to your questions? First one I received was OEM unlockable, but the screen died on it after I pushed OTA android 12 to it... the replacement they sent has OEM unlocked greyed out (as you describe) and my attempts to command line fastboot oem unlock it all result in "fails".

Curious if this is a hard blocker, or there are still advanced workarounds for this?
[Google Pixel 4a Guides, News, & Discussion] acspdx:
I don't think there's any workaround for a phone that's been in Verizon's hands.
[Google Pixel 4a Guides, News, & Discussion] beflythis:
Thnx. It's on Android 12... runs great out of box so not horribly mad, but would like custom kernel and de-bloated roms at least.

To you knowledge, are verizon phones at least rootable to some degree (in an effort to de-bloat?) Or totally hands-off / stock only?
[Google Pixel 4a Guides, News, & Discussion] stereo007:
I do not understand point 4.

Does "fastboot -w update image-sunfish-sp2a.220305.012.zip" become "fastboot --skip-reboot"?

Here on the example of March, is this correct?

flash-all.sh
[Google Pixel 4a Guides, News, & Discussion] a1291762:
It becomes fastboot --skip-reboot update image-sunfish-sp2a.220305.012.zip
[Google Pixel 4a Guides, News, & Discussion] treypop:
My phone is rooted and passes safetynet but gpay doesn't work. I'm running android 13. Any suggestions for getting it working?
[Google Pixel 4a Guides, News, & Discussion] beeshyams:
There's a dedicated thread . You are likely to get fix here

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/

Edit : are you using any Xposed modules that block access to contacts? That was the problem for me on Android 13
[Google Pixel 4a Guides, News, & Discussion] treypop:
Thx that fixed it for me
[Google Pixel 4a Guides, News, & Discussion] dadnammit:
Having trouble "re-rooting" after an update, and need troubleshooting suggestions. It's been a long time since I first rooted using the steps here: https://www.xda-developers.com/google-pixel-4a-how-to-unlock-bootloader-root-pass-safetynet/

I lost root after an OTA and am finally trying to do it again, but it's not working. Now running Android 13. I did several OTA updates while the root was lost.

STEPS:

- I extracted the boot.img from the firmware on my device: "13.0.0 (TQ1A.221205.011, Dec 2022)"

- Magisk-v25.2.apk is installed.

- Patched the boot.img using Magisk.

- Copied magisk_patched-25200_r1Bfr.img to my PC.

- Started phone in fastboot and ran: fastboot flash boot magisk_patched-25200_r1Bfr.img

- Got response of OKAY writing to boot_a

The phone starts fine, but it's not rooted.

:(

Ideas?

(Magisk has the SuperUser button greyed out, and a Root Checker detection app fails. But some banking apps now fail because I am "rooted.")
[Google Pixel 4a Guides, News, & Discussion] TheSayaMan:
Are you on official stock or a custom ROM? If custom, you can sideload magisk in recovery

adb sideload magisk apk

I haven't had this device in a few years. If there is a trwp available, you can also boot twrp and install that way with official and custom without patching the boot img
[Google Pixel 4a Guides, News, & Discussion] dadnammit:
Thanks, TheSayaMan. I'm on a stock ROM. Found a TWRP, but it doesn't look like Magisk supports intall that way anymore since v24.3. How would I do it?
[Google Pixel 4a Guides, News, & Discussion] dadnammit:
SOLVED!

The problem was an old hidden Magisk app package was present. I removed all Magisk app versions. Flashed the patched boot.img created previously by by Magisk v25.2, and then reinstalled Magisk Manager. All is working now!
[Google Pixel 4a Guides, News, & Discussion] Hatimbjp:
I tried this method now my sound and Wi-Fi is not working any clues?????
[Google Pixel 4a Guides, News, & Discussion] Natakranta:
Has anyone found a way to fix Safetynet CTS test fail on Google February image rooted with Magisk 25.2 ?
[Google Pixel 4a Guides, News, & Discussion] Koile:
I could not figure out, if this also works with Lineage or PixelExperience. Can anyone confirm, if it does?

Edit: Also: Is the problem with the broken Safetynet CTS mentioned by Natakranta already fixed?
[Google Pixel 4a Guides, News, & Discussion] soxxoz:
Hi, I have a question. After follow the guide, I have rooted but I can't edit system's files.

The consequence is strange acting from apps (Adaway works but doesn't block any ads, I thinks should be correlated). Do you have ideas?
[Google Pixel 4a Guides, News, & Discussion] DiamondJohn:
The Pixel 4A is R/O system. You have to use a Magisk module to set a change, and hence the systemless Host module when using AdAway.
[Google Pixel 4a Guides, News, & Discussion] soxxoz:
Sad thing. I was good on android 9 and there are some news. I had already installed systemless hosts module, also other reasons I have reflash entire rom and now works.

Thanks for the reply and info
[Google Pixel 4a Guides, News, & Discussion] Zlatty:
So, if you are stuck in a bootloop you have to reflash the correct boot.img, go to magisk, repatch, reflash? Asking because I am stuck in a bootloop!
[Google Pixel 4a Guides, News, & Discussion] fronto:
Could you share the link? I searched and each link I found leads to a 404

No all you need to do to get back running is "fastboot flash boot boot.img" ......using the untouched original stock boot.img you used to patch with Magisk
[Google Pixel 4a Guides, News, & Discussion] Zlatty:
Hmmm. I did that. both boot command and (boot_a, boot_b) commands with no luck. Just keep getting to the Fastboot Mode screen.

Zlatty ~ % fastboot flash boot_a /Users/zlatty/Downloads/sunfish-rp1a.200720.011/image-sunfish-rp1a.200720.011/boot.img
Sending 'boot_a' (65536 KB) OKAY [ 1.840s]
Writing 'boot_a' OKAY [ 0.674s]
Finished. Total time: 2.744s
Zlatty ~ % fastboot flash boot_b /Users/zlatty/Downloads/sunfish-rp1a.200720.011/image-sunfish-rp1a.200720.011/boot.img
Sending 'boot_b' (65536 KB) OKAY [ 1.630s]
Writing 'boot_b' OKAY [ 0.454s]
Finished. Total time: 2.304s
Zlatty ~ % fastboot reboot
Rebooting OKAY [ 0.080s]
Finished. Total time: 0.080s
zlatko.unger@zlatko-unger-C02D47E8MD
[Google Pixel 4a Guides, News, & Discussion] 12paq:
You can always find it on the Magisk Manager GitHub:

https://github.com/topjohnwu/Magisk
[Google Pixel 4a Guides, News, & Discussion] Zlatty:
it was restarting to fastboot ... I'm an idiot

use https://github.com/topjohnwu/magisk_files/tree/canary
[Google Pixel 4a Guides, News, & Discussion] fronto:
All I can think is that you might be flashing the a boot.img that does not match whats on your phone. But, I think I have the solution for you…see below.

Thanks but it seems they killed the project. I was getting the 404’s off github. Posted links on XDA and elsewhere that point there no longer good, but I found canary on an independent site and patched the file.

So, for anyone looking to root the Pixel 4a on Android 11 (200720.011), I can save you the trouble of having to find and run what’s essentially a pre-beta version of Magisk, which you only need to patch the boot.img file. You do not need Canary to run on your phone afterwards. I have regular Magisk Manager 7.5.1 running now fine with this patched boot file, here you go:

magisk_patched_sunfish-rp1a.200720.011.img
[Google Pixel 4a Guides, News, & Discussion] Zlatty:
This patched version worked! Thank you.
[Google Pixel 4a Guides, News, & Discussion] 12paq:
I'm not sure what you're doing. When I click on the link that I posted for you it takes me right to the the Magisk Github with the download files for Magisk Manager including beta and canary.

This: https://github.com/topjohnwu/Magisk or directly this: https://github.com/topjohnwu/magisk_files/tree/canary

Edit: please be careful using any Magisk files that are not from topojohnwu's git
[Google Pixel 4a Guides, News, & Discussion] Zackptg5:
Added canary link to OP, I'm on 11 now with latest canary and it's working fine

Never download magisk from anywhere other than topjohnwu's GitHub. The other sites are not legit/affiliated with him and many of them are just profiting off of his work
[Google Pixel 4a Guides, News, & Discussion] DB126:
No. Statement above refers to carrier unlock. Bootloader on Verizon branded handsets can not be unlocked. You'll need the retail variant to root.