• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Status
Not open for further replies.
Search This thread
Update from .36 to .37 with update instructions (with one tweak) in OP worked flawlessly. The tweak was editing the flash.all file by replacing '-w' with '--disable-verity --disable-verification' and save. Double click the flash.all file and updated. Booted into system and patched boot image with magisk. Fastboot flashed the patched image and good to go, root, pass SafetyNet, and all modules working.

Enjoy.
 

basily

Senior Member
Just got my P6, and got as far as doing the fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img before realizing that I didn't necessarily want to root right now because of the lack of MagiskHide.

But, after setting up my phone, now I realize that the disabling verity or verification is causing my google pay to not work. Does anyone know if I can reverse this without losing my setup?
 

capntrips

Senior Member
Aug 29, 2020
73
174
OnePlus 6T
Google Pixel 6
Just got my P6, and got as far as doing the fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img before realizing that I didn't necessarily want to root right now because of the lack of MagiskHide.

But, after setting up my phone, now I realize that the disabling verity or verification is causing my google pay to not work. Does anyone know if I can reverse this without losing my setup?

Simply unlocking your bootloader will break Google Pay, but there is a Magisk module called Universal SafetyNet Fix that will allow you to pass SafetyNet and use Google Pay.

Also, while topjohnwu's builds of Magisk have MagiskHide removed, there are a few developers maintaining their own forks with it retained (vvb2060's Magisk alpha, for example). DenyList is working for all of my apps, for whatever that's worth.
 
  • Like
Reactions: basily

basily

Senior Member
Simply unlocking your bootloader will break Google Pay, but there is a Magisk module called Universal SafetyNet Fix that will allow you to pass SafetyNet and use Google Pay.

Also, while topjohnwu's builds of Magisk have MagiskHide removed, there are a few developers maintaining their own forks with it retained (vvb2060's Magisk alpha, for example). DenyList is working for all of my apps, for whatever that's worth.
Thanks. I'll continue down this path when i have a little more time. Root on!

Quick question, what's DenyList? Is that what's in the latest canary magisk instead of magiskhide?
 

jfive74

Senior Member
Apr 15, 2008
361
40
Hey guys. after flashing firmware to return to stock and locking bootloader, device stuck on google logo. If i unlock bootloader and flash vbmeta.img, the device is usable. Can someone help with returning device back to stock? Thanks.
 

earthbend

Member
Feb 21, 2017
49
10
Google Pixel 6
I'm getting a "fastboot: unknown option -- disable-verity" when trying to disable verity, any ideas why? bootloader is unlocked

edit: i put vbmeta and opened CMD from platform tools and it works :)
edit2: somehow even though it said finished, i cant load into android, weirddd
i'm having the same issue, haven't been able to fix it yet. can you explain what you did to make it work in more detail?

edit: god, nevermind. need to use actual windows terminal instead of powershell.
 

basily

Senior Member
Ok, so i got root working, but then went and installed a couple of magisk modules, and one of them must be a problem because it just hung on the Google logo booting up. So i went back to bootloader, reflashed stock (no wipe) but didn't do the whole "flash vbmeta --disable-verity --disable-verification" before it started booting, so it hung on the logo again.

Back into bootloader to do the missing step, but now if i flash the modified boot, it hangs on the logo again.

Am i SOL now? Any way to retain my data and get root back?
 

basily

Senior Member
There are a few variables in there, but assuming the problem is still a Magisk module, see here in the FAQ. If you don't have adb when it hangs, see here for Safe Mode.
Ok, but i flashed stock (no wipe) wouldn't the magisk modules be gone?

I'm able to boot with stock boot after i do "flash vbmeta --disable-verity --disable-verification", but it goes back to hanging if i try to flash the patched boot.

I thought i read something about some state being triggered if i try to boot an unlocked phone before doing "flash vbmeta --disable-verity --disable-verification".

I guess I'll try removing all modules and/or try booting patched boot without flashing...

Thanks
 

basily

Senior Member
There are a few variables in there, but assuming the problem is still a Magisk module, see here in the FAQ. If you don't have adb when it hangs, see here for Safe Mode.
Thanks!!!! I got it working! Flashed patched boot, it hung, booted safe mode, then rebooted and all good!

Now, let's see if I can install a module or two without messing things up again, lol.
 

mermozito

Member
Nov 4, 2013
7
0
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!
  4. Update system:
    Code:
    fastboot update --disable-verity --disable-verification <drag and drop image-device-buildnumber.zip here>
  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 5453983
This means that verity and verification were not disabled before, and a wipe is required to proceed.
hello amigos
how can you update bootloader and radio, for subsequent updates, please ?
 

V0latyle

Forum Moderator
Staff member
So do we freeze the system update app? I got my pixel yesterday and did system updates then rooted. I am waiting for future fixs and need to do my research on updating correctly. Also waiting to see what modules ppl use without bootloops.
Just make sure Automatic Updates are disabled in Developer Options.
 

chuppito

Senior Member
Jun 29, 2014
234
43
Bonjour,
Pour y arriver, avec le nouveau téléphone, j'ai flashé la dernière version SD1A.210817.037 directement depuis le lien Flash sur le site Factory Google. Avec Disable Verity, désactivez la vérification et réinitialisez l'usine cochée.
The root worked the first time (while I couldn't do it at the start). I just hope that on the updates we will not need to delete the data
 
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.