[GUIDE] Pixel 4a "sunfish": Unlock Bootloader, Update, Root, Pass SafetyNet

Search This thread
By:
Advanced…
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
10,300
5
18,208
The Heartland of America
Google Pixel 5
Google Pixel 5a
Official updates for this device ended November 2023.

If you are looking for my guide on a different Pixel, find it here:
For best results, use the latest stable Magisk release.
Discussion thread for migration to 24.0+.
Note: Magisk prior to Canary 23016 does not incorporate the necessary fixes for Android 12+.

WARNING: YOU AND YOU ALONE ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS GUIDE IS WRITTEN WITH THE EXPRESS ASSUMPTION THAT YOU ARE FAMILIAR WITH ADB, MAGISK, ANDROID, AND ROOT. IT IS YOUR RESPONSIBILITY TO ENSURE YOU KNOW WHAT YOU ARE DOING.

Prerequisites:

Android Source - Setting up a device for development

Pixel OTA Images
Pixel Factory Images
Magisk Stable, Magisk Canary - Magisk GitHub

  1. Follow these instructions to enable Developer Options and USB Debugging.
  2. Enable OEM Unlocking. If this option is grayed out, unlocking the bootloader is not possible.
  3. Connect your device to your PC, and open a command window in your Platform Tools folder.
  4. Ensure ADB sees your device:
    Code: 
    adb devices
    If you don't see a device, make sure USB Debugging is enabled, reconnect the USB cable, or try a different USB cable.
    If you see "unauthorized", you need to authorize the connection on your device.
    If you see the device without "unauthorized", you're good to go.
  5. Reboot to bootloader:
    Code: 
    adb reboot bootloader
  6. Unlock bootloader: THIS WILL WIPE YOUR DEVICE!
    Code: 
    fastboot flashing unlock
    Select Continue on the device screen.

  1. Install Magisk on your device.
  2. Download the factory zip for your build.
  3. Inside the factory zip is the update zip: "device-image-buildnumber.zip". Open this, and extract boot.img
  4. Copy boot.img to your device.
  5. Patch boot.img with Magisk: "Install" > "Select and Patch a File"
  6. Copy the patched image back to your PC. It will be named "magisk_patched-23xxx_xxxxx.img". Rename this to "master root.img" and retain it for future updates.
  7. Reboot your device to bootloader.
  8. Flash the patched image:
    Code: 
    fastboot flash boot <drag and drop master root.img here>
  9. Reboot to Android. Open Magisk to confirm root - under Magisk at the top, you should see "Installed: <Magisk build number>

  1. Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.
  2. Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
  3. Allow the update to download and install. DO NOT REBOOT WHEN PROMPTED. Open Magisk, tap Install at the top, then Install to inactive slot. Magisk will then reboot your device.
  4. You should now be updated with root.

  1. Download the OTA.
  2. Reboot to recovery and sideload the OTA:
    Code: 
    adb reboot sideload
    Once in recovery:
    Code: 
    adb sideload ota.zip
  3. When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
  4. Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
  5. Reboot to bootloader.
  6. Boot the master root image (See note 1):
    Code: 
    fastboot boot <drag and drop master root.img here>
    Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
  7. Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
  8. Reboot your device. You should now be updated with root.
Note: You can use Payload Dumper to extract the contents of the OTA if you want to manually patch the new boot image. However, I will not cover that in this guide.

Please note that the factory update process expects an updated bootloader and radio. If these are not up to date, the update will fail.
  1. Download the factory zip and extract the contents.
  2. Reboot to bootloader.
  3. Compare bootloader versions between phone screen and bootloader.img build number
    Code: 
    fastboot flash bootloader <drag and drop new bootloader.img here>
    If bootloader is updated, reboot to bootloader.
  4. Compare baseband versions between phone screen and radio.img build number
    Code: 
    fastboot flash radio <drag and drop radio.img here>
    If radio is updated, reboot to bootloader.
  5. Apply update:
    Code: 
    fastboot update --skip-reboot image-codename-buildnumber.zip
    When the update completes, the device will be in fastbootd. Reboot to bootloader.
  6. Boot the master root image (See note 1):
    Code: 
    fastboot boot <drag and drop master root.img here>
    Note: If you prefer, you can manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
  7. Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
  8. Reboot your device. You should now be updated with root.
