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

Status
Not open for further replies.
Search This thread

razercortex

Senior Member
Apr 8, 2018
229
77
If this doesn't show Google's hostility towards root, I don't know what does, seeing as it now requires you to have a PC to disable verified boot every time. People are buying this phone as an alternative for the Oneplus 9 Pro, but at least with the latter you only have to sideload the full OTA and patch it using A/B.
 
  • Like
Reactions: galaxys

js042507

Senior Member
Jan 7, 2011
618
249
Google Pixel 6 Pro
If this doesn't show Google's hostility towards root, I don't know what does, seeing as it now requires you to have a PC to disable verified boot every time. People are buying this phone as an alternative for the Oneplus 9 Pro, but at least with the latter you only have to sideload the full OTA and patch it using A/B.
It IS absolutely ridiculous. I miss being able to easily update from my phone and maintain root. Still never going back to OnePlus though. And I believe yes, it doesn't require that. But they all will when they're on Android 12. It's the OS that required this new method.
 

mko000

Senior Member
Jul 27, 2011
454
220
Google Nexus 4
Huawei Nexus 6P
If this doesn't show Google's hostility towards root, I don't know what does, seeing as it now requires you to have a PC to disable verified boot every time. People are buying this phone as an alternative for the Oneplus 9 Pro, but at least with the latter you only have to sideload the full OTA and patch it using A/B.
I believe that the intention behind all these changes Google made is better device security and not anti-root.
 

razercortex

Senior Member
Apr 8, 2018
229
77
Counter question: If Google was so anti-root, why wouldn't they simply prevent unlocking the bootloader like other phone makers?

They are making a step in that direction, whether they realize it or not. For example, topjohnwu left the scene to work with them, and even though it's a green light so far, eventually Google and the project will clash.
 
Last edited:

razercortex

Senior Member
Apr 8, 2018
229
77
It IS absolutely ridiculous. I miss being able to easily update from my phone and maintain root. Still never going back to OnePlus though. And I believe yes, it doesn't require that. But they all will when they're on Android 12. It's the OS that required this new method.
Yeah, OnePlus still has problems with OOS 12. Still though, they haven't changed the process to disable verified boot, it's nearly identical to OOS 11. The only problem is the bugs, which I'm sure Google has done a better job with on the Pixel 6 series.
 

js042507

Senior Member
Jan 7, 2011
618
249
Google Pixel 6 Pro
Yeah, OnePlus still has problems with OOS 12. Still though, they haven't changed the process to disable verified boot, it's nearly identical to OOS 11. The only problem is the bugs, which I'm sure Google has done a better job with on the Pixel 6 series.
Don't get me wrong. OnePlus is still great I think. I came from the McLaren to the Pixel 6 Pro. I just prefer stock Android and updates right away. Plus the camera obviously in the Google phones is stellar.
 
  • Like
Reactions: razercortex

banshee28

Senior Member
Aug 31, 2010
193
30
Well, I had this working for a while, added some modules and tweaks then on reboot could never get to boot again. I have fastboot available and tried both flashing the original boot.img and even starting over with vbmeta.img but even after flashing, it still boots to the google logo and back to factory recovery/fastboot menus.
 

roirraW "edor" ehT

Forum Moderator
Staff member
Nice! So I think this worked perfectly so far. No issues. I do however notice a message when the bootloader boots that its unlocked, but it still proceeds to boot. I have Magisk installed and superuser access seems to be working.
That's completely normal and has been like that from the Pixel 1 or before. Other OEMs do similar (maybe some don't?) if you have the bootloader unlocked. I don't like it as it's basically advertising (if I let someone take my phone) that it's easier for them to hack, but I've never lost my phone or had one stolen, so oh well.
 
  • Like
Reactions: Lughnasadh

banshee28

Senior Member
Aug 31, 2010
193
30
That's completely normal and has been like that from the Pixel 1 or before. Other OEMs do similar (maybe some don't?) if you have the bootloader unlocked. I don't like it as it's basically advertising (if I let someone take my phone) that it's easier for them to hack, but I've never lost my phone or had one stolen, so oh well.
Thanks, my last G phone was Nexus, lol. Was not up to date on Pixel, but am now!
 
  • Love
