• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

a1291762

Senior Member
Nov 20, 2012
697
301
yasmar.net
Attached on this post are the stock and Magisk patched boot.img files from Android 12 October update (the very first Android 12 official stable update).

Patched with latest Magisk Canary version 23.0.0.1.

Can you please confirm that you don't need to do the vbmeta thing in order to boot?

This guide here seems to indicate that it's not possible to use a modified boot image unless you also disable boot image verification: https://forum.xda-developers.com/t/guide-update-to-and-re-root-android-12.4345627/
 

Typhus_

Senior Member
Can you please confirm that you don't need to do the vbmeta thing in order to boot?

This guide here seems to indicate that it's not possible to use a modified boot image unless you also disable boot image verification: https://forum.xda-developers.com/t/guide-update-to-and-re-root-android-12.4345627/
Confirm what now!?

Anyway, it's working...if it wasn't I wouldn't share it here.

Pixel 4a (sunfish) is my primary device. I always, like ALWAYS, test this before posting.

Cheers!
 

Attachments

  • Screenshot_20211021-090051.png
    Screenshot_20211021-090051.png
    158.3 KB · Views: 43
  • Screenshot_20211021-090017.png
    Screenshot_20211021-090017.png
    153.7 KB · Views: 44
  • Screenshot_20211021-090108.png
    Screenshot_20211021-090108.png
    100.2 KB · Views: 44

a1291762

Senior Member
Nov 20, 2012
697
301
yasmar.net
I dunno. Maybe it's something affecting the betas only?

I was gonna do the update tonight. I've downloaded all the things but wanted to be sure the "normal" root process would continue to work so I did a bit of googling. I found lots of people having issues, but most of the posts were related to the beta releases.

I'll try a few things while I'm doing the upgrade, just to see what works/does not work :)
 

a1291762

Senior Member
Nov 20, 2012
697
301
yasmar.net
I was gonna do the update tonight. I've downloaded all the things but wanted to be sure the "normal" root process would continue to work.

That other guide I posted (and plenty of other things on the internet) said that "dirty flashing" breaks from Android 11 to Android 12, so I didn't do my usual "factory image without the -w arg" (which is dirty flashing?). Instead, I sideloaded the full OTA package in order to do the upgrade.

Then I used Magisk 23 (release, not canary) to patch the boot.img (which I extracted from the factory image), used fastboot boot patched.img and then used Magisk to install (direct). Rebooting did not give me a bootloop and root has stuck so I guess it's good.

The Settings app is strangely huge (very large fonts and low density display) but everything else is fine. Maybe that's how it's supposed to be? I'm not a fan of the way the quick settings have been changed but I can live with it.
 

ukgoat

New member
Oct 21, 2021
4
1
I'm on Android 11, rooted with Magisk. How can I upgrade to Android 12 without messing something up or losing data? Can I just take the OTA via settings app or do I need to sideload it?
Everyone in Pixel 4A threads seems to be sideloading it.. is taking the OTA via settings -> system update bad?

I'm also skeptical about sideloading because Google's instructions say the Settings app should say "Your system is up to date", while mine says "System update available". Could that be a problem?

This is my first time doing a major Android update with unlocked bootloader / rooted, sorry for newbie questions. :oops:
 

a1291762

Senior Member
Nov 20, 2012
697
301
yasmar.net
Everyone in Pixel 4A threads seems to be sideloading it.. is taking the OTA via settings -> system update bad?

In the entire time I have owned my Pixel 4a I have never once been offered an OTA. I have no idea why.

I used sideload OTA after reading warnings about "dirty flashing", which I think is what happens when you install the factory image without -w.

I'm also skeptical about sideloading because Google's instructions say the Settings app should say "Your system is up to date", while mine says "System update available". Could that be a problem?

If you are offered the OTA and Google sends you the full OTA then it should be fine to install via settings. You'll lose root but you can get it back again afterwards (or possibly do the after update but before reboot "patch other slot" from Magisk).

If you get an incremental OTA it'll fail to apply unless you temporarily or permanently unroot.

My last phone (Mi A2 Lite) always got incremental updates so I'd temporarily unroot, install the OTA and then root the other slot before rebooting.
 

ukgoat