Note: If you prefer, you can update using the flash-all script included in the factory zip. You will have to copy the script, bootloader image, radio image, and update zip into the Platform Tools folder; you will then have to edit the script to remove the -w option so it doesn't wipe your device.
The scripted commands should look like this:
Code: 
fastboot flash bootloader <bootloader image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot flash radio <radio image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot update  --skip-reboot <image-device-buildnumber.zip>
Once this completes, you can reboot to bootloader and either boot your master patched image, or if you patched the new image, flash it at this time.

PixelFlasher by @badabing2003 is an excellent tool that streamlines the update process - it even patches the boot image for you.
The application essentially automates the ADB interface to make updating and rooting much easier. However, it is STRONGLY recommended that you still learn the "basics" of using ADB.

For instructions, downloads, and support, please refer to the PixelFlasher thread.

  1. Follow the instructions on the Android Flash Tool to update your device. Make sure Lock Bootloader and Wipe Device are UNCHECKED.
  2. When the update completes, the device will be in fastbootd. Reboot to bootloader.
  3. Boot the master root image (See note 1):
    Code: 
    fastboot boot <drag and drop master root.img here>
    Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
  4. Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
  5. Reboot your device. You should now be updated with root.

SafetyNet has been deprecated for the new Play Integrity API. More information here.

In a nutshell, Play Integrity uses the same mechanisms as SafetyNet for the BASIC and DEVICE verdicts, but uses the Trusted Execution Environment to validate those verdicts. TEE does not function on an unlocked bootloader, so legacy SafetyNet solutions will fail.

Before asking any questions, please read this post.
For help passing Play Integrity verdicts, see this thread.

I do not provide support for Magisk or modules. If you need help with Magisk, here is the Magisk General Support thread. For support specifically with Magisk v24+, see this thread.

Points of note:
  • The boot image is NOT the bootloader image. Do not confuse the two - YOU are expected to know the difference. Flashing the wrong image to bootloader could brick your device.
  • While the Magisk app is used for patching the boot image, the app and the patch are separate. This is what you should see in Magisk for functioning root:
    screenshot_20230323-072859-3-png.5870161
  • "Installed" shows the version of patch in the boot image. If this says N/A, you do not have root access - the boot image is not patched, or you have a problem with Magisk.
  • "App" simply shows the version of the app itself.
  • If you do not have a patched master boot image, you will need to download the factory zip if you haven't already, extract the system update inside it, then patch boot.img.
  • If you prefer updating with the factory image, you can also extract and manually patch the boot image if desired.
  • Some Magisk modules, especially those that modify read only partitions like /system, may cause a boot loop after updating. As a general rule, disable these modules before updating. You are responsible for knowing what you have installed, and what modules to disable.


Credits:
Thanks to @badabing2003 , @pndwal , @Displax , @Az Biker , @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!
 
Last edited:
  • Like
  • Love
Reactions: LuChaos, wmdunn, danielfpferreira and 7 others
L

largeruk

Senior Member
Aug 4, 2011
102
6
@V0latyle and all you other helpful people

A few basic questions please. I intend to use your guide to unlock the bootloader and root a Pixel 4a (non-5g) which is currently on stock rom Android 12 SP2A.220405.003. (Auto system updates are currently off in Developer options).
  1. Should I update to the latest June version of Android 12 before doing anything?
  2. Which versions of Magisk and Magisk Manager should I use to root the device?
  3. Which elements of Magisk do I need to activate and which modules do I need to install to pass all SafetyNet checks so I can use UK banking apps?
  4. I've used older versions of Magisk when the repository was built in but am unfamiliar with more recent versions where apparently there is no repo. How does one install modules now?
