Hello, I have a Asus Zenfone 4 Selfie Pro and I would like to intsall /e/OS , it currently runs on Android Nougat version 7.7.1. Here you can find all the necessary information about the device : h ttps://www.asus.com/supportonly/ASUS%20ZenFone%204%20Selfie%20Pro%20(ZD552KL)/HelpDesk_Download/
It is currently running on Android and some people have managed to run LinageOS 14.1 but currently it is no longer maintained
XDA link : h ttps://forum.xda-developers.com/f/asus-zenfone-4-selfie-selfie-pro-roms-kernels-r.6881/
TWRP seems to work : https://twrp.me/asus/asuszenfone4selfiepro.html
On Github I have found this : h ttps://github.com/shakalaca/android_kernel_asus_zd552kl h ttps://github.com/2003Frost/android_device_asus_Z01M h ttps://github.com/2003Frost/android_device_asus_Z01M-testing
use a repository for the blobs if this bothers you ("-e INCLUDE_PROPRIETARY=true") - depending on your bandwidth it’s more straightforward. I laid out the options at Failed build for bramble - #5 by tcecyk
The env var is not a default… it’s not suggested in the official doc link at step 5 - but in the repository of the docker image it is explained.
Making this old nougat build work is not easy, good luck! - as @aibd suggested, use the latest vaild nougat branch or build tag
@forart.it you’re mixing up “blobs” - a dtb is different to what is done by a extract-files.sh script - that’s for proprietary libraries and firmware files. dtb is really for hardware addressing by the kernel. When a manufacturer doesn’t publish the kernel source (bad bad bad) you can do discovery of the kernel image and reconstruct the dts file it got compiled from.
@Codex_Leicester I’d need to dig in this device, if it’s possible to reuse a common device repo that’s carried by muppets (I guess) - so that INCLUDE_PROPRIETARY would’ve an effect. The Z10M-testing repo got forked from has the script that includes the .txt. You’d need to meet the conditions to extract them or look around if you can find a repo that has them and put it into your local_manifest → it will be offered at the device/<codename> path for the build process to pick up
2003Frost, Davi Santos is open about his telegram channel on his overview page 2003Frost (Davi Santos) · GitHub, you might ask him which is more suitable. You might also be able to find out if there was any reason he did not move up Android versions. Sometimes also checking if any other forks carried on any further.
But this is one of the device trees you identified in your OP, was it not?
Hi @Codex_Leicester may I congratulate you on covering all the basics in your OP = opening post – I know how it is hard when you have done the research and find that you cannot use hyperlinks as a very new user. I am sure you will face some challenges with this older device, but I wish you luck in your learning experience!
"Hi there. Development stopped because my device broke down and would cost way too much to fix it, so I moved on to other projects.
I’m not sure but I think it’s possible to build /e/ but you’ll probably have to modify the tree to fix any compiling errors though. And since our kernel is broken, like in lineage os, not much will be working even if build is sucessfull. Also, ASUS striked my vendor repo so you’ll have to manually extract vendor files from your device.
At the time we only managed to compile a lineage version that boots but isn’t funcional. There is still a lot of work to be done."