I just did a flight test and the weird crap I had with 2.5.0 seems to have been fixed by rolling back. I was having all kinds of video signal issues that literally locked the app so hard I had to reboot the app while the bird was flying to get video back. I really think that 2.5.0 firmware is meant for the NEXT app release which is why we've been having issues. Version 1.1.6.6 of the android app was built for the 2.3.3 of the firmware which is where I went back too and just had 0 issues. Only thing I saw was my precision landing wasn't so precise but I turned APAS after take off so maybe turning the sensors off messed up the landing but it was in the neighborhood, a few feet not miles off. I had no weird altitude readings where it was off by 20+ feet with 2.5.0. But only one test so we'll see but far, far better off atm.Guys...the file from DH FORCES the drone to flash all components firmware to the version in the firmware that is on the SD card. The Autel firmware is just like DJI firmware, meaning...there is an overall firmware # like 2.5.0, but that firmware is made up of several firmware components for each separate hardware piece, so when doing this make sure to match the versions from the app to what was in the firmware release notes.
I wouldn't anticipate any issues going to earlier firmware, especially just one version earlier, UNLESS you had existing issues on that firmware. Those issues you had on that firmware would still be present.
As skipper1 says...this is not rocket science.
It is a good idea to do calibrations again though, then test fly. As long as you get the message from the RC that the flash was a success, you should be good to go after you validate the versions in the app.
If you are getting the screen as in post #22...this means that your SD card is not setup correctly with the drone-hacks file, because the drone is doing a firmware check and not reading the extra file from DH that tells the drone to not check the versions, but flash the firmware on the card.
**The biggest question is....has anyone who had drift issues on 2.5.0, rolled back the firmware to 2.3.3 and now those issues are gone? I have NOT had the time to test my drone, but hope to later today, weather permitting.
Are you sure it actually downgraded? Since you can't actually see a primary firmware number you have to go by the sub component firmware numbers to see it any of them actually rolled back.
With out this hack you can load the old 2.3.3 bin file on a card and do the update successfully but it has not actually rolled back any of the sub components. One has to check the sub to see!
I wasn't talking about the Evo.
BTW The firmware downgrade was a success. Very happy to have gotten out of 1.5.8.
In the case of the Evo II, the firmware 2.5.0 has given many problems to many pilots. Use the search option to get up to date with the various threads that talk about this.i'm planning on getting the 6K evo 2 and just saw this thread.. why is everyone downgrading and to which version is everyone downgrading to? what were the problems? i'm very hesitant at getting another autel drone after my first mishap, but the only reason i won't get a Mavic 2 pro is because of the restrictions it has built in.
i'm planning on getting the 6K evo 2 and just saw this thread.. why is everyone downgrading and to which version is everyone downgrading to? what were the problems? i'm very hesitant at getting another autel drone after my first mishap, but the only reason i won't get a Mavic 2 pro is because of the restrictions it has built in.
Version 2.3.3 with app version 1.1.6.6 is rock solid stable. That is the version that I'm posting my results on. Those versions are really stable, at least for me.i'm planning on getting the 6K evo 2 and just saw this thread.. why is everyone downgrading and to which version is everyone downgrading to? what were the problems? i'm very hesitant at getting another autel drone after my first mishap, but the only reason i won't get a Mavic 2 pro is because of the restrictions it has built in.
I understand it's part of your name, but you shouldn't skip steps if you want to achieve your goal.Holly Moly, finally found force_upgrade. Upgrade was successful. I can’t believe it, finally!
I Am so happy I finally got the upgrade in. Now to do all the calibrations and go fly, unfortunately we have rain moving in in the next 24hr.I understand it's part of your name, but you shouldn't skip steps if you want to achieve your goal.
Holly Moly, finally found force_upgrade. Upgrade was successful. I can’t believe it, finally!
I know, I know. I embarrassed to even admit it. Have fun making fun of me, I should be able to handle it.'bout time you got it right!![]()
I know, I know. I embarrassed to even admit it. Have fun making fun of me, I should be able to handle it.
So how does it fly now?
[/QUOTE
I haven’t flown it yet and may not be able to until the weekend. We have rain moving in this afternoon and will hang around until the weekend.
We use essential cookies to make this site work, and optional cookies to enhance your experience.