Replies: 3 comments
-
Yes, I think we should even prevent major version updates for non-reset keys completely (in firmware, not in update tools). |
Beta Was this translation helpful? Give feedback.
-
So the workflow would be reset first then update major version? It would be quite convienient if they would not to "dirty flash". If that is not sure, I would issue just capital letter warnings. IMHO it is not good style to patronize users too heavily. What shouldn't happen is that everything breaks without a word of warning |
Beta Was this translation helpful? Give feedback.
-
There's no reason for a major version update if it's backwards-compatible, so I'd say "yes". |
Beta Was this translation helpful? Give feedback.
-
I just updated the firmware reading that it might erase all RKs (which is fine to me). However, I wondered if that is an expected behaviour if another user is calling
My suggestion would be to actually add notices to the update json and display them on the commandline...
Beta Was this translation helpful? Give feedback.
All reactions