Database Info

Stuck in an EDL loop...

After flashing Lineage, the phone got stuck in an EDL loop after the initial reboot. Only sign on life is that it's recognized as a Qualcomm 9008 device in windows.
I did a full backup with EDL tools before getting started. Restoring this backup didn't resolve the issue. Also tried the reset command from edl-master; it executed successfully but the phone didn't wake up.
Anything else I should try?

Got the phone to work again. In case anyone else gets stuck in my position, here's what ultimately worked after lots of trial an error:
Downloaded the official Android 10 update from ZTE.
Extracted the payload using extract_android_ota_payload https://github.com/cyxx/extract_android_ota_payload
For some reason the extract would crap out in Windows; worked fine in Linux.
I then used the edl-master library to individually copy all the files to the device with _a and _b suffixes added. Most of the files go to lun4. There are 2 with the _a version in lun1 and the _b version in lun2. You can use the printgpt command to see which ones go where. After this the phone came back to life.
I was able to regain root by using Magisk to patch the boot image and then writing it back in EDL mode.

jc717 said:
Got the phone to work again. In case anyone else gets stuck in my position, here's what ultimately worked after lots of trial an error:
Downloaded the official Android 10 update from ZTE.
Extracted the payload using extract_android_ota_payload https://github.com/cyxx/extract_android_ota_payload
For some reason the extract would crap out in Windows; worked fine in Linux.
I then used the edl-master library to individually copy all the files to the device with _a and _b suffixes added. Most of the files go to lun4. There are 2 with the _a version in lun1 and the _b version in lun2. You can use the printgpt command to see which ones go where. After this the phone came back to life.
I was able to regain root by using Magisk to patch the boot image and then writing it back in EDL mode.
Click to expand...
Click to collapse
JC,
How were you able to get Magisk to patch the Android 10 boot image? I tried it, flashed the modded Boot IMG in EDL mode, and got the "Your device is corrupt. It cannpt be trusted and will no boot" message. I tried power cycling the phone and it went back to Bootlooping.

karlnorth said:
JC,
How were you able to get Magisk to patch the Android 10 boot image? I tried it, flashed the modded Boot IMG in EDL mode, and got the "Your device is corrupt. It cannpt be trusted and will no boot" message. I tried power cycling the phone and it went back to Bootlooping.
Click to expand...
Click to collapse
Is your bootloader unlocked?

jc717 said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
No. I can't figure out how to get the Bootloader to unlock on Android 10.0. Do you know of any way that I can revert to Android 9.x US build?

karlnorth said:
No. I can't figure out how to get the Bootloader to unlock on Android 10.0. Do you know of any way that I can revert to Android 9.x US build?
Click to expand...
Click to collapse
I've achieved an unlocked bootloader! Now I'm trying to figure out how to revert to a US build of Android 9.0

Could you please possibly elaborate on what you mean by the edl master library? Sorry, I have never had to work with edl type stuff before. I successfully extracted the payload I'm just not sure where to go from there. Thank you.

jc717 said:
Got the phone to work again. In case anyone else gets stuck in my position, here's what ultimately worked after lots of trial an error:
Downloaded the official Android 10 update from ZTE.
Extracted the payload using extract_android_ota_payload https://github.com/cyxx/extract_android_ota_payload
For some reason the extract would crap out in Windows; worked fine in Linux.
I then used the edl-master library to individually copy all the files to the device with _a and _b suffixes added. Most of the files go to lun4. There are 2 with the _a version in lun1 and the _b version in lun2. You can use the printgpt command to see which ones go where. After this the phone came back to life.
I was able to regain root by using Magisk to patch the boot image and then writing it back in EDL mode.
Click to expand...
Click to collapse
how did you flash it back to the devices
and do you have the file for edl now
i am stuck in to edl and alot of trial for flashing the rom get error

jc717 said:
After flashing Lineage, the phone got stuck in an EDL loop after the initial reboot. Only sign on life is that it's recognized as a Qualcomm 9008 device in windows.
I did a full backup with EDL tools before getting started. Restoring this backup didn't resolve the issue. Also tried the reset command from edl-master; it executed successfully but the phone didn't wake up.
Anything else I should try?
Click to expand...
Click to collapse
Hi jc717,
I am same situation you described, i was tried restore from my EDL backup but didn't work. How can fix this, could you explain simple as step by step for beginners, thanks.

F2 Pro completely stuck

