• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[KERNEL] [blu_spark r110 OP8/Pro/T] [A11 OOS]

Search This thread

Boing7898

Member
Aug 10, 2011
44
8
I can still try some stuff, let me know how it goes :)
Still not working, but I really appreciate your help in this!
Here's the logcat:
Code:
01-16 23:16:50.348   972   972 E [email protected]: get_mac_from_nv: Get nv mac file failed: Permission denied
01-16 23:16:50.973  2853  2917 W IWlanNetworkService: 41 > Response Processed
01-16 23:16:52.156   972   972 E [email protected]: get_mac_from_nv: Get nv mac file failed: Permission denied
01-16 23:16:54.371   972   972 E [email protected]: Failed to access driver state control param No such file or directory, 2: No such file or directory
01-16 23:16:54.371   972   972 E [email protected]: Failed to load WiFi driver
01-16 23:16:54.371   972   972 E [email protected]: Failed to initialize firmware mode controller
01-16 23:16:54.371   972   972 E [email protected]: Wifi HAL start failed
01-16 23:16:54.373  1391  2169 E HalDevMgr: Cannot start IWifi: 9 ()
01-16 23:16:54.374  1391  2169 E WifiVendorHal: Failed to start vendor HAL
01-16 23:16:54.374  1391  2169 E WifiNative: Failed to start vendor HAL
01-16 23:16:54.374  1391  2169 E WifiNative: Failed to start Hal
01-16 23:16:54.374  1391  2169 E WifiClientModeManager: Failed to create ClientInterface. Sit in Idle

Thanks man! <3
 
  • Like
Reactions: eng.stk

eng.stk

Senior Member
Mar 29, 2011
6,894
59,209
OnePlus 5T
OnePlus 6
Download right now, will report asap
Thanks again you're amazing

Still not working, but I really appreciate your help in this!
Here's the logcat:
Code:
01-16 23:16:50.348   972   972 E [email protected]: get_mac_from_nv: Get nv mac file failed: Permission denied
01-16 23:16:50.973  2853  2917 W IWlanNetworkService: 41 > Response Processed
01-16 23:16:52.156   972   972 E [email protected]: get_mac_from_nv: Get nv mac file failed: Permission denied
01-16 23:16:54.371   972   972 E [email protected]: Failed to access driver state control param No such file or directory, 2: No such file or directory
01-16 23:16:54.371   972   972 E [email protected]: Failed to load WiFi driver
01-16 23:16:54.371   972   972 E [email protected]: Failed to initialize firmware mode controller
01-16 23:16:54.371   972   972 E [email protected]: Wifi HAL start failed
01-16 23:16:54.373  1391  2169 E HalDevMgr: Cannot start IWifi: 9 ()
01-16 23:16:54.374  1391  2169 E WifiVendorHal: Failed to start vendor HAL
01-16 23:16:54.374  1391  2169 E WifiNative: Failed to start vendor HAL
01-16 23:16:54.374  1391  2169 E WifiNative: Failed to start Hal
01-16 23:16:54.374  1391  2169 E WifiClientModeManager: Failed to create ClientInterface. Sit in Idle

Thanks man! <3
I begun the hack around and don't even noticed a major derp lol
First let's try this again.
 

Attachments

  • blu_spark_r81-custom_op8x_5d2cb0ff8.zip
    20.5 MB · Views: 20

otonieru

Senior Member
May 7, 2011
3,442
2,208
Djakarta
Trying to find out whether this will work on KB2000 and Hydrogen 11.0.6.8

but seems like most of similar question were unanswered,

anybody tried it yet ?

KB2000 Cyberpunk version here. Currently on Cleanslate Kernel,

but i always love blu_spark, been using it since OP3 era
 

Boing7898

Member
Aug 10, 2011
44
8
I begun the hack around and don't even noticed a major derp lol
First let's try this again.
Okay, something definitely changed now, logs are different:
Code:
01-17 10:10:52.982   957   957 E [email protected]: Failed to write driver state control param: Invalid argument
01-17 10:10:52.982   957   957 E [email protected]: Failed to load WiFi driver
01-17 10:10:52.982   957   957 E [email protected]: Failed to initialize firmware mode controller
01-17 10:10:52.982   957   957 E [email protected]: Wifi HAL start failed
01-17 10:10:52.984  1761  1850 E HalDevMgr: Cannot start IWifi: 9 ()
01-17 10:10:52.984  1761  1850 E WifiVendorHal: Failed to start vendor HAL
01-17 10:10:52.984  1761  1850 E WifiNative: Failed to start vendor HAL
01-17 10:10:52.984  1761  1850 E WifiNative: Failed to start Hal
01-17 10:10:52.984  1761  1850 E WifiClientModeManager: Failed to create ClientInterface. Sit in Idle
01-17 10:10:52.990  1761  1850 E WifiNative: Could not get Iface object for interface null
01-17 10:10:52.994  1761  1850 E HalDevMgr: Should have at least 1 chip!
01-17 10:10:52.995   957   957 E [email protected]: get_mac_from_nv: Get nv mac file failed: Permission denied

