I need help with adb. I'm using rooted Xiaomi Redmi 6A (Android 9). Recently, I flashed the Magisk "adb root" module (https://github.com/evdenis/adb_root), which is used to access "adb root" command (adb push, adb pull). This module utilizes the adbd daemon running on your phone with root rights. It did actually work, but with one problem - now I can't use adb outside of twrp recovery. Since I already did what I wanted to do with adb root, I uninstalled this module - but it didn't do anything. Every time I'm trying to use adb, the daemon is started successfully, but adb doesn't see any devices attached. This isn't a problem with the cable or pc - before using this module, it all worked without issues. Inside the module file, I found a setpolicy.rule file:

allow adbd adbd process setcurrent

allow adbd su process dyntransition

allow su * * *

I'm looking for a way to reset adb/adbd settings to default, which hopefully would fix my problem. (I did try to contact them via their Telegram, but it seems inactive).

I need help with adb. I'm using rooted Xiaomi Redmi 6A (Android 9). Recently, I flashed the Magisk ADB Root module, which is used to access adb root command (adb push, adb pull). This module utilizes the adbd daemon running on your phone with root rights. It did actually work, but with one problem - now I can't use adb outside of TWRP recovery. 

Since I already did what I wanted to do with adb root, I uninstalled this module - but it didn't do anything. Every time I'm trying to use adb, the daemon is started successfully, but adb doesn't see any devices attached. This isn't a problem with the cable or PC - before using this module, it all worked without issues. Inside the module file, I found a setpolicy.rule file:

allow adbd adbd process setcurrent
allow adbd su process dyntransition
allow su * * *

I'm looking for a way to reset adb/adbd settings to default, which hopefully would fix my problem. (I did try to contact them via their Telegram, but it seems inactive).

I need help with adb. I'm using rooted Xiaomi Redmi 6A (Android 9). Recently, I flashed the Magisk "adb root" module (https://github.com/evdenis/adb_root), which is used to access "adb root" command (adb push, adb pull). This module utilizes the adbd daemon running on your phone with root rights. It did actually work, but with one problem - now I can't use adb outside of twrp recovery. Since I already did what I wanted to do with adb root, I uninstalled this module - but it didn't do anything. Every time I'm trying to use adb, the daemon is started successfully, but adb doesn't see any devices attached. This isn't a problem with the cable or pc - before using this module, it all worked without issues. Inside the module file, I found a setpolicy.rule file:

allow adbd adbd process setcurrent allow adbd su process dyntransition allow su * * *

I'm looking for a way to reset adb/adbd settings to default, which hopefully would fix my problem. (I did try to contact them via their Telegram, but it seems inactive).

I need help with adb. I'm using rooted Xiaomi Redmi 6A (Android 9). Recently, I flashed the Magisk "adb root" module (https://github.com/evdenis/adb_root), which is used to access "adb root" command (adb push, adb pull). This module utilizes the adbd daemon running on your phone with root rights. It did actually work, but with one problem - now I can't use adb outside of twrp recovery. Since I already did what I wanted to do with adb root, I uninstalled this module - but it didn't do anything. Every time I'm trying to use adb, the daemon is started successfully, but adb doesn't see any devices attached. This isn't a problem with the cable or pc - before using this module, it all worked without issues. Inside the module file, I found a setpolicy.rule file:

allow adbd adbd process setcurrent

allow adbd su process dyntransition

allow su * * *

I'm looking for a way to reset adb/adbd settings to default, which hopefully would fix my problem. (I did try to contact them via their Telegram, but it seems inactive).