Develop Bugs

Oneplus 3 Bricked - Unbrick doesn't work...

Hello guys,
my Oneplus 3 is hard bricked, I tried the methods in the Mega Unbrick guide, my device already gets shown as Qualcomm 9008 ... in Device Manager, so I started the MSM DownloadTool and it flashed anything without errors. But when the phone reboots I get a black screen and the white led is on.
I can't even boot to stock recovery (Volume down + power doesn't work and rebooting to recovery through fastboot doesn't work, too....) my bootloader is locked and all attempts to unlock the bootloader are failing with the error "remote: oem unlock is not allowed"
So at the moment I'm stuck in fastboot and nothing else works -.-
Can someone please help me?
The unbrick tool has an old firmware, can I replace the files with files from a newer firmware?
Thanks!

Have you tried the exact steps from Method 2? Maybe unzip it? If that doesn't work which is highly unlikely then there is not much you can do.

Puddi_Puddin said:
Have you tried the exact steps from Method 2? Maybe unzip it? If that doesn't work which is highly unlikely then there is not much you can do.
Click to expand...
Click to collapse
Yeah I tried it as I said, the MSM DownloadTool showed me Completed and the phone tried to boot up after that.
I'm now contacting the OP Customer Support, I've read a few times that they have other files to unbrick the phone with the MSM Tool.

min-dfreak said:
Yeah I tried it as I said, the MSM DownloadTool showed me Completed and the phone tried to boot up after that.
I'm now contacting the OP Customer Support, I've read a few times that they have other files to unbrick the phone with the MSM Tool.
Click to expand...
Click to collapse
Ye thats the only thing you can currently do... May i ask what you have done how did it get bricked?

I just updated AICP ota and after flashing the update my phone didn't boot up. The screen went black immediately.
So I thought that it is maybe a Problem with the ROM and I tried to go back to stock.
Flashed the stock recovery and locked the bootloader, but I couldn't boot to the stock recovery.
There it started...

Switch off the phone, connect usb ,open unbrick tool full ( method 2),Press vol up,down and power buttons same time ,tool will recognize phone then start , you must unbrick now.
NEVER LOCK YOUR PHONE.

drmuruga said:
Switch off the phone, connect usb ,open unbrick tool full ( method 2),Press vol up,down and power buttons same time ,tool will recognize phone then start , you must unbrick now.
NEVER LOCK YOUR PHONE.
Click to expand...
Click to collapse
Please read, I already did that.
The tool completed it successfully, but still black screen after a reboot.
Only the LED is flashing white.
I already contacted the support, they will do it remotely tomorrow.

min-dfreak said:
Please read, I already did that.
The tool completed it successfully, but still black screen after a reboot.
Only the LED is flashing white.
I already contacted the support, they will do it remotely tomorrow.
Click to expand...
Click to collapse
Never but never lock your bootloader...

If recovery, boot or system partition is modified. There's no harm in re locking otherwise..

Hi guy i have a big problem i buy a one plus 3 i was using it 1 month and there was a update i don't remember what it was oreo or nougat when the update downloaded i install it and the i got a bootloop 2 hours didn't boot and my device is not rooted and didn't enable developer option i tried to install stock rom by adb and fastboot with sideload it load but it stuck on 50% then it say failed tried to install recovery in fastboot i installed drive oneplus 3 ect but can't flash it i think because i have oem locked i trien to unlocked it says failed 00.6s ect and i don't have guarantee i have dash and cable charger i can charge it and go to fastboot and recovery but when i boot my phone normally i show logo one plus then the two red bullet who move then it power off

Dsn Fouad said:
Hi guy i have a big problem i buy a one plus 3 i was using it 1 month and there was a update i don't remember what it was oreo or nougat when the update downloaded i install it and the i got a bootloop 2 hours didn't boot and my device is not rooted and didn't enable developer option i tried to install stock rom by adb and fastboot with sideload it load but it stuck on 50% then it say failed tried to install recovery in fastboot i installed drive oneplus 3 ect but can't flash it i think because i have oem locked i trien to unlocked it says failed 00.6s ect and i don't have guarantee i have dash and cable charger i can charge it and go to fastboot and recovery but when i boot my phone normally i show logo one plus then the two red bullet who move then it power off
Click to expand...
Click to collapse
I'm assuming your device is OnePlus3 and not 3T
Okay. Firstly give a try to Oneplus3 openbeta Nougat special edition.
Oneplus3 : http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Method 1 : specific recovery for open beta24 available in Oneplus downloads
https://downloads.oneplus.com
Find legacy roms and find openbeta 24
Method 2: latest TWRP
If your bootloader is locked this isn't gonna work. But if it is still in unlocked .
Download TWRP for Oneplus3 from official TWRP site
Flash the recovery you choose using fast boot.
Now using asn command, try to flash the special edition.
Mostly this solves your issue. It helped me.
Let me know whether you face any issues.
Note: in this method you may lose every data you have on the phone. It boots up (if at all ? ) with fresh firmware and fresh storage (sometimes)

