As title says, but we need a working backup. Mine is broken, can someone upload a working one, plz?
This is the howto:
1. Flash a stock image (I used the August stock image MTC20F)
2. Fastboot flash TWRP 3.0.2-0
3. Boot into TWRP
4. Select Wipe -> Advanced Wipe -> Select and repair each partition individually (some won't be able to, and that's fine, just move on to the next one)
5. Restore a full nandroid backup (make sure everything is selected) and reboot
6. You should now be free of the never ending boots, and if your device is bootlooped at this point (stuck at the boot animation), you can just flash stock again.
Thanks for this solution. But I have a problem because after installing the rom file .tot have a locked bootloader, and at this moment I can not do flash twrp.
In order to unlock the bootloader command "fastboot oem unlock" I get the answer that it is not possible. NTR it can not unlock it.
Goes some way to upload twrp with a locked bootloader or a way to unlock?
Danielf85 said:
Thanks for this solution. But I have a problem because after installing the rom file .tot have a locked bootloader, and at this moment I can not do flash twrp.
In order to unlock the bootloader command "fastboot oem unlock" I get the answer that it is not possible. NTR it can not unlock it.
Goes some way to upload twrp with a locked bootloader or a way to unlock?
Click to expand...
Click to collapse
My bootloader is locked, too. The only way to write to the phone seems to be via download mode, but flashing LGH790AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot doesn't work...
To install twrp we need to unlock the bootloader.
However, when the command "fastboot oem unlock" system gives the answer
FAILED (remote: oem unlock is not allowed)
Then how to unlock?
Danielf85 said:
To install twrp we need to unlock the bootloader.
However, when the command "fastboot oem unlock" system gives the answer
FAILED (remote: oem unlock is not allowed)
Then how to unlock?
Click to expand...
Click to collapse
There's really nothing you can do to force an unlock. If you can adb sideload a full OTA zip (say for 7.0) from Google and get that to boot up, that's pretty much your best bet.
Sent from my Nexus 5X using Tapatalk
I mean, the new unlock command is:
fastboot flashing unlock
oc2 said:
I mean, the new unlock command is:
fastboot flashing unlock
Click to expand...
Click to collapse
On Nexus 5X both commands can be used (oem unlock and flashing unlock)
I followed all the steps except I can't boot to recovery...when I try (manually via ADB or automatically using Wug's tool) it just goes back into the bootloop. I can't even boot temporarily to recovery (without flashing). I'm getting close to throwing in the towel...
Did not work for me, sadly
Edit: Here's how I managed to fix the problem
1. Moved Nandroid backup to PC.
2. Download factory image MTC20F from https://developers.google.com/android/nexus/images.
3. Install factory image (This will erase all data on your phone so move your files to your PC).
4. Install TWRP 3.0.2-0 from https://dl.twrp.me/bullhead/twrp-3.0...lhead.img.html via fastboot.
5. Go in TWRP>Wipe>Advanced Wipe and repair all partitions that can be repaired (System, Data, Cache).
6. Restore Nandroid backup.
7. Success.
Hope it works for other people too, cheers
Anyone in Portland Oregon and want to take a crack at unbricking my 5x? LG gave me an RMA, but given it's not a hardware issue, I'm thinking it will be a waste of time to send it in -- I'm worried they'll just say "all your hardware is fine". Happy to buy drinks or pay a bit if someone can get me up and running.
Related
Hello all,
I have Zenfone 2 on which I intended to use a custom ROM.
So the first thing was to unlock the bootloader.
On previous occasion, on my Nexus, I had used the - fastboot oem unlock - command and it had worked. So with that in mind, I booted into the bootloader and tried the command, but it failed - saying oem command unrecognized.
Then I searched online and apparently, to unlock the bootloader, Asus has launched an app! But to be able to install the app, I need to get a normal boot happening, which is not happening now.
In between all this, I tried the commands - fastboot flash recovery <recovery.img>, fastboot flash boot <boot.img> too. But none of these were successful, and each of them returned a 'Permission denied' message, probably coz the bootloader was locked.
Now the situation is that -
- Bootloader is locked.
- Phone is stuck in bootloader
- There is no recovery installed. In fact, from the bootloader, when I try to boot into 'Recovery Mode', it goes there for a second and returns back to the bootloader. Doesn't show the normal android image with a 'X' on top.
- There is no root access.
Now I think the first step is to get root access, and for this I want to try the method with installing CWM recovery and SuperSu.
But for this, I need to be able to push the SuperSu.zip to the phone, which I am not able to.
Can somebody please help!
r the drivers for fastboot & adb update to date?
Android version?
If the phone is stuck in bootloader, you can use Asus Flash Tool to flash .raw files and unbrick the phone.
Raw files: https://yadi.sk/d/FijRoAVJtvRiG
AFT: https://yadi.sk/d/NQCiY--IsQjBr (I use AsusFlashToolInstaller1.0.0.14.exe).
you can use Asus Flash Tool to flash .raw files and unbrick the phone.
Click to expand...
Click to collapse
Have to choose wipe the data or not?
hafiz019 said:
Have to choose wipe the data or not?
Click to expand...
Click to collapse
stay away from aft. if will f**k up yor device completely. AFT is too unstable. lot of times it bricks the device to unrecoverable state. tell me the bootloader version, ifwi version shown on screen while in bootloader mode.
HI everyone,
I updated "successfully" from Kitkat to 5.0.2 on my rooted (stock ROM) Nexus 7 second gen.
Unfortunately, when I tried to upgrade to 5.1 everything seem to be normal until the device rebooted and it went through the "update process". 3/4 the way through, the green droid went on his back and the "ERROR" message appeared.
I wiped the cache partition but that doesn't help. I tried to download the update in safe mode, but no success. I also find it odd that each time I reboot my device, I get a message from Android that it is "updating my apps".
If I didn't have any apps and a lot of data on my Nexus, I would wipe the device clean but I'd rather avoid this, if at all possible.
Is there a way to upgrade to 5.1 or reinstall 5.0.2 without losing everything?
Thanks
Michael Carleone said:
Is there a way to upgrade to 5.1 or reinstall 5.0.2 without losing everything?
Click to expand...
Click to collapse
No problem. As you rooted it before then presumably it is unlocked and equipped with custom recovery, so all you have to do is:
boot TWRP
connect PC
transfer data and APKs to PC
flash OS
If you don't have TWRP installed, then boot it like this fastboot boot twrp-3.0.2-0-flo.img
k23m said:
No problem. As you rooted it before then presumably it is unlocked and equipped with custom recovery, so all you have to do is:
boot TWRP
connect PC
transfer data and APKs to PC
flash OS
If you don't have TWRP installed, then boot it like this fastboot boot twrp-3.0.2-0-flo.img
Click to expand...
Click to collapse
Hi,
Thanks for the reply. I rooted with Kingroot. I don't believe I have a custom recovery. The bootloader is locked as shown when I boot into recovery mode.
I want to avoid transferring my data and APK files to my PC.
Should I assume there is no way of reinstalling the OS without wiping out the device?Also, there is no link in the above quote: fastboot boot twrp-3.0.2-0-flo.img
Since I got no other replies, I went and restored to factory image. I do have another question. I hope I get a better response there: http://forum.xda-developers.com/nex...a/nexus-7-2013-wifi-root-marshmallow-t3515072
Thanks for the reply.
Can we compare using fastboot flashing TWRP vs Nexus Root Tool Kit: http://www.wugfresh.com/nrt/? I ended up using this utility instead because it was pretty much one click and it didn't require command lines and for whatever reason, I found instructions using fastboot a bit confusing. Which method is better or has more advantages? I left my bootloader unlocked.
Incidentally, I think there was something wrong with my Nexus image. As a result, I did use Google's instructions on how to flash etc. the OEM image. Instructions weren't ideal but I managed to figure things out: https://developers.google.com/android/images
The instructions are here which I assume would be similar if I wanted to fastboot TWRP?
To flash a system image:
Download the appropriate system image for your device below, then unzip it to a safe directory.
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
Using the adb tool: With the device powered on, execute:
adb reboot bootloader
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device. For example, to put a Nexus 5 ("hammerhead") into fastboot mode, press and hold Volume Up + Volume Down + Power as the device begins booting up.
If necessary, unlock the device's bootloader by running:
fastboot flashing unlock
or, for older devices, run:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal and navigate to the unzipped system image directory.
Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
fastboot flashing lock
or, for older devices, run:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Click to expand...
Click to collapse
Also, I could've sworn that when I rooted KitKat on my Nexus, my data wasn't wiped out. I don't recall doing anything to the bootloader. I can't recall which method I used, but I know for certain I didn't use the Nexus Root Toolkit. I should've recorded my steps when I rooted.
i rooted my nexus 7 using towel root on kitkat .. i unrooted using supersu... and ota untill marhsmallow with out a problem never use kingroot as its so un stable.
So I tried to flash another rom by flashing TWRP and unlocking the bootloader, which worked and I then had installed Freedom Os. Then I locked the Bootloader to get the Message away, but know when you charge it or turn it on it is in an boot loop which repeats the Oneplus Logo what you normally see, but very short and after that it bobrates turns the screen off and it atart again. Or I can go into fastboot mode, but when I try to go into the recovery, it goes into the Boot Loop again. Is there a way to get the Original OS back? Ive already dopwnloaded it but I cant get in on there. Can you tell me how to fix it on my own?
[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 3 > METHOD 1
If you can access fastboot mode, connect the phone to a PC, then go to ADB and erase recovery using the command " fastboot erase recovery" and install TWRP 3.0.4-1 using the command " <fastboot flash recovery <recovery.zip/img> again.
Once you do that, boot into TWRP, go to wipe and wipe everything. Once you do that, transfer the stock OOS into the internal memory using copy-paste , then go to install , select the transferred file to install the OS or else go to advance setting in TWRP and select adb sideload and use the command "adb sideload <filename.zip>".
This should install the OS on the phone.
If you want to go complete stock, then you also need to install the stock recovery. Search the forum to get the relevent files or else you can download it from the OnePlus website and later on update to latest OS via OTA.
NEVER EVER LOCK THE BOOTLOADER , IF YOU'RE USING ANY ROM OTHER THAN STOCK OS AND STOCK RECOVERY
anup807 said:
If you can access fastboot mode, connect the phone to a PC, then go to ADB and erase recovery using the command " fastboot erase recovery" and install TWRP 3.0.4-1 using the command " <fastboot flash recovery <recovery.zip/img> again.
Once you do that, boot into TWRP, go to wipe and wipe everything. Once you do that, transfer the stock OOS into the internal memory using copy-paste , then go to install , select the transferred file to install the OS or else go to advance setting in TWRP and select adb sideload and use the command "adb sideload <filename.zip>".
This should install the OS on the phone.
If you want to go complete stock, then you also need to install the stock recovery. Search the forum to get the relevent files or else you can download it from the OnePlus website and later on update to latest OS via OTA.
NEVER EVER LOCK THE BOOTLOADER , IF YOU'RE USING ANY ROM OTHER THAN STOCK OS AND STOCK RECOVERY
Click to expand...
Click to collapse
Can you tell me how to go to adb? When doing it while being in fastboot I get the error "remote: Partition erase is not allowed"
revedar said:
Can you tell me how to go to adb? When doing it while being in fastboot I get the error "remote: Partition erase is not allowed"
Click to expand...
Click to collapse
Download Universal ADB software, download the latest version and install it.
TWRP 3.0.4-1
Official Oxygen OS 4.0.3
Official Recovery
Connect your phone to the PC and then navigate to installed folder, right click holding SHIFT key and select "Open command window here"
Inside command window type
adb devices
If all the drivers are installed properly, you should see you're device ID here.
then type
adb reboot bootloader
your phone will enter fastboot mode.
then type
fastboot devices
again you should see you're device ID here.
then follow the instruction , i've given earlier.
anup807 said:
Download Universal ADB software, download the latest version and install it.
TWRP 3.0.4-1
Official Oxygen OS 4.0.3
Official Recovery
Connect your phone to the PC and then navigate to installed folder, right click holding SHIFT key and select "Open command window here"
Inside command window type
adb devices
If all the drivers are installed properly, you should see you're device ID here.
then type
adb reboot bootloader
your phone will enter fastboot mode.
then type
fastboot devices
again you should see you're device ID here.
then follow the instruction , i've given earlier.
Click to expand...
Click to collapse
So i've downloaded the software, installed the driver and typed in cmd adb devices "adb devices List of devices attached" is returned, so it seems like there is going something wrong. Is it because the Driver is installed wrong or because "target reported max download size of 440401920 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.528s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.551s"
This is returned when trying to flash. Do I have to be in fastboot mode or something else to be able to follow your instructions? In Fast Boot is written that the Device State is locked and Secure Boot is enabled. I messaged Oneplus and hope they have a solution which can just unlock the Bootloader when being in fastboot mode, so everything is fine again. I hope you can help me, but I still wanna say thank your for now
Errr... fastboot can unlock the bootloader. fastboot oem unlock
emuandco said:
Errr... fastboot can unlock the bootloader. fastboot oem unlock
Click to expand...
Click to collapse
Thank you, but it dont works because i forgot to re-enable the oem modification and usb debugging in freedom os, maybe there is an option to do this without having this enabled but I didnt found it. So I wait for a helpful answer from somebody here or from Oneplus, I consider sending my smartphone to oneplus to let them repair it if I cant do it. Just saying that modding an S3, Asus transformer pad and nvidia shield is way easier.
never ever relock your bootloader while you in custom OS
oopstairs said:
never ever relock your bootloader while you in custom OS
Click to expand...
Click to collapse
Thank you for not helping me
revedar said:
Thank you for not helping me
Click to expand...
Click to collapse
Yeah I'm sorry I can't help you in your case. I'm just stating the fact. Sorry if I offended you.
Shouldn't it still be possible to reflash the properly signed official updates? TBH I never had such a problem and thus never had to cope with it. Same with recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img Try flashing this one with fastboot. It's the official one. By flashing this one you might fix your stuff over adb sideloading the official full update zips.
Try the unbrick guide provided in the 2nd post to your query. It should definitely help. Better contact OnePlus tech2 support and they'll flash your phone for you. They're really helpful.
emuandco said:
Shouldn't it still be possible to reflash the properly signed official updates? TBH I never had such a problem and thus never had to cope with it. Same with recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img Try flashing this one with fastboot. It's the official one. By flashing this one you might fix your stuff over adb sideloading the official full update zips.
Click to expand...
Click to collapse
I already tried to do this, but the console returns something like permission denied.
anup807 said:
Try the unbrick guide provided in the 2nd post to your query. It should definitely help. Better contact OnePlus tech2 support and they'll flash your phone for you. They're really helpful.
Click to expand...
Click to collapse
The MSM Software disconnects the smartphone while the process works
U cannot flash in adb while the bootloader is locked, u can not unlock the bootloader unless u can access ur OS, I am not sure y people was trying to get u to flash via fastboot the answer was provided to u in the 2nd post
^^^ This!
It's pretty much obvious fastboot flash will not work with a locked bootloader.
It's pretty obvious unlocking the bootloader will not work, while one can not access the OS.
Unbrick tool is the only option to bring it back to life, or sending it for RMA. If unbrick tool fails, try using different drivers and make sure it is connected with the stock cable (I've only tried with a Nilkin cable besides the stock one, which always failed at different stages during the process).
Not even sure drivers must be installed manually, I've never done that myself on Windows 10, as they were automatically installed (3 different's PC's, both on x86 and x64).
Which version of stock firmware did you last have? If it was 4.0.1 or earlier, then you can use
Code:
fastboot oem 4F500301
to issue a flash command even without unlocking the bootloader. If you are on that, then use that command and flash stock recovery and then flash stock zip.
rk2612 said:
Which version of stock firmware did you last have? If it was 4.0.1 or earlier, then you can use
Code:
fastboot oem 4F500301
to issue a flash command even without unlocking the bootloader. If you are on that, then use that command and flash stock recovery and then flash stock zip.
Click to expand...
Click to collapse
I had the most recent update installed. Is there a similar command at the moment?
revedar said:
I had the most recent update installed. Is there a similar command at the moment?
Click to expand...
Click to collapse
Don't think so.
Hi,
I'm new to Z2 play ROM/TWRP things and here's my issue on a XT 1710-01 (on retca channel):
After unlocking my bootloader, I've installed TWRP 64 bits and did a backup before doing anything else, but for whatever reason, restoring it didn't work. I just thought then that I could re-flash the retail stock ROM available at https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/ , which worked fine (phone boots fine, works fine and is still on retca channel, etc.), except that now, I'm unable to re-lock the bootloader, as I get a message like "signed boot.img required" (or something alike) on "fastboot oem lock" command.
I also get the "bad key" message on the unlock warning at boot time (see attached).
Here are the commands I used to reflash the stock ROM:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
Now, I'm just wondering if I missed something or is it just that the stock ROM I reflashed is not the good one (or just unsigned) . Any help would be appreciate.
Thanks.
Need official signed by Moto image. Not available from any official source unfortunately. I have a same request to lock a bootloader.
it's very important to ask how your parachute Works before you jump off the plane
@KirMit Thanks for the follow-up.
Do you know if it would be an option for me to try to find a complete ROM/backup made by someone with the exact same model (so presumably, with the signed boot.img), flash/restore this backup on my unit and then try to relock the bootloader?
I have the same problem. Cannot find a signed boot.img
If anyone can think of a solution I would be totally interested in hearing about it.
I can live with this phone with the bootloader unlocked, but I may need to sell it, so I need to get rid of that warning screen.
Paulinga said:
I have the same problem. Cannot find a signed boot.img
If anyone can think of a solution I would be totally interested in hearing about it.
I can live with this phone with the bootloader unlocked, but I may need to sell it, so I need to get rid of that warning screen.
Click to expand...
Click to collapse
You can get rid of the warning screen, but you can't get rid of the N/A-Bad Key sign, so you must make your own boot logo (meant to cover those nasty letters with a white background) and ADB flash it as logo.bin... that's if you don't have TWRP recovery; in such case you can use a flashable zip for that matter.
Sent from my Moto Z2 Play using XDA Labs
Please look at this video:
It's in portuguese, but you will understand by just following his steps.
If you want, look at the other videos, all of them will help you(not all are about relocking bl)
If you're on october patch, there is the firmware: https://androidfilehost.com/?fid=11410932744536987421
Thanks to junior passos
xdaVTU said:
Please look at this video:
It's in portuguese, but you will understand by just following his steps.
If you want, look at the other videos, all of them will help you(not all are about relocking bl)
If you're on october patch, there is the firmware: https://androidfilehost.com/?fid=11410932744536987421
Thanks to junior passos
Click to expand...
Click to collapse
Doesn't work on my Z2p. My oem unlock is always greyed out even after trying the instructions in this video with 3 different firmwares.
For anyone who doesn't understand what's going on in the video.
1)flash the firmware.
2)flash twrp, backup boot & system.
3) restore boot and system and reboot
4) go to developer options and, enable oem unlocking
5) return to bootloader and run the lock bootloader bat file.
6)done your locked.
Or if like in my case, it does not work, oem unlocking is still greyed out.
I managed to ungrey oem unlocking but, only by flashing magisk. Somehow magisk ungreys oem unlock? Unfortunately, we cannot lock bootloader with magisk installed. Once magisk is uninstalled, oem unlocking is greyed out again?
I think I know how to get around this, adb pull boot.img that magisk has modified. Full unroot magisk, preferably with magisk uninstall zip. Then fastboot flash the patched boot image and run bootloader lock with the OEM unlock switch set.
---------- Post added at 10:32 PM ---------- Previous post was at 09:49 PM ----------
And I am locked, it worked. I now know how to lock my bootloader even when the video guide above fails to remove the greyed out oem switch.
1)flash the firmware.
2)flash twrp, backup boot & system.
3) restore boot and system
4)flash magisk and reboot
6) back up boot.img to pc
7) flash magisk uninstall zip
8)fastboot flash stock recovery
9) fastboot flash magisk modified boot
10)boot device and enable oem unlocking
11) reboot to bootloader and run bootloader lock bat file
11) oem locked!
By the way, easiest way to back up boot is use the app "partition backup & restore". Be sure to change the setting to save as img and not archive.
Yes! This!
I've never been able to go back to stock and relocking the bootloader because the OEM Unlock was always greyed out. Using the patched boot.img, as @Cupcake 1.5 explains allowed me to lock my bootloader again.
Thank you!
Cupcake 1.5 said:
I managed to ungrey oem unlocking but, only by flashing magisk. Somehow magisk ungreys oem unlock? Unfortunately, we cannot lock bootloader with magisk installed. Once magisk is uninstalled, oem unlocking is greyed out again?
I think I know how to get around this, adb pull boot.img that magisk has modified. Full unroot magisk, preferably with magisk uninstall zip. Then fastboot flash the patched boot image and run bootloader lock with the OEM unlock switch set.
---------- Post added at 10:32 PM ---------- Previous post was at 09:49 PM ----------
And I am locked, it worked. I now know how to lock my bootloader even when the video guide above fails to remove the greyed out oem switch.
1)flash the firmware.
2)flash twrp, backup boot & system.
3) restore boot and system
4)flash magisk and reboot
6) back up boot.img to pc
7) flash magisk uninstall zip
8)fastboot flash stock recovery
9) fastboot flash magisk modified boot
10)boot device and enable oem unlocking
11) reboot to bootloader and run bootloader lock bat file
11) oem locked!
By the way, easiest way to back up boot is use the app "partition backup & restore". Be sure to change the setting to save as img and not archive.
Click to expand...
Click to collapse
TravellingGuy said:
Yes! This!
I've never been able to go back to stock and relocking the bootloader because the OEM Unlock was always greyed out. Using the patched boot.img, as @Cupcake 1.5 explains allowed me to lock my bootloader again.
Thank you!
Click to expand...
Click to collapse
Hi all, ok i'm late unfortunately can you help me ? i have the boot magisk signed and key is ok. But when i'm reflashing recovery stock, there is also a bad key.
So there is still the warning at startup, i think this is due to this issue
smbld said:
Hi all, ok i'm late unfortunately can you help me ? i have the boot magisk signed and key is ok. But when i'm reflashing recovery stock, there is also a bad key.
So there is still the warning at startup, i think this is due to this issue
Click to expand...
Click to collapse
Ha, it's been too long since I used this phone. I can't help, unfortunately.
Hello all
I desperately try to relock my bootloader but failed many times and I am shortly before giving up. I was once on a locked bootloader on LOS but camera didn't work. (Couldn't reproduce)
Maybe you see something I missed out / didn't understand.
The main reason is, that some apps like ebanking check the state of the bootloader. And they also don't go through Securenet because of huawei.
So what I tried with this setup:
sign both boot.img and twrp.img with BootSignature.jar using own private key
Twrp Using: twrp-3.5.2_9-0-oneplus3
boot img from:
lineage-17.1-20210330-microG-oneplus3
lineage-18.1-20210403-microG-oneplus3
With firmware: oxygenos-9.0.6-firmware-3 from https://github.com/nvertigo/firmware-3t/tree/master/archive/op3
Mostly I got the ideas from https://forum.xda-developers.com/t/device-forum-rules-please-read-before-posting.3333345/
And what I do is this:
Using fastboot flash signed recovery
boot into recovery
whipe everything (is this needed every time?), data, factory reset, all partitions except internal & usb
reboot into recovery
sideload lineageos with signed boot.img inside
fastboot oem unlock => directly restarts after 'yes'
boot into LOS
fastboot oem unlock => directly restarts after 'yes' again
Do you see something I do wrong? Should I use other versions/files?
Hope to find a way
Edit: Also I can go back to stock where it gets locked again using the latest OnePlus3_16_A.86_191104_repack.