Also getting a lot of these, not sure if they're related to WiFi but I'll post them anyways.
Code:
01-17 10:10:53.078   658   664 E [email protected]: Error opening kernel wakelock stats for: wakeup46: Permission denied
01-17 10:10:53.081   658   664 E [email protected]: Error opening kernel wakelock stats for: wakeup82: Permission denied
01-17 10:10:53.104   658   664 E [email protected]: Error opening kernel wakelock stats for: wakeup47: Permission denied
01-17 10:10:53.109   658   664 E [email protected]: Error opening kernel wakelock stats for: wakeup45: Permission denied
01-17 10:11:12.135  1761  2841 E system_server: Unknown name for ifindex 1 with more than 154924 bytes of traffic
01-17 10:11:12.137  1761  3424 E system_server: Unknown name for ifindex 1 with more than 154924 bytes of traffic
01-17 10:11:13.143  1761  2841 E system_server: Unknown name for ifindex 1 with more than 154924 bytes of traffic

As always, thanks man <3
 
  • Like
Reactions: eng.stk

eng.stk

Senior Member
Mar 29, 2011
6,894
59,209
OnePlus 5T
OnePlus 6
Okay, something definitely changed now, logs are different:
Code:
01-17 10:10:52.982   957   957 E [email protected]: Failed to write driver state control param: Invalid argument
01-17 10:10:52.982   957   957 E [email protected]: Failed to load WiFi driver
01-17 10:10:52.982   957   957 E [email protected]: Failed to initialize firmware mode controller
01-17 10:10:52.982   957   957 E [email protected]: Wifi HAL start failed
01-17 10:10:52.984  1761  1850 E HalDevMgr: Cannot start IWifi: 9 ()
01-17 10:10:52.984  1761  1850 E WifiVendorHal: Failed to start vendor HAL
01-17 10:10:52.984  1761  1850 E WifiNative: Failed to start vendor HAL
01-17 10:10:52.984  1761  1850 E WifiNative: Failed to start Hal
01-17 10:10:52.984  1761  1850 E WifiClientModeManager: Failed to create ClientInterface. Sit in Idle
01-17 10:10:52.990  1761  1850 E WifiNative: Could not get Iface object for interface null
01-17 10:10:52.994  1761  1850 E HalDevMgr: Should have at least 1 chip!
01-17 10:10:52.995   957   957 E [email protected]: get_mac_from_nv: Get nv mac file failed: Permission denied

Also getting a lot of these, not sure if they're related to WiFi but I'll post them anyways.
Code:
01-17 10:10:53.078   658   664 E [email protected]: Error opening kernel wakelock stats for: wakeup46: Permission denied
01-17 10:10:53.081   658   664 E [email protected]: Error opening kernel wakelock stats for: wakeup82: Permission denied
01-17 10:10:53.104   658   664 E [email protected]: Error opening kernel wakelock stats for: wakeup47: Permission denied
01-17 10:10:53.109   658   664 E [email protected]: Error opening kernel wakelock stats for: wakeup45: Permission denied
01-17 10:11:12.135  1761  2841 E system_server: Unknown name for ifindex 1 with more than 154924 bytes of traffic
01-17 10:11:12.137  1761  3424 E system_server: Unknown name for ifindex 1 with more than 154924 bytes of traffic
01-17 10:11:13.143  1761  2841 E system_server: Unknown name for ifindex 1 with more than 154924 bytes of traffic

As always, thanks man <3
Ok let's see if this tackles it.
 

Attachments

  • blu_spark_r82-custom_op8x_5d2cb0ff8.zip
    22 MB · Views: 21

Boing7898

