Development [KERNEL] [blu_spark r139 OP9/Pro] [A13 Custom]

[eng.stk]

Than state that in the post?

It's implied on every release post and been discussed.
No need to get salty.

 

[golfgtiedition30]

{Mod edit: Quoted post has been deleted. Oswald Boelcke}
And there's no need for language like that...

 

[osm0sis]

Having a misunderstanding and/or disagreement is one thing, but insults and name-calling cross a line.

 

[Badger50]

Thread lightly cleaned.

As osm0sis stated above, there is absolutely no need for name calling if there are disagreements. Please be courteous when replying to other members as is
required by XDA Rule 2.3:

2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.

Your cooperation is expected and appreciated in matters such as these forum wide. Thank you, and a pleasant day to all.

-Regards: Badger50

 

[skywalker_fakih]

Does this work on custom roms based on oos13?
Like latest nameless rom?

 

[eng.stk]

Does this work on custom roms based on oos13?
Like latest nameless rom?

You have your answer a couple posts back, don't be lazy.

 

[reffu]

Flashed the latest r_123 on OnePlus 9 Pro (LE2123) (throught Franco Kernel Manager app) on the rooted Nameless AOSP latest build, which is A13, based on OOS13(!) firmware. Booted, but stuck on the lockscreen, with not working touchscreen, "no cellular data" is showing. Can't shut down normally by long pressing only power button, pressing all 3 keys shuts down.
Kinda expected that behaviour, so I backed up previus boot img, and safely resotred it through a fastboot.
Showing this just for someone who would try to flash it on OOS13 firmware based custom. Don't do it yet

Just confirming that I flashed through Kernel Flasher (OP9 non-pro Nameless A13, based on OOS13) and saw the same behavior of touchscreen not working and no cellular data, so it's not limited to just OP9 Pro or FKM.

 

[Mr.Conkel]

On Crdroid v9.1 (01/14/23) with r123 installed warp charging is a bit buggy.
It works but for a very limited amount of time, normally resulting in taking out the charger and plugging it in again just for it to warp charge.
Note that the device isn't too hot in these cases and should be in optimal condition to warp charge correctly as it does start as soon as the cable is plugged in and only stops sometime after.

 

[eng.stk]

On Crdroid v9.1 (01/14/23) with r123 installed warp charging is a bit buggy.
It works but for a very limited amount of time, normally resulting in taking out the charger and plugging it in again just for it to warp charge.
Note that the device isn't too hot in these cases and should be in optimal condition to warp charge correctly as it does start as soon as the cable is plugged in and only stops sometime after.

That's known with some custom stuff, there's nothing more to add for it.
Feel free to send a patch our way.

 

[Mr.Conkel]

That's known with some custom stuff, there's nothing more to add for it.
Feel free to send a patch our way.

If only I knew how, I'm not sure how similar all this is too other kernels like Requiem where I seem to have less charging issues and Arter97 where I have no issues at all (I have used every kernel from a custom rom, 9/10 its Crdroid)
The other issue is Keystore which you may be able to talk to Gwolfu (Gabriel) about which is an issue with the kernel and it can log you out of accounts like Microsoft outlook, Instagram, Facebook, Snapchat etc.
I do remember him mentioning the issue that it was indeed due to the kernel if I find the mention I will paste it here. But I am also having my outlook accounts logout randomly so far though that's the only problem.
I'm just trying to help report known issues

 

[Mr.Conkel]

Found it, hopefully this will give you enough insight on how to fix these errors. I wouldn't really know what I'm looking at so

Revert "arm64: mm: Don't invalidate FROM_DEVICE buffers at start of D… · DerpFest-Devices/[email protected]

…MA transfer" This reverts commit 7b9c3bfbad2510478ac29221d2c40a09184ce6a1. This causes issues with Lahaina, especially with keystore. Signed-off-by: Juhyung Park <[email protected]&...

github.com

 

[alb94]

If only I knew how, I'm not sure how similar all this is too other kernels like Requiem where I seem to have less charging issues and Arter97 where I have no issues at all (I have used every kernel from a custom rom, 9/10 its Crdroid)
The other issue is Keystore which you may be able to talk to Gwolfu (Gabriel) about which is an issue with the kernel and it can log you out of accounts like Microsoft outlook, Instagram, Facebook, Snapchat etc.
I do remember him mentioning the issue that it was indeed due to the kernel if I find the mention I will paste it here. But I am also having my outlook accounts logout randomly so far though that's the only problem.
I'm just trying to help report known issues

