Are there instructions somewhere on how to create local repositories to build /e/ for the ASUS Zenfone 8 with “repo sync” (without using a Docker image)?
Hello @bnsmb, welcome to this forum.
[HOWTO] build /e/ the (full) classic way (no docker, no scripts, just 'make')
How-To: Building an /e/OS ROM the Repo Sync way for an unsupported device using LineageOS sources
Thanks, I know that there is a working /e/ image for the ASUS Zenfone 8.
For me, however, it is important that I can compile the CustomROM I use myself
I use this because of its flexibility
Thanks all for the links and answers.
After a few unsuccessfull attempts to compile /e/ for the ASUS Zenfone 8 without using the Docker image, I finally decided to use the Docker image to build /e/ for the ASUS Zenfone 8. as described here
https://doc.e.foundation/support-topics/build-e
This worked without any problems, except that the instruction
The device code can be found in the /e/OS device list or by running the following command via adb:
$ adb shell getprop ro.product.device
does not work for the ASUS Zenfone 8 – ro.product.device for this phone is “ASUS_I006D”, but the device ID for the command to create the image is “sake”
(as stated for this phone on the page https://doc.e.foundation/devices )
I have documented my efforts to create an /e/ OS image for the ASUS Zenfone 8 here:
And for the records:
Since LineageOS 20, the TWRP image for the ASUS Zenfone 8 no longer boots when LineageOS is installed on the phone.
(see http://bnsmb.de/My_HowTos_for_Android.html#How_to_use_TWRP_if_LineageOS_20.x_is_installed). And since /e/ is based on LineageOS, this also applies to /e/.
For this reason, I have created some “special” TRWP images for /e/ on the ASUS Zenfone 8 - see http://bnsmb.de/My_HowTos_for_Android.html#TWRP_images_for_ASUS_Zenfone_8_with_e for details and links to download the images.
The TWRP images are also available on github:
https://github.com/bnsmb/recovery-images-for-ASUS-Zenfone-8/tree/main/recovery_images/ugly_images
The script for creating these TWRP images is available here
https://bnsmb.de/files/public/Android/create_ugly_twrp_image.sh
and also on github:
it might also work for other phones with the same problem.
IMHO the default recovery for the LineageOS (and therefor also for /e/) is somehow crippled because the access to the files in the /data partition is not possible when the phone is booted into the recovery.
One note for the instructions on the page https://doc.e.foundation/support-topics/build-e:
On Linux the default non-root user should be added to the group “docker”. All users in the group “docker” can execute docker commands without using sudo.
not to derail the thread, just as a side note - true on:
but ! - some devices recovery fstab allows to mount from the cli. In any case there is no UI to do it. Is your only goal to change the build strings?
The script creates a new TWRP image using the kernel from the LineageOS boot image and the ramdisk from the original TWRP image. That’s why I call it “ugly” image - it should only be used when really necessary.
I have successfully tested the ugly TWRP image with each of the /e/ versions and also with LineageOS and some other LineageOS-based customROMs for the ASUS Zenfone 8.
IMHO, a recovery without access to the /data partitions lacks the most important feature for maintenance
I use the recovery for automatic installation and customization of the Android OS (ok, most people don’t need that), but in most cases you boot into the recovery to repair some files in /data or backup files from the /data partition when the real OS on the phone is no longer usable. And this is not possible with the LineageOS recoveries.
On some devices, the recovery Fstab allows mounting from the Cli.
Do you know of a LineageOS restore with this feature?
I would like to see how it is implemented.
with the right fstab + kernel you can just mount in the adb session you have with the recovery.
The issue user ran into was a recovery kernel that couldn’t mount the filesystem. Context were space issues during/after upgrade. It’d be nice for lineage/e to use twrps openrecoveryscript.
As for how it’s implemented, in that old thread I linked how twrp goes about it.
1 Like