Hi, Just got my Mavic 2 Zoom today - (Upgrading from a Mavic Pro). I've spent the past 4 hours trying to get it to update. Current status is showing all 4 LED's as RED - a critical error I believe.
These are the steps I went through.
1. Take delivery of M2Zoom - Smile - a lot.
2. Unbox and charge both the controller and the battery
3. Connect iPhone to Controller - load up DJI Go 4.3.3
4. Proceed to update FW as directed.
5. Update completed - Controller and AC both rebooted
and now the fun begins.....
6. RC no longer connected to AC
7. AC shows all LED's Solid Red - RC shows 'Connecting'
8. Can't retry FW update via Go4 as the RC and AC are disconnected
9. Move to PC and install DJI Assistant for Mavic 2 (Latest version from DJI website)
10. Connect AC to PC - DJI Assistant recognises M2Zoom and shows that there is an update available
11. Update FW - fails every time at 75%
12. Still can't connect RC to AC - Relink button on AC does nothing at all
13. Move to Second PC that has never had DJI assistant installed and repeat from step 9.
14. Fail - again and again and again.
15. Battery on AC now too low to continue.
16. Go downstairs - plug RC and AC battery in to their respective chargers.
17. Get Beer from fridge, (Corona - as you're asking)
18. Go back to 1st PC and Vent.
19. Contemplate whether I'll trust it in the air after so many FW issues, (if I can get it in the Air)
20. HUGELY Disappointed.

21. Get 2nd Corona from fridge - Cheers!
22. Battery now charged again - goto step 9.
23. FW update (V01.00.0100) now failed at 87% - (I think the beer is helping TBH)
24. Goto step 9
25. Goto Step 9 whilst watching awesome videos from my faithful, reliable Spark.
26. Uninstall everything and goto step 9 - consider getting the third Corona from the fridge.
27. Start new thread about the utterly miserable experience I'm having with my £1100 Paperweight.

I had this problem. Then it went away when I turned off a bunch of other wifi and Bluetooth signals in the house including the TV.  It might had had done something. I can't say for sure.

Step 17 was the fatal mistake.  

You should have gone with

Followed by Chasers of

Several things to check.
1) Do you have a fast (10-Mbps) and reliable (no packet drops) internet connection - make sure nothing else hogs your internet connection
2) Make sure nothing else is running on PC - disable any Virus detection software
3) Try different USB cable - make sure USB connector fully seats on MP2
4) If you didn't disable Signed Driver checking in PC BIOS when you installed Assistant-2 - you need too

HedgeTrimmer Posted at 2018-10-12 18:13
Several things to check.
1) Do you have a fast (10-Mbps) and reliable (no packet drops) internet connection - make sure nothing else hogs your internet connection
2) Make sure nothing else is running on PC - disable any Virus detection software

1 - Yes
2 - Yes
3 - Yes
4 - Yes

Still showing red on all four corners and fails to update / become usable - I logged a ticket with DJI last night - no response. So with a heavy heart and after a total of 7 hours faffing about I've logged a return with Amazon and the Wife has packed it up ready to go. Back to the MP.

HedgeTrimmer Posted at 2018-10-12 18:05
Step 17 was the fatal mistake.  

You should have gone with

Humm,

1. No, dirt slow, as sloe as I can order.
2. No
3. No
4. No

All kinds of stuff on this slow laptop.

Never have had a FW update issue on the MPP, or the M2Z, once I just did it in DJIGo4 from a phone hotspot.

I guess some ppl just get all the bad luck...sorry....I'll send good thoughts..

Hi DTH, we're sorry for the late response and the troubles you encountered. Just to verify, has the unit been activated? Sorry for my question as I do not see any Mavic 2 icon under your avatar for now.
Regarding the firmware update, does the same error 0x02e904 appear every time? If yes, please kindly refer to the below and export the corresponding upgrade log, we'll forward to our engineers to check the exact status, thanks!

Assistant 2(Windows) C: /Users/XXXXXX/AppData/Roaming/DJI Assistant 2/upgrade_log
Assistant 2(MAC): ~/Library/Application Support/DJI Assistant 2/upgrade_log
APP(IOS): Click the DJI logo on the left upper corner more than 10 times, you will see the log and copy it to us
APP(Android): dji/dji.go.v4/log/cache/up_new_all

DJI Susan Posted at 2018-10-14 00:43
Hi DTH, we're sorry for the late response and the troubles you encountered. Just to verify, has the unit been activated? Sorry for my question as I do not see any Mavic 2 icon under your avatar for now.
Regarding the firmware update, does the same error 0x02e904 appear every time? If yes, please kindly refer to the below and export the corresponding upgrade log, we'll forward to our engineers to check the exact status, thanks!

