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

Search This thread

Donnie267

Senior Member
Oct 23, 2017
119
5
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.
 
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

New member
Mar 30, 2021
1
0
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

Code:
(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

Senior Member
Oct 29, 2013
85
9
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.
 
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
 

Top Liked Posts

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

    Moto G7
    Code:
    /*
     * Your warranty is now void.
     *
     * I am not responsible for bricked devices, dead SD cards,
     * thermonuclear war, or you getting fired because the alarm app failed. Please
     * do some research if you have any concerns about features included in this ROM
     * before flashing it! YOU are choosing to make these modifications, and if
     * you point the finger at me for messing up your device, I will laugh at you.
     */

    Introduction:
    This is the Official Lineage OS 16.0 thread for the Motorola Moto G7, codename river.

    Join our Moto G7 Development Telegram Group!

    How to Install:
    Please follow the instructions on our Official LineageOS Wiki page here.
    IF YOU ARE COMING FROM STOCK AND WANT TO INSTALL CUSTOM ROMS FOR FIRST TIME, INSTALL "Copy Partitions Zip" FROM POST #2

    If you don't follow these instructions, please don't expect support here. We also don't support 3rd party addons (Magisk/XPosed/Dolby/Viper/etc.), so please don't seek support if you use these.

    Notes:
    • Official Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status. (Magisk works fine with SafetyNet patcher modules, though is not supported.)

    Download:


    XDA:DevDB Information
    river-lineageos, ROM for the Moto G7

    Contributors
    erfanoabdi, SyberHexen
    Source Code: https://github.com/LineageOS

    ROM OS Version: Android 10
    ROM Kernel: Linux 4.x
    Based On: LineageOS

    Version Information
    Status: Nightly

    Created 2019-11-16
    Last Updated 2020-08-09
    6
    Copy Partitions Zip
    - courtesy @ @filipepferraz
    Download
    4
    I had the same issue. It's not the size of the partition, its the order the software is installed and the reboots done during the process. I joined the telegram group for the G7 and found some very helpful information related to the installation of LineageOS 16.0 on the G7. Here are the steps for a clean flash.

    Very important - Flash the copy-partitionsAB.zip to replicate the slot A and slot B layout.
    - Clean flash:
    1) Put the phone in bootloader mode
    1.2) Connect phone to PC with a USB cable.
    1.3) In a Command prompt window, run "fastboot getvar all".
    1.4) Make slot A the active slot "fastboot set_active a".
    1.5) Boot TWRP "fastboot boot twrp.img" (use the file name on your PC for the TWRP img file)
    1.6) check active slot in Reboot menu - set to A
    2) Flash lineage zip
    3) Flash twrp installer zip
    3.5) Format data while in TWRP.
    4) Reboot to bootloader from TWRP.
    5) fastboot -w (this will wipe your userdata partition)
    6) Reboot to TWRP recovery (it should be installed when you flashed the twrp-installer zip)
    6.5) check active slot in Reboot menu - set to A
    7) Flash opengapps zip (use the arm64 version)
    7.5) Flash magisk zip (optional, only if you want root)
    8) Reboot system on slot A

    The G7 is my first A/B slot device and I struggled with the configuration. TWRP recovery is part of the boot partition. Installing the lineage zip, then the TWRP installer zip seems to be the required order. Then, rebooting TWRP from the installed image works to install OpenGApps. The active slot is very important, too. Many times during my installation ordeal, I would think that slot a was active, but it was slot b. I installed the copy-partitions zip when we were made aware of no bootloader on slot b a few weeks ago.

    Good luck.

    I flashed mine in almost the same way. So far loving LOS 16 w/ pico gapps

    1) Put the phone in bootloader mode
    1.2) Connect phone to PC with a USB cable.
    1.3) In a Command prompt window, run "fastboot getvar all".
    1.4) Make slot A the active slot "fastboot set_active a".

    Coming from stock it is automatically on slot A. Slot B on my device is blank because I clean flashed motos latest firmware.
    1.5) Boot TWRP "fastboot boot twrp.img" (use the file name on your PC for the TWRP img file)
    1.6) check active slot in Reboot menu - set to A
    Format data in TWRP
    Wipe /system, /data, & cache (not internal storage)

    2) Flash lineage zip
    3) Flash twrp installer zip
    3.5) Format data while in TWRP.
    4) Reboot to bootloader from TWRP.
    5) fastboot -w (this will wipe your userdata partition)
    6) Reboot to recovery (TWRP will load on slot B automatically)
    Slot automatically changes to B on reboot (B was set to active during LOS install; slot A is set to inactive so it doesn't boot anymore)
    6.5) check active slot in Reboot menu - set to A
    7) Flash opengapps zip (use the arm64 version)
    fastboot -w
    7.5) Flash magisk zip (optional, only if you want root)
    I left out root this time.
    8) Reboot system on slot A
    Boot system (no slot choice B is the only active slot).

    My only gripe is that updates through the LOS updater menu take like 30 minutes. They finish fine but half an hour is that normal?
    3
    Hello,

    I have received this week my new phone : Moto G7 (river) (xt1962-5)
    And, as a lot of people here, it took me a lot of tries and error messages to manage to just install LineageOS 16.0 + Gapps.
    The LineageOS official procedure never worked for me.
    Here are my learnings :

    My phone came with the stock OS (build PPO29.80-29) on slot A.
    It automatically installed a Motorola OTA update (build PPO29.80-66) on slot B.
    So at that point both slots were populated. (This is a pre-requirement)
    Then I unlocked the bootloader.
    The slot B is the one I wanted to install LineageOS because this is the slot with the most up to date secondary partitions (like /vendor /radio)

    Here is the only procedure I could repeat without any bugs/error messages :
    * Boot to bootloader
    * "fastboot --set-active=a"
    * "fastboot boot twrp-3.3.1-2-river.img" (temporay boot of TWRP on slot A)
    * format /data
    * Reboot to bootloader
    * "fastboot boot twrp-3.3.1-2-river.img" (temporay boot of TWRP on slot A)
    * Wipe /data /cache /system (will apply automatically to slot B)
    * "adb sideload lineage-16.0-20200207-nightly-river-signed.zip" (will apply automatically to slot B)
    * Reboot to recovery slot B (LineageOS recovery)
    * Install update : "adb sideload open_gapps-arm64-9.0-pico-20200207.zip" (will apply automatically to slot B)
    * Stay inside the LineageOS recovery and do a factory reset
    * Reboot
    * Enjoy


    The only thing I missed is that I was not able to do a backup of the stock ROM, so I will not be able to update secondary partitions (like /vendor /radio) in the future.