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

Search This thread
By:
Advanced…
Aballamis

Aballamis

Senior Member
Oct 10, 2016
138
19
United States
Samsung Galaxy Tab A series
OnePlus 5
osm0sis said:
No such issues here:
Code: 
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).
🤔
Click to expand...
Click to collapse
But thanks for the tip
 
Aballamis

Aballamis

Senior Member
Oct 10, 2016
138
19
United States
Samsung Galaxy Tab A series
OnePlus 5
Mr.Conkel said:
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
Click to expand...
Click to collapse
Thanks for the info. Yea, that's the exact error I got in TWRP. That vendor_dlkm was bigger than that partition. That's why it wouldn't flash directly in TWRP
 
Aballamis

Aballamis

Senior Member
Oct 10, 2016
138
19
United States
Samsung Galaxy Tab A series
OnePlus 5
alb94 said:
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.
Click to expand...
Click to collapse
Yea I got it to work with fkm. Although I copy & pasted the link from the "link" part when clicked on the "custom" config from the OP into the config part of the fkm flasher, but it said there was some problem and to contact my developer. But I manually flashed and it worked
 
Aballamis

Aballamis

Senior Member
Oct 10, 2016
138
19
United States
Samsung Galaxy Tab A series
OnePlus 5
Mr.Conkel said:
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
Click to expand...
Click to collapse
When you say you're on the 01/20/23 release, to what do you refer? The latest kernel (123) is 01/10/23 and latest crDroid is 01/13/23
 
osm0sis

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,307
34,656
Halifax
GT-i9250
Google Nexus 4
Aballamis said:
Seems your log is from Franco kernel updater, my post said I used TWRP. 🤔
Click to expand...
Click to collapse
No, that's cut from the end of my recovery.log from TWRP. You can tell from the digest/compatibility/SELinux checks and "I:" log entries.

For comparison, here's my FKM log for the same kernel:
Code: 
Archive:  /data/data/com.franco.kernel/files/blu_spark_r123-custom_op9x_9feb79506.zip
  inflating: anykernel.sh
  inflating: banner
  inflating: Image
  inflating: LICENSE
   creating: META-INF/
   creating: META-INF/com/
   creating: META-INF/com/google/
   creating: META-INF/com/google/android/
  inflating: META-INF/com/google/android/update-binary
  inflating: META-INF/com/google/android/updater-script
   creating: ramdisk/
   creating: ramdisk/overlay.d/
  inflating: ramdisk/overlay.d/init.blu_spark.rc
   creating: ramdisk/overlay.d/sbin/
  inflating: ramdisk/overlay.d/sbin/init.blu_spark_boot.sh
   creating: tools/
  inflating: tools/magiskboot
  inflating: tools/fec
  inflating: tools/busybox
  inflating: tools/lptools_static
  inflating: tools/httools_static
  inflating: tools/magiskpolicy
  inflating: tools/ak3-core.sh
  inflating: vendor_dlkm.img
   creating: vendor_ramdisk/
   creating: vendor_ramdisk/lib/
   creating: vendor_ramdisk/lib/modules/
  inflating: vendor_ramdisk/lib/modules/msm_drm.ko
                          _   _
    ___ _ __   __ _   ___| |_| | __
   / _ \ '_ \ / _` | / __| __| |/ /
  |  __/ | | | (_| |_\__ \ |_|   <
   \___|_| |_|\__, (_)___/\__|_|\_\ 
              |___/
 
 
### blu_spark kernel for OnePlus 9/Pro ###
 
AnyKernel3 by osm0sis @ xda-developers
 
AK_BASE_VERSION=20230110
 
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.223058 seconds, 860.8MB/s
Parsing boot image: [/tmp/anykernel/boot.img]
HEADER_VER      [3]
KERNEL_SZ       [37730816]
RAMDISK_SZ      [45800072]
OS_VERSION      [13.0.0]
OS_PATCH_LEVEL  [2023-01]
PAGESIZE        [4096]
CMDLINE         []
KERNEL_FMT      [raw]
RAMDISK_FMT     [lz4_legacy]
VBMETA
267038 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       [37730816]
RAMDISK_SZ      [45800072]
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      [45812502]
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-12
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-12
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.246686 seconds, 778.3MB/s
Parsing boot image: [/tmp/anykernel/boot.img]
VENDOR_BOOT_HDR
HEADER_VER      [3]
RAMDISK_SZ      [20321781]
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
84993 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      [20321781]
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      [20324197]
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]
 
 
Done!
 
