[ROM][UNOFFICIAL] LineageOS-18.1 [mako]

Search This thread

bpham1

Member
Jan 18, 2013
13
3
I'm running lineage-16.0-20210311, and am having issues with SOD. Switching from 17.1, which had been running very smooth for 3 months. I will try to get some logs next ime. This happens constantly.
 
Last edited:

voron00

Senior Member
Mar 8, 2011
343
1,102
Google Nexus 4
LeEco Le Pro3
Sorry if I sound naive, but why is 16.0 better? I need help understanding why since it's no longer supported. I get that there's problems with 18.1, but why is 17.1 troublesome?
It has mostly to do with frequent build failures due to low RAM for me, but also some features such as miracast are not supported in 17.1. I'll try to build a 17.1 tonight and upload it, but it will be untested.
 

Ashwynn_Thorne

New member
Apr 26, 2021
3
0
It has mostly to do with frequent build failures due to low RAM for me, but also some features such as miracast are not supported in 17.1. I'll try to build a 17.1 tonight and upload it, but it will be untested.
Ahh, I see, thanks for letting me know!

Woa!!! Thanks so much for that! I really wasn't fishing for that at all. That's so great though, thanks!
 
  • Wow
Reactions: voron00

mickeymk

New member
May 2, 2021
3
0
I am new to the forum, so please bear with me.
Is it still possible to flash lineageos 16 and GAPPS without repartition? I noted in the early posts that you could flash gapps pico version that excluded the text to speech.
Without trying to read all 31 pages, is that solution still viable?
 

Akhilesh S V

Senior Member
I am new to the forum, so please bear with me.
Is it still possible to flash lineageos 16 and GAPPS without repartition? I noted in the early posts that you could flash gapps pico version that excluded the text to speech.
Without trying to read all 31 pages, is that solution still viable?
Yes it is possible. After flashing LOS 16.0 delete System apps like Calendar, Calculator, Jelly, etc and flash Gapps Pico.
 

Massedil

Senior Member
Dec 7, 2016
83
33
Paris
Hello @voron00,

Thank you for your great work on the Nexus 4.

I have seen here that you solved a TWRP bug to allow decrypting data partition.

I tried with the TWRP built by you (3.5.2_9-0) without success :

Code:
I:Is encrypted, do decrypt page first
I:Switching packages (TWRP)
I:Set page: 'decrypt'
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 0
I:TWFunc::Set_Brightness: Setting brightness control to 114
I:Set overlay: ''
I:Set page: 'trydecrypt'
I:operation_start: 'Decrypt'
D:crypt_ftr->fs_size = 11167744
I:Using scrypt with keymaster for cryptfs KDF
I:TWRP keymaster max API: 1
I:Signing safely-padded objectcould not find any keystore module
Failed to init keymaster 0/1
E:Keymaster signing failedE:kdf failedW:failure decrypting master keyE:Failed to decrypt master key
E:Password did not matchFailed to decrypt data.
I:Set page: 'decrypt'
I:operation_end - status=1
I:Set page: 'trydecrypt'
I:operation_start: 'Decrypt'
D:crypt_ftr->fs_size = 11167744
I:Using scrypt with keymaster for cryptfs KDF
I:TWRP keymaster max API: 1
I:Signing safely-padded objectcould not find any keystore module
Failed to init keymaster 0/1
E:Keymaster signing failedE:kdf failedW:failure decrypting master keyE:Failed to decrypt master key
E:Password did not matchFailed to decrypt data.
I:Set page: 'decrypt'
I:operation_end - status=1
I:Set page: 'trydecrypt'
I:operation_start: 'Decrypt'
D:crypt_ftr->fs_size = 11167744
I:Using scrypt with keymaster for cryptfs KDF
I:TWRP keymaster max API: 1
I:Signing safely-padded objectcould not find any keystore module
Failed to init keymaster 0/1
E:Keymaster signing failedE:kdf failedW:failure decrypting master keyE:Failed to decrypt master key
E:Password did not matchFailed to decrypt data.


The good password unlock correctely LineageOS (version lineage-17.1-20210521-UNOFFICIAL-mako), but impossible to decrypt the /data partition in TWRP.

Do I do something wrong ?
 

voron00

