Hello
We have a TRB142 device, with fw 7.10 and Batch 036. The device is in a reboot loop, flashing all signal LEDs. Tried to do a factory reset without success. I can access ssh or web interface only a few seconds, but device reboots constantly.
Is it possible to recover the device via ADB/fastboot? Where can I download .ubi files for this device?
Thank you in advance.
Jose Luis.
Greetings, jcolladoa,
Thank you for your message,
According to your description it seems that the device is facing some hardware related issues.
In this case you should contact your sales manager / reseller, so they could contact us regarding device’s warranty. If the warranty is still valid, your device will be either repaired or changed to a new product.
Kind regards,
V.
Thank you, Vilius,
Unfortunately, the device’s acquisition date is greater than 3 years, so the warranty period expired.
Hence, apart from buying a new TRB142, I think that my only option is to try a fastboot recovery (does it exist another procedure?). Could you please show me how to proceed? Where could I obtain the appropiate files? I don’t care about bricking the device; it’s currently unusable.
Thank you in advance.
Kind regards,
JL.
Greetings, jcolladoa,
Thank you for your swift response,
I have removed the device’s serial number from your message, because it is sensitive information, please refrain from posting sensitive data to a public forum.
For troubleshooting purposes, we will require more sensitive information from your end, such as the troubleshoot file, which may contain passwords, public IP addresses, serial numbers, and such. To avoid leaking this information, we have sent you a form to fill out, which you will receive in your e-mail inbox that you have registered your account with in the forums. In the Ticket ID field of the form, please enter the ID of this thread, which is 16217.
Thank you,
V.
Thank you, Vilius.
Sorry, I didn’t imagine that a serial number is sensitive information. Ok, when I receive the email, I will proceed as you have indicated.
Hello, @Vilius
Finally I received a communication from you Teltonika noting that the device guarantee period is over.
So, I will appreciate if you could send me the ADB driver for TRB142 (older links to Drive doesn’t work). I’ll try to do a fastboot rescue by myself. Any damage to the device will be under my entire responsibility.
Kind regards,
JL
Greetings, jcolladoa,
I hope this message finds you well.
I have sent you a follow-up email with the next steps on how we can proceed. Please check your inbox at your convenience.
Warm regards,
V.
Greetings, @Vilius,
I have been waiting for your email with next steps to proceed, but it doesn’t appear in my incoming box, also checked my spam box. Could you please resend it to me?
Kind regards,
JL
Greetings,
Thank you for your message,
I have resent an email with further instructions please let me know if you received it.
Kind regards,
V.
Greetings,
Here is a brief summary of our remote session,
We downloaded the fastboot utility along with the required files for the recovery procedure. However, the device was not detected by the software. Since the unit is continuously rebooting and cannot enter fastboot mode, this strongly suggests a hardware-related fault. In this case, the device will likely require repair or replacement.
Warm regards,
V.
Greetings,
Thank you for your support.
After reviewing the steps, I saw that the problem was that the Google USB drivers weren’t installed. I downloaded them from the Google website, forced the driver installation on the Android device, and now fastboot recognizes it.
Vilius, I have followed the next steps:
fastboot.exe flash rootfs_a rootfs.ubi
fastboot.exe flash rootfs_b rootfs.ubi
fastboot.exe reboot
At this stage, the device starts and stays stable at firmware version TRB1_R_33.07.04.14
But if I try to install a new firmware (for instance, 00.07.19.4), after installation the device enters again in a loop.
I guess that I forget a step sending something else to the device (you send me another file, kernel.img. Is it true?
Thank you again.
Best regards,
JL
Greetings,
I hope this message finds you well.
I am glad that you managed to install the required drivers and now the fastboot recognises the device. I have sent you an email regarding this issue. Could you please confirm or reply to that email so we can proceed with the next steps?
Best regards,
V.
Hello,
Here is a brief summary of our remote session,
We were able to put the device into fastboot mode, but since this recovery method is only intended as a last resort, it usually points to deeper issues when it fails to bring the device back to normal operation. After attempting a firmware upgrade, the unit continued to fall into a reboot loop.
I reached out to our IoT engineering team for further insight, and their assessment indicates that the behavior is likely caused by a hardware-level problem - most commonly related to FLASH memory or an issue with the device’s power circuitry.
Given these findings, the best next step would be to contact your reseller regarding repair or replacement.
Warm regards,
V.
Greetings,
Thank you for your invaluable support. As I mentioned in the email, we consider this issue to be closed. Anyway, we would like to ask you one last favor before closing this ticket.
In subsequent investigation, I discovered that the modem (Quectel EC21-EU) was unreachable in the faulty unit , which could be (broken modem) the root cause of the device’s malfunction.
In the same installation, we replaced the faulty device with another TRB142 with the same specifications (and from the same batch 036). Unfortunately, the new unit has failed again after two months of operation, and for the same reason (modem unreachable). A firmware update (latest stable version) also did not solve the problem.
All of this (two failures of the same type in the same location; we have 550 units distributed throughout the country and they don’t experience these types of failures) leads us to believe that we have a systemic problem, not attributable to the device itself, but to the rest of the installation.
Given the recurring nature of the failure, we would appreciate your advice on the underlying problem and where to begin troubleshooting (antenna/cabling issues, SWR, electromagnetic noise, electrical discharges, etc.). We are not currently attributing the problem to storms.
Thank you again.
Best regards
Greetings, @jcolladoa,
Thank you for your message.
Could you please confirm whether the replaced device is still covered under warranty?
If so, you may initiate the RMA process to return the device for replacement and further investigation.
Regarding the operating environment, I recommend checking the wiring and power supply units. In cases of unstable or excessive voltage, the device may malfunction. As for electromagnetic noise, it can affect signal strength by interfering with radio waves; however, it should not directly impact the modem itself.
Please let me know if you need any additional assistance.
Warm regards,
V.
This topic was automatically closed after 60 days. New replies are no longer allowed.