Member
Aug 10, 2011
44
8
Ok let's see if this tackles it.
Hmm this is weird. I don't always get the usual error logs when enabling WiFi, I get them more constantly when disabling it (toggling it off, it doesn't ever turn on really). But anyways, the logs are the same I think:
Code:
01-17 23:08:06.045   951   951 E [email protected]: Failed to write driver state control param: Invalid argument
01-17 23:08:06.045   951   951 E [email protected]: Failed to load WiFi driver
01-17 23:08:06.045   951   951 E [email protected]: Failed to initialize firmware mode controller
01-17 23:08:06.045   951   951 E [email protected]: Wifi HAL start failed
01-17 23:08:06.046  1758  1846 E HalDevMgr: Cannot start IWifi: 9 ()
01-17 23:08:06.046  1758  1846 E WifiVendorHal: Failed to start vendor HAL
01-17 23:08:06.046  1758  1846 E WifiNative: Failed to start vendor HAL
01-17 23:08:06.047  1758  1846 E WifiNative: Failed to start Hal
01-17 23:08:06.047  1758  1846 E WifiClientModeManager: Failed to create ClientInterface. Sit in Idle
01-17 23:08:06.049  1758  1846 E WifiNative: Could not get Iface object for interface null
01-17 23:08:06.052  1758  1846 E HalDevMgr: Should have at least 1 chip!
01-17 23:08:06.052   951   951 E [email protected]: get_mac_from_nv: Get nv mac file failed: Permission denied
01-17 23:08:06.074     0     0 E         : [20210117_23:08:06.044876]@1 Timed-out!!

Ty♥
 

eng.stk

Senior Member
Mar 29, 2011
6,894
59,209
OnePlus 5T
OnePlus 6
Hmm this is weird. I don't always get the usual error logs when enabling WiFi, I get them more constantly when disabling it (toggling it off, it doesn't ever turn on really). But anyways, the logs are the same I think:
Code:
01-17 23:08:06.045   951   951 E [email protected]: Failed to write driver state control param: Invalid argument
01-17 23:08:06.045   951   951 E [email protected]: Failed to load WiFi driver
01-17 23:08:06.045   951   951 E [email protected]: Failed to initialize firmware mode controller
01-17 23:08:06.045   951   951 E [email protected]: Wifi HAL start failed
01-17 23:08:06.046  1758  1846 E HalDevMgr: Cannot start IWifi: 9 ()
01-17 23:08:06.046  1758  1846 E WifiVendorHal: Failed to start vendor HAL
01-17 23:08:06.046  1758  1846 E WifiNative: Failed to start vendor HAL
01-17 23:08:06.047  1758  1846 E WifiNative: Failed to start Hal
01-17 23:08:06.047  1758  1846 E WifiClientModeManager: Failed to create ClientInterface. Sit in Idle
01-17 23:08:06.049  1758  1846 E WifiNative: Could not get Iface object for interface null
01-17 23:08:06.052  1758  1846 E HalDevMgr: Should have at least 1 chip!
01-17 23:08:06.052   951   951 E [email protected]: get_mac_from_nv: Get nv mac file failed: Permission denied
01-17 23:08:06.074     0     0 E         : [20210117_23:08:06.044876]@1 Timed-out!!

Ty♥
That's with r82?

go to a root terminal and type:
start wpa_supplicant
insmod /system/lib/modules/wlan.ko
 

Boing7898

Member
Aug 10, 2011
44
8
That's with r82?

go to a root terminal and type:
start wpa_supplicant
insmod /system/lib/modules/wlan.ko
Yup, also rebooted twice to make sure it was loaded properly.
Code:
kebab:/ # start wpa_supplicant
kebab:/ # insmod /system/lib/modules/wlan.ko
insmod: failed to load /system/lib/modules/wlan.ko: File exists
1|kebab:/ # insmod /system/lib/modules/wlan.ko
insmod: failed to load /system/lib/modules/wlan.ko: File exists
1|kebab:/ # lsmod
Module                  Size  Used by
wlan                 7110656  0
kebab:/ #

Still getting this in logcat after the commands you gave me
Code:
01-17 23:24:55.381   960   960 E [email protected]: Failed to write driver state control param: Invalid argument
01-17 23:24:55.381   960   960 E [email protected]: Failed to load WiFi driver
01-17 23:24:55.381   960   960 E [email protected]: Failed to initialize firmware mode controller
01-17 23:24:55.381   960   960 E [email protected]: Wifi HAL start failed
01-17 23:24:55.383  1804  1895 E HalDevMgr: Cannot start IWifi: 9 ()
01-17 23:24:55.383  1804  1895 E WifiVendorHal: Failed to start vendor HAL
01-17 23:24:55.383  1804  1895 E WifiNative: Failed to start vendor HAL
01-17 23:24:55.383  1804  1895 E WifiNative: Failed to start Hal
01-17 23:24:55.383  1804  1895 E WifiClientModeManager: Failed to create ClientInterface. Sit in Idle
01-17 23:24:55.392   960   960 E [email protected]: get_mac_from_nv: Get nv mac file failed: Permission denied
01-17 23:24:57.204   960   960 E [email protected]: get_mac_from_nv: Get nv mac file failed: Permission denied
01-17 23:24:57.409     0     0 E         : [20210117_23:24:55.381072]@2 Timed-out!!
 

eng.stk

