{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Wiki.
This post is for Nexus 9 (Wi-Fi) model.
See post #2 for Nexus 9 (LTE) model.
Important Info
The newest lineage 14.1 flounder (Wi-Fi) builds rely on proprietary vendor and firmware components from the N9F27M (October 2017) monthly update from google. This means your device needs to have the vendor and bootloader img from that update. They can be extracted from the factory image on google's site here. Or you can use the ones linked below that I already extracted:
* vendor-flounder-n9f27m.img
* bootloader-flounder-3.50.0.0143.img
The vendor img is flashable with twrp or fastboot, but for the bootloader img use fastboot.
More information and installation instructions can be found on the LineageOS wiki here.
Download Links
LineageOS: https://download.lineageos.org/flounder
LineageOS servers no longer make 14.1 builds for any devices. You can use my builds here. My older builds are here.
Google apps: http://opengapps.org/?arch=arm64&api=7.1&variant=nano (Use arm64 / 7.1)
su addon zip (for root): Install zip / Removal zip
NOTE#1: After su addon install, root is disabled by default. You can enable it in developer options.
NOTE#2: My unofficial builds do not force encrypt.
Weather Provider Addon (Optional)
For those that like the lineage cLock widget, here's the OpenWeather apk you need to get weather info.
https://mirrorbits.lineageos.org/WeatherProviders/OpenWeatherMapWeatherProvider.apk
Note: You'll need an api key from OpenWeather.
Stats
https://stats.lineageos.org/
Credits
Many thanks to the LineageOS team and all the contributors out there in the community :good:
Contributors
Hashbang173, razorloves
Source Code:
Device tree: https://www.github.com/LineageOS/android_device_htc_flounder/tree/cm-14.1
Kernel tree: https://www.github.com/LineageOS/android_kernel_htc_flounder/tree/cm-14.1
Vendor tree: https://github.com/TheMuppets/proprietary_vendor_htc/tree/cm-14.1
Android version: 7.1.2 Nougat
Kernel version: Linux 3.10.103
Status: Nightly
Reserved
This post is for Nexus 9 (LTE) model.
Important Info
The newest lineage 14.1 flounder_lte (LTE) builds rely on proprietary vendor and firmware components from the N4F27P (October 2017) monthly update from google. This means your device needs to have the vendor and bootloader img from that update. They can be extracted from the factory image on google's site here. Or you can use the ones linked below that I already extracted:
* vendor-flounder_lte-n4f27p.img
* bootloader-flounder_lte-3.50.0.0143.img
The vendor img is flashable with twrp or fastboot, but for the bootloader img use fastboot.
More information and installation instructions can be found on the LineageOS wiki here.
Download Links
LineageOS: https://download.lineageos.org/flounder_lte
LineageOS servers no longer make 14.1 builds for any devices. You can use my builds here. My older builds are here.
Google apps: http://opengapps.org/?arch=arm64&api=7.1&variant=nano (Use arm64 / 7.1)
su addon zip (for root): Install zip / Removal zip
NOTE#1: After su addon install, root is disabled by default. You can enable it in developer options.
NOTE#2: My unofficial builds do not force encrypt.
Weather Provider Addon (Optional)
For those that like the lineage cLock widget, here's the OpenWeather apk you need to get weather info.
https://mirrorbits.lineageos.org/WeatherProviders/OpenWeatherMapWeatherProvider.apk
Note: You'll need an api key from OpenWeather.
Stats
https://stats.lineageos.org/
Credits
Many thanks to the LineageOS team and all the contributors out there in the community :good:
Contributors
Hashbang173, razorloves
Source Code:
Main device tree: https://www.github.com/LineageOS/android_device_htc_flounder_lte/tree/cm-14.1
Inherited device tree: https://www.github.com/LineageOS/android_device_htc_flounder/tree/cm-14.1
Kernel tree: https://www.github.com/LineageOS/android_kernel_htc_flounder/tree/cm-14.1
Vendor tree: https://github.com/TheMuppets/proprietary_vendor_htc/tree/cm-14.1
Android version: 7.1.2 Nougat
Kernel version: Linux 3.10.103
Status: Nightly
Wooooh! It's here
Can Nexus9 (lte) use this rom? If flash this rom only can not use lte,i can accept it.
Yeah! This is great news!
Will definitely flash this rom on my laggy N9
Can I dirty flash from the unofficial builds or should I do a full wipe?
Will it work on the LTE version? I don't mind if LTE does not work as long as I can try out the ROM without getting boot loops.
hextence said:
Will it work on the LTE version? I don't mind if LTE does not work as long as I can try out the ROM without getting boot loops.
Click to expand...
Click to collapse
I think so!
LTE version?
For people who need LTE
perfec
Is the Nexus 9 LTE going to have official support?
Sent from my iPhone using Tapatalk
Thank you very much! I hope it is less laggy than the stock firmware.
vendor image is critical at time of OS installation
Hi there.
First of all, thanks so much for the official N9 build for Lineage. Really appreciate it.
I wanted to describe my experience this morning. I should start by saying that I am *not* a hacker, just an enthusiastic user. I can follow instructions, and have been using non-stock ROMs since Cyanogen 7.
I was upgrading from the most recent version of Cyanogen. Before I started, I upgraded to the latest TWRP. Then when booting into recovery, found that my decryption passphrase didn't work. I downgraded version by version until twrp-3.0.2-0-flounder.img which is apparently the latest that worked. After installing Lineage OS, I upgraded to the newest TWRP again.
More importantly, I wanted to point out that by following the instructions on the Lineage OS wiki for the Nexus 9, I almost got to the point of thinking I had bricked my device.
The main reason is that the instructions don't mention the Vendor image issue at all: https://wiki.lineageos.org/devices/flounder/install
After wiping, installing Lineage OS and GApps pico, I rebooted. When it got to the decryption passphrase, I got the pop-up warning about the Vendor image being mismatched. No problem, I thought, as I've seen that before on Cyanogen installs. I put in my decryption passphrase. The screen remained unchanged for a couple of minutes, then I got something I'd never seen before. A page notifying me that my passphrase was correct, but the system was corrupt, and an option to fix it (no other option was available except to force power-off). So I took that option and it rebooted into TWRP. It boots into recovery and apparently runs a script and reboots the system again. But the same issue occurred again, nothing was fixed.
No problem, I thought, I'll just power-off, boot into the bootloader, enter recovery, and try again. Except that after installing Lineage, I found that volume-down+power button no longer started the bootloader!!! I tried many times, but the best I got was the device booting into the system and getting the same problem where it said the system is corrupt. It was at this point that I thought I had bricked the device - can't boot into system, can't get to the bootloader, so can't get to the recovery.
After many attempts, I tried one last thing:
Boot into system
On the corruption notification screen, I pressed the button to "fix" the system corruption
when the device rebooted into Recovery to run the script, instead of entering my passphrase, I hit cancel. This cancelled the script process but left me in recovery. I then selected reboot -> bootloader. Success!!
I was then able to connect the device to my laptop and copy the Vendor image I had extracted from the official Google system image using
Code:
fastboot flash vendor vendor.img
I then rebooted, and everything worked fine.
So it seems that in this instance, it may be critical to install the Vendor image before the first reboot. In earlier versions of Cyanogen when I had a vendor image mismatch it never prevented the device from booting and I was able to update it later on.
In which case, whoever has access to the wiki on the Lineage website - could you add those instructions in?
Just to add - I now seem to have bricked the device. Everything was working fine. I rooted the device using the supplied zip. It booted up fine. Now it won't reboot. It gets to the decryption passphrase field - verifies the password, continues to boot, and never finishes.
I can't get into the bootloader. Volume down+power doesn't work. Is there another way to do this?
Was using stock android on my Nexus 9. Already had root with the latest TWRP recovery installed. Did not run into any issues during the install(forgot to flash the Gapp at first, but could do it later in recovery, again no issues)
This is the first time I am using a Custom ROM. Got some questions .
1. I have the default apps for the lineage OS along with the same Gapps, How to remove the default lineage OS apps?
4. If anyone can share the advantages of the Nightly over custom ROM , it'll be great.
Other than these, no other major issues so far. will update the thread with the user experience
For anyone with LTE model please test this build. Let me know if there's any issues with lte or anything.
https://www.androidfilehost.com/?fid=889764386195906667
Here's the N4F27E vendor img for the LTE model, if you need it.
vendor-volantisg-n4f27e.img
thanks
No more testing needed. Results were good. Nightlies started for LTE model.
yhvo2gt9 said:
Just to add - I now seem to have bricked the device. Everything was working fine. I rooted the device using the supplied zip. It booted up fine. Now it won't reboot. It gets to the decryption passphrase field - verifies the password, continues to boot, and never finishes.
I can't get into the bootloader. Volume down+power doesn't work. Is there another way to do this?
Click to expand...
Click to collapse
Decryption passphrase in TWRP? Or Lineage?
---------- Post added at 04:51 PM ---------- Previous post was at 04:49 PM ----------
Just to let you all know, I got Lineage up and running, restored from my gmail account. I had stuck with 6.0.1 stock, 7 never cooperated, it was still getting laggy and what not. I will post more details about the install in a bit, but I just wanted to let any curious parties know this build seems to be working OK
Is the poor volume fixed in the official build or do we still need to flash a custom kernel to fix it?
I just flashed a minute ago. I've been waiting for this to be released. I switched over to Lineage on my OnePlus when it first came out. The nexus has been way too laggy on the latest stock releases. I hope this helps. I received a vendor image mismatch error on boot up but so far no issues. I'm going to flash gapps and will report back later. Thanks for working on this!!
The LTE one appears to be working fine in my tablet. Thank you
Sent from my iPhone using Tapatalk
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 9.0 (Pie) which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS GitHub repo and if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Official LineageOS website
Official LineageOS changelogs
Downloads Links
Latest Release
Google Applications (optional) :
OpenGapps (Use packages for ARM64, Android 9.0, Nano)
Information : Flash the GApps before the first boot. If not, a clean flash is recommended.
Flashing and updating
LineageOS clean install :
- Wipe dalvik, system, vendor, and data
- Flash this vendor image on both slots
- Flash the LineageOS ROM zip from the recovery in both slots
- Reboot
- (Optional) Flash a GApps package to have the Google Applications after first reboot
- (Optional) Every additional zip you want to flash
- Wipe the dalvik
- Reboot
LineageOS addonsu for root access :
- (Download) Download the addonsu for arm64
- (Optional) Flash the zip on a working Lineage installation (once)
- (Information) Upon ROM updates, the addonsu is preserved
- Reboot
About the builds
- Device Side Sources are here.
Issues and reports
- Report issues only if you use the ROM kernel
- If an additional mod is installed, make sure it's unrelated, and mention it
- Make sure the issue wasn't discussed earlier in the threads
- Share a log of the error
LineageOS available for PL2 also thanks to :
- Google AOSP
- The LineageOS Team
- CodeAurora Forums
- The CyanogenMod Team
XDA:DevDB Information
LineageOS-16.0, ROM for the Nokia 6 (2018)
Contributors
TheImpulson
Source Code: https://github.com/lineageos
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Pie Vendor
Version Information
Status: Stable
Current Stable Version: 16.0
Created 2019-02-08
Last Updated 2019-04-23
Information about build
Builds requires you to be on the latest Pie firmware/vendor. In case you are on Oreo and want to try this ROM, flash Stock Pie vendor on both slots first. You can download it here from my GDrive. This ROM uses prebuilt/non-opensource implementation and thus depends upon the vendor provided by OEM.
Reserved
Reserved
Thanks man!!
Will definitely try tomorrow!!
It is not flashing...i tried to flash via twrp in both slots but while rebooting it says that "no os installed" and when i try to boot into system...it's just gets stuck in bootloop..
Mad_maxx said:
It is not flashing...i tried to flash via twrp in both slots but while rebooting it says that "no os installed" and when i try to boot into system...it's just gets stuck in bootloop..
Click to expand...
Click to collapse
Same here. It is flashing "OK" in TWRP but upon reboot it says "No OS installed".
Hey guys,
I'm currently researching a way to upgrade my Nokia 6.1 TA-1054.
Right now the phone is on a "global" Nougat firmware which was preinstalled. I cannot receive updates and am hoping get to an up to date version.
Does anyone know whether it's possible to upgrade to the firmware of this thread, with Nougat as a starting point?
My approach would be to unlock the bootloader, boot into TWRP and install this ROM.
I'd be very thankful for any advice. Hopefully we can establish a process for other people stuck on TA-1054 to update their phones.
Cheers
Where is link???may I knows it
nooby_pls said:
Hey guys,
I'm currently researching a way to upgrade my Nokia 6.1 TA-1054.
Right now the phone is on a "global" Nougat firmware which was preinstalled. I cannot receive updates and am hoping get to an up to date version.
Does anyone know whether it's possible to upgrade to the firmware of this thread, with Nougat as a starting point?
My approach would be to unlock the bootloader, boot into TWRP and install this ROM.
I'd be very thankful for any advice. Hopefully we can establish a process for other people stuck on TA-1054 to update their phones.
Cheers
Click to expand...
Click to collapse
Whatever you do, please do not flash the official Android One ROM on TA-1054. The device will brick permanently with the official Pie update.
Sent from my Nokia 8.1 using XDA Labs
Good to see someone got something running/building for the device. I've got the TA-1043 and when needed I can try to help a bit. The Download link ends in a 404, so I guess no builds are available for download. I'm keeping an eye on this thread.
T_I said:
Good to see someone got something running/building for the device. I've got the TA-1043 and when needed I can try to help a bit. The Download link ends in a 404, so I guess no builds are available for download. I'm keeping an eye on this thread.
Click to expand...
Click to collapse
Updated links.
Great to see you managed to run Lineage on this Nokia! I will definitely try it out in some weeks.
Pushed a new build today!
Changelog:
-Fixed in-call audio
-Upstream Kernel
Is it really stable for daily use? Anyone tested? Thanks
Edit: If I flash lineageos and later want to revert to stock how to do it?
Windoors said:
Is it really stable for daily use? Anyone tested? Thanks
Edit: If I flash lineageos and later want to revert to stock how to do it?
Click to expand...
Click to collapse
It's stable and works great. I don't release untested builds.
For going back to stock again, you can backup before from TWRP, and restore later on.
Nokia 6.1 ROMs list
Hello. I installed the LineageOS 16 on my ta-1043, but i want to know if are there other Pie-based custom ROMs for Nokia 6.1 beside Lineage, aosp extended. Thanks!
I installed the image and after some issues (user error) I managed to get it running. However, I haven't solved all mistakes I made yet. Somehow I can'y seem to flash TWRP 3.2.3 official and Magisk and/or addonsu won't seem to stick. Looks like an issue with the slots. I'm trying a factory reset to see if that helps.
Edit: Got addon su working, flash when booting from slot B, switch slot to slot A, boot bootloader, fastboot boot twrp, install, switch back to B, install again and reboot. However, I didn't manage to flash twrp and Magisk. Ad soon as a patch on boot is done, it gets reset somehow. (and afterwards addon su is gone as well)
Edit 2: I had some issues with contact sync and setup. I had to manually find the apps for setup and contacts sync to give them the required permissions. After a reboot sync worked and android setup was able to finish.
TheImpulson said:
Pushed a new build today!
Changelog:
-Fixed in-call audio
-Upstream Kernel
Click to expand...
Click to collapse
I hope that you can become the official maintainer of this device.
---------- Post added at 06:17 AM ---------- Previous post was at 06:14 AM ----------
TheImpulson said:
It's stable and works great. I don't release untested builds.
For going back to stock again, you can backup before from TWRP, and restore later on.
Click to expand...
Click to collapse
Why does Nokia have no official lineage OS?
Working like a charm. Thanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
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.
All the source code for LineageOS is available in the LineageOS GitHub. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the changelog for a full list of changes & features.
DISCLAIMER: LineageOS Legal
Requirement: Oneui 3.0 (DTL1).
Instructions:
Flash Lineage Recovery or grab the files from the download below and use the instruction from there to flash it
Format Data/Factory Reset
Flash the build (Use adb sideload, or push the file to sdcard with mtp)
Reboot
Notes:
VoLTE, IMS, and other samsung specific stock rom features wont be ported or fixed.
Download:
r5q 18.1
r5q recovery
Support Group: Telegram
Reporting Bugs
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:
I do this kind of stuff on my free time. If you like my work, please consider buying me a drink (donation) by clicking the link below.
Paypal
Archive link: Github Releases
Kernel source: Github
hell of a ride to install this. nearly impossible to make recovery work (its because oneui 3 update i read somewhere?? problems with booting in newly installed recovery after using odin....damn)
my steps to get a proper recovery and this build running
- installed samsung android 11 / oneui3
- patched boot.img and rooted the rom
- installed twrp manager app
- put the twrp img on handy, installed it via twrp manager app
- tataa twrp installed
- had problems to decrypt handy (fixed after i wiped internal storage only)
- installed lineageos via twrp
rom works good so far. all i need works. so i use it as my daily driver. thanks for your work
immerblind said:
hell of a ride to install this. nearly impossible to make recovery work (its because oneui 3 update i read somewhere?? problems with booting in newly installed recovery after using odin....damn)
my steps to get a proper recovery and this build running
- installed samsung android 11 / oneui3
- patched boot.img and rooted the rom
- installed twrp manager app
- put the twrp img on handy, installed it via twrp manager app
- tataa twrp installed
- had problems to decrypt handy (fixed after i wiped internal storage only)
- installed lineageos via twrp
rom works good so far. all i need works. so i use it as my daily driver. thanks for your work
Click to expand...
Click to collapse
I think i had to mention this, booting recovery now requires you to have usb plugged in while you're punching the recovery combo to enter recovery.
Also, i've fixed the lineage recovery yesterday, sorry for the hassle.
New release are up! New release have a new repo right here https://github.com/mainey/r5q-archive/releases , hopefully this would be less confusing for the end users to find files needed. The old repo would now only releases new vendor updates from samsung.
New build: https://github.com/mainey/r5q-archive/releases/tag/ROM-20210121
note: i might or might not announce new builds in the future all the time, if you want to be notified when releases are published, make sure to click the watch button on the top right on the github repo page
What's handy?
How did you patch boot.img and root the ROM?
Is there a how-to for noobs? I guess all my knowledge on how to flash custom ROMs from 2 years ago are completely useless after all.
Thanks!
immerblind said:
hell of a ride to install this. nearly impossible to make recovery work (its because oneui 3 update i read somewhere?? problems with booting in newly installed recovery after using odin....damn)
my steps to get a proper recovery and this build running
- installed samsung android 11 / oneui3
- patched boot.img and rooted the rom
- installed twrp manager app
- put the twrp img on handy, installed it via twrp manager app
- tataa twrp installed
- had problems to decrypt handy (fixed after i wiped internal storage only)
- installed lineageos via twrp
rom works good so far. all i need works. so i use it as my daily driver. thanks for your work
Click to expand...
Click to collapse
Ok, I found the instructions for patching boot.img:
[HOW-TO-ROOT] [G770F/DS] Galaxy S10 Lite International Model
Models: SM-G770F or SM-G770F/DS Frequently used key combinations keys: FORCE REBOOT: Hold "Volume Down" and "Bixby/Power" button. DOWNLOAD MODE: With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via...
forum.xda-developers.com
darth.cabs said:
What's handy?
How did you patch boot.img and root the ROM?
Is there a how-to for noobs? I guess all my knowledge on how to flash custom ROMs from 2 years ago are completely useless after all.
Thanks!
Click to expand...
Click to collapse
Got new account nice to be here too..
Vaughnn said:
我想我不得不提一下,启动恢复现在需要您在插入恢复组合以进入恢复时插入USB。
另外,我昨天修复了血统恢复,很抱歉给您带来麻烦。
Click to expand...
Click to collapse
Vaughnn said:
LineageOS是免费的,社区构建的Android 11售后固件发行版,旨在提高设备的现有Android的性能和可靠性。
LineageOS基于Android开源项目,并得到了Android社区中许多人的额外贡献。无需安装任何Google应用程序即可使用它。下面链接的是一个来自另一个Android项目的程序包,这些程序可以还原Google部件。LineageOS仍然包含各种特定于硬件的代码,无论如何它们也正在缓慢地开源。
LineageOS的所有源代码都在LineageOS GitHub中提供。如果您想为LineageOS做出贡献,请访问Gerrit Code Review。您还可以查看更改日志以获取更改和功能的完整列表。
要求: Oneui 3.0(DTL1)。
指示:
Flash Lineage Recovery或从下面的下载文件中获取文件,然后使用此处的说明对其进行刷新
格式化数据/恢复出厂设置
刷新构建(使用adb侧载,或使用mtp将文件推送到sdcard)
重启
笔记:
请勿使GAPP闪烁,这包括最小的GAPP。我将发布带有gapps的版本,直到gapps程序包足够适合我的需求为止。
VoLTE,IMS和其他三星特定的rom功能将不会移植或修复。
在使用指纹之后或之前,屏幕有时会闪烁,这只是免责声明,如果有人使用此版本的癫痫病患者,我将不承担任何责任
错误:
接近度(可能无法在某些应用程序上运行)
5Ghz热点
下载:
r5q 18.1
r5q恢复
支持小组: 电报
报告错误
如果您正在运行自定义内核或已安装Xposed,请不要报告错误
问题发生后立即拿起logcat。(除非您知道自己在做什么,否则请至少包括日志的几页,而不仅仅是最后几行。)
如果是随机重新引导,请抓住/ proc / last_kmsg。(除非您在重新启动之前就可以获取它,否则不要费心获取一个logcat。重新启动之后的logcat是没有用的)
如果从根shell运行“ setenforce 0”后问题消失了,请抓住/data/misc/audit/audit.log
Code:
您的-
LineageOS版本:
LineageOS下载网址:
Gapps版本:
你是否 -
擦拭:
使用钛备份还原:
出现问题后重新启动:
你正在用吗 -
任务杀手:
非库存内核:
其他修改:
根据需要提供任何其他信息(观察/问题发生的频率/它工作的最新版本/等):[/ CODE]
[B]我会在业余时间做这种事情。如果您喜欢我的工作,请考虑通过单击下面的链接为我买一杯饮料(捐赠)。[/B]
[URL='https://www.paypal.com/donate/?cmd=_donations&[email protected]']贝宝[/URL]
存档链接:[URL='https://github.com/mainey/release-r5q/releases']Github版本[/URL]
内核来源:[URL='https://github.com/mainey/android_kernel_samsung_r5q']Github[/URL]
[/QUOTE]
Hello, I would like to ask how my phone is currently Android 10 and One ui is 2.1. I want to change to LineageOS.
[/QUOTE]
Click to expand...
Click to collapse
immerblind said:
hell of a ride to install this. nearly impossible to make recovery work (its because oneui 3 update i read somewhere?? problems with booting in newly installed recovery after using odin....damn)
my steps to get a proper recovery and this build running
- installed samsung android 11 / oneui3
- patched boot.img and rooted the rom
- installed twrp manager app
- put the twrp img on handy, installed it via twrp manager app
- tataa twrp installed
- had problems to decrypt handy (fixed after i wiped internal storage only)
- installed lineageos via twrp
rom works good so far. all i need works. so i use it as my daily driver. thanks for your work
Click to expand...
Click to collapse
Hello, I would like to ask how my phone is currently Android 10 and One ui is 2.1. I want to change to LineageOS.
Rom is fine. There's simply not much to tell about. It runs runs runs. No problems at all. Twrp or lineageos recovery....whatever. all good
Would it be possible to have a version without Gapps?
Vaughnn said:
New release are up! New release have a new repo right here https://github.com/mainey/r5q-archive/releases , hopefully this would be less confusing for the end users to find files needed. The old repo would now only releases new vendor updates from samsung.
New build: https://github.com/mainey/r5q-archive/releases/tag/ROM-20210121
note: i might or might not announce new builds in the future all the time, if you want to be notified when releases are published, make sure to click the watch button on the top right on the github repo page
Click to expand...
Click to collapse
Is your lineageos 19 beta google-free?
Hi. Can anyone confirm if [BETA] Lineage 19 20220307 Beta 4 is stable enough as daily ROM?
Banking apps work? OIS+EIS during video recording?
Thank you.
Vaughnn said:
Requirement: Oneui 3.0 (DTL1).
Instructions:
Flash Lineage Recovery or grab the files from the download below and use the instruction from there to flash it
Format Data/Factory Reset
Flash the build (Use adb sideload, or push the file to sdcard with mtp)
Reboot
Click to expand...
Click to collapse
First of all thank you for your time and energy.
I'm having problem flashing latest beta 4.
I'm coming android 11 Oneui 3.1. My device is was rooted with unlocked bootloader.
1. I've flashed the lineage recovery via odin (Including vbmeta_disable) and upon reboot (it needed 2 boots to get into recovery) I chose factory reset of the device.
2. I've enabled developer options and saw my bootloader was unlocked.
3. I've booted into recovery
4. I've flashed the lienage os 19 beta 4 with google apps
I keep getting status error 2 and installation is aborted :O(
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
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.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Introduction
This is the official Lineage OS thread for the Motorola Moto X4, codename payton.
We support all the T-Mobile, International, and Project Fi variants, as their bootloaders are unlockable, while we can't support the Verizon and AT&T variants, as their bootloaders are permanently locked.
How to install via Lineage Recovery
Please follow the official instructions
Install LineageOS on payton | LineageOS Wiki
wiki.lineageos.org
HOW TO UPDATE LINEAGEOS WITH LINEAGE RECOVERY
Please follow the official LineageOS Wiki instructions for our device
Update LineageOS on payton | LineageOS Wiki
wiki.lineageos.org
How to install via TWRP
Boot the newest TWRP .img from the Official TWRP Project Site.
IF YOU ARE COMING FROM STOCK AND WANT TO INSTALL CUSTOM ROMS FOR FIRST TIME, INSTALL "Copy Partitions Zip" FROM POST #2
In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
ADB sideload the newest weekly
(Optionally) You can flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though the pre-installed Lineage Recovery instance will do everything you need it to in most cases. We don't recommend or support the use of the TWRP installer, as it is overwritten on every update (will need to be re-installed every update), and has no addon.d-v2 persistence.
Click "Reboot", then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps
Reboot
How to upgrade from 17.1 via Lineage Recovery
Please follow the official instructions
Upgrade LineageOS on payton | LineageOS Wiki
wiki.lineageos.org
How to upgrade from 17.1 via TWRP
Boot the newest TWRP .img from the Official TWRP Project Site.
IF YOU ARE COMING FROM STOCK AND WANT TO INSTALL CUSTOM ROMS FOR FIRST TIME, INSTALL "Copy Partitions Zip" FROM POST #2
In TWRP, click "Wipe", then select "advanced" and select "cache" and wipe.
ADB sideload the newest weekly build or copy it to your device and install the zip
(Optionally) You can flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though the pre-installed Lineage Recovery instance will do everything you need it to in most cases. We don't recommend or support the use of the TWRP installer, as it is overwritten on every update (will need to be re-installed every update), and has no addon.d-v2 persistence.
Click "Reboot", then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps
Reboot
Notes
Official Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status. (Magisk works fine, though is not supported.)
Official Lineage OS builds ship with full treble compatibility, with VNDK runtime enforcement! This means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run any GSI (yes, even Pie!) without need for hacks or additional flashable zips. We relabeled /oem as /vendor (as /oem isn't used in custom ROM's anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image. Please don't report GSI bugs here, report them instead to the GSI's maker.
Download
Official:
LineageOS Downloads
download.lineageos.org
Unofficial test builds:
https://osdn.net/projects/lineageos-for-payton/releases/p17369
Google Apps (GApps)
MindTheGapps:
Codefire - Listing of gapps
GCam Mods
Wichaya GCam APKs - Google Camera Port
Modified Google Camera app by Wichaya.
www.celsoazevedo.com
XDA:DevDB Information
Lineage OS 18.1, ROM for the Moto X4
Contributors
erfanoabdi, ThE_MarD, Lineage Team
Source Code: https://github.com/LineageOS
ROM Firmware Required: Official Pie
Important extra links
Payton Stock firmware:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Copy partitions link for download can be found on the LineageOS Wiki install instructions for Payton page here:
Install LineageOS on payton | LineageOS Wiki
wiki.lineageos.org
Heyyo, a new test build is up! The link can be found on the first post under the unofficial test builds link. lineage-18.1-20210119-UNOFFICIAL-payton contains some audio tweaks for echo-reference, speaker volume boost as well, so please test all voice call and audio recording functions.
ThE_MarD said:
Heyyo, a new test build is up! The link can be found on the first post under the unofficial test builds link. lineage-18.1-20210119-UNOFFICIAL-payton contains some audio tweaks for echo-reference, speaker volume boost as well, so please test all voice call and audio recording functions.
Click to expand...
Click to collapse
For wifi display we can update wfd from caf
Seems works on other roms
Heyyo @dhinesh_cool , the CAF blobs you are referring to are from Board Support Packages, which do not have any transferrable rights as it isn't publicly available like a stock ROM for a device.
LineageOS does not allow blobs from BSP because of that, to avoid any potential legal issues.
So hopefully another solution presents itself... Or if we're lucky? A better solution replaces Miracast
ThE_MarD said:
Heyyo @dhinesh_cool , the CAF blobs you are referring to are from Board Support Packages, which do not have any transferrable rights as it isn't publicly available like a stock ROM for a device.
LineageOS does not allow blobs from BSP because of that, to avoid any potential legal issues.
So hopefully another solution presents itself... Or if we're lucky? A better solution replaces Miracast
Click to expand...
Click to collapse
Ahh that bad
Another question is offline charging works?
Offline charging works, but the animation is broken.
Edit: Is the selinux permessive?
@dhinesh_cool oh snap, offline charging animation is broken lol... We will have to check into that then.
@Sujanth the test builds I released are selinux enforcing. I did just try testing with permissive and it still failed, so the issue lies elsewhere... I'll try some stuff and see what we need to do to solve it
Ok. I played cod and scwitch to telelgram. Then I switch back to cod. But the game loads from the beginning. In other rom it doesn't happen. I think the ram management could be impoved.
Heyyo, another test build is going up! The upload should be done within 30 minutes of this post and link to test builds are in the first post. lineage-18.1-20210202-UNOFFICIAL-payton contains fixes for the offline charging animation and for WiFi hotspot with WPA2 (it isn't merged yet on LineageOS, but hopefully it does before we go official on 18.1).
There is also some echo-reference changes so if someone could please test it with VoIP apps and see if there's still echo or not
Audio from front facing video is working?
ThE_MarD said:
Heyyo, another test build is going up! The upload should be done within 30 minutes of this post and link to test builds are in the first post. lineage-18.1-20210202-UNOFFICIAL-payton contains fixes for the offline charging animation and for WiFi hotspot with WPA2 (it isn't merged yet on LineageOS, but hopefully it does before we go official on 18.1).
There is also some echo-reference changes so if someone could please test it with VoIP apps and see if there's still echo or not
Click to expand...
Click to collapse
Offline charging is working now. Thanks.I am testing the other fixes and write then back.
Edit: Hotspot with WPA2 also works with 2,4 GHz band. But with 5.0gHz band i can't find the hotspot. Need any logs?
I did also a whatsapp call, no echo or mic problems.
But volume of the speaker is low. Can you fix it?
And radio FM doesn't work.
When I want to call somebody, the telephone screen is not coming, but you hear the call tone.
How to upgrade to this ROM from Lineage 17.1? Thanks.
Heyyo @derienardani , yes that was fixed on 18.1 like it was on 17.1.
@Sujanth , WiFi Hotspot WPA2 on 5GHz works fine for me, albeit there's more changes coming to it so I'm unsure yet what will be the final form of it... I'll post a new build when it changes again.
As for speaker volume? It was increased from 32 to 34 and no plans to go higher as some users said at 36 they get distortion.
FM Radio is a known bug that we are still looking into.
For the telephone bug? Please ensure you have a default phone app selected
@artu72 the upgrade instructions for 18.1 are the same as 17.1 except for GApps MindTheGapps is the recommended one to use either addon-v2 or v3 is fine.
MindTheGapps - Google Drive
Heyyo, a new test build is going up! As always it is in the first post and is uploading meow so it'll be about 30 minutes. lineage-18.1-20210211-UNOFFICIAL-payton contains some perf fixes so that cpufreq also properly scales up and down.
ThE_MarD said:
Heyyo @derienardani , yes that was fixed on 18.1 like it was on 17.1.
@Sujanth , WiFi Hotspot WPA2 on 5GHz works fine for me, albeit there's more changes coming to it so I'm unsure yet what will be the final form of it... I'll post a new build when it changes again.
As for speaker volume? It was increased from 32 to 34 and no plans to go higher as some users said at 36 they get distortion.
FM Radio is a known bug that we are still looking into.
For the telephone bug? Please ensure you have a default phone app selected
@artu72 the upgrade instructions for 18.1 are the same as 17.1 except for GApps MindTheGapps is the recommended one to use either addon-v2 or v3 is fine.
MindTheGapps - Google Drive
Click to expand...
Click to collapse
I haven't installed any other phone apps. So i don't think I need to select it. Same bug also present in corvus a11.
Hi, first time using Lineage OS here. After sideloading LineageOS, i am just not able to install Gapps. Tried using MindtheGapps 11, tried sideloading, flashing, nothing happened. Either the phone starts to bootloop or it boots to recovery or it boots to Lineage OS without any google apps. Can someone please tell me where i am going wrong?
Edit: I realised i was flashing the wrong GApps, so i tried flashing ARM64 Android 10 nano pack. The screen gets stuck at the LOS boot logo before booting back to TWRP.
SOS
Heyyo @warhead1721972 , please ensure you are following the instructions. After flashing LineageOS ROM, you must reboot to recovery and then flash GApps.
A/B devices are different than traditional A-only devices as the ROM is always flashed to the inactive slot (IE, if A is active, the ROM will be flashed to B) so after the ROM flashes successfully it tells the bootloader that next reboot to switch slots. The reboot to recovery then switches to that slot (in our example, it switches to B) so that we can flash GApps on top of the newly flashed ROM.
Installing updates via the LineageOS Updater does use addon.d scripts to keep the installed GApps, but any manual flashing of ROM (either first time or manually upgrading) requires manually rebooting to recovery and flashing GApps as it does not use addon.d scripts.
ThE_MarD said:
Heyyo @warhead1721972 , please ensure you are following the instructions. After flashing LineageOS ROM, you must reboot to recovery and then flash GApps.
A/B devices are different than traditional A-only devices as the ROM is always flashed to the inactive slot (IE, if A is active, the ROM will be flashed to B) so after the ROM flashes successfully it tells the bootloader that next reboot to switch slots. The reboot to recovery then switches to that slot (in our example, it switches to B) so that we can flash GApps on top of the newly flashed ROM.
Installing updates via the LineageOS Updater does use addon.d scripts to keep the installed GApps, but any manual flashing of ROM (either first time or manually upgrading) requires manually rebooting to recovery and flashing GApps as it does not use addon.d scripts.
Click to expand...
Click to collapse
First i sideload the rom zip in slot A along with TWRP and then i reboot to the recovery to set the current slot to B and then flash GApps. On flashing it, there are no errors, but on booting up the system for the first time, i get redirected to TWRP. Is something wrong with my phone?
Till now i have been using ViperOS for quite some time, until i wanted to try something new. Really wanna give LOS a try.
@warhead1721972 , just to check since you're using TWRP, when you switched ROMs are you wiping Dalvik, cache, data and system?
Also, are you reinstalling TWRP after flashing LOS? Because if you are, you must use the TWRP installer zip and not flash the TWRP image as that kernel isn't compatible with the ROM.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
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.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Introduction
This is the official Lineage OS thread for the Motorola Moto X4, codename payton.
We support all the T-Mobile, International, and Project Fi variants, as their bootloaders are unlockable, while we can't support the Verizon and AT&T variants, as their bootloaders are permanently locked.
How to install via Lineage Recovery
Please follow the official instructions
Install LineageOS on payton | LineageOS Wiki
wiki.lineageos.org
HOW TO UPDATE LINEAGEOS WITH LINEAGE RECOVERY
Please follow the official LineageOS Wiki instructions for our device
Update LineageOS on payton | LineageOS Wiki
wiki.lineageos.org
How to install via TWRP
Boot the newest TWRP .img from the Official TWRP Project Site.
IF YOU ARE COMING FROM STOCK AND WANT TO INSTALL CUSTOM ROMS FOR FIRST TIME, INSTALL "Copy Partitions Zip" FROM POST #2
In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
ADB sideload the newest weekly
(Optionally) You can flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though the pre-installed Lineage Recovery instance will do everything you need it to in most cases. We don't recommend or support the use of the TWRP installer, as it is overwritten on every update (will need to be re-installed every update), and has no addon.d-v2 persistence.
Click "Reboot", then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps
Reboot
How to upgrade from the previous version via Lineage Recovery
Please follow the official instructions
Upgrade LineageOS on payton | LineageOS Wiki
wiki.lineageos.org
How to upgrade from the previous version via TWRP
Boot the newest TWRP .img from the Official TWRP Project Site.
IF YOU ARE COMING FROM STOCK AND WANT TO INSTALL CUSTOM ROMS FOR FIRST TIME, INSTALL "Copy Partitions Zip" FROM POST #2
In TWRP, click "Wipe", then select "advanced" and select "cache" and wipe.
ADB sideload the newest weekly build or copy it to your device and install the zip
(Optionally) You can flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though the pre-installed Lineage Recovery instance will do everything you need it to in most cases. We don't recommend or support the use of the TWRP installer, as it is overwritten on every update (will need to be re-installed every update), and has no addon.d-v2 persistence.
Click "Reboot", then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps
Reboot
Notes
Official Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status. (Magisk works fine, though is not supported.)
Official Lineage OS builds ship with full treble compatibility, with VNDK runtime enforcement! This means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run any GSI (yes, even Pie!) without need for hacks or additional flashable zips. We relabeled /oem as /vendor (as /oem isn't used in custom ROM's anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image. Please don't report GSI bugs here, report them instead to the GSI's maker.
Download
Official:
LineageOS Downloads
download.lineageos.org
Unofficial test builds:
https://osdn.net/projects/lineageos-for-payton/releases/p17369
Google Apps (GApps)
MindTheGapps:
Codefire - Listing of gapps
GCam Mods
Wichaya GCam APKs - Google Camera Port
Modified Google Camera app by Wichaya.
www.celsoazevedo.com
Contributors
erfanoabdi, SevenRock, ThE_MarD, Moto sdm660 devs, the Lineage Team
Source Code: https://github.com/LineageOS
ROM Firmware Required: Official Pie
Important extra links
Payton Stock firmware:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Copy partitions link for download can be found on the LineageOS Wiki install instructions for Payton page here:
Install LineageOS on payton | LineageOS Wiki
wiki.lineageos.org
Heyyo, a new test build is going up! lineage-19.1-20220416-UNOFFICIAL-payton contains Moto Camera 2 app and fixes for offline charging as well
Release lineage-19.1 lineage-19.1-20220416-UNOFFICIAL-payton - lineageos-for-payton - OSDN
Release lineage-19.1 lineage-19.1-20220416-UNOFFICIAL-payton - lineageos-for-payton #osdn
osdn.net
VERY special thanks to SevenRock for doing the majority of the LOS 19.1 trees for Moto sdm660 and payton
I decided to take the plunge tonight, waste a few hours and try out the 20220416 test build. So far so good, though I'll grant you I've only had it running for a couple hours. The install going from 18.1 to 19.1 went smooth. I'm not sure if audio will end up a little weak when calling someone. When I did a Voice call from my google number to my phone number, and then played back the message, my voice sounded a bit weak vs the voice mail prompts. I need to try it with a real phone call and see if others think I sound weak.
Apps seem to be running fine so far, though I'm a fairly light user. The only issue I've seen is TWRP 3.5 seems to get stuck in a boot loop when rebooting to recovery from lineageOS 19.1 but didn't when rebooting from TWRP. My new laptop doesn't seem to like fastboot, so I need to try lineage recovery install from another computer and see if that fixes it. I know TWRP isn't officially supporting Android 12 yet, and suspect this isn't an issue with your build. This did prevent me from trying Magisk, so that will need to wait too.
Can't say I'm a fan of the new "Material You" theme. The new quick tiles are annoyingly large. I need to figure out how to get a sound toggle tile to work right. But again, those are general OS issues and nothing to do with the build you did!
I'll see how it fairs over the next couple days and let you know, but so far seems good. Thanks for the build!
I installed this rom but can't get Magisk installed. Anyone know how?
Heyyo guys, for TWRP please try my latest test build
[OFFICIAL&TESTS]TWRP for the Motorola Moto X4 (Payton)
#include /* * Your warranty is now void. * * I am 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...
forum.xda-developers.com
I installed the 16 Apr build Sun night using NikGapps 13 Apr stock (excluding Pixel Launcher since I'd had issues with it on the prev build) and the Fi add-on. Other than having to clear storage/cache for Conn Services and Fi, everything has been working really well. Setup was much smoother this time, MotoCam2 is really nice, and also no random reboots like on the 22 Mar build.
When upgrading from the 22 Mar to 16 Apr build though, I got a boot loop and had to clean install. I'd had the same issue in the past back when I used the unofficial 18.1. Is this a known issue? Official 18.1 builds never had this problem. I guess next time I'll first try disabling security unlock.
Btw, is this really 12.1 and not 12.0? The phone settings only indicate '12'. I used the 'S' gapps and not 'SL', fwiw. Thanks!
The 4/16 build has been running fine for me the last few days. I may need to decrypt to get a working recovery it seems. Other than that the couple things that look like they're missing from settings are:
I don't see anywhere to adjust the color palette. It's purely based on wallpaper derived colors. Sounds like stock 12 supports modifying, does lineageOS not? I really don't like having my colors dictated by the wallpaper.
Accesibility/Vibration & Haptic strength -- this menu has no haptic strength control despite the name. It'd be nice if it did. I know this has existed in at least some of the past ROMs, though can't recall if that was Havoc or LineageOS.
Otherwise bluetooth, wifi, calling, messaging all seem good as does interaction.
I also ended up using NikGapps 13 simply because that was what I had good luck with on 18.1.
I'm not sure about the bootloop jeremywh7 saw as I went directly from 18.1 to the 0416 19.1 build with a clean install. If there's another test build and once I get a recovery working, I can try doing a dirty flash for an upgrade. I know on 18.1 I was able to dirty flash w/o a problem.
So far so good but I haven't done extensive testing yet. I got Magisk working.
Nice
Heyyo @jeremywh7, LineageOS 19.1 is Android 12.1 so you must use Android 12.1 (12L) GApps which might be your bootloop issue.
The color palette is indeed picked by the wallpaper which is annoying... It thinks my background of my family should mean my color is a skin-colored pink... oof lol
ThE_MarD said:
The color palette is indeed picked by the wallpaper which is annoying... It thinks my background of my family should mean my color is a skin-colored pink... oof lol
Click to expand...
Click to collapse
Yeah, I'd agree that's not a great choice on it's part! So I take it that for LineageOS 19.1 at least it's expected to have no control of this? I was under the impression that with stock Android 12 you could disable the automated picker and manually choose a color which I don't see in 19.1. If true that sounds like going with a 3rd party tool do do so
@ThE_MarD
Congrats!!! First official Lineage OS 19.1 payton build from the roaster
My question: Is it safe to dirty flash 19.1 as upgrade from an (last) official build of 18.1 (No GApps installed)? Wait for TWRP 3.6.1_11 or latest 3.6.1_9 is working for that?
Heyyo. Exciting times! First official build of LOS 19.1 for payton is up!
@jtnc, tbh no idea as I haven't really checked into the material you stuff lol...
@wkn000 you can upgrade without wiping data, please follow the instructions in the first post.
You can use the latest test build of TWRP or use Lineage Recovery
I did a factory reset and have flashed the first official build of LOS 19.1. I then immediately sideloaded NikGapps-core-arm64-12.1 before the first boot but I only got the LOS startup dialog, and there doesn't seem to be any Gapps.
I also tried the same proceedure but using MindTheGapps-12.1.0 (20220416), but no still no Gapps.
Are there any tricks for loading Gapps using adb and lineage recovery, or does this only work with TWRP.
WackyDoo said:
[...] I then immediately sideloaded NikGapps-core-arm64-12.1 before the first boot but I only got the LOS startup dialog, and there doesn't seem to be any Gapps.
Click to expand...
Click to collapse
Immediately, w/o a reboot? You have to reboot into recovery after flashing an A/B ROM (to switch to the newly flashed ROM - #6 in the install steps) before flashing Gapps/etc. ;-)
jeremywh7 said:
Immediately, w/o a reboot? You have to reboot into recovery after flashing an A/B ROM (to switch to the newly flashed ROM - #6 in the install steps) before flashing Gapps/etc. ;-)
Click to expand...
Click to collapse
I was following the upgrade instructions ( https://wiki.lineageos.org/devices/payton/upgrade ) since I was coming from the previous version of LineageOS?? The upgrade instructions specifically mention that we should not reboot before flashing extra addons like gapps.
I will try the install instructions linked in the OP later, skipping the unlocking and, I guess, not running the copy_partitions script since I already ran than with the previous ROM.
I followed the same instructions and got the same result coming from the previous lineage version. I went back into the lineage recovery, reflashed the GAPPS and rebooted. Had a little trouble signing into my Google account as the 2 step authentication notification struggled to come through on the phone. I got around this by setting myself up as another user rather than the "owner". Everything seems to be working OK except the bluetooth connection to my car. The phone is connected and contacts appear on the car dashboard along with the battery and signal strength indicators- but calls don't come through the car - only to the phone's own speaker and microphone.
I followed the instructions and it updated to 19.1 without issue. Now, though, about every 5 minutes or so I get a "popup" or whatever it's called that says "Intent Filter Verification Service keeps stopping". Somewhat annoying. If I "force stop" the Intent Filter Verification Service app, it stops doing it, obviously. But upon reboot it starts right back up again. I don't have any of the gapps installed, but I do have microg, unsure if that's related. Overall though, it works pretty well.
To avoid boot loops,
Keep in mind to reboot to recovery between each sideload
Sideload lineage 19
Reboot to recovery
Sideload gapps
Reboot to recovery
Sideload Magisk
Power Off
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
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.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Introduction
This is the official Lineage OS thread for the Motorola Moto X4, codename payton.
We support all the T-Mobile, International, and Project Fi variants, as their bootloaders are unlockable, while we can't support the Verizon and AT&T variants, as their bootloaders are permanently locked.
How to install via Lineage Recovery
Please follow the official instructions
Install LineageOS on payton | LineageOS Wiki
wiki.lineageos.org
HOW TO UPDATE LINEAGEOS WITH LINEAGE RECOVERY
Please follow the official LineageOS Wiki instructions for our device
Update LineageOS on payton | LineageOS Wiki
wiki.lineageos.org
How to install via TWRP
Boot the newest TWRP .img from the Official TWRP Project Site.
IF YOU ARE COMING FROM STOCK AND WANT TO INSTALL CUSTOM ROMS FOR FIRST TIME, INSTALL "Copy Partitions Zip" FROM POST #2
In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
ADB sideload the newest weekly
(Optionally) You can flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though the pre-installed Lineage Recovery instance will do everything you need it to in most cases. We don't recommend or support the use of the TWRP installer, as it is overwritten on every update (will need to be re-installed every update), and has no addon.d-v2 persistence.
Click "Reboot", then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps
Reboot
How to upgrade from the previous version via Lineage Recovery
Please follow the official instructions
Upgrade LineageOS on payton | LineageOS Wiki
wiki.lineageos.org
How to upgrade from the previous version via TWRP
Boot the newest TWRP .img from the Official TWRP Project Site.
IF YOU ARE COMING FROM STOCK AND WANT TO INSTALL CUSTOM ROMS FOR FIRST TIME, INSTALL "Copy Partitions Zip" FROM POST #2
In TWRP, click "Wipe", then select "advanced" and select "cache" and wipe.
ADB sideload the newest weekly build or copy it to your device and install the zip
(Optionally) You can flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though the pre-installed Lineage Recovery instance will do everything you need it to in most cases. We don't recommend or support the use of the TWRP installer, as it is overwritten on every update (will need to be re-installed every update), and has no addon.d-v2 persistence.
Click "Reboot", then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps
Reboot
Notes
Official Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status. (Magisk works fine, though is not supported.)
Official Lineage OS builds ship with full treble compatibility, with VNDK runtime enforcement! This means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run any GSI (yes, even Pie!) without need for hacks or additional flashable zips. We relabeled /oem as /vendor (as /oem isn't used in custom ROM's anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image. Please don't report GSI bugs here, report them instead to the GSI's maker.
Known Bugs
some users with Verizon and their MVNO's cannot send text messages
Download
Official builds:
LineageOS Downloads
download.lineageos.org
Unofficial test builds:
Package lineage-20 - lineageos-for-payton - OSDN
Package lineage-20 - lineageos-for-payton #osdn
osdn.net
Google Apps (GApps)
MindTheGapps:
Codefire - Listing of gapps
GCam Mods
Wichaya GCam APKs - Google Camera Port
Modified Google Camera app by Wichaya.
www.celsoazevedo.com
Developer Resources
GitHub - LineageOS/android_device_motorola_payton
Contribute to LineageOS/android_device_motorola_payton development by creating an account on GitHub.
github.com
GitHub - LineageOS/android_device_motorola_sdm660-common
Contribute to LineageOS/android_device_motorola_sdm660-common development by creating an account on GitHub.
github.com
GitHub - LineageOS/android_kernel_motorola_msm8998
Contribute to LineageOS/android_kernel_motorola_msm8998 development by creating an account on GitHub.
github.com
Contributors
erfanoabdi, SevenRock, SyberHexen, ThE_MarD, Moto sdm660 devs, the Lineage Team
Source Code: https://github.com/LineageOS
ROM Firmware Required: Official Pie
Important extra links
Payton Stock firmware:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Copy partitions link for download can be found on the LineageOS Wiki install instructions for Payton page here:
Install LineageOS on payton | LineageOS Wiki
wiki.lineageos.org
Hi! Working properly.
In this release adaptive storage is perfect.
VoLTE working. Only battery consumption is slightly higher.
Did an upgrade install from last lineage 19 build, and seems to be working fine, so far. Cannot test phone calls, as it seems AT&T towers block this phone, and Consumer Cellular uses AT&T towers in my area.
I gave this a shot over the weekend. I had some initial problems on the first install, but tried a second clean install and things were generally stable. I was able to make calls, though didn't try receiving any. Apps seemed to work as expected (though I'm not a heavy user).
What I hadn't tried was any SMS messages until this morning. I received one and it promptly rebooted the phone. I then tried sending a text from my GVoice account to my phone SMS account and as soon as the phone tried to receive the message, it'd reboot. I gave it a quick try at getting a log of this happening, but failed. I've reverted back to 19.1 as this is my daily phone. I'll probably give it a try again this weekend and can try and get a log capture then.
I also upgraded to LOS20, no problems, also sending and receiving SMS works fine.
@ThE_MarD : You and your team did a good job! Thanks
I noticed one problem: I get a hint - "App updates are ready - Connect to a network to continue", but I'm already connected to wifi. No updates possible!
After a system reboot everything is ok I thought, but after some minutes "App-Updates....
Heyyo @woodpe , thanks man but it was definitely SevenRock who handled LOS 20 for payton I just did the builds and XDA threads heh I guess he'd rather do the hobby side and less the PR side
For that message, can you please send logcat and maybe a picture of what you're seeing? Which GApps did you use btw?
I use MindTheGaps13 arm64 from the link in the instructons. I hope logcat I did is ok (I'm an old guy(74) but I've never done one before)!
Attached you'll find the pictures and log.txt
Thanks
Sorry, can't attach log.txt (3,1 MB)
Solved, zipped the file!
Anyone else tried this on Verizon? And if SK, can you send SMS texts? On my reinstall it seems like everything is working fine other than sending a SMS. When I do that I get a message failed error, both with the aosp and google message apps. I can receive messages fine though. See screenshot or attached log.
I see messages about RCS not working I think in the log, not sure if this is related or not. 19.1 works fine.
One question: when I enable USB debugging in the Developer options it is disabled after a reboot.
Any solution possible?
This is my first post, so first a friendly hello to all.
I have the test build on my second X4 since today. The upgrade and the installation of MindTheGapps with the lineage recovery were without problems. Everything important to me seems to work: Phone calls, SMS, wifi, mobile data, GPS, bluetooth and NFC connection to my bike computers and to the "Teufel Boomster" with apt-x HD audio. I have not noticed any bugs or issues so far. USB debugging is still enabled even after a reboot.
A big thank you to all developers, I love my two X4 and hope they will be supported for a long time.
One question: will the next test builds and the first official build of LineageOS 20 be offered as an update or do I have to install them as an upgrade again?
@paukenschlag
I was able to upgrade from 17.1 to 18.1 and further to 19.1 now just by dirty flash zip from SD with TWRP. No GApps installed, Magisk had to be reinstalled. That's all for me.
I guess upgrade to 20 will be same way.
some bank apps will not work with public keys and not last security patch
security error UA599 R:4,5
wkn000 said:
@paukenschlag
I was able to upgrade from 17.1 to 18.1 and further to 19.1 now just by dirty flash zip from SD with TWRP. No GApps installed, Magisk had to be reinstalled. That's all for me.
I guess upgrade to 20 will be same way.
Click to expand...
Click to collapse
I reinstalled the test build with the lineage recovery and a factory reset, this time without gapps - no problems.
Seems to work fine for me with MindTheGapps. Im using this version: MindTheGapps-13.0.0-arm64-20221025_100653
Noticed:
Changelog 27 - Thriving Thirteen, Amazing Aperture, Careful Commonization
X_X
lineageos.org
Heyyo, as @rseiler mentioned LineageOS 20 official is out and payton build is ready for download!
Downloaded, installed (with twrp-3.6.2_11-0-payton, encryption disabled), restored Magisk and MicroG and... IT WORKS!!!
Many thanks to all maintainers (represented by ThE_MarD here) of this new build version, well done!
Installed the official build on both my paytons, each with lineage recovery, one with MindTheGapps, one without. No problems with the installation, everything seems to work. Thanks to all!