• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][OFFICIAL][enchilada][11] LineageOS 18.1

Search This thread
Nov 7, 2015
20
3
Hey, I had installed 11/30 build and there is an update. So do I have to flash los.img from my twrp for ota? or will the ota work directly with twrp?
 

vikash1994b

Senior Member
Dec 7, 2012
995
584
27
New Delhi
Xiaomi Mi 3
Xiaomi Mi A1
Hey, I had installed 11/30 build and there is an update. So do I have to flash los.img from my twrp for ota? or will the ota work directly with twrp?
Just update using the updater, you will need to reboot devices after the update is installed just like stock rom, keep in mind TWRP recovery will be replaced with LOS recovery after the updater.
 

rhhd

Senior Member
Jan 19, 2011
77
8
MUC
I am having a serious problem with the camera app on LinOS 18.1 Nightly 30/11/2021 (but I have been observing this for a while now on earlier nightlies as well):

The *preview* in the camera app correctly focuses the way I want. But the moment I push the trigger button, the focus changes to something apparently random, ruining the shot.

This happens *all the time*. A reboot fixes this behaviour but only for a very short time. I basically have to reboot every time before I want to take a close-up shot.

See sample photos attached: screenshot with preview just before trigger, and actual picture taken.
 

Attachments

  • 2021-12-08 10.11.20 - Kopie.png
    2021-12-08 10.11.20 - Kopie.png
    1.9 MB · Views: 43
  • 2021-12-08 10.11.30 - Kopie.jpg
    2021-12-08 10.11.30 - Kopie.jpg
    763.7 KB · Views: 43

vikash1994b

Senior Member
Dec 7, 2012
995
584
27
New Delhi
Xiaomi Mi 3
Xiaomi Mi A1
I am having a serious problem with the camera app on LinOS 18.1 Nightly 30/11/2021 (but I have been observing this for a while now on earlier nightlies as well):

The *preview* in the camera app correctly focuses the way I want. But the moment I push the trigger button, the focus changes to something apparently random, ruining the shot.

This happens *all the time*. A reboot fixes this behaviour but only for a very short time. I basically have to reboot every time before I want to take a close-up shot.

See sample photos attached: screenshot with preview just before trigger, and actual picture taken.
+1 snap camera mostly captures blurry photos.
 

madman

Senior Member
Apr 21, 2011
1,615
443
Planet Earth
OnePlus 5
OnePlus 6
Is it advisable to keep the firmware upto date? I was using OP5 as my phone until recently and firmware was usually shipped with the ROM itself (of course not that the support has stopped for it, nothing is changing)
 

CrysisLTU

Senior Member
Feb 1, 2012
311
371
Is it advisable to keep the firmware upto date? I was using OP5 as my phone until recently and firmware was usually shipped with the ROM itself (of course not that the support has stopped for it, nothing is changing)
Firmware is not shipped via LOS updates for OP6, you have to update it manually. As long as you are on OOS11 firmware, you shouldn't need to worry about it, whether it's OOS11, 11.1.1.1 or 11.1.2.2 - all of them work fine. I am running 11.1.2.2 right now and I haven't noticed any differences between the older 11 firmwares.
 
  • Like
Reactions: Eruurk and madman
Is it advisable to keep the firmware upto date? I was using OP5 as my phone until recently and firmware was usually shipped with the ROM itself (of course not that the support has stopped for it, nothing is changing)

TL;DR:
It's generally a good idea to keep it updated as new OOS versions are released, following the instructions linked above.
Testing minor firmware updates by flashing individual partitions from fastbootd as explained in the link is easy enough to roll back if it's not working right.

Long-winded:
Mostly, yes. The actual binary blobs that LineageOS for oneplus_sdm845 is built against aren't always the most current but in general it's a good idea to watch the release notes and see if there's any mention of requiring newer firmware.
Sometimes LuK doesn't get around to updating things very frequently as they have a lot on their plate in general, or it's been tested and there's no major difference in the libraries/binaries that are actually utilized. For example, the current version of vendor blobs from the github repo, which the nightlies are presumably built against, was pulled from the OOS 11.0 release (OnePlus6Oxygen_22.J.53_OTA_053_all_2104202241_ecefb.
If you feel like testing as soon as a new version pops up on Oxygen Updater, please feel free to share your results with the entire class so everyone can benefit.
In general, as long as you're not changing major Android versions (i.e. 10.x to 11.x), you can actually use the LOS recovery/fastbootd process as listed in the wiki link above to DOWNGRADE firmware (like, from 11.1.2.2 to 11.1.1.1) without requiring reinstallation or formatting data or factory resetting, in case an update causes problems. It's the SYSTEM security patch level, not VENDOR patch level, that has the anti-rollback encryption requirement -- so don't try to flash last month's ROM release and expect it to just work without having to format data & lose everything in internal storage.
 

treyy

Senior Member
Nov 19, 2010
246
28
hello together,

i installed the last nightly lineage-18.1-20211207-nightly-enchilada-signed.zip on my oneplus 6. so far everything is Working. But is there any Option to stop the keyboard Vibration? Vibration when touching is already deselected.thx

Edit. found it
 
Last edited:

Not_perfect

Member
Mar 27, 2019
26
5
I'm on FW OOS 10.3.9 and LOS 18.1-20210511.
This is gonna be guide to update fw ;)

  1. remove encryption password
  2. take backup (as a precaution)
  3. flash OOS zip file with desired firmware level, flash custom rom zip file, flash twrp (without rebooting or changing active partition inbetween)
  4. reboot into recovery (active partition should change)
  5. repeat step 3 (to get other partition on the same firmware level)
  6. reboot into system and re-set encryption password and fingerprints
I'm on FW OOS 10.3.9 and LOS 18.1-20210511. I want to update the firmware, because I have no speech in Navigation.
Is this way still right? To OOS 10.3.12 and last LOS.
The wiki instruction to upgrade the fw is to complicated for me. Tryed this but didn't managed.
 
Last edited:

kouzelnik3

Senior Member
Dec 29, 2011
466
137
24
Prague
jakubkasanda.g6.cz
OnePlus 6
I'm on FW OOS 10.3.9 and LOS 18.1-20210511.

I'm on FW OOS 10.3.9 and LOS 18.1-20210511. I want to update the firmware to OOS, because I have no speech in Navigation.
Is this way still right? To OOS 10.3.12 and last LOS.
The wiki instruction to upgrade the fw is to complicated for me. Tryed this but didn't managed.
Yup, this guide is still right. :)
 
  • Like
Reactions: Not_perfect

lamahgra

Senior Member
Jan 27, 2008
113
54
11.1.2.2 should be .15-00007-SDM845_GEN_PACK-1.437410.1.446401.1
Follow the wiki instructions again: https://wiki.lineageos.org/devices/enchilada/fw_update
And make sure you are using the latest LOS recovery with latest platform-tools.

followed the instruction again... same problem:


Screenshot_20211206-103743_Einstellungen.png

Code:
12-06 10:42:21.725  2839  2839 D QtiCarrierConfigHelper: WARNING, no carrier configs on phone Id: 0
12-06 10:42:27.456  3381  3468 I ThermalEngine: Monitor : quiet_therm = 29633, msm_therm = 30735, xo_therm = 30441, battery_therm = 293,current_now = -297000
12-06 10:42:27.680   832   832 E [email protected]: Failed to write driver state control param: Invalid argument
12-06 10:42:27.681   832   832 E [email protected]: Failed to load WiFi driver
12-06 10:42:27.681   832   832 E [email protected]: Failed to initialize firmware mode controller
12-06 10:42:27.681   832   832 E [email protected]: Wifi HAL start failed
12-06 10:42:27.683  1698  2310 E HalDevMgr: Cannot start IWifi: 9 ()
12-06 10:42:27.684  1698  2310 E WifiVendorHal: Failed to start vendor HAL
12-06 10:42:27.684  1698  2310 E WifiNative: Failed to start vendor HAL
12-06 10:42:27.684  1698  2310 E WifiNative: Failed to start Hal
12-06 10:42:27.684  1698  2310 E WifiClientModeManager: Failed to create ClientInterface. Sit in Idle
12-06 10:42:27.685  1698  2310 D WifiScanRequestProxy: Sending scan available broadcast: false
12-06 10:42:27.686  1698  2313 I WifiScanningService: Received a request to disable scanning, UID = 1000
12-06 10:42:27.686  1698  2313 I WifiScanningService: wifi driver unloaded
12-06 10:42:27.687  1698  2310 I WifiScanRequestProxy: Scanning is disabled
12-06 10:42:27.688  1698  2310 D WifiClientModeManager: received an invalid message: { when=-20s555ms what=2 arg1=2 target=com.android.wifi.x.com.android.internal.util.StateMachine$SmHandler }
12-06 10:42:27.688  1698  2310 D WifiController: STA disabled, return to DisabledState.
12-06 10:42:27.689  1698  2310 D WifiController: EnabledState.exit()
12-06 10:42:27.689  1698  2310 D WifiController: DisabledState.enter()
12-06 10:42:27.679     0     0 E         : Timed-out!!
 

