Howto: Rooting DJI Crystal Sky

Also my DJI Pilot app doesn't run, but DJI GO v4 works.

Do you mean using flashfire and SuperSU? I don't know, for me it looks like an additional unecessary step:

First of all, we want to avoid persistent root as it can be detectable by apps.
I didn't notice any behaivior of DJI Go 4.3.16 and Pilot 1.7.0 on a rooted device,
but I didn't give it a very deep look. Didn't even decompile the bytecode of the stock apps, just made sure they work as before.

There are other DJI daemons that run as root and can detect (persistently) rooted device with 99% probability if they wish to do so.
These methods involve looking up several system properties that can only been changed when the device is rooted. If the values don’t match an unrooted device it’ll flag it as rooted. (Super)su and Busybox binaries are often present on rooted devices, so a simple file system check can detect it as well.
Some root handlers mount the /system partition as read-write, another way etc.

Losing warranty, bricking, is only one reason why we want to avoid it.
So SuperSU and other things you would probably don't care about on
an emulator - are extremely important here.
The guide should be focused about gaining a temp root, install the stuff (Gapps, apks, firewall rules that you need, reboot and go to a clean state.
By clean I mean system-wise unrooted, with your stuff installed and working.
This part is totally missing from your guide for now.
People who want persistent root can go all the way further and install the
unstable garbage like SuperSU, but it shouldn't be a default for all.

Also we want to make sure it's future proof for any next updates, as it will
be less trivial for DJI and other apps to check for device modifications,
we can safely sideload/update any userspace app without worries.

Back to the original question, no - that method will not work since the original installd will check for the following manifests:
> dji.pilot.pad, com.DeviceTest, com.google.android.apps.maps

In the patched installd, this check is zeroed out with 'a's:
< aaa.aaaaa.aaa, aaa.aaaaaaaaaa, aaaaaaaaaa.aaaaaaa.aaaa.aaaa

Here are both files -
Original: https://mega.nz/#!3MwB1bDR!QlsCdfe_0MDBRlt5InA32QZllPssUKG1MCYC0WgECjo
Patched:
https://mega.nz/#!mY41wRCJ!_U8wDHMUJloyQF6gniKn63ozAl1lxzHkEP0G4HaZQr8

To patch, just replace /system/bin/installd with the patched one.

The copy/overwrite needs to be done with ES Explorer Pro as it handles properly overwriting a file with read/only partitions etc. If you try to modify it directly, the unmodified version would be restored automatically from a cache, erasing your changes.

Got the root from under Windows10 on v3.00.02.00.

Hi there,

Managed to get root too from under Windows10 on v3.00.02.00.
Used the old files I downloaded to get root on the Crystalsky running v2.x

I do have a problem though with FlashFire v0.73 not willing to run.
When fired up, it will properly ask for root admission and then runs some internal routines and force closes somewhere on Checking for Pro...

Never had a FlashFire Pro version. Tried downloading again from  other sites as well, but all keep force closing.

Has anybody any clue as to how to solve this issue?

***EDIT 1***
Managed to overcome the issue by downloading the light version from here:
https://a2zapk.com/97066-root-flashfire-0-73-mod-lite-a2z.html

Next problem I now face is that I cannot flash the newly downloaded Gapps ARM 5.1 pico for some reason. :(
Downloaded that package from official site:
https://opengapps.org/#downloadsection

And yes, I did download the correct version as I have Android v5.1.1 running.

This is kind of sad as it was the whole reason I tried to upgrade the old playstore v17.4.28-all because it apparently doesn't run under firmware v3.00.02.00 anymore. (Yeah, tried clearing cache and data from Play store app too)

***EDIT 2***
Seems the problem of not being able to flash Gapps resides with the FlashFire app I installed.

***EDIT 3***
Still trying.
Seems like the problem of Playstore not working anymore might be that after the firmware update, there is no device ID for Google servers to be found on the device as the directory /data/data/com.google.android.gsf/databases/gservices.db is nowhere to be found...

I suppose that would get installed when flashing Gapps, but the flashing tool from Chainfire won't work any more...

Hope anyone else did manage and is willing to share howto.

***FINAL EDIT***
It worked out.
Read 2 posts below :)

Regards,

Yeah, figured as much.

Here's the thought. Don't install the new firmware if you want to root and install the google play store.

Well here you go.

I managed to get Gapps and all working!

Finally a simple factory reset and reinstalling FlashFire and then flashing Gapps did the trick.

Now over to the second Crystalsky :D

Regards,