Hi everyone,
I'm having this "locked bootloader" issue as probably hundreds other people do, since January update appeared. In my case the phone became unusable, stuck on MI logo, and also there is no recovery available.
I can only use fastboot.
I understand that some people managed to completely erase the eMMC and reflash the bootloader while the phone is connected to the computer in "Qualcomm HS-USB QDLoader 9008" or "QHS_USB Bulk" mode.
I can't figure out how to boot the phone in either of these modes! When connected through fastboot the MI4C is being recognized as "Marshall London Bootloader Interface". When I just turn it on and it's stuck on MI logo, it isn't recognized by device manager at all.
I'm on Windows 10 64 bit. Anyone has any idea what needs to be done to access these modes on Mi4C?
Many Thanks!
dsafro said:
Hi everyone,
I'm having this "locked bootloader" issue as probably hundreds other people do, since January update appeared. In my case the phone became unusable, stuck on MI logo, and also there is no recovery available.
I can only use fastboot.
I understand that some people managed to completely erase the eMMC and reflash the bootloader while the phone is connected to the computer in "Qualcomm HS-USB QDLoader 9008" or "QHS_USB Bulk" mode.
I can't figure out how to boot the phone in either of these modes! When connected through fastboot the MI4C is being recognized as "Marshall London Bootloader Interface". When I just turn it on and it's stuck on MI logo, it isn't recognized by device manager at all.
I'm on Windows 10 64 bit. Anyone has any idea what needs to be done to access these modes on Mi4C?
Many Thanks!
Click to expand...
Click to collapse
You need a working phone with USB debug enabled, then " adb reboot edl" from cmd... Sorry but if you are in a boot loop there is no knows way to access the Qualcomm mode...
There is no way for you to go into EDL mode. You need to apply for unlock permission from Xiaomi if you want to fix your mi4c yourself.
I applied for permission on Feb 1, and I got it today (Feb 18) despite the Chinese New Year holidays. I haven't even received my mi4c from China yet, and am not even a diamond member at miui.com, either. Good luck!!
dsafro said:
Hi everyone,
I'm having this "locked bootloader" issue as probably hundreds other people do, since January update appeared. In my case the phone became unusable, stuck on MI logo, and also there is no recovery available.
I can only use fastboot.
I understand that some people managed to completely erase the eMMC and reflash the bootloader while the phone is connected to the computer in "Qualcomm HS-USB QDLoader 9008" or "QHS_USB Bulk" mode.
I can't figure out how to boot the phone in either of these modes! When connected through fastboot the MI4C is being recognized as "Marshall London Bootloader Interface". When I just turn it on and it's stuck on MI logo, it isn't recognized by device manager at all.
I'm on Windows 10 64 bit. Anyone has any idea what needs to be done to access these modes on Mi4C?
Many Thanks!
Click to expand...
Click to collapse
Did you try flashing it with Miflash? I got bricked yesterday, so I reflashed system this way, but via Qualcomm HS-USB QDLoader. Also, my phone did not react to anything except bootloader mode (holding buttons for a long long time), no charging, no lights - nothing.
Me too
Me too. :crying:
Hi,
I have the same problem of the bootloader locked. Not let me do anything. It is blocked. I've tried to give instructions by ADB, but will not let me load any file since it claims to be the phone locked.
I have applied the code unlock via SMS to Xiaomi, but they are very slow. Yesterday I wrote and asked you to unlock it. They asked me 2 days more waiting, at least.
This is still horrible, a shame.
I read the post of a colleague who manages to unlock it but has to be the phone working. For those who stayed with my at startup, there is no solution.
Regards.
my oneplus one is hard bricked. i tried several tools to recover my OPO, sadly nothing worked. The problem i've figured out is, that after flasing the 8974_msimage.mbn image my phone disconnects (sound from windows), reconnects again and the msm8974 download tool starts again. so i'm stuck like in this video:
The Qualcomm Flash image loader doesn't give me an error message (i can flash everything - i did so with Color.zip and with OPO Recovery Tools files), but still i get no vibration, no led light or anything else from the phone.
so what can i do for now? that's actually not my first android phone which is hard bricked (i helped a lot of friends of mine and i'm computer scientist as well....), so can anyone, please, help me!!!!
regards
markus
Hello I was running a mi 5s plus with TWRP and everything was fine until I had a terrible idea of flashing the newest recovery rom from xiaomi through TWRP. It seemed to work but after a reboot my phone got stuck in a state where the screen is blank and I get no reactions from anything. When I connect it to PC and flash usin miFlash it says it was successful but the phone stays in that mode when I hold the power button i just hear the sound on my PC of the cable being connected and Dissconected but it still stays the same. In device manager it is called qualcomm hs-usb qdloader 9008. Please Help
Are you flashing the fastboot ROM?
Sent from my Xiaomi MI 5s Plus using XDA Labs
OKProductions said:
Hello I was running a mi 5s plus with TWRP and everything was fine until I had a terrible idea of flashing the newest recovery rom from xiaomi through TWRP. It seemed to work but after a reboot my phone got stuck in a state where the screen is blank and I get no reactions from anything. When I connect it to PC and flash usin miFlash it says it was successful but the phone stays in that mode when I hold the power button i just hear the sound on my PC of the cable being connected and Dissconected but it still stays the same. In device manager it is called qualcomm hs-usb qdloader 9008. Please Help
Click to expand...
Click to collapse
Hello,
I am stuck with the very same issue. After I flashed the Multi Lingual EU Rom everything went pitchblack and no more response to everything I tried. In device manager it says Quectel QD Loader 9008 (COM3), but nor in MI Flash neither in ADB + Fastboot I get any result.
So yes, I could really use all the help I can get. Thankx
I'm facing the same issue, no one found a solution?
4ur0r said:
I'm facing the same issue, no one found a solution?
Click to expand...
Click to collapse
try leave the phone for a week and charge
lp777 said:
try leave the phone for a week and charge
Click to expand...
Click to collapse
thanks for your reaply, i'll try leaving the phone for a while until battery drains out and then charge it.
4ur0r said:
thanks for your reaply, i'll try leaving the phone for a while until battery drains out and then charge it.
Click to expand...
Click to collapse
If someone else is facing this problem, I can confirm that leaving the phone discharging (while off) will make the phone exit EDL mode and then you just need to recharge it and it will work as before.
Hello, my OP6 is stuck in a constant bootloop (can't get past the loading screen with the One plus logo + Powered by android). Battery is still working, can enter Fastboot Mode but Bootloader is locked. Already tried to enter recovery mode and managed to do so, wiped cache and data successfully however when I tried to click on erase everything (pictures...), it says failed.
So, as a last resort, I downloaded MSM Download Tool for OP6 to flash the Original ROM. Installed Qualcomm Drivers succesfully (I already tried several) and put the phone in EDL Mode by holding both volume up and down buttons before plugging the phone to the computer. The phone get recognized succesfully in Device Manager as Qualcomm HS-USB QD Loader 9008 and the LED turns green when I start MSM Download Tool.
However, everytime, MSM Download Tool stops at 12 seconds and displays this :
Status : N/A ;
Status of Communication : FirehoseCheckRSP failed; Errorno : 258 ;
Status of last communication : Erasing Partition Misc failed
NB : please note that I already tried different ports (USB 2.0 and 3.0) and cables (tried with the original one and another one).
Please help me to sort this out (phone was working perfectly fine until then and put itself in a bootloop out of nowhere in the middle of the night). Please note I also have Teamviewer in case anyone amongst you want to perform things directly from the computer.
Thanks in advance to those who will help, Regards.
jon amt said:
Hello, my OP6 is stuck in a constant bootloop (can't get past the loading screen with the One plus logo + Powered by android). Battery is still working, can enter Fastboot Mode but Bootloader is locked. Already tried to enter recovery mode and managed to do so, wiped cache and data successfully however when I tried to click on erase everything (pictures...), it says failed.
So, as a last resort, I downloaded MSM Download Tool for OP6 to flash the Original ROM. Installed Qualcomm Drivers succesfully (I already tried several) and put the phone in EDL Mode by holding both volume up and down buttons before plugging the phone to the computer. The phone get recognized succesfully in Device Manager as Qualcomm HS-USB QD Loader 9008 and the LED turns green when I start MSM Download Tool.
However, everytime, MSM Download Tool stops at 12 seconds and displays this :
Status : N/A ;
Status of Communication : FirehoseCheckRSP failed; Errorno : 258 ;
Status of last communication : Erasing Partition Misc failed
NB : please note that I already tried different ports (USB 2.0 and 3.0) and cables (tried with the original one and another one).
Please help me to sort this out (phone was working perfectly fine until then and put itself in a bootloop out of nowhere in the middle of the night). Please note I also have Teamviewer in case anyone amongst you want to perform things directly from the computer.
Thanks in advance to those who will help, Regards.
Click to expand...
Click to collapse
Please try fastboot command and log in to recovery. once in recovery flash the os you had before of its stock then flash them and reboot system. If its going on bootloop again try flashing manually from bootloader itself. Hope it helps
Hello everyone,
History : So i was using Rice driod on my OP 8T peacefully and i got an update on the rom. i installed the update via local update of the rom and after reboot the phone never booted back. i tried all button combos to make to boot anything like fastboot or recovery etc but nothing worked.
Problem : While connecting to PC the device shows as "Qualcomm HS Diagnostic 900E" I know it should show as 'qualcomm hs loader 900' something which indicates EDL state. So i can't perform MSM. There are not port showing in MSM either. Its blank. Even after forcefully trying to boot EDL ( button combos ), it always boots back to same state.
Fixes i have tried : Reinstalled qualcomm drivers many times, also tried many other versions of MSM including the Hydrogen OS one. No solution.
Can anyone please help me with this situation. Its been few days now and i have really no hope left with the device.
alp47470 said:
Hello everyone,
History : So i was using Rice driod on my OP 8T peacefully and i got an update on the rom. i installed the update via local update of the rom and after reboot the phone never booted back. i tried all button combos to make to boot anything like fastboot or recovery etc but nothing worked.
Problem : While connecting to PC the device shows as "Qualcomm HS Diagnostic 900E" I know it should show as 'qualcomm hs loader 900' something which indicates EDL state. So i can't perform MSM. There are not port showing in MSM either. Its blank. Even after forcefully trying to boot EDL ( button combos ), it always boots back to same state.
Fixes i have tried : Reinstalled qualcomm drivers many times, also tried many other versions of MSM including the Hydrogen OS one. No solution.
Can anyone please help me with this situation. Its been few days now and i have really no hope left with the device.
Click to expand...
Click to collapse
complete noob here but I have heard someone said they fixed using indian msm tool, maybe I am wrong, idk
LR7875 said:
complete noob here but I have heard someone said they fixed using indian msm tool, maybe I am wrong, idk
Click to expand...
Click to collapse
I have tried MSM already no fix as it doesn't detect the device in EDL state. Hence no port shows up
alp47470 said:
I have tried MSM already no fix as it doesn't detect the device in EDL state. Hence no port shows up
Click to expand...
Click to collapse
does the computer even detect your device? what name of the device does it show up
alp47470 said:
I have tried MSM already no fix as it doesn't detect the device in EDL state. Hence no port shows up
Click to expand...
Click to collapse
1st, make sure your device is connected and recognized as 9008 HS-USB QDLoader.
2nd, try using MSM of 9R Ported ROM for 8T, it works in almost every situation
LinhBT said:
1st, make sure your device is connected and recognized as 9008 HS-USB QDLoader.
2nd, try using MSM of 9R Ported ROM for 8T, it works in almost every situation
Click to expand...
Click to collapse
The 1st one is main problem. It doesn't recognise as 9008 HS-USB QDLoader, it always keeps showing to 900E mode.
just a long shot, as i am on a 5t not the 8, but has windoze perhaps updated and "fixed" the usb driver on your behalf?
my 5t was invisible after unlocking, until i forced windoze to update the driver to an unsigned (working) version
[EOL][11.0][OFFICIAL] LineageOS 18.1 for Oneplus 5 & 5T
Is there anybody out there!ðŸ¤
forum.xda-developers.com
alp47470 said:
The 1st one is main problem. It doesn't recognise as 9008 HS-USB QDLoader, it always keeps showing to 900E mode.
Click to expand...
Click to collapse
That's a total different device state, it's on Diag mode, not EDL mode. Try to turn off the device COMPLETELY, then either using hardkeys ( VOL + VOL - press and hold at the same time, plug in cable ) or use Deep-Fash cable to put the device into correct EDL 9008 mode.
So, guys i was finally able to fix the device by EDL point method. Somehow the device was able to boot to edl anyhow. The drivers were correct and so was the cable etc, Thank you all for still helping me.
So relieved so my 8T alive again.
alp47470 said:
So, guys i was finally able to fix the device by EDL point method. Somehow the device was able to boot to edl anyhow. The drivers were correct and so was the cable etc, Thank you all for still helping me.
So relieved so my 8T alive again.
Click to expand...
Click to collapse
Could you please be more specific as to how you got it to connect in EDL mode - it would help others who end up in the same situation.
BillGoss said:
Could you please be more specific as to how you got it to connect in EDL mode - it would help others who end up in the same situation.
Click to expand...
Click to collapse
As you know already the phone wasn't able to go to EDL mode no matter what i did. I really don't know what caused the issue and why it wasn't booting even after using button combos (both vol) or to power off manually (vol up and power) it was went to Diagnostic Mode.
Here's what i did :
-Went to local shop for removing the back panel by those heating machines
-Unplug battery
-Then used the EDL points on the motherboard to force the device to boot EDL (this method is more seen in Mi , Redmi phones)
-The device immediately recognised by just one tap on "enum" now.
Thats how i flashed the OS, plugged the battery and panel, reboot
Thanks for sharing that - much appreciated.
alp47470 said:
As you know already the phone wasn't able to go to EDL mode no matter what i did. I really don't know what caused the issue and why it wasn't booting even after using button combos (both vol) or to power off manually (vol up and power) it was went to Diagnostic Mode.
Here's what i did :
-Went to local shop for removing the back panel by those heating machines
-Unplug battery
-Then used the EDL points on the motherboard to force the device to boot EDL (this method is more seen in Mi , Redmi phones)
-The device immediately recognised by just one tap on "enum" now.
Thats how i flashed the OS, plugged the battery and panel.
Click to expand...
Click to collapse
So the localshop is using Testpoint trick. It has the same effect as using Deep-Flash cable but more trustable, only that u will have to open the back cover.
Congrats on successfully rescue the device mate
LinhBT said:
So the localshop is using Testpoint trick. It has the same effect as using Deep-Flash cable but more trustable, only that u will have to open the back cover.
Congrats on successfully rescue the device mate
Click to expand...
Click to collapse
Thanks bro. Actually the shop kepper didn't do anything. Instead he was saying that the battery was damaged or something (probably scamming me) or he actually didn't had any idea for real. I had read about EDL point thing, so i just asked the shopkeeper to just remove the back panel. Rest i came home and did everything lol. NGL it was scary as hell.
In the process i also discovered that 8T and 9R being mostly identical also have same EDL points on motherboard. Same positioning too.
alp47470 said:
Thanks bro. Actually the shop kepper didn't do anything. Instead he was saying that the battery was damaged or something (probably scamming me) or he actually didn't had any idea for real. I had read about EDL point thing, so i just asked the shopkeeper to just remove the back panel. Rest i came home and did everything lol. NGL it was scary as hell.
In the process i also discovered that 8T and 9R being mostly idenical also have same EDL points on motherboard. Same positioning too.
Click to expand...
Click to collapse
Ah I see, same here when I 1st try the Testpoint trick few years back, scary as hell cuz that was the only phone I had at that time ))))
Btw, yes, 9R and 8T shares almost everything besides of SOC's name ( Snap870 in fact is Snap865 OCing ). That's why I told u to use the MSM Tool of 9R port ROM for 8T, it passes almost every errors u may face when using MSM of 8T itself!
alp47470 said:
As you know already the phone wasn't able to go to EDL mode no matter what i did. I really don't know what caused the issue and why it wasn't booting even after using button combos (both vol) or to power off manually (vol up and power) it was went to Diagnostic Mode.
Here's what i did :
-Went to local shop for removing the back panel by those heating machines
-Unplug battery
-Then used the EDL points on the motherboard to force the device to boot EDL (this method is more seen in Mi , Redmi phones)
-The device immediately recognised by just one tap on "enum" now.
Thats how i flashed the OS, plugged the battery and panel, reboot
Click to expand...
Click to collapse
Hi, I'm the same boat after a bad flash of OSS12, hard brick, black screen, not detected in Windows devices manager, no vibration with every button combination ...
Could you share where the edl points are on the OnePlus 8T motherboard please ?
I would be eternally grateful!
NZX-DeSiGN said:
Hi, I'm the same boat after a bad flash of OSS12, hard brick, black screen, not detected in Windows devices manager, no vibration with every button combination ...
Could you share where the edl points are on the OnePlus 8T motherboard please ?
I would be eternally grateful!
Click to expand...
Click to collapse
Here.. hope it helps