CrysisLTU

Senior Member
Feb 1, 2012
311
371
followed the instruction again... same problem:


View attachment 5479723
Code:
12-06 10:42:21.725  2839  2839 D QtiCarrierConfigHelper: WARNING, no carrier configs on phone Id: 0
12-06 10:42:27.456  3381  3468 I ThermalEngine: Monitor : quiet_therm = 29633, msm_therm = 30735, xo_therm = 30441, battery_therm = 293,current_now = -297000
12-06 10:42:27.680   832   832 E [email protected]: Failed to write driver state control param: Invalid argument
12-06 10:42:27.681   832   832 E [email protected]: Failed to load WiFi driver
12-06 10:42:27.681   832   832 E [email protected]: Failed to initialize firmware mode controller
12-06 10:42:27.681   832   832 E [email protected]: Wifi HAL start failed
12-06 10:42:27.683  1698  2310 E HalDevMgr: Cannot start IWifi: 9 ()
12-06 10:42:27.684  1698  2310 E WifiVendorHal: Failed to start vendor HAL
12-06 10:42:27.684  1698  2310 E WifiNative: Failed to start vendor HAL
12-06 10:42:27.684  1698  2310 E WifiNative: Failed to start Hal
12-06 10:42:27.684  1698  2310 E WifiClientModeManager: Failed to create ClientInterface. Sit in Idle
12-06 10:42:27.685  1698  2310 D WifiScanRequestProxy: Sending scan available broadcast: false
12-06 10:42:27.686  1698  2313 I WifiScanningService: Received a request to disable scanning, UID = 1000
12-06 10:42:27.686  1698  2313 I WifiScanningService: wifi driver unloaded
12-06 10:42:27.687  1698  2310 I WifiScanRequestProxy: Scanning is disabled
12-06 10:42:27.688  1698  2310 D WifiClientModeManager: received an invalid message: { when=-20s555ms what=2 arg1=2 target=com.android.wifi.x.com.android.internal.util.StateMachine$SmHandler }
12-06 10:42:27.688  1698  2310 D WifiController: STA disabled, return to DisabledState.
12-06 10:42:27.689  1698  2310 D WifiController: EnabledState.exit()
12-06 10:42:27.689  1698  2310 D WifiController: DisabledState.enter()
12-06 10:42:27.679     0     0 E         : Timed-out!!
Code:
12-06 10:42:27.684  1698  2310 E WifiVendorHal: Failed to start vendor HAL
12-06 10:42:27.684  1698  2310 E WifiNative: Failed to start vendor HAL
12-06 10:42:27.684  1698  2310 E WifiNative: Failed to start Hal

Seems like the issue is with vendor HAL. I guess that would imply the problem is still with the vendor firmware. Do you have logs from when you were flashing the firmware via fastboot?
 

lamahgra

Senior Member
Jan 27, 2008
113
54
Code:
12-06 10:42:27.684  1698  2310 E WifiVendorHal: Failed to start vendor HAL
12-06 10:42:27.684  1698  2310 E WifiNative: Failed to start vendor HAL
12-06 10:42:27.684  1698  2310 E WifiNative: Failed to start Hal

Seems like the issue is with vendor HAL. I guess that would imply the problem is still with the vendor firmware. Do you have logs from when you were flashing the firmware via fastboot?
no - i flash the firmware again - give me 5 minutes
 

lamahgra

Senior Member
Jan 27, 2008
113
54
Code:
12-06 10:42:27.684  1698  2310 E WifiVendorHal: Failed to start vendor HAL
12-06 10:42:27.684  1698  2310 E WifiNative: Failed to start vendor HAL
12-06 10:42:27.684  1698  2310 E WifiNative: Failed to start Hal

