To mention a small issue.

[azzzddddd]

The uppercase ** Nubia** originates from the PRODUCT_BRAND variable defined in your twrp_NX769J.mk file:

device_NX769J/twrp_NX769J.mk

Line 18 in c918e94

PRODUCT_BRAND := Nubia

In the Extracting variables from .mk file script, this PRODUCT_BRAND value is extracted and used to construct the DEVICE_DIRECTORY variable:

DEVICE_DIRECTORY="device/$brand"

Since $brand holds the value Nubia, the script creates the directory device/Nubia.

The build process will result in the following error:

device/Nubia/NX769J/twrp_NX769J.mk:26: error: _nic.PRODUCTS.[[device/Nubia/NX769J/twrp_NX769J.mk]]: "device/nubia/NX769J/device.mk" does not exist.

Solution

• Please change the first letter of the manufacturer's name to lowercase.

😊😊😊

[DarkestSpawn]

I never had an issue when building this on my Ubuntu machine but changed

[DarkestSpawn]

The uppercase ** Nubia** originates from the PRODUCT_BRAND variable defined in your twrp_NX769J.mk file:

device_NX769J/twrp_NX769J.mk

     Line 18
  in
  [c918e94](/DarkestSpawn/device_NX769J/commit/c918e94f148e75e6ff9de7932356c17470f99aa4)





    
      
       PRODUCT_BRAND := Nubia

In the Extracting variables from .mk file script, this PRODUCT_BRAND value is extracted and used to construct the DEVICE_DIRECTORY variable:

DEVICE_DIRECTORY="device/$brand"

Since $brand holds the value Nubia, the script creates the directory device/Nubia.

The build process will result in the following error:

device/Nubia/NX769J/twrp_NX769J.mk:26: error: _nic.PRODUCTS.[[device/Nubia/NX769J/twrp_NX769J.mk]]: "device/nubia/NX769J/device.mk" does not exist.

Solution

• Please change the first letter of the manufacturer's name to lowercase.

😊😊😊

Also are you building for A15 or A14?

[azzzddddd]

A15

[DarkestSpawn]

A15

Those 3 builds you have posted herehttps://github.com/azzzddddd/recovery_device_tree_NX769J/releases did not boot for me on A15 (OS 10.0.4). All get stuck at starting the Keystore service. Just thought I would pass that along.

12-21 19:32:33.920 1 1 E init : Control message: Could not find 'aidl/android.system.keystore2.IKeystoreService/default' for ctl.interface_start from pid: 492 (/system/bin/servicemanager) 05-27 13:15:10.651 506 506 W ServiceManager: Waited one second for android.system.keystore2.IKeystoreService/default (is service started? are binder threads started and available?) 05-27 13:15:10.651 492 492 I servicemanager: Since 'android.system.keystore2.IKeystoreService/default' could not be found, trying to start it as a lazy AIDL service 05-27 13:15:10.651 492 2308 W libc : Unable to set property "ctl.interface_start" to "aidl/android.system.keystore2.IKeystoreService/default": error code: 0x20 05-27 13:15:10.651 492 2308 I servicemanager: Tried to start aidl service android.system.keystore2.IKeystoreService/default as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.

[azzzddddd]

A15

Those 3 builds you have posted herehttps://github.com/azzzddddd/recovery_device_tree_NX769J/releases did not boot for me on A15 (OS 10.0.4). All get stuck at starting the Keystore service. Just thought I would pass that along.

12-21 19:32:33.920 1 1 E init : Control message: Could not find 'aidl/android.system.keystore2.IKeystoreService/default' for ctl.interface_start from pid: 492 (/system/bin/servicemanager) 05-27 13:15:10.651 506 506 W ServiceManager: Waited one second for android.system.keystore2.IKeystoreService/default (is service started? are binder threads started and available?) 05-27 13:15:10.651 492 492 I servicemanager: Since 'android.system.keystore2.IKeystoreService/default' could not be found, trying to start it as a lazy AIDL service 05-27 13:15:10.651 492 2308 W libc : Unable to set property "ctl.interface_start" to "aidl/android.system.keystore2.IKeystoreService/default": error code: 0x20 05-27 13:15:10.651 492 2308 I servicemanager: Tried to start aidl service android.system.keystore2.IKeystoreService/default as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.

Oh, due to my oversight, I forgot to add the keymaster service. I need to see if I have time to rectify it next month.
It seems the keystore hal wasn't added either. I'm confused, I remember adding it locally.

