Related
hey guys i have a hardbricked mi5 no fast boot or charging if i connect to the computer it says unknown usb device.how to fix my device any ideas.
Try to find and install drivers for qualcomm hs-usb qdloader 9008.
if you hardbrick your pc prob detect your phone as Qualcomm hs-usb qloader 9008 . Just install any MIUI rom use MiFlashTool . you can find tutorial in MIUI forum . Because i got hardbrick last week . and my phone work again after install MIUI rom .
How to solve it
gowtham300 said:
hey guys i have a hardbricked mi5 no fast boot or charging if i connect to the computer it says unknown usb device.how to fix my device any ideas.
Click to expand...
Click to collapse
I know it's been a long while since you had this problem, but as I have to face it myself without any clue how to solve it I thought it was a good idea to recover this thread.
First of all, let me say it happened to me with a Xiaomi mi5s. I had already installed adb & fastboot, as well as Xiaomi drivers from the Xiaomi Unlock Tool.
The problem arose when I made a partial firmware upgrade through fastboot in order to install LOS 14.1 via TWRP. I could not geet into fastboot mode, the screen went completely black and no charging LED. Curiously my laptop (Win10) made a tiny nose everytime I pluged or unplugged it (the same one it does everytime you plug a new device) and saw that it recognised it as a 'Qualcomm HS-USB qloader 9008'. More curiously, Xiaomi Flash Tool (BTW, it was the beta version although I guess the latest version would have worked as well) recognised the device although everytime I tried to flash an official firmware I got a message error: 'cannot receive hello packet'.
Well, after some research I was scared because I didn't want to open the phone to unplug the battery or anything. But I read somewhere that someone had the same problem as me and that he tried Xiaomi Flash Tool until it worked.
That was it, that was the clue. Xiaomi Flash Tool ready, having initially recognised my mi5s, the phone connected to the laptop, I made the combination to get into fastboot (holding volume - & power button) until my laptop made a tiny nose (the same one I explained at the beginning). As soon as I heard it I left the phone and clicked on the flash button on Xiaomi Flash Tool. Yes, it worked out. I installed latest development chinese MIUI rom. From there, I got into fastboot, flashed a new recovery... Well that's another history, the fact is that the mi5s is working again and I must say I feel really relived.
If anyone encounters the same problem I had I hope this post is of any help to him/her.
21prods said:
I know it's been a long while since you had this problem, but as I have to face it myself without any clue how to solve it I thought it was a good idea to recover this thread.
First of all, let me say it happened to me with a Xiaomi mi5s. I had already installed adb & fastboot, as well as Xiaomi drivers from the Xiaomi Unlock Tool.
The problem arose when I made a partial firmware upgrade through fastboot in order to install LOS 14.1 via TWRP. I could not geet into fastboot mode, the screen went completely black and no charging LED. Curiously my laptop (Win10) made a tiny nose everytime I pluged or unplugged it (the same one it does everytime you plug a new device) and saw that it recognised it as a 'Qualcomm HS-USB qloader 9008'. More curiously, Xiaomi Flash Tool (BTW, it was the beta version although I guess the latest version would have worked as well) recognised the device although everytime I tried to flash an official firmware I got a message error: 'cannot receive hello packet'.
Well, after some research I was scared because I didn't want to open the phone to unplug the battery or anything. But I read somewhere that someone had the same problem as me and that he tried Xiaomi Flash Tool until it worked.
That was it, that was the clue. Xiaomi Flash Tool ready, having initially recognised my mi5s, the phone connected to the laptop, I made the combination to get into fastboot (holding volume - & power button) until my laptop made a tiny nose (the same one I explained at the beginning). As soon as I heard it I left the phone and clicked on the flash button on Xiaomi Flash Tool. Yes, it worked out. I installed latest development chinese MIUI rom. From there, I got into fastboot, flashed a new recovery... Well that's another history, the fact is that the mi5s is working again and I must say I feel really relived.
If anyone encounters the same problem I had I hope this post is of any help to him/her.
Click to expand...
Click to collapse
fixed long time ago , but i appreciate your help and you taking time to do this for me
You are welcome. I was afraid I wouldn't be of much help to you but I thought that it was a good idea anyway to leave my experience just in case at some point it proves helpful to someone.
Hi,
I have a following problem with my Redmi 4X. I tried to flash new rom and reboot my phone on twrp. When the phone shut down nothing happens anymore just black screen. No fastboot or recovery mode. When I contact the phone to Windows pc it shows in device manager: Qualcomm HS-USB Diagnostics 900E (COM20). I have tried to flash new rom with QFIL and Miflash (tried to change the driver to Qualcomm HS-USB QDLoader 9008).
With QFIL the error is: Download Fail: Switch to EDL FailFailed to switch to Emergency Download mode.
With Miflash the error is: Cannot receive hello packet. MiFlash is trying to reset status!
Any suggestions?
https://www.youtube.com/watch?v=uxrhJkSZc6E
Already tried that. Doesn't seem to change a thing.
Shouldn't it turn the driver to "Qualcomm HS-USB QDLoader 9008" after test point method?
This is what shows in command prompt:
C:\Windows\system32>adb reboot edl
error: device '(null)' not found
C:\Windows\system32>adb devices
List of devices attached
C:\Windows\system32>
k4rpp4 said:
Shouldn't it turn the driver to "Qualcomm HS-USB QDLoader 9008" after test point method?
This is what shows in command prompt:
C:\Windows\system32>adb reboot edl
error: device '(null)' not found
C:\Windows\system32>adb devices
List of devices attached
Click to expand...
Click to collapse
After the test point method you will see a new "9008" device in the Device Manager.
Then all of the above commands will be completely irrelevant and useless.
In the 9008 mode use MiFlash, not QFIL/QPST, to reflash your phone.
Cheers!
The test points seems to change nothing. I think that after the " adb devices" command I should see my device listed but that is not the case and therefore impossible to flash rom. Somehow I should be able to change the "900E mode" to "9008 mode" without changing the driver manually and I think the test point method should do just that.
Here is video of what I have tried to do. If someone could point out what to do differently to get the flash work I would be very grateful.
https://drive.google.com/open?id=1aOkb3FCBzanMUW3WSdyuxyQO-33rdsBv
Windows 10 will not accept the 9008 driver because the driversignature ist not signed from Microsoft.
If you will unbrick it with Windows 10 64bit look here: https://www.youtube.com/watch?v=2d8KEruHWPg
and here: https://www.maketecheasier.com/install-unsigned-drivers-windows10/
Had allready done that also. Gave it another try without success
k4rpp4 said:
Had allready done that also. Gave it another try without success
Click to expand...
Click to collapse
Is the Qualcomm 9008 driver now installed?
Did you start the mi-flash tool with administrator privileges?
I installed the Qualcomm drivers but device manager still shows 900E driver unless I manually change it to 9008.
edit:
I finally succeeded with test point method. Now flashing. Im so grateful to you ConradB.
k4rpp4 said:
I installed the Qualcomm drivers but device manager still shows 900E driver unless I manually change it to 9008.
edit:
I finally succeeded with test point method. Now flashing. Im so grateful to you ConradB.
Click to expand...
Click to collapse
Perfect :good:
Bro please help my device in bricked
k23m said:
After the test point method you will see a new "9008" device in the Device Manager.
Then all of the above commands will be completely irrelevant and useless.
In the 9008 mode use MiFlash, not QFIL/QPST, to reflash your phone.
Cheers!
Click to expand...
Click to collapse
Thank you buddy .. Your 4 years old post help me to turn on my hard brick redmi 4x.
I don't know the actual reason of hard brick but The situation was my phone was in condition like
1. Possible to go in fastboot mode
2. When turning on there is only mi logo for fraction of second.
I tried test point method as described . It turned on in one attempt..I just want to add something. I face some issues after test point flashing . So I just flash miui again . Then It's working perfectly fine. After Test point flash check your battery. Maybe fully drained. Just charge it and turn it on..
I am posting this just for Information..
sayan990 said:
Thank you buddy .. Your 4 years old post help me to turn on my hard brick redmi 4x.
I don't know the actual reason of hard brick but The situation was my phone was in condition like
1. Possible to go in fastboot mode
2. When turning on there is only mi logo for fraction of second.
I tried test point method as described . It turned on in one attempt..I just want to add something. I face some issues after test point flashing . So I just flash miui again . Then It's working perfectly fine. After Test point flash check your battery. Maybe fully drained. Just charge it and turn it on..
I am posting this just for Information..
Click to expand...
Click to collapse
I do had same issue with my mobile but even when I tried to flash MIUI I got "ACK count don't match" attached img
Hello everyone,
I recently stopped using my Nokia 8 in favor of my new iPhone 11. However, I wanted to keep it just so I have an emergency Android phone. I found an article that says that there is a possible way to update Nokia 8 via TWRP. Of course, I didn’t trust it, so I backed up my phone via TWRP. Here are the steps I took after back up:
- I deleted everything from the device including the OS, excluding SD
- I tried installing the image but it failed
- I then restored my backup
However, phone won’t boot even after I restored my backup. I followed these instructions (forum.xda-developers.com/nokia-8/how-to/guide-restore-nokia-to-stock-t3867646/) to flash the stock firmware, but the OST LA program keeps giving me 0xc3b9 something like tool func not ready. Can anyone help me? Thanks in advance!
- I have my bootloader unlocked, if anyone’s wondering.
EDIT: I have followed the steps with more care, and I managed to advance to the flashing process, but it gets a new error; 0xc6DA
EDIT 2: I realized I don't have critical unlocked. I can't access my unlock.key since download link expired long ago. Is there any way I can unlock the critical at this moment?
Does your computer recognize your device in 9008 mode?
dongvatm said:
Does your computer recognize your device in 9008 mode?
Click to expand...
Click to collapse
How do I enter 9008 mode?
dongvatm said:
Does your computer recognize your device in 9008 mode?
Click to expand...
Click to collapse
UPDATE: It's recognized as HS-USB Diagnostics 9008
You must use OST LA 6.2.8 and firmware NB1-488 android 8.1. then update via emegency download. It works on EDL mode.
dongvatm said:
You must use OST LA 6.2.8 and firmware NB1-488 android 8.1. then update via emegency download. It works on EDL mode.
Click to expand...
Click to collapse
Do you have a link for OST LA 6.2.8 and its patch?
Link: https://fih-firmware.hikaricalyx.com/hmd_en.html
You can download ost LA and firmware at this link.
dongvatm said:
Link: https://fih-firmware.hikaricalyx.com/hmd_en.html
You can download ost LA and firmware at this link.
Click to expand...
Click to collapse
I get another error message that image upload with Sahara protocol failed - even though I have Qualcomm drivers
RaleBurazer said:
I get another error message that image upload with Sahara protocol failed - even though I have Qualcomm drivers
Click to expand...
Click to collapse
Don't you have installed qualcom usb drive: Qualcom Qloader usb 9008?
dongvatm said:
Don't you have installed qualcom usb drive: Qualcom Qloader usb 9008?
Click to expand...
Click to collapse
Yes, I do have that driver, and my phone is shown as 9008 device in device manager while I’m in EDL, however I get an error which said that image upload using Sahara protocol failed. Is there any fix for that?
QDloader 9008 not HS USB diagnostic 9008
dongvatm said:
QDloader 9008 not HS USB diagnostic 9008
Click to expand...
Click to collapse
Oh yeah, it's shown as HS USB diagnostic 9008. How do I change it to QDLoader 9008?
RaleBurazer said:
Oh yeah, it's shown as HS USB diagnostic 9008. How do I change it to QDLoader 9008?
Click to expand...
Click to collapse
You must download Qualcomm Usb driver. Use google to find it. Good luck
RaleBurazer said:
Oh yeah, it's shown as HS USB diagnostic 9008. How do I change it to QDLoader 9008?
Click to expand...
Click to collapse
Does it work?
dongvatm said:
Don't you have installed qualcom usb drive: Qualcom Qloader usb 9008?
Click to expand...
Click to collapse
dongvatm said:
Does it work?
Click to expand...
Click to collapse
I managed to get Qualcomm QDLoader 9008, but I still get the “Image upload with Sahara protocol failed” error
RaleBurazer said:
I managed to get Qualcomm QDLoader 9008, but I still get the “Image upload with Sahara protocol failed” error
Click to expand...
Click to collapse
It's a good new if your computer recognize 9008 mode. Your phone's main is alive. Sahara failed because your phone is in EDL mode too long time. I don't know exactly how to fix it. The last hint: let take out your battery and insert again. Or Press and hold vol - + power 15-20s. Good luck
dongvatm said:
It's a good new if your computer recognize 9008 mode. Your phone's main is alive. Sahara failed because your phone is in EDL mode too long time. I don't know exactly how to fix it. The last hint: let take out your battery and insert again. Or Press and hold vol - + power 15-20s. Good luck
Click to expand...
Click to collapse
Now I managed to get rid of Sahara upload error, but I again got 0xc6DA error
Have you tried the instructions here: https://forum.xda-developers.com/nokia-8/how-to/how-downgraded-pie-to-oreo-t3888178
Optimus_Toaster said:
Have you tried the instructions here: https://forum.xda-developers.com/nokia-8/how-to/how-downgraded-pie-to-oreo-t3888178
Click to expand...
Click to collapse
Update on the whole situation:
I managed to get to the download mode, and flash OREO NOVEMBER boot image on it. It successfully booted into Pie that I previously had installed. When I tried to follow the instructions given in the quoted post, I install November OTA successfully, but when I try to install December update, it says that I should use the 488K package. After I do that, it aborts the installation because there is no driver directory found. I think “Okay, November is fine” but when I try to reboot it goes into EDL. I again managed to flash the OREO boot image, and boot again into PIE (how is this possible?)
Also sidenote: WiFi doesn’t work. It didn’t work even after the first time I flashed Oreo boot. Can anyone perhaps provide me with a stock Pie boot image? Or does anyone know any other solution?
Back to stock - the aftermath
Hi all,
https://forum.xda-developers.com/showthread.php?t=4081895
(please read first and last post)
In short: I found some sketchy Android 10 update for Nokia 8, tried it out, did not work. Tried to restore my TWRP backup, did not work. Tried to bring back stock firmware via OST LA, did not work. I then flashed stock Oreo November 2018 boot image, and got into my Pie, but WiFi wasn't working. I then flashed pre-Magisk-rooted pre-TWRP-installed boot image, and WiFi works. However...
When my phone boots, it boots with Android logo instead of Nokia's
My phone is detected as Dual SIM, even tho it is not.
When I try to flash OTAs via TWRP, it doesn't work
I am looking for a solution on how to remove the Dual SIM problem and how to make my phone again boot with a classic Nokia logo. Any help? Thanks in advance!
Hi there, thanks for standing by.
Fast forward. Once installed the image with platform tools and rebooted the device I get the message Qualcomm CrashDump Mode.
Now in Qualcomm Crashdump Mode, it has been listed as " QUSB_BULK_SN: E8AC606F " in the driver manager.
After that, I installed QDLoader HS-USB Driver_64bit and restarted my desktop.
Now in the " device manager " COM and LPT is listed as Qualcomm HS-USB QDLoader 9008 (COM10) the phone is switched off, caption.
Last but not least what I wanted is to unbrick my phone to EU_OxygenOS_10.5.11 through MSM Download Toolv4.0, so I'm doing that and the device is now shut down and can be recognized in the device manager as I mentioned.
Opened MSM, chose Other, and now I'm able to see COM10 on index 1 Connected, selected EU, Sha 256 check, Auto reboot check, and Started. On the first attempt, I get a "Firehose Communication Handshake failed". Was confused and I thought I'm going to unbrick it with no problem, I got mad at this point, and I opened MSM again, after starting it I get "Open Serial Device" and a few moments after that Sahara Communication failed - Waiting for device. After disconnecting the cable and reconnecting it, the device is not shown in MSM nor in COM and LPT ports.
What is missing I'm not sure since I've tried a lot of that.
Any expert tech assistance would be great and appreciate it.
lukegonewild said:
Hi there, thanks for standing by.
Fast forward. Once installed the image with platform tools and rebooted the device I get the message Qualcomm CrashDump Mode.
Now in Qualcomm Crashdump Mode, it has been listed as " QUSB_BULK_SN: E8AC606F " in the driver manager.
After that, I installed QDLoader HS-USB Driver_64bit and restarted my desktop.
Now in the " device manager " COM and LPT is listed as Qualcomm HS-USB QDLoader 9008 (COM10) the phone is switched off, caption.
Last but not least what I wanted is to unbrick my phone to EU_OxygenOS_10.5.11 through MSM Download Toolv4.0, so I'm doing that and the device is now shut down and can be recognized in the device manager as I mentioned.
Opened MSM, chose Other, and now I'm able to see COM10 on index 1 Connected, selected EU, Sha 256 check, Auto reboot check, and Started. On the first attempt, I get a "Firehose Communication Handshake failed". Was confused and I thought I'm going to unbrick it with no problem, I got mad at this point, and I opened MSM again, after starting it I get "Open Serial Device" and a few moments after that Sahara Communication failed - Waiting for device. After disconnecting the cable and reconnecting it, the device is not shown in MSM nor in COM and LPT ports.
What is missing I'm not sure since I've tried a lot of that.
Any expert tech assistance would be great and appreciate it.
Click to expand...
Click to collapse
It sounds like you've corrupted your bootloader. Have you already used this guide? I suggest asking for support there.
I fixed it already, it works with 11.9.9.
@lukegonewild
I have the same error as you -> "Firehose Communication Handshake Failed"
I have tried my main Windows 11 PC and also a Windows 10 machine. It makes no difference.
That's strange, because I remember using the same tool 2 years ago
Can you please tell me how you fixed it?
marcelhdhd said:
@lukegonewild
I have the same error as you -> "Firehose Communication Handshake Failed"
I have tried my main Windows 11 PC and also a Windows 10 machine. It makes no difference.
That's strange, because I remember using the same tool 2 years ago
Can you please tell me how you fixed it?
Click to expand...
Click to collapse
Hi 🖐️
Make sure you install the right drivers for Qualcomm, also you must know that you cannot go for Oxygen 10.5.11, only 11 , you pick which image you would like your phone running from Oxygen 11 releases just remember that you can't go for lower software image like 10.5.11 cause it's not the system settings software. In theory OnePlus is not letting you install earlier releases that are 10 or lower. Respond which image file you're flashing in next reply, if it's the 11.9.9 I'll explain it in the comments section, it's not that complicated.
lukegonewild said:
Hi 🖐️
Make sure you install the right drivers for Qualcomm, also you must know that you cannot go for Oxygen 10.5.11, only 11 , you pick which image you would like your phone running from Oxygen 11 releases just remember that you can't go for lower software image like 10.5.11 cause it's not the system settings software. In theory OnePlus is not letting you install earlier releases that are 10 or lower. Respond which image file you're flashing in next reply, if it's the 11.9.9 I'll explain it in the comments section, it's not that complicated.
Click to expand...
Click to collapse
Thanks for your reply, but I managed to find the problem a few hours later. It was a bad USB-C cable.
Head -> Table
Hi i got an ASUS ROG 3 I003DD ZS661KS - 6A017CN TENCENT edition bricked while updating any solution? I tried everything from computer but not opening at all, screen total black and no recovery mode starts,
Any help is appreciated
what is the device showing identified as under device manager when plugged in from the side port?
Nothing black screen, i tried up down button and power but nothing, few days ago recovery mode worked now nothing.. i tried to look some programm for force boot the phone through pc but all websites link are empty, I don’t know what to do.. i was updating the phone then this happened..
Get the device in EDL mode with working Qualcom drivers and a good connection to your pc. Then follow below guide, all needed looks to be there. You can get the device in EDL mode with a flash cable that you can buy cheap or make one yourself from a USB cable - there are guides online for doing that too.
[UNBRICK/RAW] Revive your bricked ASUS ROG Phone 3 [23-NOV-2021]
Unbrick your ASUS ROG Phone 3 for free!! Don't pay for this stuff anywhere, it's your device and you deserve the right to fix it yourself. I noticed some people in the community charging upto 50$ for the firmware which should've been free from...
forum.xda-developers.com
I connected the phone with EDL cable the computer recognize as Qualcom device etc.. but
i tried to flash the raw stock firmware trough pc and EDL cable but nothing says Sahara error mode while the process