Last edited:
Mr.Conkel

Mr.Conkel

Senior Member
Oct 10, 2020
300
84
London
Nexus 7 (2013)
OnePlus 5T
Aballamis said:
When you say you're on the 01/20/23 release, to what do you refer? The latest kernel (123) is 01/10/23 and latest crDroid is 01/13/23
Click to expand...
Click to collapse
There are test builds on SF for Crdroid. Not totally recommended you use them as they might have unfinished features or bugs. But most of them are fine for daily use. They're not official releases so there's no changelog just look in the v9 folder
 
  • Like
Reactions: Aballamis
Aballamis

Aballamis

Senior Member
Oct 10, 2016
138
19
United States
Samsung Galaxy Tab A series
OnePlus 5
osm0sis said:
No, that's cut from the end of my recovery.log from TWRP. You can tell from the digest/compatibility/SELinux checks and "I:" log entries.

For comparison, here's my FKM log for the same kernel:
Code: 
Archive:  /data/data/com.franco.kernel/files/blu_spark_r123-custom_op9x_9feb79506.zip
  inflating: anykernel.sh
  inflating: banner
  inflating: Image
  inflating: LICENSE
   creating: META-INF/
   creating: META-INF/com/
   creating: META-INF/com/google/
   creating: META-INF/com/google/android/
  inflating: META-INF/com/google/android/update-binary
  inflating: META-INF/com/google/android/updater-script
   creating: ramdisk/
   creating: ramdisk/overlay.d/
  inflating: ramdisk/overlay.d/init.blu_spark.rc
   creating: ramdisk/overlay.d/sbin/
  inflating: ramdisk/overlay.d/sbin/init.blu_spark_boot.sh
   creating: tools/
  inflating: tools/magiskboot
  inflating: tools/fec
  inflating: tools/busybox
  inflating: tools/lptools_static
  inflating: tools/httools_static
  inflating: tools/magiskpolicy
  inflating: tools/ak3-core.sh
  inflating: vendor_dlkm.img
   creating: vendor_ramdisk/
   creating: vendor_ramdisk/lib/
   creating: vendor_ramdisk/lib/modules/
  inflating: vendor_ramdisk/lib/modules/msm_drm.ko
                          _   _
    ___ _ __   __ _   ___| |_| | __
   / _ \ '_ \ / _` | / __| __| |/ /
  |  __/ | | | (_| |_\__ \ |_|   <
   \___|_| |_|\__, (_)___/\__|_|\_\
              |___/
 
 
### blu_spark kernel for OnePlus 9/Pro ###
 
AnyKernel3 by osm0sis @ xda-developers
 
AK_BASE_VERSION=20230110
 
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.223058 seconds, 860.8MB/s
Parsing boot image: [/tmp/anykernel/boot.img]
HEADER_VER      [3]
KERNEL_SZ       [37730816]
RAMDISK_SZ      [45800072]
OS_VERSION      [13.0.0]
OS_PATCH_LEVEL  [2023-01]
PAGESIZE        [4096]
CMDLINE         []
KERNEL_FMT      [raw]
RAMDISK_FMT     [lz4_legacy]
VBMETA
267038 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       [37730816]
RAMDISK_SZ      [45800072]
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      [45812502]
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-12
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-12
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.246686 seconds, 778.3MB/s
Parsing boot image: [/tmp/anykernel/boot.img]
VENDOR_BOOT_HDR
HEADER_VER      [3]
RAMDISK_SZ      [20321781]
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
84993 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      [20321781]
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      [20324197]
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]
 
 
Done!
Click to expand...
Click to collapse
Aaahhh. It looked like TWRP, what confused me was this part of first line "Installing zip file '/sdcard/franco.kernel_updater". I guess you just had downloaded it from the config in FKM or something so that was the directory. I was hasty in my reply. Plus it just didn't feel right for me to question - not putting anybody on a pedestal but I've been around long enough to see your username on lots of things, I.E. anykernel3. Odds & ends was my first bookmark, too.