Hi,
My phone is actually dying and I don't know how to recover it this time.
I had a perfectly working setup with latest weekly update of Xiaomi eu MIUI , TWRP and magisk, and know even fastboot is not responding.
I usually don't like when people say that, but I think a malware did it, as my apps started not responding in a few minutes, and the reboot finished the job.
Now it won't boot anymore, when it's plug the notification led is red, and fastboot is detected but commands are stuck.
Also, TWRP is neither accessible from "power + vol up" since last miui eu update, nor from fastboot since the "accident"
If someone have any advice on how to unlock fastboot, flash back the rom or any other way to recover my phone, please help
Also, if you want to know the rest of the story, it's here...
I was using my phone as usual, trying to setup a bridge openvpn connection. (like everyone :laugh: )
The issue is that the only app claiming to do that isn't free, and I want to be sure I can make it work before spending any money.
So I tried to patch it and different apks (I know it's bad...), and while transferring an apk from my laptop to my phone, I noticed the transfer was kinda slow for a few seconds (nothing worrying, but unusual)
Then some of my apps didn't want to launch and, back to the app drawer, most of my apps had their package names, with no icons...
It was at this moment Jackson I knew I screwed up...
I then tried rebooting, and the phone stayed a few minutes on the MIUI screen, then shut off.
After a reboot, I noticed the red led, the absence of boot animation, and the bootloop.
Obviously, if I had a fastboot access, it would be easy to boot on TWRP and then flash back my rom properly but I can't...
EDIT: to make this clearer (I know the post above is a little bit messy), I have the following issues:
- No access to TWRP (for flashing)
- Fastboot is accessible but broken enough so flash/boot to twrp is not possible
- I just though of EDL mode, but "fastboot oem edl" doesn't seems to work
- I prefer to avoid opening my phone (to access to the EDL test points)
EDIT2: You can't flash anything in EDL mode without specific autorisations from xiaomi, so this mode becomes way more useless than on my previous Mi A1. I managed to miraculously flash some things by using miflash in fastboot mode. Maybe working on a windows os instead of gnu/linux helped somehow...

Thelm76 said:
Hi,
My phone is actually dying and I don't know how to recover it this time.
I had a perfectly working setup with latest weekly update of Xiaomi eu MIUI , TWRP and magisk, and know even fastboot is not responding.
I usually don't like when people say that, but I think a malware did it, as my apps started not responding in a few minutes, and the reboot finished the job.
Now it won't boot anymore, when it's plug the notification led is red, and fastboot is detected but commands are stuck.
Also, TWRP is neither accessible from "power + vol up" since last miui eu update, nor from fastboot since the "accident"
If someone have any advice on how to unlock fastboot, flash back the rom or any other way to recover my phone, please help
Also, if you want to know the rest of the story, it's here...
I was using my phone as usual, trying to setup a bridge openvpn connection. (like everyone :laugh: )
The issue is that the only app claiming to do that isn't free, and I want to be sure I can make it work before spending any money.
So I tried to patch it and different apks (I know it's bad...), and while transferring an apk from my laptop to my phone, I noticed the transfer was kinda slow for a few seconds (nothing worrying, but unusual)
Then some of my apps didn't want to launch and, back to the app drawer, most of my apps had their package names, with no icons...
It was at this moment Jackson I knew I screwed up...
I then tried rebooting, and the phone stayed a few minutes on the MIUI screen, then shut off.
After a reboot, I noticed the red led, the absence of boot animation, and the bootloop.
Obviously, if I had a fastboot access, it would be easy to boot on TWRP and then flash back my rom properly but I can't...
Click to expand...
Click to collapse
Hi
I had a similar situation
I comfigured an app and during configuration the phone start framing
I rebooted and stucked at miui screen
I tried to reboot in recovery ,nothing
I downloaded latest miui for europe 12.0.3 and mi flash
For me fastboot worked to flash latest firmware from xiaomi
And now is working and my bootloader is locked

Thelm76 said:
Hi,
My phone is actually dying and I don't know how to recover it this time.
[/hide]
Click to expand...
Click to collapse
Xiaomi.eu has TWRP issue...
Go to https://www.androidfilehost.com/?w=files&flid=50678 and find your recovery (lmi) and flash it with fastboot and boot to recovery.
fastboot flash recovery twrp.img
fastboot boot twrp.img
Now download the new ROM 20.10.16, push it to the internet storage and install it dirty... Wipe Cache and reboot....

My problem is almost same, i unlock the bootloader to flash xiaomi.eu rom from global rom, unlocking and flashing custom recovery was done smoothly, when i tried to flash xiaomi.eu rom version 12.0.8 it booted back to recovery, and i format the data partition and booted to system, and same result. I tried global its same result.
Then i tried miflash tool, " antirollback error ".
Now i don't know what to do. Hope my precious poco f2 pro is not bricked, coz i can still manage to boot in custom recovery, and can use miflash tool but error.
Can someone out there help me please. Thanks in advance.

Eldybug said:
My problem is almost same, i unlock the bootloader to flash xiaomi.eu rom from global rom, unlocking and flashing custom recovery was done smoothly, when i tried to flash xiaomi.eu rom version 12.0.8 it booted back to recovery, and i format the data partition and booted to system, and same result. I tried global its same result.
Then i tried miflash tool, " antirollback error ".
Now i don't know what to do. Hope my precious poco f2 pro is not bricked, coz i can still manage to boot in custom recovery, and can use miflash tool but error.
Can someone out there help me please. Thanks in advance.
Click to expand...
Click to collapse
Since you have access to a properly working fastboot and recovery, I believe there is always a way to recover your phone.
I'll be glad to help you but for now, I'm more focused on my issue.
Only thing, while using miflash, be careful to never lock your bootloader since you would have to open your phone to access EDL mode in case of bootloop
(but you can lock it afterwards if you want)

Enricosteph said:
Xiaomi.eu has TWRP issue...
Go to https://www.androidfilehost.com/?w=files&flid=50678 and find your recovery (lmi) and flash it with fastboot and boot to recovery.
fastboot flash recovery twrp.img
fastboot boot twrp.img
Now download the new ROM 20.10.16, push it to the internet storage and install it dirty... Wipe Cache and reboot....
Click to expand...
Click to collapse
Well, the main issue here is that fastboot seems to be broken too...

i found this for you on the LOS rom for poco f2 pro (am not the autor) this is for the "Anti-rollback error" (i hope that can help you):
romabah said:
Gentlemen with EU versions of Poco F2 pro, could you help me out?
Right now i am running 12.0.2.0 QJKEUXM.
To flash Lineage i first need to flash MIUI V12.0.3.0.QJKMIXM via MiFlash. I tried to do that but got an Anti-rollback error.
Checking via fastboot i saw that my phones anti rollback value is 1, but MIUI V12.0.3.0.QJKMIXM firmware has an anti rollback of 0.
Some folks say to delete first 5-6 lines in text editor from .bat file, but at the same time people tell everywhere to NOT flash firmware with lower value that your current anti rollback.
Any advice? How did other EU folks fix this?
Edit: I fixed it! I will NOT and cannot claim that this will fix all rollback error's, but it fixed mine.
0) This is applicable to fastboot version of MIUI V12.0.3.0.QJKMIXM (aka tgz file that you need to extract twice)
1) Move the extracted firmware directory imi_global_images_V12.0.3.......ets.ets. ( map with flash_all.bat, images ) to C: directory and rename to something short, like xiaomiFirm.
This will solve a lot of weird error's as MiFlash doesnt like long directories
2) Within the moved map open flash_all.bat with text editor and delete everything starting and including "::check anti_version" to and including "echo %..."
This removes the anti rollback check somehow. The reason for only editing flash_all.bat is because this is the .bat file that is run when you choose clean all option in MiFlash, i assume you dont want to clean all and lock now do you?
3) After finishing flashing mine gave error Not catch checkpoint flash is not done, but booted normally. Gave me a heart attack.
Sanity check: When running cmd "fastboot getvar anti" it returned "anti: 1"
Meaning i just flashed a ROM with anti of 0 on a phone with a anti value of 1. At least i believe so.
In any case, thank all for giving feedback for other ways of fixing this.
Click to expand...
Click to collapse

