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
Related
hello, i have hard brick at my mi8 .
When i try to press the power button the phone doesn't boot, If i try to go into recovery mode it doesn't boot and same for fastboot mode.
The screen is unresponsive (no backlight) and it doesn't vibrate. When i connect the phone to my computer it is automatically recognized as Qualcomm HS-USB QDLoader 9008 (COM5) which correspond to the EDL mode (i think).
When try to flash any rom with miflash i get the error " cannot receive hello packet.
Can anyone help me ?:crying:
anderssx1 said:
hello, i have hard brick at my mi8 .
When i try to press the power button the phone doesn't boot, If i try to go into recovery mode it doesn't boot and same for fastboot mode.
The screen is unresponsive (no backlight) and it doesn't vibrate. When i connect the phone to my computer it is automatically recognized as Qualcomm HS-USB QDLoader 9008 (COM5) which correspond to the EDL mode (i think).
When try to flash any rom with miflash i get the error " cannot receive hello packet.
Can anyone help me ?:crying:
Click to expand...
Click to collapse
Likely you have too much power coming from your usb ports, use a usb hub such as this: https://www.amazon.com/BYEASY-Porta...jbGlja1JlZGlyZWN0JmRvTm90TG9nQ2xpY2s9dHJ1ZQ==
Now try Mi Flash again, make sure that the lock bootloader (which is checked by default) is unchecked.
Now it should work, be sure that you are using a fastboot rom and not a recovery rom. ( a recovery rom will not work)
Make sure that it is a fast boot for your device : If you have a global device here is a link with quite a few fastboot roms :https://c.mi.com/thread-1899815-1-0.html
If you still have trouble let me know, and tell me specifically how you arrived at your brick, I helped someone with this exact issue a couple of weeks ago, and I was going to link you to that thread. But i can't find it at the moment.
I get the same error " cannot receive hello packet" with hub USB.
MY xioami mi 8 is global version, i unlock the bootloader and make a downgrade with twrp to a older version of stable rom, and when the phone start ,its all ok and login my mi account, and the phone goes down and never more boot. Always in the pc i get qualcom port (edl mode) . Sorry for my bad english.:crying:
I think i need account with EDL authorization to flash any rom. And i can't found anyone to save me..
Try https://forum.xda-developers.com/mi-8/how-to/unbrick-mi8-edl-authorized-account-t3896677
Thank you .. i try this metod but no success
About s-unlock .. anyone knows if the service is online?
anderssx1 said:
About s-unlock .. anyone knows if the service is online?
Click to expand...
Click to collapse
Maybe try this site : MOD EDIT: link removed
I dont have his name but one of the techs from this site is a frequent XDA user and supposedly legit.
In the end there is a risk of losing $12. Seems to be worth $12 to me.
I send message to this brother , and it's 40 dollars .. i'm thinking about
thanks for reply
Hello all,
A friend of mine said he was careless and installed an A2 Lite ROM to his A2. All I know is he can't fix the phone no matter what he tried.
Can we do something about this? Or is the phone permanently bricked?
lelele5 said:
Hello all,
A friend of mine said he was careless and installed an A2 Lite ROM to his A2. All I know is he can't fix the phone no matter what he tried.
Can we do something about this? Or is the phone permanently bricked?
Click to expand...
Click to collapse
try flashing stock rom
Thank you for the reply. Will get back to you as soon as I get an answer from him.
Okay, I got some more info: From what my friend said:
He installed the ROM but after selecting "restart device" it didn't boot up.
Pressing button combinations has no effect either.
When the device is connected to PC Windows recognizes it as "Qualcomm HS-USB QDLoader 9008(COM3)".
He also tried different versions of MiFlash but he is getting "The Write timed out" and "cannot read hello packets" (???) errors.
Since the device isn't reacting to button presses he can't activate fastboot.
This was translated from another language. Hope I didn't make any mistakes.
EDIT: He tried edl before, it didn't work.
Now he is getting "Error loading type library/DLL".
Your friend need to do Flash Point
Ask him to google "How to flash a qualcomm soc with qpst via com port". I'm sure he'd find a lot of videos on youtube guiding through the entire process. Also tell him to keep the stock fastboot rom downloaded, coz he'll be needing that.
Flashing a wrong rom destroyed the partition table of his device. If he cant fix it himself, tell him to visit a nearby service centre. He'll get the device back in a few days or so.
lelele5 said:
Okay, I got some more info: From what my friend said:
He installed the ROM but after selecting "restart device" it didn't boot up.
Pressing button combinations has no effect either.
When the device is connected to PC Windows recognizes it as "Qualcomm HS-USB QDLoader 9008(COM3)".
He also tried different versions of MiFlash but he is getting "The Write timed out" and "cannot read hello packets" (???) errors.
Since the device isn't reacting to button presses he can't activate fastboot.
This was translated from another language. Hope I didn't make any mistakes.
EDIT: He tried edl before, it didn't work.
Now he is getting "Error loading type library/DLL".
Click to expand...
Click to collapse
all is fine ...
he can flash it in miflash in edl mode
if computer can see the 9008 com port he is already in edl
the error with hello packets is because he waits too long to start flashing ..he needs to unplug phone then when he plugs it in he must have everything prepared then press flash quickly
he can wait for battery to run out of charge ...then prepare miflash ...then plug in phome ...the EXACt moment it wakes press flash
then it will work
Thanks a lot for your time and help everyone. He got frustrated and sent it to a service center. I couldn't convince him. It works fine now, though.
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!
Hey everyone,
yesterday my zenfone 8 just shutdown without any sign of a problem before . i thought its nothing but since then it dosnt turn on !!!
my only hope is when i connected it to my pc i got qualcomm 900e , i managed to change it to Qualcomm HS-USB QDLoader 9008 with driver update.
but still no fastboot no nothing.
i understand there is a way with qfil tool but i dont know how to get the files for it. any help please???
i see that qfil can fix it with rawdata and patch0 but i dont have this files. can some one please help???
You can get it on ROMdevelopers
QFIL / UnBrick - QMSCT_ForCSC_DefaultFuseLock_Sake_30.02.46.108_repkg.zip
AzimBahar said:
You can get it on ROMdevelopers
QFIL / UnBrick - QMSCT_ForCSC_DefaultFuseLock_Sake_30.02.46.108_repkg.zip
Click to expand...
Click to collapse
Hey azim , i downloaded the files but it seems it knows that i am on 900e even when i tries to use other drivers to be 9008. can you please assits how to get out of 900e?? btw i managed to get the files out of my device but sahara server failed because of 900e :/
Connect phone to pC using test point and follow guides
Trigger device to 9008 mode-
1. Remove USB cable and battery (Change a new chipset, UFS
should be empty)
2. Connect the battery
3. Device will boot into the emergency download mode
4. Confirm that the device manager has detected “Qualcomm HS-
USB QDLoader 9008 (COM x)”.
& Its may help too
ZS590KS_Keybox_Keymaster_HDCP_Online_Tool_M1220.zip
AzimBahar said:
Trigger device to 9008 mode-
1. Remove USB cable and battery (Change a new chipset, UFS
should be empty)
2. Connect the battery
3. Device will boot into the emergency download mode
4. Confirm that the device manager has detected “Qualcomm HS-
USB QDLoader 9008 (COM x)”.
& Its may help too
ZS590KS_Keybox_Keymaster_HDCP_Online_Tool_M1220.zip
Click to expand...
Click to collapse
I dont understand what i need to do . I even tried with edl cable but still stuck on 900e
Once try to uninstall USB Driver & install ASUS QCOM Driver.
As you said , i managed to change it to Qualcomm HS-USB QDLoader 9008 with driver update
Click to expand...
Click to collapse
After try again !
Note - You May use EDL Cable for EDL mode !
AzimBahar said:
Once try to uninstall USB Driver & install ASUS QCOM Driver.
After try again !
Note - You May use EDL Cable for EDL mode !
Click to expand...
Click to collapse
I tried with edl cable... Only test point left to find
duduhayo said:
I tried with edl cable... Only test point left to find
Click to expand...
Click to collapse
sir i have the same issues, are you know the test point right now?
Kiyori said:
sir i have the same issues, are you know the test point right now?
Click to expand...
Click to collapse
Hey, i wish. No one found it, I am still waiting for the one
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