mavic pro platinum firmware downgrade

wucaiss · Jun 19, 2018

pepeleascov said:
What firmware are you using to downgrade? did you removed the mentioned modules from it?

thanks for the reply，issue sloved，just follow Maverick78's guide，the only thing is that the precising landing is not working now，is yours ok？

pepeleascov · Jun 19, 2018

wucaiss said:
thanks for the reply，issue sloved，just follow Maverick78's guide，the only thing is that the precising landing is not working now，is yours ok？

Precision landing won't work because you're flashing the old flight controllers, who doesn't have the precision landing feature

wucaiss · Jun 20, 2018

pepeleascov said:
Precision landing won't work because you're flashing the old flight controllers, who doesn't have the precision landing feature

understood.

esuohdica · Jun 23, 2018

Maverick78 said:
Link to the modded Djigo i use :
DJI Go 4.1.22-mod.zip

Hey Maverick, I'm just going through this whole process now with my MPP. Can you tell me which mods are activated in your version of the .22 app? Cheers

Rayearth · Jun 24, 2018

Hi guys, I followed the procedure to rollback Mavic Pro Platinum and modify height limit.
After installing SD card I downgraded from 1.04.0300 (original) to 1.04.0000 (original) and from there to 1.03.0700 (mod, no 1200,1201,1202,1203 modules). Modified height limit parameter and afterwards flashed modded 1.04.0300 (no 305,306,905 modules).
I got 'motor current error', wasn't comfortable with that so I did a factory reset and flashed back the original 1.04.0300 to finally have some fun with the new toy without messing with in its' guts.

Then I got back to the idea and followed Steven Lawyer's tutorial here Rooting Mavic Pro in Latest firmware with Force FCC and Boost and No NFZ - RC Groups

In step 3 "Flash FW.700" I'm not able to get DUMLdore 3.07 to show the 1.03.0700 fw installed. Flashed it like 10 times and it always say I'm on 1.04.0300. Tried other versions of DUMLdore run on either Windows 7 or 10. Same result.

Actually even after I flash back the original 1.04.0300, the DJI Assistant 2 (1.1.2) is unable to show me what version I'm currently on.
The NLD MOD Client 1.7.0.1 states that it cannot identify my fw version and shows these version info below.

After flashing original 1.03.0700:
{"DEVICE_MODEL":"wm220","MODULES":[
{"MODULE":"Camera4K","FIRMWARE":"2.6.484"},
{"MODULE":"Camera4K_Loader","FIRMWARE":"2.6.484"},
{"MODULE":"FC_Loader","FIRMWARE":"34.4.0.23"},
{"MODULE":"FC","FIRMWARE":"3.2.30.13"},
{"MODULE":"Gimbal303","FIRMWARE":"1.50.12.1"},
{"MODULE":"1860","FIRMWARE":"1.5.0.20"},
{"MODULE":"CPLD","FIRMWARE":"0.0.4.8"},
{"MODULE":"UltrasonicM0","FIRMWARE":"1.0.0.8"},
{"MODULE":"CP","FIRMWARE":"47.26.2.11"},
{"MODULE":"Battery0","FIRMWARE":"1.0.18.16"},
{"MODULE":"ESC0","FIRMWARE":"0.0.0.0"},
{"MODULE":"ESC1","FIRMWARE":"0.0.0.0"},
{"MODULE":"ESC2","FIRMWARE":"1.1.0.71"},
{"MODULE":"ESC3","FIRMWARE":"1.1.0.71"}]}

After flashing original 1.04.0300:
{"DEVICE_MODEL":"wm220","MODULES":[
{"MODULE":"Camera4K","FIRMWARE":"2.10.519"},
{"MODULE":"Camera4K_Loader","FIRMWARE":"2.10.519"},
{"MODULE":"FC_Loader","FIRMWARE":"34.4.0.24"},
{"MODULE":"FC","FIRMWARE":"3.2.44.7"},
{"MODULE":"Gimbal303","FIRMWARE":"1.50.12.10"},
{"MODULE":"1860","FIRMWARE":"1.6.0.35"},
{"MODULE":"2100","FIRMWARE":"1.1.0.2"},
{"MODULE":"CPLD","FIRMWARE":"0.0.4.9"},
{"MODULE":"UltrasonicM0","FIRMWARE":"1.0.0.11"},
{"MODULE":"DJI_Vision","FIRMWARE":"1.3.0.99"},
{"MODULE":"CP","FIRMWARE":"47.26.2.18"},
{"MODULE":"Battery0","FIRMWARE":"1.0.18.24"},
{"MODULE":"ESC0","FIRMWARE":"1.1.0.71"},
{"MODULE":"ESC1","FIRMWARE":"1.1.0.71"},
{"MODULE":"ESC2","FIRMWARE":"1.1.0.71"},
{"MODULE":"ESC3","FIRMWARE":"1.1.0.71"}]}

Have you encountered similar issues? How can I get DJI Assistant to show the current fw version or NLD to identify it properly? And finally what could be wrong that DUMLdore does not show the .0700 fw after flash?

Arpath · Jun 24, 2018

Rayearth said:
Hi guys, I followed the procedure to rollback Mavic Pro Platinum and modify height limit.
After installing SD card I downgraded from 1.04.0300 (original) to 1.04.0000 (original) and from there to 1.03.0700 (mod, no 1200,1201,1202,1203 modules). Modified height limit parameter and afterwards flashed modded 1.04.0300 (no 305,306,905 modules).
I got 'motor current error', wasn't comfortable with that so I did a factory reset and flashed back the original 1.04.0300 to finally have some fun with the new toy without messing with in its' guts.

Then I got back to the idea and followed Steven Lawyer's tutorial here Rooting Mavic Pro in Latest firmware with Force FCC and Boost and No NFZ - RC Groups

In step 3 "Flash FW.700" I'm not able to get DUMLdore 3.07 to show the 1.03.0700 fw installed. Flashed it like 10 times and it always say I'm on 1.04.0300. Tried other versions of DUMLdore run on either Windows 7 or 10. Same result.

Actually even after I flash back the original 1.04.0300, the DJI Assistant 2 (1.1.2) is unable to show me what version I'm currently on.
The NLD MOD Client 1.7.0.1 states that it cannot identify my fw version and shows these version info below.

After flashing original 1.03.0700:
{"DEVICE_MODEL":"wm220","MODULES":[
{"MODULE":"Camera4K","FIRMWARE":"2.6.484"},
{"MODULE":"Camera4K_Loader","FIRMWARE":"2.6.484"},
{"MODULE":"FC_Loader","FIRMWARE":"34.4.0.23"},
{"MODULE":"FC","FIRMWARE":"3.2.30.13"},
{"MODULE":"Gimbal303","FIRMWARE":"1.50.12.1"},
{"MODULE":"1860","FIRMWARE":"1.5.0.20"},
{"MODULE":"CPLD","FIRMWARE":"0.0.4.8"},
{"MODULE":"UltrasonicM0","FIRMWARE":"1.0.0.8"},
{"MODULE":"CP","FIRMWARE":"47.26.2.11"},
{"MODULE":"Battery0","FIRMWARE":"1.0.18.16"},
{"MODULE":"ESC0","FIRMWARE":"0.0.0.0"},
{"MODULE":"ESC1","FIRMWARE":"0.0.0.0"},
{"MODULE":"ESC2","FIRMWARE":"1.1.0.71"},
{"MODULE":"ESC3","FIRMWARE":"1.1.0.71"}]}

After flashing original 1.04.0300:
{"DEVICE_MODEL":"wm220","MODULES":[
{"MODULE":"Camera4K","FIRMWARE":"2.10.519"},
{"MODULE":"Camera4K_Loader","FIRMWARE":"2.10.519"},
{"MODULE":"FC_Loader","FIRMWARE":"34.4.0.24"},
{"MODULE":"FC","FIRMWARE":"3.2.44.7"},
{"MODULE":"Gimbal303","FIRMWARE":"1.50.12.10"},
{"MODULE":"1860","FIRMWARE":"1.6.0.35"},
{"MODULE":"2100","FIRMWARE":"1.1.0.2"},
{"MODULE":"CPLD","FIRMWARE":"0.0.4.9"},
{"MODULE":"UltrasonicM0","FIRMWARE":"1.0.0.11"},
{"MODULE":"DJI_Vision","FIRMWARE":"1.3.0.99"},
{"MODULE":"CP","FIRMWARE":"47.26.2.18"},
{"MODULE":"Battery0","FIRMWARE":"1.0.18.24"},
{"MODULE":"ESC0","FIRMWARE":"1.1.0.71"},
{"MODULE":"ESC1","FIRMWARE":"1.1.0.71"},
{"MODULE":"ESC2","FIRMWARE":"1.1.0.71"},
{"MODULE":"ESC3","FIRMWARE":"1.1.0.71"}]}

