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

Search This thread

Eric_Lev

Senior Member
Jan 27, 2019
1,288
2,447
Angers
androidfilehost.com
Is it possible to upgrade from (latest) official nightly v15.1 to official nightly v16 without wiping data?
I've tried an early build which in the end forced me to reinstall everything (because of bootloop) and would like to avoid doing that over again.
TIA.

In recovery mode :
- install the highly recommended TWRP (https://androidfilehost.com/?fid=1395089523397907195)
- boot to recovery
- wipe the two caches and format system
- install lineage-16.0-20190306-nightly-oneplus3-signed.zip, GApp and then SU addon (if you want)
- boot to system, wait and enjoy ... Perhaps!
 
  • Like
Reactions: EVOLw

nvertigo67

Senior Member
Dec 28, 2011
6,038
12,396
Is it possible to upgrade from (latest) official nightly v15.1 to official nightly v16 without wiping data?
I've tried an early build which in the end forced me to reinstall everything (because of bootloop) and would like to avoid doing that over again.
TIA.

Who would have guessed that after my last posting: for major version bumbs I'd recommend a clean flash without restoring data, because otherwise you'll need to check for each and every hickup if it's a s8de effect from a dirty migration.

Others swear on issue free dirty migration.

It's up to your decission.
 

Uqbar

Senior Member
Aug 17, 2009
1,138
138
Regnum Utriusque Siciliæ
127.0.0.1
In recovery mode :
- install the highly recommended TWRP (https://androidfilehost.com/?fid=1395089523397907195)
- boot to recovery
- wipe the two caches and format system
- install lineage-16.0-20190306-nightly-oneplus3-signed.zip, GApp and then SU addon (if you want)
- boot to system, wait and enjoy ... Perhaps!
I was actually willing to go the other way around: from v15.1 to v16.

---------- Post added at 04:02 PM ---------- Previous post was at 04:00 PM ----------

Who would have guessed that after my last posting: for major version bumbs I'd recommend a clean flash without restoring data, because otherwise you'll need to check for each and every hickup if it's a s8de effect from a dirty migration.

Others swear on issue free dirty migration.

It's up to your decission.
The offical blog entry says that if I am coming from a vanilla v15.1 nightly to a vanilla v16 nightly I should not need any wipe but just a so-called dirty flashing.
Unluckily it didn't work last time, as I wrote.
Now I know there was a TWRP issue i can overcome with a special TWRP image.
Anything else?
 

Eric_Lev

Senior Member
Jan 27, 2019
1,288
2,447
Angers
androidfilehost.com
dianlujitao's recommendation:

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 (My unofficial TWRP is highly recommended: https://androidfilehost.com/?fid=1395089523397907195)
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
 

Uqbar

Senior Member
Aug 17, 2009
1,138
138
Regnum Utriusque Siciliæ
127.0.0.1
dianlujitao's recommendation:

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 (My unofficial TWRP is highly recommended: https://androidfilehost.com/?fid=1395089523397907195)
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
I knew that. It's almost a clean install once you wipe data and do a factory reset.
Which is what I would like to avoid.
Thanks anyway
 

Eric_Lev

Senior Member
Jan 27, 2019
1,288
2,447
Angers
androidfilehost.com
Last edited:
  • Like
Reactions: nvertigo67

nvertigo67

Senior Member
Dec 28, 2011
6,038
12,396
Which is what I would like to avoid.

Belive it or not: we have understood that you don't want to do a clean flash - repeating that doesn't change our recommendation.

In the end a clean flash saves time over a dirty flash: if you sum up just the time you, @Eric_Lev and me are spending on this, would be enough to setup about 5 apps... I'm trying to do support for over 5 years now; I guess about 20% of all issues relate to incompatible data and or settings. No matter wether you like it or not.
 

Eric_Lev

Senior Member
Jan 27, 2019
1,288
2,447
Angers
androidfilehost.com
Belive it or not: we have understood that you don't want to do a clean flash - repeating that doesn't change our recommendation.

In the end a clean flash saves time over a dirty flash: if you sum up just the time you, @Eric_Lev and me are spending on this, would be enough to setup about 5 apps... I'm trying to do support for over 5 years now; I guess about 20% of all issues relate to incompatible data and or settings. No matter wether you like it or not.

In French, we say "le jeu en vaut la chandelle" ... perhaps in English, "The game is worth the candle" ... perhaps in Italian "Il gioco vale la candela" ?

Thanks to google translator.
 

aney1

Senior Member
Jun 2, 2012
73
41
OnePlus 3
OnePlus 7
I seem to be having issue with camera app. Can't open it, keeps crashing.
I've followed the steps from the lineageos blog for flashing without data wipe. (Upgade firmware to 5.0.8 > reboot > wipe system partition > sideload lineage-16.0-20190306-nightly-oneplus3-signed.zip > sideload opengapps 9.0 pico package > sideolad addon su > reboot)
So far everything works except for the camera app, for which I've cleared cache and data and it didn't help. Any ideas?
I'd rather like to avoid wiping everything unless this is the only choice. Is there a way to backup all data/applications and then after clean install restore it there?

I know it's a bit hard to follow this thread with all the unnecessary noise, but a solution for Snap not working has been posted a while back.
Reason: You dirty flashed from 14.1 to 15.1 to 16.
15.1 -> 16 is officially supported, and shouldn't cause any problems. Flashing from 14.1 to 16 isn't supported and is causing issues even if you go through 15.1.
The solution has been posed by aci89 in the Oneplus One Thread (and reposted by here by Kurt Krummbein)
You need to delete the line "<renamed-package new="org.lineageos.snap" old="com.cyanogenmod.snap" />" from "/data/system/packages.xml".
Then reboot to recovery, wipe cache and Snap will be working.
 

Kurt Krummbein

Senior Member
Jul 19, 2011
556
407
OnePlus X
OnePlus 3T
I know it's a bit hard to follow this thread with all the unnecessary noise, but a solution for Snap not working has been posted a while back.
Reason: You dirty flashed from 14.1 to 15.1 to 16.
15.1 -> 16 is officially supported, and shouldn't cause any problems. Flashing from 14.1 to 16 isn't supported and is causing issues even if you go through 15.1.
The solution has been posed by aci89 in the Oneplus One Thread (and reposted by here by Kurt Krummbein)
You need to delete the line "<renamed-package new="org.lineageos.snap" old="com.cyanogenmod.snap" />" from "/data/system/packages.xml".
Then reboot to recovery, wipe cache and Snap will be working.

Hm, this should have been fixed in 20190305 build :( with Snap: Add back original-package in manifest

Ciao
Kurt
 
  • Like
Reactions: nvertigo67

nvertigo67

Senior Member
Dec 28, 2011
6,038
12,396
Hm, this should have been fixed in 20190305 build :( with Snap: Add back original-package in manifest

Ciao
Kurt

Yep, thought that, too. That's why it doesn't came to my mind to suggest your solution.

After rethinking:
If one comey from (14.x to) 15.1 to 16.0 0206 the line (which meeds to ne deleted) isn't created in the first place, and snap is working. If one goes from (14.x to) 15.1 to 16.0 0203 the line is created and not deleted again by flashin 0206.

(Just to be the one: only happens for two times dirty flashers - clean flashers would have saved the time dealing with this.)
 

realtos

Senior Member
Nov 11, 2018
80
30
is it me or is the notication on SMS gone? i only get the icon on top. i see new settin for that in the app, my guess its a new feature in WIP?
 

Furai90

Member
Sep 2, 2010
11
1
I know it's a bit hard to follow this thread with all the unnecessary noise, but a solution for Snap not working has been posted a while back.
Reason: You dirty flashed from 14.1 to 15.1 to 16.
15.1 -> 16 is officially supported, and shouldn't cause any problems. Flashing from 14.1 to 16 isn't supported and is causing issues even if you go through 15.1.
The solution has been posed by aci89 in the Oneplus One Thread (and reposted by here by Kurt Krummbein)
You need to delete the line "<renamed-package new="org.lineageos.snap" old="com.cyanogenmod.snap" />" from "/data/system/packages.xml".
Then reboot to recovery, wipe cache and Snap will be working.

I'll take a look into it. But I'm pretty sure I came directly from 15.1 clean flash. But maybe my memory is bad about it.
If you have easy solution for keeping data for all the apps I'm all for clean flashing. Don't want to run into more issues though the rest of the phone seems to be working correctly.

And I did search the thread for "camera" keyword, didn't think of searching for "snap".

EDIT: So apparently it worked. Thanks a lot guys! :)
 
Last edited:
G

GuestX00836

Guest
Flashing issue when downloading latest update from system: reboots to TWRP & just sits there. I have TWRP 3.2.3-10. If I download from net & install from TWRP everything goes fine.
Why isn't install script working?
 

rasikreality

Senior Member
Oct 20, 2015
167
62
Madrid
OnePlus 3
Xiaomi Mi A1
I've installed the latest build and, for some reason, I can't use Google Assistant. I've installed Aroma GApps with Google app (obviously), and every time I long press at the home button it vibrates but nothing more happen (I have the "launch voice Assistant when long pressing" option enabled). When I say "Ok, Google", voice search is activated, but not the assistant. When I enter at the notifications section on the Google app, it redirects me to the discover section.
I've tried to clean all data on the Google app settings but it doesn't seems to work.
 

BillGoss

Senior Member
Sep 2, 2010
5,220
4,595
Sydney
OnePlus 8T
is it me or is the notication on SMS gone? i only get the icon on top. i see new settin for that in the app, my guess its a new feature in WIP?
The stock Messaging app uses the default notification sound only (no option to change it as was possible in previous versions). I hope they fix it eventually.

SMS Notification is OK.
You can activate notifications (sound and display) in the new features of SMS app.
This is true for the Google Messages app, but not the stock Messaging app (I'm on 190306).

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

6bre6eze6

Member
Aug 19, 2014
14
10
I've installed the latest build and, for some reason, I can't use Google Assistant. I've installed Aroma GApps with Google app (obviously), and every time I long press at the home button it vibrates but nothing more happen (I have the "launch voice Assistant when long pressing" option enabled). When I say "Ok, Google", voice search is activated, but not the assistant. When I enter at the notifications section on the Google app, it redirects me to the discover section.
I've tried to clean all data on the Google app settings but it doesn't seems to work.

Make sure to set Google to be your default Assist app. Settings, Apps & Notifications, Default Apps. Had none chosen for me, enabling Google there did the trick.
 

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.