Senior Member
Mar 8, 2011
343
1,102
Google Nexus 4
LeEco Le Pro3
Hello @voron00,

Thank you for your great work on the Nexus 4.

I have seen here that you solved a TWRP bug to allow decrypting data partition.

I tried with the TWRP built by you (3.5.2_9-0) without success :

Code:
I:Is encrypted, do decrypt page first
I:Switching packages (TWRP)
I:Set page: 'decrypt'
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 0
I:TWFunc::Set_Brightness: Setting brightness control to 114
I:Set overlay: ''
I:Set page: 'trydecrypt'
I:operation_start: 'Decrypt'
D:crypt_ftr->fs_size = 11167744
I:Using scrypt with keymaster for cryptfs KDF
I:TWRP keymaster max API: 1
I:Signing safely-padded objectcould not find any keystore module
Failed to init keymaster 0/1
E:Keymaster signing failedE:kdf failedW:failure decrypting master keyE:Failed to decrypt master key
E:Password did not matchFailed to decrypt data.
I:Set page: 'decrypt'
I:operation_end - status=1
I:Set page: 'trydecrypt'
I:operation_start: 'Decrypt'
D:crypt_ftr->fs_size = 11167744
I:Using scrypt with keymaster for cryptfs KDF
I:TWRP keymaster max API: 1
I:Signing safely-padded objectcould not find any keystore module
Failed to init keymaster 0/1
E:Keymaster signing failedE:kdf failedW:failure decrypting master keyE:Failed to decrypt master key
E:Password did not matchFailed to decrypt data.
I:Set page: 'decrypt'
I:operation_end - status=1
I:Set page: 'trydecrypt'
I:operation_start: 'Decrypt'
D:crypt_ftr->fs_size = 11167744
I:Using scrypt with keymaster for cryptfs KDF
I:TWRP keymaster max API: 1
I:Signing safely-padded objectcould not find any keystore module
Failed to init keymaster 0/1
E:Keymaster signing failedE:kdf failedW:failure decrypting master keyE:Failed to decrypt master key
E:Password did not matchFailed to decrypt data.


The good password unlock correctely LineageOS (version lineage-17.1-20210521-UNOFFICIAL-mako), but impossible to decrypt the /data partition in TWRP.

Do I do something wrong ?
Ahh, looks like it only works with 18.1 encryption, sorry.

Fresh 16.0 build with June security patches: lineage-16.0-20210617-UNOFFICIAL-mako-signed
 

wartle.S

Senior Member
Mar 4, 2014
129
213
Cebu
Google Pixel 4
Realme X2 Pro
Is it possible to have a link to your build ?
I will be building a new build based on @voron00's latest device tree commit

But if you want to test, here it is:

ROM: lineage-18.1-20210609-UNOFFICIAL-mako.zip [new build is up!]
GAPPS-GO: antman_gapps-arm-11.0-go-20210609-mako.zip [new build is up!]
BUGS: no radio/baseband

Note: this is Lineage Go based thanks to @acroreiser for the GApps Go as Go related commits and @voron00 for keeping our mako alive.
 
Last edited:
  • Like
Reactions: Massedil

wartle.S

Senior Member
Mar 4, 2014
129
213
Cebu
Google Pixel 4
Realme X2 Pro
My hard drive with linux/build setup has died today so i guess that will mark the end of developement of mako for me. This device has suffered enough already and i think 16.0 was the last usable version with decent performance. So build from June 17 was the last one from me. Maybe I'll see you around.
I'm sorry to read this. Thanks man for maintaining mako all these years.

Anyways, I have built a new Lineage 18.1 with Android Go.

Changelogs:
- June security patch
- Radio/baseband fix thanks to @voron00

ROM: lineage-18.1-20210708-UNOFFICIAL-mako.zip
GAPPS GO: antman_gapps-arm-11.0-go-20210708-mako.zip

Sources:
Device: https://github.com/wartle/android_device_lge_mako/tree/lineage-go
GApps Go: https://github.com/wartle/gapps_android_11_go

Credits:
@voron00
@acroreiser
Lineage OS team

Screenshots:
Screenshot_20210708-183249_Trebuchet.jpgScreenshot_20210708-183258_Trebuchet.jpgScreenshot_20210708-183308_Settings.jpgScreenshot_20210708-183354_Settings.jpgScreenshot_20210708-183408_Android_System.jpg
 
