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

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

Search This thread

JarlPenguin

Recognized Developer
Oct 16, 2018
998
886
Earth
github.com
Moto G5S
Moto G7
Thank you for your consideration. If I were you, I would respond in the same way. Sorry asking an impossible request.
BTW, someone out there have experience install different type of stock? I mean, what happens if I install reteu stock, for example, to my XT-1797 (retapac). This might break my phone into brick state?
I want to ask before I might damage my montana.
Waiting for your experience.

Edit: Just say it is a stupid idea is okay. LoL.
You should install either retapac or retail stock.
 

buddhist_monkey

New member
Oct 8, 2017
4
0
Fürth
Hey guys!
Facing some problems and need your help quite urgently...

Since the last ota update trebuchet crashed several times, but started running right away. Last night the phone shut down completely. When I restarted it in the morning, there was only some strange notification that offered to reset to factory settings. This didn't work, too.
All attempts to restore backups failed. The following error was shown: "Error opening: '/data/system/packages.list' (no such file or directory)"
I've checked via TWRP, the file is there...
My last attempts produced "extractTarFork() process ended with ERROR: 225"

Any ideas?

Thanks in advance!
 

Attachments

  • IMG_20210814_232906.jpg
    IMG_20210814_232906.jpg
    954.8 KB · Views: 17

xproot

Member
Jul 30, 2021
5
0
Moto G5
Moto G5S
The ROM is not working on my device model XT1791
First time boot I tried to do it without wiping the default factory update to see what would happen. After some time it showed an encrypting screen that lasted for like 10-20 minutes, then it went back to the boot animation and didn't do anything else

Second time I wiped the data like I'm supposed to and tried booting, it did nothing for like an hour, just on the boot animation
 

JarlPenguin

Recognized Developer
Oct 16, 2018
998
886
Earth
github.com
Moto G5S
Moto G7
Hey guys!
Facing some problems and need your help quite urgently...

Since the last ota update trebuchet crashed several times, but started running right away. Last night the phone shut down completely. When I restarted it in the morning, there was only some strange notification that offered to reset to factory settings. This didn't work, too.
All attempts to restore backups failed. The following error was shown: "Error opening: '/data/system/packages.list' (no such file or directory)"
I've checked via TWRP, the file is there...
My last attempts produced "extractTarFork() process ended with ERROR: 225"

Any ideas?

Thanks in advance!
Why are you using TWRP in the first place? The only supported recovery is LineageOS recovery - TWRP can cause problems in Android 10 and above
The ROM is not working on my device model XT1791
First time boot I tried to do it without wiping the default factory update to see what would happen. After some time it showed an encrypting screen that lasted for like 10-20 minutes, then it went back to the boot animation and didn't do anything else

Second time I wiped the data like I'm supposed to and tried booting, it did nothing for like an hour, just on the boot animation
Did you perform a factory reset in LineageOS recovery?
 
  • Like
Reactions: xproot

JarlPenguin

Recognized Developer
Oct 16, 2018
998
886
Earth
github.com
Moto G5S
Moto G7
Thanks. Wasn't aware of this.
No OS is found and I wasn't able to connect to PC in bootloader.
Still, any suggestions?
By the way, I wasn't able to use an old backup of stock 8.1.
You have no choice but to factory reset. Make sure you have a backup of EFS and Persist as well, just in case you lose IMEI. Also, the wiki contains clear instructions on how to install the ROM, so make sure you follow them.
 

Korin67

Senior Member
Feb 24, 2018
225
97
Hello montana owners,
I have a "half-broken" montana (XT1797, RETAPAC). I know I was silly because I did not backup /persist and EFS. Before totally give up about my montana, I want to know what happened to my phone.
The situation is as follows:
When go back to the latest stock ROM, I can see the baseband (ends with the letter 'u'). But IMEI=0, ofc no communication with SIM is possible. Then, came back to custom ROM, LOS18.1. Under this custom ROM I can see the baseband (the same as that in stock ROM but the last letter changed to 'R'). Surprisingly, I can see IMEIs. Yes, I can use SIM, but only with 3G. It does not try to receive LTE signals. So I call my montana "half-broken". I checked /persist folder. It exists but EMPTY; No file there.
I tried erase modemst1/2 approach without success. First of all why custom ROM can get correct IMEIs with empty /persist?
I do not expect recover my montana. I want to know what is the real reason why my montana is not fully functional. Any suggestion to analyze my montana is appreciated.
 

