Database Develop

Porting (Kang) Keymaster Firmware

Anyone ever attempted to kang Keymaster Firmware from a different device? I have tried the firmware from bacon, hammerhead, and g3. I have tried with and without the TARGET_KEYMASTER_WAIT_FOR_QSEE flag.
See these commits:
https://github.com/blastagator/cm_d...mmit/a50026b03824e65e852dc975e369f89a6e8e33a6
https://github.com/blastagator/them...mmit/b5951a58a4df5cabc8f928fae2476629cc73b1fa
https://github.com/blastagator/LGG2_Kernel/commit/655b64e43cbcd4550671cadf8bc19b6c495b3190
The result is always the same in dmesg:
Code:
[0][4371: keystore]QSEECOM: qseecom_load_app: App (keymaster) does'nt exist, loading apps for first time
[0][4371: keystore]QSEECOM: qseecom_load_app: scm_call failed resp.result unknown, -12
[0][4371: keystore]QSEECOM: qseecom_ioctl: failed load_app request: -14
This is the only related thing I've found:
http://androidforums.com/threads/beta-4-4-2-stock-kitkat.952314/
Very old and no answer.
I suspect the firmware might be signed to the device type and thus we might be SOL, but I was bored and messing around. Alternatively, perhaps the kernel is missing something. I looked for commits that may be missing from qseecom.c and smc.c, but nothing jumped out at me.
Figured I'd post a dev thread and maybe we can find an answer.
edit: This is my cheat sheet to myself, so far, for how to add hardware crypto to a device:
Code:
Needed commits:
Probable problem: G2 has no keymaster firmware, need to borrow someone else's
See this commit:
https://github.com/blastagator/themuppets_proprietary_vendor_lge/commit/b5951a58a4df5cabc8f928fae2476629cc73b1fa
g2-common/g2-common-vendor-blobs.mk
+ vendor/lge/g2-common/proprietary/vendor/firmware/keymaster/keymaster.b00:system/vendor/firmware/keymaster/keymaster.b00 \
+ vendor/lge/g2-common/proprietary/vendor/firmware/keymaster/keymaster.b01:system/vendor/firmware/keymaster/keymaster.b01 \
+ vendor/lge/g2-common/proprietary/vendor/firmware/keymaster/keymaster.b02:system/vendor/firmware/keymaster/keymaster.b02 \
+ vendor/lge/g2-common/proprietary/vendor/firmware/keymaster/keymaster.b03:system/vendor/firmware/keymaster/keymaster.b03 \
+ vendor/lge/g2-common/proprietary/vendor/firmware/keymaster/keymaster.mdt:system/vendor/firmware/keymaster/keymaster.mdt \
And, actually put the files in that folder, so they get copied.
CRUCIAL: MUST match this name and path!!! (Other things like keymaste.mdt and such are for if the files are in the modem)
Also, symlinks are NOT needed if we put the file into proprietary like this!
Device commit:
https://github.com/blastagator/cm_device_lge_g2-common/commit/a50026b03824e65e852dc975e369f89a6e8e33a6
BoardConfig
+# Encryption / Keymaster
+TARGET_HW_DISK_ENCRYPTION := true
+TARGET_KEYMASTER_WAIT_FOR_QSEE := true
+
NOTE: Not sure about wait_for_qsee --- MAYBE needed????
g2.mk
+# Keystore
+PRODUCT_PACKAGES += \
+ keystore.msm8974
+
Note: The resulting /system image will have TWO keystore files, this is correct
I checked a bacon image to confirm there are supposed to be two. One labeled msm8974 & one labeled default
Probable needed kernel changes:
Config
-# CONFIG_DM_REQ_CRYPT is not set
+CONFIG_DM_REQ_CRYPT=y
-# CONFIG_CRYPTO_DEV_QCRYPTO is not set
+CONFIG_CRYPTO_DEV_QCRYPTO=y
If dm-req-crypt.c doesn't build, need this commit:
https://github.com/blastagator/LGG2_Kernel/commit/50ddb1a013065cefa35151e9ded72aadcd210611
(platform: msm: Fix compile when CONFIG_PFT is not set)
include/linux/pft.h
-static inline int pft_get_key_index(struct inode *inode, u32 *key_index,
+static inline int pft_get_key_index(struct bio *bio, u32 *key_index,

blastagator said:
Anyone ever attempted to kang Keymaster Firmware from a different device?
Click to expand...
Click to collapse
Maybe, you have to add something like this:
https://github.com/CyanogenMod/andr...mmit/595cf776441389d147f4b4e7ec316aa02d74d14e

Rangell11 said:
Maybe, you have to add something like this:
https://github.com/CyanogenMod/andr...mmit/595cf776441389d147f4b4e7ec316aa02d74d14e
Click to expand...
Click to collapse
That is for if the firmware is in the /modem partition. I know it's finding the firmware because if I remove the files the error messages go away and the keystore service crashes without a specific error.
I've also insured permissions 0644 on the files and I've put selinux in permissive to see if that would help, but same errors.

blastagator said:
I've also insured permissions 0644 on the files and I've put selinux in permissive to see if that would help, but same errors.
Click to expand...
Click to collapse
Like this??
http://review.cyanogenmod.org/#/c/155981/
Did you try this?
http://review.cyanogenmod.org/#/c/137146/
PS:
I think our G2 not support TARGET_KEYMASTER_WAIT_FOR_QSEE flag.
http://review.cyanogenmod.org/#/c/102410/

Rangell11 said:
Like this??
http://review.cyanogenmod.org/#/c/155981/
Click to expand...
Click to collapse
After clean boot I used "setenforce 0" to see if it would load after that. (keystore service keeps repeatedly attempting to load in the background and can be seen with 'dmesg'.) Disabling enforcing should have solved any selinux problem, but the same error persisted.
Rangell11 said:
Did you try this?
http://review.cyanogenmod.org/#/c/137146/
Click to expand...
Click to collapse
Keymaster is in the system partition and not the modem partition (for my tests anyway), so this wouldn't be needed. I will say the contact was not 'context=ubject_r:firmware_file:s0', it was listed as a regular system file, however, in permissive mode this should not matter. Maybe I will try another test when I have some time where the ROM is compiled permissive and the files have the correct context.
I don't think it is this issue though, as the keymaster firmware is found and qseecomd is attempting to load it.
Rangell11 said:
PS:
I think our G2 not support TARGET_KEYMASTER_WAIT_FOR_QSEE flag.
http://review.cyanogenmod.org/#/c/102410/
Click to expand...
Click to collapse
Thanks. I did some testing and tried both, no luck with either.
Looks like there are at least a couple updates to scm that I could try:
https://github.com/dorimanx/DORIMANX_LG_STOCK_LP_KERNEL/commits/master/arch/arm/mach-msm/scm.c
https://github.com/dorimanx/DORIMANX_LG_STOCK_LP_KERNEL/commits/master/drivers/misc/qseecom.c
Will try updating kernel when I have some free time.
edit: Pulled in a bunch of kernel changes and compiled the boot image to be permissive:
https://github.com/blastagator/LGG2_Kernel/commits/cm-13.0
Still the same error codes.
Code:
[ 0.480347 / 01-01 00:00:00.473] QSEECOM: qseecom_probe: support_bus_scaling=0x1
[ 0.480356 / 01-01 00:00:00.473] QSEECOM: qseecom_probe: disk-encrypt-pipe-pair=0x2
[ 0.480365 / 01-01 00:00:00.473] QSEECOM: qseecom_probe: file-encrypt-pipe-pair=0x0
[ 0.480374 / 01-01 00:00:00.473] QSEECOM: qseecom_probe: qsee-ce-hw-instance=0x0
[ 0.480382 / 01-01 00:00:00.473] QSEECOM: qseecom_probe: qseecom.appsbl_qseecom_support = 0x0
[ 0.480421 / 01-01 00:00:00.473] QSEECOM: qseecom_probe: secure app region addr=0x7b00000 size=0x500000
[ 3.174366 / 01-13 05:47:06.160] init: Starting service 'qseecomd'...
[ 3.207945 / 01-13 05:47:06.193] init: Starting service 'keystore'...
[ 3.221661 / 01-13 05:47:06.206] warning: `qseecomd' uses 32-bit capabilities (legacy support in use)
[ 3.476387 / 01-01 05:47:06.146] QSEECOM: qseecom_load_app: App (keymaster) does'nt exist, loading apps for first time
[ 3.476494 / 01-01 05:47:06.146] QSEECOM: qseecom_load_app: scm_call failed resp.result unknown, -12
[ 3.476511 / 01-01 05:47:06.146] QSEECOM: qseecom_ioctl: failed load_app request: -14
[ 3.477964 / 01-01 05:47:06.146] init: Service 'keystore' (pid 275) exited with status 1
[ 3.477985 / 01-01 05:47:06.146] init: Service 'keystore' (pid 275) killing any children in process group
The last 5 lines just repeat indefinitely.
.

blastagator said:
After clean boot I used "setenforce 0" to see if it would load after that. (keystore service keeps repeatedly attempting to load in the background and can be seen with 'dmesg'.) Disabling enforcing should have solved any selinux problem, but the same error persisted.
Click to expand...
Click to collapse
Do you know why they did not use this change for our G2?
http://review.cyanogenmod.org/#/c/89419/
http://review.cyanogenmod.org/#/c/89418/

Rangell11 said:
Do you know why they did not use this change for our G2?
http://review.cyanogenmod.org/#/c/89419/
http://review.cyanogenmod.org/#/c/89418/
Click to expand...
Click to collapse
qcrypto is currently disabled, so there wouldn't be a need to apply similar patches to the current kernel, unless HW encryption were figured out.
I added those two commits, but I doubt this is the issue.

@blastagator
I've pushed my keymaster to Github: https://github.com/GalaticStryder/hardware_qcom_keymaster
This is the one we use on bacon and onyx on AOSPA builds.
Backporting 3.10 qseecom isn't needed and probably will break the APIs the blobs were compiled for. I'm gonna test this on nougat as well right now.
I'd actually ask for your help on AOSPA, I've got a semi-working RIL and some other great stuff to play with but I can't get the built-in kernel to boot after flashing, only boots when flashing my kernel externally.
The image is bumped, the mkbootimg was revisited twice but there's no go. I don't want to ship a prebuilt image to workaround this. I've tried CM14 kernel with my GCC 4.9 patches for androidkernel- toolchain and Lambda as well.

GalaticStryder said:
@blastagator
I've pushed my keymaster to Github: https://github.com/GalaticStryder/hardware_qcom_keymaster
This is the one we use on bacon and onyx on AOSPA builds.
Backporting 3.10 qseecom isn't needed and probably will break the APIs the blobs were compiled for. I'm gonna test this on nougat as well right now.
I'd actually ask for your help on AOSPA, I've got a semi-working RIL and some other great stuff to play with but I can't get the built-in kernel to boot after flashing, only boots when flashing my kernel externally.
The image is bumped, the mkbootimg was revisited twice but there's no go. I don't want to ship a prebuilt image to workaround this. I've tried CM14 kernel with my GCC 4.9 patches for androidkernel- toolchain and Lambda as well.
Click to expand...
Click to collapse
Without going too far OT, do you have a thread for the AOSPA you're working on? Curious what manifest you're using.
re: keymaster - I pulled the blobs from Bacon and it looks like the cm-13 nightlies use the latest hardware_qcom_keymaster. I don't think there have really been any big changes to the API. I could be wrong though!

blastagator said:
Without going too far OT, do you have a thread for the AOSPA you're working on? Curious what manifest you're using.
re: keymaster - I pulled the blobs from Bacon and it looks like the cm-13 nightlies use the latest hardware_qcom_keymaster. I don't think there have really been any big changes to the API. I could be wrong though!
Click to expand...
Click to collapse
I'm making progress using everything from CAF and patching the needed parts on demand.
The stuff AOSPA already has in their Github I'm sending to Gerrit: https://gerrit.aospa.co/#/q/status:open
The parts I needed to dive deeper I've forked or created the repos manually: https://github.com/GalaticStryder
My next step is to "decommonize" the power package to be able to hint impulse instead of ondemand and to update MSM8974 code that is two years old.
The only problem I'm facing is that the otapackage seems to flash the boot.img in a bad manner, causing boot certification problem. If I manually flash the boot.img after the otapackage it works like a charm, the problem is somewhere in the boot flashing script part of the ota_from_target_files python script, might be pushing the boot.img using imgdiff and causing the bootloader to refuse due to mismatching certification inside the boot sector. This is my hypothesis but it might be what is happening.

GalaticStryder said:
I'm making progress using everything from CAF and patching the needed parts on demand.
The stuff AOSPA already has in their Github I'm sending to Gerrit: https://gerrit.aospa.co/#/q/status:open
The parts I needed to dive deeper I've forked or created the repos manually: https://github.com/GalaticStryder
My next step is to "decommonize" the power package to be able to hint impulse instead of ondemand and to update MSM8974 code that is two years old.
The only problem I'm facing is that the otapackage seems to flash the boot.img in a bad manner, causing boot certification problem. If I manually flash the boot.img after the otapackage it works like a charm, the problem is somewhere in the boot flashing script part of the ota_from_target_files python script, might be pushing the boot.img using imgdiff and causing the bootloader to refuse due to mismatching certification inside the boot sector. This is my hypothesis but it might be what is happening.
Click to expand...
Click to collapse
Well beyond the scope of my dive into android fun. Wish I could help! What is your ultimate goal? Paranoid Android?
It is also very exciting to see the push of Android stuff into the mainline kernel. Hope for the future!

Realized additional blobs for qseecom:
https://github.com/blastagator/them...mmit/09bc989cdb0db9bc47f7501dbf36be2a155ca168
Also, updated boardconfig since the bacon qseecomd supports TARGET_KEYMASTER_WAIT_FOR_QSEE
https://github.com/blastagator/cm_d...mmit/6ca7cd8835afa57ebec9b47fc56514d87ee95e34
Building now. Not sure if I can test tonight, but fingers crossed, maybe it will work!
No luck. Still the same errors:
Code:
12-31 23:22:39.385 2697 2697 I keystore: Found keymaster0 module Keymaster QCOM HAL, version 3
12-31 23:22:39.385 2697 2697 I SoftKeymaster: system/keymaster/soft_keymaster_device.cpp, Line 122: Creating device
12-31 23:22:39.385 2697 2697 D SoftKeymaster: system/keymaster/soft_keymaster_device.cpp, Line 123: Device address: 0xb6b64000
12-31 23:22:39.386 2697 2697 D QCOMKeyMaster: keymaster app is loaded
12-31 23:22:39.386 2697 2697 D QCOMKeyMaster: keymaster app got loaded at attempt number 0
12-31 23:22:39.386 2697 2697 D QSEECOMAPI: : QSEECom_get_handle sb_length = 0x2000
12-31 23:22:39.386 2697 2697 D QSEECOMAPI: : App is not loaded in QSEE
12-31 23:22:39.392 2697 2697 E QSEECOMAPI: : Error::Load image request failed ret = -1, errno = 14
12-31 23:22:39.392 2697 2697 E QSEECOMAPI: : Error::Loading image failed with ret = -1
12-31 23:22:39.393 2697 2697 D QSEECOMAPI: : QSEECom_get_handle sb_length = 0x2000
12-31 23:22:39.393 2697 2697 D QSEECOMAPI: : App is not loaded in QSEE
12-31 23:22:39.393 2697 2697 E QSEECOMAPI: : Error::Cannot open the file /firmware/image/keymaste.mdt
12-31 23:22:39.393 2697 2697 E QSEECOMAPI: : Error::Loading image failed with ret = -1
12-31 23:22:39.393 2697 2697 E QCOMKeyMaster: Loading keymaster app failed
12-31 23:22:39.393 2697 2697 E keystore: Error opening keystore keymaster0 device.
12-31 23:22:39.393 2697 2697 E keystore: keystore keymaster could not be initialized; exiting
Guessing there is some sort of signature check that is matching the expected device to the keymaster firmware file. Unfortunately qseecomapi and keymaster are closed source, so it is kind of a guessing game...
Code:
/**
* @brief Open a handle to the QSEECom device.
*
* - Load a secure application. The application will be verified that it is
* secure by digital signature verification.
* Allocate memory for sending requests to the QSAPP
*
* Note/Comments:
* There is a one-to-one relation for a HLOS client and a QSAPP;
* meaning that only one app can communicate to a QSAPP at a time.
*
* Please note that there is difference between an application and a listener
* service. A QSAPP must be loaded at the request of the HLOS,
* and all requests are orginated by the HLOS client.
* A listener service on the otherhand is started during start-up by a
* daemon, qseecomd.
*
* A HLOS application may create mutiple handles to the QSAPP
*
* @param[in/out] handle The device handle
* @param[in] fname The directory and filename to load.
* @param[in] sb_size Size of the shared buffer memory for sending requests.
* @return Zero on success, negative on failure. errno will be set on
* error.
*/
int QSEECom_start_app(struct QSEECom_handle **clnt_handle, const char *path,
const char *fname, uint32_t sb_size);
Perhaps something in one of the .prop files could be changed to trick the app into passing a device check, but again, this is all very speculative.

blastagator said:
Anyone ever attempted to kang Keymaster Firmware from a different device? I have tried the firmware from bacon, hammerhead, and g3. I have tried with and without the TARGET_KEYMASTER_WAIT_FOR_QSEE flag.
The result is always the same in dmesg:
Code:
[0][4371: keystore]QSEECOM: qseecom_load_app: App (keymaster) does'nt exist, loading apps for first time
[0][4371: keystore]QSEECOM: qseecom_load_app: scm_call failed resp.result unknown, -12
[0][4371: keystore]QSEECOM: qseecom_ioctl: failed load_app request: -14
Click to expand...
Click to collapse
Hello @blastagator,
were you able to fix that Keymaster Issue , if so mind telling us how ?
Because , iam facing similar issues in YU4711 (jalebi)

sooorajjj said:
Hello @blastagator,
were you able to fix that Keymaster Issue , if so mind telling us how ?
Because , iam facing similar issues in YU4711 (jalebi)
Click to expand...
Click to collapse
No. Tried several things with no luck.

What is a keymaster firmware?
And what is it good for?

wq0913562 said:
What is a keymaster firmware?
And what is it good for?
Click to expand...
Click to collapse
Maybe this config is need for porting firmware from different devices.

wq0913562 said:
What is a keymaster firmware?
And what is it good for?
Click to expand...
Click to collapse
cryerenable said:
Maybe this config is need for porting firmware from different devices.
Click to expand...
Click to collapse
No, it is used to enable hardware backed keystore (i.e. hardware accelerated encryption)

blastagator said:
No, it is used to enable hardware backed keystore (i.e. hardware accelerated encryption)
Click to expand...
Click to collapse
hello
i'm facing a similar problem on my lineage 13 port for the lg stylo 2 plus the qseecomapi is keeping looking for the keymaste.mdt file
E QSEECOMAPI: Error::Cannot open the file /firmware/image/keymaste.mdt errno = 2
E QSEECOMAPI: Error::Loading image failed with ret = -1
Click to expand...
Click to collapse
and our device does not have one do you know how to bybass this, ty.

messi2050 said:
hello
i'm facing a similar problem on my lineage 13 port for the lg stylo 2 plus the qseecomapi is keeping looking for the keymaste.mdt file
and our device does not have one do you know how to bybass this, ty.
Click to expand...
Click to collapse
I got frustrated with it. Only other idea I had was to port all common blobs from similar device and see if that works.

blastagator said:
I got frustrated with it. Only other idea I had was to port all common blobs from similar device and see if that works.
Click to expand...
Click to collapse
Are you still active?
Just found this. Not sure if it can help.
http://bits-please.blogspot.de/2016/06/extracting-qualcomms-keymaster-keys.html
https://android.googlesource.com/platform/hardware/qcom/keymaster/+/master
Maybe I'll give it a try to port keymaster now that we have updated 3.4.113 kernel...

Try to port Ubuntu Touch for Moto G 2014

Hi , i'm trying to port Ubuntu Touch for Moto G 2014
can any one help me to resolve this error
make: *** No rule to make target '/home/walid/phablet/out/host/linux-x86/framework/signapk.jar', needed by '/home/walid/phablet/out/target/product/titan/obj/APPS/TimeService_intermediates/TimeService.apk'. Stop.
Edit :
I'm in the end step of booting
[ 7.433841,1] initrd: mounting /dev/disk/by-partlabel/boot as /root/android//boot
[ 7.454993,3] initrd: checking mount label recovery
[ 7.457615,0] initrd: mounting /dev/disk/by-partlabel/recovery as /root/android//recovery
[ 7.497315,3] initrd: checking mount label mmc_host*
[ 7.517051,2] initrd: checking mount label usb1
[ 7.554915,0] initrd: checking mount label zram0
[ 7.558913,1] initrd: mounting /dev/zram0 as /root/android/none
[ 7.563701,1] initrd: mounting /root/var/lib/lxc/android/system.img as /root/android/system
[ 7.631982,1] systemd-udevd[181]: Validate module index
At this point the system try to mount system.img
But after that the system crash
[ 7.998344,1] Crash partition in use!
[ 8.998513,1] wcnss crash shutdown 0
[ 8.998592,1] Rebooting in 5 seconds..
[ 13.998672,1] Going down for restart now
[ 13.999581,1] failed to disable wdog debug: -4
[ 13.999672,1] Calling SCM to disable SPMI PMIC arbiter
PREV
Linux version 3.4.42-g832c593-dirty ([email protected]) (gcc version 4.8 (GCC) ) #5 SMP PREEMPT Thu Feb 2 21:02:43 UTC 2017
full log her,
https://drive.google.com/file/d/0B-F-xs4jYP12dWdsWGFXYlpIeEU/view?usp=sharing
Can any one help me please
Edit again:
Ubuntu Touch now work in my phone , yes work , but no RIL, no Camera and no Wifi.
I will start fix this bugs as soon as possible
https://drive.google.com/file/d/0B-F-xs4jYP12ellZQ25FR05SWVk/view?usp=sharing

walidham said:
Hi , i'm trying to port Ubuntu Touch for Moto G 2014
can any one help me to resolve this error
make: *** No rule to make target '/home/walid/phablet/out/host/linux-x86/framework/signapk.jar', needed by '/home/walid/phablet/out/target/product/titan/obj/APPS/TimeService_intermediates/TimeService.apk'. Stop.
Click to expand...
Click to collapse
ask to dev by PM nobody responde here

marianoasis said:
ask to dev by PM nobody responde here
Click to expand...
Click to collapse
thanks, i resolved the error by adding signapk.jar in out/host/linux-x86/framework.
The problem now, in deodexed apk file(TimeService.apk...) , i will try disabled it in build.

walidham said:
thanks, i resolved the error by adding signapk.jar in out/host/linux-x86/framework.
The problem now, in deodexed apk file(TimeService.apk...) , i will try disabled it in build.
Click to expand...
Click to collapse
good luck with that. and happy new year dude!

marianoasis said:
good luck with that. and happy new year dude!
Click to expand...
Click to collapse
Thanks,
I have compiled and generated boot.img, system.img and recovery.img
But after installation, phone can't boot.
Now come the real work, i will fix boot first (i must see ubuntu touch start).
Happy new year

marianoasis said:
good luck with that. and happy new year dude!
Click to expand...
Click to collapse
Hi
I compiled Source code based on ubport ub5.1 using CM12.1 device tree
recovery.img work fine, i can boot in recovery mod (Ubports Recovery)
But boot.img is big i got this error
error: /home/walidham/ub5/out/target/product/titan/boot.img too large (10729472 > [10771200 - 270336])
Can any one help me how i can reduce boot.img size ?

walidham said:
Hi
I compiled Source code based on ubport ub5.1 using CM12.1 device tree
recovery.img work fine, i can boot in recovery mod (Ubports Recovery)
But boot.img is big i got this error
error: /home/walidham/ub5/out/target/product/titan/boot.img too large (10729472 > [10771200 - 270336])
Can any one help me how i can reduce boot.img size ?
Click to expand...
Click to collapse
Did you resolved the error(making boot.IMG smaller).... After compiling what did you get zimage or boot.img directly.....????

radelpha said:
After compiling what did you get zimage or boot.img directly.....????
Click to expand...
Click to collapse
when i change max size in BoardConfig.mk, after compilation i have 3 files : system.img, recovery.img and boot.img and others files like ramdisk_android.img, ramdisk_ubuntu.img, dt.img....
But still can't flash boot.img (failled due to the size is big).
I'm now trying to delete unneeded drivers and files in device tree and hope will work

walidham said:
when i change max size in BoardConfig.mk, after compilation i have 3 files : system.img, recovery.img and boot.img and others files like ramdisk_android.img, ramdisk_ubuntu.img, dt.img....
But still can't flash boot.img (failled due to the size is big).
I'm now trying to delete unneeded drivers and files in device tree and hope will work
Click to expand...
Click to collapse
Hmmm... Give it a try... Try unpacking the boot.IMG(Ubuntu) and unpack stock titans boot.IMG then replace its zimage(stock) with ubuntu's zimage then repack it.... Hope this works.....

radelpha said:
Hmmm... Give it a try... Try unpacking the boot.IMG(Ubuntu) and unpack stock titans boot.IMG then replace its zimage(stock) with ubuntu's zimage then repack it.... Hope this works.....
Click to expand...
Click to collapse
When i just unpack and repack the boot.img generated, the size is reduced (10.8mb to 9.5mb), i don't know why?, i got 5 files :
boot.img-base,
boot.img-cmdline,
boot.img-pagessize,
boot.img-ramdisk.gz and
boot.img-zimage
I will try your idea

walidham said:
When i just unpack and repack the boot.img generated, the size is reduced (10.8mb to 9.5mb), i don't know why?, i got 5 files :
boot.img-base,
boot.img-cmdline,
boot.img-pagessize,
boot.img-ramdisk.gz and
boot.img-zimage
I will try your idea
Click to expand...
Click to collapse
Yes.... Flash this boot.IMG with only fastboot or else it won't work.....

Now i have the three files : recovery.img, boot.img and systme.img based on cm-12.1
recovery work , but after flashing boot and system , phone stop in moto logo,
Her some logs :
<3>[ 2.643604,2] init: failed to open '/sys/class/graphics/fb1/msm_fb_type'
<3>[ 2.643745,2] init: failed to open '/sys/class/graphics/fb2/msm_fb_type'
<3>[ 2.644593,2] init: Unable to open persistent property directory /data/property errno: 2
<6>[ 2.763154,0] cpr_scale: Down: cpr status = 0x000025dd (error_steps=7)
<3>[ 0.947143,0] mdss_mdp_parse_dt_prop_len: Error from prop qcom,mdss-ad-off : spec error in device tree
<4>[ 1.077626,1] mmi_factory: probe of factory_support.71 failed with error -16
Can any one help me

I'm in the end step of booting
[ 7.433841,1] initrd: mounting /dev/disk/by-partlabel/boot as /root/android//boot
[ 7.454993,3] initrd: checking mount label recovery
[ 7.457615,0] initrd: mounting /dev/disk/by-partlabel/recovery as /root/android//recovery
[ 7.497315,3] initrd: checking mount label mmc_host*
[ 7.517051,2] initrd: checking mount label usb1
[ 7.554915,0] initrd: checking mount label zram0
[ 7.558913,1] initrd: mounting /dev/zram0 as /root/android/none
[ 7.563701,1] initrd: mounting /root/var/lib/lxc/android/system.img as /root/android/system
[ 7.631982,1] systemd-udevd[181]: Validate module index
At this point the system try to mount system.img
But after that the system crash
[ 7.998344,1] Crash partition in use!
[ 8.998513,1] wcnss crash shutdown 0
[ 8.998592,1] Rebooting in 5 seconds..
[ 13.998672,1] Going down for restart now
[ 13.999581,1] failed to disable wdog debug: -4
[ 13.999672,1] Calling SCM to disable SPMI PMIC arbiter
PREV
Linux version 3.4.42-g832c593-dirty ([email protected]) (gcc version 4.8 (GCC) ) #5 SMP PREEMPT Thu Feb 2 21:02:43 UTC 2017
full log her,
https://drive.google.com/file/d/0B-F...ew?usp=sharing

Stuck in boot animation
https://drive.google.com/file/d/0B-F-xs4jYP12dWFlSUVqTmV3RDQ/view?usp=sharing

Ubuntu Touch now work in my phone , yes work , but no RIL, no Camera and no Wifi.
I will start fix this bugs as soon as possible

@walidham i try to port using cm 13.1 what you defconfig ? thanks, and good work, waiting for fix ...

horuxan said:
@walidham i try to port using cm 13.1 what you defconfig ? thanks, and good work, waiting for fix ...
Click to expand...
Click to collapse
Sorry, you want port Ubuntu Touch using cm-13.0 ?
If yes, you must change titan_defconfig using this script
https://github.com/janimo/phablet-porting-scripts
But you must disable some flags like CONFIG_DEBUG_RODATA

Congo for your first boot... and please contact @h2o64 as he ported ubuntu touch to moto g 2013.... Hope he will help you

walidham said:
Sorry, you want port Ubuntu Touch using cm-13.0 ?
If yes, you must change titan_defconfig using this script
https://github.com/janimo/phablet-porting-scripts
But you must disable some flags like CONFIG_DEBUG_RODATA
Click to expand...
Click to collapse
thanks @walidham )))) :fingers-crossed:
---------- Post added at 05:33 PM ---------- Previous post was at 05:32 PM ----------
walidham said:
Sorry, you want port Ubuntu Touch using cm-13.0 ?
If yes, you must change titan_defconfig using this script
https://github.com/janimo/phablet-porting-scripts
But you must disable some flags like CONFIG_DEBUG_RODATA
Click to expand...
Click to collapse
thanks @walidham )))) :fingers-crossed:

[ROM][UNOFFICIAL]LineageOS 14.1 for One Mini 2

Introduction
This is UNOFFICIAL LineageOS 14.1 for HTC One Mini 2.
Please use this thread to report bugs, request features, and offer feedback.
Installation instructions
You must unlock your bootloader or be S-OFF.
You must have a custom recovery installed. (TWRP)
Fully wipe your device from Recovery (Data, Dalvik and Cache!) and install the LineageOS 14.1 ROM.
If you would use Gapps install it now and than reboot.
The first boot will take a while!
Disclaimer
OFFICIAL DISCLAIMER
/*
* Your warranty is now void.
*
* I am not responsible for bricked device, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
Changelog
Release V0.8 (21.06.2018)
Update to latest LOS upstream
Added latest WCNSS firmware
EGL buffer_age extension support disabled
exFAT support added
Amplifier deadlock fixed
wcnss_service added to set the correct HTC MAC address during initialization
Default USB mode removed
ZRAM max. compression streams have been increased to 4
Switched ZRAM compression algorithm to LZ4
Switched to ADB over FunctionFS
Kernel: Added many patches to ZRAM, zsmalloc and zpool which improve functionality and performance
Kernel: Switched to new prima wifi driver
Kernel: Added exFAT and sdFAT drivers
Kernel: Added FunctionFS support
Kernel: Pgtable mapping for zsmalloc enabled
Kernel: RCU boost enabled
Kernel: Linux regulatory feature enabled
Kernel: Added some patches to sdcardfs and USB gadget driver
Look here for full kernel changelog (Last commit from previous release: 0d4c423)
Older changelogs:
Release V0.7 (20.01.2018)
Update to latest LOS upstream
Shrink USB Charging Images to fit 720p screen properly
Rework init power script a bit
Unbreak perfd
Hide sRGB toggle in developer options
nfc: Advertise extended length support for IsoDep frames (Thanks to stkl)
Kernel: ANDROID: sdcardfs: notify lower file of opens
Kernel: ANDROID: sdcardfs: Add default_normal option
Kernel: Enable some perf-related configs
Kernel: drivers: touchscreen: Fix active touchscreen during calls and power button camera shortcut
Kernel: drivers: i2c: Use older QUP bus driver to fix wakeup issues on memul
Look here for full kernel changelog (Last commit from previous release: 2d22c8c)
Release V0.6 (25.11.2017)
Fix USB Accessory mode
Add ANT+ support
Swappiness has been set to 100
Kernel: Pocket check added for dt2w
Kernel: Fixed non-working microphone during a call on loudspeaker
Kernel: Improved the bus recovery procedure in qup i2c driver
Kernel: Register SPS IRQ with IRQF_NO_SUSPEND flag
Kernel: Reworked kernel config
Kernel: Merged Tag "v3.4.100"
Kernel: Merged Tag "v3.4.113"
Kernel: Max readahead size changed to 512KB
Kernel: Fix high load average from uninterruptible waits
Kernel: Do not allocate new hw_event if event is duplicate
Kernel: interactive: turn boost_pulse off on boost off
Kernel: interactive: Remove unnecessary cpu_online() check
Kernel: ablk_helper - Replace memcpy with struct assignment
Kernel: Don't plug the I/O queue in do_io_submit()
Look here for full kernel changelog (Last commit from previous release: 4e5b7fb)
Release V0.5 (04.11.2017)
Amplifier HAL improvements
Removed useless button backlight support on liblights
GPS HAL cleanup
Enabled CLANG compilation for GPS HAL
Removed some deprecated flags
Fix tombstones creation
Root directories now created on early-init
Missing directories under /data are now created
Cleaned up main QC init script
XTRA download now uses https
Cleaned up OMX codecs packages
Added GPS configuration for China
DRM ClearKey plugin is now builded from source
Fix gpuclk and reset_count denials
Added missing OMX codecs decoders
Removed deprecated media blobs
Cleaned up bluetooth config
Decreased in call volume to about 74dB
Enabled GLONASS support
Kernel: Added Himax touchscreen driver
Look here for full kernel changelog (Last commit from previous release: 2fc6b22)
Release V0.4 (13.09.2017)
"New" CAF based kernel on version 3.4.90
AptX Support added
Earpiece volume Increased
startOffsetMs removed from media_profile to avoid capturing the video record tone while recording the video with camcorder
Sepolicy rework
thermal-engine moved to vendor/bin
Amplifier: removed a forgotten debug
Build rild and libril from caf source
Compile libril with GCC instead of Clang to avoid RIL crash while establishing outgoing calls
Fix crashing RIL when trying to print "Create UIM thread on SUB%d with name %s" with Clang libc
media codecs config updated
Addded media codecs performance config
Adreno blobs updated to LA.BF.1.1.3_rb1.12
Build GPS HAL from source
Added overlay-based GPS configs
A-GPS re-enabled
Changed from 2 to 3 FramebufferSurface buffers to avoid tearing because of invalid fence semantics
Fixed null pointer de-reference klocwork error in liblight
fstab cleaned up
Added device model information to the USB config
Removed the "KERNEL_MISSING_CLOCK_BOOTTIME_ALARM" because our kernel now has the proper support
USB config cleaned up
Removed unused CameraParameters_EXT header
Disabled face detection in the params In addition to making the UI saner. This should fix manual focussing the camera when in auto-focus mode.
All changes to support our One Mini 2 on the new CAF based kernel can be found here: https://github.com/nightcore500/android_kernel_htc_msm8974-caf_rebase/commits/lineage-14.1
Release V0.3 (08.07.2017)
Enable Ambient Display
Increase ZRAM to 400MB
Set default USB mode to charged to fix the USB mode bug on switching from "charging" to "MTP" mode
Rework on init.qcom.bt.sh
Remove DAC override permission which would allow rmt_storage daemon unix permissions to everything and add the system and wakelock group to these service
Adjust mpdecision service permissions to access procfs filesystem
Remove writes to non-existent IPv6 nodes
Remove useless property triggers
Properly set thermal control flags
Ensure boot-with-noop as this results in much shorted boot times
Adjust power config (Starting mpdecision later in boot to improve boot time and some more minimal changes)
Remove some permissions these are allready globally defined in device/qcom/sepolicy
Enable blur
Remove some unused permissions
Update to latest LOS upstream
Kernel: Only expose su when daemon is running
Kernel: Add some filesystem, net etc. patches (look here for full changelog)
Release V0.2-himax hotfix (12.05.2017)
Kernel: Enable himax touchscreen driver
Release V0.2 (11.05.2017)
switch to userdebug
switch to enforcing mode
fix NFC
switch to Jelly Browser
switch to Moto 8226 Thermal Engine
Update Qualcomm MSM Interface, Radio Interface Layer, GPS blobs
Update Camera & Sensor blobs
Update Widevine DRM blobs
Update graphics blobs
remove unused proprietary files
selinux: fix some denials
Kernel: re-add DT2W
Kernel: re-add our RT5506 changes
Kernel: fix SDCard driver
Release V0.1-Alpha (06.05.2017)
(Based on the source of CM13)
eng build
disable pre-odex for now
rename to lineageos
fix some platform configs
Update bootloader message offset flag
enable sdclang
enable legacy camera HAL1
Add GraphicBuffer shim for camera hal
enable text relocations for camera blobs
remove some configs
enable GCC LIBC for rild blobs
re-enable jemalloc for low-memory
set selinux to permissive for now
set media.stagefright.legacyencoder
remove old unused dhcp inits and configs
remount debugfs
some changes on core framework configs
some changes on init script
move chargeled to c++
set KERNEL_MISSING_CLOCK_BOOTTIME_ALARM because our kernel does not have support for it
some changes on media codec config
set NXP_CHIP_TYPE
changes on Permission configs
set Qualcomm Bluetooth SOC ID
remove enhanced NFC feature
switch to shared graphics driver repo
use prebuild rild from the last cm13 release for now
disable agps for now
some more changes
Kernel - clone the msm8974 kernel source from lineageos and change to our last kernel config
Kernel - enable RPFILTER
Kernel - signal: allow to send any siginfo to itself (to get debuggerd back to running)
Kernel - switch back to our Prima WLAN driver
Downloads
ROM v0.8 LineageOS 14.1 21.06.2018
md5sum for ROM v0.8 LineageOS 14.1 21.06.2018
Older releases:
ROM v0.7 LineageOS 14.1 20.01.2018
md5sum for ROM v0.7 LineageOS 14.1 20.01.2018
ROM v0.6 LineageOS 14.1 25.11.2017
md5sum for ROM v0.6 LineageOS 14.1 25.11.2017
ROM v0.5 LineageOS 14.1 04.11.2017
md5sum for ROM v0.5 LineageOS 14.1 04.11.2017
ROM v0.4 LineageOS 14.1 13.09.2017
md5sum for ROM v0.4 LineageOS 14.1 13.09.2017
ROM v0.3 LineageOS 14.1 08.07.2017
md5sum for ROM v0.3 LineageOS 14.1 08.07.2017
ROM v0.2-himax_hotfix LineageOS 14.1 12.05.2017
md5sum for ROM v0.2-himax_hotfix LineageOS 14.1 12.05.2017
ROM v0.2 LineageOS 14.1 11.05.2017
md5sum for ROM v0.2 LineageOS 14.1 11.05.2017
ROM v0.1-Alpha LineageOS 14.1 06.05.2017
Root add-on: su (arm)
Open Gapps for all ROMs: Gapps
Thanks
Big thanks to MrAnswer for his one mini 2 that i can use for development purposes.
XDA:DevDB Information
LineageOS 14.1 for One Mini 2, ROM for the HTC One Mini 2
Contributors
nightcore500
Source Code: https://github.com/nightcore500
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Latest stock
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 0.8
Stable Release Date: 2018-06-21
Current Beta Version: 0.6
Beta Release Date: 2017-11-25
Created 2017-05-06
Last Updated 2018-06-21

Reserved

Amazing! Thanks for your dev!
As you know I don't own this device but is good to know 8974 is not dead
Feel free to highlight me here or on IRC if you need something. Also I have some contacts which can help to become official when you will be ready

Cool. gonna try this
---------- Post added at 03:35 PM ---------- Previous post was at 03:30 PM ----------
Is it 7.0 or 7.1?
---------- Post added at 03:36 PM ---------- Previous post was at 03:35 PM ----------
oh nvm
---------- Post added at 03:59 PM ---------- Previous post was at 03:36 PM ----------
When theres a new update will i have to wipe data? I am kind of a newbie to roms.

Andruxcx said:
Is it 7.0 or 7.1?
Click to expand...
Click to collapse
7.1.2
Andruxcx said:
When theres a new update will i have to wipe data? I am kind of a newbie to roms.
Click to expand...
Click to collapse
If you are already on lineageos 14.1 you don't need a full wipe.

nightcore500 said:
7.1.2
If you are already on lineageos 14.1 you don't need a full wipe.
Click to expand...
Click to collapse
Thanks. So i tried the rom and everything seems fine for now except that i cant get out of strict mode with dev options. Is there a way to turn strict mode off?
---------- Post added at 05:45 PM ---------- Previous post was at 05:43 PM ----------
For those who want root dont install super su it will bootloop your device. just download it from this link ~ https://download.lineageos.org/extras ~ and flash it in twrp :good:
---------- Post added at 06:04 PM ---------- Previous post was at 05:45 PM ----------
Not sure if this is a bug but i cant see any contacts when i go to the import from sim window

Andruxcx said:
Thanks. So i tried the rom and everything seems fine for now except that i cant get out of strict mode with dev options. Is there a way to turn strict mode off?
Click to expand...
Click to collapse
No, its a debugging feature thats automatic enabled on eng builds. This build is currently only for development purposes. I switch to userdebug on the next releases.

nightcore500 said:
No, its a debugging feature thats automatic enabled on eng builds. This build is currently only for development purposes. I switch to userdebug on the next releases.
Click to expand...
Click to collapse
Okay

Does this need TWRP version 3 to flash or the 2.8.5.0 flashes as well ?

Awesome. Did a clean install after full wipe (using TWRP 3) and started testing.
Working:
System UI, GApps
Stable networking (WiFi 2.4 + 5 GHz), Cellular 3G and 4G
Bluetooth (audio, data)
Simple NFC tag
Camera, flash, torch
Audio in/out (loud and clear)
GPS
Sensors (magnetic, light, proximity - proximity little buggy, but that problem existed before)
Running much smoother than the latest CM13 build overall
Problems / Not Working:
DT2W
16GB SanDisk SD card not working - worked before and also with another Android 7.1 device (older 8GB SanDisk works - have to figure out why)
Some root issues, most lilkely due to eng build incompatibilities with my apps
Just played around for an hour and so far it's running pretty stable (not a single app crash). Looks like we're on the right track.
The issued I experienced before (CM13) with OTG are still the same - surprise - but that's not of priority.

Received ERROR when flashing via twrp, both 2.8.5.0 and 3.0.2:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
Updater process ended with ERROR: 7
ERROR installing zip file '/externl_sd/lineage_memul-ota.zip'
I tried dirty flash with STOCK ROM installed, so I did a complete wipe of SYSTEM, CACHE, DALVIK CACHE and DATA and installed successfully.
Also I have this Red Screen border flash when touching screen at times, NOT always but mostly, I have checked developer options all settings are off but still it wont go away. I read about strict mode but there is no options in settings, any ideas, I even turned off developer options but still remains.
INITIAL REVIEW.
Way better than CM13
Slightly laggy, I will assume due to alpha state
Crystal clear audio
Camera is crisp clear with photos compared to CM13
Boot/reboot more than once tried is a bit slow
SD read in gallery is too slow could be due to slow MMC read/write and first time reading too many images - fine after it loads all images

TryllZ said:
Received ERROR when flashing via twrp, both 2.8.5.0 and 3.0.2:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
Updater process ended with ERROR: 7
ERROR installing zip file '/externl_sd/lineage_memul-ota.zip'
I tried dirty flash with STOCK ROM installed, so I did a complete wipe of SYSTEM, CACHE, DALVIK CACHE and DATA and installed successfully.
Also I have this Red Screen border flash when touching screen at times, NOT always but mostly, I have checked developer options all settings are off but still it wont go away. I read about strict mode but therte is no options in settings, any ideas.
Click to expand...
Click to collapse
Look at https://forum.xda-developers.com/showpost.php?p=72190216&postcount=7

nightcore500 said:
Look at https://forum.xda-developers.com/showpost.php?p=72190216&postcount=7
Click to expand...
Click to collapse
Thanks, missed that.
:good::good::good: ROM

stkl said:
16GB SanDisk SD card not working - worked before and also with another Android 7.1 device (older 8GB SanDisk works - have to figure out why)
Click to expand...
Click to collapse
Seems to be an issue with die SD card driver, UHS-1 cards (tested with SanDisk Ultra) are not supported by our current kernel.
The same card (verified genuine btw.) has been working with CM13.
kmsg:
[ 7841.388709] c0 22066 mmc1: slot status change detected (0 -> 1), GPIO_ACTIVE_LOW
[ 7841.775759] c0 18205 mmc1: new ultra high speed DDR50 SDHC card at address aaaa
[ 7841.781131] c0 18205 mmcblk1: mmc1:aaaa SU16G 14.8 GiB
[ 7841.803148] c0 0 mmc1: data txfr (0x00200000) error: -84 after 16 ms
[ 7841.803201] c0 0 sdhci: =========== REGISTER DUMP (mmc1)===========
[ 7841.803247] c0 0 sdhci: Sys addr: 0x00000000 | Version: 0x00003e02
[ 7841.803292] c0 0 sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000008
[ 7841.803336] c0 0 sdhci: Argument: 0x00000000 | Trn mode: 0x00000033
[ 7841.803381] c0 0 sdhci: Present: 0x03f80206 | Host ctl: 0x00000017
[ 7841.803425] c0 0 sdhci: Power: 0x0000000f | Blk gap: 0x00000000
[ 7841.803469] c0 0 sdhci: Wake-up: 0x00000000 | Clock: 0x00000007
[ 7841.803512] c0 0 sdhci: Timeout: 0x00000008 | Int stat: 0x00000000
[ 7841.803557] c0 0 sdhci: Int enab: 0x03ff800b | Sig enab: 0x03ff800b
[ 7841.803600] c0 0 sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[ 7841.803645] c0 0 sdhci: Caps: 0x2329c8b2 | Caps_1: 0x00008007
[ 7841.803689] c0 0 sdhci: Cmd: 0x0000123a | Max curr: 0x00000000
[ 7841.803734] c0 0 sdhci: Resp 1: 0x5b590000 | Resp 0: 0x00000900
[ 7841.803779] c0 0 sdhci: Resp 3: 0x0a404012 | Resp 2: 0x76b27f80
[ 7841.803820] c0 0 sdhci: Host ctl2: 0x0000000c
[ 7841.803859] c0 0 sdhci: ADMA Err: 0x00000003 | ADMA Ptr: 0x2e300008
[ 7841.803909] c0 0 mmc1: clk: 50000000 clk-gated: 0 claimer: mmcqd/1 pwr: 14
[ 7841.803957] c0 0 mmc1: rpmstatus[pltfm](runtime-suspend:usage_count:disable_depth)(0:0:0)
[ 7841.804003] c0 0 sdhci: ===========================================
[ 7841.810959] c0 27665 mmcblk1: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0xb00
[ 7842.098945] c0 18205 mmcblk1: p1

stkl said:
Seems to be an issue with die SD card driver, UHS-1 cards (tested with SanDisk Ultra) are not supported by our current kernel.
The same card (verified genuine btw.) has been working with CM13.
kmsg:
[ 7841.388709] c0 22066 mmc1: slot status change detected (0 -> 1), GPIO_ACTIVE_LOW
[ 7841.775759] c0 18205 mmc1: new ultra high speed DDR50 SDHC card at address aaaa
[ 7841.781131] c0 18205 mmcblk1: mmc1:aaaa SU16G 14.8 GiB
[ 7841.803148] c0 0 mmc1: data txfr (0x00200000) error: -84 after 16 ms
[ 7841.803201] c0 0 sdhci: =========== REGISTER DUMP (mmc1)===========
[ 7841.803247] c0 0 sdhci: Sys addr: 0x00000000 | Version: 0x00003e02
[ 7841.803292] c0 0 sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000008
[ 7841.803336] c0 0 sdhci: Argument: 0x00000000 | Trn mode: 0x00000033
[ 7841.803381] c0 0 sdhci: Present: 0x03f80206 | Host ctl: 0x00000017
[ 7841.803425] c0 0 sdhci: Power: 0x0000000f | Blk gap: 0x00000000
[ 7841.803469] c0 0 sdhci: Wake-up: 0x00000000 | Clock: 0x00000007
[ 7841.803512] c0 0 sdhci: Timeout: 0x00000008 | Int stat: 0x00000000
[ 7841.803557] c0 0 sdhci: Int enab: 0x03ff800b | Sig enab: 0x03ff800b
[ 7841.803600] c0 0 sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[ 7841.803645] c0 0 sdhci: Caps: 0x2329c8b2 | Caps_1: 0x00008007
[ 7841.803689] c0 0 sdhci: Cmd: 0x0000123a | Max curr: 0x00000000
[ 7841.803734] c0 0 sdhci: Resp 1: 0x5b590000 | Resp 0: 0x00000900
[ 7841.803779] c0 0 sdhci: Resp 3: 0x0a404012 | Resp 2: 0x76b27f80
[ 7841.803820] c0 0 sdhci: Host ctl2: 0x0000000c
[ 7841.803859] c0 0 sdhci: ADMA Err: 0x00000003 | ADMA Ptr: 0x2e300008
[ 7841.803909] c0 0 mmc1: clk: 50000000 clk-gated: 0 claimer: mmcqd/1 pwr: 14
[ 7841.803957] c0 0 mmc1: rpmstatus[pltfm](runtime-suspend:usage_count:disable_depth)(0:0:0)
[ 7841.804003] c0 0 sdhci: ===========================================
[ 7841.810959] c0 27665 mmcblk1: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0xb00
[ 7842.098945] c0 18205 mmcblk1: p1
Click to expand...
Click to collapse
Thanks, I have fixed the problem yesterday evening: https://github.com/nightcore500/and...mmit/08a899fdb120982aaad42c6c6ea9315a60a908e5
Its included in the next release.

OK, I should have pulled fresh sources... anyway, great

As far as I can judge, nightcore uses the latest msm8974 kernel source from lineage? Invisiblek has here synced the mmc driver some time ago to caf/LA.BF.1.1.1_rb1.26. (https://github.com/LineageOS/androi...mmit/b7a99c094be02d78d1a9f7f8e5898bd702df82c7) That problem was already announced by some people to the devs. But nobody had ever cared about it. Or what do you mean stkl?

Yes, exactly. Same code snippet referenced be nightcore. Should be fixed now. Just started a new build, will test tomorrow.
The UHS problem has been fixed and reverted numerous times in the past, not only for CM/LOS...

When I select image(s) for deletion, sometimes the delete button shows sometimes it doesn't.
Anyone knows how to make a flashable zip of stock apps, Thanks..

Finusfix said:
As far as I can judge, nightcore uses the latest msm8974 kernel source from lineage? Invisiblek has here synced the mmc driver some time ago to caf/LA.BF.1.1.1_rb1.26. (https://github.com/LineageOS/androi...mmit/b7a99c094be02d78d1a9f7f8e5898bd702df82c7) That problem was already announced by some people to the devs. But nobody had ever cared about it. Or what do you mean stkl?
Click to expand...
Click to collapse
Yeah the git entry I always revert when building the One Mini 2 is the following commit:
b7a99c094be02d78d1a9f7f8e5898bd702df82c7
This is when all the MMC stuff changed to fit the M8 and similar and stopped working for the Memul.

Building AOSP Extended

I'm trying to build AOSP Extended for Sanders but I'm facing problem during compiling stuff. I used:
Device repo: https://github.com/AospExtended-Devices/android_device_motorola_sanders
Kernel source: https://github.com/Jorg3Lucas/android_kernel_motorola_msm8953
Vendor repo: https://github.com/AospExtended-Devices/android_vendor_motorola_sanders
Problem:
Code:
[ 36% 29755/82171] build /home/qkiz/android/out/target/product/sanders/obj/ETC/sepolicy.recovery_intermediates/sepolicy
FAILED: /home/qkiz/android/out/target/product/sanders/obj/ETC/sepolicy.recovery_intermediates/sepolicy
/bin/bash -c "(ASAN_OPTIONS=detect_leaks=0 /home/qkiz/android/out/host/linux-x86/bin/checkpolicy -M -c 30 -o /home/qkiz/android/out/target/product/sanders/obj/ETC/sepolicy.recovery_intermediates/sepolicy.tmp /home/qkiz/android/out/target/product/sanders/obj/ETC/sepolicy.recovery_intermediates/sepolicy.recovery.conf ) && (/home/qkiz/android/out/host/linux-x86/bin/sepolicy-analyze /home/qkiz/android/out/target/product/sanders/obj/ETC/sepolicy.recovery_intermediates/sepolicy.tmp permissive > /home/qkiz/android/out/target/product/sanders/obj/ETC/sepolicy.recovery_intermediates/sepolicy.permissivedomains ) && (if [ \"userdebug\" = \"user\" -a -s /home/qkiz/android/out/target/product/sanders/obj/ETC/sepolicy.recovery_intermediates/sepolicy.permissivedomains ]; then echo \"==========\" 1>&2; echo \"ERROR: permissive domains not allowed in user builds\" 1>&2; echo \"List of invalid domains:\" 1>&2; cat /home/qkiz/android/out/target/product/sanders/obj/ETC/sepolicy.recovery_intermediates/sepolicy.permissivedomains 1>&2; exit 1; fi ) && (mv /home/qkiz/android/out/target/product/sanders/obj/ETC/sepolicy.recovery_intermediates/sepolicy.tmp /home/qkiz/android/out/target/product/sanders/obj/ETC/sepolicy.recovery_intermediates/sepolicy )"
device/motorola/sanders/sepolicy/vendor/file.te:36:ERROR 'Duplicate declaration of type' at token ';' on line 78529:
# sysfs
type sysfs_adsp, fs_type, sysfs_type;
checkpolicy: error(s) encountered while parsing configuration
36% 29757/82171] build /home/qkiz/android/out/target/product/sanders/obj/ETC/sepolicy_neverallows_intermediates/plat_pub_policy.cil /home/qkiz/android/out/host/linux-x86/bin/checkpolicy: loading policy configuration from /home/qkiz/android/out/target/product/sanders/obj/ETC/sepolicy_neverallows_intermediates/plat_pub_policy.conf /home/qkiz/android/out/host/linux-x86/bin/checkpolicy: policy configuration loaded /home/qkiz/android/out/host/linux-x86/bin/checkpolicy: writing CIL to /home/qkiz/android/out/target/product/sanders/obj/ETC/sepolicy_neverallows_intermediates/plat_pub_policy.cil.tmp [ 36% 29758/82171] //frameworks/base/libs/services:libservices clang++ aidl/frameworks/base/core/java/com/android/internal/os/IDropBoxManagerService.cpp [ 36% 29759/82171] //frameworks/base/libs/services:libservices clang++ src/os/StatsLogEventWrapper.cpp [ 36% 29760/82171] //frameworks/base/libs/services:libservices clang++ src/os/StatsDimensionsValue.cpp [ 36% 29761/82171] //frameworks/base/libs/services:libservices clang++ src/os/DropBoxManager.cpp [ 36% 29762/82171] //frameworks/native/services/utils:libserviceutils clang++ PriorityDumper.cpp ninja: build stopped: subcommand failed. build/make/core/main.mk:21: recipe for target 'run_soong_ui' failed [0;31m#### failed to build some targets (44:39 (mm:ss)) ####[00m
Anyone facing similar problem. Or maybe I used wrong repos to build image.

I fixed three errors and successfully build AOSP Extended with April security patch.
Sent from my Motorola Moto G (5S) Plus using XDA Labs

QkiZMR said:
I fixed three errors and successfully build AOSP Extended with April security patch.
Sent from my Motorola Moto G (5S) Plus using XDA Labs
Click to expand...
Click to collapse
How did you fixed it?
What did you do?

I commented out mentioned in error lines in policy file.

[fixed] Lineage OS 16 - Audio won't play (Sounds work)

Device: Moto X4 (1900-7)
OS: lineage-16.0-20190812-nightly-payton-signed (also tried nightly 20190819 and 20190820)
Notification Sounds: work
Dial Tones: work
Phone line Audio: works
Audio via Speaker: does not work
Audio via Headphones: does not work
Audio via Bluetooth: works (!?!)
I can't find any similar symptoms anywhere online
what I've (unsuccessfully) tried:
- installing lineage over and over again (various builds)
- install a "lineage-audio-fix.zip"
- switching Mono output on and off
any Ideas? Any further info I could provide? logs?
Thanks, hobbes
edit:
output of "adb shell su -c dmesg"
brings a lot of these lines:
[ 4695.467079] msm_audio_ion_free Invalid params
[ 4695.467422] msm-pcm-dsp soc:qcom,msm-pcm: ASoC: platform prepare error: -12
[ 4695.467426] soc_pcm_prepare: Issue stop stream for codec_dai due to op failure -12 = ret
[ 4695.469671] SDM660 Media1: ASoC: prepare FE SDM660 Media1 failed
[ 4695.574314] mdss_dsi_panel_on[0]-. Pwr_mode(0x0A) = 0x9c
[ 4695.574869] mdss_dsi_post_panel_on[0]-.
[ 4695.575070] mdss_fb_set_hw_param: invalid value 3 for CABC
[ 4695.681948] q6asm_callback: cmd = 0x10db3 returned error = 0x3
[ 4695.682095] __q6asm_open_write: DSP returned error[ADSP_EUNSUPPORTED]
[ 4695.682108] msm_pcm_playback_prepare: q6asm_open_write_with_retry failed (-38)
this block repeats

hobbesDMS said:
...
Click to expand...
Click to collapse
Fixed it. Had to flash back to the Motorola Stock OS (look for "payton retail" and "flash-all" on google to find instructions) - this should get the audio working again.
Then follow these two youtube videos: Z6bZZJseEvg and NWOBa88eJRs to install lineage (I found this guide far better than the official one)