Seems like the issue is with vendor HAL. I guess that would imply the problem is still with the vendor firmware. Do you have logs from when you were flashing the firmware via fastboot?
Code:
./fastboot flash --slot=all abl abl.img
Sending 'abl_a' (2132 KB)                          OKAY [  0.065s]
Writing 'abl_a'                                    OKAY [  0.020s]
Sending 'abl_b' (2132 KB)                          OKAY [  0.063s]
Writing 'abl_b'                                    OKAY [  0.018s]
Finished. Total time: 0.172s
./fastboot flash --slot=all aop aop.img
Sending 'aop_a' (180 KB)                           OKAY [  0.005s]
Writing 'aop_a'                                    OKAY [  0.007s]
Sending 'aop_b' (180 KB)                           OKAY [  0.005s]
Writing 'aop_b'                                    OKAY [  0.005s]
Finished. Total time: 0.027s
./fastboot flash --slot=all bluetooth bluetooth.img
Sending 'bluetooth_a' (748 KB)                     OKAY [  0.020s]
Writing 'bluetooth_a'                              OKAY [  0.011s]
Sending 'bluetooth_b' (748 KB)                     OKAY [  0.019s]
Writing 'bluetooth_b'                              OKAY [  0.009s]
Finished. Total time: 0.064s
./fastboot flash --slot=all cmnlib cmnlib.img
Sending 'cmnlib_a' (372 KB)                        OKAY [  0.011s]
Writing 'cmnlib_a'                                 OKAY [  0.008s]
Sending 'cmnlib_b' (372 KB)                        OKAY [  0.010s]
Writing 'cmnlib_b'                                 OKAY [  0.007s]
Finished. Total time: 0.041s
./fastboot flash --slot=all cmnlib64 cmnlib64.img
Sending 'cmnlib64_a' (488 KB)                      OKAY [  0.013s]
Writing 'cmnlib64_a'                               OKAY [  0.009s]
Sending 'cmnlib64_b' (488 KB)                      OKAY [  0.013s]
Writing 'cmnlib64_b'                               OKAY [  0.007s]
Finished. Total time: 0.047s
./fastboot flash --slot=all devcfg devcfg.img
Sending 'devcfg_a' (40 KB)                         OKAY [  0.002s]
Writing 'devcfg_a'                                 OKAY [  0.006s]
Sending 'devcfg_b' (40 KB)                         OKAY [  0.001s]
Writing 'devcfg_b'                                 OKAY [  0.004s]
Finished. Total time: 0.018s
./fastboot flash --slot=all dsp dsp.img
Sending 'dsp_a' (32768 KB)                         OKAY [  0.888s]
Writing 'dsp_a'                                    OKAY [  0.193s]
Sending 'dsp_b' (32768 KB)                         OKAY [  0.830s]
Writing 'dsp_b'                                    OKAY [  0.225s]
Finished. Total time: 2.140s
./fastboot flash --slot=all fw_4j1ed fw_4j1ed.img
Sending 'fw_4j1ed_a' (344 KB)                      OKAY [  0.009s]
Writing 'fw_4j1ed_a'                               OKAY [  0.008s]
Sending 'fw_4j1ed_b' (344 KB)                      OKAY [  0.009s]
Writing 'fw_4j1ed_b'                               OKAY [  0.006s]
Finished. Total time: 0.038s
./fastboot flash --slot=all fw_4u1ea fw_4u1ea.img
Sending 'fw_4u1ea_a' (344 KB)                      OKAY [  0.009s]
Writing 'fw_4u1ea_a'                               OKAY [  0.008s]
Sending 'fw_4u1ea_b' (344 KB)                      OKAY [  0.009s]
Writing 'fw_4u1ea_b'                               OKAY [  0.007s]
Finished. Total time: 0.037s
./fastboot flash --slot=all hyp hyp.img
Sending 'hyp_a' (388 KB)                           OKAY [  0.010s]
Writing 'hyp_a'                                    OKAY [  0.008s]
Sending 'hyp_b' (388 KB)                           OKAY [  0.010s]
Writing 'hyp_b'                                    OKAY [  0.007s]
Finished. Total time: 0.040s
./fastboot flash --slot=all keymaster keymaster.img
Sending 'keymaster_a' (228 KB)                     OKAY [  0.007s]
Writing 'keymaster_a'                              OKAY [  0.008s]
Sending 'keymaster_b' (228 KB)                     OKAY [  0.006s]
Writing 'keymaster_b'                              OKAY [  0.006s]
Finished. Total time: 0.030s
./fastboot flash --slot=all LOGO LOGO.img
Sending 'LOGO_a' (7824 KB)                         OKAY [  0.211s]
Writing 'LOGO_a'                                   OKAY [  0.055s]
Sending 'LOGO_b' (7824 KB)                         OKAY [  0.209s]
Writing 'LOGO_b'                                   OKAY [  0.053s]
Finished. Total time: 0.533s
./fastboot flash --slot=all modem modem.img
Sending 'modem_a' (117012 KB)                      OKAY [  3.080s]
Writing 'modem_a'                                  OKAY [  0.642s]
Sending 'modem_b' (117012 KB)                      OKAY [  3.058s]
Writing 'modem_b'                                  OKAY [  0.635s]
Finished. Total time: 7.418s
./fastboot flash --slot=all oem_stanvbk oem_stanvbk.img
Sending 'oem_stanvbk' (952 KB)                     OKAY [  0.025s]
Writing 'oem_stanvbk'                              OKAY [  0.012s]
Finished. Total time: 0.040s
./fastboot flash --slot=all qupfw qupfw.img
Sending 'qupfw_a' (64 KB)                          OKAY [  0.002s]
Writing 'qupfw_a'                                  OKAY [  0.006s]
Sending 'qupfw_b' (64 KB)                          OKAY [  0.002s]
Writing 'qupfw_b'                                  OKAY [  0.004s]
Finished. Total time: 0.019s
./fastboot flash --slot=all storsec storsec.img
Sending 'storsec_a' (24 KB)                        OKAY [  0.001s]
Writing 'storsec_a'                                OKAY [  0.006s]
Sending 'storsec_b' (24 KB)                        OKAY [  0.001s]
Writing 'storsec_b'                                OKAY [  0.004s]
Finished. Total time: 0.017s
./fastboot flash --slot=all tz tz.img
Sending 'tz_a' (2008 KB)                           OKAY [  0.053s]
Writing 'tz_a'                                     OKAY [  0.019s]
Sending 'tz_b' (2008 KB)                           OKAY [  0.053s]
Writing 'tz_b'                                     OKAY [  0.017s]
Finished. Total time: 0.148s
./fastboot flash --slot=all xbl xbl.img
Sending 'xbl_a' (3212 KB)                          OKAY [  0.085s]
Writing 'xbl_a'                                    OKAY [  0.034s]
Sending 'xbl_b' (3212 KB)                          OKAY [  0.083s]
Writing 'xbl_b'                                    OKAY [  0.076s]
Finished. Total time: 0.283s
./fastboot flash --slot=all xbl_config xbl_config.img
Sending 'xbl_config_a' (96 KB)                     OKAY [  0.003s]
Writing 'xbl_config_a'                             OKAY [  0.009s]
Sending 'xbl_config_b' (96 KB)                     OKAY [  0.003s]
Writing 'xbl_config_b'                             OKAY [  0.007s]
Finished. Total time: 0.027s
./fastboot flash --slot=all vendor vendor.img
Invalid sparse file format at header magic
Sending sparse 'vendor_a' 1/4 (261703 KB)          OKAY [  6.884s]
Writing 'vendor_a'                                 OKAY [  1.436s]
Sending sparse 'vendor_a' 2/4 (240994 KB)          OKAY [  6.400s]
Writing 'vendor_a'                                 OKAY [  1.336s]
Sending sparse 'vendor_a' 3/4 (253584 KB)          OKAY [  6.671s]
Writing 'vendor_a'                                 OKAY [  2.581s]
Sending sparse 'vendor_a' 4/4 (16364 KB)           OKAY [  0.427s]
Writing 'vendor_a'                                 OKAY [  0.103s]
Invalid sparse file format at header magic
Sending sparse 'vendor_b' 1/4 (261703 KB)          OKAY [  6.759s]
Writing 'vendor_b'                                 OKAY [  1.452s]
Sending sparse 'vendor_b' 2/4 (240994 KB)          OKAY [  6.332s]
Writing 'vendor_b'                                 OKAY [  1.330s]
Sending sparse 'vendor_b' 3/4 (253584 KB)          OKAY [  6.611s]
Writing 'vendor_b'                                 OKAY [  2.615s]
Sending sparse 'vendor_b' 4/4 (16364 KB)           OKAY [  0.421s]
Writing 'vendor_b'                                 OKAY [  0.104s]
 

CrysisLTU

Senior Member
Feb 1, 2012
311
371
Code:
./fastboot flash --slot=all abl abl.img
Sending 'abl_a' (2132 KB)                          OKAY [  0.065s]
Writing 'abl_a'                                    OKAY [  0.020s]
Sending 'abl_b' (2132 KB)                          OKAY [  0.063s]
Writing 'abl_b'                                    OKAY [  0.018s]
Finished. Total time: 0.172s
./fastboot flash --slot=all aop aop.img
Sending 'aop_a' (180 KB)                           OKAY [  0.005s]
Writing 'aop_a'                                    OKAY [  0.007s]
Sending 'aop_b' (180 KB)                           OKAY [  0.005s]
Writing 'aop_b'                                    OKAY [  0.005s]
Finished. Total time: 0.027s
./fastboot flash --slot=all bluetooth bluetooth.img
Sending 'bluetooth_a' (748 KB)                     OKAY [  0.020s]
Writing 'bluetooth_a'                              OKAY [  0.011s]
Sending 'bluetooth_b' (748 KB)                     OKAY [  0.019s]
Writing 'bluetooth_b'                              OKAY [  0.009s]
Finished. Total time: 0.064s
./fastboot flash --slot=all cmnlib cmnlib.img
Sending 'cmnlib_a' (372 KB)                        OKAY [  0.011s]
Writing 'cmnlib_a'                                 OKAY [  0.008s]
Sending 'cmnlib_b' (372 KB)                        OKAY [  0.010s]
Writing 'cmnlib_b'                                 OKAY [  0.007s]
Finished. Total time: 0.041s
./fastboot flash --slot=all cmnlib64 cmnlib64.img
Sending 'cmnlib64_a' (488 KB)                      OKAY [  0.013s]
Writing 'cmnlib64_a'                               OKAY [  0.009s]
Sending 'cmnlib64_b' (488 KB)                      OKAY [  0.013s]
Writing 'cmnlib64_b'                               OKAY [  0.007s]
Finished. Total time: 0.047s
./fastboot flash --slot=all devcfg devcfg.img
Sending 'devcfg_a' (40 KB)                         OKAY [  0.002s]
Writing 'devcfg_a'                                 OKAY [  0.006s]
Sending 'devcfg_b' (40 KB)                         OKAY [  0.001s]
Writing 'devcfg_b'                                 OKAY [  0.004s]
Finished. Total time: 0.018s
./fastboot flash --slot=all dsp dsp.img
Sending 'dsp_a' (32768 KB)                         OKAY [  0.888s]
Writing 'dsp_a'                                    OKAY [  0.193s]
Sending 'dsp_b' (32768 KB)                         OKAY [  0.830s]
Writing 'dsp_b'                                    OKAY [  0.225s]
Finished. Total time: 2.140s
./fastboot flash --slot=all fw_4j1ed fw_4j1ed.img
Sending 'fw_4j1ed_a' (344 KB)                      OKAY [  0.009s]
Writing 'fw_4j1ed_a'                               OKAY [  0.008s]
Sending 'fw_4j1ed_b' (344 KB)                      OKAY [  0.009s]
Writing 'fw_4j1ed_b'                               OKAY [  0.006s]
Finished. Total time: 0.038s
./fastboot flash --slot=all fw_4u1ea fw_4u1ea.img
Sending 'fw_4u1ea_a' (344 KB)                      OKAY [  0.009s]
Writing 'fw_4u1ea_a'                               OKAY [  0.008s]
Sending 'fw_4u1ea_b' (344 KB)                      OKAY [  0.009s]
Writing 'fw_4u1ea_b'                               OKAY [  0.007s]
Finished. Total time: 0.037s
./fastboot flash --slot=all hyp hyp.img
Sending 'hyp_a' (388 KB)                           OKAY [  0.010s]
Writing 'hyp_a'                                    OKAY [  0.008s]
Sending 'hyp_b' (388 KB)                           OKAY [  0.010s]
Writing 'hyp_b'                                    OKAY [  0.007s]
Finished. Total time: 0.040s
./fastboot flash --slot=all keymaster keymaster.img
Sending 'keymaster_a' (228 KB)                     OKAY [  0.007s]
Writing 'keymaster_a'                              OKAY [  0.008s]
Sending 'keymaster_b' (228 KB)                     OKAY [  0.006s]
Writing 'keymaster_b'                              OKAY [  0.006s]
Finished. Total time: 0.030s
./fastboot flash --slot=all LOGO LOGO.img
Sending 'LOGO_a' (7824 KB)                         OKAY [  0.211s]
Writing 'LOGO_a'                                   OKAY [  0.055s]
Sending 'LOGO_b' (7824 KB)                         OKAY [  0.209s]
Writing 'LOGO_b'                                   OKAY [  0.053s]
Finished. Total time: 0.533s
./fastboot flash --slot=all modem modem.img
Sending 'modem_a' (117012 KB)                      OKAY [  3.080s]
Writing 'modem_a'                                  OKAY [  0.642s]
Sending 'modem_b' (117012 KB)                      OKAY [  3.058s]
Writing 'modem_b'                                  OKAY [  0.635s]
Finished. Total time: 7.418s
./fastboot flash --slot=all oem_stanvbk oem_stanvbk.img
Sending 'oem_stanvbk' (952 KB)                     OKAY [  0.025s]
Writing 'oem_stanvbk'                              OKAY [  0.012s]
Finished. Total time: 0.040s
./fastboot flash --slot=all qupfw qupfw.img
Sending 'qupfw_a' (64 KB)                          OKAY [  0.002s]
Writing 'qupfw_a'                                  OKAY [  0.006s]
Sending 'qupfw_b' (64 KB)                          OKAY [  0.002s]
Writing 'qupfw_b'                                  OKAY [  0.004s]
Finished. Total time: 0.019s
./fastboot flash --slot=all storsec storsec.img
Sending 'storsec_a' (24 KB)                        OKAY [  0.001s]
Writing 'storsec_a'                                OKAY [  0.006s]
Sending 'storsec_b' (24 KB)                        OKAY [  0.001s]
Writing 'storsec_b'                                OKAY [  0.004s]
Finished. Total time: 0.017s
./fastboot flash --slot=all tz tz.img
Sending 'tz_a' (2008 KB)                           OKAY [  0.053s]
Writing 'tz_a'                                     OKAY [  0.019s]
Sending 'tz_b' (2008 KB)                           OKAY [  0.053s]
Writing 'tz_b'                                     OKAY [  0.017s]
Finished. Total time: 0.148s
./fastboot flash --slot=all xbl xbl.img
Sending 'xbl_a' (3212 KB)                          OKAY [  0.085s]
Writing 'xbl_a'                                    OKAY [  0.034s]
Sending 'xbl_b' (3212 KB)                          OKAY [  0.083s]
Writing 'xbl_b'                                    OKAY [  0.076s]
Finished. Total time: 0.283s
./fastboot flash --slot=all xbl_config xbl_config.img
Sending 'xbl_config_a' (96 KB)                     OKAY [  0.003s]
Writing 'xbl_config_a'                             OKAY [  0.009s]
Sending 'xbl_config_b' (96 KB)                     OKAY [  0.003s]
Writing 'xbl_config_b'                             OKAY [  0.007s]
Finished. Total time: 0.027s
./fastboot flash --slot=all vendor vendor.img
Invalid sparse file format at header magic
Sending sparse 'vendor_a' 1/4 (261703 KB)          OKAY [  6.884s]
Writing 'vendor_a'                                 OKAY [  1.436s]
Sending sparse 'vendor_a' 2/4 (240994 KB)          OKAY [  6.400s]
Writing 'vendor_a'                                 OKAY [  1.336s]
Sending sparse 'vendor_a' 3/4 (253584 KB)          OKAY [  6.671s]
Writing 'vendor_a'                                 OKAY [  2.581s]
Sending sparse 'vendor_a' 4/4 (16364 KB)           OKAY [  0.427s]
Writing 'vendor_a'                                 OKAY [  0.103s]
Invalid sparse file format at header magic
Sending sparse 'vendor_b' 1/4 (261703 KB)          OKAY [  6.759s]
Writing 'vendor_b'                                 OKAY [  1.452s]
Sending sparse 'vendor_b' 2/4 (240994 KB)          OKAY [  6.332s]
Writing 'vendor_b'                                 OKAY [  1.330s]
Sending sparse 'vendor_b' 3/4 (253584 KB)          OKAY [  6.611s]
Writing 'vendor_b'                                 OKAY [  2.615s]
Sending sparse 'vendor_b' 4/4 (16364 KB)           OKAY [  0.421s]
Writing 'vendor_b'                                 OKAY [  0.104s]
Everything seems fine. Hmm, not sure what the issue could be. If WiFi works with other ROMs, then it can't be a hardware problem. Try submitting a bug report to GitLab: https://wiki.lineageos.org/how-to/bugreport
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    Instructions :
    Downloads :
    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code:
    What is your--
    LineageOS version:
    LineageOS Download url:
    Gapps version:
    
    Did you--
    wipe:
    restore with titanium backup:
    reboot after having the issue:
    
    Are you using--
    a task killer:
    a non-stock kernel:
    other modifications:
    
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
    Whenever we take photo using stock lenage camera it is not focussing and pic get blurred
    1
    Do you guys also have the issue that if you take a photo in WhatsApp, the actually taken image always is BIGGER than shown on the screen before shooting the photo? Like, the image itself catches more than is shown on the screen, I am not talking file size.

    I had a similar issues as long as I was using GCam. After using GCam, this problem would also be present in other apps accessing the camera. A reboot fixed it.

    So I stopped using GCam, and went back to the default camera app.
    1
    Hi! I just installed LOS on a NOS ("new old stock") Oneplus 6 EU Version I got for a bargain. First I updated completely Stock to OOS 11.1.2.2. Then I installed the 20211228 build according to instructions. I am using a german provider in the O2/Telefonica Network. I activated VoLTE and VoWifi in the settings, but seeing the diagnostics when dialing *#*#4636#*#* it shows me it is using GSM for the calls, even though being connected to 4G with good signal strength. Is it a configuration thing or do I have to go through this Qualcom Modem Setup procederes, which can be found in the Stock ROM threads?
    To answer my own question: Yes, I had to use the Qualcom tools.

    How to enable VoLTE:
    1. Enable in settings and see if it works
    2. If yes, good, you're done. If no, follow this guide: https://forum.xda-developers.com/t/...geos-17-1-for-eu-carriers-oneplus-6t.4119785/

    Important: Backup your EFS Partition before applying any changes. You delete a config, which I dont know if it could be necessary at some point, or if you delete some other config by accident.

    Remark: You do not need magisk. It is enough to enable ADB + ADB root in developer settings. You can enable adb root by typing "adb root". When you then enter "adb shell", you have root permission. Also the mentionend "setprop" command didnt work. This one works: "setprop sys.usb.config diag,serial_cdev,rmnet,adb"
    1
    To answer my own question: Yes, I had to use the Qualcom tools.

    How to enable VoLTE:
    1. Enable in settings and see if it works
    2. If yes, good, you're done. If no, follow this guide: https://forum.xda-developers.com/t/...geos-17-1-for-eu-carriers-oneplus-6t.4119785/

    Important: Backup your EFS Partition before applying any changes. You delete a config, which I dont know if it could be necessary at some point, or if you delete some other config by accident.

    Remark: You do not need magisk. It is enough to enable ADB + ADB root in developer settings. You can enable adb root by typing "adb root". When you then enter "adb shell", you have root permission. Also the mentionend "setprop" command didnt work. This one works: "setprop sys.usb.config diag,serial_cdev,rmnet,adb"
    Omg, I had already given up on this, thank you so much, I got volte and vowifi working now, awesome
    1
    In b4 don't ask for ETAs, I know...
    But does anyone know if @LuK1337 is working on lineageos 19 for enchilada, or anyone else for that matter. Last year he had an early test build ready in October, now it's December. I'm definitely not complaining, just wondering if someone puts effort into this or if I will have to look for another device soon.
  • 30
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    Instructions :
    Downloads :
    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code:
    What is your--
    LineageOS version:
    LineageOS Download url:
    Gapps version:
    
    Did you--
    wipe:
    restore with titanium backup:
    reboot after having the issue:
    
    Are you using--
    a task killer:
    a non-stock kernel:
    other modifications:
    
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
    3
    If anybody is curious, Ive been crawling through the code commits. Unfortunately, it looks like both Enchilada and Fajita will have to wait for some time due to issues that were encountered when booting. At least for Fajita. It will be some time until we get our first official build.

    UPDATE 1: Both Enchilada and Fajita have been reverted from the hudson branch, which indicates official commit status has been reversed. Our savior Luk has got hands full with work on these issues I imagine, so wait times will extend. Hang tight lads! We will land on Hudson soon, I hope.

    UPDATE 2: That was quick! Seems like Luk figured out the issue for Fajita and has opened a commit to merge fajita to 18.1 official again. Fajita and enchilada are merged to the Hudson branch once again. This is good news, and I am hoping that the enchilada build will be posted and merged on schedule.
    3
    Anyone else having touchscreen issues with the latest build? Like not responding to some touches and not being able to pull down the notification shade?

    Edit: reverted to last week's build and the issue is gone. So some commit messes with the touchscreen.