You have no items in your shopping cart.
Monday, June 23, 2025 6:10:03 PM

Firmware flashing stuck at 62%

6 years ago
#1313 Quote
Hey there, still sitting on very first 01.00.0000 as of september 2018. what is safest method to upgrade to .0100 to be able for patching sweeties to my bird?
thanks!
0
6 years ago
#1328 Quote
Just got my M2 back from DJI and like most folks here they replaced it with a new bird. It came with the 0.00.0000 firmware.

Whatever you do, do not apply the NLD NFZ patch to the 0.00.0000 or 1.00.0000 (don't mess with anything ending in 4 zeros)

Flash it first to the 1.00.0100 which is the version that it suppose to work with the NFZ patch.

As soon as NLD gets my license key activated for my new bird I'm going to try to apply the nfz patch again and see if it works.
1
6 years ago
#1392 Quote
In the email they sent me it said that they replaced the "core board" and in doing so, the serial number would change. It also showed a different serial for the camera. The camera should not change with a new core board.
Got my bird back today and like everyone else its a new bird (in my old box) and not the one I sent in. I will have to check out the camera as that is the only thing that worries me. I had a good camera on mine and some folks have had bad cameras.
1
6 years ago
#1735 Quote
I received my bird back from dji yesterday (haven't had time to test it) but it was a brand new bird, new serial, new cam...Hoping like others it doesnt mess up my hasselblad b/c I loved my cam on my first mp2
0
6 years ago
#1822 Quote
Finally the NFZ patch for my M2 worked!

Received the bird with v0.00.0000, flashed it successfully to .0100 using DOMLdore v3.2 flashing tool and applied the NFZ patch via the new Mod Client 1.9.1.0
I did not know there was a 0.00.0000 and a 1.00.0000. Seems 0.00.0000 is not recognized or documented.

Under the forum folder, Mavic 2 Pro --> and a post I title "Can someone please confirm that the NFZ patch worked on the Mavic 2?" Page 2, Post #1809 by Gregory (me) I explain exactly the how I got the NFZ patch to work. These sequence of events might help someone.
0
6 years ago
#1986 Quote
Brett wrote:
In the email they sent me it said that they replaced the "core board" and in doing so, the serial number would change. It also showed a different serial for the camera. The camera should not change with a new core board.
Got my bird back today and like everyone else its a new bird (in my old box) and not the one I sent in. I will have to check out the camera as that is the only thing that worries me. I had a good camera on mine and some folks have had bad cameras.


Camera seems ok.

New bird came with the .0000 firmware version.
I used DJI Assistant 2 to upgrade to version .0200.
Then used NLD app to downgrade to version .0100.
Used NLD app to apply NFZ removal.
Started the props inside my house for the first time in over half a year (house is in NFZ although it wasn't when I originally bought the M2P).

Now at least I feel confident that when I show up on a job with a wavier, I don't have to worry that the DJI app will not accept the code. Heard too many nightmares of that happening.
0
5 years ago
#4093 Quote
Hi!
I bought a drone with .0100 software initially, then purchased a key and tried to apply NFZ mode in app.. it failed multiple times.
Seeing, that's a common problem I've tried to update thru DJI assistant to .0300 version. With some manipulation it showed me that I upgraded succesfully (not having the 62-75% stucks as other had) but still I can not bind my RC to the bird.
Then I installed .0400 (in DJI GO 4 official app ) ONLY on RC with hope that it can rescue the situation, but noway...
That means my drone is dead?
thanks
0
5 years ago
#4164 Quote
Sounds like a DOA drone straight from DJI, this was a common bug in the first 6 months of the MP2 line.

That said, i dont know why you upgraded to 0300!
0