Phantom Pro 3 - Constant Beeping, Failed Firmware, Bricked?, Please help!

Joined
Sep 21, 2020
Messages
12
Reaction score
2
Hello,

Found the latest firmware 1.11 and tried updating, now I keep getting constant fails...I've tried formatting the card, different sd card, multiple times, still beeping.

My ipad shows the firmware to be updated, but the drone is constantly beeping...

Any help would be greatly appreciated

Thank you all in advance,

Alan
 

Attachments

  • P3X_FW_LOG_AB.txt
    45.8 KB · Views: 150
  • P3X_FW_RESULT_AB.txt
    7.2 KB · Views: 179
  • unnamed.jpg
    unnamed.jpg
    1.5 MB · Views: 263
  • unnamed (1).jpg
    unnamed (1).jpg
    1.1 MB · Views: 233
  • unnamed (2).jpg
    unnamed (2).jpg
    807.3 KB · Views: 210
  • unnamed (3).jpg
    unnamed (3).jpg
    961.7 KB · Views: 252
  • unnamed (4).jpg
    unnamed (4).jpg
    1.2 MB · Views: 256
  • unnamed (5).jpg
    unnamed (5).jpg
    1.1 MB · Views: 241
Last edited:
You have several modules that are not detected. First thing I’d try would be; format the card again then put a debug file on it then the original firmware version you had on it, 1.10.90, and try that update. Probably won’t work but worth a try.
 
Thanks KachemakDiver,

So I formatted the card
Created a debug file called P3X_FW_DEBUG on the card
Put P3X_FW_V01.10.0090 bin file on the card
Inserted card, and the light on the gimbal turned to green

Still constant beeping, removed sd card and this is what the logs say...


========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.10.0090.bin
Result: Abort.
The current firmware does not support downgrade. Use a different version of firmware to downgrade the target version.

[00012801]========== remo-con disconnect. boot(15) ============
[00012876]Packet [C:\P3X_FW_V01.10.0090.bin] detected, card sn [0xcb12416a].
[00012955]Packet upgrade start...

[00013035]Packet checking...
[00013109]Packet vlink 01.10.0090 <-> 01.10.0090.
[00013187]Record vlink 01.11.0020 <-> 01.11.0020 (flow = 6).
[00013261]Packet upgrade failed at packet checking.
 
  1. Just formatted the sd card using the dji go app
  2. Added the P3X_FW_V01.11.0020.bin file to sd card on pc
  3. Plugged the sd card into the drone
  4. Powered up Remote controller and ipad, connected to the ipad cable, turned on drone; I was able to take a video and picture from the drone with the ipad dji go app
  5. Constantly beeps
  6. Gimbal was flashing green/red ultimately turning to red

here are the logs:

P3X_FW_RESULT_AB

========== 2020.09.22 09:37:17 =====================
Packet: P3X_FW_V01.11.0020.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.


P3X_FW_LOG_AB
[00012822]========== 2020.09.22 09:37:17. boot(15) ============
[00012898]Packet [C:\P3X_FW_V01.11.0020.bin] detected, card sn [0xcb12416a].
[00012975]Packet upgrade start...

[00013060]Packet checking...
[00013140]Packet vlink 01.11.0020 <-> 01.11.0020.
[00013216]Record vlink 01.11.0020 <-> 01.11.0020 (flow = 0).
[00013291]Done.

[00013372]Version checking[1]...
[00025958][03 06][00] device not detected.
[00038536][03 05][00] device not detected.
[00038626][04 00][00] v1.48.0.0 -> v1.48.0.0
[00051202][11 00][00] device not detected.
[00063778][11 01][00] device not detected.
[00076353][12 00][00] device not detected.
[00088935][12 01][00] device not detected.
[00101514][12 02][00] device not detected.
[00114096][12 03][00] device not detected.
[00114294][15 00][00] v1.1.2.0 -> v1.1.2.0
[00126880][17 00][00] device not detected.
[00139469][17 01][00] device not detected.
[00139581][19 00][00] v1.0.8.96 -> v1.0.8.96
[00139658][01 00][00] v1.32.5432 -> v1.32.5432
[00139735][01 01][00] v1.32.5432 -> v1.32.5432
[00139842][08 00][00] v0.13.0.7 -> v0.13.0.7
[00139940][09 00][00] v4.1.0.0 -> v4.1.0.0
[00140017]Packet upgrade failed at version checking.
 
When you start the update, does the gimbal light do the green-red green-red at all? What sounds come from the gimbal?
According to the results log it states the failed firmware version as the 1.11.0020, which is what you said also. DJI made that firmware version to where you are not supposed to be able to downgrade the firmware versions. Although the update failed, it has updated some of the modules.
DJI also has an unofficial firmware version to repair the P3P’s that version 1.11.0020 created an ESC error. It’s called 1.11.0030. It was specifically for ESC error repair. I don’t know if it would be beneficial for your situation or not. I attached the file for it if you decide to try it.
Other than that, you may have to replace the motherboard.
 
When I start the update yes does the green to red blink for about 2minutes, then goes to red, gimbal definitely makes noises like the normal low beep noise...then when it hits red the gimbal has a long constant beep and wants to stay straight, if i move it it goes back to straight position.

Okay I will try to find the attached file you added and update this bad boy.
 
I couldn’t get the attachment to complete, so here’s a thread from the forum you can view and download the firmware version from.
Look towards the bottom of post # 1 and you will find the link.
 

Attachments

  • Safari - Sep 22, 2020 at 10:02 AM.pdf
    304.2 KB · Views: 289
  • Like
Reactions: alancostarica
  1. Formatted card using DJI Go app
  2. Added P3X_FW_V01.11.0030.bin to SD card from PC
  3. Plugged in SD card to drone
  4. Beeping like crazy, goes green to red for 2 minutes, then stays constant red.
Here are the log files:


P3X_FW_RESULT_AB
========== 2020.09.22 12:26:55 =====================
Packet: P3X_FW_V01.11.0030.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.


P3X_FW_LOG_AB
[00012925]========== 2020.09.22 12:26:55. boot(15) ============
[00013005]Packet [C:\P3X_FW_V01.11.0030.bin] detected, card sn [0xcb12416a].
[00013090]Packet upgrade start...

[00013174]Packet checking...
[00013251]Packet vlink 01.11.0030 <-> 01.11.0020.
[00013326]Record vlink 01.11.0020 <-> 01.11.0020 (flow = 0).
[00013526]Done.

[00013606]Version checking[1]...
[00026183][03 06][00] device not detected.
[00038762][03 05][00] device not detected.
[00038852][04 00][00] v1.48.0.0 -> v1.48.0.0
[00051437][11 00][00] device not detected.
[00064015][11 01][00] device not detected.
[00076592][12 00][00] device not detected.
[00089171][12 01][00] device not detected.
[00101748][12 02][00] device not detected.
[00114323][12 03][00] device not detected.
[00114524][15 00][00] v1.1.2.0 -> v1.1.2.0
[00127109][17 00][00] device not detected.
[00139689][17 01][00] device not detected.
[00139789][19 00][00] v1.0.8.96 -> v1.0.8.96
[00139873][01 00][00] v1.32.5432 -> v1.32.5432
[00139953][01 01][00] v1.32.5432 -> v1.32.5432
[00140049][08 00][00] v0.13.0.7 -> v0.13.0.7
[00140149][09 00][00] v4.1.0.0 -> v4.1.0.0
[00140227]Packet upgrade failed at version checking.
 
So many modules not detected including the VPS and all ESCs. Are there any cables disconnected inside or out?
 
  • Like
Reactions: KachemakDiver
So many modules not detected including the VPS and all ESCs. Are there any cables disconnected inside or out?
I thought about that also. The OP didn’t mention a crash, just the 1.11.0020 failed update. At this point I wouldn’t rule out anything.
 
  • Like
Reactions: Oso
Alright taking the screw drivers out...Time for an operation to find some loose cables..

Just tried to downgrade firmware but get the "cant downgrade" message

So many modules not detected including the VPS and all ESCs. Are there any cables disconnected inside or out?

Maybe inside, Yes I have crashed it, there was some damage to one of the propeller motor housing...maybe there is a loose cable there now? Nothing was noticeable when I repaired it. I was able to wrap some aluminum tape to the housing and flew it about 20 more times. I've had the drone stored for about a year and after booting it up, that's when the beeping began!
 
That’s what confuses me. Although it was crashed, you have flown it numerous times since then. But,,, I wouldn’t rule out anything now. Did you check the grey ribbon cable going to the OFDM/VPS module? Is it plugged in completely and making good contact? And the grey one from the drone to the camera,, check also to be sure that each grey wire is fully inserted into the white connector.
 
  • Like
Reactions: Photomaton
That’s what confuses me. Although it was crashed, you have flown it numerous times since then. But,,, I wouldn’t rule out anything now. Did you check the grey ribbon cable going to the OFDM/VPS module? Is it plugged in completely and making good contact? And the grey one from the drone to the camera,, check also to be sure that each grey wire is fully inserted into the white connector.

Just popped out the two plastic pins, disconnected and reseated the two wires..

Started up the drone, same beeping, exact same error logs..no new modules have becomes available..
 
Just popped out the two plastic pins, disconnected and reseated the two wires..

Started up the drone, same beeping, exact same error logs..no new modules have becomes available..
After checking the cables you would still need to try the update again.
Are you taking the shell halves apart to check the cables inside?
 
"So many modules not detected including the VPS and all ESCs. Are there any cables disconnected inside or out?"

any link to matching modules to the device; ESC's....etc?
thanks
 
"So many modules not detected including the VPS and all ESCs. Are there any cables disconnected inside or out?"

any link to matching modules to the device; ESC's....etc?
thanks
Is this what you are asking for?
 

Attachments

  • Safari - Sep 22, 2020 at 3:15 PM.pdf
    95.1 KB · Views: 321

Members online

No members online now.

Forum statistics

Threads
143,066
Messages
1,467,359
Members
104,936
Latest member
hirehackers