adb does not recognize the device

zye1996 commented

2019-03-26 10:41:49 -07:00

(Migrated from github.com)

Hi, it seems that I successfully update the firmware (as the rp1 is connected as a mass storage device). But I cannot find the device through adb devices command. Is there any advice?

HappyZ commented

2019-03-26 13:45:44 -07:00

(Migrated from github.com)

can you try a different cable, or restart adb server via adb kill-server && adb start-server? If you are on linux, it seems you need sudo permission to see devices via adb devices.

Or, you can go into the diagnosis mode, mount the system partition, and check the log there to see if adbd is started.

can you try a different cable, or restart adb server via `adb kill-server && adb start-server`? If you are on linux, it seems you need sudo permission to see devices via `adb devices`. Or, you can go into the diagnosis mode, mount the system partition, and check the log there to see if adbd is started.

zye1996 commented

2019-03-26 15:50:23 -07:00

(Migrated from github.com)

I checked the wire and it should be no problem. Could you give me more detailed description about how to find the log file in diagnosis mode?

zye1996 commented

2019-03-26 15:52:14 -07:00

(Migrated from github.com)

And the devices is shown as a USB serial device on the computer instead of an Android device. Is it what supposed to be?

HappyZ commented

2019-03-26 20:52:25 -07:00

(Migrated from github.com)

It supposes to have the serial connection for DPA. What if you flashed the
one without mass storage?

I'll take a close look tomorrow when I get home.

On Tue, Mar 26, 2019, 18:52 zye1996 notifications@github.com wrote:

And the devices is shown as a USB serial device on the computer instead of
an Android device. Is it what supposed to be?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/HappyZ/dpt-tools/issues/81#issuecomment-476883782,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEdSKnMp2vny8jfqUbVNmUiDLm1b8o-Nks5vaqSegaJpZM4cMDpq
.

It supposes to have the serial connection for DPA. What if you flashed the one without mass storage? I'll take a close look tomorrow when I get home. On Tue, Mar 26, 2019, 18:52 zye1996 <notifications@github.com> wrote: > And the devices is shown as a USB serial device on the computer instead of > an Android device. Is it what supposed to be? > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/HappyZ/dpt-tools/issues/81#issuecomment-476883782>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AEdSKnMp2vny8jfqUbVNmUiDLm1b8o-Nks5vaqSegaJpZM4cMDpq> > . >

zye1996 commented

2019-03-27 05:56:34 -07:00

(Migrated from github.com)

I did both but neither PKGs work

HappyZ commented

2019-03-27 08:40:24 -07:00

(Migrated from github.com)

what did it say when you run adb devices? just empty list?

I looked into the image but didn't find anything suspicious. If you exit DPA, restart the device but keep the cable connected, will adb devices show you anything?

FYI, what system were you using? MacOS?

what did it say when you run `adb devices`? just empty list? I looked into the image but didn't find anything suspicious. If you exit DPA, restart the device but keep the cable connected, will `adb devices` show you anything? FYI, what system were you using? MacOS?

zye1996 commented

2019-03-27 09:16:11 -07:00

(Migrated from github.com)

I get an empty list from adb devices. I tried both Windows and Ubuntu. Let me try what you suggest and get back to you.

I get an empty list from **adb devices**. I tried both Windows and Ubuntu. Let me try what you suggest and get back to you.

zye1996 commented

2019-03-27 19:53:17 -07:00

(Migrated from github.com)

adb still shows nothing. how would adb search through devices attached and check whether the devices is enabled adb?

HappyZ commented

2019-04-02 14:13:40 -07:00

(Migrated from github.com)

Sometimes the cable does not have data pin connected and you can only charge it via the cable. Just to confirm if you can use the same cable for DPA connections before.

In your Ubuntu, what does lsusb say after you plug in?

Sometimes the cable does not have data pin connected and you can only charge it via the cable. Just to confirm if you can use the same cable for DPA connections before. In your Ubuntu, what does `lsusb` say after you plug in?

HappyZ commented

2019-04-02 22:31:25 -07:00

(Migrated from github.com)

@zye1996 I just tested many more times, and it indeed can be slow to load up the adbd module since I've used an in-secured version (rooted on its own). In my "not working" case, I have to wait for a minute or two after the device turns on.. You just have to be patient and keep trying adb kill-server && adb start-server && adb devices.

And lsusb and dmesg on ubuntu can tell you more info.

@zye1996 I just tested many more times, and it indeed can be slow to load up the adbd module since I've used an in-secured version (rooted on its own). In my "not working" case, I have to wait for a minute or two after the device turns on.. You just have to be patient and keep trying `adb kill-server && adb start-server && adb devices`. And `lsusb` and `dmesg` on ubuntu can tell you more info.

HappyZ commented

2019-05-10 17:45:44 -07:00

(Migrated from github.com)

closed as there are no further discussions. similar findings are already discussed in wiki rooting guide. The idea is if current pkg does not work (slow start on the insecured adbd), then user can try the old pkg with a fixed adb key provided before. Check wiki and #87 for more details.

adb does not recognize the device #81