- Jun 23, 2016
....Question - What is the safe/proper way of proceeding on Pixel 6 pro?
First run after boot, Magisk Delta asks for additional configuration steps to be done and gives following options:
Normal Magisk (not Delta) raise same request to perform additional tasks but didn't give any options, hence am unsure which one should I proceed with (tend to think about direct). With that said, it could be third (after OTA) as effectively I did sideload OTA.
- Choose and patch file ( bootloader is locked with avbroot and I don't know how then incorporate patched file into OTA, as only OTA can be sideloaded).
- Direct installation (recommended).
- Install in inactive slot (after OTA).
Thanks for help!
Just now trying to understand your issue...Android Flash tool fails as it tries to unlock bootloader, which fails. I've tried from fastboot level directly.
The OEM Unlocking hasn't been touched (and should be enabled - allowing unlock).
For whatever reason it looks like it simply doesn't work. Not sure why - the only thing which did happen was that run of Magisk additional steps straight after which the system has been bricked.
Yes, I can't get to recovery either.
Do I have a hard brick now? Can I do maybe anything from fastboot level (having all images, including signed ones)?
Seems this may have complicated by several unusual factors...
Do you have Magisk installed using avbroot script and bootloader re-locked with custom keys registered?... Saw you mentioned that in other thread but can't see it mentioned here...
Did you also take Install → Install to Inactive Slot in Magisk App?... This is broken at least for late P6 and P7 ROMs as update engine now checks partition digests and will mark the partition as corrupted... Pixel users on recent ROMs have been avoiding this installation method for a while now...
... If you used avbroot it seems boot, recovery, or vendor_boot image may all be patched (to replace the OTA signature verification certificates with the custom OTA signing certificate) in addition to boot or init_boot being patched with magiskinit...
- Also, if OEM unlocking is disabled with locked bootloader and root when system became corrupt device is 'hard bricked' (fastboot flashing unlock will not be allowed)... From what you say you shouldn't be facing this however, unless you use a mod that messes with OEM Unlocking setting... Apparently some forks of USNF do disable this but @kdrag0n disapproved a merge request in official USNF...
- Regardless of OEM Unlock you can't perform 1) a regular (unpatched) A/B OTA update (you should have blocked this via a Magisk module etc) or 2) take the Direct install method for updating Magisk (Magisk updates must be done by repatching) or device will become unbootable and unrecoverable without unlocking the bootloader again (and thus, triggering a data wipe)...
Further to avbroot pitfalls, if you're on Android 13 QPR2 Beta 1 (T2B1.221118.006) or later Betas (and possibly even latest stable), Magisk patching boot IMG has been failing due to Compression method of ramdisk in Pixel 6 boot image is incorrect #6441. This has meant that P6 series Beta ROM users have needed to use/patch a corresponding P7 series boot.img (yes, boot.img not initboot.img... Magisk actually adds the missing generic ramdisk) to have working Magisk... So P6 pro users would patch/flash boot.img from corresponding P7 pro Beta build...
- This issue was deemed by Magisk Devs a Google issue not to be fixed in Magisk, but this has just changed with this fix for the incompatible compression algorithm merged only hours ago: Force ramdisk format to lz4_legacy for v4. So with 25211, P6 users should no longer need to patch P7 images to use Magisk...
I have no experience with Pixel device at all, but as long as you haven't disabled OEM Unlocking it seems to me:
- You should be able to recover device at least by unlocking bootloader and fastboot flashing with factory reset (if OEM Unlocking is enabled)...
- You may even be lucky enough to be able to (dirty) flash without unlocking or data wipe if you have carefully avoided any operation that causes an unsigned or differently-signed boot image to be flashed.
Magisk with a locked bootloader was always going to be fraught (trouble)... Hopefully the above notes will be helpful however...
And Pixel users will be better able to advise on recovery options... PW