Downgrading firmware on P3P from 1.10.9 to 1.7.6

[xxxntwv]

Tried this on my advanced to downgrade to 1.9.6.0 and after it completed it shows the correct firmware in the app but shows a main controller error at the top of the screen.i tried calibrating the imu but no success.the only way I can get rid of the error is to upgrade back to the latest firmware.

 

[Jarkko Sydänmaanlakka]

I bought mine for 47 USD from eBay. I'm still waiting it to arrive, so no status update yet Only thing that I'm worried about is that the module I bought is ODFM v2 receiver. I wonder if the v2 has less power than v1 ODFM?

I got the new v2 ofdm receiver and it seems to work fine. Only thing is that my AC fw is now 1.7.60+. I flew two batteries yesterday and had zero problems. I don't see anything suspicious in the update log. :/ I understand that the + means module mismatch but what module?

[00011910]Packet [C:\P3S_FW_V01.07.0060.bin] resumed, card sn [0x7dd86162].
[00012021]Packet vlink 01.07.0060 <-> 01.06.0040.
[00012107]Version checking[2]...
[00012238][03 05][00] v34.2.0.9 -> v34.2.0.9 need upgrade.
[00012358][03 06][00] v2.4.13.0 -> v2.4.13.0 need upgrade.
[00012452][04 00][00] v1.41.0.0 -> v1.41.0.0 need upgrade.
[00012623][11 00][00] v1.7.15.1 -> v1.7.15.1 need upgrade.
[00012752][12 00][00] v1.10.0.0 -> v1.10.0.0 need upgrade.
[00012887][12 01][00] v1.10.0.0 -> v1.10.0.0 need upgrade.
[00013037][12 02][00] v1.10.0.0 -> v1.10.0.0 need upgrade.
[00013166][12 03][00] v1.10.0.0 -> v1.10.0.0 need upgrade.
[00017751][15 00][00] v1.1.2.0 -> v1.1.2.0 need upgrade.
[00017887][17 00][00] v1.1.1.7 -> v1.1.1.7 need upgrade.
[00018066][17 01][00] v1.0.2.7 -> v1.0.2.7 need upgrade.
[00018163][19 00][00] v255.255.255.254 -> v1.0.8.96
[00018369][01 00][05] v1.23.4920 -> v1.23.4920 need upgrade
[00018454][01 01][00] v1.23.4920 -> v1.23.4920 need upgrade
[00018564][09 00][00] v2.13.0.0 -> v2.13.0.0 need upgrade.
[00018644]Done.

[00018734]Firmware upgrading[2]...
[00018996][01 01] Firmware upgrade start...
[00049402][01 01] Firmware upgrade finished successfully.
[00049512][12 00] Firmware upgrade start...
[00107791][12 00] Firmware upgrade finished successfully.
[00107911][12 01] Firmware upgrade start...
[00171794][12 01] Firmware upgrade finished successfully.
[00171907][12 02] Firmware upgrade start...
[00236005][12 02] Firmware upgrade finished successfully.
[00236126][12 03] Firmware upgrade start...
[00296541][12 03] Firmware upgrade finished successfully.
[00296684][17 00] Firmware upgrade start...
[00375460][17 00] Firmware upgrade finished successfully.
[00375579][17 01] Firmware upgrade start...
[00433563][17 01] Firmware upgrade finished successfully.
[00433664][11 00] Firmware upgrade start...
[00485484][11 00] Firmware upgrade finished successfully.
[00485604][03 05] Firmware upgrade start...
[00551666][03 05] Firmware upgrade finished successfully.
[00552204][03 06] Firmware upgrade start...
[00849448][03 06] Firmware upgrade finished successfully.
[00849549][15 00] Firmware upgrade start...
[00885942][15 00] Firmware upgrade finished successfully.
[00886067][09 00] Firmware upgrade start...
[00939795][09 00] Firmware upgrade finished successfully.
[00939928][04 00] Firmware upgrade start...
[00998306][04 00] Firmware upgrade finished successfully.
[00998392]Done.

