how to build an Android image from lineage source for raspberry pi 3?
I’ve followed all the instructions from lineage website, but When I was applying breakfast command not able to see my device vendor name in device folder.
Related
Hi everyone,
I'm currently working on building Lineage OS 13, which is unsupported on the Nexus 7 2013. My device has WiFi issues with 14.1 and none of the Marshmallow ROMs incorporate a fix for the Krack vulnerability. Since this fix is already part of the cm-13.0 branch, I've been trying to build it but running into the following error when I run "breakfast flo".
Code:
build/core/product_config.mk:257: *** No matches for product "lineage_flo". Stop.
Device flo not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
I have already incorporated the Muppet's proprietary blobs for Flo but don't know how to deal with this error. I have experience with the Linux command line and programming using Java but am new to ROM-building.
flamingspartan3 said:
Hi everyone,
I'm currently working on building Lineage OS 13, which is unsupported on the Nexus 7 2013. My device has WiFi issues with 14.1 and none of the Marshmallow ROMs incorporate a fix for the Krack vulnerability. Since this fix is already part of the cm-13.0 branch, I've been trying to build it but running into the following error when I run "breakfast flo".
Code:
build/core/product_config.mk:257: *** No matches for product "lineage_flo". Stop.
Device flo not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
I have already incorporated the Muppet's proprietary blobs for Flo but don't know how to deal with this error. I have experience with the Linux command line and programming using Java but am new to ROM-building.
Click to expand...
Click to collapse
You will need to apply device tree rebrand like it's done in 14.1: https://github.com/LineageOS/android_device_asus_flo/commit/e596a332b44ea40769fc516c451728b1cd58eb2b
flex1911 said:
You will need to apply device tree rebrand like it's done in 14.1: https://github.com/LineageOS/android_device_asus_flo/commit/e596a332b44ea40769fc516c451728b1cd58eb2b
Click to expand...
Click to collapse
Thanks for the help! I was able to get it to work by running 'lunch cm_flo-userdebug' and then mka.
Are you sure the Krack fix isn't already in 14.1:
https://www.lineageos.org/Changelog-15/
KRACK Wi-Fi vulnerability has been fixed in both LineageOS 14.1 and 13.0
Click to expand...
Click to collapse
Hi!
I have been looking some time for a Lineage 16.0 device tree to build Lineage 16.0 to this phone and as I forked the 17.1 repo made by whatawurst I started to change it accordingly and the reason for it is that I intend to build libhybris with Lineage 16.0 as a base since there's no hybris-17.1....... YET (It's coming though).... to it so that I may boot Sailfish OS as well.
I had to change the standard local manifest and make my own repos for obvious reasons.
Now here's the fun part.
I extracted the blobs from the phone and put them in my vendor repo and synced without a problem.
I then ran source build/envsetup.sh && lunch lineage_beyond2lte-userdebug and it worked OK.
As I started to build Lineage I got an error about a missing ril file and YES I suspect that it's missing a lot more files as well.
I have no clue why ./extract-files.sh in /android/lineage/device/samsung/beyond2lte looked for files that aren't in the stock vendor directory.
I guess it differs from Lineage version to another.
I also know that Lineage 16.0 won't boot on a Q bootloader, but I don't intend to boot Lineage after it's built.
I'd appreciate if someone here would be kind enough to help me fix any missing files so that Lineage 16.0 will build.
When I can confirm that it builds I'll start to try: https://github.com/mer-hybris/hybris-patches/tree/hybris-16.0
Here's my device tree for Lineage 16.0: https://github.com/Umeaboy/android_device_samsung_beyond2lte
I am building Lineage OS 17.1 for a Samsung Galaxy S7. I need to modify the kernel configuration. I would really appreciate it if someone could point me to how I could do this... I need to add some device drivers.
Thanks
Y=
Hi YileKu,
Can you share the steps to build 17.1 for galaxy S7? I only found the guide to build cm14.1 from official website, but I'm not success
Hi. I want to try to build lineage os 17/18 for my old phone. I have env and I already build package for other phone. For Nexus 4 there and only some old lineage os 15 builds. How to prepare lineage os 18 based on lineage os 15? Is it possible or maybe it needs to be done from scratch. Is there any instruction how to do this?
Porting a ROM means there's a similar device with a working LineageOS on it. Which means it's already built, and only small modifications to make it stable for you.
Porting doesn't work the way you described. You can't build Android 12 on top of Android 8, every new major Android update, Google releases a new source code.
Then, manufacturers/developers modify it to their sweets. What you want to do is to build LineageOS 18/17 for an unsupported device. There's a lot of guides online about it. The context matters.
Can you share some links about building lineage os for unsupported devices? Will it help somehow when there are some old versions builds?
How can i exctract boot.img (for magisk, bootloader unlocked) from updated phone? This model have not twrp or other custom recovery.
As I know this device is like the Motorola G9 Play due to model is XT2083-8, maybe you could contact or try any method to the before mentioned model.
Motorola G9 Play twrp recovery works (zip installing )
mishak750 said:
Motorola G9 Play twrp recovery works (zip installing )
Click to expand...
Click to collapse
any rom tested??? Did you have the dual sim version?
my defy dual sim. i install zip via recovery (magisk).
Rom what i test (install via fastboot) lineage os 19-18(not work nfc) crdroid (android 10).
mishak750 said:
Rom what i test (install via fastboot) lineage os 19-18(not work nfc) crdroid (android 10).
Click to expand...
Click to collapse
Any link to it? Mine is single SIM (XT2083-8), also device processor is SM665, I don't know if there's any difference with SM662.
What link?
mishak750 said:
What link?
Click to expand...
Click to collapse
the link used for recovery and os
twrp part function work (used only for install magisk!!) taken from motorola g9 play branch
lineage os 19
[GSI][12] LineageOS 19.x GSI (A64B/64B)
Background: This is a natural continuation/extension of the LineageOS 18.x GSIs I've been making since 2020. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and...
forum.xda-developers.com
mishak750 said:
Rom what i test (install via fastboot) lineage os 19-18(not work nfc) crdroid (android 10).
Click to expand...
Click to collapse
Hello.
Is there any community ROM for Defy?
Link?
Thank.
The official Android 11 is RZD 31.13 Security Update about November 2021
Only gsi (treble).
This treble ?
Home
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Any chance of community rom?
It's a shame, because Defy is one of the few civilian-looking rugged phones...
Android 13 AOSP GSI Rom works.
Generic System Image releases | Platform | Android Developers
developer.android.com
ARM64+GMS gsi_gms_arm64-exp-T1B3.221003.003-9173718-1aa73579.zip
or
ARM64 aosp_arm64-exp-T1B3.221003.003-9173718-7eba5aba.zip
Tested with unlocked bootloader
You can flash system.img and vbmeta.img with fastbootd.
fastboot flash system system.img fastboot flash vbmeta vbmeta.img fastboot -w (wipes all data)
Click to expand...
Click to collapse
Maybe you need this to fix resize system partition error.
fastboot delete-logical-partition product
You can enter fastbootd via stock recovery.
What is fastbootd? How to Enable and Boot?
Google introduced the Android 10 operating system back in September 2019. Android 10 brought in new support for resizable partition which relocates the
www.getdroidtips.com
Edit:
phhusson Android 12 builds works too. (system-squeak-arm64-ab-vndklite-gapps)
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Andy Yan's personal builds // GSI Lineage 20 works
[GSI][12] LineageOS 19.x GSI (A64B/64B)
Background: This is a natural continuation/extension of the LineageOS 18.x GSIs I've been making since 2020. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and...
forum.xda-developers.com
lineage-20.0-20221109-UNOFFICIAL-gsi_arm64_vS.img