How To Guide [GUIDE] Pixel 6 "oriole": Unlock Bootloader, Update, Root, Pass SafetyNet

Search This thread
By:
Advanced…
G

gazdajezda

Senior Member
Apr 24, 2011
441
85
Ok, thank you! Yes, I do have Automatic System Updates toggle disabled, but ... Now I need to see what are proper Magisk, SNF version files for A13 and then I will update. God I hope root will work and I will be able to restore all my apps with Swift.

My current versions now:
  • Magisk: a468fd94 (25205) with modules:
    • Systemless Hosts 1.0 by Magisk
    • Universal SafetyNet Fix v2.3.1 by kdrag0n
Those working 3 (root, systemless hosts and USNF) functionalities are what I need in new ROM. Others can be restored. I just don't know how to update, with reboot or sahall I download latest A13 Factory Image and flash / root it. If that way, I need to patch both slots with new boot image so new bootloader will 100% be installed, according to your other thread.
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
6,756
2
11,011
The Heartland of America
Google Pixel 5
Google Pixel 5a
gazdajezda said:
Ok, thank you! Yes, I do have Automatic System Updates toggle disabled, but ... Now I need to see what are proper Magisk, SNF version files for A13 and then I will update. God I hope root will work and I will be able to restore all my apps with Swift.
Click to expand...
Click to collapse
You don't have to restore anything. The safest way to upgrade is by sideloading the OTA; you can then re-root after the update is finished.

However, THIS IS EXTREMELY IMPORTANT: READ >>>THIS<<< BEFORE YOU UPDATE TO ANDROID 13.
gazdajezda said:
My current versions now:
  • Magisk: a468fd94 (25205) with modules:
    • Systemless Hosts 1.0 by Magisk
    • Universal SafetyNet Fix v2.3.1 by kdrag0n
Those working 3 (root, systemless hosts and USNF) functionalities are what I need in new ROM. Others can be restored. I just don't know how to update, with reboot or sahall I download latest A13 Factory Image and flash / root it. If that way, I need to patch both slots with new boot image so new bootloader will 100% be installed, according to your other thread.
Click to expand...
Click to collapse
No - you don't patch both slots, the boot image has nothing to do with the bootloader.

This is what you should do just to be safe:
  1. Go into Magisk and tap Uninstall > Restore Images. Reboot.
  2. Follow the instructions in the first post of this thread to sideload the OTA. Use the latest OTA image.
  3. After updating using the OTA, let the device boot into Android and finish its update.
  4. Once the update is finished, sideload the OTA one more time - the OTA method does not update both slots at the same time, so you want to make sure that both bootloader slots get updated.
  5. Once you have updated BOTH slots, follow the instructions under Initial Root to re-root.
I would recommend going to Magisk Stable 25.2 as the canary/alpha builds have been troublesome. I would also recommend updating Universal SafetyNet Fix with this modified USNF module to pass Play Integrity.

If you feel a bit more brave, you can update using the factory images, since you'll need to download those to get the new boot image anyway. The only difference is that before you do anything else, you would want to flash both bootloader slots at the same time:

fastboot flash bootloader --slot=all <path to bootloader image or drag+drop into command line> fastboot reboot bootloader

Verify that the bootloader version is bootloader-raven-slider-1.2-9465321
 
  • Like
Reactions: gazdajezda
G

gazdajezda

Senior Member
Apr 24, 2011
441
85
@V0latyle : thank you for this. I will do OTA sideload. There is just one thing I do not know what is gonna happen. You write:

Go into Magisk and tap Uninstall > Restore Images. Reboot
Click to expand...
Click to collapse

Also, I have been informed by the system that after reboot update of downloaded update will be performed. So, after I will uninstall Magisk and choose Reboot, update will start? And after it finish I do a sideload? Or shall I uninstall Magisk and then boot to recovery directly with:

adb reboot sideload
Click to expand...
Click to collapse

Sorry, if this is lame question, but I prefer to ask than sorry.
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
6,756
2
11,011
The Heartland of America
Google Pixel 5
Google Pixel 5a
gazdajezda said:
@V0latyle : thank you for this. I will do OTA sideload. There is just one thing I do not know what is gonna happen. You write:



