Downgrading firmware on P3P from 1.10.9 to 1.7.6

[neven]

Now I noticed difference in module 11.00...

 

[ferraript]

This looks fine to me but I'm bit worried about the + sign. Should I be?

everything's alright
+ sign means that your battery is still on newer firmware (because firmware of the battery can be downgraded by debug file only)

so you can now continue to 1.7.60 and so on as you mentioned

 

[ferraript]

but wait a second
you should be worried about this:
[19 00][00] v255.255.255.254 -> v1.0.8.96

I saw something like that on github and in the end that module reported version 0.0.0.0

when was that module updated to 255.255.255.254?

 

[neven]

So module 11 is battery? Let me check if I understand why battery wasn't downgraded. Last battery upgrade was in 1.10.90 and it will stay on that version until I downgrade to FW version which had battery module upgrade inside WITH debug file?
As for that weird subnet mask looking version I think that was like that for some time now.

 

[ferraript]

AC FW 1.9.60 has battery module bin versioned 1.8.0.0
AC FW 1.8.80 has battery module bin versioned 1.7.15.1

you downgraded from 1.9.60 to 1.8.80 without debug file, so you still have battery with firmware from 1.9.60
once you downgrade from 1.8.80 to 1.7.60 with debug file, your battery will have firmware from 1.7.60

but in this moment, if I were you, I would be really worried about that [1900] module (FPGA air model 0)
you can read about it here

 

[neven]

but in this moment, if I were you, I would be really worried about that [1900] module (FPGA air model 0)
you can read about it here

Thanks for the tip. From the topic you gave me link to looks like FW 1.4.10 with debug forced change in module 1900. I got my P3P with 1.5.30 installed and v255.255.255.254 was already there for 1900. I think I'll be safe to go to to 1.6.40 like I planned to but I'll wait now to see if any of smart people on the forum could shed some light on this.
When you bought your P3P? Which FW was it originally? How was module version number for 1900 changing in your case during upgrades and downgrades?

Edit: Looks like someone else got 0.0.0.0 on 1900 without going to 1.4.60 but by going to 1.7.60 and then upgrading to 1.8.80. Now I'm more worried.

 

[ferraript]

I got my P3P with 1.5.30 installed and v255.255.255.254 was already there for 1900

are you 100 % positive on this?
if you are, I think in your case special firmware package needs to be applied to get you correctly down to 1.7.60

or, better plan
I compared your current modules with 1.7.60 modules
you need to downgrade 3 modules only:
0306 from 2.4.14.5 to 2.4.13.0
0400 from 1.44.0.0 to 1.41.0.0
0900 from 3.0.0.10 to 2.13.0.0

so ask somebody to extract these modules' bins from P3X_FW_V01.07.0060.bin and update only them
I have P3A so I hope some P3P user could do it for you
if there will be no volunteer, I'll do it for you later, just let me know

and remember, if you don't want to risk losing that 1900 module, never ever use debug file again

 

[neven]

are you 100 % positive on this?
if you are, I think in your case special firmware package needs to be applied to get you correctly down to 1.7.60

Check my log file attached. I think I'm reading it correctly.

or, better plan
I compared your current modules with 1.7.60 modules
you need to downgrade 3 modules only:
0306 from 2.4.14.5 to 2.4.13.0
0400 from 1.44.0.0 to 1.41.0.0
0900 from 3.0.0.10 to 2.13.0.0

so ask somebody to extract these modules' bins from P3X_FW_V01.07.0060.bin and update only them
I have P3A so I hope some P3P user could do it for you
if there will be no volunteer, I'll do it for you later, just let me know

and remember, if you don't want to risk losing that 1900 module, never ever use debug file again

I think I'll be able to extract them too with a help from github project. But I'll give it a few days before I try that to see if I could get some more informations about this. Thanks.

 

[ferraript]

>I think I'm reading it correctly
yeah, you are reading it correctly

>But I'll give it a few days before I try that to see if I could get some more informations about this
of course, there is no need to rush

by the way, I gave you modules' versions instructions based on P3A firmware and as I can see it wasn't good idea, because P3P uses another versions
so in total you need to downgrade 5 modules: 0100, 0101, 0306, 0400 and 0900, starting with 0100 as it contains the firmware loader

 

[Pete Leare]

I'm about to start this downgrade. Do you have to rollback GO before you downgrade the RC?
I'm on the latest IOS version. Thanks!


Sent from my iPhone using PhantomPilots

 

[neven]

I'm about to start this downgrade. Do you have to rollback GO before you downgrade the RC?
I'm on the latest IOS version. Thanks!


Sent from my iPhone using PhantomPilots

I did my RC downgrade to 1.5.8 with latest Go for Android (3.1.3).


Sent from my iPhone using PhantomPilots

 

[Jarkko Sydänmaanlakka]

Update to my " [01276092][19 00][00] v0.0.0.0 -> v1.0.8.96 need upgrade. " problem...

So, my AC won't update the module 19 00, it sits on v0.0.0.0 whatever I try. I even tried to downgrade the AC all the way down to v1.2.7 and then used the service bin. Even that didn't bring the module 19 00 back to life.
Now I'm waiting for a new ODFM receiver board ( I believe that fw module 19 00 is the ODFM ) to arrive sometime next week. Hopefully I am back in the air next week
I'm now on AC version 1.7.60 and the update log shows that everything else is good, only the module 19 00 is not ok.... So, fingers crossed.

 

[neven]

Can you guys check at which point of Upgrade/Downgrade 19 00 became 0.0.0.0?


Sent from my iPhone using PhantomPilots

 

[neven]

The problem is that the text log indicates that history succes is deleted and all updates are with module 19 00 on v.0.0.0.0
As i can remember i succeeded to roll back the bird to 1.4 and i wanted to test(what i shouldn't have done) upgading again to 1.5, then it went wrong.

Is it possible that you did the upgrade to 1.5 with DEBUG file still on SD?

 

[Grumpy]

I am having a hell of a time with the new firmware update, freaking sucks and has messed my machine up. At least I believe it is the firmware. Worked great before I installed it. Anyways, what are the pro's and con's of downgrading to an older firmware vs the newest version? I think I may do it, just wanted to know if the updates are superior to the older one you recommend, such as compass, motors, things like that. Or are the additions negligible? Any info would be great. Thanks.

 

[neven]

I might have done that! Anyway i interchanged the OFDM module with another P3A for troubleshooting and it came back alive! So either i buy a new one or wait until somebody comes with a softwarefix.

That's a good news. How much are those?

 

[Jarkko Sydänmaanlakka]

That's a good news. How much are those?

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?

 

[Pete Leare]

Probably could have installed the whole bin file including the debug file with each battery but i chose to change the name of the extracted file mi03 to "PBATTERYFw3" and it worked...the "+" is gone.

Chazz, where did you get the extracted file mi03 from? Can you post it?

 

[Pete Leare]

Perform a reset of the settings via the app.

Hi @airbender, I know you were/are using an android device, but do you know where the IOS 'reset' option is in DJI Go? I have downgraded to IOS GO V. 2.9.1 and DG AC to 1.7.60 & RC 1.5.80.
Thanks,

 

[airbender]

Hi @airbender, I know you were/are using an android device, but do you know where the IOS 'reset' option is in DJI Go? I have downgraded to IOS GO V. 2.9.1 and DG AC to 1.7.60 & RC 1.5.80.
Thanks,

'fraid I don't.