Themes / Apps / Mods [DEV][EOL] Vbmeta Patcher, Devinfo Patcher, and Boot Image Tool

[cbomb1337]

I was on the A1 firmware and it was bad so O reverted to the version 37 I think it was called using Android flash tool using wipe and upgraded to the a5 Australian firmware and didn't check the disable Verity or verification and didn't check wipe. And it updated and worked fine and then I flashed the downloaded boot file with the new magisk canary and flashed it so this seems to work. I'm guessing this now means we can like update via system settings and download new boot img and pstch it and flash like usual right.

 

[capntrips]

I was on the A1 firmware and it was bad so O reverted to the version 37 I think it was called using Android flash tool using wipe and upgraded to the a5 Australian firmware and didn't check the disable Verity or verification and didn't check wipe. And it updated and worked fine and then I flashed the downloaded boot file with the new magisk canary and flashed it so this seems to work. I'm guessing this now means we can like update via system settings and download new boot img and pstch it and flash like usual right.

Canary 23016 doesn't enable patching the inactive slot on Pixel devices, so you would still need a custom build to take the OTA via System Update. The issue I'm currently experiencing is that my Pixel 6 doesn't even detect an OTA is available, but I'm not sure how common that is.

 

[capntrips]

I made a new build of Magisk, based on 23016, with the updated bootctl binary, so you can flash to the inactive slot after an OTA, assuming your device even detects one is available.

 

[bzz11g]

anyone using my Magisk builds that has gotten it?

Hi, I taking root with your build of Magisk v23015-19f2116b, then before OTA I'm updating to b7bdd55c build, then I receive OTA and successfully update my phone

Now I'm updating to latest 23016 build from previous post

What should I do here (update menu after install new build)?

 

[capntrips]

Hi, I taking root with your build of Magisk v23015-19f2116b, then before OTA I'm updating to b7bdd55c build, then I receive OTA and successfully update my phone

Thanks for the feedback. I may try to reinstall the November update with the factory image, see if that allows me to find the December update. Maybe there's still some lingering weirdness from installing it originally, given I was doing quite a bit of testing during that update.

Now I'm updating to latest 23016 build from previous post

What should I do here?

I'm not entirely sure what you're asking, but if you're updating builds, you're probably looking for Direct Install.

 

[bzz11g]

I'm install new build v23016-8f719c7b
Open Magisk app and see Update button

My question is this: Do I need to upgrade Magisk (direct install) or just leave it as it is?
If I need it: should I upgrade only in the current slot, or in both?

Thank you

 

[capntrips]

I'm install new build v23016-8f719c7b
Open Magisk app and see Update button
My question is this: Do I need to upgrade Magisk (direct install) or just leave it as it is?
If I need it: should I upgrade only in the current slot, or in both?

Yes, you'll want to keep your app, ramdisk, binaries, and scripts in sync, so anytime you install a new version of the Magisk app, you should update Magisk, as well.

Only update the current slot. When you do an OTA, you can do both, if you want, but anytime you install to the inactive slot, it will force you to switch slots.

 

[cbomb1337]

Thank you I will check ota when next updates released for Australia. If it doesn't find anything I will just use the online flash tool. I downloaded ur modified APK for installing to next slot. Will test that to if ota finds update.

 

[capntrips]

I made a draft pull request to include an updated bootctl in the build process of Magisk. If I get some positive feedback from them, I'll clean it up and submit it to be merged.

On a related note, even after going back to stock for two weeks, I was never given the option to install the delta OTA. I tried installing the factory image and full OTA for the November release, but neither helped, so I manually installed and rooted the December update today. Hopefully I'll be able to install the January delta OTA.

 

[bzz11g]

I made a draft pull request to include an updated bootctl in the build process of Magisk. If I get some positive feedback from them, I'll clean it up and submit it to be merged.

On a related note, even after going back to stock for two weeks, I was never given the option to install the delta OTA. I tried installing the factory image and full OTA for the November release, but neither helped, so I manually installed and rooted the December update today. Hopefully I'll be able to install the January delta OTA.

Jan OTA already available, i'm waiting for system optimization

 

[bzz11g]

Confirm successfully update to Jan build with ota

Spoiler: build

Thank you @capntrips for this greet opportunity!

 

[shoey63]

Confirm successfully update to Jan build with ota

How did you get the ota take?
I restored stock boot and got this

(I'm on AU December firmware)

 

[bzz11g]

How did you get the ota take?
I restored stock boot and got this
(I'm on AU December firmware)

I think you need VBmeta tool patcher from 1st post of this tread to revert vbmeta status in Stock condition

 

[shoey63]

I think you need VBmeta tool patcher from 1st post of this tread to revert vbmeta status in Stock condition

I first rooted with canary 23016 so I've never touched vbmeta. Must be a region thing.
Thanks for your confirmation that it works though. . . .

 

[capntrips]

How did you get the ota take?
I restored stock boot and got thisView attachment 5508855
(I'm on AU December firmware)

If you filter your logcat for update_engine during install, it'll give you an error message. My first guess would have been the vbmeta partition, but if you never patched it, my only thought would be Magisk restored the wrong boot image, somehow.

 

[capntrips]

In Magisk news, an updated bootctl landed in Magisk. Unfortunately, installation to the inactive slot has not. I made a fresh PR containing only that change.

I also made a fresh build with the new bootctl binary included and installation to the inactive slot enabled. This is functionally equivalent to my previous builds, unless there are other upstream changes you're interested in.

I was finally offered an OTA on my Pixel 6, so I was able to take the January delta OTA using this build.

 

[shoey63]

If you filter your logcat for update_engine during install, it'll give you an error message. My first guess would have been the vbmeta partition, but if you never patched it, my only thought would be Magisk restored the wrong boot image, somehow.

I thought that too, so I restored original boot with DD command, still no luck.
Now I remember that I flashed November modem over December firmware. This must have caused the mismatch.
In the end I just brute forced the January update on the PC by flashing the images after swapping slots lol.
So no more using devinfo patcher then?

 

[capntrips]

So no more using devinfo patcher then?

It's still handy for testing and development (for example, to verify new bootctl builds), but most users have no need for any of the tools in the OP, at this point. Someone on a pre-23016 build of Magisk might need Vbmeta Patcher to take an OTA; otherwise, they're only there because I haven't bothered to retire them, yet.

 

[draymond1987]

Does anybody have December vbmeta and boot, that can be thrown into a zip to flash via EX app?? I don't have a PC, nor will I, for awhile.

 

[capntrips]

The PR enabling installation to the inactive slot on Pixel devices has been merged, so my builds will be retired when the next canary (23017) drops.