Nope - not a prophet of past events, merely observing that on one hand you complain about DJI and their firmware but on the other hand when their equipment tells you theres a fault, rather than heeding the warning that a "Persistent" error should be reported for further analysis you kept reebooting until you couldn't see the error and thought you'd fixed it. As for you following instructions - you've missed my point I'm saying that you DIDN'T follow instructions and kept rebooting until you couldn't see the fault rather than investigate the root cause.
I don't care about your personal attack on me, as it happens I really am an engineer, I have 30 plus years of experience in dealling with microprocessor controlled equipment ranging from simple domestic appliances upwards, I've seen people who've rebooted equipment multiple times when it's shown an error and eventually got it to start seemingly normally - then seem incredibly suprised and distressed when said equipments fault returns while it's operating and causes a major failure. The intention here was not to personally attack you but to put the information out there that if an error persists after a couple of reboots then, on something as safety critical as a UAV it's better to err on the side of caution and not fly until the fault has been fully investigated.
Oh, and just to be an "Incredibly smart", "know it all", I actually said " this is a complex piece of kit and occasional computational or startup sequence errors do happen" ( I did originally miss out the word startup but have edited the post for clarity) - by which I meant that yes sometimes you get a bug that causes a phantom error on startup so a reboot would usually clear that - if however it doesn't clear after a second reboot then that would really have to be counted as persistent.