Many thanks
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
10,300
5
18,208
The Heartland of America
Google Pixel 5
Google Pixel 5a
largeruk said:
@V0latyle and all you other helpful people

A few basic questions please. I intend to use your guide to unlock the bootloader and root a Pixel 4a (non-5g) which is currently on stock rom Android 12 SP2A.220405.003. (Auto system updates are currently off in Developer options).
  1. Should I update to the latest June version of Android 12 before doing anything?
Click to expand...
Click to collapse
You can, but you don't have to. You'll be downloading the factory image so you can patch the boot image anyway, so you might as well take advantage of the newest security update.
largeruk said:
  1. Which versions of Magisk and Magisk Manager should I use to root the device?
Click to expand...
Click to collapse
The two are the same. First, make sure you are only using the authentic Magisk from John Wu's Github, linked in the OP. Secondly, you can use almost any version of Magisk, but Android 12 support wasn't included until Canary 23010, meaning any version prior, including Stable v23.0 may not work properly. Since Public Beta 25.0 is out, just use that.
largeruk said:
  1. Which elements of Magisk do I need to activate and which modules do I need to install to pass all SafetyNet checks so I can use UK banking apps?
Click to expand...
Click to collapse
Ensure Zygisk and DenyList are enabled. Enable DenyList on the Play Store and the apps you want to hide root from; it will not work on system processes. Install the Universal SafetyNet Fix module, linked in the OP. Installing USNF will likely also install MagiskHide Props Config.

Confirm SafetyNet is passing with YASNAC.
largeruk said:
  1. I've used older versions of Magisk when the repository was built in but am unfamiliar with more recent versions where apparently there is no repo. How does one install modules now?
Click to expand...
Click to collapse
Again, the only legitimate source for Magisk is the Magisk Github. Do not use any other version from any other site. The repository continues to be alive and well. If you're talking about the module library, that is no longer included in Magisk, so you have to install the modules manually through Magisk. For more help with this, please see the Magisk help threads, also linked in the OP
 
  • Like
Reactions: largeruk
L

largeruk

Senior Member
Aug 4, 2011
102
6
V0latyle said:
Ensure Zygisk and DenyList are enabled. Enable DenyList on the Play Store and the apps you want to hide root from; it will not work on system processes. Install the Universal SafetyNet Fix module, linked in the OP. Installing USNF will likely also install MagiskHide Props Config.

Confirm SafetyNet is passing with YASNAC.
Click to expand...
Click to collapse
@ V0latyle Thanks very much for your incredibly helpful reply - much appreciated. Just some quick follow-ups for clarity please.
  • Zygisk - I assume that is enabled within Magisk somewhere?
  • DenyList - how exactly do I enable this 'on the Play Store'?
  • When you say DenyList will not work on system processes, I assume you mean things like Google Play Store etc? If so, is the mere installation of Magisk through the process you describe in the op now enough to hide Magisk and root from system processes?
Thanks again for your help and patience.
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
10,300
5
18,208
The Heartland of America
Google Pixel 5
Google Pixel 5a
largeruk said:
@ V0latyle Thanks very much for your incredibly helpful reply - much appreciated. Just some quick follow-ups for clarity please.
  • Zygisk - I assume that is enabled within Magisk somewhere?
  • DenyList - how exactly do I enable this 'on the Play Store'?
  • When you say DenyList will not work on system processes, I assume you mean things like Google Play Store etc? If so, is the mere installation of Magisk through the process you describe in the op now enough to hide Magisk and root from system processes?
Thanks again for your help and patience.
Click to expand...
Click to collapse
Not to be rude but these are questions you should be asking in the Magisk support thread. Also, Google is your friend.

Here's how to get to the settings:
Screenshot_20220614-092537.png

Screenshot_20220614-092617.png

Screenshot_20220614-092646~2.png

Google Play Store is not a system process. Google Play Services on the other hand is, and blocking it in MagiskHide used to be pretty standard for passing SafetyNet attestation.

For further questions please use the Magisk support threads, linked in the OP under "Pass SafetyNet"
 
  • Like