SivaMaxwell said:
I'm assuming your device is OnePlus3 and not 3T
Okay. Firstly give a try to Oneplus3 openbeta Nougat special edition.
Oneplus3 : http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Method 1 : specific recovery for open beta24 available in Oneplus downloads
https://downloads.oneplus.com
Find legacy roms and find openbeta 24
Method 2: latest TWRP
If your bootloader is locked this isn't gonna work. But if it is still in unlocked .
Download TWRP for Oneplus3 from official TWRP site
Flash the recovery you choose using fast boot.
Now using asn command, try to flash the special edition.
Mostly this solves your issue. It helped me.
Let me know whether you face any issues.
Note: in this method you may lose every data you have on the phone. It boots up (if at all ? ) with fresh firmware and fresh storage (sometimes)
Click to expand...
Click to collapse
Yeah i have oneplus 3 my bootloader is locked can't flash anything im going to try method 1
By the way why beta 24 why not lastest update ? And whene i download it do you want me to flash it with sideload like #adb sideload openbeta24.zip ?

Dsn Fouad said:
Yeah i have oneplus 3 my bootloader is locked can't flash anything im going to try method 1
By the way why beta 24 why not lastest update ? And whene i download it do you want me to flash it with sideload like #adb sideload openbeta24.zip ?
Click to expand...
Click to collapse
The file I gave link to is a special edition by Oneplus for Openbeta-Nougat. You can go to Nougat from any rom.
Rom: http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Specific recovery should be downloaded from Oneplus website.
You can sideload using adb or store internal storage and flash.
I tried with latest TWRP recently and it worked.
Note that all your data gets wiped if you use oneplus-recovey and asn sideload

SivaMaxwell said:
The file I gave link to is a special edition by Oneplus for Openbeta-Nougat. You can go to Nougat from any rom.
Rom: http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Specific recovery should be downloaded from Oneplus website.
You can sideload using adb or store internal storage and flash.
I tried with latest TWRP recently and it worked.
Note that all your data gets wiped if you use oneplus-recovey and asn sideload
Click to expand...
Click to collapse
The problem is i dont have store internal storage and when i try to flash anything it say oem locked not allowed and when i flash a rom with adb sideload jfjd.zip it stuck on 60% will it be complete if i use your beta ?

Dsn Fouad said:
The problem is i dont have store internal storage and when i try to flash anything it say oem locked not allowed and when i flash a rom with adb sideload jfjd.zip it stuck on 60% will it be complete if i use your beta ?
Click to expand...
Click to collapse
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery

SivaMaxwell said:
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
Click to expand...
Click to collapse
Thanks i will download and give it a try

SivaMaxwell said:
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
Click to expand...
Click to collapse
Before that i downloaded msm download tool 3.0.8 i tested it and it boot but it say enter pin password i dont know what is the pin i didn't use a pin before it was working

Dsn Fouad said:
Before that i downloaded msm download tool 3.0.8 i tested it and it boot but it say enter pin password i dont know what is the pin i didn't use a pin before it was working
Click to expand...
Click to collapse
Simply reboot to recovery and say yes to wipe every data.
Note1:
all your internal data is wiped in the method I suggested. I can recall there is a method to recover data only if bootloader is unlocked. If your bootloader is locked there is no other way.
Note2: your data will be formatted to f2fs file system. If you want to flash any custom ROM, YOU SHOULD CHECK COMPATIBILITY WITH F2FS in that ROM forums.
It's better to always have EXT4 file system. You can change this file system with TWRP

SivaMaxwell said:
Simply reboot to recovery and say yes to wipe every data.
Note1:
all your internal data is wiped in the method I suggested. I can recall there is a method to recover data only if bootloader is unlocked. If your bootloader is locked there is no other way.
Note2: your data will be formatted to f2fs file system. If you want to flash any custom ROM, YOU SHOULD CHECK COMPATIBILITY WITH F2FS in that ROM forums.
It's better to always have EXT4 file system. You can change this file system with TWRP
Click to expand...
Click to collapse
Bootloader is locked i tryed to flash the 24 beta yoi give me but it stuck on 47 and say failed im just going to sell it

Dsn Fouad said:
Bootloader is locked i tryed to flash the 24 beta yoi give me but it stuck on 47 and say failed im just going to sell it
Click to expand...
Click to collapse
Even if the bootloader is locked, you can boot into the current rom and unlock simply by going to advanved options.
It is a very simple process.

[Q] How to restore Xperia XA2 stock boot image?

Hi!
I have a problem with my new Sony Xperia XA2. When I got my new phone I decided to flash LineageOS 16.0 (the unofficial build from LuK1337), however the Lineage-build is not the problem. I got the problem when I tried to flash TWRP and Magisk, and I've realised that I did it too quick.
Here's what I did:
0. Unlocked bootloader
1. Booted TWRP
2. Flashed LineageOS
3. Flashed GAPPS.
4. Flashed Magisk.
So far, so good. This worked.
5. Decided to flash TWRP to get rid of the standard recovery.
6. Now both the standard recovery and TWRP seems to be gone.
Is there a way to revert to the standard recovery? I've tried to download FlashTool and XperiFirm, and I've downloaded the correct stock image for my Xperia XA2 Dual (H4113), but I cannot get it to only flash the bootloader.
My understanding is that the recovery and bootloader resides on the same partition. Is this correct?
When I try to flash the bootloader with FlashTool, I get an error stating that the device is identifying as H3113, which is the single-sim-version.
Thank you for the help!

I managed to get my phone working again by using Emma, as I had managed to soft-brick my phone. The bootloader said that the phone was corrupt, and turned off after 5 seconds. Using Emma and the bundled USB-C-USB-A-cable did the trick for me.
Now I'm going to install TWRP once more, and hopefully I'll manage it correctly this time.

My understanding is that we cannot install TWRP as a replacement recovery on this device because there is no true recovery partition. It's part of the boot partition. Hopefully someone will come along and correct me if I'm wrong.

You can install twrp on a/b devices. However, it installs to /boot. Thus every upgrade kills it. Which really sucks as lineage recovery sucks bad.

hjahre said:
Hi!
I have a problem with my new Sony Xperia XA2. When I got my new phone I decided to flash LineageOS 16.0 (the unofficial build from LuK1337), however the Lineage-build is not the problem. I got the problem when I tried to flash TWRP and Magisk, and I've realised that I did it too quick.
Thank you for the help!
Click to expand...
Click to collapse
Hello,
sorry for the delay.
You can use EMMA to flash back the stock firmware, however if you don't want your data lost, use flashtool ( http://flashtool.net ) and make sure your userdata is Wipe Excluded

what is the trick of USB-C-USB-A
Hello friend, what is the trick of USB-C-USB-A, can you explain it, because I can not get flashtools to work on my sony xa2, explain me the trick please

cristianrb said:
Hello friend, what is the trick of USB-C-USB-A, can you explain it, because I can not get flashtools to work on my sony xa2, explain me the trick please
Click to expand...
Click to collapse
There's really no trick to it. Just plug the cable bundled with the phone and plug it into your PC.
My problem was that I've got a Macbook Pro that only have USB-C ports. When I tried a cable with USB-C connectors in both ends, my phone would not let me flash from my computer. When I used the bundled cable and a USB-hub it worked as it should

Xa2 black screen and flickering after lineage os 16 installation and reboot

Hey guys,
i have a screen issue with my xa2, android 8.0:
I followed the steps from wiki.lineageos.org/devices/pioneer/install until subtopic ''Installing LineageOS from recovery, point 8 (optional step)'' and used ''adb reboot sideload'' to install gapps nano.
After the successful installation my phone rebooted not into TWRP but Lineage OS recovery.
I chose ''reboot system'' and since this step, my screen is all black aside from occasional vertical lines and flickering.
The screen occassionally shows white background with flickering and switches to black again.
Somehow i can still take screenshots and switch into flashmode.
I tried to run sonys flashtool ''Emma'' and try to reset it to a android stock ROM, but even after this successful step the black screen and flickering continues.
Can anyone help me?
[EDIT:]
My PC still recognizes my phone in adb devices and fastboot devices and i can still execute respective commands with cmd, but its mainly the screen which is black and hinders my work.

same here, still looking for a solution...

eviv-bulgroz said:
same here, still looking for a solution...
Click to expand...
Click to collapse
Does it matter which android version was installed on your devices prior to the LineageOS setup?
I had android 8.0.

same issue here. i stupidly upgraded my xa2 to android 8.0 then downgraded via sonys emma tool before following the procedure from the lineage wiki. all went well, i was able to boot and do stuff, although the camera was making problems, but all of sudden the screen turned flickery. maybe it has something to do with propietary drivers getting lost in the android 8.0 update process? now emma doesn't recognize the device. any ideas?

dooom808 said:
same issue here. i stupidly upgraded my xa2 to android 8.0 then downgraded via sonys emma tool before following the procedure from the lineage wiki. all went well, i was able to boot and do stuff, although the camera was making problems, but all of sudden the screen turned flickery. maybe it has something to do with propietary drivers getting lost in the android 8.0 update process? now emma doesn't recognize the device. any ideas?
Click to expand...
Click to collapse
I have the same problem...
Version Number of xa2: H3113
No luck with anything I tried (emma, newflasher, any twrp) with fastboot on linux mint or win 7 tools (emma newflasher).
Hope with time will come some solution...
Best regards,
tencarsb

Check this post: https://forum.xda-developers.com/showpost.php?p=79799244&postcount=930
it should solve your problem.

Moto Z Play has no OS

OK, so my Moto Z Play has no OS on it, and it boots into TWRP.
It's been awhile since I touched the phone since the part of the screen shattered, so I don't remember doing anything related to twrp on it.
Anyway, I want to know if there is any way to get it running again, or is it trash?

timster01 said:
OK, so my Moto Z Play has no OS on it, and it boots into TWRP.
It's been awhile since I touched the phone since the part of the screen shattered, so I don't remember doing anything related to twrp on it.
Anyway, I want to know if there is any way to get it running again, or is it trash?
Click to expand...
Click to collapse
Damn. That sucks. I guess you're in the same boat as me needing some help too.

If it boots to TWRP all you would need is a ROM on an SD card...
If you're looking to go back to stock try this guide: https://forum.xda-developers.com/moto-z-play/how-to/guide-motorola-z-play-xt-1635-02-t4063701

masivb said:
If it boots to TWRP all you would need is a ROM on an SD card...
If you're looking to go back to stock try this guide: https://forum.xda-developers.com/moto-z-play/how-to/guide-motorola-z-play-xt-1635-02-t4063701
Click to expand...
Click to collapse
Although I have had TWRP on an old device before, I know Android 8 and later doesn't like to be messed with. And Android 8 Oreo is what I want to update it to since it only had 6 now.
It's an XT1635-02 Internationa version that was sold in Mexico and has the attmx software channel. I of the understanding that the software channel doesn't really matter.
Can I update it with RSDLite through fastboot? And would "ADDISON_OPNS27.76-12-22-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" I got from androidfilehost.com be the correct firmware to update it with? Also the current baseband is "M8953_10203.02.04.42R ADDISON_ROW_CUST" with a build number of "MPN24.104-25". Does that make a difference?
I do appreciate someone finally trying to help. Thanks, Masiv.

masivb said:
If it boots to TWRP all you would need is a ROM on an SD card...
If you're looking to go back to stock try this guide: https://forum.xda-developers.com/moto-z-play/how-to/guide-motorola-z-play-xt-1635-02-t4063701
Click to expand...
Click to collapse
I was able to get a rom from alberto97 loaded, but want to go back to stock and am stuck at step 4 of your instructions
when trying to enter a fastboot command, the cmd window just sits on <waiting for device>. I'm not sure where to go from here.

timster01 said:
I was able to get a rom from alberto97 loaded, but want to go back to stock and am stuck at step 4 of your instructions
when trying to enter a fastboot command, the cmd window just sits on <waiting for device>. I'm not sure where to go from here.
Click to expand...
Click to collapse
If you're stuck on step 4 most likely OEM_Flashing is disabled
Type:
Code:
fastboot flashing unlock
to re-enable fastboot flashing and repeat step 4.
Edit:
<waiting for device> could be driver issue. re-install Moto usb drivers: https://support.motorola.com/us/en/drivers

moto z play does not switch on and it shows no os
hello sir,
i tried to install lineage os 17 for moto z play. it shows in twrp that updater process ended with error 7. so look up for what is problems solution. so i made some changes to transcript. but problem doesn't solve.
but after that i can switch on my phone. when carefully search my twrp. so when i click on reboot, it shows no os installed. and my phone doesn't open at all. it only shows your phone boot in 5 seconds. then black screen. after some time again it shows your phone boot in 5 seconds.
so i tried to install android pie version through sd card.and i download custom rom for that procedure.but again it end with updater process ended with error 7.
now i'm very bored, confused and whatnot. so i search for moto z play stock rom and so i can reinstalled my older version. so i look up your article about it.
but when i open cmd through your file and give command of fastboot. it shows no cmmand regarding fastboot.
so i'm stuck. please help me.
phone- MOTO XT1635-02
after go to work whrn return i see that my phone does not goes into fastboot mod.
it only blink white light on top.

masivb said:
If you're stuck on step 4 most likely OEM_Flashing is disabled
Type:
Code:
fastboot flashing unlock
to re-enable fastboot flashing and repeat step 4.
Edit:
<waiting for device> could be driver issue. re-install Moto usb drivers: https://support.motorola.com/us/en/drivers
Click to expand...
Click to collapse
Thank you. I was able to restore Android 8.0 onto the Z Play.

LunaEros said:
Although I have had TWRP on an old device before, I know Android 8 and later doesn't like to be messed with. And Android 8 Oreo is what I want to update it to since it only had 6 now.
It's an XT1635-02 Internationa version that was sold in Mexico and has the attmx software channel. I of the understanding that the software channel doesn't really matter.
Can I update it with RSDLite through fastboot? And would "ADDISON_OPNS27.76-12-22-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" I got from androidfilehost.com be the correct firmware to update it with? Also the current baseband is "M8953_10203.02.04.42R ADDISON_ROW_CUST" with a build number of "MPN24.104-25". Does that make a difference?
I do appreciate someone finally trying to help. Thanks, Masiv.
Click to expand...
Click to collapse
RDSLite I don't know enough about but I know it can hard brink your device if a flash goes wrong - I wouldn't recommend it.
That also sounds like a Marshmallow ROM. The latest stock on your phone is most like Noguat or Oreo bootloader so you won't be able to flash marshmallow so that explains why it wasn't working.
The easiest thing to do is download the April Oreo patch zip and use fastboot flash it back to stock from the link I posted previously. That should get you out of every scenario as it has been verified by me to work even from a bricked state back to stock.

It's all good. I was finally able to flash it up to 8.0.0. Thanks.

pankajr95 said:
moto z play does not switch on and it shows no os
hello sir,
i tried to install lineage os 17 for moto z play. it shows in twrp that updater process ended with error 7. so look up for what is problems solution. so i made some changes to transcript. but problem doesn't solve.
but after that i can switch on my phone. when carefully search my twrp. so when i click on reboot, it shows no os installed. and my phone doesn't open at all. it only shows your phone boot in 5 seconds. then black screen. after some time again it shows your phone boot in 5 seconds.
so i tried to install android pie version through sd card.and i download custom rom for that procedure.but again it end with updater process ended with error 7.
now i'm very bored, confused and whatnot. so i search for moto z play stock rom and so i can reinstalled my older version. so i look up your article about it.
but when i open cmd through your file and give command of fastboot. it shows no cmmand regarding fastboot.
so i'm stuck. please help me.
phone- MOTO XT1635-02
after go to work whrn return i see that my phone does not goes into fastboot mod.
it only blink white light on top.
Click to expand...
Click to collapse
Hello friends,
my motoz play has been hard brick for almost half year now.
i search what i can do for solution. but doing some research, i have able to unbrick my phone.
how it is i don't know.
but i can what i have done to go through problem.
i have download
1. moto device manager
2. minimal adb and fastboot version 1.4.3
4. qualcomm usb driver for windows
3. Rescue and Smart Assistant
4. blank flash file
so after installing Qualcomm USB driver, my device shows in divece manager......

Phone stuck in boot loop [solved] / LOS installation keeps failing [unresolved]