I'll try to make a type C deep flash cable to flash fastboot, and edit this message to explain if this works

Thelm76 said:
Well, the main issue here is that fastboot seems to be broken too...
Click to expand...
Click to collapse
Try to hold down only Vol Down and connect it to your computer

Enricosteph said:
Try to hold down only Vol Down and connect it to your computer
Click to expand...
Click to collapse
I don't know if this was my cable or fastboot oem edl, but windows recognised the phone as qualcomm qdloader 9008. I'll now try to update fastboot, install twrp and check the extent of the damages.

Fangstergangsta said:
i found this for you on the LOS rom for poco f2 pro (am not the autor) this is for the "Anti-rollback error" (i hope that can help you):
Click to expand...
Click to collapse
Indeed, OP, try to flash everything from the start thep by step.

You must stop therapeutic relentlessness!!!
Just plug out the charger and let him die softly...
Put him back in his sweet box after his last breathe
Bury him in your garden with a decent burial : he deserve it!!!!
It's HIS TIME, dude....
Regards

Mastakony said:
You must stop therapeutic relentlessness!!!
Just plug out the charger and let him die softly...
Put him back in his sweet box after his last breathe
Bury him in your garden with a decent burial : he deserve it!!!!
It's HIS TIME, dude....
Regards
Click to expand...
Click to collapse
Haha it's not therapeutic relentlessness when you're sure it will live again in a few days (and fully working!)
It just need a good memory wipe and android replacement
As I managed to get to emergency mode, I can now easily replace its software
EDIT: I didn't know that for these xiaomi devices, you need very specific autorisations to flash something with EDL... Fortunately, after messing around with miflash, I managed to unlock myself out of this infinite loop

