How to factory reset Jetson TX2 without Jetpack?

About 2 years ago, I badly screwed up the Ubuntu installation on my Jetson TX2. It’s been sitting in a box since. I am now trying to get Jetpack 4.3 installed on it. However, the SDK Manager cannot find the TX2. I put it into reset mode and didn’t see it on my host with lsusb.

How can I get the TX2 back to its original factory default without using Jetpack? Here’s some information:

Host: ASUS ZenBook with Ubuntu 18.04 and 16GB RAM

JetPack 4.3 SDK Manager for Jetson TX2

Hi eric1,

Are you using VM server?
Please put your device into recovery mode and use ‘lsusb’ command to make sure your TX2 micro-usb port is work or not first.

Thanks for your reply! I’m not using a VM. I dual booted Ubuntu onto the ASUS ZenBook for the host.

I put the TX2 into recovery mode, connected the ZenBook to the microUSB port of the TX2, ran lsusb on the host, and did not see the device.

I believe that the TX2 is severely damaged in its software. I have no reason to believe it’s a hardware issue, although I cannot rule out the possibility.

Hi eric1,

Can you boot up your TX2 now?
If yes, you can use uart console and run below command to put your device into recovery mode:
sudo reboot forced-recovery

We need to make sure the micro-usb port is working and into RCM, then we can start flash image.

I cannot see the HDMI output from the TX2. My monitor says “unsupported format” when I turn on the TX2, so it is getting some signal from it.

Is there anything I can do to change the format to see its output?

Hi eric1,

Better skipping the first configuration of user account w/o using HDMI. Please refer to below page.

https://elinux.org/Jetson/General_debug

Do beware that a monitor is not a reliable method to know if anything is going wrong. Serial console is a far better method. See:
http://www.jetsonhacks.com/2017/03/24/serial-console-nvidia-jetson-tx2/

You monitor also must be truly HDMI and not use a VGA adapter.

The cable used between the micro-B USB of the Jetson and the host PC must also be of good quality (charger cables usually fail). The cable which comes with the dev kit works quite well, and if you have switched to a different cable, then I would say the lack of success may be related to the cable quality.

I connected the TX2 to another monitor and I get console output now. It seems to freeze at the same point every time it turns on. I can type until it freezes, and then it becomes unresponsive.

What does the USB cable look like / how long is it? I had two USB cables in the Jetson box, although I’m not sure if either is the original.

Thanks!

I checked an unboxing video on Youtube, and it appears that I have the right USB cable. This is it right?

Just want to get back to the original question.

Are you able to flash the board? The photo you paste is a kernel log when system is booting up. Nothing to do with the flash.

I am not able to flash the board. The kernel gets frozen at the point of the picture I provided. I do not see the TX2 via lsusb on the host.

I’m currently setting up a serial console. This is not my area of expertise, so it’s slow going.

Ok, Just also want to make sure that you know how to set device into recovery mode, right?

Yes, it suppressed the kernel log when I did that, so I believe it set it correctly into recovery mode

Hi eric1,

The Jetson module is in Force Recovery mode if you see the message:

Bus Device : ID 0955: 7c18 Nvidia Corp.

Please check on your host machine with lsusb command.

I got it flashing! For some reason, I re-did the Manual Setup, and it worked this time.

Thanks everyone!

1 Like

This is the correct table in that image for flashing. Take care of this cable since quality data cables of this type are hard to get. If you’ve flashed with a different cable, then I would recommend flashing again using the correct cable.

In a case where the monitor shows freezing at some point, then you might use a serial USB UART cable (3.3V logic level). The lockup could be as simple as video not working, but the rest of the system functioning…or it could be a hard lockup, and a serial console would give you more information prior to video failing. Hard to say without that. This is the URL for serial console on the TX2:
http://www.jetsonhacks.com/2017/03/24/serial-console-nvidia-jetson-tx2/