Database Info

Cannot get ROMs to boot after installing from TWRP

I have had success flashing two ROMS (Lineage OS with MicroG and HavocOS) so far, but at some point, I am now getting nowhere fast trying to reinstall either of these after several clean attempts. I keep ending up at a black screen with a blue light and no more TWRP and no more bootable OS.
Here's what I did...
Starting fresh... Used MSMDownloadTool V4 to install OOS (enchilada_22_O.09_180517) then updated with local update file (OnePlus6Oxygen_22_OTA_030_all_1904032206)
Then, enable developer options, OEM unlock, USB debugging, advanced reboot
Reboot to fastboot and execute "fastboot oem unlock" in Powershell with admin rights
Reboot to OOS, then check developer options again, all good
Reboot to fastboot, execute "fastboot boot twrp-3.2.3-x_blu_spark_v9.91_op6.img"
Reboot to TWRP, install Magisk-v19.2.zip, reboot to OS (to verify root)
Reboot to TWRP, install ROM zip, then install twrp-3.2.3-x_blu_spark_v9.91_op6.
Select Reboot to Recovery within TWRP
And then.... black screen with blue solid light. Can't load TWRP nor can I boot into OS.
I have also tried wiping during some of these attempts and that didn't help. At one point, I had a bricked phone with no bootloader/fastboot, but saved it with the MSM tool.
Can someone please tell me what am I doing wrong? I see some ROMs (such as Lineage0S 16 with MicroG) saying to install a stock OOS twice along with TWRP, then the LOS ROM+TWRP, but I could never get beyond the first attempt at installing stock ROM+TWRP. Same thing happens.
EDIT: Resolved below.

Do you have magisk installed after reboot twrp ?

cypress16 said:
I have had success flashing two ROMS (Lineage OS with MicroG and HavocOS) so far, but at some point, I am now getting nowhere fast trying to reinstall either of these after several clean attempts. I keep ending up at a black screen with a blue light and no more TWRP and no more bootable OS.
Here's what I did...
Starting fresh... Used MSMDownloadTool V4 to install OOS (enchilada_22_O.09_180517) then updated with local update file (OnePlus6Oxygen_22_OTA_030_all_1904032206)
Then, enable developer options, OEM unlock, USB debugging, advanced reboot
Reboot to fastboot and execute "fastboot oem unlock" in Powershell with admin rights
Reboot to OOS, then check developer options again, all good
Reboot to fastboot, execute "fastboot boot twrp-3.2.3-x_blu_spark_v9.91_op6.img"
Reboot to TWRP, install Magisk-v19.2.zip, reboot to OS (to verify root)
Reboot to TWRP, install ROM zip, then install twrp-3.2.3-x_blu_spark_v9.91_op6.
Select Reboot to Recovery within TWRP
And then.... black screen with blue solid light. Can't load TWRP nor can I boot into OS.
I have also tried wiping during some of these attempts and that didn't help. At one point, I had a bricked phone with no bootloader/fastboot, but saved it with the MSM tool.
Can someone please tell me what am I doing wrong? I see some ROMs (such as Lineage0S 16 with MicroG) saying to install a stock OOS twice along with TWRP, then the LOS ROM+TWRP, but I could never get beyond the first attempt at installing stock ROM+TWRP. Same thing happens.
Click to expand...
Click to collapse
What I did is this...
After your first step which is "Starting fresh... Used MSMDownloadTool V4 to install OOS (enchilada_22_O.09_180517) then updated with local update file (OnePlus6Oxygen_22_OTA_030_all_1904032206)", I install again the "OnePlus6Oxygen_22_OTA_030_all_1904032206" to follow the step that requires flashing OOS twice.
Then I followed the steps in https://forum.xda-developers.com/oneplus-6/how-to/tutorial-decrypt-flash-rom-pie-oreo-roms-t3838643, this is to decrypt my device and to be able to flash any ROM infinite times without corrupting again my device.

I suggest you use a newer MSM tool to restore to stock. Then, do local upgrade twice to install the zip on the both slots. Then proceed to unlock the bootloader.

Anytime u flash twrp u need to flash magisk too (no need to reboot if you are using the same slot before flashing magisk) , I think on the last step u forget that
Just boot to twrp and flash magisk again

I wrote that before ? 2e post

