[ROM][Official][Nightly] LineageOS 16.0 for OnePlus 3/3T

Search This thread

nvertigo67

Senior Member
Dec 28, 2011
6,038
12,396
My bad it was your scripts.

No. @Dirk Has done a Magisk Script. Two different scripts/approaches. In deed there are three different approaches:
  1. Changing the security patch date (https://forum.xda-developers.com/on...-nlos-16-0-t3879405/post78433987#post78433987 )
  2. Changing the the build fingerprint AND the date (Magisk module)
  3. Changing only the build fingerprint to an old oos 5.x (Magisk script)

I linked my posting because of the background information.
 
  • Like
Reactions: 64ashg

Andrew1999

Senior Member
Mar 8, 2014
320
86
hey everyone, i apologize for the question i realize its probably been asked before multiple times but i saw many conflicting posts regarding this
im currently running oos 9.0.5 rooted with magisk and twrp recovery. what are the steps I have to go through to install this rom
as far as i know from my older devices:
wipe system data cache dalvik cache
install rom gapps and magisk
reboot
are there any extra steps i have to go through like decryption or extra firmwares or such?
also from what i've read in the recent posts hotspot is broken in the latest builds so please let me know what is the latest build with functioning hotspot.
sorry for the many questions and long post
thank you
 

Johannes1098

Senior Member
Jul 19, 2017
161
177
hey everyone, i apologize for the question i realize its probably been asked before multiple times but i saw many conflicting posts regarding this
im currently running oos 9.0.5 rooted with magisk and twrp recovery. what are the steps I have to go through to install this rom
as far as i know from my older devices:
wipe system data cache dalvik cache
install rom gapps and magisk
reboot
are there any extra steps i have to go through like decryption or extra firmwares or such?
also from what i've read in the recent posts hotspot is broken in the latest builds so please let me know what is the latest build with functioning hotspot.
sorry for the many questions and long post
thank you

The steps are correct, you can perform an installation from OOS 9.x without any patched firmware etc.
But watch your TWRP version, use the newest one from https://dl.twrp.me/oneplus3/
 

prateektaneja

Senior Member
Jul 10, 2014
168
62
Some of the previous posts suggest the possibility of being able to lock the bootloader on this ROM? Is this true? And if possible, can this be done irrespective of ROMs?
 

BillGoss

Senior Member
Sep 2, 2010
5,238
4,617
Sydney
OnePlus 8T
Some of the previous posts suggest the possibility of being able to lock the bootloader on this ROM? Is this true? And if possible, can this be done irrespective of ROMs?
Yes, you can lock the bootloader on this rom.
This is also true for the official TWRP.
A rom has to have the boot image signed with the keys used by OnePlus and then it'll work on a locked bootloader.
But don't ask me how to do that - I don't know.

Sent from my OnePlus 3T using XDA Labs
 
  • Like
Reactions: prateektaneja

Xydia

Member
Nov 4, 2015
6
1
Hi Team,

I want to dirty flash the latest LOS 16 ROM. My proposed plan:
- blu_spark TWRP 3.2.3-1 -> TWRP 3.3.1-1
- LOS 16.0-20190928 -> LOS 16.0-2020
- SuperSU 2.82 -> ?
- Firmware? -> OxygenOS 9.03?

Questions:
- Is SuperSU considered a mod? If so, how else can I gain root? I don't want to get ignored :angel:.
- From TWRP: `dm-verity must be disabled in fstab`. Does this ROM disable dm-verity?
- What does this ROM use, EXT4 or F2FS?
- Where is OxygenOS 9.0.3 Firmware?
- What is the order of flashing? TWRP Bootloader < OxygenOS Firmware, LOS ROM, SuperSU?

Thanks!
 

BillGoss

Senior Member
Sep 2, 2010
5,238
4,617
Sydney
OnePlus 8T
Hi Team,

I want to dirty flash the latest LOS 16 ROM. My proposed plan:
- blu_spark TWRP 3.2.3-1 -> TWRP 3.3.1-1
- LOS 16.0-20190928 -> LOS 16.0-2020
- SuperSU 2.82 -> ?
- Firmware? -> OxygenOS 9.03?

Questions:
- Is SuperSU considered a mod? If so, how else can I gain root? I don't want to get ignored :angel:.
- From TWRP: `dm-verity must be disabled in fstab`. Does this ROM disable dm-verity?
- What does this ROM use, EXT4 or F2FS?
- Where is OxygenOS 9.0.3 Firmware?
- What is the order of flashing? TWRP Bootloader < OxygenOS Firmware, LOS ROM, SuperSU?

Thanks!
Su:I wouldn't use SuperSU (it's not been supported for a long time). I'd use the latest (stable) Magisk 20.3.
Dm-verity: not an issue
Format: You can use either ext4 or f2fs for the data partition. Your choice.
Firmware: the latest is 9.0.6, so use that. If you're coming from 5.0.8 I suggest you read https://forum.xda-developers.com/on...-5-0-8-firmware-barrier-t3941164/post79758055
Flashing: flash updated TWRP, firmware, rom, Magisk


Sent from my OnePlus 3T using XDA Labs
 

prateektaneja

Senior Member
Jul 10, 2014
168
62
Yes, you can lock the bootloader on this rom.
This is also true for the official TWRP.
A rom has to have the boot image signed with the keys used by OnePlus and then it'll work on a locked bootloader.
But don't ask me how to do that - I don't know.

Sent from my OnePlus 3T using XDA Labs

