I'm trying to build paranoid android from source, using a CM12.1 device tree. Here's the link:https://github.com/valascus/android_device_elephone_p8000
I've already tried to modify some things... no sucess.
It gives me this error when i try to lunch:
Code:
lunch cm_p8000-user
build/core/product_config.mk:233: *** Can not locate config makefile for product "cm_p8000". Stop.
WARNING: Trying to fetch a device that's already there
WARNING: device/elephone/p8000/pa.dependencies file not found
build/core/product_config.mk:233: *** Can not locate config makefile for product "cm_p8000". Stop.
** Don't have a product spec for: 'cm_p8000'
And this one when i try to build directly:
Code:
build/core/envsetup.mk:158: *** No config file found for TARGET_DEVICE . Stop.
WARNING: Trying to fetch a device that's already there
WARNING: device/elephone/p8000/pa.dependencies file not found
build/core/envsetup.mk:158: *** No config file found for TARGET_DEVICE . Stop.
** Don't have a product spec for: 'pa_p8000'
** Do you have the right repo manifest?
Starting compilation
build/core/product_config.mk:252: *** No matches for product "full". Stop.
Any clue?
Someone???
Still nobody.... Jesus...
It appears you're trying to build a cm build rather than a PA build, but I have to ask, why the hell are you trying to build with code that's well over a year old and unfinished?
Related
Code:
Which would you like? [full-eng] 9
ls: cannot access device/*/D710/cm.mk: No such file or directory
build/core/product_config.mk:234: *** Cannot locate config makefile for product "cm_D710". Stop.
Device D710 not found. Attempting to retrieve device repository from CyanogenMod Github ([URL]http://github.com/CyanogenMod[/URL]).
Repository for D710 not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
ls: cannot access device/*/D710/cm.mk: No such file or directory
build/core/product_config.mk:234: *** Cannot locate config makefile for product "cm_D710". Stop.
** Don't have a product spec for: 'cm_D710'
** Do you have the right repo manifest?
Re: [Q]Proprietary Drivers for compiling?
I suggest installing CM10.1 then with ADB added to your path, run the extract script.
Sent from my SPH-D710 using xda premium
Deleted
Im getting a new error when im in lunch menu.
Code:
Which would you like? [full-eng] 9
ls: cannot access device/*/D710/cm.mk: No such file or directory
build/core/product_config.mk:234: *** Cannot locate config makefile for product "cm_D710". Stop.
Device D710 not found. Attempting to retrieve device repository from CyanogenMod Github ([URL]http://github.com/CyanogenMod[/URL]).
Repository for D710 not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
ls: cannot access device/*/D710/cm.mk: No such file or directory
build/core/product_config.mk:234: *** Cannot locate config makefile for product "cm_D710". Stop.
** Don't have a product spec for: 'cm_D710'
** Do you have the right repo manifest?
Your best bet is to jump on irc.
webchat.freenode.net
irc.freenode.net:6667
Then join #jb-dev-e4gt
Sent from my SPH-D710 using xda premium
EDIT: The compile was so far but then i got this error:
Code:
cannot create /home/austin/beanstalk/out/target/product/d710/obj/KERNEL_OBJ/usr/include/linux/atm_nicstar.h: Read-only file system
/home/austin/beanstalk/out/target/product/d710/obj/KERNEL_OBJ/usr/include/linux/atm_nicstar.h.tmp: Read-only file system
make[4]: *** [/home/austin/beanstalk/out/target/product/d710/obj/KERNEL_OBJ/usr/include/linux/.install] Error 30
make[3]: *** [linux] Error 2
make[2]: *** [headers_install] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/austin/beanstalk/kernel/samsung/smdk4210'
make: *** [/home/austin/beanstalk/out/target/product/d710/obj/KERNEL_OBJ/usr] Error 2
make: *** Waiting for unfinished jobs....
collect2: ld terminated with signal 6 [Aborted], core dumped
make: *** [/home/austin/beanstalk/out/host/linux-x86/obj/EXECUTABLES/mkbootfs_intermediates/mkbootfs] Error 1
make: *** Deleting file `/home/austin/beanstalk/out/host/linux-x86/obj/EXECUTABLES/mkbootfs_intermediates/mkbootfs'
make: unlink: /home/austin/beanstalk/out/host/linux-x86/obj/EXECUTABLES/mkbootfs_intermediates/mkbootfs: Read-only file system
I've been following along with the instructions on the cyanogenmod wiki on building for M8.
(I'd post the link, but the system won't let me since I'm new)
I'm doing this on Ubuntu 16.04 LTS.
I managed to get all the way to the command: breakfast m8
But here I'm stuck. It's throwing an error, and I can't seem to figure out what to do about it.
I'd very much appreciate a hint. The response from the command is below:
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:234: *** Can not locate config makefile for product "cm_m8". Stop.
Device m8 not found. Attempting to retrieve device repository from CyanogenMod Github
Found repository: android_device_htc_m8
Default revision: cm-13.0
Checking branch info
Checking if device/htc/m8 is fetched from android_device_htc_m8
CyanogenMod/android_device_htc_m8 already fetched to device/htc/m8
Syncing repository to retrieve project.
sh: 1: repo: not found
Repository synced!
Looking for dependencies
Dependencies file not found, bailing out.
Done
build/core/product_config.mk:234: *** Can not locate config makefile for product "cm_m8". Stop.
** Don't have a product spec for: 'cm_m8'
** Do you have the right repo manifest?
Hey,
what do I have to do to build the latest LineageOs for my I9195?
I know the following guide:
https://forum.xda-developers.com/chef-central/android/how-to-build-lineageos-14-1-t3551484
But when running
Code:
breakfast serranoltexx
I got following error.
Code:
** Don't have a product spec for: 'lineage_serranoltexx'
** Do you have the right repo manifest?
Does someone of you have some infos for me?
Thanks
Dominik
Uups. Think reading the manual not complete. It seems that extracting proprietary blobs does not work.
Got error:
Code:
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/samsung/serranoltexx/lineage.mk]]: "vendor/samsung/serrano-common/serrano-common-vendor.mk" does not exist. Stop.
Does the extracting work through VirtualBox? Currently I have some issues.
I am trying to build LineageOS 13 for my device and I'm following this guide: https://forum.xda-developers.com/chef-central/android/how-to-build-lineageos-14-1-t3551484
I'm using this device tree: https://github.com/vampirefo/android_device_blu_Life_One_X2_Mini
and this vendor tree: https://github.com/vampirefo/android_vendor_blu_Life_One_X2_Mini
I do not have the kernel source and I am hoping I can use a precompiled kernel. I have synced the LineageOS 13.0 repo and synced the device and vendor tree.
this is my output for "source build/envsetup.sh"
Code:
including device/blu/Life_One_X2_Mini/vendorsetup.sh
including device/generic/mini-emulator-arm64/vendorsetup.sh
including device/generic/mini-emulator-armv7-a-neon/vendorsetup.sh
including device/generic/mini-emulator-mips/vendorsetup.sh
including device/generic/mini-emulator-x86_64/vendorsetup.sh
including device/generic/mini-emulator-x86/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/bash_completion/git.bash
including vendor/cm/bash_completion/repo.bash
When I run the command "croot" I get "command not found". I assume it's the same as doing "cd ~/android/system". When I run the command "breakfast full_Life_One_X2_Mini" I get the following error:
Code:
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:238: *** Can not locate config makefile for product "lineage_full_Life_One_X2_Mini". Stop.
Device full_Life_One_X2_Mini not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Repository for full_Life_One_X2_Mini not found in the LineageOS Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:238: *** Can not locate config makefile for product "lineage_full_Life_One_X2_Mini". Stop.
** Don't have a product spec for: 'lineage_full_Life_One_X2_Mini'
** Do you have the right repo manifest?
** Warning: 'full_Life_One_X2_Mini' is using CM-based makefiles. This will be deprecated in the next major release.
build/core/product_config.mk:238: *** Can not locate config makefile for product "cm_full_Life_One_X2_Mini". Stop.
Device full_Life_One_X2_Mini not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Repository for full_Life_One_X2_Mini not found in the LineageOS Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:238: *** Can not locate config makefile for product "cm_full_Life_One_X2_Mini". Stop.
** Don't have a product spec for: 'cm_full_Life_One_X2_Mini'
** Do you have the right repo manifest?
I'm missing something obvious but I can't see it. I'm building this in Arch Linux
Thanks
srgrusso said:
I am trying to build LineageOS 13 for my device and I'm following this guide: https://forum.xda-developers.com/chef-central/android/how-to-build-lineageos-14-1-t3551484
I'm using this device tree: https://github.com/vampirefo/android_device_blu_Life_One_X2_Mini
and this vendor tree: https://github.com/vampirefo/android_vendor_blu_Life_One_X2_Mini
I do not have the kernel source and I am hoping I can use a precompiled kernel. I have synced the LineageOS 13.0 repo and synced the device and vendor tree.
this is my output for "source build/envsetup.sh"
Code:
including device/blu/Life_One_X2_Mini/vendorsetup.sh
including device/generic/mini-emulator-arm64/vendorsetup.sh
including device/generic/mini-emulator-armv7-a-neon/vendorsetup.sh
including device/generic/mini-emulator-mips/vendorsetup.sh
including device/generic/mini-emulator-x86_64/vendorsetup.sh
including device/generic/mini-emulator-x86/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/bash_completion/git.bash
including vendor/cm/bash_completion/repo.bash
When I run the command "croot" I get "command not found". I assume it's the same as doing "cd ~/android/system". When I run the command "breakfast full_Life_One_X2_Mini" I get the following error:
Code:
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:238: *** Can not locate config makefile for product "lineage_full_Life_One_X2_Mini". Stop.
Device full_Life_One_X2_Mini not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Repository for full_Life_One_X2_Mini not found in the LineageOS Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:238: *** Can not locate config makefile for product "lineage_full_Life_One_X2_Mini". Stop.
** Don't have a product spec for: 'lineage_full_Life_One_X2_Mini'
** Do you have the right repo manifest?
** Warning: 'full_Life_One_X2_Mini' is using CM-based makefiles. This will be deprecated in the next major release.
build/core/product_config.mk:238: *** Can not locate config makefile for product "cm_full_Life_One_X2_Mini". Stop.
Device full_Life_One_X2_Mini not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Repository for full_Life_One_X2_Mini not found in the LineageOS Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:238: *** Can not locate config makefile for product "cm_full_Life_One_X2_Mini". Stop.
** Don't have a product spec for: 'cm_full_Life_One_X2_Mini'
** Do you have the right repo manifest?
I'm missing something obvious but I can't see it. I'm building this in Arch Linux
Thanks
Click to expand...
Click to collapse
You may need to edit the(device tree) device.mk's to reflect the files you're working with
Sent from my N9515 using Tapatalk
bcrichster said:
You may need to edit the(device tree) device.mk's to reflect the files you're working with
Sent from my N9515 using Tapatalk
Click to expand...
Click to collapse
here is my vendorsetup.sh
Code:
add_lunch_combo full_Life_one_X2_Mini-userdebug
and my AndroidProducts.mk
Code:
PRODUCT_MAKEFILES := \
$(LOCAL_DIR)/full_Life_One_X2_Mini.mk
I have been looking at this for a week and still can't see what is wrong. I'm starting to feel stupid. Maybe someone sees something I don't. The person who built the tree has built a few roms with it so it has to be something I'm doing wrong. If you need to look at the rest of the tree here is the link.
https://github.com/vampirefo/android_device_blu_Life_One_X2_Mini
Edit: found my error in my vendorsetup.sh should be "full_Life_One_X2_Mini-userdebug" not "full_Life_one_X2_Mini-userdebug"
srgrusso said:
here is my vendorsetup.sh
Code:
add_lunch_combo full_Life_one_X2_Mini-userdebug
and my AndroidProducts.mk
Code:
PRODUCT_MAKEFILES := \
$(LOCAL_DIR)/full_Life_One_X2_Mini.mk
I have been looking at this for a week and still can't see what is wrong. I'm starting to feel stupid. Maybe someone sees something I don't. The person who built the tree has built a few roms with it so it has to be something I'm doing wrong. If you need to look at the rest of the tree here is the link.
https://github.com/vampirefo/android_device_blu_Life_One_X2_Mini
Click to expand...
Click to collapse
Use "lunch" instead of breakfast (device).. Lemme pull it up in a min and have a better look
Edit: another possibility could be LineageOS's change from vendor/cm to vendor/lineage that needs reflected in you lineage.mk
Sent from my N9515 using Tapatalk
bcrichster said:
Use "lunch" instead of breakfast (device).. Lemme pull it up in a min and have a better look
Edit: another possibility could be LineageOS's change from vendor/cm to vendor/lineage that needs reflected in you lineage.mk
Sent from my N9515 using Tapatalk
Click to expand...
Click to collapse
Ok i have made it a little further. now when I do lunch I get the following error
Code:
You're building on Linux
Breakfast menu... pick a combo:
1. aosp_arm64-eng 9. lineage_espresso3g-userdebug 17. lineage_toro-userdebug
2. aosp_arm-eng 10. lineage_espressowifi-userdebug 18. m_e_arm-userdebug
3. aosp_mips64-eng 11. lineage_ks01lte-userdebug 19. mini_emulator_arm64-userdebug
4. aosp_mips-eng 12. lineage_maguro-userdebug 20. mini_emulator_mips-userdebug
5. aosp_x86_64-eng 13. lineage_manta-userdebug 21. mini_emulator_x86_64-userdebug
6. aosp_x86-eng 14. lineage_mondrianwifi-userdebug 22. mini_emulator_x86-userdebug
7. full_Life_One_X2_Mini-userdebug 15. lineage_roth-userdebug
8. full_P780-userdebug 16. lineage_toroplus-userdebug
... and don't forget the bacon!
Which would you like? [aosp_arm-eng] 7
build/core/product_config.mk:243: *** _nic.PRODUCTS.[[device/blu/Life_One_X2_Mini/full_Life_One_X2_Mini.mk]]: "frameworks/native/build/phone-xxhdpi-4096-dalvik-heap.mk" does not exist. Stop.
Device Life_One_X2_Mini not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Repository for Life_One_X2_Mini not found in the LineageOS Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:243: *** _nic.PRODUCTS.[[device/blu/Life_One_X2_Mini/full_Life_One_X2_Mini.mk]]: "frameworks/native/build/phone-xxhdpi-4096-dalvik-heap.mk" does not exist. Stop.
** Don't have a product spec for: 'full_Life_One_X2_Mini'
** Do you have the right repo manifest?
could this be wrong?
Code:
#Dalvk Heap's
$(call inherit-product, frameworks/native/build/phone-xxhdpi-4096-dalvik-heap.mk)
$(call inherit-product, frameworks/native/build/phone-xxhdpi-4096-hwui-memory.mk)
Time to chase the errors.
thanks for helping me.
srgrusso said:
Ok i have made it a little further. now when I do lunch I get the following error
Code:
You're building on Linux
Breakfast menu... pick a combo:
1. aosp_arm64-eng 9. lineage_espresso3g-userdebug 17. lineage_toro-userdebug
2. aosp_arm-eng 10. lineage_espressowifi-userdebug 18. m_e_arm-userdebug
3. aosp_mips64-eng 11. lineage_ks01lte-userdebug 19. mini_emulator_arm64-userdebug
4. aosp_mips-eng 12. lineage_maguro-userdebug 20. mini_emulator_mips-userdebug
5. aosp_x86_64-eng 13. lineage_manta-userdebug 21. mini_emulator_x86_64-userdebug
6. aosp_x86-eng 14. lineage_mondrianwifi-userdebug 22. mini_emulator_x86-userdebug
7. full_Life_One_X2_Mini-userdebug 15. lineage_roth-userdebug
8. full_P780-userdebug 16. lineage_toroplus-userdebug
... and don't forget the bacon!
Which would you like? [aosp_arm-eng] 7
build/core/product_config.mk:243: *** _nic.PRODUCTS.[[device/blu/Life_One_X2_Mini/full_Life_One_X2_Mini.mk]]: "frameworks/native/build/phone-xxhdpi-4096-dalvik-heap.mk" does not exist. Stop.
Device Life_One_X2_Mini not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Repository for Life_One_X2_Mini not found in the LineageOS Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:243: *** _nic.PRODUCTS.[[device/blu/Life_One_X2_Mini/full_Life_One_X2_Mini.mk]]: "frameworks/native/build/phone-xxhdpi-4096-dalvik-heap.mk" does not exist. Stop.
** Don't have a product spec for: 'full_Life_One_X2_Mini'
** Do you have the right repo manifest?
could this be wrong?
Code:
#Dalvk Heap's
$(call inherit-product, frameworks/native/build/phone-xxhdpi-4096-dalvik-heap.mk)
$(call inherit-product, frameworks/native/build/phone-xxhdpi-4096-hwui-memory.mk)
Time to chase the errors.
thanks for helping me.
Click to expand...
Click to collapse
Ok I change "$(call inherit-product, frameworks/native/build/phone-xxhdpi-4096-dalvik-heap.mk)" to "$(call inherit-product, frameworks/native/build/phone-xxxhdpi-4096-dalvik-heap.mk)"
and changed "$(call inherit-product, frameworks/native/build/phone-xxhdpi-4096-hwui-memory.mk)" to "$(call inherit-product, frameworks/native/build/phone-xxxhdpi-4096-hwui-memory.mk)"
and here is my final result:
Code:
Trying dependencies-only mode on a non-existing device tree?
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=6.0.1
LINEAGE_VERSION=
TARGET_PRODUCT=full_Life_One_X2_Mini
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv7-a-neon
TARGET_2ND_CPU_VARIANT=cortex-a53
HOST_ARCH=x86_64
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.14.13-1-ARCH-x86_64-with-arch
HOST_BUILD_TYPE=release
BUILD_ID=MOI10E
OUT_DIR=/mnt/UserData/Projects/lineageos-13/android/system/out
============================================
I think I'm looking good for now
Thank you for your help. I'll post if I get anymore errors I can't figure out.
I'm stuck on this error.
Code:
make: *** No rule to make target '/.txt', needed by '/mnt/UserData/Projects/lineageos-13-blox2-mini/android/system/out/target/common/obj/PACKAGING/checkpublicapi-cm-last-timestamp'. Stop.
Edit: I got around this error by disabling api checking
srgrusso said:
I am trying to build LineageOS 13 for my device and I'm following this guide: https://forum.xda-developers.com/chef-central/android/how-to-build-lineageos-14-1-t3551484
I'm using this device tree: https://github.com/vampirefo/android_device_blu_Life_One_X2_Mini
and this vendor tree: https://github.com/vampirefo/android_vendor_blu_Life_One_X2_Mini
I do not have the kernel source and I am hoping I can use a precompiled kernel. I have synced the LineageOS 13.0 repo and synced the device and vendor tree.
this is my output for "source build/envsetup.sh"
When I run the command "croot" I get "command not found". I assume it's the same as doing "cd ~/android/system". When I run the command "breakfast full_Life_One_X2_Mini" I get the following error:
I'm missing something obvious but I can't see it. I'm building this in Arch Linux
Thanks
Click to expand...
Click to collapse
vendor should be lineage instead of cm. Check you make file.
I know development stopped for this phone but I was looking to see how difficult it would be to build my own ROM with PE 12 following this guide and it appears I need some binaries but I have no idea how to get that so I am failing here:
Code:
[email protected]:~/android/pe# source build/envsetup.sh
including vendor/aosp/vendorsetup.sh
[email protected]:~/android/pe# lunch aosp_albus-userdebug
02:35:02 Build sandboxing disabled due to nsjail error.
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
build/make/core/product_config.mk:160: error: Can not locate config makefile for product "aosp_albus".
02:35:02 dumpvars failed with: exit status 1
Device albus not found. Attempting to retrieve device repository from PixelExperience-Devices Github (http://github.com/PixelExperience-Devices).
Found repository: device_motorola_albus
Checking branch info
Calculated revision: twelve
Branch twelve not found
02:35:05 Build sandboxing disabled due to nsjail error.
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
build/make/core/product_config.mk:160: error: Can not locate config makefile for product "aosp_albus".
02:35:05 dumpvars failed with: exit status 1
02:35:07 Build sandboxing disabled due to nsjail error.
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
build/make/core/product_config.mk:160: error: Can not locate config makefile for product "aosp_albus".
02:35:08 dumpvars failed with: exit status 1
** Don't have a product spec for: 'aosp_albus'
** Do you have the right repo manifest?
Any idea how difficult it is to get past this and to get a PE 12 ROM built for this device? I assume once I get the binaries I would also need to modify some code and a bunch of files...
nmajin said:
I know development stopped for this phone but I was looking to see how difficult it would be to build my own ROM with PE 12 following this guide and it appears I need some binaries but I have no idea how to get that so I am failing here:
Code:
[email protected]:~/android/pe# source build/envsetup.sh
including vendor/aosp/vendorsetup.sh
[email protected]:~/android/pe# lunch aosp_albus-userdebug
02:35:02 Build sandboxing disabled due to nsjail error.
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
build/make/core/product_config.mk:160: error: Can not locate config makefile for product "aosp_albus".
02:35:02 dumpvars failed with: exit status 1
Device albus not found. Attempting to retrieve device repository from PixelExperience-Devices Github (http://github.com/PixelExperience-Devices).
Found repository: device_motorola_albus
Checking branch info
Calculated revision: twelve
Branch twelve not found
02:35:05 Build sandboxing disabled due to nsjail error.
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
build/make/core/product_config.mk:160: error: Can not locate config makefile for product "aosp_albus".
02:35:05 dumpvars failed with: exit status 1
02:35:07 Build sandboxing disabled due to nsjail error.
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
build/make/core/product_config.mk:160: error: Can not locate config makefile for product "aosp_albus".
02:35:08 dumpvars failed with: exit status 1
** Don't have a product spec for: 'aosp_albus'
** Do you have the right repo manifest?
Any idea how difficult it is to get past this and to get a PE 12 ROM built for this device? I assume once I get the binaries I would also need to modify some code and a bunch of files...
Click to expand...
Click to collapse
You are missing all the trees for the device; as you seem to have no clue i'd recommend you at least start by building A11. A12 won't boot on albus without significant modifications to the rom, which PE has not included in it's upstream.
For building a rom you need:
The rom structure (Duh)
The device tree (usually called device_brand_codename, in this case device_motorola_albus and store in device/motorola/albus to be properly detected)
The kernel tree (which usually inherits the name of the SOC, in this case msm8953 and goes into kernel/msm8953)
Vendor tree (which follows the same naming convention as device tree and goes in vendor/motorola/albus)
marcost22 said:
You are missing all the trees for the device; as you seem to have no clue i'd recommend you at least start by building A11. A12 won't boot on albus without significant modifications to the rom, which PE has not included in it's upstream.
For building a rom you need:
The rom structure (Duh)
The device tree (usually called device_brand_codename, in this case device_motorola_albus and store in device/motorola/albus to be properly detected)
The kernel tree (which usually inherits the name of the SOC, in this case msm8953 and goes into kernel/msm8953)
Vendor tree (which follows the same naming convention as device tree and goes in vendor/motorola/albus)
Click to expand...
Click to collapse
Thanks for the reply, and yea maybe I’ll start with PE 11 then. Would building that provide the trees for the device or how do you go about getting those? I did read about the modifications needed for PE 12 to get around the iptables drop but willing to mess with it and only plan to use this phone for the projector mod.
nmajin said:
Thanks for the reply, and yea maybe I’ll start with PE 11 then. Would building that provide the trees for the device or how do you go about getting those? I did read about the modifications needed for PE 12 to get around the iptables drop but willing to mess with it and only plan to use this phone for the projector mod.
Click to expand...
Click to collapse
Given the fact that this device had official PE 11 support, those trees (for A11) would be hosted on the PE-Device github. The vendor tree however would be hosted in their gitlab (or you can generate it with the device tree, by having the device plugged in and running extract-files