Ok so I was wrong! This fw was not corrupted because the man who created it is not good enough, etc... The guy is basically a "hero" in the dji modding scene, and I have used his mavic pro and spark modding guides sucessfully, so it wouldnt make sense that he randomly just uploaded some corrupt p3 fw files online for no reason. He is not at fault at all. This is all my mistake.... I feel like such a stupid noob
let me make clear how this whole ordeal happened.
I have never done such a stupid move in my life before. In my initial post I say that I accidentally powered down and thought that this is what caused the bricking of the mc. Most people can't believe that the p3x can get bricked easily on power down/interruption of fw updates, and they are correct. IT CAN'T. Upon further inspection (and after receiving the mc replacement unit from a local repair shop and soldering it in place as i mentioned here on my previous posts) I found out that my p3x is functional once again. I then went to reflash the modded digdat0 PMCAPPFw3.bin. I let it finish succesfully. Then I restart the drone and I get the no-lights esc-motor beep beep forever pattern.
I sit down this morning with a clear head and a good coffee and inspect the PMCAPPFw3.bin that I inserted in the sd card to update through the notepad.
THEN i realize my monumental and stupidest/noobest mistake I have ever made in my life!!!!!
all this time, instead of cloning the whole repository of digdat0 (the man who has made the hacked fw) and downloading it and using the PMCAPPFw3.bin I want to use for updating, i did the following stupid action:
I was right clicking on the "P3X_FW_V01.11.0020_m0306.bin_MODDED" file and "save as" instead of going into the file option of github and clicking the download button/raw.
So i inspect the "stupid download mistake P3X_FW_V01.11.0020_m0306.bin_MODDED" I updated to the poor p3x which has now bricked not one but two mc's!!!! It shows up on notepad as follows (just the start of it, I am copying it with parts missing so it wont mess with my post, its clearly html code):
!DOCTYPE html
ink rel="ns-prefetc" href="
https://githb.githubassets.com"
Can you believe my stupidity???? I basically flashed the mc with html code!!!!!!!
The correctly downloaded digdat0 modded fw file is like this in notepad (just the start part of it, I won't copy the hole code):
� e���m���o���“���•���—��� ™���›��� �Η��γ���΅���΅���΅���΅���΅���΅���±¤��·¤��½¤��Γ¤��Ι¤��α¤��η¤��ν¤��σ¤��ω¤��΅���¤��΅����S���S��YS��΅���Ο¤��΅���΅���΅���΅���΅���΅���΅����¤���¤��“¤��¥¤��΅���΅���]¤��c¤��i¤��Υ¤��΅���΅���Ι-���§��΅���΅����¥��΅���C΅��΅���΅���o¤��u¤��΅���΅����¥���¥���¥��G΅��΅���΅���΅���½U��ΙU���V��΅���;|���¥��#¥��)¥��{¤��™¤��«¤��΅���΅���΅���΅���΅���΅���΅���΅����¤��‡¤��΅���΅���΅���΅��� ΅����π¶�πΣϋ�µ�π«πpω�π�� !�π�ϊ@� !�πxΰ`�½�µ�½�΄χϋ�Ό�πΤϊ�π7Ή�µ7πgπ.ύhFGπεpH !�`A`Α`�π�ψ�πΔψlH�0�π�jH<0�π™hFHπζψ �½fH !A`�`�`Α`pG�µ�π2�π£ψ�¨�π%ϋ/π½ώaπ`�π}ψaπƒώ�π ψ πPω�π·ϊ�π€ϊ�π�ω�π«ϋTH !�0Rπ�ώχΦhF%π�ύ �Oτzq�ϋρςN �™Pπ…ψP΅R Pπ�ψHI� �`�½�µOπΙFLahI�a`OπΗΰh (�ΠΤι���B�ΡOπΊ !α`OπΊ h (�Π½θ�@ G�½�µOπbώ�πuϊ½θ�@Ϊη4H�µ@hh±2HOτ�q�0�π΅ πςψ�πώ½θ�@�πsΊ#πIω½θ�@&π¨Ό(H�0�π«Ώ&I� H`pG$I H`pG"H@hpG H€hpG�µ%π�ό�L h�()Ρ�π�ΰh@�ΰ` h@��!°ϋρς `�ϋ�
Have you ever seen such stupid/noob mistakes being made before in the dji modding scene? I feel so ashamed! I will try to flash the mc's with the stlink v2 programmer I will be receiving in the mail tomorrow (monday), and now at least I have found the culprit of my problems!!!! Do you believe I am approaching this stlink flashing method correctly? I will attach to swdio, swclk, 3v3 and gnd pads to the corresponding pins of the programmer and try to use the stlink software to flash the PMCAPPFw3.bin file. Will that suffice, or do I have to actually go and use the tool you mention above to unpack the latest dji p3x fw and locate the 0305 module itself and flash that to the stm32? I have only used the dji tools for calibration of the spark gimbal (succesfully) and even managed to use the same tool to calibrate the mavic air gimbal and the p4 gimbal. But I have had trouble using the pyetoelf tool or the other tools, i get errors in the command prompt, even though my python install works ok (since i can run the spark gimbal calibration succesfully)