Also, I have been informed by the system that after reboot update of downloaded update will be performed. So, after I will uninstall Magisk and choose Reboot, update will start? And after it finish I do a sideload? Or shall I uninstall Magisk and then boot to recovery directly with:



Sorry, if this is lame question, but I prefer to ask than sorry.
Click to expand...
Click to collapse
I forgot that you have an update pending.

Just to be safe, disable the modules in Magisk. You can go ahead and reboot normally and let the automatic OTA do its thing.

Once it's done, you can sideload the OTA, but you'll only need to do this once as the system will have updated one slot.
 
  • Like
Reactions: gazdajezda
G

gazdajezda

Senior Member
Apr 24, 2011
441
85
So, I just disable Magisk modules and reboot for pending update do the work? Or shall I also uninstall Magisk, switch images before reboot?

And if system boots into some strange mode (as last time) I can then just do a sideload or in worst case flash/wipe (as last time)?

Ok, tommorow after work I will read all this again and do the process (I need a working phone on work, so I will do that tommorow - it's getting late here). Thank you for all!
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
6,756
2
11,011
The Heartland of America
Google Pixel 5
Google Pixel 5a
gazdajezda said:
So, I just disable Magisk modules and reboot for pending update do the work? Or shall I also uninstall Magisk, switch images before reboot?
Click to expand...
Click to collapse
Just disable modules. The OTA overwrites the boot image in the other slot
gazdajezda said:
And if system boots into some strange mode (as last time) I can then just do a sideload or in worst case flash/wipe (as last time)?
Click to expand...
Click to collapse
Strange mode? What do you mean?
gazdajezda said:
Ok, tomorrow after work I will read all this again and do the process (I need a working phone on work, so I will do that tommorow - it's getting late here). Thank you for all!
Click to expand...
Click to collapse
Honestly the best way to update, I think, would be using the factory method via Pixel Flasher. It'll update both bootloader slots at the beginning so at the very least that will prevent a bootloader brick.

Make sure you are using Platform Tools 33.0.3. Do not use 34.0+ yet.
 
S

Svensemann666

Member
Jan 9, 2015
9
2
IF anyone is struggeling to get root on his Pixel 6 on the actual DP Android 14 : bluejay_beta-upp2
Use the Pre Build from Magisk 25.2:
https://easyupload.io/u0hpgk or get offical from
https://github.com/topjohnwu/Magisk/actions/runs/4373376674#artifacts

Use the boot.img from the Pixel 7, the one i uploaded is already patched:
https://easyupload.io/4rc9lh
or get offical from https://developer.android.com/about/versions/14/download

Also dont forget to install Displax Safetynet Mod 3.0 by Displax
github.com

GitHub - Displax/safetynet-fix at integrity

Google SafetyNet attestation workarounds for Magisk - GitHub - Displax/safetynet-fix at integrity
github.com github.com
Greetz :)
 
Last edited:
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
6,756
2
11,011
The Heartland of America
Google Pixel 5
Google Pixel 5a
Svensemann666 said:
IF anyone is struggeling to get root on his Pixel 6 on the actual DP Android 14 : bluejay_beta-upp2
Use the Pre Build from Magisk 25.2:
https://easyupload.io/u0hpgk
Use the boot.img from the Pixel 7, the one i uploaded is already patched:
https://easyupload.io/4rc9lh
Also dont forget to install Displax Safetynet Mod 3.0 by Displax
github.com

GitHub - Displax/safetynet-fix at integrity

Google SafetyNet attestation workarounds for Magisk - GitHub - Displax/safetynet-fix at integrity
github.com github.com
Greetz :)
Click to expand...
Click to collapse
What is the "Pre build" you posted?

I strongly advise to ONLY download Magisk from the offical Github repo.
 
S

Svensemann666

