Part of me wonders (perhaps unjustifiably) if I should continue using those flags even though magisk can now do the job, just in case we might need it again (for different condition), and it would necessitate yet another wipe.Correct. The issue was with the AVB and vbmeta headers in the boot image. Magisk now accounts for this when it performs the patch. We can now update normally - just flash the update and patch the boot image, as simple as that.
Before you ask, no, you don't need to do anything now. Just update to Magisk 23016. When the next update comes, update normally. You don't have to worry about verity/verification, and it won't require a wipe.
No, but there is no other reason that you'd need to use them. The problem was with how Magisk handled the AVB header in the boot image. This has now been fixed. I have not verified this, but I'm willing to bet that if you were to re-disable verity/verification after enabling them, it would be absolutely transparent - as long as you're using Magisk 23016 or newer.Part of me wonders (perhaps unjustifiably) if I should continue using those flags even though magisk can now do the job, just in case we might need it again (for different condition), and it would necessitate yet another wipe.
There shouldn't be any harm keeping those flags, should it?
Interesting - assuming the procedure with Magisk Canary is followed properly, then a wipe wouldn't be needed in going from A11 to A12, correct? Assuming that's true, is a wipe still recommended or no?
Do you have the latest SDK Platform-Tools: r31.0.3 installed on your computer?I followed the steps (I use canary, etc)...but I still get the following message:
target reported max download size of 268435456 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.422s]
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 2.567s
Thanks for your help. I had two fastboot.exe files on my computer. Now it works!Is your bootloader is unlocked?
"sending 'boot' (98304 KB)..."
The boot part is missing the slot it is sending it to Sending 'boot_a'...
Are you using SDK Platform-tools r. 31.0.3?
Check to confirm you are using the fastboot command in the folder you extracted SDK Platform-tools r. 31.0.3?
Open a file manager and do a search for fastboot.exe. It should only find one fastboot.exe file.
Are you using a Windows computer?
Did you try changing the USB cord?
If you do not have another cable try using the 2.0 USB port.
To get the boot.img you want to patch with Magisk. You must extract it from the redfin-sq1a.999998.988-factory-99a9aa99.zip ==> image-redfin-sq1a.999999.999.zip
The command to root with the Magisk patched boot.img is:The patched boot.img does not work for me. I updated to Android 12 a while ago but was not able to root after the update. I did follow all of the instructions in the thread (including using 23016 canary and the most recent boot.img).
I tried both: flashing with fastboot flash boot boot_magisk.img and with --slot all
I used the most recent image and extracted the boot.img file from there. However, the boot process gets far further than before (with the bar below the G), but still ends up in a boot loop. fastboot boot boot_magisk.img also does not work (after having flashed the clean boot.img before). I double checked that the build-number is the one which fits the factory image.
I would be very glad if somerone could help here since I am out of ideas for a solution here.
fastboot flash boot magisk.img
fastboot boot magisk.img
Thanks for your reply!
Did you dirty flash Android 12, removed the -w from the flash-all.bat file?
Because I think we have our wires crossed.
Did you have Magisk Manager hidden before the upgrade?Thank you for your reply!
No, I was previously with root before the upgrade and then lost it.
I managed to fix it. It turns out it were the modules that were preventing my phone to start. I removed them with adb and it started.
I'm not sure if I can upgrade as on my previous attempts, the magisk manager would just not open.
fastboot flashing unlockand press enter.
fastboot rebootat the Command Prompt and press enter.
fastboot flashing lock
fastboot -w update image-redfin-aa9a.999999.999.zip
fastboot update image-redfin-sp1a.999999.999.zip
flash-allat the Command Prompt and press enter.
flash-allat the Command Prompt and press enter.
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash boot --slot all boot.img
fastboot flash boot "name of patched boot".imgwithout the quote marks at the Prompt and press enter.
fastboot rebootat the Prompt and press enter.
fastboot flash boot boot.img --slot all
fastboot devicesto verify communication with phone. It should return your phone's serial number.
You should have your stock image you can push over. I do not think replacing the boot image with another patched image would disable anything. You can also use adb to remove any modules. Regardless heres my patched boot image and the command to remove modules. Power off, connect phone enter this command, hold power button to boot phone.