Alright. If you want to try again send me a pm, I'll send you an updated anykernel.zip so we can check if that changes anything for you.
did you try "fastboot getvar all" in bootloader?
Yes i was flashing the update with -w removed but it wont reboot to fastbootd to continue the update, so i extracted the update image and did fastboot update image.zip and updsted this way, Will try the getvar and report back
It might need a complete wipe as I don´t think the new zip will fix whatever is wrong currently. There might be a chance it might not make the bug appear though, if the underlying issue is not present on a clean installation.
I guess there are no corrupt files. It's probably related to verity and something is screwed up there, which throws up this corrupt warning.
It could very well be related to verity. When I first returned from protonAOSP to stock January update I did not disable verity (just wiped and updated to January) and that's when I had the issue.
How is protonaosp? Compared to stock, as i will only wipe my phone if im going to flash proton otherwise no
It was buried in posts because after my previous flashing issues, I went through and was reading pages after pages about the patching because I did not want the issue again.
It was a good rom, snappier than stock and a little bit better battery life, but not as customizable as I had hoped it was. Also, I had a glitch to where if I would try to check an email it would not load on the first try, I would have to back out and then re-open the email to have it load properly. Other than that, it was pretty solid.
Correct. If you're already rooted, flashing the kernel.zip via exkm for fkm will preserve root.
Thank you very much for the kernel, I have been using your kernel on my Pixel 3.Correct. If you're already rooted, flashing the kernel.zip via exkm for fkm will preserve root.
Follow the instructions in the first post.
This fixed my issue finally! Just reflashed Jan Firmware with disabled verity and v1.5.0 kernel works now
Managed 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)
