don´t flash 1.4.0 on November build. It´s made for december and won´t boot on november firmware.
Oops, glad you noticed that.
I think it should work to not disable the vbmeta flags on 1.3.0 if the boot.img provided in the download section is patched with magisk 23016 and the instructions are followed correctly.
I think the difference is that there is no flashable zip for 1.3, so the 3 separate images have to be flashed. But patching the provided boot image with Magisk 23016 before flashing should bypass the need to disable verity & verification.
yes, it´s ultimately related to magisk, but it also affects the kernel.zips.
That's probably the easiest solution if you're patient enoughThank you very much for the great support and the detailed answers
So I'll wait for the upcoming january update (and probably the corresponding kernel update?) before flashing this beauty.
I want to flash it as a flashable zip and do not want to do a factory reset. For my understanding I don't need to disable the verify and verification flags for future kernel updates with the latest magisk canary?
All a bit confusing. Wasn't that complicated on the phones I had before
Thanks! I must've been confused and thinking that I was responding in someone else's kernel thread. Oh crazy me!
looking forward to the new release tho.
Yes flashed it too, it works fine.I can confirm v.1.4.0 works fine with January update
forum.xda-developers.com
I was on December build.Boot failure, but on a dirty flash of the January factory image using the below method and flashing the kernel with the EK Kernel Manager.
Rooting with the newest Magisk.
Method to upgrade every month, without wiping data and retaining root
Caution: I originally wrote this guide when it was necessary to disable verity and verification before flashing patched boot.img. Now Magisk has overcome this requirement and some users have reportedly flashed updates without disabling...
Well, some people are rooted in tradition....Some would even say that you need to "commit" to this hobby in order to root safely.
I'll see myself out now...
This is only for the stock kernel. A few things have changed with the Pixel 6 boot image that have required Magisk fixes. If a kernel developer is using the stock kernel as a base and incorporates the same changes, then yes one would want to use the latest Canary. However, many developers either use an old base, or build their kernel from scratch using the original kernel source; in those cases one could probably use almost any version of Magisk since 24000.Sorry, but I was referring to the above guideline. Returning to stable now.
Some would even say that you need to "commit" to this hobby in order to root safely.It's important to pay attention to the commits and update notes
echo 1 > /sys/module/damon_reclaim/parameters/enabledManaged to reproduce the issue. It´s a magisk issue that surfaces probably since 2.0.1 where direct USB access was added and was not kernel related.
05-08 08:45:40.268 778 778 D Zygote : Forked child process 18269
05-08 08:45:40.269 3697 5245 I AssistantForeground: Get launcher package: com.google.android.apps.nexuslauncher
05-08 08:45:40.269 1579 1769 I ActivityManager: Start proc 18269:com.cm_prod.bad/u0a313 for pre-top-activity {com.cm_prod.bad/com.e_i.bad.controls.activities.StartActivity}
05-08 08:45:40.271 18269 18269 I Magisk : zygisk64: [com.cm_prod.bad] is on the denylist
05-08 08:45:40.274 18269 18269 D Magisk : denylist: Unmounted (/system/bin/magiskpolicy)
05-08 08:45:40.274 18269 18269 D Magisk : denylist: Unmounted (/system/bin/magisk)
05-08 08:45:40.274 18269 18269 D Magisk : denylist: Unmounted (/system/bin/app_process64)
05-08 08:45:40.274 18269 18269 D Magisk : denylist: Unmounted (/system/bin/app_process32)
05-08 08:45:40.275 18269 18269 D Magisk : denylist: Unmounted (/system/bin)
05-08 08:45:40.275 18269 18269 D Magisk : denylist: Unmounted (/product/overlay)
05-08 08:45:40.272 18269 18269 W main : type=1400 audit(0.0:1514): avc: denied { search } for name="firmware" dev="dm-4" ino=722 scontext=u:r:zygote:s0 tcontext=u:object_r:vendor_fw_file:s0 tclass=dir permissive=0
05-08 08:45:40.276 18269 18269 D Magisk : denylist: Unmounted (/dev/G8MMn)
05-08 08:45:40.277 18269 18269 D Magisk : denylist: Unmounted (/system/etc/hosts)
05-08 08:45:40.277 18269 18269 D Magisk : denylist: Unmounted (/system/app/Stk)
05-08 08:45:40.277 18269 18269 D Magisk : denylist: Unmounted (/vendor/etc/powerhint.json)
