• 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

GivIn2It

Member
Jul 12, 2021
28
10
Samsung Galaxy A52 5G
This is a question for the OP. I have a new in box pixel 6 pro. Should I put my sim card in and set it up with Google, etc before I follow your procedure, or can I just straight up update and root it as is, in its virgin state with no sim card?

Hopefully I have my posting skills adjusted correctly.
 

roirraW "edor" ehT

Recognized Contributor
This is a question for the OP. I have a new in box pixel 6 pro. Should I put my sim card in and set it up with Google, etc before I follow your procedure, or can I just straight up update and root it as is, in its virgin state with no sim card?

Hopefully I have my posting skills adjusted correctly.
Update and root as is without a SIM card. You can do either way, but might as well since you're starting fresh already.
 

GivIn2It

Member
Jul 12, 2021
28
10
Samsung Galaxy A52 5G
Update and root as is without a SIM card. You can do either way, but might as well since you're starting fresh already.
Thanks for that reply.
I got to the fastboot update --disable-verity --disable-verification image-raven-sd1a.210817.037.zip. I got :
--------------------------------------------
Bootloader Version...: slider-1.0-7714574
Baseband Version.....: g5123b-91479-210916-B-7738070
Serial Number........:
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' FAILED

Device version-bootloader is 'slider-1.0-7714574'.
Update requires 'slider-1.0-7860951'.

fastboot: error: requirements not met!

So what do I do now?
 
Last edited:

vlubosh

Senior Member
Sep 8, 2007
220
143
Bratislava
Google Pixel 6 Pro
Thanks for that reply.
I got to the fastboot update --disable-verity --disable-verification image-raven-sd1a.210817.037.zip. I got :
--------------------------------------------
Bootloader Version...: slider-1.0-7714574
Baseband Version.....: g5123b-91479-210916-B-7738070
Serial Number........:
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' FAILED

Device version-bootloader is 'slider-1.0-7714574'.
Update requires 'slider-1.0-7860951'.

fastboot: error: requirements not met!

So what do I do now?
use android web flasher, dont forget to mark disable verity/verification:


then from downloaded file extract zip, from the zip boot img. with magisk app patch boot.img and flash patched boot.img.
 
  • Like
Reactions: roirraW "edor" ehT

V0latyle

Forum Moderator
Staff member
Update and root as is without a SIM card. You can do either way, but might as well since you're starting fresh already.
Shouldn't matter. It may be easier to skip through initial setup if you don't have the SIM in or connect to WiFi.
That would SUCK if the 1st of the month was on a Tuesday :p :p :p
Yeah, it's always kinda annoying waiting another week for the update to drop. But at least we get updates direct from Google, so we get to stay cutting edge; I'm sure a lot of us know the pain of being stuck on older vendor firmware waiting a year or more for them to finally release their flavor of the next Android version. Samsung is probably one of the worst offenders, mostly because they retain very little from AOSP and instead build everything in their proprietary One UI. And instead of using vanilla Android apps, everything has to be their own stuff - photos, Bixby, etc etc etc.

Speaking of which, have those of you on Verizon noticed that My Verizon, Verizon Cloud, and Verizon Messages automatically install on initial setup, even if you never had them installed before?
 

bobby janow

Senior Member
Jun 15, 2010
6,108
2,147
<snip>

Speaking of which, have those of you on Verizon noticed that My Verizon, Verizon Cloud, and Verizon Messages automatically install on initial setup, even if you never had them installed before?
Yes and sometimes even if you disable 'my verizon services' it will re-enable itself. If I'm not lazy I'll pm uninstall it but it still comes back on the monthly update. Annoying at best.
 

GivIn2It

Member
Jul 12, 2021
28
10
Samsung Galaxy A52 5G
use android web flasher, dont forget to mark disable verity/verification:


then from downloaded file extract zip, from the zip boot img. with magisk app patch boot.img and flash patched boot.img.
The web flasher wont let me use .037, when I search for SD1A.210817.037 (7862242), it finds it, but then it states Build not found. The web flasher only offers October, and I don't see the point of that when November is available. Amy ideas on installing .037? Maybe I should try installing the .037 OTA, then following the OP?
 
  • Wow
Reactions: roirraW "edor" ehT

vlubosh

Senior Member
Sep 8, 2007
220
143
Bratislava
Google Pixel 6 Pro
The web flasher wont let me use .037, when I search for SD1A.210817.037 (7862242), it finds it, but then it states Build not found. The web flasher only offers October, and I don't see the point of that when November is available. Amy ideas on installing .037? Maybe I should try installing the .037 OTA, then following the OP?
I also first tíme tried your method but have i think same issue, dont have tíme to search how to fix it, therefore tried web Android flasher, but i dont know why you see only older firmware.
 
  • Wow
Reactions: roirraW "edor" ehT
Speaking of which, have those of you on Verizon noticed that My Verizon, Verizon Cloud, and Verizon Messages automatically install on initial setup, even if you never had them installed before?
That's one of the "features" of the Verizon firmware. (I'm running Verizon on unlocked phone)

Edit: didn't see it was already answered.
 
Last edited:
  • Like
Reactions: V0latyle

GivIn2It

Member
Jul 12, 2021
28
10
Samsung Galaxy A52 5G
I also first tíme tried your method but have i think same issue, dont have tíme to search how to fix it, therefore tried web Android flasher, but i dont know why you see only older firmware.
Here's how I fixed it:

How To Guide [Pixel 6 Pro] Easy STEP BY STEP Unlock-Root (Az Biker)​

post# 64 {No time to figure out the intricacies of linking posts here, too much valuable time wasted already.
 

Dave Lister

Senior Member
Feb 16, 2010
103
52
Here's how I fixed it:

How To Guide [Pixel 6 Pro] Easy STEP BY STEP Unlock-Root (Az Biker)​

post# 64 {No time to figure out the intricacies of linking posts here, too much valuable time wasted already.

(btw, the post # in the upper right corner is the hyperlink to that post)
 

V0latyle

Forum Moderator
Staff member
Yes and sometimes even if you disable 'my verizon services' it will re-enable itself. If I'm not lazy I'll pm uninstall it but it still comes back on the monthly update. Annoying at best.
I haven't had it come back after updates. Only on initial setup.
That's one of the "features" of the Verizon firmware. (I'm running Verizon on unlocked phone)

Edit: didn't see it was already answered.
Except I'm not running the Verizon variant; I'm running the vanilla.
 
I haven't had it come back after updates. Only on initial setup.

Except I'm not running the Verizon variant; I'm running the vanilla.
Probably something Google and Verizon agreed too then.

If you reset your phone and don't activate esim or insert Verizon sim card during initial set up, it probably won't happen again. If running unlocked firmware.
 
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.