Database Info

Urgent help needed + QFIL

Hi guys,
As mentioned in a previous thread, my F1 is soft bricked, only with the Oppo logo, no fastboot or recovery. I need to flash it again with a soft called QFIL (soft for Qualcomm devices). But it can't be done with the ordinary stock roms, I need a specific rom compatible with QFIL, like the ones used in the service centers. Is there anyone who can provide me with such a rom, or a link to download one in order to save my device?
Thank you

Can someone owning a Oppo f1 use QFIL to extract all the necessary files in order to flash them to my phone? I would be very grateful.

I have the, flashing tool and rom needed to unbrick the f1 from any softbricked state.
Let me know if you still need it, and I'll upload it somewhere and write a quick guide.
Worked for me even after I killed the bootloader.

tb303lava said:
I have the, flashing tool and rom needed to unbrick the f1 from any softbricked state.
Let me know if you still need it, and I'll upload it somewhere and write a quick guide.
Worked for me even after I killed the bootloader.
Click to expand...
Click to collapse
Hi, good news, I would be glad and would appreciate if you could send them to me.
Thanks in advance.

QDLoader Flasher Drivers and Firmware.
This will unbrick the Oppo F1f even if bootloader has been corrupted.
How to:
Download and extract this archive.
Install the QDLoader driver found in the DRIVER directory of the extracted archive.
Switch phone off, hold Vol-Up and connect USB cable between phone Pc .
Run Msm8x39DownloadTool.exe (in F1EX_11_A.05_160128 directory) as Administrator.
Select phone type (16GB or 32GB)
Choose the port your phone is connected to from the list. (It will be the one which says Com Device as Device Type.
Tick "Reset when .."
Click Start.
Let it do its thing, and bam! working stock F1f.
warning this will delete all user data.
Any questions PM me.
Al

tb303lava said:
QDLoader Flasher Drivers and Firmware.
This will unbrick the Oppo F1f even if bootloader has been corrupted.
How to:
Download and extract this archive.
Install the QDLoader driver found in the DRIVER directory of the extracted archive.
Switch phone off, hold Vol-Up and connect USB cable between phone Pc .
Run Msm8x39DownloadTool.exe (in F1EX_11_A.05_160128 directory) as Administrator.
Select phone type (16GB or 32GB)
Choose the port your phone is connected to from the list. (It will be the one which says Com Device as Device Type.
Tick "Reset when .."
Click Start.
Let it do its thing, and bam! working stock F1f.
warning this will delete all user data.
Any questions PM me.
Al
Click to expand...
Click to collapse
Hi, I downloaded the zip, followed your steps and...my phone is alive and everything works perfectly. Thank you so much for your help. Couldn't have been done without you.

How to choose the port?? I am not able to choose the port. When i connect it to pc whole holding volume up button it doesn't show anything.

sir is your file is from optus australia
tb303lava said:
QDLoader Flasher Drivers and Firmware.
This will unbrick the Oppo F1f even if bootloader has been corrupted.
How to:
Download and extract this
Install the QDLoader driver found in the DRIVER directory of the extracted archive.
Switch phone off, hold Vol-Up and connect USB cable between phone Pc .
Run Msm8x39DownloadTool.exe (in F1EX_11_A.05_160128 directory) as Administrator.
Select phone type (16GB or 32GB)
Choose the port your phone is connected to from the list. (It will be the one which says Com Device as Device Type.
Tick "Reset when .."
Click Start.
Let it do its thing, and bam! working stock F1f.
warning this will delete all user data.
Any questions PM me.
Al
Click to expand...
Click to collapse
oppo f1f from optus australia need qfill firmware
i m from india set come to me for sim unlock
i follow this guide (How To unlock Oppo F1f - Guide unlock network Oppo mobile F1f from youtube) to flash modified firmware
but at the first step i flashed magictricks.zip & set goes to qdloader 9008 mode after reboot
so i need optus australia firmware,thanks in advance

Need some help - Msm8x39DownloadTool.exe not finding phone
Qualcomm HS-USB QSLoader9008 on COM3, according to Device Manager, yet Msm8x39DownloadTool.exe doesn't want to find it at all - Device not connected.
Any help would be really appreciated.
Edit: I have made some progress with some steps not included above.
1) Disable 'Driver Signature Enforcement' in Windows (Google is your friend)
2) Before installing the provided drivers, hold the Volume Up button on your phone, and insert USB from PC > Phone. This places the phone into QHSUSB mode and will be found in Device Manager, under Ports (The Android Bootloader Interface (fastboot) device has an ID of '18D1-D00D', while the QHSUSB device ID is '05C6-9008'.. bingo!).
3) Install the driver as directed. This will change the device from QHSUSB mode to HS-USB QDLoader 9008 on COM3.
Continue with the rest of the guide.
Stock recovery will be returned (v1.2 Rooted - I don't remember this). From here you can install Project Spectrum again, and return back to ColorOS after that.
Hopefully this helps.

tb303lava said:
QDLoader Flasher Drivers and Firmware.
This will unbrick the Oppo F1f even if bootloader has been corrupted.
How to:
Download and extract this archive.
Install the QDLoader driver found in the DRIVER directory of the extracted archive.
Switch phone off, hold Vol-Up and connect USB cable between phone Pc .
Run Msm8x39DownloadTool.exe (in F1EX_11_A.05_160128 directory) as Administrator.
Select phone type (16GB or 32GB)
Choose the port your phone is connected to from the list. (It will be the one which says Com Device as Device Type.
Tick "Reset when .."
Click Start.
Let it do its thing, and bam! working stock F1f.
warning this will delete all user data.
Any questions PM me.
Al
Click to expand...
Click to collapse
I tried this my phone has no Fastboot but recovery says V1.2(Rooted)
I tried this multiple times without luck.

As you still have access to stock recovery, you dont need to use download mode.
Simply put a stock rom zip on your sdcard and flash via the stock recovery. (might have to wipe data also if flashing a different version of the rom).
That will fix your phone.
To get access to fastboot (should you need to flash TWRP recovery), flash magictricks.zip via recovery.
If your phone is so busted you no longer have access to fastboot and recovery it will automatically default to QDloader mode (download mode).
If you want to access download mode while your recovery is still ok, switch phone off, hold Vol-Up (or Vol-down, can't recall) and plug in the usb cable.
AS LONG AS YOU HAVE ACCESS TO RECOVERY, USE THAT TO FLASH A STOCK FIRMWARE, GETTING THE QDLOADER DRIVERS CORRECTLY INSTALLED ON WINDOWS CAN BE RATHER TRICKY.

tb303lava said:
I have the, flashing tool and rom needed to unbrick the f1 from any softbricked state.
Let me know if you still need it, and I'll upload it somewhere and write a quick guide.
Worked for me even after I killed the bootloader.
Click to expand...
Click to collapse
Hey man can you help I've soft bricked my oppo, please need flashing tool and rom

phaw16 said:
I tried this my phone has no Fastboot but recovery says V1.2(Rooted)
I tried this multiple times without luck.
Click to expand...
Click to collapse
HEY BRO HOW DID YOU FIX YOUR F1f SAME PROBLEM HERE I TRY THE STEPS ABOVE BOT INSTALLATION FAILED WHEN FLASHING A ROM please HElp me ver 1.2(rooted)

after flashing my f1f just going to RECOVERY then its auto turn ON and recovery again. bootloop to recovery any fix?

tb303lava said:
QDLoader Flasher Drivers and Firmware.
This will unbrick the Oppo F1f even if bootloader has been corrupted.
How to:
Download and extract this
Install the QDLoader driver found in the DRIVER directory of the extracted archive.
Switch phone off, hold Vol-Up and connect USB cable between phone Pc .
Run Msm8x39DownloadTool.exe (in F1EX_11_A.05_160128 directory) as Administrator.
Select phone type (16GB or 32GB)
Choose the port your phone is connected to from the list. (It will be the one which says Com Device as Device Type.
Tick "Reset when .."
Click Start.
Let it do its thing, and bam! working stock F1f.
warning this will delete all user data.
Any questions PM me.
Al
Click to expand...
Click to collapse
thanks sir, its work
Edabigael said:
after flashing my f1f just going to RECOVERY then its auto turn ON and recovery again. bootloop to recovery any fix?
Click to expand...
Click to collapse
u neeed to flash OTA firmware from recovery, that what i did.. i use F1EX_11_OTA_002_all_201601170010.. put on your sd card and install

[HOWTO]Unlock bootloader/root for most G7's except T-Mo via EDL Mode (EASIER METHOD)

Hi everyone!!
IMPORTANT:NEVER SELECT ERASE OR FORMAT PARTITIONS IN LGUP. IT WILL MESS WITH YOUR IMEI
Im making a new guide to unlock your bootloader/root your device. Its easier to do a little bit risker but if you do it slowly you wont mess up your phone and in the event you do you can always recover it. Remember to FOLLOW ALL THE STEPS or you may end up messing up your phone, The best thing is, you dont need to downgrade to even unlock the bootloader!!
DISCLAIMER: I AM NOT RESPONSIBLE IF YOUR PHONE BRICKS! YOU ARE FOLLOWING THIS GUIDE AND ITS YOUR CHOICE TO DO IT OR NOT TO DO IT AND YOURE THE ONE DOING IT. I JUST WANT TO HELP OTHERS OUT.
If you cant for some reason access fastboot even flashing the v35 file, use this guide: https://forum.xda-developers.com/lg-g7-thinq/how-to/verizon-lg-g710vm20f-t4057031 it says verizon but i think most of the models of the g7 cant acess fastboot so you can try this.
Requirments:
-A PC
-USB Cable to connect your phone of course
- V35 ABL
--The LG FIrehose file
- QPST/QFIL
-9008 drivers FOLLOW THIS GUIDE!! To install drivers properly IF WINDOWS DOESNT INSTALL THEM AUTOMATICALLY!!
-ADB PLATFORM or someway to access fastboot via cmd
-PATIENCE!!
Steps.
Download the V35 abl,LG Fire house file, download and install qppst and install the 9008 drivers (WUNDOWS 10 should automatically do it for you) If not, download it and install them.
Boot into edl mode via connecting your phone to the pc then turning it off. Hold Vo- and power and keep pushing the vol+ button multiple times when it turns off.
Go into device manager and check if its detected. to check open up device manager and check Ports and it should say Some port 9009 Qualcomm or something like that (IF theres a question mark, exclamation mark or it says qhusb bulk even after you install the drivers, make sure you disable driver signature enforcment on windows and install the drivers again. Theres multiple ways to do it just google on how to disable driver signature enforcment windows 10. Same with windows 7/8,)
Run as administrator qfil and select flat build,.
--Programmer Type: Load the firehose file
-- On the top go to configuration and where it says Device type, make sure you change it to ufs.
-- Click ok to save and exit
At this point qfil should be detecting your port . If not there should be a select port button next to it on top.
Go to Tools then Partition Manager
A window should pop up with all the partitions. If you get a shara failed error, make sure your drivers are installed correctly and try rebooting into edl again once more. To do that just hold vol - and power until the lg logo comes up and then keep holding vol - and power again and once it turns off again just do the edl combination again.
Search for abl_a and right click on it. First do Read Data, it should take only a couple of seconds Then Load Image and load the v35 image. It should say GPT Finished or something like that at the log with no errors.
Reboot holding volume - and power for like 20-30 seconds until the lg logo comes up Then hold the down button to boot into fastboot or it will automatically boot into fastboot depending on what version of android you are on.
Open the folder where your adb tools are, then hold shift +Right Click in the folder and open powershell. Type and enter CMD
Enter: Fastboot oem unlock it should output with OKAY, If it gives you unknown command, try a USB 2.0 port and then turn off your phone and while its booting up enter the command before you boot into fastboot. Once thats done dont close the window yet!!
Once thats done you can now restore your other abl so you can boot back into android. To do that run %appdata% in the search bar or in the run window by holding the windows button and pressing the R button. Then you should be in C:\Users\{YOUR USERNAME}\AppData\Roaming
Open up the Qualcomm folder --> QFIL --> COMPORT#
There should be a ReadData Blah blah.bin in there. Drag and drop that in the folder where your adb tools are
then go back to the window i told you not to close (The powershell/cmd window) then do fastboot flash abl_a (The file name with ReadData) without the ( ).
Now you can turn off the phone vial holding volume - and power and then reboot into android!! You should get a bootloader unlocked or a cannot be checked for courrption message! Congrats your bootloader is unlocked!!
To root: Just back up your boot image via and then find it in %Appdata% put it in your phone then use magisk manager to patch the boot file and then take that boot file and then flash it to boot_a via edl.
I tried my best to write this guide and sorry for my grammatical mistakes. Ill be helping people unlock/root their bootloaders for free during this covid time as well. If you want to donate you can always tell me but its not necessary.
Ill try making a video as soon as i can.

Nice guide,
Will I able to use this guide to root my G7 verizon version ? (G710VM)
Thanks ?

nyolai said:
Nice guide,
Will I able to use this guide to root my G7 verizon version ? (G710VM)
Thanks
Click to expand...
Click to collapse
Should be in theory

nyolai said:
Nice guide,
Will I able to use this guide to root my G7 verizon version ? (G710VM)
Thanks
Click to expand...
Click to collapse
Yes and no. Yes it will unlock the bootloader but the problem with verizon there is no fastboot unless you erase the laf imgs.
Which is why in my guide I use the crossflashed ULM11g it has fastboot and the oem unlock enable button which makes it easier to issue the "fastboot oem unlock" command.
Give it a try and if your not good at doing this with qfil will brick your device. If you run into issues try my guide.
https://forum.xda-developers.com/lg-g7-thinq/how-to/verizon-lg-g710vm20f-t4057031

netookska05 said:
Yes and no. Yes it will unlock the bootloader but the problem with verizon there is no fastboot unless you erase the laf imgs.
Which is why in my guide I use the crossflashed ULM11g it has fastboot and the oem unlock enable button which makes it easier to issue the "fastboot oem unlock" command.
Give it a try and if your not good at doing this with qfil will brick your device. If you run into issues try my guide.
https://forum.xda-developers.com/lg-g7-thinq/how-to/verizon-lg-g710vm20f-t4057031
Click to expand...
Click to collapse
Ill add your link to my thread.

Awesomeslayerg said:
Requirments:
-A PC
-USB Cable to connect your phone of course
- V35 ABL
-The LG FIrehose file
- QPST/QFIL
-9008 drivers
-ADB PLATFORM or someway to access fastboot via cmd
-PATIENCE!!
Click to expand...
Click to collapse
All the links to files redirect to "Unbrick G7" file.

I m stuck in this step
A window should pop up with all the partitions. If you get a shara failed error, make sure your drivers are installed correctly and try rebooting into edl again once more. To do that just hold vol - and power until the lg logo comes up and then keep holding vol - and power again and once it turns off again just do the edl combination again.
always got Shara failed error.
Has windows 10 and tried all possibilities.
The driver not detected automatically so installed manually. Please Help

TigerV said:
I m stuck in this step
A window should pop up with all the partitions. If you get a shara failed error, make sure your drivers are installed correctly and try rebooting into edl again once more. To do that just hold vol - and power until the lg logo comes up and then keep holding vol - and power again and once it turns off again just do the edl combination again.
always got Shara failed error.
Has windows 10 and tried all possibilities.
The driver not detected automatically so installed manually. Please Help
Click to expand...
Click to collapse
Do you have ELF File for the programmer> The one included in the zip file? Sorry i didnt include the ABL Ill update the zip soon Do you get an exclmation mark or something on the ports in devnice manager?

Awesomeslayerg said:
Do you have ELF File for the programmer> The one included in the zip file? Sorry i didnt include the ABL Ill update the zip soon Do you get an exclmation mark or something on the ports in devnice manager?
Click to expand...
Click to collapse
Thanks for your update.
Yes I m using the same ELF file from zip.
The driver not installed automatically so I have installed it manually via device manager and thn no exclamation mark. But somehow its not work. Tried many time but the same issue

Can you please update the link of 9008 driver and guide? Its not working (may be bad link)

TigerV said:
Can you please update the link of 9008 driver and guide? Its not working (may be bad link)
Click to expand...
Click to collapse
Fixed it. Make sure whenever you close qfil or everythime you get that error just reboot into edl mode again.

****.. Unlocked bootloader. Lost Widewine L1. Relocked bootloader again. but Widewine L3 is available. Anyway to get it back to L1. I remember My pixel and Op6 could get back Widewine L1 after relocking bootloader again.

Awesomeslayerg said:
Fixed it. Make sure whenever you close qfil or everythime you get that error just reboot into edl mode again.
Click to expand...
Click to collapse
Thanks somehow I manged for get edl and flashed the image.
Now getting another issue. when I do "Fastboot oem unlock" its say
FAILED (remote: unknown command)
finished. total time: 0.002s
tried will all method with different PC, Different USB and all as mentioned in the main post, but no luck.

TigerV said:
Thanks somehow I manged for get edl and flashed the image.
Now getting another issue. when I do "Fastboot oem unlock" its say
FAILED (remote: unknown command)
finished. total time: 0.002s
tried will all method with different PC, Different USB and all as mentioned in the main post, but no luck.
Click to expand...
Click to collapse
From ecperince just keep doing that. Nut before entering fastboot put the command in and press enter then reboot directly into fastboot. Kerp doing it unt you see the orsnge unlocked bootloader on your g7 screen

Hey op or whomever can help point me in the right direction: when looking at used/refurbished g7's which models should I ask sellers about or steer away from like the LMG710R (I know the LMG710TM is a no go, what about the Sprint unlocked for GSM and what's there code if I want to avoid them?)?
Thanks.

the v35abl file is not avaliable

wente said:
the v35abl file is not avaliable
Click to expand...
Click to collapse
here is the same link from main post (that link has some hyperlink issue)
https://androidfilehost.com/?fid=1899786940962574206

Would this work on LG710N (korean) ??

Once the bootloader is unlocked with this method DRM is lost forever. Even relocking the bootloader will not bring Widewine certification to L1. I am back to stock with locked bootloader. Widewine is at L3.

Awesomeslayerg said:
From ecperince just keep doing that. Nut before entering fastboot put the command in and press enter then reboot directly into fastboot. Kerp doing it unt you see the orsnge unlocked bootloader on your g7 screen
Click to expand...
Click to collapse
have tried many many time and all possible way but no luck
---------- Post added at 06:25 PM ---------- Previous post was at 06:23 PM ----------
coolrevi said:
Once the bootloader is unlocked with this method DRM is lost forever. Even relocking the bootloader will not bring Widewine certification to L1. I am back to stock with locked bootloader. Widewine is at L3.
Click to expand...
Click to collapse
re-lock and stock flash also not in bring back to L1? I can not even unlock my boot-loader. stuck at "fastboot oem unlock" and its not working, tried all possible way

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.

oneplus 8t(tmo) hardstuck in fastboot mode

Been trying to fix my phone for two days. first time rooting and it was kind of a success besides the wifi not working so i wanted to undo the root. tried many things and apparently messed up many things. The phone will not go into recovery mode. It wont turn on. if i try to flash anything i get many different errors(even twrp). And yes ive made sure everything is for my phones version(s). Oneplus 8t tmobile. so basically the phone can turn off and go into fastboot and the only thing inbetween that is it shows the 1+ logo for a split second.
"fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable."
"unknown partition"
"FAILED (remote: 'Flashing is not allowed for Critical Partitions" btw bootloader is unlocked so dont understand how this is happening unless im misunderstanding the meaning
msm will not detect my phone also. even updated the qualcomm drivers and still nothing. however can't really find a sure fire way to determine if the phone is in edl mode besides it connecting in msm. which i haven't been able to do even at the start of yesterday when the phone could atleast flash twrp and boot edl from there. Pls help

lostneedfound said:
Been trying to fix my phone for two days. first time rooting and it was kind of a success besides the wifi not working so i wanted to undo the root. tried many things and apparently messed up many things. The phone will not go into recovery mode. It wont turn on. if i try to flash anything i get many different errors(even twrp). And yes ive made sure everything is for my phones version(s). Oneplus 8t tmobile. so basically the phone can turn off and go into fastboot and the only thing inbetween that is it shows the 1+ logo for a split second.
"fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable."
"unknown partition"
"FAILED (remote: 'Flashing is not allowed for Critical Partitions" btw bootloader is unlocked so dont understand how this is happening unless im misunderstanding the meaning
msm will not detect my phone also. even updated the qualcomm drivers and still nothing. however can't really find a sure fire way to determine if the phone is in edl mode besides it connecting in msm. which i haven't been able to do even at the start of yesterday when the phone could atleast flash twrp and boot edl from there. Pls help
Click to expand...
Click to collapse
WiFi not working because the boot.img you flash is not match your system version.
ULTRAJC said:
If you have to use online source patched boot.img, don't flash, only do "fastboot boot boot.img", if it can successfully boot into the system, then use magisk patch current system boot.img and reboot.
Click to expand...
Click to collapse
You can use command "fastboot oem edl".
EDL mode(usually a full black screen) will timeout in few seconds if not receive any command from MSM, so you can start MSM flash frist then put phone to EDL.
Two possible situations need attention:
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
Some_Random_Username said:
Why is my device getting in Qualcomm crashdump mode in spite of a successful download?
Your unit was most likely manufactured after March 9th 2021, see https://forum.xda-developers.com/t/...ice-to-oxygenos.4180837/page-14#post-84789741 for reference. You therefore need to use HydrogenOS 11.0.7.12 MSM to recover your device linked at https://www.oneplusbbs.com/thread-5886794-1.html (mirrored at https://mega.nz/file/O8UySbgR#cXGlHkdA_7CYEhKIrek9zzAEwJ7Vx1D5BZdemnPlvGE by @pikatenor ). Getting new OxygenOS MSM tools is nowadays impossible unless you own the device it is meant for, so OP will not be updated to add new OxygenOS MSM tools allowing to workaround this issue. Feel however free to reach out to me in DM if you would like to get told how to maximise your chances to obtain one.
Click to expand...
Click to collapse
If MSM just not work or you not using Windows, you can follow:
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com

ULTRAJC said:
WiFi not working because the boot.img you flash is not match your system version.
You can use command "fastboot oem edl".
EDL mode(usually a full black screen) will timeout in few seconds if not receive any command from MSM, so you can start MSM flash frist then put phone to EDL.
Two possible situations need attention:
If MSM just not work or you not using Windows, you can follow:
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
Click to expand...
Click to collapse
fastboot oem edl results in FAILED (remote: unknown command). tried it in minimal adb and fastboot and platformtools.

and that is the guide ive been following. however i keep getting partition issues.

lostneedfound said:
and that is the guide ive been following. however i keep getting partition issues.
Click to expand...
Click to collapse
Fastboot unbrick guide didn't work for you?
Maybe continue to try the key combination, open device manager, if you see devices name: …QDLoader 9008(driver installed) or …QHUSB_BULK(driver not install). That's EDL mode.
Some guide suggest this two command may work:
"fastboot reboot edl"
"fastboot reboot-edl"
Also can try "fastboot boot recovery that have adb.img" then use command "adb reboot edl".

okay so i none of that worked just continues to say unknown command or unknown partition. with the qual com i dont see anything otherthan android device for phone related stuff in the device manager. is there something ican do to get these partition errors to go away? last night i wasn't having any trouble with them and now they are everywhere and i really dont understand why becuase i hardly flashed anything last night. today i started flashing stuff from the guide you recommended/the one ive been using all this time and thats when the partition errors started and now im seeing them everywhere and i followed the guide down to the dime.

solved out of pure rage i restored my pc to factory and when it started back up i redownload msm and phone connected perfectly. also correctly rooted by adb pulling my own boot.img. ty for your help

lostneedfound said:
solved out of pure rage i restored my pc to factory and when it started back up i redownload msm and phone connected perfectly. also correctly rooted by adb pulling my own boot.img. ty for your help
Click to expand...
Click to collapse
That was one way to go, but for others. The problem was your adb/fastboot was old. Should no longer use the minimal adb it's outdated. Always use the latest platform tools.

nujackk said:
That was one way to go, but for others. The problem was your adb/fastboot was old. Should no longer use the minimal adb it's outdated. Always use the latest platform tools.
Click to expand...
Click to collapse
Exactly @nujackk ,
I have found the most likely reason for an "unknown command" message to a newer fastboot command is an old fastboot.exe version.

Bricked Oneplus 8T (device state - locked) data recovery

Hi All!
I am in a bit of an unfortunate situation, and am also not that knowledgeable with Android.
I want to recover data on my phone, I would be happy with just recovering the photos.
My Oneplus 8T currently gives me a Quallcom crash dump error when trying to boot. I am also able to go into Fastboot mode with the power button + volume up/down.
Just now, I tried booting the device to TWRP recovery. I first installed Google usb driver, then updated the driver of my Oneplus 8T in device manager. I installed a TWRP recovery image of a Oneplus 8T and put that file where I downloaded Google platform tools. I then ran 'fastboot devices' and saw my device. However, after running 'fastboot boot twrp.img', I received the error 'boot is not allowed in Lock state'.
I cannot remember if USB debugging is enabled or not. I would really appreciate it if anyone could help me out as online articles have been quite useless and also very confusing.

Try fastboot getvar all then do fastboot set_active to either a or b depending on which partion you are on you want to change it also pretty sure USB debugging doesn't matter in bootloader you can also try fastboot oem unlock to unlock bootloader to boot twrp unless you updated to oos twrp doesn't work yet

No no no no.
you have loaded dynamic system image = Super image with incorrect.
Go to this link https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_8T/
And choose your union and version you want.
Download better driver https://onepluscommunityserver.com/list/Unbrick_Tools/Qualcomm drivers.7z
Now you can use the MSM download troll and get your phone back. Install driver and unzip MSM. Start MSM with admin. Select download mode in MSM. Now press power and vol - and vol + at the same time. Your PC will see a new device. Your phone screen is black. Start MSM and wait for it to finish. Google Translate.

JonasHS said:
No no no no.
you have loaded dynamic system image = Super image with incorrect.
Go to this link https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_8T/
And choose your union and version you want.
Download better driver https://onepluscommunityserver.com/list/Unbrick_Tools/Qualcomm drivers.7z
Now you can use the MSM download troll and get your phone back. Install driver and unzip MSM. Start MSM with admin. Select download mode in MSM. Now press power and vol - and vol + at the same time. Your PC will see a new device. Your phone screen is black. Start MSM and wait for it to finish. Google Translate.
Click to expand...
Click to collapse
With MSM he will get everything wiped on his device. This is not he is intending to do.

AK138 said:
Hi All!
I am in a bit of an unfortunate situation, and am also not that knowledgeable with Android.
I want to recover data on my phone, I would be happy with just recovering the photos.
My Oneplus 8T currently gives me a Quallcom crash dump error when trying to boot. I am also able to go into Fastboot mode with the power button + volume up/down.
Just now, I tried booting the device to TWRP recovery. I first installed Google usb driver, then updated the driver of my Oneplus 8T in device manager. I installed a TWRP recovery image of a Oneplus 8T and put that file where I downloaded Google platform tools. I then ran 'fastboot devices' and saw my device. However, after running 'fastboot boot twrp.img', I received the error 'boot is not allowed in Lock state'.
I cannot remember if USB debugging is enabled or not. I would really appreciate it if anyone could help me out as online articles have been quite useless and also very confusing.
Click to expand...
Click to collapse
Run fastboot flash recovery twrp.img ... And then fastboot reboot recovery or choose recovery on your phone.
Sometimes holding volume up and power to do a soft reset boots back into system worth a try.