Thank you for the response. I flashed the official TWRP, am running this ROM and just tries fastboot oem lock. On choosing to lock the bootloader from the phone using the volume keys, the phone reboots without unlocking the bootloader. Any help on what might I be missing out on?

Edit: Got it! Turns out you have to chose to NOT lock your bootloader in order to lock it.
 
Last edited:

BillGoss

Senior Member
Sep 2, 2010
5,238
4,617
Sydney
OnePlus 8T
Thank you for the response. I flashed the official TWRP, am running this ROM and just tries fastboot oem lock. On choosing to lock the bootloader from the phone using the volume keys, the phone reboots without unlocking the bootloader. Any help on what might I be missing out on?

Edit: Got it! Turns out you have to chose to NOT lock your bootloader in order to lock it.
Yes, clearly an error in the coding. It applies also to unlocking.

Sent from my OnePlus 3T using XDA Labs
 
  • Like
Reactions: nvertigo67

Xydia

Member
Nov 4, 2015
6
1
Su:I wouldn't use SuperSU (it's not been supported for a long time). I'd use the latest (stable) Magisk 20.3.
Dm-verity: not an issue
Format: You can use either ext4 or f2fs for the data partition. Your choice.
Firmware: the latest is 9.0.6, so use that. If you're coming from 5.0.8 I suggest you read https://forum.xda-developers.com/on...-5-0-8-firmware-barrier-t3941164/post79758055
Flashing: flash updated TWRP, firmware, rom, Magisk


Sent from my OnePlus 3T using XDA Labs

Hooray it worked!

I've found two issues:
- Encryption - it doesn't work. In the UI I select it but get back a locked screen. UPDATE: I managed to fix this by "TWRP > Format Data".
- Enabling SELinux - your link suggests reflashing the modded firmware... it didn't fix it

Thanks!
 
Last edited:
  • Like
Reactions: BillGoss

nvertigo67

Senior Member
Dec 28, 2011
6,038
12,396
Hooray it worked!

I've found two issues:
- Encryption - it doesn't work. In the UI I select it but get back a locked screen. UPDATE: I managed to fix this by "TWRP > Format Data".
- Enabling SELinux - your link suggests reflashing the modded firmware... it didn't fix it

Thanks!

You are mixing different topics:
  • Encryption is working. It is breaking, if you change the unlocked bl from 5.x to 9.x. For details read (not blindly flash): https://forum.xda-developers.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164. If you want to relock the bl, it's mandatory to relock BEFORE updating tne bl, of course. If you boot your bl 5.x encrypted data partition with an unlocked 9.x updated bl once, your encryption is broken and a reformat is mandatory, as explained in tbe mentioned posting:
    Before processing further we need to know and accept some basic information on the bootloader and the keymaster:
    • If you just update the firmware from 5.0.x to 9.0.x and boot the above defined setup, your data is gone. It doesn't matter if you boot to recovery or system: your data is gone.
    • If you just downgrade the firmware from 9.0.x to 5.0.x on a system formated and encrypted with 9.0.x and boot, your data is gone. It doesn't matter if you boot to recovery or system: your data is gone.
  • If you've updated to 9.x bl and expirience selinux is permissive and flashing the 5.x bl again, you need to start from scratch. In doubt (e.g. flashed different fws together with different gapps and magisk can create a chaotic status) use an unbrick tool.
  • If you update the fw - especially if updating the bl as part of fw) - order is very important (as well as for changing bl's status). Rebboting is absolutly mandatory before formating if you've decided to update the bl in an unlocked state.
 
  • Like
Reactions: qhsusb_bulk

Oswald Boelcke

Senior Moderator / Moderator & RC-RT Committees
Staff member
@slev!n @knpk13 @nvertigo67 @150208 @nvertigo67
I just want to let you know that I've deleted a few of your posts regarding the latest "balck screen" discussion, and I apologise for that. Please continue/follow the discussion here: https://forum.xda-developers.com/oneplus-3/help/emmc-error-suddenly-black-screen-t4075449/
Initially, I intended to move your post to that thread but I realised it wouldn't work due to the timestamps as @slev!n had created the new thread after his post here.

EDIT: I played a bit, and all of your posts have now been moved to the thread I've linked above i.e. nothing of your valuable contributions got lost.
 
Last edited:

unimke

Senior Member
Aug 27, 2016
359
58
Hi everyone,

Anyone know why this is happening?
 

Attachments

  • Screenshot_20200401-194443_Settings.png
    Screenshot_20200401-194443_Settings.png
    91.5 KB · Views: 381
  • Screenshot_20200401-194502_Settings.png
    Screenshot_20200401-194502_Settings.png
    141.1 KB · Views: 382

Top Liked Posts

  • There are no posts matching your filters.
  • 137
    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?
    1. Download the zip(s)
    2. Install a compatible Recovery (Official TWRP 3.3 or higher is highly recommended: https://twrp.me/oneplus/oneplusthree.html)
    3. Perform a nandroid backup of your current ROM (Optional)
    4. Wipe data/factory reset
    5. Flash LineageOS
    6. Optional: Install the Google Apps addon package
    7. Reboot

    Source code:

    Credits:
    • LineageOS Team & Contributors
    • Code Aurora Forum
    • ......

    Download:

    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
    79
    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:

    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:
    63
    The 0302 official build failed to boot due to a technical issue with signing, it should be fixed with the upcoming build. Sorry for any inconvenience that may have been caused to you.
    63
    A warning on leaked Pie builds

    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.
    62
    Good news (maybe), after communicating with oneplus stuff they promised fw upgrading with unlocked bl will be fixed in future builds.