yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4 XL 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 4

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 XL Guides, News, & Discussion] kmry:
Thanks for the guide, im currently on android 12, planing to downfgrade to Android 11, will be ok to follow the Master Root guide to patch, downgrade and root at the same time to Android 11?
[Google Pixel 4 XL Guides, News, & Discussion] V0latyle:
Yep.
[Google Pixel 4 XL Guides, News, & Discussion] dortok:
I can pass SafetyNet but GPay does not allow contactless. The only thing unclear is what settings you used from MagiskHide Props Config. Can you please share?
[Google Pixel 4 XL Guides, News, & Discussion] V0latyle:
I didn't change anything under MHPC or UNSF, and tap to pay works fine on my Pixel 5.
[Google Pixel 4 XL Guides, News, & Discussion] dortok:
I thought the purpose of MHPC is to easily change the prop settings to another device. Does it even do anything by just installing the module?
[Google Pixel 4 XL Guides, News, & Discussion] V0latyle:
I'm not sure, I've never messed with anything under the hood, and honestly I didn't install it myself - I'm not sure how it got installed. Other users have mentioned success using only USNF.
[Google Pixel 4 XL Guides, News, & Discussion] Broken.exe:
Thank you for well written guides, will this guide work with any android version? I'm willing to follow this rooting process at Android 13
[Google Pixel 4 XL Guides, News, & Discussion] V0latyle:
Yes
[Google Pixel 4 XL Guides, News, & Discussion] jljtgr:
I just wanted to make a comment about the blanket statement of using the latest platform tools.

As of this writing, v34.0.0 is the most current, but it did not work for me and flashing the full images to a Pixel 4 XL.

{...}
extracting product.img (2440 MB) to disk... took 10.694s
extracting system.img (821 MB) to disk... took 4.031s
extracting system_ext.img (298 MB) to disk... took 1.498s
extracting system_other.img (23 MB) to disk... took 0.121s
extracting vendor.img (823 MB) to disk... took 4.021s
archive does not contain 'vendor_other.img'
Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)
fastboot: error: Command failed

Using v33.0.3 of the platform tools worked correctly for the Feb 2023 and Oct 2022 images. v34.0.0 failed for both of those.
[Google Pixel 4 XL Guides, News, & Discussion] Lughnasadh:
v34.0.0 has problems with fastbootd. It basically skips it, so v33.0.3 is the one people should be using right now until they fix it. There has been an issue opened up for it.
[Google Pixel 4 XL Guides, News, & Discussion] Graeme354:
Just a question, what does it take to get TWRP recovery to "stay" on a Pixel 4XL ?? Every time I update Lineage it just disappears 🤔
[Google Pixel 4 XL Guides, News, & Discussion] V0latyle:
I explained this recently in another thread:

On previous versions of Android it was possible to repack TWRP into the boot ramdisk, but that is no longer possible on Android 12/13.

Short answer: You cannot replace stock recovery with TWRP on a Pixel phone. You can live boot it for temporary use only.
[Google Pixel 4 XL Guides, News, & Discussion] Graeme354:
OK buddy, thanks anyway. 👍
[Google Pixel 4 XL Guides, News, & Discussion] V0latyle:
Glad to be of help
[Google Pixel 4 XL Guides, News, & Discussion] Graeme354:
I have TWRP'd in the wrong place I think as it would not stay. Any help in the resurrection of my 4XL will result in a substantial donation. My bad as I was told not to try and make it permanent in the first place. I am wearing the donkeys ears already. 🫡
[Google Pixel 4 XL Guides, News, & Discussion] V0latyle:
Always ALWAYS ask questions before you try the unknown. I am guessing you borked your partitions trying to create a recovery partition...which wouldn't work by the way because the bootloader only knows "boot"

But, assumptions won't do any good, so please explain exactly what you did and how you got to this point?

DO NOT try to rebuild your partitions until we figure out what is going on, as you will most likely permabrick your device.
[Google Pixel 4 XL Guides, News, & Discussion] Graeme354:
I flashed to boot, to both slots A and B and a recovery drive I think you call it. I have ADHD and am compulsive. I reckon I'm going to have to flash firmware and start again buddy. 😕
[Google Pixel 4 XL Guides, News, & Discussion] V0latyle:
Pixels do not have a recovery partition; the recovery kernel lives in the boot image. Replacing the stock recovery requires modifying the ramdisk which generally breaks Magisk.

The proper way to use TWRP on a Pixel is to live boot it, without flashing.

