How to rollback Mavic firmware

LivinLarge · Dec 16, 2017

RevInstant said:
I suppose the only way to know about the camera is to test it out? There aren’t any other identifying markers?

Perhaps by the date of manufacture, but I don't know when they changed over. Mine works much better on 1080/60 now so I must have the later hardware. Just take it outside and shoot a 1 minute video of subjects with horizontal lines (siding roofing.) You will know as soon as you playback the video, if yours is fixed or not.

Haloweenhamster · Dec 17, 2017

RevInstant said:
I suppose the only way to know about the camera is to test it out? There aren’t any other identifying markers?

Yes
Check log on mavic using (if you are on fw below 1.3.1000)
Slack

If you are on 1.3.1000 onwards its FTP
Ftp://192.168.42.2
upgrade/dji/log/upgrade00.log
Then ask how to decrypt or send log to be decrypted

New
found A9SE, hw_str: CA02 Ver.A HY
new hardware, jump over on old file!

Old
found A9, hw_str: FC220 Ver.A

Will look like this

12-12 11:16:19.114 251 251 I DUSS&63[ sys_p1_check_ver:2469]:: check version for wm220_0100_v02.05.56.61_20170911.pro.fw.sig
12-12 11:16:19.123 251 251 I DUSS&63[ sys_p1_is_old_hardware:2252]:: found A9, hw_str: FC220 Ver.A
12-12 11:16:19.123 251 251 I DUSS&63[ sys_p1_check_ver:2584]:: 1:0: Same version.
12-12 11:16:19.123 251 251 I DUSS&63[ sys_p1_check_ver:2469]:: check version for wm220_0100_v02.08.05.06_20170906_ca02.pro.fw.sig
12-12 11:16:19.130 251 251 E DUSS&63[ sys_p1_check_ver:2567]:: hw_ver not match, jump over! current: FC220 Ver.A target: CA02
12-12 11:16:19.130 251 251 E DUSS&63[sys_p1_check_compability: 234]:: check version for file wm220_0100_v02.08.05.06_20170906_ca02.pro.fw.sig error
12-12 11:16:19.130 251 251 I DUSS&63[ sys_p1_check_ver:2469]:: check version for wm220_0101_v02.08.05.06_20170906_ca02.pro.fw.sig
12-12 11:16:19.138 251 251 E DUSS&63[ sys_p1_check_ver:2567]:: hw_ver not match, jump over! current: FC220 Ver.A target: CA02
12-12 11:16:19.138 251 251 E DUSS&63[sys_p1_check_compability: 234]:: check version for file wm220_0101_v02.08.05.06_20170906_ca02.pro.fw.sig error
12-12 11:16:19.138 251 251 I DUSS&63[ sys_p1_check_ver:2469]:: check version for wm220_0101_v02.05.56.61_20170911.pro.fw.sig
12-12 11:16:19.148 251 251 I DUSS&63[ sys_p1_is_old_hardware:2252]:: found A9, hw_str: FC220 Ver.A
12-12 11:16:19.148 251 251 I DUSS&63[ sys_p1_check_ver:2584]:: 1:1: Same version.

RevInstant · Dec 17, 2017

Spent my morning getting the Mavic onto .700 and watching those digdat0 videos.

God bless that guy and everyone else that made that absurdly simple for someone like me o_o

Next step is figuring out flight controller firmware and what to do about the DjiGo app. Kinda lost on the app since it always restricted flight unless I upgraded.

Ash77 · Dec 17, 2017

RevInstant said:
Spent my morning getting the Mavic onto .700 and watching those digdat0 videos.

God bless that guy and everyone else that made that absurdly simple for someone like me o_o

Next step is figuring out flight controller firmware and what to do about the DjiGo app. Kinda lost on the app since it always restricted flight unless I upgraded.

Nice one. What firmware did you have on your Mavic before hand?

RevInstant · Dec 17, 2017

Ash77 said:
Nice one. What firmware did you have on your Mavic before hand?

If I'm not mistaken is was .800? The Mavic I got was made on Aug 8th and I was able to fairly easily roll back to .700

But this was all because I'd accidentally updated my original Mavic to the latest firmware without knowing about NFZ's and all the lockdown DJI had implemented.

Ash77 · Dec 17, 2017

RevInstant said:
If I'm not mistaken is was .800? The Mavic I got was made on Aug 8th and I was able to fairly easily roll back to .700

But this was all because I'd accidentally updated my original Mavic to the latest firmware without knowing about NFZ's and all the lockdown DJI had implemented.

