yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] xflowy:
hey guys!

Any ideas on how to fix the following message in Magisk? Also the Update Button at the top of the app wont go away too, despite having installed Magisk directly over the app already.

Your device needs additional setup for magisk to work properly.​
[Google Pixel 6 Pro] Jindivikk2:
What I did was uninstall then reinstall magisk, patch the boot.img then flash the new magisked boot.img
[Google Pixel 6 Pro] rav101:
I had this when I was rooted on stock (though everything worked fine anyway). When I patched and rooted Kirisakura on a newer version of Magisk Canary, the issue went away. I had to patch the Kirisakura boot.img and flash it I was already on the latest version of the app and that didn't need uninstalling and reinstalling.
[Google Pixel 6 Pro] nafi2000:
Iam on a rooted phone , flashing this kernel need verified boot command before flashing each items ? Or just patched boot image ?. Does that wipe my data ?
[Google Pixel 6 Pro] notegalaxy:
1.0.5 all gone smoothly on my device. used latest magisk canary and no issues with root.

I just followed the instructions on the first page word for word and all went well. make sure you patch the boot.img in magisk canary before proceeding. No data wipe this end and booted up fine.
[Google Pixel 6 Pro] nafi2000:
What is the adjustment in the command for flashing boot image ?--disable-verity and --disable-verification ?

do we need to flash vbmeta again ?
[Google Pixel 6 Pro] Freak07:
If you did the vbmeta step when initially rooting the phone, just patch boot.img if you want to stay rooted and follow the instructions.
[Google Pixel 6 Pro] nafi2000:
VB meta step done in rooting and I believe it has disabled verification till I flash vbmeta again. So I just need to simply flash patched boot image without any issue. Ok. I got it thanks
[Google Pixel 6 Pro] cultofluna:
You're flashing vbmeta with the flags disabled just once before rooting..

After you can flash whatever you want...
[Google Pixel 6 Pro] notegalaxy:
Those commands are only for vmbeta (vbmeta flashed with disabling verification and verity flags) as a prerequisite. are you on stock kernel rooted or kiri 1.0.0/1.0.2 rooted? you don't need to flash vmbeta again, but if you are on an older kiri version you have to flash the stock vendor_boot img. If you are already rooted just follow the instructions on the first page
[Google Pixel 6 Pro] Burt Squirtz:
Oh! One thing I wanted to ask is, if you're already rooted on a lower version of kirisakura, do you still have to follow all the same steps?
[Google Pixel 6 Pro] Freak07:
It´s always best to flash all three provided images, even if one release might have no changes that end up in the dtbo.img for example. Avoids errors and is simplest way, since you need to be in fastboot/fastbootd anyway for flashing.

Next version will probably have modifications that end up in vendor_dlkm for example.

It´s just easier to always flash all three provided images, instead of checking each release what to actually flash if not all three need to be updated anyway. Avoids confusion, errors and other things.
[Google Pixel 6 Pro] Utini:
Except when you flash an OTA updated (or rather the factory images for updating)?

Then you havee to disable vbmeta right after flashing but before booting?

E.g.:

fastboot --disable-verity --disable-verification update xxx.zip
[Google Pixel 6 Pro] MArtyChubbs:
Thanks @Freak07

So far so good! Jumped in on 1.05 and no issues at all.
[Google Pixel 6 Pro] daniel.1983:
Same here with V4A, no issues! Thanks
[Google Pixel 6 Pro] Lughnasadh:
Thank you for making our pipes clean again 😁
[Google Pixel 6 Pro] jcp2:
Sorry it took so long to respond. Thank You so much. I followed the instructions and am updated to 1.8.4 now. Still getting random reboots often. Here are the files you wanted.
[Google Pixel 6 Pro] mohammed510:
Tested on latest Proton rom that is based on 12L and march security patch. However I'm still having touch issues and long press doesn't work on the sides of the display. Tested on clean install
[Google Pixel 6 Pro] Freak07:
That probably means proton doesn't use the updated Touchscreen firmware/drivers from the beta with march security patch yet.

