Database Info

[Q] problem with fastboot

hi.
I didn't use my tf700 for one year and after one year i forgot my pattern(password).
my tablet was unlock and root and twrp or cmw (i didn't remember exactly) was installed on my device
then i turn my device off , when it was connected with my computer then hold power button and volume down
and then i go to RCK for going to recovery twrp but then an android image with red dangerous sign ( ! in a red traiangel )
so i choose wipe data sign.and all of things in my device deleted also my password.
now i can use my device but i want to install a custom rom. there is a problem that i haven't usb icon for fastboot(when power up with volume down)
how i can fix it or installing twrp for rooting and installing custom rom?
(excuse me if my english language isn't good)

nasiroddin said:
hi.
I didn't use my tf700 for one year and after one year i forgot my pattern(password).
my tablet was unlock and root and twrp or cmw (i didn't remember exactly) was installed on my device
then i turn my device off , when it was connected with my computer then hold power button and volume down
and then i go to RCK for going to recovery twrp but then an android image with red dangerous sign ( ! in a red traiangel )
so i choose wipe data sign.and all of things in my device deleted also my password.
now i can use my device but i want to install a custom rom. there is a problem that i haven't usb icon for fastboot(when power up with volume down)
how i can fix it or installing twrp for rooting and installing custom rom?
(excuse me if my english language isn't good)
Click to expand...
Click to collapse
If you see three icons on your bootloader menu, you have a newer bootloader version than ICS. You can ckeck the bootloader version when you are in it and it is in the upper left corner with a small tiny prints. You are also already in the the fastboot mode if you are in the bootloader menu. You can check your fastboot by typing "fastboot devices" to see if your PC can communicate with your device. Good luck...:fingers-crossed:

on the top left corner writes: "key driver not found.. booting os
android cardhu-user bootloader..............
starting fastboot USB download protocol"
now where i should write "fastboot device" ?

nasiroddin said:
on the top left corner writes: "key driver not found.. booting os
android cardhu-user bootloader..............
starting fastboot USB download protocol"
now where i should write "fastboot device" ?
Click to expand...
Click to collapse
sbdags created a zip installer for twrp and you can check out the script here:
http://forum.xda-developers.com/showthread.php?t=2646279
This is a very nice tutorial for installing adb/fastboot and you can find out more information on this post:
http://forum.xda-developers.com/showthread.php?t=2688891
Please read through these two posts before proceeding with installing your new twrp, good luck...:fingers-crossed:

[Q] Bootloader locked after OTA XNPH05Q

Hi all,
I just installed the OTA update for XNPH05Q. My bootloader was previously unlocked, TWRP installed and rooted.
Now that the OTA is installed I wanted to re-root (SuperSU Pro Survival didn't work), but when I boot into recovery mode I only get the default 'Cyanogen Recovery' and trying to flash the SuperSU binary fails with 'Signature File unavailable' error.
Any idea what went wrong? My phone was heavily customized and I would really try to avoid the hassle of going through the full process to unlock the bootloader again... It will take several hours to restore everything, and since I'm using some sideloaded apps I don't even know if I will find them again - and now I can't even use Titanium anymore to backup them, the OTA happened already
Thanks for your input!

Your bootloader is still unlocked, it only restored stock recovery. So you only need to flash twrp, you won't lose any data doing that. And to stop the stock recovery getting flashed when installing OTA, go to Settings > Developer options. Then disable the 'Update recovery with system updates' option.

Thanks, that made my day! I'm currently travelling and have no access to a computer, but I'll flash TWRP again as soon as I'm back home and proceed from there.

Viking84 said:
Thanks, that made my day! I'm currently travelling and have no access to a computer, but I'll flash TWRP again as soon as I'm back home and proceed from there.
Click to expand...
Click to collapse
You can use Flashify to flash TWRP directly from your phone.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Transmitted via Bacon

timmaaa said:
You can use Flashify to flash TWRP directly from your phone.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Transmitted via Bacon
Click to expand...
Click to collapse
That requires root though which he doesn't have.

Gryphie said:
That requires root though which he doesn't have.
Click to expand...
Click to collapse
Yeah, I didn't really think that one through.
Transmitted via Bacon

If you have fastboot set-up you can run the command for oem unlock again and it shouldn't wipe anything. Happened with me After going to XNPH05Q my bootlocked got relocked as well and I was trying to flash cm12 and I couldnt figure out for the life of me why it would keep booting to fastboot and recovery wasnt working. So when all else failed and I said eff it I dont care if it wipes, I re-ran the command (after checking bootloader status and seeing that it got locked) and I was able to boot up just fine without any data loss.
That's just my personal experience though.
I did that because even after flashing different version of TWRP recovery and different ROMs my phone kept booting straight to fastboot.

I just arrived back home (literally stepped out of the airport 45 minutes ago) and as of this moment, my OPO is up & rooted again, with all data intact. Thanks for your great support!!!

Viking84 said:
I just arrived back home (literally stepped out of the airport 45 minutes ago) and as of this moment, my OPO is up & rooted again, with all data intact. Thanks for your great support!!!
Click to expand...
Click to collapse
Can you please tell how did you flashed TWRP again, as I have the same issue as you had.

Sure. I first had to tell my PC to use the correct drivers again - basically after installing the OTA, Windows recognized the phone anew and used the default drivers. So go to your device manager (Windows-Key + 'Break' -> device manager), search for your phone (I don't remember in which category it showed up, but just browse all until you find 'A00001'. Right klick, select 'change driver'. Go to 'have disk' and select 'ADB' from the list on the left, then on the right you should find the driver that is already installed [given that you had an ADB driver already, otherwise check this site for the driver download: http://twrp.me/devices/oneplusone.html].
To check if it worked, open a command line [Windows-Key + R, write cmd in the field and hit enter]. Now type "adb devices" [enter] and if [device ID] (some random numbers) is listed in the menu, all is fine.
Download the most recent TWRP image file from http://dl.twrp.me/bacon/ and save it somewhere.
Now, in the same command line enter "adb reboot bootloader", this will put your phone in fastboot mode.
Once this is done, check if the driver is still recognizing your phone by entering "fastboot devices", and check if the device is still listed.
If this checks out, enter "fastboot flash recovery [FULL PATH TO RECOVERY FILE]" -> e.g. "fastboot flash recovery c:\Users\viking84\Desktop\twrp-2.8.6.0-bacon.img"
This will take a couple minutes (3-4 for me).
Once it's done, enter "fastboot reboot" in the console, and your phone will reboot into recovery (if it doesn't, just switch it back of and restart it with power + volume up to enter the recovery menu). From there you can just install the SuperSU binary as you're used to.

Thx for the detailed step guide... Will perform these steps today.
Sent from my Oneplus One

Viking84 said:
Sure. I first had to tell my PC to use the correct drivers again - basically after installing the OTA, Windows recognized the phone anew and used the default drivers. So go to your device manager (Windows-Key + 'Break' -> device manager), search for your phone (I don't remember in which category it showed up, but just browse all until you find 'A00001'. Right klick, select 'change driver'. Go to 'have disk' and select 'ADB' from the list on the left, then on the right you should find the driver that is already installed [given that you had an ADB driver already, otherwise check this site for the driver download: http://twrp.me/devices/oneplusone.html].
To check if it worked, open a command line [Windows-Key + R, write cmd in the field and hit enter]. Now type "adb devices" [enter] and if [device ID] (some random numbers) is listed in the menu, all is fine.
Download the most recent TWRP image file from http://dl.twrp.me/bacon/ and save it somewhere.
Now, in the same command line enter "adb reboot bootloader", this will put your phone in fastboot mode.
Once this is done, check if the driver is still recognizing your phone by entering "fastboot devices", and check if the device is still listed.
If this checks out, enter "fastboot flash recovery [FULL PATH TO RECOVERY FILE]" -> e.g. "fastboot flash recovery c:\Users\viking84\Desktop\twrp-2.8.6.0-bacon.img"
This will take a couple minutes (3-4 for me).
Once it's done, enter "fastboot reboot" in the console, and your phone will reboot into recovery (if it doesn't, just switch it back of and restart it with power + volume up to enter the recovery menu). From there you can just install the SuperSU binary as you're used to.
Click to expand...
Click to collapse
I have successfully re-rooted by device using the above procedure. The only difference was even after flashing recovery and installing SuperSU through TWRP I was not able to see SuperSU app in phone, but then I went to Playstore and downloaded it from there and it worked!
So thank you for your help and detailed procedure!

I somehow broke TWRP

I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.

mattlokk said:
I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.
Click to expand...
Click to collapse
Did you set:
Allow oem unlock in dev opt.
Fastboot protocol into BL?
Twrp app & manager need root to work.

Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link

thanks for the help, i'll try and work through this soon.

fpozar said:
Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link
Click to expand...
Click to collapse
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.

mattlokk said:
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.
Click to expand...
Click to collapse
Okay so I'm guessing you have stock ROM.
To flash TWRP you have to enter fastboot mode (vol down + power I believe) and flash the twrp image with fastboot flash recovery twrp.img (rename the shield tablet twrp to just twrp.img and place it into your easy adb and fastboot folder)
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck

fpozar said:
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck
Click to expand...
Click to collapse
Agreed. This is probably what is happening (as described on the TWRP webpage here:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Alternately, immediately rooting (flash SuperSU or Magisk) right after flashing TWRP, will prevent TWRP from being replaced with stock recovery.
Although the inconsistent fastboot connection, and how much trouble you had flashing TWRP initially, is a bit worrisome. Try using a different cable (maybe the one you are using is not connecting well?) try another USB port on the computer, and don't use a USB hub (connect direct to the PC).

Well, like they say: persistence is key. I kept pushing and trying new things until eventually.... I bricked the device. No, not really, it's working great now on LineageOS.
Thanks again to everyone who helped me out :good:. I'm still not sure exactly what caused TWRP to stop working on my device, however following this guide helped me fix it: https://forum.xda-developers.com/shield-tablet/help/help-stuck-nvidia-boot-screen-t3076462
The "flash-all.bat" restored everything to stock (including the recovery mode) and after that I was able to flash the latest TWRP and install Lineage.

Oukitel WP2 root issues - twrp not installing

Sorry, can not find any threads her on this
New Oukitel WP2 Android 8
Unlocked bootloader using ADB
ran "fastboot flash recovery WP2.img" and computer said finished
'phone said OK!
Tried "fastboot recovery" BUT all the 'phone will display is ==> fastboot mode in micro writing bottome left of screen
Tried volume up/power - nothing volume down/power - after warning about unlocked bootloader
bot into STANDARD Android 8 boot menu.
Having unlocked many Samsung 'phones, this is confusing me!
Also, after this how do you actually root the 'phone (or is twrp the root kit) as super SU reports
unrooted telephone.
Any clues gratefully accepted
Thanks
John

JR44 said:
Sorry, can not find any threads her on this
New Oukitel WP2 Android 8
Unlocked bootloader using ADB
ran "fastboot flash recovery WP2.img" and computer said finished
'phone said OK!
Tried "fastboot recovery" BUT all the 'phone will display is ==> fastboot mode in micro writing bottome left of screen
Tried volume up/power - nothing volume down/power - after warning about unlocked bootloader
bot into STANDARD Android 8 boot menu.
Having unlocked many Samsung 'phones, this is confusing me!
Also, after this how do you actually root the 'phone (or is twrp the root kit) as super SU reports
unrooted telephone.
Any clues gratefully accepted
Thanks
John
Click to expand...
Click to collapse
After fastboot flashing TWRP, type the command below.
adb reboot recovery
Sent from my SM-S767VL using Tapatalk

Thanks for reply but ONLY boots into the stock android 8 recovery and will not boot into twrp
tried various methods and each time adp says flashed recovery (tried it with different names recovery.img twrp.img etc)
and shows data transferred on 'phone screen.
BUT your suggestion and all those on the various websites but will still not boot into the custome recovery
and although I am used to working on Samsung 'phones, this one beats me! Eveb fulll factory reset 3 times!
TWRP is recovery-20181231-0237.img from multiple sites.
I do not know how to find if the recovery has actually been installed or something is stopping it running.
Just tried again in case:-
ANDROID RECOVERY
OUKITEL /WP2/WP2
8.0.0/o00623/1532584305
user/release-keys
use vol.....
hen usual list+-
reboot system now
reboot to bootloader
etc etc
no TWRP
'Phone does show "strange condition - unlocked bootloader - device can not be trusted" on each boot,
so everything else seems fine.
Spent 5 hours on this! Was going to use super su but could use magisk instead IF I can get to the
recovery stage!
rgds
JR44 said:
Sorry, can not find any threads her on this
New Oukitel WP2 Android 8
Unlocked bootloader using ADB
ran "fastboot flash recovery WP2.img" and computer said finished
'phone said OK!
Tried "fastboot recovery" BUT all the 'phone will display is ==> fastboot mode in micro writing bottome left of screen
Tried volume up/power - nothing volume down/power - after warning about unlocked bootloader
bot into STANDARD Android 8 boot menu.
Having unlocked many Samsung 'phones, this is confusing me!
Also, after this how do you actually root the 'phone (or is twrp the root kit) as super SU reports
unrooted telephone.
Any clues gratefully accepted
Thanks
John
Click to expand...
Click to collapse

JR44 said:
Thanks for reply but ONLY boots into the stock android 8 recovery and will not boot into twrp
tried various methods and each time adp says flashed recovery (tried it with different names recovery.img twrp.img etc)
and shows data transferred on 'phone screen.
BUT your suggestion and all those on the various websites but will still not boot into the custome recovery
and although I am used to working on Samsung 'phones, this one beats me! Eveb fulll factory reset 3 times!
TWRP is recovery-20181231-0237.img from multiple sites.
I do not know how to find if the recovery has actually been installed or something is stopping it running.
Just tried again in case:-
ANDROID RECOVERY
OUKITEL /WP2/WP2
8.0.0/o00623/1532584305
user/release-keys
use vol.....
hen usual list+-
reboot system now
reboot to bootloader
etc etc
no TWRP
'Phone does show "strange condition - unlocked bootloader - device can not be trusted" on each boot,
so everything else seems fine.
Spent 5 hours on this! Was going to use super su but could use magisk instead IF I can get to the
recovery stage!
rgds
Click to expand...
Click to collapse
After flashing TWRP, you can't let the device boot to any other mode, you have to boot directly to recovery. If you allow the device to boot into any mode other than recovery, it will revert back to stock recovery. The only way to keep TWRP is to boot directly into TWRP immediately after flashing.
Try this, flash the TWRP file using the fastboot flash recovery (name of file) command. Then, after it flashes, try using this command:
fastboot boot recovery (name of your specific file)
This may allow you to boot into TWRP and keep TWRP recovery so that you can boot into it at any time after that.
Sent from my SM-S767VL using Tapatalk

Thanks for reply but does not work...
WP2 has already had bootloader unlocked developer options and adb commands, including an automatic wipe of 'phone.
Then without touching anything else, the follwoing have been entered from a clean boot of 'phone and Win7. twrp.img file is named "recovery.img" in same directory as adb etc (C:\ for testing)
twrp file is "recovery.img" in same directory as adb etc (C:\ for testing)
twrp file is "recovery.img" in same directory as adb etc (C:\ for testing)
issue command> adb reboot bootloader
computer response OK
'phone shows "fastboot" in miniscule text
issue command> "fastboot flash recovery recovery.img"
computer says> "target reported max download size 134217728 bytes"
then
"sending 'recovery' (15010kb)"
then
"OKAY [0.65 seconds}"
then
"writing 'recovery'..."
then
"finished. total time 1.06 s"
'phone says "transmission ok then a checksum"
after a wait
issue command> "fastboot boot recovery.img"
computer says "downloading 'boot.img'"
then
"OKAY 0.64 s"
then
"booting....."
then OKAY 0.47s"
then
"finished"
'Phone boots into normal logo then to a NORMAL STARTUP - NOT to any bootloader
argh!!!
adb devices returnes OUKIWP2000015176
Any clues as to what is wrong or what I am missing!
cheers
John
UK

JR44 said:
Thanks for reply but does not work...
WP2 has already had bootloader unlocked developer options and adb commands, including an automatic wipe of 'phone.
Then without touching anything else, the follwoing have been entered from a clean boot of 'phone and Win7. twrp.img file is named "recovery.img" in same directory as adb etc (C:\ for testing)
twrp file is "recovery.img" in same directory as adb etc (C:\ for testing)
twrp file is "recovery.img" in same directory as adb etc (C:\ for testing)
issue command> adb reboot bootloader
computer response OK
'phone shows "fastboot" in miniscule text
issue command> "fastboot flash recovery recovery.img"
computer says> "target reported max download size 134217728 bytes"
then
"sending 'recovery' (15010kb)"
then
"OKAY [0.65 seconds}"
then
"writing 'recovery'..."
then
"finished. total time 1.06 s"
'phone says "transmission ok then a checksum"
after a wait
issue command> "fastboot boot recovery.img"
computer says "downloading 'boot.img'"
then
"OKAY 0.64 s"
then
"booting....."
then OKAY 0.47s"
then
"finished"
'Phone boots into normal logo then to a NORMAL STARTUP - NOT to any bootloader
argh!!!
adb devices returnes OUKIWP2000015176
Any clues as to what is wrong or what I am missing!
cheers
John
UK
Click to expand...
Click to collapse
I don't know, I'll keep looking, if I find anything useful, I'll post it.
Sent from my SM-S767VL using Tapatalk

Still not working
If anyone else is reading this post I am still unable to flash the twrp recovery
downloaded from http://www.mediafire.com/file/cp6cw164fse2bpa/Oukitel_WP2_twrp.rar/file
Every time I try the flash commands it looks like it has sent to device - only takes 0.5 seconds and
'phone says received.
Unable to boot into recovery twrp - always comes back with stock android 8 recovery OR an error
message about can not open.
Any more suggestions please as annoying! OR is there adifferent twrp recovery out there I can
]use with Odin? or Magiisk?
Many thanks
john

JR44 said:
If anyone else is reading this post I am still unable to flash the twrp recovery
downloaded from http://www.mediafire.com/file/cp6cw164fse2bpa/Oukitel_WP2_twrp.rar/file
Every time I try the flash commands it looks like it has sent to device - only takes 0.5 seconds and
'phone says received.
Unable to boot into recovery twrp - always comes back with stock android 8 recovery OR an error
message about can not open.
Any more suggestions please as annoying! OR is there adifferent twrp recovery out there I can
]use with Odin? or Magiisk?
Many thanks
john
Click to expand...
Click to collapse
Odin is for Samsung devices only. You can't use Odin on your device.
Sent from my SM-S767VL using Tapatalk

OnePlus 8T stuck on FastBoot and Recovery Mode

So I tried today to install evolution x on my brand new OnePlus 8T and when the installation was over I noticed that my phone would not reboot. When I tried to reboot it myself then it went back to FastBoot.
I tried the "Start" and the "Restart bootloader" options but it didn't work.
I tried the "Power off" option and then restarted it but it went back to FastBoot
I even tried the "Recovery mode" but with every option in it nothing changed. I was either going back to Recovery Mode or to FastBoot
I would really appreciate any help. Please let me know if I can do anything.

You can follow this guide:
[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Use button combination boot up EDL mode is little tricky. If you can access fastboot, use command "fastboot oem edl" boot EDL.
You may need to install the EDL driver manually, This is very important:
Some_Random_Username said:
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008 ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
Click to expand...
Click to collapse

sfoklus said:
So I tried today to install evolution x on my brand new OnePlus 8T and when the installation was over I noticed that my phone would not reboot. When I tried to reboot it myself then it went back to FastBoot.
I tried the "Start" and the "Restart bootloader" options but it didn't work.
I tried the "Power off" option and then restarted it but it went back to FastBoot
I even tried the "Recovery mode" but with every option in it nothing changed. I was either going back to Recovery Mode or to FastBoot
I would really appreciate any help. Please let me know if I can do anything.
Click to expand...
Click to collapse
I'm assuming you used TWRP from https://forum.xda-developers.com/t/recovery-11-alpha-teamwin-recovery-project-8t-kebab.4302449/ to flash the rom. I'm guessing you forgot to flash the TWRP installer after flashing the rom otherwise you'd be able to get back to TWRP.
Flash the TWRP img file to recovery again while you're in fastboot. That should let you boot into recovery.