You have no items in your shopping cart.
Monday, June 23, 2025 9:16:04 PM

Firmware flashing stuck at 62%

6 years ago
#1046 Quote
Will wrote:
After downgrading to v01.00.0200 using Assistant 2, the bird would not downgrade to
v01.00.0100 using NLD. But I was able to downgrade to v01.00.0000 and apply the NFZ patch. After that, the bird would not link to the RC. The LED next to the link button flashes red very slowly. Pressing the link button or holding the link button doesn't do any good.

I was able to use Assistant 2 to successfully flash v01.00.0200, v01.00.0300, and v01.00.0400 but the bird still won't link. I'm focusing on the slowely flashing link LED next the link button behind the little rubber tab on the right side of the bird.

Does anyone know what that means?


Hmm there is a small chance its not software related, see following vid:
https://www.youtube.com/watch?v=Sh2gXA0OuL0
0
6 years ago
#1050 Quote
I am using Win10 64bit via VM.

The linking problem between drone and controller should be fixable by connecting the supplied USB between them?
0
6 years ago
#1052 Quote
Will wrote:
After downgrading to v01.00.0200 using Assistant 2, the bird would not downgrade to
v01.00.0100 using NLD. But I was able to downgrade to v01.00.0000 and apply the NFZ patch. After that, the bird would not link to the RC. The LED next to the link button flashes red very slowly. Pressing the link button or holding the link button doesn't do any good.

I was able to use Assistant 2 to successfully flash v01.00.0200, v01.00.0300, and v01.00.0400 but the bird still won't link. I'm focusing on the slowely flashing link LED next the link button behind the little rubber tab on the right side of the bird.

Does anyone know what that means?



Dont send it to DJI just use it for parts im going to save up for another drone sorry it happened  to you  too Im going to make lots on videos on why NOT to use NLD if they  cant find a fix ...... I hope they find one
0
6 years ago
#1053 Quote
Jacek wrote:
Hmm there is a small chance its not software related, see following vid:
https://www.youtube.com/watch?v=Sh2gXA0OuL0


I've actually seen this video prior to ever pushing that button so personally I've been cautious.  I believe the light on my M2 has been flashing ever since the beginning of my firmware upgrade issues and prior to me ever physically touching the button.

At least in my case the video you're referring to is not the cause.  Thank you for pointing this out though.
0
6 years ago
#1054 Quote
Jesse wrote:
Hmm there is a small chance its not software related, see following vid:
https://www.youtube.com/watch?v=Sh2gXA0OuL0

I've actually seen this video prior to ever pushing that button so personally I've been cautious.  I believe the light on my M2 has been flashing ever since the beginning of my firmware upgrade issues and prior to me ever physically touching the button.

At least in my case the video you're referring to is not the cause.  Thank you for pointing this out though.


ya that guy used a f-ing pin to push the Sync button..... stupid
0
6 years ago
#1055 Quote
Scott wrote:
I am using Win10 64bit via VM.

The linking problem between drone and controller should be fixable by connecting the supplied USB between them?


I was hopeful of this but have not had any luck.  I've connected and powered on in different orders but connecting the two via usb cable has not had any effect on either.   Let us know if you have a different experience.

I'm curious how many people have been affected by this glitch.  I'm assuming just a few as you'd think they'd post a warning or take M2/ NLD offline until they had a fix.  
0
6 years ago
#1056 Quote
Jacek wrote:


Hmm there is a small chance its not software related, see following vid:
https://www.youtube.com/watch?v=Sh2gXA0OuL0


I can verify that at least for me, the switch is not the problem. I had pushed it many times with my fingernail, so I opened it up to make sure....
0
6 years ago
#1058 Quote
Jesse wrote:
I am using Win10 64bit via VM.

The linking problem between drone and controller should be fixable by connecting the supplied USB between them?

I was hopeful of this but have not had any luck.  I've connected and powered on in different orders but connecting the two via usb cable has not had any effect on either.   Let us know if you have a different experience.

I'm curious how many people have been affected by this glitch.  I'm assuming just a few as you'd think they'd post a warning or take M2/ NLD offline until they had a fix.  



yes  take it down b4 you F up any more peoples drones...... if they dont there just taking peoples money and selling something they KNOW will F up drones
0
6 years ago
#1059 Quote
Scott wrote:
Hey guys I had some struggles to get my M2P downgraded and patching applied. My final workaround was this;

v1.9.0.1 NLD

Upgrade M2P via DJI Assistant 2 to v01.00.0400



Not having any luck using the current Assistant 2 to upgrade to .0400.  It fails at 75% and gives the error message "undefined 0x02e904"

Windows 10 x64 and opening all programs as administrator.
0
6 years ago
#1060 Quote
Quad808 wrote:
Not sure if this will fix this issue or not...we are testing this and trying to duplicate this issue.

NLD firmware flashing...completely rewritten.  If the firmware flashing gets "stuck" leave NLD alone and restart the bird.  Upon re connection, NLD will continue flashing the firmware.

Try this:
connect up the bird to NLD.
Run the NFZ patch again.  Ok if it fails.
Flash the same version of firmware.  See above if it gets "stuck"
Turn on the RC for this procedure and leave it on.

Also, when posting here, give us your OS version.


Quad808, I tried all you mentioned several days ago before I posted this to no avail.
Using Win 10 64bit (no connection problems)
Please note something, this specific problem is not random:

Jesse commented the following on this thread "I've spent the last 36 hours in a panic trying to upgrade/downgrade/refresh the firmware and can not get past 75%.  For me it hangs at "Flashing cp to 34.96.02.03" which starts at 62% and never gets past 75%." Using assistant 2 he gets "undefined 0x02e904" error.

I am having the same problem and the system hangs for me at the same exact point showing the same exact message; hangs at 75% and shows "Flashing cp to 34.96.02.03" and when using assistant 2 I also get the "undefined 0x02e904" error message.

Mathematically speaking this is not a coincidence, something in the NFZ patch, after it is applied, is causing this in firmware 1.00.0000 (also resulting in the rc not able to link to the bird)
I am still gathering collective information from other folks to see is the same thing(stuck firmware) is happening with 1.00.0100
What I have seen so far only 0000 is "getting stuck"

We should all be at 1.00.0100 but the NFZ patch is not working so logically everyone is downgrading to the next allowable version to see if it works, and getting stuck.

As other's throughout the forum suggested I also highly suggest removing 1.00.0000 (possibly the old 0.00.0600 also) from Client 1.9.0.1 so more folks don't get stuck and their bird completely grounded.
And of course, look to resolve the main problem; why is the NFZ patch is not working on so many M2's!!!!!!!!

1