yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] bzz11g:
Hi @capntrips I recive my phone and now I try root my device, but after fastboot boot C:\ADB\magisk_patched-23015_poDko.img

bootloader update screen, but after reboot no option in magisk "Direct install"

may be I need disable vbmeta before boot command?

https://xdaforums.com/t/root-users-read-this-before-updating.4356233/#post-85877931

--upd

Yes command is need

fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img

reboot

wipe data

reboot in bootloader then

fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot boot C:\ADB\magisk_patched-23015_poDko.img

And Direct install available in Magisk APP
[Google Pixel 6] capntrips:
On the Pixel 5a, at least, you don't have to flash vbmeta with disable flags with my latest Magisk builds, as it signs the boot image. I'm still waiting for the December update to roll out my Pixel 6, but as soon as it is available, I'll test it.
[Google Pixel 6] bzz11g:
I can't boot patched_boot.img without vbmeta disable

I already receive December update, now I performing backup and try to update
[Google Pixel 6] Lughnasadh:
Not sure if you are aware but root is broken on the Dec. update for the Pixel 6 series but seems like a fix may have been found.

Pixel 6 pro, recent android december update breaks root. · Issue #5057 · topjohnwu/Magisk

Device: Google Pixel 6 Pro 512GB Android version: Android 12 (SQ1D.211205.016.A1, Dec 2021) Magisk version name: 5d6d241 Magisk version code: 23015 The recent android december update for google pix...

github.com
[Google Pixel 6] bzz11g:
wow, then I will stop updating process and wait someone feedback
[Google Pixel 6] capntrips:
I pushed a build with the proposed fix cherry-picked.

Edit: I pulled the build in favor of newer ones based on 23016, which includes the fix.
[Google Pixel 6] mac796:
I havnt updated the December yet you think this will work for the pro version. I'll try it out
[Google Pixel 6] capntrips:
Someone tested the fix on a Pixel 6 Pro and reported success here.
[Google Pixel 6] capntrips:
Correct, you'll have to use Vbmeta Patcher to restore the vbmeta partition in your active slot before you'll be able to take the OTA; otherwise, update_engine will detect the difference and abort the update.
[Google Pixel 6] mac796:
Do I have to do anything with verity before. Or just patch VBmeta? Sorry for all the questions
[Google Pixel 6] bzz11g:
OTA not working for me(( I try it 4 times, every time - error

View attachment 5481947
[Google Pixel 6] mac796:
Wouldn't you have to take the full update?
[Google Pixel 6] bzz11g:
@capntrips looks for the path to install updates over the air if you have root access, without PC

that's what this whole topic is about
[Google Pixel 6] capntrips:
You have either boot or vbmeta in your active slot patched. You have to restore both before you'll be able to take an OTA.

Edit: Vbmeta Patcher and Boot Image Tool should be able to tell you.

The goal of this thread is to be able to take the delta OTA.
[Google Pixel 6] mac796:
Sorry I'm used to one plus when we did it like this it was with the full ota.
[Google Pixel 6] bzz11g:
Yes, i'm restore stock boot.img

How I can restore vbmeta status?

---upd i'm found vbmeta patche in 1st post, make another try
[Google Pixel 6] capntrips:
Vbmeta Patcher will be able to restore it.
[Google Pixel 6] bzz11g:
Do i need change vbmeta status again after intalling OTA before make "Direct install" in Magisk app?

--now ota installing successfully, but not reboot, i'm waiting for Optimization

View attachment 5481955
[Google Pixel 6] capntrips:
You theoretically shouldn't have to patch vbmeta at all.

Edit: Signing the boot image is not needed.
[Google Pixel 6] bzz11g:
Ok, i think we need 20-30 minutes to figure out this

very slow Optimizing process, progress 1/3 in 10 min
[Google Pixel 6] capntrips:
It took mine an hour for the November update. I'll keep an eye out for the final word.
[Google Pixel 6] bzz11g:
I managed to update, everything is fine

I don't use Vbmeta Patcher after installing update, just make direct install in active (old) slot and then make install in opposit slot and reboot from magisk

Optimization took about hour

Thank you for this great tool!

View attachment 5482003 View attachment 5482005 View attachment 5482009
[Google Pixel 6] HarryShan:
I've just updated to Dec stock full image using fastboot update without --disable.... flags, and now I find myself unable to boot from any patched boot.img including using your b7bdd55c.

Do you have an idea on what could have caused this? Is there something like boot log I can look into?

Edit: updating to 23016 fixed it all for me. Thanks for all the work you've done!
[Google Pixel 6] capntrips:
Glad you got it working. I still haven't been able to test it myself, as I seem to have this issue and still haven't gotten the OTA. I may break down and do a full OTA, but I was hoping to be able to test the delta OTA process, given that's the whole point in this thread.

Has anyone else not gotten the OTA notification? anyone using my Magisk builds that has gotten it?
[Google Pixel 6] 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.
[Google Pixel 6] capntrips:
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.
[Google Pixel 6] 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.
[Google Pixel 6] bzz11g:
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)?

View attachment 5483683
[Google Pixel 6] capntrips:
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.

I'm not entirely sure what you're asking, but if you're updating builds, you're probably looking for Direct Install.
[Google Pixel 6] bzz11g:
I'm install new build v23016-8f719c7b

Open Magisk app and see Update button

View attachment 5483747

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
[Google Pixel 6] capntrips:
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.
[Google Pixel 6] 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.
[Google Pixel 6] 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.
[Google Pixel 6] bzz11g:
Jan OTA already available, i'm waiting for system optimization
[Google Pixel 6] bzz11g:
Confirm successfully update to Jan build with ota

Spoiler content hidden.

Thank you @capntrips for this greet opportunity!
[Google Pixel 6] shoey63:
How did you get the ota take?

I restored stock boot and got thisView attachment 5508855

(I'm on AU December firmware)
[Google Pixel 6] bzz11g:
I think you need VBmeta tool patcher from 1st post of this tread to revert vbmeta status in Stock condition
[Google Pixel 6] shoey63:
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. . . .
[Google Pixel 6] capntrips:
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.
[Google Pixel 6] 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.
[Google Pixel 6] shoey63:
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?
[Google Pixel 6] capntrips:
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.
[Google Pixel 6] 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.
[Google Pixel 6] 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.
[Google Pixel 6] Nightf0x_007:
Vbmeta app gives me unexpected format
[Google Pixel 6] capntrips:
The Unexpected Format exception is thrown when the app encounters a missing magic header or avbtool version number in one of the vbmeta slots. My guess is one of your vbmeta partitions is corrupted. I suppose the app could be reworked to allow it to work with any good partitions and to ignore the bad ones, but I'm unlikely to put in the work, given the app is basically obsolete, with the latest version of Magisk (23016) working with stock vbmeta partitions.
[Google Pixel 6] Nightf0x_007:
Yes there is something wrong with my phone as i have corrupted device warning when rebooting i feel its because of dm-verity/verification

Is there anyway to fix this vbmeta problems/disabling dm, without wiping my device

TIA
[Google Pixel 6] capntrips:
With Magisk 23016, you no longer need to the disable flags. I would suggest using the Android Flash Tool to install latest stock for your device. As long as you don't check the box for it, it won't wipe your data. Also, don't check the disable flags, or it may bootloop then ask you to factory reset, though you can still recover from that state using the flash tool.
[Google Pixel 6] Nightf0x_007:
Should i completely uninstall magisk or restore images before reflashing latest stock via android flash tool?
[Google Pixel 6] capntrips:
Unless you have a Magisk module causing conflicts, there should be no need. The flash tool will write a stock boot partition.
[Google Pixel 6] shoey63:
Canary 23017 is released

I'm assuming the procedure now is to uninstall @capntrips build and install Official canary, then do a direct install?
[Google Pixel 6] capntrips:
Looks good to me. I probably had something left over from testing, but I had to hide my build in the app, first, as I was getting a compatibility error while trying to install official, even after uninstalling my build and rebooting.
[Google Pixel 6] Lughnasadh:
Very appreciative of your work on this. Nice to have the "install to inactive slot" option back again. Thanks 👍
[Google Pixel 6] bzz11g:
Magisk v24 are available

Releases · topjohnwu/Magisk

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com

In a couple of weeks we will find out whether it is possible to update the OTA on the official Magisk ;)
[Google Pixel 6] capntrips:
I pulled the builds from my fork of the Magisk repo, since everything needed to take the delta OTA should now be in official. There should be little need for the apps from the OP, at this point, but I'll leave those builds up, in case someone has a use for them. Thanks to everyone who tested builds and reported back.
[Google Pixel 6] bzz11g:
confirm successfully install Feb OTA with official build of Magisk 24.1
[Google Pixel 6] airtower:
I've never been through the uninstall magisk process before. "Complete uninstall" doesn't force a reboot or anything does it? Just Uninstall Magisk > Take OTA > Install to Inactive > Reboot?
[Google Pixel 6] capntrips:
Unless you're running into startup issues with a module, there's likely no need to do a Complete Uninstall. Restore Images will revert your boot partition to stock, so you're able to take the OTA.
[Google Pixel 6] capntrips:
Seeing all the issues people are having in the guide threads, I just wanted to note that I used canary build 24102 to take the February OTA on a Pixel 6 and a Pixel 5a, both without issue.

In the worst case, you'll have to fallback to the full factory image, if something goes wrong.
[Google Pixel 6] shoey63:
I tried to update to L12 Beta this way. It booted straight to fastboot afterwards. Had to force it to loop 3 times to get it to swap to the other slot and back to previous working Feb update.

Anyone else?
[Google Pixel 6] mac796:
I'm wondering if my problem was running a custom kernel. Updating it often, maybe when I restored images it restored to last update. I'm not sure just guessing. But if it fails all I had to do was run the Android flash tool with no wipe.
[Google Pixel 6] capntrips:
Does Magisk work with Android 12L at all, currently? A quick Google search and a search of the Magisk Github turned up basically nothing.

Edit: It looks like the source code won't be available until public release, for whatever that's worth.

Did you get an Installation Failed error in System Update? If so, that could certainly be your issue. If not, it's unlikely, since update_engine checks the hash (of part of) your boot partition during the update, and it will fail if it is different.

Magisk should only backup the stock boot image, and it should pass the original stock image's hash through multiple flashes. I don't know anything about the kernel installation process, so that could potentially be the weak link.
[Google Pixel 6] phaino00:
I read in the thread here that root and modules were working:

https://xdaforums.com/t/android-12l-beta-opt-in-now-available.4400411/unread
[Google Pixel 6] mkhcb:
So say I have magisk 24102 on the December update and I want the easiest way to update with root (and not lose my data). How would I do it? Can I system update?
[Google Pixel 6] capntrips:
I use the OTA instructions in the OP:

Spoiler content hidden.

Or if you prefer something a bit more visual:

Spoiler content hidden.
[Google Pixel 6] mkhcb:
Thanks for the visual instructions. My OTA keeps failing to install the update, so I guess I am stuck with flashing the update with my computer this weekend. This however is much simpler and something I'll use for the March update! Thanks!
[Google Pixel 6] airtower:
System update by itself won't even work if rooted. Some have been able to restore images, take the OTA, then flash Magisk to the inactive slot, but this doesn't work for many (including me) and could put your device in a unbootable state.

Since you don't seem to be in a rush, just dirty flash the full factory image. There are several threads here outlining this process, which keeps root and data intact.
[Google Pixel 6] capntrips:
Those that have this issue seem to be in the relative minority. Are you still planning to record logs of the process for the March update? It is expected to be released on March 7. I'm planning to record the logs on my devices, as well. Hopefully between the good and bad logs, we'll be able to find the cause of the issue.

It might also be interesting to see the output of bootctl get-current-slot and bootctl get-active-boot-slot before taking the update and before and after flashing to the inactive slot. You can download bootctl from the Magisk repo here.
[Google Pixel 6] airtower:
I'll be on it!
[Google Pixel 6] mkhcb:
I however would love the ability to unroot, then use system update, and then re-root. That be phenomenal!
[Google Pixel 6] airtower:
You can try it, worst case a dirty flash will get you back
[Google Pixel 6] mkhcb:
I tried that method. Systems update won't update for me.
[Google Pixel 6] capntrips:
I took the March OTA on a Pixel 5a and logged everything. One quirk was the grepped output piped into tee was always a few lines behind the logcat in an adb shell. It didn't flush the last of the lines until the device restarted or was unplugged. If I interrupted the process first, it did not flush.

Hopefully the Pixel 6 update drops in the next few days.
[Google Pixel 6] airtower:
As long as Google holds up their end of the bargain, I should have time to do this this afternoon.

grep needs its argument in quotes though right? grep "update_engine"? My CLI skills are weak.
[Google Pixel 6] capntrips:
Since the argument contains no whitespace, quotes are optional.

Edit: You'll need to chmod +x the bootctl binary and call it with an absolute (/data/local/tmp/bootctl) or relative (./bootctl) path, since it is unlikely to be on your PATH. You can get the binary here. If you have trouble with bootctl, you should be able to use Devinfo Patcher from the OP to get the active slot.
[Google Pixel 6] capntrips:
The OTA did not go smoothly for me. I ended up at the red eio screen, which changed to the usual orange unlocked screen then to the charging screen. After holding the power button for 30 seconds, it rebooted back into the previous slot on the Feb update. Fortunately, I took the extra step of doing a direct install after installing the OTA, so I was still rooted.

I rebooted into the bootloader, changed the slot back to the March update and tried a variety of fastboot flash and fastboot boot commands with no success.

I let my slot switch again, and booted back into the Feb update. I opened System Update and was immediately given the post install screen with the reboot button. Upon clicking reboot, it gave me a the Downloading and installing screen, which completed in just under a minute and rebooted without an additional prompt [1]. I restored the stock image in Magisk during that time, but I have no idea if that mattered.

This time it booted into the (stock) March update successfully. I watched update_engine in logcat, and when it completed merging [2], I rebooted into the bootloader and fastboot booted the patched image. This time it booted without issue, so I direct installed in Magisk and rebooted, again successfully.

I suspect the merges [2] were related the abbreviated update process [1]. I'm going to try to switch my slot back to the Feb update to see if it will let me do the entire operation a second time. If not, I may try installing the Feb update with the flash tool, to see if that works.

During the scramble, I lost track of which logs go with which operation, but I'll try to organize and post them when I've tried a few more things.
[Google Pixel 6] airtower:
I was unsuccessful as well, but had a different experience. I PM'd you the info and logs as requested.
[Google Pixel 6] capntrips:
I was unable to go back to the Feb update, as it would require a data wipe due to a bootloader update.

Here are the update and restart logs from my first attempt, where the update initially seemed to complete as usual but failed to boot and rolled back to the previous slot. It caught me offguard when it booted into the previous slot, so I didn't catch the first few seconds of the reboot log:

update.log

reboot.log

Here are the update and restart logs from my second attempt, there the update took less than a minute and rebooted without an additional prompt. The system booted into a stock March update:

update.log

reboot.log

Some quick notes:

All above used Magisk 24304. In step 5, the active boot slot was still unchanged, so this was different from a Pixel 5a. The patched images from steps 10 and 11 were identical, and is the exact image I'm now using on a functional March update. I did not get a chance to test the signed version before the phone booted into the previous slot. I did attempt to use it after changing the slot back, but the update was marked as failed by that point.

In the next day or two, I'll try to compare the logs against the test run on a Pixel 5a from earlier in the month.
[Google Pixel 6] shoey63:
Successful March OTA update for me. Zero issues.

Pixel 6 with latest Magisk Alpha 24301 (saves the need to "hide" the app with a random package id/name)

- First I disabled zygisk and modules and rebooted.

- Restored stock boot with uninstall/restore images function.

- Took OTA update

- Installed to inactive slot (also direct install in case of failed update)

- Rebooted while in Magisk.

It fired straight up with March update installed.

The method is sound but it looks like the latest Canary is somewhat borked.

Many issues on various threads.
[Google Pixel 6] capntrips:
Glad to hear it worked on a Pixel 6. It sounds like my issue was likely with Magisk 24304. I might have to transfer all of my data to my Pixel 5a, so I can wipe and run some tests (or better yet, just wipe the Pixel 5a and see if the March update fails with 24304 on there, as well).
[Google Pixel 6] airtower:
My OTA failed (bootlooped while running post update cleanups), but 24.3 is now running fine after a March full image flash with USNF, Systemless, and Zygisk enabled.

I didn't disable anything in magisk, but I wonder if direct installing post-OTA is a factor in your success.
[Google Pixel 6] capntrips:
I installed the April update with 24305 and got the dm-verity corruption screen. I let it bootloop once and it rolled back to the March slot. I moved to my Pixel 5a over the weekend, so I'll do a full wipe with flash tool and start over with 24.3 stable and see if that works.

I did compare the 5a March update logs to both my and @airtower's Pixel 6 logs, but I didn't see anything obvious. I would be interested in seeing the full logcat output (no grep) on a failed reboot without corruption.
[Google Pixel 6] airtower:
FWIW I flashed April update earlier today with the flash tool and patched boot image. No issues.
[Google Pixel 6] capntrips:
After a clean flash of the March update with the flash tool, I tried to take the April OTA with Magisk 24.3 stable, but it bootlooped 3 times (Google logo only, it never made it to G logo with the progress bar) then rolled back to the March slot.

If anyone successfully takes the delta OTA, please share what version of Magisk you used.
[Google Pixel 6] bzz11g:
hi @capntrips ! I'm in the same boat, magisk 24300