I see. I’m running the latest firmware So I’m pretty much stuffed until some bright sparks work their magic on it

RevInstant · Dec 17, 2017

Alright. I could use some help from you guys again.

So I've been browsing YT and the forums and I can't seem to find any suggestions for DJIGo4 app version recommendations for IOS. I currently have an iPhone X, if it matters, and want to make sure if it connects that it wont continue to bug me with update popups. Also not sure if I need to do anything to remove the NFZ restrictions inside of the app itself. I've got everything set on the Mavic end, NFZ removed and stuff. It's just the Go4 app that I'm stuck on.

rickw · Dec 17, 2017

rickw · Dec 17, 2017

I use 4.0.6

RevInstant · Dec 17, 2017

rickw said:
I use 4.0.6

I’ll give that one a go. Thanks

Does the firmware on the Mav impact the version of Go I should use?

angusc · Dec 17, 2017

RevInstant said:
Next step is figuring out flight controller firmware and what to do about the DjiGo app. Kinda lost on the app since it always restricted flight unless I upgraded.

Check out and install "no root fire wall" that can stop the DJI app from connecting to the server and therefore checking for any updates on its software.

RevInstant · Dec 17, 2017

I can not get this process to download the older GO4 apps to work. It seems basic enough and I downloaded the right versions of iTunes and Charles but I can't get the "Edit req" tab to show up at all x.x

rickw · Dec 17, 2017

watch video closely

rickw · Dec 17, 2017

did you dl and use older version of itunes?

RevInstant · Dec 17, 2017

rickw said:
did you dl and use older version of itunes?

Yeah. It’s weird. I’m going to wipe it and try again tonight.

For now I’ve got a seemingly larger concern. I tried taking it outside to see if it’d even fly with the mods and I get a constant GPS disconnect error that keeps me from launching. Tried calibrating multiple times and no luck.

Have you guys ever encountered this? I’m wondering if I put the wrong value in someone when doing the parameter change or if it’s a result of trying to fly a craft on older firmware with an updated Go4 app.

rickw · Dec 17, 2017

you can use any version of go4

Borntofly · Dec 17, 2017

modbuilder said:
I need ideas for a communication problem while trying to flash 3.700 to the RC. I've successfully used DUMLdore-2 to rollback FW on AC from 3.900 to 3.700. Have downloaded the 3.700 zipped BIN file for the RC and unzipped it (double checked to make sure I'm asking for the RC firmware). Connected RC to PC, powered up both RC and AC (that's the process called for in my DJI owner documentation for connecting Assistant2 to RC), launched Assistant2 to check for connection, and it hooks up fine. Shutdown Assistant2, launched DUMLdore and it initially reports connected on COM4. Made sure DUMLdore is set for RC. Tried Backup FW, and it fails with a time out in about 5-10 seconds and no longer shows a connection. Have to repeat the whole start up process to re-connect, and this time check for setting to RC and go straight to load FW and Flash without trying Backup. It appears to Load but gets another timeout after 5-10 seconds when it tries to flash. Again shows no connection after the timeout. Have tried re-downloading and unzipping both DUMLdore and FW bin files for 3.700 for RC. Also have use both 7-zip and Winzip for unzipping. 7-zip reports an unexpected end while unzipping the RC bin file, but Winzip does not. Unzipped executables from both 7-zip and Winzip produce the same appearance and time out performance while running DUMLdore with the 3.700 RC FW.

Am out of gas on ideas and trial/error. Am hoping some of the experts can hold my hand through the connection problem. TIA......... R

I believe I have a similar situation. While the issue isn't with my rc. It's with the AC. Using the current Dumldore v2, I've been able to run a backup, however when I try to flash, I get the dreaded "check ftp on a browser for connection" message. I've checked the rdnis, even added the IP address to it. No positive results. Here's what's happening, when I connect the AC via USB, powered on, then open dumldore, dumldore sees the connected ac and I then select my file for flash. During the uploading process, similar to Modbuilder, I get a disconnect chime and dumldore ceases to continue with the upload and eventually kicks back the ftp error msg. Now here's the kicker.... ALL usb's disconnect from the PC and won't reconnect unless I reboot the computer. I've checked all drivers, uninstalled and reinstalled just to be sure. Also tried it against another computer, and it flashed just fine, tho it's not my computer. ****.

Not sure what else to investigate. This photo shows the rdnis check. Oddly I've only seen this happen once.