Have you encountered similar issues? How can I get DJI Assistant to show the current fw version or NLD to identify it properly? And finally what could be wrong that DUMLdore does not show the .0700 fw after flash?

Hy i never could see my Firmware with dji sssistant
but i tried three times the rollback and midification like discribed and with the last try it works fine.
But you have to be carefull inbeetween my sensors were disabled.
Yoe have to make carefully test after proccessing Firmware Action

Kind regards

ferraript · Jun 24, 2018

Rayearth said:
DJI Assistant 2 (1.1.2) is unable to show me what version I'm currently on

yeah, that's a known issue
you need to have newest DJI Assistant installed if you want to check FW version, but since you use NLD client, you can just believe what it says

>FW versions of modules
as you can see by yourself, somewhere on the way down from 1.4.300 to 1.3.700 your ESC0 and ESC1 modules lost their FW completely
I followed that StevenLawyer's guide too and I think that the same thing happened to me twice (yesterday was the last time)
after downgrading to 1.3.700 I got ESC error and the only cure was to upgrade to original 1.4.300

and then I got an idea
if all I want to do is to have new firmware with flight controllers from 1.3.700, why should I downgrade down to 1.3.700 and then upgrade back up?
it's useless
all I need to do is to flash flight controllers from 1.3.700
so I took 1.3.700 FW, removed all modules except 0305 and 0306 and I flashed it with DUMLdore
and it worked like a charm!