I don't have the time to compile another build just to account for this. So for the time being you'd either have to stick with the issue or restore stock proton kernel.
[Google Pixel 6 Pro] jcp2:
@Freak07 Any Idea why 1.7.0 is great but 1.8.4 causes my phone to reboot every 3-5 mins?
[Google Pixel 6 Pro] Admiral2145:
Do a fresh install... I went from 1.7 to 1.84 no issue and updated to newest beta 3 modem with phenomenal results.
[Google Pixel 6 Pro] jcp2:
I did a fresh install yesterday back to stock kernel and then to 1.8.4 and reboot city :( then Back to stock kernel and 1.7.0 and stable as can be.
[Google Pixel 6 Pro] Jiggs82:
Can u send a screenshot of your about phone? Are you sure you downloaded and flashed the 1.8.4 kernel for Raven Feb patch 12 stock Rom? Are u using any mods?
[Google Pixel 6 Pro] jcp2:
I am 100% sure that I download 1.8.4 from the A12 raven folder. I am on the stock A12 Feb update v2 rom. My about would show you that I'm running kiri raven kernel 1.7.0 because 1.8.4 just reboots constantly. @Freak07 asked me to post the pstore folder from root dir as soon as my phone rebooted. I posted the folder, just waiting for him/her/them to take a look and respond.
[Google Pixel 6 Pro] Jiggs82:
Ok then what about any mods? That could be causing the reboots to because when I was Feb a12 stock n Kiri 1.8.4 kernel I didn't have any reboots. It was running fine...
[Google Pixel 6 Pro] jcp2:
Just Magisk 24.3 and Universal SafetyNet Fix (Zygisk) v2.2.1 and Magisk Hide Props Config v6.1.1 - Zero issues when 1.7.0 is installed.
[Google Pixel 6 Pro] Freak07:
I took a look at the log and I don´t know why this would happen only to you and nobody else seemingly, but I can see the kernel crashing.

Did you flash the kernel.zip or followed the manual instructions? You said you downloaded from the raven folder, I´m a bit confused as there´s no raven folder, just zips/files labeled with raven/oriole.

If you did the manual installation, did you make sure to also flash the powerhint magisk module?

Attached is a kernel.zip for you to try and see if you still run into this issue.

This is for stable A12, not the beta!
[Google Pixel 6 Pro] jcp2:
I followed your instructions in post #4 to manually flash the individual files from the Raven factory firmware zip to get back to stock kernel. Then I Patched the stock boot.img in Magisk 24.3 to get root. I then flashed 1.8.4 with exkm. I did not flash powerhint module though. Here is the link I used for 1.8.4 https://androidfilehost.com/?fid=2981970449027570894

Is this the correct link for the powerhint module? https://androidfilehost.com/?fid=2981970449027570903
[Google Pixel 6 Pro] Freak07:
Alright that´s good. If you flashed the 1.8.4.zip, you´re not supposed to flash the powerhint module so that´s fine. (it´s only for the manual installation of the kernel, for users not flashing the zip via a kernel manager):)

If you find some time it would be great if you could report back about the 1.9.0 zip. :)

After the installation you´ll see the AK3 helper module in magisk manager module list, which includes the powerhint module.
[Google Pixel 6 Pro] jcp2:
Thanks for the help. So to confirm, When I flash 1.9.0, I should not flash the powerhint module. Can I dirty flash over 1.7.0, or do I need to go back to stock kernel first? I'll follow up in the morning. It's 1:17 am here, and I don't want to Bork the phone doing it while I am so tired.
[Google Pixel 6 Pro] Freak07:
yes. if you flash the zip via any kernel manager app, instructions in post #1. (powerhint module is included in the kernel.zip)

if you decide to do the manual installation as per the instructions in post #4 and flash the images via fastboot, the powerhint module needs to be flashed separately.

You should be able to dirty flash. but if you have some extra minutes, restoring stock first via fastboot/fastbootd might not hurt.

Alright. I hear from you later then, have a good sleep. :)
[Google Pixel 6 Pro] jcp2:
My OCD woke me up! UPDATE..... dirty flashed 1.9.0 over 1.7.0 and have been using my phone for 30 minutes with zero reboots!!!! :) :) :) Thank You so much @Freak07 You are a rock star!

I'm going back to sleep now ;)
[Google Pixel 6 Pro] mohammed510:
Can i flash despair over this one or should i flash stock first?
[Google Pixel 6 Pro] Freak07:
It's always better to restore stock. It doesn't matter in case of boot, dtbo and vendor_boot, but since both zips contain vendor_dlkm, which is part of the super partition, it's better to restore stock vendor_dlkm via fastbootd, not flashing via exkm.
[Google Pixel 6 Pro] Nekromantik:
thanks for all the work and help you give all @Freak07

you are one of the better devs on xda who hardly complains or is rude even though sometimes its difficult when members here are not very polite.

im not on 12L yet but look forward to flashing your latest edition once March firmware is released.
[Google Pixel 6 Pro] krystiano:
I have question.

I have never flashed custom kernel for any phone.

I just want be sure.

At the moment I'm on stock kernel. I just rooted my phone.i have magisk and few modules as well.

It's worth to instal cutom kernel ?? (I know on first page is all benefits listed but some of them i don't understand 🤪🤪)

Can I use app. Franco kernel manager to flash this kernel ??

What when I have OTA update from Google?? (I'm on A12 stock with February)

Thank you for any answer.
[Google Pixel 6 Pro] jcp2:
you can use franco manager or exkm. I use exkm because it is more familiar to me.
[Google Pixel 6 Pro] Freak07:
I suggest to use google if you don´t understand everything that´s in the first post. :) The first post is pretty detailed already with a lot of links.

Yes you can use either FKM or EXKM to flash it.

You need to follow one of the guides found on this forum to update your phone when an update is available. But you already need to follow those guides when you rooted the phone.
[Google Pixel 6 Pro] krystiano:
Thank you guys @jcp2 and @Freak07 for your help.
[Google Pixel 6 Pro] vassosman:
Flashed 1.9.0 via FKM on QRP3 Beta and its just chilling at the boot screen with the bar loading. Will leave it for a bit, but might have to revert to 1.8.9 when I get home if its not working.
[Google Pixel 6 Pro] Freak07:
1.9.0 will not work on the beta. It's for stable A12. It was compiled for a user having a kernel panic on A12.

I edited the post to reflect this, so nobody else will accidentally flash it.

Sorry about that.
[Google Pixel 6 Pro] krystiano:
So last official is 1.8.4 yes??

I'm on 1.9 with no problems but I'm on A12
[Google Pixel 6 Pro] jcp2:
I was that lucky user, and it wasn't just the kernel that was having a panic either...... JK ;) :)
[Google Pixel 6 Pro] vassosman:
Might I suggest a new naming/version scheme?

12.1.9.0 vs 12L.1.8.9??
[Google Pixel 6 Pro] Freak07:
Maybe a good idea for the future. 👍

Though all previous kernels i put out for A12l had A12L in the filename.

I probably enable also the androidversion check in the zip, so the A12 zips will just abort flashing on A12L and vice versa.
[Google Pixel 6 Pro] vassosman:
Also fwiw, Samsung USB-C to 3.5mm is causing rebooting on QPR3 with 1.8.9 when unplugged

Also, when I post here I'm not trying to get a fix asap. I appreciate your work and never mean to sound like I'm rushing or anything lol
[Google Pixel 6 Pro] Divine Bicycle:
I'm getting high temperatures on the latest build. Constantly high even though I don't ever use my phone for anything more strenuous than watching YouTube videos or making videos around 1 minute long. I have been reading for the last 20 mins and this is the temperature :

