Troubleshooting
If you see any of the following issues:
- msp-osd will not switch to HD mode even though you are using Betaflight 4.4 or newer
- msp-osd will not pick up FC specific fonts stored on the SD card
- msp-osd only shows the OSD on part of the screen
- msp-osd only shows the upper left part of the OSD on screen
You should check if your UART between the FC and VTX is wired up correctly in both directions. These issues can result from only having the TX from the FC wired up to the RX on the VTX with the RX from the FC to the TX on the VTX disconnected. One way to check for this issue is to turn on the DJI Custom OSD option in the menus. You should see all OSD elements being drawn double on the screen. If you don't then the UART needs attention.
If you update to V01.04.0000 (or similar) after rooting and then proceed to install wtfos, sometimes you can get kicked back to V01.00.0606 and loose O3 AU support. This happens because sometimes Assistant will only flash the second slot. Use the following commands in the configurator CLI:
unrd slot_1.status_successful 0
unrd slot_1.status_active 0
unrd slot_2.status_active 1
reboot
Then refresh the configurator. Health checks will come up saying slot 1 is corrupt. Press attempt fix, slot 1 will be re-flashed to the correct version.
Sometimes you need to switch modes on the V2 goggles and may not able to do so through the menus for one reason or another.
To switch to DIY Mode:
unrd product_type wm150_gls
reboot
To switch to DJI FPV Drone mode:
unrd product_type wm170_gls
reboot
This can happen because wtfos was installed in firmware slot_2 but your device reset to slot_1 due to a low battery issue or some other related problem. In such a situation wtfos fails to re-install properly into slot_1 because part of it is already installed and visible in /blackbox/wtfos.
Copy and paste the following script into the CLI in the configurator to try to automatically resolve the issue:
WTFOS_DIR=/blackbox/wtfos
if [ -d "$WTFOS_DIR" ] ; then
echo "cleaning up previous wtfos in /blackbox"
rm -rf "$WTFOS_DIR"
rm -rf /blackbox/wtfos.log
echo "wtfos cleaned up, please reboot your device and try installing wtfos again"
echo "you may use 'reboot' to do so"
else
echo "wtfos install not found, aborting"
exit 1
fi
If the script tells you it aborted for some reason, come talk to us on Discord and tell us the whole output. Otherwise you should see instructions to reboot your device and try installing wtfos again in the CLI output.
unrd product_type wm150_gls
reboot
In order to re-flash the currently inactive slot to a stock state you can run the following:
umount /proc/cmdline #skip on v2 goggles
update_engine --update_package=/cache/ota.zip &
busybox tail -f /tmp/recovery.log &
After the process is done, unrd will be set automatically so that the next time you boot the slot you just flashed will be active.
On everything except V2 goggles you will neet to re-root your Goggles after this process to re-gain CLI access.
Rinse and repeat to restore both slots to stock on V2 Goggles. On V1 Goggles and air side one slot will always have to be rooted to be able to flash the other.
Try the following commands in cli:
opkg install --force-reinstall dinit
/opt/etc/init.d/S01dinit.sh start
opkg remove tweak-prevent-force-upgrade
reboot
Just update to the latest wtfos using configurator, the issue will be fixed automatically.
The following is here for reference purposes only.
There's an (unknown) issue that writes OSD stream data into gui translation files.
To disable this behavior, edit /system/gui/etc/diskorc.xml (eg with vi) and change
<parameter name="addtranslations" value="true" />
to
<parameter name="addtranslations" value="false" />
Use the following to restore the original files:
mkdir /tmp/systwo
mount -t ext4 /dev/block/platform/soc/f0000000.ahb/f0400000.dwmmc0/mirror/system_2 /tmp/systwo
cp /tmp/systwo/gui/lang/* /system/gui/lang/
sync
/system/bin/umount -d -l /system
sleep 1
/system/bin/mount -o rw,remount /system
sleep 1
cp /tmp/systwo/gui/lang/* /system/gui/lang/
sync
reboot
