Flash Jetson OS image fails at step4 of SDK Manager

My host is a linux-ubuntu-18.04, i’ve tried several times,
I’ve connected the correct-subC port on the Xavier to the host,
During Step3 of the SDK manager (v1.3.1.7110) installing JetPack 4.4.1,
I get to this point:, about %36

16:18:06 DEBUG: Flash Jetson AGX Xavier 16GB/32GB: using adapter to install NV_L4T_FLASH_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER to /home/kdunne/nvidia/nvidia_sdk/JetPack_4.4.1_Linux_JETSON_AGX_XAVIER
16:18:06 INFO: Flash Jetson AGX Xavier 16GB/32GB: ###############################################################################
16:08:35 INFO: Flash Jetson AGX Xavier 16GB/32GB: Error: probing the target board failed.
16:08:35 INFO: Flash Jetson AGX Xavier 16GB/32GB: Make sure the target board is connected through
16:08:35 INFO: Flash Jetson AGX Xavier 16GB/32GB: USB port and is in recovery mode.
16:08:35 INFO: Flash Jetson AGX Xavier 16GB/32GB: [ Component Install Finished with Error ]
16:08:35 INFO: Flash Jetson AGX Xavier 16GB/32GB: [host] [ 4.00 KB used. Disk Avail: 782.20 GB ]
16:08:35 INFO: Flash Jetson AGX Xavier 16GB/32GB: [ NV_L4T_FLASH_XAVIER_WITH_OS_IMAGE_COMP Install took 6s ]
16:08:35 ERROR: Flash Jetson AGX Xavier 16GB/32GB: [error]: : [exec_command]: /bin/bash -c /tmp/tmp_NV_L4T_FLASH_XAVIER_WITH_OS_IMAGE_COMP.sh; [error]:

The cable and USB port are good, i’ve tested them independently, the NVIDIA dev-board appears to be connected, from DMESG:
[ 3222.261097] usb 1-5.3.3: new high-speed USB device number 13 using xhci_hcd
[ 3222.362369] usb 1-5.3.3: New USB device found, idVendor=0955, idProduct=7019, bcdDevice= 1.02
[ 3222.362374] usb 1-5.3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3222.362377] usb 1-5.3.3: Product: APX
[ 3222.362379] usb 1-5.3.3: Manufacturer: NVIDIA Corp.

lsusb shows:
Bus 001 Device 011: ID 0955:7019 NVidia Corp.

It should probably be working based on what you describe. Is the host PC a VM? This tends to cause such problems. If you are going through a USB HUB, then you might consider trying to connect the USB directly without the HUB.

Thanks Linuxdev for thinking on this, but no the host PC is an Ubuntu 18.04 bare-metal (non-VM) and the USB is directly plugged in.
I removed/re-installed the SDKManager on the same computer and got the same result, though interestingly it remembered my NVIDIA login, and the place where it left off in the SDK-install… Installing the SDKManager on another computer also running Ubuntu 18.04 is now completed the flashing, and on to the CUDA install. This would indicate that the SDKManager or the first-computer hardware is at fault.
So now to eliminate the first-computer-hardware… “how do I completely obliterate the SDKManager on the first computer” in order to validate this theory by starting from scratch again on that computer? Originally when installing I had plugged the USB-C connector from the Host into the wrong USB-C input on the Xavier,and the SDKManager, i believe, never ‘got over that’. or something.

When deleting the old SDKM, did you remove the “~/.nvsdkm” content? There is a lot of metadata there, not sure if this is where credentials are stored, but quite likely it is. You could in fact probably leave the “.deb” installed (unless there is a more recent version), and recursively delete the “~/.nvsdkm” and “~/nvidia” content. Running the sdkm program again would fill in that content as needed.

Yes, using the wrong USB-C port would indeed cause such a failure.