10947 questions

13051 answers

20353 comments

27719 members

0 votes
822 views 15 comments
by
Just purchased a new TRB140 and attempted upgrading the firmware using the WebUI. Following the upgrade the device fails to start.

The LED's just flash in the following pattern: fourth signal signal strength LED flashes once, then all signal strength LEDs flash twice.

Have attempted a factory reset, however all that happens is all signal LEDs flash. Not able to connect to the WebUI, ping, or SSH etc (attempted using a static ip address). Also there are no link lights on the ethernet connections (laptop or TRB140).

Any assistance in resolving this issue would be greatly appreciated.

1 Answer

0 votes
by
Hello,

Regarding to the issue your having may i know the TRB batch no. and could you try doing this steps:

1. Remove all cable and antenna of the TRB device.
2. Plug the power cable.
3. After 2-3 mins insert a LAN cable and see if the Ethernet port led will blink
4. Check your laptop/pc if the trb device is detected check if the network cable is plugged or unplugged.
5. If the TRB140 is detected but is not reachable via web ui try pinging 192.168.2.1. Now if their is no ping results
you can try using the USB cable found in the back instead of LAN (ethernet) cable and see if there are some positive results.

Hope it helps

Regards,
Jerome
by
Hello,

Could you try using Window OS instead of Linux OS?

Kindly provide me feedback on this.

Thank you and have a nice day!

Regards,
Jerome
by
Hi Jerome,

Same issue with Windows, "adb devices" fails to list the device.

Many thanks,

André
by

Hello, 

May i know what adb installer are you using could you try installing the ADB installer 1.3? 

Then follow this steps: 

Turn off/unplug TRB14x;

2. Press and hold reset button, at the same time plug the power cable and keep holding reset button for about 5 seconds (mobile signal LED's should start blinking);

3. Download and install adb from this link: https://forum.xda-developers.com/showthread.php?t=2588979

4. Open CMD with admin rights;

5. Download rootfs.ubi (https://we.tl/t-tWBYLa956X)

6. Use cd command to navigate to the place where you saved the rootfs.ubi file (Example: cd C:\Users\Jerome\Desktop\Test);

7.Then use this command: fastboot flash rootfs_a rootfs.ubi ;

8.When it completes the process use this command; fastboot flash rootfs_b rootfs.ubi ;

9.When it is done unplug and plug your device again, it should boot up as normal;

10.Install the latest software through WebUI.


I have tested this on my side but i am using Windows 7 OS. And i was able to flash
Thank you and have a nice day!

Regards,
Jerome
 

by

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é

by
Hello,

Could we do a short remote session for this one? Just send me the Anydesk id of yours via PM :)

Thank you and have a nice day!
Stay Safe

Regards,
Jerome