Well done for trying @xShottaZx ! I have not used aospdtgen before. I did have a quick run though late last night but got no useful result. My comments below are therefore based that and “What I might try next” !
I did not manage so far to collect a copy of Android Dumps / sony / pdx237 · GitLab it is marked “protected” I got no complete download and could not login.
This source appears to be a ROM dump already (but it is unknown if produced as required in instructions by)
Android stock ROM dump (made with dumpyara).
Had I managed to collect that download I would have added it to my working environment as dump_path with no further modification.
- (My understanding is that one would apply dumpyara to an actual
pdx237stock ROM, rather than an already dumped product.)
Now looking at the usage instructions
usage: python3 -m aospdtgen [-h] [-o OUTPUT] dump_path
My intention had been to run the command as
python3 -m aospdtgen -o my-device-tree-product pdx237_download
Maybe your collected .zip (substituted as pdx237_download or dump_path) would produce a different result like this ? (you might experiment with the .zip or the extracted contents).
I don’t know your previous experience with ROM building so I hesitate to give entry level tips … but …
-
I would try to complete a build as Build for pdx234 | LineageOS Wiki. When you get to
extract.files.shyou do not need to do this as your proprietary blobs can be found here GitHub - TheMuppets/proprietary_vendor_sony_pdx234. As you say GitHub - LineageOS/android_kernel_sony_sm8550 is needed but is shown here android_device_sony_sm8550-common/lineage.dependencies at lineage-21 · LineageOS/android_device_sony_sm8550-common · GitHub as a dependency so is expected to appear inroomservice.xml.- (The resulting build is no use to you but you might do this just to prove you have a working build environment for LineageOS. Also you probably already noticed LineageOS is at Android 14 (U), while /e/OS is not ready for that yet at Android 13(T), so you would not be able to move onto /e/OS till “end of summer”, but you could further experiment with https://github.com/lineageos4microg.)
-
(No direct use to you for LineageOS build other than “learner experimentation”) but during my research I fould GitHub - sonyxperiadev/device-sony-pdx237
-
Maybe this thread, [Walkthrough] device.xml for local_manifests will throw light on the device tree and the need for it for an unsupported device but not for a supported device. (Notice that the device tree is not mentioned in the Lineage build instructions for the supported device
pdx234.)
Liberating a new phone is no easy job, congratulations on where you got (even if it seems disappointing so far !).
Better than my suggestions … follow @Petefoth’s suggestion and build AOSP, here vendor blobs are already supplied, no need for extract.files.sh. The output of this build could be quite interesting to you. (You might during the course of this look for a stock ROM for your phone so that you have a known path to return if your build installs but is unsatisfactory for daily use. Might be found here ? Xperia Stock ROM - Database of Sony Xperia Firmware)