yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] gazdajezda:
V0latyle: is Magisk 24101 enough for that? I also had problem with OTA update (exactly same problem as others - booted old version). February BT fixes are tempting since i have disconnect issues with car BT.

Edit - i just updated to 24102 - this is last and fully supported version for all operations described here yes?
[Google Pixel 6] V0latyle:
Yes, however Stable 24.1 has all the necessary fixes as well.

For Canary, you have to use 23016 or newer.
[Google Pixel 6] Galaxea:
After using my phone with the FEB update the whole day with no problems, I decided now to configure a few things, and one of them is causing my phone to freeze exactly 2 minutes after booting. Once it hangs if I leave it for about 30 seconds it reboots itself.

What I added was:

(1) blu_spark r49 kernel - which I just downgraded to r45 again and it is still happening so it can't be that,

(2) SafetyNetFix module for Magisk (from the OP's link)

(3) MagiskHideProps config module (from the OP's link)

I have tried to remove the modules from Magisk but it still keeps hanging after 2 minutes and then rebooting 30 seconds later.

Please tell me what I need to do to "undo" the changes that these modules may changed so that I can get my phone working again. Is there a logcat I can view to see what the problem is? How do I go about this. Thanks!

EDIT: Forgot to mention that it is running hot again and only charges slowly with the official charger - same issue I had yesterday when trying to upgrade to FEB security patch. I would suggest staying away from FEB update if you use all these things that I just added!
[Google Pixel 6] gazdajezda:
Thanx. I have Canary branch selected (24102 is last version there). But i will wait with upgrade, since others have problems with safetynet, hide module... all stuff i use.
[Google Pixel 6] dadoc04:
Gotcha...thx.

Yea I'm updated and bootloader unlocked but haven't done the verity and verification yet. Thx for the reply
[Google Pixel 6] capntrips:
When you fastboot flash with the disable flags, it patches the flag bits of the image buffer before flashing it, so patching vbmeta with those same flags is equivalent.

This is why simply restoring boot in Magisk doesn't allow the delta OTA to complete, as the patched flags cause the initial SHA256 verification to fail.

Magisk doesn't backup your boot.img when you flash it via fastboot, which makes it difficult to restore your images the next time you want to take an OTA.
[Google Pixel 6] V0latyle:
Oh okay, so it's not actually patching the image itself, but rather forcing the OTA process to flash vbmeta with those options.

You shouldn't have to restore anything if you take an OTA. I personally don't recommend automatic OTA in our case because of the vbmeta issue. Since it's an out of band update, the OTA (and any other update process) will overwrite any patched boot images with the stock boot images, therefore you'd lose root post update.
[Google Pixel 6] capntrips:
If by it you mean the patcher tool I posted, it restores the active vbmeta partition to stock to allow the delta OTA. After the OTA, it patches both vbmeta partitions to prevent the system from booting with verity and verification enabled.

And correct, it does nothing with images, only partitions.

I was referring to the delta OTA via System Update. I should have clarified.

The vbmeta issue is exactly why I made the tool. As noted above, it has the capability of patching the vbmeta partition after taking the OTA.

As for boot, I'm working on another tool to extract the image from the inactive slot after taking the OTA, so it can be Magisk patched without the need to download the full factory image, but since flashing to the inactive slot is currently disabled (for good reason), you still need a computer to fastboot boot it. When the Dec update is released, I'm planning to do some testing around that issue.
[Google Pixel 6] V0latyle:
I guess I don't understand the point, because having a rooted system (and vbmeta disabled) in my experience doesn't prevent out of band OTAs. I'd still recommend someone taking the system update, because they won't be able to root after it restarts the device, and if they disable vbmeta again they'll have to wipe. But it's good having someone with cool ideas working to make it easier for folks
[Google Pixel 6] capntrips:
I'm not familiar with "out of band" OTAs, and a quick Google didn't immediately turn anything up. Mind elaborating on that?

As for losing root or having to wipe, I'm not seeing significant distinction between the methods. In both cases you have to patch the boot image in Magisk, flash it (either Direct Install in Magisk or fastboot flash), and patch vbmeta with the disable flags (though the method here is slightly different, but with the same end result).
[Google Pixel 6] V0latyle:
A/B System Updates

Out of band OTAs is how devices with alternate slots update. Pixel devices (and some others) have A/B slots. The way an out of band update works is the system downloads and unpacks it to the inactive slot, then performs a reboot switching to that slot. This permits seamless updates by minimizing downtime; the update doesn't take any longer than a normal reboot, and when the device switches slots, the "new" system is ready to go.

This also provides a fallback solution in case something goes wrong with the update - if the device isn't able to boot successfully into the updated slot, it will automatically fail back to the "old" slot so the user can keep using the device.
[Google Pixel 6] c19932:
I am trying to update via the OTA method. Is it neccessary to flash vmetab and patched boot to both slots?
[Google Pixel 6] torsti:
done everything like in first post (flashtool Version). After boot, phone crashes and I only can chose try again or factory reset. I think I have bricked it :(

now I have restored to actual Build via Flashtool :)

any tips how to gain root again?

my idea: Flash again with flashtool and the "disable flags" after that flashing magisk patched boot?

Tryed and it Fails. Need to wipe angain
[Google Pixel 6] t-ryder:
Worked like a charm for me. Yesterday I flashed oriole-sd1a.210817.037 to my rooted Pixel 6 (after creating a full storage backup and system/app backup using Swift Backup).

I downloaded the factory image ZIP package, zipped radio and bootloader to my platform-tools folder. Booted to bootloader and flashed radio and bootloader (you need to be on the latest bootloader, otherwise fastboot won't let you flash the ZIP image zipped from the ZIP package).

fastboot flash bootloader bootloader.img --slot all
fastboot reboot bootloader
fastboot flash radio radio.img --slot all
fastboot reboot bootloader

Then I flashed the ZIP image.

fastboot update --disable-verity --disable-verification image.zip

I booted to the updated system and patched the latest boot.img (zipped from the ZIP image) with Magisk canary. Then I flashed it with fastboot.

fastboot flash boot magiskboot.img --slot all

Rebooted and checked Magisk which runs in Zygisk. All good, did hide Magisk Manager again and checked if the Safety Net Magsik Module works ... all banking and streaming apps available and working.

Thanks to @V0latyle and all you nice folks.
[Google Pixel 6] drnizeguy:
Well, I forgot to disable the verified boot, so now I'm rootless.

Before wiping the device I tried to temporarly boot the patched boot.img for root to make a full backup

fastboot boot magisk_patched_XXX.img

But after rebooting it goes straight into bootloader.

Is there still a way boot a rooted boot.img?
[Google Pixel 6] vandyman:
I have not ever tried this, but:

What happens if you boot the other slot.?
[Google Pixel 6] drnizeguy:
How can we select the other slot?
[Google Pixel 6] drnizeguy:
found it.

fastboot --set-active=a

But that won't boot either.
[Google Pixel 6] V0latyle:
Booting a rooted kernel works on the Pixel 5, even with AVB enabled. I suspect there's more things that need to be figured out on the Pixel 6.
[Google Pixel 6] vandyman:
I need to learn more about the A/B slots.

It has been about two years since I looked into it.

For some reason, I always thought that the inactive slot retained the old image until you update again.
[Google Pixel 6] Ens0:
I followed the steps for the update but for some reason I got into a bootloop. does anyone know how to unbrick or format everything back to locked bootloader? I tried to do it through recovery but it still leads to a bootloop.
[Google Pixel 6] antny:
I used the Android Flash Tool to get back to square one
[Google Pixel 6] Ens0:
Thank you! I'll give this a try
[Google Pixel 6] V0latyle:
Why do you want to re lock the bootloader? If you intend on rooting, just leave it unlocked.
[Google Pixel 6] Galaxea:
Even dirty flashing the FEB update via AFT did not fix the freezing issue.

I am now dirty flashing the JAN update to see if that gets it stable again.
[Google Pixel 6] dilruk:
Anybody successfully moved to 12 L beta while retaining root and no wipe? Just curious
[Google Pixel 6] V0latyle:
Unfortunately your best bet is a clean install.
[Google Pixel 6] Galaxea:
I think that is what I have done. I flashed the JAN update and all is better except for the painfully slow charging. It says "Charging rapidly" but charges at the same rate as charging your phone from a laptop USB port.

I did do a factory reset (if that is what you mean by 'clean') as when I flashed the JAN update myself I got the corrupted message so I used AFT again and it worked.

I think I am going to try 12L now as I can't live with this slow charging and I don't have much to lose (besides time...) as my phone has been wiped 3 times in the last 2 days.
[Google Pixel 6] V0latyle:
Before you try a beta, I would suggest using AFT one more time, and force flash all partitions. If that doesn't fix the charging issue, and downgrading to a previous build doesn't either, it's most likely a hardware issue.
[Google Pixel 6] Galaxea:
I did force flash the last two times that I flashed but no difference.

I have just finished loading 12L and I am very happy with it so far. My battery % went from 23% to 100% immediately, so I think the previous versions were not displaying it properly - it most likely was charging normally but the phone was not seeing it.

What's the easiest way to wipe battery stats? I had a few apps that could do it a while ago but can't remember which ones now.

My phone seems much snappier on 12L but that could be due to not all my apps being restored yet...

Thanks for your suggestions as always.
[Google Pixel 6] vandyman:
I see you have been having troubles installing the monthly updates with root.

Why would you complicate your issues trying to install A12L? Just curious!
[Google Pixel 6] Galaxea:
It is precisely because I was having such issues with (only) the FEB update that I decided to try 12L, and so far I am loving it, but only time will tell if it was a good move. If nothing is broken then I will stay on it till the "stable" releases are a bit more stable.
[Google Pixel 6] dilruk:
Finally got a Pixel cuz I wanted to try all these. It's a shame if I didn't 😂
[Google Pixel 6] Yavia:
worked for me although i had to boot in safe mode to disable a module that was bootlooping me after the update
[Google Pixel 6] crypticc:
Thanks very much for this. Worked perfectly

Spoiler content hidden.
[Google Pixel 6] airtower:
Just as another data point for those that had issues attempting an OTA with 'install to inactive' for magisk and are still on the fence about the Feb OTA - a full factory image flash following the instructions in the OP worked fine for me. No battery or reboot issues, magisk works, SafetyNet passes, etc.

Hopefully I don't have any issues with the OTA and magisk next time! I have pretty sparse access to a windows PC for platform-tools, so PC-less updates are big deal for me.
[Google Pixel 6] gazdajezda:
I'm still on november patch since I do not have a time and will to set a whole phone from scratch all over again.
[Google Pixel 6] capntrips:
You don't have to wipe your data to upgrade. Remove -w from flash-all, uncheck wipe in the flash tool, or upgrade to Magisk 23017 or later and take the OTAs (though that would require initially restoring your vbmeta partition, since you probably used Magisk 23015 or older to root a build that old, so it would probably be easier to use one of the other methods). I'm not all that familiar with the sideload method, but I don't think it requires anything special to avoid a wipe.
[Google Pixel 6] V0latyle:
I don't think OTA requires restoring vbmeta. @gazdajezda should be able to update any desired way without worrying about vbmeta at all.
[Google Pixel 6] capntrips:
To clarify, I was referring to the delta OTA via System Update. update_engine checks the hashes of the partitions in the active slot before applying the diffs to the inactive slot, vbmeta included.
[Google Pixel 6] V0latyle:
Ah, makes sense. Well, this is a simple fix, as restoring vbmeta doesn't require wiping data.

@mustardseeds continuing the conversation from the Pro thread, I would recommend you use the latest Platform Tools. I have no experience with TinyADB, and there are known issues with using outdated versions of ADB, which I assume TinyADB is based on.

Please follow these instructions to the letter and report back.

Ensure TinyADB is not running:

adb kill-server

Download Platform Tools 32.0.0 and unzip to its own folder

Start a command prompt in that folder (Shift + right click)

Connect your phone to your PC and start ADB:

adb devices

This will fail if another instance of the ADB daemon is already running.

Download the "oriole" February OTA (do not unzip)

Reboot your device to sideload mode:

adb reboot sideload

When device screen indicates it's ready, send the file:

adb sideload <drag and drop the February OTA into the command window>

Allow the update to complete, then reboot your device.

Let us know how it goes.
[Google Pixel 6] Dahenjo:
I successfully sideloaded the latest 220205.004 OTA, lost root (was on latest stable Magisk 24.1 that I left installed), then patched & flashed boot.img from the matching 220205.004 factory image to regain root, all working well & nothing was wiped, still says Feb 5 security update but lists the correct new build number.
[Google Pixel 6] V0latyle:
The security update is separate from the system version. On the Pixel 5, the security update was September until the January system update came out.
[Google Pixel 6] airtower:
OTA with Magisk A/B still isn't working. Device rebooted to .003, and I've gotten a few unresponsive system components (iwlan, something related to media).

Magisk said target slot was _a, which I'm pretty sure became my active slot when I full image flashed earlier this week. I'll pay more attention next time around but wonder if there's an issue there.

Edit: so during the process of a factory image flash I was unable to access internal storage via USB. Had to adb push/pull. It seems that even though it rebooted to the same build (003), something had indeed changed and it wasn't just a fluke issue. I'm beginning to think Magisk isn't handling a/b properly on this device.

Factory flash was otherwise straightforward and everything works fine on 004.
[Google Pixel 6] capntrips:
You can check your current slot with getprop ro.boot.slot_suffix.
[Google Pixel 6] Admiral2145:
Trying to do the Feb Ota by uninstalling magisk and restoring image however, it keeps failing to take... This is my 1st Ota with root... Trying to do Ota without pc and keep root with magisk
[Google Pixel 6] torsti:
After I disabled magisk, I tried to update but the installation was cancelled with an error.
[Google Pixel 6] capntrips:
Spoiler content hidden.
[Google Pixel 6] andreipaval:
This is the exact process that I did, but after the reboot from Magisk, I'm still on the 003 first Feb patch, with root, and with the OTA installed and ready to reboot. So the Magisk "Install to inactive slot after OTA" basically did nothing, or just did not force the change of slots. I'm still in the old slot, in the exact same state like before rebooting from Magisk.
[Google Pixel 6] bige93:
Same for me. Tried to update OTA after uninstalling Magisk. After reboot (via Magisk):
[Google Pixel 6] Admiral2145:
Glad it's not just me... Is it a work around to fix Ota failing
[Google Pixel 6] andreipaval:
I just patched the boot in Magisk, copied to PC, installed the full OTA with adb sideload, rebooted, waited to settle,

then flashed the patched boot in bootloader.

No issues.
[Google Pixel 6] Dahenjo:
This didn't work for me on the first February update with same/similar problems and I ultimately had to do a complete factory flash. So here's what I did this time that worked:

- Download both the latest SQ1D.220205.004 OTA and the matching Factory images.

- Sideload the OTA (refer to this post by OP) and reboot to system, you should be updated except you lost root.

- Unzip the Factory image completely and copy the boot.img to /Download folder on phone, then patch it in the Magisk app and transfer it to your platform tools folder on computer.

- Reboot phone to bootloader, flash the patched boot.img (fastboot flash boot <filename>), reboot to system and you should have root again.
[Google Pixel 6] stankyou:
Got fed up with OTA method and just sideloaded the darn thing. No errors. 😁
[Google Pixel 6] Admiral2145:
The master boot from January that I have I re-flash that or download the February update and patch it? This is my 1st time in a pixel device...

Thx
[Google Pixel 6] airtower:
This should work, but it doesn't
[Google Pixel 6] Lughnasadh:
Patch the boot image of the firmware version you are on. If you are on the February build, patch the February boot image.
[Google Pixel 6] capntrips:
Can one of you that's having trouble getting the OTA to stick gather your logs for the entire installation process, including the following reboot? You can filter it for update_engine (or not, it's easy enough to do later). The output from Magisk before the reboot might be helpful, as well.
[Google Pixel 6] Admiral2145:
I'm currently on the January update trying to get to the 2nd February Ota that keeps failing within android... so now I'm going to manually update with pc 🤦‍♂️... So I need to d/l Feb update and get the kernel and patch it with magisk?
[Google Pixel 6] airtower:
I can do this, but I'll need a little help with the adb commands to make sure I get everything you need. I also don't plan to fuss with the OS until the March update.
[Google Pixel 6] Lughnasadh:
Yes, patch the boot image of the firmware you are on. If you are on the 2nd February build, patch the boot image from the 2nd February build.
[Google Pixel 6] capntrips:
On Linux, you can do something like:

adb logcat | grep update_engine | tee update.log
adb logcat | grep update_engine | tee reboot.log

With those commands you'll filter the log output for update_engine, print the matches to the terminal, and write the output to log files on your computer.

I don't have immediate access to a Windows machine to test it, but you should be able to do something like:

adb shell 'logcat | grep update_engine' > update.log
adb shell 'logcat | grep update_engine' > reboot.log

You won't see the output on the command prompt, but the output should be written to the log files.

For the output from Magisk, there's a Save Log button in the top right corner of the installation window. A toast message will pop up with the location of the file.
[Google Pixel 6] gazdajezda:
In the begining of month i tried installing OTA (P6, Magisk 24102) but without success (i totaly follow all guides, have latest adb tools...) I so i just reroot again and leave a fully working phone as is. I will update, when i will have time for case i will again must install all from beginning. Also, few have problems with phone reboots etc, so no, thanks since i need working phone.
[Google Pixel 6] crypticc:
Same error for me (but in English)

I grabbed ADB logcat and the error delayed to SHA checksum of the target.

These were the key error messages. I've not included the two lines proceeding this which had the SHA checksum because I didn't google those so they're no in my browser history, but there was a statement around

expected checksum :-------

and

actual checksum :------

"Unable to open ECC source partition vbmeta_system, file /dev/block/platform/14700000.ufs/by-name/vbmeta_system_b: Invalid argument (22)"

"The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem"

The installation from stock to the January earlier Feb security update took fine using the uninstall magisk, download OTA, install magisk to inactive slot method

Also if relevant I rooted with the canary build that did not need vbmeta to be modified. I do have a copy of old vbmeta because I

did disable verity when I first got phone,

but I then found I didn't need it so I re-enabled verity.

But is there any way to check what I vbmeta I have now on each slot?

p.s.

in the end I did a ADB Sideload of the latest OTA Feb update and that worked fine. But the above is because I'm curious why I couldn't install the OTA SQ1D.220205.004 functionality like I did for SQ1D.220205.003, Feb 2022.

Spoiler content hidden.
[Google Pixel 6] capntrips:
Note that vbmeta and vbmeta_system are two separate partitions, and the error message above is from the latter. I have no idea how it would have gotten out of sync with the rest of your partitions.

As for checking which ones you have, you can download the factory images from the last few months and compare the hashes against what you have in each slot. You can run the following commands from an adb shell to get your current hashes:

dd if=/dev/block/platform/14700000.ufs/by-name/vbmeta_system_a bs=4096 count=1 status=none | sha256sum
dd if=/dev/block/platform/14700000.ufs/by-name/vbmeta_system_b bs=4096 count=1 status=none | sha256sum

Note, though, that these will only match if your vbmeta_system partitions are stock. I have no idea if any of the flash methods that disable verity and verification affect vbmeta_system.

The hashes for my vbmeta_system partitions are ceb42fb2516e76e279baa1f7941bde364efbbbda960d8fc6bd08ad15e721a060 and 79685401c619e35b2de1f886335e16c1ac03df854e9d2364e8e2b3f3743fbfab, which should be from SQ1D.220205.004 and SQ1D.220205.003, respectively. I also happen to still have the image from SQ1D.211205.017, which is 9389cd92abe675486b0835e2413e7bb252b7a4434486b22100306157f304fcf2.
[Google Pixel 6] fairyshacker:
I'm currently on SQ1D.220205.004 rooted with magisk & few modules.

how do i update to 12L (b3), without loosing root?
[Google Pixel 6] V0latyle:
Read the OP, please.
[Google Pixel 6] fairyshacker:
ok
[Google Pixel 6] fairyshacker:
will try as per below

Before you download the OTA, open Magisk, tap Uninstall, then Restore Images.

Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update

Allow the update to download and install. DO NOT REBOOT WHEN PROMPTED. Open Magisk, tap Install at the top, then Install to inactive slot. Magisk will then reboot your device.

You should now be updated with root.
[Google Pixel 6] forty9er:
sorry operator error