Related
hi
Sorry for my English
I wanted to root my phone but made a mistake somewhere.
now the phone is always off. when connected to the computer, program RSD see him as QHSUSB_DLOAD; computer see him as Qualcomm HS-USB QDLoader 9008
RSD don`t flasing(The phone failed to switch to fastboot mode)(FAIL) flasing cabl dont helped.
How reestablished bootloader
nobody knows how to help me?
It appears that you have a corrupt boot loader and unfortunately we do not have any of the files available to us that would be needed to fix your phone.
They would be the proprietary binaries and low level boot images from Qualcomm for flashing to a new board at the factory.
We have such repair kits for some earlier OMAP based devices but I have not heard of or seen any such files for the Qualcomm S4 devices, sorry.
If you wish to make a clean install without bothering about backup and so and so then I can guide you through that.
kaskoraja said:
If you wish to make a clean install without bothering about backup and so and so then I can guide you through that.
Click to expand...
Click to collapse
how?
same problem
i have the same problem and the same brick. Can anyone help us?:crying:
+ to brick reason
Ral126 said:
i have the same problem and the same brick. Can anyone help us?:crying:
Click to expand...
Click to collapse
You forget, thats you also try to flash MIUI!
St.Noigel said:
You forget, thats you also try to flash MIUI!
Click to expand...
Click to collapse
Yes) I tried))) But for the beginning i need to reestablished bootloader.
ASUS PadFone 2 QHSUSB_DLOAD error
I've an ASUS Padfone 2 with the same error. Looks like it's kind of easy to get these Qualcomm devices into this f*cking issue
My case is detailed here: http://forum.xda-developers.com/showthread.php?t=2220775
kaskoraja said:
If you wish to make a clean install without bothering about backup and so and so then I can guide you through that.
Click to expand...
Click to collapse
Good evening,
I bricked the Innos D9 because I installed 2 new roms .........
I first stalled the DNS and it was a very nice rom but I was not 100% happy ...........than I installed the Cloudfone rom and this was very bad..........than I wanted to go back to the DNS rom and I got the same problem as yours.
I searched for a solution and I found a video on YouTube ..." Restore Acronis Backup on CloudFone Thrill 430X (Innos D9) " and after this experiment my Innos D9 is totally dead.....it isn't recognized by the computer ....not even by clicking or holding any button ..........when I connect the USB to my laptop I can only hear the sound that something has been connected to the laptop ........but nothing is visible.
any help to unbrick my phone?
One thing you could try is sending a message over to Josh at mobiletechvideos.com and see if he can help. It looks like they offer JTAG repairs for hard bricks(link).
Note: I don't work for mobiletechvideos or anything. I just had my Samsung Focus power button repaired by them a couple weeks ago and they did a pretty nice job.
I've got same problem with Asus Padfone A66.
I installed the qualcomm drivers, and QPST program is see my phone, but i have no idea howto use this program, or howto convert image files to (proper) .hex format, or howto build needed files. My cpu is MSM8260 and QPST see my phone as Q/QCP-XX (Download). And maybe I need for a proper MPRG8260.hex and aml, mbm files for flashing. so QPST sjust throwing error, ahnd happen nothing.
http://forum.xda-developers.com/showpost.php?p=45548210&postcount=3
Hello everyone, I'm having the same problem .
Someone found a solution to this problem?
I have a RAZR HD .
Thank's
So, I side loaded build no. 13.8.26.76 to my phone, not knowing that it was meant only for the snapdragon 410 counterpart (mine is 615 one). It installed successfully until I rebooted and phone stayed dead. I think I hard bricked it
No logo, no charging, can't enter recovery or fastboot. No nothing... Connected device to PC, and windows doesn't recognize it.
Please help me....
sree27 said:
So, I side loaded build no. 13.8.26.76 to my phone, not knowing that it was meant only for the snapdragon 410 counterpart (mine is 615 one). It installed successfully until I rebooted and phone stayed dead. I think I hard bricked it
No logo, no charging, can't enter recovery or fastboot. No nothing... Connected device to PC, and windows doesn't recognize it.
Please help me....
Click to expand...
Click to collapse
Can you go to recovery mode ?? If yes please flash your device compatibility custom rom like RR rom ..if u cant go to even recovery mode..
RIP asus zenfone max Just Change your Motherboard of your phone
Thanks
Its dead u can recover i also had same issue ...mine works now ....email me [email protected]
Hello, I had a very little progress. I gave up about my asus zenfone max a year ago but glad that now looks like there's a hope in reviving my phone. I was able to download the right files to flash with QFIL. Most people here say that their PC detected QUALCOMM HS-USB QDLOADER 9008 but mine detect it as QUALCOMM HS-USB DIAGNOSTICS 9006. Due to excitement, I flashed it anyway and it created some memory partition on my hard drive whenever I plug the phone but QFIL gave me an error of :
** Download Fail: Switch To EDL Fail Failed to switch to Emergency Download Mode
I tried to google this error, some encountered it and was able to get a resolution by just removing the battery before plugging it in but our zenfone is with non removable battery. I have no luck yet. Anyone got suggestions ?
MJMarra34 said:
Hello, I had a very little progress. I gave up about my asus zenfone max a year ago but glad that now looks like there's a hope in reviving my phone. I was able to download the right files to flash with QFIL. Most people here say that their PC detected QUALCOMM HS-USB QDLOADER 9008 but mine detect it as QUALCOMM HS-USB DIAGNOSTICS 9006. Due to excitement, I flashed it anyway and it created some memory partition on my hard drive whenever I plug the phone but QFIL gave me an error of :
** Download Fail: Switch To EDL Fail Failed to switch to Emergency Download Mode
I tried to google this error, some encountered it and was able to get a resolution by just removing the battery before plugging it in but our zenfone is with non removable battery. I have no luck yet. Anyone got suggestions ?
Click to expand...
Click to collapse
Check my post for detailed instructions. And yes, I did face that issue and fixed it by reinserting the battery. It's a bit risky, but worth a try. Try watching some YouTube teardown videos
sree27 said:
Check my post for detailed instructions. And yes, I did face that issue and fixed it by reinserting the battery. It's a bit risky, but worth a try. Try watching some YouTube teardown videos
Click to expand...
Click to collapse
Oh Great! do you have a link of your instructions man? thank you! so I really have to dissassemble the phone?
MJMarra34 said:
Oh Great! do you have a link of your instructions man? thank you! so I really have to dissassemble the phone?
Click to expand...
Click to collapse
It's on my profile. I haven't mentioned the disassembly part since it was not required in general cases. Check my profile for the detailed instructions
Hey Man. I'm currently working on my phone. I already tried removing the battery but I'm still getting the error:
Download Fail: Switch to EDL Fail.
hopes are going narrow. Now I don't know what to do.
MJMarra34 said:
Hey Man. I'm currently working on my phone. I already tried removing the battery but I'm still getting the error:
Download Fail: Switch to EDL Fail.
hopes are going narrow. Now I don't know what to do.
Click to expand...
Click to collapse
Are you on fastboot mode? What is on your display?
Im still at the part with the QFIL. Im retrying it right now bruh.. hmmm
MJMarra34 said:
Im still at the part with the QFIL. Im retrying it right now bruh.. hmmm
Click to expand...
Click to collapse
If you're having trouble with QFIL, best thing to do is uninstall Qualcomm drivers, reboot, reinstall, try again. Repeat until you can flash without problem.
I had to uninstall many times. Don't lose hope. It takes a lot of effort
hey Sree. I noticed that it is being detected as Qualcomm HS-USB diagnostics 9006. So what I did is I forced driver to install Qualcomm HS-USB QDLoader 9008. I'm now having a Sahara error. I'll try reinstalling drivers but I have a quastion. Does QFIL version matter ?
MJMarra34 said:
hey Sree. I noticed that it is being detected as Qualcomm HS-USB diagnostics 9006. So what I did is I forced driver to install Qualcomm HS-USB QDLoader 9008. I'm now having a Sahara error. I'll try reinstalling drivers but I have a quastion. Does QFIL version matter ?
Click to expand...
Click to collapse
I don't know. I used the latest one. Try the version linked in my original post. Also, of you're getting sahara fail, it's ok. You're on right track. Uninstall driver, reboot and reinstall. It'll take hell a lot of tries, but will work eventually
My problem is that I can't even try to do the procedure in the other threads that i've read because my pc simples dont recognize anything when i install the qualcomm drivers. Any tips? Thank you in advance. I want to try this thread [GUIDE][QFIL MODE]Unbrick your Le Pro3, tested and working. But simply the qualcomm port doesnt appear in the device manager.
Bad cable or need to reinstall drivers...
marik1 said:
Bad cable or need to reinstall drivers...
Click to expand...
Click to collapse
I tried with two different cables and reinstalled the drivers a few times now. No port in the device manager. Just the Android ADB Interface tha showed when I installed the leeco adb drivers. On the ports just appear the standard Comunication port and printer port. I tried everything, the volume bottons power, etc. The Flash One dont recognize the phone for QFIL.
Say sth more about your phone state and history...
marik1 said:
Say sth more about your phone state and history...
Click to expand...
Click to collapse
I dont have hardware problems. I flashed the Pixel Experience rom in february with sucess but I didnt like it. It had too much battery drain. Then I wanned to try some other rom like AICP. But in the process of flashing something went wrong. I wasnt able to flash it, always gave me the error 7. Then it simply died. I was rebooting TWRP mode and it went dead. Now just vibrates when I try to turn on. I tried the QFIL process (both volumes + power) but I dont even know. How can we know that it in qfil mode? My pc wont recognize anything. Not in Flash One, Not in QPST, nothing. Am I doing something wrong? The phone vibrates so its charged. I installed the Qualcomm drivers properly, I thing, eventhow it doesnt appear the qualcomm 9008 port in the device manager. Its suppose to appear before the phone is pluged right? Thank you for the reply.
I've no idea how to help you... Sorry.
gradim said:
I dont have hardware problems. I flashed the Pixel Experience rom in february with sucess but I didnt like it. It had too much battery drain. Then I wanned to try some other rom like AICP. But in the process of flashing something went wrong. I wasnt able to flash it, always gave me the error 7. Then it simply died. I was rebooting TWRP mode and it went dead. Now just vibrates when I try to turn on. I tried the QFIL process (both volumes + power) but I dont even know. How can we know that it in qfil mode? My pc wont recognize anything. Not in Flash One, Not in QPST, nothing. Am I doing something wrong? The phone vibrates so its charged. I installed the Qualcomm drivers properly, I thing, eventhow it doesnt appear the qualcomm 9008 port in the device manager. Its suppose to appear before the phone is pluged right? Thank you for the reply.
Click to expand...
Click to collapse
Instead of creating a new post why not just read the enormous unbrick forums that exists and have proven steps. Many, Many phones have been debricked using those steps.
Hint, read the last pages for updated links to the software tools needed.
Next, I just found this cable which will help immensely with unbricking your device: https://www.amazon.com/GPG-EDL-Cabl...r1&keywords=edl+cable+for+wall+qualcomm+usb+c
tsongming said:
Instead of creating a new post why not just read the enormous unbrick forums that exists and have proven steps. Many, Many phones have been debricked using those steps.
Hint, read the last pages for updated links to the software tools needed.
Next, I just found this cable which will help immensely with unbricking your device: https://www.amazon.com/GPG-EDL-Cabl...r1&keywords=edl+cable+for+wall+qualcomm+usb+c
Click to expand...
Click to collapse
I've tried four different cables now and nothing. Thank you for minding but I think there isn't a solution for my leeco. Its dead and no one can help him.
Is yours 722?
Sent from my SM-A730F using xda premium
mchlbenner said:
Is yours 722?
Sent from my SM-A730F using xda premium
Click to expand...
Click to collapse
No, x720 6gb ram 64 rom.
gradim said:
No, x720 6gb ram 64 rom.
Click to expand...
Click to collapse
Is your phone completely Dead or do you have fashboot or anything working.
Do have a red flashing light?
Sent from my SM-A730F using xda premium
mchlbenner said:
Is your phone completely Dead or do you have fashboot or anything working.
Do have a red flashing light?
Sent from my SM-A730F using xda premium
Click to expand...
Click to collapse
Completely dead, just vibrates when I press power and yes, I sometimes have the red light, sometimes flashing, sometimes stable.
gradim said:
I dont have hardware problems. I flashed the Pixel Experience rom in february with sucess but I didnt like it. It had too much battery drain. Then I wanned to try some other rom like AICP. But in the process of flashing something went wrong. I wasnt able to flash it, always gave me the error 7. Then it simply died. I was rebooting TWRP mode and it went dead. Now just vibrates when I try to turn on. I tried the QFIL process (both volumes + power) but I dont even know. How can we know that it in qfil mode? My pc wont recognize anything. Not in Flash One, Not in QPST, nothing. Am I doing something wrong? The phone vibrates so its charged. I installed the Qualcomm drivers properly, I thing, eventhow it doesnt appear the qualcomm 9008 port in the device manager. Its suppose to appear before the phone is pluged right? Thank you for the reply.
Click to expand...
Click to collapse
Your phone is probably fixable.
Based on what you stated above, it seems that you downloaded and attempted to install the wrong version of TWRP and now your phone has no recovery at all.
Here is partial instructions I posted in the unbricking forum : https://forum.xda-developers.com/showpost.php?p=76100899&postcount=121
Use those instructions along with is mentioned below. I have personally helped so many people unbrick their phone that I have lost track and this is the reason why the posts are so long and extensive. Because sometimes what works for one person does not work for the next. So I have essentially have taken everyone's great advice and updated the links, made the instructions steps a little more concise and easier to read, fixed some incorrect steps or added the needed skipped steps. Plus added my own research into what I believe is now a definitive guide for unbricking the Leeco variants X720 and X727. The point of not reposting the information here is to keep everything from becoming more fragmented.
Yes, it's possible that you have a hardware issue. But, its also possible that it can be fixed!
Remember that you will not see the port unless you are in EDL mode
Just press volume △ (+) and volume ▽ (–) buttons together while powering the phone on.
It should now be EDL mode. If you cannot get into EDO mode, you cannot do anything else.
If you get an error, press and hold the power button while at the same time hold vol up + and down simultaneously plug the usb cord into the back of the computer while holding the buttons.
Yes, It's a pain and this is why the deep flash cable is handy....it's a special cable ( so your extra cables will do nothing to help you) The deep flash cable will automatically put your phone into EDL mode and allow you to use Flash on.
Install the Qualcomm QDLoader 9008 driver: https://goo.gl/9E3bKq or the from links provided in the unbrick forum.
There are multiple versions or Qfil, some have issues. I posted the correct one that works.
FOR anything else go to that forum read my and everyone else's posts. Again, I keep all of my linked files are up to date, and many are located on my own drives.
You can make one of these cables. Here's a video that shows you how:
https://www.youtube.com/watch v=kSiGsYK66gM&lc=z220yhtqvwyyct21pacdp432sh2xjecek10dae1jen5w03c010c.1524884617336803
it will not be a quick fix.
There are 4 or 5 different unbricking options and it requires persistence and patience.
The good news is that your phone has a solution that may work.
So when your where flashing a rom you got error 7 and your phone went dead.
I had gotten that same error.
Error could mean two things 1) update recovery or update firmware.
My point is sounds nice like hardware issue.
These phones are known for just dieing.
Also getting into that mode you have to push power+volume+volume- at the same time.
Sent from my SM-A730F using xda premium
So I've managed to brick my device (A2017G) after trying to flash LineageOS 15.1. Here's a summary of my particular situation:
- I was on AEX and tried to flash LOS 15.1. Things went wrong when I got error 7 and tried to reboot. Can't boot to recovery ever since.
- I can still boot into fastboot. Tried flashing TWRP (3.2.3-0), supposedly it installs but I can't boot into it.
- I bought an edl cable (search for EDL Tief Flash Qualcomm 9008 2-in-1 Kabel für Z3 X/Octopus on Amazon.de) but still can't get it into edl mode. I've tried several different combinations and timings, because there seem to be different methods of using the edl cable and I don't know which one is correct. Anyhow, none of the methods have worked so far and I can only get it recognized as dfu. Although I did manage to get it recognized as QUSB_BULK on one occasion, but not sure how I did it and haven't been able to recreate it since.
I've been looking up information for 2 hours on possible fixes, but there's just so much information (sometimes incomplete) that I can't make heads or tails of it anymore. So hopefully one of you can help me or maybe you've been in the exact same situation. The most important thing right now is I'd like to know if there's still a way out of this or if it's bricked for good.
If you are still stuck in DFU mode then you might want to try this:
https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229/page1
AnonVendetta said:
If you are still stuck in DFU mode then you might want to try this:
https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229/page1
Click to expand...
Click to collapse
Thanks! It actually worked, I can't believe it. Much appreciated, you saved me from needlessly buying a new phone.
hi, everyone , i m tring to revive my hard bricked oneplus 8 pro but without any luck i m getting "firehosecheckrsp failed errno 258" error , i tried every possible solution a did find (Drivers, Cable, USB 2 , other pc) , i m convinsed tha i shoud start search for a motherboard replacements (even that i coudnt find on the internet)
so please if anyone could help me (Phone stuck on EDL mode - recognised by pc but buttons combination doesn't work )
If you're in edl mode, have you attempted to MSM back to stock?
That's about as low level as you can get, so from a recovery perspective if that doesn't work then nothing will.
Also have you tried holding all the buttons for a long time? Say 30 seconds?
Bare in mind that EDL mode will not remain on for very long, you have to have the MSM tool open and ready for the connection, then with the phone off. Connect it to pc and hold volume up and down, you'll hear the windows ding and it'll say connected on the MSM tool, then and only then click start, flashing should commence and it'll remain locked in EDL until complete.
Lastly you're in warranty so you shouldn't need to buy or replace anything.
dladz said:
If you're in edl mode, have you attempted to MSM back to stock?
That's about as low level as you can get, so from a recovery perspective if that doesn't work then nothing will.
Also have you tried holding all the buttons for a long time? Say 30 seconds?
Bare in mind that EDL mode will not remain on for very long, you have to have the MSM tool open and ready for the connection, then with the phone off. Connect it to pc and hold volume up and down, you'll hear the windows ding and it'll say connected on the MSM tool, then and only then click start, flashing should commence and it'll remain locked in EDL until complete.
Lastly you're in warranty so you shouldn't need to buy or replace anything.
Click to expand...
Click to collapse
Thanks for you're replay , but the phone is always on EDL mode even if i unplug the battery (open phone) when i plug again the phone goes automatically to EDL mode and MSM tool show the phone as connected , but when i try to pass the flash, i got the 258 error
ahmadOnePlus said:
Thanks for you're replay , but the phone is always on EDL mode even if i unplug the battery (open phone) when i plug again the phone goes automatically to EDL mode and MSM tool show the phone as connected , but when i try to pass the flash, i got the 258 error
Click to expand...
Click to collapse
Did you make sure you changed the target device?
Also, what model 8 pro? Are you using correct msm for that model? And it almost sounds like you aren't using correct drivers. Qualcomm USB drivers are needed
jamescable said:
Did you make sure you changed the target device?
Also, what model 8 pro? Are you using correct msm for that model? And it almost sounds like you aren't using correct drivers. Qualcomm USB drivers are needed
Click to expand...
Click to collapse
+1 to this
You need these so the phone is detected correctly in windows. Here is a link.
Qualcomm HS-USB QDLoader 9008 Drivers: Download and Installation Guide
Download Qualcomm HS-USB QDLoader 9008 drivers for communicating with your Android device in Emergency Download (EDL) mode. Learn how to install these drivers on any Windows 11/10/8.1/8/7 computer.
www.thecustomdroid.com
I have the same problem. I have a 7T but stuck with the same error firehose check rsp failed, errno:258
gcf81 said:
I have the same problem. I have a 7T but stuck with the same error firehose check rsp failed, errno:258
Click to expand...
Click to collapse
Hey, I think you reached out to me on YouTube. Do you know for sure which model of OnePlus 7T you have? There are two common versions in North America HD1907 (T-Mobile) and HD1905 (international unlocked)
Nick-Henkey said:
Hey, I think you reached out to me on YouTube. Do you know for sure which model of OnePlus 7T you have? There are two common versions in North America HD1907 (T-Mobile) and HD1905 (international unlocked)
Click to expand...
Click to collapse
Hey Nick, thanks for responding. It was bought unlocked North America version but then ATT customer support went into the phone while trying to fix something and I think they locked it right before it crashed.
gcf81 said:
Hey Nick, thanks for responding. It was bought unlocked North America version but then ATT customer support went into the phone while trying to fix something and I think they locked it right before it crashed.
Click to expand...
Click to collapse
Looking around, the North America version should be running international firmware (HD1905):
OnePlus 7T hardware variants
I was curious about the different hardware variants of the 7T and decided to ask support once EU launch went over and they kindly answered. HD1900: China HD1901: India HD1903: Europe HD1905: North America HD1907: T-Mobile USA
forum.xda-developers.com
I presume that you're using this MSM tool - https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.3994835/
Did you try all of the steps suggested by OP, yet?
Install drivers
Change to factory cable
Different USB port
Different Windows computer?
The only thread I could find where this problem was solved was on the OnePlus forum. The user completely removed and reinstalled the Qualcomm drivers (a different PC should handle that) - https://forums.oneplus.com/threads/solved-closed-trying-to-unbrick-op5t.956810/