Man, I know you from the telegram. What I can say is that I never had problems with keystore again. I've already used this latest kernel on Crdroid, Nameless, Stag and now I'm testing it on EvoX, and so far I don't have those problems you mentioned. About the Outlook account, do you use any backup application to restore it?

 

[Mr.Conkel]

Man, I know you from the telegram. What I can say is that I never had problems with keystore again. I've already used this latest kernel on Crdroid, Nameless, Stag and now I'm testing it on EvoX, and so far I don't have those problems you mentioned. About the Outlook account, do you use any backup application to restore it?

No I don't, but my outlook account has been logging itself out recently.
I haven't had any issues since I've logged back in.
I flashed clean yesterday latest version and this kernel with the recommended app to do so I'm not sure what exactly the issue is..

 

[Aballamis]

@eng.stk

You say you only support OOS but I'm noticing all the current builds are custom OS only?

I am on crDroid 9.1, so if no support, I guess disregard and I'll hope somebody else can help.

When I flash in latest unofficial TWRP, getting error: vendor_dlkm larger than vendor_dlkm partition: aborting. I would throw in a log, but it's been forever since I exported a recovery log. I'll try to figure it out.

If anyone reads this and has any ideas, I'd appreciate it. For some reason, the crDroid kernel REALLY doesn't like the aftermarket Bluetooth adapter for my Audi, which is a big problem, as the car has no Aux port. I was hoping blu_spark would fix it.

 

[osm0sis]

@eng.stk

You say you only support OOS but I'm noticing all the current builds are custom OS only?

I am on crDroid 9.1, so if no support, I guess disregard and I'll hope somebody else can help.

When I flash in latest unofficial TWRP, getting error: vendor_dlkm larger than vendor_dlkm partition: aborting. I would throw in a log, but it's been forever since I exported a recovery log. I'll try to figure it out.

If anyone reads this and has any ideas, I'd appreciate it. For some reason, the crDroid kernel REALLY doesn't like the aftermarket Bluetooth adapter for my Audi, which is a big problem, as the car has no Aux port. I was hoping blu_spark would fix it.

No such issues here:

Installing zip file '/sdcard/franco.kernel_updater/blu_spark_r123-custom_op9x_9feb79506.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
I:Update binary zip
Verifying package compatibility...
Package doesn't contain compatibility.zip entry
I:Extracting updater binary 'META-INF/com/google/android/update-binary'
I:Zip does not contain SELinux file_contexts file in its root.
 