Edit: just realised this image only shows 58°C. When I looked it said 71°C.
[Google Pixel 6 Pro] Freak07:
capturing a video is not really light usage. Immediately afterwards temps might be a bit higher.

Things to keep in mind:

CPU gets boosted to max upon opening any app. So immediately after opening FKM temps for the first three sensors are similar to your screenshot (or even higher) . After a few seconds they drop to lower levels on my end.

Two screenshots attached, one immediately after opening FKM and one about 15 seconds later.

It seems your device is generally just warmer than mine, especially when looking at the other sensors from your screenshot.

You'll notice some sensors, the ones closer to the CPU/GPU drop/rise more quickly than others, which are further away from the SOC itself. (That's why you also didn't catch them at the temp you saw briefly with the screenshot.)

With no active cooling the temps closer to the SOC can't drop below the levels or a certain threshold that's usually a bit above the temps further away from the SOC.

That means with a generally cooler device the temps of sensors closer to the SOC will also drop below levels of those of a generally hotter device, but also do so faster.

It can have many reasons why one device is seemingly generally "hotter" than another. Power source connected, ambient temp, using a case that traps heat (also when holding it in warm hands vs the device sitting resting on a table),keeping the device close to the body in a pocket and start usage from there vs keeping it on a desk, various usage patterns, installed apps, background usage of apps, network reception.... Etc.

Check your background usage for any apps that might hog resources. You can do so via top command, i explained that a few days inago already. The kernel just grants CPU cycles to apps/services that request it.

Please zip up and post contents of sys/fs/pstore immediately, once your device has rebooted after the crash. :)
[Google Pixel 6 Pro] Freak07:
hey,

please try this kernel on QPR3 and see if unplugging still crashes the phone.
[Google Pixel 6 Pro] vassosman:
Loaded it up. I didnt have the samsung adapter as I'm at work right now but tried the ESR (bought onamazon) adapter and no reboots! Will keep you posted.

Also fwiw, QPR3 is still "Android 12" according to the flash script.
[Google Pixel 6 Pro] Freak07:
thanks for testing the USB C thingy. :)

Yes, google refers to Android "12L" still as Android 12 in device props.

You can check ro.build.version.release on your device running 12L firmware and it will still return "12". That´s what the zip checks for.

To circumvent this I added a check for sdk version. The zip you flashed will only flash to 12L (sdk32) at the moment and abort if it´s flashed on stable february firmware (sdk31).

Unfortunately that check will stop working once march stable firmware will drop and supposedly bump to 12.1.0 as well. Then sdk will be 32 for stable as well. :)
[Google Pixel 6 Pro] spr33:
Silly question but I can't seem to find any info anywhere about it:

Does the kernel force 120hz? Mine doesn't seem to dip below 120hz even when idle.

12L QPR build. No unusual tweaks or mods. Checked top for unrulely processes and nothing.

Curious to find out before I investigate what it could be.

(Oh, and yes, I've checked settings and dev options to make sure it's not set to force 120hz) :)

Edit:

Just wanted to point out that forcing to 60hz reduces it to 60 and also when enabling battery saving mode does too.
[Google Pixel 6 Pro] Freak07:
No the kernel doesn't force 120hz. Userspace controls refresh rate switching in the end, not the kernel.

Low ambient brightness will force 120hz, low screen brightness will force 120hz. Don't know if there are other conditions.

Using camera will force 60hz for example.

It's all set by userspace. So if it gets to 60hz on power save mode, something with dynamic refresh rate service (display idletimer) might be wonky.
[Google Pixel 6 Pro] Sek0n:
Just a warning if you're on magisk canary. Don't take the update today. It made my phone bring up the "Your phone is corrupt, and may not work properly" message at boot, then just hung at the google logo.

Dirty flash of the OS got it working again. Tested installing the kernel again, and it still did it. Repeated, but used stable magisk, and the kernel worked. Still have the corrupt message now tho.

