I successfully updated the Inspire 1, first remote and three batteries. I deleted the success TXT file on the USB and put the drive into the second remote. The process started just like the other but it never stopped beeping and the blue light stayed on. I eventually turned it off but now it will not restart. I have searched this forum for solutions from the last update and I have reformated the drive, reformated as EXFAT, tried an update from the card in the gimbal but it not longer seems to be in the mood to update. I would appreciate any ideas or help. As I never had any problems with my Inspire to date I rather regret the update.

Fully Established

My concern as well... I am yet to upgrade firmware. I feel your pain... please keep us posted... hopefully Support or someone here might offer some solution..

Spent an hour with online support. They gave up and asked me to write to US support. It is somewhat baffling how the same file can work so well on one remote and fail so completely on the other and leave no way back.

A number of people have mentioned that they had to try different USB sticks before they got it going. Did you try that option?

That is a great suggestion and I have tried and failed. I also formatted on a PC and a MAC. On boot up now I get two long beeps even with the USB drive in. It seems to be in a corrupt state and will not even see the update file.

Im keeping my wifi turned off on all my devices for a little while while I see the outcome of everybodies firmware updates and initial flights.  No Wifi, no chance of being forced to update.  

This was not a forced update, I am a victim of my own actions.

fullyestablishe Posted at 2015-4-16 02:45
That is a great suggestion and I have tried and failed. I also formatted on a PC and a MAC. On boot  ...

The only other thing I saw mentioned is that people are deleting the txt file after each device upgrade, and also made sure that the firmware file is the only one on the drive. I updated by second remote this morning without problem, but I noticed that it paused a couple of times during.  May not mean anything.

I really appreciate your help; I did do that as it is in the instructions for the second controller. I believe without doing it the controller would see the success file and stop. Your messages have helped me pass the time as I move up the phone queue at DJI.

Been there, done that, ugh.   Watch the Hitler video a few times for some cheering up….

Just finished updating both my I1's, 3 remotes and two batteries. I had to connect the remote to the camera to get it to upgrade. Checked all systems on both birds and all 3 remotes and everything works great! No problems or issues with mine. I did take the SD card out each time, check the txt file for "Success" then deleted the txt files to start the next upgrade.

Sorry to hear your's isn't working. Both birds took about 10-15 min. to update and all three remotes took about 5-10 min. to update.

Seems like déjà vu with the last firmware upgrade. By the way, it seemed unnecessarily cruel to plug the cable into the gimbal whilst it was on, it was not at all happy.

@fullyestablished

What color is the indicator?
If white, use the OF_BIN file floating around.

Worked for me...

call DJI SUPPORT they helped me last time when I was trying g to update my 2nd controller they sent me a different zip file and it fixed the problems and it updated the controller

tim.warth@gmail Posted at 2015-4-16 04:12
@fullyestablished

What color is the indicator?

No actually it is purple. DJI support were super helpful and sent me the ofd.bin file to wipe off the corrupt version and start again. Sadly that did not work. It just starts up with two long baleful beeps and sits there. On the bright side, it is a rather splendid shade of purple.

joekeantang@gma Posted at 2015-4-16 04:39
call DJI SUPPORT they helped me last time when I was trying g to update my 2nd controller they sent  ...

They were really helpful but the bin file that they sent made no difference.

Wow sorry to hear that so are they making you a ticket and sending it to get repair?

I am waiting for Thomas to reply to my email, he asked me to if there was a problem. That, however, was several hours ago. I really don't want to go through the telephone queue again. Thomas could not have been more sympathetic or helpful.

I had the same problem with my 2nd controller.  Everything else updated with no problems.  Mine controller didn't brick, just long beep and red error light after attempted updates.  I also had DJI Tech Support trying to get it working including using the gs_ofdm.bin file - no luck.  I just bought the controller (hadn't even used it yet).  DJI said it's likely defective and to send it back to the dealer for replacement.  If anyone finds a solution please keep us posted.

established, I had exactly the same issue last software update.

Many hours with online support to fix. My 2nd controller would not update via usb stick, eventually updated by connecting directly to camera. Deleted the HIDDEN txt file that was on the sd card first though. Update worked after this.

What a wonderful process this is!

Wolfman Posted at 2015-4-16 09:27
established, I had exactly the same issue last software update.

Many hours with online support to  ...

My heart skipped when I read about the hidden txt file, perhaps that was stopping the upgrade on the reluctant  remote. I tried the technique but it did not work. I did get the following log file back

[00010279]========== 2014.01.01 00:00:10 unsynchronized ======
[00010299]Packet [C:\WM610_FW_V01.02.01.00.bin] detected.
[00010307]Packet upgrade start...

[00010321]Packet checking...
[00010332]Done.

[00010339]Version checking[1]...
[00010346][01 00] v1.7.2499 -> v1.7.2499
[00010354][01 01] v1.7.2499 -> v1.7.2499
[00010399][03 05] v34.1.0.5 -> v34.1.0.5
[00010434][03 06] v2.0.5.10 -> v2.0.5.10
[00010448][04 00] v1.16.0.76 -> v1.16.0.76
[00010473][05 00] v2.5.6.1 -> v2.5.6.1
[00010489][08 00] v1.11.0.19 -> v1.11.0.19
[00010509][09 00] v1.7.0.3 -> v1.7.0.3
[00010534][11 00] v3.2.1.0 -> v3.2.1.0
[00010595][12 00] v1.3.0.60 -> v1.3.0.60
[00010653][12 01] v1.3.0.60 -> v1.3.0.60
[00010713][12 02] v1.3.0.60 -> v1.3.0.60
[00010773][12 03] v1.3.0.60 -> v1.3.0.60
[00010846][15 00] v1.1.2.0 -> v1.1.2.0
[00010873][17 00] v1.1.0.1 -> v1.1.0.1
[00010933][17 01] v2.0.0.1 -> v2.0.0.1
[00010949][19 00] v1.0.8.59 -> v1.0.8.59
[00010956]Packet upgrade cancelled at version checking.

and I am guessing it is showing that everything it can see is on the right version so cancelled the update. I would guess that it could not see the controller and there will be no entry for that.

I have been working on this for 14 hours, it now flies badly, will not hold altitude and its sensor values keep going awry; I currently have a mod of 1100, its Z is out so no wonder it drifts up and down 3 metres. Today I brought it back to me starting at 2.5m and when I stopped it it drifted down, to half a metre, to 10cm, 2cm  and touched down with the rotors still running just bobbing into the grass. How could the sonar and flow sensor not put a stop to it. I had 57 perfect flights before the upgrade and now it is a real handful.