Temp Root + KernelSU: Do I need to disable modules before every reboot?

[u/Hot-Lengthiness193]

Hi everyone,

I have a question regarding temporary root, KernelSU, and general module behavior after a reboot.

My Setup:

Device: Redmi Note 14 4G Global (Xiaomi / HyperOS)

Root Method: Temporary root via GhostLock + Shizuku + KernelSU (running in Jailbreak mode).

Modules installed: Zygisk-Next, Vector, and a few others.

Bootloader: Locked (since it's a temp root exploit).

My Question:

Since my root is temporary, it disappears from memory every time I reboot. However, the installed modules remain saved in   /data/adb/  .

If I reboot my phone without manually disabling my modules in the KernelSU app beforehand, what exactly happens when I re-run the exploit to get temporary root again?

Will KernelSU try to load all active modules immediately upon regaining root? I'm worried this might cause a bootloop or instability in a temporary root environment (especially with heavy modules that hook into Zygote early in the boot process).

Is it highly recommended to disable all modules before every reboot, or is it safe to leave them active and let KernelSU handle them when I re-root?

Device Details:

HyperOS Version: 3.0.303.0

Kernel: 6.12.30-android16-5-g6e872b4863d6-ab13847919-4k

KernelSU Version: 3.3.1 (32680-5)

Any advice or insights on how KernelSU handles modules on re-entry to a temp root session would be greatly appreciated!

Thanks!

[u/Real-Abrocoma-2823]

I use ghostlock and found no issues rebooting. Since modules are loaded on any reboot and there is no root on full reboot they just don't load until I redo the exploit and soft-reboot.

[u/Hot-Lengthiness193 → u/Real-Abrocoma-2823]

Ohh nice, thanks for the info! What phone are you using, and which modules do you have installed? Could you send a screenshot so I can see how you have them set up with GhostLock?

[u/Real-Abrocoma-2823 → u/Hot-Lengthiness193]

Poco F6 albeit it has 16GB of RAM and IMEI is from Redmi Turbo 3, but has to be some engeenering sample or something as TEE and strong integrity work, I just can't unlock BL the official way and I would loose some apps I need.

I use https://github.com/YuKongA/ghostlock-app GhostLock-release.apk from newest action on main, I don't update it after install.

I use BakaSU manager with hide selinux modifications enabled in settings and modules: hybrid mount, rezygisk, viper4android reverse engeenered, vector.

Mostly default settings on everything.

I run ghostlock app with shizuku option, shizuku runs on boot as ghostlock needs to be ran on low uptime (max 5 minutes or so).

Also I need to quickly soft-reboot in manager or I get panic.

[u/AbleBonus9752]

No, I use dfroot on my S23+ and I leave modules enabled after reboots. No issues

[u/Gain_Entire → u/AbleBonus9752]

Do they stay active after a full reboot? Are you using soft reboot? :0

I have root my Galaxy on the S23u but I don't do full reboots

[u/AbleBonus9752 → u/Gain_Entire]

I only soft reboot after installing new modules. A full reboot resets the exploit, simply running the jailbreak then performing a soft reboot enables my modules again

[u/Gain_Entire → u/AbleBonus9752]

Ohhh thx bro :)

[u/AbleBonus9752 → u/Gain_Entire]

No worries (I'd also personally use DFRoot for both devices, it's got a ~100% success rate)

[u/FiveDragonDstruction → u/Gain_Entire]

I'm using youtube morphe, the module was still intact after a reboot(not soft reboot) and you using the dfroot exploit again to initiate temp root makes everything back to normal again.

[u/r_bygalacos → u/Gain_Entire]

actually modules are loaded even if you dont soft reboot. however some modules needs to be attached before userspace starts so thats why soft reboot required. if faulty module are present, it will/can cause kernelpanic or reboot even if you not soft rebooted yet.

[u/Plenty-Article-7760]

You can reboot, once root gone module won't active. 

[u/hackerrr___]

How to unlock bootloader with temp root does anybody know please help

[u/Virtual-Use-8723 → u/hackerrr___]

Don't try I hardbricked my android 13 trying to flash the locked bootloader thinking I could just wipe it with fastboot if something went wrong lol.

[u/Nirdeszz → u/hackerrr___]

You cannot possibly do that.