so if you wanna try it too, then:
after you get root with DUMLRacer, in step 6 you check it with adb shell command
and then, in step 3 (it's called STEP 3: Flash FW.700), there is a link to file V01.03.0700_no_905_Mavic_dji_system.bin
download it and remove from it all modules except 0305 and 0306 (and that wm220.cfg.sig file)
flash it with the newest DUMLdore
after it's done, check in DJI Assistant 1.1.2 that modding is possible for all the parameters
then you can continue with STEP 5: Remove the NFZ Files

Quad808 · Jun 25, 2018

Gang,
NLD support here. We are working on our firmware identification process right now, and it will be fixed soon.
Some points: using mixed firmware cripples precision landing. Period. No fix.
Anytime you flash up or down and have any sensor errors, flash the same firmware again. Always flash twice, no matter what.
1st flash takes about 15 min, 2nd error checking takes 3

esuohdica · Jun 26, 2018

Well I followed Mavericks method and I ended up getting loads of ESC errors like others have. Also, I had the DJI Go app 4.1.3 (Steven Lawyers Boost app) disconnect completely during my test flight. I tried to reconnect a couple of times during the flight, but managed to return to home and land OK, this scared me! Never had a disconnection like that before, it always came back, but this time I couldn't reconnect, even after I landed and restarted the app!

Anyway this is what I did, in order, maybe someone can point out where I went wrong!?
Starting from a standard MPP with latest firmware 1.4.300. (in a CE country UK)
(All I am really looking for is more range, I have tried the Boost app and force FCC apps, but they don't seem to be working on latest MPP firmware? Is this true?).

*Inserted the SDcard, after a struggle with the tight front clips on the shell!
*Used Dumbledore 3.07 to flash back to 1.3.700 using the prepared FW file that Maverick shared.
*Repeated the flash to make sure - Showed version 1.3.700 at end and completed 100%
*Adjusted flight parameters with Assistant 1.1.2 Sport+ GPS+ Unlock height, disable NFZ etc.
* Used Dumbledore 3.07 to flash forwards to 1.4.300 using the version that Maverick shared.
*Repeat the flash to make sure - Showed version 1.4.300 at end and completed 100%
*recalibrate IMU and compass
*Test fly - all parameter mods worked, Height restriction removed OK... But I had the errors mentioned above.

Any ideas?
Like I said I am after more reliable range, not really bothered about removing height limits and NFZ, so potentially I could revert back to latest firmware, only if I could guarantee that either force Boost or force FCC was working on standard 1.4.300.

The NLD site seems to say that force FCC works on the standard latest firmware, can anyone confirm this?

Cheers all.

Rayearth · Jun 27, 2018

ferraript said:
yeah, that's a known issue
you need to have newest DJI Assistant installed if you want to check FW version, but since you use NLD client, you can just believe what it says

Even on the newest DJI Assistant the software is not showing anything but 'Cannot load firmware list. Please retry'.
I'm just guessing that maybe the flashed firmware is not identified as legitimate.

ferraript said:
so if you wanna try it too, then:
after you get root with DUMLRacer, in step 6 you check it with adb shell command
and then, in step 3 (it's called STEP 3: Flash FW.700), there is a link to file V01.03.0700_no_905_Mavic_dji_system.bin
download it and remove from it all modules except 0305 and 0306 (and that wm220.cfg.sig file)
flash it with the newest DUMLdore
after it's done, check in DJI Assistant 1.1.2 that modding is possible for all the parameters
then you can continue with STEP 5: Remove the NFZ Files

Thanks ferraript, your approach sounded reasonable so I followed your advise.
I flashed only the 3 files from 1.03.0700 (wm220.cfg.sig and the flight controller modules 0305, 0306) over the 1.04.0300 fw. Height_limit parameter in DJI Assistant is visible so that's a success.

I noticed that after flashing, DUMLdore is showing that I'm currently on 1.03.0700

Wish I knew how is this software recognizing fw version...

NLD shows a mixed fw as expected:

{"DEVICE_MODEL":"wm220","MODULES":[
{"MODULE":"Camera4K","FIRMWARE":"2.10.519"},
{"MODULE":"Camera4K_Loader","FIRMWARE":"2.10.519"},
{"MODULE":"FC_Loader","FIRMWARE":"34.4.0.23"},
{"MODULE":"FC","FIRMWARE":"3.2.30.13"},
{"MODULE":"Gimbal303","FIRMWARE":"1.50.12.10"},
{"MODULE":"1860","FIRMWARE":"1.6.0.35"},
{"MODULE":"2100","FIRMWARE":"1.1.0.2"},
{"MODULE":"CPLD","FIRMWARE":"0.0.4.9"},
{"MODULE":"UltrasonicM0","FIRMWARE":"1.0.0.11"},
{"MODULE":"DJI_Vision","FIRMWARE":"1.3.0.99"},
{"MODULE":"CP","FIRMWARE":"47.26.2.18"},
{"MODULE":"Battery0","FIRMWARE":"1.0.18.24"},
{"MODULE":"ESC0","FIRMWARE":"1.1.0.71"},
{"MODULE":"ESC1","FIRMWARE":"1.1.0.71"},
{"MODULE":"ESC2","FIRMWARE":"1.1.0.71"},
{"MODULE":"ESC3","FIRMWARE":"1.1.0.71"}]}

Gonna check the quad in action as soon as the weather gets better at my location.

I'm wondering, do you guys have any errors in your update logs? Do you know what to look for if checking for flash fails?

ferraript · Jun 28, 2018

Rayearth said:
Height_limit parameter in DJI Assistant is visible so that's a success

I'm glad it worked

>Even on the newest DJI Assistant the software is not showing anything but 'Cannot load firmware list. Please retry'.
that's strange, it works fine for me
but it doesn't matter because we have firmware working so we don't need new DJI Assistant anymore

>I noticed that after flashing, DUMLdore is showing that I'm currently on 1.03.0700
same for me - I believe it shows FW version according to the flight controllers FW version as this is the most important value for us, modders

Quad808 · Jul 6, 2018

DD will show you the firmware version of your last flash, since the flashed firmware is loaded on the bird. Flashing ONLY 305/306 and the .cfg.sig is the way to go...why go down and go back up? Unless you are super picky and NEED to show you are on 01.04.0300 for some reason, even though you are on mixed. Well done and good tip ferraript.
We at NLD have found that the DJI flashing process is basically...well...crap. Since we have revamped our firmware detection methods, we check every module version and are finding quite a lot of firmware that not all modules have flashed, especially the camera module for some reason. It's no wonder that when people downgrade and upgrade and downgrade there are weird problems. Always flash twice. And if you get weird performance, flash it a 3rd time.

krassest · Jul 29, 2018

Hi, I have a big problem.
Yesterday I downgraded my MPP to 1.03.0700 (installed an SD card before). I had to use DD 2.12 for the step from 1.04.0000 to 1.03.0700. I did a little testing with height and it worked fine.
Today I was trying to update to 1.04.0300 (without 305, 306, 905). I did use DD 3.1. The first try went good and I went out for testing. Almost crashed it because somehow the sensors where not working (no protection at all). OK I thought let's do the upgrade again but now it was stuck in the flashing process at 99% and kept connecting and disconnecting (the USB chime) all the time. I waited 10 mins and then powered off and disconnected.
After that nothing works out. I can't get any connection to the RC nor connection to the PC via USB and the fan does not work any more.

Any ideas how to come out of this.

TBdog86 · Jul 29, 2018

krassest said:
Hi, I have a big problem.
Yesterday I downgraded my MPP to 1.03.0700 (installed an SD card before). I had to use DD 2.12 for the step from 1.04.0000 to 1.03.0700. I did a little testing with height and it worked fine.
Today I was trying to update to 1.04.0300 (without 305, 306, 905). I did use DD 3.1. The first try went good and I went out for testing. Almost crashed it because somehow the sensors where not working (no protection at all). OK I thought let's do the upgrade again but now it was stuck in the flashing process at 99% and kept connecting and disconnecting (the USB chime) all the time. I waited 10 mins and then powered off and disconnected.
After that nothing works out. I can't get any connection to the RC nor connection to the PC via USB and the fan does not work any more.

Any ideas how to come out of this.

You locked up the bird, And lost its comms drivers, And also corrected the drivers you were using on your computer probably. I’m assuming the main light on the back is a steady red, once the bird is Initialized.

This happened to and I could only get it out of that mode in one way.

This might sounds crazy but it works, unplug battery and let any residual voltage dissipate.

Find your self another computer ( not the one that you had the failure on) Install a fresh copy of the latest DJI assistant 2. Basically what you’re trying to do is to connect your DJI Mavic pro to a new computer that does not have any corruption in the COM port so that way when you initially reconnect your Mavic for the first time to the computer that you just installed DJI assistant 2, it will try to reload the Comms drivers. After this happens immediately update your software for me I updated to version 1.4.100 then back down.

I did try initially do use the same computer that my Mavic got locked up on by uninstalling DJI but it would not work or use my other laptop in on the first attempt no problems.

krassest · Jul 29, 2018

OK, thanks for the quick reply.
You are right, I got the steady red LED.
I will try it as soon as I'm home again. Any idea how it comes to that mess?
Yesterday I did about 20 attempts of firmware downgrade until it worked finaly with 1.03.700. No such problams at all.
I thought the re-upgrade to 1.04.300 would be easier.

TBdog86 · Jul 29, 2018

No idea why, gotta be a bug somewhere. It's tricky to get out of it sometimes too. Its happened to me 2 times.

I'm stuck with Motor over-current alarm (Convinced it's FM, since I get the warning even when I pull back the settings, then it goes away completely when upgrade back to say 1.4.1, Need to bring it back down again and see what happens to rule out any other possibilities)

Haven't not tried to rollback and bring the mod's with me back to 1.4.1.

Nosebump · Jul 29, 2018

Out of curiosity, WHY do you want to downgrade? Are you experiencing problems with the latest version (-I'm not)? Is there a performance enhancement for the old? The only problem that was confusing was on initial boot-up. I had to agree to the legal boilerplate, but when I continued, it bounced me back to the beginning of the process. Finally I saw (-dimly) a box that had to be checked. Once I did that I could continue. Other than that, the latest version works correctly.

As a rule, I generally wait as long as I can before upgrading. If there are problems, they'll show up here.

krassest · Jul 30, 2018

Nosebump said:
Out of curiosity, WHY do you want to downgrade?

in my case to get rid of the height limit

krassest · Jul 30, 2018

TBdog86 said:
After this happens immediately update your software for me I updated to version 1.4.100 then back down.

What program for the update? DJI-Assistant2 or DUMLdoreV3

TBdog86 · Jul 30, 2018

krassest said:
What program for the update? DJI-Assistant2 or DUMLdoreV3

Use assistant 2 to reload the firmware at 1.4.100 that way it gets a good clean copy, then redo the downgrade and upgrade again.

I did the downgrade then upgraded back yesterday, but I keep getting a motor current warning once I downgrade. (Not sure if you are seeing this also)