Recent content by gdanas87

I cannot stress this enough: this is not at all @Digdat0's hack that is the problem, but the way I wrongly flashed it/implemented it... This is how this thread started. My mistake was that I was clicking right click and save to the fw file and my browser was not downloading it as a simple...

to anyone who might want to know how this turned out! long story (not so) short: I managed to connect to the stm32 which was read/write protected and had to be wiped in order to be used. I managed to unpack the latest p3p fw with dji fw tools and use 0305 (loader) and 0306 (app) modules but it...

I received the st link v2, downloaded the stlink utility, connected to the corresponding pins on the mc, but I get nothing. Can not connect. That went well lol. I guess I am out of luck, will just have to get a new whole mainboard now

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...

true true.. I am such a fool. I just used this guys guides to hack my mp and spark so I thought his p3 methods would be reliable... I am the only one to blame though. I have ordered an stlink v2 to try and flash the mc with the module. Now I need to find a way to unpack the bin/hex of the 03 05...

ok update. I received the replacement "used" mc. Soldered carefully to my mainboard. Drone started up, all good. Flashed 11.20 successfully, all worked fine. EVERYTHING GREAT and working as it should. I then go and reflash with the hacked fw, I let it finish. It finished sucessfully. I say wow...

Hello guys, I have bricked not one but TWO mc's trying to apply the digdat0 nfz hack. First one was my fault (turned it off during update), second one I was so lucky to find an old mc locally for free, pulled it from a bad esc board and soldered onto my p3p maiboard and it worked perfectly. Then...

First of all let me say wow this explanation is great. Yesterday I tried very carefully to solder some hair thin wires to the pb10 and pb11 tiny tiny pads on the MC. Pb10 I did ok (while my solder Iron was heating up), pb11 I accidentally pulled because I had forgotten my solder Iron on too high...

The problem is that no matter how many times I try to upgrade I get 0306 device not connected so it thinks the MC is not plugged in. This all happened because of interrupted fw update (my stupid mistake). I was thinking there was an easy way to flash the contents of the MCAPPFw.bin (for the 0306...

So using the bin file of the 0306 fw and flashing (assuming I can even get it to connect with the ftdi adapter) wont do anything? I have to get an stlink and copy over the contents of the 0306 part of the fw bin file using the offset you suggest?

Hello I am having the exact same problems with Sionbach, looks like I have only destroyed m0306 as well after an interrupted update. I have an ftdi adapter and need to unpackage the fw to get the m0306 fw and flash it manually. I have located the boot0 pin and pb10 and pb11 pins which I will...

Thank you for the reply, I only tried linking through the app and not with the remote buttons press sequence. Here is a video of what happens , though I have only tried pressing once the button on the side of the aircraft (as you see in video) but it doesnt go in bind mode. Weird thing also is...

Can anyone help me figure out what this flashing code means? It started happening a few days ago when I turn on the drone the led first turns on green and then it cycles through rgy colors. Front arms stay red, rear arms flashing yellow and my remote doesnt connect anymore and when I try to bind...