New member
Oct 21, 2021
4
1
In the entire time I have owned my Pixel 4a I have never once been offered an OTA. I have no idea why.

I used sideload OTA after reading warnings about "dirty flashing", which I think is what happens when you install the factory image without -w.



If you are offered the OTA and Google sends you the full OTA then it should be fine to install via settings. You'll lose root but you can get it back again afterwards (or possibly do the after update but before reboot "patch other slot" from Magisk).

If you get an incremental OTA it'll fail to apply unless you temporarily or permanently unroot.

My last phone (Mi A2 Lite) always got incremental updates so I'd temporarily unroot, install the OTA and then root the other slot before rebooting.
Thanks for the answer! The upgrade via OTA was successful.
There were some problems when rerooting though: after flashbooting the patched Magisk image, phone was in a bootloop. Had to flashboot original boot.img, uninstall Magisk app, flashboot patched boot.img again, and then it was fine.
Had to reinstall all Magisk modules too, but now it works. :)
 

amphi66

Senior Member
Dec 17, 2010
1,066
325
PacNW
Google Pixel 6
Thanks for the answer! The upgrade via OTA was successful.
There were some problems when rerooting though: after flashbooting the patched Magisk image, phone was in a bootloop. Had to flashboot original boot.img, uninstall Magisk app, flashboot patched boot.img again, and then it was fine.
Had to reinstall all Magisk modules too, but now it works. :)
Can you list the actual steps you took for success?
 

ukgoat