Senior Member
Mar 29, 2011
6,894
59,209
OnePlus 5T
OnePlus 6
Yup, also rebooted twice to make sure it was loaded properly.
Code:
kebab:/ # start wpa_supplicant
kebab:/ # insmod /system/lib/modules/wlan.ko
insmod: failed to load /system/lib/modules/wlan.ko: File exists
1|kebab:/ # insmod /system/lib/modules/wlan.ko
insmod: failed to load /system/lib/modules/wlan.ko: File exists
1|kebab:/ # lsmod
Module                  Size  Used by
wlan                 7110656  0
kebab:/ #
Well, then you're out of luck.
Seems like dependencies run deeper, not something I'm going to tackle, sorry.
 
  • Like
Reactions: Boing7898

Boing7898

Member
Aug 10, 2011
44
8
Well, then you're out of luck.
Seems like dependencies run deeper, not something I'm going to tackle, sorry.
I managed to rmmod wlan and then insmod it with success and got this log from dmesg, I don't know if it can help but it's something new:
Code:
[  542.799679] wlan_hdd_state wlan major(474) initialized
[  542.801588] msm_pcie_enable: PCIe: Assert the reset of endpoint of RC0.
[  542.805381] [20210117_23:30:30.344917]@3 msm_pcie_enable: PCIe: RC0: PCIE20_PARF_INT_ALL_MASK: 0x7f80c202
[  542.807616] [20210117_23:30:30.347153]@3 pcie_phy_init: PCIe RC0 PHY is ready!
[  542.817699] [20210117_23:30:30.357235]@3 msm_pcie_enable: PCIe: Release the reset of endpoint of RC0.
[  542.834535] [20210117_23:30:30.374071]@3 msm_pcie_link_train: PCIe RC0 link initialized
[  542.847261] [20210117_23:30:30.386797]@3 cnss_pci 0000:01:00.0: enabling device (0000 -> 0002)
[  542.849281] [20210117_23:30:30.388813]@2 cnss_pci 0000:01:00.0: Falling back to syfs fallback for: qca6390/amss20.bin
[  542.858436] [20210117_23:30:30.397970]@3 ueventd: firmware: loading 'qca6390/amss20.bin' for '/devices/platform/soc/1c00000.qcom,pcie/pci0000:00/0000:00:00.0/0000:01:00.0/firmware/qca6390!amss20.bin'
[  542.870378] [20210117_23:30:30.409906]@3 ueventd: loading /devices/platform/soc/1c00000.qcom,pcie/pci0000:00/0000:00:00.0/0000:01:00.0/firmware/qca6390!amss20.bin took 12ms
[  543.018860] [20210117_23:30:30.558385]@2 [E][mhi_create_devices] :mhi_create_devices
[  543.021257] [20210117_23:30:30.560791]@2 [E][mhi_create_devices] :mhi_create_devices
[  543.023087] [20210117_23:30:30.562623]@2 [E][mhi_uci_probe] channel:LOOPBACK mhi_uci_probe mhi_uci_1101_00.01.00_0 successfully probed
[  543.210704] [20210117_23:30:30.750231]@1 cnss2 b0000000.qcom,cnss-qca6390: Falling back to syfs fallback for: qca6390/regdb.bin
[  543.220455] [20210117_23:30:30.759987]@3 ueventd: firmware: loading 'qca6390/regdb.bin' for '/devices/platform/soc/b0000000.qcom,cnss-qca6390/firmware/qca6390!regdb.bin'
[  543.221476] [20210117_23:30:30.761009]@3 ueventd: firmware: could not find firmware for qca6390/regdb.bin
[  543.221556] [20210117_23:30:30.761092]@3 ueventd: firmware: attempted /etc/firmware/qca6390/regdb.bin, open failed: No such file or directory
[  543.221613] [20210117_23:30:30.761149]@3 ueventd: firmware: attempted /odm/firmware/qca6390/regdb.bin, open failed: No such file or directory
[  543.221666] [20210117_23:30:30.761203]@3 ueventd: firmware: attempted /vendor/firmware/qca6390/regdb.bin, open failed: No such file or directory
[  543.221720] [20210117_23:30:30.761257]@3 ueventd: firmware: attempted /firmware/image/qca6390/regdb.bin, open failed: No such file or directory
[  543.221797] [20210117_23:30:30.761333]@3 ueventd: firmware: attempted /vendor/firmware_mnt/image/qca6390/regdb.bin, open failed: No such file or directory
[  543.222014] [20210117_23:30:30.761548]@3 ueventd: loading /devices/platform/soc/b0000000.qcom,cnss-qca6390/firmware/qca6390!regdb.bin took 1ms
[  543.222362] [20210117_23:30:30.761896]@1 cnss2 b0000000.qcom,cnss-qca6390: Falling back to syfs fallback for: 14wlan.b0e[  543.230550] [20210117_23:30:30.770085]@3 ueventd: firmware: loading '14wlan.b0e' for '/devices/platform/soc/b0000000.qcom,cnss-qca6390/firmware/14wlan.b0e'
[  543.231455] [20210117_23:30:30.770990]@3 ueventd: loading /devices/platform/soc/b0000000.qcom,cnss-qca6390/firmware/14wlan.b0e took 1ms
[  543.266828] [20210117_23:30:30.806365]@1 (NULL device *): Falling back to syfs fallback for: wlan/qca_cld/qca6390/WCNSS_qcom_cfg.ini
[  543.274415] [20210117_23:30:30.813951]@2 ueventd: firmware: loading 'wlan/qca_cld/qca6390/WCNSS_qcom_cfg.ini' for '/devices/virtual/firmware/wlan!qca_cld!qca6390!WCNSS_qcom_cfg.ini'
[  543.274884] [20210117_23:30:30.814421]@2 ueventd: firmware: could not find firmware for wlan/qca_cld/qca6390/WCNSS_qcom_cfg.ini
[  543.274965] [20210117_23:30:30.814503]@2 ueventd: firmware: attempted /etc/firmware/wlan/qca_cld/qca6390/WCNSS_qcom_cfg.ini, open failed: No such file or directory
[  543.275014] [20210117_23:30:30.814553]@2 ueventd: firmware: attempted /odm/firmware/wlan/qca_cld/qca6390/WCNSS_qcom_cfg.ini, open failed: No such file or directory
[  543.275060] [20210117_23:30:30.814598]@2 ueventd: firmware: attempted /vendor/firmware/wlan/qca_cld/qca6390/WCNSS_qcom_cfg.ini, open failed: No such file or directory
[  543.275105] [20210117_23:30:30.814644]@2 ueventd: firmware: attempted /firmware/image/wlan/qca_cld/qca6390/WCNSS_qcom_cfg.ini, open failed: No such file or directory
[  543.275150] [20210117_23:30:30.814689]@2 ueventd: firmware: attempted /vendor/firmware_mnt/image/wlan/qca_cld/qca6390/WCNSS_qcom_cfg.ini, open failed: No such file or directory
[  543.275292] [20210117_23:30:30.814828]@2 ueventd: loading /devices/virtual/firmware/wlan!qca_cld!qca6390!WCNSS_qcom_cfg.ini took 1ms