[DarkestSpawn]

A15

Those 3 builds you have posted herehttps://github.com/azzzddddd/recovery_device_tree_NX769J/releases did not boot for me on A15 (OS 10.0.4). All get stuck at starting the Keystore service. Just thought I would pass that along.
12-21 19:32:33.920 1 1 E init : Control message: Could not find 'aidl/android.system.keystore2.IKeystoreService/default' for ctl.interface_start from pid: 492 (/system/bin/servicemanager) 05-27 13:15:10.651 506 506 W ServiceManager: Waited one second for android.system.keystore2.IKeystoreService/default (is service started? are binder threads started and available?) 05-27 13:15:10.651 492 492 I servicemanager: Since 'android.system.keystore2.IKeystoreService/default' could not be found, trying to start it as a lazy AIDL service 05-27 13:15:10.651 492 2308 W libc : Unable to set property "ctl.interface_start" to "aidl/android.system.keystore2.IKeystoreService/default": error code: 0x20 05-27 13:15:10.651 492 2308 I servicemanager: Tried to start aidl service android.system.keystore2.IKeystoreService/default as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.

Oh, due to my oversight, I forgot to add the keymaster service. I need to see if I have time to rectify it next month. It seems the keystore hal wasn't added either. I'm confused, I remember adding it locally.

I pulled that update with those and updated two minor things for testing and made it as the Android 15 branch. Gave credit to you and added a readme with credits to everyone since I deleted the other tree I used (I had it set to private that was the corrected version I was using, my apologies. It was used for testing originally and the BotchedRPR tree was for him trying to work on Decrypt here. Only difference was that change you asked for in the private one.)

Also one question about the vendor.prop since that I have not messed with or seen.

# Crypto ro.hardware.keystore_desede=true ro.crypto.metadata_init_delete_all_keys.enabled=true ro.product.cuptsm=REALME|ESE|01|02 vendor.wv.oemcrypto.debug.enable_prov40=true

Should that be calling REALME or our device?

[azzzddddd]

A15

Those 3 builds you have posted herehttps://github.com/azzzddddd/recovery_device_tree_NX769J/releases did not boot for me on A15 (OS 10.0.4). All get stuck at starting the Keystore service. Just thought I would pass that along.
12-21 19:32:33.920 1 1 E init : Control message: Could not find 'aidl/android.system.keystore2.IKeystoreService/default' for ctl.interface_start from pid: 492 (/system/bin/servicemanager) 05-27 13:15:10.651 506 506 W ServiceManager: Waited one second for android.system.keystore2.IKeystoreService/default (is service started? are binder threads started and available?) 05-27 13:15:10.651 492 492 I servicemanager: Since 'android.system.keystore2.IKeystoreService/default' could not be found, trying to start it as a lazy AIDL service 05-27 13:15:10.651 492 2308 W libc : Unable to set property "ctl.interface_start" to "aidl/android.system.keystore2.IKeystoreService/default": error code: 0x20 05-27 13:15:10.651 492 2308 I servicemanager: Tried to start aidl service android.system.keystore2.IKeystoreService/default as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.

Oh, due to my oversight, I forgot to add the keymaster service. I need to see if I have time to rectify it next month. It seems the keystore hal wasn't added either. I'm confused, I remember adding it locally.

I pulled that update with those and updated two minor things for testing and made it as the Android 15 branch. Gave credit to you and added a readme with credits to everyone since I deleted the other tree I used (I had it set to private that was the corrected version I was using, my apologies. It was used for testing originally and the BotchedRPR tree was for him trying to work on Decrypt here. Only difference was that change you asked for in the private one.)

Also one question about the vendor.prop since that I have not messed with or seen.

# Crypto ro.hardware.keystore_desede=true ro.crypto.metadata_init_delete_all_keys.enabled=true ro.product.cuptsm=REALME|ESE|01|02 vendor.wv.oemcrypto.debug.enable_prov40=true

Should that be calling REALME or our device?

I think using README is better. I will try the prop commands you mentioned.

[DarkestSpawn]

A15