Thanks for all the tips. Finally got it working. This is nothing like the Samsung phones I'm used to.....
Here is the process I followed and I finally have a working system with the Havoc Rom, MicroG, the blu_spark kernel and magisk:
MSMDownloadTool V4 to install OOS (enchilada_22_O.09_180517) then updated with local update file (OnePlus6Oxygen_22_OTA_030_all_1904032206)
Unlock booloader
Flash TWRP
Reboot to TWRP and flash oos 9.0.5 ota zip and flash TWRP
Reboot to TWRP
Flash oos 9.0.5 ota zip and TWRP again
Reboot to TWRP
Factory reset
Flash ROM
Reboot TWRP
Flash Magisk
Flash Kernel
Reboot to TWRP
Flash microg
Resume normal life after two excruciating days of failed attempts

Accidentally formatted system partition in recovery

Hi, after installing TWRP, I was trying to do a fresh start on my op7 pro, but accidentally while formatting, I also happen to selected my system partition and formatted it.
Now I'm stuck on fastboot screen and can not install recovery or OS any how....
Can I recover without using msm tool from their support...
Help please

I think this
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424

Just flash the latest build again from TWRP
- Download full OTA
- boot to TWRP
- plug phone to PC and move the downloaded OTA to phone internal storage
- In TWRP browse to OTA and flash it but DO NOT REBOOT
- flash TWRP installer
- reboot to TWRP and flash installer again just to be sure
- Reboot to system

Jaco2k said:
Just flash the latest build again from TWRP
- Download full OTA
- boot to TWRP
- plug phone to PC and move the downloaded OTA to phone internal storage
- In TWRP browse to OTA and flash it but DO NOT REBOOT
- flash TWRP installer
- reboot to TWRP and flash installer again just to be sure
- Reboot to system
Click to expand...
Click to collapse
I tried to do the same, but everytime I try to boot into recovery from fastboot, I get the same error
- FAILED (remote: Failed to load/authenticate boot image: Load Error)
Even tried different versions of twrp but same is happening

So, wait a minute... You did not install TWRP to the recovery partition before starting to format stuff?
---------- Post added at 03:30 PM ---------- Previous post was at 03:27 PM ----------
In your first post you say "after installing TWRP"
If you have correctly installed TWRP you should be able to get to recovery by holding down power button and volume up button.

Jaco2k said:
So, wait a minute... You did not install TWRP to the recovery partition before starting to format stuff?
Click to expand...
Click to collapse
I did, installed TWRP quite a while ago before all this.
I was testing the latest dp on my mobile, but later I decided to revert back to stable. I flashed the pie version in local upgrade and wanted to start over.
So after booting once, I rebooted into TWRP and mistakenly selected system partition along with local storage in wipe option.
And now fastboot is the only thing I can boot in

I somehow don't think you are telling the story exactly as it went
I am assuming you flashed a full build and rebooted without flashing TWRP in-between.
Also, I am assuming you have flashed an older build that has the fastboot bug.
This means that you might be pretty screwed.
You can try to ADB push the full OTA via fastboot and flash it there using command line.
I guess at this point you are not caring anymore if you keep your data, right?
Also, there were some patched boot images laying around that might be worth flashing to see if fastboot is working on them.
As you have come across, there is a fastboot bug in some builds - I guess at some point it was fixed and then it reoccurred.
---------- Post added at 03:43 PM ---------- Previous post was at 03:39 PM ----------
BTW, I guess the link already posted in this thread might be your best bet, since you have removed TWRP when you flashed the updated build and you cannot fastboot recovery, as you have found out, due to a bug from OnePlus.

