How To Guide [CLOSED] Firmware is out! Get your root on!

Status
Not open for further replies.
Search This thread

V0latyle

Forum Moderator
Staff member
Update 12/15/21: Magisk 23016 incorporates fixes for vbmeta header patching; disabling verity/verification is no longer necessary. Update and root should work as it always has - simply patch and flash the boot image.

Any update method can be used. If you've already disabled verity/verification, simply don't worry about it at next update; no need to re-enable.

I am closing this thread.

On Android 12, boot verification must be disabled in order to run a patched boot image. Unfortunately, if you have never disabled it before, it will require you to wipe data. To be clear:
***************************************************
PERMANENT ROOT CURRENTLY REQUIRES A DATA WIPE.
***************************************************
However, if you don't want to lose your data, you can "live boot" the patched image as long as /vbmeta and /boot are stock. This will allow you to use temporary root. DO NOT attempt to Direct Install Magisk to the boot image.

For subsequent updates, it is imperative that you do not allow the device to boot into system before you have disabled Verified Boot.

What this means: If you sideload the OTA, IMMEDIATELY reboot to bootloader and reflash /vbmeta with --disable-verity and --disable-verification. If you dirty flash the factory image, make sure you add these two switches to the command.

If you fail to do this, and allow the device to boot into system, you WILL have to wipe data to disable it again.

IF YOU ARE ROOTED, DO NOT USE AUTOMATIC UPDATES AS THIS WILL REFLASH /VBMETA WITHOUT DISABLING BOOT VERIFICATION!


Factory Images

OTA Images

Latest Magisk Canary

  1. On your device, enable Developer Options (tap build number 8 times), and enable the OEM Unlocking toggle. Reboot to bootloader:
  2. Code:
    adb reboot bootloader
  3. Unlock bootloader:
    Code:
    fastboot flashing unlock
  4. Download the latest factory image and extract it. Inside, you will find the bootloader image, the radio image, and the image-device-buildnumber.zip. Extract boot.img and vbmeta.img from this zip.
  5. Flash vbmeta:
    Code:
    fastboot flash vbmeta --disable-verity --disable-verification <drag and drop vbmeta.img>
  6. Allow the device to boot into Android. Once you have Magisk installed, copy the boot.img and patch it in Magisk, then copy it back to your PC.
  7. Reboot to bootloader.
  8. Flash patched boot image:
    Code:
    fastboot flash boot <drag and drop magisk_patched-23xxx_xxxxx.img>
  9. Reboot into system.

  1. Download the latest factory image and extract it. Inside, you will find the bootloader image, the radio image, and the image-device-buildnumber.zip. Extract boot.img from this zip.
  2. Reboot to bootloader.
  3. Update bootloader and radio if they are out of date. BE CAREFUL, A MISTAKE CAN BRICK YOUR DEVICE! If you update the bootloader, remember to reboot back to bootloader so that the update reads the correct bootloader version.
  4. Update system:
    Code:
    fastboot update --disable-verity --disable-verification <drag and drop image-device-buildnumber.zip here>
    Note: If you get an error for bootloader/radio version, this means you need to update bootloader and/or radio; go back to step 3.
  5. Allow the device to boot into Android. Copy the boot.img and patch it in Magisk, then copy it back to your PC.
  6. Reboot to bootloader.
  7. Flash patched boot image:
    Code:
    fastboot flash boot <drag and drop magisk_patched-23xxx_xxxxx.img>
  8. Reboot into system.

I personally do not recommend updating via OTA Sideload, as you would have to download and extract the factory zip anyway. AUTOMATIC OTA WILL LOSE ROOT AND REQUIRE A WIPE TO ROOT AGAIN.
  1. Sideload the OTA. When complete, IMMEDIATELY reboot to bootloader.
  2. Reflash vbmeta:
    Code:
    fastboot flash vbmeta --disable-verity --disable-verification <vbmeta.img>
  3. Boot to system and allow the update to complete.
  4. Patch and flash the boot image.

Note: If you run into a bootloader message
failed to load/verify boot images
this means you forgot to disable verity and verification. Reflash vbmeta with the --disable options.

If you run into this recovery message
View attachment 5455805

This means that verity and verification were not disabled before, and a wipe is required to proceed.
 

Attachments

  • 1636492906625.png
    1636492906625.png
    205.7 KB · Views: 5,051
Last edited:

mmarcz

Senior Member
Nov 22, 2006
143
48
So it looks like if you grabbed the Pixel 6 OTA yesterday, you are on 036, and that binary is not yet posted. Please correct if I am wrong. Cant wait to root this thing, non V4A audio is horrible
 
  • Like
