Database Info

[Q] Bootloop, fastboot is not recognized

Hi everybody,
I tried to unlock and root my device with the nexus 5 multi Tool 3.0 and now i am stuck in a bootloop.
My nexus is unlocked, it had installed CMW (yet i had chosen to selected twrp. Normaly it should have rebooted but it went automattically in CMW). So i wanted to go out of CMW and it asked if it wanted to restore the original recovery but i denied it and then it stuck in BOOTLOOP.
I tried the unbrick tool of KWOGGER but it failed, it said "fastboot is not recognized as an internal or external command operable program or batch file"
Since i could get into CMW i tried to do a factory reset but it would be still in bootloop.
I then tried; http://forum.xda-developers.com/showthread.php?t=2513701, But it still said "fastboot is not recognized as an internal or external command operable program or batch file" when i doubble clicked on "flash-all"
I Am getting desperate here, i just got my device. Can someone please help me

Install drivers. Don't use toolkits until you know what they are doing.
Sent from my Nexus 5 using Tapatalk

Follow this to return to stock. Then don't use tools but learn how to do it manually. http://forum.xda-developers.com/showthread.php?p=47156064
Edit, saw I linked you to the same site. Don't panic. You don't have adb fastboot set up right. Follow those instructions carefully.

[Q] Motorola Moto G Lost OS

Hey guys,
Recovery : TWRP 2.6.3.3
USB Debugging : Off
Cannot connect to PC.
Recently, I accidently formatted my Moto G through the advanced wipe and I selected all the partitions to be wipe such as dalvik cache, data, internal storage, cache and system. And now my Moto G doesn't have any OS in it and I can't reboot it at all. I don't have any idea what to do right now. Can someone please help me how can I install a new rom for my Moto G so I can use it like a normal phone again. Please no harsh words, I know it's my mistake and I really need help.

Make sure you post things like this in the Q&A section ull get better help over there then in this General section

Xavier102296 said:
Make sure you post things like this in the Q&A section ull get better help over there then in this General section
Click to expand...
Click to collapse
Thanks

You just need to flash a ROM.

Ammar115 said:
Hey guys,
Recovery : TWRP 2.6.3.3
USB Debugging : Off
Cannot connect to PC.
Recently, I accidently formatted my Moto G through the advanced wipe and I selected all the partitions to be wipe such as dalvik cache, data, internal storage, cache and system. And now my Moto G doesn't have any OS in it and I can't reboot it at all. I don't have any idea what to do right now. Can someone please help me how can I install a new rom for my Moto G so I can use it like a normal phone again. Please no harsh words, I know it's my mistake and I really need help.
Click to expand...
Click to collapse
If you are able to go to recovery(which you should be able to do), download any custom ROM of your choice like PA, CM, SLIM etc.. flash that rom by following the Installation instructions in the thread. YOu should be able to get the phone back to normal. And if you want the stock ROM, then download the stock files and flash it, you might loose custom recovery, then follow the same things you did to get TWRP in the first place.

phanitej said:
If you are able to go to recovery(which you should be able to do), download any custom ROM of your choice like PA, CM, SLIM etc.. flash that rom by following the Installation instructions in the thread. YOu should be able to get the phone back to normal. And if you want the stock ROM, then download the stock files and flash it, you might loose custom recovery, then follow the same things you did to get TWRP in the first place.
Click to expand...
Click to collapse
I would if I could. The problem is I formatted the whole phone which included the internal storage too. My CM Rom is in the internal storage and it's already deleted. I tried to connect my phone to the pc so that I could transfer a rom into it but failed cause my pc won't recognized my phone as the media transfer devices. It's only recognized my phone as fastboot falcon s. I've installed Motorola Device Manger but it's also failed. I also tried to install using adb sideload but I got device not found error and my phone doesn't listed in the device attached after I typed 'adb devices'. For the OTG and memory card reader method I haven't try yet because I don't have any of it.

Ammar115 said:
I would if I could. The problem is I formatted the whole phone which included the internal storage too. My CM Rom is in the internal storage and it's already deleted. I tried to connect my phone to the pc so that I could transfer a rom into it but failed cause my pc won't recognized my phone as the media transfer devices. It's only recognized my phone as fastboot falcon s. I've installed Motorola Device Manger but it's also failed. I also tried to install using adb sideload but I got device not found error and my phone doesn't listed in the device attached after I typed 'adb devices'. For the OTG and memory card reader method I haven't try yet because I don't have any of it.
Click to expand...
Click to collapse
What does it say when you try
Code:
adb devices
or
when you reboot to bootloader with phone connected and type
Code:
fastboot devices
If it shows a device for fastboot devices then follow this to flash back to stock. Make sure you download the right stock firmware for your phone.

phanitej said:
What does it say when you try
Code:
adb devices
or
when you reboot to bootloader with phone connected and type
Code:
fastboot devices
If it shows a device for fastboot devices then follow this to flash back to stock. Make sure you download the right stock firmware for your phone.
Click to expand...
Click to collapse
when I type 'adb devices' it give me an error saying that my device is not found. for the 'fastboot devices', I tried it too but also an error. It say, 'fastboot' is not recognized as an internal or ecternal command, operable program or batch file.

Ammar115 said:
when I type 'adb devices' it give me an error saying that my device is not found. for the 'fastboot devices', I tried it too but also an error. It say, 'fastboot' is not recognized as an internal or ecternal command, operable program or batch file.
Click to expand...
Click to collapse
It seems like you dont have fastboot files. Follow the same link that i posted in the previous one. It has portable adb & fastboot files. Download that and then follow instructions. You should be able to get to fastboot. Once you are there the job is almost done. Hope it helps
Edit: Here is the link to download and install the minimal adb & fatsboot files

phanitej said:
It seems like you dont have fastboot files. Follow the same link that i posted in the previous one. It has portable adb & fastboot files. Download that and then follow instructions. You should be able to get to fastboot. Once you are there the job is almost done. Hope it helps
Edit: Here is the link to download and install the minimal adb & fatsboot files
Click to expand...
Click to collapse
This is what I get using minimal adb and fastboot. What does it mean?

phanitej said:
It seems like you dont have fastboot files. Follow the same link that i posted in the previous one. It has portable adb & fastboot files. Download that and then follow instructions. You should be able to get to fastboot. Once you are there the job is almost done. Hope it helps
Edit: Here is the link to download and install the minimal adb & fatsboot files
Click to expand...
Click to collapse
I've followed all the instructions but my phone still not rebooting. When I try to reboot it, it only show me the warning of unlocked bootloader screen, black screen, warning of unlocked bootloader screen then dead android screen. What should I do now?

It means your phone is in fastboot mode and recognised by your PC. Next you'll have to "fastboot flash" the necessary files to install a recovery and a system, and you should be good to go.

Few weeks back I ****ed up soft bricked my phone had kindda same issue when I switch my phone on I get a dead android logo. Gave to the service center in India and got a replacement a new xt1033
P.s I was trying to root and my warranty was void still got a new one try your luck bruhhh
Sent from my XT1033 using XDA Free mobile app

SbM_ said:
It means your phone is in fastboot mode and recognised by your PC. Next you'll have to "fastboot flash" the necessary files to install a recovery and a system, and you should be good to go.
Click to expand...
Click to collapse
I only want to connect my phone to my pc so I can transfer any rom to my phone so that I can install the rom. But right now, my pc won't recognized it as media transfer that's why I can't transfer any file to my phone. I tried everything. I've installed motorola device manager but all that I got is motorola adb interface that make my phone can connect to the pc when in bootloader mode.I don't have any OTG cable or mobile sd card reader.

phanitej said:
It seems like you dont have fastboot files. Follow the same link that i posted in the previous one. It has portable adb & fastboot files. Download that and then follow instructions. You should be able to get to fastboot. Once you are there the job is almost done. Hope it helps
Edit: Here is the link to download and install the minimal adb & fatsboot files
Click to expand...
Click to collapse
Hey, I've done all of the flashing instruction from the xda forum link that you gave me. My problem for now is, why is my phone not rebooting? The only thing that happen after the flashing is my phone only show the 'warning bootloader unlocked' and the dead android with red triangle screen. It won't boot into the stock rom that I've flashed. The stock rom/firmware that I used is correct. Please help me.. I really need to use my phone.

