P3 Pro - Beep from Hell !!!

Anthony Radford said:
I'm wondering this: it originally had v1.5.xx or v1.6.xx FW, and I was trying to upgrade straight to v1.8.80. Is that correct, or would I have to increment up? Meaning, install v1.7 and then v1.8?


Sent from my iPhone using PhantomPilots mobile app
Click to expand...

I've never heard a definitive answer on this. I've seen some threads that say it is "recommended" to do them in sequence, yet I've seen multiple posts on this and other sites where people have gone as far as 1.4 straight to 1.8.80 without issue. Kinda doubt that's it honestly.

Mike
 
Anthony Radford said:
I'm wondering this: it originally had v1.5.xx or v1.6.xx FW, and I was trying to upgrade straight to v1.8.80. Is that correct, or would I have to increment up? Meaning, install v1.7 and then v1.8?


Sent from my iPhone using PhantomPilots mobile app
Click to expand...
I did it in order When I got to 1.8...just like you, Nothing Would not take it and yes I followed all of the DJI instructions. I will wait for 1.9
 
I actually have that page bookmarked, and have used it... Like I said, I've followed every step and every instruction published... Official and unofficial... Still- I start the update process and it just goes on and on... Periods of green/red blinks, a moment of blinking green, then green/red again... For hours at a time... Yet it NEVER succeeds or fails


Sent from my iPhone using PhantomPilots mobile app
 
The only thing I might try in your situation is start going backwards trying to find a FW that might load. Try 1.7. If that fails, try 1.6, and so on. You'd think the part of the code that actually loads the FW would be in nvram or even ROM so that it couldn't be corrupted but I've seen a few posts where a FW update failure resulted in DJI having to perform their "voodoo" to get one loaded. One post even mentioned that on the repair slip it said something like "FW update failure" so apparently it is possible to brick them with a failed FW update.

Mike
 
Anthony,

Good morning. I woke up late today and noticed that your problem is not yet resolved.

Now I understand that you see unknown version for AC FW. In this situation, you can't downgrade to 1.7. That's why I wanted this info.

Will you post txt file generated after FW update process if there is one on your SF card?
 
Mike, I'm trying 1.7 now, but as far as previous FW's, I can't find 1.6... The next "previous" I can find is 1.3


Sent from my iPhone using PhantomPilots mobile app
 
Alok, here are the log texts. This first one is the MISC/LOG hidden file...


Sent from my iPhone using PhantomPilots mobile app
 
========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.05.0030.bin
Upgrading ...
Result: Success.

========== 2015.12.01 00:50:42 =====================
Packet: P3X_FW_V01.05.0030.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2015.12.03 07:15:50 =====================
Packet: P3X_FW_V01.05.0030.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3X_FW_V01.05.0030.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2015.12.03 09:12:37 =====================
Packet: P3X_FW_V01.05.0030.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2015.12.06 07:32:26 =====================
Packet: P3X_FW_V01.05.0030.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2015.12.06 08:01:19 =====================
Packet: P3X_FW_V01.05.0030.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2016.01.19 13:07:53 =====================
Packet: P3X_FW_V01.05.0030.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

========== 2016.05.03 19:01:21 =====================
Packet: P3X_FW_V01.08.0080.bin

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

========== 2016.05.03 20:02:23 =====================
Packet: P3X_FW_V01.08.0080.bin

========== 2016.05.03 20:03:42 =====================
Packet: P3X_FW_V01.08.0080.bin

========== 2016.05.03 20:05:26 =====================
Packet: P3X_FW_V01.08.0080.bin

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

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


Sent from my iPhone using PhantomPilots mobile app
 
Ok, my bad - the above is NOT the hidden log, but the Result Log from the root location


Sent from my iPhone using PhantomPilots mobile app
 
Have you tried holding down the link button on the Phantom while powering up with the firmware in the card? That was offered as a fix for this sort of problem a number of firmware revisions ago. IIRC it worked for me once. Easy to try. Supposedly puts the Phantom in some sort of state to better accept firmware.