Anyways, thanks for trying! Looks like I'm going to switch ROMs and get something that can run your kernel. Your determination and knowledge of the Android system and its kernel convinced me instantly!♥

EDIT:
Looks like it's calling /vendor/etc/init/hw/init.oem.rc at line 16 and then crashing with error 127 which is file not found or not +x'd

Code:
on property:wlan.driver.status=ok
    start load_wlan_driver

service load_wlan_driver /vendor/bin/sh /vendor/bin/load_wlan_driver

There's no file called load_wlan_driver in /vendor/bin, I think that's the problem?
Nevermind, it's just a file that calls insmod wlan.ko, no big deal since we're already doing that manually.
Oh well.
 
Last edited:

eng.stk

Senior Member
Mar 29, 2011
6,894
59,209
OnePlus 5T
OnePlus 6
I managed to rmmod wlan and then insmod it with success and got this log from dmesg, I don't know if it can help but it's something new:
Code:
[  542.799679] wlan_hdd_state wlan major(474) initialized
[  542.801588] msm_pcie_enable: PCIe: Assert the reset of endpoint of RC0.
[  542.805381] [20210117_23:30:30.344917]@3 msm_pcie_enable: PCIe: RC0: PCIE20_PARF_INT_ALL_MASK: 0x7f80c202
[  542.807616] [20210117_23:30:30.347153]@3 pcie_phy_init: PCIe RC0 PHY is ready!
[  542.817699] [20210117_23:30:30.357235]@3 msm_pcie_enable: PCIe: Release the reset of endpoint of RC0.
[  542.834535] [20210117_23:30:30.374071]@3 msm_pcie_link_train: PCIe RC0 link initialized
[  542.847261] [20210117_23:30:30.386797]@3 cnss_pci 0000:01:00.0: enabling device (0000 -> 0002)
[  542.849281] [20210117_23:30:30.388813]@2 cnss_pci 0000:01:00.0: Falling back to syfs fallback for: qca6390/amss20.bin
[  542.858436] [20210117_23:30:30.397970]@3 ueventd: firmware: loading 'qca6390/amss20.bin' for '/devices/platform/soc/1c00000.qcom,pcie/pci0000:00/0000:00:00.0/0000:01:00.0/firmware/qca6390!amss20.bin'
[  542.870378] [20210117_23:30:30.409906]@3 ueventd: loading /devices/platform/soc/1c00000.qcom,pcie/pci0000:00/0000:00:00.0/0000:01:00.0/firmware/qca6390!amss20.bin took 12ms
[  543.018860] [20210117_23:30:30.558385]@2 [E][mhi_create_devices] :mhi_create_devices
[  543.021257] [20210117_23:30:30.560791]@2 [E][mhi_create_devices] :mhi_create_devices
[  543.023087] [20210117_23:30:30.562623]@2 [E][mhi_uci_probe] channel:LOOPBACK mhi_uci_probe mhi_uci_1101_00.01.00_0 successfully probed
[  543.210704] [20210117_23:30:30.750231]@1 cnss2 b0000000.qcom,cnss-qca6390: Falling back to syfs fallback for: qca6390/regdb.bin
[  543.220455] [20210117_23:30:30.759987]@3 ueventd: firmware: loading 'qca6390/regdb.bin' for '/devices/platform/soc/b0000000.qcom,cnss-qca6390/firmware/qca6390!regdb.bin'
[  543.221476] [20210117_23:30:30.761009]@3 ueventd: firmware: could not find firmware for qca6390/regdb.bin
[  543.221556] [20210117_23:30:30.761092]@3 ueventd: firmware: attempted /etc/firmware/qca6390/regdb.bin, open failed: No such file or directory
[  543.221613] [20210117_23:30:30.761149]@3 ueventd: firmware: attempted /odm/firmware/qca6390/regdb.bin, open failed: No such file or directory
[  543.221666] [20210117_23:30:30.761203]@3 ueventd: firmware: attempted /vendor/firmware/qca6390/regdb.bin, open failed: No such file or directory
[  543.221720] [20210117_23:30:30.761257]@3 ueventd: firmware: attempted /firmware/image/qca6390/regdb.bin, open failed: No such file or directory
[  543.221797] [20210117_23:30:30.761333]@3 ueventd: firmware: attempted /vendor/firmware_mnt/image/qca6390/regdb.bin, open failed: No such file or directory
[  543.222014] [20210117_23:30:30.761548]@3 ueventd: loading /devices/platform/soc/b0000000.qcom,cnss-qca6390/firmware/qca6390!regdb.bin took 1ms
[  543.222362] [20210117_23:30:30.761896]@1 cnss2 b0000000.qcom,cnss-qca6390: Falling back to syfs fallback for: 14wlan.b0e[  543.230550] [20210117_23:30:30.770085]@3 ueventd: firmware: loading '14wlan.b0e' for '/devices/platform/soc/b0000000.qcom,cnss-qca6390/firmware/14wlan.b0e'
[  543.231455] [20210117_23:30:30.770990]@3 ueventd: loading /devices/platform/soc/b0000000.qcom,cnss-qca6390/firmware/14wlan.b0e took 1ms
[  543.266828] [20210117_23:30:30.806365]@1 (NULL device *): Falling back to syfs fallback for: wlan/qca_cld/qca6390/WCNSS_qcom_cfg.ini
[  543.274415] [20210117_23:30:30.813951]@2 ueventd: firmware: loading 'wlan/qca_cld/qca6390/WCNSS_qcom_cfg.ini' for '/devices/virtual/firmware/wlan!qca_cld!qca6390!WCNSS_qcom_cfg.ini'
[  543.274884] [20210117_23:30:30.814421]@2 ueventd: firmware: could not find firmware for wlan/qca_cld/qca6390/WCNSS_qcom_cfg.ini
[  543.274965] [20210117_23:30:30.814503]@2 ueventd: firmware: attempted /etc/firmware/wlan/qca_cld/qca6390/WCNSS_qcom_cfg.ini, open failed: No such file or directory
[  543.275014] [20210117_23:30:30.814553]@2 ueventd: firmware: attempted /odm/firmware/wlan/qca_cld/qca6390/WCNSS_qcom_cfg.ini, open failed: No such file or directory
[  543.275060] [20210117_23:30:30.814598]@2 ueventd: firmware: attempted /vendor/firmware/wlan/qca_cld/qca6390/WCNSS_qcom_cfg.ini, open failed: No such file or directory
[  543.275105] [20210117_23:30:30.814644]@2 ueventd: firmware: attempted /firmware/image/wlan/qca_cld/qca6390/WCNSS_qcom_cfg.ini, open failed: No such file or directory
[  543.275150] [20210117_23:30:30.814689]@2 ueventd: firmware: attempted /vendor/firmware_mnt/image/wlan/qca_cld/qca6390/WCNSS_qcom_cfg.ini, open failed: No such file or directory
[  543.275292] [20210117_23:30:30.814828]@2 ueventd: loading /devices/virtual/firmware/wlan!qca_cld!qca6390!WCNSS_qcom_cfg.ini took 1ms

