[ROM][OFFICIAL][RIVER][NIGHTLIES] LineageOS 17.1

[Donnie267]

Is anyone aware if there's any work being done to update to 18.1? Would be nice to use a more updated version of android.

 

[NTGDeveloper]

Is anyone aware if there's any work being done to update to 18.1? Would be nice to use a more updated version of android.

Pretty sure that LOS Official doesn't announce new versions until the end of March/beginning of April. That's at least what it has been for 16 and 17 the past couple of times. Keep an eye out on https://lineageos.org for any updates.

 

[castleofiron]

i think my device got bricked, i got through all the steps but when the device started its first boot after whole flash, it restarted to bootloader, and now it says oem_locked.
i tried to run twrp by boot command it says permission denied.

this is what i got from getvar all

what can i do now, there is no os installed, and im stuck at bootloader that does not allow anything, and i tried again to unlock bootloader but it is not working

(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-river_retail-cf76a327f28-210125
(bootloader) product: river
(bootloader) board: river
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RH64AB RV=08 PV=05 FV=0000000000000005
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: 9af1a87f
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-river_retail-cf76a327f28-210125
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
(bootloader) pcb-part-no:
all: listed above

 

[TheShanMan]

I just did my first OTA update today and Magisk+Modules did not carry over to the other slot. They were originally installed on Slot B, but when the device switched to A, it wasn't installed. That goes for all of my boot image mods, like TWRP. It was replaced with the stock LineageOS recovery. I don't know if it will do the same thing on another OTA update that switches the slot again, but we will have to see what happens next week.

I just installed the new OTA update, which is my 2nd update. It looks like magisk does persist in a given slot. So when I first installed LOS, I installed magisk. When I installed my first OTA update, I had to install it again (other slot), although my modules persisted. When I installed my second update just now (back to the first slot), I did NOT have to install magisk again. So in summary it seems you have to install magisk once per slot and then you're gtg from then on.

 

[kdm6389]

Does this ROM support VoLTE?

 

[SyberHexen]

Does this support VoLTE

There are no known issues with VoLTE

 

[Droid4200]

There are no known issues with VoLTE

That's weird, at first I thought 17 had it, then it disappeared, I upgraded to 18, it did get volte, then downgraded back to 17 and the option in setting doesn't have volte. But speaking of volte I need to upgrade to get that back it'd a nice feature to not lose data when my phone rings. Was there an extra step or something I needed to flash to get volte on 17? I haven't reflashed in so long I actually forgot.
Thanks