Related
NLOS is an unofficial LineageOS build with many additions. These additions started small and have grown large over the month. So, it's time to name it NLOS - which still is an UNOFFICIAL LineageOS build.
Thanks to @UnbracedTundra NLOS has it's own logo, bootanimation and wallpapers.
LineageOS is a free, community built, aftermarket firmware distribution of Android 8 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
My priorities are stabillity, battery, performance - in that order. This build is optimized for oneplus3t - it will flash and run on a oneplus3, because it's an unified build, but it's optimized for 3t!
In addition this rom contains two patches (https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch and https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch, ported to Oreo) to be microG ready - this means freedom of choice to flash either gapps or install (microG How to use Android without Google Apps).
NLOS doesn't require any mods to work with @Arnova8G2's GoogleCamera Mod (more details in S4turno's thread ). Just install the modded Gcam - no need to flash twrp-front-fix-oreo-op3-3t.zip, nor to use the magisk module.
The kernel is prepared for Wireguard VPN - to use Wireguard for vpn-tunnels you need to get the WireGuard-apk from playstore. WireGuard developer @zx2c4 runs a dedicated Wireguard Thread.
NLOS features OMS Service Mode - the successor of ThemeInterfacer. This means you don't need root and/or andromeda to have full Substratum Theming! It's faster then andromeda and does not rely on a tethered pc-connection. It has more exposueres (items exposed to the themers) then the rooted solution. If substratum should ask for root previlegs, deny it.
Currently known issue can be found here.
If you find an issue, follow these instructions: https://forum.xda-developers.com/showpost.php?p=58239877&postcount=3
Everybody has his very own definition of "clean flash" or "dirty flash". I use these phrases like descriped in this posting: https://forum.xda-developers.com/showpost.php?p=58239877&postcount=2
{
"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 isn't void: we are on an oneplus device.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
This thread is for Unofficial LineageOS 15.1 builds for oneplus3 and onepluy3t. The following will not be supported here:
Custom kernels
Mods
Xposed
gapps packages bigger then opengapps-nano
I don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files (i.e. by using gapps larger then opengapps-nano)
First time flashing NLOS 15.1 on your device, or coming from another ROM:
Backup your current ROM and make sure you have backups of your data you want to keep.
Download the ROM below in the downloads section.
Download current MindTheGapps for arm64. If you insist on using gapps, don't use a package larger then nano.
Download and flash twrp-3.2.3-0!
Download and flash latest OxygenOS Oreo firmware.
Format data: in twrp tap on wipe and then tap on format data. This will delete all data, remove encryption and leave you with ext4, which is highly recommended. If you are insisting to use f2fs see: https://forum.xda-developers.com/on...1-20180223-t3754855/post75688089#post75688089 - NOT recommended!
Wipe system, data and caches.
Flash NLOS.
Flash Google Apps. If you want to use microG skip this step and install microG (How to use Android without Google Apps).
Optional: flash Magisk (if you need root)
Reboot (as usual: first boot takes loooooong )
Updating this rom
Dirty flashing should work just fine: reboot into recovery (if necesarry flash the firmware zip recommended by the release notes) and flash the updated NLOS zip - don't forget to wipe dalvik and cache. Settings, apps and even google apps are preserved.
Important: if you encounter any issues, a clean install is recommended and even required if you need support.
I won't build on a daily (or nightly) basis. I will publish new builds, if I fixed something, important upstream changes or new security patchlevels.
LineageOS changelog: https://www.cmxlog.com/15.1/
Build 20190208
Releasenotes:
NLOS-15.1 relays on Oreo firmware. OxygenOS 5.0.8 firmware or later is needed:
Oneplus 3T: OxygenOS 5.0.8 firmware
Oneplus 3: OxygenOS 5.0.8 firmware
For a complete list of additional cherry picks see: current.pick.sh.
This is most probably the second last build. I'm planing one more build, when the Feb. security patch is merged. If somebody wants to continue building and supporting nlos-15.1, drop me a note.
Changelog (Last repo sync: 8 Feb 2019, 14:09:19 CET / 8 Feb 2019, 13:09:19 UTC):
Merge tag 'v3.18.134' of git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable into linux-stable/merge-15.1 — Nvertigo
ARM: dts: msm: FIxup GPU 0mhz clock — Nvertigo
drivers: video: mdss: Fix direct references to HZ — celtare21
drivers: ipa: Fix direct references to HZ — Humberto Borba
drivers: platform: gsi: Fix direct references to HZ — Humberto Borba
drivers: hwmon: Fix direct references to HZ — Humberto Borba
drivers: i2c: Fix direct references to HZ — Humberto Borba
Convert few critical drivers to use msecs_to_jiffies insted of HZ — Dorimanx
msm: kgsl: Remove POPP — Sultan Alsawaf
current.pick.sh: O_asb_2019-02. — Nvertigo
current.pick.sh: introduce a safer repopick. — Nvertigo
op3/t: nfc: advertise support for extended length NFC — Paul Keith
NLOS-Bootlogo
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)
[SIZE="+2"]DOWNLOAD[/SIZE]
Happy flashing!
History
Build 20190127
Releasenotes:
NLOS-15.1 relays on Oreo firmware. OxygenOS 5.0.8 firmware or later is needed:
Oneplus 3T: OxygenOS 5.0.8 firmware
Oneplus 3: OxygenOS 5.0.8 firmware
For a complete list of additional cherry picks see: current.pick.sh.
This is most probably the second last build. I'm planing one more build, when the Feb. security patch is merged. If somebody wants to continue building and supporting nlos-15.1, drop me a note.
Changelog (Last repo sync: 27 Jan 2019, 13:01:40 CET / 27 Jan 2019, 12:01:40 UTC):
current.pick.sh: force picking abandoned battery customisation commits (220407, 220422, 219299) — Nvertigo
op3: Restore better load balancing after boot — Thomas Shum
WG: squash WireGuard-0.0.20190123. — Nvertigo
Merge tag 'v3.18.133' of git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable into linux-stable/merge-15.1 — Nvertigo
NLOS-Bootlogo
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)
[SIZE="+2"]DOWNLOAD[/SIZE]
Happy flashing!
Firmware
NVertigo's Oxygen Firmware Archive
TWRP
Latest official twrp
Thread for official twrp
Google Apps:
MindTheGapps-8.1.0-arm64-20180223_195845.zip
Source and toolchains
https://github.com/LineageOS/
https://github.com/nvertigo/local_manifest/tree/nlos-15.1 (If you want to build this rom yourself, consult the file named README, it's outdated, but still helpfull)
Aytex, who made all of the banners on this post.
team-exynos5420 for the OP templete.
All the LineageOS-Team.
@Lord Boeffla for patiencely answering my questions.
@koenkk
@Sultanxda
@TheFrozen4 for documentation and optimizing this OP.
The microG Team
@UnbracedTundra for all the awesome NLOS-ArtWork.
@zx2c4 for Wireguard VPN (dedicated Wireguard Thread)
@Arnova8G2 for his GoggleCamera port.
@S4turno for this great thread on GoggleCamera Mods.
@knpk13 for debugging this OP.
Substratum Dev Team
@danieldmm for opening my eyes for the obvious...
@mcdachpappe for helping me with additional notification slider options.
...and everybody I forgot.
Happy flashing!
XDA:DevDB Information
NLOS-15.1, ROM for the OnePlus 3
Contributors
nvertigo67, dianlujitao
Source Code: https://github.com/nvertigo/local_manifest/tree/nlos-15.1
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: latest
Based On: LineageOS 15.1
Version Information
Status: Stable
Created 2018-12-04
Last Updated 2018-12-04
Known Issues
fixed: NLOS can't initially encrypt f2fs data partitions (though ext4 is working flawlessly).
fixed: NLOS can't change the encryption passphrase for f2fs/ext4 data partitions (though ext4 is working flawlessly).
fixed: adb and mtp doesn't work out of the box. Workaround:
put in QS-tile "adb over network"
disable wifi
enable "adb over network" with the added tile (tile shows 0.0.0.0)
connect usb cable
an expandable notification shows up
expand it, tap it and select "file transfer": voila.
If you've run through the above adb and mtp are working fine - even trough reboots... automagicaly...
If secure boot password, pin or pattern is set: LiveDisplay's Settings show color profile as "Standrad" after a reboot, though the configuered LiveDisplay's color profile is correctly aplied.
Notification lights have hickups.
fixed: With no substratum themes applied and dark mode enabled the qs edit page is in stealth mode (white text on white background). For reference see: https://forum.xda-developers.com/ap...um-support-t3606400/post76619564#post76619564
Where has "keep wifi on during sleep"?
Sadly this isn't working anymore.
The maker of betterbatterystats offers also a tool to accomblish this task and much more:
betterwifionoff
When switching from lineage-14.1 to lineage-15.1 I found idle bat usage doubled: what has been 0.4 % per hour on nougat increased on oreo to 0.8 to 1.0 % per hour.
On n I've always used "only if charging" for "keep wifi on during sleep", but the access to this setting has been vanished by google. So I exprimented with wifi conf file, kernel driver and wakelock blocking on kernel level. Nothing really solved the adsitional idle drain.
I'm still surprised, what I found while searching settings (cli): the setting "wifi_sleep_policy" is still there! Google has just droped the access via Settings->Network&Internet->Wi-Fi and makes "Always" the default , but the setting is still available and is working like on n.
Value: Function
0: Never
1: only when plugged in
2: Always
To get restore my n setting (keep wifi on while sleep only when plugged in), I only need to connect via adb (I prefer adb over network, but it works as well with usb), and issue this command:
Code:
adb shell settings put global wifi_sleep_policy 1
After spending endless hours on kernel and debugging, this simple command brought back 0.4%/h idle bat usage.
How To: format data with f2fs with current official TWRP
Current twrp (3.2.1-0) can't change the data fs to f2fs. The reason for this breakage is, that twrp expects a mkfs.f2fs command that knows "-r size" as cli-option, but the image is shipped with a version that doesn't know about "-r".
To get data formated as f2fs with space for the encryption footer, you just need to follow these simple steps:
Download attached mkfs-f2fs.zip.
Unzip and place the contained mkfs.f2fs in /sdcard/Download.
Boot to current twrp-3.2.1-0.
In twrp:
Home-Screen->Advanced->Terminal
Code:
cp -vi /sdcard/Download/mkfs.f2fs /tmp
chmod 0755 /tmp/mkfs.f2fs
/tmp/mkfs.f2fs -t 0 -r 16384 /dev/block/bootdevice/by-name/userdata #for the lazy, if on op3/t can use /dev/block/sda15
flash rom (or use the installed rom, which is factory reseted by formating data), reboot t system amd encrypt your device.
The mkfs.f2fs binary is taken from the original twrp-3.2.1-0. This will only work for 64-bit devices:
Code:
file mkfs.f2fs
mkfs.f2fs: ELF 64-bit LSB pie executable ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /sbin/linker64, BuildID[md5/uuid]=46b5f32d88973c91f79744258599a19a, stripped
stuff.
UPDATE
Build 20180225
Releasenotes:
NLOS-15.1 relays on Oreo firmware. ob16 or later is needed, I strongly recommend using ob22 (because that's what I'm testing with): oxygenos-ob22-firmware.zip
beta03 users can just dirty flash beta02 (don't forget to wipt cache and dalvik after the dirty flash!) Since GCam is updated, I recooment wiping GCams data.
Changelog (synced lineageos 15.1 02/25 at 14:01:07 UTC):
Update GoogleCamera to GoogleCamera-Pixel2Mod-Arnova8G2-V6.apk — Nvertigo
Bring back busybox. — Nvertigo
Switch kernel branch to linux-stable/nlos-15.1. — Nvertigo
Merge tag 'v3.18.96' into linux-stable/merge-15.1 — Nvertigo
NLOS-Bootlogo
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)
[SIZE="+2"]DOWNLOAD[/SIZE]
Happy flashing!
set up wizard keeps crashing using the gapps on the OP, tried the lineage - mindthegapps and everything went fine
vinoxflame said:
set up wizard keeps crashing using the gapps on the OP, tried the lineage - mindthegapps and everything went fine
Click to expand...
Click to collapse
If you're using open gapps just exclude "LSetupWizard" in the gapps-config file.
With the version from 18th February the setup wizard is working, if you are going for a fresh installation.
vinoxflame said:
set up wizard keeps crashing using the gapps on the OP, tried the lineage - mindthegapps and everything went fine
Click to expand...
Click to collapse
crian said:
If you're using open gapps just exclude "LSetupWizard" in the gapps-config file.
Click to expand...
Click to collapse
...if there is an issue, it's either sepolicy or gapps... (devs rule of thumb)
I was so happy, finding a 8.1 package that worked (on beta01 for me)...
It would be great, if we can share gapps info here. Please report which gapps package is working with uri, and which doesn't (uri not mandatory... ).
nvertigo67 said:
...if there is an issue, it's either sepolicy or gapps... (devs rule of thumb)
I was so happy, finding a 8.1 package that worked (on beta01 for me)...
It would be great, if we can share gapps info here. Please report which gapps package is working with uri, and which doesn't (uri not mandatory... ).
Click to expand...
Click to collapse
Will this work on op3 too?
Aasresh said:
Will this work on op3 too?
Click to expand...
Click to collapse
Most propably: yes.
I don't have my hands on a 3, and I made it my self a rule to only build and push for devices I have my hands on. That's why I stay in 3t forum though it's essentially an unified build. On the other hand: whenever a setting can be tuned for either for sd820 or sd821, I go for sd821. Other then that, NLOS should work on both models, and I try my best to give you support here.
Does the 15.1 version of NLOS have EAS? I vaguely remember the 14.1 version having it...
doubleaykay said:
Does the 15.1 version of NLOS have EAS? I vaguely remember the 14.1 version having it...
Click to expand...
Click to collapse
Nope
doubleaykay said:
Does the 15.1 version of NLOS have EAS? I vaguely remember the 14.1 version having it...
Click to expand...
Click to collapse
No.
I've removed it from 14.1 some time ago, because wireguard has triggered some (of perhaps much more) merging errors. After doing some testing (which showed, that plain los was on level with los+eas , regarding speed and bat life [in deed plain los was slightly better on bat life]) I removed (broken-hearted) EAS again.
OMS service mode
TheGatorade said:
Can't wait for rootless OMS patch
This rom looking good, surprisingly stable for a beta
Click to expand...
Click to collapse
Stay tuned. Need to cleanup the sources and make a clean build.
nvertigo67 said:
No.
I've removed it from 14.1 some time ago, because wireguard has triggered some (of perhaps much more) merging errors. After doing some testing (which showed, that plain los was on level with los+eas , regarding speed and bat life [in deed plain los was slightly better on bat life]) I removed (broken-hearted) EAS again.
Click to expand...
Click to collapse
Gotcha. Good to know that plain LOS is just as good with battery life. Thank you
For people having trouble with gapps try flashing the rom then complete the setup wizard then flash gapps.
Worked for me.
UPDATE (OMS Service Mode)
Build 20180226
Releasenotes:
NLOS-15.1 relays on Oreo firmware. ob16 or later is needed, I strongly recommend using ob22 (because that's what I'm testing with): oxygenos-ob22-firmware.zip
beta04 users can just dirty flash beta02 (don't forget to wipt cache and dalvik after the dirty flash!) Since GCam is updated, I recooment wiping GCams data.
OMS Service Mode is still work in progress. Sometimes you need to activate a theme once again after "compile&activate". Some themes (i.e. flux - though it's working flawlessly) refuses to deactivate, but flashing /sdcard/substratum/SubstratumRescue.zip removes all activated overlays. Rebooting is sometimes neccessary. Wiping caches and dalvik may be a good idea, too. SwiftDark and Flux seem to work otherwise.
Special thanx to @danieldmm for helping me out of my brainlock with pointing me to https://substratum.review/ . Without his help I would be still searching for commits currently not meeged... ...that would have taken looooong.... *lol*
Changelog (synced lineageos 15.1 02/25 at 14:01:07 UTC):
OMS Service Mode: https://substratum.review/#/q/branch:o+(status:merged+OR+status:open) and https://github.com/nvertigo/android_frameworks_base/commit/e5cc87691ea4ba482914adee36821243fe39f7b4
op3: Use exfat-nofuse — dianlujitao
Merge remote-tracking branch 'lneageos/lineage-15.1' into linux-stable/merge-15.1 — Nvertigo
NLOS-Bootlogo
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)
[SIZE="+2"]DOWNLOAD[/SIZE]
Happy flashing!
EDIT:
HOTFIX:
Set sepolicy temporary to permissive, if you want to deactivate an overlay.
Dirty flashed nlos-15.1 20180226 over 20180225 cause some bugs.
Op3T boots but few seconds after the screen becomes black and the phone reboot to recovery.
Revert to 20180225.
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.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). 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 our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for LineageOS 16.0 builds for OnePlus 3/3T. The following will not be supported here:
Custom kernels
Mods
Xposed
We don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Tips:
You need at least OxygenOS 9.0.2 firmware, otherwise you'll get error 7 when installing the zip. Latest firmware is recommended.
Installation:
First time flashing LineageOS 16.0 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery (Official TWRP 3.3 or higher is highly recommended: https://twrp.me/oneplus/oneplusthree.html)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package
Reboot
Source code:
https://github.com/lineageos
Credits:
LineageOS Team & Contributors
Code Aurora Forum
......
Download:
Official: https://download.lineageos.org/oneplus3
Last unofficial: https://androidfilehost.com/?fid=1395089523397903569
XDA:DevDB Information
LineageOS, ROM for the OnePlus 3
Contributors
dianlujitao
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Version Information
Status: Beta
Created 2018-11-13
Last Updated 2019-08-12
Reserved
Changelog:
2018.11.13:
Initial release
2018.11.17:
Sync latest source
Fixed directly reboot to recovery when attempting to enter power on password when secure boot enabled
Downgraded kernel to LA.UM.7.5.r1-02500-8x96.0 due to CAF stability regression, but there's still a race condition which could cause random kernel panic, especially when attempting to wake up the device, I'm still debugging on this.
Improved GPS performance
Minor bug fixes
2018.11.29:
Sync latest source
Kernel baseline updated to LA.UM.7.6.r1-03600-89xx.0
Thanks to a clue provided by @markakash , the "random kernel panic on wake up" issue seems to be fixed now. The ROM is probably stable enough for daily use, so I call it "beta" instead of "alpha" now. Please report if you still have the issue.
Minor bug fixes
2018.12.02:
Sync latest source
IMS experiments, VoLTE is confirmed working, VoWiFi is untested
Battery life optimization
Fix fingerprint sensor not respond on first boot and after user switched
Minor bug fixes
2018.12.05:
Sync latest source
SELinux enforcing for now, let me know if there're any regressions
Minor bug fixes
2018.12.15:
Sync latest source
Fix some suspend issue
Kernel baseline updated to LA.UM.7.5.r1-03700-8x96.0
Minor bug fixes
2018.12.22:
Sync latest source
Slider key fix by @nvertigo67
App launch boost & touch boost, hope it helps reduce lagging
2018.12.30:
Sync latest source
Kernel baseline updated to LA.UM.7.5.r1-04000-8x96.0
WiFi display support
Bug fixes & improvements
2019.1.1:
Sync latest source
Various bugs in the last build have been addressed
Working unofficial SU addon: https://androidfilehost.com/?fid=11410963190603887268
Happy New Year & Enjoy!
2019.1.12:
Sync latest source
Add support for always-on-display
Minor bug fixes
2019.1.24:
Sync latest source
Fix touchscreen when gesture disabled
Fix whatsapp and CamScanner camera issue? Not sure, need feedback
Minor bug fixes
2019.2.10:
Sync latest source
Update kernel to LA.UM.7.5.r1-04100-8x96.0
Livedisplay & touchscreen gestures internal API migration
Allow disabling new USB gadgets when the device is locked
Minor bug fixes
2019.3.1:
Sync latest source
Fix weird color after boot? Need your confirmation
Performance optimizations
New offmode charging animation
Minor bug fixes
Note that some features/bugfixes will NOT be included in the upcoming official builds, be aware before switching from unofficial to official.
Future:
https://download.lineageos.org/oneplus3/changes/
Your opinion on migrating to official Pie firmware
dianlujitao said:
As you're aware, OnePlus started Pie closed beta days ago, and there're already leaked builds. I made a new Lineage build with blobs from one OOS9.0 leak, installed and updated firmware. On first boot after fw update, when boot animation was done, unexpectedly, I didn't see my launcher desktop as usual, but an "Decryption unsuccessful" warning telling me that my data was corrupted. Undoubtedly, after rebooting to TWRP it failed to mount /data thus I lost everything on my internal storage.
After several experiments I finally figured out the cause:
If your data is encrypted and bootloader is unlocked, after upgrading to Pie modem firmware, there's 100% chance of your data to become corrupted, and probably no way to restore them. The cause is on firmware side, probably something wrong with key migration, so there's no way for 3rd party developers to fix it. Note that which ROM was in use pre-upgrade doesn't matter at all, i.e., if bootloader was unlocked and you were upgrading from OOS 5.0.8(enforce encryption by default) to OOS 9.0, you'll lose all personal data after reboot from recovery installation. Interestingly, everything works as expected if bootloader was locked.
I couldn't comprehend why do they apply diverse low-level strategies to locked and unlocked bootloader. Arguably this is a bug and should be fixed when they started rolling OTA updates to the public, but it's also possible that this is by design and aims to restrict "unsafe" operations. Regardless, always be careful and backup your data before upgrading firmware in the near future.
Click to expand...
Click to collapse
Unfortunately they still didn't fix the issue in the OxygenOS 9.0 Community Beta released hours ago, in contract their PR claimed "SW team is aware of this issue" during the early closed beta stage. Given the fact the issue persists in both public H2OS and OOS build, I highly doubt if they're actively working on fixing the issue or they'd even gaf. Ofc it's still possible but very unlikely for them to fix it in future builds.
Now I'd like to know your opinion on migrating to Pie firmware. Device owners with encrypted data and unlocked bootloader MUST either backup data or relock bootloader before installing new firmware, others are not affected. Please vote.
Nice
Is it possible to update with a wipe system only ?
good
whats the difference in this build and does this uses 4.4 kernel ?
Playa82 said:
Finally
Is it possible to update with a wipe system only ?
Click to expand...
Click to collapse
Why this question is asked each time ?
You have TWRP right ? So backup your current install, flash without wiping, if it goes wrong, you know you have to clean flash, simple.
Plus, from the O.P of this thread:
O.P said:
Installation:
First time flashing LineageOS 16.0 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery (Latest official TWRP is highly recommended: https://twrp.me/oneplus/oneplusthree.html)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package
Reboot
Click to expand...
Click to collapse
lol, right when I clean flashed 15.1 and reinstalled everything from too many dirty flashes
karkiankit said:
does this uses 4.4 kernel ?
Click to expand...
Click to collapse
Why don't you check yourself? OP clearly states which kernel is in use:
https://github.com/dianlujitao/android_kernel_oneplus_msm8996/blob/lineage-16.0/Makefile#L1-L3
Nice!.. op3 community love u
Thank you
Weeew the legend is back. Awesome job
hi guys, what about these builds https://nyyu.tk/builds i also get ota update nightly
ele95 said:
hi guys, what about these builds https://nyyu.tk/builds i also get ota update nightly
Click to expand...
Click to collapse
Tried 9/11/18 build from jenkins. It wouldn't boot. You are welcome to try his latest one though and check if it boots.
Screenshots pls... Anyone??
Encryption still not working
Reboots to recovery right after "enter PIN" shows up
Racc145 said:
Encryption still not working
Reboots to recovery right after "enter PIN" shows up
Click to expand...
Click to collapse
IIRC, we need OnePlus sources from Android Pie for encryption to work correctly.
pjgowtham said:
Tried 9/11/18 build from jenkins. It wouldn't boot. You are welcome to try his latest one though and check if it boots.
Click to expand...
Click to collapse
dirty flash works and bootup fine for me but there is no sim signal so i revert to old one
Racc145 said:
Encryption still not working
Reboots to recovery right after "enter PIN" shows up
Click to expand...
Click to collapse
The same happened to me also. I'm encrypted on f2fs coming from OOS with a clean install.
@dianlujitao could you please add in the OP that it needs to be installed on an unencrypted phone - assuming that the reboot to recovery is caused by booting on an encrypted device.
Sent from my OnePlus3T using XDA Labs
Sometimes when I try to unlock using the fingerprint reader the screen stays black, while the buttons light up. The phone freezes and I need to reboot it. Someone else experienced the same issue?
Racc145 said:
Encryption still not working
Reboots to recovery right after "enter PIN" shows up
Click to expand...
Click to collapse
you knew that going in this, so why write and be supprised?
Team Win Recovery Project
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Read more about TWRP here: https://twrp.me/about/
WHAT THIS THREAD IS ABOUT?
This thread is about a serious TWRP development for the Xiaomi Redmi Note 6 Pro. By serious I mean a development which isn't using device tree which was just badly kanged from another device or it's a dirty port without any direct compilation from source. That means that issues like a low brightness, which is caused by a maintainer not being able to set the real maximum brightness which is supported by the device, aren't here.
FEATURES:
MTP support
USB OTG storage support
Hardware Qualcomm-based full-disk encryption support ( ext4 & f2fs )
ext4, f2fs, NTFS, fat file system support (read, write, format, backup & restore)
Covers more partitions for nandroid backup and the backup/restore of them really works!
Covers more partitions for image installation, including System, Vendor, Cust, Cache, Userdata, persist, persistbak, boot logo, modem firmware, and even Bluetooth firmware
ADB root
Always synced with signatures from Android platform, so you don't have to worry about the signature mismatch on MIUI incremental OTA installation
Full SELinux support
Support for Asian languages
Included logd/logcat support
Support for mounting USB storage - Mount -> Mount USB Storage in recovery menu.
ISSUE?
If you face any problem then just let me know and i will fix it asap. I'm not a magician to know everything, so if you won't report it then it's probably not gonna be fixed.
CHANGELOG
3.2.3.0, 18.1.2019
- initial release
3.2.3.1, 19.1.2019
- Fixed USB storage, from now on you can mount it
by clicking on Mount -> Mount USB Storage in the recovery menu.
3.2.3.2, 21.1.2019
- Imported selinux service contexts
- Added ability to backup/restore system/vendor images
- increased platform security values to override anti-rollback features to something rather insane
- Added system vold decryption support, since a process of getting keystore to work
on this device was a pure hell for me, but still this is in testing, just let me know if it works for you, but be careful and better backup your data before trying this...
3.3.0.1, 15.4.2019
- Slightly modified screen offset, so you can now see clock in the statusbar.
- Updated decryption blobs to pie, decryption should now work properly, after that there is also slightly improved vold decryption in case that default decryption fails
- Updated kernel to Android 9.0
DOWNLOAD LINK
3.2.3.0, 18.1.2019
Download
3.2.3.1, 19.1.2019
Download
3.2.3.2, 21.1.2019 - warning: this is test build!
Download
3.3.0.1, 15.4.2019
Download
DECRYPTION Builds (ported builds without source)
3.2.3.0, 27.4.2019
Changelog: Initial release
Download
XDA:DevDB Information
TWRP, Tool/Utility for the Xiaomi Redmi Note 6 Pro
Contributors
ATG Droid
Version Information
Status: Stable
Current Stable Version: 3.2.3.1
Stable Release Date: 2019-01-19
Created 2019-01-18
Last Updated 2019-01-19
Reserved
Device tree sources will be up later, don't worry about that. For kernel, I used prebuilt, so there isn't even what to publish.
Reserved
I'm using AOSP Extended, and data decryption does not work.
vdng9338 said:
I'm using AOSP Extended, and data decryption does not work.
Click to expand...
Click to collapse
Ok, will push a test build for it soon...
Edit: Here it is, someone test it please
https://www.androidfilehost.com/?fid=11410963190603903670
Thank You for this Serious development. Really Appreciate.
Ok, just pushed another update..
3.2.3.1 - 19.1.2019
Changelog: Fixed USB storage, from now on you can mount it by clicking on Mount -> Mount USB Storage in the recovery menu.
https://www.androidfilehost.com/?fid=11410963190603903811
Also tell me if the /data decryption works now
Finally, true TWRP builds there
with 3.2.3.1 it still cannot decrypt the data partition (I have entered the numbers that corresponds to the unlock pattern I have defined in Miui)
clemenza011 said:
with 3.2.3.1 it still cannot decrypt the data partition (I have entered the numbers that corresponds to the unlock pattern I have defined in Miui)
Click to expand...
Click to collapse
Here is another test build for it, in this one I switched to a decryption using vold, which should finally work i hope. Anyway, send me a log once you guys try it.
https://www.androidfilehost.com/?fid=11410963190603904132
ATG Droid said:
Here is another test build for it, in this one I switched to a decryption using vold, which should finally work i hope. Anyway, send me a log once you guys try it.
https://www.androidfilehost.com/?fid=11410963190603904132
Click to expand...
Click to collapse
another failed decrypt with the latest version - recovery log attached. Thanks!
edit: I have removed fingerprints, then switched from pattern to pure Pin unlock, and yet again decrypt failed - recovery2.log attached
ATG Droid said:
Team Win Recovery Project
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Read more about TWRP here: https://twrp.me/about/
WHAT THIS THREAD IS ABOUT?
This thread is about a serious TWRP development for the Xiaomi Redmi Note 6 Pro. By serious I mean a development which isn't using device tree which was just badly kanged from another device or it's a dirty port without any direct compilation from source. That means that issues like a low brightness, which is caused by the maintainer not being able to set real maximum brightness which is supported by the device, aren't here.
FEATURES:
MTP support
USB OTG storage support
Hardware Qualcomm-based full-disk encryption support ( ext4 & f2fs )
ext4, f2fs, NTFS, fat file system support (read, write, format, backup & restore)
Covers more partitions for nandroid backup and the backup/restore of them really works!
Covers more partitions for image installation, including System, Vendor, Cust, Cache, Userdata, persist, persistbak, boot logo, modem firmware, and even Bluetooth firmware
ADB root
Always synced with signatures from Android platform, so you don't have to worry about the signature mismatch on MIUI incremental OTA installation
Full SELinux support
Support for Asian languages
Included logd/logcat support
Support for mounting USB storage - Mount -> Mount USB Storage in recovery menu.
ISSUE?
If you face any problem then just let me know and i will fix it asap. I'm not a magician to know everything, so if you won't report it then it's probably not gonna be fixed.
CHANGELOG
3.2.3.0, 18.1.2019
- initial release
3.2.3.1, 19.1.2019
- Fixed USB storage, from now on you can mount it
by clicking on Mount -> Mount USB Storage in the recovery menu.
DOWNLOAD LINK
3.2.3.0, 18.1.2019
Download
3.2.3.1, 19.1.2019
Download
XDA:DevDB Information
TWRP, Tool/Utility for the Xiaomi Redmi Note 6 Pro
Contributors
ATG Droid
Version Information
Status: Stable
Current Stable Version: 3.2.3.1
Stable Release Date: 2019-01-19
Created 2019-01-18
Last Updated 2019-01-19
Click to expand...
Click to collapse
Thank you for your commitment with serious development and hard work.
Hope to see soon a final and official TWRP based on your version.
Keep debugging. Regards,
I'm also having trouble decrypting the date, no password is correct.
gostavovinicius said:
I'm also having trouble decrypting the date, no password is correct.
Click to expand...
Click to collapse
Decryption is always the most complicated thing to fix on every device. Anyway, I already encrypted my device and I'm trying to fix it, it will just take some time...
Ayyy, new update is out.
Changelog:
- Imported selinux service contexts
- Added ability to backup/restore system/vendor images
- increased platform security values to override anti-rollback features to something rather insane
- Added system vold decryption support, since a process of getting keystore to work
on this device was a pure hell for me, but still this is in testing, just let me know if it works for you, but be careful and better backup your data before trying this...
Download link:
https://www.androidfilehost.com/?fid=11410963190603905629
does this one have non anti rollback protecion?
bornlivedie said:
does this one have non anti rollback protecion?
Click to expand...
Click to collapse
Yep, that's what I mentioned in a changelog. And if you're talking about that "anti rollback" protection which is here promoted by the guy who compiled that fork of a TWRP called pitch black, then don't believe it. He didn't changed the required properties for it in his device tree. So it's actually just a clickbait and his recovery build doesn't really support that.
Actually his build doesn't even include the proper max. brightness which is supported by the LCD driver of this device. That's why I mentioned in a OP that compared to other TWRP builds here this thread is meant to be a serious development and not just a joke.
ATG Droid said:
Yep, that's what I mentioned in a changelog. And if you're talking about that "anti rollback" protection which is here promoted by the guy who compiled that fork of a TWRP called pitch black, then don't believe it. He didn't changed the required properties for it in his device tree. So it's actually just a clickbait and his recovery build doesn't really support that.
Actually his build doesn't even include the proper max. brightness which is supported by the LCD driver of this device. That's why I mentioned in a OP that compared to other TWRP builds here this thread is meant to be a serious development and not just a joke.
Click to expand...
Click to collapse
My bad, I read the entire changelog and yet somehow missed that line... I feel like a dumbass.
Thanks for the clarification, that's actually very important.
ouch, I have removed fingerprints, set pin protection, flashed latest twrp. When I rebooted to recovery, got just the twrp background, frozen, no any options. Worseover, I have turned the phone off, then on, and it asks me for password. I tried with the pin I have set before, yet it says - wrong password. so I cannot get my phone started and I do not know what else to do.
clemenza011 said:
ouch, I have removed fingerprints, set pin protection, flashed latest twrp. When I rebooted to recovery, got just the twrp background, frozen, no any options. Worseover, I have turned the phone off, then on, and it asks me for password. I tried with the pin I have set before, yet it says - wrong password. so I cannot get my phone started and I do not know what else to do.
Click to expand...
Click to collapse
It definetely wasn't frozen. Services would time-out. Just reboot back to the recovery, backup data, backup files in internal memory (sdcard). Format data, restore the previous backup of data and copy back the previous files from /sdcard again. After that flash the 3.2.3.1 version of a recovery and everything will be ok.
Team Win Recovery Project[TWRP]
Latest Version : 3.4.0-0-oneplus3
ChangeLog :
Device ChangeLog :-
* EDL Mode Optimised
* Few asserts added
* Misc Cleanup
RECOVERY ChangeLog :-
- Include Latest Twrp Code
For More Info
Download :- Unavailable
NOTES
- Reboot to TWRP and flash lastest IMG file as Recovery
- Can also be flashed via termial/Command Prompt.
Commands
fastboot flash recovery twrp-3.4.0-0-oneplus3-20200616.img
faatboot boot twrp-3.4.0-0-oneplus3-20200616.img
Source
Kernel :- https://github.com/LineageOS/android...neplus_msm8996
XDA:DevDB Information
TEAMWIN RECOVERY PROJECT, Tool/Utility for the OnePlus 3
Contributors
Gaurav24
Version Information
Status: Stable
Current Stable Version: 3.4.0-0
Stable Release Date: 2020-06-16
Created 2020-06-16
Last Updated 2020-06-16
Just updated my SAR twrp to this unofficial one by flashing image in twrp. Working fine and seems to have /system mounted as /system_root and /system, probably for backward compatibility.
Thanks for building, as it is the latest unofficial official, it will be my recovery from now on.
Edit: SAR patches are nicely integrated (see github).
Screenshot
What if SAR TWRP and Magisk?
Johan2020 said:
Thanks for building, as it is the latest unofficial official, it will be my recovery from now on.
Click to expand...
Click to collapse
There's no mention of 3.4 on the official website. Also what makes this recovery better? I'm not sure I understand much of the changelog. Hopefully the screen lock bug has been fixed. I assumed the next release would mainly be geared towards dynamic partitions support for newer devices running Android 10.
What's new?
Compatible with pre-10 roms? toybox/busybox? backup /system still broken?
Ah yes, the twrp app if you confirm yes to install will cause bootloop. That's all i can think what's wrong with the official.
Do we know if f2fs is properly managed now ? Thanks for the info.
Thread closed on behalf of the OP @Gaurav24
OP doesn't maintain this project any longer.
WETA Kernel SM-G991U/U1/0 Snapdragon only
*** This will only work on Snapdragon devices with an unlocked bootloader..
SM-G991U/U1 - SM-G9910
Telegram thread linked at bottom
See post #2 for install steps
Changelog...
R5.03
Upstreamed to 5.4.128
Enabled all tcp cong
Westwood tcp default
Disabled unneeded platforms
R5.02
Telegram thread merged into N20.S20 group, check new links.
Upstreamed to 5.4.127
all modules now inlined, no need for magisk helper module.
added wireguard
Power usage tweaks
More
R4.04
Upstreamed to 5.4.123
R4.03
Upstreamed to 5.4.122
R4.02
Upstreamed to 5.4.121
R4.01
Upstreamed to 5.4.120
R4
Testing phase complete
Upstreamed to 5.4.119
R3
Rebased off UAG source code
R2
Upstreamed to 5.4.118
Fixed Torch/Flash
R1
built using CU8 kernel source
Upstreamed to 5.4.117
Fully permissive
KNOX disabled
Wireguard
Misc debugging disabled
Kernel Downloads
Telegram thread
--------------------->
Beer fund
XDA:DevDB Information
Kernel for the Samsung Galaxy S21 Ultra
Contributors
Mentalmuso, mentalmuso
Source Code: - Kernel Source
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: R1
Created 2021-05-10
Last Updated 2020-05-10
*** Be aware, there may be a need to wipe data if you desire to go back to stock kernel, my suggestion is to backup your stock BOOT partition and DATA before flashing. This way you can return to your original setup easily. It is unknown at this stage what data is causing an issue going back to stock. If you find it, be sure to share.
* You must have bootloader unlocked and rooted your device with Magisk before flashing this kernel. Magisk is essential for camera and wacom.
* Boot times are approx 60-75sec at the moment, itll sit on the yellow triangle splash for approx 60sec and the bootanimation for 5sec.
* When flashing this kernel, an AnyKernel helper module is installed. This is a Magisk Module that is essential for the operation of Camera and Wacom. Removal of this module while running this kernel will break camera and spen.
* Kernel zip labels have either a P or E in them, P=Fully Permissive, E=Enforcing (switchable)
To install
download and flash the kernel installer zip in TWRP or any custom recovery
--->
mine2
How is it working ?
Hey, any idea if you are going to produce something similar for the exynos version (o1s)?
I have extracted the config from my exynos S21 (https://gist.github.com/wolverine2k/f647be12fbdf95ad8beec416f107772b)
What compiler you used?