Anyways, thanks for trying! Looks like I'm going to switch ROMs and get something that can run your kernel. Your determination and knowledge of the Android system and its kernel convinced me instantly!♥

EDIT:
Looks like it's calling /vendor/etc/init/hw/init.oem.rc at line 16 and then crashing with error 127 which is file not found or not +x'd

Code:
on property:wlan.driver.status=ok
    start load_wlan_driver

service load_wlan_driver /vendor/bin/sh /vendor/bin/load_wlan_driver

There's no file called load_wlan_driver in /vendor/bin, I think that's the problem?
Nevermind, it's just a file that calls insmod wlan.ko, no big deal since we're already doing that manually.
Oh well.
Yeah exactly, we're doing our thing so it wouldn't make any difference.
you don't have anything under /vendor/firmware/wlan/qca_cld/qca6390/ ?
 
  • Like
Reactions: Boing7898

mjnhvudn

Member
Jul 28, 2016
21
10
I have oneplus 8t kb2000 software version currently is 11.0.6.9 BA please show me how to install blu_spark kernel oneplus Android 11 on my 8T okay ?? please help me !! thanks
 

stmims1124

Senior Member
Sep 28, 2010
280
199
Gaithersburg, MD
OnePlus 8T
DWHxIK

Kernel features:
  • Build with Google Clang version 12.0.1 + LLD linker
  • Full -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc
  • Less is more: stockish OP8 builds based on OnePlusOSS/android_kernel_oneplus_sm8250 for max stability
  • Systemless installer (doesn't touch system 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 sm8250 patchset
  • No OC, use 300HZ base timer frequency
  • msm_performance touchboost toggle on/off (enabled by default), tweaked cpu_boost driver
  • Enhanced TCP methods (westwood is default), Network tweaks and updated drivers
  • Several I/O control tweaks, added schedulers ZEN v2 is default, advanced filesystems enabled (F2FS, ExFAT, NTFS, CIFS & NFS)
  • ZRAM Swap (LZ4) and with swap file disabled
  • 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 option
  • Gamepad support enabled (xbox, ps4, switch)
  • USB Fast Charge (USB mode up to 900mA with MTP on)
  • FS fsync toggle on/off
  • Wakelock blockers available
  • wireguard support
  • CDROM emulation on mass_storage (compatible with DriveDroid 0.10.36+)
  • Compatible with Kernel Adiutor, EXKM, FKM and others


DOWNLOAD KERNEL ZIP
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 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 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/op8

pp-acceptance-medium.png

If you like my work, donations are always welcome.
Don't forget to hit thanks and rate the thread nicely, it's free ;)


