Jetson Orin NX 16GB Bricked After Failed JetPack 7.2 Flash - No UART Output, No LED, Force Recovery Not Detected

Device: Jetson Orin NX 16GB JetPack Target Version: 7.2 Host OS: Ubuntu (SDKManager)


Problem Description:

I was attempting to flash JetPack 7.2 onto my Jetson Orin NX 16GB using SDKManager with an SD card connected via a USB adapter. During the flashing process, the system froze and I noticed the Jetson had lost power — the fan had stopped spinning. After restoring power, the device shows no signs of life: no fan spin, no LEDs, and no UART output.


What I Have Tried:

1. Force Recovery Mode I bridged the FC REC and GND pins using a jumper while the device was powered off, then applied power. I monitored lsusb continuously using watch -n 0.5 lsusb but the device never appears as NVIDIA Corp. APX (0955:7020). I tried multiple sequences:

  • Power off → jumper → power on → wait → remove jumper
  • Power on → jumper → reset

2. UART Debug Console I built a UART bridge using an ESP32 (HardwareSerial bridged to USB Serial at 115200 baud). The ESP32 loopback test works correctly (characters echo back). I connected ESP32 TX → Jetson RX and ESP32 RX → Jetson TX with shared GND. However, no output is received from the Jetson at any baud rate (9600, 57600, 115200). This suggests the device is not reaching even the Boot ROM stage.

3. Power Supply I verified the 12V 5A DC barrel jack power supply with a multimeter — voltage is correct and the supply is known-good (was working before the failed flash).

4. SDKManager Error Log During the failed flash attempt, SDKManager reported the following error:

15:21:51 ERROR: File System and OS - target_image: mknod: 
/home/berat/nvidia/nvidia_sdk/JetPack_7.2_Linux_JETSON_ORIN_NX_.../rootfs/dev/random: 
File exists
15:21:51 ERROR: File System and OS - target_image: command error code: 11
15:21:51 SUMMARY: File System and OS - target_image: Installation failed.

This appears to be a host-side rootfs conflict from a previous partial installation attempt.


Current Status:

  • No LED activity
  • No fan spin on power
  • No UART output at any baud rate
  • Device not detected in lsusb even in Force Recovery Mode
  • Multiple USB-C cables tested, direct connection to host (no hub or adapter)

Questions:

  1. Is there any other method to enter Force Recovery Mode that I might be missing for this carrier board?
  2. Could the QSPI be so corrupted that even the Boot ROM fails to bring up the USB recovery interface?
  3. Is there any hardware-level recovery option beyond Force Recovery + USB flash?

Any help would be greatly appreciated. Thank you.İşte güncellenmiş metin:


Title: Jetson Orin NX 16GB Bricked After Failed JetPack 7.2 Flash - No UART Output, No LED, Force Recovery Not Detected


Device: Jetson Orin NX 16GB JetPack Target Version: 7.2 Host OS: Ubuntu (SDKManager)


Problem Description:

I was attempting to flash JetPack 7.2 onto my Jetson Orin NX 16GB using SDKManager with an SD card connected via a USB adapter. During the flashing process, the system froze and I noticed the Jetson had lost power — the fan had stopped spinning. After restoring power, the device shows no signs of life: no fan spin, no LEDs, and no UART output.


What I Have Tried:

1. Force Recovery Mode I bridged the FC REC and GND pins using a jumper while the device was powered off, then applied power. I monitored lsusb continuously using watch -n 0.5 lsusb but the device never appears as NVIDIA Corp. APX (0955:7020). I tried multiple sequences:

  • Power off → jumper → power on → wait → remove jumper
  • Power on → jumper → reset

2. UART Debug Console I built a UART bridge using an ESP32 (HardwareSerial bridged to USB Serial at 115200 baud). The ESP32 loopback test works correctly (characters echo back). I connected ESP32 TX → Jetson RX and ESP32 RX → Jetson TX with shared GND. However, no output is received from the Jetson at any baud rate (9600, 57600, 115200). This suggests the device is not reaching even the Boot ROM stage.

3. Power Supply I verified the 12V 5A DC barrel jack power supply with a multimeter — voltage is correct and the supply is known-good (was working before the failed flash).

4. SDKManager Error Log During the failed flash attempt, SDKManager reported the following error:

15:21:51 ERROR: File System and OS - target_image: mknod: 
/home/berat/nvidia/nvidia_sdk/JetPack_7.2_Linux_JETSON_ORIN_NX_.../rootfs/dev/random: 
File exists
15:21:51 ERROR: File System and OS - target_image: command error code: 11
15:21:51 SUMMARY: File System and OS - target_image: Installation failed.

This appears to be a host-side rootfs conflict from a previous partial installation attempt.


Current Status:

  • No LED activity
  • No fan spin on power
  • No UART output at any baud rate
  • Device not detected in lsusb even in Force Recovery Mode
  • Multiple USB-C cables tested, direct connection to host (no hub or adapter)

Questions:

  1. Is there any other method to enter Force Recovery Mode that I might be missing for this carrier board?
  2. Could the QSPI be so corrupted that even the Boot ROM fails to bring up the USB recovery interface?
  3. Is there any hardware-level recovery option beyond Force Recovery + USB flash?

Any help would be greatly appreciated. Thank you.

Hello @beratyumak2711!

Based on the title and content of your topic, it looks like it may receive better visibility and feedback in a different category. We took the liberty of moving it for you.

If this was an incorrect assessment, please send me a direct message.

Disclaimer: this moderation suggestion and message were generated with AI assistance.

Hi,

Just to confirm the sequence — do you connect the flashing (USB) cable between the host and the device before putting it into recovery mode?

Thanks

Yes ı tried it.

There is no update from you for a period, assuming this is not an issue anymore.
Hence, we are closing this topic. If need further support, please open a new one.
Thanks
~0722

Hi,

Some questions to confirm:

  • Is your ubuntu a native or a virtual machine?

Thanks