evdenis / adb_root Goto Github PK

What is the password adb root android 8.1.0

hello
when i select install from storage i cant select the adb_root.zip, however i can install other magisk zip modules

Google translate:
Is it possible for adbd to listen on 127.0.0.1 for port forwarding ( for example https://github.com/Magisk-Modules-Repo/ssh ) or add
iptables -A INPUT -p tcp -s 127.0.0.1 --dport ${port adbd} -j ACCEPT
iptables -A INPUT -p tcp -s 0.0.0.0/0 --dport ${port adbd} -j DROP

Is there anyone already test on Android 14?

I know that the description states that this works on Android 9 & 10, but I'll ask anyway - has this been tested on Android 8.1?

seems devices like the samsung s20 lineup do not use a "usual" adbd binary in /system/bin
this results in adb root not working after installing this module

Wouldn't be surprised if #8 is related.

Figured it might be some non-eng prop being set, so tried https://github.com/evdenis/enable_eng but that didn't work and actually broke the settings app as well?

Another guess I had was that selinux was causing issues, so I tried https://github.com/evdenis/selinux_permissive but that actually caused my device to boot loop. Seems samsung must have an additional check somewhere to make sure permissive is not set, as even running su; setenforce 0 in adb shell causes the device to immediately crash and reboot.

Poking around a stock system, I see the following adb related files that might be useful in figuring out what we need to swap out to actually get this working:

# find /system -name "*adbd*"
/system/lib64/libadbd_auth.so
/system/lib64/libadbd_fs.so
/system/apex/com.google.android.adbd.apex
/system/lib/libadbd_auth.so
/system/lib/libadbd_fs.so

I also read somewhere that adbd sometimes is present in the boot.img ramdisk but at least on my device this is not the case.
To check on your own device, get the boot.img and run the following

abootimg -x boot.img
mkdir initrd; cd initrd
# you may need to be root to avoid permissions issues when extracting in the next step
su root
gunzip -c ../initrd.img | cpio -i
exit
find . -name "*adbd*"

iPad 2 Wi-Fi + Cellular iOS 9.3.5

try loading the attached zip in magisk manager. i've fixed this!
adb_root.zip

Originally posted by @GamerGirlandCo in #11 (comment)

When I installed adb_root,adb install command cannot be used.

Performing Streamed Install
adb: failed to install .apk: cmd: Can't find service: package

1. Andriod 9
2. arm64

Ignore - does not work in Android 11 didn't saw this early

I rooted using Magisk, and I get "su" rights.
I installed adb_root.zip using Magisk manager and rebooted, however I still get error,

adb root
adbd cannot run as root in production builds

Phone: OnePlus 8
OS: Oxygen OS 11.0.4.4

Please help ...

@evdenis USB Debugging does not work once this module is installed and enabled in Magisk.

I can't install apps with adb when this module is activated.
But why do we need this module? I found it can directly set com.android.shell with root permission using the SuperUser settings of Magisk.

You are life saver. I can confirm chrome remote debug working on Android 10 because of this module.

Hi, thanks for your work. adb shell works fine on root but adb pull root only files still fail. I guess there should be another patch on this.

The idea is to make this module more secure by design, while still allow root debugging for developers/users.

Instead of:

int adbd_main(int server_port) {
     // descriptor will always be open.
     adbd_cloexec_auth_socket();

     auth_required = false;
 
     adbd_auth_init();

We can modify the original function's prop to something different, like:

int adbd_main(int server_port) {
     // descriptor will always be open.
     adbd_cloexec_auth_socket();
 
    if (android::base::GetBoolProperty("ro.adb.insecure", true)) {
        auth_required = false;
    }
 
     adbd_auth_init();

Then, adbd will check for ro.adb.insecure instead of ro.adb.secure. This also avoid SafetyNet detection.
By default, ro.adb.insecure should be false, so that if the phone gets connected to a new/unknown PC, it won't just trust and give all root permissions. The user can revert to the old behavior with ro.adb.insecure=true if they need (like for example a dead phone display).

After installing it via Magisk and rebooting the phone, adb now says:

List of devices attached
cexxxxxxxxxxxxxx03      offline

I already disabled and re-enabled USB debugging, revoked permissions, killed the adb server. Nothing seems to work. It was working fine before installing this zip.

Also, after revoking permission, no new trust device dialog comes up when I replug and rerun the adb command, which is weird. Seems like the package is broken somehow.

S7 Edge - Android 10

Im successfully install adb root on my magisk. but now i cant connect to device, the usb didnt recognize phone. and adb devices show no list.
my device is xiaomi 5X

After I installed the module，use adb devices ，no device found。

my phone is pixel 2xl，android 10，magisk v22.1

Hi,
Thank you for providing the adb_root. But I didn't get the adbd running because of this: "/system/bin/sh: /system/bin/adbd: not executable: 64-bit ELF file", after I did everything in duraki's hot fix.
Since I'm working on a critical issue and I don't have too much time to research on how to build from your source code, could you please provide the 32-bit build for me?
Thanks a lot!