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

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

Search This thread

amphi66

Senior Member
Dec 17, 2010
1,066
325
PacNW
Google Pixel 6
I'm in the exact position you are hope someone can help.

If you folks don't mind I'll join the party still waiting.
Still a bit confused here.
The plan was to
1. uninstall Magisk using the Restore Images option (no reboot),
2. then install the Android 12 OTA offering from System.
3. Again, no reboot, but power off and boot into Fastboot to flash the Magisk-modified boot image.
⁴. Finally reboot device and reinstall Magisk from the app (or worst case reinstall from the original apk}

Sound reasonable?
 

a1291762

Senior Member
Nov 20, 2012
698
301
yasmar.net
Still a bit confused here.
The plan was to
1. uninstall Magisk using the Restore Images option (no reboot),

This only works if you used Magisk to install (direct). Otherwise Magisk won't have the vanilla image to restore and you will need to fastboot flash the vanilla boot image matching your current version.

2. then install the Android 12 OTA offering from System.

If you can get Google to offer it to you, sure. I cannot, so I used OTA sideload but it's the same thing.

3. Again, no reboot, but power off and boot into Fastboot to flash the Magisk-modified boot image.

Which image? If you're going to grab some random image from the internet you need to make sure it matches your system, including Magisk version. That's why I make my own patched image.

If you use fastboot boot instead of flash you can recover easier if it doesn't work (just reboot, no need to flash something else).

When I did this upgrade, I let the system boot without Magisk once but it should be fine to avoid that.

⁴. Finally reboot device and reinstall Magisk from the app (or worst case reinstall from the original apk}

If you have flashed a patched image there's no need to reflash from Magisk.

Also, Magisk is not going to make a proper (vanilla) backup if you flashed a patched image from fastboot. This makes more sense if you used fastboot boot in the previous step as it will backup the vanilla image and make root permanent.
 
  • Like
Reactions: amphi66

amphi66

Senior Member
Dec 17, 2010
1,066
325
PacNW
Google Pixel 6
This only works if you ...[snip]...
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
 

a1291762

Senior Member
Nov 20, 2012
698
301
yasmar.net
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

If there's no backup, Magisk will no doubt complain. If the backup isn't vanilla the OTA might fail (depends on if it's a full or partial OTA).

Hopefully (if correct) this will help me for future updates and help others who are hesitant about this slightly different process

Yeah that looks fine.

I plan to go back to the old upgrade process (flash the factory image without -w) for the next update. It seemed to be unsafe for this upgrade, although I am fairly sure someone on this thread did do it (accidentally) and the only trouble they had was needing to fully uninstall Magisk and then re-install it again...
 
  • Like
Reactions: amphi66

amphi66

Senior Member
Dec 17, 2010
1,066
325
PacNW
Google Pixel 6
If there's no backup, Magisk will no doubt complain. If the backup isn't vanilla the OTA might fail (depends on if it's a full or partial OTA).



Yeah that looks fine.

I plan to go back to the old upgrade process (flash the factory image without -w) for the next update. It seemed to be unsafe for this upgrade, although I am fairly sure someone on this thread did do it (accidentally) and the only trouble they had was needing to fully uninstall Magisk and then re-install it again...
Makes sense to use that method for a non-major security update versus a whole new release of Android. I'll report on my results
 

amphi66

Senior Member
Dec 17, 2010
1,066
325
PacNW
Google Pixel 6
Makes sense to use that method for a non-major security update versus a whole new release of Android. I'll report on my results
Hmmm .. .. .. all looked like it worked, but when phone rebooted to system it was to Android 11. I had skipped the "restart now" at the end of the update and forced Fastboot.

After the "official" restart it did boot to A12. Now we will see if Magisk root will return ... (time out for this post, edit below added)

Fastboot booting to the patched Magisk file was successful and Magisk properly direct installed, retaining modules. So apparently the system reboot after upgrade is needed, but all-in-all an easy, successful adventure. Overall time about 40 minutes (w/o 'worry time included). I think the benefit of letting System do the update is that it avoids a potential issue w/ apps due to a "dirty flash".

Thank you
 
Last edited:

clocke

Senior Member
Jul 21, 2010
223
8
College Station, TX
If you are comparing stock apple IOS to Android OS, it took me 2 hours to get my mom's brand new iphone in a workable state (no changes to OS). I had my pixel 4a bootloader unlocked, rooted, and data restored in 1.5 hours. Comparing bootloader unlocked and rooted android phones to stock apple phones is like comparing apples and Venus Fly Traps.
 

bobbarker2

Senior Member
Aug 30, 2013
1,525
532
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.
I've never experienced that before. Last time I dealt with temporary root was when I had a device with TWRP... but people get unique situations.
 

bobbarker2

Senior Member
Aug 30, 2013
1,525
532
If you are comparing stock apple IOS to Android OS, it took me 2 hours to get my mom's brand new iphone in a workable state (no changes to OS). I had my pixel 4a bootloader unlocked, rooted, and data restored in 1.5 hours. Comparing bootloader unlocked and rooted android phones to stock apple phones is like comparing apples and Venus Fly Traps.
I was comparing the migration to a new phone with apple to android.

Apple I just hand the carrier the two devices and they become identical. I don't know about app data/logins/etc as I don't use the phones, only done it for other non-tech-savvy people and they were always happy with the results.

Google One keeps unchecking Backup up MMS for some reason on my device. And even when it restored, it restored only some of the apps I downloaded from the play store and actively use, some others that I installed once and uninstalled, and only a few days of SMS/MMS. Like I said, I'm glad I use a third-party app for backing up my stuff.
 

clocke

Senior Member
Jul 21, 2010
223
8
College Station, TX
I was comparing the migration to a new phone with apple to android.

Apple I just hand the carrier the two devices and they become identical. I don't know about app data/logins/etc as I don't use the phones, only done it for other non-tech-savvy people and they were always happy with the results.

Google One keeps unchecking Backup up MMS for some reason on my device. And even when it restored, it restored only some of the apps I downloaded from the play store and actively use, some others that I installed once and uninstalled, and only a few days of SMS/MMS. Like I said, I'm glad I use a third-party app for backing up my stuff.
My mom's did restore everything well, better than android (specifically text messages), but I also keep a backup of mine as well. Other than that, the process, in my experience, was better on android.
 

Typhus_

Senior Member
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!
 

Attachments

  • boot-sunfish-sp1a.211105.002.img
    64 MB · Views: 8
  • magisk_patched_boot-sunfish-sp1a.211105.002.img
    64 MB · Views: 33
  • Like
Reactions: amphi66

Provee

Senior Member
May 31, 2021
85
17
How are you guys able to pass safety net checks? Is magisk hide still available on android 12 versions of magisk?
 

Provee

Senior Member
May 31, 2021
85
17
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
Are you able to pass without magisk hide? I'm just worried since I hear magisk hide isn't going to be available on Android 12.
 

leechxyz1

Member
Jan 10, 2011
22
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?
 

Provee

Senior Member
May 31, 2021
85
17
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?
I don't think you can, the developer of magisk said he is removing the root hiding feature of magisk. I was afraid of this, this means custom rom users and root users won't be able to pass safety net anymore. I hope an alternative solution comes out soon.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 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: