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

Search This thread

Eric_Lev

Senior Member
Jan 27, 2019
1,130
2,257
Angers
androidfilehost.com
Yeah I tried that. But since BL is locked, it throws "format failed" error. I guess my only option is to try unbrick tool.
As expected ...
I never tried with a locked BL but via adb root (if USB debugging and Rooted debugging were enabled in dev options) ... ?
However I guess your only option is to try unbrick tool.
 
  • Like
Reactions: $anket

Hemuli

Senior Member
Dec 6, 2013
199
52
I already write this Query a While ago, facing issue of parallel running of this 3 Apps...

While keeping ROOT BASED ADBLOCK on ADAWAY , hiding the AMAZON on MAGISK, hiding the Magisk Manager done all ,, Still AMAZON stucks out saying not working... Any Solutions !! ??????
Maybe your adblock lists are blocking amazon?
 

$anket

Senior Member
Feb 10, 2012
85
14
I did format data/system/cache multiple times in los recovery but still not able to side load anything. I think when I formatted data in recovery, it messed up my data partition. This error "E:Failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: No such file or directory" appeared only when I formatted data initially. There was no such error before performing format data.
My conclusion is, formatting system + format data/factory reset in LOS Recovery makes the device unbootable. Even adb sideload won't work. I might be wrong.
Similar issue is discussed here.

Can anyone with a spare device confirm this? (Only do this if u have Unlocked BL)
 

$anket

Senior Member
Feb 10, 2012
85
14
Of course the phone can't boot if you wipe the system partition!
Yes I know. But it should allow me adb sideload a rom. But it didn't. During adb sideload, it get stucks around 12% and throws me that bind error. And everytime I boot into recovery, this bind error is displayed permanently at the bottom of the screen.
 

johngare

Senior Member
Dec 19, 2014
126
29
sagay
Anyone experiencing an issue when your screen turns off snd then upon turning it back on either by fingerprint or powerbutton, the screen just keeps on flickering and won't open unless you restart it which is pretty annoying.
 

Cotopaxi42

Senior Member
Aug 30, 2015
79
5
Hi there! Happy to see the OP3 getting LOS 18.1!
Just a few questions before I update from 17.1:
- how is the GPS working? On 16.1 it worked very well, fast and accurate but on 17.1, not so good on my device, even after the GPS patch from months ago (I am not using GApps)
- is it possible to choose the 4G network manually and not only automatically? This option works on LOS 17.1 for the OP3 but I know it doesn't work on the OP2 and OP5 on LOS 17.1 (you can not select manually the network, it's automatic only)
Thanks a lot for your answers!
 

snyperius

Member
Oct 4, 2018
44
22
Hi there! Happy to see the OP3 getting LOS 18.1!
Just a few questions before I update from 17.1:
- how is the GPS working? On 16.1 it worked very well, fast and accurate but on 17.1, not so good on my device, even after the GPS patch from months ago (I am not using GApps)
- is it possible to choose the 4G network manually and not only automatically? This option works on LOS 17.1 for the OP3 but I know it doesn't work on the OP2 and OP5 on LOS 17.1 (you can not select manually the network, it's automatic only)
Thanks a lot for your answers!
With a little gps.conf file tweaking, the GPS on my OP3T is at least as good as it is with OOS (sub-half a minute GPS position fix indoors.) I've written down what I did in a comment above somewhere, read back or search for it.
 

defi231

Senior Member
Aug 24, 2012
67
18
I guess the problem exists because of Magisk issue #4147. @dianlujitao is obviously aware of the problem. Let's hope topjohnwu can fix it :).
that reminds me of the beginning of LOS 16 there where similar problems with magisk topjohnwu and LOS from dianlujitao, nvertigo created a workaround / bootsigner


would this help in this case too?
 

an0ndr0id

New member
Apr 30, 2019
3
1
I already write this Query a While ago, facing issue of parallel running of this 3 Apps...

While keeping ROOT BASED ADBLOCK on ADAWAY , hiding the AMAZON on MAGISK, hiding the Magisk Manager done all ,, Still AMAZON stucks out saying not working... Any Solutions !! ??????
Preferences > Root based ad blocker > Deselect Enable web server
 
  • Like
Reactions: vettayyan

an0ndr0id

New member
Apr 30, 2019
3
1
A dirty flash update resulted in a boot loop. Installing a patched boot image (I created it before flashing the update) fixed the problem.
I noticed that the Magisk add-on script execution had an error but finished successfully:
Code:
sh: 21: unknown operand
! Unable to detect Magisk Manager APK for BootSigner
I ran the 04.12 ota update and received the same Magisk error (the 04.05 update did not have this this error) resulting in a bootloop. Are you patching each update?
 
Last edited:

BillGoss

Senior Member
Sep 2, 2010
4,541
3,932
Sydney
OnePlus 3T
OnePlus 8T
I ran the 04.12 ota update and received the same Magisk error (the 04.05 update did not have this this error) resulting in a bootloop. Are you patching each update?
I'm back on an unlocked bootloader so I no longer have problems dirty flashing updates. In fact, I'm on 0412 after dirty flashing it over 0405. Magisk add-on survived nicely.

But if you have a locked bootloader then you'll need to create a patched boot image of 0412 using the Magisk app when the system is running and then in TWRP install that patched image in the boot partition after you've dirty flashed 0412.
 

an0ndr0id

New member
Apr 30, 2019
3
1
I'm back on an unlocked bootloader so I no longer have problems dirty flashing updates. In fact, I'm on 0412 after dirty flashing it over 0405. Magisk add-on survived nicely.

But if you have a locked bootloader then you'll need to create a patched boot image of 0412 using the Magisk app when the system is running and then in TWRP install that patched image in the boot partition after you've dirty flashed 0412.
My bootloader is unlocked as well. But I keep getting that same Magisk error followed by bootloop.
 

BillGoss

Senior Member
Sep 2, 2010
4,541
3,932
Sydney
OnePlus 3T
OnePlus 8T
My bootloader is unlocked as well. But I keep getting that same Magisk error followed by bootloop.
Hmm.
I went back to have a look at my logs from my dirty flashing of 0412, which booted without issues, and saw this:
Code:
! Unable to detect Magisk app APK for BootSigner
Error preloading public library libandroid.so: dlopen failed: library "libstatssocket.so" not found: needed by /system/lib64/libandroid_runtime.so in namespace system
libc: Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 1989 (main), pid 1989 (main)
Aborted

Very weird. So it's works for me even with the error but it doesn't work for you.