Foot in mouth, tail tucked accordingly, returning to my corner, lol.
 
  • Haha
Reactions: osm0sis
Aballamis

Aballamis

Senior Member
Oct 10, 2016
138
19
United States
Samsung Galaxy Tab A series
OnePlus 5
Mr.Conkel said:
There are test builds on SF for Crdroid. Not totally recommended you use them as they might have unfinished features or bugs. But most of them are fine for daily use. They're not official releases so there's no changelog just look in the v9 folder
Click to expand...
Click to collapse
Oh, ok. Thanks for the info. I might check it out. I usually stick to stable builds. I've got plenty of backup devices, I just don't know enough hardcore knowledge and coding and stuff to sift through stuff. I'm much more well versed in implementation of tools and mods than understanding the programming and language. I really wanna learn, but it's all stuff you've gotta (I guess) teach yourself online and have a lot of patience. I've tried to go to local community colleges in different places I've lived and take specific classes, but they never offer anything too relevant. Go up to the head/chair of Computer Science dept and he'll say "what the hell is mobile Linux coding?" - Phones, d*ck!
 
  • Haha
Reactions: Mr.Conkel
B

bonfire9211

Member
Aug 18, 2017
18
4
OnePlus 9 Pro
Klusio19 said:
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 :D
Click to expand...
Click to collapse
So I seem to have made the same mistake with one issue: I haven't flashed twrp yet and am stuck on the nameless recovery which only allows adb sideload flashing. And PC doesn't recognize the phone in any state giving me "device descriptor request failed".
If anyone has a solution I'll appreciate it as my phone is bricked for now.
I'm using a 9 pro btw
 
K

Klusio19

Senior Member
Nov 13, 2018
201
47
Tarnobrzeg
OnePlus 9 Pro
bonfire9211 said:
So I seem to have made the same mistake with one issue: I haven't flashed twrp yet and am stuck on the nameless recovery which only allows adb sideload flashing. And PC doesn't recognize the phone in any state giving me "device descriptor request failed".
If anyone has a solution I'll appreciate it as my phone is bricked for now.
I'm using a 9 pro btw
Click to expand...
Click to collapse
Just flash stock boot.img from Nameless via fastboot
 
You must log in or register to reply here.

Similar threads

Steve0007
  • Sticky