As I managed to get to emergency mode, I can now easily replace its software
Click to expand...
Click to collapse
How are you going to flash the software?

Well,
By using edl mode and miflash, I got some errors as I was not authorised to do this operation, so I rebooted to fastboot, reused miflash, and I don't know which kind of magic did that but after some files flashed and an error, I was able to boot on TWRP. With this done, I tried to keep my data but didn't worked, and as I have everything constantly backup, I dicided to do a flashall.
now, I think I have a good MIUI base to flash MIUI EU back

Thelm76 said:
Well,
By using edl mode and miflash, I got some errors as I was not authorised to do this operation, so I rebooted to fastboot, reused miflash, and I don't know which kind of magic did that but after some files flashed and an error, I was able to boot on TWRP. With this done, I tried to keep my data but didn't worked, and as I have everything constantly backup, I dicided to do a flashall.
now, I think I have a good MIUI base to flash MIUI EU back
Click to expand...
Click to collapse
I have the same situation plus no fastboot or recovery at all.. Please tell me how did you resolve it?

ghannaiem said:
I have the same situation plus no fastboot or recovery at all.. Please tell me how did you resolve it?
Click to expand...
Click to collapse
Is the phone detected by the pc in usb?
And when you press power+ sound + or - What is happening?

NOSS8 said:
Is the phone detected by the pc in usb?
And when you press power+ sound + or - What is happening?
Click to expand...
Click to collapse
Yes , detected by usb but as qcom 9008,
And when holding down power button with + or - vol it restarts again to 9008 .
So it is not detected by any means, but only detected in edl mode

ghannaiem said:
Yes , detected by usb but as qcom 9008,
And when holding down power button with + or - vol it restarts again to 9008 .
So it is not detected by any means, but only detected in edl mode
Click to expand...
Click to collapse
how did it happen?

My imei got lost so I tried to flash eng rom through MI flash to fix it. It flashes all except certain file called (aop. Mbn) so I tried to flash it by cmd commands via fastboot and then the phone bricked.. No booting to fastboot anymore , no recovery. even with disconnecting battery and reconnecting again... Phone only recognized in Edl mode and when flashing through MI flash it asks for edl authorization... Account login successful but then flash fail cuz account is not authorized. So I think The only solution will be authorized account or patched prog_ufs file

TWRP error: Unable to open /system_root/system/apex

In last working condition, my phone is the TMO branded device, converted to global 10.5.11 with Magisk and TWRP.
I decided to update to 10.5.12 via Local Upgrade, as I've done previously to update. The OOS update went fine but I encountered an issue when updating Magisk to 21.4. After attempting to install to inactive slot and reboot, my phone went into QualComm CrashDump mode. Attempting to boot into TWRP or the system resulted in being thrown back into CrashDump mode. I could still get to fastboot, so I booted TWRP from fastboot and was able to at least recover my device into a working state; albeit not how it should be working. I am currently on TMO ROM fresh from msm restore, 10.5.7.IN55CB, bootloader unlocked. Phone works, signal good, IMEI good, can receive texts, etc.
From that point on, no matter if I msm back to T-Mobile firmware, flash the Global fastboot ROM, factory reset, etc I'm getting an error I can't seem to find any hits on while searching.
"Unable to mount storage
E: Unable to open /system_root/system/apex
E: Unable to load apex images from system/apex"
I'm assuming I messed up my slot_b because prior to using the msm tool, if I tried to boot from slot_b it would send me to CrashDump mode while attempting to boot from slot_a directly after attempting slot_b would send me into stock recovery mode where I could do a factory reset and successfully boot into the system. After attempting a factory reset (and format data) via TWRP I then was being sent to CrashDump mode by trying to boot from either slot or trying to enter recovery mode. When first attempting to msm, holding vol+ and plugging device in would send phone to EDL mode where it would stay for a few seconds, then reboot into CrashDump Mode. I didn't think I was getting into EDL mode, but once it showed connected in the msm tool I quickly hit start and the restore process started.
While typing this, I tried to update magisk by installing to the inactive slot (which would be slot_b) and upon reboot I went straight to fastboot. I got the message included in the 2nd image attached.