Did you remove, rename, or otherwise modify any of the partitions on the device?
[Google Pixel 4 XL Guides, News, & Discussion] Graeme354:
No, I did nor rename anything, nor had magisk installed. I no longer root my phones and will just do anything to debloat and DeGoogle. Live boot I know nothing about and used adb from my laptop. I just wanted TWRP permanent , flashed and reflashed , with TWRP to be in the situation I am now. I have a Samsung A52s modified and working and keep 2 phones for when I f**k up as you can see. I am no developer and will make a substantial donation to anyone who assists me to resurrect my phone. All I want to do is to adb sideload and leave it be. It won't do it. 😕
[Fire Q&A, Help & Troubleshooting] donnje:
Hi,

after installing the newly opened app, do I confirm the popup and then send me back to the home?

any soluzion, please?

I have a FireTv 3rd Gen with Fire OS 7.2.7.9
[General Topics] imzack:
Okay, i just got a HTC ppc-6800 from US CELLULAR, i dont know what the problem is, mabye something to do with internet sharing, idk, but i just installed the WMWIFI router software on the mogul and it starts up and then finally says FATAL ERROR ????? Does anybody know what im doing wrong? is there any settings i need to change for this to work??? and i do have my wifi turned on.

thanks
[General Topics] Towertopper:
Wifi troubles

I went through hell trying to get wifi working in my home with the router and after a week I figured out it was the wireless security camera's I had interfering with the router.
[POCO M3 Pro / Redmi Note 10 / 10T 5G] bonmatheus:
Hi!

For the last 3 weeks I was trying to unlock my Redmi note 10 5g to put the global version on it. (Buy Chinese)

Well, I got it yesterday, but it's giving this problem here that it doesn't want to restart. Does this fit like soft brick? If yes, how can I solve this problem?

OBS: I've already passed the 12.5.5 recovery file and it didn't help.

Thanks :)
[POCO M3 Pro / Redmi Note 10 / 10T 5G] wetito:
The problema Is nota clear, buy of your phone dont boot reflash correct firmware via fastboot. I suggest stato on china version. Is Better than global. Miui 13 stabile Is available with more function than global. Do you want change your phone with mi è global? 🤣

In the video i didnt saw any error message
[POCO M3 Pro / Redmi Note 10 / 10T 5G] bonmatheus:
I installed global version 12.5.3 and it worked LOL

Global version 12.5.5 is giving a lot of trouble.

I will install the Chinese version myself
[POCO M3 Pro / Redmi Note 10 / 10T 5G] wetito:
12.5.5 ota is bugged. but i have flashed full rom without problems
[Google Pixel 4a Guides, News, & Discussion] V0latyle:
Official updates for this device ended November 2023.

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

Pixel 3

Pixel 3XL

Pixel 3a

Pixel 3aXL

Pixel 4

Pixel 4XL

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 4a Guides, News, & Discussion] roxy1712:
Just a caveat, this doesn't appear to work with anything other than stock Android (e.g., will not work with Lineage).
[Google Pixel 4a Guides, News, & Discussion] V0latyle:
Correct, this is only meant for stock ROMs and stock kernels.
[Google Pixel 4a Guides, News, & Discussion] largeruk:
@V0latyle and all you other helpful people

A few basic questions please. I intend to use your guide to unlock the bootloader and root a Pixel 4a (non-5g) which is currently on stock rom Android 12 SP2A.220405.003. (Auto system updates are currently off in Developer options).

Should I update to the latest June version of Android 12 before doing anything?

Which versions of Magisk and Magisk Manager should I use to root the device?

Which elements of Magisk do I need to activate and which modules do I need to install to pass all SafetyNet checks so I can use UK banking apps?

I've used older versions of Magisk when the repository was built in but am unfamiliar with more recent versions where apparently there is no repo. How does one install modules now?

Many thanks
[Google Pixel 4a Guides, News, & Discussion] V0latyle:
You can, but you don't have to. You'll be downloading the factory image so you can patch the boot image anyway, so you might as well take advantage of the newest security update.

The two are the same. First, make sure you are only using the authentic Magisk from John Wu's Github, linked in the OP. Secondly, you can use almost any version of Magisk, but Android 12 support wasn't included until Canary 23010, meaning any version prior, including Stable v23.0 may not work properly. Since Public Beta 25.0 is out, just use that.

Ensure Zygisk and DenyList are enabled. Enable DenyList on the Play Store and the apps you want to hide root from; it will not work on system processes. Install the Universal SafetyNet Fix module, linked in the OP. Installing USNF will likely also install MagiskHide Props Config.

