I'm with Az on this one!! But again, I work in IT. We're usually pretty lazy when it comes to that stuffMeh... erase two characters VS type in a bunch of characters from memory...
I'm taking the poor memory, lazy, fewer clicks equals more chicks route!
Remove the -w, live longerer and prosperer
Please spoiler your photo, thanks!New magisk canary
Wait, so you went into the Magisk App, restored images, went into System settings and updated via System Update (OTA), then before rebooting went back into Magisk and updated Magisk via "inactive slot" method and then hit reboot in Magisk and it bootlooped in the same slot you started with?
Nope, I updated to January by dirty flashing the factory image.
Other slot wasn't "updated", was just the same version.
I mean yeah, assuming that Magisk just commands system to perform the same reboot process it would do after OTA, in which case system would be looking for a "newer" version on slot B. Question is whether I could manually change to slot B and successfully boot.
Ok, makes sense now. Since you flashed the factory image you stayed on the same slot. Magisk didn't detect your inactive slot was updated (because it wasn't) so it didn't force the phone to switch slots upon reboot.
(famous last words 
)
It did - device attempted to boot slot B, started to load kernel, then bootlooped back to slot A.
Shouldn't have to restore images. Just apply OTA, install to inactive slot, reboot.
But I guess we'll find out for sure in February. The new changes to Magisk were tested on both the Pixel 5 and 6 with success before the changes were merged so we should be good.
You need to restore images first in order to pass pre-OTA block verifications. Then apply OTA, then install to inactive slot and reboot.
I could have sworn I was able to OTA update at some point without restoring stock images. What you're saying makes sense though. Because things.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock
...
OKAY [ 0.032s]
finished. total time: 0.033sC:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloaderC:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot "master root.img"
target reported max download size of 261095424 bytes
sending 'boot_a' (131072 KB)...
OKAY [ 3.137s]
writing 'boot_a'...
FAILED (remote: failed to flash partition (boot_a))
finished. total time: 3.172sC:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot "master root.img"
downloading 'boot.img'...
OKAY [ 3.059s]
booting...
OKAY [ 0.032s]
finished. total time: 3.091s
You should be using the latest Platform Tools. https://developer.android.com/studio/releases/platform-tools
even more dangerous willing to say this in public on a forumThe running joke is that I'm on the hook for multiple bans, never knowing when they'll hit
.connect phone to pc. reboot to recovery and press top volume button to enter recovery option then sideload update and continue through commands of adb
That's more or less how I updated, although I didn't use the script.
That's why it's a running joke...even more dangerous willing to say this in public on a forum
Please read the thread before you post, as the question had already been answered some time ago.
I do it this way every time. I flash the full factory image with the "-w " removed, I go ahead and boot as is just to make sure there's no problems on 100% stock, then I Magisk the boot.img that I've extracted from the inner zip file, then flash that rooted boot.img, boot, and confirm everything's still working.
Sorry. I realized my mistake.
That's an excellent idea for @android_dan.Have you tried live booting followed by a direct install?
I suggested the Official Google Android Flash Tool site because it has fixed things that manually flashing the factory image hasn't, in at least a dozen examples I've read about in this section alone in the six months the P6P has been out.
fastboot boot <path_to_magiskboot.img>fastboot flash boot <path_to_magiskboot.img>adb devicesadb reboot bootloaderfastboot flashing unlockfastboot flash boot <drag and drop master root.img here>adb reboot sideloadadb sideload ota.zipfastboot boot <drag and drop master root.img here>fastboot flash bootloader <drag and drop new bootloader.img here>fastboot flash radio <drag and drop radio.img here>fastboot update --skip-reboot image-codename-buildnumber.zipfastboot boot <drag and drop master root.img here>flash-all script included in the factory zip. You will have to copy the script, bootloader image, radio image, and update zip into the Platform Tools folder; you will then have to edit the script to remove the -w option so it doesn't wipe your device.fastboot update bootloader <bootloader image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot update radio <radio image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot update --skip-reboot --slot=all <image-device-buildnumber.zip>fastboot boot <drag and drop master root.img here>Part of it is due to device differences - non A/B devices can't use seamless updates, so re-rooting is only possible by either patching the boot image directly, or by flashing Magisk in a custom recovery.
Notice the date of that post, 16 months ago. Magisk Canary 23017 re-incorporated the ability to install to inactive slots.