JerryDaBaaws said:
Hi, after installing TWRP, I was trying to do a fresh start on my op7 pro, but accidentally while formatting, I also happen to selected my system partition and formatted it.
Now I'm stuck on fastboot screen and can not install recovery or OS any how....
Can I recover without using msm tool from their support...
Help please
Click to expand...
Click to collapse
Just get the fastboot ROM for the same version you're on. For example 9.5.10 then you HAVE to use the one for 9.5.10.
https://androidfilehost.com/?w=files&flid=294300
Just download the Fastboot ROM (Make sure it's for your device as well). If on GM21aa then that's the one you use.
Put the phone in Fastboot mode and attach the phone to PC
Type Fastboot devices and make sure it comeback with your device serial number (like 6 or 8 digits, cant remember exactly)
Unzip the fastboot ROM and click on Flash-all.bat
Your phone will be like new as if shipped with 9.5.10 or whatever ROM you're on. There will be no root/TWRP/files (photos or music). You will have to do it all again but your phone will be working.

[21/07/2019][EMUI-8.X] TWRP 3.4.0.0 for Huawei P8 Lite 2017

Welcome to the TWRP Project for Huawei P8 Lite 2017 family devices
Installation
Reboot to bootloader.
run: fastboot flash recovery_ramdisk recovery.img
Downloads
Read the second post.
Bugs
Backup (Welcome to Huawei World)
Huru: give me "Error finding input device".
MTP (I'm working on it).
Pushing files related on MTP issues, you have to use adb to upload files into sdcard.
Kernel:
I'm not voilating any kind of license, because I'm still using the one provided by Emui 8.0. So all credits goes to Huawei.
Additional Credits
@Dil3mm4 for gpio advice that let me fix huru
@zxz0O0 for your script, I just create a 0.5 version that it is compatible with 3.3.x twrp
my intention isn't "stealing" your works.
Sources
https://github.com/hak86/twrp_device_huawei_hi6250-twrp
XDA:DevDB Information
TWRP Recovery for P8 Lite 2017, ROM for the Huawei P8lite/P8 Lite
Contributors
haky 86
Source Code: https://github.com/hak86?tab=repositories
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Emui-8.x
Based On: LineageOS/AOSP
Version Information
Status: Alpha
Stable Release Date: 2019-07-30
Beta Release Date: 2019-07-30
Created 2019-07-30
Last Updated 2019-07-30

twrp-3.3.1.0-emui-8.x-prague-30072019.img
https://sourceforge.net/projects/p8...3.3.1.0-emui-8.x-prague-30072019.img/download
Initial build
twrp-3.3.1-0-v1-18112019-hi6250-emui8-haky86.img
https://sourceforge.net/projects/hi...-v1-18112019-hi6250-emui8-haky86.img/download
Fix ADB.
Fix resize system.
backup should be fine.
twrp-3.3.1-0-v1.5-21112019-hi6250-emui8-haky86.img
https://sourceforge.net/projects/hi...1.5-21112019-hi6250-emui8-haky86.img/download
Fix Rebooting stuff.
Fix Wiping, you can flash roms with full wipes, by;
1-Wipe > Format Data > YES.
2-Wipe > Advanced Wipe > select Dalvik / ART Cache > Cache > Data > Internal Storage > System > Flash ROM then GAPPS then enjoy.
twrp-3.3.1-0-v2.0-03032020-hi6250-emui8-haky86.img
https://sourceforge.net/projects/hi...2.0-03032020-hi6250-emui8-haky86.img/download
nothing special.
twrp-3.4.0.0-v1-hi6250-emui8.img
https://sourceforge.net/projects/hi...WRP/twrp-3.4.0.0-v1-hi6250-emui8.img/download
nothing special.
Reserved
Huru
Download my HuRUpdater_0.5.zip from "attached files" so all credits to the original author.
Flash it like usually, it is just compatible with 3.3.x twrp.

Update
* Huru is fixed now.
* Read the second post.

is it better as askuccios twrp or others?Thanx.

-CALIBAN666- said:
is it better as askuccios twrp or others?Thanx.
Click to expand...
Click to collapse
askuccio's one huru doesn't work while mine it is, I'll fix mtp in next build.

Glad to see that your still developing for this device!
I'm from TWRP 3.2.1-0 April 8th build Round 2, will I be able to switch from the current one to your brand new version?

F2196G said:
Glad to see that your still developing for this device!
I'm from TWRP 3.2.1-0 April 8th build Round 2, will I be able to switch from the current one to your brand new version?
Click to expand...
Click to collapse
the only thing that need a fix, copying files but you can push them using adb till I fix it. for the rest of things such wipe, installing custom roms are fine. for huru use my edited version 0.5 in the second post.

haky 86 said:
the only thing that need a fix, copying files but you can push them using adb till I fix it. for the rest of things such wipe, installing custom roms are fine. for huru use my edited version 0.5 in the second post.
Click to expand...
Click to collapse
And switch from my current TWRP is fine right? Do I need other adb commands or they're always the same?

i think u can flash the image with ur current twrp, or not?

-CALIBAN666- said:
i think u can flash the image with ur current twrp, or not?
Click to expand...
Click to collapse
I prefer to flash recoveries from pc via adb

Hey Haky 86, is it able to flash / update your .img via Flashify app?

F2196G said:
Hey Haky 86, is it able to flash / update your .img via Flashify app?
Click to expand...
Click to collapse
that app for qualcomm devices I think, never tried so use fastboot

Sorry for so many questions... But..
I have to tell you what happened to me.
I had Bootloader unlocked, FRP unlocked, official PRA-LX1 8.0.0.400(C432) and rooted with Magisk.
Then I tried to flash a ROM, but I proceeded without nandroid backup, and I data formatted instead of wiping. Then I flashed ROM and GApps, but I was on bootloop. Then I followed https://forum.xda-developers.com/p8...uide-brick-huawei-p8-lite-2017-maybe-t3816694 this guide (Problem No.3), factory resetted from erecovery, and now I can boot to OS with no problems. But now, PC, adb and fastboot do not recognize the device even if the device is in Fastboot&Rescue mode.
adb devices says nothing. fastboot devices either.
HiSuite does not recognize the device. If I plug in the USB cable, PC says nothing, no sound, and the device goes in charge mode, without asking for a USB mode(charge only, file transfer or photo transfer) what can I do? Is it safe to root this firmware by flashing Magisk zip from current TWRP since I cannot communicate with the device from command prompt?

F2196G said:
Sorry for so many questions... But..
I have to tell you what happened to me.
I had Bootloader unlocked, FRP unlocked, official PRA-LX1 8.0.0.400(C432) and rooted with Magisk.
Then I tried to flash a ROM, but I proceeded without nandroid backup, and I data formatted instead of wiping. Then I flashed ROM and GApps, but I was on bootloop. Then I followed https://forum.xda-developers.com/p8...uide-brick-huawei-p8-lite-2017-maybe-t3816694 this guide (Problem No.3), factory resetted from erecovery, and now I can boot to OS with no problems. But now, PC, adb and fastboot do not recognize the device even if the device is in Fastboot&Rescue mode.
adb devices says nothing. fastboot devices either.
HiSuite does not recognize the device. If I plug in the USB cable, PC says nothing, no sound, and the device goes in charge mode, without asking for a USB mode(charge only, file transfer or photo transfer) what can I do? Is it safe to root this firmware by flashing Magisk zip from current TWRP since I cannot communicate with the device from command prompt?
Click to expand...
Click to collapse
1-that guide for nougat firmware that have different fastboot command.
2-I'm not Huawei assistance as I'm not going to help each one that doesn't use stock recovery to boot my whole roms, also OpenKirin recommend stock recovery to wipe data for booting roms.

haky 86 said:
Update
* Huru is fixed now.
* Read the second post.
Click to expand...
Click to collapse
backup still not working?

F2196G said:
backup still not working?
Click to expand...
Click to collapse
no, will never ever work.

for all here with the request to flash it over current twrp.
Ive tested it and flashed it in askuccius twrp and it works flawlessly, no problem.
In twrp just change to img flash option and flash new twrp as recovery ramdisk, reboot to recovery, tada. Greetz!!!

-CALIBAN666- said:
for all here with the request to flash it over current twrp.
Ive tested it and flashed it in askuccius twrp and it works flawlessly, no problem.
In twrp just change to img flash option and flash new twrp as recovery ramdisk, reboot to recovery, tada. Greetz!!!
Click to expand...
Click to collapse
I specify in the op how to install but seems most people ignore what I wrote.

Developments of this device has been discontinued, since most of people have troubles and bugs with my stuff as you are free to use what you want.
I'm gonna move to another phone.

twrp-3.3.1-0-v1-18112019-hi6250-emui8-haky86.img
https://sourceforge.net/projects/hi...-v1-18112019-hi6250-emui8-haky86.img/download
Fix ADB.
Fix resize system.
backup should be fine.

[Guide] Installing Blu_spark TWRP | Magisk 20.1 On Stable Oxygen OS 10

Hi there just incase someone else who had problems [like me]
who is hesitant or looking for a guide on how to install Blu_Spark TWRP and Root the device.
The guide below will work 99.9% of the time. just follow the instructions carefully
Necessary Files:
Install OnePlus 6 Driver
Install Fastboot Drivers
TWRP Image
Magisk 20.1
twrp-3.3.1-x_blu_spark_v9.107_op6
Stock boot image thanks [URL="https://forum.xda-developers.com/member.php?u=6994095" @Akhil701[/URL]
Step 1: [dont do this if you have installed ADB and Fastboot already]
Install Oneplus 6, ADB and Fastboot Drivers from the link above
* Reboot PC after installing
Step 2:
Put
Code:
Stock Boot Image [boot.img]
twrp-3.3.1-x_blu_spark_v9.107_op6.zip and
Magisk-v20.1.zip
on your internal storage
Also Put
Code:
twrp-3.3.1-11-enchilada-Q-mauronofrio.img
on your desktop
Step 3: Reboot device in fastboot/bootloader mode
Step 4: Connect Device to PC Via USB Cable
Step 5: On your desktop Press Shift Right Click then click the [Open Command Prompt Here]
Step 6: on the CMD Windows Type
Code:
fastboot devices
Press enter and see if your device shows up.
Step 7: type in the CMD Window
Code:
fastboot flash boot twrp-3.3.1-11-enchilada-Q-mauronofrio.img
press enter then after that on your phone screen use volume up or down button to reboot to recovery
Step 8:
Once you have the TWRP Screen
flash the stock boot image [boot.img] in boot partition [DO NOT Reboot!]
now go back and flash the Blu_Spark TWRP and then reboot to recovery
Step 9: Rooting
Flash Magisk 20.1.zip then reboot to system.
Thats it! no data will be wiped as long as your bootloader is already unlocked.
thanks to
@Funk Wizard for the initial instruction on how to install twrp and root
 @eng.stk for the Blu_Spark TWRP
 @mauronofrio for the initial TWRP Image
 @Akhil701 for the stock boot.img
 @remewer for inspiration to build this guide.​

Patched boot.img or why we need the boot image after flashing OOS10 via local update?

Sh0X31 said:
Patched boot.img or why we need the boot image after flashing OOS10 via local update?
Click to expand...
Click to collapse
im not sure about that also. im just hesitant to skip that step. it might break something. thats why i added that step on this guide

Thnx, this was a very easy walkthrough.
Only thing I want to say is that not everyone knows how to flash the 'boot.img' through TWRP. Maybe you can explain that in more detail.

no patched boot.img you need
1. connect your OP6 to PC
2. flash TWRP (from mauronofrio) by fastboot from PC
3. reboot from fastboot to recovery
4. in TWRP flash stock img OOS, don´t reboot
5. in TWRP flash TWRP (blu_spark 9.107)
6- reboot to TWRP to another slot
7. in TWRP flash Magisk 20.1
8. reboot to system

I have noticed this too, probably they have changed somehow the system, even fastboot boot doesn't work anymore....
I had to install magisk via boot.img patching

Functionally on OOS 10.0.1 OP6 ?

So I was unable to flash the new OTA through twrp running on my rooted OP6.
As such, I opted to install the new OTA through the "local install" option.
That worked great. Settings area all the same. Bootloader still unlocked (I double checked).
Drivers are all installed on my Windows 10 PC.
However, no matter what I attempt to flash from command prompt I always get:
FAILED (remote: unkown command)
Does anyone know of a solution yet?
I have been reinstalling drivers and rebooting my PC with no luck thus far.
Any ideas?
Thanks in advance.
Update:
Whelp now that it is upgraded to Android 10 (and was wiped of all data when I locked and then unlocked the bootloader again) it will not allow me to downgrade back to Andriod 9 through the local upgrade option and since I can not get fastboot to accept any commands I am stuck now in Andriod 10 without the ability to change anything at the moment.

Brisky86 said:
So I was unable to flash the new OTA through twrp running on my rooted OP6.
As such, I opted to install the new OTA through the "local install" option.
That worked great. Settings area all the same. Bootloader still unlocked (I double checked).
Drivers are all installed on my Windows 10 PC.
However, no matter what I attempt to flash from command prompt I always get:
FAILED (remote: unkown command)
Does anyone know of a solution yet?
I have been reinstalling drivers and rebooting my PC with no luck thus far.
Any ideas?
Thanks in advance.
Update:
Whelp now that it is upgraded to Android 10 (and was wiped of all data when I locked and then unlocked the bootloader again) it will not allow me to downgrade back to Andriod 9 through the local upgrade option and since I can not get fastboot to accept any commands I am stuck now in Andriod 10 without the ability to change anything at the moment.
Click to expand...
Click to collapse
i knew it while reading but thanks to the screenshot you provided you saved me from sounding "user error" once again and piss of so many who prefer to blame things and others LOL
in short, wrong command, it's fastboot flash boot <image name>
BTW and since i'm already at it, if anyone has a Mac runniing 10.15 "Catalina" and fastboot is working from terminal, i'd like to learn how he/she's done it
just came to my mind to ask here since i have to use windows 10 under parallels desktop to fastboot flash my android stuff at the moment and of course that's just an "Emergency" choice for me, everyone using both platforms will understand

magnamentis said:
i knew it while reading but thanks to the screenshot you provided you saved me from sounding "user error" once again and piss of so many who prefer to blame things and others LOL
in short, wrong command, it's fastboot flash boot <image name>
BTW and since i'm already at it, if anyone has a Mac runniing 10.15 "Catalina" and fastboot is working from terminal, i'd like to learn how he/she's done it
just came to my mind to ask here since i have to use windows 10 under parallels desktop to fastboot flash my android stuff at the moment and of course that's just an "Emergency" choice for me, everyone using both platforms will understand
Click to expand...
Click to collapse
Wow. Okay.
This is becoming a comedy of errors on my part.
Oh boy now I am getting Qualcom flashdump messages...
Huh now it is just booting normal but not letting me get into the new recovery flash...
I got it all fixed.
Thank you everyone for your help and patience with my posts.

Does 10.0.1 still have the ability to do screen-off gestures for music? I like 10 but on my wife's 7t, either she didn't turn them on, our it didn't have them so I'm curious if there same thing is happening with this? I also noticed on her 7t, constant data problems when's switching from WiFi to data. Sometimes data won't come back and only a reboot solves. I know it's a bug on OOS 10 on 7t but wondering if it's a device specific bug or an Android 10 bug? Anyone having op6 issues with data not coming back when switching from WiFi?

WIFI problem solved!
Below OOS 10.0.1 back inTWRP
Wipe: cache, system and vendor
Flash OOS 10
Flash boot img
Flash TWRP
Flash Magisk
Reboot system
Reboot recovery
Flash OOS 10.0.1
Flash boot img
Flash TWRP
Flash Magisk
Reboot system
Wifi works

After rooting 10.0.1 with magisk 20.1 mobile network is gone. no sim pin, no metwork. after unroot everything is fine

Hello Mates,
i updated my rooted oneplus 6 from 10 to 10.01 and after that use this method to root again. But there is a Problem now: My WiFi doesnt work? I cant activate it.
Do anybody know how i can fix that Problem?
Thank you in Advance
Best Regards
Coktail

As above. No wifi, no sound. What's going on?

Coktail said:
Hello Mates,
i updated my rooted oneplus 6 from 10 to 10.01 and after that use this method to root again. But there is a Problem now: My WiFi doesnt work? I cant activate it.
Do anybody know how i can fix that Problem?
Thank you in Advance
Best Regards
Coktail
Click to expand...
Click to collapse
cubic25 said:
As above. No wifi, no sound. What's going on?
Click to expand...
Click to collapse
Look 2 posts up...

ryanallaire said:
Look 2 posts up...
Click to expand...
Click to collapse
Unroot doesn't work for me. Still no wifi and audio.

Hi guys, sorry to resurrect this thread. I did everything in the correct order using 10.0.3.0 and after step 8 (reboot after flashing blu_spark) my phone gets stuck on blu_spark splash screen without any option to boot into twrp. Normal boot results in bootloop... Any ideas? Do I need to use different versions of twrp.img and .zip?

dynamode said:
Hi there just incase someone else who had problems [like me]
who is hesitant or looking for a guide on how to install Blu_Spark TWRP and Root the device.
The guide below will work 99.9% of the time. just follow the instructions carefully
@Funk Wizard for the initial instruction on how to install twrp and root
@eng.stk for the Blu_Spark TWRP
@mauronofrio for the initial TWRP Image
@Akhil701 for the stock boot.img
@remewer for inspiration to build this guide.​
Click to expand...
Click to collapse
Hello.
I´m on 10.3.0 op6, I followed all the steps and when i finish the step 8 and reboot, i stuck on the recovery message. I repeat all the steps flashing clean rom and always have the same problem.....
Can someone help me? Because i don´t know another way for installing magisc....
Thanks!!!

loggstar said:
Hi guys, sorry to resurrect this thread. I did everything in the correct order using 10.0.3.0 and after step 8 (reboot after flashing blu_spark) my phone gets stuck on blu_spark splash screen without any option to boot into twrp. Normal boot results in bootloop... Any ideas? Do I need to use different versions of twrp.img and .zip?
Click to expand...
Click to collapse
I am in exactly the same position here.
Followed all the steps and am now stuck on the blu_spark boot screen for the past 15 minutes

[LineageOS 20] Bootloop after OTA, can't adb/fastboot as it does not recognise the phone

OnePlus 8T KB2003 running lineage-20.0-20230105-nightly with Magisk 25.2 patched boot image.
Yesterday I installed latest OTA lineage-20.0-20230112-nightly, patched boot.img through Magisk to inactive slot before OTA reboot, rebooted and now I am in a bootloop.
I was about to flash original lineage boot.img from payload_dumper through flashboot, and I find neither fastboot nor adb work at all. My device is not recognised on adb or fastboot when I plug in the usb-c cable.
I checked platform-tools version and google adb drivers to be updated (reinstalled from 15-second ADB installer), swapped usb-c cable, changed host usb port... but no outcome.
I tried adb/fastboot devices pluging another android 13 phone, and everything works. So I discarded drivers, cable and port.
I plugged my turned off OnePlus with the same cable and port, and it charges. So I discarded usb port from OnePlus.
The only thing that gets me thinking is that I did not enabled usb debugging mode in lineageos 20 (as I did in lineageos19 and maybe the option was set to default after the update), but now I cannot check as it does not boot to system.
I guess there is no way to enable it from fastboot/recovery mode, or to change active slot to b (I am currently in a, and in b I could reboot normally), as I cannot fastboot this device (fastboot --set-active=b)
Any idea? Data factory would not help as I would be unable to adb push rom and gapps.
Thanks in advance as I am pretty lost.

The usb debugging setting in developer options only lets you use ADB commands while booted in android.
It shouldn't influence ADB or fastboot from working in recovery or fastboot mode.
Note: ADB doesn't work in the root of recovery you would have to go to “Advanced” -> “Enable ADB” to use it from recovery.
If fastboot isn't working in fastboot mode you can try using fastboot from recovery.
For this you can go to the recovery and then “Advanced” -> “Enter fastboot”.
It shouldn't be the newest OTA lineage-20.0-20230112-nightly at least as i'm currently running it including Magisk without any problems. I am running the newest F.15 firmware instead of F.13 firmware though.
Also I installed magisk by sideloading it after renaming the .apk to .zip which keeps magisk installed through Addon.d like gapps. So i didn't use the inactive slot installation. (Not sure if you can sideload it after first boot)

Vipe838 said:
The usb debugging setting in developer options only lets you use ADB commands while booted in android.
It shouldn't influence ADB or fastboot from working in recovery or fastboot mode.
Note: ADB doesn't work in the root of recovery you would have to go to “Advanced” -> “Enable ADB” to use it from recovery.
If fastboot isn't working in fastboot mode you can try using fastboot from recovery.
For this you can go to the recovery and then “Advanced” -> “Enter fastboot”.
It shouldn't be the newest OTA lineage-20.0-20230112-nightly at least as i'm currently running it including Magisk without any problems. I am running the newest F.15 firmware instead of F.13 firmware though.
Also I installed magisk by sideloading it after renaming the .apk to .zip which keeps magisk installed through Addon.d like gapps. So i didn't use the inactive slot installation. (Not sure if you can sideload it after first boot)
Click to expand...
Click to collapse
Wow, thank you so much!
I could connect with fastbootd (from recovery, Advanced --> Enter Fastboot), could flash boot.img and got it to boot.
Thank you again.