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

HolyAngel

Recognized Developer / Inactive Recognized Contrib
Sep 14, 2008
3,927
13,633
263
Springfield
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
 

DJesri13

Senior Member
Apr 29, 2018
138
21
18
Before I mess up my phone, Do I just run "adb reboot bootloader" then "fastboot flashing unlock" then "fastboot flash boot [Android11RootPatch].img" then "fastboot reboot", set up the phone, install magisk?
I haven't rooted in a while and I'm also just a user not a developer.
 
  • Like
Reactions: Zlatty

Xenanthropy

Member
Oct 19, 2018
9
3
0
Hmm, not seeming to work on mine... I tried both flashing my own acquired (and patched with magisk) boot.img as well as your patched boot, and neither seem to want to boot :( when I reboot, it just boots back into fastboot and says "reason: no valid slots to boot" (or something to that effect, i've already patched the original boot.img back) Tried flashing the patched img to both slot A and B, nothing seemed to work. Got the furthest with my own patched image, the google logo would turn to the G and act like it was loading but it continued to "load" for a good 10 minutes so I just gave up.
 

DJesri13

Senior Member
Apr 29, 2018
138
21
18
Hmm, not seeming to work on mine... I tried both flashing my own acquired (and patched with magisk) boot.img as well as your patched boot, and neither seem to want to boot :( when I reboot, it just boots back into fastboot and says "reason: no valid slots to boot" (or something to that effect, i've already patched the original boot.img back) Tried flashing the patched img to both slot A and B, nothing seemed to work. Got the furthest with my own patched image, the google logo would turn to the G and act like it was loading but it continued to "load" for a good 10 minutes so I just gave up.
It also isn't working for me. It won't let me flash the boot image. I also tried my own image patched with magisk.

Edit: I all my attempts to flash the boot partition failed so I can still boot the OS
 
Last edited:

HolyAngel

Recognized Developer / Inactive Recognized Contrib
Sep 14, 2008
3,927
13,633
263
Springfield
@DJesri13
@Xenanthropy

Sounds like possibly not flashing correctly or you weren't already on the latest firmware. You need to be on the firmware matching the boot.img. This is pulled directly from the factory image. Try flashing that first and then this image and see what happens.

For flashing this after flashing same firmware on android 10 for instance:

fastboot flash boot root.boot.sunfish-qd4a.200805.003.img

make sure you're flashing to 'boot', the 3rd word in the command. if you don't put that it won't flash or if you put something other than 'boot' you could have other issues.. Should still be fixable by flashing the factory images.
 

Xenanthropy

Member
Oct 19, 2018
9
3
0
@DJesri13
@Xenanthropy

Sounds like possibly not flashing correctly or you weren't already on the latest firmware. You need to be on the firmware matching the boot.img. This is pulled directly from the factory image. Try flashing that first and then this image and see what happens.

For flashing this after flashing same firmware on android 10 for instance:

fastboot flash boot root.boot.sunfish-qd4a.200805.003.img

make sure you're flashing to 'boot', the 3rd word in the command. if you don't put that it won't flash or if you put something other than 'boot' you could have other issues.. Should still be fixable by flashing the factory images.
I just checked my build version (i'd upgraded to android 11 beta via the ota update by signing up for the beta) and it matches the boot img, RPB3.200720.005.

When I run "fastboot flash boot root.boot.sunfish-rpb3.200720.005.img" it flashes it properly, but upon rebooting it just reboots back into fastboot stating that there was an error. It wouldn't boot on my custom patched boot.img either so i'm not sure what the issue is here.
My current steps were:
1. get phone, immediately unlock bootloader
2. opt-in to android 11 beta, check for updates and upgrade to the beta (rpb3.200720.005)
3. extracted boot.img from the Android 11 beta OTA update, patch it with magisk and attempt to flash (doesn't work, google logo just loads indefinitely)
4. Try flashing your patched boot.img, which results in the phone immediately rebooting and stating an error with the boot slot

If i'm doing something wrong, i'm not sure what it is. I can provide more details if necessary
 

HolyAngel

Recognized Developer / Inactive Recognized Contrib
Sep 14, 2008
3,927
13,633
263
Springfield
I just checked my build version (i'd upgraded to android 11 beta via the ota update by signing up for the beta) and it matches the boot img, RPB3.200720.005.

When I run "fastboot flash boot root.boot.sunfish-rpb3.200720.005.img" it flashes it properly, but upon rebooting it just reboots back into fastboot stating that there was an error. It wouldn't boot on my custom patched boot.img either so i'm not sure what the issue is here.
My current steps were:
1. get phone, immediately unlock bootloader
2. opt-in to android 11 beta, check for updates and upgrade to the beta (rpb3.200720.005)
3. extracted boot.img from the Android 11 beta OTA update, patch it with magisk and attempt to flash (doesn't work, google logo just loads indefinitely)
4. Try flashing your patched boot.img, which results in the phone immediately rebooting and stating an error with the boot slot

If i'm doing something wrong, i'm not sure what it is. I can provide more details if necessary
Ah ok gotcha. it sounds like you did everything right too. Might need a magisk update or something else for that then. May remove the beta root image then..
 

Xenanthropy

Member
Oct 19, 2018
9
3
0
Are you currently running the Android 11 beta? It would be nice to know if someone was able to get the beta rooted properly so we could see what steps they took.
 

DJesri13

Senior Member
Apr 29, 2018
138
21
18
When I try to flash the boot img I get
FAILED (remote: Failed to write to partition Not Found)

Should I try to flash to the boot slot?

EDIT: I flashed and it went through but now it just boots to the bootloader, flashing the stock boot img doesn't fix it. Ill reflash the factory image and again later maybe
 
Last edited:

xxTECRAxx

Senior Member
Apr 11, 2013
54
7
28
When I try to flash the boot img I get
FAILED (remote: Failed to write to partition Not Found)

Should I try to flash to the boot slot?

EDIT: I flashed and it went through but now it just boots to the bootloader, flashing the stock boot img doesn't fix it. Ill reflash the factory image and again later maybe
i am also in the same boat here. unlocked and then fastboot flash boot root.boot.sunfish-qd4a.200805.003.img (to slot a)
it booted to Google logo then restarted into bootloader fastboot mode.
it says no valid slot to boot. see attached image
 

Attachments

DJesri13

Senior Member
Apr 29, 2018
138
21
18
i am also in the same boat here. unlocked and then fastboot flash boot root.boot.sunfish-qd4a.200805.003.img (to slot a)
it booted to Google logo then restarted into bootloader fastboot mode.
it says no valid slot to boot. see attached image
Yep, I was getting the same results using the beta firmware and boot img provided and my own as well as the Augusta firmware with the provided images and my own that I pulled from the factory image and ones I patched.

Anyone know if it is possible to sideload magisk as a zip?
 

xxTECRAxx

Senior Member
Apr 11, 2013
54
7
28
i relfashed the factory image, then dropped magisk into phone with windows explorer. installed magisk then redid the fastboot flash boot root.boot.sunfish-qd4a.200805.003.img and she just booted up. unsure if i have root though

EDIT: i have root!

---------- Post added at 11:23 PM ---------- Previous post was at 11:03 PM ----------

Yep, I was getting the same results using the beta firmware and boot img provided and my own as well as the Augusta firmware with the provided images and my own that I pulled from the factory image and ones I patched.

Anyone know if it is possible to sideload magisk as a zip?
if you're stuck inside fastboot, then reflash the factory image from this file sunfish-qd4a.200805.003-factory-fac7c08d.zip using the included "flash-all.bat". once that completes, boot phone back up and go to settings to enable developer options. then enable USB debugging and finally transfer the magisk.apk into the phone using windows explorer. once all this is done, start over at the top:
  • adb reboot bootloader
  • fastboot flash boot root.boot.sunfish-qd4a.200805.003.img
  • fastboot reboot
  • get paid
 
Last edited:
  • Like
Reactions: Zlatty

DJesri13

Senior Member
Apr 29, 2018
138
21
18
Can someone help me out, I don't understand why I can't boot up after flashing the stock or the batched boot image. My bootloader says slot a and that's the one I flashed to. I tried the beta but right now I'm back on Android 10 and neither will let me boot up.