yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3a XL Guides, News, & Discussion] V0latyle:
Official updates for this device ended September 2022.

If you are looking for my guide on a different Pixel, find it here:

Pixel 3

Pixel 3XL

Pixel 3a

Pixel 4

Pixel 4XL

Pixel 4a

Pixel 4a (5G)

Pixel 5

Pixel 5a

Pixel 6

Pixel 6 Pro

For best results, use the latest stable Magisk release.

Discussion thread for migration to 24.0+.

Note: Magisk prior to Canary 23016 does not incorporate the necessary fixes for Android 12+.

WARNING: YOU AND YOU ALONE ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS GUIDE IS WRITTEN WITH THE EXPRESS ASSUMPTION THAT YOU ARE FAMILIAR WITH ADB, MAGISK, ANDROID, AND ROOT. IT IS YOUR RESPONSIBILITY TO ENSURE YOU KNOW WHAT YOU ARE DOING.

Prerequisites:

Latest SDK Platform Tools - if Platform Tools is out of date, you WILL run into problems!

USB Debugging enabled

Google USB Driver installed

I recommend using Command Prompt for these instructions; some users have difficulty with PowerShell.

Make sure the Command Prompt is running from your Platform Tools directory!

Android Source - Setting up a device for development

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Points of note:

The boot image is NOT the bootloader image. Do not confuse the two - YOU are expected to know the difference. Flashing the wrong image to bootloader could brick your device.

While the Magisk app is used for patching the boot image, the app and the patch are separate. This is what you should see in Magisk for functioning root:

"Installed" shows the version of patch in the boot image. If this says N/A, you do not have root access - the boot image is not patched, or you have a problem with Magisk.

"App" simply shows the version of the app itself.

If you do not have a patched master boot image, you will need to download the factory zip if you haven't already, extract the system update inside it, then patch boot.img.

If you prefer updating with the factory image, you can also extract and manually patch the boot image if desired.

Some Magisk modules, especially those that modify read only partitions like /system, may cause a boot loop after updating. As a general rule, disable these modules before updating. You are responsible for knowing what you have installed, and what modules to disable.

Credits:

Thanks to @badabing2003 , @pndwal , @Displax , @Az Biker , @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!
[Google Pixel 3a XL Guides, News, & Discussion] Cheetah_Bear:
Hi, thank you for the guide. I am very new here and I have some questions that I hope you can answer before I proceed.

First of all, I assume I should back up my device on an external medium if I screw the pooch. With that in mind, do you have any suggestions/ links on guides that can help me with that? If not, I'm sure I can do some good digging to find something suitable.

Second, I'm not exactly sure what "Bonito" is and from what I have seen from googling, it seems to be connected to the LineageOS operating system. Is this different from the current, factory OS that my phone is running? Is there a way to root my device without changing the factory OS if that's the case? If not, that's okay, I don't mind switching to an open-source OS that seems to have a good reputation.

Third, is the guide supposed to be followed sequentially with the first step being, "Spoiler: Downloads" and the last step being, "Spoiler: Pass SafetyNet?" Or are the first 3 steps, "Spoiler: Downloads", "Spoiler: Unlock Bootloader" and, "Spoiler: Initial Root / Create Master Root Image" are essential steps and the subsequent steps afterwards are based on personal needs? Ideally, using Android Flash Tool seems painless and foolproof which is perfect for me. Afterwards, I will attempt to copy the Spoiler: Pass SafetyNet" step.

Fourth, what is your take on using Android Flash Tool vs TOOL ALL IN ONE for flashing? TOOL ALL IN ONE seems even more painless and fool-proof and apart from backing up, seems easier. But I would love your take on this?

Feel free to answer any or none of these questions. I know it's a lot but id rather ask questions to a staff member before proceeding?

Thanks again for the guide!
[Google Pixel 3a XL Guides, News, & Discussion] V0latyle:
Without root, there is no way to do a full backup including app data. The best you can do is sync your Pixel with your Google account.

"Bonito" is Google's internal name for the device and has little to do with the software. The Pixel 5 is "redfin", the 5a is "bramble", the Pixel 2 was "walleye".

As far as rooting your device, yes - if you follow this guide, you will gain root on the stock OS. I am currently using my Pixel 5 with the OEM firmware, patched with Magisk.

This guide is not sequential; I provided different instructions for different scenarios. The downloads are simply the resources you will need. To attain root, simply follow the instructions under "Initial Root". When the June update is released, you can update using your method of choice, and follow the relevant instructions to regain root.

I personally do not like using third party tools, and I simply use adb/fastboot. The Android Flash Tool is simply for flashing factory firmware and cannot flash custom images.

No worries. It sounds like you have a lot to learn but you're at the right place; XDA is full of knowledgeable people who can help you out.

Thank you for your appreciation.
[Google Pixel 3a XL Guides, News, & Discussion] Cheetah_Bear:
Well, with a bit of hard work and head-bashing into my desk, my phone is fully rooted and backed up. I want to extend my thanks again for this guide. I'll be sure to return when the next updates roles around.

I am still trying to play around with Safety Net and my financial app. YASNAC says my Saftey Net passes, but my finance app won't open because it's still, somehow, detecting root, even after being placed under the Deny List.

Regardless, that is a problem for another day. Today is a day of celebration because my phone is rooted and rocking. 🥳🥳

Thank you again.
[Google Pixel 3a XL Guides, News, & Discussion] V0latyle:
Make sure you're using USNF and MHPC; DenyList alone won't do it.

You may also have to block the Play Store due to Play Protect.
[Google Pixel 3a XL Guides, News, & Discussion] BadRx:
Can I do anything with my 3a XL if the OEM debugging is greyed out? Honestly, is it really moddless?
[Google Pixel 3a XL Guides, News, & Discussion] V0latyle:
Most likely not. There is no way to force unlock. If you bought a branded variant like Verizon, unlocking the bootloader is not possible.
[Google Pixel 3a XL Guides, News, & Discussion] BadRx:
Why is that? I find that sooo... disturbing. From a hobbyist point of view this is just so unacceptable. You mean to tell me that I can't flash the chips somehow on this phone? Now there was a way carrier lock... you mean to tell me there is no way to carrier unlock? Not even the carrier? That's... just hard to believe.
[Google Pixel 3a XL Guides, News, & Discussion] V0latyle:
I'm talking about bootloader unlock. It is a well known fact, having been established since the original Pixel (if not the Nexus series) that Google devices sold through carriers such as Verizon are not bootloader unlockable. This is why if you want a completely unlocked device, you must buy directly from Google.

As far as carrier unlock...that depends on the carrier. If you bought your device from Google, it's already carrier unlocked. But if you bought it through a carrier, they may or may not unlock it depending on their own policies. I don't know what Verizon's is, but most US carriers will allow carrier unlock as long as 1) there is no lien on the device (it's paid off) and 2) your account is not under contractual obligations.

It may seem weird to you, but they're protecting their investments. You can't reasonably expect a carrier to provide you a device at a discount with no restrictions. Either buy used from Swappa, or new full price from Google, and use the carrier only as a carrier. If you buy a phone through them, don't expect the same freedom.
[Google Pixel 3a XL Guides, News, & Discussion] 4L3xN3t:
Hi, before spamming all my stuff here, is this the right place to ask for help in the process of rooting (installing magisk and patching the boot.img) my pixel 3a XL?

thank you

Alex
[Google Pixel 3a XL Guides, News, & Discussion] V0latyle:
Did you read the OP?
[Google Pixel 3a XL Guides, News, & Discussion] 4L3xN3t:
yes, I spent much more time on reading it and preparing the needed stuff than doing the process :)

if you're referring to the warning, yes, I'm quite familiar with ADB, Magisk, Android and Root, but not 100%. I've played with some devices in the past, but the last before the 3aXL was a Nexus6 and a lot of thing changed in the root process and I'm a bit confused.

anyway, if it's ok, I would try to explain what's appening, I got a bootloop at the last step of rooting

Alex
[Google Pixel 3a XL Guides, News, & Discussion] V0latyle:
What Android build are you on? Did you update?

What version of Magisk are you using?

What process did you use to root?
[Google Pixel 3a XL Guides, News, & Discussion] 4L3xN3t:
ok, well, so, as I said I've an unlocked Pixel 3aXL with a stock ROM (bonito-sp2a.220505.006).

I'm on a fresh configured PC and just downloaded the latest platform-tools, USB driver, factory image, Magisk 25.2 canary.

Followed the guide in this page for the initial root, so I installed magisk, took the boot.img from the factory image, copied into the phone and patched via Magisk app. copied the patched boot.img into my platform-tools folder and flashed on the phone from the recovery via fastboot.

Now, after rebooting, the bootloop came. I just fix it flashing back the factory image, but of corse i'm still not rooted.

Maybe something related to the two boot_a and boot_b slots?

reading the boot.img flashing log it said it was flashed on boot_a (unfortunately i didn't check the actual slot before, I suppose was still boot_a) but then when i flashed the factory image to get rid of the bootloop it went on boot_b.

So I suspect I could have a misalignment beetween the two slot, but I'm not sure at all and anyway don't know exactly how to align them.

thank you
[Google Pixel 3a XL Guides, News, & Discussion] V0latyle:
No, there's no "misalignment" between slots. Each slot has its own partitions, and the system will boot from whatever slot is active. So, since you're on Slot A, the system will load the boot image from /boot_a, and run the system from /system_a. It doesn't cross over.

When I asked "what build" are you running, I meant which Android release, not your phone type. I also asked how you updated - factory image or OTA?

Where did you download Magisk from? There is no "25.2 canary". The current Canary is 25203, but Stable should work just fine.

I suspect you may be doing something wrong, hence the bootloop. Rule of thumb: When you encounter a problem. ALWAYS make sure you're doing everything right, and don't assume there's something wrong with the system until you have gone back through the instructions and made sure you're doing everything correctly.

Word of advice: When someone asks you specific questions, make sure you answer all of them with as much detail as possible. The more information we have, the better we are able to help you.
[Google Pixel 3a XL Guides, News, & Discussion] 4L3xN3t:
ok, sorry, you're right, I lost something.

I wrote "bonito-sp2a.220505.006" because it thought it gives the information that I'm on the last available update for this phone of android 12.1. I always updated via OTA (I think it could be also interesting to know that I hadn't Magisk installed or any other modification at the time of the last update).

about Magisk I assumed that "25203" means "a release (the third?) of the 25.2", my fault...but anyway yes, I have the canary 25203, used it instead of the stable because sometimes in the past with other phones using it was the solution to some installation issues but I think this is not the problem.

I repeated the process (only the 9 steps of the "Spoiler: Initial Root / Create Master Root Image" guide) more than once, so I'm trying to understand if there might be something else wrong or corrupted.

partially unrelated question about the slots: if I force to boot from the slot A I'm supposed to go back to the bootloop, right?

Did you have anything in mind about this?

thank you
[Google Pixel 3a XL Guides, News, & Discussion] V0latyle:
I generally recommend against switching slots unless absolutely necessary, and especially not if you update via OTA. The reason for this is if you force the device to boot from the "old" slot, Anti-Rollback Protection will kick in and cause a boot loop.

Since you're able to boot with the unpatched image, just flash that for the time being. Your device has to finish up the update after booting, and the rooted image can sometimes cause a problem with this. Once the device has been running for a bit, say 10 minutes or so, you should be able to safety flash the patched image.

