Hi Jerome,
Have tested this process with Windows 10 and Linux.
Have ensured where possible that the most recent version of ADB is installed on Linux system. The although not version 1.3 as you listed the version being used on my system appears to have been built in April 2020 and were downloaded from: https://developer.android.com/studio/releases/platform-tools which sates to have the most recent versions of this software.
Following is a copy and paste from my Linux terminal:
andre@Laptop:~/ADB> ./adb --version
Android Debug Bridge version 1.0.41
Version 30.0.2-6538114
Installed as /mnt/data01/Installs/ADB/adb
andre@Laptop:~/ADB> ./adb devices
List of devices attached
andre@Laptop:~/ADB> ./fastboot flash rootfs_a ../Downloads/rootfs.ubi;
< waiting for any device >
^C
andre@Laptop:~/ADB>
Please note that the "< waiting for any device >" message is the same on Windows and Linux and does not go away unless pressing Ctrl+C.
From my reading there are three reasons for "waiting for any device": 1 the required drivers are not set up, 2 the target device is not in developer mode, 3 The USB cable is faulty.
As to point 1:
The Operating System has detected the device as per the following output from dmesg:
[246966.671410] usb 1-2: new high-speed USB device number 18 using xhci_hcd
[246966.826522] usb 1-2: New USB device found, idVendor=18d1, idProduct=d00d
[246966.826527] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[246966.826530] usb 1-2: Product: Android
[246966.826533] usb 1-2: Manufacturer: Google
[246966.826535] usb 1-2: SerialNumber:
As to point 2. I can confirm that the instructions of disconnecting the power, pressing and holding the reset button while plugging in the power supply and holding for at least 5 seconds have been followed. The result is all signal strength lights flash.
To test the configuration I plugged in an old HTC mobile phone.
dmesg output:
[247582.822713] usb 1-2: new high-speed USB device number 34 using xhci_hcd
[247582.972091] usb 1-2: New USB device found, idVendor=0bb4, idProduct=0f87
[247582.972096] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[247582.972099] usb 1-2: Product: Android Phone
[247582.972102] usb 1-2: Manufacturer: HTC
[247582.972104] usb 1-2: SerialNumber:
As you can see, after accepting the notification to allow USB debugging on the phone, ADB sees the HTC phone:
andre@Laptop:~/ADB> ./adb devices
List of devices attached
FA536YJ02535 device
Retrying with the TBR140 using exact same cable etc:
[247781.957602] usb 1-2: New USB device found, idVendor=18d1, idProduct=d00d
[247781.957607] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[247781.957610] usb 1-2: Product: Android
[247781.957613] usb 1-2: Manufacturer: Google
[247781.957615] usb 1-2: SerialNumber:
andre@Laptop:~/ADB> ./adb devices
List of devices attached
andre@Laptop:~/ADB>
As to point 3, as the USB cable worked with the HTC phone it should be safe to say the cable being used does not have a fault.
Please note as stated before, the exact same result of ADB not seeing the device also occurs on Windows 10 (which was based on a fresh fully patched install on a clean system as I do not use Windows).
Output from Windows 10:
C:\Users\andre>adb version
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
C:\Users\andre>adb devices
List of devices attached
C:\Users\andre>
When you performed your test, did you also apply the firmware patch via the WEB UI that appears to have disabled my device? Maybe this is contributing to why this is not working?
Many thanks,
André