Do you need help getting out of the boot loop?
Restoring backup of boot and system partitions only of last backup (effectively rolls back the update) is simplest way to get things going again.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    For what it is worth.... I did not take any logs or whatever...
    I am using a gps config where I am using pool.ntp.org and let the auto selection decide.
    Normally this is only taking 3-5 seconds (no Google stuff on my phone and wifi and bluetooth scanning disabled).
    Though.... sometimes it is not. The work around for me then (take note of the order!) is starting the app using gps and then disabling gps >>> wait till icon in taskbar is gone, and enable gps again.
    This way in 3-5 seconds I have my gps back, not the other way around though....

    One of my apps is not working correctly with 18.1 gps, where it was with 17.1 gps. So it seems something is changed in between, but did not check already in the changelogs. For those who want to try: the route.nl app will take the right gps location on startup, after that gps is not refreshed anymore, where other apps are working correctly.
    Ah. That workaround helps. Worked for me. Yeah, but somethings not right.
    @dianlujitao
    Could you maybe have a look? I would be happy to provide more data if needed.
    4
    Yes it helps,, But how to take my home screen or lockscreen is my Question, Some thing i like to show on Home screen or Lock screen , whats the way out??
    Well, for the home screen there's a way if you are rooted, have installed Termux, and are willing to put a widget on your home screen.
    Since this has nothing to do with Los 18.1, it's time to take the conversation elsewhere.
    Send me a PM if you want to try the above suggestion.
    3
    Hi guys, is this LOS18.1 ok for all day use ? No great troubles ? Battery is ok ? I'm on arrow os actually. Thanks
    Why is everyone asking the same without looking to previous posts?!?

    To answer your questions: yes, no and yes.... ;-)

    LOS 18.1 is my daily driver from the first builds, did a fresh install when it became official.
    No issues here, everything is working including bluetooth, hotspot etc...
    3
    So does anybody else have issues with GPS? Like said in my post before, there is simply no satellites shown. Changing the NTP Server to Europe in the GPS config fixed it for a day. Now it doesnt work again. I also tested Oxygen OS to exclude an hardware flaw, I have no issues getting a fix in OOS.
    I now set set the logging level to verbose, an thats what is repeatedly shown:
    Code:
    04-21 08:18:17.370   581  1512 D LocSvc_GnssAdapter: reportPositionEvent]: fromUlp 0 status 2
    04-21 08:18:17.370   581  1512 D LocSvc_ApiV02: reportPosition:2512]: Ignoring position report with sess status = 7, fix id = 69
    04-21 08:18:17.371   581  1503 V LocSvc_nmea: Entering loc_nmea_generate_pos line 481
    04-21 08:18:17.371   581  1503 V LocSvc_nmea: Exiting loc_nmea_generate_pos line 979 0
    04-21 08:18:18.372   581  1512 V LocSvc_api_v02: locClientIndCb:949]: Indication: msg_id=36 buf_len=18 pCallbackData = 0x7aa9aaa350
    04-21 08:18:18.373   581  1512 V LocSvc_api_v02: locClientGetSizeByEventIndId:2382]: event ind Id 36 size = 488
    04-21 08:18:18.373   581  1512 V LocSvc_api_v02: locClientGetSizeAndTypeByIndId:730]: indId 36 is an event size = 488
    04-21 08:18:18.373   581  1512 I LocSvc_ApiV02: <--- globalEventCb line 115 QMI_LOC_EVENT_POSITION_REPORT_IND_V02
    04-21 08:18:18.373   581  1512 V LocSvc_ApiV02: globalEventCb:120] client = 0x7aa9aaa350, event id = 36, client cookie ptr = 0x7b39aaa110
    04-21 08:18:18.373   581  1512 V LocSvc_LBSApiV02: eventCb:61] client = 0x7aa9aaa350, event id = 36, event name = QMI_LOC_EVENT_POSITION_REPORT_IND_V02 payload = 0x79e4f0ea30
    04-21 08:18:18.373   581  1512 D LocSvc_ApiV02: eventCb:3954]: event id = 36
    04-21 08:18:18.373   581  1512 D LocSvc_ApiV02: Reporting position from V2 Adapter
    04-21 08:18:18.373   581  1512 D LocSvc_ApiV02: reportPosition:2264 QMI_PosPacketTime  1779 (sec)  137992285 (nsec)
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase: flags: 0
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   source: 0
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   latitude: 0.000000
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   longitude: 0.000000
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   altitude: 0.000000
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   speed: 0.000000
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   bearing: 0.000000
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   accuracy: 0.000000
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   timestamp: 0
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   rawDataSize: 0
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   rawData: 0x0
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   Session status: 2
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:  Technology mask: 0
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:  SV used in fix (gps/glo/bds/gal/qzss) :              (0/0/0/0/0)
    04-21 08:18:18.374   581  1512 D LocSvc_IzatAdapterBase: reportPositionEvent: default implementation invoked
    04-21 08:18:18.374   581  1512 D LocSvc_GnssAdapter: reportPositionEvent]: fromUlp 0 status 2
    04-21 08:18:18.374   581  1512 D LocSvc_ApiV02: reportPosition:2512]: Ignoring position report with sess status = 7, fix id = 70
    04-21 08:18:18.374   581  1503 V LocSvc_nmea: Entering loc_nmea_generate_pos line 481
    04-21 08:18:18.375   581  1503 V LocSvc_nmea: Exiting loc_nmea_generate_pos line 979 0
    3
    I just want to drop a couple of lines on the subject of LineageOS 18.1, OnePlus 3T, and my status.

    First, thanks to lots of people on XDA in general and quite a few in this thread in particular.

    I stopped using my 3T sometime last year, since it hadn't had any updates from 1+ since late 2019, and I gifted my wife a new phone (Xiaomi Mi Note 10 pro, slow but great cam). So I took her old Nokia 8, which was fine and faster (got all important data off my 3T, got all important apps and connections running). But: it also didn't get updates since Oct/Nov 2020. And I desperately want a backup device, so I figured I should get the 3T up and running.
    Following instructions here and at the LineageOS device site, I unlocked the bootloader, installed TWRP - I still don't know if the LineageOS recovery would have been better, but it works - flashed LOS, MindTheGApps and Magisk.

    I didn't necessarily want to root my phone, but figured I'd give it a go. I have some old Galaxy S4's in the household running LOS 17, and with F-Droid with the background installation, getting updates is really much easier.
    I did have trouble with Magisk 22100, I think it's somewhere in this thread that 22104 will get the device past safetynet. So I got that one, forgot how I flashed it (within Magisk? Don't remember, must be getting old...) but it does work fine.

    All my banking apps work. Well, now they do, after getting Magisk to hide. I had one app that somehow detected something non-standard, but luckily the programmers just made it show a warning: "we don't support rooted Android devices, continue at your own risk [ ok ] [ cancel ]" so that was acceptable.
    I don't know how they could detect the device is rooted. Perhaps they detect the unlocked bootloader?

    I also missed how to get the device encrypted, I now read in this thread how to do it, but it will have to wait for another day.
    Yesterday I updated to the latest nightly, I wasn't quite sure if I would run into trouble, but all was fine, still rooted, banking stuff still working, etc.

    Like I said, the 3T is my backup device, but with all that I have used it setting it up, I can say that LineageOS feels snappy. Battery life is great, but I don't use it with my 2 SIM cards (so just WiFi).

    Next I'll update my N8 - sometime last year I got the unlock code when Nokia /HMD were still giving those out - but not until I have another redundant device.
  • 40
    LineageOS is a free, community-built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
    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 18.1 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 an 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 18.1 on your device, or coming from another ROM?
    1. Download the zip(s)
    2. Install a compatible Recovery (Official TWRP 3.4+ is highly recommended: https://dl.twrp.me/oneplus3/)
    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
    • ......

    Changelog and Download:
    Known issues:​
    • This build is HIGHLY EXPERIMENTAL and NOT WELL TESTED.
    • Wifi display not work, don't ever attempt to use it or the system will crash.
    • VoLTE is not tested and I don't know if it ever works, please give feedback if you're able to verify.
    • Fixed the sensor_SMD wakelock
    • Fixed ringtone when bluetooth headset connected
    13
    Regarding the sensor_SMD wake lock:
    Generally, the rom can go for long periods without this wake lock showing up:
    View attachment 5215977View attachment 5215981
    But the wake lock can start at random times:
    View attachment 5215983View attachment 5215985
    And when it starts, it will stop the device from going into deep sleep (look at the "Awake (Screen off)" figures). This will drain the battery a lot faster than normal. See 210209-174541-log.zip for logs.

    However, I find that the wake lock will always start when the phone is fully recharged (I usually do this just before I go to bed). See 210209-174541-log.zip for logs.
    View attachment 5215983View attachment 5216001

    Fortunately, a reboot gets rid of the wake lock.
    Nice finding. Just check the source and that should be the Significant Motion Detector if I'm not wrong. Dunno if there are any drawbacks but you should be able to disable it by adding " ro.vendor.sensors.smd=false" to /vendor/build.prop, please try if it helps.
    13
    I've been running this rom for a week now. I've not had any problems with it - no system reboots, no system FCs, no performance lags or stutters (though I don't play games).
    Battery life is not quite as good as 17.1, but I still only charge the phone once a day. Of course this is with the fix for the sensor_SMD wake lock from https://forum.xda-developers.com/t/...s-18-1-for-oneplus-3-3t.4230665/post-84465491
    The only other minor annoyance than the issues I mentioned in https://forum.xda-developers.com/t/...s-18-1-for-oneplus-3-3t.4230665/post-84456483 is that there's no "Mark as read" option on SMS notifications.

    Great work @dianlujitao! This is now my daily driver. I look forward it becoming an official version.
    12
    Regarding the sensor_SMD wake lock:
    Generally, the rom can go for long periods without this wake lock showing up:
    Screenshot_20210210-044409_BBS.pngScreenshot_20210210-044354_BBS.png
    But the wake lock can start at random times:
    Screenshot_20210209-174523_BBS.pngScreenshot_20210209-174531_BBS.png
    And when it starts, it will stop the device from going into deep sleep (look at the "Awake (Screen off)" figures). This will drain the battery a lot faster than normal. See 210209-174541-log.zip for logs.

    However, I find that the wake lock will always start when the phone is fully recharged (I usually do this just before I go to bed). See 210209-174541-log.zip for logs.
    Screenshot_20210209-174523_BBS.pngScreenshot_20210209-202825_BBS.png

    Fortunately, a reboot gets rid of the wake lock.
    12
    I just built LOS 18.1 (see attached roomservice.xml for OP3/3T and OP5T) for testing (with the March security update - see attached screenshot).
    I successfully flashed LOS 18.1 on official LOS 17.1 via a dirty flash (wipe system/caches + flash build & MindTheGapps-11.0.0-arm64-20210220_140101).
    Note that I didn't flash Magisk and that safetynet passed (see attached screenshot - my BL is locked)
    Download :
    - Build 0312 : https://androidfilehost.com/?fid=2188818919693753932
    - MindTheGapp : https://wiki.lineageos.org/gapps.html

    Thanks for the great job @dianlujitao !
    DOWNLOAD:
    * Build type : unofficial ... daily or weekly ... it depends on LOS gerrit
    * Synced LineageOS sources
    * All credit goes to LOS Team and @dianlujitao
    ==> https://androidfilehost.com/?w=files&flid=323965&sort_by=date&sort_dir=DESC
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone