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

[ROM][OFFICIAL][montana][11] LineageOS 18.1

Search This thread

mattdpollard

Member
Sep 9, 2020
25
7
I think this ROM is abandoned... =(
I'm going back to the Stock ROM.
It's updated weekly so hardly abandoned, I think!

As far as I understand, once it went official, bugs were to be reported on gitlab, not in this thread. https://gitlab.com/LineageOS/issues/android/-/issues?scope=all&state=opened

This is what we are told to do in the first post in this thread.

So the ROM is active but this thread isn't the main place to raise issues.

I don't know if anyone has raised the OTA update issue in the official bug reporting system, I hadn't until now as it isn't an urgent issue for me. But if you want it fixed as far as I understand that is the place to report it, so I have just reported it as an issue there.
 
Last edited:

jaysonwcs

Member
Apr 21, 2020
9
1
Moto G5S
It's updated weekly so hardly abandoned, I think!

As far as I understand, once it went official, bugs were to be reported on gitlab, not in this thread. https://gitlab.com/LineageOS/issues/android/-/issues?scope=all&state=opened

This is what we are told to do in the first post in this thread.

So the ROM is active but this thread isn't the main place to raise issues.

I don't know if anyone has raised the OTA update issue in the official bug reporting system, I hadn't until now as it isn't an urgent issue for me. But if you want it fixed as far as I understand that is the place to report it, so I have just reported it as an issue there.
Oh, I didn't know that.
I will do that.

Thanks!
 

mattdpollard

Member
Sep 9, 2020
25
7
The OTA update failure continues with today's build (19 July 2021).
I opened a bug report here last week as per the instructions in the first post in this thread, but it does not appear to have been assigned yet: link

Out of curiosity, is there anyone on this thread who is still able to successfully update using in the built-in app?
 

newinnov

Senior Member
Sep 11, 2012
225
52
Hi Jarl,

Montana does not support VoLTE with "vi" carrier, Every time call comes devices switches to 3g instead of taking volte call.
4g bands are supported by g5s too ie - B1, B3, B5, B41 .

Is volte working fine for you guys?
 

newinnov

Senior Member
Sep 11, 2012
225
52
The OTA update failure continues with today's build (19 July 2021).
I opened a bug report here last week as per the instructions in the first post in this thread, but it does not appear to have been assigned yet: link

Out of curiosity, is there anyone on this thread who is still able to successfully update using in the built-in app?
As far as I know , ota update is broken at present for several devices not just for montana with lineage, it used to work fine for older android versions though. SO may be problem with lineage side...
 

JarlPenguin

Recognized Developer
Oct 16, 2018
979
874
Earth
github.com
Moto G5S
Moto G7
Any reason for that? TWRP backups, File manager and the Terminal are very useful.
It's not worth it. Decryption with PIN/pattern as method doesn't work with Android 11+ due to some changes that Google has made. Our recovery partition is too small to hold any version of TWRP past the Nougat-based version, so we can't fix that either.
Also, the average user won't have a need to use the file manager or terminal inside recovery, and backups can be done using LineageOS' built-in Seedvault app and using dd for special partitions (persist and EFS). If they do need to use a terminal inside recovery, they can always use ADB.
 
  • Like
Reactions: rpcll

rpcll

Senior Member
Aug 14, 2014
74
6
I'm kind of afraid of messing up the upgrade from 17.1 to 18.1 and losing data.
So if i do a TWRP backup now, then switch to lineageos recovery and flash the 18.1 zip and sth goes wrong, how do I go back? can i reflash the old twrp and restore my backup?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    With the advice of OP and my own research, I can finally recover IMEI for my montana. I write the steps I took. Since OP knows everything about montana and related phones, his explanation is kind of difficult for newbies like me. So I offer description that could be understood by anyone. The essence for this operation is to do 'persist fix', that is not clear for newbies. For detailed explanation about persist fix, refer to the article in other thread that is targeted to 'potter'. For short, you should change ownership for the folders (and their contents) of /persist/rfs and /persist/hlos_rfs. Please keep in mind that this ownership change operation only be done under Nougat stock ROM. So, our 1st step is to install Nougat to your phone.
    (1) Download Nougat stock ROM.
    Whatever software channel is for your phone, find Nougat stock is not easy. Try find the Nougat stock for RETAIL.
    (2) Install Nougat to your phone
    Install with fastboot is quite straitforward. I was advised by OP to avoid flash bootloader and gpt. I do not know the reason, but I did it accordingly. You might be disappointed when you boot RETAIL Nougat stock. The baseband shows 'unknown'. Of course, you cannot see IMEI. But relax, these are not essential at this stage.
    (3) Install TWRP
    No need to explain here I guess.
    (4) Install Magisk
    Under TWRP you can install Magisk to your Nougat stock ROM.
    (5) Reboot to your Nougat ROM
    You should see Magisk logo in your Nougat. Then enable developer options and enable ADB debugging.
    (6) Connect your phone to PC
    You connect your phone to PC via adb. adb devices should show your phone is connected as device. Then type su. With the aid of Magisk you can get root privilege. Then do
    ls -l /persist
    you should show various files. If not, check the steps. Still you do not see anything, no help could be possible, sorry.
    After this follow 'persist fix' operation (change the ownership).
    (7) Reboot to bootloader
    You can do:
    fastboot erase modemst1
    fastboot erase modemst2
    I do not know if these operations are really needed or not. Just do it to keep everything for sure. Then, reboot to the system. You might be disappointed again because you cannot see IMEI. This is because baseband is unknown, do not worry, go ahead.
    (8) Install the latest Oleo ROM
    Go into your latest Stock ROM. Now you should see correct baseband, and IMEI! Yes it is back.

    I hope this description works for you. Thank you for your reading.
    1
    Install with fastboot is quite straitforward. I was advised by OP to avoid flash bootloader and gpt.
    You shouldn't flash bootloader and gpt because it'll try to downgrade the bootloader and partition table which will result in a hard brick that can only be fixed with a working blankflash.
  • 3
    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 18.1 build.
    
    2020-10-13:
    Initial release.


    Source code:
    3
    I've uploaded a build for LineageOS 18.1. Official status will be gained shortly after we've tested things on a wider variety of devices.
    3
    Thank you! Just curious, what was the core reason of the issue?
    It was a problem with the F2FS driver.
    2
    I'm not rushing him for updates, just a question to mention that someone still with some interest on his ROM
    I will continue with this project, but only after the 18.1 source is fully ready.
    2
    Hi, OTA update worked great today, thanks Jarlpenguin!