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

[$anket]

Wow !

Did you try via fastboot ?

fastboot erase userdata

Yeah I tried that. But since BL is locked, it throws "format failed" error. I guess my only option is to try unbrick tool.

 

[Eric_Lev]

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) ... ?

https://xdaforums.com/t/rom-official-nightly-lineageos-17-1-for-oneplus-3-3t.3990061/post-82169973

However I guess your only option is to try unbrick tool.

 

[$anket]

I never tried with a locked BL but via adb root (if USB debugging and Rooted debugging were enabled in dev options) ... ?

Sadly I enabled USB debugging only. I think it won't matter now as I have no os installed.

However I guess your only option is to try unbrick tool.

Yeah i hope it works.

 

[Hemuli]

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]

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)

 

[BillGoss]

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)

Of course the phone can't boot if you wipe the system partition!

 

[Eric_Lev]

Sadly I enabled USB debugging only. I think it won't matter now as I have no os installed.

Yeah i hope it works.

About your adb issue:

- Did you enable ADB in Advanced options of LOS recovery before applying from ADB ?

- Did you check your USB cable ?

- Does adb devices find your device ?

 

[$anket]

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.

 

[$anket]

Does adb devices find your device ?

Yeah device was getting detected in adb as well as fastboot.

By the way I solved the issue using Unbrick tool.

 

[johngare]

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]

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]

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]

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

boot image is not correctly resigned by addon.d · Issue #2013 · topjohnwu/Magisk

due to investigation of some members(see posting), the issue was found that addond is not correctly resigning the bootimage

github.com

would this help in this case too?

 

[an0ndr0id]

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

 

[an0ndr0id]

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:

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?

 

[JoniKatita]

Hello,

Cannot access TTS. When I try to configure it, it crashes the settings app.
Is this a known issue? Any fix?

Thanks

 

[BillGoss]

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]

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.

 

[votz11]

My bootloader is unlocked as well. But I keep getting that same Magisk error followed by bootloop.

install magisk.apk like normal app , work for me at least

 

[BillGoss]

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:

! 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.