So ive decided to release precompiled apk binaries with random pkg names on my telegram group channel separate instead of custom change ability due to obvious security hazards and unstability, if anyone wants to avoid HMAL for this PKG ID detection issues then you can install this separate release, upto your wish to install

will keep changing pkg ids if it gets detected in the future but the main KSUN manager will always be com.rifsxd.ksunext

new random pkg id build coming in 10 - 20 mins.

https://t.me/ksunext_group/73411

Go grab it

Bye bye ksun detection

No HMA/L used

A little reminder,

You have to uninstall the original KSUN manager to install the spoofed manager

Stop asking me to add KPM support to KSUNEXT, it's useless and very unstable and experimental and hugely vulnerable to inject code to the kernel, which mostly is being used for cheats and malicious usecase and i won't support this movement at all.

To all the fucking scammers, yes you! Go die in hell for scamming people for 30 to even 100 usd for ksunext installation and setup, you are getting paid for something i maintain for free, i hope you all die in hellfire for scamming innocent people for so much money and blackmail them to brick them, who ever is this mr.root go kill yourself please.

If anyone needs help for anything related to ksunext, just fucking dm me or ping me in the group t.me/ksunext_group i always see your message and help whenever i can don't fall for these scams

Imagine paying scammers instead of donating to open source projects 😭

Apatch next I pay 50usdt

I have seen a total of 10 - 15 people paying for ksunext rooting which would sum upto a thousand usd

I'm gonna go insane in Telegram

A bit of FYI,

If you want to use sound modules i.e Dolby and Viper4Android then you need to disable umount for those sound module apps for the processing to work correctly.

To address the issue on the proprietary code of ksuinit being closed source, it also exists on ksunext, since we are really against closed source software, it makes sense to drop LKM mode to keep ksunext fully open source, but it makes sense for them to keep it closed source for obvious reason to not be exploited by others and possibly code theft or a reason something entire unknown but it's making a fuss over the community, tbh i could just drop ksuinit LKM mode entirely from ksunext in next release untill we can reverse engineer it or an entirely alternative new code to replace the proprietary code ksuinit.

Till then ksunext may not support LKM.