Reactions: EriecTan and largeruk
L

largeruk

Senior Member
Aug 4, 2011
102
6
Apologies for raising questions that, as you rightly point out, should have been posed in other threads. Lesson learnt.

A quick follow-up to my original set of questions. Given that I will be rooting with the latest (June) Magisk-patched factory image, will I need to update the bootloader and radio prior to flashing the patched stock img?

I've compared the versions between phone screen and those contained in the stock factory zip. Both versions appear to be older the current stock one:-
  • bootloader version on phone is c2f2-0.4-8048765 vs bootloader-sunfish-s5-0.4-8351029 on stock image
  • radio version on phone g8150-00123-220122-B-8106568 vs radio-sunfish-g7150-00090-220406-b-8411773.
Thanks again for all your advice. Much appreciated.
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
10,300
5
18,208
The Heartland of America
Google Pixel 5
Google Pixel 5a
largeruk said:
Apologies for raising questions that, as you rightly point out, should have been posed in other threads. Lesson learnt.

A quick follow-up to my original set of questions. Given that I will be rooting with the latest (June) Magisk-patched factory image, will I need to update the bootloader and radio prior to flashing the patched stock img?

I've compared the versions between phone screen and those contained in the stock factory zip. Both versions appear to be older the current stock one:-
  • bootloader version on phone is c2f2-0.4-8048765 vs bootloader-sunfish-s5-0.4-8351029 on stock image
  • radio version on phone g8150-00123-220122-B-8106568 vs radio-sunfish-g7150-00090-220406-b-8411773.
Thanks again for all your advice. Much appreciated.
Click to expand...
Click to collapse
If the build numbers are different, you should update them. Don't worry about the numbers appearing "older"; as far as I can tell it doesn't seem like Google uses consecutive numbers for bootloader and radio.
 
  • Like
Reactions: largeruk
A

acspdx

Member
Dec 2, 2016
23
4
This morning, my rooted Pixel 4a informed me that there was a "Security update available," even though I have Automatic System Updates turned off in Developer Options. And because I changed the device's signature in order to pass SafetyNet, it says it's an update for a Nexus 6P.

Obviously I don't want this update to install — especially since it's for the wrong device! Will it go ahead and download/install the update the next time I restart? (Or did it already download it?!) How can I abort this process?

Screenshot_20220620-093720.png
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
10,300
5
18,208
The Heartland of America
Google Pixel 5
Google Pixel 5a
acspdx said:
This morning, my rooted Pixel 4a informed me that there was a "Security update available," even though I have Automatic System Updates turned off in Developer Options. And because I changed the device's signature in order to pass SafetyNet, it says it's an update for a Nexus 6P.

Obviously I don't want this update to install — especially since it's for the wrong device! Will it go ahead and download/install the update the next time I restart? (Or did it already download it?!) How can I abort this process?

View attachment 5641937
Click to expand...
Click to collapse
I would recommend immediately changing the signature back to the 4a. Changing it should not be necessary to pass SafetyNet. Installing the Nexus software at the very least may fail to boot, and at the very worst may brick your device. The update has already unpacked to the alternate slot, so tapping Restart will attempt to reboot to that slot.
 
A

acspdx

Member
Dec 2, 2016
23
4
V0latyle said:
I would recommend immediately changing the signature back to the 4a. Changing it should not be necessary to pass SafetyNet.
Click to expand...
Click to collapse
When I first rooted it, I tried passing SafetyNet with an unmodified signature, but it didn't work; that's why I changed it. At any rate, I just reset things in MagiskHide Props Config, but I didn't reboot yet.

What to do about the already-downloaded update? Can I delete it somehow?
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
10,300
5
18,208
The Heartland of America
Google Pixel 5
Google Pixel 5a
acspdx said:
When I first rooted it, I tried passing SafetyNet with an unmodified signature, but it didn't work; that's why I changed it. At any rate, I just reset things in MagiskHide Props Config, but I didn't reboot yet.

