Related
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.
I'm hoping someone can help me out here. I've been trying for hours to restore my OnePlus 8T with the global MSM tool and I keep getting the Sahara communication failed error over and over again. My drivers are successfully installed and I've tried 5 different USB ports and 3 different types of cables and nothing works. I've tried rebooting my PC multiple times, and 2 out of the 3 cables I've used are official OnePlus cables.
Some_Random_Username said:
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
Click to expand...
Click to collapse
I AM STUCK IN EDL. ALL I GET IS SAHARA COMMNICATION FAILED. I NEED HELP
1
Hi, RootK1t...
Thank you soooooooooooo much for this !
This little and powerful trick brings my old OPPO R7 Plus back to life !!!
I have similar problem, but my phone is totally dead. can't enter EDL, Bootloader or Recovery.
is there anything I can do?
andrew_yousry said:
I have similar problem, but my phone is totally dead. can't enter EDL, Bootloader or Recovery.
is there anything I can do?
Click to expand...
Click to collapse
andrew_yousry said:
I have similar problem, but my phone is totally dead. can't enter EDL, Bootloader or Recovery.
is there anything I can do?
Click to expand...
Click to collapse
EDL is a Emergency Download Mode thats cant Destroy by Software!!
Hello there!
My phone was bricked because I was flashing xiaomi.eu ROM in fastboot mode using cmd, and the flashing process was stopped midway.
I am able to enter into EDL mode only and only by using the test points, my phone is recognised as "Qualcomm HS-USB QDLoader 9008" as it should and also appears in MiFlash.
But when I try to flash a ROM (I tried global and Chinese) it gives me this error: "object reference is not set to an instance of the object".
I believe I have all the necessary drivers and my battery is probably long dead since the phone has been bricked for about a month now.
I read a bunch of articles describing similar problems but none of them gave a clear answer.
BlackTrade30 said:
Thank you for the quick reply!
I was guessing I needed an authorized account but MiFlash usually clearly indicated when you did. Something like "Authentication error". At least I have a solution!
Also, the thread you linked; the guy had symptoms that are exactly the same as I have. Unfortunately, he hasn't replied to me yet. According to him, he managed to get the phone unbricked using QFIL but didn't describe how. But thank you for bringing it to my attention!
Click to expand...
Click to collapse
Some old phones can be flashed without authorization but the k30 pro / poco f2 pro cannot.
Hello!
I have exactly the same problem as you (phone bricked after xiaomi.eu fastboot update) but i don't manage to enter in EDL mode even with testpoint... What did you used to do it?
Also, how much did you pay for the auth account perm?
Thanks.
Try flash it by UMT
MaximeMNT said:
Hello!
I have exactly the same problem as you (phone bricked after xiaomi.eu fastboot update) but i don't manage to enter in EDL mode even with testpoint... What did you used to do it?
Also, how much did you pay for the auth account perm?
Thanks.
Click to expand...
Click to collapse
Hello!
I manager to fix the phone!
Entering EDL mode should be possible using the test points.
Make sure your battery is disconnected.
Connect the USB to your phone but not to the PC.
Then short out the two pins.
I used tweezers to short them out.
While shorted plug in the USB the the PC. The PC then should detect the phone as a COM-PORT, you need the drivers if it says bulk device. It has to be USB 9008.
Now you need someone who can flash.
Mod edit: Paid services TG link removed.
EDL are Qcom's special access protocol. You should be able to flash via Qfil or Qpst suite, not Mi tool.
MA7MOD_GSM said:
Try flash it by UMT
Click to expand...
Click to collapse
UMT is free tool ???
NOSS8 said:
Some old phones can be flashed without authorization but the k30 pro / poco f2 pro cannot.
Click to expand...
Click to collapse
Respected sir,
Soft bricked locked bootloader Redmi 4 has same error in edl mode. Initially it was successfully flashed in edl with miflash few days ago to global fastboot rom Santoni_10.3NAMMIXM. It was working properly. Then It was showing latest update available 11.0.2NAMMIXM in setting, I downloaded and rebooted then after sometime It redirected 'mi recovery 3.0' instead of restarting the mobile automatically. Then i choosen to 'reboot to system' by volume buttons. Then it stucked on mi logo. Now i can't enter in "mi recovery 3.0". But by volume buttons i can fastboot, and In edl by shorting test points. Both are detecting device in miflash tool.
Fastboot mode flashing gives me "critical partition error"
EDL mode gives "object reference not set as an object" error in miflash tool this time.
Dear sir any suggestion or resolve for that.please help.
Thank you sir
chandan shah said:
Respected sir,
Soft bricked locked bootloader Redmi 4 has same error in edl mode. Initially it was successfully flashed in edl with miflash few days ago to global fastboot rom Santoni_10.3NAMMIXM. It was working properly. Then It was showing latest update available 11.0.2NAMMIXM in setting, I downloaded and rebooted then after sometime It redirected 'mi recovery 3.0' instead of restarting the mobile automatically. Then i choosen to 'reboot to system' by volume buttons. Then it stucked on mi logo. Now i can't enter in "mi recovery 3.0". But by volume buttons i can fastboot, and In edl by shorting test points. Both are detecting device in miflash tool.
Fastboot mode flashing gives me "critical partition error"
EDL mode gives "object reference not set as an object" error in miflash tool this time.
Dear sir any suggestion or resolve for that.please help.
Thank you sir
Click to expand...
Click to collapse
Hello,
Voila, a perfectly detailed and unequivocal post as we would like to see more often.
Have you tried re-flashing 10.3NAMMIXM?
Send me the Miflash log (starting with Miflash "version") in private messages.
NOSS8 said:
Hello,
Voila, a perfectly detailed and unequivocal post as we would like to see more often.
Have you tried re-flashing 10.3NAMMIXM?
Send me the Miflash log (starting with Miflash "version") in private messages.
Click to expand...
Click to collapse
Yes sir.
I have tried to refresh again in edl mode for SANTONI_10.3NAMMIXM but gives same error all the time.
Most surprising thing is that just 7 days ago i had been successfully flashed 10.3nammixm
But on the same version miflash tool, same computer, same rom file, this time it gives error: "object reference not set as an object"
Mi flash tool : miflash20220218
I sent you log on private conversation please check.
Thank you for quick response sir.
NOSS8 said:
Hello,
Voila, a perfectly detailed and unequivocal post as we would like to see more often.
Have you tried re-flashing 10.3NAMMIXM?
Send me the Miflash log (starting with Miflash "version") in private messages.
Click to expand...
Click to collapse
Thank you sir for your suggestion.
I have revived again my redmi 4 device.
Flashed an older version of rom santoni_global_images_V8.2.12.0.MAMMIEA_20170629.0000.00_6.0_global_751410291c.tgz
With miflash-20220218
Thanks again.
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
So i recently wanted to root my OOS 12 oneplus nord, and i bricked it..
i cant get into fastbootD, Recovery, or anything at all except fastboot, the device is detected as Android bootloader interface in device manager, i have tried using: msm tool, flashing normal rom (error: partition not found and Flashing is not allowed for critical partition)
As a last resort, this worked for me : [OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Azeld said:
As a last resort, this worked for me : [OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Click to expand...
Click to collapse
As I said, msm didn’t work for me
Hafted said:
As I said, msm didn’t work for me
Click to expand...
Click to collapse
may be need to reinstall drivers? should be displayed differently in the device manager than Android bootloader interface.
gorro8 said:
may be need to reinstall drivers?
Click to expand...
Click to collapse
Nope, I can’t get it into edl mode, I did manage once but I got the you need to restart error and I couldn’t get it back there
Hafted said:
Nope, I can’t get it into edl mode, I did manage once but I got the you need to restart error and I couldn’t get it back there
Click to expand...
Click to collapse
what do you do to enter the edl mode?
what cable are you using?
gorro8 said:
what do you do to enter the edl mode?
what cable are you using?
Click to expand...
Click to collapse
Using official one plus cable, I hold bot volume keys for about 40 seconds, then connect the cable and only then I let my hands go off the keys
I found a problem similar to yours. they say it's the wrong driver
[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions
I messed up trying to install TWRP on c.17 OOS12 Now the mobile is bricked. 1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device. 2. I tried the ALL IN ON TOOL, but getting "UNHANDLED...
forum.xda-developers.com
download the correct drivers and replace them in the device manager
gorro8 said:
I found a problem similar to yours. they say it's the wrong driver
[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions
I messed up trying to install TWRP on c.17 OOS12 Now the mobile is bricked. 1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device. 2. I tried the ALL IN ON TOOL, but getting "UNHANDLED...
forum.xda-developers.com
Click to expand...
Click to collapse
Ok, I’ll try that and give you an update, Ty!
worth trying another USB port too, even if they are supposed to be the exact same. Same thing happened with my laptop, tried another (presumably identical) USB port and it works first time, every time
Hafted said:
Using official one plus cable, I hold bot volume keys for about 40 seconds, then connect the cable and only then I let my hands go off the keys
Click to expand...
Click to collapse
1st, u really should find the exact drivers. But also very important to remember booting your PC into Test Mode with Driver Signature Enforcement OFF - BEFORE installing the EDL 9008 Drivers for your device.
Besides, after you press and hold both Vol buttons, u should plug the device in IMMEDIATELY, not waiting for 40 seconds, since each time the device boots into EDL mode, if there's no connection is established in 5 seconds , the device will automatically out of EDL mode.
Hey, so after some time (I got a new phone by now) I managed to fix it, turns out that i had to instantly put in the cable, just like how LinhBT Said
LinhBT said:
waiting for 40 seconds, since each time the device boots into EDL mode, if there's no connection is established in 5 seconds , the device will automatically out of EDL mode.
Click to expand...
Click to collapse
Here is something that might work for unbricking and/or getting in to EDL-mode:
Unable to reinstall Oxygen OS from custom ROM. FAILED (remote: Flashing is not allowed for Critical Partitions ). Need assistance, details below.
Hello, friends. So I am here following this exact tutorial : https://www.thecustomdroid.com/oneplus-nord-oxygenos-restoration-guide/ I currently am stuck there @pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$...
forum.xda-developers.com