No, I don't think so. Disable DroneID is probably blocked in the FC firmware of the drone. (Not verified)
Newer drones or newer firmware do not accept such a command.
Forced 500m is a feature of this hack.
Check out some strings from this hack::
enable_force_500
disable_app_login
country_code=%c%c
enable_fcc
enable_force_5_8
enable_force_fcc
enable_force_4G
disable_uuid
disable_droneid
disable_poilt_pos
enable_boost
disable_app_login
Yes, de facto it is copied to the device in to the tmp directory where the file fcc.tar is unpacked, its rights are set, run and finally deleted. Among other things, the ELF file modifies the target file "libDexHelper.so"
The adb authorization itself is still a mystery to me..
The interesting thing is that adb "unauthorized device" appears only after the second RC restart. Probably, after the first restart with the fcc hack, some "cleaning" routine is also started, so after the second restart, the device is unauthorized.
I am trying to install Total commander with no success. Any idea?
error message:: No matching abis
I will answer myself: it was necessary to use a different version of the apk
I have a similar case. Error 40021 appears after gimbal replacement. Gimbal is working. It can be calibrated, but the error remains.
I suspect that the second hand gimbal has already recorded the board's serial number or vice versa.
I'm afraid the horizontal speeds will be encoded deeper in the firmware outside this table.
Maybe partly affect the speed of the parameter "go_home_current" it seems that the battery current is limited to 9A during the return home.
I offer my tested predefined parameters:
Hi Damian,
on this video: [Mavic Mini] Re enable developer tools in DJI Assistant 2
Is actually more than 500 meters? It doesn't seem so high to me.
Thank you for more information.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.