How to rollback Mavic firmware

[Haloweenhamster]

Some stripped back fw
1.3.400 fc 305 & 306 to load old fc
1.3.700 fc 305, 306 & 905
1.4.0000 gim 400 to set version back to 0000
1.4.0000 nofc -305 & 306 to update to 0000 -fc
1.4.0100 nofc -305, 306 & 905

Meet Google Drive – One place for all your files

Added complete packages

 

[Haloweenhamster]

Sorry if people tried to connect, noticed that sharing had turned off, should work now

 

[Xtreme Drone Pilot]

Thanks for these files. What about RC and Goggles, can they be upgraded to official 1.4.0000 or they need modded FW, too?

 

[Haloweenhamster]

Standard update

 

[Haloweenhamster]

Some stripped back fw
1.3.400 fc 305 & 306 to load old fc
1.4.0000 gim 400 to set version back to 0000
1.4.0000 nofc -305 & 306 to update to 0000 -fc
1.4.0000 bat 1100 to update additional batteries

Meet Google Drive – One place for all your files

If you are on 1.4.0000 already then use 1.3.400 fc followed by 1.4.0000 gim

If you are on any other version then its 1.3.400 fc followed by 1.4.0000 nofc

If you have additional batteries not on 1.4.0000 then use 1.4.0000 bat for a quicker update

 

[satanael]

Sorry the developer of DUMLdore posted the answer 23rd Oct, I missed it
View attachment 24580

Hello everyone,

I'm trying to find a way to get back to life my mavic pro RC who is still stuck on "CONNECTING_" since my last update try with the Dji 2 assistant ...
Even with your setup, i'm still getting the FTP connection error with DUMLdore V1.93 on Windows 10 (firewall off, internet off, NDIS IP setup done, usb cable plugged before powered on, DUMLdore run as admin).

I think it's due to the fact that my mavic RC as no valid firmware installed since the last update... Firmware shown is V00.00.0000 with the DJI 2 assistant soft !
I still waiting some help from DJI, but i'm still trying to solve this issue alone.

 

[Haloweenhamster]

If assistant 2 can connect to it to show fw v00.00.0000 then can't you use it to install the latest fw?

 

[satanael]

If assistant 2 can connect to it to show fw v00.00.0000 then can't you use it to install the latest fw?

Nope i can"t, the upgrade process not even start to reach the 1%. It quickly fails as shown in the log below :

[20:31:18][WebGetter2 ] send get firmware file request...
[20:31:18][WebFileGetter ] Downloading [wm220_2803_v00.00.03.08_20170302_cd02.pro.fw.sig] 100% 8400.30 kB/s
[20:31:18][WebGetter2 ] send get firmware file request...
[20:31:18][WebFileGetter ] Downloading [wm220_2803_v00.00.03.08_20170302_cd01.pro.fw.sig] 100% 8018.47 kB/s
[20:31:18][WebGetter2 ] send get firmware file request...
[20:31:18][WebFileGetter ] Downloading [wm220_2803_v00.00.04.08_20170828_cd03.pro.fw.sig] 100% 7669.84 kB/s
[20:31:18][WebGetter2 ] send get firmware file request...
[20:31:18][WebFileGetter ] Downloading [wm220_0905_v01.00.01.05_20170727.pro.fw.sig] 100% 20395.54 kB/s
[20:31:18][UpgradeMgr ] Download finished.
[20:31:18][UpgradeMgr ] Package Version: [01.04.0000]
[20:31:18][UpgradeMgr ] Total [2] file need to upgrade:
[20:31:18][UpgradeMgr ] Ofdm_ground(7) Size 4238080
[20:31:18][UpgradeMgr ] Dm368_ground(1) Size 25753952
[20:31:18][UpgradeMgr ] End file list!
[20:31:18][UpgradeMgr ] total upgrade time : 61431
[20:31:18][UpgradeMgr ] enable_upgrading_flag: true
[20:31:22][upgrade1860Ex ] get upgrade log file failed!!! retcode: 0
[20:31:22][upgrade1860Ex ] ======================= UPGRADE FAILURE: upgrade prepare failure, ErrorCode: 255
[20:31:22][upgrade1860Ex ] ======================= Time : 3.79 second
[20:31:22][DiagMsg ] upgrade prepare failure, ErrorCode: 255
[20:31:22][UpgradeMgr ] Dm368_ground(1) result false
[20:31:22][UpgradeManager ] WebActionResult:
[20:31:22][UpgradeMgr ] upgrade_pack_file_data time used: 3.787 Second
[20:31:22][UpgradeMgr ] enable_upgrading_flag: false

 

[Xtreme Drone Pilot]

Just wanted to say thank you to all helpful members who share their knowledge. Thanks to lifting the altitude limit, I was able to fly in Eastern Sierra Nevada where the desert rises at a shallow angle (probably no more than 5-10% grade) thousands of feet from valleys to mountain ranges, with no roads or trail to come closer to them. So I flew about 4km towards mountains and eventually reached altitude of more than 500m above the takeoff point, yet the whole time I was no more than 200ft above the ground, well below the FAA 'recommendation'! 100% legit, and this arbitrary 500m limit is as stupid as a text editor that won't allow you to type any words starting with 'f' just because there's an f word.

Signed,
Responsible pilot

 

[Xtreme Drone Pilot]

After 1.4.000 sans 305&306, with verbatim digdat0's configuration, I have two obvious problems:

1. The checkbox for precision takeoff is gone, only standard takeoff.
2. On RTH, it starts landing facing the way it flew home, it doesn't turn to match the heading of the takeoff.

Any ideas?

 

[angusc]

If assistant 2 can connect to it to show fw v00.00.0000 then can't you use it to install the latest fw?

Does anyone know if it is possible to put the Mavic RC in to a bootloader state to see adb commands or in to a debug mode and access settings via adb or pc?

 

[Xtreme Drone Pilot]

After 1.4.000 sans 305&306, with verbatim digdat0's configuration, I have two obvious problems:

1. The checkbox for precision takeoff is gone, only standard takeoff.
2. On RTH, it starts landing facing the way it flew home, it doesn't turn to match the heading of the takeoff.

Any ideas?

I've flashed stock .700, then modded 1.4.0000. The precision takeoff checkbox is back, but RTH problem remains. Anyone?

 

[Drone Master]

I really like this thread guys!
Thanks @digdat0 and @jezzab for your support thus far.
Keep the info flowing!
Also thanks to @clackey , @LuvMyTJ and @dirkclod for this thread to exsist!
Good stuff! It’s everything we needed for our Mavs to fly without BS.!
Why is this not a sticky by now? Hehe.....

 

[JustViewerFun]

There's no issue rolling it back from 1.4.000

Last week, I rolled back both the Mavic and RC from my modified 01.04.0000 firmware to 01.03.0400 to test what I thought was a gimbal roll problem. I ran a test start the motors right afterwards and all seemed to be fine until I went out to fly. On several occasions, my Mavic wouldn't startup and said something like "incompatible firmware. Update required." It also said the motors would remain locked until the update was done - something to that effect at least. It didn't make any sense, because I rolled back both the controller and the Mavic. One battery ran fine, but the another had this same problem. It Go4 didn't give me an option to sync the battery firmware - and I didn't expect it to since it was already newer and had whatever 01.03.0400 needed.

After cycling the power on the remote a few times, I finally cleared the "incompatible firmware" message and was able to fly without any other problems. This happened several times this last week. It was very strange, and I don't understand why rolling back from 01.04.0000 to 01.03.0400 caused this problem. I had rolled back to 01.03.0400 from other versions of firmware without any problems whatsoever, but going from 01.04.0000 back to 01.03.0400 sure gave me a lot of unexpected and inconsistent trouble.

Has anybody else experienced anything like this? Does anyone know why on the rolled back firmware it would say "incompatible firmware" and lock the motors, but after a few restarts of the RC and Mavic it would be fine?

 

[angusc]

Could it be some internal cache storage in the Go 4 app from the new firmware that takes a few restarts to clear out and settle down after installing the older forbade firmware?

 

[Haloweenhamster]

So you had 1 battery with the correct fw that was fine, other batteries with newer fw which is know to throw up messages and you are wondering why you had problems?

Try searching battery firmware

the mavic compares the last installed fw to the battery fw and checks that they are the same

If you turn on the RC, open the app, click go fly, then turn on mavic it skips the fw check

 

[JustViewerFun]

I just did the following and flashed back to AC in usual time if around 15 minutes:

1) Deleted folders 305 & 306 from latest firmware V01.04.0000.
2) Connected AC to dumldor and backed up my modified firmware V01.03.700 from AC to Dumldore.
3) Opened that backup using 7-zip and copied the folders 305 & 306 in to new firmware bin file.
4) Flashed modified firmware v01.04.0000 took around 15 as usual.
5) check parameters folder and all modified settings present and correct.

Thanks for detailing the steps, angusc. I thought the firmware flash would only flash the modules that were present in the package and leave the others alone.

The first and second time I upgraded to 01.04.0000, I did step 1, but I didn't do Step 3. Looking at my backup from that upgrade, I see that the 305 and 306 modules were missing completely from my Mavic. I didn't experienced any flight problems. On my third time upgrading, I did Step 3. I haven't flown yet to see if there is a difference.

I noticed that DJI Assistant2 shows my current version as "01.04.0000-". Next to the latest version It says "Upgrade" and the button is highlighted (see image below). Stupid question here , but does that mean DJI Assistant2 is recognizing that my current firmware is modified or not the same as the latest version? My tests connecting the RC and Mavic said I had the latest version and I was not prompted to upgrade. Are others with modified 01.04.0000 firmware seeing this also?

View media item 1379

 

[JustViewerFun]

Could it be some internal cache storage in the Go 4 app from the new firmware that takes a few restarts to clear out and settle down after installing the older forbade firmware?

I didn't restart Go4 between restarting the RC and Mavic. The problem just went away.

 

[JustViewerFun]

So you had 1 battery with the correct fw that was fine, other batteries with newer fw which is know to throw up messages and you are wondering why you had problems?

Try searching battery firmware

the mavic compares the last installed fw to the battery fw and checks that they are the same

If you turn on the RC, open the app, click go fly, then turn on mavic it skips the fw check

All batteries were on the same firmware. After the upgrade/downgrades, I tested with each battery to make sure they were - something I always do when upgrading/downgrading firmware. No problems, no prompts to match battery FW with Mavic/RC. After the problem cleared on the first battery the rest had no such problems.

I skipped the FW check - I always do - but in my experience, Go4 still checks the firmware in the background and display on the top bar before taking off. I've been flying my Mavic for 9 months on older version FW, and never before have I been blocked from flight. With the error/message and motor lock, it was the same backup that I previously loaded and had no problems with.

Very strange, huh?

 

[Haloweenhamster]

One battery ran fine, but the another had this same problem. It Go4 didn't give me an option to sync the battery firmware - and I didn't expect it to since it was already newer and had whatever 01.03.0400 needed.

that's why I thought you had left newer firmware on one battery

I have seen 2 people say about the new go app locking their mavics, I'm guessing dji are trying to clamp down but its not working correctly yet