Recent content by FlowDrone

I don't own the original Smart Controller... only RC (RM330) and RC Pro (RM510) It's literally the same patch that the Sincoder program applies to your RM330... I just snatched all of the files his program downloads, and intercepted all of the ADB commands his program executes (which was super...

nice Yankee Candles :)

Firmware updated to 01.02.0600, official Sincoder FCC Patch ran fine! My offline patch also runs fine. SAFE TO UPDATE!

Update is 871.33MB, for the RC (RM330) only, and while it says "Fixed some minor bugs" I think the fact it came out 24 hours after the previous update means it fixes something rather significant. I'll report back once I've finished installing it and re-applied the FCC again

Want me to test with my RC and report back if FCC still works after update? I don't mind because I have multiple drones and remotes (my RC Pro is FCC anyway, so there's zero real risk for me)

DJI does have guidance for issues like these: Use DJI Assistant 2 to push the update from your computer to your device.

The Windows Defender alert is due to the fact that the DJI FCC executable is designed to connect to a remote system, download executables, and run them. This triggers Defender because, theoretically, ANYTHING could be downloaded and executed, and Windows Defender has no way of knowing what is...

Give it another go

Be patient... the server keeps going down because it's being bombarded with tons of requests at the same time.

FCC confirmed! Patch is working (and on latest firmware, I should add). Please be patient for a while guys... a lot of people are trying to hit the server all at once, and it's a bit of a problem for Sincoder's service. Let the program run for 5 minutes, if it still shows "connect faild" kill...

Hi all, was just testing while talking with Sincoder... the prohibited error has been fixed. Try again!

ADB commands I've managed to work out look a little like this: adb push %fcc% /vendor/bin/%elf% adb push %libllg% /vendor/bin It basically pushes the two Android binaries (the ELF file and the libllg.so file) to the vendor's binary folder.

One of the files created by the patch back when the server was online was a file called ".ses" Inside this plain-text document were two lines of string data, the first looked to be the serial of my DJI RC, the second is a key (which I believe is generated based on the serial)

It's an earlier version of the same hack. Just ran the executable and can confirm it also attempts to connect to the same 47.100.49.90 IP address (and the service is still down on this address)

Sadly not so useful, beyond confirming that the executable was definitely packed (which we already know). It reveals only that it is a Console Application for Win64 (64 bit Windows). The DLL is actually a general USB Library used by many different applications, compiled in Microsoft C++ (and...