Now I'm going to bed lol
[Google Pixel 6 Pro] Lughnasadh:
I can confirm this. Got stuck in bootloader mode after flashing Canary 24303 while on 1.8.9 (12L). Reflashed the stock boot.img, dtbo.img, dtbo_vendor_boot.img and vendor_dlkm.img to get back to stock and it booted.

Repatched the stock boot image with Canary 24303 and it booted.

Reflashed Kirisakura 1.8.9 (12L) and got stuck in bootloader mode again. Did not get the corrupt message after any of this but I still have verity and verification disabled.

I'm on QPR3 Beta 1.

@Freak07
[Google Pixel 6 Pro] cmh714:
I am on 12 using 1.90 and got the same......
[Google Pixel 6 Pro] Lughnasadh:
May be the new sepolicy injection mechanism introduced in 24302 and 303 🤔
[Google Pixel 6 Pro] cmh714:
Yeah, gonna leave the kernel alone for now :)
[Google Pixel 6 Pro] Nekromantik:
glad I saw this before I updates Magisk! Will stay on 24301 until kernel is updated
[Google Pixel 6 Pro] Face_Plant:
*sigh* I really wish I'd seen this before updating Magisk on my lunch break this afternoon and soft bricking my phone...

Is Magisk canary still required for root on Android 12, or will stable/beta work now?
[Google Pixel 6 Pro] Lughnasadh:
Stable/Beta will work fine.
[Google Pixel 6 Pro] Freak07:
It seems the magiskboot binary from the new canary is not playing nicely with the slightly outdated one that´s in my anykernel.zip for repacking the kernel while flashing.

I guess it´s called canary for a reason...

Here are zips that should allow updating to the latest magisk canary.

First flash the kernel.zip matching your device and firmware. Then updating to the latest canary via magisk manager should work.

Everybody that ran into a bootloop, can just restore back to stock kernel by flashing boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img via fastboot/fastbootd. Then update to latest magisk canary by patching the boot.img and flashing again via fastboot.

Zips for stable A12 are labeled with "A12", for the QPR3 A12L Beta are labeled with "A12L".
[Google Pixel 6 Pro] WhoIsJohnGalt1979:
@Freak07 Does that take care of the "Device is corrupt" message? I tried downgrading the canary to 24301 and also stable 24300, the error message stays, functionally am able to use stock kernel with 24303 and any kernel based kernel on 24301 and 24300, but regardless, that device is corrupt stays. Any thoughts?
[Google Pixel 6 Pro] Freak07:
Can´t give you an answer as I simply don´t know.

Something with verity is not how it should be. There´s a thread were I read about assumptions some of the verity tables get corrupted, which causes the message to be displayed.

It happened seemingly randomly to others. It fixed itself for others randomly after updating their devices when a new firmware update dropped.

I´m running with verity disabled since I got the device and didn´t see it once.

I think it´s related to keeping verity enabled and relying on magisk patching the boot.img, since whenever the canary allowed for keeping verity enabled.
[Google Pixel 6 Pro] WhoIsJohnGalt1979:
thank you for that reply. This echoes with what I have read from @Lughnasadh. Helps me reconcile with the situation mentally lol. I do not have verity disabled. Thanks again.
[Google Pixel 6 Pro] cmh714:
Maybe I read/did something wrong, but the new kernel still locks up my device....
[Google Pixel 6 Pro] Freak07:
You're on a12L?
[Google Pixel 6 Pro] cmh714:
Sorry for not posting that info....I am on 12 Stable
[Google Pixel 6 Pro] Freak07:
I was able to flash the 1.9.0 zip without problems on A12 stable while being rooted with magisk 24303.

