Yup, i've been in 1000 for a week, then i downgrade to 900. Maybe i'll stick around 900 'til next update
Hi were you on 1000 first version released on 8-22 or 1000 second version released on 8-25? Thanks.
Yup, i've been in 1000 for a week, then i downgrade to 900. Maybe i'll stick around 900 'til next update
cool. since you tried DZB 0.7 , I suggest you to download latest DronezBreak v.0.8 since it's released by dev just now. it has unlock features if your drone forced to updateYup, i've been in 1000 for a week, then i downgrade to 900. Maybe i'll stick around 900 'til next update
Actually i've tried both, mate.. LOLHi were you on 1000 first version released on 8-22 or 1000 second version released on 8-25? Thanks.
Thank you for reply. I was asking because in other thread there was mentioned that 2nd version have rollback protection so therefore I was curious if there is possibility to rollback also 2nd version. Thanks for confirmation. DavidActually i've tried both, mate.. LOL
I thought there were a difference between that 2 firmware, but the fact i thought that they're the same. IMO
cool. since you tried DZB 0.7 , I suggest you to download latest DronezBreak v.0.8 since it's released by dev just now. it has unlock features if your drone forced to update
DroneZBreak by mavicBreak
==================================================
GitHub - mavicBreak/DroneZBreak: Change DJI drones flight controller parameters and flash firmwares natively on OSX
[v0.8 changelog 03.SEP.2017]
———————————————————————————-
+ Unlock option if drone is locked and forced to FW upgrade thx to kilrah
+ stability fixes
cheers
You're welcome mate. Actually, like i said earlier, i'm not using my mavic to fly more that 2 km or push it to the limit or maybe fly higher (in my country Indonesia, it has 150 m limit to fly a drone) or higher speed. Nope, i use my drone to make an aerial photos. It's a new experience for me and the .900 firmware fit what i need. Not to mention that .1000 is a bad firmware, i just don't like its exposure default setting, it's too over exposed though the saturation is nice. But i rather have a little bit under exposed photos than over exposed so that i can keep a little detail on my photos.
Nice to meet you anyway, David.
- Agung -
I think I've done everything correctly but I can't DUMLdore to run enough to show the user interface.
1) Run DJI Assistant 2 first to verify the connection to the Mavic
2) right-click DUMLdore.exe and run as administrator get one of these
View attachment 21109
The contents of of the window:
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: dumldore.exe
Problem Signature 02: 1.88.0.0
Problem Signature 03: 59a5199d
Problem Signature 04: DUMLdore
Problem Signature 05: 1.88.0.0
Problem Signature 06: 59a5199d
Problem Signature 07: 5
Problem Signature 08: bd
Problem Signature 09: System.NullReferenceException
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
I'm running Windows 7. Just downloaded/installed DUMLdore as explained in the YouTube in post #1
Anybody have this problem and/or know how to fix this?
Right click on the dumldore tool and chose properties click compatibility and change to windows 7 compatible click okay. Disable your antivirus or firewall and try again. If no go wr can get the the log and examine
Forgot to mention that I had already set the compatibility.Perhaps you need to set compatibility first? You can read at first page post #10
Forgot to mention that I had already set the compatibility.
Thanks @digdat0 . I know the routine with inconsistent FW found with batteries. And thanks for your genius support on keeping us flying with freedom.No need to use dumldore, just put battery in and when itnsays inconsistent firmware update it, that only does battery
Thanks. I managed to get this to work by using a different PC. The PC that I was using for this has had so many things installed and uninstalled that it's hard to tell where the problem could have been. Your comment about repairing/reinstalling .net was the catalyst I needed to try a different PC.Have you installed .net framework? If you do, try repair .net framework or reinstall and try it again.
Thanks. I managed to get this to work by using a different PC. The PC that I was using for this has had so many things installed and uninstalled that it's hard to tell where the problem could have been. Your comment about repairing/reinstalling .net was the catalyst I needed to try a different PC.
Just got done doing .700 which completed without a problem. @digdat0 's video in post #1 says that the Assistant may not show the updating complete when it actually has completed. This can be determined by turning on the RC and, if it connects, then the updating is complete. Have a look at the video to make sure I've got it right.Are there any tips or solutions to issues around update hangs?
I was able to downgrade to 400 no probs, now I'm trying to flash 700 - the image gets sent to the AC, and in assistant I can see progress...but it seems to hang / f'up at around 60 percent.
How did it work with 400, and not 700?
Is it a case of repeatedly trying?
It gives an error at 60 percent though. AC still on 400.Just got done doing .700 which completed without a problem. @digdat0 's video in post #1 says that the Assistant may not show the updating complete when it actually has completed. This can be determined by turning on the RC and, if it connects, then the updating is complete. Have a look at the video to make sure I've got it right.
We use essential cookies to make this site work, and optional cookies to enhance your experience.