5, Compilation, Clearing the previously compiled content, because the files in the out directory that have been generated conflict with TWRP, will cause TWRP compilation to fail.(make clean)
or you can restore the previously compiled content
$mv out ../
$make recoveryimage -j36
6, Upgrade the compiled recovery.img separately (out/target/product/rk3399/recovery.img)
7, After upgrading, enter the system and execute the following command:
$adb reboot recovery
To only burn the stock recovery.img or TWRP.img recovery, you can use AndroidTool.
Only select the recovery partition and point it to the image location.
Also the last button on the bottom, it will get the partition layout from your device to get the correct location of the recovery partition, you must do this first.
For Linux flashing or TWRP in English only Khadas will be able to help.
Just one problem - when I reboot Edge-V it always boots to TWRP and from it’s menu when I choose Reboot > System or Reboot > Bootloader it says “No OS installed”. Is it so that TWRP does not recognize Android Pie?
Thanks, looking forward to it.
I hope it will have interesting new features and bug-fixes RK did.
I just hope Google didn’t make Android 10 more strict with security etc, they always want to lock down things more so users can’t root or use Magisk or have nice features anymore. I read Google wants to use Key Attestation then apps like Magisk won’t be able to pass Safetynet anymore in future and with users that use their developer accounts they make it impossible to install any apps from USB, download now and you can only use the Google Play Store for apps, I hope this doesn’t happen in Android 11/12 for normal users. But if things change for the worse, I think lots of users will move over to Linux like KDE BigScreen OS that now also have a tv optimised OS where users have no restrictions, it will be interesting to see what happens in future.
BTW, for the latest Magisk Manager on Android 9, you also need to enable the checkbox in Magisk Manager’s Settings for ‘Magisk Hide’ to hide the app from Safetynet otherwise the ‘Basic Integrity’ test will fail.
For Firmware with TWRP Recovery,
we must also find a way to use it with micro-sd cards to update firmware on emmc eg. with SDDiskTool.
Currently SDDiskTool only supports upgrading firmware on emmc with stock recovery from a micro-sd card.
You are right there but it’s a custom LineageOS they adapted, not official firmware from Amlogic. It’s also a lot more difficult to maintain and keep updated since hundreds of patches and changes have to be ported every time to make it work.