What to do about the already-downloaded update? Can I delete it somehow?
Click to expand...
Click to collapse
I don't know of a way to manually wipe the alternate slot. You could dirty flash the current factory image to both slots.

I am passing SafetyNet on my otherwise stock Pixel 5 using USNF + MHPC, no "under the hood" changes, although I have DenyList enabled on banking/DRM apps as well as Play Store.
 
A

acspdx

Member
Dec 2, 2016
23
4
OK, deep breaths... I think I can do this. It's OK that the "master root" file was created on the previous version, right?

Let me make sure I have all the steps correct:
  • Reboot to bootloader.
  • % fastboot flash bootloader bootloader-sunfish-s5-0.4-7758095.img
  • Reboot to bootloader.
  • % fastboot flash radio radio-sunfish-g7150-00078-211007-b-7801723.img
  • Reboot to bootloader.
  • % fastboot update --skip-reboot --slot=all image-sunfish-sq1a.220205.002.zip
  • [When the update completes, the device will be in fastbootd.]
  • Reboot to bootloader.
  • % fastboot boot master_root.img
Does that look right? There's no "fastboot flash boot" step?
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
10,300
5
18,208
The Heartland of America
Google Pixel 5
Google Pixel 5a
acspdx said:
OK, deep breaths... I think I can do this. It's OK that the "master root" file was created on the previous version, right?

Let me make sure I have all the steps correct:
  • Reboot to bootloader.
  • % fastboot flash bootloader bootloader-sunfish-s5-0.4-7758095.img
  • Reboot to bootloader.
  • % fastboot flash radio radio-sunfish-g7150-00078-211007-b-7801723.img
  • Reboot to bootloader.
  • % fastboot update --skip-reboot --slot=all image-sunfish-sq1a.220205.002.zip
  • [When the update completes, the device will be in fastbootd.]
  • Reboot to bootloader.
  • % fastboot boot master_root.img
Does that look right? There's no "fastboot flash boot" step?
Click to expand...
Click to collapse
If you have a newer version of Magisk installed, you can just re-patch the new boot image.

And yes, you can choose to flash the boot image instead:
Code: 
fastboot flash boot --slot=all <patched boot image>

However, this will prevent OTA updates as there will be no "original" boot image.

The reason why I suggested booting an older patched image is to save the trouble of re-patching the image every time there's an update. Any version of Magisk can use almost any patched image for root, which it can then use to patch the images that are in /boot.
 
A

acspdx

Member
Dec 2, 2016
23
4
OK, so doing the Magisk "direct install" or using adb tools to "flash boot" is an either/or thing? It sound like, if I have Magisk 24, that'll be easier.
 
You must log in or register to reply here.

Similar threads

Zackptg5
[GUIDE] Unlock/Root/Safetynet for Pixel 4a
Replies
541
Views
88K
soxxoz
soxxoz
T
  • Locked
CalyxOS for Pixel 4a Sunfish
Replies
68
Views
15K
T
TheSayaMan
F
Pixel 4a Debloat
Replies
31
Views
20K
ersnkhrmn
ersnkhrmn
T
  • Locked
[CLOSED]Twrp for pixel 4a Sunfish
Replies
8
Views
9K
Oswald Boelcke
Oswald Boelcke
T
  • Locked
