We have numerous AGX Xaviers that we are trying to reuse on a new project.
I’m using the SDK to flash to Jetpack 5.1.5 and all goes well apart from one very annoying point.
Despite doing a manual install and defining a new username and password the old user name (and sometimes unknown password) appear after flashing.
Hi,
What do you mean about old user after flashing?
Is it still a /home/${old_user_name} in your device after flashing?
Thanks
Only the old user name appears on the login screen. The new userid I requested via manual setup is not being created. I now have the password to this device and can see that the home dircetory for the old user was created when I flashed. I ask for a user called “newname” and get “one”. I would really like to do the equivalent of a “factory reset” and set these devices to Jetpack 5.1.5 with new userids.
In your host PC, in the flash software, go to “Linux_for_Tegra/rootfs/etc/”. Then see if your user name is listed in file “passwd”. For example, view with:
cat passwd | grep -i 'the name of the account'
If the user name has been put into that, the it is because the flash software was set up for that name/pass already before flash to become part of the flash. If not, then something mysterious is going on, e..g, the device being flashed might not be the expected device.
The flash, despite saying successful, has some errors in the logs. Looks like some partitions are not being updated. Old /home and /etc . I have attached the logs and a photo. When the system boot I see Jetson uefi frimware from 2025-03-04.
SDKM_logs_JetPack_5.1.5_Linux_for_Jetson_AGX_Xavier_modules_2025-04-10_08-17-04.zip (130.2 KB)
It is hard to tell what is going on from screenshots. Are you flashing eMMC? Is there any other kind of storage device involved, e.g., SD card or NVMe?
The flash software itself, on the host PC, would keep changes made to the software being flashed, and one can set up a user name and password and home directory content on the host PC before flashing. If anyone had set that up and you did not wipe out the “Linux_for_Tegra/rootfs/” subdirectory, then that content will be added as previously edited each time the Jetson is flashed.
If content is not doing what you think it should do, then it must be either (A) the boot device is not what you think, which can happen more easily than most people know due to the lack of a true BIOS and each flash essentially also flashing BIOS with boot preferences, or it can be (B), the flash content itself has this on it.
I’m flashing to the eMMC. I have cleared down the LInux_for_Tegra directory several time and the username that appears is not one I ever configured. Just tried a second device and flashing the APP partition works without issue. It’s some specific about this device. I checked and there is no SD card or NVME in/on it.
What confuses me is it keeps saying sucessfully flashed but nothing has changed in the APP partition. Its the same if i restore a backup from another machine to this device using the flash.sh command .
How can I see if I’m flashing to the wrong boot disk?
I suppose this is one of the issues you get when you don’t know what the prior user did with the hardware.
Problem solved - this device was unique - there was a NVME card in it - I had been flashing the eMMC and booting from NVME.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.