"ADB Root access is disabled" Even with root access enabled

Question

I'm trying to patch Tingle on my Xiaomi Redmi 4A running on LineageOS 17.1 via ADB for enabling system spoofing signature for microG. But I'm getting this error :ADB Root access is disabled by system setting - enable in Settings -> System -> Developer options everytime I type adb root in cmd (running as admin). My device is rooted with Magisk 20.4 and the 'Super Access' option is enabled as "Apps and ADB". I've also enabled "Android debugging" option under the 'Settings -> System -> Developer options'.

But I'm unable to find any option called 'ADB Root access' or 'Root Access' under 'Settings -> System -> Developer options'. I've also tried abdb Insecure by Chainfire.

But with no luck, the problem still persist. I just want to get root access in my adb interface to be able to use Tingle.

Note : I'm on Android 10. My SELinux status is enforcing (not permissive) and my ROM isn't stock nor official.

Thanks in advance! Any kind of help would be highly appreciated. <3

Answer 1

As @biAji pointed out, the 'Rooted debugging' option is not shown if ro.debuggable is set to 0 in the system props. The ADB as root option will be visible in developer options if you add the line ro.debuggable=1 anywhere in the /system/build.prop file.

If you cannot edit the file as root but su is working in the adb shell or any terminal app then SmartPack Kernel Manager might be able to help. Install the app and go to the Build prop Editor section from the menu. If you can find a key-value pair ro.debuggable then edit its value to 1. If it doesn't exist then create a new prop with that name as key and the value as 1.

Now reboot the device and check if an ADB as Root option appears in developer options. If it does, the build.prop file was successfully edited and now you can uninstall SmartPack.

Answer 2

After check the source code, this settings item will be available if the device is debuggable

    @Override
    public boolean isAvailable() {
        return Build.IS_DEBUGGABLE;
    }

And it's depend on the system props ro.debuggable which is set to 0 in my case.

I think I need a debuggable-boot image to patch the device.