Member
Jan 9, 2015
9
2
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
6,756
2
11,011
The Heartland of America
Google Pixel 5
Google Pixel 5a
gazdajezda said:
I did it & all it happened was just a normal ordinary reboot, hehe. Still on A12 (june 2022 release). This phone is cursed... Do not understand nothing, really.
Click to expand...
Click to collapse
Odd. This is probably because the Automatic System Updates toggle in Developer Options was turned off.

Go ahead and use Pixel Flasher + the factory update image.
 
G

gazdajezda

Senior Member
Apr 24, 2011
441
85
For now I will leave it as it is. Everything works. Update will come in play on weekend, when I have a time. For now, this is it 😀
 
  • Like
Reactions: V0latyle
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
6,756
2
11,011
The Heartland of America
Google Pixel 5
Google Pixel 5a
darkerm said:
I just got a New Pixel 6 today. This is the version its currently running and there is a New Android 13 update.
what should I do to I can Root and install custom ROM? Please Help
Click to expand...
Click to collapse
Please post your question only once, per the Forum Rules:
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
  • You can bump your unanswered question once every 24 hours
  • Duplicate threads and posts will be removed
  • Always post in an existing thread if a topic already exists, before creating a new thread.
  • Use our search function to find the best forum for your device.
  • Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
  • Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
Click to expand...
Click to collapse
Instructions for updating and rooting your device are in the first post of this thread.
 
  • Sad
Reactions: darkerm
darkerm

darkerm

Senior Member
Feb 29, 2012
647
72
Dhaka
OnePlus One
Xiaomi Redmi Note 5 / 5 Plus
Which version do I need to flash to make sure I can Downgrade to any older Android version? Please help
1680192112906.png
 

Attachments

  • Screenshot_20230330-214218.png
    Screenshot_20230330-214218.png
    150.1 KB · Views: 14
  • Screenshot_20230330-214301.png
    Screenshot_20230330-214301.png
    199 KB · Views: 15
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
6,756
2
11,011
The Heartland of America
Google Pixel 5
Google Pixel 5a
darkerm said:
Which version do I need to flash to make sure I can Downgrade to any older Android version? Please help
View attachment 5876405
Click to expand...
Click to collapse
I don't think you understand this whole anti-rollback thing. Once you upgrade to Android 13, you will not be able to downgrade to a previous version. You can force an Android 12 factory image to install on the Android 13 bootloader but it will not work properly. I'm not sure how this applies to custom ROMs.

The difference between the versions you pictured is only in the baseband (modem firmware). Everything else is the same.
 
darkerm

darkerm

Senior Member
Feb 29, 2012
647
72
Dhaka
OnePlus One
Xiaomi Redmi Note 5 / 5 Plus
V0latyle said:
I don't think you understand this whole anti-rollback thing. Once you upgrade to Android 13, you will not be able to downgrade to a previous version. You can force an Android 12 factory image to install on the Android 13 bootloader but it will not work properly. I'm not sure how this applies to custom ROMs.

The difference between the versions you pictured is only in the baseband (modem firmware). Everything else is the same.
Click to expand...
Click to collapse
so after I update to any A13 ROM I wont be able to go back to any older ROM at all?
I just unlocked the Bootloader and I am in A12 stock. Should I just go and update the OTA to A13? If I do so can I root A13?
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
6,756
2
11,011
The Heartland of America
Google Pixel 5
Google Pixel 5a
darkerm said:
so after I update to any A13 ROM I wont be able to go back to any older ROM at all?
Click to expand...
Click to collapse
It sounds to me like you didn't do some necessary reading.

Please go back and read the original post in the warning thread where you first posted.

Remember that before you ask a question in a thread, you should read the WHOLE original post. Many of the questions you're asking have been answered, and it's rude to ask when the answers are readily available.

Once the official Android 13 update completes, the bootloader anti-rollback protection will be enabled, meaning you will not be able to flash an older bootloader version. Since the factory update images check for bootloader and baseband versions, the only way to install an Android 12 image is with the --force flag, but the official Android 12 release does not work properly on the Android 13 bootloader.

