FORUMS
Remove All Ads from XDA

✦✦✦ [GUIDE] Build LineageOS ✦ How To use Github ✦✦✦

3,380 posts
Thanks Meter: 4,690
 
By FSadino, Retired Forum Moderator on 6th February 2017, 03:26 AM
Post Reply Email Thread
2nd August 2019, 09:49 AM |#441  
FSadino's Avatar
OP Retired Forum Moderator
Flag Skynet
Thanks Meter: 4,690
 
Donate to Me
More
Updated for Lineage 16.0 branch build
26th August 2019, 09:28 AM |#442  
Junior Member
Thanks Meter: 1
 
More
Query on unsupported device
Quote:
Originally Posted by Relentless Terminator

Reserved

Thanks for this excellent guide. I just want to know the best method for pulling proprietary blobs if the device is not part of the Muppets list? In fact not lineage rom exists for the device. Then how should I go about it?
Thanks a lot in advance
26th August 2019, 09:43 AM |#443  
FSadino's Avatar
OP Retired Forum Moderator
Flag Skynet
Thanks Meter: 4,690
 
Donate to Me
More
Quote:
Originally Posted by ptrtoptr

Thanks for this excellent guide. I just want to know the best method for pulling proprietary blobs if the device is not part of the Muppets list? In fact not lineage rom exists for the device. Then how should I go about it?
Thanks a lot in advance

9. Extract proprietary blobs
Method 1
28th August 2019, 01:36 PM |#444  
Junior Member
Thanks Meter: 1
 
More
Query on Unsupported device
Quote:
Originally Posted by Relentless Terminator

9. Extract proprietary blobs
Method 1

Many thanks for your quick response. Method 1 refers to using extract-files.sh

But AFAIK, extract-files.sh needs a list of proprietary files to extract. If the device is unsupported how will I know which files should be extracted or not (to put in this list).

Thanks in advance for your response. Much appreciated
28th August 2019, 02:02 PM |#445  
Senior Member
Thanks Meter: 246
 
More
Quote:
Originally Posted by ptrtoptr

Many thanks for your quick response. Method 1 refers to using extract-files.sh



But AFAIK, extract-files.sh needs a list of proprietary files to extract. If the device is unsupported how will I know which files should be extracted or not (to put in this list).



Thanks in advance for your response. Much appreciated

Try an error method

Gesendet von meinem Pixel 2 XL mit Tapatalk
28th August 2019, 02:34 PM |#446  
Junior Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by tschmid

Try an error method

Gesendet von meinem Pixel 2 XL mit Tapatalk

Many thanks for your response. But since I am new to this, I am not sure I understand what that means. Could you please explain a little more? Thanks
28th August 2019, 07:52 PM |#447  
Senior Member
Thanks Meter: 246
 
More
Quote:
Originally Posted by ptrtoptr

Many thanks for your response. But since I am new to this, I am not sure I understand what that means. Could you please explain a little more? Thanks

Example if you've a Samsung device have a look at device tree of a Samsung device and copy files 1 per 1 (exp bin files for WiFi) then build and try

Gesendet von meinem Pixel 2 XL mit Tapatalk
29th August 2019, 06:35 AM |#448  
Junior Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by tschmid

Example if you've a Samsung device have a look at device tree of a Samsung device and copy files 1 per 1 (exp bin files for WiFi) then build and try

Gesendet von meinem Pixel 2 XL mit Tapatalk

Great! Thanks, will try
The Following User Says Thank You to ptrtoptr For This Useful Post: [ View ] Gift ptrtoptr Ad-Free
17th November 2019, 01:35 PM |#449  
Junior Member
Thanks Meter: 9
 
More
Is generic build for emulator supported and runnable?
I am trying to build LOS 16.0 for emulator. Build is successful but booting fails because it can not find root device /dev/vda1. Here is what I did:

Code:
$ repo init -u https://github.com/LineageOS/android.git -b lineage-16.0
$ repo sync
$ source build/envsetup.sh
# also tried lineage_x86-userdebug and lineage_arm-userdebug on next lines with the same result
$ breakfast lineage_x86_64-userdebug
$ brunch lineage_x86_64-userdebug
After trying it to run in emulator it does not boot:

