Doesn't that imply a risk for first next official incremental OTA OOS update a->b slot swap onto a potentially faulty slot (b being untouched by MSM) from the past? A risk, and potential disaster, that could simply have been avoided? After all, the original idea of seamless update actually wanted to avoid various kinds of unrecoverable update issues.
I don't know exactly but it works. I know there were many issues with the 8 Pro when people already had OOS A11 and wanted to flash A10 Custom rom.
Signal is on both phones, not running any GApps. I've got microG and signature spoofing enabled. Seems to happen on the one phone multiple times per day, and has only happened once on the other phone. I have a backup of the contacts, but it's frustrating to have to restore a backup multiple times a day...
...
[ 5.654171] [ 5.654164]@1 cnss: Voltage for CPR: 948mV
[ 5.654178] [ 5.654176]@1 cnss: CPR is not enabled
[ 5.654182] [ 5.654180]@1 cnss: Device frequency is 19200000 HZ
[ 5.654189] [ 5.654184]@1 cnss: Target capability: chip_id: 0x0, chip_family: 0xb, board_id: 0xff, soc_id: 0xffffffff, fw_version: 0x10198325, fw_build_timestamp: 2020-10-19 05:40, fw_build_id: QC_IMAGE_VERSION_STRING=WLAN.HST.1.0.1.r1-00805-QCAHSTSWPL_SILICONZ-1.329032.1.337663.1, otp_version: 0x48001d
[ 5.654198] [ 5.654195]@1 cnss: Sending BDF download message, state: 0xb, type: 4
[ 5.654204] [ 5.654202]@1 cnss: Get the value of bdf_WifiChain_mode: 0
[ 5.654207] cnss: cnss get_prj_version(): 14
[ 5.654209] cnss: cnss get_hw_board_version(): 21
[ 5.654212] cnss: cnss get_rf_version(): 11
[ 5.654216] cnss: FW name added with prefix: qca6390/regdb.bin
[ 5.654260] [ 5.654256]@1 cnss2 b0000000.qcom,cnss-qca6390: Falling back to syfs fallback for: qca6390/regdb.bin
[ 5.659944] [ 5.659932]@1 configfs-gadget gadget: high-speed config #1: b
[ 5.660064] [ 5.660060]@1 usb_gadget_vbus_draw USB setting current is 500mA
[ 5.660192] [ 5.660185]@1 msm-dwc3 a600000.ssusb: Avail curr from USB = 500
[ 5.660201] [ 5.660196]@1 SMBLIB: smblib_set_prop_sdp_current_max: set usb current_max=500000
[ 5.660573] [ 5.660570]@1 android_work: sent uevent USB_STATE=CONFIGURED
[ 5.666212] [ 5.666210]@6 dashd: type=USB_PD, soc=85, temp=26, vbat=4190, ibat=586
[ 5.680361] [ 5.680354]@1 QSEECOM: qseecom_load_app: App (gfp9678) does'nt exist, loading apps for first time
[ 5.724441] [ 5.724437]@5 get_param_by_index_and_offset[79] sid_index = 0 offset = 108 buf = 00000000de838868 length = 48
[ 5.740897] [ 5.740895]@4 cnss: Failed to load BDF: qca6390/regdb.bin
[ 5.740907] [ 5.740906]@4 cnss: Sending BDF download message, state: 0xb, type: 1
[ 5.740910] [ 5.740909]@4 cnss: Get the value of bdf_WifiChain_mode: 0
[ 5.740911] cnss: cnss get_prj_version(): 14
[ 5.740912] cnss: cnss get_hw_board_version(): 21
[ 5.740913] cnss: cnss get_rf_version(): 11
[ 5.740924] cnss2 b0000000.qcom,cnss-qca6390: Falling back to syfs fallback for: bdwlan.elf
[ 5.743169] [ 5.743167]@5 cnss: Failed to load BDF: bdwlan.elf
[ 5.743215] [ 5.743214]@5 cnss: ASSERT at line 1705
[ 5.743218] [ 5.743217]@5 ------------[ cut here ]------------
[ 5.743236] [ 5.743229]@5 WARNING: CPU: 5 PID: 316 at ../../../../../../kernel/oneplus/sm8250/drivers/net/wireless/cnss2/qmi.c:1705 cnss_wlfw_bdf_dnld_send_sync+0x79c/0x8d0
...
I have an idea why it's broken. Mind joining IRC channel? https://webchat.freenode.net/?channels=#titandev
It you want to test something out in like 10 minutes, send me a msg on irc.
done all this. I'm gonna try installing magisk via side loading instead of patch the boot image and check if that makes any difference.
Don't do it yet. I will give you what I use. I had the same issues that you faced.
Or one could just do what I asked about so that I could fix it properly rather than forcing people to flash some magisk trash...
Lol. Its a temp fix. Basically sets the entire device props to Pixel 5. That's all
You are way too harsh, man. And I only shared this because he said he was gonna clean flash because of this reason alone. @LuK1337 hahaha, man you're grumpy. I'm not on irc and do not have the time to get on it now. @theincognito the temp fix worked, thanks.
I guess my builds won't work out of box anytime soon in that case. In any case if there's someone who feels like being useful and has L1 on their device, feel free to message me ^^
Ended up doing the same thing here; the version on Fedora must be outdated. I've now pulled the latest platform-tools. I'm now in the same bootloop. Originally, trying to flash gave me a "wipe super partition" error, so I ran `fastboot wipe-super ./super_empty.img` and now trying to fastboot update gives me:
$ sudo ./fastboot update ../lineage-18.1-20201213_013139-UNOFFICIAL-kebab.zip
--------------------------------------------
Bootloader Version...: unknown
Baseband Version.....:
Serial Number........: dd496bc0
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Setting current slot to 'a' OKAY [ 0.005s]
extracting boot.img (96 MB) to disk... took 0.347s
archive does not contain 'boot.sig'
Sending 'boot_a' (98304 KB) OKAY [ 3.539s]
Writing 'boot_a' OKAY [ 0.369s]
extracting dtbo.img (24 MB) to disk... took 0.107s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (24576 KB) OKAY [ 0.861s]
Writing 'dtbo_a' OKAY [ 0.144s]
archive does not contain 'dt.img'
extracting recovery.img (96 MB) to disk... took 0.360s
archive does not contain 'recovery.sig'
Sending 'recovery_a' (98304 KB) OKAY [ 3.673s]
Writing 'recovery_a' OKAY [ 0.268s]
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.002s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_system_a' OKAY [ 0.002s]
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Sending 'super' (4 KB) OKAY [ 0.001s]
Updating super partition FAILED (remote: 'Unable to write new partition table')I ended up going back to factory with the MSM Tool every time I messed mine up (keep a Windows drive for Gaming still).