Again, I do not know how this affects custom ROMs.
darkerm said:
I just unlocked the Bootloader and I am in A12 stock. Should I just go and update the OTA to A13?
Click to expand...
Click to collapse
That is up to you.
darkerm said:
If I do so can I root A13?
Click to expand...
Click to collapse
Yes, the instructions in the first post of this thread tell you how to do this.
 
  • Like
Reactions: darkerm
A

armourer1

Member
Feb 15, 2009
20
2
So, sorry I am lost and I think it would be better to ask then lose my phone -:)

I have reading various methods to update and here my state now:
I am on Android 12, May 5 2022 (SP2A.220505.002) Canadian Version of Pixel 6
I have the latest Canary Magick installed: 25210, both app and boot image pathed.

So, what is my best route of update as I understand it:

1. open Magisk, tap Uninstall, then Restore Images.
2. reboot, I will lose my root - I undertand
3. Check for OTA and install it
4. Check what version I have after OTA (I hope it will be latest 13) and donload the same image
5. Extract bootloader and "fastboot flash bootloader --slot=all xxx"
6. Go the regular root path from the first post



Thanks a lot for any help!!!
 
H

Homeboy76

Recognized Contributor
Aug 24, 2012
3,883
2,328
Google Pixel XL
Google Pixel 7 Pro
armourer1 said:
So, sorry I am lost and I think it would be better to ask then lose my phone -:)

I have reading various methods to update and here my state now:
I am on Android 12, May 5 2022 (SP2A.220505.002) Canadian Version of Pixel 6
I have the latest Canary Magick installed: 25210, both app and boot image pathed.

So, what is my best route of update as I understand it:

1. open Magisk, tap Uninstall, then Restore Images.
2. reboot, I will lose my root - I undertand
3. Check for OTA and install it
4. Check what version I have after OTA (I hope it will be latest 13) and donload the same image
5. Extract bootloader and "fastboot flash bootloader --slot=all xxx"
6. Go the regular root path from the first post



Thanks a lot for any help!!!
Click to expand...
Click to collapse
If you want to root your phone after updating, follow one of the following sets of instructions in the OP

Spoiler: Update and Root Factory Image

Spoiler: Update and Root using PixelFlasher <<RECOMMENDED FOR NOVICES>>

Spoiler: Update and Root using the Android Flash Tool
 
  • Like
Reactions: V0latyle and badabing2003
You must log in or register to reply here.

Similar threads

H
How To Guide [Guide] Root Pixel 6 with Magisk + Unlock Bootloader + Pass SafetyNet + More
Replies
630
Views
112K
H
Homeboy76
L
How To Guide Sim unlock tmobile pixel 6
Replies
177
Views
55K
illegalnature
illegalnature
H
How To Guide Converting Japanese Pixel 6 to Global version
Replies
146
Views
53K
kevin3688
kevin3688
Typhus_
Themes / Apps / Mods [MOD][MAGISK][ANDROID 12] Addon Features for Pixel Devices - Pixel 6 Thread
Replies
368
Views
58K
mobile_sensei
mobile_sensei
MikeChannon
  • Sticky
