[Stock/Rooted Boot Images] Pixel 4a [NOV 02]

Search This thread

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
12,303
1
14,761
Gothenburg
Google Nexus 4
Nexus 6
My magisk hide (23, no beta) does not work, If I disable it in settings and reopen settings it is unchecked again. The Magisk Hide option in superuser tab isnt there as well.

Any ideas how to solve that?
What version of Magisk and the Magisk app do you have installed (you could simply post a screenshot of the main window of the app)? Lately there's been some reports of similar issues where users have had mismatching versions installed...

And for those that are worried about MagiskHide being replaced with the Deny list in future releases of Magisk: I wouldn't worry. Google still hasn't pulled the plug on us (as they eventually will) and it's still perfectly possible to pass SN. You'll likely need Universal SafetyNet Fix v2.2.0+ though (which isn't yet released as a free upgrade, but should be soon), or similar patches added to the ROM you're using.
 
  • Like
Reactions: kkjb and Provee

leechxyz1

Member
Jan 10, 2011
22
2
What version of Magisk and the Magisk app do you have installed (you could simply post a screenshot of the main window of the app)? Lately there's been some reports of similar issues where users have had mismatching versions installed...

And for those that are worried about MagiskHide being replaced with the Deny list in future releases of Magisk: I wouldn't worry. Google still hasn't pulled the plug on us (as they eventually will) and it's still perfectly possible to pass SN. You'll likely need Universal SafetyNet Fix v2.2.0+ though (which isn't yet released as a free upgrade, but should be soon), or similar patches added to the ROM you're using.

Thanks for helping. Here you can see my version:


photo5195462547896120579.jpg
 

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
12,303
1
14,761
Gothenburg
Google Nexus 4
Nexus 6
Thanks for helping. Here you can see my version:
That was exactly your issue... You have the Canary installed (build 23011), that doesn't have MagiskHide. But, you have the stable app (build 23000). Mismatch.

Either install the Canary app and set stuff up with the Deny list (and USNF if you want to pass SafetyNet), or uninstall Magisk and reinstall the stable release (yes, an uninstall is needed for this downgrade).
 
  • Like
Reactions: kkjb and leechxyz1

leechxyz1

Member
Jan 10, 2011
22
2
That was exactly your issue... You have the Canary installed (build 23011), that doesn't have MagiskHide. But, you have the stable app (build 23000). Mismatch.

Either install the Canary app and set stuff up with the Deny list (and USNF if you want to pass SafetyNet), or uninstall Magisk and reinstall the stable release (yes, an uninstall is needed for this downgrade).
Thank you, this solved the problem. I did set up USNF, but safetynet still fails because the cts profile match fails. Any recommendations what to do to pass this?
 

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
12,303
1
14,761
Gothenburg
Google Nexus 4
Nexus 6
Thank you, this solved the problem. I did set up USNF, but safetynet still fails because the cts profile match fails. Any recommendations what to do to pass this?
Depends on a bunch of things...

Are you using the Magisk Canary release, with Deny list? If so, are you using USNF v2.2.0 (v1.2.0 or lower should in theory also work, but anything else won't work with Zygisk)?
 
  • Like
Reactions: leechxyz1

leechxyz1

Member
Jan 10, 2011
22
2
Depends on a bunch of things...

Are you using the Magisk Canary release, with Deny list? If so, are you using USNF v2.2.0 (v1.2.0 or lower should in theory also work, but anything else won't work with Zygisk)?
Currently I am using the latest github version (v.2.1.1), installed together with latest riru locally as there is no built-in repo browser in latest magisk canary. Where do I get v2.2.0?
 

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
12,303
1
14,761
Gothenburg
Google Nexus 4
Nexus 6
Currently I am using the latest github version (v.2.1.1), installed together with latest riru locally as there is no built-in repo browser in latest magisk canary. Where do I get v2.2.0?
USNF v2.2.0 is currently available as a paid pre-release on @kdrag0n's Patreon. It should soon be released for free though... The v2.1.1 release won't work on the Magisk Canary because of incompatibilities between Riru and Zygisk.
 
  • Like
Reactions: kkjb and leechxyz1

DiamondJohn

Recognized Contributor
Aug 31, 2013
6,074
5,958
Sydney
Thanks for that very detailed explanation. Based on your input I will change my procedure to:

1. Patch A12 Magisk boot.img w/ Magisk 23 and save to PC
2. Uninstall Magisk from phone using the Restore Image option (hopefully that will work) w/o reboot. If it doesn't work (how will I know?) I can Fastboot flash the stock October Security Update Image to match the ROM version using now
3. Install the OTA A12 Update (it was not offered as I have that option off, but when I looked for it it came up as "ready to update"). It is the full 1.6GB image. Power off (no reboot) when complete
4. Reboot to Fastboot then Fastboot Boot my patched Magisk boot.img from Step 1
5. That should reboot me to System with temporary root and I can use Magisk to direct install.

Hopefully (if correct) this will help me for future updates and help others who are hesitant about this slightly different process
I have only upgraded in A11, and the last time I did a wipe (commented line showing a previous dirty falsh/nowipe).Before I started the below, I extracted the boot.img and patched the new boot on my current install, and transferred that back onto my PC. I am running a windows PC and transferred it all to G:\flash_stock\ as having too long a path has previously caused issues with fastboot, especially with spaces in the paths. I ran each step individually and manually waited for it to complete. ie not as a single batch. I download the factory images from the web, not by OTA.

Code:
adb kill-server

PATH=%PATH%;"%SYSTEMROOT%\System32";"C:\Java\x86\Android\android-sdk\platform-tools";
cd /d G:\flash_stock

fastboot devices
fastboot flash bootloader bootloader-sunfish-s5-0.3-7357976.img
fastboot reboot-bootloader

fastboot flash radio radio-sunfish-g7150-00047-210319-b-7220401.img
fastboot reboot-bootloader

REM fastboot --skip-reboot update image-sunfish-rq3a.211001.001.zip
fastboot -w update image-sunfish-rq3a.211001.001.zip

fastboot reboot-bootloader

fastboot devices
fastboot flash boot magisk_patched-23000_ogfF2.img

fastboot reboot

adb kill-server

==========================================================================================
Now, regarding the A12 upgrade, this is where it may be getting a little funky.

This is a strange case that has happened since this morning. I am on the latest A11 with an unlocked bootloader and rooted and running stable Magisk. Not a magisk beta or Alpha test build.

Screenshot_20211110-134603.png
As expected, I have never received stock update notification for Android 11 or even when the first A12 factory image was available. HOWEVER, this morning I turned on my phone and noticed a notification that an updated factory image was available for A12. When I check in system, it clearly offers me the upgrade. Whike still unlocked and rooted.
Screenshot_20211110-135104.png
I have not re-locked the bootloader or downgraded/replaced the boot image with a non magisk one. I NEVER expected to ever get an official upgrade while unlocked and rooted. The one thing that is a little funky about this latest upgrade though, is that it is specific to my region and service provider. Maybe I would never have gotten offered A11 upgrades even If I was running stock.
12.0.0 (SP1A.211105.004, Nov 2021, Telstra, Optus, Vodafone AU).PNG

I'm just gonna wait for the first android 12 custom rom for our device and flash that haha.
Yeah, I havent seen any absolute glowing reviews of the new A12 interface/os. My next move is from stock A11 to maybe custom Bliss A11, before I switch to A12.
 

a1291762

Senior Member
Nov 20, 2012
734
316
yasmar.net
I have also today received an OTA request. The first I have ever seen on this phone.

My installed build number matches the most recent on the download site, unless it's trying to change me from the generic to a carrier-specific build.

How odd...

FWIW: My children run locked so they do normally get offered OTAs.
 

wolfenstein3de

Senior Member
Feb 27, 2014
76
9
Kraków
I have also today received an OTA request. The first I have ever seen on this phone.

My installed build number matches the most recent on the download site, unless it's trying to change me from the generic to a carrier-specific build.

How odd...

FWIW: My children run locked so they do normally get offered OTAs.

I had this OTA request for the 2nd time and I've decided to proceed. It was wrong idea, because I qasn't able to root it and now all I can see are ads! Also no Magisk modules and even my Tasker tasks are out.
 
Last edited:

Typhus_

Senior Member
Hello!

Attached on this post are the stock and Magisk patched boot.img files from Android 12 December update.

Patched with latest Magisk Canary version 23.0.1.5.


Remember, to root your Pixel 4a all you need to do is to connect your device on your PC and:

*Reboot to bootloader*
Code:
adb reboot bootloader

*Erase current boot partition*
Code:
fastboot erase boot

*Flash Magisk Patched boot.img into boot partition*
Code:
fastboot flash boot magisk_patched_boot-sunfish-sq1a.211205.008.img

*Reboot to system*
Code:
fastboot continue


Cheers!
 

Attachments

  • boot-sunfish-sq1a.211205.008.img
    64 MB · Views: 29
  • magisk_patched_boot-sunfish-sq1a.211205.008.img
    64 MB · Views: 45
  • Like
Reactions: betacrypt

@localhost

Member
Aug 3, 2012
7
0
Hello!

Attached on this post are the stock and Magisk patched boot.img files from Android 12 December update.

Patched with latest Magisk Canary version 23.0.1.5.


Remember, to root your Pixel 4a all you need to do is to connect your device on your PC and:

*Reboot to bootloader*
Code:
adb reboot bootloader

*Erase current boot partition*
Code:
fastboot erase boot

*Flash Magisk Patched boot.img into boot partition*
Code:
fastboot flash boot magisk_patched_boot-sunfish-sq1a.211205.008.img

*Reboot to system*
Code:
fastboot continue


Cheers!
I am seeing a boot loop on your attached magisk patched. I get the same file when patching your stock with Magisk. I have verified the same file is created patched from the google factory image.

SHA256 FE929CA9F47691202E9B1BC2616ACF9B3F991BA5AFB5526A9B00FC05A5617BD5

I came from 11 rooted to 12 by OTA. Are you using and working with your patched boot?
 
Last edited:

Typhus_

Senior Member
I am seeing a boot loop on your attached magisk patched. I get the same file when patching your stock with Magisk. I have verified the same file is created patched from the google factory image.

SHA256 FE929CA9F47691202E9B1BC2616ACF9B3F991BA5AFB5526A9B00FC05A5617BD5

I came from 11 rooted to 12 by OTA. Are you using and working with your patched boot?
Yes, obviously.
 

Typhus_

Senior Member
Hello!

Attached on this post are the stock and Magisk patched boot.img files from Android 12 January 2022 update.

Patched with latest Magisk Canary version 23.0.1.6.


Remember, to root your Pixel 4a all you need to do is to connect your device on your PC and:

*Reboot to bootloader*
Code:
adb reboot bootloader

*Erase current boot partition*
Code:
fastboot erase boot

*Flash Magisk Patched boot.img into boot partition*
Code:
fastboot flash boot magisk_patched_boot-sunfish-sq1a.220105.002.img

*Reboot to system*
Code:
fastboot continue


Cheers!
 

Attachments

  • boot-sunfish-sq1a.220105.002.img
    64 MB · Views: 23
  • magisk_patched_boot-sunfish-sq1a.220105.002.img
    64 MB · Views: 54

Typhus_

Senior Member
Hello!

Attached on this post are the stock and Magisk patched boot.img files from Android 12 February 2022 update.

Patched with latest Magisk Canary version 24.1.0.2.


Remember, to root your Pixel 4a all you need to do is to connect your device on your PC and:

*Reboot to bootloader*
Code:
adb reboot bootloader

*Erase current boot partition*
Code:
fastboot erase boot

*Flash Magisk Patched boot.img into boot partition*
Code:
fastboot flash boot magisk_patched_boot-sunfish-sq1a.220205.002.img

*Reboot to system*
Code:
fastboot continue


Cheers!
 

Attachments

  • boot-sunfish-sq1a.220205.002.img
    64 MB · Views: 14
  • magisk_patched_boot-sunfish-sq1a.220205.002.img
    64 MB · Views: 30

Top Liked Posts

  • There are no posts matching your filters.
  • 24
    We have stock factory boot images, I'm only posting the latest builds.
    The rooted android 10 images are rooted with latest Magisk 20.4
    The rooted 11 images are rooted with latest Magisk Canary 4e0a3f5e
    You will still need to install the Magisk Manager to use root. Root will not work without it.
    You HAVE to be bootloader unlocked in order to flash a boot image, meaning these Verizon images are likely useless but google does say it covers extra carriers too. The 11 images seem to be unified in terms of Verizon and other carriers, but do NOT cover

    Make sure to match the boot image build number to your own build number. (Settings/about/android version/build number)

    -

    Android 11 - RP1A - NOV - Stock Factory Boot
    Stock Boot Image - Global - rp1a.201105.002 - All carriers except EMEA, SG, and IN
    AFH

    Old Stock Boot Versions

    Android 11 - RP1A - Oct - Stock Factory Boot
    Stock Boot Image - Global - rp1a.201005.006 - All carriers except EMEA, SG, and IN
    AFH

    Android 11 - RP1A - Sept - Stock Factory Boot
    Stock Boot Image - Global - rp1a.200720.011 - All carriers except EMEA, SG, and IN
    AFH

    Android 11 Beta R3 - RPB3 - Stock Factory Boot
    Stock Boot Image - Global - rpb3.200720.005
    AFH

    Android 10 - QD4A - Aug - Stock Factory Boot
    Stock Boot Image - Global - QD4A.200805.003
    AFH

    Stock Boot Image - VZW/JP - QD4A.200805.001
    AFH

    --


    Android 11 - RP1A - Nov - Rooted Factory Boot
    Rooted Boot Image - Global - rp1a.201105.002 - All carriers except EMEA, SG, and IN
    AFH


    Old Rooted Boot Versions

    Android 11 - RP1A - Oct - Rooted Factory Boot
    Rooted Boot Image - Global - rp1a.201005.006 - All carriers except EMEA, SG, and IN
    AFH

    Android 11 - RP1A - Sept - Rooted Factory Boot
    Rooted Boot Image - Global - rp1a.200720.011 - All carriers except EMEA, SG, and IN
    AFH

    Android 11 Beta R3 - RPB3 - Rooted Factory Boot - Thanks to @Xenanthropy !
    Rooted Boot Image - Global - rpb3.200720.005
    AFH

    Android 10 - QD4A - Aug - Rooted Factory Boot
    Rooted Boot Image - Global - QD4A.200805.003
    AFH

    Rooted Boot Image - VZW/JP - QD4A.200805.001
    AFH

    --


    For root on Android 11, you need the latest Magisk Canary that can be found here

    Steps to proceed:
    Unlock Bootloader
    Ensure you are on latest android version
    Ensure you have the latest versions of adb/fastboot tools
    Download the desired boot image and place where adb tools have access
    Connect phone to pc and open terminal/cmd prompt to where you put that desired boot image

    On the phone:
    Go to Settings/About and scroll to the bottom
    tap 'Build Number' 7 times
    type password/pincode if you have it otherwise don't worry
    Go to Settings/System/Developer Options
    Enable OEM Unlocking
    Enable USB Debugging
    Accept USB Debugging prompt on phone - If this doesn't pop-up by itself, unplug phone and plug back in to pc and then it should pop-up, HAVE to allow access..

    On pc type:
    adb reboot bootloader
    fastboot flashing unlock

    On phone:
    Volume up/down to YES and press power button to proceed with bootloader unlock and wiping data partition
    fastboot reboot

    --

    Flash Boot Image on Bootloader Unlocked Device
    Ensure you are on an android version matching the boot image you want to download(Check Settings/About - Click on Android Version - Look at 'Build Number')
    Download desired boot image on pc and place it where somewhere you have adb/fastboot access
    Connect phone to pc and open terminal/cmd prompt to where you put that desired boot image
    Reboot phone to bootloader

    on pc type:
    fastboot flash boot desired-bootimage-name.img
    fastboot reboot

    --

    To Pass CTS w/root- Courtesy of @quangtran1
    After flashing rooted kernel:
    In Magisk Manager, install the MagiskHide Props Config module;

    Execute command 'su -c props' using a terminal app on the phone;

    Choose 'Force BASIC key attestation' option from menu;

    Choose from fingerprints list, it should default to Pixel 4a, just Confirm
    Reboot
    ?????
    Profit

    --

    If you want or need to make your own rooted boot image
    You need the latest Magisk Manager installed.
    Stable Magisk for Android 10, maybe 11 | Canary Magisk for Android 11 for sure.
    Download the desired Stock Boot Image from here or extract it yourself from Google's Factory Image zip.
    Copy to sdcard of your device.
    Open Magisk Manager, click the first 'Install' button next to 'Magisk is up to date'.
    Click 'Install'.
    Click 'Select and Patch a File'
    Find and select the desired Stock Boot Image.
    You will find the magisk patched, Rooted Boot Image in the sdcard/Download folder titled 'magisk_patched.img'
    Copy that to your pc and flash your pixel 4a from fastboot or copy to the phone and flash with exkm/fkm/etc.
    Reboot
    Install Magisk Manager
    Enjoy being rooted.


    XDA:DevDB Information
    [Stock/Rooted Boot Images] Pixel 4a [NOV 02], Tool/Utility for the Google Pixel 4a

    Contributors
    HolyAngel
    Source Code: https://developers.google.com/android/images#sunfish


    Version Information
    Status: Snapshot

    Created 2020-08-24
    Last Updated 2020-11-02
    6
    Hello!

    Attached on this post are the stock and Magisk patched boot.img files from Android 11 April update.

    Patched with latest Magisk version 22.0.


    Remember, to root your Pixel 4a all you need to do is to connect your device on your PC and:

    *Reboot to bootloader*
    Code:
    adb reboot bootloader

    *Erase current boot partition*
    Code:
    fastboot erase boot

    *Flash Magisk Patched boot.img into boot partition*
    Code:
    fastboot flash boot magisk_patched_boot-sunfish-rq2a.210405.005.img

    *Reboot to system*
    Code:
    fastboot continue


    Cheers!
    6
    Hello!

    Attached on this post are the stock and Magisk patched boot.img files from Android 11 July update.

    Patched with latest Magisk Canary version 23.0.0.1.


    Remember, to root your Pixel 4a all you need to do is to connect your device on your PC and:

    *Reboot to bootloader*
    Code:
    adb reboot bootloader

    *Erase current boot partition*
    Code:
    fastboot erase boot

    *Flash Magisk Patched boot.img into boot partition*
    Code:
    fastboot flash boot magisk_patched_boot-sunfish-rq3a.210705.001.img

    *Reboot to system*
    Code:
    fastboot continue


    Cheers!
    6
    Hello, here are the stock and magisk patched boot.img files for January Update

    Can confirm here that it's working with the latest Magisk release
    5
    Alright, posted with credits. Thanks again! Saves me a bit of time tonight to keep working on a kernel and then TWRP and a ROM after that.

    Speaking of.. Here's a sneak preview :cool: