People that want to downgrade their FW on their phantom 3's

[ferraript]

Thank you for usefull information. I wander if those older versions of Litchi would work with 1.7.60 with same result regarding sending flight parameters.

if you have FW 1.7.60 with customized flight parameters, I can't see any reason why would you need older versions of Litchi

 

[ferraript]

today I did another high-altitude test
this time I really tried to have AC in position, where distance was at least two times larger than height
result is, my P3A flawlessly got to 1208 m height, distance was 2900 m (that means angle was 22.6°)
it took 5 minutes to get there, battery was at 70 % up there
AC comfortably landed with 27 % remaining (I saw that there was enough power to get back, so I didn't rush it - if I had flown straight to homepoint, I would have landed with 40 %)

who needs Mavic if there is this amazing machine?

 

[flyNfrank]

today we had nice weather so I could finally test my downgraded P3A (AC at 1.4.10 with RC at 1.4.30)
I calibrated the compass, I haven't done it for a long time
flight was ok, I didn't have the issue you had described
when I rotated AC to specific direction and pushed elevator stick, bird flew exactly to that direction, no "drifting" at all
thanks to Litchi I also finally broke that 500 m height barrier, AC flew up to 636 m, then I lost connection completely (distance was only 530 m and so angle was larger than 45° - not optimal conditions for signal at all)
next time I will try these high-altitude flights with larger distance

Setting personal height records can be very addictive! I use to do that and stopped right before taking delivery of the P3 when it 1st came out in May 2015. Using a 100% totally stock P2V+ I made it up to 4600ft or 1402m. I lost 2 drones doing that hobby. I know things I experience wouldn't happen now because the technology in the new drones are way better then they were back then.

 

[Paul A Byers]

Sounds like an awful lot of crap just to fly a drone. Starting to get disillusioned with all of this. Rant.

Sorry

 

[FredzMaxxUAV]

if you have FW 1.7.60 with customized flight parameters, I can't see any reason why would you need older versions of Litchi

What are customized flight parameters exactly?

 

[FredzMaxxUAV]

Do these methods work no matter what motors you have (old or new)? I think there were never Phantoms with new motors with FW 1.1.9 and even 1.3.2 (not sure about that one). Would downgrading a bird with new motors still work fine with FW 1.1.9 or 1.3.2?

 

[Varming]

In my P3P log (downgradet fra 1.10 to 1.9 I see this:

[00012805]Packet [C:\P3X_FW_V01.09.0060.bin] detected, card sn [0xdcdf2bd3].
[00012883]Packet upgrade start...

[00012958]Packet checking...
[00013036]Packet vlink 01.09.0060 <-> 01.08.0080.
[00013112]Record vlink 01.09.0060 <-> 01.08.0080 (flow = 0).
[00013189]Done.

[00013268]Version checking[1]...
[00013371][03 05][00] v34.2.0.9 -> v34.2.0.9
[00013491][03 06][00] v2.4.20.18 -> v2.4.20.18
[00013573][04 00][00] v1.44.0.0 -> v1.44.0.0
[00013731][11 00][00] v1.8.0.0 -> v1.8.0.0
[00013891][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[00013960][11 01][00] v1.8.0.0 -> v2.0.0.33
[00014105][12 00][00] v1.10.0.0 -> v1.10.0.0
[00014219][12 01][00] v1.10.0.0 -> v1.10.0.0
[00014371][12 02][00] v1.10.0.0 -> v1.10.0.0
[00014505][12 03][00] v1.10.0.0 -> v1.10.0.0
[00014675][15 00][00] v1.1.2.0 -> v1.1.2.0
[00014800][17 00][00] v1.1.1.7 -> v1.1.1.7
[00014961][17 01][00] v1.0.2.7 -> v1.0.2.7
[00015075][19 00][00] v1.0.8.96 -> v1.0.8.96
[00015149][01 00][00] v1.30.5036 -> v1.30.5036
[00015229][01 01][00] v1.30.5036 -> v1.30.5036
[00015325][08 00][00] v0.13.0.7 -> v0.13.0.7
[00015415][09 00][00] v3.0.0.10 -> v3.0.0.10
[00015495]Packet upgrade cancelled at version checking.


I'm curious: What is this line about:
00013891][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.

Everything seems to work fine so it's just curiousity (and I've already tried to Google it)

 

[neven]

1.10.90 to 1.7.60 with no problems. I was bit reluctant because my P3P had that odd 255.255.255.254 version for module 1900 but everything went fine. 1.8.80 to 1.7.60 with debug took bit over 30 minutes so be patient. Also put your drone outside on a balcony (unless you are in Australia right now) when doing FW flashing because it gets pretty hot.
I also downgraded my RC (GL300C) to 1.5.8 from 1.8.0 using the graduation hat method with DJI Go 3.1.3. I tried 1.5.8 directly from 1.8.0 but it failed so i did 1.8.0 -> 1.6.0 -> 1.5.8.

 

[Apilot101]

What are customized flight parameters exactly?

1.7 FW was released from DJI without being encrypted. There are a few guys here that are going into the FW and manipulating the max limits to get the P3 to do what they want. For example ...to change max pitch angle to make it fly faster. I don't know of any successful attempts to remove the height limit from 1.7 yet. Or NFZ yet. It's only a matter of time.

 

[Apilot101]

Do these methods work no matter what motors you have (old or new)? I think there were never Phantoms with new motors with FW 1.1.9 and even 1.3.2 (not sure about that one). Would downgrading a bird with new motors still work fine with FW 1.1.9 or 1.3.2?

Motors don't matter. My quad has new motors and took it step by step from 1.7 down to 1.1.9. Worked fine. I went back to 1.4 to use Litchi to get the most for now.

 

[Radol]

When i downgrade Phantom Advance with debug method from 01.09.0060 to 01.08.0080, i always get the "+" with 08.0080 and message "Camera update required".
Try to update for newest version then down ver-by-ver and have the same result.
What can i try else?

Picture from net

 

[ferraript]

When i downgrade Phantom Advance with debug method from 01.09.0060 to 01.08.0080, i always get the "+" with 08.0080 and message "Camera update required"....

post here the last few rows from P3S_FW_LOG_AB.txt file, just like Varming did four posts ago, so we can see firmware versions of the modules

 

[Radol]

post here the last few rows from P3S_FW_LOG_AB.txt file, just like Varming did four posts ago, so we can see firmware versions of the modules

[00021196]========== remo-con disconnect. boot(15) ============
[00021282]Packet [C:\P3S_FW_V01.08.0080.bin] detected, card sn [0x2c3379dd].
[00021360]Packet upgrade start...
[00022002]Packet checking...
[00022633]Packet vlink 01.08.0080 <-> 01.07.0060.
[00022783]Done.
[00022864]Version checking[1]...
[00022972][03 05][00] v34.2.0.9 -> v34.2.0.9 need upgrade.
[00023092][03 06][00] v2.4.14.5 -> v2.4.14.5 need upgrade.
[00023170][04 00][00] v1.44.0.0 -> v1.44.0.0 need upgrade.
[00023331][11 00][00] v2.0.0.33 -> v1.7.15.1, firmware v2.0.0.33 not support.
[00023409][11 00][00] v2.0.0.33 -> v1.7.15.1
[00023585][12 00][00] v1.10.0.0 -> v1.10.0.0 need upgrade.
[00023720][12 01][00] v1.10.0.0 -> v1.10.0.0 need upgrade.
[00023852][12 02][00] v1.10.0.0 -> v1.10.0.0 need upgrade.
[00024148][12 03][00] v1.10.0.0 -> v1.10.0.0 need upgrade.
[00024262][15 00][00] v1.1.2.0 -> v1.1.2.0 need upgrade.
[00024415][17 00][00] v1.1.1.7 -> v1.1.1.7 need upgrade.
[00024615][17 01][00] v1.0.2.7 -> v1.0.2.7 need upgrade.
[00024750][19 00][00] v255.255.255.254 -> v1.0.8.96
[00024861][01 00][00] v1.23.4920 -> v1.23.4920 need upgrade
[00024962][01 01][00] v1.23.4920 -> v1.23.4920 need upgrade
[00025111][09 00][00] v3.0.0.10 -> v3.0.0.10 need upgrade.
[00025223]Done.
[00027328]Waiting for user confirm...
[00037475]Timeout, start upgrade automatically.
[00037681]Firmware upgrading[1]...
[00052861][01 00] Firmware upgrade start...
[00012975][01 00] Firmware upgrade finished successfully.
[00013082]Done.
[00013195]Packet [C:\P3S_FW_V01.08.0080.bin] resumed, card sn [0x2c3379dd].
[00013316]Packet vlink 01.08.0080 <-> 01.07.0060.
[00013425]Version checking[2]...
[00013585][03 05][00] v34.2.0.9 -> v34.2.0.9 need upgrade.
[00013746][03 06][00] v2.4.14.5 -> v2.4.14.5 need upgrade.
[00013877][04 00][00] v1.44.0.0 -> v1.44.0.0 need upgrade.
[00014085][11 00][00] v2.0.0.33 -> v1.7.15.1, firmware v2.0.0.33 not support.
[00014195][11 00][00] v2.0.0.33 -> v1.7.15.1
[00014358][12 00][00] v1.10.0.0 -> v1.10.0.0 need upgrade.
[00014519][12 01][00] v1.10.0.0 -> v1.10.0.0 need upgrade.
[00014692][12 02][00] v1.10.0.0 -> v1.10.0.0 need upgrade.
[00014873][12 03][00] v1.10.0.0 -> v1.10.0.0 need upgrade.
[00014992][15 00][00] v1.1.2.0 -> v1.1.2.0 need upgrade.
[00015148][17 00][00] v1.1.1.7 -> v1.1.1.7 need upgrade.
[00015333][17 01][00] v1.0.2.7 -> v1.0.2.7 need upgrade.
[00015464][19 00][00] v255.255.255.254 -> v1.0.8.96
[00015571][01 00][05] v1.23.4920 -> v1.23.4920 need upgrade
[00015676][01 01][00] v1.23.4920 -> v1.23.4920 need upgrade
[00015884][09 00][00] v3.0.0.10 -> v3.0.0.10 need upgrade.
[00015998]Done.
[00016102]Firmware upgrading[2]...
[00016333][01 01] Firmware upgrade start...
[00046721][01 01] Firmware upgrade finished successfully.
[00047008][12 00] Firmware upgrade start...
[00108379][12 00] Firmware upgrade finished successfully.
[00108511][12 01] Firmware upgrade start...
[00168848][12 01] Firmware upgrade finished successfully.
[00168989][12 02] Firmware upgrade start...
[00230561][12 02] Firmware upgrade finished successfully.
[00230681][12 03] Firmware upgrade start...
[00289853][12 03] Firmware upgrade finished successfully.
[00289991][17 00] Firmware upgrade start...
[00367709][17 00] Firmware upgrade finished successfully.
[00367872][17 01] Firmware upgrade start...
[00425573][17 01] Firmware upgrade finished successfully.
[00425692][03 05] Firmware upgrade start...
[00497148][03 05] Firmware upgrade finished successfully.
[00497458][03 06] Firmware upgrade start...
[00831789][03 06] Firmware upgrade finished successfully.
[00831909][15 00] Firmware upgrade start...
[00868359][15 00] Firmware upgrade finished successfully.
[00868498][09 00] Firmware upgrade start...
[00920698][09 00] Firmware upgrade finished successfully.
[00920842][04 00] Firmware upgrade start...
[00979843][04 00] Firmware upgrade finished successfully.
[00979959]Done.
[00980068]Version checking[3]...
[00980223][03 05][05] v34.2.0.9 -> v34.2.0.9 need upgrade.
[00980381][03 06][05] v2.4.14.5 -> v2.4.14.5 need upgrade.
[00980503][04 00][05] v1.44.0.0 -> v1.44.0.0 need upgrade.
[00980701][11 00][00] v2.0.0.33 -> v1.7.15.1, firmware v2.0.0.33 not support.
[00980810][11 00][00] v2.0.0.33 -> v1.7.15.1
[00980994][12 00][05] v1.10.0.0 -> v1.10.0.0 need upgrade.
[00981150][12 01][05] v1.10.0.0 -> v1.10.0.0 need upgrade.
[00981309][12 02][05] v1.10.0.0 -> v1.10.0.0 need upgrade.
[00981495][12 03][05] v1.10.0.0 -> v1.10.0.0 need upgrade.
[00981608][15 00][05] v1.1.2.0 -> v1.1.2.0 need upgrade.
[00981776][17 00][05] v1.1.1.7 -> v1.1.1.7 need upgrade.
[00981970][17 01][05] v1.0.2.7 -> v1.0.2.7 need upgrade.
[00982105][19 00][00] v255.255.255.254 -> v1.0.8.96
[00982335][01 00][05] v1.23.4920 -> v1.23.4920 need upgrade
[00982439][01 01][05] v1.23.4920 -> v1.23.4920 need upgrade
[00982585][09 00][05] v3.0.0.10 -> v3.0.0.10 need upgrade.
[00982702]Packet upgrade finish successfully.

 

[quaddamage]

[00021282]Packet [C:\P3S_FW_V01.08.0080.bin] detected, card sn [0x2c3379dd].
[00021360]Packet upgrade start...
[00022002]Packet checking...
[00022633]Packet vlink 01.08.0080 <-> 01.07.0060.

That's a typical upgrade log. You upgraded 1.07.0060 to 1.08.0080.

[00980068]Version checking[3]...
[...]
[00980701][11 00][00] v2.0.0.33 -> v1.7.15.1, firmware v2.0.0.33 not support.

This means battery has newer firmware and was not upgraded. This is why you see the "+".

[00982105][19 00][00] v255.255.255.254 -> v1.0.8.96

This means you have the cost reduced version of OFDM module (aka OFDMv2), which does not have FPGA on it. No FPGA -> no FPGA firmware update.
The v2 has proprietary Artosyn chip instead, which cannot be upgraded. Its internals are not programmable.

 

[ferraript]

I couldn't write it better, quaddamage, great analysis

Radol: if that error message is the only problem and all the systems work fine, great
if not, you'll have to upgrade back to the point where there are no error messages
and one more warning for you: I've seen people with this OFDM module with 255.255.255.254 firmware playing too much with downgrades and upgrades until the module totally stopped responding - you don't wanna get to this point (unless you want to buy another one)

 

[Radol]

,
Radol: if that error message is the only problem and all the systems work fine, great
if not, you'll have to upgrade back to the point where there are no error messages

Camera is not work properly at 1.08.0080+ version((
Point, where there are no error messages is 01.09.0060, but i want 01.07.0060 for change height limit.
Does it mean i can do it for this Phantom, right?

 

[ferraript]

Camera is not work properly at 1.08.0080+ version((
Point, where there are no error messages is 01.09.0060, but i want 01.07.0060 for change height limit.
Does it mean i can do it for this Phantom, right?

since January there is no need to downgrade to 1.7.60 because all FW versions became patchable
so if your AC is working fine in 1.9.60, patch and apply this FW