Open KevinMX opened 5 months ago
Okay so I've checked last time I've flashed my LicheePi 4A I used sudo
too. It's simplest to just call sudo fastboot
and never worry again...
This issue comes back to us since ruyi
0.8.0+ changed the logic of invoking sudo
, ruyi
will wait for fastboot
infinitely for a device which will never show up due to lack of udev rules...
TL;DR: We should probably put a note somewhere; or just use
sudo
forfastboot
, like what we did fordd
, which should avoid the hassle:)In the flashing process of LPi4A, there are two stages (or as I would probably call it):
fastboot reboot
, flash all images into onboard eMMCSince
ruyi
does not run as root (as said by the RuyiSDK Device Provisioning Wizard & by design), and LPi4A's VID/PID is very unlikely to be there by default: udev rules (which, at least AFAIK, Debian & Arch are using this one)There's a change in the board's VID/PID between two stages, and this must be configured before we start the flashing process, since we're not running
fastboot
as root.udev rules like this will be needed: