TaruTaruKing
commented
4 years ago Nah, this was a common problem after firmware updates from what I've read. I believe it is firmware related, so I am just working backwards from 1.11.0200 to 1.03.0200 and then I will go forwards. Just thought I could try those files if that didn't work as a last ditch effort before I toss the board. I could bake it or use a hot air blower on it I guess, but I do think it's firmware related. I found this post that made me attempt the stepped firmware downgrade/upgrade, but it's pretty tedious lol
"Hi Guys,
I know this is an old thread, but thought it worthwhile sharing with you how I fixed this without sending the aircraft back to DJI, or replacing any hardware. I posted this last night on another forum, but I'm not sure about the rules of link sharing from other forums(?), so I'll just add the entire post here:
Right, I've had this issue myself, and have just managed to fix it without RMA or hardware replacement. It's pretty much taken me all weekend though, researching this and other forums.
So I tried different firmware versions on the aircraft, the two firmware versions available on the controller, nothing.
Then I found this link showing how to help 'force' upgrade or downgrade firmware: forcing fw downgrade with P3X_FW_DEBUG · Issue #4 · mefistotelis/phantom-firmware-tools · GitHub It's a very simple thing to enable, just create a file called P3X_FW_DEBUG in the root of the SD card you are using to do the firmware upgrade. I did that by creating a text file, naming it as above, and removing the .txt extension.
Reading in the above link, mefistotelis states that he believes that long jumps in firmware upgrades are not ideal.
So, and this was the painful bit, I decided to try and flash the firmware in order by version steps - it took bloody ages: I found this link on one of these forums where you can download all the versions of firmware for the P3P:
DJI Phantom Accessories & Tips - Phantom Help I downloaded them all, and started with the current version, going one by one down to a much older version (not the oldest version): v1.10.9 v1.09.6 v1.08.8 v1.07.6 v1.06.4 v1.05.3 v1.04.1 v1.03.2 v1.02.6
All of them failed with the long dirty tone sounding on the aircraft at the end of the upgrade process, but I persevered. Noting that each time, the aircraft would mostly boot as normal, but still showing 'No Image Transmission' when connected. Also, a few times, the aircraft would not properly start at all, and instead would start beeping loudly 'like an alarm' clock and no lights showing on the aircraft as some posters have commented. BUT, the upgrades would still run through, so I kept going, and after applying the next version down, the loud beeping would stop and the aircraft lights would come back on. Eventually, I got to the earliest version (v1.02.6) with none of the upgrades reporting successful, but then I started incrementing firmware versions from oldest to newest as follows:
from v1.02.6 v1.03.2 v1.04.1 v1.05.3 v1.06.4 v1.07.6 v1.08.8 and on this version, the firmware update was successful - for the first time!
Not quite believing it had worked, I decided to power on the craft and controller (which was running v1.5 firmware).
Lo and behold, the **** picture is back and working again! I can't believe it! I am going to cancel the RMA that I raised today, while I was halfway through this process and lost hope - convinced it was a hardware issue!
I hope the above process works for anyone else out there who has tried many different ways to fix their issue.
It just goes to show, it's not 'definitely a hardware issue' if you get both the: [00028828][15 00][00] device not detected. [00041697][08 00][00] device not detected. at the same time.
Best of luck!"
szupi
rufiooo
Hi, we have several Phantom 3 Advanced drones which were upgraded to Pro by changing gimbals or camera control boards and flashing Pro firmware. After a several hours flashing of firmware, all Pro camera control boards NAND died. Therefore we bought some Advanced control boards where is no NAND memory to fail. But there is our problem:
It was possible to change from Adv to Pro by SD card with P3X firmware, which was flashed. But Phantom 3 with Professional firmware ignore P3S (Advanced) BIN file and it ignore all known debug files.
Is there a way how to flash Advanced BIN file to board which was flashed with Pro BIN file? If it works from Adv to Pro, it should work from Pro to Ad.
In DJI Go there is no error, only message that camera firmware update is required.