Yes
Current kernels aren't suited for newer builds yet
As soon as the "new format" aka SAR is finished and working just as fine as older builds, SAR Versions will probably be made
[ROM][UNOFFICIAL][montana][9.0.0_r46] LineageOS 16.0
- Thread starter JarlPenguin
- Start date
Current kernels aren't suited for newer builds yet
As soon as the "new format" aka SAR is finished and working just as fine as older builds, SAR Versions will probably be made
Ramdisk is not included in boot images of system-as-root builds, it was moved to /system
Hence the name system-as-root, before ramdisk in boot image was mounted at root, but now system has ramdisk and is mounted as root. This is why actual Android system path in SAR is /system/system (depending on mount point). Boot image only has kernel.
Last edited:
https://build.twrp.me/twrp-3.4.0-0-montana.img - should fix most issues, forceencrypt disabler (if flashed) should always be flashed last after ROM and add-on flashing. GApps seems to persist, not definitely tested yet. Feedback appreciated.
Clean flash instructions:
Boot TWRP
Format system, data, vendor, cache, dalvik
Reboot to recovery
Flash LOS zip
Reboot to recovery
Flash any add-ons (if you want to)
Flash forceencrypt disabler (if you want to)
In order to get GApps to persist across dirty flashes (warning: not tested, probably only needs to be done once if you already had LOS installed before, if clean flashing this shouldn't be needed)
Boot to TWRP on existing SAR build with GApps installed
Dirty flash LOS SAR
Flash OpenGApps
Reboot to device
See if OpenGApps is there
Reboot to TWRP
Dirty flash LOS SAR
Reboot to device
--> GApps should still be there.
Update: GApps indeed does persist across dirty flashes. Please use the linked build.
Also, for anyone curious, a reboot to TWRP is required after flashing LOS in a clean flash to flash other add-ons so that TWRP can apply needed changes after recognizing the system as Android 9 SAR (since before flashing system partition is empty and therefore detection of installed system is impossible).
Clean flash instructions:
Boot TWRP
Format system, data, vendor, cache, dalvik
Reboot to recovery
Flash LOS zip
Reboot to recovery
Flash any add-ons (if you want to)
Flash forceencrypt disabler (if you want to)
In order to get GApps to persist across dirty flashes (warning: not tested, probably only needs to be done once if you already had LOS installed before, if clean flashing this shouldn't be needed)
Boot to TWRP on existing SAR build with GApps installed
Dirty flash LOS SAR
Flash OpenGApps
Reboot to device
See if OpenGApps is there
Reboot to TWRP
Dirty flash LOS SAR
Reboot to device
--> GApps should still be there.
Update: GApps indeed does persist across dirty flashes. Please use the linked build.
Also, for anyone curious, a reboot to TWRP is required after flashing LOS in a clean flash to flash other add-ons so that TWRP can apply needed changes after recognizing the system as Android 9 SAR (since before flashing system partition is empty and therefore detection of installed system is impossible).
Last edited:
The updated image has been posted in the TWRP thread and website.
Last edited:
A new update is available (in case you haven't noticed). The changelog and downloads are in the OP, as always. Thanks for using this ROM.
Since this is the first stable release, I'd like to thank @karthick mostwanted and @wh0dat for the excellent trees, @wiktorek140 for helping me with the kernel, and last but not least @GivFNZ for testing the majority of my test builds.
Since this is the first stable release, I'd like to thank @karthick mostwanted and @wh0dat for the excellent trees, @wiktorek140 for helping me with the kernel, and last but not least @GivFNZ for testing the majority of my test builds.
SELinux: Enforcing ?
Edit : just dirty flashed it, apart from the same first boot that doesn't complete, all is fine ?
Edit : just dirty flashed it, apart from the same first boot that doesn't complete, all is fine ?
Last edited:
Samehere after clean install. I noticed it only happens when I hit 'yes' when asked for the secure start at the dialog setting a password.
Have you got bootloop or are you stuck on first boot ?
It's not the same.
For a reason I do not know, SAR builds cannot complete first boot properly after clean flash, you need to force a reboot in order to use it. Bur after it works very well.
It's not the same.
For a reason I do not know, SAR builds cannot complete first boot properly after clean flash, you need to force a reboot in order to use it. Bur after it works very well.
I'm stuck on my first boot.
I already try to force a reboot multiple time but still stuck my device won't boot.
How can I check my version ?
My device come from France it's maybe a XT1793 or XT1794 I know these versions come from Europe.
I used the last TWRP 3.4.0.1
Hello, unfortunately this issue is quite hard to debug, so if you can assist me by providing logcats, that would be helpful. It would also help if you could figure out if the problem disappears after forcing SELinux into permissive mode.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
23
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, official TWRP (3.4.0 and newer) and GApps (if you need them)
- Flash the downloaded TWRP via fastboot
- Boot to recovery
- Format system, vendor, data, cache, and dalvik cache
- Reboot to recovery
- Flash the latest build
- Reboot to recovery
- Flash GApps and any other necessary add-ons
Note: Long first boot times are normal due to forced encryption. Please do not reboot your device when it is booting up the first time, instead wait patiently. If it takes more than 10 minutes to boot then please notify me here with a logcat.
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:
- Unofficial builds: GitHub
- Recovery: Official TWRP
- Google Apps: OpenGApps (nano package is advisable, but you definitely should avoid using stock/super packages)
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
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:
Source code:
- Common device tree: https://github.com/JarlPenguin/android_device_motorola_msm8937-common-1
- Device tree: https://github.com/JarlPenguin/android_device_motorola_montana
- Kernel: https://github.com/HyperTeam/android_kernel_motorola_msm8937
XDA:DevDB Information
LineageOS 16.0 for Moto G5S, ROM for the Moto G5S
Contributors
JarlPenguin, AsD Monio, wiktorek140, GivFNZ, karthick mostwanted, wh0dat, rajatgupta1998
Source Code: https://github.com/LineageOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Oreo
Based On: CyanogenMod/AOSP
Version Information
Status: Stable
Current Stable Version: 1.1
Stable Release Date: 2020-08-24
Current Beta Version: 1.0b3
Beta Release Date: 2019-03-15
Created 2019-03-15
Last Updated 2020-09-1811Hello,
New LineageOS 16.0 build avaiable here (https://sourceforge.net/projects/mo...16.0-20200502-UNOFFICIAL-montana.zip/download)
CHANGELOG:
- default kernel included (radium compatibility)
- fixed error in AudioFX
- April security patches
- Minor tweaks
- fixed "Internal error" on eva kernel
INSTALLATION:
- Make a backup
- flash rom zip via recovery
- Optional instalation step
- install additional mods (magisk, gapps, audio mod etc.)
- reboot to system
WARNING! First boot may take ~10 min!
ADDITIONALS:
- Prebuilded ProjektEva kernel here (https://sourceforge.net/projects/montana/files/3.18/ProjektEva/boot-projekteva-20200503.img/download - !!!MAGISK PREFLASHED!!!)
Optional instalation step:
- Install boot-projektEva-2020-05-02.img as image into BOOT partition9If anyone is wondering what happened, I've been really busy these past few weeks, so that is why no updates have been launched.
On the other hand, sneak peek into next update:
Fixed video recording in Snap, Moto Camera, etc. (Partly thanks to @AsD Monio)
Project Treble (Team effort of me and @AsD Monio)
Fixed time resetting on reboot
Updated lots of blobs
And more77Hello, everyone! I have good news! Wi-Fi is FIXED! Thanks a lot to @wiktorek140 (for reading & helping me with logs) and @GiovaniFNZ (for testing all of my builds) on Telegram. Now all that is left is fixing Moto Actions, which is pretty much a piece of cake.
