I've managed to build Froyo with the CM vendor tree for vision(ie: Desire Z/G2).
The build worked (ive used the same tree to build for a wildfire and desire as well with no issues) - pulled a couple of files (librpc.so and the libcamera libs) from the desire out/ directory.
I'm using dsixda's kitchen to cook then roms, when i push the rom to the phone and attempt to flash it, it fails with "assert failed: write_raw_image("/tmp/boot.img", "boot")" (Status 7)
i am able to flash CM6.1.1.1 and CM7.0.3 with no worries - if i use the boot.img from CM6.1.1 the rom will flash, but then goes a bit special once the rom boots.
I assumed the cm 6.1.1 rom would have the same boot.img as my built CM 6.1.1 vendor + android 2.2.1 - but i'm gravely mistaken
obviously my issue is building the boot.img from the source tree - can anyone give me some hints as to where i should look?
issue resolved - was a kitchen problem
changing the offending lines in updater-script to:
Code:
package_extract_file("boot.img", "/dev/block/mmcblk0p22");
seems to have fixed the issue.
Hi folks,
i build my own unofficial lineageOS 14.1 roms for my oneplus 3 and this roms working fine.
I also extracted the device specific blobs directly from the latest OxygenOS rom image.
Unfortunately, the DASH charging functionality dont work. During the extraction of the blobs, the extract files script shows an error, that the "dashd" blob couldnt be found from the script. I decided to look into the proprietary-files.txt for any dash related things and there is this line:
-sbin/dashd:rootfs
I cannot find the dashd file in the official Oxygen rom and yeah...i messed up a little bit...
Has someone already implemented the DASH functionality in his own unofficial build? Can someone give me a hint, where to get the missing blob?
Thanks, WeeZel
daWeeZel said:
Hi folks,
i build my own unofficial lineageOS 14.1 roms for my oneplus 3 and this roms working fine.
I also extracted the device specific blobs directly from the latest OxygenOS rom image.
Unfortunately, the DASH charging functionality dont work. During the extraction of the blobs, the extract files script shows an error, that the "dashd" blob couldnt be found from the script. I decided to look into the proprietary-files.txt for any dash related things and there is this line:
-sbin/dashd:rootfs
I cannot find the dashd file in the official Oxygen rom and yeah...i messed up a little bit...
Has someone already implemented the DASH functionality in his own unofficial build? Can someone give me a hint, where to get the missing blob?
Thanks, WeeZel
Click to expand...
Click to collapse
I have found the files in this repository : github.com/OnePlusOSS/android_vendor_oneplus_oneplus3/blob/oneplus3/6.0.1/sbin/dashd
Sorry the forum doesn't allow me to post link ...
I'm no expert and just wanted to try and build Mi5s lineageos kernel with just a few minor changes, not the whole rom, but after flashing it doesn't boot.
This is more or less what I've done:
Downloaded lineageos Mi5s source:
https://github.com/LineageOS/android_kernel_xiaomi_msm8996
Downloaded Gooogle's prebuilt toolchain:
https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/
Setup a build system following guides/tutorials from here and there.
Got it to successfully build after a few fixes to source but it doesn't pass the Mi logo.
The 3 images in the output folder are, Image, Image.gz and Image.gz-dtb, from what I've read in various tutorials was to use the Image.gz-dtb image.
So initially I unpacked stock lineageos boot.img and repacked it with my compiled Image.gz-dtb, also I've tried Anykernel2, but it just results in a non booting kernel.
I'm not sure what I'm missing and any help is really appreciated.
Hello,
that's my first steps to building LOS myself.
In the build instruction is only the branch "cm-14.1" listed, can I use lineage-16, too?
Why I have at the end of compiling an recovery.img and what is the difference between TWRP?
Need I for building the LOS .zip for the proprietary blobs? Where can I find an archive of old LOS-ZIPs?
I have a failure with the compilation, how can I debug this? The error is ninja wrapper.
Can I brick my phone, with wrong setting or actions?
Sony has published a configuration with instructions how to compile AOSP from source: https://github.com/sonyxperiadev/device-sony-pdx213
My question is, what would be the expected difference between this vendor configuration, and something like phh-treble?
My understanding is phh-treble is an AOSP generic system image with some fixes applied, while this configuration seems to be literally just that: configuration files.
Of course if you start to compare a more custom GSI to AOSP it has extra features but I'm not so much interested in that, I'm more interested in all the hardware working correctly.
So what's more likely to provide full device functionality, a phh-treble GSI or AOSP based on the vendor configuration?
I'd expect that the vendor image would be the most reliable (as it's from Sony themselves) to take the most advantage of its device-specific hardware. I just checked today and they finally have the image in the "software binaries" that used to have only config files: https://developer.sony.com/file/download/software-binaries-for-aosp-android-11-0-kernel-4-19-lena/
What's actually inside this software binaries image? Is it something you're supposed to flash to your device?
About software binaries (aka vendor image):
https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/build-aosp-android-android-11-0-0
- Step #7 "Flash vendor image to your device".
Huh interesting. The Lineage GSI is almost 2GB while this image is only 300MB unzipped. So I was like... wait is this really a whole ROM? But uh, I guess so!
I thought maybe it's like... just the kernel or something. I think Lineage also includes other partitions. I wonder what would happen if you take the Lineage GSI and then use this as the OEM partition. Horrible things probably haha
pepijndevos said:
Huh interesting. The Lineage GSI is almost 8GB while this image is only 300MB unzipped. So I was like... wait is this really a whole ROM? But uh, I guess so!
Click to expand...
Click to collapse
Hey, when is the GSI so big? It's supposed to be <3GB, wouldn't fit in your /system otherwise.
Sorry was looking at the wrong one (Raspberry Pi) for my phone was indeed 1.8GB but still.
Looking at the link it seems like they do actually flash the OEM partition, and THEN flash the AOSP image partitions. So maybe it DOES actually make sense to use this OEM partition? But I definitely need to understand better what each partition is for before I brick my phone haha
Okay so reading up a bit, GSI only flashes system as far as I can tell, so besides vbmeta and system, all other partitions are original(?)
The linked binary is just the oem partition. Since I did not touch my oem partition when installing the GSI, it probably still contains the original? So is there really any point in flashing this binary? Is there a way to unpack and inspect it? Disk image mounter doesn't like it.
pepijndevos said:
Sony has published a configuration with instructions how to compile AOSP from source: https://github.com/sonyxperiadev/device-sony-pdx213
My question is, what would be the expected difference between this vendor configuration, and something like phh-treble?
My understanding is phh-treble is an AOSP generic system image with some fixes applied, while this configuration seems to be literally just that: configuration files.
Of course if you start to compare a more custom GSI to AOSP it has extra features but I'm not so much interested in that, I'm more interested in all the hardware working correctly.
So what's more likely to provide full device functionality, a phh-treble GSI or AOSP based on the vendor configuration?
Click to expand...
Click to collapse
Phh-treble is a generic system image ( /system only,concept of treble is to use your vendor implementation witch hardware-specific parts without requiring additionnal Work )
phh gsi fix issue of devices specific hardware from oem ( phh fix headset issue in gsi lena for ex )
SODP ( Sony aosp ) is rom witch only open sources stuff .
I have compiled SODP before and actually its isnt stable in this devices ( bug ril, no sound ... )
Until xperiadev fix all issue, we have stable GSI ( I use in daily for professional use ! I have no Bad surprise) we have pe a12,lineage 19 gsi...