Firmware kill switch

xman1 · Jul 14, 2017

Has anyone had time to dig through firmware .0400 to see if this switch exists in it as well?

<release version="01.03.0700" antirollback="1" enforce="0" enforce_ext="cn:0," from="2017/05/05" expire="2018/05/05>

So we know .0700 will not be working next May. Just hoping .0400 is still OK here.

HKFEVER · Jul 14, 2017

From what I have seem in different forums, the expiry date is set to one year from the manufacture date.

But what is the expiry date for?

xman1 · Jul 14, 2017

HKFEVER said:
From what I have seem in different forums, the expiry date is set to one year from the manufacture date.

But what is the expiry date for?

Kill switch to force an update of the firmware. I wonder if we can mod it somehow to put it sometime in 2030.

4wd · Jul 14, 2017

It does say enforce = "0" so might not be turned on.

Robbyg · Jul 14, 2017

It doesn't matter anymore. They have gone way past the point of fixing problems like that.

Rob

xman1 · Jul 14, 2017

Robbyg said:
It doesn't matter anymore. They have gone way past the point of fixing problems like that.

Rob

What do you mean? I see the firmware is open using a Busybox exploit, but I don't see where this is fixed.

Robbyg · Jul 14, 2017

xman1 said:
What do you mean? I see the firmware is open using a Busybox exploit, but I don't see where this is fixed.

Things are evolving by the hour.
I don't think a problem that is months away is a concern right now. As it stands the stuff is wide open, so when someone gets around to it I think it will be fixed in a matter of hours.

Rob

Forrest · Jul 15, 2017

Robbyg said:
It doesn't matter anymore. They have gone way past the point of fixing problems like that.

Rob

Robby I hope you hang around here awhile.

Kilrah · Jul 15, 2017

People have reportedly been using firmwares with dates that are past expiration and it's been no issue, so the current stance is "there's a way to make firmwares expire but it' not been enabled".

It's also not known what that "expiry" means, could also be that you can continue using it, just not reflash it if you were on another version.

funkyjunky · Jul 15, 2017

xman1 · Jul 15, 2017

Good to know guys. Thanks for the info.

Funkyjunky - how did you pull that one from the firmware?

funkyjunky · Jul 17, 2017

It´s in clear text in this file: "01.03.0400.cfg.sig" (you find this in the assistant-folder where the other *.sig-Firmware files are cached

xman1 · Jul 17, 2017

Thanks

dacoco · Feb 11, 2018

.400 expired yesterday. Does the Mavic still work after GPS Fix?

Kilrah · Feb 11, 2018

Can confirm a Mavic will still install .400 today while knowing the current date and start motors with GPS.
I.e. that "expiry" does nothing at all as previously suspected.