[ROM][OFFICIAL][cedric][11] LineageOS 18.1

Search This thread

matiusuario

Member
Nov 18, 2020
29
19
Okay, to stop myself going round in circles can someone please clarify / confirm the following:

1. Do I HAVE TO flash stock Oreo before using any of the later Lineage releases (16.0, 18.1)?

2. If I do how do I do that? I am after straightforward and complete instructions (I have read about backing up the IMEI and passing safetynet - it's unclear to me whether these are necessary considerations).

3. What is the difference between 16.0 and 18.1 in terms of security? I see 18.1 is 'official' and 16.1 'unofficial', what does this mean?

4. It may be easier (I just want something straightforward) to go back to Lineage 14.1 (which I had been using for ages) but it seems that if I do this after flashing LOS 18.1 there may be issues. What issues?

What I did was:

• My phone was running Lineage 14.1 unofficial.
• I flashed LOS 18.1 using an old version of TWRP (non-64 bit I think).
• There are however problems with system time; GPS (it works but not with certain apps); and system speed i.e. it seems slow.
• I would like to look at alternatives but want to do it properly.

Any help much appreciated, thanks.
Hi again.
Some other things adding to what I replied in the other thread:
1. You have to flash stock only when switching from a7/a8 to a9-or-later or from a9-or-later to a7/a8. Some issues might appear if you don't do so are fingerprint functionality lost, loudspeaker calls and I don't know what else.
2. Back up efs and persist with twrp 3.5.2 or later only once, not needed every time you flash a ROM. But remember where you save the back up. More-than-one place is recommended. e.g sd and pc.
3. Read the other thread.
4. As you aren't sure what your current firmware base is, I suggest you to upgrade twrp, then install twrp-flashable stock and the rom you want. (stock version depends on what rom you are willing to install).
 

Ciantic

Member
Jan 21, 2019
5
0
Hi again.
Some other things adding to what I replied in the other thread:
1. You have to flash stock only when switching from a7/a8 to a9-or-later or from a9-or-later to a7/a8. Some issues might appear if you don't do so are fingerprint functionality lost, loudspeaker calls and I don't know what else.
2. Back up efs and persist with twrp 3.5.2 or later only once, not needed every time you flash a ROM. But remember where you save the back up. More-than-one place is recommended. e.g sd and pc.
3. Read the other thread.
4. As you aren't sure what your current firmware base is, I suggest you to upgrade twrp, then install twrp-flashable stock and the rom you want. (stock version depends on what rom you are willing to install).
Hi again.
Some other things adding to what I replied in the other thread:
1. You have to flash stock only when switching from a7/a8 to a9-or-later or from a9-or-later to a7/a8. Some issues might appear if you don't do so are fingerprint functionality lost, loudspeaker calls and I don't know what else.
2. Back up efs and persist with twrp 3.5.2 or later only once, not needed every time you flash a ROM. But remember where you save the back up. More-than-one place is recommended. e.g sd and pc.
3. Read the other thread.
4. As you aren't sure what your current firmware base is, I suggest you to upgrade twrp, then install twrp-flashable stock and the rom you want. (stock version depends on what rom you are willing to install).

I got 8.1 Android error as well, but fixed it by flashing CEDRIC_RETAIL_8.1.0_OPP28.85-19-4-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip which is found in here:

https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/cedric/official/RETAIL/

You open the zip to your computer and painfully do the fastboot commands as instructed in this thread:

fastboot oem fb_mode_set
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk....
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot

After that LineageOS 18.1 installed fine.

As a word of caution some reported that SIM card does not work after that, given that I use with WIFI only I don't care.
 
Last edited:

matiusuario

Member
Nov 18, 2020
29
19
I got 8.1 Android error as well, but fixed it by flashing CEDRIC_RETAIL_8.1.0_OPP28.85-19-4-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip which is found in here:

https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/cedric/official/RETAIL/

You open the zip to your computer and painfully do the fastboot commands as instructed in this thread:

fastboot oem fb_mode_set
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk....
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot

After that LineageOS 18.1 installed fine.

As a word of caution some reported that SIM card does not work after that, given that I use with WIFI only I don't care.
Well... That's why I said to install the twrp-flashable stock, it's just one-tap and done, moreover it's safer because you won't screw it up by a wrong command nor loose your imei tinkering with software channels
 

Ciantic

Member
Jan 21, 2019
5
0
Well... That's why I said to install the twrp-flashable stock, it's just one-tap and done, moreover it's safer because you won't screw it up by a wrong command nor loose your imei tinkering with software channels
I tried TWRP flash stock before doing that, it didn't remove the Android 8.1 error.

Specifically I tried this:

cedric-twrp-OPP28.85-13.zip

It flashed just fine, but didn't remove error.

So fastboot was required?
 

matiusuario

Member
Nov 18, 2020
29
19
I tried TWRP flash stock before doing that, it didn't remove the Android 8.1 error.

Specifically I tried this:

cedric-twrp-OPP28.85-13.zip

It flashed just fine, but didn't remove error.

So fastboot was required?
That's because version [...]85-13 is not the latest. You should install "cedric-twrp-OPPS28.85-19-4-2.zip" to avoid the "Upgrade firmware and retry" error
 

pawelluk

Member
Sep 18, 2016
5
0
Hello,

I have a moto G5 XT1671. I have booted into stock rom, and verified android 8.1. Have followed the procedure multiple times with flashing recovery, and then the latest lineageos rom through sideload.

So here is the issue. Every time I try the stock rom it boots into it no issues, and all works. Then when I flash the latest lineageos rom, it always just boots into recovery no matter what I do.

I have cleared dalvik, data, system, cache, and flashed lineageos again with no success.

Should add no errors while flashing.

Any feedback would be much appreciated.
 

pawelluk

Member
Sep 18, 2016
5
0
Hello,

I have a moto G5 XT1671. I have booted into stock rom, and verified android 8.1. Have followed the procedure multiple times with flashing recovery, and then the latest lineageos rom through sideload.

So here is the issue. Every time I try the stock rom it boots into it no issues, and all works. Then when I flash the latest lineageos rom, it always just boots into recovery no matter what I do.

I have cleared dalvik, data, system, cache, and flashed lineageos again with no success.

Should add no errors while flashing.

Any feedback would be much appreciated.

Found out that I could only boot into ROM whether stock or lineageos by using this sequence BOOTLOADER->FACTORY MODE.

I fixed the issue using this guide:

 

Top Liked Posts

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

    Code:
    #include <std_disclaimer.h>
    
    /*
    * Your warranty is now void.
    *
    * We are 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 us for messing up your device, we will laugh at you.
    *
    */

    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.

    Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.

    Instructions:
    • Download the latest build, recovery image and GApps (if you need them)
    • Flash the downloaded recovery image via fastboot
    • Boot to recovery
    • Format system and perform a factory reset
    • Reboot to recovery
    • Flash the latest build
    • Flash GApps and any other necessary add-ons

    What's working:
    • WiFi
    • Camera and Camcorder
    • Bluetooth
    • NFC
    • Fingerprint - Oreo firmware required
    • GPS
    • OTG
    • Video Playback
    • Audio
    • RIL
    • VoLTE/VoWiFi
    • USB tethering/audio
    • SELinux: Enforcing

    Known issues:
    • You tell me

    Downloads:

    Reporting Bugs
    • All bugs should be reported here: Issue Tracker
    • 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 /proc/last_kmsg. (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:

    Thanks to:
    @GivFNZ for testing my builds
    @wiktorek140, @karthick mostwanted, @wh0dat, @KalilDev, @AsD Monio, @GoldeneyeS2, @Steve Mathew Joy and @rajatgupta1998 for their hard work on our device sources
    LineageOS team

    Changelogs:

    Code:
    2021-04-08:
    Initial build.


    Source code:
    5
    just to verify.
    i have to put this on a sd card and install them on the phone with TWRP?
    No, sorry for not explaining.
    You download the ZIP on your PC, extract it (or extract NON-HLOS.bin from the ZIP).
    Then you reboot your phone to the bootloader, connect it to the PC and flash the file to the modem partition:
    Bash:
    fastboot flash modem NON-HLOS.bin
    3
    No, that didn't help. I tried that already. Tried again now, flashed newest recovery image and tried again - didn't work. Updated to latest version with adb sideload.

    Thanks for your efforts by the way :)
    It should be fixed in the next build - you'll still have to sideload that one, but future builds should update OTA fine
    3
    And sadly there probably won't be a LOS 19 build for cedric ever, see https://lineageos.org/Changelog-26/ (section Let’s talk about legacy devices…) It says there: "[...] for devices using kernel versions 3.18 and below, this may be the end of the road." Well, cedric is on 3.18...
    Yeah, I've seen that as well; it would be great if @JarlPenguin could somehow comment on that one.
    If we ever get sensors and in-call audio fixed on 4.9, then LineageOS 19 will officially be supported. Until then there will be no (un)official support.
    3
    Okaaay ... this seems to be more compliacted than expected. How did you guys upgrade to Oreo FW? Where did you get it from?

    Thanks
    update firmware from pc in fastboot mode volume down (-) connect to pc

    Firmware LATAM XT1670 (amxla) Mini
    Firmware RETAIL XT167x (retail) Mini