Downgrading firmware on P3P from 1.10.9 to 1.7.6

[Neon Euc]

Hi peeps thanks for all the info! Awesome.

I can confirm successful downgrade from 1.11 using debug file for P3A to 1.10. I did another step to 1.9 (no + signs) because I had ESC status error. In the end the status error was caused by something else but it was worth the try. (bird is flying again though)

Also maybe handy to ad this link in the main article (if not already):
DJI Phantom Accessories & Tips - Phantom Help

It's a link the all the previous P3 Advanced firmwares.
I tried to flash with P3X files .... took a while b4 I realized it was for P3P not P3A.. duh...

I am not exactly sure which version P3A I have but it has the new motors and the part #96 mainboard.

AC was flying again this afternoon using FW:
AC=1.9
RC=1.6
GO=2.4.2

I'm not sure if I will up- or downgrade from here. If the RC power restriction from FW RC 1.6 is confirmed I'll probably downgrade to RC 1.5.8 and 1.7 for the bird.

Thanks again and hope my contribution is of any help.

Cheers,
Pat

Quick question. If I downgraded the bird with the firmware would it automatically downgrade the remote too?
That's the only thing I don't understand at the moment otherwise I would do that too

 

[VibeyPhantom]

Quick question. If I downgraded the bird with the firmware would it automatically downgrade the remote too?
That's the only thing I don't understand at the moment otherwise I would do that too

Read b4 attempting anything. It's all there, in the 1st post

 

[Serpent]

Help.. My Phantom is stuck. I tried downgrading from P3X_FW_V01.10.0090 to P3X_FW_V01.06.0040 going one firmware at a time. After waiting for the sound to stop and the LED to stop flashing it then went to loud continuous beeps after turning on. I tried to re-do the last firmware but it didn't help. I then tried to re-install P3X_FW_V01.10.0090 without the debug file present and it was still loud beeping. I then tried to re-downgrade through all the firmwares to P3X_FW_V01.05.0030 without any luck. Still loud beeping. Each time i'm waiting for the LED to stop flashing.

Attaching the log file.

Last few entries of results file:

========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3X_FW_V01.10.0090.bin
Upgrading ...

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.10.0090.bin

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

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.08.0080.bin
Upgrading ...

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.07.0060.bin
Upgrading ...



========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.06.0040.bin
Upgrading ...

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.05.0030.bin
Upgrading ...

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.06.0040.bin
Upgrading ...


Thanks for any assistance.

Serpent

 

[Crunch97]

I can confirm downgrading to 1.7 on a first or second generation bird

 

[Crunch97]

Help.. My Phantom is stuck. I tried downgrading from P3X_FW_V01.10.0090 to P3X_FW_V01.06.0040 going one firmware at a time. After waiting for the sound to stop and the LED to stop flashing it then went to loud continuous beeps after turning on. I tried to re-do the last firmware but it didn't help. I then tried to re-install P3X_FW_V01.10.0090 without the debug file present and it was still loud beeping. I then tried to re-downgrade through all the firmwares to P3X_FW_V01.05.0030 without any luck. Still loud beeping. Each time i'm waiting for the LED to stop flashing.

Attaching the log file.

Last few entries of results file:

========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3X_FW_V01.10.0090.bin
Upgrading ...

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.10.0090.bin

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

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.08.0080.bin
Upgrading ...

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.07.0060.bin
Upgrading ...



========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.06.0040.bin
Upgrading ...

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.05.0030.bin
Upgrading ...

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.06.0040.bin
Upgrading ...


Thanks for any assistance.

Serpent

Mine logs looked pretty much the same as yours going from 1.9 to 1.8 I had to remove the debug file that was the only time it showed success from 1.9 - 1.8 tested the bird flies fine I however did not have the loud beeping I would start from the top and go down double check each firmware by inserting the card and seeing if the upgrade took by looking for firmware is equal to or older than current

 

[Serpent]

Mine logs looked pretty much the same as yours going from 1.9 to 1.8 I had to remove the debug file that was the only time it showed success from 1.9 - 1.8 tested the bird flies fine I however did not have the loud beeping I would start from the top and go down double check each firmware by inserting the card and seeing if the upgrade took by looking for firmware is equal to or older than current