Confirm SafetyNet is passing with YASNAC.

Again, the only legitimate source for Magisk is the Magisk Github. Do not use any other version from any other site. The repository continues to be alive and well. If you're talking about the module library, that is no longer included in Magisk, so you have to install the modules manually through Magisk. For more help with this, please see the Magisk help threads, also linked in the OP
[Google Pixel 4a Guides, News, & Discussion] largeruk:
@ V0latyle Thanks very much for your incredibly helpful reply - much appreciated. Just some quick follow-ups for clarity please.

Zygisk - I assume that is enabled within Magisk somewhere?

DenyList - how exactly do I enable this 'on the Play Store'?

When you say DenyList will not work on system processes, I assume you mean things like Google Play Store etc? If so, is the mere installation of Magisk through the process you describe in the op now enough to hide Magisk and root from system processes?

Thanks again for your help and patience.
[Google Pixel 4a Guides, News, & Discussion] V0latyle:
Not to be rude but these are questions you should be asking in the Magisk support thread. Also, Google is your friend.

Here's how to get to the settings:

Spoiler content hidden.

Google Play Store is not a system process. Google Play Services on the other hand is, and blocking it in MagiskHide used to be pretty standard for passing SafetyNet attestation.

For further questions please use the Magisk support threads, linked in the OP under "Pass SafetyNet"
[Google Pixel 4a Guides, News, & Discussion] largeruk:
Apologies for raising questions that, as you rightly point out, should have been posed in other threads. Lesson learnt.

A quick follow-up to my original set of questions. Given that I will be rooting with the latest (June) Magisk-patched factory image, will I need to update the bootloader and radio prior to flashing the patched stock img?

I've compared the versions between phone screen and those contained in the stock factory zip. Both versions appear to be older the current stock one:-

bootloader version on phone is c2f2-0.4-8048765 vs bootloader-sunfish-s5-0.4-8351029 on stock image

radio version on phone g8150-00123-220122-B-8106568 vs radio-sunfish-g7150-00090-220406-b-8411773.

Thanks again for all your advice. Much appreciated.
[Google Pixel 4a Guides, News, & Discussion] V0latyle:
If the build numbers are different, you should update them. Don't worry about the numbers appearing "older"; as far as I can tell it doesn't seem like Google uses consecutive numbers for bootloader and radio.
[Google Pixel 4a Guides, News, & Discussion] acspdx:
This morning, my rooted Pixel 4a informed me that there was a "Security update available," even though I have Automatic System Updates turned off in Developer Options. And because I changed the device's signature in order to pass SafetyNet, it says it's an update for a Nexus 6P.

Obviously I don't want this update to install — especially since it's for the wrong device! Will it go ahead and download/install the update the next time I restart? (Or did it already download it?!) How can I abort this process?

View attachment 5641937
[Google Pixel 4a Guides, News, & Discussion] V0latyle:
I would recommend immediately changing the signature back to the 4a. Changing it should not be necessary to pass SafetyNet. Installing the Nexus software at the very least may fail to boot, and at the very worst may brick your device. The update has already unpacked to the alternate slot, so tapping Restart will attempt to reboot to that slot.
[Google Pixel 4a Guides, News, & Discussion] acspdx:
When I first rooted it, I tried passing SafetyNet with an unmodified signature, but it didn't work; that's why I changed it. At any rate, I just reset things in MagiskHide Props Config, but I didn't reboot yet.

What to do about the already-downloaded update? Can I delete it somehow?
[Google Pixel 4a Guides, News, & Discussion] V0latyle:
I don't know of a way to manually wipe the alternate slot. You could dirty flash the current factory image to both slots.

I am passing SafetyNet on my otherwise stock Pixel 5 using USNF + MHPC, no "under the hood" changes, although I have DenyList enabled on banking/DRM apps as well as Play Store.
[Google Pixel 4a Guides, News, & Discussion] acspdx:
Is that what you'd recommend I'd do, to prevent installing an inappropriate update? (And do you have a link that explains how to "dirty flash to both slots"?)
[Google Pixel 4a Guides, News, & Discussion] V0latyle:
OP of this thread, under Update and root factory image, except you'd want to use the --slot=all argument to overwrite both slots.
[Google Pixel 4a Guides, News, & Discussion] acspdx:
That's in the "fastboot update" command?
[Google Pixel 4a Guides, News, & Discussion] V0latyle:
Yes.

