`adb devices` and `fastboot devices` returns no device [answered]

asked 2019-05-11 08:51:55 +0200

jimjamz
1716 ●47 ●60 ●65

Feature: Seeing the Xperia X in adb and fastboot

Background:

Given I have an Xperia X

And I have a Linux laptop

And the Xperia X is powered off

And the USB cable is connected to my laptop

And I press and hold the VOLUME_UP button

And I insert the USB cable into the Xperia X

And the red light becomes a blue light

Scenario: Entering fastboot

When I enter fastboot devices into the laptop terminal

Then I should see the Xperia X

But I don't see any devices

Scenario: Entering adb

When I enter adb devices into the laptop terminal

Then I should see the Xperia X

But I don't see any devices

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by molan
close date 2019-05-15 18:02:27.260113

Comments

try different cable and usb port

bomo ( 2019-05-11 09:10:45 +0200 )edit

Also you may need to be root or sudo the commands on the linux.

Manatus ( 2019-05-11 10:42:31 +0200 )edit

1

I tried a different cable and USB port. No joy. Also, I tried the commands with sudo already and still no success. Sorry, I should have mentioned this earlier.

jimjamz ( 2019-05-11 14:22:05 +0200 )edit

I'm not sure if it makes any difference, but Developer tools are enabled in Sailfish OS on the device.

jimjamz ( 2019-05-11 14:25:12 +0200 )edit

Can anyone confirm that they are able to successfully recognise their Xperia X device with adb and fastboot when not using the official genuine Sony-branded USB cable that comes with the device? Although I have tested a couple of different USB cables, I don't have access to my original Sony cable and I think @bomo may be right. I seem to recall having this issue when I flashed the device the first time way back when in October 2017. I'm currently using an official genuine Nokia/Microsoft-branded cable, and I think this may be the issue.

jimjamz ( 2019-05-12 01:49:32 +0200 )edit

1

answered 2019-05-15 03:44:32 +0200

jimjamz
1716 ●47 ●60 ●65

The actual problem appeared to be the Nokia/Microsoft USB cable I was using. I temporarily borrowed another selection of USB cables, and although it was very hit and miss between the range of cables, fastboot devices was able to recognise the device. Yet, strangely, adb devices created a catastrophic error but that should be raised as a separate question.

Android Debug Bridge version 1.0.40 Version 4797878 Installed as /home/jimjamz/opt/adb-fastboot/platform-tools/adb

edit flag offensive delete publish link

0

answered 2019-05-11 09:17:17 +0200

harry

4827 ●49 ●60 ●55

https://together.jolla.co...

updated 2019-05-11 09:23:39 +0200

I guess it is the USB 3 issue. Search here and you will find a link to a jolla support page which says that if you are using linux with a USB 3 port you should put a USB 2 hub in between. I had non so I did flashing with a windows pc.

and update the adb version. see https://together.jolla.com/question/194868/help-installing-on-xa2-stuck-at-flashing-vendor_b-partition-waiting-for-device/

edit flag offensive delete publish link

Comments

I'm afraid it's not a USB 3.0 related issue. My laptop is a 10-year old Macbook with only USB 2.0. It is the same laptop that I used to flash Sailfish to my Xperia X when it was first released back in October 2017.

jimjamz ( 2019-05-11 14:21:10 +0200 )edit

What version fastboot are you running upon Mac, as I'm using fastboot version 0e9850346394-android?

scoobyman ( 2019-05-11 17:35:17 +0200 )edit

I'm running a Debian Linux distribution, not MacOS. fastboot version is fastboot version 28.0.0-4797878.

jimjamz ( 2019-05-12 01:42:10 +0200 )edit

`adb devices` and `fastboot devices` returns no device [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by molan
close date 2019-05-15 18:02:27.260113

Comments

2 Answers

Comments

Question tools

Stats

Related questions

`adb devices` and `fastboot devices` returns no device [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by molan close date 2019-05-15 18:02:27.260113

Comments

2 Answers

Comments

Question tools

Public thread

Stats

Related questions

The question has been closed for the following reason "the question is answered, an answer was accepted" by molan
close date 2019-05-15 18:02:27.260113