{
"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"
}
Moto Z2 Force
Code:
- Your warrenty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the official Lineage OS thread for the Motorola Moto Z2 Force, codename nash.
We support both the Sprint, International, and T-Mobile 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:
Necessary Base Firmware: 8.0.0 (OCSX27.1.2, May 2018) (for TMO, or equivalent security patches for other variants)
Boot the newest TWRP .img from the Official TWRP Project Site.
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 ot 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 - MindTheGApps arm64 are recommended, OpenGApps are compatible with A/B as of 09102018, but I still only reccoemend and support MindTheGApps.
(Optionally) Flash SU - you'll need to turn it on from in developer settings after first boot Lineage OS SU Addon. - Magisk works fine, though is not supported.
Reboot
Known Problems:
Audio Mods don't work (this includes headphone jacks on mods) -- We can't fix this, don't use custom ROM's if you care about these.
Official Lineage OS builds will not ever allow Moto's Battery Mod "Efficiency Mode" to work -- though these can be made to work unofficially, join our discord if you're interested in this feature.
Wi-Fi Calling won't work until either the International or T-Mobile variant gets 8.1 blobs.
Ultrasonic Proximity Sensor doesn't work -- likely won't ever. It is used my Motorola's Active Display, but by nothing in Lineage.
Compass doesn't work -- no clue why.
Stock Display Color Profiles (the ones in Settings, "Display", "Colors") -- The ones in Settings, "Display", "LiveDisplay" work.
The default LiveDisplay "Natural" setting in Settings, "Display", "LiveDisplay", will occasionally dispaly color corruption, to deal with this, just swap to the "SRGB" profile, and swap back to "Natural", or leave it on "SRGB if you don't mind, then you won't experience those infrequent issues.
Notes:
Official Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status.
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:
LineageOS Updater
XDA:DevDB Information
[OFFICIAL] [WEEKLIES] [TREBLE] Lineage OS 15.1, ROM for the Moto Z2 Force
Contributors
npjohnson, invisiblek, erfanoabdi
Source Code: https://github.com/LineageOS
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: 8.0.0 (OCSX*)
Based On: LineageOS
Version Information
Status: Stable
Created 2018-07-15
Last Updated 2019-03-18
first (always wanted to do that)
thanks for this, nice work everyone!!!
Nice, I was wondering when we were going to get an official thread. I'll be waiting for the 17th to install the weekly.
I have the international version (-05) and have installed plenty of these version (since unofficial release from both invisiblek site and ods.ninja site) as well as the official weeklies (all versions already released) and everything works (based on the description here and known issues), so I'd say it's safe to say intl version had been tested and known to be working as well.
Let me know if you need additional/specific tests that I can do here.
Thanks the official post!
Also, how about volte support? Is it supposed to work?
felipevsw said:
I have the international version (-05) and have installed plenty of these version (since unofficial release from both invisiblek site and ods.ninja site) as well as the official weeklies (all versions already released) and everything works (based on the description here and known issues), so I'd say it's safe to say intl version had been tested and known to be working as well.
Let me know if you need additional/specific tests that I can do here.
Thanks the official post!
Also, how about volte support? Is it supposed to work?
Click to expand...
Click to collapse
If it isn't in the bugs list, its expected to work, it works on TMO and SPR. And I'll flag the international as compatible, thanks.
Since it isn't in known issues, I assume VoIP compression was fixed?
Edit: known workaround is use Bluetooth for video/VoIP calls. I don't know if USB audio would work or not.
Uzephi said:
Since it isn't in known issues, I assume VoIP compression was fixed?
Edit: known workaround is use Bluetooth for video/VoIP calls. I don't know if USB audio would work or not.
Click to expand...
Click to collapse
Added to OP as an issue.
??? for listing known accurate issues ???
I was pissed after installing Invictrix rom only to find out sound mods don't work.
I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.
fixed, can remove this.
DTHayakawa said:
I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.
Click to expand...
Click to collapse
Anything that uses VoIP compression is broken. Most video calling or internet calling apps in general use it.
DTHayakawa said:
I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.
Click to expand...
Click to collapse
1. Added to known bugs.
2. I don't experience this (and if it is present, its platform wide, and not our problem specifically).
3. I can't really easily support a prebuilt app all that easily. The B&W cam us supported in the default Snap camera.
Also, OTA will be broken until we figure out why signing server's aren't signing our payload zips right.
To work around this, you can update weekly by sideloading the nightly, rebooting to recovery (important), re-sideloading any mods you use (GApps, AddonSU, etc.).
fixed, can remove post now.
Uzephi said:
Anything that uses VoIP compression is broken. Most video calling or internet calling apps in general use it.
Click to expand...
Click to collapse
So I assume this would apply to hangouts and hangouts dialer?
npjohnson said:
Also, OTA will be broken until we figure out why signing server's aren't signing our payload zips right.
To work around this, you can update weekly by sideloading the nightly, rebooting to recovery (important), re-sideloading any mods you use (GApps, AddonSU, etc.).
Click to expand...
Click to collapse
Resolved.
Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?
MattKilla said:
Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?
Click to expand...
Click to collapse
I was literally plugging in to try this ROM until I read this. Have you tried Magisk yet?
Magisk Works
3's&7's said:
I was literally plugging in to try this ROM until I read this. Have you tried Magisk yet?
Click to expand...
Click to collapse
I have ran into this same issue when flashing build > lineage-15.1-20180721-nightly-nash-signed.zip
I can confirm that it happens with both TWRP 3.2.2-2 & TWRP 3.2.1-1
I flashed Magisk 16.4 and it works flawlessly no issues.
I am very happy with this ROM it works great for me. Thank You Devs! :good:
MattKilla said:
Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?
Click to expand...
Click to collapse
was TWRP installed or did you just boot to it?
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"
}
PixelExperience for Mi Max 2[OXYGEN]
What is this?
Pixel Experience is an AOSP/CAF based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device
Based on Android 9.0
Whats working?
Code:
[LIST]
[*]Wifi
[*]RIL
[*]Mobile data
[*]GPS
[*]Camera
[*]Flashlight
[*]Camcorder
[*]Bluetooth
[*]FMRadio
[*]Fingerprint Sensor
[*]Lights
[*]Sound / vibration
[*]Face unlock
[*]OTG
[/LIST]
Known issues
Code:
[LIST]
[*]Users facing in-call echo even now can follow [url=https://forum.xda-developers.com/showpost.php?p=79080851&postcount=67]this[/url]. And don't forget to thank for the post!
[*]In-call volume not adjustable
[*]Vendor Image mismatch can come up with some Magisk Module
[*]Screen Mirroring doesn't work
[/LIST]
-
DON'T FLASH GAPPS, ALREADY INCLUDED
Download from Google Drive
Donate to PEX Developer - jhenrique09
Liked my work? Give me a beer
Translation
Help with project translation
Telegram channel
Stay tuned
Flashing Instructions
Code:
[LIST=1]
[*]Download PixelExperience_oxygen-V.v-YYYYMMDD-HHMM-UNOFFICIAL.zip
[*]Formatting instructions:
-> [B]Existing Users:[/B] Wipe /system and /vendor partitions only
-> [B]Existing Users facing issues after installation:[/B] Wipe /system, /vendor, /cache and /dalvik or art partitions
-> [B]New User/Clean Installations:[/B] Wipe /data, /system, /vendor, /cache and /dalvik or art partitions
[*]Be sure to flash the latest Dev Firmware files (Please google them)
[*]Now flash the ROM.zip
[*]Optional Steps:
-> Flash Magisk 19.3 for root access
-> Flash the audio mods if needed (Link is provided below) - [B][COLOR="Red"]Instructions[/COLOR][/B]:
=> First flash the TWRP_Arise_Sound_System_Dolby_Atmos.zip package
=> Then flash Clear Soundmod (sangga).zip package, and you're good to go!
[*]Reboot
[/LIST]
Extras Download link:
Arise Mod(Note that the mod takes a few minutes to install): https://drive.google.com/open?id=1qV2b6PPKMgyil1OtGJ_JnM8us-p3cpVL
Magisk module to resolve "Magisk not installed" issue: Magiskd-Helper
Sources :
PixelExperience source code : https://github.com/PixelExperience/
Translation : https://translate.pixelexperience.org/
Telegram channel : https://t.me/PixelExperience
Contributors :
@Hard_Rock83
Source Code: https://github.com/rakeshraimca/Kernel_xiaomi_oxygen
XDA:DevDB Information
[9.0] Pixel Experience - Mi Max 2 (Oxygen) - 12-Jan-2019, ROM for the Xiaomi Mi Max 2
Contributors
V_v3k, Hard_Rock83
Source Code: https://github.com/PixelExperience/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 3
Stable Release Date: 2019-03-10
Created 2019-01-12
Last Updated 2019-03-10
Release Changelogs:
Jan-2019
Initial release
Everything works
Magisk Mods may cause vendor image issues.
Feb-2019
Buggy release
Mar-2019
Apr-2019
Jun-2019 - Current Release
Res2
Nice to see this ROM getting support as its quite good
Do you have any plans on making it official?
Based on hardrock latest sources or older sources?
What is the latest firmware dev, where do i get it from? What do you mean when you say ,,flash latest firmware dev first"?
SMS
I love this rom !!!
But I really need some help ... Please...
SMS - not working. for me (orenge - romania).
To test the above problem and to clarify if there is a problem from my network operator or PixelExperience, I flashed the ugly ROM MIUI Dev (12/27/2018) and updated last night to last dev build (09-01-2019).
Unfortunately, SMSs work with MIUI ...
On MIUI: * # * # 4636 # * # * - works correctly, and displays my SMSC number at refresh. (I also managed to see the number from SMSC in Havoc build 4, after I moved the SIM into Slot 1 but the SMSs were still not going to the destination. In Slot 1 I usually have SDCARD...)
I just flashed the latest version of Pixel and I have the same problem: SMS does not leave. I can receive, but I can not send.
I've already tried other apps: Textra and SMS Messeging(AOSP)
I have attached a logcat of sms sending time.
Can someone help me ...
thank you
PS.
Before installing MIUI, I tested with Arrow build 13 (10-01-2019) and Havoc OS build 4, clean flash (format: vendor, date, system, cash, dalvik, all...) and the problem persisted ...
mfd10000 said:
I love this rom !!!
But I really need some help ... Please...
SMS - not working. for me (orenge - romania).
Click to expand...
Click to collapse
I don't know what the issue is but it sounds similar to what I experienced on one of the other pie ROMs.
MMS working fine prior to upgrade but couldn't get it work on Pie.
It's almost like the phone isnt reading the APN type correctly.
Google Messages app was reporting the service as not available on the network, which is obviously incorrect, as it works perfectly again after rolling back to the previous ROM.
mfd10000 said:
I love this rom !!!
But I really need some help ... Please...
SMS - not working. for me (orange - romania).
..
Click to expand...
Click to collapse
Ok..
Strange...
I've managed to solve SMS sending by changing to "Settings-> Network & Internet-> Mobile network-> Preffered network type" in anything that does not contain LTE ...
As soon as the network type contains LTE, SMS does not work ... Unfortunately, I think changing the setting means I can not use VoLTE anymore ...
cool subbed and adding to the index!
is it TREBLE enabled?
Facing mic problem on discord and pubg. Mic work for a MI and then off
Okay so have been using this rom for a lot of time.
Here are few bugs I am facing.
1. Kernel auditor, gain sets back to 12 even after enabling the script, after every reboot.
2. I used H/W mido module from magisk to disable HW keys, so after that I am receiving -"there is an internal problem with your device. contact your manufacturer for details" after every reboot.
3. There is safety net failing in magisk, so for making ctsprofile true I used, patcher and after that, safety net is passed but root is removed automatically and even after flasking magisk zip so manytimes root is not getting enabled.
(*In havoc it was working properly)
These are few issues which is not getting resolved, even after many attempts.
Overall best stable rom, first preference after HAVOC OS.
sinhapratik.11136 said:
Okay so have been using this rom for a lot of time.
Here are few bugs I am facing.
1. Kernel auditor, gain sets back to 12 even after enabling the script, after every reboot.
2. I used H/W mido module from magisk to disable HW keys, so after that I am receiving -"there is an internal problem with your device. contact your manufacturer for details" after every reboot.
3. There is safety net failing in magisk, so for making ctsprofile true I used, patcher and after that, safety net is passed but root is removed automatically and even after flasking magisk zip so manytimes root is not getting enabled.
(*In havoc it was working properly)
These are few issues which is not getting resolved, even after many attempts.
Overall best stable rom, first preference after HAVOC OS.
Click to expand...
Click to collapse
I think op is not interested or active for some time.
[email protected] said:
I think op is not interested or active for some time.
Click to expand...
Click to collapse
Maybe, not active. But who knows might be updating or working on making it official.
mfd10000 said:
Ok..
Strange...
I've managed to solve SMS sending by changing to "Settings-> Network & Internet-> Mobile network-> Preffered network type" in anything that does not contain LTE ...
As soon as the network type contains LTE, SMS does not work ... Unfortunately, I think changing the setting means I can not use VoLTE anymore ...
Click to expand...
Click to collapse
I had that problem too with Pixel Experience on Oreo as well as Pie. I'm in Canada with Virgin Mobile. You can still use LTE for data, try unchecking "use enhanced LTE for voice calls". You won't be able to use volte but at least you can still use LTE data.
daubh said:
I had that problem too with Pixel Experience on Oreo as well as Pie. I'm in Canada with Virgin Mobile. You can still use LTE for data, try unchecking "use enhanced LTE for voice calls". You won't be able to use volte but at least you can still use LTE data.
Click to expand...
Click to collapse
Hello!
Yes I know...
But I really want to use VoLTE.
Anyway, meanwhile, I falshed Havoc OS.
The problem, unfortunately, is the same.
Probably the Orange Romania network operator uses network switching to sending SMS and not sending them all over LTE ...
I can send SMS messages if VoLTE is active to another phone number that uses VoLTE.
Is this probably possible due to RCS ...?
Hey guys! I was busy with my end semester exams till yesterday so couldn't do much(probably none). So I've gone through most of your issues.
For people facing network issues with SMS/MMS, you didn't have this issue with MIUI right?
And it has Treble enabled(thanks to Hard_Rock83 bro)!
Just to be on a safer side, be on the latest dev firmware. You can get it from the update file manually for the time being.
As for the internal error issue, I'll need some time identifying it, for now to pass CTS profile, please use the "MagiskHide Props Config" module. And avoid using any module that affects the system.
Also please be aware that, I'm currently not planning to make it official.
Next update will be available soon (Using latest codes from Hard_Rock83)
V_v3k said:
For people facing network issues with SMS/MMS, you didn't have this issue with MIUI right?
Click to expand...
Click to collapse
I forgot to post an update on my MMS issue.
Don't waste any time looking into it as it turned out to be a service provider issue. I just hadn't noticed it until Pie.
Well done on completing your exams and looking forward to trying out the next build.
V_v3k said:
Hey guys! I was busy with my end semester exams till yesterday so couldn't do much(probably none). So I've gone through most of your issues.
For people facing network issues with SMS/MMS, you didn't have this issue with MIUI right?
And it has Treble enabled(thanks to Hard_Rock83 bro)!
Just to be on a safer side, be on the latest dev firmware. You can get it from the update file manually for the time being.
As for the internal error issue, I'll need some time identifying it, for now to pass CTS profile, please use the "MagiskHide Props Config" module. And avoid using any module that affects the system.
Also please be aware that, I'm currently not planning to make it official.
Next update will be available soon (Using latest codes from Hard_Rock83)
Click to expand...
Click to collapse
Good to know that you are back
How is this different to the 'Official' Build?
From October 17th onwards, the Official builds had merged N9 sources which has ridden users the chance of flashing custom kernels due to the new N9 dependency. These builds aim to backtrack that, reverting to S9(+)'s Oreo Vendor, to gain custom kernel support again. Also, the firmware source used in the 'Official' builds have become fairly antique, so it was time for a refresh and use the latest and final Oreo source (BSB1) Samsung had to give, and an upstreamed kernel of latest (almost always) ELS thanks to @Eamo5's Endurance Kernel being baked into the builds.
Aside from these factors and a few more listed below, this is the LineageOS you know and love. Although LineageOS' nightly-build system is great, there is only so much change that can happen over a night. You can expect these builds updating to cover latest Security Patch a.k.a Monthly Builds, but maybe more if a great change is required.
Simple motive: Have a solid daily driver before the Pie Tree sources are dropped.
Screenshots
If you are on the App they may instead be at the bottom of the post
{
"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"
}
What's working:
As this build is based on the 'Official' LineageOS build, it complies with the device support requirements, which means including but not limited to these hardwares will work:
Wi-Fi
Bluetooth
Mobile Network (Calling, Data, etc.)
Audio
USB
GPS
NFC
Camera
Fingerprint Sensor - Noticeable speed improvement reverting to an S9(+) Vendor.
Software:
The build has overridden auto-generated fingerprint keys, with an official, whitelisted fingerprint from Samsung, which can also be found in MagiskHideProps. This ensures SafetyNet passes without the need for extra flashing - refer to above screenshot also.
F2FS Support - Instructions to switch from default ext4 to f2fs
Miscellaneous - Overlays:
- Dialer - Call recording enabled. If your country is not blacklisted (for legality reasons) you should see a 'Record' button during your call.
- Trebuchet - Notification Badges
- Files - File Operation Dialog Box, Default Show Internal Storage
- Settings - Default Enable Autobrightness for Night Time flashers; Default Disable Bluetooth and LED
- SystemUI - Button to Expand Notifications; Notifications fade on dismiss
- Snap: api v2 enabled for better quality pictures and remove green artefacts & flashing.
What's not working:
Samsung's own features such as Samsung Pay, KNOX, Theme Center, Game Launcher, etc. won't be ported to LineageOS. They may have their own implementation to similar functions, though.
Iris sensor does not work because AOSP upstream does not support that yet.
IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port.
Encryption Support as of now, exploring for a workaround (if there is one).
Bugs:
Lock screen shortcut - Camera: Screen flashes white, and then Camera force closes using shortcut.
Work around: Install another app using Camera action (e.g. SnapChat) and set stock Camera to default for shortcut.
Instructions:
Make sure TWRP has been installed and is functional.
Download the latest build, Vendor and optionally GApps - Links found under the header below.
Reboot to Recovery
Wipe data and cache (required if you are not currently using LOS and are coming from OneUI or SamExp.)
Install Vendor image to Vendor partition.
Flash the latest build (and GApps if you downloaded it)
If you are on and beyond April Patch (OneUI), do not flash a found Oreo Firmware as you will lose Baseband (Sim, Network, RIL). There is also no need to change firmware.
Reboot to System.
If a new build is released, to update:
Downloading and flashing a later build, will automatically replace (wipe & install) the /system partiton and retain your compatible User /data partition and firewall due to LineageOS' addon.d supprort.
You also do not need to flash GApps again, as they too have addon.d support, backing up which GApps you have installed and holding them until after the /system partition wipe has been done.
Same applies to Magisk Root due to (you guessed it) addon.d support too. It holds your currently installed Modules until after the /system partition wipe has been done.
Therefore, due to these addon.d files surviving because of the way LineageOS.zip manipulates the wipe to the /system partition there is no need to wipe partitions manually. Just leave it to the lone flash.
However, do remove any system modified theme overlays (substratum) to ensure no loop on boot, which may then result needing to wipe.
Downloads:
Vendor: Included to the respective Device drives below
Samsung Galaxy S9 (G960F): https://drive.google.com/drive/folders/131WWohHbpeZroYaHISBPpPnhDKYA6kj2
Samsung Galaxy S9+ (G965F): https://drive.google.com/drive/folders/1cr-ivOdTj8lo3p9kYjGcxT1AvgFYy3M9
OpenGApps (Optional): https://opengapps.org/
Contact:
Telegram Group - Handle @invisibazinga2 a.k.a Lil' G-Raf
Contributors:
Big thanks to: @jesec ; @Synt4x.93 ; @Ivan_Meler ; @Eamo5 ; please check GitHub commit history for anybody that I may have missed out, you have all been great!
ROM Information
LineageOS Source: https://github.com/LineageOS
Android Security Patch: May
Android Version: 8.1.0
Kernel Version: ELS - 4.9.xx - Endurance Kernel - Version subjected to change with ELS updates.
Device Source: https://github.com/AzzyC
Thanks for the rom! What would be the best way of installing gcam here? I've tried installing the apk on the official build but the quality wasn't too nice. Tried to flash the libs as well and got a bootloop. Thanks for your work!!
enetzlsg said:
Thanks for the rom! What would be the best way of installing gcam here? I've tried installing the apk on the official build but the quality wasn't too nice. Tried to flash the libs as well and got a bootloop. Thanks for your work!!
Click to expand...
Click to collapse
Hey man! Yeh on the official build as the vendor was N9 based, our modded S9(+) libs wouldn't be compatible. Fortunately, just before writing this reply, I flashed the lib for my device (S9) and then installed GCam and it got going nicely! There is a 4.1_fix.apk (fixed for OneUI lib) and just a regular 4.1.apk (built on Oreo lib).
Let me know how it goes man! And appreciate your compliments ?
the screenshots look like pie roms... clock is on left side ..i thought finally a good lineage 16 build.. yet thanks for the 15.1 build though.. ??
i came from soldier rom pie and after installing the rom according to the instruction.
full wipe, vendor image than rom and gapps and lastly the firmware.
everything boots and works but the phone doesnt detect my sim card nor the latest wifi network i was connected too. it does sees my neighbors wifi, for some reason it doesnt detect mine. i tried to change the baseband for fixing the sim card problem but no luck.
please help me/ im on s9 g960f
kmo1997 said:
i came from soldier rom pie and after installing the rom according to the instruction.
full wipe, vendor image than rom and gapps and lastly the firmware.
everything boots and works but the phone doesnt detect my sim card nor the latest wifi network i was connected too. it does sees my neighbors wifi, for some reason it doesnt detect mine. i tried to change the baseband for fixing the sim card problem but no luck.
please help me/ im on s9 g960f
Click to expand...
Click to collapse
It seems as though you were on and beyond the OneUI April Patch, which in the description of the Firmware zip it clearly indicates a warning to not flash the zip. I can't say anymore than these warnings unfortunately, after that it is up to the User.
A common fix that people do, to get back to normal state, is flash the latest DevBase with all of its complementary files. The April Patch had introduced a version change from U2 to U3 which makes downgrading impossible, without side effects. Please heed to warnings more in the future. Thanks
AzzyC said:
It seems as though you were on and beyond the OneUI April Patch, which in the description of the Firmware zip it clearly indicates a warning to not flash the zip. I can't say anymore than these warnings unfortunately, after that it is up to the User.
A common fix that people do, to get back to normal state, is flash the latest DevBase with all of its complementary files. The April Patch had introduced a version change from U2 to U3 which makes downgrading impossible, without side effects. Please heed to warnings more in the future. Thanks
Click to expand...
Click to collapse
thank you and sorry. i installed back to soldier rom with his firmware and everything works fine. but i really want to try your rom, so what firmware should i install with it?
kmo1997 said:
thank you and sorry. i installed back to soldier rom with his firmware and everything works fine. but i really want to try your rom, so what firmware should i install with it?
Click to expand...
Click to collapse
Glad you're back to normal state!
Users has been able to boot and use the ROM just by installing the provided Vendor image and remaining on the same firmware. Let me know how it goes and if I can recommend other users to do the same, if they are in a similar situation. Thanks
AzzyC said:
Glad you're back to normal state!
If I remember correctly a User has been able to boot and use the ROM just by installing the provided Vendor image and remaining on the same firmware. Let me know how it goes and if I can recommend other users to do the same, if they are in a similar situation. Thanks and hope it works out!
Click to expand...
Click to collapse
yep, works like magic. thank you very much!
AzzyC said:
Hey man! Yeh on the official build as the vendor was N9 based our modded S9(+) libs wouldn't be compatible. Fortunately, just before writing this reply, I flashed the lib for my device (S9) and then installed GCam and it got going nicely! There is a 4.1_fix.apk (fixed for OneUI lib) and just a regular 4.1.apk (built on Oreo lib).
Let me know how it goes man! And appreciate your compliments ?
Click to expand...
Click to collapse
one ui lib didn't work out for me
I always noticed that oreo roms were laggy. I heard somewhere that it was a HWC bug, NOT that HWC was disabled. So... my question... does this unofficial version of lineageos lags like the other oreo roms?
Muntasir Mahmud Saif said:
one ui lib didn't work out for me
Click to expand...
Click to collapse
You tried a OneUI vendor lib, on an Oreo Vendor? Read the post again.
LavaSnake54 said:
I always noticed that oreo roms were laggy. I heard somewhere that it was a HWC bug, NOT that HWC was disabled. So... my question... does this unofficial version of lineageos lags like the other oreo roms?
Click to expand...
Click to collapse
Can assure there is no lag here, but you can find out by trying of course aha! The kernel definitely smoothens out the whole experience and with decent battery (see sceenshot for example result) and HWC is active.
AzzyC said:
Can assure there is no lag here, but you can find out by trying of course aha! The kernel definitely smoothens out the whole experience and with decent battery (see sceenshot for example result) and HWC is active.
Click to expand...
Click to collapse
Looks like a solid daily driver for me. Will definitely try it soon.
AzzyC said:
You tried a OneUI vendor lib, on an Oreo Vendor? Read the post again.
Can assure there is no lag here, but you can find out by trying of course aha! The kernel definitely smoothens out the whole experience and with decent battery (see sceenshot for example result) and HWC is active.
Click to expand...
Click to collapse
one ui lib bro..i am using that lib on my one ui currently for quite a few months..
Muntasir Mahmud Saif said:
one ui lib bro..i am using that lib on my one ui currently for quite a few months..
Click to expand...
Click to collapse
I don't see what is not to grasp here, you are flashing a Pie vendor lib on an Oreo Vendor. How would that work out? Didn't think I'd have to spell it out, but you've spammed this issue across 3 posts now:
Use the Oreo modded lib (not the Pie/OneUI lib), as this ROM is based on an Oreo Vendor, and the 4.1.apk (not the 4.1_fix.apk).
Hey guys!
I was doing a test run for a particular change and I thought I'd do a quick update for both devices. Starlte built just fine but I ran out of disk space when finishing star2lte so the compile failed (at 91% ?)
Not to fret, the May Security Patch has not yet been merged into LineageOS so this would have been just another build on April Patch. However, the included kernel has updated to latest of Endurance, though you can just flash Eamon's latest kernel zip to update and have the same effect.
Both devices will of course get an update when May Patch is out. Gracias bien
For starlte:
https://drive.google.com/drive/mobile/folders/131WWohHbpeZroYaHISBPpPnhDKYA6kj2
Gcam link please?
AzzyC said:
I don't see what is not to grasp here, you are flashing a Pie vendor lib on an Oreo Vendor. How would that work out? Didn't think I'd have to spell it out, but you've spammed this issue across 3 posts now:
Use the Oreo modded lib (not the Pie/OneUI lib), as this ROM is based on an Oreo Vendor, and the 4.1.apk (not the 4.1_fix.apk).
Click to expand...
Click to collapse
sorry if i did wrong or hurt your feelings but can you please provide those two files?
LavaSnake54 said:
Gcam link?
Click to expand...
Click to collapse
Muntasir Mahmud Saif said:
can you please provide those two files?
Click to expand...
Click to collapse
https://f.celsoazevedo.com/file/gcamera/GCam_5.1.018.177470874.41362666_IDan_N6_4.1.apk
AzzyC said:
https://f.celsoazevedo.com/file/gcamera/GCam_5.1.018.177470874.41362666_IDan_N6_4.1.apk
Click to expand...
Click to collapse
you are dope bro .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"
}
Moto Z2 Force
Code:
- Your warrenty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 17.1 thread for the Motorola Moto Z2 Force, codename nash.
Join our Moto Z2 Force Development Discord server!
How to Install:
Please follow the instructions on our Official LineageOS Wiki page here.
If you don't follow these instructions, please don't expect support here. We also don't support 3rd party addons (Magisk/XPosed/Dolby/Viper/etc.), so please don't seek support if you use these.
Known Bugs:
Camera Mods don't work.
Official Lineage OS builds will not ever allow Moto's Battery Mod "Efficiency Mode" to work.
The EQ Apps for Audio Mods (eg. JBL2 App) won't work, and will crash.
Ultrasonic Proximity Sensor doesn't work -- No support present in the OSS Audio HAL. If it was written in, it wouldn't be used by anything in Lineage, as the normal proximity sensor works fine.
Notes:
Official Lineage OS builds for nash ship with full Project Treble compatibility! Flash GSI's to your heart's content after flashing Lineage. Please don't report GSI bugs here, report them instead to the GSI's maker.
Technical details on our Treble implementation:
Treble is enabled with VNDK29, and VNDK runtime enforcement. VNDK runtime enforcement means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run GSIs. without need for hacks or additional flashable zips. We relabeled /oem to /vendor (as /oem isn't wasn't used in custom ROMs 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.
Download:
LineageOS Updater
npjohnson's Personal Updater -- These are experimental, likely to break/eat your cat/destroy your data, and include GApps -- you'll only find support for these in the Discord linked above.
XDA:DevDB Information
[OFFICIAL] [NIGHTLIES] LineageOS 17.1, ROM for the Moto Z2 Force
Contributors
npjohnson, erfanoabdi, invisiblek
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Newest firmware available for your variant
Based On: LineageOS
Version Information
Status: Stable
Created 2020-04-01
Last Updated 2020-04-15
Removed
Hey, I cant find the link of lineaeg 17.1? (Build 0401, yesterday i found!) Just a joke?
How can I unlock bootloader, install TWRP and LineageOS on my XT1789-04 (AT&T)?
It is a beautiful day!
Although there's no download links.
A Sad Story said:
Hey, I cant find the link of lineaeg 17.1? (Build 0401, yesterday i found!) Just a joke?
Click to expand...
Click to collapse
I downloaded and installed and everything is ok xD
bogante said:
I downloaded and installed and everything is ok xD
Click to expand...
Click to collapse
I cant find link. In download.lineageos no build of 17. Can u share it?
A Sad Story said:
I cant find link. In download.lineageos no build of 17. Can u share it?
Click to expand...
Click to collapse
Oh man, my upload speed is 50kb/s it will take forever
Hi devs!
Trying it out, seems pretty great! Very few bugs (not related to device probably, just LOS17).
Only device bug I've found is the camera focus: it doesn't seem to be focusing properly (or at all).
If you need any logs let me know - eager to help out.
EDIT: That's weird. Somehow after using the camera app and moving the thing around I got it to work again. Although it's sporadic at best - focusing isn't working reliably.
EDIT 2: Found what allows it to work sometimes: open and close the camera app briefly time and time again and it starts working.
Has anyone with Reliance Jio tried it? I'm not able to get VoLTE going. Phone info (*#*#4636#*#*) has VoLTE provisioned enabled but greyed out. IMS Service status says not registered for IMS registration, and Not Available for everything else.
I jumped to 17.1 straight from stock, so not sure if it used to work in 16.0. I manually tried adding the ims apn for Jio, but no go...
Jelixis said:
Hi devs!
Trying it out, seems pretty great! Very few bugs (not related to device probably, just LOS17).
Only device bug I've found is the camera focus: it doesn't seem to be focusing properly (or at all).
If you need any logs let me know - eager to help out.
EDIT: That's weird. Somehow after using the camera app and moving the thing around I got it to work again. Although it's sporadic at best - focusing isn't working reliably.
EDIT 2: Found what allows it to work sometimes: open and close the camera app briefly time and time again and it starts working.
Click to expand...
Click to collapse
I'm facing same issue
---------- Post added at 10:08 AM ---------- Previous post was at 10:07 AM ----------
ph03n!x said:
Has anyone with Reliance Jio tried it? I'm not able to get VoLTE going. Phone info (*#*#4636#*#*) has VoLTE provisioned enabled but greyed out. IMS Service status says not registered for IMS registration, and Not Available for everything else.
I jumped to 17.1 straight from stock, so not sure if it used to work in 16.0. I manually tried adding the ims apn for Jio, but no go...
Click to expand...
Click to collapse
Again facing the same issue here
Calls don't work with jio and I'm also facing camera focus issues
ph03n!x said:
Has anyone with Reliance Jio tried it? I'm not able to get VoLTE going. Phone info (*#*#4636#*#*) has VoLTE provisioned enabled but greyed out. IMS Service status says not registered for IMS registration, and Not Available for everything else.
Click to expand...
Click to collapse
Adding to my quote here, I got incoming calls coming in! Only outgoing is not, the rest of the stuff I've reported remains the same. Also, the phone is able to query the status of Call Waiting and Call Forwarding, so IMS is partially working. This is a pure LTE provider, does not have a fallback.
Shreeram02 said:
Again facing the same issue here
Calls don't work with jio and I'm also facing camera focus issues
Click to expand...
Click to collapse
I haven't tried the camera. But did you upgrade from LOS16, and did Jio work fine there?
ph03n!x said:
Adding to my quote here, I got incoming calls coming in! Only outgoing is not, the rest of the stuff I've reported remains the same. Also, the phone is able to query the status of Call Waiting and Call Forwarding, so IMS is partially working. This is a pure LTE provider, does not have a fallback.
I haven't tried the camera. But did you upgrade from LOS16, and did Jio work fine there?
Click to expand...
Click to collapse
Yea incoming calls are fine btw normal messages don't work either
Yes in los 16 everything is fine
in los 17(not 17.1)(the September 21 unofficial build) calling is working fine camera has same bugs there too tho
But if u want everything working los16 is the option
@erfanoabdi @ThE_MarD @npjohnson not sure if you had a chance to review this - while this installs in LOS17.1, does not really control efficiency mode.
However we can still see the battery % of the Incipio Mod:
https://forum.xda-developers.com/z2-play/themes/motomodbattery-service-lineageos-15-1-t3895041/
https://github.com/devilsclaw/MotoModBattery
I was looking for a way to find the mod's battery % and stumbled on this...
no signal
i dunno what im doing wrong but when i flash LoS 17.1 and reboot the rom start but i have no signal
bogante said:
i dunno what im doing wrong but when i flash LoS 17.1 and reboot the rom start but i have no signal
Click to expand...
Click to collapse
Do you see your phone's IMEI in settings > about phone? Baseband version when you tap the Android version (10) in the same screen?
Magisk manager
I update LOS 16 to this 17.1 and everything seems to work fine, no real bugs. I've installed latest 7.2 google camera port from Arnova and picture/video/selfies are great. Phone calls no problems and it's a my impression but finally loudspeaker volume is higher than previous lineage versions. Only a question, maybe someone can help me, I've lost magisk root access, is it possible to install it with a temporaney twrp as in LOS 16 or is there any other method please?
[SOLVED] Maybe could be useful for someone. I tried the pie method: I've installed Magisk zip booting (not flashing) TWRP 3.3.1-0 (the 3.3.1-1 doen't boot on my device). Everything is working fine, I don't have any glitch and now my devices is rooted too
Getting Glitches when Playing Games Like Asphalt 9 also Same Camera Focusing Problem here too.
I'm seeing glitches in the home screen/ launcher too. Happens at random, gets psychedelic when unlocking - there are wavy lines (stock LOS17.1 wallpaper) on the image that move. Screenshot does not capture this, but I can take a photo if it helps figure the problem.
Messing with Developer Options (disabling overlay, etc) has not effect. Let me know if I can help troubleshoot...
Heyyo @ph03n!x, my nash is broken btw so I can't help too much.
Anywho, for the graphical glitches? Please try to go into your LiveDisplay settings and disable any special profile you have selected. I think those profiles are actually broken on nash hence the graphical issues when waking up the device after it sleeps.
Can you do me a favor please? Test my latest build of TWRP for nash. version 3.3.1-1 that contains a bunch of fixes and so far no feedback...
https://forum.xda-developers.com/showpost.php?p=82170641&postcount=590
{
"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"
}
Google Pixel 3a XL
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 18.1 thread for the Google Pixel 3a XL.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
bonito
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Kernel Source: https://github.com/LineageOS/android_kernel_google_msm-4.9
Going to try it now.
Thank you!
npjohnson said:
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Click to expand...
Click to collapse
syntax error Are we talking about the Kernel being bundled?
ssurell said:
syntax error Are we talking about the Kernel being bundled?
Click to expand...
Click to collapse
What? No, firmware, like modem, bootloader, etc.
Question:
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
So are you saying if we root there is no support? As most of us coming from stock would at least need root temporarily to restore all our apps.
Can anyone confirm if root even works on this build. I woudnt see any reason not but would like to know cause of the above reason.
UPDATE: Decided to just go for it and everything is working great so far. Took a little work to get google apps working instead of the included aosp ones (phone calendar and contacts) and a bt more work to get it to pass safteynet but its all working 100% now. Also tested this build with both ex kernel and mvk and they both seem to work just fine as well. Will report back if anything changes as have only been running it.a few hours but so far no issues or complaints at all.
Great job LOS team
What is the official way to obtain root access? or is there one any more?
cliffordd said:
What is the official way to obtain root access? or is there one any more?
Click to expand...
Click to collapse
Based on the above statement i quoted sounds like root is not "officially" supported at all. That said to get root i followed the process by which you patch a boot image file with magisk manager. Making it pass safteynet net took additional steps.
If you need more details on either process just post back and i can be more detailed
adm1jtg said:
If you need more details on either process just post back and i can be more detailed
Click to expand...
Click to collapse
Yes please - maybe message me off thread, as this topic might not be appropriate on here.
I have Magisk app installed, due to using Titanium Backup to keep a backup of my app. The upgrade went great and everything is working fine under LOS 18.1. But I miss the ability to take backups and use certain features properly on the device (ie clipboard sharing and other features in KDE Connect, scheduling backups etc) There used to be a package provided by LOS to add or remove su - https://download.lineageos.org/extras but that seems to have stopped now. I was just wondering if there was an "official" way of doing it!
I actually held off upgrading due to the previous download being released on 1st April and not finding some previous April fools pranks to be very funny!!
cliffordd said:
Yes please - maybe message me off thread, as this topic might not be appropriate on here.
I have Magisk app installed, due to using Titanium Backup to keep a backup of my app. The upgrade went great and everything is working fine under LOS 18.1. But I miss the ability to take backups and use certain features properly on the device (ie clipboard sharing and other features in KDE Connect, scheduling backups etc) There used to be a package provided by LOS to add or remove su - https://download.lineageos.org/extras but that seems to have stopped now. I was just wondering if there was an "official" way of doing it!
I actually held off upgrading due to the previous download being released on 1st April and not finding some previous April fools pranks to be very funny!!
Click to expand...
Click to collapse
sent you a private
cliffordd said:
What is the official way to obtain root access? or is there one any more?
Click to expand...
Click to collapse
i flashed the version of Magisk (v21.4) via the LineageOS recovery using the adb sideload and just updated to v22 via the app. I haven't had any issues with root since installing.
First off, I want to say thank you for all the hard work on these builds.
I have came across one issue that isn't working for me, but might not be something everyone else uses a lot. My "squeeze" for Assistant isn't working, but I can change it to take a screenshot of any other option, except the Assistant. Am I doing something wrong or is there another settings need to activate for it to work?
Thanks!
Really want to try this, but can't "fastboot boot twrp.img" or "fastboot flash boot twrp.img" in Android 11 to backup my partitions. What's the point of Android OS if I can't backup my system? I can boot into Lineage OS Recovery, enable adb, figure out the partition names, dd the partitions from shell or pull with adb? But good grief, kinda ridiculous if you ask me.
Haven't been able to use twrp since Android 9 far as i know
lineage-18.1-20210401-nightly-bonito-signed.zip
Searching Settings aborts after a matter of seconds and while typing.
Derelict non-clearable notifications requiring reboot or force close.
Desk Clock stuck at "Loading".
The final LOS 17 seems more polished, but lingering notifications are still present requiring force close.
Nevermind, user error.
ssurell said:
lineage-18.1-20210401-nightly-bonito-signed.zip
Searching Settings aborts after a matter of seconds and while typing.
Derelict non-clearable notifications requiring reboot or force close.
Desk Clock stuck at "Loading".
The final LOS 17 seems more polished, but lingering notifications are still present requiring force close.
Click to expand...
Click to collapse
you're using opengapps - don't do that ;p
Use MindTheGapps, which doesn't break that feature.
npjohnson said:
you're using opengapps - don't do that ;p
Use MindTheGapps, which doesn't break that feature.
Click to expand...
Click to collapse
Actually, it's the first time I've used MindTheGapps. I used OpenGapps after falling back to 17.1 though since it is recommended on the LOS site. I kind of liked the Slim Gapps feel of MTG though, and might try it on 17.1
ssurell said:
Actually, it's the first time I've used MindTheGapps. I used OpenGapps after falling back to 17.1 though since it is recommended on the LOS site. I kind of liked the Slim Gapps feel of MTG though, and might try it on 17.1
Click to expand...
Click to collapse
weird - we don't have MTG builds for 17.1 though, sadly.
How do I disable encrypted device? Tried ElemntalX kernel and Disable_Dm-Verity_ForceEncrypt_quota.zip but phone is still encrypted under security settings after first boot.
When I see "Say Hello To Trust", I just want to punch it in the face. Somebody just needs to build an updated LOS 16 so we have TWRP and possible access to /data (formerly user space) and call it a day.
ssurell said:
How do I disable encrypted device? Tried ElemntalX kernel and Disable_Dm-Verity_ForceEncrypt_quota.zip but phone is still encrypted under security settings after first boot.
When I see "Say Hello To Trust", I just want to punch it in the face. Somebody just needs to build an updated LOS 16 so we have TWRP and possible access to /data (formerly user space) and call it a day.
Click to expand...
Click to collapse
Why do you want encryption disabled?
It's hardware backed, and FBE, so very little gain from running unencrypted...
"Trust" has nothing to do with encryption, it can be on, off, trust just reports it to the user.
Why do you want TWRP? Lineage Recovery does the job just fine. What do you mean "/data (formerly userspace)"? That statement doesn't make much sense.
Regardless of all the above, the disabel force encrypt zip, followed by `fastboot -w` to format userdata ought to do it - but be warned, if you set a PIN, Android (AOSP, not a lineage thing specifically) will re-encrypt you... hence there being no point.
{
"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 13, 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.
Instructions :
https://wiki.lineageos.org/devices/instantnoodlep
Downloads :
https://download.lineageos.org/instantnoodlep
GPL compliance :
https://github.com/LineageOS/android_kernel_oneplus_sm8250
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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (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:
Thank for the new release!
Just flashed it. No issues so far.
I have just noticed that the "unlocked bootloader" message returned after flashing latest oos13 firmware. So, every time i restart my device i get the following "your device has been unlocked and can't be trusted". Just wanted to make sure that this is normal (since it was gone in oos12 firmware) and to alert other people about it.
For people who will root and need to pass safetynet the good old methods work however i was unable to find an android13 fingerprint using propsconfig. Instead i used a fingerprint for android 12 and i was able to pass all safetynet checks.
desosav said:
I have just noticed that the "unlocked bootloader" message returned after flashing latest oos13 firmware. So, every time i restart my device i get the following "your device has been unlocked and can't be trusted". Just wanted to make sure that this is normal (since it was gone in oos12 firmware) and to alert other people about it.
Click to expand...
Click to collapse
It's normal:
[Unlocked Bootloader][OOS13/OOS 13 based ROMs] How to remove bootloader unlocked message for OnePlus 8 Pro
This is a guide to remove the ugly "Your device has been unlocked and can't be trusted" or "The bootloader is unlocked and software integrity cannot be guaranteed" for OP8 Pro. This message was removed on OOS 12 which was one great thing by OP...
forum.xda-developers.com
desosav said:
For people who will root and need to pass safetynet the good old methods work however i was unable to find an android13 fingerprint using propsconfig. Instead i used a fingerprint for android 12 and i was able to pass all safetynet checks.
Click to expand...
Click to collapse
I want to ask about this
I've been using magisk, and have been unable to pass safety check on the stock ROM and thought Magisk stopped trying to beat safety net, so I stopped trying also.
It seems you have resolved this.
Can I ask you for direction on how to do this myself after I move to lineageos?
I don't necessarily need full instructions and would appreciate any guidance you can offer me.
Thanks
JustinChase said:
I want to ask about this
I've been using magisk, and have been unable to pass safety check on the stock ROM and thought Magisk stopped trying to beat safety net, so I stopped trying also.
It seems you have resolved this.
Can I ask you for direction on how to do this myself after I move to lineageos?
I don't necessarily need full instructions and would appreciate any guidance you can offer me.
Thanks
Click to expand...
Click to collapse
I haven't tried on 20 yet, but:
root with magisk then add the following modules:
propsconfig and change the fingerprint to a pixel 6 pro
kdragons safetynet patch
Make sure play store and other services are on the magisk deny list.
There are more detailed instructions in various threads specific to each step, but this is the gist of it.
No issues with following the lineage os version upgrade procedure to keep from needing to format data? The upgrade procedure didn't have about needing oos13 firmware beforehand, so I wasn't sure if it'd make a difference.
-update-
No issues yet after following the upgrade procedure without flashing oos13 stock fw first.
I still have some weird issue where it makes me have to sign in to the T-Mobile network. I think it's because I had a Verizon sim in sim slot 2 at one point.. it'll probably require a network settings reset to fix..
Is the 48MP sensor on the camera still locked? Just wondering considering the changes with the camera app and API with LOS 20.
d3viou5 said:
I haven't tried on 20 yet, but:
root with magisk then add the following modules:
propsconfig and change the fingerprint to a pixel 6 pro
kdragons safetynet patch
Make sure play store and other services are on the magisk deny list.
There are more detailed instructions in various threads specific to each step, but this is the gist of it.
Click to expand...
Click to collapse
hi, @d3viou5 how did you root?
I've updated from LOS19 to LOS20, following the official procedure.
Now. I've
- Installed Magisk (tried both canary and stable)
- extracted the boot.img with Payloader-Dumper-Go
- patched boot.img with Magisk
- flashed patched boot.img, system is NOT rooted
- tried to boot (not flash) the patched boot.img, again system NOT rooted
I'm missing something?
thx!
Installed manually coming from LOS 19.1. Did not update firmware, but did the DTBO and VBMETA flashing to be on the safe side. No issues and running very smooth so far. New camera app gets good pics with good lighting. Low light is 2014 quality.
miramax001 said:
hi, @d3viou5 how did you root?
I've updated from LOS19 to LOS20, following the official procedure.
Now. I've
- Installed Magisk (tried both canary and stable)
- extracted the boot.img with Payloader-Dumper-Go
- patched boot.img with Magisk
- flashed patched boot.img, system is NOT rooted
- tried to boot (not flash) the patched boot.img, again system NOT rooted
I'm missing something?
thx!
Click to expand...
Click to collapse
If you go into recovery, sideload magisk apk. That's what I did with 25.2 and it's rooted.
mattgyver said:
If you go into recovery, sideload magisk apk. That's what I did with 25.2 and it's rooted.
Click to expand...
Click to collapse
Thanks @mattgyver
The problem WAS the WORK profile (with SHELTER).
I had to remove my WORK PROFILE (from SETTINGS->ACCOUNT)
And then, sideload magisk.apk (renamed as magisk.zip) and now I'm rooted again.
ThX!
roaringcrown said:
Installed manually coming from LOS 19.1. Did not update firmware, but did the DTBO and VBMETA flashing to be on the safe side. No issues and running very smooth so far. New camera app gets good pics with good lighting. Low light is 2014 quality.
Click to expand...
Click to collapse
Hi, I'm guessing you "dirty flashed" LOS 20 over 19.1 through the LOS recovery?
I was hoping to avoid factory resetting/formatting...
Thanks!
Kuronosu said:
Hi, I'm guessing you "dirty flashed" LOS 20 over 19.1 through the LOS recovery?
I was hoping to avoid factory resetting/formatting...
Thanks!
Click to expand...
Click to collapse
yes, just follow the official guide
Upgrade LineageOS on instantnoodlep | LineageOS Wiki
wiki.lineageos.org
How to install the rom with twrp? i.m using oneplus 8 pro global varient ty
@LuK1337
Thanks for the great work!
I'm currently trying to build LOS 20 myself and as far as I can tell everything compiled properly.
However in the last steps of the build I receive the following error:
Bash:
The following HALs in device manifest are not declared in FCM <= level 4:
[email protected]::IEffectsFactory/default
[email protected]::IDevicesFactory/default
[email protected]::IBootControl/default
[email protected]::IMediaCasService/default
[email protected]::ICryptoFactory/wfdhdcp
[email protected]::ICryptoFactory/widevine
[email protected]::IDrmFactory/wfdhdcp
[email protected]::IDrmFactory/widevine
[email protected]::ICryptoFactory/clearkey
[email protected]::IDrmFactory/clearkey
[email protected]::IHealth/default
[email protected]::IDevice/qti-default
[email protected]::IDevice/qti-dsp
andro[email protected]::IDevice/qti-gpu
[email protected]::IDevice/qti-hta
android.hardware.power.IPower/default (@1)
[email protected]::IRadio/slot1
[email protected]::IRadio/slot2
[email protected]::ISecureElement/SIM1
[email protected]::ISecureElement/SIM2
[email protected]::ISecureElement/eSE1
[email protected]::ISoundTriggerHw/default
[email protected]::IUsb/default
android.hardware.vibrator.IVibrator/default (@1)
android.hardware.wifi.hostapd.IHostapd/default (@1)
android.hardware.wifi.supplicant.ISupplicant/default (@1)
[email protected]::IWifi/default
INCOMPATIBLE
stderr:ERROR: files are incompatible: Runtime info and framework compatibility matrix are incompatible: No compatible kernel requirement found (kernel FCM version = 5).
For kernel requirements at matrix level 5, For config CONFIG_DEBUG_FS, value = y but required n
For kernel requirements at matrix level 6, For config CONFIG_ANDROID_PARANOID_NETWORK, value = y but required n
: Success
Any idea why this is happening?
sToRm1nG said:
@LuK1337
Thanks for the great work!
I'm currently trying to build LOS 20 myself and as far as I can tell everything compiled properly.
However in the last steps of the build I receive the following error:
{code}
The following HALs in device manifest are not declared in FCM <= level 4:
[email protected]::IEffectsFactory/default
[email protected]::IDevicesFactory/default
[email protected]::IBootControl/default
[email protected]::IMediaCasService/default
[email protected]::ICryptoFactory/wfdhdcp
[email protected]::ICryptoFactory/widevine
[email protected]::IDrmFactory/wfdhdcp
[email protected]::IDrmFactory/widevine
[email protected]::ICryptoFactory/clearkey
[email protected]::IDrmFactory/clearkey
[email protected]::IHealth/default
[email protected]::IDevice/qti-default
[email protected]::IDevice/qti-dsp
[email protected]::IDevice/qti-gpu
[email protected]::IDevice/qti-hta
android.hardware.power.IPower/default (@1)
[email protected]::IRadio/slot1
[email protected]::IRadio/slot2
[email protected]::ISecureElement/SIM1
[email protected]::ISecureElement/SIM2
[email protected]::ISecureElement/eSE1
[email protected]::ISoundTriggerHw/default
[email protected]::IUsb/default
android.hardware.vibrator.IVibrator/default (@1)
android.hardware.wifi.hostapd.IHostapd/default (@1)
android.hardware.wifi.supplicant.ISupplicant/default (@1)
[email protected]::IWifi/default
INCOMPATIBLE
stderr:ERROR: files are incompatible: Runtime info and framework compatibility matrix are incompatible: No compatible kernel requirement found (kernel FCM version = 5).
For kernel requirements at matrix level 5, For config CONFIG_DEBUG_FS, value = y but required n
For kernel requirements at matrix level 6, For config CONFIG_ANDROID_PARANOID_NETWORK, value = y but required n
: Success
{code}
Any idea why this is happening?
Click to expand...
Click to collapse
You seem to be doing something wrong, e.g. building -user instead of -userdebug or something else.
LuK1337 said:
You seem to be doing something wrong, e.g. building -user instead of -userdebug or something else.
Click to expand...
Click to collapse
Yeah, you're right... I was building user isntead of userdebug.
Thank you so so much for this! ♥ It works like a charm and it's so so much better than OxygenOS 13 (I can minimize notifications omg!!!1!).
The only thing I personally am missing, is the classic LOS 18 style quick shortcuts in the pull-down notification menu. I always used 1 row with 6 circles, but since LOS 19 it changed to 2 rows with only 4 large shortcuts. But oh well, I guess you can't have everything!
Thank you for maintaining this device @LuK1337 !
@LuK1337
Thank you for your great work.
Not only for your work for this great Oneplus 8 Pro device, but also for other devices before!
You are really one of the most important and best device maintainers.
haxorinjector said:
How to install the rom with twrp? i.m using oneplus 8 pro global varient ty
Click to expand...
Click to collapse
TWRP is only available for A11 and lower. It does not work on A12 or A13.