Reactions: roirraW "edor" ehT

V0latyle

Forum Moderator
Staff member
Magisk Canary 23016 has been released; this incorporates vbmeta header fixes, meaning disabling verity/verification should no longer be necessary.

Additionally, this version also incorporates some fstab fixes for the Pixel 6 / 6 Pro.

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.

OP has been updated.
 
Last edited:

banshee28

Senior Member
Aug 31, 2010
193
30
So i originally had this setup and working then managed to get stuck in this bootloop!!

I originally flashed Nov update, but at this point would like to start all over! I can wipe all data, and start with the Dec update since Mgisk now should be working. Since I cant seem to use adb or the Andorid Flash tool, is my only option fastboot commands and should I do the same steps as before just with the Dec images?

** Edit: Used the flash tool and got the Dec image installed now! Will work on rooting again with the latest Magisk and flashing boot.img.
 
Last edited:
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 45
    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
    1636658711744.png

    This means that verity and verification were not disabled before, and a wipe is required to proceed.
    11
    So, what exactly are then the steps to flash the OTA without losing root and without wiping everything again? :D
    Currently I'm with Magisk Alpha (Safetynet passed) on .015 firmware.
    1. Download both the OTA AND the factory zips.
    2. Extract boot.img and vbmeta.img from the factory zip.
    3. Patch the new boot.img in Magisk and copy it back to your PC.
    4. Reboot into recovery and sideload the OTA
    Code:
    adb reboot sideload
    adb sideload ota.zip
    5. When the update completes, you'll still be in recovery. DO NOT REBOOT. Select "Enter fastboot"
    6. In fastboot, flash vbmeta:
    Code:
    fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
    7. Now flash boot:
    Code:
    fastboot flash boot magisk_patched-23xxx_xxxxx.img
    8. Reboot, you should come into the new update with root.

    Remember: You get ONE CHANCE, and ONE CHANCE ONLY to flash /vbmeta while in fastboot. If you do something wrong, you will either have to wipe data, or go without root.
    7
    015 rooted to 036 no wipe update
    1. Download the factory image.
    2. Copy boot.img to your phone. Patch with Magisk.
    3. Edit Flash-all.bat
      remove -w and add --disable
      fastboot update --disable-verity --disable-verification image-raven-sd1a.210817.036.zip
    4. Run Flash-all.bat
    5. Boot (don't flash) patched image
      fastboot boot magisk_patched-xxxxx.img
    6. Launch Magisk and tap Install, then Direct Install.
    5
    I think you made the same mistake as me, you extracted the factory image archive, and tried to patch the resulting bootloader-raven-slider-XXXXX.img directly thinking it was the file to patch as it began by "boot" and had the ".img" extension.
    If that's the case, from the factory archive extraction you have to then extract the image-raven-XXXXXXX.zip archive, containing the final "boot.img" file to patch.

    @V0latyle you may want to develop a little bit this part in the OT tutorial, as we might won't be the only ones making this mistake ;)
    In all fairness, this is exactly what my instructions are:
    1. Download the factory image. Extract it, then extract the raven-image.zip inside it
    2. Copy boot.img to your phone. Patch with Magisk, then copy patched image back to PC.

    I'm not really trying to make something idiot proof, there's a certain point where limited knowledge and experience is a good reason to NOT try something. If you're unlocking your phone and messing with software, you SHOULD know what you're doing, and at the very least how to fix it if something goes wrong. This forum is not official support, no one here bears any liability whatsoever, and I don't want to give inexperienced and unfamiliar people the impression they can do something that's way outside of their realm of understanding - just like I wouldn't tell someone how to service their brakes if they don't know the difference between a jack and a jackstand.

    I guess what I'm saying is, if you mistake the bootloader image for the boot image, you probably shouldn't be doing any modifications to your device.