Those 3 builds you have posted herehttps://github.com/azzzddddd/recovery_device_tree_NX769J/releases did not boot for me on A15 (OS 10.0.4). All get stuck at starting the Keystore service. Just thought I would pass that along.
12-21 19:32:33.920 1 1 E init : Control message: Could not find 'aidl/android.system.keystore2.IKeystoreService/default' for ctl.interface_start from pid: 492 (/system/bin/servicemanager) 05-27 13:15:10.651 506 506 W ServiceManager: Waited one second for android.system.keystore2.IKeystoreService/default (is service started? are binder threads started and available?) 05-27 13:15:10.651 492 492 I servicemanager: Since 'android.system.keystore2.IKeystoreService/default' could not be found, trying to start it as a lazy AIDL service 05-27 13:15:10.651 492 2308 W libc : Unable to set property "ctl.interface_start" to "aidl/android.system.keystore2.IKeystoreService/default": error code: 0x20 05-27 13:15:10.651 492 2308 I servicemanager: Tried to start aidl service android.system.keystore2.IKeystoreService/default as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.

Oh, due to my oversight, I forgot to add the keymaster service. I need to see if I have time to rectify it next month. It seems the keystore hal wasn't added either. I'm confused, I remember adding it locally.

I pulled that update with those and updated two minor things for testing and made it as the Android 15 branch. Gave credit to you and added a readme with credits to everyone since I deleted the other tree I used (I had it set to private that was the corrected version I was using, my apologies. It was used for testing originally and the BotchedRPR tree was for him trying to work on Decrypt here. Only difference was that change you asked for in the private one.)
Also one question about the vendor.prop since that I have not messed with or seen.
# Crypto ro.hardware.keystore_desede=true ro.crypto.metadata_init_delete_all_keys.enabled=true ro.product.cuptsm=REALME|ESE|01|02 vendor.wv.oemcrypto.debug.enable_prov40=true
Should that be calling REALME or our device?

I think using README is better. I will try the prop commands you mentioned.

Did you ever attempt a new build? Also I've tried that one you had posted and it still never booted. I also tried various attempts myself and could not get it to boot. I know the original tree you did was a rebase off of the one I had then modified to a Houji rebuild that had a working decrypt. I don't know if its cause I am on NEEA build and that's causing the issue (I doubt).

[azzzddddd]

A15

Those 3 builds you have posted herehttps://github.com/azzzddddd/recovery_device_tree_NX769J/releases did not boot for me on A15 (OS 10.0.4). All get stuck at starting the Keystore service. Just thought I would pass that along.
12-21 19:32:33.920 1 1 E init : Control message: Could not find 'aidl/android.system.keystore2.IKeystoreService/default' for ctl.interface_start from pid: 492 (/system/bin/servicemanager) 05-27 13:15:10.651 506 506 W ServiceManager: Waited one second for android.system.keystore2.IKeystoreService/default (is service started? are binder threads started and available?) 05-27 13:15:10.651 492 492 I servicemanager: Since 'android.system.keystore2.IKeystoreService/default' could not be found, trying to start it as a lazy AIDL service 05-27 13:15:10.651 492 2308 W libc : Unable to set property "ctl.interface_start" to "aidl/android.system.keystore2.IKeystoreService/default": error code: 0x20 05-27 13:15:10.651 492 2308 I servicemanager: Tried to start aidl service android.system.keystore2.IKeystoreService/default as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.

Oh, due to my oversight, I forgot to add the keymaster service. I need to see if I have time to rectify it next month. It seems the keystore hal wasn't added either. I'm confused, I remember adding it locally.

I pulled that update with those and updated two minor things for testing and made it as the Android 15 branch. Gave credit to you and added a readme with credits to everyone since I deleted the other tree I used (I had it set to private that was the corrected version I was using, my apologies. It was used for testing originally and the BotchedRPR tree was for him trying to work on Decrypt here. Only difference was that change you asked for in the private one.)
Also one question about the vendor.prop since that I have not messed with or seen.
# Crypto ro.hardware.keystore_desede=true ro.crypto.metadata_init_delete_all_keys.enabled=true ro.product.cuptsm=REALME|ESE|01|02 vendor.wv.oemcrypto.debug.enable_prov40=true
Should that be calling REALME or our device?

I think using README is better. I will try the prop commands you mentioned.

Did you ever attempt a new build? Also I've tried that one you had posted and it still never booted. I also tried various attempts myself and could not get it to boot. I know the original tree you did was a rebase off of the one I had then modified to a Houji rebuild that had a working decrypt. I don't know if its cause I am on NEEA build and that's causing the issue (I doubt).

My abilities are limited, and I am at my wit's end, but I have heard that TWRP for Xiaomi sm8650 can successfully decrypt the data. You can go and compare it.🤔
xiaomi sm8650 twrp
This is the author, but he hasn't published it on GitHub.😢
cc.zip