[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] Freak07:
FAQ

F.A.Q:

Question: Why does the kernel version show as "unavailable" in settings after flashing it.

Answer: Asus does not allow for custom kernel names in their settings. If the kernel string doesn´t fit their regex, it will display as unavailable there. Nothing can be done about it. Use a kernel manager to check the kernel version.

Question: Is root preserved when flashing this kernel?

Answer: Yes, the AnyKernel.zip will detect root and keep it.

Question: How do I return back to stock or another kernel.

Answer: Extract boot.img as well as dtbo.img from matching firmware you are on and flash the extracted boot.img and dtbo.img via fastboot. If you want to keep root flash back the magisk_patched_boot.img. Or dirty flash your rom.

Question: Why is having Magisk installed mandatory for this kernel?

Answer: Android 10s changes to partitions, doesn´t allow files in system/ and vendor/ to be replaced. This kernel is very far from the stock kernel. To account for this I can´t force load the stock kernel-modules for certain drivers as it happens on kernels that are closer to stock.

Instead we use Magisks function to overlay certain files during boot. Without a working Magisk environment the kernel cannot function.

Question: I have a phone that is converted from CN to WW and now there´s a warning from hardwarestub. Can I hide it?

Answer: Yes, I created a Magisk Module for those that want to hide the notification, so nobody needs to rely on paid apps.

The Magisk module can be found attached to this post.

Please note that refresh rate can´t be changed when the module is flashed. To able to change refresh rate or to remove the module, simple remove it in Magisk Manager and do a full reboot. I´ll attach it to the third post on this thread. There will be no support for this module from my side and no other support for converted devices.

Question: How to report bugs properly?

Answer: Have a look at post #3 in the linked thread. The linked guide is a pretty good starting point.

Before reporting any bug make sure you´re running on a stock configuration. That´s means you´re not using any mods, tweaks in kernel managers or other root tweaks , magisk modules, scripts or other modifications that alter various functions like sound mods, data traffic, sleeping behaviour, scheduler, magical battery tweaks etc.

Try to describe the issue as detailed as possible! Give your exact setup, like rom, magisk version, kernel version.

Is the issue reproducible? Does it happen frequently?

Provide logs, otherwise debugging is a lot harder. If you can already reproduce the issue and provide logs it greatly limits the amount of time I have to spent until I figure out how to reproduce it.

If the device force reboots/randomly reboots (that means you see the bootloader unlocked screen!) provide a .zip with the contents of sys/fs/pstore.

If the issue happens while the device is running provide a dmesg plus a logcat that you take while/shortly after the issue happens. This will log what´s running in the current session. Try to be as detailed as possible what´s happening when the issue appears. It will also help me in reading the log!