I just saw this on GitHub which shows that it may be a 2 step process (one with debug file present and one without debug file present) to properly downgrade each firmware so there is no '+' showing in the DJI Go app About page. Apparently the '+' means there is a firmware module mismatch.

1.10 -> 1.9 + Debug
1.9 -> 1.8
1.8 -> 1.8 + Debug
1.8 -> 1.7
1.7 -> 1.7 + Debug
1.7 -> 1.6
1.6 -> 1.6 + Debug
1.6 -> 1.5
1.5 -> 1.5 + Debug
1.5 -> 1.4
1.4 -> 1.4 + Debug
1.4 -> 1.3
1.3 -> 1.3 + Debug
1.3 -> 1.2
1.2 -> 1.2 + Debug
1.2 -> MVOM0Fw.bin
1.2 -> 1.1.9 (Red Led, Long Beep, FW Not Updated)
1.2 -> 1.1.9 + Bind (All the same)

 

[Serpent]

From what I see on the P3X_FW_LOG_AB file and according to this source (DJI Firmwares · mefistotelis/phantom-firmware-tools Wiki · GitHub) the ESC center board and VPS Module board are not being detected. Wondering if a hardware failure occured during the downgrade/upgrade process.

Does anyone know if there's a software way to fix this or should I now be taking the drone in for repair?
[00027460][11 00][00] device not detected.
[00040032][12 00][00] device not detected.
[00052613][12 01][00] device not detected.
[00065200][12 02][00] device not detected.
[00077776][12 03][00] device not detected.
[00090356][15 00][00] device not detected.
[00102941][17 00][00] device not detected.

 

[Delboy1000]

From what I see on the P3X_FW_LOG_AB file and according to this source (DJI Firmwares · mefistotelis/phantom-firmware-tools Wiki · GitHub) the ESC center board and VPS Module board are not being detected. Wondering if a hardware failure occured during the downgrade/upgrade process.

Does anyone know if there's a software way to fix this or should I now be taking the drone in for repair?
[00027460][11 00][00] device not detected.
[00040032][12 00][00] device not detected.
[00052613][12 01][00] device not detected.
[00065200][12 02][00] device not detected.
[00077776][12 03][00] device not detected.
[00090356][15 00][00] device not detected.
[00102941][17 00][00] device not detected.

 

[Delboy1000]

Hi Everyone,
I am new to Phantom Pilots so I hope I will not upset anyone.
I upgraded my out of warranty P3P to the latest firmware after it had spent some months sat doing nothing. Upgrade failed and I got the infamous 08 and 15 device not detected messages. Downgraded following the first post advice and back up again to 1.11 and all worked except camera transmission - still not detected, several attempts later still no joy so bought a brand new camera for £192 in an EBay auction. 5 minutes after delivery I had a fully functioning P3P that only required a camera firmware upgrade which took only a few minutes.

Much cheaper than a return to a DJI repairer - but why the hell should I have to spend hard earned cash after a firmware upgrade fried my camera transmitter or whatever bit of circuitry DJI cannot build properly. More to the point why no advice from DJI to only do a firmware upgrade if you have a cooling fan directed at the gimbal?

 

[Oso]

Hi Everyone,
I am new to Phantom Pilots so I hope I will not upset anyone.

Welcome to the forum!

I upgraded my out of warranty P3P to the latest firmware after it had spent some months sat doing nothing. Upgrade failed and I got the infamous 08 and 15 device not detected messages.Downgraded following the first post advice and back up again to 1.11 and all worked except camera transmission - still not detected

Was everything including image transmission working fine prior to the first failed FW update attempt?

I ask because we have had numerous threads which started with, "I haven't used it in a while and it was working perfectly the last time, but now...."

We learned some time ago that there is a known issue with bad blocks sometimes forming in the NAND memory when the P3 is not used for long periods of time. If you didn't check first that all was well before updating, you may have already had an issue without realizing it.

why the hell should I have to spend hard earned cash after a firmware upgrade fried my camera transmitter or whatever bit of circuitry DJI cannot build properly. More to the point why no advice from DJI to only do a firmware upgrade if you have a cooling fan directed at the gimbal?