Were you rooted before?
[Google Pixel 3a XL Guides, News, & Discussion] 4L3xN3t:
The last update was done in May, so I think I waited way more than 10minutes :)

I really can't remember if I rooted when I bought it, with android 10, but if so (with magisk anyway), after the upgrade to 11 I didn't root again for sure.
[Google Pixel 3a XL Guides, News, & Discussion] V0latyle:
Hmm. I am not sure why you are having problems now. The only thing I can suggest is flash the factory image using the instructions in the OP; you can also use the Android Flash Tool. You shouldn't need to wipe your device. Double and triple check to make sure you're patching the correct boot image, maybe post some screenshots or something (use spoilers) to show what you're doing. 99% of the time, if you are using the correct software, the problem is likely Magisk modules or incorrect patching.
[Google Pixel 3a XL Guides, News, & Discussion] 4L3xN3t:
when I flash the factory image (as I did l 2days ago), I use the "flash-all.bat" included in the original zip after I delete the "-w" from "fastboot -w update imagexyz.zip" and this way it doesn't wipe the phone.

I'll try again in the nex days (hope to have time in the weekend) doing some screenshot

stay tuned.

thank you
[Google Pixel 3a XL Guides, News, & Discussion] V0latyle:
I don't think it's so much the factory image as it is a problem with the boot image.

This is what I would do:

Connect phone to your PC, open the storage in your file explorer

Remove any boot images already on the device

Check the /downloads folder and remove all patched images

Create a new folder titled "Boot image" in device storage

Verify that you have the correct factory image for your device (this is the September build for "bonito")

Extract the contents of the factory image; open the image-bonito-buildnumber.zip inside it, and copy boot.img to the folder you extracted the factory image to. Keep this folder open

Copy the same boot.img to the Boot Image folder you just created on the phone

Open Magisk, select Settings > Download Path, select the Boot Image folder (this forces Magisk to put the patched image in that folder)

Go back to the main Magisk screen, select Install > Select and Patch a File, select the boot.img in the Boot Image folder, proceed with the patch

When complete, go back to your PC and copy the newly patched boot image that's now in the Boot Image folder back to the extracted folder

Open a command line window in your ADB Platform Tools folder

Reboot your device to bootloader: adb reboot bootloader

Flash the patched image to your device: fastboot flash boot <drag and drop the patched image into the command window>

Reboot your device: fastboot reboot

