This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
howto:recover_remote_control_pairing_on_spark [2018/08/23 15:07] validat0r [Restore pairing with saved 11pkey] |
howto:recover_remote_control_pairing_on_spark [2019/09/20 09:27] (current) validat0r Typos and additional information in Note 2 |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Save and recover remote control pairing with Spark ====== | ====== Save and recover remote control pairing with Spark ====== | ||
- | Pairing the remote control (RC) to your Spark is normally a task for the first day of playing with your new toy: Do it with directions from the DJI GO 4 App or do it manually by pressing some buttons on the devices. But if you accidentialy | + | Pairing the remote control (RC) to your Spark is normally a task for the first day of playing with your new toy: Do it with directions from the DJI GO 4 App or do it manually by pressing some buttons on the devices. But if you accidentally |
==== Pairing Spark and RC manually ==== | ==== Pairing Spark and RC manually ==== | ||
Line 9: | Line 9: | ||
- If not, you've better have read this manual before | - If not, you've better have read this manual before | ||
- | ==== Saving your 11pkey of a current pairing ==== | + | ==== Saving your 11pkey |
This step is essential for an accidental un-paring, e.g. by pressing the power button on the Spark for 6 sec until it beeps twice, which means " | This step is essential for an accidental un-paring, e.g. by pressing the power button on the Spark for 6 sec until it beeps twice, which means " | ||
- | The goal is to look for and write down the " | + | The goal is to look for and write down the " |
- Root your bird with DUMLracer | - Root your bird with DUMLracer | ||
Line 21: | Line 21: | ||
==== Restore pairing with saved 11pkey ==== | ==== Restore pairing with saved 11pkey ==== | ||
- | Say, you've un-paired your Spark from the RC, accidentially | + | Say, you've un-paired your Spark from the RC, accidentally |
What' | What' | ||
Now the previously saved 11pkey comes in handy. | Now the previously saved 11pkey comes in handy. | ||
Line 37: | Line 37: | ||
Of course, you can do the editing on an //adb shell// with //busybox vi / | Of course, you can do the editing on an //adb shell// with //busybox vi / | ||
- | Note: The 11pkey lives on the RC, too, of course. In a perfect world you would have to possibility to just look if up on the RC. | + | Note: The 11pkey lives on the RC, too, of course. In a perfect world you would have to possibility to just look it up on the RC. |
Note 2: Although there seems to be no indication on the Spark AC itself, it's possible that the RC has some kind of information with which AC it was paired beforehand (MAC wise), so it's unclear if this method can be used with a different Spark with a different Wifi MAC address. | Note 2: Although there seems to be no indication on the Spark AC itself, it's possible that the RC has some kind of information with which AC it was paired beforehand (MAC wise), so it's unclear if this method can be used with a different Spark with a different Wifi MAC address. | ||
- | Note 3: There are rumours that pressing | + | Edit: Turns out, you can just align the MAC addresses of two Sparks by manipulating / |
+ | |||
+ | - adb shell | ||
+ | - busybox hexdump -C / | ||
+ | - cd /;mount -o remount,rw /amt;echo -e -n \\x60\\x60\\x1f\\x12\\x34\\x56 > / | ||
+ | - now you have an AC with the MAC 60: | ||
+ | - please pick a random 12:34:56 part and leave the 60:60:1f alone. The latter might be important for auto-pairing. | ||
+ | |||
+ | Note 3: Pressing | ||