Archive:  /sdcard/franco.kernel_updater/blu_spark_r123-custom_op9x_9feb79506.zip
  inflating: tools/fec
  inflating: tools/httools_static
  inflating: ramdisk/overlay.d/init.blu_spark.rc
  inflating: META-INF/com/google/android/updater-script
  inflating: LICENSE
  inflating: META-INF/com/google/android/update-binary
  inflating: ramdisk/overlay.d/sbin/init.blu_spark_boot.sh
  inflating: vendor_ramdisk/lib/modules/msm_drm.ko
  inflating: tools/magiskpolicy
  inflating: vendor_dlkm.img
  inflating: tools/ak3-core.sh
  inflating: Image
  inflating: anykernel.sh
  inflating: tools/magiskboot
  inflating: tools/busybox
  inflating: tools/lptools_static
  inflating: banner
                          _   _
    ___ _ __   __ _   ___| |_| | __
   / _ \ '_ \ / _` | / __| __| |/ /
  |  __/ | | | (_| |_\__ \ |_|   <
   \___|_| |_|\__, (_)___/\__|_|\_\ 
              |___/
 
 
### blu_spark kernel for OnePlus 9/Pro ###
 
AnyKernel3 by osm0sis @ xda-developers
 
AK_BASE_VERSION=20230110
 
Unmounting...
Mounting...
/vendor (fstab)
/product (fstab)
/system_ext (fstab)
/system_root (fstab)
/apex/com.android.adbd (loop)
/apex/com.android.adservices (loop)
/apex/com.android.apex.cts.shim (loop)
/apex/com.android.appsearch (loop)
/apex/com.android.art (loop)
/apex/com.android.btservices (loop)
/apex/com.android.cellbroadcast (loop)
/apex/com.android.conscrypt (loop)
/apex/com.android.extservices (loop)
/apex/com.android.i18n (loop)
/apex/com.android.ipsec (loop)
/apex/com.android.media (loop)
/apex/com.android.media.swcodec (loop)
/apex/com.android.mediaprovider (loop)
/apex/com.android.neuralnetworks (loop)
/apex/com.android.ondevicepersonalization (loop)
/apex/com.android.os.statsd (loop)
/apex/com.android.permission (loop)
/apex/com.android.resolv (loop)
/apex/com.android.runtime (loop)
/apex/com.android.scheduling (loop)
/apex/com.android.sdkext (loop)
/apex/com.android.tethering (loop)
/apex/com.android.tzdata (loop)
/apex/com.android.uwb (loop)
/apex/com.android.vndk (loop)
/apex/com.android.wifi (loop)
/system (bind)
/persist (direct)
 
Checking device...
OnePlus9Pro
 
Checking Android version...
13
 
Installing...
Setting up for simple automatic vendor_boot flashing...
/dev/block/by-name/boot_a
/data: 0 bytes trimmed
192+0 records in
192+0 records out
201326592 bytes (192.0MB) copied, 0.210646 seconds, 911.5MB/s
Parsing boot image: [/tmp/anykernel/boot.img]
HEADER_VER      [3]
KERNEL_SZ       [40954368]
RAMDISK_SZ      [45617714]
OS_VERSION      [13.0.0]
OS_PATCH_LEVEL  [2023-01]
PAGESIZE        [4096]
CMDLINE         []
KERNEL_FMT      [raw]
RAMDISK_FMT     [lz4_legacy]
VBMETA
266231 blocks
Loading cpio: [ramdisk-new.cpio]
Loading cpio: [ramdisk-new.cpio]
Extract [.backup/.magisk] to [/tmp/anykernel/split_img/.magisk]
 
Magisk detected! Patching kernel so reflashing Magisk is not necessary...
Parsing boot image: [/tmp/anykernel/boot.img]
HEADER_VER      [3]
KERNEL_SZ       [40954368]
RAMDISK_SZ      [45617714]
OS_VERSION      [13.0.0]
OS_PATCH_LEVEL  [2023-01]
PAGESIZE        [4096]
CMDLINE         []
KERNEL_FMT      [raw]
RAMDISK_FMT     [lz4_legacy]
VBMETA
Repack to boot image: [/tmp/anykernel/boot-new.img]
HEADER_VER      [3]
KERNEL_SZ       [37730816]
RAMDISK_SZ      [45619414]
OS_VERSION      [13.0.0]
OS_PATCH_LEVEL  [2023-01]
PAGESIZE        [4096]
CMDLINE         []
 
/dev/block/mapper/vendor_dlkm_a
Removing any existing vendor_dlkm_ak3...
Best group seems to be oneplus_dynamic_partitions_a
Attempting to create vendor_dlkm_ak3...
Best group seems to be oneplus_dynamic_partitions_a
Growing partition 1
Creating dm partition for vendor_dlkm_ak3 answered 1 at /dev/block/dm-7
Replacing vendor_dlkm_a with vendor_dlkm_ak3...
Best group seems to be oneplus_dynamic_partitions_a
Best group seems to be oneplus_dynamic_partitions_a
Creating dm partition for vendor_dlkm_ak3 answered 1 at /dev/block/dm-7
Best group seems to be oneplus_dynamic_partitions_a
 
/dev/block/by-name/vendor_boot_a
192+0 records in
192+0 records out
201326592 bytes (192.0MB) copied, 0.222141 seconds, 864.3MB/s
Parsing boot image: [/tmp/anykernel/boot.img]
VENDOR_BOOT_HDR
HEADER_VER      [3]
RAMDISK_SZ      [20294272]
DTB_SZ          [2833287]
PAGESIZE        [4096]
NAME            []
CMDLINE         [androidboot.hardware=qcom androidboot.memcg=1 androidboot.usbcontroller=a600000.dwc3 cgroup.memory=nokmem,nosocket loop.max_part=7 lpm_levels.sleep_disabled=1 msm_rtb.filter=0x237 pcie_ports=compat service_locator.enable=1 swiotlb=0 ip6table_raw.raw_before_defrag=1 iptable_raw.raw_before_defrag=1 buildvariant=userdebug]
RAMDISK_FMT     [lz4_legacy]
VBMETA
84883 blocks
Loading cpio: [ramdisk-new.cpio]
cp: '/tmp/anykernel/split_img/dtb' and 'dtb' are the same file
Parsing boot image: [/tmp/anykernel/boot.img]
VENDOR_BOOT_HDR
HEADER_VER      [3]
RAMDISK_SZ      [20294272]
DTB_SZ          [2833287]
PAGESIZE        [4096]
NAME            []
CMDLINE         [androidboot.hardware=qcom androidboot.memcg=1 androidboot.usbcontroller=a600000.dwc3 cgroup.memory=nokmem,nosocket loop.max_part=7 lpm_levels.sleep_disabled=1 msm_rtb.filter=0x237 pcie_ports=compat service_locator.enable=1 swiotlb=0 ip6table_raw.raw_before_defrag=1 iptable_raw.raw_before_defrag=1 buildvariant=userdebug]
RAMDISK_FMT     [lz4_legacy]
VBMETA
Repack to boot image: [/tmp/anykernel/boot-new.img]
HEADER_VER      [3]
RAMDISK_SZ      [20322007]
DTB_SZ          [2833287]
PAGESIZE        [4096]
NAME            []
CMDLINE         [androidboot.hardware=qcom androidboot.memcg=1 androidboot.usbcontroller=a600000.dwc3 cgroup.memory=nokmem,nosocket loop.max_part=7 lpm_levels.sleep_disabled=1 msm_rtb.filter=0x237 pcie_ports=compat service_locator.enable=1 swiotlb=0 ip6table_raw.raw_before_defrag=1 iptable_raw.raw_before_defrag=1 buildvariant=userdebug]
 
Unmounting...
Unmounting apex...
 
Done!
I:Updater process ended with RC=0
I:Install took 67 second(s).

 

[alb94]

@eng.stk

You say you only support OOS but I'm noticing all the current builds are custom OS only?

I am on crDroid 9.1, so if no support, I guess disregard and I'll hope somebody else can help.

When I flash in latest unofficial TWRP, getting error: vendor_dlkm larger than vendor_dlkm partition: aborting. I would throw in a log, but it's been forever since I exported a recovery log. I'll try to figure it out.

If anyone reads this and has any ideas, I'd appreciate it. For some reason, the crDroid kernel REALLY doesn't like the aftermarket Bluetooth adapter for my Audi, which is a big problem, as the car has no Aux port. I was hoping blu_spark would fix it.

Do you have root? If so, just flash it via FKM. In the post he attaches the link for you to import the settings there and then flash.

 

[Mr.Conkel]

@eng.stk

You say you only support OOS but I'm noticing all the current builds are custom OS only?

I am on crDroid 9.1, so if no support, I guess disregard and I'll hope somebody else can help.

When I flash in latest unofficial TWRP, getting error: vendor_dlkm larger than vendor_dlkm partition: aborting. I would throw in a log, but it's been forever since I exported a recovery log. I'll try to figure it out.

If anyone reads this and has any ideas, I'd appreciate it. For some reason, the crDroid kernel REALLY doesn't like the aftermarket Bluetooth adapter for my Audi, which is a big problem, as the car has no Aux port. I was hoping blu_spark would fix it.

Usually I don't use Twrp for flashing this kernel. However, when doing so I fully recommend you decrypt your device as it will break sideload updates to the slot you install it too.
But in any case, try using Crdroid recovery and sideload the zip I'm using the kernel just fine on 01/20/23 release

 

[Aballamis]

Usually I don't use Twrp for flashing this kernel. However, when doing so I fully recommend you decrypt your device as it will break sideload updates to the slot you install it too.
But in any case, try using Crdroid recovery and sideload the zip I'm using the kernel just fine on 01/20/23 release

What will break side load updates? The kernel?

 

[Mr.Conkel]

What will break side load updates? The kernel?

Yea, its due to the resize in vendor_dlkm.
Regardless if you replace the imgs with the stock ones something gets tripped due to the resize. Therefore, it will break side loading on the slot you install it too.
For example, if you were to install on slot a in Crdroid then flash an update you would now be on slot b. However if another update drops you cannot flash it because of the resize, simply put it won't let you.
The best way to avoid issues is to decrypt and backup your data with twrp then just move other crucial files to pc and clean flash. Then you can restore your data, I do this a lot myself as I love the kernel but it is a bit tedious to update

 

[Aballamis]

No such issues here:

Installing zip file '/sdcard/franco.kernel_updater/blu_spark_r123-custom_op9x_9feb79506.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
I:Update binary zip
Verifying package compatibility...
Package doesn't contain compatibility.zip entry
I:Extracting updater binary 'META-INF/com/google/android/update-binary'
I:Zip does not contain SELinux file_contexts file in its root.
 
Archive:  /sdcard/franco.kernel_updater/blu_spark_r123-custom_op9x_9feb79506.zip
  inflating: tools/fec
  inflating: tools/httools_static
  inflating: ramdisk/overlay.d/init.blu_spark.rc
  inflating: META-INF/com/google/android/updater-script
  inflating: LICENSE
  inflating: META-INF/com/google/android/update-binary
  inflating: ramdisk/overlay.d/sbin/init.blu_spark_boot.sh
  inflating: vendor_ramdisk/lib/modules/msm_drm.ko
  inflating: tools/magiskpolicy
  inflating: vendor_dlkm.img
  inflating: tools/ak3-core.sh
  inflating: Image
  inflating: anykernel.sh
  inflating: tools/magiskboot
  inflating: tools/busybox
  inflating: tools/lptools_static
  inflating: banner
                          _   _
    ___ _ __   __ _   ___| |_| | __
   / _ \ '_ \ / _` | / __| __| |/ /
  |  __/ | | | (_| |_\__ \ |_|   <
   \___|_| |_|\__, (_)___/\__|_|\_\
              |___/
 
 
### blu_spark kernel for OnePlus 9/Pro ###
 
AnyKernel3 by osm0sis @ xda-developers
 
AK_BASE_VERSION=20230110
 
Unmounting...
Mounting...
/vendor (fstab)
/product (fstab)
/system_ext (fstab)
/system_root (fstab)
/apex/com.android.adbd (loop)
/apex/com.android.adservices (loop)
/apex/com.android.apex.cts.shim (loop)
/apex/com.android.appsearch (loop)
/apex/com.android.art (loop)
/apex/com.android.btservices (loop)
/apex/com.android.cellbroadcast (loop)
/apex/com.android.conscrypt (loop)
/apex/com.android.extservices (loop)
/apex/com.android.i18n (loop)
/apex/com.android.ipsec (loop)
/apex/com.android.media (loop)
/apex/com.android.media.swcodec (loop)
/apex/com.android.mediaprovider (loop)
/apex/com.android.neuralnetworks (loop)
/apex/com.android.ondevicepersonalization (loop)
/apex/com.android.os.statsd (loop)
/apex/com.android.permission (loop)
/apex/com.android.resolv (loop)
/apex/com.android.runtime (loop)
/apex/com.android.scheduling (loop)
/apex/com.android.sdkext (loop)
/apex/com.android.tethering (loop)
/apex/com.android.tzdata (loop)
/apex/com.android.uwb (loop)
/apex/com.android.vndk (loop)
/apex/com.android.wifi (loop)
/system (bind)
/persist (direct)
 
Checking device...
OnePlus9Pro
 
Checking Android version...
13
 
Installing...
Setting up for simple automatic vendor_boot flashing...
/dev/block/by-name/boot_a
/data: 0 bytes trimmed
192+0 records in
192+0 records out
201326592 bytes (192.0MB) copied, 0.210646 seconds, 911.5MB/s
Parsing boot image: [/tmp/anykernel/boot.img]
HEADER_VER      [3]
KERNEL_SZ       [40954368]
RAMDISK_SZ      [45617714]
OS_VERSION      [13.0.0]
OS_PATCH_LEVEL  [2023-01]
PAGESIZE        [4096]
CMDLINE         []
KERNEL_FMT      [raw]
RAMDISK_FMT     [lz4_legacy]
VBMETA
266231 blocks
Loading cpio: [ramdisk-new.cpio]
Loading cpio: [ramdisk-new.cpio]
Extract [.backup/.magisk] to [/tmp/anykernel/split_img/.magisk]
 
Magisk detected! Patching kernel so reflashing Magisk is not necessary...
Parsing boot image: [/tmp/anykernel/boot.img]
HEADER_VER      [3]
KERNEL_SZ       [40954368]
RAMDISK_SZ      [45617714]
OS_VERSION      [13.0.0]
OS_PATCH_LEVEL  [2023-01]
PAGESIZE        [4096]
CMDLINE         []
KERNEL_FMT      [raw]
RAMDISK_FMT     [lz4_legacy]
VBMETA
Repack to boot image: [/tmp/anykernel/boot-new.img]
HEADER_VER      [3]
KERNEL_SZ       [37730816]
RAMDISK_SZ      [45619414]
OS_VERSION      [13.0.0]
OS_PATCH_LEVEL  [2023-01]
PAGESIZE        [4096]
CMDLINE         []
 
/dev/block/mapper/vendor_dlkm_a
Removing any existing vendor_dlkm_ak3...
Best group seems to be oneplus_dynamic_partitions_a
Attempting to create vendor_dlkm_ak3...
Best group seems to be oneplus_dynamic_partitions_a
Growing partition 1
Creating dm partition for vendor_dlkm_ak3 answered 1 at /dev/block/dm-7
Replacing vendor_dlkm_a with vendor_dlkm_ak3...
Best group seems to be oneplus_dynamic_partitions_a
Best group seems to be oneplus_dynamic_partitions_a
Creating dm partition for vendor_dlkm_ak3 answered 1 at /dev/block/dm-7
Best group seems to be oneplus_dynamic_partitions_a
 
/dev/block/by-name/vendor_boot_a
192+0 records in
192+0 records out
201326592 bytes (192.0MB) copied, 0.222141 seconds, 864.3MB/s
Parsing boot image: [/tmp/anykernel/boot.img]
VENDOR_BOOT_HDR
HEADER_VER      [3]
RAMDISK_SZ      [20294272]
DTB_SZ          [2833287]
PAGESIZE        [4096]
NAME            []
CMDLINE         [androidboot.hardware=qcom androidboot.memcg=1 androidboot.usbcontroller=a600000.dwc3 cgroup.memory=nokmem,nosocket loop.max_part=7 lpm_levels.sleep_disabled=1 msm_rtb.filter=0x237 pcie_ports=compat service_locator.enable=1 swiotlb=0 ip6table_raw.raw_before_defrag=1 iptable_raw.raw_before_defrag=1 buildvariant=userdebug]
RAMDISK_FMT     [lz4_legacy]
VBMETA
84883 blocks
Loading cpio: [ramdisk-new.cpio]
cp: '/tmp/anykernel/split_img/dtb' and 'dtb' are the same file
Parsing boot image: [/tmp/anykernel/boot.img]
VENDOR_BOOT_HDR
HEADER_VER      [3]
RAMDISK_SZ      [20294272]
DTB_SZ          [2833287]
PAGESIZE        [4096]
NAME            []
CMDLINE         [androidboot.hardware=qcom androidboot.memcg=1 androidboot.usbcontroller=a600000.dwc3 cgroup.memory=nokmem,nosocket loop.max_part=7 lpm_levels.sleep_disabled=1 msm_rtb.filter=0x237 pcie_ports=compat service_locator.enable=1 swiotlb=0 ip6table_raw.raw_before_defrag=1 iptable_raw.raw_before_defrag=1 buildvariant=userdebug]
RAMDISK_FMT     [lz4_legacy]
VBMETA
Repack to boot image: [/tmp/anykernel/boot-new.img]
HEADER_VER      [3]
RAMDISK_SZ      [20322007]
DTB_SZ          [2833287]
PAGESIZE        [4096]
NAME            []
CMDLINE         [androidboot.hardware=qcom androidboot.memcg=1 androidboot.usbcontroller=a600000.dwc3 cgroup.memory=nokmem,nosocket loop.max_part=7 lpm_levels.sleep_disabled=1 msm_rtb.filter=0x237 pcie_ports=compat service_locator.enable=1 swiotlb=0 ip6table_raw.raw_before_defrag=1 iptable_raw.raw_before_defrag=1 buildvariant=userdebug]
 
Unmounting...
Unmounting apex...
 
Done!
I:Updater process ended with RC=0
I:Install took 67 second(s).

Seems your log is from Franco kernel updater, my post said I used TWRP.