Reactions: V0latyle

vandyman

Senior Member
Jul 30, 2012
830
443
S.Jersey
Google Pixel 5
Google Pixel 6
For some reason I can not unlock the bootloader on the P6.

I unlocked the bootloader in the developer options.
Tried "fastboot flashing unlock" and the CMD says waiting for device.

I can transfer files from the pc to the P6 with no problems.
Maybe I need to check on an ADB driver!

EDIT: Google ADB driver was needed.
 
Last edited:

XNine

Senior Member
Dec 28, 2010
638
277
Denver
HTC 10
OnePlus 6
Until a Magisk hide alternative is available, what's the point in rooting for those who don't develop? Most banking apps (among others) won't work.

Not to downplay the significance of the importance of this, just asking.
 
  • Like
Reactions: alek889

vandyman

Senior Member
Jul 30, 2012
830
443
S.Jersey
Google Pixel 5
Google Pixel 6
Until a Magisk hide alternative is available, what's the point in rooting for those who don't develop? Most banking apps (among others) won't work.

Not to downplay the significance of the importance of this, just asking.
Geez, the firmware was just released today. Give the devs some time, there are other devices they need to update their mods on as well.
 

XNine

Senior Member
Dec 28, 2010
638
277
Denver
HTC 10
OnePlus 6
Geez, the firmware was just released today. Give the devs some time, there are other devices they need to update their mods on as well.
Again, I was just asking what would be the benefit of rooting for a daily driver for most people (not devs), not trying to be impatient or rude. From my fairly limited understanding, Hide is pretty essential for a plethora of apps to work while rooted.
 

vandyman

Senior Member
Jul 30, 2012
830
443
S.Jersey
Google Pixel 5
Google Pixel 6
Again, I was just asking what would be the benefit of rooting for a daily driver for most people (not devs), not trying to be impatient or rude. From my fairly limited understanding, Hide is pretty essential for a plethora of apps to work while rooted.
Gotha!
When I had my Pixel 5 rooted I did not need to use hide. I use PNC Bank with no issues. I do not us Gpay, to me it is a waste of time.
I use root for AdAway, Appdash, EX Kernel, and SD Maid.
 

V0latyle

Forum Moderator
Staff member
Until a Magisk hide alternative is available, what's the point in rooting for those who don't develop? Most banking apps (among others) won't work.

Not to downplay the significance of the importance of this, just asking.
Use Magisk 23001. You don't have to use 23011. I believe 23000 stable will also work as it still has MagiskHide if I'm not mistaken and works with Riru.
 

DefeatedSouls

Member
Oct 28, 2021
13
3
Also, I’ve got build number showing SD1A.210817.019.C2. Just got my 6 today and didn’t do the OTA security update as batteries to low. Will this work or nope?
 

V0latyle

Forum Moderator
Staff member
Also, I’ve got build number showing SD1A.210817.019.C2. Just got my 6 today and didn’t do the OTA security update as batteries to low. Will this work or nope?
Patch the image from the factory zip, and boot it instead of flashing it. Then, once booted, use Direct Install in Magisk to patch the boot image already on your phone.
 

file13th

New member
Until a Magisk hide alternative is available, what's the point in rooting for those who don't develop? Most banking apps (among others) won't work.

Not to downplay the significance of the importance of this, just asking.
For instance, I need root to use Adguard in local Proxy mode and third-party VPN service. Also, I use CapitalOne, Amex, Discover, Tdbank and Chase with NO MagiskHide. There were problems with Chase, but later they probably realized it's a crap - to block rooted phones to access the app to pay your card. Some of these apps don't let you to login by a fingerprint, but it's not a big deal to enter the password (you won't forget one at least, haha)
 
  • Like