[00998480]Version checking[3]...
[00998594][03 05][05] v34.2.0.9 -> v34.2.0.9 need upgrade.
[00998718][03 06][05] v2.4.13.0 -> v2.4.13.0 need upgrade.
[00998851][04 00][05] v1.41.0.0 -> v1.41.0.0 need upgrade.
[00999018][11 00][05] v1.7.15.1 -> v1.7.15.1 need upgrade.
[00999142][12 00][05] v1.10.0.0 -> v1.10.0.0 need upgrade.
[00999287][12 01][05] v1.10.0.0 -> v1.10.0.0 need upgrade.
[00999498][12 02][05] v1.10.0.0 -> v1.10.0.0 need upgrade.
[00999622][12 03][05] v1.10.0.0 -> v1.10.0.0 need upgrade.
[00999714][15 00][05] v1.1.2.0 -> v1.1.2.0 need upgrade.
[00999903][17 00][05] v1.1.1.7 -> v1.1.1.7 need upgrade.
[01000064][17 01][05] v1.0.2.7 -> v1.0.2.7 need upgrade.
[01000183][19 00][00] v255.255.255.254 -> v1.0.8.96
[01000266][01 00][05] v1.23.4920 -> v1.23.4920 need upgrade
[01000352][01 01][05] v1.23.4920 -> v1.23.4920 need upgrade
[01000462][09 00][05] v2.13.0.0 -> v2.13.0.0 need upgrade.
[01000549]Packet upgrade finish successfully.

 

[Nekenieh]

I've the same v255.255.255.254 in the Log after changing OFDM v2. Bird is flying great though so why bordering
Actually i think the +sign means that you did a downgrade without the DEBUG file and you should not worry about it.

 

[Pete Leare]

Pretty sure that if you flash the same FW you currently have on the P3 WITH the debug file it will get rid of the +. (i.e. Don't downgrade/upgrade the FW, just flash the current FW with the debug file)

 

[Jarkko Sydänmaanlakka]

Pretty sure that if you flash the same FW you currently have on the P3 WITH the debug file it will get rid of the +. (i.e. Don't downgrade/upgrade the FW, just flash the current FW with the debug file)

I did flash the same FW using debug file but the plus didn't disappear. So, the theory doesn't work.

 

[Nekenieh]

I did flash the same FW using debug file but the plus didn't disappear. So, the theory doesn't work.

 

[Nekenieh]

Might it be that the + only disappears when you do an actual downgrade with DEBUG file? As long as everything is functional(on the FW i want) I honestly don't care the + and leave like it is.

 

[Pete Leare]

Ahh, okay - it did for me.. several times. Good luck!

 

[xxxntwv]

After downgrading mine the app shows main controller error,the only way I could resolve this is to upgrade back to the latest. I only went down to 1.9.6 should I continue to downgrade to the next one or will that just cause more issues?

 

[Nekenieh]

After downgrading mine the app shows main controller error,the only way I could resolve this is to upgrade back to the latest. I only went down to 1.9.6 should I continue to downgrade to the next one or will that just cause more issues?

RC Firmware??

 

[xxxntwv]

RC Firmware??

I downgraded the rc to 1.6.0 and aircraft to 1.9.60.after I did this the app would connect but had the red warning at the top that said main controller error. I tried imu calibration and compass but the warning was still there,so I upgraded back to the latest and warning went away

 

[airbender]

The plus sign means that one of the parts of the drone is at a different firmware level than what it's expecting.

When I downgraded mine, I used the same battery for the entire process and I don't have the plus sign. But if I put in one of my other batteries that were updated when the rest of the AC was at the latest, it does show the plus sign.

 

[cristalius]

HI,
Can some one explain more deeper what is the advantage of 1.7.6. I read this "Why 1.7.0060? This was the only version of the firmware that was released with an unencrypted flight controller module, making it an ‘obvious’ choice for modifications. By accident or design of a disgruntled employee, no one who can tell is saying anything."
...but honestly I did not understand what is the advantage of that.

 

[airbender]

Can some one explain more deeper what is the advantage of 1.7.6. I read this "Why 1.7.0060? This was the only version of the firmware that was released with an unencrypted flight controller module, making it an ‘obvious’ choice for modifications. By accident or design of a disgruntled employee, no one who can tell is saying anything."
...but honestly I did not understand what is the advantage of that.

In a nutshell, the unencrypted firmware allows for those who are smarter than I am to be able to 'reverse engineer' (might not the exact correct term to use) the code DJI used to run the drone and potentially change the behavior of various aspects of the drone, like maximum movement speed.

It's the best choice for those who like to tinker. At this time, this tinkering isn't recommended unless you are willing to risk bricking your bird, as it's still in the very early days and there hasn't been anything figured out on how to fix it. Basically, if you have to ask, you don't want to try it.

I assembled these steps for those who might want to get things ready for that day, if it ever happens, and for those who were very unhappy with how their AC worked after installing newer FW and wanted to go back to previous versions where they were happy with how it performed

 

[Digdat0]

hey guys - i finally, FINALLY have a working camera again. Some of you may recall i was one of the first to brick my p3p bird and cam by doing the procedure wrong. I'm going to get the bricked p3p back together (kinda took it apart) and try to re-install 1.8 with my working camera and see if i can get the compass error to go away and it back in the air. Looks like alot of information herea and great results, you guys have come along way!

 

[airbender]

hey guys - i finally, FINALLY have a working camera again. Some of you may recall i was one of the first to brick my p3p bird and cam by doing the procedure wrong. I'm going to get the bricked p3p back together (kinda took it apart) and try to re-install 1.8 with my working camera and see if i can get the compass error to go away and it back in the air. Looks like alot of information herea and great results, you guys have come along way!

Good luck, I look forward to the results of your attempts and work!

 

[Weanuts]

Please Airbender might you help. I love the post but when Downgrading in the P3X_FW_RESULT_AB.txt file I get:

Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:15 remo-con disconnect======
Packet: P3X_FW_V01.10.0090.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:15 remo-con disconnect======
Packet: P3X_FW_V01.10.0090.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.10.0090.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:14 remo-con disconnect======
Packet: P3X_FW_V01.09.0060.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:14 remo-con disconnect======
Packet: P3X_FW_V01.09.0060.bin
Upgrading ...

========== 2014.01.01 00:00:14 remo-con disconnect======
Packet: P3X_FW_V01.09.0060.bin
Upgrading ...

It appears ok in my birds response within DJI Go app. No "+"

Is this a normal response in the "result" file?
thanks

 

[Digdat0]

Finally got the camera hooked up to the bricked p3a (it shows permanent compass error). It appears to start the firmware process, but i get flashing green/red and BEEP-BEEP .. i cant find anything on this. You guys know? I tried formattting SD card, different SDcard, tried 1.8, 1.9, tried forced upgrade holding VPS button, also tried DEBUG file. No go .. and absolutely no logs created on the SD card. I was able to use this camera to upgrade a different p3a, so i know the camera is good.

 

[neven]

Finally got the camera hooked up to the bricked p3a (it shows permanent compass error). It appears to start the firmware process, but i get flashing green/red and BEEP-BEEP .. i cant find anything on this. You guys know? I tried formattting SD card, different SDcard, tried 1.8, 1.9, tried forced upgrade holding VPS button, also tried DEBUG file. No go .. and absolutely no logs created on the SD card. I was able to use this camera to upgrade a different p3a, so i know the camera is good.

Is anything created on SD? Directory structure?

 

[Digdat0]

Is anything created on SD? Directory structure?

yeah it creates the directory structure, and i can see the log folder, just nothing inside it and no P3X_FW_RESULT_AB.txt file created. I do have hidden files showing, no files though.