-
Notifications
You must be signed in to change notification settings - Fork 12
Troubleshooting
If the rooting process tells you the process was a success however you are unable to find any devices to connect to from the main page of the configurator, then you are stuck in a "root loop". We're aware of this issue in the configurator and are working solve to it. Since it appears to be PC dependent you may wish to try other devices you have access to. Failing that you can also use the command line margerine exploit to root as it is unaffected by the bug and then proceed to install wtfos via the configurator.
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:
UPDATE=/cache/ota.zip
WTFOS_DIR=/blackbox/wtfos
if [ $(unrd slot_1.status_active) == "1" ] ; then
if [ $(unrd slot_1.status_successful) == "1" ] ; then
if [ -d "$WTFOS_DIR" ] ; then
if [ -f "$UPDATE" ] ; then
if mount | grep -q '/proc/cmdline'; then
echo "removing cmdline bindmount"
umount /proc/cmdline
fi
echo "found $UPDATE, reflashing slot_2"
echo "please wait, this will take a few minutes"
update_engine --update_package=$UPDATE
unrd slot_2.status_active 0
unrd slot_1.status_active 1
echo "slot_2 restored to factory state"
fi
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
else
echo "slot_1 is not successful, aborting"
fi
else
echo "slot_1 is not active, aborting"
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 goggles and try installing wtfos again in the CLI output.
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