12

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

 1 year ago
source link: https://forum.xda-developers.com/t/stock-rooted-boot-images-pixel-4a-nov-02.4153249/page-16#post-86992987
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.

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

amphi66

Senior Member
Dec 17, 2010 1,105 PacNW Google Pixel 6
After updating to 220205, I got a bootloop and couldn't boot.
Can anyone boot with 220205 with Magisk?

worked fine. flashed factory image & Magisk-patched boot.img. Goodluck

whalesky

Member
Dec 29, 2010 Osaka
Thank you for your reply.
Some module was doing something wrong. (I don't know what caused it because it all disappeared with adb wait-for-device shell magisk --remove-modules)
Everything worked fine!

a1291762

Senior Member
Nov 20, 2012 yasmar.net
After updating to 220205, I got a bootloop and couldn't boot.
Can anyone boot with 220205 with Magisk?

Yep. sunfish 220205, Magisk 24.1, works fine.

What I do (summarised) is
1 download the factory image
2 extract it and the embedded zip until you have boot.img
3 send that to the phone and use Magisk manager to patch it. Send it back to the pc
4 replace the -w in the flash_all script with --skip-reboot. Add these 3 extra lines to the end.
fastboot reboot-bootloader
sleep 5
fastboot boot patched.img
5 run the script
6 use Magisk manager to install (direct)

Edit: Thanks XDA for hiding the other replies!

Vedarshi

Senior Member
Oct 25, 2012 Mumbai
After updating to 220205, I got a bootloop and couldn't boot.
Can anyone boot with 220205 with Magisk?
EDIT: fixed after downloading firmware and verifying boot image. A12 working with root now.


I faced the same problem, I have tried cleanflashing the build and the following 2 approaches. Still stuck on Google loading bar during boot (adb is accessible but cannot move past this). The only fix is to reflash the build.
I have also tried the following -
Code: 
fastboot boot magisk.img
adb wait-for-device shell magisk --remove-modules
Code: 
fastboot erase boot
fastboot flash boot magisk.img
fastboot reboot
adb wait-for-device shell magisk --remove-modules
Both result in the stuck loading screen
Last edited: Feb 24, 2022

amphi66

Senior Member
Dec 17, 2010 1,105 PacNW Google Pixel 6
Used the same process as always, but flashing March Factory Image failed and phone hung on G__ (would not boot).
Returned to Fastboot and re-flashed the previously successful February Update. This regained use of phone, but root is lost and there is no "Direct Install" for Magisk even after flashing the previously used Feb Magisk-patched bootloader. Any ideas? Thanks

amphi66

Senior Member
Dec 17, 2010 1,105 PacNW Google Pixel 6
Used the same process as always, but flashing March Factory Image failed and phone hung on G__ (would not boot).
Returned to Fastboot and re-flashed the previously successful February Update. This regained use of phone, but root is lost and there is no "Direct Install" for Magisk even after flashing the previously used Feb Magisk-patched bootloader. Any ideas? Thanks

Updated the Feb Magisk to 24.1 (where it was before), reflashed a repatched boot.img and then to phone and all is well. Although Magisk was shown as "not installed" I suspect there was still "stuff" in there as all setting and modules self-returned to their previous settings.

Now, why did the March update flash fail?

a1291762

Senior Member
Nov 20, 2012 yasmar.net
Updated the Feb Magisk to 24.1 (where it was before), reflashed a repatched boot.img and then to phone and all is well. Although Magisk was shown as "not installed" I suspect there was still "stuff" in there as all setting and modules self-returned to their previous settings.
If Magisk says it's not installed, then your boot isn't patched. Maybe the fastboot flash command has flashed the wrong boot partition? (eg. the inactive boot slot?) Doing fastboot boot patched.img should get you temporary root, from which you can use Magisk to make it permanent.
Now, why did the March update flash fail?
For what it's worth, I upgraded Magisk to 24.3 yesterday, and I installed the March OS (220305.012) today. All went smoothly. I use the factory image, remove the -w argument from the flash-all.sh script so that data is not wiped, then I fastboot boot the patched image (which I build with Magisk before the upgrade) and get Magisk to install itself (so it creates an on-phone backup).

I don't bother to boot with the stock boot.img, but if you're having trouble, maybe try letting it boot with the stock image before trying to boot the patched image?

If you can't boot the March update with Magisk enabled, check the version you have, and check the modules you've got. Disabling them all before you upgrade might help? If that works, enable them one at a time until you find the problematic one.
Hello!

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

Patched with latest Magisk Canary version 24.3.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-sp2a.220305.012.img
*Reboot to system*
Code: 
fastboot continue
Cheers!

Attachments

  • boot-sunfish-sp2a.220305.012.img
    64 MB · Views: 22
  • magisk_patched_boot-sunfish-sp2a.220305.012.img
    64 MB · Views: 45

amphi66

Senior Member
Dec 17, 2010 1,105 PacNW Google Pixel 6
Has anyone seen the 12.1 update notification in System Updates yet? After the earlier issue I thought I might try that before re-flashing the Factory Image again.

amphi66

Senior Member
Dec 17, 2010 1,105 PacNW Google Pixel 6
Tried again (new download) using usual method to flash March Factory Image, but again fails with error "does not meet requirements"?
February update reflashes just fine .. .. ...
Sideload of March update went well. So all is done, just do not know why the Factory Image flash failed
Last edited: Mar 16, 2022

graf773

New member
May 14, 2022
Hello
Phone stuck in bootloop
I'm trying to upload a factory image to restore the work, but I get Device Unlock Disabled
Trying to unlock via fastboot.exe flashing unlock I get FAILED (remote: 'flashing unlock is not allowed')
Through Recovery mode > Apply update from ADB > on the computer adb sideload firware.zip gives an error E: Footer is wrong E: signature verification failed
How i can restore my device if the bootloader cannot be unlocked?

HolyAngel

Recognized Dev / Inactive Recognized Contributor
Sep 14, 2008 3,939 13,652 Springfield
Hello
Phone stuck in bootloop
I'm trying to upload a factory image to restore the work, but I get Device Unlock Disabled
Trying to unlock via fastboot.exe flashing unlock I get FAILED (remote: 'flashing unlock is not allowed')
Through Recovery mode > Apply update from ADB > on the computer adb sideload firware.zip gives an error E: Footer is wrong E: signature verification failed
How i can restore my device if the bootloader cannot be unlocked?

Hmm sounds like a partition is corrupted or something.. The first thing I do on any phone is unlock the bootloader so you can always flash whatever. In your case... You could try sideloading the latest ota zip from google and install through recovery, otherwise I'm not too sure. Could be done :/

[deXter]

Senior Member
Aug 23, 2008
Hello!

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

Patched with the latest Magisk v25 released only a few minutes ago!

Cheers,
Dex

Attachments

  • boot-sunfish-sq3a.220605.009.img
    64 MB · Views: 0
  • magisk_25000_patched_boot-sunfish-ota-sq3a.220605.009.img
    64 MB · Views: 0

Top Liked Posts

  • 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 - Nov - Rooted Factory Boot
    Rooted Boot Image - Global - rp1a.201105.002 - All carriers except EMEA, SG, and IN
    AFH


    Old Rooted Boot Versions

    --


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

report

Recommend

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK