Setup guide
Rooting can void your warranty, trip Samsung Knox and, in rare cases, stop a phone from starting normally. These tools are made by independent developers, not by #Hex Next. Follow each project's own instructions, keep a backup, and only use them on a phone you own.
Before you start: locked bootloaders
- Stay off new security updates. Temporary root on a locked bootloader is confirmed to work up to the October 2026 security update so far, but Samsung will patch the exploit soon. Avoid installing security updates, and turn off Auto update system in Developer options.
- Never change anything that runs while the phone is starting. With a locked bootloader, any setting that modifies the phone during boot will almost certainly brick it or leave it in a boot loop. Only changes made after the phone has finished starting are safe, such as getting root again automatically once it has booted.
- Don't touch settings you don't understand. In Root My Galaxy and KernelSU, never apply a setting before you know exactly what it does.
- Keep modules to a minimum. Only install KernelSU modules you absolutely need, such as Zygisk (required for any module to work) and Vector (LSPosed).
1. Get root
Pick the method that matches your phone and its security update (Settings › About phone › Software information).
Check the community guide first: Awesome Temporary Root. Which method works depends on your exact model, firmware build and kernel, and it changes with every security update. That guide keeps the current list, so the beta build of #Hex Next links to it as well: on the welcome screens, in the in-app guide and under Settings › Root help. The Google Play version links to no root guide.
In the guide: Samsung Galaxy phones · Quick start · Modules · Troubleshooting
The methods below are the ones #Hex Next users have confirmed on Galaxy phones. If the community guide lists something newer for your phone, follow the guide.
Root My Galaxy
Works for older devices on older security updates.
Root My Galaxy Next
The continuation of Root My Galaxy, for newer models and security updates.
DirtyFrag + Diabl0w's KernelSU
These two go hand in hand. Together they work on almost every Samsung device up to about the June or July 2026 security update.
Root My Galaxy Ultra
Works on the September and October 2026 security updates.
KernelSU-Next
The best root manager to use with any Root My Galaxy method.
KernelSU asks you to upgrade after Root My Galaxy?
- Open KernelSU-Next › Actions › Build Manager CI.
- Open the latest workflow run that passed and download its
managerfile. - Use it to update your KernelSU-Next manager. This usually fixes it without rooting again.
- If it doesn't, try the next older passed run, and keep going down the list until you find the version that matches your phone. Be patient: one of them will work.
2. Install Zygisk and Vector
- Download any one Zygisk variant: Zygisk Next, NeoZygisk or ReZygisk. Whichever you like. Install it in KernelSU › Modules, then reboot.
- Download Vector (the current LSPosed), install it in KernelSU › Modules, then reboot again.
Soft reboot every time you grant root. With temporary root, root comes back only after you run your root method again following a restart. Each time you do, perform a soft reboot so Zygisk loads. Every other module, Vector included, depends on it.
3. Install the HexNext-QS-Notifications-Module
Download HexNext-QS-Notifications-Module.apk
Owner and beta builds of #Hex Next can also install it for you: Theme Packs › System UI hook › Install module.
- Install the APK.
- Open Vector from its notification, or from KernelSU › Modules › Vector.
- With Vector open, go to the Modules tab and tap HexNext-QS-Notifications-Module. Don't enable it yet.
- Tick System UI in its scope first. You may need to use the filter to show system apps.
- Once System UI is ticked, switch the module on with the toggle in the top right corner. Then force stop #Hex Next from its app settings page (Settings › Apps › #Hex Next › Force stop) and open it again. No reboot is needed.
Note: Vector loads the hook when System UI starts, so on some phones a force stop is not enough. If the card's badge stays yellow (Module Hook Installed but Not Running), do a soft reboot.
Updating the module? Install the new APK over the old one, then do a soft reboot before you apply a theme again. System UI keeps running the old version until it restarts, and until version 1.9 or newer runs, #Hex Next leaves the Quick panel music player icons as One UI draws them.
You're set
#Hex Next can now theme your phone to its fullest, with no further setup. The hook loads by itself every time you grant root after a restart. Just don't forget the soft reboot each time, or Zygisk won't load and the modules that depend on it won't run.
In #Hex Next, Theme Packs › System UI hook shows a green Module Hook Running badge once it is running. Turn on Quick panel tiles in full colour and Notification card art there.