Ammar115 said:
Hey, I've done all of the flashing instruction from the xda forum link that you gave me. My problem for now is, why is my phone not rebooting? The only thing that happen after the flashing is my phone only show the 'warning bootloader unlocked' and the dead android with red triangle screen. It won't boot into the stock rom that I've flashed. The stock rom/firmware that I used is correct. Please help me.. I really need to use my phone.
Click to expand...
Click to collapse
K there's a resolve for this...Provided that you haven't ****ed up your phone by making it hard bricked...
1 - Get a freaking rom and sideload it through TWRP to boot into system...
+ Download a ROM
+ Put it in the same folder as ADB and Fastboot and rename it to something easier that you can type exactly (ex: 1.zip, backup.zip...)
+ Shift + Right Click at a blank field in the window
+ Choose Open Command....
+ On TWRP, go to Advanced => Sideload => Tick the 2 boxes => Swipe to start sideloading
+ Type in adb sideload <yourzipname>.zip on the cmd (on your computer)
+ Wait for the process to finish, then you now have a working phone...
2 - Follow this guide using the proper firmwares that match your original one : http://forum.xda-developers.com/showthread.php?t=2542219

Zerelth said:
K there's a resolve for this...Provided that you haven't ****ed up your phone by making it hard bricked...
1 - Get a freaking rom and sideload it through TWRP to boot into system...
+ Download a ROM
+ Put it in the same folder as ADB and Fastboot and rename it to something easier that you can type exactly (ex: 1.zip, backup.zip...)
+ Shift + Right Click at a blank field in the window
+ Choose Open Command....
+ On TWRP, go to Advanced => Sideload => Tick the 2 boxes => Swipe to start sideloading
+ Type in adb sideload <yourzipname>.zip on the cmd (on your computer)
+ Wait for the process to finish, then you now have a working phone...
2 - Follow this guide using the proper firmwares that match your original one : http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Done but still, the same thing happened.

Ammar115 said:
I only want to connect my phone to my pc so I can transfer any rom to my phone so that I can install the rom. But right now, my pc won't recognized it as media transfer that's why I can't transfer any file to my phone. I tried everything. I've installed motorola device manager but all that I got is motorola adb interface that make my phone can connect to the pc when in bootloader mode.I don't have any OTG cable or mobile sd card reader.
Click to expand...
Click to collapse
Your PC will not recognize it as media transfer / storage while you are in bootloader / fastboot mode, its perfectly normal. When you type fastboot devices it should show you a number which means it working as intended. This is an old thread but it shows how to transfer your ROM to sdcard via adb push command. http://forum.xda-developers.com/showthread.php?t=1667929

Ammar115 said:
I only want to connect my phone to my pc so I can transfer any rom to my phone so that I can install the rom. But right now, my pc won't recognized it as media transfer that's why I can't transfer any file to my phone. I tried everything. I've installed motorola device manager but all that I got is motorola adb interface that make my phone can connect to the pc when in bootloader mode.I don't have any OTG cable or mobile sd card reader.
Click to expand...
Click to collapse
The output of the "fastboot devices" command clearly shows your phone is recognised by your PC. As I said all you need to do now is use the correct "fastboot flash" commands to restore recovery and system. Tutorials can be found in this forum.

Thank you.
I would like to say thank you to all peoples who help me solving my lost os problem. Thanks for all the informations. My moto G is working perfectly normal right now.

Can I still install any recovery(CWM or TWRP) after I have forgotten my password?

My question is: Is there any way that i can install any custom recovery now, when I am locked out of my phone, so I can try Method 7 from this post . I have enabled USB debugging, but for some reason, my device is unauthorized from executing adb commands.
I have Xiaomi Redmi Note 3, and have forgotten its password. I have tried Method 2, 5 and 6 from this post, but to no avail.
I tried method 2 and 5 which requires ADB to be installed, but I was not able to access my phone. I have USB debugging enabled and my phone is not rooted. When I tried to run the following code:
Code:
adb devices
adb shell
it showed that my phone is unauthorized and error: device unauthorized This adb server's $ADB_VENDOR_KEYS is not set
Here's the screenshot:
When trying method 6, I had to change the path of ADB driver because the file I downloaded from the post, had its own ADB driver which clashed with my already installed ADB driver, but even after that, it again showed the above error. Here' the screenshot:
Finally I want to try method 7 from the above post, which requires custom recovery to be installed on the phone, is there any way now?
Though it seems now that the I have only one option left and that is to factory reset my phone, but if , there is any other way by which I can bypass my lock screen, please please please inform me.