Code:
$ emulator -show-kernel
...
[    0.000000] Linux version 4.4.124+ ([email protected]) (gcc version 4.9.x 20150123 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Aug 16 04:59:43 UTC 2018
[    0.000000] Command line: qemu=1 no_timer_check androidboot.hardware=ranchu clocksource=pit no-kvmclock console=ttyS0,38400 android.qemud=1 android.checkjni=1 qemu.gles=1 qemu.encrypt=1 qemu.opengles.version=131072 [email protected] qemu.wifi=1 mac80211_hwsim.channels=2 androidboot.android_dt_dir=/sys/bus/platform/devices/ANDR0001:00/properties/android/ skip_initramfs rootwait ro init=/init root=/dev/vda1 loop.max_part=7 ramoops.mem_address=0xff018000 ramoops.mem_size=0x10000 memmap=0x10000$0xff018000 qemu.dalvik.vm.heapsize=192m
...
[    0.984823] VFS: Cannot open root device "vda1" or unknown-block(253,1): error -6
[    0.985395] Please append a correct "root=" boot option; here are the available partitions:
[    0.986019] 0100           16384 ram0  (driver?)
[    0.986385] 0101           16384 ram1  (driver?)
[    0.986760] 0102           16384 ram2  (driver?)
[    0.987134] 0103           16384 ram3  (driver?)
[    0.987496] 0104           16384 ram4  (driver?)
[    0.987855] 0105           16384 ram5  (driver?)
[    0.988224] 0106           16384 ram6  (driver?)
[    0.988586] 0107           16384 ram7  (driver?)
[    0.988950] 0108           16384 ram8  (driver?)
[    0.989311] 0109           16384 ram9  (driver?)
[    0.989682] 010a           16384 ram10  (driver?)
[    0.990098] 010b           16384 ram11  (driver?)
[    0.990475] 010c           16384 ram12  (driver?)
[    0.990843] 010d           16384 ram13  (driver?)
[    0.991215] 010e           16384 ram14  (driver?)
[    0.991587] 010f           16384 ram15  (driver?)
[    0.991957] fd00         1338980 vda  driver: virtio_blk
[    0.992395] fd10              56 vdb  driver: virtio_blk
[    0.992809] fd20         2097152 vdc  driver: virtio_blk
[    0.993229] fd30            1024 vdd  driver: virtio_blk
[    0.993643] fd40           63092 vde  driver: virtio_blk
[    0.994060] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(253,1)
...
Partition /dev/vda1 does not exists only /dev/vda exists. Kernel however is started with parameter root=/dev/vda1. Why this misalignment? Am I missing something?

Is running LOS in emulator officially supported? Has anyone tried it? Am I using correct combo? If not, what is the right one and what is the purpose of lineage_{x86,x86_64,arm,arm64}-userdebug combos?

Thanks for any hint.
23rd December 2019, 02:34 PM |#450  
Senior Member
Thanks Meter: 18
 
More
hi
i see this error after brunch command :

error: vendor/xiaomi/msm8953-common/Android.bp:22:1: module "[email protected]" variant "android_arm64_armv8-a_core_shared": module source path "vendor/xiaomi/msm8953-common/proprietary/lib64/[email protected]" does not exist


and i dont know what should i do!!![COLOR="Silver"]
23rd December 2019, 02:47 PM |#451  
FSadino's Avatar
OP Retired Forum Moderator
Flag Skynet
Thanks Meter: 4,690
 
Donate to Me
More
Quote:
Originally Posted by babakhad

hi
i see this error after brunch command :

error: vendor/xiaomi/msm8953-common/Android.bp:22:1: module "[email protected]" variant "android_arm64_armv8-a_core_shared": module source path "vendor/xiaomi/msm8953-common/proprietary/lib64/[email protected]" does not exist


and i dont know what should i do!!![COLOR="Silver"]

Missing proprietary files
The Following User Says Thank You to FSadino For This Useful Post: [ View ] Gift FSadino Ad-Free
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes