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?
[ROM][OFFICIAL][enchilada][11] LineageOS 18.1
- Thread starter LuK1337
- Start date
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.
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.
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
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.
Terminator.J
Senior Member
Update firmware on enchilada | LineageOS Wiki
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.
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
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:
I'm on FW OOS 10.3.9 and LOS 18.1-20210511.
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.
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.This is gonna be guide to update fw
- remove encryption password
- take backup (as a precaution)
- flash OOS zip file with desired firmware level, flash custom rom zip file, flash twrp (without rebooting or changing active partition inbetween)
- reboot into recovery (active partition should change)
- repeat step 3 (to get other partition on the same firmware level)
- reboot into system and re-set encryption password and fingerprints
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
Thanks kouzelnik3! If so, it should also work with latest OOS(11.XX) and this TWRP https://xdaforums.com/t/recovery-11-official-teamwin-recovery-project.4306803/?
kouzelnik3
Senior Member
Yup, it definitely should and will work this way. I have updated this way too.
followed the instruction again... same problem:
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 android.hardware.wifi@1.0-service: Failed to write driver state control param: Invalid argument
12-06 10:42:27.681 832 832 E android.hardware.wifi@1.0-service: Failed to load WiFi driver
12-06 10:42:27.681 832 832 E android.hardware.wifi@1.0-service: Failed to initialize firmware mode controller
12-06 10:42:27.681 832 832 E android.hardware.wifi@1.0-service: 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 HalSeems 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]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
./fastboot flash --slot=all vendor vendor.img
Invalid sparse file format at header magic
could this be a error
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
36
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
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:98Guys I was checking out the gerrit and found something to be excited about.
If I interpret it right, we should be included in the initial batch of devices being promoted to 19.1
and Luk1337 is probably staying our Maintainer.6
GAPPS are preserved. If you dont need anything fancy, then also just use LineageOS recovery. This will most probably also fix your update isues on OP3.Dear Forum, i plan to switch my OP6 back to LOS as well.
Back, because once i bought it some years ago, i was running LOS on it, but then switched to OOS, due to some struggles (and it was the first phone since the good old Motorola Milestone, where CyanogenOS gave me Froyo for the first time ).
I don't need root or anything extraordinary, just LOS and Google apps. my Question: will the build in updater work and preser Gapps during updates? In the past due to A/B Layout, i always had to go to recovery, flash update and gapps, reboot into Recovery, flash gapps again, to no loose them.
And on my OP3 the builtin Updater is not working, i always have to flash manually through TWRP ;(
Thanks in advance!
Also had a OP3 before and LOS recovery worked flawless.
Slightly "offtopic":
I was kind of afraid that our OP6 support was dropped, because nothing happened on the LineageOS Gerrit regarding our device. But Lukasz jsut pushed a whole lot of commits. So Android 12 seems inbound! (Whenever LOS team decides to release)
4
No need for fastboot. Go into the Magisk app before installing the OTA, click on Uninstall Magisk, then Restore Images. Now install the OTA via the built in updater. Once the OTA update is installed, do not reboot. Go back into the Magisk app. Click on Install Magisk, select Install to Inactive Slot (After OTA), and only then reboot.
Full instructions can be found here: https://topjohnwu.github.io/Magisk/ota.html
![[GER]Roxxor](/data/avatars/s/2923/2923886.jpg?1600603243){kind=avatar}