General Google Pixel 6
Replies
43
Views
39K
cmfCyangenModteam
cmfCyangenModteam

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 3
    V0latyle
    V0latyle
    [email protected] said:
    Thanks for replying here...
    So long story short...
    I need to unlock the bootloader its obvious... And I need a root...
    Are these commands are just enough?
    1. adb reboot bootloader
    2. fastboot flashing unlock
    3. Now I have downloaded ota and also factory image what exactly I have to do after unlocking the bootloader.... Patching by masgisk boot.img from factory zip>update.zip to device and pc and then flash?
    4. Now if yes, then what I have to do? And where and why I use the active slots commands?
    Click to expand...
    Click to collapse
    You don't need to mess with the slots, unless the device is on Android 12, in which case you'll want to flash the new bootloader to both slots.

    Again, the instructions on updating and rooting your device are in the first post of this thread. Go back and read it, please. If you have questions about something specific, I'll be happy to help, but I took the time to write an exhaustive guide, and I would appreciate it if you used it instead of asking me to give you answers that are already readily available.
    View
    1
    Lughnasadh
    Lughnasadh
    [email protected] said:
    So I m also new to Pixel 6 and I dont know how many OTA I have taken including this month , currently I m on tq2a.230505.002 Build , I havent unlocked the bootloader yet, if its useless and I m gonna brick my device so its no use, please help me out too.. What I need to do ?

    🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑

    ***Note: THIS IS NOT A ROOT GUIDE. For...
    forum.xda-developers.com forum.xda-developers.com
    Click to expand...
    Click to collapse
    Read the OP in this thread.
    View
  • 51
    V0latyle
    V0latyle
    ⚠️⚠️⚠️WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST! ⚠️⚠️⚠️

    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.

    However, @Displax has modified the original Universal SafetyNet Fix by kdrag0n; his mod is able to force basic attestation instead of hardware, meaning that the device will pass BASIC and DEVICE integrity.

    Mod available here. Do not use MagiskHide Props Config with this mod.

    This is my configuration that is passing Safety Net. I will not provide instructions on how to accomplish this. Attempt at your own risk.

    Zygisk + DenyList enabled
    All subcomponents of these apps hidden under DenyList:
    • Google Play Store
    • GPay
    • Any banking/financial apps
    • Any DRM media apps
    Modules:
    • Universal SafetyNet Fix 2.3.1 Mod - XDA post
    To check SafetyNet status:
    To check Play Integrity status:
    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
    7
    V0latyle
    V0latyle
    Magisk Canary was updated to 23016 last night. This includes a fix for the vbmeta header issue, meaning that disabling verity/verification should no longer be required, and we should be able to root as we did before. This needs testing, make sure you back up your data and photos before you do this!

    Additionally, for the Pixel 6 and 6 Pro, fstab will now load from /system/etc which should fix the root issue many of you were having.

    Q: "If verity/verification are disabled, do I need to enable them now?"
    A: No. The only thing you have to do is update to Magisk 23016.
    Q: "Will enabling verity/verification wipe my data?"
    A: No.

    I will be updating the OP to reflect this.
    View
    5
    capntrips
    capntrips
    Magisk 24306 (release notes) is now available on the canary channel, and I can confirm that the installation to the inactive slot OTA method is working for the April update.
    View
    5
    soodz
    soodz
    V0latyle said:
    Interesting. How did you command the reboot?

    When I tried to update this way on my wife's 5a, it bootlooped back to the original slot.
    Click to expand...
    Click to collapse
    I always follow these steps once I know the OTA is available:

    1. Open Magisk and select 'Uninstall Magisk -> Restore Images'
    2. Open Settings and Download/Install OTA *DO NOT REBOOT*
    3. Go back to Magisk and select 'Install -> Install to Inactive Slot (After OTA)' *DO NOT REBOOT*
    4. Go back to Settings and 'Reboot' to finalize the OTA
    View
    5
    capntrips
    capntrips
    KedarWolf said:
    So, if I use this tool after rooting OTA updates will work and I'll still have root?

    Edit: And can you explain more clearly the process on how to do this?
    Click to expand...
    Click to collapse

    No, the tool does nothing to maintain root. It simply allows you to take the OTA. You will still need to reboot into fastboot and flash or boot from a patched boot image.

    The steps would be:
    1. Restore boot in the Magisk app
    2. Restore vbmeta in Vbmeta Patcher
    3. Take the OTA in System Updater
    4. Patch vbmeta in Vbmeta Patcher
    5. Patch the new boot image in the Magisk app and copy it to your computer
    6. Reboot into fastboot
    7. Boot from the new patched boot image
    8. Direct Install Magisk in the Magisk App
    As I noted the quote post, this process should be considered experimental until it has been more thoroughly tested. You should consider backing up any critical data before attempting it, in case something goes wrong.

    I'm working on another tool to make it a bit easier to acquire the new boot image in step 5, but that will likely be a few days. Hopefully we'll be able to install Magisk to the inactive slot on Pixel devices again in the future, which would consolidate steps 5-8.
    View

New posts