ID:
ISOLATION_SECONDARY_USERCategory: Emulation, profiles, and isolation Status in RKNHardering 2.10.0: Active check Role in the verdict: Medium
This page describes the actual implementation in RKNHardering 2.10.0. It distinguishes what can be done without root, what requires root, and where a mitigation only reduces one signal without hiding the VPN as a whole.
If the extracted user ID is not 0 and is not in the clone set, the checker creates ISOLATION_SECONDARY_USER with a medium-confidence review finding.
A dataDir of the form /data/user/<id>/, where <id> != 0 and is not 999 or in 950..959.
It identifies a separate Android user. This is a normal multi-user mode, but it changes the installed-app set, VPN configuration, and network policies relative to the owner user.
How the line affects the report: The line does not produce a final verdict on its own, but it sets needsReview=true and adds medium-confidence evidence.
The /data/user_de/ path and vendor-specific behavior may not match the regular expression. Private or work profiles may also fall into this branch when they have a nonzero user ID.
This line must be evaluated together with neighboring signals. A clean result from a single API does not simultaneously cover Java Binder, libc, raw netlink/syscalls, procfs/sysfs, local sockets, and server-side indicators.
If the profile is not part of the test, install and run the app under the primary user (user 0). Export its data before deleting a work, private, or clone profile: deleting the profile erases its apps and storage. Shelter and Insular are useful for managed profiles, but they do not hide the existence of a separate Android user.
Using root to spoof the user ID, /data/user/<id> path, or DevicePolicyManager responses creates an inconsistent state and can damage the profile. It is safer to run the app under the correct user rather than masking the profile. Hooks placed in the target process for a single check may additionally trigger HOOK_MARKERS, RWX_MEMORY_REGIONS, and LIBRARY_INTEGRITY.
adb shell pm list users
adb shell am get-current-user
adb shell cmd user list
Confirm which user has the package installed: adb shell pm list packages --user 0 | grep rknhardering.
After any change, force-stop both RKNHardering and the VPN client, start them again, and repeat the full scan. Zygisk, Xposed, and kernel modules usually require a reboot. Compare not only this line but also neighboring signals: a partial hook often creates inconsistencies between APIs.
The probe itself runs with ordinary app permissions and does not request root. The ADB commands below are for orientation only: adb shell runs under a different UID and may see either more or less than the app process. The decisive test is to run the check again after a force-stop.
Deleting a secondary user erases all of that user’s data, not only RKNHardering.
Recreate the user and restore the backup. Do not manually copy app data between UIDs.
Medium. Verified against the else if (userId != 0) branch.
The status of a third-party solution does not automatically carry over to this device. A module developer’s claim is only the initial hypothesis; confirmation requires a reproducible RKNHardering result on the specific Android version, firmware, and kernel.
NativeSignsChecker.kt — main native/legacy verdict logic.NativeSignalId.kt — complete ID registry.NativeSignalCatalog.kt — category, slug, and line mapping.Related signals: isolation-clone, isolation-work-profile.