Come on DJI, sort this out or at least document it well enough to let somebody else do it.
 
WetDog said:
Have you tried holding down the link button on the Phantom while powering up with the firmware in the card? That was offered as a fix for this sort of problem a number of firmware revisions ago. IIRC it worked for me once. Easy to try. Supposedly puts the Phantom in some sort of state to better accept firmware.

Come on DJI, sort this out or at least document it well enough to let somebody else do it.
Click to expand...

Definitely sounds like it's worth a try! I think I would also make sure the RC is off, take the props off, do the above, and just let it sit for an hour, ignoring any lights or sounds. It's possible it could take longer or not go through the normal sequence if it's recovering from some sort of failure and I'd be tempted to give it a long time without bothering it. Then check your results log to see if any new entries. Your log file shows signs of life to me. Several times you got "Upgrading" WRT the 1.8 firmware... although the last couple dozen only show "packet".

Mike
 
So, like a migraine headache sufferer, you are suggesting leaving the P3 in a dark, quiet room to help it heal?

Now that's an approach I've not though of. Or are you suggesting the OP sit in the dark, quiet room?
 
Ok, giving that a try... Sounds similar to booting a phone to "recovery mode" ... I think there should be a way to "factory reset" the firmware, like you can do on a phone


Sent from my iPhone using PhantomPilots mobile app
 
WetDog said:
So, like a migraine headache sufferer, you are suggesting leaving the P3 in a dark, quiet room to help it heal?

Now that's an approach I've not though of. Or are you suggesting the OP sit in the dark, quiet room?
Click to expand...

Close. The idea was to maybe put it in a bathroom and close the door for an hour while it's trying to update... to avoid the pilot getting a migraine from the beeping. And give it more than enough time to do whatever it needed while in there. Might want to check the potty afterward though just to be sure nothing needs to be flushed after leaving it in there that long. ;)

Mike
 
Too funny mike... Well, I tried @WetDog's idea of holding in the Link button while powering on... Let it run for 1 1/2 hours and still No Joy...

Seriously, there HAS to be a way to Factory Reset or Reflash the firmware.!?!?. Easy to do with SmartPhones...


Sent from my iPhone using PhantomPilots mobile app
 
Ugh. I keep checking back hoping you'd post "that did it!" That sucks. And I agree. You'd think there would be some fallback that would let it suck up that bin file and apply it. Did you get any new entries in your results log file?

Mike
 
Nope. No such luck yet! I do however have a set of replacement connection wires (part 42, I think) on the way. Hopefully it could be just a bad "grey" wire...(?). When I got this Phantom, it did have some crash damage, including broken yaw arm and the front grey wire's leads were pulled out of its connector. I was able to press the leads back into their respective spots in the connector, and I thought all was well. But I did order the replacement set though..


Sent from my iPhone using PhantomPilots mobile app
 
Wow. You didn't think it was worth mentioning this was a damaged Phantom.

I'm out.
 
Actually, in my very first sentence, on my very first post- I did state that "I made some repairs to my gimbal"


Sent from my iPhone using PhantomPilots mobile app
 

Similar threads

M
P3p issues
Replies
2
Views
832
Phantom 3 Pro/Adv
crash1sttime
crash1sttime
A
Phantom 3 Standard- Weird problem
Replies
147
Views
6K
General Discussion
quaddamage
quaddamage
G
No running lights at all, Non stop buzz buzz buzz on drone, rc requires c1+c2+snap button just to come on with power cable inserted at all
Replies
3
Views
1K
Phantom 3 Pro/Adv
quaddamage
quaddamage
S
P3 Firmware Post Crash Firmware Update Issue
Replies
8
Views
782
Firmware
Capt KO
Capt KO
Z
P3A Gimbal Going Crazy After Crash - But All Motors Aligned
Replies
20
Views
4K
Phantom Crash & Flyaway Assistance
Droneted
Droneted

Recent Posts

Members online

No members online now.
Total: 1,857 (members: 0, guests: 1,857)

Forum statistics

Threads
143,514
Messages
1,471,057
Members
105,489
Latest member
AlienzEyes