Development [KERNEL]Radioactive Kernel v1.1.9[A12L] [2022.06.09][UNIFIED PIXEL6/PIXEL6PRO]

[acuicultor]

hi, sorry if this question has been asked but it's been a while since i last rooted any Android phone
first of, thanks for ur hard work. yesterday i've tried flashing your kernal via FKM. rebooted the phone and it stucked at the device is corrupted. i presed the power button, it went away but it just stuck at Google logo
any idea what i've been doing wrong? or is it because i'm on Magisk Canary?

Pixel 6 running 12 L. rooted running magisk Canary 24306

Yes that's magisk canary issue, to get rid of the corrupt message you have to flash February boot.img and try to reboot, it'll fail but the message will disappear, then you can reboot to bootloader again and flash the current stock boot.img (april), once you've rebooted into system without any problem then you can root again but make sure you use magisk stable only

Just a reminder to anyone using fsync off, make sure you have adequate backups, I had a hard reset happen on my device while debugging an apk, and I lost a bunch of data (mostly data written between restarts)

Fsync shouldn't be turned off from the point of view of the security, I've added the option but must be used at the discretion of the user.

 

[fitree]

Yes that's magisk canary issue, to get rid of the corrupt message you have to flash February boot.img and try to reboot, it'll fail but the message will disappear, then you can reboot to bootloader again and flash the current stock boot.img (april), once you've rebooted into system without any problem then you can root again but make sure you use magisk stable only

Fsync shouldn't be turned off from the point of view of the security, I've added the option but must be used at the discretion of the user.

after almost 30 minutes of tinkering, i managed to boot up your beloved kernel flawlessly. thanks a lot for your guidance!

 

[acuicultor]

after almost 30 minutes of tinkering, i managed to boot up your beloved kernel flawlessly. thanks a lot for your guidance!

Nice to hear that you have sorted the problem.

 

[Kris Chen]

When I downloading the fastboot zip file and extracting it. I copy boot.img to use magisk patch boot.img and then replace the boot.img to keep root in my pixel 6 pro.
When executing "flash-RadioactiveKernel.bat" and rebooting phone, it said that data has been crashed and I had to do factory reset. No way to do so I do factory reset and then resetup my pixel 6 pro from the ground. Yes, I have this kernel in my phone now and everything is working well.
Actaully speaking, I have one question here: If next month OTA released, the kernel should be the google default one and I still need to go the same way to flash this Kernel and resetup everything ?

 

[acuicultor]

When I downloading the fastboot zip file and extracting it. I copy boot.img to use magisk patch boot.img and then replace the boot.img to keep root in my pixel 6 pro.
When executing "flash-RadioactiveKernel.bat" and rebooting phone, it said that data has been crashed and I had to do factory reset. No way to do so I do factory reset and then resetup my pixel 6 pro from the ground. Yes, I have this kernel in my phone now and everything is working well.
Actaully speaking, I have one question here: If next month OTA released, the kernel should be the google default one and I still need to go the same way to flash this Kernel and resetup everything ?

No, there's nothing wrong with the kernel and of course a data wipe is not necessary at all to use it, your issue is that you're using an incompatible magisk version, use only magisk stable for root and everything will be fine, this problem is widely known and discussed in almost every pixel6 series thread, in fact i've told the solution literally two post above yours.

 

[Kris Chen]

No, there's nothing wrong with the kernel and of course a data wipe is not necessary at all to use it, your issue is that you're using an incompatible magisk version, use only magisk stable for root and everything will be fine, this problem is widely known and discussed in almost every pixel6 series thread, in fact i've told the solution literally two post above yours.

Thanks for your reply.
Actually speaking, I use magisk stable version to patch boot.img ~ (The version of Magisk in my phone is 24.3 and I think it' stable version if I'm not wrong)

BTW, your kernel is really running so smoothly in my pixel6pro.
Thanks !!

 

[Paz9]