Of course you can. Just boot your phone into fastboot and do "fastboot flash recovery <recovery image name>.IMG" and you'll flash it. And you can't access the adb because your screen is locked... This is how companies prevent phone hacking
So flash custom recovery, backup the /data , factory reset and after resetting restore the /data backup. And you're good to go. I suggest you using TWRP, because I use it and it never left me hanging Keep me updated.
Sent from Lenovo a6000 1GB version.

Install TWRP or CWM with fastboot and then flash the Unlock me! zip that I've created and you won't lose your data.
Sent by my iPad using Tapatalk

joe2k01 said:
Install TWRP or CWM with fastboot and then flash the Unlock me! zip that I've created and you won't lose your data.
Sent by my iPad using Tapatalk
Click to expand...
Click to collapse
Didn't know that such package existed... I'd still do it my way if your phone was laggy/corrupted,... Else do the package flash. Keep me updated!
Sent from Lenovo a6000 1GB version.

Thanks! a lot, could you please guide me a little bit, how should I proceed?
MGlolenstine said:
Of course you can. Just boot your phone into fastboot and do "fastboot flash recovery <recovery image name>.IMG" and you'll flash it. And you can't access the adb because your screen is locked... This is how companies prevent phone hacking
So flash custom recovery, backup the /data , factory reset and after resetting restore the /data backup. And you're good to go. I suggest you using TWRP, because I use it and it never left me hanging Keep me updated.
Sent from Lenovo a6000 1GB version.
Click to expand...
Click to collapse
Thanks! a lot for reply, As I am still a newbie and trying to learn few things. Could you please guide me how should I proceed?
Like What files I need to download and from where? Also how should I use these files to install recovery?

dost25 said:
Thanks! a lot for reply, As I am still a newbie and trying to learn few things. Could you please guide me how should I proceed?
Like What files I need to download and from where? Also how should I use these files to install recovery?
Click to expand...
Click to collapse
OK... So first boot into fastboot. When you've done that, connect It to your pc with usb, download fastboot package from somewhere on xda(you'll find it).
Open command prompt "CD" to the directory where your fastboot is located in, put recovery image in the folder where fastboot.exe is and type "fastboot flash recovery <recovery file name>.IMG". I'm gonna update this answer in 2 days, when I get to my pc, so try to do it by these instructions, if something isn't working, comment and we'll resolve the problem. If something isn't clear, just ask. Keep me updated.
Sent from Lenovo a6000 1GB version.

Ok i will try
MGlolenstine said:
OK... So first boot into fastboot. When you've done that, connect It to your pc with usb, download fastboot package from somewhere on xda(you'll find it).
Open command prompt "CD" to the directory where your fastboot is located in, put recovery image in the folder where fastboot.exe is and type "fastboot flash recovery <recovery file name>.IMG". I'm gonna update this answer in 2 days, when I get to my pc, so try to do it by these instructions, if something isn't working, comment and we'll resolve the problem. If something isn't clear, just ask. Keep me updated.
Sent from Lenovo a6000 1GB version.
Click to expand...
Click to collapse
Can unlocking my bootloader somehow brick my phone?

Everything can brick your phone. Updating my lenovo phone with official update hardbricked mine... But yeah, it can.

Cannot boot my OnePlus 6! Please help!

Hey guys!
So, my OnePlus 6 won't boot! My problems started when I tried to flash MIUI 10 port. Idk what I did, and appeared to me "your device is corrupted". But ok, i could boot normally.
Then, I tried to downgrade, as there is a tutorial here in XDA, I was in OOS 9.0.4, then rollback to 5.1.1 (i guess) with appropriate file. Installed it, and rebooted it. But it was taking longer than I expected, and I rebooted it into fastboot mode to flash stock image into fastboot (as there is a tutorial here too). And after this, the ROM install, in my computer everything seems to be ok, but as soon as the CMD reboots it, the message "unlocked bootloader" appears, and then, goes black. Only that. Oh, the notification LED also lights up white!
I connected it into my pc, and i can hear the sound that "something is plugged in", but I can do nothing. I can access fastboot mode normally though.
Tried the tutorial in msm download tool, but had some problems... I mean, it doesn't recognize my phone, but if I put in PowerShell, and type "fastboot devices", it recognizes it.
Could you please help me?

aw4y_ said:
Hey guys!
So, my OnePlus 6 won't boot! My problems started when I tried to flash MIUI 10 port. Idk what I did, and appeared to me "your device is corrupted". But ok, i could boot normally.
Then, I tried to downgrade, as there is a tutorial here in XDA, I was in OOS 9.0.4, then rollback to 5.1.1 (i guess) with appropriate file. Installed it, and rebooted it. But it was taking longer than I expected, and I rebooted it into fastboot mode to flash stock image into fastboot (as there is a tutorial here too). And after this, the ROM install, in my computer everything seems to be ok, but as soon as the CMD reboots it, the message "unlocked bootloader" appears, and then, goes black. Only that. Oh, the notification LED also lights up white!
I connected it into my pc, and i can hear the sound that "something is plugged in", but I can do nothing. I can access fastboot mode normally though.
Tried the tutorial in msm download tool, but had some problems... I mean, it doesn't recognize my phone, but if I put in PowerShell, and type "fastboot devices", it recognizes it.
Could you please help me?
Click to expand...
Click to collapse
Did you installed fastboot adb drivers and oneplus drivers?
Or maybe try to wipe everything in fastboot and then install fastboot stock rom...

Follow the guide of msmdownloadtool, it's the best way to recover your phone, it's a pain the part of install the qualcom driver, but persist

only way to recover stock receovery and back to normal is to install msmdownload tool you can see the videos available on you tube
---------- Post added at 12:36 PM ---------- Previous post was at 12:34 PM ----------
https://drive.google.com/open?id=19CzsxB-ew088fPqrn_KSZ9Wkh5mru6Pe
download from my google drive

https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Use this method

siddhrsh said:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Use this method
Click to expand...
Click to collapse
I tried this method before, and find this method to be simpler. If the PC is not recognizing your phone, try powering completely off, then press Volume Up button for at least 5 secs before plugging into the PC and going into the MSM flashing tool. You don't need OnePlus drivers preinstalled for the PC to recognize your phone in this state. From there, just click "Start" on the MSM flashing tool, and wait for your phone to boot back to life. Take note any data inside will be completely wiped clean, like it was flashed from the factory. This YouTube guide here will help you better understand this.

aw4y_ said:
Hey guys!
So, my OnePlus 6 won't boot! My problems started when I tried to flash MIUI 10 port. Idk what I did, and appeared to me "your device is corrupted". But ok, i could boot normally.
Then, I tried to downgrade, as there is a tutorial here in XDA, I was in OOS 9.0.4, then rollback to 5.1.1 (i guess) with appropriate file. Installed it, and rebooted it. But it was taking longer than I expected, and I rebooted it into fastboot mode to flash stock image into fastboot (as there is a tutorial here too). And after this, the ROM install, in my computer everything seems to be ok, but as soon as the CMD reboots it, the message "unlocked bootloader" appears, and then, goes black. Only that. Oh, the notification LED also lights up white!
I connected it into my pc, and i can hear the sound that "something is plugged in", but I can do nothing. I can access fastboot mode normally though.
Tried the tutorial in msm download tool, but had some problems... I mean, it doesn't recognize my phone, but if I put in PowerShell, and type "fastboot devices", it recognizes it.
Could you please help me?
Click to expand...
Click to collapse
If you are able to use fastboot, can you download the latest compatibly TWRP for your device from the official website (twrp.me) get the IMG & ZIP files ( you can use just the image for both, but to keep it simple get both).
Boot into TWRP using the image you just downloaded by running
Code:
fastboot boot <img file name>
Your device should reboot into TWRP.
With your device in TWRPyou should be able to push the file to the phone using ADB push.
Code:
adb push <twrp zip file.zip> /sdcard/
From within TWRP install this zip image. * Now you should have a permanent TWRP recovery, until another OS/recovery flash.
To get the OS on the phone now -
Download the most recent official release for Stable OOS.
Code:
adb push <full os image.zip> /sdcard/
*That should put the file in the root of the SD card folder.
Again use TWRP to install this zip file on to the phone. * This will wipe the TWRP image we had just installed.
To get TWRP again, just flash TWRP after the OS image flash.
I would also suggest, reboot back into TWRP and install the OS & TWRP again as above.
Flashing the OS twice will flash the same version on both Partition A & B. This is essential.
If you find these steps confusing then the simple solution would be to use the MSM downlad tool it does everything for you with a few clicks.

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.