Pmbootstrap: ADB server didn't ACK

Created on 20 Aug 2017  路  4Comments  路  Source: postmarketOS/pmbootstrap

When trying to run the following in the native chroot:

adb start-server

I get:

* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon

strace: https://github.com/postmarketOS/pmbootstrap/files/1237075/adbtrace.txt

bug pmbootstrap

All 4 comments

That's funny, it seems to work when you explicitly start it:

/ # adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
/ # adb devices
List of devices attached

...and when you start it again, it simply gets ignored. So you could change the code to always start it before and it should work.

    "adb": {
            "depends": ["android-tools"],
            "actions":
            {
                "list_devices": [["adb", "start-server"],
                                 ["adb", "devices"]],
                "sideload": [["adb", "start-server"],
                             ["adb", "wait-for-usb-sideload"],
                             ["adb", "sideload", "$RECOVERY_ZIP"]],
            }
    },

@ollieparanoid This didn't help, however I found out, when I mount the whole sysfs inside the chroot, adb starts working.

Maybe something is not mounted, that is needed for networking/adb in the chroot?

after mounting /sys/dev/, it works perfectly

Cool, that you've found that out!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

cmdr2 picture cmdr2  路  7Comments

craftyguy picture craftyguy  路  7Comments

Decatf picture Decatf  路  4Comments

Asara picture Asara  路  6Comments

pavelmachek picture pavelmachek  路  7Comments