It's easy to accidentally flash the RoT with an A image when its boot preference is set to B, or vice versa. This leads to great confusion when your new image does not run after the RoT resets. Similarly, other commands like humility tasks can end up using an archive that doesn't match what's actually running. It would be helpful for humility to print a warning message if it detects these situations. This could probably be done as part of the ID check, by checking if the running PC matches the range in the archive.
Someday we could turn the warning into a hard error or have humility automatically detect which archive to use, but let's start with just the warning.
It's easy to accidentally flash the RoT with an A image when its boot preference is set to B, or vice versa. This leads to great confusion when your new image does not run after the RoT resets. Similarly, other commands like
humility taskscan end up using an archive that doesn't match what's actually running. It would be helpful for humility to print a warning message if it detects these situations. This could probably be done as part of the ID check, by checking if the running PC matches the range in the archive.Someday we could turn the warning into a hard error or have humility automatically detect which archive to use, but let's start with just the warning.