[CLOSED]GrapheneOS for Pixel 4a Sunfish
Replies
25
Views
8K
T
TNSMANI

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 10
    V0latyle
    V0latyle
    Official updates for this device ended November 2023.

    If you are looking for my guide on a different Pixel, find it here:
    For best results, use the latest stable Magisk release.
    Discussion thread for migration to 24.0+.
    Note: Magisk prior to Canary 23016 does not incorporate the necessary fixes for Android 12+.

    WARNING: YOU AND YOU ALONE ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS GUIDE IS WRITTEN WITH THE EXPRESS ASSUMPTION THAT YOU ARE FAMILIAR WITH ADB, MAGISK, ANDROID, AND ROOT. IT IS YOUR RESPONSIBILITY TO ENSURE YOU KNOW WHAT YOU ARE DOING.

    Prerequisites:

    Android Source - Setting up a device for development

    Pixel OTA Images
    Pixel Factory Images
    Magisk Stable, Magisk Canary - Magisk GitHub

    1. Follow these instructions to enable Developer Options and USB Debugging.
    2. Enable OEM Unlocking. If this option is grayed out, unlocking the bootloader is not possible.
    3. Connect your device to your PC, and open a command window in your Platform Tools folder.
    4. Ensure ADB sees your device:
      Code: 
      adb devices
      If you don't see a device, make sure USB Debugging is enabled, reconnect the USB cable, or try a different USB cable.
      If you see "unauthorized", you need to authorize the connection on your device.
      If you see the device without "unauthorized", you're good to go.
    5. Reboot to bootloader:
      Code: 
      adb reboot bootloader
    6. Unlock bootloader: THIS WILL WIPE YOUR DEVICE!
      Code: 
      fastboot flashing unlock
      Select Continue on the device screen.

    1. Install Magisk on your device.
    2. Download the factory zip for your build.
    3. Inside the factory zip is the update zip: "device-image-buildnumber.zip". Open this, and extract boot.img
    4. Copy boot.img to your device.
    5. Patch boot.img with Magisk: "Install" > "Select and Patch a File"
    6. Copy the patched image back to your PC. It will be named "magisk_patched-23xxx_xxxxx.img". Rename this to "master root.img" and retain it for future updates.
    7. Reboot your device to bootloader.
    8. Flash the patched image:
      Code: 
      fastboot flash boot <drag and drop master root.img here>
    9. Reboot to Android. Open Magisk to confirm root - under Magisk at the top, you should see "Installed: <Magisk build number>

    1. Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.
    2. Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
    3. Allow the update to download and install. DO NOT REBOOT WHEN PROMPTED. Open Magisk, tap Install at the top, then Install to inactive slot. Magisk will then reboot your device.
    4. You should now be updated with root.

    1. Download the OTA.
    2. Reboot to recovery and sideload the OTA:
      Code: 
      adb reboot sideload
      Once in recovery:
      Code: 
      adb sideload ota.zip
    3. When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
    4. Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
    5. Reboot to bootloader.
    6. Boot the master root image (See note 1):
      Code: 
      fastboot boot <drag and drop master root.img here>
      Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
    7. Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
    8. Reboot your device. You should now be updated with root.
    Note: You can use Payload Dumper to extract the contents of the OTA if you want to manually patch the new boot image. However, I will not cover that in this guide.

    Please note that the factory update process expects an updated bootloader and radio. If these are not up to date, the update will fail.
    1. Download the factory zip and extract the contents.
    2. Reboot to bootloader.
    3. Compare bootloader versions between phone screen and bootloader.img build number
      Code: 
      fastboot flash bootloader <drag and drop new bootloader.img here>
      If bootloader is updated, reboot to bootloader.
    4. Compare baseband versions between phone screen and radio.img build number
      Code: 
      fastboot flash radio <drag and drop radio.img here>
      If radio is updated, reboot to bootloader.
    5. Apply update:
      Code: 
      fastboot update --skip-reboot image-codename-buildnumber.zip
      When the update completes, the device will be in fastbootd. Reboot to bootloader.
    6. Boot the master root image (See note 1):
      Code: 
      fastboot boot <drag and drop master root.img here>
      Note: If you prefer, you can manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
    7. Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
    8. Reboot your device. You should now be updated with root.
    Note: If you prefer, you can update using the flash-all script included in the factory zip. You will have to copy the script, bootloader image, radio image, and update zip into the Platform Tools folder; you will then have to edit the script to remove the -w option so it doesn't wipe your device.
    The scripted commands should look like this:
    Code: 
    fastboot flash bootloader <bootloader image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot flash radio <radio image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot update  --skip-reboot <image-device-buildnumber.zip>
    Once this completes, you can reboot to bootloader and either boot your master patched image, or if you patched the new image, flash it at this time.

    PixelFlasher by @badabing2003 is an excellent tool that streamlines the update process - it even patches the boot image for you.
    The application essentially automates the ADB interface to make updating and rooting much easier. However, it is STRONGLY recommended that you still learn the "basics" of using ADB.

    For instructions, downloads, and support, please refer to the PixelFlasher thread.

    1. Follow the instructions on the Android Flash Tool to update your device. Make sure Lock Bootloader and Wipe Device are UNCHECKED.
    2. When the update completes, the device will be in fastbootd. Reboot to bootloader.
    3. Boot the master root image (See note 1):
      Code: 
      fastboot boot <drag and drop master root.img here>
      Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
    4. Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
    5. Reboot your device. You should now be updated with root.

    SafetyNet has been deprecated for the new Play Integrity API. More information here.

    In a nutshell, Play Integrity uses the same mechanisms as SafetyNet for the BASIC and DEVICE verdicts, but uses the Trusted Execution Environment to validate those verdicts. TEE does not function on an unlocked bootloader, so legacy SafetyNet solutions will fail.

    Before asking any questions, please read this post.
    For help passing Play Integrity verdicts, see this thread.

    I do not provide support for Magisk or modules. If you need help with Magisk, here is the Magisk General Support thread. For support specifically with Magisk v24+, see this thread.

    Points of note:
    • The boot image is NOT the bootloader image. Do not confuse the two - YOU are expected to know the difference. Flashing the wrong image to bootloader could brick your device.
    • While the Magisk app is used for patching the boot image, the app and the patch are separate. This is what you should see in Magisk for functioning root:
      screenshot_20230323-072859-3-png.5870161
    • "Installed" shows the version of patch in the boot image. If this says N/A, you do not have root access - the boot image is not patched, or you have a problem with Magisk.
    • "App" simply shows the version of the app itself.
    • If you do not have a patched master boot image, you will need to download the factory zip if you haven't already, extract the system update inside it, then patch boot.img.
    • If you prefer updating with the factory image, you can also extract and manually patch the boot image if desired.
    • Some Magisk modules, especially those that modify read only partitions like /system, may cause a boot loop after updating. As a general rule, disable these modules before updating. You are responsible for knowing what you have installed, and what modules to disable.


    Credits:
    Thanks to @badabing2003 , @pndwal , @Displax , @Az Biker , @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!
    View
    2
    V0latyle
    V0latyle
    largeruk said:
    @ V0latyle Thanks very much for your incredibly helpful reply - much appreciated. Just some quick follow-ups for clarity please.
    • Zygisk - I assume that is enabled within Magisk somewhere?
    • DenyList - how exactly do I enable this 'on the Play Store'?
    • When you say DenyList will not work on system processes, I assume you mean things like Google Play Store etc? If so, is the mere installation of Magisk through the process you describe in the op now enough to hide Magisk and root from system processes?
    Thanks again for your help and patience.
    Click to expand...
    Click to collapse
    Not to be rude but these are questions you should be asking in the Magisk support thread. Also, Google is your friend.

    Here's how to get to the settings:
    Screenshot_20220614-092537.png

    Screenshot_20220614-092617.png

    Screenshot_20220614-092646~2.png

    Google Play Store is not a system process. Google Play Services on the other hand is, and blocking it in MagiskHide used to be pretty standard for passing SafetyNet attestation.

    For further questions please use the Magisk support threads, linked in the OP under "Pass SafetyNet"
    View
    2
    X vu S
    X vu S
    V0latyle said:
    I was trying to help you find a simpler option, which is why I recommended the Android Flash Tool

    As long as you've restored the device to stock completely meaning both slots, locking the bootloader is fine.

    So, in this case, use the factory image method in the OP, and make sure you use the --slot=all flag when flashing. You can use the included script, but you have to use the flag for each flashing operation. Here's the long hand:
    fastboot flash bootloader --slot=all <bootloader image> fastboot reboot bootloader fastboot flash radio --slot=all <radio image> fastboot reboot bootloader fastboot update -w --slot=all --skip-reboot image-sunfish-buildnumber.zip

    It should end up in fastbootd mode once completed

    fastboot reboot bootloader fastboot flashing lock fastboot continue

    There might be a simpler way to do this, as I've been doing some reading:
    fastboot flashall -w
    Click to expand...
    Click to collapse
    Hi, thanks for the follow up. I turned off the VPN and after that it worked, I was able to flash and lock. So far, everything appears to be in working order and back to locked bootloader Thanks for all of that, it's very helpful info. Thanks
    View
    1
    V0latyle
    V0latyle
    largeruk said:
    @V0latyle and all you other helpful people

    A few basic questions please. I intend to use your guide to unlock the bootloader and root a Pixel 4a (non-5g) which is currently on stock rom Android 12 SP2A.220405.003. (Auto system updates are currently off in Developer options).
    1. Should I update to the latest June version of Android 12 before doing anything?
    Click to expand...
    Click to collapse
    You can, but you don't have to. You'll be downloading the factory image so you can patch the boot image anyway, so you might as well take advantage of the newest security update.
    largeruk said:
    1. Which versions of Magisk and Magisk Manager should I use to root the device?
    Click to expand...
    Click to collapse
    The two are the same. First, make sure you are only using the authentic Magisk from John Wu's Github, linked in the OP. Secondly, you can use almost any version of Magisk, but Android 12 support wasn't included until Canary 23010, meaning any version prior, including Stable v23.0 may not work properly. Since Public Beta 25.0 is out, just use that.
    largeruk said:
    1. Which elements of Magisk do I need to activate and which modules do I need to install to pass all SafetyNet checks so I can use UK banking apps?
    Click to expand...
    Click to collapse
    Ensure Zygisk and DenyList are enabled. Enable DenyList on the Play Store and the apps you want to hide root from; it will not work on system processes. Install the Universal SafetyNet Fix module, linked in the OP. Installing USNF will likely also install MagiskHide Props Config.

    Confirm SafetyNet is passing with YASNAC.
    largeruk said:
    1. I've used older versions of Magisk when the repository was built in but am unfamiliar with more recent versions where apparently there is no repo. How does one install modules now?
    Click to expand...
    Click to collapse
    Again, the only legitimate source for Magisk is the Magisk Github. Do not use any other version from any other site. The repository continues to be alive and well. If you're talking about the module library, that is no longer included in Magisk, so you have to install the modules manually through Magisk. For more help with this, please see the Magisk help threads, also linked in the OP
    View
    1
    V0latyle
    V0latyle
    ethaneastt said:
    hey idk if you’re still active
    Click to expand...
    Click to collapse
    Easy way to tell:
    1000001126.png

    ethaneastt said:
    but i would really appreciate some help with my google pixel. idk if we can dm somewhere but here is basically the just of things vvv
    Click to expand...
    Click to collapse
    I don't do private support, and there was no need to copy your post into PM. I prefer to keep conversations like this out in the open because they might help someone else with the same question.
    ethaneastt said:
    So basically I haven't used my rooted phone in a few weeks and have just been letting a family member use it. Anyways I get it back today and see that pokemon go is no longer opening and my root access checker is saying that root access is not properly installed on the device. Even though I've been using root access for about 6 months just fine before taking a break. No clue what could've caused this or how to fix this because I have no knowledge on this, I was just able to root it in the first place via a YouTube video.
    Click to expand...
    Click to collapse
    Follow the first post of this guide to re-root your device using the "Initial Root" guide. You'll need to download the factory firmware package that matches your current build: to see what your current build is, either drag the windowshade all the way down and look at the bottom, or go to Settings > About phone > very bottom under Build Number.

    All you should need to do is patch the boot image in Magisk and flash it to your device.

    Do not use any other root solution.

    Make sure you only have one instance of Magisk installed on your device. If the Magisk app was previously hidden, you might still have a stub somewhere.
    View

New posts