Hi Susan, it's already been returned - I did however buy another one today - and that has worked perfectly following the same method as the first. I have even bought Care Refresh - Just in-case
Any idea when precision landing will be added? Without it the landing accuracy is pretty poor compared to my MP or my Spark.
(Not sure why it's not showing up on my profile though)

DTH Posted at 2018-10-14 11:08
Hi Susan, it's already been returned - I did however buy another one today - and that has worked perfectly following the same method as the first. I have even bought Care Refresh - Just in-case  
Any idea when precision landing will be added? Without it the landing accuracy is pretty poor compared to my MP or my Spark.
(Not sure why it's not showing up on my profile though)

Thanks for the clarification. About the precision landing, we do not have the estimated turnaround for now, sorry about this. If this is an update, we'll release on our website at the first time. Appreciate your patience and support.

As for the icon under the Avatar, do you use the same email address to activate the Mavic 2 and login to the forum? If yes, please kindly provide us with your email address and aircraft SN, we'd like to check the exact status.

Hello, I am having this EXACT same problem in addition the "connect/bind light" next to the connect button does not light up when button pressed at any stage? Any help would be greatly appreciated. Unfortunately I am not in the position to return it with ease!

I have succeeded in updating the firmware after about 10 attempts. No to try connect the RC still no light!

I had a very similar issue as described above - except that mine started after multiple successful flights.

I have had nothing but smooth flying and have had zero incidents and have used utmost caution when handling/shipping/flying my new expensive toy.

Upon turning on the AC and the Remote, the AC would show flickering yellow leds on the hind legs (indicating that it's trying to connect). The remote would stay in a "connecting..." state.

I figured for some reason perhaps the two became unlinked so i proceeded to try and "re-link" them.

Now i'm no stranger to drones/controllers/receivers and flight controllers - I've built a dozen or so FPV racers and have done my fair bit of troubleshooting - so binding a drone/receiver to a RC is relatively straightforward.

As per the DJI documentation, i proceeded to get the remote in its binding state (i used both the app and the button combination to do this) - but my problem was this:

Whenever i pressed the little bind button on the AC, the bind light (which is supposed to light up) did not do so. It's like I just couldn't get the AC to go into Link/Bind mode.

Eventually i resorted to various firmware upgrades / downgrades (I had multiple successful flights using 01.00.0200 prior to the sudden connection problems between the AC and RC). I did this using the DJI Assistant App on my Windows 10 desktop. Using the app wasn't an option anymore, since the RC and AC could not connect.

Just like in the thread above i struggled for hours to get the firmware installations to complete - and when i eventually did, i still had the no-binding-light and just-connecting issue as described above.

Eventually i returned to the retailer where i purchased the Mavic - a very reputable local high-end camera dealership who are also official DJI suppliers. The guy in the shop basically did exactly what i tried, but with no luck (could not bind and could not update firmware/downgrade firmware or reset to factory settings).

They sent it away to the regional head office - and i have been informed that they too have not been able to get the two units to bind - and that they are now shipping the Mavic/RC and Battery to DJI China.

Now I live on the other side of the world (Cape Town, South Africa), and sending something to China and back takes upwards of 6 weeks (and is really expensive even by international standards).

They also took the liberty to inform me that should DJI decide to charge me for any "repairs" that i would be provided with a quote - and if I decide to decline the quote, i would be liable for the expensive shipping.

What makes everything even worse is that my wife and I have an upcoming trip to the Philippines - we leave around mid-March - and i purchased the Mavic mostly with this trip in mind - giving me a few months to get used to it before traveling.

I am extremely disappointed with my purchase - the lack in local technical expertise/really bad after-sales support and the reliability of the unit itself.

I am quite sure I will never purchase another DJI product again.

I DON'T KNOW WHY NO ONE HAS SAID THIS YET

You need ASSISTANT 2   F O R  MAVIC 2.................NOT FOR MAVIC

Go back and uninstall Assistant 2 for Mavic.......find the Assistant 2 for MAVIC 2 AND  install......try again,  have a beer on me.   HMMMMM....should be this one " DJI Assistant 2 For Mavic v2.0.6
2018-12-21 "

Randy

rwynant V1 Posted at 1-6 09:26
I DON'T KNOW WHY NO ONE HAS SAID THIS YET

You need ASSISTANT 2   F O R  MAVIC 2.................NOT FOR MAVIC

I didn't specify the version of DJI Assistant in my previous post - apologies for that. I was using DJI Assistant 2 for my Mavic 2 Pro - version 2.0.6 to be exact (which at the time when i tried was the latest).



For all the versions of firmware that i tried, the download completed successfully, the transmission to the AC worked successfully, but, depending on the version 01.00.0000 / 01.00.0100 or 01.00.0200 the actual installation would fail at different percentages on the aircraft.

I also uploaded quite a few error logs for the failed installations.

After multiple retries, eventually it worked and i got *.0200 installed again on both the RC and AC (the RC again (the same versions that worked for numerous flights before the connection issues started).

The 1 out of 10 successful firmware installations i can live with (multiple other users complained about the same thing on the forums and other sites) - but the problem where the RC and AC could not link still persisted.

Also - as mentioned - the retailer as well as their regional office both concurred that there was an issue - hence them sending the aircraft back to China.

I am currently having the same issue with upgrading firmware (to v01.00.0200) of my AC using the latest Assistant v2.0.6.. it gets to 99% and goes straight to Update failed.
I have tried upgrading to the lower version of firmware and got to 100% and the failure popped up as soon as it started transmitting. I keep trying so far. Will upload the log if it fails again.

If DJI really wants to make this working easily then the assistent should allow us to download the firmware file and install it in a separate step. I feel like it keeps downloading the complete file and failing on instalation. The download is ridicilously slow for some reason despite my fast broadband. Thanks for any advice how to upgrade the firmware so i can finally fly my drone. Not a good start so far.
Btw upgrading firmware of the RC was smooth.
...
another upgrade failed at the start of transmitting after finishing the download.. Log Upload fails despite i have internet connection..
--- log upload error ---
[20:35:27.245][DJIWebFileGetter    ] Reply error :299
[20:35:27.245][DJIWebFileGetter    ] Reply error string :Error downloading <url removed>/upgrade_log - server replied: Unprocessable Entity
---

--- relevant lines from the log following the download and failing at the start of upgrade ---
[20:29:14.312][DJIWebFileGetter    ] Downloading [wm240_0801_v10.00.08.17_20181114.pro.fw.sig] 100% 255.97 kB/s
[20:29:14.312][DJIWebFileGetter    ] [OnFinish]reply statusCode=200
[20:29:15.170][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   0.00 second
[20:29:15.385][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   0.22 second
[20:29:15.637][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   0.47 second
[20:29:15.888][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   0.72 second
[20:29:16.146][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   0.98 second
[20:29:16.388][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   1.22 second
[20:29:16.647][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   1.48 second
[20:29:16.888][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   1.72 second
[20:29:17.144][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   1.97 second
[20:29:17.391][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   2.22 second
[20:29:17.651][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   2.48 second
[20:29:17.886][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   2.72 second
[20:29:18.146][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   2.98 second
[20:29:18.393][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   3.22 second
[20:29:18.638][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   3.47 second
[20:29:18.893][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   3.72 second
[20:29:19.141][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   3.97 second
[20:29:19.388][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   4.22 second
[20:29:19.636][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   4.47 second
[20:29:19.886][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   4.72 second
[20:29:20.148][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   4.98 second
[20:29:20.389][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   5.22 second
[20:29:20.641][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   5.47 second
[20:29:20.887][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   5.72 second
[20:29:21.139][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   5.97 second
[20:29:21.401][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   6.23 second
[20:29:21.646][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   6.48 second
[20:29:21.899][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   6.73 second
[20:29:22.138][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   6.97 second
[20:29:22.389][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   7.22 second
[20:29:22.638][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   7.47 second
[20:29:22.896][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   7.73 second
[20:29:23.144][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   7.97 second
[20:29:23.390][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   8.22 second
[20:29:23.643][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   8.47 second
[20:29:23.886][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   8.72 second
[20:29:24.136][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   8.97 second
[20:29:24.394][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   9.22 second
[20:29:24.647][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   9.48 second
[20:29:24.894][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   9.72 second
[20:29:25.135][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   9.97 second
[20:29:25.145][DJIFirmwareUpgrader ] Wait [         prepare]   0.01 second
[20:29:25.154][DJIFirmwareUpgrader ] Wait [         prepare]   0.02 second
[20:29:47.089][DJIIdentifierMgr    ] Device Remove COM6
[20:29:47.089][DJISerialIo         ] Free COM6 success!
[20:29:47.089][DJICmdIo            ] DJICmdIo closed.
[20:29:47.089][DJIDeviceMgr        ] DevRemoved, Uav, wm240, 01.00.0000, d2c93546cedb5624df59ac7adb3b4f1920c4d1ea
[20:29:47.090][DJIFirmUpgrader2    ] GetUpgradeLog file timeout!!!
[20:29:47.090][DJIFirmUpgrader2    ] ======================= UPGRADE FAILURE: ftp net error
[20:29:47.090][DJIFirmUpgrader2    ] ======================= Time :  31.92 second
[20:29:47.230][DJIIdentifierMgr    ] Device Arrive COM6
[20:29:47.230][DJICmdIo            ] open COM6
[20:29:47.449][DJISerialIo         ] Open COM6 success!
[20:29:47.449][DJIIdentifierMgr    ] open device succeed
[20:29:47.449][DJISecondIdentifier_] release class DJIIdentifierInterface<class DJISecondIdentifier>
[20:29:47.449][DJISecondIdentifier_] Release DJIIdentifier.
[20:29:47.564][DJISecondIdentifier_] GetSerialNumber failed!!! Error Code: 0xe0
[20:29:47.564][DJIIdentifierMgr    ] [Uav          , wm240        , 01.00.0000   ], App
[20:29:47.565][DJIDeviceMgr        ] device service ready! COM6
[20:29:47.565][DJIDeviceMgr        ] DevArrival, Uav, wm240, ln02,01.00.0000, d2c93546cedb5624df59ac7adb3b4f1920c4d1ea, normal
[20:29:47.572][DJIUpgradeMgr       ] set date time to device 0x0901 success!!!
[20:29:47.574][DJIDynamicParamTable] Table: 0, Size: 1339 , Hash: f24afe12
[20:29:47.574][DJIDynamicPushTable ] Table: 0, Size: 48   , Hash: fdb84000
[20:29:47.574][DJIDynamicCmdTable  ] Cmd Table Size: 112  , Hash: f24afe12
[20:29:47.576][DJIDynamicParamTable] GetConfigTableAttribute failed!!! Error Code: 9
[20:29:47.577][DJIDynamicPushTable ] Table: 1, Size: 42   , Hash: fdf3e000
[20:29:47.661][DJIDynamicPushTable ] GetPushConfigTableAttribute failed!!! Error Code: 9
[20:29:47.662][DJIDynamicTableMgr  ]   0%
[20:29:47.673][DJIDynamicTableMgr  ]   1%
[20:29:47.677][DJIDynamicTableMgr  ]   2%
[20:29:47.681][DJIDynamicTableMgr  ]   3%
[20:29:47.682][DJIUpgradeMgr       ] set date time to device 0x0801 success!!!
[20:29:47.685][DJIDynamicTableMgr  ]   4%
[20:29:47.689][DJIDynamicTableMgr  ]   5%
[20:29:47.710][DJIDynamicTableMgr  ]   6%
[20:29:47.739][DJIDynamicTableMgr  ]   7%
[20:29:47.748][DJIDynamicTableMgr  ]   8%
[20:29:47.756][DJIDynamicTableMgr  ]   9%
[20:29:47.773][DJIDynamicTableMgr  ]  10%
[20:29:47.776][DJIDynamicTableMgr  ]  11%
[20:29:47.861][DJIWebFileGetter    ] [OnFinish]reply statusCode=200
[20:29:48.016][DJIIdentifierMgr    ] Device Remove COM6
[20:29:48.016][DJISerialIo         ] Free COM6 success!
[20:29:48.016][DJICmdIo            ] DJICmdIo closed.
[20:29:48.016][DJIDeviceMgr        ] DevRemoved, Uav, wm240, 01.00.0000, d2c93546cedb5624df59ac7adb3b4f1920c4d1ea
[20:29:48.017][DJIDynamicParamTable] GetConfigTableItemAttribute timeout
[20:29:48.017][DJIDynamicParamTable] GetConfigTableItemAttribute timeout
the timeout goes for sone time..
--

here are relevant lines from another log as the Log Upload doesn't work for me.. the file is too big and upload speed too slow or whatever reason there is for not working..
anyway.. i used Samsung USB-C cable with a better result as the connection between my Win10 and the AC wasn't dropping. i thought it was feature of the Assistant but it seems not.. it seems that the supplied USB-C cable is faulty hence the "Device Remove COM6" records in my previous logs..  however the upgrade still fails..

[20:53:47.617][DJIWebFileGetter    ] Downloading [wm240_0801_v10.00.08.17_20181114.pro.fw.sig] 100% 253.35 kB/s
[20:53:47.617][DJIWebFileGetter    ] [OnFinish]reply statusCode=200
[20:53:48.506][DJIFirmwareUpgrader ] Wait [   enter_upgrade]   0.00 second
[20:53:48.506][DJIFirmUpgrader2    ] GetUpgradeLog file timeout!!!
[20:53:48.506][DJIFirmUpgrader2    ] ======================= UPGRADE FAILURE: DoEnterUpgradeMode Timeout
[20:53:48.506][DJIFirmUpgrader2    ] ======================= Time :   0.00 second

What do you say DJI?? Shall I return the drone??

tomaash Posted at 1-7 00:07
here are relevant lines from another log as the Log Upload doesn't work for me.. the file is too big and upload speed too slow or whatever reason there is for not working..
anyway.. i used Samsung USB-C cable with a better result as the connection between my Win10 and the AC wasn't dropping. i thought it was feature of the Assistant but it seems not.. it seems that the supplied USB-C cable is faulty hence the "Device Remove COM6" records in my previous logs..  however the upgrade still fails..

I totally agree that the re-downloading just doesn't make sense - surely after downloading the payload and verifying file integrity the download shouldn't be required again. They should make re-download source package an option.

I'm sure I downloaded the exact same version 01.00.0200 payload about 10 times before it eventually upgraded successfully. I used both the supplied cable and another USB-C cable that came with my GoPro 7. Both transmitted to the AC successfully, but in both cases the installations failed numerous times. I can't recall with which cable the installation eventually succeeded.

Unfortunately for me, even with the firmware back in place, my AC still didn't want to go into the linking state after pressing the link button. Whether that could be firmware-related or not is a different kettle of fish.

karlp Posted at 1-7 03:07
I totally agree that the re-downloading just doesn't make sense - surely after downloading the payload and verifying file integrity the download shouldn't be required again. They should make re-download source package an option.

I'm sure I downloaded the exact same version 01.00.0200 payload about 10 times before it eventually upgraded successfully. I used both the supplied cable and another USB-C cable that came with my GoPro 7. Both transmitted to the AC successfully, but in both cases the installations failed numerous times. I can't recall with which cable the installation eventually succeeded.

After about 40 days my Mavic is in the way home. The amount of time spent waiting for the repair by far outweighs the time that I've had it in my posession.

Just for the other users - the pro-forma invoice from the repair people reads as follows:

"After carrying out the damage assessment, we found that the Core Board is damaged. Due to under warranty, DJI will provide free repair service"

I maintain that I've had about three weeks of successful flying and always handled my MP2 with utmost caution and delicacy and that it is extremely unlikely that anything that I did could have affected the board. I have a strong suspicion that the "core board" was damaged from day one (I also had firmware update issues from day one), but I only noticed issues when my linking/binding troubles started.

Glad they replaced it, but really p*ssed off that it took a month and a half.

I have now lost a month and a half of warranty and flying time, and I don't want to speculate on how they "repaired" (or with what they replaced) the damaged board.

This whole experience has been a serious blow to my opinion of how trustworthy/reliable DJI products are and I hope nobody else has to go through it like I did.

Hello,

I have just bought Mavic 2 zoom, and after activated and updated RC i have problem with update AC.
I tried everything from this movie: https://www.youtube.com/watch?v=0qheJJtvPFY but no success.

Now I tried update by DJI Assistant 2 (V2.0.6).
1. I Connected AC and power on.

2. I Clicked Upgrade and after few seccond I have Update failed with 0% downloaded


I Was uploaded error log.

Please help me - what can i do next?

Today everything OK. Update succesfull.

Bricked by the update here too.. lost remote connection and nothing i did seems to fix it..

wont bind back no matter what...

When I encounter hiccups with firmware installation I shutting down everything. After that I upgrade remote first. Restarting. And connect drone. All updates perfectly.

Flouts Posted at 4-21 13:01
Bricked by the upodate here too.. lost remote connection and nothing i did seems to fix it..

wont bind back no matter what...

i will just send my drone to dji for service no luck with  NLD

piotrzuba Posted at 2-22 05:35
Today everything OK. Update succesfull.

does it work

If you guys are trying to update w/ an overclocked PC especially w/ RAM OCed that is unstable it will corrupt updates and installations w/o saying a word.

I have exactly the same issue. My Mavic 2 Zoom Drone firmware crashes at 75% always. Now Drone doesnt bing with RC.
I just tried to upgrade a thousand times with no success. Tries everything for almost two weeks. No Help from DJI either.. SHAME on YOU DJI..
I was almost FORCED by DJI to do a firmware upgrade and now have a bricked Mavic 2 Zoom.  (DJI Go is always forcing me to upgrade).
WTF DJI!! PLEASE SOLVE THIS PROBLEM!!!
I have paid 1200 Dollars and need a SOLUTION. START putting DJI Assist 2 version that enables a FULL HARDWARE RESET. This is outrageous..
This is unbelievable. You force us to do an upgrade and then dont help us solve the problem YOU CREATED.
Its the last DJI drone I buy. You are not helping your customers, you ARE LOOSING CREDIBILITY.

This is not a hardware error. This is FIRMWARE UPGRADING ERROR.
The Drone was fine . never ever gave any error until I upgraded the firmware.
After upgrade (crashed upgrading at 75%) never ever could I bind the RC to the Drone.
After 1000000000000000000000000000000000000000 tries, I know know that its DJI Fault, you should be getting a new Assist 2 That enables to restore corrupt firmware installation since that option existed in Mavic Pro.

Me and 1000000000000000000 others having the same issue.
This is not Tolerable. You are earning a lot of money from us and are not behaving as professionals.
You know what the problem is.
FIX IT!!!!
A VERY ANGRY CUSTOMER

interesting....  i got lucky i guess. Bought it  and charged it 100% and let it do all the firmware updates. No issues.  Wonder what the outcome wil be for you.
I would redo everything again but this time using all different cables and PC. then see what happens. Ive had firmware updates fail due to a bad cable that worked 100% fine but just would not do updates. This was on smartphones. Would not hurt to try my suggestion.. might save you a head ache

djiuser_64G1x5Gpuov1 Posted at 4-26 16:25
This is not a hardware error. This is FIRMWARE UPGRADING ERROR.
The Drone was fine . never ever gave any error until I upgraded the firmware.
After upgrade (crashed upgrading at 75%) never ever could I bind the RC to the Drone.

Agreed with the above

TRIED  ON 2 DIFF PCS..NO LUCK ON EITHER.. ITS A SOFTWARE PROBLEM CAUSED BY FAULTY  PROGRAMMING ON THE FIRMWARE..
GET YOUR PEOPLE TO SOLVE THE ISSUE GUYS.. TAKING THE BIRD TO DJI IS NO SUPPORT WHATSOEVER

Hi,
I faced the same problem. My drone turned into a brick in firmware upgrade. The update finished with a "undefined 0x02e904" error at 75%. RC does not connect to AC.
I got the drone a week ago. Just a week, Carl!
I am very upset.
Today I will take it to the service center.

Sorry to hear about all the trouble you guys are having. I have the Zoom and didn't have these troubles.

But I also didn't use assistant 2. I only do updates using my iPad connected to Wifi. The few times it's

failed I just use my iPhone.

I am having the same problem with my M2P.

I avoided updating because past experience with my P3P told me that updating FW rarely benefits me.

After continued pressure to update, I tried to update FW on my M2P, and I get the same freeze at 75% and I cannot link AC to my Smart Controller.

It's been a while since any posts have been added here.  

Is there ANY good news with this issue?

a lot of folks have better luck using a usb2 port and not the usb3, I had problems using usb3, changed to usb2 and it all went along fine.

raven swe Posted at 11-14 00:24
a lot of folks have better luck using a usb2 port and not the usb3, I had problems using usb3, changed to usb2 and it all went along fine.

Ok.

I will try this later this evening.

Thanks.

Hi Guys,

I have the same problem, controller not connecting despite following the instructions. Has anyone come up with a solution. I have had only one 20 minute flight & I purchased a PGYTech Box for carry and Storage.

Frustrated to say the least.  

gerrythedub Posted at 11-16 08:07
Hi Guys,

I have the same problem, controller not connecting despite following the instructions. Has anyone come up with a solution. I have had only one 20 minute flight & I purchased a PGYTech Box for carry and Storage.

This was probably not the place for this problem. But just to update RC and drone connected this afternoon, Why & How I don't know. Gremlins I assume.

DJI Susan Posted at 2018-10-14 00:43
Hi DTH, we're sorry for the late response and the troubles you encountered. Just to verify, has the unit been activated? Sorry for my question as I do not see any Mavic 2 icon under your avatar for now.
Regarding the firmware update, does the same error 0x02e904 appear every time? If yes, please kindly refer to the below and export the corresponding upgrade log, we'll forward to our engineers to check the exact status, thanks!

Hi, DJI Susan!

I have same problem with update my mavic 2 pro. I repeat update process many times, but it forever fails.
This error in my log
[08:57:09.809][DJIDeviceMgr        ] DevArrival, Uav, wm240, ln01,01.00.0400, 9d47181ae6f5f9bf500c49389b3784ada0fea892, normal
[08:57:09.809][DJISoftUpdater      ]  platform:mac software_version:2.0.10.8 model_type:wm240 firmware_version:01.00.0400
[08:57:09.810][DJIDeviceMgr        ] Info Ui...
[08:57:10.361][DJIWebFileGetter    ] [OnFinish]reply statusCode=200
[08:57:10.361][DJISoftUpdater      ] get check ok
[08:58:21.703][DJIFirmUpgrader2    ] send stop
[08:58:21.703][DJIFirmUpgrader2    ] Upgrade Module: 09 007  error,Error Code: 04, Reason:  当前模块连接不上
[08:58:21.713][DJIFirmUpgrader2    ] receive upgrade finish
[08:58:24.968][DJIIdentifierMgr    ] Device Remove /dev/cu.usbmodem14205
[08:58:24.969][DJICmdIo            ] DJICmdIo closed.
[08:58:24.969][DJIDeviceMgr        ] DevRemoved, Uav, wm240, 01.00.0400, 9d47181ae6f5f9bf500c49389b3784ada0fea892
[08:58:24.970][DJIDeviceMgr        ] Info Ui...
[08:58:24.970][DJICmdIo            ] io fail Timeout Commands
[08:58:24.970][DJIFirmUpgrader2    ] GetUpgradeLog file timeout!!!
[08:58:24.970][DJIFirmUpgrader2    ] ======================= UPGRADE FAILURE: push upgrade failed status, Error Code: 0x02e904

And after reconnect drone to DJI Assistent - errors and timeouts from modules
[08:58:44.687][DJIDynamicTableMgr  ] load from file: Template v3.2.14.0.cfg
[08:58:44.739][DJIDynamicTableMgr  ] dyn_mgr read, TIME: 1215(ms).
[08:58:44.772][DJIDynamicParamTable] book g_status_rc_current_urgent_mode_switch, but not exist
[08:58:44.773][DJIDynamicParamTable] book g_real_status_control_real_mode, but not exist
[08:58:44.782][DJIDynamicParamTable] book g_status_rc_current_urgent_mode_switch, but not exist
[08:58:44.782][DJIDynamicParamTable] book g_real_status_control_real_mode, but not exist
[08:58:48.374][DJIUpgradeMgr       ] set date time to device 0x0901 timeout!!!
[09:06:04.973][DJISoftUpdater      ]  platform:mac software_version:2.0.10.8 model_type: firmware_version:
[09:06:04.974][DJIDeviceMgr        ] Refresh DevArrival, Uav, wm240, ln01,01.00.0400, 9d47181ae6f5f9bf500c49389b3784ada0fea892, normal
[09:06:04.974][DJISoftUpdater      ]  platform:mac software_version:2.0.10.8 model_type:wm240 firmware_version:01.00.0400
[09:06:05.517][DJISoftUpdater      ]  platform:mac software_version:2.0.10.8 model_type: firmware_version:
[09:06:05.518][DJIDeviceMgr        ] Refresh DevArrival, Uav, wm240, ln01,01.00.0400, 9d47181ae6f5f9bf500c49389b3784ada0fea892, normal
[09:06:05.518][DJISoftUpdater      ]  platform:mac software_version:2.0.10.8 model_type:wm240 firmware_version:01.00.0400
[09:06:05.633][DJIWebFileGetter    ] [OnFinish]reply statusCode=200
[09:06:05.633][DJISoftUpdater      ] get check ok
[09:06:06.014][DJIWebFileGetter    ] [OnFinish]reply statusCode=200
[09:06:06.014][DJISoftUpdater      ] get check ok
[09:06:06.015][DJIWebFileGetter    ] [OnFinish]reply statusCode=200
[09:06:06.015][DJISoftUpdater      ] get check ok
[09:06:06.018][DJIWebFileGetter    ] [OnFinish]reply statusCode=200
[09:06:06.018][DJISoftUpdater      ] get check ok
[09:06:24.016][DJISoftUpdater      ]  platform:mac software_version:2.0.10.8 model_type: firmware_version:
[09:06:24.017][DJIDeviceMgr        ] Refresh DevArrival, Uav, wm240, ln01,01.00.0400, 9d47181ae6f5f9bf500c49389b3784ada0fea892, normal
[09:06:24.017][DJISoftUpdater      ]  platform:mac software_version:2.0.10.8 model_type:wm240 firmware_version:01.00.0400
[09:06:24.105][DJISoftUpdater      ]  platform:mac software_version:2.0.10.8 model_type: firmware_version:
[09:06:24.105][DJIDeviceMgr        ] Refresh DevArrival, Uav, wm240, ln01,01.00.0400, 9d47181ae6f5f9bf500c49389b3784ada0fea892, normal
[09:06:24.106][DJISoftUpdater      ]  platform:mac software_version:2.0.10.8 model_type:wm240 firmware_version:01.00.0400
[09:06:24.339][DJIDeviceInfoEnumera]   4%  1/24 Camera4K(0)
[09:06:24.347][DJIDeviceInfoEnumera]   8%  2/24 Mvo(5)
[09:06:24.353][DJIDeviceInfoEnumera]  12%  3/24 ESC0(0)
[09:06:24.354][DJIDeviceInfoEnumera]  16%  4/24 Gimbal303(0)
[09:06:24.357][DJIDeviceInfoEnumera]  20%  5/24 Battery0(0)
[09:06:24.363][DJIDeviceInfoEnumera]  25%  6/24 CPLD(3)
[09:06:24.375][DJIDeviceInfoEnumera]  29%  7/24 perception(only query version)(0)
[09:06:24.377][DJIDeviceInfoEnumera]  33%  8/24 tof(2)
[09:06:24.378][DJIDeviceInfoEnumera]  37%  9/24 FC(6)
[09:06:24.387][DJIWebFileGetter    ] [OnFinish]reply statusCode=200
[09:06:24.388][DJISoftUpdater      ] get check ok
[09:06:24.400][DJIDeviceInfoEnumera]  41% 10/24 eagle(1)
[09:06:24.401][DJIDeviceInfoEnumera]  45% 11/24 Camera LENS(4)
[09:06:24.463][DJIDynamicParamTable] book g_status_rc_current_urgent_mode_switch, but not exist
[09:06:24.464][DJIDynamicParamTable] book g_real_status_control_real_mode, but not exist
[09:06:24.478][DJIWebFileGetter    ] [OnFinish]reply statusCode=200
[09:06:24.478][DJISoftUpdater      ] get check ok
[09:06:24.485][DJIWebFileGetter    ] [OnFinish]reply statusCode=200
[09:06:24.485][DJISoftUpdater      ] get check ok
[09:06:24.487][DJIDynamicParamTable] book g_status_rc_current_urgent_mode_switch, but not exist
[09:06:24.489][DJIDynamicParamTable] book g_real_status_control_real_mode, but not exist
[09:06:24.512][DJIWebFileGetter    ] [OnFinish]reply statusCode=200
[09:06:24.512][DJISoftUpdater      ] get check ok
[09:06:24.650][DJIDeviceInfoEnumera]  50% 12/24 ESC1(1)
[09:06:24.963][DJIDeviceInfoEnumera]  54% 13/24 ESC2(2)
[09:06:25.260][DJIDeviceInfoEnumera]  58% 14/24 ESC3(3)
[09:06:26.349][DJIDeviceInfoEnumera] QueryDeviceVersion Timeout, Fail Dev: FC_Loader(3:5)
[09:06:26.349][DJIDeviceInfoEnumera]  62% 15/24 FC_Loader(5)
[09:06:26.349][DJIDeviceInfoEnumera] QueryDeviceVersion Timeout, Fail Dev: ADS-B(8:6)
[09:06:26.350][DJIDeviceInfoEnumera]  66% 16/24 ADS-B(6)
[09:06:26.350][DJIDeviceInfoEnumera] QueryDeviceVersion Timeout, Fail Dev: 1860(9:1)
[09:06:26.350][DJIDeviceInfoEnumera]  70% 17/24 1860(1)
[09:06:26.350][DJIDeviceInfoEnumera] QueryDeviceVersion Timeout, Fail Dev: NFZ(9:5)
[09:06:26.350][DJIDeviceInfoEnumera]  75% 18/24 NFZ(5)
[09:06:26.350][DJIDeviceInfoEnumera] QueryDeviceVersion Timeout, Fail Dev: navigation(only query version)(17:7)
[09:06:26.350][DJIDeviceInfoEnumera]  79% 19/24 navigation(only query version)(7)
[09:06:26.380][DJIDeviceInfoEnumera] QueryDeviceVersion Timeout, Fail Dev: Camera4K_Loader(1:1)
[09:06:26.380][DJIDeviceInfoEnumera]  83% 20/24 Camera4K_Loader(1)
[09:06:26.380][DJIDeviceInfoEnumera] QueryDeviceVersion Timeout, Fail Dev: eagle(internal)(8:5)
[09:06:26.381][DJIDeviceInfoEnumera]  87% 21/24 eagle(internal)(5)
[09:06:26.381][DJIDeviceInfoEnumera] QueryDeviceVersion Timeout, Fail Dev: CP(9:7)
[09:06:26.381][DJIDeviceInfoEnumera]  91% 22/24 CP(7)
[09:06:26.381][DJIDeviceInfoEnumera] QueryDeviceVersion Timeout, Fail Dev: AirSense MCU(31:1)
[09:06:26.381][DJIDeviceInfoEnumera]  95% 23/24 AirSense MCU(1)
[09:06:26.381][DJIDeviceInfoEnumera] QueryDeviceVersion Timeout, Fail Dev: AirSense CPLD(31:4)
[09:06:26.381][DJIDeviceInfoEnumera] 100% 24/24 AirSense CPLD(4)
[09:06:26.381][DJIDeviceInfoEnumera] eagle          (8 :1) Ldr : 10.00.10.04 App : 10.00.10.04   WM240 AC Ver.A
[09:06:26.382][DJIDeviceInfoEnumera] FC_Loader      (3 :5) device no reply, request timeout!  
[09:06:26.382][DJIDeviceInfoEnumera] FC             (3 :6) Ldr : 00.00.00.00 App : 03.04.00.52  wm220 163CGB9R0A4RSX
[09:06:26.382][DJIDeviceInfoEnumera] Battery0       (11:0) Ldr : 00.00.00.01 App : 02.74.07.12   BA01WM240BAT
[09:06:26.382][DJIDeviceInfoEnumera] ESC0           (12:0) Ldr : 01.00.00.41 App : 01.01.00.72   WM240_ESC_V7
[09:06:26.382][DJIDeviceInfoEnumera] ESC1           (12:1) Ldr : 01.00.00.41 App : 01.01.00.72   WM240_ESC_V7
[09:06:26.382][DJIDeviceInfoEnumera] ESC2           (12:2) Ldr : 01.00.00.41 App : 01.01.00.72   WM240_ESC_V7
[09:06:26.382][DJIDeviceInfoEnumera] ESC3           (12:3) Ldr : 01.00.00.41 App : 01.01.00.72   WM240_ESC_V7
[09:06:26.382][DJIDeviceInfoEnumera] CPLD           (18:3) Ldr : 00.00.00.00 App : 00.00.03.05   DJI CPLD
[09:06:26.382][DJIDeviceInfoEnumera] ADS-B          (8 :6) device no reply, request timeout!  
[09:06:26.382][DJIDeviceInfoEnumera] Gimbal303      (4 :0) Ldr : 00.01.00.16 App : 00.01.10.78   GB11
[09:06:26.382][DJIDeviceInfoEnumera] 1860           (9 :1) device no reply, request timeout!  
[09:06:26.382][DJIDeviceInfoEnumera] NFZ            (9 :5) device no reply, request timeout!  
[09:06:26.383][DJIDeviceInfoEnumera] Mvo            (17:5) Ldr : 00.02.12.01 App : 00.02.12.01   wm240
[09:06:26.383][DJIDeviceInfoEnumera] navigation(only query version)(17:7) device no reply, request timeout!  
[09:06:26.383][DJIDeviceInfoEnumera] Camera4K       (1 :0) Ldr : 00.00.00.01 App : 00.10.00.04   WM240
[09:06:26.383][DJIDeviceInfoEnumera] Camera4K_Loader(1 :1) device no reply, request timeout!  
[09:06:26.383][DJIDeviceInfoEnumera] Camera LENS    (1 :4) Ldr : 00.00.00.01 App : 00.09.00.02   LN01
[09:06:26.383][DJIDeviceInfoEnumera] eagle(internal)(8 :5) device no reply, request timeout!  
[09:06:26.383][DJIDeviceInfoEnumera] CP             (9 :7) device no reply, request timeout!  
[09:06:26.383][DJIDeviceInfoEnumera] perception(only query version)(18:0) Ldr : 00.00.00.00 App : 01.06.05.01   
[09:06:26.383][DJIDeviceInfoEnumera] AirSense MCU   (31:1) device no reply, request timeout!  
[09:06:26.383][DJIDeviceInfoEnumera] AirSense CPLD  (31:4) device no reply, request timeout!  
[09:06:26.383][DJIDeviceInfoEnumera] tof            (18:2) Ldr : 01.00.00.02 App : 01.00.00.14   WM240_TOF_v2
[09:06:26.441][DJIFirmPackListRefre] Release Product: 1
[09:06:27.694][DJIWebFileGetter    ] [OnFinish]reply statusCode=200
[09:06:27.864][DJIWebFileGetter    ] [OnFinish]reply statusCode=302
[09:06:29.101][DJIWebFileGetter    ] [OnFinish]reply statusCode=200
[09:06:29.252][DJIWebFileGetter    ] [OnFinish]reply statusCode=302
[09:06:29.264][DJIWebFileGetter    ] [OnFinish]reply statusCode=200
[09:06:29.416][DJIWebFileGetter    ] [OnFinish]reply statusCode=302
[09:06:29.430][DJIWebFileGetter    ] [OnFinish]reply statusCode=200
[09:06:29.432][DJIFirmPackListRefre] Camera LENS(1:4) Cur: 00.09.00.02, Dst: 00.09.00.99

I try 510, 400, 300 version in DJI Assistant 2, but error 0x02e904 in 75% is always. I try reinstall Assistant application, try in both my Mac and Windows PCs - but error 0x02e904 in 75% is always

Can you help me? I purchased drone from a TaoBao DJI authorized seller through my sister, when she lived in China Mainland, but we in Russia, now. Russian service center calculated $500 for repair my drone and service center do not have this spare part now, it is not known when it will be available