Honestly not sure, all I can tell you is adbd (the server) is part of the ROM, so I'm not sure why it wouldn't work as with other clients.
Did you try running `stop adbd; start adbd;` first to make sure it's also running as root?
Edit: Searching the thread, here's what our resident adb hacking guru @Surge1223 suggested back in the day for localhost adb: https://forum.xda-developers.com/sho...9#post68334459
F5321: / $ su F5321: / # setprop service.adb.tcp.port 5555 F5321: / # adb kill-server F5321: / # adb tcpip 5555 F5321: / # stop adbd F5321: / # start adbd F5321: / # adb connect localhost:5555
---------- Post added at 07:03 PM ---------- Previous post was at 06:11 PM ----------
There's quite a bit behind this, it depends on the env in root shell, uid or the process that executed "adb shell" or "adb connect" etc, also depends the order of which dirs it scans to find the keys, I don't quite remember the order anymore but back when I made this I prioritized having it search /sdcard instead of /data/misc because the idea was to gain uid 2000 (shell) perms without using a pc or having root
Sorry for a dumb question, but what is "it" that is scanning for "the keys"? Which keys?
Are you saying something is searching for adb_keys in /sdcard instead of /data/misc?
If so, should I copy /data/misc/adb/adb_keys to /sdcard? I will give that a shot.
One of the app I use draw over other apps and prevent me from tapping "OK" on the auth dialog. I have to disable the app, authorize adb, then enable the app back. I eventually want to script all steps from adb connecting to mounting encrypted volume for easy one click and obviously not being able to click "OK" gets in the way.
F5321: / # adb connect localhost:5555 F5321: / # adb devices localhost:5555 unauthorized emulator-5554 unauthorized
- "emulator-5554" always asks for authorization even with the key copied in /data/misc/adb/adb_keys, just like localhost.
- adb shows only one authorization dialog. If I get emulator-5554, that's the only one that gets authorized, effectively preventing me from authorizing localhost.
- I still have no idea where emulator-5554 came from, but I took a wild guess and uninstalled an app called "WiFI ADB" that I had on my phone. I have not seen emulator-5554 ever since.