JarlPenguin

Recognized Developer
Oct 16, 2018
998
886
Earth
github.com
Moto G5S
Moto G7
Hello montana owners,
I have a "half-broken" montana (XT1797, RETAPAC). I know I was silly because I did not backup /persist and EFS. Before totally give up about my montana, I want to know what happened to my phone.
The situation is as follows:
When go back to the latest stock ROM, I can see the baseband (ends with the letter 'u'). But IMEI=0, ofc no communication with SIM is possible. Then, came back to custom ROM, LOS18.1. Under this custom ROM I can see the baseband (the same as that in stock ROM but the last letter changed to 'R'). Surprisingly, I can see IMEIs. Yes, I can use SIM, but only with 3G. It does not try to receive LTE signals. So I call my montana "half-broken". I checked /persist folder. It exists but EMPTY; No file there.
I tried erase modemst1/2 approach without success. First of all why custom ROM can get correct IMEIs with empty /persist?
I do not expect recover my montana. I want to know what is the real reason why my montana is not fully functional. Any suggestion to analyze my montana is appreciated.
On LineageOS you should check /mnt/vendor/persist.
 

Korin67

Senior Member
Feb 24, 2018
225
97
Would you mind trying to flash stock 7.1 (with exception of bootloader and gpt) and erasing modemst, and then applying the OTA updates?
If possible I will. However, I only find 8.1.0 Stock ROM for RETAPAC. Yes, I could find stock 7.1 for RETAIL. But when I tried, I found that baseband is unknown at that time.
 

MrNice

Senior Member
Jan 2, 2021
97
4
Countryside
I don't recall the details, but I think it was when I first switched from 17.1 lineage with TWRP, to 18.1 with Lineage recovery, that the phone would restart to the PIN entry screen but would not accept my PIN. In the end after trying various workarounds found online, I had to wipe the phone and start from zero. I seem to recall others having a similar issue, maybe discussed earlier in this thread. So definitely back up as much as you can preferably manually to be sure (seedvault unfortunately excludes a lot for me at least), and I think somewhere I saw someone suggest removing the PIN and fingerprint lock before you do the upgrade, but then someone earlier in this chain seems to say they had the same issue even having done that.

That issue was fixed in a recent build, so it shouldn't happen anymore (at least according to the user who was affected, it was fixed)
Hi
The issue mattdpollard had is exactly what I have right now.
I own a Samsung Galaxy S6 with LOS 17.1 for only 3 months. I did one weekly update fine but few weeks later the same process failed as explained above. I had to recover from a nandroid backup.
I try to solve that now but I didn't know this is a outlined issue. As JarlPenguin said this issue is now fixed, could you let me in what LOS version 17.1 or 18.1 and a link to it.
I don't think LOS 18.1 is reliable for Samsung S6. Could you confirm?
So, I stop my test here and will recover with my nandroid backup again.
I hope you have all these answers. Advice are welcome as I am not very skilled in this field.
Thanks
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Good to know then. LineageOS won't boot on a device running < 8.1 firmware.
    Yeah I think that's what I was running, but I don't think I was on the very latest version. Anyway thanks for your works !
  • 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
    • USB tethering/audio
    • SELinux: Enforcing

    Known issues:
    • VoWiFi
    • 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
    Hi, normally I post here only when there is a problem. This time I wanted to post just to say everything has been working very smoothly for weeks and I really appreciate all the work that goes into making that happen!
    3
    Thank you! Just curious, what was the core reason of the issue?
    It was a problem with the F2FS driver.
    2
    Hi, OTA update worked great today, thanks Jarlpenguin!