You're welcome. Yes, get the unlocked model. With a few very rare exceptions, Verizon models of Pixels can't have their bootloader unlocked. You'll still be able to use Verizon as a carrier with the unlocked model and be able to unlock your bootloader though.
I just re flashed the original boot.img and it still does not install the same error message
so i need dowload the full ota, patch boot img, install ota and re-root?
Not the OTA, but the factory image. The process for the 6a is exactly the same as all previous Pixel devices; if you need more information check my guide on the Pixel 6.
You can, you just have to restore the boot image. OTA Updates with Magisk
Extract it from the factory image, as usual.
great thank you very much.Extract it from the factory image, as usual.
how do you boot patched boot.img before flashing it?Just a heads up. As already told by ctfrommn, it's always a better approach to first boot the magisk patched boot file. And if everything works well and good, you could then Direct Install it via Magisk.
Although directly flashing should also work, but its always better to be on the safer side.
Ok, first time taking OTA and dealing with root in over 8 years.
All you really needed to do was do the system update and factory reset. Everything else was extraneous.Thanks for instructions around unlocking the bootloader!
My device came preinstalled with April update and OEM unlocking was greyed out. I removed google account in settings, took the SIM card out, updated to June patch, did factory reset, setup the device without Wifi and google account, after setting up I connected to Wifi and once I reinserted the SIM card I was able to toggle the OEM unlocking option in developer settings. Great stuff!
Yes, of course. That's always been the case but removing the account, taking out the sim card, only connecting to wifi without a sim card.. that's what I meant. Reset after the update and just continue setting up as usual. Any connection to the internet will suffice.
adb reboot bootloader
fastboot flashing unlock
fastboot flash boot magisk_patched.img
You won't like this answer, but if you don't know what you're doing, you shouldn't be doing this.
I think you misunderstand me.I'm done for tonight
Somehow I got to the point where the security update got installed!!! I followed the ota with magisk guide and did not restart after it, went into the magisk, installed onto the secondary partition (or whatever it's called), rebooted.. and the phone completely froze.. I thought "that's it, this pixel has had a nice long 1wk long life ".
Held the power button for over 30 seconds, booted up, went to magisk, patched the boot.img file, flashed it, and nothing - still no security update installed.
I want to offload the process of updating the phone to my wife, but I kinda like permanent root for acc control, etc
fastboot flash boot <boot image>, you're actually writing that binary to the /boot partition. If you do this with a patched image, Magisk does not have a backup.
fastboot boot <boot image>, you're sending the binary to the device to load instead of what's written to /boot. If you boot a patched image, then perform Direct Install in Magisk, Magisk then creates a backup of the original image in /boot so as to be able to restore it later.
I would not recommend doing this. While the kernel may be the same, the boot image contains other components that are updated with almost every release, such as the Android security engine. It's OK to temporarily boot an older image, but I recommend always flashing the boot image that corresponds to the update.
Download the factory update package (not the OTA) and extract boot.img from within it, then flash in bootloader:
fastboot flash boot <boot image>
Magisk operates via a kernel patch to grant root access. If you flash an unpatched boot image, you lose root, meaning Magisk is unable to load any modules. The only time this would cause a boot loop is if you updated via OTA, then flashed an older boot image; the system would see the mismatch and assume the update failed.
As this thread ages, not everyone will have the June 2022 update. That's why I suggested/put the steps in to do it themselves with matching firmware to what their device is on.
This DID NOT work for me. That's why I wrote this up the way I did.To get the `OEM Unlock` option in Developer Options to work, it's simpler to just manually flash 12.1.0 (SD2A.220601.004, Jun 2022, Verizon, Verizon MVNOs) and then wipe.
Even though it's label as Verizon, it should work for all carriers.
If you're bootloader is already unlocked, you just have to flash the patched magisk boot img, correct. I wrote this up for those having issue with not having the ability even if it is an unlocked from google device
these instructions sound like "the usual process", but for the 6a isn’t there something to patch regarding vbmeta as well?
(never had a phone that "needed" this, but in my understanding it "should" be necessary with the 6a? won’t have time to try out myself before the weekend, just asking ..)