New member
Oct 21, 2021
4
1
Can you list the actual steps you took for success?
apply OTA update via system settings -> power off -> enter fastboot mode -> fastboot boot flash boot magisk_patched.img -> reboot -> here is when bootloop started happening (couldn't get past lock screen without the phone restarting) -> power off -> enter fastboot mode -> fastboot boot flash boot.img -> reboot -> uninstall Magisk app -> power off -> enter fastboot mode -> fastboot boot flash magisk_patched.img -> reboot -> install Magisk app

If you uninstall Magisk app in the first place (before flashing Magisk-patched boot img), you might be fine and avoid the bootloop altogether.
Maybe the bootloop happened to me because of some specific Magisk module I had installed... I'm not sure. Or maybe you're supposed to uninstall the Magisk app first and I just didn't know about it.
Hope this helps.
 
  • Like
Reactions: amphi66

bobbarker2

Senior Member
Aug 30, 2013
1,525
532
I'm in a weird predicament.. been running A11 rooted for ages, decided to upgrade to A12. Followed all the original steps that people have success with..
1. D/L the full october A12 from Google website.
2. Extracted boot.img, patched it with magisk 23. Disabled my magisk modules.
3. Installed the A12 firmware. Let it boot once with regular boot.img
4. Reboot to bootloader and flashed my patched boot.img.

But now when I run Manager, it is showing as "Installed: N/A" for the boot image and I lost root! I even tried the posted October A12 boot.img in the thread and it is same behavior.

I even tried uninstall magisk manager before flashing boot.img as post above had some problems with that but still no luck.

I see OP says full flash with wipe is necessarry for permanent root, but I'm not even getting temporary.

Edit: Oh well will try full wipe flash and see how it goes.. man why did I think today would be a good day fiddle with my phone :(
 
Last edited:

goofball2k

Senior Member
Oct 5, 2010
1,571
458
Ottawa
I was running Android 11 (June patch) rooted with Magisk. This is what I did to upgrade to 12. Could have been easier to do it some other way but I've tried other ways and something usually ends up breaking and I didn't want to have to wipe and rebuild.

1. Downloaded the Android 12 zip, to get the boot.img file so I could patch it with Magisk
2. Extracted boot.img, copied to phone and patched it with magisk.
3. Copied the magisk patched boot.img file to computer, and put into the same folder as the platform tools.
4. With phone connected to computer, rebooted to fastboot and flashed the stock june boot img (matched the version I was running at the time). Rebooted to Android
5. Updated OTA using Settings -> System -> System Update
6. Once it installed Android 12, and rebooted to Android, I then rebooted back to bootloader, and flashed the magisk patched boot img file.
7. Rebooted to Android 12, ran Magisk, and it was rooted with my old modules not enabled (but still installed).
 

bobbarker2

Senior Member
Aug 30, 2013
1,525
532
I guess it's too late, but next time, try to fastboot boot patched.img and then use Magisk to install (direct).
Flashing the patched.img is the same as magisk install direct.. the latter requires root - which I don't have for some reason.

I'm now on a clean install of A12, flashed patched boot img, Magisk detects that its Installed but nothing detects root except Magisk Manager, where I can do a direct install...

Edit: Weird, I had to have the manager app uninstalled first. So for A12 my steps for successful root were:
1. Create patched boot.img using Magisk 23
2. Uninstall Magisk Manager + Magisk related stuff (Lsposed etc)
3. Flash A12 full wipe, boot into A12 and enable usb debugging
4. Fastboot flash boot patched_boot.img
5. Boot and install Magisk Manager.
 
Last edited:
  • Like
Reactions: amphi66

amphi66

Senior Member
Dec 17, 2010
1,066
325
PacNW
Google Pixel 6
Flashing the patched.img is the same as magisk install direct.. the latter requires root - which I don't have for some reason.

I'm now on a clean install of A12, flashed patched boot img, Magisk detects that its Installed but nothing detects root except Magisk Manager, where I can do a direct install...

Edit: Weird, I had to have the manager app uninstalled first. So for A12 my steps for successful root were:
1. Create patched boot.img using Magisk 23
2. Uninstall Magisk Manager + Magisk related stuff (Lsposed etc)
3. Flash A12, boot into A12 and enable usb debugging
4. Fastboot flash boot patched_boot.img
5. Boot and install Magisk Manager.
Still waiting myself, but ready to proceed. Any thoughts or issues w/ Android 12 on the 4a?
 

bobbarker2

Senior Member
Aug 30, 2013
1,525
532
It's working smooth.. I'm probably behind in the 'hide root' game, but still using Magisk 23, USNP + Magisk Props. Lets me pass safteynet. Just spent an hour getting it configured, apps restored, accounts setup again etc. Google really sucks at restoring your data - I even have a Google One subscription and it only restored 1/4 of my text messages. Good thing I use a 3rd party backup app. Apple definitely has Google beat when it comes to getting a new device or upgrading OS versions.
 
  • Like
Reactions: amphi66

amphi66

Senior Member
Dec 17, 2010
1,066
325
PacNW
Google Pixel 6
It's working smooth.. I'm probably behind in the 'hide root' game, but still using Magisk 23, USNP + Magisk Props. Lets me pass safteynet. Just spent an hour getting it configured, apps restored, accounts setup again etc. Google really sucks at restoring your data - I even have a Google One subscription and it only restored 1/4 of my text messages. Good thing I use a 3rd party backup app. Apple definitely has Google beat when it comes to getting a new device or upgrading OS versions.
I missed the part in your 5 steps where you did a full wipe. I thought uninstalling Magisk and then reflashing afterwards did the trick. That's a shame
 

bobbarker2

Senior Member
Aug 30, 2013
1,525
532
I missed the part in your 5 steps where you did a full wipe. I thought uninstalling Magisk and then reflashing afterwards did the trick. That's a shame
Added for clarity. I'd hazard a guess that doing the OTA sideload will have better success rate.. I always just do full flash without -w by default and didn't think about doing differently when going from 11 to 12.
 

a1291762

Senior Member
Nov 20, 2012
697
301
yasmar.net
Flashing the patched.img is the same as magisk install direct.. the latter requires root - which I don't have for some reason.

fastboot boot patched.img gets you temporary root. Then you use Magisk to make it permanent.
It is the same as fastboot flash in theory, but in practice, it is easier to make a mistake using fastboot flash.
Also, if you use Magisk to flash, it backs up the vanilla boot and you can use Magisk to restore it later.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    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.
    2
    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).
    2
    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.
    1
    Hello!

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

    Patched with latest Magisk Canary version 23.0.1.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-sp1a.211105.002.img

    *Reboot to system*
    Code:
    fastboot continue


    Cheers!
    1
    How are you guys able to pass safety net checks? Is magisk hide still available on android 12 versions of magisk?
    My 4a passes just fine, as it did under A11. I do have some Magisk modules installed: MagiskHide Props Config, Riru, Busybox, Seamless Hosts, & Universal SafetyNet Fix. I don't recall if one specific module did the trick, tho
  • 22
    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: