Currently the user still needs to do two things, try to automate them:
[ ] click build model 9 times to enable adb mode.
[ ] manually press and hold POWER OFF+VOLUME UP after the twrp recovery package is installed, to boot into recovery mode. Recovery mode can also be accessed from adb reboot recovery, however, the FP2 OS automatically removes the customly installed TWRP recovery when it boots, so rebooting from fastboot into adb (the normal FP2OS) removes the TWRP recovery, which means the adb reboot recovery will not access TWRP. At the same time fastboot reboot recovery throws an error indicating something like the recovery is not available. Perhaps this error has to do with the naming of the TWRP image file. The manual equivalent of fastboot reboot recovery which is holding the two buttons at/before power up does work.
[ ] The user needs to press on the phone to configure the LineageOS configuration, this could possibly be automated by asking the user the questions in advance in terminal. If so, the advantage could be to trade screen clicks with typed text, and to remove the delay in configuring the productivity setup after LineageOS has been fully loaded.
Currently the user still needs to do two things, try to automate them:
build model
9 times to enableadb
mode.POWER OFF+VOLUME UP
after thetwrp
recovery package is installed, to boot into recovery mode. Recovery mode can also be accessed fromadb reboot recovery
, however, the FP2 OS automatically removes the customly installed TWRP recovery when it boots, so rebooting from fastboot into adb (the normal FP2OS) removes the TWRP recovery, which means theadb reboot recovery
will not access TWRP. At the same timefastboot reboot recovery
throws an error indicating something like the recovery is not available. Perhaps this error has to do with the naming of the TWRP image file. The manual equivalent offastboot reboot recovery
which is holding the two buttons at/before power up does work.