Pixel 3xl build with modified vendor partition.

184 views
Skip to first unread message

subhani shaik

unread,
Sep 6, 2019, 2:47:16 PM9/6/19
to android-porting
@All, I am making a minor change to existing vendor partition and hitting the Google splash screen. Following are the steps, 

repo init -u https://android.googlesource.com/platform/manifest -b android-9.0.0_r21

repo sync -j32 -c --no-clone-bundle --no-tags





curl --output - https://dl.google.com/dl/android/aosp/google_devices-crosshatch-pq1a.181205.006-44e2a750.tgz | tar -xzvf -

tail -n +315 extract-google_devices-crosshatch.sh | tar -zxvf -





curl --output - https://dl.google.com/dl/android/aosp/qcom-crosshatch-pq1a.181205.006-7656db33.tgz | tar -xzvf -

tail -n +315 extract-qcom-crosshatch.sh | tar -xzvf -



make -j80

mkdir dist; make -j80 dist DIST_DIR=dist



load images aosp_crosshatch-img-eng.subhanishaik.zip using fastboot flashall --slot a



With above step everything works great.



Next step, include a sample binary in /vendor/test/

Make the required changes to include the above package in vendor.img, verify it through vendor/bin as well as look into the new vendor.img image.



I also modify the device/google/crosshatch/BoardConfig-common.mk to include the following lines so custom vendor.img is created.



BOARD_USES_VENDORIMAGE := true

BOARD_VENDORIMAGE_PARTITION_SIZE := 805306368

BOARD_VENDORIMAGE_FILE_SYSTEM_TYPE := ext4

TARGET_COPY_OUT_VENDOR := vendor



make clobber; rm -rf out; rm -rf dist; make -j80; mkdir dist; make -j80 dist DIST_DIR=dist



unzip the new aosp.img image

fastboot flashall --slot a



after this the Pixel3 XL is hung at the Google boot screen. Can you please let me know if there is any issue abv or any other signing of the images?



Appreciate the help.

Reply all
Reply to author
Forward
0 new messages