Not kernel related has anyone noticed restricted apps going back to 'optimized' aster a restart? Never noticed this before.
Edit: doesn't happen all the time, just randomly
edit2: it seems app preferences gets reset? some of my apps request permissions to manage files after a reboot.
this never happened before on stock/locked BL. or at least never noticed

 

[Gytole]

Not kernel related has anyone noticed restricted apps going back to 'optimized' aster a restart? Never noticed this before.
Edit: doesn't happen all the time, just randomly
edit2: it seems app preferences gets reset? some of my apps request permissions to manage files after a reboot.
this never happened before on stock/locked BL. or at least never noticed

I have noticed apps even acting like I have never used them before...
For example, I have Tmobile tuesdays installed for a few months now and I have had to resign in three times, and 8 ball pool had me resign in the ither day I thought that was strange? But even snapchat told me to log in twice something weird is going on. Maybe Tensor? No idea...

 

[Paz9]

I have noticed apps even acting like I have never used them before...
For example, I have Tmobile tuesdays installed for a few months now and I have had to resign in three times, and 8 ball pool had me resign in the ither day I thought that was strange? But even snapchat told me to log in twice something weird is going on. Maybe Tensor? No idea...

yes i noticed this with my backup app that runs at 12 am every day. i had to log back in and link my google account again.

 

[Paz9]

yes i noticed this with my backup app that runs at 12 am every day. i had to log back in and link my google account again.

@acuicultor any ideas what's going on?

Usage access, PIP settings all going back to default after a reset. (Sometimes after the 4th reset)

 

[acuicultor]

@acuicultor any ideas what's going on?

Usage access, PIP settings all going back to default after a reset. (Sometimes after the 4th reset)

Idk but that's rom userspace related nothing that a kernel can do.

 

[Paz9]

Idk but that's rom userspace related nothing that a kernel can do.

I figured as much, I even used the flash tool before installing the kernel to make sure everything was stock before using it.

@Gytole curious, do you have naptime installed?

 

[Gytole]

I figured as much, I even used the flash tool before installing the kernel to make sure everything was stock before using it.

@Gytole curious, do you have naptime installed?

Do not my friend, actually? NEVER used it. Know of it, and have known of it for years? Just never used it. I get above average battery life though with my weird techniques

 

[Paz9]

Do not my friend, actually? NEVER used it. Know of it, and have known of it for years? Just never used it. I get above average battery life though with my weird techniques

That's the only change I've done from my last setup.
Very strange, usage access is also getting reset, app restrictions, picture in picture settings.

 

[Admiral2145]

Is this a go on may update?

 

[Kris Chen]

I figured out why I suffered from bootloop ~

I have to flash one commend :
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img

Then it won't bootloop and makes me enter system ... So I needless to format my data and lost everything....

 

[Nekromantik]

I figured out why I suffered from bootloop ~

I have to flash one commend :
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img

Then it won't bootloop and makes me enter system ... So I needless to format my data and lost everything....

You no longer need to disable verity. If you on latest stable magisk then you can just flash. So before flashing kernel, make sure your old kernel is patched with latest stable magisk and then disable any modules. Then flash.
Modules can cause issues also. If Verity was the issue then you wont see bootloop you will see a message saying your system is corrupt instead and it wont boot into android and then you disable verity.

 

[acuicultor]

Hi folks, here comes the monthly update, this month is a HUGE one since i decided to merge kernel common into Google's stable source.

Highlights on this release:
Built on top of Google's MAY 2022 12L source
merged linux stable kernel up to 5.10.101
merged android12-5.10 branch from https://android.googlesource.com/kernel/common
update to latest google clang 14.0.6 prebuilt version
added multi-gen LRU
source clean up (removed various drivers and superfluous commits)

Like always download link and detailed changelog in op.

Enjoy!!!!

 

[phaino00]

Updated May fw (via flash of factory image) and Radioactive (via FKM) and all is good.

 

[Admiral2145]

After I gain root and flash kernel via fkm it bootloops... Then I have to manually flash the full Ota and re-root... Using magisk 24.307 and may update. Am I doing something wrong last update April worked without a issue