The device should boot with root. Open Magisk, verify that Installed under the Magisk section at the top shows the fingerprint ID and Magisk build number (in my case, Installed 38ab6858 (25203)
[Google Pixel 3a XL Guides, News, & Discussion] 4L3xN3t:
LOL, I heard in june that google would have released the last update for the 3aXL in july or august. monday the last update wasn't still released. today there's a september update...well I'll have to update first and then try this
[Google Pixel 3a XL Guides, News, & Discussion] V0latyle:
Support for the Pixel 3/3XL ended in June. Support for the 3a series was only guaranteed until May of this year so you're essentially on borrowed time:

View attachment 5706471
[Google Pixel 3a XL Guides, News, & Discussion] anlgrbz:
Got the following error when running the 8th step of

'Spoiler: Initial Root / Create Master Root Image' Would appreciate any help!

View attachment 5751841

I guess the partition size is not large enough for boot_b? Do you think if it is a good idea to change to patiotion_a? Based on the above discussion I am reluctant to do
[Google Pixel 3a XL Guides, News, & Discussion] anlgrbz:
Turns out problem is I downloaded the wrong image from google's side --- Be careful there are several files with the exact same build number! Make sure downloaded zip file starts with [bonito]!
[Google Pixel 3a XL Guides, News, & Discussion] V0latyle:
Yes, I can immediately tell you were using the wrong file. Notice how it tells you the partition size (65MB) vs the image size (98MB)
[Google Pixel 4 Guides, News, & Discussion] V0latyle:
Official updates for this device ended February 2023.

If you are looking for my guide on a different Pixel, find it here:

Pixel 3

Pixel 3XL

Pixel 3a

Pixel 3aXL

Pixel 4XL

Pixel 4a

Pixel 4a (5G)

Pixel 5

Pixel 5a

Pixel 6

Pixel 6 Pro

For best results, use the latest stable Magisk release.

Discussion thread for migration to 24.0+.

Note: Magisk prior to Canary 23016 does not incorporate the necessary fixes for Android 12+.

WARNING: YOU AND YOU ALONE ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS GUIDE IS WRITTEN WITH THE EXPRESS ASSUMPTION THAT YOU ARE FAMILIAR WITH ADB, MAGISK, ANDROID, AND ROOT. IT IS YOUR RESPONSIBILITY TO ENSURE YOU KNOW WHAT YOU ARE DOING.

Prerequisites:

Latest SDK Platform Tools - if Platform Tools is out of date, you WILL run into problems!

USB Debugging enabled

Google USB Driver installed

I recommend using Command Prompt for these instructions; some users have difficulty with PowerShell.

Make sure the Command Prompt is running from your Platform Tools directory!

Android Source - Setting up a device for development

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Points of note:

The boot image is NOT the bootloader image. Do not confuse the two - YOU are expected to know the difference. Flashing the wrong image to bootloader could brick your device.

While the Magisk app is used for patching the boot image, the app and the patch are separate. This is what you should see in Magisk for functioning root:

"Installed" shows the version of patch in the boot image. If this says N/A, you do not have root access - the boot image is not patched, or you have a problem with Magisk.

"App" simply shows the version of the app itself.

If you do not have a patched master boot image, you will need to download the factory zip if you haven't already, extract the system update inside it, then patch boot.img.

If you prefer updating with the factory image, you can also extract and manually patch the boot image if desired.

Some Magisk modules, especially those that modify read only partitions like /system, may cause a boot loop after updating. As a general rule, disable these modules before updating. You are responsible for knowing what you have installed, and what modules to disable.

Credits:

Thanks to @badabing2003 , @pndwal , @Displax , @Az Biker , @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!
[Google Pixel 4 Guides, News, & Discussion] largeruk:
@V0latyle The Pixel phone I'm rooting belongs to a friend who wants it rooted. Prior to doing anything (thankfully!), I established that the phone is actually a Pixel 4, not a 4a.

I downloaded the correct stock image for that model and then followed all your instructions. This included updating the bootloader and radio from the factory stock zip before flashing the Magisk-patched boot image.

Everything went well and the phone is now rooted with your recommended Magisk modules to pass SafetyNet. However, the wifi no longer works on the phone. I don't have his sim to test if mobile signal/data works. Thinking the problem might be the new radio, I found and reflashed the oId radio image but no joy.

What steps do I need to take to resolve the situation and get wifi working again?

Thanks for your help.

UPDATE: I've managed to restore the phone back to stock firmware (Mar 22 flame for Pixel 4 - the version it was given to me in) ang got the wifi working again. The bootloader is still unlocked. I cannot figure out what I did in the rooting process that affected the functioning of the wifi :unsure:
[Google Pixel 4 Guides, News, & Discussion] V0latyle:
I had your post moved to this thread to keep the other one on topic.

I don't think there's anything you could have possibly done during the flashing or patching process to cause WiFi to stop working. Try again using the latest update; make absolutely sure it's for "flame", no other version.
[Google Pixel 4 Guides, News, & Discussion] zerodi:
Dear

V0latyle​

Will the magisk posted here and process work on latest Android 13 build ?

Many Thanks
[Google Pixel 4 Guides, News, & Discussion] V0latyle:
Rooting Android 13 works exactly the same way as Android 12 and 11. Just make sure you're using the latest Magisk release, which should be 25.3.
[Google Pixel 4 Guides, News, & Discussion] zerodi:
excellent many thanks