How To Guide [GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13-F20/F74
Replies
2K
Views
302K
TheGhost1951
TheGhost1951
OPTeam
  • Sticky
General [OnePlus 9 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
Replies
835
Views
219K
lenndogg228
lenndogg228
stazz83
Themes / Apps / Mods Gcam for OnePlus 9 pro
Replies
417
Views
136K
Arcide
Arcide
chandu dyavanapelli
Development [ROM][OOS CAM][OFFICIAL][OnePlus 9 Pro][13.0.0_r30]Nameless AOSP[2023/03/20]
Replies
2K
Views
194K
cavid3232
cavid3232
kristofpetho
  • Locked
Development EOL - [KERNEL] [OOS] Omega Kernel OOS11 [September 18, 2021]
Replies
937
Views
106K
Timmmmaaahh!
Timmmmaaahh!

Top Liked Posts

24 Hours 30 Days All time
  • 1
    U
    unzumutbar
    T0Tal_N00b said:
    running latest Nameless, No sound whatsoever. tried installing viper and other audio mods with the same result. Wavelet gives me an error saying wavelet was unable to instantiate QUALCOMM technologies virtualization... Also tried with disabling dolby and its other related packages and without as well
    Click to expand...
    Click to collapse
    Update Nameless. Sound on 230320 works again with the kernel.
    View
  • 10
    eng.stk
    eng.stk
    blu_spark_r129 release (A13 custom)

    New build is up (y)

    I tested with lineage-20.0-20230214-nightly, kernel build may work with other ROMs that use similar device/kernel trees (confirm before flashing).
    This kernel is tested for the 9 Pro but it's unified, so should work for the OP9 also.

    For flashing and easy of install logging, Kernel Flasher is recommended

    You can use Kernel Flasher/FKM download kernel feature, just import the link bellow in the app updates/flash section.
    Download config: custom


    Changelog:
    • ThinLTO build with custom upstream LLVM 16.x (Clang 16.0.0-rc3 + LLD linker + IAS)
    • HACK: binder: Disable freeze related ioctls (fixes ongoing issues and crashed in LOS20, without changing freezer ROM settings)
    • For root, Magisk 25.2 or newer is mandatory
    Click to expand...
    Click to collapse


    Keep in mind: I am mostly interested on debugging stuff with logs and reproducible steps to replicate the issue.


    No mirrors please
    Don't forget to hit like, it's free :)
    View
    10
    eng.stk
    eng.stk
    blu_spark_r136 release (A13 custom)

    New build is up (y)

    I tested with lineage-20.0-20230314-nightly, kernel build may work with other ROMs that use similar device/kernel trees (confirm before flashing).
    This is only for ROMS with A13 fw kernel patchset.
    This kernel is tested for the 9 Pro but it's unified, so should work for the OP9 also.

    For flashing and easy of install logging, Kernel Flasher is recommended

    You can use Kernel Flasher/FKM download kernel feature, just import the link bellow in the app updates/flash section.
    Download config: custom


    Changelog:
    • ThinLTO build with custom upstream LLVM 14.x (Clang 14.0.6 + LLD linker + IAS)
    • Merge lineage-20.0 from LineageOS/android_kernel_oneplus_sm8350
    • Small cleanup
    • Merge ASB-2023-03-05
    • For root, Magisk 25.2 or newer is mandatory
    Click to expand...
    Click to collapse


    Keep in mind: I will give no active support for custom ROMs besides LineageOS.
    I am mostly interested on debugging stuff with logs and reproducible steps to replicate the issue.


    No mirrors please
    Don't forget to hit like, it's free :)
    View
    8
    eng.stk
    eng.stk
    blu_spark_r134 release (A13 custom)

    New build is up (y)

    I tested with lineage-20.0-20230307-nightly, kernel build may work with other ROMs that use similar device/kernel trees (confirm before flashing).
    This is only for ROMS with A13 fw kernel patchset.
    This kernel is tested for the 9 Pro but it's unified, so should work for the OP9 also.

    For flashing and easy of install logging, Kernel Flasher is recommended

    You can use Kernel Flasher/FKM download kernel feature, just import the link bellow in the app updates/flash section.
    Download config: custom


    Changelog:
    • ThinLTO build with custom upstream LLVM 16.x (Clang 16.0.0-rc3 + LLD linker + IAS)
    • Merge lineage-20.0 from LineageOS/android_kernel_oneplus_sm8350
    • Rebase for vendor A13 kernel patchset
    • drivers: vendor/techpack: fix build errors for clang-16
    • make: remove op build logspam
    • defconfig: sync with lineage-20.0-20230307-nightly
    • For root, Magisk 25.2 or newer is mandatory
    Click to expand...
    Click to collapse


    Keep in mind: I am mostly interested on debugging stuff with logs and reproducible steps to replicate the issue.


    No mirrors please
    Don't forget to hit like, it's free :)
    View
    6
    eng.stk
    eng.stk
    reffu said:
    I'm guessing that the new release is based off of OOS 13, since that's how other OOS 13-based custom ROMs have behaved when trying to flash blu_spark (since the current release of blu_spark is based of OOS 12)
    Click to expand...
    Click to collapse
    This.
    Rebasing atm, will wait for the build to drop for my op9p
    View
    3
    osm0sis
    osm0sis
    I'll say it again:
    osm0sis said:
    Presumably the ROMs that things are broken with just need to merge the latest Lineage changes.
    Click to expand...
    Click to collapse

    Go report these issues in your ROM thread instead and ask them to get up to date on their Lineage base, since the base has changed due to the OOS13 firmware upgrade.
    View
  • 95
    eng.stk
    eng.stk
    DWHxIK

    Kernel features:
    • Build with custom upstream LLVM 14.x (Clang 14.0.6 + LLD linker + IAS)
    • full ThinLTO -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc
    • Less is more: stockish OP9 builds based on OnePlusOSS/android_kernel_oneplus_sm8350 for max stability
    • Systemless installer (doesn't touch system/vendor partition, OTA friendly), AnyKernel3 backend (compatible with autoflash apps)
    • Removed some debug and logging options
    • ARM enhanced performance and battery patches
    • CVE security patches, general upstream and CAF fixes for important subsystems
    • Modded schedutil governor merged from latest CAF sm8350 patchset
    • No OC, use 250HZ base timer frequency
    • msm_performance touchboost toggle on/off (enabled by default), tweaked cpu_boost driver
    • Enhanced TCP methods (westwood is default, BBR available), Network tweaks and updated drivers
    • Several I/O control tweaks, advanced filesystems enabled (F2FS, ExFAT, NTFS, CIFS & NFS)
    • ZRAM Swap (4GB LZ4 default) and with file disabled (2 GB storage gain), LZO-RLE and ZSTD are available
    • Vibrator Strength tunable and Gesture Haptic Feedback control (touchpanel and FPR)
    • KGSL fixes and general improvements for GPU driver
    • adrenoboost ready (disabled by default)
    • Backlight min brightness and brightness scaling (custom) option
    • Gamepad support enabled (xbox, ps4, switch)
    • USB2 Fast Charge (USB mode up to 900mA with MTP on)
    • FS fsync toggle on/off
    • Wakelock blockers available
    • wireguard support
    • Compatible with Kernel Flasher, EXKM, FKM , Kernel Adiutor and others


    DOWNLOAD KERNEL ZIP
    Kernel Flasher/FKM download configs: oos | custom
    (No mirrors please)​


    Setup and troubleshoot: To install just flash the zip on a stock setup with either TWRP or autoflash kernel app.
    If you come from other kernel or have any issues, you should restore your stock boot.img/vendor_boot.img or dirty flash your ROM before flashing blu_spark zip to avoid problems. Also uninstall or clean data of any kernel control app you're using.
    If you are upgrading between blu_spark versions, just flash the kernel zip.

    About bugs and reports: don't bother to post if a log isn't ready or without steps so the behavior can be replicated. I only active support stock OOS ROM with NO mods whatsoever (apart from root). That includes NO support if using xposed, Magisk with added modules, etc.
    If you're using custom ROMs (including stock based ones) and OOS Open Betas you're much on your own. I'm mostly interested on debugging stuff in stock and stable OOS.
    Also try not to spam the thread with OT. There's threads for all kind of stuff, use them.

    Going back to stock: This kernel installer doesn't change your filesystem. You can backup your boot.img/vendor_boot.img with TWRP or kernel app before flashing blu_spark if you want to go back to full stock or just dirty flash your full ROM.


    Source Code: https://github.com/engstk/op9
    Don't forget to hit thanks, it's free ;)


    OnePlus 9 Pro development unit donated by OnePlus. Big shouts to them :)
    Very proud for being on the OnePlus Developer Program, special thanks to dev relations team.
    View
    31
    eng.stk
    eng.stk
    blu_spark_r23 release

    First blu_spark build for the OP9 series is up (y)

    This kernel is tested for the 9 Pro but it's unified, so should work for the OP9 also (need some fixes since code is broken). So backup you boot if you want to test and let me know :)
    Kernel already have some merged goodies and I think I have a good base to work with. For a couple days of work, it's not bad :)
    I'll take a look into more stuff to come, some things in OP are WIP. Stay tuned!

    You can use FKM download kernel feature, just import the links bellow in the app.
    FKM download configs: oos


    Changelog:
    • Build with Google Clang 12.0.5 + LLD linker
    • Synchronize codes for OnePlus 9/Pro Oxygen 11.2.6.6.LE25AA
    • Several build error fixes and quirks handled
    • Compilation improvements an cruf removed
    • Some goodies already merged like filesystem stuff, cpu governor & boost/msm perf, TCP algos, wakelock blocker, vibration and haptic feedback control, gpu adrenoboost, etc
    • All drivers builtin, wifi stack and datarmmnet merged from CAF
    • net/wireguard: merge v1.0.20210424
    Click to expand...
    Click to collapse


    Keep in mind: I will give no active support for custom ROMs (including OOS based ones).
    I am mostly interested on debugging stuff in stock stable OOS (with logs and reproducible steps to replicate the issue).


    No mirrors please
    Don't forget to hit thanks, it's free :)
    View
    21
    Timmmmaaahh!
    Timmmmaaahh!
    [Thread Cleaned]

    Good (or perhaps not so good?) day everyone! I've removed a few posts but left the ones that matter: civilized closure of conflict – social media can learn a thing or two from this. As we sit behind our desks and in our couches (or on a plane, even that's a thing nowadays), protected by that anonymity shield, we easily throw our words out into the world. And sometimes we regret them. Unfortunately, we find it so easy to judge one another for that. But facing the fact that we're all just humans that make mistakes, I believe we know that we shouldn't judge so quickly. Now more than ever; kindness should prevail.

    Thank you for your attention and have an energetic day or quiet night in your part of the world. If you need a chat, drop me a line. Just keep our development threads focused on development and mutual respect.

    Cheers!
    Timmy
    Forum Moderator
    View
    18
    eng.stk
    eng.stk
    blu_spark_r120 release (A13 custom)

    New build is up (y)

    I tested with lineage-20.0-20230103-nightly-lemonadep, kernel build may work with other ROMs that use similar device/kernel trees.
    This kernel is tested for the 9 Pro but it's unified, so should work for the OP9 also.

    For flashing and easy of install logging, Kernel Flasher is recommended

    You can use Kernel Flasher/FKM download kernel feature, just import the link bellow in the app updates/flash section.
    Download config: custom


    Changelog:
    • ThinLTO build with custom upstream LLVM 15.x (Clang 15.0.6 + LLD linker + IAS)
    • Rebase and cleanup for lineage-20.0
    • Merge lineage-20.0 from LineageOS/android_kernel_oneplus_sm8350
    • defconfig: sync with lineage-20.0-20230101-nightly
    • makefile: disable some clang spam
    • AnyKernel3 updates (v20221201)
    • For root, Magisk 25.2 or newer is mandatory
    Click to expand...
    Click to collapse


    Keep in mind: I am mostly interested on debugging stuff with logs and reproducible steps to replicate the issue.


    No mirrors please
    Don't forget to hit like, it's free :)
    View
    17
    eng.stk
    eng.stk
    blu_spark_r52 release

    New build is up (y)

    This kernel is tested for the 9 Pro but it's unified, so should work for the OP9 also.

    You can use FKM download kernel feature, just import the links bellow in the app.
    FKM download configs: oos


    Changelog:
    • Synchronize codes for OnePlus 9 Oxygen 11.2.10.10
    • f2fs: shrink node_write lock coverage
    • AnyKernel3 updates (v20211215)
    • Couple init runtime adjusts to better UX
    • For root, Magisk 23.0 or higher is mandatory
    Click to expand...
    Click to collapse


    Keep in mind: I will give no active support for custom ROMs (including OOS based ones).
    I am mostly interested on debugging stuff in stock stable OOS (with logs and reproducible steps to replicate the issue).


    No mirrors please
    Don't forget to hit thanks, it's free :)
    View

New posts