I guess the title already says it all, but just in case:
I tried to put LineageOS on this used XZ2 I bought a few days ago, everything went fine until side loading the Lineage image. Appaerently there as some data corruption and the installation failed halfway through... unfortunately the phone dropped out of recovery mode and has been stuck in a boot-loop ever since.
I can still access the phone via fastboot after the battery runs out and before it goes into its bootloop again, even managed to flash the recovery image (in boot_b if that's important) - but somehow seem unable to actually boot into recovery... given that I have still access via fastboot, the situation might still be salvageable?
also tried booting the phone-specific twrp via fastboot boot <twrp>.img but that sadly also sent me back into the boot loop.
fastboot reboot recovery also sends me to the bootloop
any other ideas?

Did you format (not wipe!) /data before booting LOS?

Thanks for the reply!
I followed these instructions but something failed at the end:
Install LineageOS on xz2c | LineageOS Wiki
wiki.lineageos.org
but later yesterday I was able to find somewhat of a work around. Since from browsing this forum many people seemed to have had similar issues, here is what worked for me:
- break out of the reboot-loop and shut down the phone by pressing and holding volume up + volume down + power button
- the phone should vibrate about 3 times to confirm
- download your phones standard firmware via xperifirm
[TOOL] XperiFirm ~ Xperia Firmware Downloader [v5.6.5]
[TOOL] XperiFirm ~ Xperia Firmware Downloader [v5.6.5] NOTE: This thread is the only official source of XperiFirm! Websites like xperifirm.com and xperifirmtool.com were not authorized to redistribute my software! XperiFirm... Allows you to...
forum.xda-developers.com
- download new flasher
[TOOL] Newflasher (xperia command line flasher)
Disclaimer: newflasher tool was made for testing and educational purposes, ME is not responsible for what you do on/with your device using newflasher, you must agree that you using newflasher on your own risk, I am not responsible if you brick...
forum.xda-developers.com
- put the phone into flashmode - press and hold volume down, connect the usb cable, and then also press and hold power, the phone should go into flash mode indicated by a green led
- follow the instructions (basically put the newflasher executable into the firmwarefolder created by xperifirm and execute
if everything goes well you should recieve a functioning (but wiped) device. still better than a paper weight
---------------------------------------------------------------
edit: tried to flash LOS again, but same error as first time (Error applying update: 28 (kdowloadoperationexecutionerror)
which prevents me from successfully installing LOS... I only found this:
[GUIDE][HOW TO FIX] 28 (ErrorCode::kDownloadOperationExecutionError) | 5 (ErrorCode::kPostInstallRunnerError)
In this short guide, I will explain to you how to easily fix the recovery error, the name of which can be found in the title. This guide is only a collection of information found on the Internet and a simple explanation of the problem. It was...
forum.xda-developers.com
which kinda explains the issue, but not how to fix it in my case on my device... any suggestions?
edit2:
tried over 10 different firm wars ranging from the latest 18.1 to some older 17.1, tried via the official lineageos recovery image and also via twrp.. always the same result... installation failed
I have been trying for over 3 hours now... but I just can't find (nor fix) the issue)

Hey so I was having this same issue and seem to have resolved it by doing a firmware upgrade using the oxygen firmware located here. I already have twrp installed and had no issues logging into the recovery, but i could never get logged into the system. Using twrp i just moved the oxygen file onto the phone and flashed it directly from the recovery. I then switched to the partition i installed it to and it booted up. It looks like i had everything right except for the firmware. Good luck!
[Download] Stable OxygenOS 11 For OnePlus 6/6T Based on Android 11
Stable OxygenOS 11 For OnePlus 6 and 6T just rolled out for OnePlus 6 and 6T. Download Android 11 based on OxygenOS 11 for OnePlus 6/6T.
www.androidsage.com

iitzzMalice said:
Hey so I was having this same issue and seem to have resolved it by doing a firmware upgrade using the oxygen firmware located here. I already have twrp installed and had no issues logging into the recovery, but i could never get logged into the system. Using twrp i just moved the oxygen file onto the phone and flashed it directly from the recovery. I then switched to the partition i installed it to and it booted up. It looks like i had everything right except for the firmware. Good luck!
[Download] Stable OxygenOS 11 For OnePlus 6/6T Based on Android 11
Stable OxygenOS 11 For OnePlus 6 and 6T just rolled out for OnePlus 6 and 6T. Download Android 11 based on OxygenOS 11 for OnePlus 6/6T.
www.androidsage.com
Click to expand...
Click to collapse
Hmmm.. I just realized you're using a different phone than me. My bad. Hopefully it helps that i had the same issue and resolved it by using oxygen firmware. Good luck to you!

thanks for the response
I think I identified the issue, which might be very much firmware related.
Essentially because my phone has the wrong stock firmware and LOS refuses to install on that despite being the same hardware as the "supported" firmware.
so what I probably need is a way to install H8314 firmware on an SO-05K model... there's a thread about that, but so far I have not been successful
(alternatively altering the LOS firmware itself to install on the SO-05K...)