Hi there. MSM back to stick. Funny ways your time logging in to Google it anything. Murray let the phone after up. Take the OTA to current firmware 10.5.23 I think. Then bootloader unlock and flash global. Happy modding!

Nathan.7118391 said:
Hi there. MSM back to stick. Funny ways your time logging in to Google it anything. Murray let the phone after up. Take the OTA to current firmware 10.5.23 I think. Then bootloader unlock and flash global. Happy modding!
Click to expand...
Click to collapse
So taking the OTA on T-Mobile firmware is the part I'm missing? Because I've went back to stock with MSM, and I've took the OTA on global firmware (just not to 11.x) and problem persists

lordcheeto03 said:
So taking the OTA on T-Mobile firmware is the part I'm missing? Because I've went back to stock with MSM, and I've took the OTA on global firmware (just not to 11.x) and problem persists
Click to expand...
Click to collapse
Yup, I always take the TMO OTA then bootloader unlock and global flash. If not then try another global file. Happy modding!

Nathan.7118391 said:
Yup, I always take the TMO OTA then bootloader unlock and global flash. If not then try another global file. Happy modding!
Click to expand...
Click to collapse
So I reverted back to TMO stock with msm tool, updated TMO firmware, unlocked BL, booted to fastbootd and ran the flashall.bat in 10.5.7 Global firmware... it all was going fine until it needed to reboot... it went to Qualcomm CrashDump mode... Slot B is buggered. I hold both vol buttons + power until it turns off, then do it again to enter bootloader mode. fastboot boot twrp.img and it takes me to twrp where I can toggle the boot slot back to a (I can't do fastboot set_active b from fastboot, it just throws up the fastboot help) and I can boot back into recovery.
The msm tool and global fastboot ROM I flashed is the same one I initially performed the conversion with when I first got the device. Even when on slot_a I am still getting the errors in the first picture I attached in OP; slot_b still gives me the errors posted in the 2nd picture.
edit:
I reverted with msm one more time, followed through the process to convert to global (minus taking the OTA first) and now it's flashing the global firmware. It successfully rebooted as it's supposed to do and it continued the install. On system.img, vendor.img, and product.img so far it has said "invalid sparse file format at header magic" then "resizing system_a" etc for all the partitions mentioned... but no, slot_b is still dead.
I see that the script flashes, say vendor.img but it says vendor_a... Can I manually do it through fastboot (or edit the flash all.bat) to flash to slot_b instead of a?

lordcheeto03 said:
So I reverted back to TMO stock with msm tool, updated TMO firmware, unlocked BL, booted to fastbootd and ran the flashall.bat in 10.5.7 Global firmware... it all was going fine until it needed to reboot... it went to Qualcomm CrashDump mode... Slot B is buggered. I hold both vol buttons + power until it turns off, then do it again to enter bootloader mode. fastboot boot twrp.img and it takes me to twrp where I can toggle the boot slot back to a (I can't do fastboot set_active b from fastboot, it just throws up the fastboot help) and I can boot back into recovery.
The msm tool and global fastboot ROM I flashed is the same one I initially performed the conversion with when I first got the device. Even when on slot_a I am still getting the errors in the first picture I attached in OP; slot_b still gives me the errors posted in the 2nd picture.
edit:
I reverted with msm one more time, followed through the process to convert to global (minus taking the OTA first) and now it's flashing the global firmware. It successfully rebooted as it's supposed to do and it continued the install. On system.img, vendor.img, and product.img so far it has said "invalid sparse file format at header magic" then "resizing system_a" etc for all the partitions mentioned... but no, slot_b is still dead.
I see that the script flashes, say vendor.img but it says vendor_a... Can I manually do it through fastboot (or edit the flash all.bat) to flash to slot_b instead of a?
Click to expand...
Click to collapse
OP said sparse magic invalid is fine and won't hurt anything. If you are having trouble booting the phone then I suggest you wipe data. That's what's I had to do in order for it to work. Though the first few times I did it I didn't wipe any data and it worked just fine. I think OP said you can modify the script if you know what you're doing. Happy modding!

Nathan.7118391 said:
If you are having trouble booting the phone then I suggest you wipe data.
Click to expand...
Click to collapse
When you say wipe data, do you mean how, like, when you use msm tool data gets wiped? Or maybe you mean how data gets wiped when you unlock bootloader? Perhaps you mean like the flashall.bat wipes data as well...
I'm almost certain it's slot_b, I just need to know how to repair slot_b

Did you ever figure this out? I have a list of problems that all started with the exact problem your having now here

i'm getting same error again and again, can you help me to troubleshoot this. ASAP

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.

Question Soft bricked device I don't know what to do.

Hello,
My oneplus 9 boots into fastboot, I can use fastboot on my pc but when I try to flash twrp (fastboot boot twrp.img) it tells me FAILED (command write failed (Unknown error)) I don't know what to do

Fastboot flash recovery is correct process to flash twrp
Simple go to oneplus recovery wipe cache your good to go all user apps removed and data will retains

you can run the MSM Tool also. Or, try and boot into Lineage recovery or TWRP, if fastboot flash recovery doesnt work, just do fastboot boot recovery.img

Venkata Prathap said:
Fastboot flash recovery is correct process to flash twrp
Simple go to oneplus recovery wipe cache your good to go all user apps removed and data will retains
Click to expand...
Click to collapse
It gave the same error
illusiveairforce said:
you can run the MSM Tool also. Or, try and boot into Lineage recovery or TWRP, if fastboot flash recovery doesnt work, just do fastboot boot recovery.img
Click to expand...
Click to collapse
I wanted to install it, but it is hosted on google drive and when downloading it blocked me saying it has viruses. Please send me a mirror.
Also I can't access my phone using fastboot anymore, fastboot devices gives nothing, it however shows up in device manager.

I just put a link on a different thread one sec

ONEPLUS 9 china unbrick
ONEPLUS 9 china unbrick what i must to do to bypass model id and flash device
forum.xda-developers.com
Password: cn1d

illusiveairforce said:
ONEPLUS 9 china unbrick
ONEPLUS 9 china unbrick what i must to do to bypass model id and flash device
forum.xda-developers.com
Password: cn1d
Click to expand...
Click to collapse
Isn't that only for the China version? Mine is eu

fastboot works again, it was a driver issue. doing
fastboot boot twrp.img : FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot flash recovery twrp.img : FAILED (remote: '(recovery_a) No such partition')

illusiveairforce said:
ONEPLUS 9 china unbrick
ONEPLUS 9 china unbrick what i must to do to bypass model id and flash device
forum.xda-developers.com
Password: cn1d
Click to expand...
Click to collapse
Using this, after 6s it said an error talking about O2 (don't remember exactly) and now it says sahara communicatino failed.

It says "Unsupported target O2".

If your partition system is dead (slot A not found when booting on recovery), only MSM tool can help you at this stage. But for OP9 this is a pain in ass to use it; I never used it before but there is multiple topic for using the right version, and as I read it can pass by MSM for pro version first before returning to non pro

I let my phone charge this night as it had no battery, and now It just does nothing, doesn't get into fastboot, when plugged to pc it says USB device not recognized, and pressing volume up + volume down doesn't get the phone into EDL.

akboy7015 said:
If your partition system is dead (slot A not found when booting on recovery), only MSM tool can help you at this stage. But for OP9 this is a pain in ass to use it; I never used it before but there is multiple topic for using the right version, and as I read it can pass by MSM for pro version first before returning to non pro
Click to expand...
Click to collapse
Okay got myself back into EDL. Using the oneplus 9 pro MSM tool from there https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-eu-glo-in.4272549/
It said "Device not match image"

After trying 5 differennt MSM Tool one of them worked and my phone is back to stock. Thank you all !

magalie78 said:
After trying 5 differennt MSM Tool one of them worked and my phone is back to stock. Thank you all !
Click to expand...
Click to collapse
Witch one ? It could be useful for someone else