OnePlus 8 Pro development unit donated by OnePlus. Big shouts to them :)
Very proud of being on the OnePlus Developer Program, special thanks to dev relations team.
@eng.stk , I just wanted to say thank you for your excellent work here. I'm a bit late in finding your kernel for the 8T, but better late than never. I'm still getting used to the new XDA app, and finally remembered/found the "cross device development" thread. The 8T hasn't had a wealth of dedicated development as of yet (though that's understandable), but I've finally found stuff that works for the 8T. So far I've tested out 3 custom kernels for the 8T, and as is right now, I can say with confidence that your kernel has proven to be the best...at least in my experience, for my specific needs. I don't want/need a kernel with f**k-tons of additional features...I just need something that performs well, while still maintaining good battery life, and you have provided exactly that. Actually, my idle drain has been surprisingly low, even compared to Radioactive Kernel (which has also proven great). So yeah... thank you for all you've done here! I hope you feel the gratitude from the community here, as a whole. With that, I shall stop rambling. Cheers you you! 🥂🍻
 
  • Like
Reactions: names and eng.stk

Top Liked Posts

  • There are no posts matching your filters.
  • 27
    blu_spark_r110 release

    New build is up (y)

    This kernel is tested for the 8 Pro and 8T variants which I have, regular OP8 in OOS 11 is said to be working fine by some users.
    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.7 + LLD linker (updated)
    • hwtracing: Add entries from kona-coresight (tentative less idle draw)
    • defconfig: enable ld deadcode elimination
    • arm64: Allow LD_DEAD_CODE_DATA_ELIMINATION to be selected
    • arm64: Keep alternative-instruction sections
    • AnyKernel3 updates (v20210721)
    • For root, Magisk v23.0 or newer is mandatory


    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 :)
    4
    Alright! Not the first time i see someone ranting against butter. Is it that bad? The only bad thing i noticed is that bluetooth was wasting too much battery. Which is a no-no to me.
    You are free to use whatever on your phone. Just don't complain after.
    If you use extras like that, you will get no support from me.
    It's in OP, people should read that before posting on a kernel thread talking about derps when using random crap that promotes ultra performance/infinite battery.
    Tired of this mumbo jumbo, users should know better.
    2
    Works wonders on op8.
    Went "back" to A11 after some issues on A10, and even though i do like to try different kernels, i somehow always end back to this one. Ty for keeping it updated and always great / fast respons, really do appriciate you're work & time mr. @eng.stk
    2
    Good to see you here eng.stk, your kernel is awsome, just replace my OP6T today.
    I have a feature request, can you help to to add battery idle functionality to your custom kernel? I use ACCA to limit my battery since OP6T, it will be useful if the kernel support battery idle.
    It does work with ACCA. Using it for 2 months already.
    1
    Just a thought because I know it's no longer being developed.. By any chance did you flash that Butterlimits thing? If so, try uninstall updates to Google play services and reinstall. It's been known to cause location issues
    Removing the latest update of google play services did the trick!!! Thankx!!!

    Btw, did not use Butterlimits....
  • 63
    DWHxIK

    Kernel features:
    • Build with Google Clang version 12.0.7 + LLD linker
    • Full -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc
    • Less is more: stockish OP8 builds based on OnePlusOSS/android_kernel_oneplus_sm8250 for max stability
    • Systemless installer (doesn't touch system 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 sm8250 patchset
    • No OC, use 300HZ 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, added schedulers ZEN v2 is default, advanced filesystems enabled (F2FS, ExFAT, NTFS, CIFS & NFS)
    • ZRAM Swap (LZO-RLE default) and with file disabled, LZ4 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 option
    • Gamepad support enabled (xbox, ps4, switch)
    • USB Fast Charge (USB mode up to 900mA with MTP on)
    • FS fsync toggle on/off
    • Wakelock blockers available
    • wireguard support
    • CDROM emulation on mass_storage (compatible with DriveDroid 0.10.36+)
    • Compatible with Kernel Adiutor, EXKM, FKM and others


    DOWNLOAD KERNEL ZIP
    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 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 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/op8
    Don't forget to hit thanks, it's free ;)


    OnePlus 8 Pro development unit donated by OnePlus. Big shouts to them :)
    Very proud of being on the OnePlus Developer Program, special thanks to dev relations team.
    29
    blu_spark_r109 release

    New build is up (y)

    This kernel is tested for the 8 Pro and 8T variants which I have, regular OP8 in OOS 11 is said to be working fine by some users.
    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.7 + LLD linker
    • Add some build improvements
    • Silence a couple logging and debug
    • wireguard updates (v1.0.20210606)
    • AnyKernel3 updates sync
    • For root, Magisk v23.0 or newer is mandatory


    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 :)
    27
    blu_spark_r110 release

    New build is up (y)

    This kernel is tested for the 8 Pro and 8T variants which I have, regular OP8 in OOS 11 is said to be working fine by some users.
    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.7 + LLD linker (updated)
    • hwtracing: Add entries from kona-coresight (tentative less idle draw)
    • defconfig: enable ld deadcode elimination
    • arm64: Allow LD_DEAD_CODE_DATA_ELIMINATION to be selected
    • arm64: Keep alternative-instruction sections
    • AnyKernel3 updates (v20210721)
    • For root, Magisk v23.0 or newer is mandatory


    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 :)
    26
    blu_spark_r101 release

    New build is up (y)

    This kernel is tested for the 8 Pro and 8T variants which I have, regular OP8 in OOS 11 is said to be working fine by some users.
    You can use FKM download kernel feature, just import the links bellow in the app.
    FKM download configs: oos


    Changelog:
    • Revert "fs: exfat: sync with v5.8-1arter97"
    • defconfig: disable IKHEADERS
    • Remove some logspam and debug
    • net/wireguard: merge v1.0.20210424
    • AnyKernel3 updates sync
    • For root, Magisk v22.1 or newer is mandatory


    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 :)
    24
    blu_spark_r94 release

    New build is up (y)

    This kernel is tested for the 8 Pro and 8T variants which I have, regular OP8 in OOS 11 is said to be working fine by some users.
    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.4 + LLD linker
    • BACKPORT: lib/lzo: implement run-length encoding (zram default now, better compress/speed ratio)
    • BACKPORT: GKI: hwtracing: Add a driver for disabling coresight clocks (backport from Pixel 5, less idle draw)
    • BACKPORT: lz4: fix kernel decompression speed
    • A couple of build improvements
    • Further disable audit
    • defconfig: enable ZSTD
    • Remove some logspam
    • AnyKernel3 sync
    • For root, Magisk v22.1 or newer is mandatory


    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 :)