Last edited:

skoczo

Member
Dec 30, 2013
31
0
I have a problem with missing bluetooth address after lineage os installation. When i flash back to stock 4.2.2 i can see bluetooth address and bluetooth is working. Do you have any idea why i have this issue and how to fix it? Where bluetooth address is stored? On which partition?
address.png
IMG_20210727_204018.jpg


In logs i found
07-27 11:51:56.448 1396 1396 F DEBUG : pid: 1226, tid: 1253, name: HwBinder:1226_1 >>> /vendor/bin/hw/android.hardware.bluetooth@1.0-service <<< 07-27 11:51:56.448 1396 1396 F DEBUG : uid: 1002 07-27 11:51:56.448 1396 1396 F DEBUG : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr -------- [B]07-27 11:51:56.448 1396 1396 F DEBUG : Abort message: 'Open: No Bluetooth Address!'[/B] 07-27 11:51:56.448 1396 1396 F DEBUG : r0 00000000 r1 000004e5 r2 00000006 r3 b3209790 07-27 11:51:56.448 1396 1396 F DEBUG : r4 b32097a4 r5 b3209788 r6 000004ca r7 0000016b 07-27 11:51:56.448 1396 1396 F DEBUG : r8 b32097a0 r9 b3209790 r10 b32097c0 r11 b32097b0 07-27 11:51:56.448 1396 1396 F DEBUG : ip 000004e5 sp b3209760 lr b39a4c03 pc b39a4c16 07-27 11:51:56.487 1396 1396 F DEBUG : 07-27 11:51:56.487 1396 1396 F DEBUG : backtrace: 07-27 11:51:56.487 1396 1396 F DEBUG : #00 pc 0005ec16 /apex/com.android.runtime/lib/bionic/libc.so (abort+166) (BuildId: 1c34385a63ae9f807822c87c6b4126d2) 07-27 11:51:56.488 1396 1396 F DEBUG : #01 pc 00005a1d /system/lib/liblog.so (__android_log_assert+176) (BuildId: e8dc42b680d3bfbe493b7e4247c0accd)
 

voron00

Senior Member
Mar 8, 2011
343
1,102
Google Nexus 4
LeEco Le Pro3
I have a problem with missing bluetooth address after lineage os installation. When i flash back to stock 4.2.2 i can see bluetooth address and bluetooth is working. Do you have any idea why i have this issue and how to fix it? Where bluetooth address is stored? On which partition?View attachment 5372009View attachment 5372011

In logs i found
07-27 11:51:56.448 1396 1396 F DEBUG : pid: 1226, tid: 1253, name: HwBinder:1226_1 >>> /vendor/bin/hw/android.hardware.bluetooth@1.0-service <<< 07-27 11:51:56.448 1396 1396 F DEBUG : uid: 1002 07-27 11:51:56.448 1396 1396 F DEBUG : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr -------- [B]07-27 11:51:56.448 1396 1396 F DEBUG : Abort message: 'Open: No Bluetooth Address!'[/B] 07-27 11:51:56.448 1396 1396 F DEBUG : r0 00000000 r1 000004e5 r2 00000006 r3 b3209790 07-27 11:51:56.448 1396 1396 F DEBUG : r4 b32097a4 r5 b3209788 r6 000004ca r7 0000016b 07-27 11:51:56.448 1396 1396 F DEBUG : r8 b32097a0 r9 b3209790 r10 b32097c0 r11 b32097b0 07-27 11:51:56.448 1396 1396 F DEBUG : ip 000004e5 sp b3209760 lr b39a4c03 pc b39a4c16 07-27 11:51:56.487 1396 1396 F DEBUG : 07-27 11:51:56.487 1396 1396 F DEBUG : backtrace: 07-27 11:51:56.487 1396 1396 F DEBUG : #00 pc 0005ec16 /apex/com.android.runtime/lib/bionic/libc.so (abort+166) (BuildId: 1c34385a63ae9f807822c87c6b4126d2) 07-27 11:51:56.488 1396 1396 F DEBUG : #01 pc 00005a1d /system/lib/liblog.so (__android_log_assert+176) (BuildId: e8dc42b680d3bfbe493b7e4247c0accd)

 

Top Liked Posts