This one is a head scratcher, but DJI is unfortunately well known for poor communication. Even so, they have known about the bad memory issue and the overheating issue for a long time. Even if they didn't want to do a recall to fix the memory, it would be so simple to communicate out a reminder about using a fan of some kind when doing an update or when using the simulator. Perhaps a splash screen in the app or simply putting it in the release notes would help. Even though we have seen from the last FW update that many don't read the release notes, it would at least be more widely known with so little effort. We have been telling people about using a fan in the Pro/Adv forum almost since the P3 was released, but only a small subset of P3 owners read this forum. Too many owners are unaware.

 

[Delboy1000]

Welcome to the forum!


Was everything including image transmission working fine prior to the first failed FW update attempt?

I ask because we have had numerous threads which started with, "I haven't used it in a while and it was working perfectly the last time, but now...."

We learned some time ago that there is a known issue with bad blocks sometimes forming in the NAND memory when the P3 is not used for long periods of time. If you didn't check first that all was well before updating, you may have already had an issue without realizing it.

This one is a head scratcher, but DJI is unfortunately well known for poor communication. Even so, they have known about the bad memory issue and the overheating issue for a long time. Even if they didn't want to do a recall to fix the memory, it would be so simple to communicate out a reminder about using a fan of some kind when doing an update or when using the simulator. Perhaps a splash screen in the app or simply putting it in the release notes would help. Even though we have seen from the last FW update that many don't read the release notes, it would at least be more widely known with so little effort. We have been telling people about using a fan in the Pro/Adv forum almost since the P3 was released, but only a small subset of P3 owners read this forum. Too many owners are unaware.

Don't know, I upgraded Go first which told me that AC and RC both required firmware upgrades which I did blindly, innocently believing that DJI would let me know if precautions were required before updating. A warning on the download page of their site would be simple but I guess that they are afraid to even suggest that there may a fault in case people litigate en-masse and it costs them a fortune in recall.

What we need is a DJI whistle blower with the evidence to show they know it is their mistake and have failed to remedy it.

 

[Serpent]

Well.. remarkable.. I thought to retry 1.10 firmware again and this time finally the bird stopped the loud continuous beeping after waiting about 20 minutes. It took about another 20 minutes for the process to completely finish. Now I have just flashing yellow lights and no camera view from the Go app. Motors still won't start up from the RC however. My current module version list is as follows:

[01832738]Version checking[6]...
[01832863][03 05][05] v34.2.0.9 -> v34.2.0.9 need upgrade.
[01833004][03 06][05] v2.4.20.28 -> v2.4.20.28 need upgrade.
[01833098][04 00][05] v1.48.0.0 -> v1.48.0.0 need upgrade.
[01833323][11 00][05] v1.8.0.0 -> v1.8.0.0 need upgrade.
[01833483][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[01833576][11 01][00] v1.8.0.0 -> v2.0.0.33
[01833716][12 00][05] v1.11.0.0 -> v1.11.0.0 need upgrade.
[01833852][12 01][05] v1.11.0.0 -> v1.11.0.0 need upgrade.
[01833987][12 02][05] v1.11.0.0 -> v1.11.0.0 need upgrade.
[01834112][12 03][05] v1.11.0.0 -> v1.11.0.0 need upgrade.
[01834341][15 00][05] v1.1.2.0 -> v1.1.2.0 need upgrade.
[01834467][17 00][05] v1.1.1.7 -> v1.1.1.7 need upgrade.
[01834627][17 01][05] v1.0.2.7 -> v1.0.2.7 need upgrade.
[01834732][19 00][00] v1.0.8.96 -> v1.0.8.96 need upgrade.
[01834825][01 00][05] v1.32.5432 -> v1.32.5432 need upgrade
[01834915][01 01][05] v1.32.5432 -> v1.32.5432 need upgrade
[01835032][08 00][05] v0.13.0.7 -> v0.13.0.7 need upgrade.
[01835312][09 00][05] v3.0.0.10 -> v3.0.0.10 need upgrade.
[01835404]Packet upgrade failed at firmware upgrade.

 

[chazz]

Well.. remarkable.. I thought to retry 1.10 firmware again and this time finally the bird stopped the loud continuous beeping after waiting about 20 minutes. It took about another 20 minutes for the process to completely finish. Now I have just flashing yellow lights and no camera view from the Go app. Motors still won't start up from the RC however. My current module version list is as follows:

[01832738]Version checking[6]...
[01832863][03 05][05] v34.2.0.9 -> v34.2.0.9 need upgrade.
[01833004][03 06][05] v2.4.20.28 -> v2.4.20.28 need upgrade.
[01833098][04 00][05] v1.48.0.0 -> v1.48.0.0 need upgrade.
[01833323][11 00][05] v1.8.0.0 -> v1.8.0.0 need upgrade.
[01833483][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[01833576][11 01][00] v1.8.0.0 -> v2.0.0.33
[01833716][12 00][05] v1.11.0.0 -> v1.11.0.0 need upgrade.
[01833852][12 01][05] v1.11.0.0 -> v1.11.0.0 need upgrade.
[01833987][12 02][05] v1.11.0.0 -> v1.11.0.0 need upgrade.
[01834112][12 03][05] v1.11.0.0 -> v1.11.0.0 need upgrade.
[01834341][15 00][05] v1.1.2.0 -> v1.1.2.0 need upgrade.
[01834467][17 00][05] v1.1.1.7 -> v1.1.1.7 need upgrade.
[01834627][17 01][05] v1.0.2.7 -> v1.0.2.7 need upgrade.
[01834732][19 00][00] v1.0.8.96 -> v1.0.8.96 need upgrade.
[01834825][01 00][05] v1.32.5432 -> v1.32.5432 need upgrade
[01834915][01 01][05] v1.32.5432 -> v1.32.5432 need upgrade
[01835032][08 00][05] v0.13.0.7 -> v0.13.0.7 need upgrade.
[01835312][09 00][05] v3.0.0.10 -> v3.0.0.10 need upgrade.
[01835404]Packet upgrade failed at firmware upgrade.

i believe flashing yellow means the RC isn't connected...Maybe try to re-linking the RC to the bird...

 

[Serpent]

Thank you Chazz. Great help. I finally got it working again. Took many hours of updating and lots of waiting. Re-calibrated the compass and got it to talk happily with RC which was at a lower firmware level.

 

[kevinwo]

Thanks airbender, has been downgraded from 1.10.9 to 1.6.4, app use Android 3.1.3, IOS use 3.1.11, did not find forced to upgrade the firmware, but prompted to upgrade, but can be normal flight. Thank you for sharing!

 

[Serpent]

Can safely say that after all the loud beeping and modules not found that the drone is working as well as ever again. Thank you to Chazz for his great help. I'm not sure if that was the definitive thing that fixed it as it was when I re-applied 1.10 that it finally stopped the loud beeps and started to behave like normal again.

 

[chazz]

I believe what ultimately fixed it for you wasn't the modules but the fact you let it update through all that loud beeping and didn't care about the possible overheating issue...I had the same issue once when i interrupted an update and the next time i tried to update i got the crazy loud ESC beeping continuously for maybe a 30min while in the background i could hear the very faint d-d-d which made me let it keep going...It was one of the most painful things i had to listen to and I wanted to stab my eardrums with an ice pick..So hats off to you for enduring this and being patient and happy to see your flying again bud!

 

[EastOfTexas]

Any reports on how the 1.11 --> 1.10.9 worked out? I am in a situation where that is looking like my only option. Any thoughts, much appreciated!


UNCONFIRMED: At this time, we have only heard of one rollback attempt from the 1.11 FW, and it was just back to 1.10. With DJI now actively working to prevent people from 'tweaking' the firmware, it is possible that 1.11 has something in it that makes this riskier than normal.

 

[marck1991]

I rolled back from 1.11 to 1.7 too with debug method. Can confirm it is working for me. I'm having the board P01012.09 .
I did it like:
1.11 -> 1.10 + Debug
1.10 -> 1.9 + Debug
1.9 -> 1.8
1.8 -> 1.8 + Debug
1.8 -> 1.7
1.7 -> 1.7 + Debug
The last step was important for me, every version step was fine without a + except for 1.8 -> 1.7. There I had to use again debug method on 1.7 itself otherwise I got a + .

EDIT: I have to say that I did the update from 1.10 to 1.11 within the day the update was released the first time on 06.07.2017. And the downgrade was done within the next two days. I don't know whether DJI modified 1.11 to prevent downgrading. I attached the 1.11 I downloaded at 06:30PM at the release day and which I used to upgrade. LINK

 

[airbender]

I rolled back from 1.11 to 1.7 too with debug method. Can confirm it is working for me. I'm having the board P01012.09 .

Awesome, thanks for sharing! OP updated with a link to your post