Verity is disabled on my end. Don't know if that could change anything in that case. How about you?
[Google Pixel 6 Pro] cmh714:
Well then damn. :) I flashed factory, I repatched boot with new magisk and flashed that, then flashed your kernel in EXKM...any other suggestions? and TY!!
[Google Pixel 6 Pro] Jerreth:
likewise i just flashed fully factory image wiping all and re rooted flashed your 1.9.0 on stock android 12 and then flashed the 24303 and it is black screen no boot with the corruption error.
[Google Pixel 6 Pro] cmh714:
I actually get as far as Google showing up but it sits there forever....
[Google Pixel 6 Pro] Jerreth:
just flashed back to stock and it boots but the corruption message is still present now i guess i need to disable verity check to lose that huh
[Google Pixel 6 Pro] Jerreth:
hmmm after verity disable it will not boot either i must be doing something wrong
[Google Pixel 6 Pro] Lughnasadh:
Using:

QPR3 Beta 1

Canary Magisk 24303

The new 1.8.9 12L kernel

Verity and verification disabled

Just flashed the new kernel while being on Canary 24303 and got stuck in the bootloader, as reported earlier. Flashed the 4 images to return to stock. Flashed the patched stock boot image and it booted fine. No corruption message.

Appears the newest kernel version is still not working on QPR3 Beta 1.
[Google Pixel 6 Pro] Jerreth:
is there a link to properly disable verity and verification? i would like to do this but when i ran the command it stopped booting

nevermind i found i need to wipe again lol ill leave it enabled.
[Google Pixel 6 Pro] Lughnasadh:
Put the vbmeta image in your Platform Tools folder and run this command. WARNING: You will have to wipe/factory reset your phone for your phone to boot.

fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
[Google Pixel 6 Pro] Jerreth:
so if i do this do i just install the stock firmware over whatever is there and let it wipe or do i need to factory wipe from within the recovery?

Also is this something that must be done after installing an update? say the latest image with the -w removed?
[Google Pixel 6 Pro] WhoIsJohnGalt1979:
lol @Lughnasadh to my rescue again. I was on Q3B1 when I chose to update Magisk canary 24301 to 24303 and encountered the Device is Corrupt message. I tried wiping my device twice, downgrading Magisk etc to no avail when I chanced to see the words in bold, you have to trick your phone to see a new OS has been installed. So I took a chance and wiped installed Android 12 Feb update and lo behold, the error message vanished, I wiped flashed Q3B1 subsequently and am back to normalcy lol....Been quite an afternoon.
[Google Pixel 6 Pro] Lughnasadh:
After running the command it should throw you into Rescue Party where you will have an option to factory reset.

If you want to keep verity and verification disabled then you must keep it disabled on every update (since updates replace the vbmeta with the disabled flags with the stock vbmeta). If using flash-all to update, just remove the -w and replace it with the disabling command (see screenshot below).
[Google Pixel 6 Pro] Jerreth:
wow right on thank you so much for that, im hoping that when the march update drops this will not be necessary for me this is the first time i have ever seen this error.
[Google Pixel 6 Pro] Lughnasadh:
Actually, if you don't want to wipe there is a chance that when you update to March the corrupt message may disappear.

But that doesn't mean you won't get it again. So your choice of whether to disable verity and verification.
[Google Pixel 6 Pro] Phascinate:
Here's a copy of the 24300 version of Magisk for the latest Beta for anyone who needs it to flash manually (Pixel 6 Pro). If needed, I can get you a copy of the Pixel 6 version.
[Google Pixel 6 Pro] Jerreth:
yeah i may do that i just factory wiped today ill see what happens with the update if it fails to fix it ill wipe and disable :) thanks for your input and help
[Google Pixel 6 Pro] Phascinate:
I actually got the corrupt screen to go away by simply flashing the boot.img of an earlier version of the Pixel firmware (February) and then letting it attempt to boot (but obviously fail) and then flashing the latest Beta boot.img. I don't know why it worked but it reset that screen and it hasn't come back.
[Google Pixel 6 Pro] Phascinate:
Update: Using the 24300 Magisk boot.img for the latest Beta (see above for a download), I successfully installed the 1.8.9 version of this Kernel. Good luck developer! You rock!