Reactions: 12paq and Nimueh
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 24
    Update 12/15/21: Magisk 23016 incorporates fixes for vbmeta header patching; disabling verity/verification is no longer necessary. Update and root should work as it always has - simply patch and flash the boot image.

    Any update method can be used. If you've already disabled verity/verification, simply don't worry about it at next update; no need to re-enable.

    I am closing this thread.

    On Android 12, boot verification must be disabled in order to run a patched boot image. Unfortunately, if you have never disabled it before, it will require you to wipe data. To be clear:
    ***************************************************
    PERMANENT ROOT CURRENTLY REQUIRES A DATA WIPE.
    ***************************************************
    However, if you don't want to lose your data, you can "live boot" the patched image as long as /vbmeta and /boot are stock. This will allow you to use temporary root. DO NOT attempt to Direct Install Magisk to the boot image.

    For subsequent updates, it is imperative that you do not allow the device to boot into system before you have disabled Verified Boot.

    What this means: If you sideload the OTA, IMMEDIATELY reboot to bootloader and reflash /vbmeta with --disable-verity and --disable-verification. If you dirty flash the factory image, make sure you add these two switches to the command.

    If you fail to do this, and allow the device to boot into system, you WILL have to wipe data to disable it again.

    IF YOU ARE ROOTED, DO NOT USE AUTOMATIC UPDATES AS THIS WILL REFLASH /VBMETA WITHOUT DISABLING BOOT VERIFICATION!


    Factory Images

    OTA Images

    Latest Magisk Canary

    1. On your device, enable Developer Options (tap build number 8 times), and enable the OEM Unlocking toggle. Reboot to bootloader:
    2. Code:
      adb reboot bootloader
    3. Unlock bootloader:
      Code:
      fastboot flashing unlock
    4. Download the latest factory image and extract it. Inside, you will find the bootloader image, the radio image, and the image-device-buildnumber.zip. Extract boot.img and vbmeta.img from this zip.
    5. Flash vbmeta:
      Code:
      fastboot flash vbmeta --disable-verity --disable-verification <drag and drop vbmeta.img>
    6. Allow the device to boot into Android. Once you have Magisk installed, copy the boot.img and patch it in Magisk, then copy it back to your PC.
    7. Reboot to bootloader.
    8. Flash patched boot image:
      Code:
      fastboot flash boot <drag and drop magisk_patched-23xxx_xxxxx.img>
    9. Reboot into system.

    1. Download the latest factory image and extract it. Inside, you will find the bootloader image, the radio image, and the image-device-buildnumber.zip. Extract boot.img from this zip.
    2. Reboot to bootloader.
    3. Update bootloader and radio if they are out of date. BE CAREFUL, A MISTAKE CAN BRICK YOUR DEVICE! If you update the bootloader, remember to reboot back to bootloader so that the update reads the correct bootloader version.
    4. Update system:
      Code:
      fastboot update --disable-verity --disable-verification <drag and drop image-device-buildnumber.zip here>
      Note: If you get an error for bootloader/radio version, this means you need to update bootloader and/or radio; go back to step 3.
    5. Allow the device to boot into Android. Copy the boot.img and patch it in Magisk, then copy it back to your PC.
    6. Reboot to bootloader.
    7. Flash patched boot image:
      Code:
      fastboot flash boot <drag and drop magisk_patched-23xxx_xxxxx.img>
    8. Reboot into system.

    I personally do not recommend updating via OTA Sideload, as you would have to download and extract the factory zip anyway. AUTOMATIC OTA WILL LOSE ROOT AND REQUIRE A WIPE TO ROOT AGAIN.
    1. Sideload the OTA. When complete, IMMEDIATELY reboot to bootloader.
    2. Reflash vbmeta:
      Code:
      fastboot flash vbmeta --disable-verity --disable-verification <vbmeta.img>
    3. Boot to system and allow the update to complete.
    4. Patch and flash the boot image.

    Note: If you run into a bootloader message
    failed to load/verify boot images
    this means you forgot to disable verity and verification. Reflash vbmeta with the --disable options.

    If you run into this recovery message
    View attachment 5455805

    This means that verity and verification were not disabled before, and a wipe is required to proceed.
    7
    I managed to get the 64mb incremental OTA to install via System Update without having to rewipe data. The basic gist was I restored the stock boot.img in the Magisk app, then used dd to reset the disable flag bits in vbmeta, took the OTA from System Update, then used dd to restore the disable flags before rebooting.

    The downside is that switched me to slot B, which seems to come with compatibility issues with with Magisk on the Pixel 6. I immediately experienced the loss of root that others have described on reboot. It turns out that the Magisk app doesn't detect the change in slot and defaults to slot A.

    The solution to losing root on reboot was to fastboot flash boot_b magisk_patched-23011_xxxxx.img.

    Edit: A solution for the slot detection issue has been merged with mainline Magisk. It should be included in canary build 23014.
    6
    You're a beautiful human being. Thank you!
    My wife thinks so too, although "beautiful" isn't the word she uses
    6
    A new Magisk canary build (23013) was released 13 hours ago (release notes).

    Also, the PR that fixes slot detection on Pixel 6 has been merged, but it unfortunately didn't make it into 23013. Hopefully the wait for 23014 won't be too long.