[Kernel | Android 10 | One UI 2.5 | FUF5/FUH1/FUJ2/FUK1/FVC2/FVH1] BeastMode Kernel v2 for N960F | v2.18f1a3 | 20230223

[ykkfive]

Hi mate, long time no see. After flash this kernel for noble rom v3.4 FVH1, my device get lost root How to fix it? Thanks.

why patch with v23 instead of v25.2 ? using fvc2 boot.img during v25.2 patching process = bootloop, flashing v23 patched = no root, patching either download with v25.2 = bootloop when img is flashed

sorry i have no time to upgrade to magisk 25.x, nor to test it due to my hands' problems as it may take quite a long time for me to recovery my phone due to my low productivity

pls read my next post

 

[ykkfive]

for those who wanna install newer magisk like 25, you may try the followings:

1 get the boot.img without root
2 open your rom's installation zip file
3 you should find "magisk" and "boot.img" in different folders
4 if this is the case, continue to the next step. else stop here and abort the process
5 extract the boot.img from the zip and save it somewhere as backup (you can roll it back by putting this boot.img back to the zip file)
6 replace the boot.img in the zip with my boot.img and install the new rom

note that as stated in point 4 above, this should let you to trick the zip file script file and installation should process as usual. however, some roms will put a tool to repack the kernel during the installation process (you should find a file/folder named something like AIK). in this case it may not work properly as the rom maker may intented to make some changes to the kernel, and you may have to completely uninstall magisk after boot, then reinstall magisk app and follow the steps to root it


for flashing my kernel with an existing rom (with magisk), you may try:
1 get my boot.img
2 patch my boot.img in magisk app
3 flash the patched boot.img above


common problems for losing root are:
1 with a magisk 25 rom installed, you flashed my kernel
2 you flahsed my kernel and then (re)jnstall the rom

both situations will caused the magisk confused, as flashing my kernel to and existing rom will overwrite the existing magisk, and installing a new rom after flashing my kernel will overwrite my kernel


hope this helps

 

[ColdFishy]

I am unsure whether I did something wrong but it would appear that the max frequency setting for BIG is not respected.
(using MTweak latest). However, max frequency for LITTLE works as intended.
For context - used it to underclock.

EDIT: also LED uses fade regardless of settings (OFF: 800ms in / 800ms out | on works as intended)

 

[ykkfive]

I am unsure whether I did something wrong but it would appear that the max frequency setting for BIG is not respected.
(using MTweak latest). However, max frequency for LITTLE works as intended.
For context - used it to underclock.

EDIT: also LED uses fade regardless of settings (OFF: 800ms in / 800ms out | on works as intended)

they are working properly (i underclock too)

try another manager, or take a look at your saved profile. i have seen the settings in the profile were not correctly saved, with the old settings mixed with new settings in one of the manager before

 

[ColdFishy]

they are working properly (i underclock too)

try another manager, or take a look at your saved profile. i have seen the settings in the profile were not correctly saved, with the old settings mixed with new settings in one of the manager before

Indeed, you are right. Change of manager now makes the BIG respect their settings. (from MTweaks to TTweaks for anyone wondering)

The LED however persists using fade mode. (Testing it via manager diplays the LED correctly, however any actual notification makes it use the fade instead.) Also manager/settings issue?

 

[ykkfive]

Indeed, you are right. Change of manager now makes the BIG respect their settings. (from MTweaks to TTweaks for anyone wondering)

The LED however persists using fade mode. (Testing it via manager diplays the LED correctly, however any actual notification makes it use the fade instead.) Also manager/settings issue?

let me check, coz i use fading mode all the time

 

[ibrahim_qt7]

Hi everyone just want to share the latest benchmark i got with this kernel..
unfortunately no one care about the score anymore but I'll share it anyway

i manage to break 2500 barrier idk if anyone did it with this kernel but i did ... hopefully you guys can share your benchmarks as before.

 

[ykkfive]

Hi everyone just want to share the latest benchmark i got with this kernel..
unfortunately no one care about the score anymore but I'll share it anyway
View attachment 5865921
i manage to break 2500 barrier idk if anyone did it with this kernel but i did ... hopefully you guys can share your benchmarks as before.

yours beat mine
if i remember correctly, i got about 74x and 24xx respectively

nah, i think most of them have joined the one ui 5.x partly already. and records show that only 1/5 of them still interested in this old thing

 

[ykkfive]

Indeed, you are right. Change of manager now makes the BIG respect their settings. (from MTweaks to TTweaks for anyone wondering)

The LED however persists using fade mode. (Testing it via manager diplays the LED correctly, however any actual notification makes it use the fade instead.) Also manager/settings issue?

regarding the led thing, i have tested and you are right. during the test it is fine but not working for other notifications although the "values" are the same in both situations. or maybe by default it is breathing? idk

i would suggest, if you insist, to lower the second silder to 100 to make it as normal blinks instead in your kernel mgr

 

[mihnoi]

Hello. Do I still need to modify fstab for f2fs or can i format using twrp. Also, can i use newer versions of twrp, like 3.6.1 or should i stick with 3.3.1 ? Thx

 

[ykkfive]

Hello. Do I still need to modify fstab for f2fs or can i format using twrp. Also, can i use newer versions of twrp, like 3.6.1 or should i stick with 3.3.1 ? Thx

add the following lines to fstab.samsungexynos9810 (make a backup first) under /vendor/etc:

look for cache ... ext4 and append this line below (1 single line)

/dev/block/platform/11120000.ufs/by-name/CACHE /cache f2fs noatime,nosuid,nodev,discard wait,check


look for data ..... ext4 and append (1 single line)

/dev/block/platform/11120000.ufs/by-name/USERDATA /data f2fs noatime,nosuid,nodev,discard,usrquota,grpquota,fsync_mode=nobarrier wait,check,encryptable=footer,quota


you can try system partition also but it failed to boot on my n9 with magisk 23, some tweaks needed to force magisk to mount it as f2fs but i didnt have time to dig into it

i am stll using the twrp i mentioned before

ps remember to backup /sdcard also coz formatting data partition will erase sdcard too

good luck

 

[Dino-Rhino]

Thank you so much for all.