fastboot update --skip-reboot --slot=all image-device-buildnumber.zip
[Google Pixel 4a Guides, News, & Discussion] acspdx:
OK, deep breaths... I think I can do this. It's OK that the "master root" file was created on the previous version, right?

Let me make sure I have all the steps correct:

Reboot to bootloader.

% fastboot flash bootloader bootloader-sunfish-s5-0.4-7758095.img

Reboot to bootloader.

% fastboot flash radio radio-sunfish-g7150-00078-211007-b-7801723.img

Reboot to bootloader.

% fastboot update --skip-reboot --slot=all image-sunfish-sq1a.220205.002.zip

[When the update completes, the device will be in fastbootd.]

Reboot to bootloader.

% fastboot boot master_root.img

Does that look right? There's no "fastboot flash boot" step?
[Google Pixel 4a Guides, News, & Discussion] V0latyle:
If you have a newer version of Magisk installed, you can just re-patch the new boot image.

And yes, you can choose to flash the boot image instead:

fastboot flash boot --slot=all <patched boot image>

However, this will prevent OTA updates as there will be no "original" boot image.

The reason why I suggested booting an older patched image is to save the trouble of re-patching the image every time there's an update. Any version of Magisk can use almost any patched image for root, which it can then use to patch the images that are in /boot.
[Google Pixel 4a Guides, News, & Discussion] acspdx:
OK, so doing the Magisk "direct install" or using adb tools to "flash boot" is an either/or thing? It sound like, if I have Magisk 24, that'll be easier.
[Google Pixel 4a Guides, News, & Discussion] V0latyle:
If you want to be able to restore the stock images, yes.

Flashing the patched image to /boot is "permanent", meaning you won't be able to restore the stock image in Magisk, which may be necessary for OTA updates. If you don't intend to update via OTA, this isn't a problem. I personally prefer to dirty flash the factory image every time there's an update.

If you temporarily boot the patched image, Magisk will create a backup of the original boot image when you select Direct Install. This allows restoring the unpatched image.

As far as the Magisk version, I'd recommend the most recent - 25.1. You can use older versions of Magisk, but they won't include the same fixes and updates.
[Google Pixel 4a Guides, News, & Discussion] acspdx:
I'll definitely update Magisk, but I'll wait until after I do this stuff. I don't want to do anything that might require a restart, with that erroneous Nexus update hanging around.
[Google Pixel 4a Guides, News, & Discussion] V0latyle:
Simply restarting won't cause the phone to update. There are only two ways that will cause a reboot to the alternate slot. One is by selecting Restart Now under System Updates; the other is Install to Inactive Slot in Magisk. As long as you don't do either of those, simply commanding a reboot should reboot the device without switching slots.
[Google Pixel 4a Guides, News, & Discussion] acspdx:
Oh! I didn't realize that. So "Restart Now" on the system update panel really means "Restart and Install Update," whereas a normal reboot (say, via the power button) doesn't do anything other than reboot into the existing OS?

If so, that's a relief. I guess I could just ignore it indefinitely unless I really want whatever enhancements are in the update.

(However, having filled up this thread with all my questions, I almost feel an obligation to try the update now so I can let people know how it goes!)
[Google Pixel 4a Guides, News, & Discussion] V0latyle:
By the way...You aren't installing TWRP, are you? I just noticed on my Samsung tablet

Yep

I don't know how to prevent it from downloading updates...but again, I'll recommend returning the device signature to what the device actually is, just in case you make a mistake. It's easy to absentmindedly tap buttons you didn't mean to
[Google Pixel 4a Guides, News, & Discussion] acspdx:
No, everything is stock.

Yes, I did that immediately, and I'll look into the DenyList thing.
[Google Pixel 4a Guides, News, & Discussion] adem_blackv:
Guys/ HEEELP

I cant download factory images from official site

Somebody same?

I want instal android 11
[Google Pixel 4a Guides, News, & Discussion] V0latyle:
Why not? They're available at https://developers.google.com/android/images#sunfish
[Google Pixel 4a Guides, News, & Discussion] ReservedName:
I'm on RQ1A.201205.008 right now and the last update for an app I use says it's incompatible in the app store. I've been able to sideload the app and it runs fine and the devs confirmed there shouldn't be any restriction for my device but I think I need to try taking the ota and going to Android 12. it's been so long since I took an ota and I have root and magisk. is there any reason to think taking the ota will fix that issue? I also need to find the right set of instructions to take an ota but preserve root and data (or preserve data and restore root)