Nope, I'm doing everything right. Right Magisk, on dirty flash after installing the kernel, boot failure. I'll wait for an updated kernel. 
No i like to keep track of the download count via android file host.Thanks for the fast update
Any hope you'll could provide a FKM json config ?
Keep it disabled, it works flawlessSo to update there are three methods now?
1. Old way prior to 1.3.0
2. New manual way (which can either be done via ADB of exkm)
3. The .zip file to flash via e.g. exkm
Is that correct?
Also: If I currently have verity disabled, does flashing the kernel still work or do I need to enable verity first (which will factory wipe the device)?
No that's not really correct. 1.3.0 instructions are just for 1.3.0 and below. I guess I'll remove them from the OP now, as nobody will be on November any longer.So to update there are three methods now?
1. Old way prior to 1.3.0
2. New manual way (which can either be done via ADB of exkm)
3. The .zip file to flash via e.g. exkm
Is that correct?
Also: If I currently have verity disabled, does flashing the kernel still work or do I need to enable verity first (which will factory wipe the device)?
The biggest risk is unlocking the bootloader and rooting the device. Pay attention to what you install or run on your phone, then you will be fine.
Do we still need to flash the additional Powerhint magisk module with the kernel?
No just sideload it and you are good to go.Ok last question for me I think. If I flash this do will I have to remove it to flash to the next pixel update?
Updating via fastboot flashing (e.g. flash-all.bat) the next update will remove the kernel. You actually don't want to keep the kernel when updating. For example, the 1.4 version was made for December. If you flashed it on the November build it wouldn't boot (and vice-versa I believe). So you could run into problems when updating if the kernel you are on is not compatible with the new firmware. It's always best to wait until the developer updates the kernel for that specific firmware.Ok last question for me I think. If I flash this do will I have to remove it to flash to the next pixel update?
Ok, that is good then, so when I update to the newest Pixel update this won't cause an issue, I will just have to reflash the kernel if I want to/when it's updated.Updating via fastboot flashing (e.g. flash-all.bat) the next update will remove the kernel. You actually don't want to keep the kernel when updating. For example, the 1.4 version was made for December. If you flashed it on the November build it wouldn't boot (and vice-versa I believe). So you could run into problems when updating if the kernel you are on is not compatible with the new firmware. It's always best to wait until the developer updates the kernel for that specific firmware.
Correct, if using fastboot to update.Ok, that is good then, so when I update to the newest Pixel update this won't cause an issue, I will just have to reflash the kernel if I want to/when it's updated.
Be careful bro. Restoring stock might soft brick the device. Has happened to me more often than not with other kernels.I flashed the latest with EXKM, no issues. I did back up the stock kernel first but I haven't tested restoring same. The OP instructions differ so I'll defer. I flash the full build without wiping rather than side load OTAs and re-root afterwards, I do disable all Magisk modules and flash kernel last but I'm just a creature of habit.
If you know this is completely off topic why not open a new thread with a question tag and just describe your problem there?Off topic: pixel 6 here, i installed a gms doze magisk modules & uninstalled it, sometimes i receive notifications as a bulk at once when i switch from mobile data to wifi & vice versa, now on since yesterday im only receiving whatsapp notifications, i dirty flashed jan. Firmware image but nothing changed, cleared gms & google apps data but also nothing (sometimes after clearing google app data notifications arrive then stops again)
Im sorry i know its off topic but if anyone have any tip on how to fix this, thanks
Installed & uninstalled the modules & still no notifications, ran (dumpsys deviceidle disable) still also no notifications
The instructions for manual flash of kernel are in post #5. Keep in mind, OP does not support this process anymore.Is there any way to manually flash? I want to try it on latest beta cause I want full magisk. Rn I'm with p7 boot workaround for root. So I have root and magisk modules enabled for the already installed apps that need root but since magisk can't recognize root can't give root permission to new apps or flash modules. The thing is that I can't install this kernel as well since I can't grant root to kernel flashers. Funny thing I uninstalled kernel flashers done days ago cause I hadn't use it for long and it already had root.... Any way to flash this kernel? I don't even know if it will boot. Thanks