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

Search This thread
Feb 26, 2021
7
1

Attachments

  • Screenshot 2022-06-06 at 23-42-06 LineageOS Downloads.png
    Screenshot 2022-06-06 at 23-42-06 LineageOS Downloads.png
    51.3 KB · Views: 51

Con89

Member
Jul 27, 2021
7
0
Hi! When I try to put the original ROM through Moto rescue and assist everything goes well but I have no cellhone network. Can anyone point me in the right direction to solve this please?
 

[email protected]

New member
Aug 10, 2022
2
0
Hello. I am hoping this is the correct place to ask this? Please bear with me as this is going to be a lengthy post.

I tried to unlock the bootloader on my Motorola G5S but it didn't work. I still get this error message when I turn on the phone:

Your device has failed verification and may not work properly.

To learn more, visit:
motorola.com/unlockbootloader

ID: N/A

Your device will boot in 5 seconds.

Note it doesn't boot in 5 seconds. It doesn't boot at all.

I tried the steps at the address given:

DEVICE ID AND UNLOCK KEY​

Now that you understand the risks associated with unlocking the bootloader, let’s get started!

First, we’ll need to get your device ready to get the device ID and unlock key. You’ll need to do a few things to get this.

  1. Install the Android SDK. You can download it here.
  2. Install the latest Motorola USB Drivers. Get them here.

Next, you will need to get your device ID.

TO GET YOUR DEVICE ID​

  1. Put your device in fastboot mode (press the power button and volume down button at the same time and connect your device to your computer with a USB cable).
  2. On your computer, open a command prompt or Terminal session.
  3. Go to the Directory where you installed the Android SDK tools, and type:$ fastboot oem get_unlock_data
  4. This fastboot command will return a character string. This is the Device ID which you will be using to generate your unique unlock key.

    Example Device ID (PC User)$ fastboot oem get_unlock_data
    (bootloader) 0A40040192024205#4C4D3556313230
    (bootloader) 30373731363031303332323239#BD00
    (bootloader) 8A672BA4746C2CE02328A2AC0C39F95
    (bootloader) 1A3E5#1F53280002000000000000000
    (bootloader) 0000000
    Example Device ID (Mac Users)INFO0A40040192024205#4C4D3556313230
    INFO30373731363031303332323239#BD00
    INFO8A672BA4746C2CE02328A2AC0C39F95
    INFO1A3E5#1F53280002000000000000000
    INFO0000000
  5. To generate your unlock code, you’ll need to paste together the 5 lines of output into one continuous string without "bootloader or info" or white spaces. Using the example above, the line you’d send us would be:
  6. 0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
  7. Copy the Device ID string, being sure there are no spaces, and paste it into the "Make Sure you Device Is Unlockable" field below. This will verify that your device can be unlocked.

MAKE SURE YOUR DEVICE IS UNLOCKABLE​

Paste the Device ID string into the field below to verify that your device is unlockable:

I got the email with the unique code to unlock the bootloader of your Motorola phone.

I had to use a slightly different command (.\fastboot). Here is the output of unlocking the bootloader:

PS C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot oem get_unlock_data
fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ fastboot oem get_unlock_data
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException


Suggestion [3,General]: The command fastboot was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\fastboot". See "get-help about_Command_Precedence" for more details.
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) 3A15980418526607#
(bootloader) 5A593332324D39443937004D6F746F2047200000#
(bootloader) 17C6E283DBADE567A7E51F140FE711B0469027F2#
(bootloader) 1D91D6BA000000000000000000000000
OKAY [ 0.018s]
finished. total time: 0.019s
PS C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot devices
fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ fastboot devices
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException


Suggestion [3,General]: The command fastboot was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\fastboot". See "get-help about_Command_Precedence" for more details.
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot devices
ZY322M9D97 fastboot
PS C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot oem unlock H5CHEA5N3JTQ7R2IOOSF
fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ fastboot oem unlock H5CHEA5N3JTQ7R2IOOSF
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException


Suggestion [3,General]: The command fastboot was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\fastboot". See "get-help about_Command_Precedence" for more details.
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot oem unlock H5CHEA5N3JTQ7R2IOOSF
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.006s]
finished. total time: 0.007s
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot oem unlock H5CHEA5N3JTQ7R2IOOSF
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.006s]
finished. total time: 0.008s
PS C:\Program Files (x86)\Minimal ADB and Fastboot>

For some reason typing just fastboot throws up an error. Not sure why. But when I add .\ in front of it, it works.

I cannot check 'Allow OEM Unlock' in Android Settings > Developer as the phone won't boot. But I'm pretty sure (99%) that I had that turned on the last time I used the phone. (Its been sitting in a drawer for several years).

This is what it displays once I pasted my Device ID string

You should have received an email with your Unlock Key. If you did not, check you spam folder. Inside the email is a UNIQUE_KEY, a 20-character alphanumeric code that you will use to unlock your device.

Unlock your device​

  1. Turn off your device.
  2. Start your device in fastboot mode. To do this on most Motorola devices, push and hold the power and volume down at the same time, release the power button then release volume down. The device will power up in fastboot mode
  3. Connect the device to the computer with a USB cable. You'll get a confirmation message on the device will indicate that it's connected.
  4. Open a command window or terminal on your computer.
  5. Change field to show the path to the tools folder within the Android SDK folder.
  6. Verify that the desktop and device are connected by entering the following in the command field:$ fastboot devicesYou should see that your device is connected.
  7. Now you will unlock the bootloader. Simply enter the following in the command line:$ fastboot oem unlock UNIQUE_KEYThe UNIQUE_KEY is the code you received in the email. It is case-sensitive.
  8. If the line was entered correctly, your device's screen will confirm that your device is unlocked. You have just unlocked your device's bootloader.
  9. After a device is successfully unlocked, it will reboot and when it starts again you will see the screen below.
unlockedbootloader_320.png


It didn't confirm that my device is unlocked. And this screen didn't appear. And it didn't reboot. So should I run the command again? Will that brick the phone?

So now I am thinking I should install a custom ROM to override the default OS provided by Motorola.

Is there any chance of recovering this phone?

Note it doesn't show up in Windows Explorer at all. Well not completely. It shows up as J: drive but I cannot access it. I think due to it being OEM locked?

One more thing. I have installed adb fastboot on my PC from the instructions here:


I checked the logs on the phone and I think it completed the unlock successfully? I'm not certain though.
 

Attachments

  • IMG20220810135742.jpg
    IMG20220810135742.jpg
    1.7 MB · Views: 23
Last edited:

ZenurikSD

Member
Jun 16, 2022
5
1
Moto G5S
Don't mean to sound pushy or arrogant but are we still going to see changes for this? I see the system notifying about new updates but there's no changelog anywhere AFAIK.

I'm asking because I'm having severe battery drain issues with this ROM and I want to know if this is still being supported.
 

Korin67

Senior Member
Feb 24, 2018
249
112
I also noticed the same issue. What I am testing is adjust:
Battery -> Battery saver and performance -> Performance profile: Efficiency. In default the selections is in the middle. I am testing one level lower. It says power saving at the cost of higher latency.
Yes, if the battery drain would be reduced this ROM is perfect.
 

ZenurikSD

Member
Jun 16, 2022
5
1
Moto G5S
I also noticed the same issue. What I am testing is adjust:
Battery -> Battery saver and performance -> Performance profile: Efficiency. In default the selections is in the middle. I am testing one level lower. It says power saving at the cost of higher latency.
Yes, if the battery drain would be reduced this ROM is perfect.

Yeah, the performance profiles made basically no difference here. If I it leave it on at ~30% over the night, sometimes I wake up with it turned off completely drained.
Reboots also take out huge chunks of battery (only visually apparently), and I'm afraid it's decalibrating and draining battery cycles / reducing the lifespan. It's really bad.
 
  • Like
Reactions: Korin67

Korin67

Senior Member
Feb 24, 2018
249
112
I suspect that the ROM does not go into deep sleep when idling. Waiting for the OP's comment.

Edit: So far, to avoid battery drain issue, the only way is to downgrade to LOS15.1 (I have not tried LOS16.0 yet). LOS15.1 works perfect, battery lasts more than three days for light users like me.
 
Last edited:

LucasBonald

New member
May 8, 2018
1
0
Hello everyone! I installed the Rom yesterday in my montana, but I've been facing problems in my calls. I can't hear anyone and they can't hear me. Is the only issue that I observed. Is anyone could help me with this? Thank you very much!
 
Feb 18, 2019
53
4
I unlocked bootloader, flashed recovery
PHP:
lineage-18.1-20221003-recovery-montana

flashed with recovery adb the
Code:
flashed the lineage-18.1-20221003-nightly-montana with result "Total xfer: 1.00x"
with result “Total xfer: 1.00x”

After reboot, the lineage boot animation dots are moving to the left side in endless loop.

Repeated the steps multiple times without any luck.

Is anyone could help me with this? Thank you very much! What's missing?
 
Last edited:

mri0

Member
Aug 1, 2018
14
3
Hello everyone! I might give this ROM a try. On my Moto G5 lineageos-18 also by @JarlPenguin works like a charme. Before install I would like to know if everyone is having the battery drain issue with the current version or only a few people? Thank you.

Edit: 2nd question: Is anyone running the other kernel? What are the experiences with it?
 
Last edited:

Juno1337

Senior Member
Jan 17, 2014
64
19
Moto G5S
Xiaomi Poco X3 NFC
Hello everyone! I might give this ROM a try. On my Moto G5 lineageos-18 also by @JarlPenguin works like a charme. Before install I would like to know if everyone is having the battery drain issue with the current version or only a few people? Thank you.

Edit: 2nd question: Is anyone running the other kernel? What are the experiences with it?
No battery drain issue, however, be aware that this phone runs A11 very poorly. It can get very slow at times. Honestly the g5s shouldn't be upgraded past A10 as that is the last android version that it can run at an acceptable speed. Unless you really want as recent of a version as possible I suggest sticking with A10.
 
  • Like
Reactions: rillrill

rillrill

Senior Member
Nov 2, 2013
52
7
OnePlus 5T
Installed lineage-18.1-20230101-nightly-montana-signed a couple weeks ago.
Performance is not that great but okay for me. Wi-Fi connection drops once in while and i have to reconnect manually. Overall i still think its 100x better than on stock.

Thank you for your work, JarlPenguin! Can't wait for the next nightly!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    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:
    5
    Next build will have improved boot speed.
    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.