So I was going through the rooting process for the second time on my ATT Moto X and while in bootloader flashing 4.2.2 something went wrong and it wasn't fully flashed. There was no error, it just said "Done" on bootloader. So I restarted the phone and ever since then the phone has had a black screen, although when I plug it into my computer it recognizes it. With that said, I've tried to use RSD Lite but it just fails to put it into fastboot mode, and it does not come up under either fastboot devices or adb devices.
Not sure what else I could do from here. Holding the power button and volume down button to get into bootloader doesn't work either. Does anyone here have any ideas?
TsterT said:
So I was going through the rooting process for the second time on my ATT Moto X and while in bootloader flashing 4.2.2 something went wrong and it wasn't fully flashed. There was no error, it just said "Done" on bootloader. So I restarted the phone and ever since then the phone has had a black screen, although when I plug it into my computer it recognizes it. With that said, I've tried to use RSD Lite but it just fails to put it into fastboot mode, and it does not come up under either fastboot devices or adb devices.
Not sure what else I could do from here. Holding the power button and volume down button to get into bootloader doesn't work either. Does anyone here have any ideas?
Click to expand...
Click to collapse
Can you clarify a few things?
First, have you been on 4.2.2 this entire time, or were you attempting to 'downgrade'?
Next, when you "turn on" the device, you say it has a black screen...does it light up at all, or vibrate?
And third, when you say the device is 'recognized' by the PC, how is it recognized? When you go to Device Manager, do you see a listing for "qhsusb_bulk"? If not, what is the device listed as?
Sorry I didn't specify those things in the original post, but I appreciate you taking the time to respond.
I was originally on 4.4 and was in the process of downgrading to 4.2.2 post-camera.
The phone does not light up or vibrate or anything, but I can hear it connect on my computer. Not that this is the computer making the sound, not the phone.
And third, my phone comes up as a listing on RSD Lite v6.5.1. It does not provide any information, it just says it is connected. My device is listed as "Qualcomm HS-USB QDLoader 9008 (COM4)"
TsterT said:
Sorry I didn't specify those things in the original post, but I appreciate you taking the time to respond.
I was originally on 4.4 and was in the process of downgrading to 4.2.2 post-camera.
The phone does not light up or vibrate or anything, but I can hear it connect on my computer. Not that this is the computer making the sound, not the phone.
And third, my phone comes up as a listing on RSD Lite v6.5.1. It does not provide any information, it just says it is connected. My device is listed as "Qualcomm HS-USB QDLoader 9008 (COM4)"
Click to expand...
Click to collapse
OK, I understand. There may be hope for you but it will require patience and exacting precision. Don't get your hopes up TOO much, but I will attempt to help you.
Normally, it is NOT possible to downgrade, but (thankfully) 4.4 > 4.2.2 Post-Camera is the one exception.
First, I realize that RSD Lite shows "Qualcomm HS-USB QDLoader 9008 (COM4)", but I need you to open Device Manager and tell me what it says in there. If you aren't familiar with how to get there, simply press the start button, and type 'device manager' (without quotes, of course). It should show up under "Control Panel", assuming you are on Windows 7.
Also, tell me for sure which version of Windows your PC is running.
Then we can proceed further.
"Qualcomm HS-USB QDLoader 9008 (COM4)" is from Device Manager. RSDLite simply lists the model as "QHSUB_DLOAD"
I am running Windows 8.1 64bit
TsterT said:
"Qualcomm HS-USB QDLoader 9008 (COM4)" is from Device Manager. RSDLite simply lists the model as "QHSUB_DLOAD"
I am running Windows 8.1 64bit
Click to expand...
Click to collapse
Ah, OK. This is good news.... "QHUSB_DLOAD"
Basically, you have somehow corrupted your bootloader.
Please reference this thread: http://forum.xda-developers.com/showpost.php?p=49876179&postcount=1
If you follow the instructions exactly, we should be able to force your phone into fastboot mode. From there, we can manually flash back to 4.4
Remember, there are no guarantees with this, and I don't even know if it has been attempted or is possible in Windows 8. So if you aren't successful, get your hands on a Windows 7 PC, and try again.
If you get stuck, post back here and I will attempt to help.
Sweet man, I really appreciate your help. I'll try all of that and report back here when done. Thank you again.
TsterT said:
Sweet man, I really appreciate your help. I'll try all of that and report back here when done. Thank you again.
Click to expand...
Click to collapse
One last comment: Do NOT use a USB 3.0 port for this. Only use a USB 2.0 port. Good Luck, and let us know how it works out....
Hell ya, it worked like a charm. Back into bootloader. Thank you again for helping me so quickly. You're awesome.
TsterT said:
Hell ya, it worked like a charm. Back into bootloader. Thank you again for helping me so quickly. You're awesome.
Click to expand...
Click to collapse
Welcome!!! Glad it went so smoothly for you. Remember to give 'thanks' to the OP of the De-Bricking thread I linked you to.
:good:
Help please
Help please
hi Bro
I followed ur step bcz my phone got stuck on the 4th step
http://forum.xda-developers.com/moto...t1060-t3118342
when i did the 4th step it got lack for around 30 min and nothing happens i quit the application and the phone is still in black screen
i have attached images with error what i get
i have moto xt1060
Related
Tried rooting moto xt1060 5.1 with the locked boot loader method, and then got stuck at the black screen from running python. Computer still recognizes it as a QCUSB (COM4) or something similar to that, but screen doesn't turn on at all. Tried every button combo, usb port, how-to's, but I'm a newbie with this. Any help would be appreciated. Thanks.
Its hardbrick, run root file inside that package, but first read and install every drivers mention on that post.
Salik Iqbal said:
Its hardbrick, run root file inside that package, but first read and install every drivers mention on that post.
Click to expand...
Click to collapse
which package?
motoexuser said:
which package?
Click to expand...
Click to collapse
The one you tried too root?
Salik Iqbal said:
The one you tried too root?
Click to expand...
Click to collapse
i tried it. no errors, but phone screen is still black. i am gonna charge the phone over night and try again.
also i get this error every time i try to run RSD lite "phone failed to switch to fast boot"
other info if it helps:
- phone is always recognized as "Qualcomm HS-USB QDLoader 9008 (COM5)"
- computer makes connecting and disconnecting sound when button combinations are held
motoexuser said:
i tried it. no errors, but phone screen is still black. i am gonna charge the phone over night and try again.
also i get this error every time i try to run RSD lite "phone failed to switch to fast boot"
other info if it helps:
- phone is always recognized as "Qualcomm HS-USB QDLoader 9008 (COM5)"
- computer makes connecting and disconnecting sound when button combinations are held
Click to expand...
Click to collapse
Well you need some extra help now.. will send you a package on monday.
Salik Iqbal said:
Well you need some extra help now.. will send you a package on monday.
Click to expand...
Click to collapse
thanks
I accidentally deleted my phone OS using TWRP.
So, I fixed this and installed stock android firmware for my device and locked the bootloader.
It was all set up nicely. Then, I decided to update to the latest android version and now it showed the updating logo and everything and the screen suddenly went black and it won't show anything.
I have tried holding power and volume down for 2 minutes but have had no luck.
I have tried charging with many USB cables.
When I plug a USB cable into my phone and computer, I get the error message "USB Device Not Recognized".
Please help me fix this error and help me to get my phone working again, thank you in advance.
You broke the bootloader, this can be solved if Moto releases the blankflash files, however motorola has no idea in releasing those files. get some other mobile, no other alternatives as of now.
Jon_6 said:
I accidentally deleted my phone OS using TWRP.
So, I fixed this and installed stock android firmware for my device and locked the bootloader.
It was all set up nicely. Then, I decided to update to the latest android version and now it showed the updating logo and everything and the screen suddenly went black and it won't show anything.
I have tried holding power and volume down for 2 minutes but have had no luck.
I have tried charging with many USB cables.
When I plug a USB cable into my phone and computer, I get the error message "USB Device Not Recognized".
Please help me fix this error and help me to get my phone working again, thank you in advance.
Click to expand...
Click to collapse
Sorry Bro, you've completely bricked your phone. Even if Motorola releases blank flash files for Moto G 2 Titan, your mobile should be detected as "Qualcomm HS-USB Qdloader 9008". But as you mentioned that when you connect your phone with PC, it shows USB DEVICE NOT RECOGNISED, so there is nothing you can do now. Try giving it to service centre see if they can help
pkdon123 said:
Sorry Bro, you've completely bricked your phone. Even if Motorola releases blank flash files for Moto G 2 Titan, your mobile should be detected as "Qualcomm HS-USB Qdloader 9008". But as you mentioned that when you connect your phone with PC, it shows USB DEVICE NOT RECOGNISED, so there is nothing you can do now. Try giving it to service centre see if they can help
Click to expand...
Click to collapse
Thank you for your reply. I tried plugging my phone into my PC again after leaving it for a while and charging it for a few hours. Now, it shows as Qualcomm HS-USB Qdloader 9008 as you said. For some reason, it wasn't recognised last time I connected my phone to my computer.
Karthik_pm said:
You broke the bootloader, this can be solved if Moto releases the blankflash files, however motorola has no idea in releasing those files. get some other mobile, no other alternatives as of now.
Click to expand...
Click to collapse
Thank you for your answer, in the meantime, I'll just buy a cheap SIM-free phone that is in my Moto G.
I may as well use that and when my contract is finished, buy a new phone.
Jon_6 said:
Thank you for your reply. I tried plugging my phone into my PC again after leaving it for a while and charging it for a few hours. Now, it shows as Qualcomm HS-USB Qdloader 9008 as you said. For some reason, it wasn't recognised last time I connected my phone to my computer.
Click to expand...
Click to collapse
Well That's A Good News But I've Tried Searching Blank Flash Files on Google, Unfortunately I'm Unable To Find The Files For TITAN, The Files Available Online Are for Moto G FALCON, Which Wont Work Here..
Hi I just recived my mi5 and was wanting to put a stock android rom on it that is stable, I see a couple of ROMs on here but not sure what to use or where to start if anyone can give me a guide and correct ROM to use, I'm in UK Scotland
Sent from my HTC One using Tapatalk
Please help me my phone is in EDL mode and i can't flash anything on it. It does not turn on no led no light no display no response. Just Qualacomm QDLoader 9008
Everytime i flash it gives me an error.
Max buffer sector is 256.
Errors and so on.....
How to fix please
I have reinstalled all drivers and programs , tried a lot of miflash versions , fastboot roms like 6-8. Many pc restarts
casuk said:
Hi I just recived my mi5 and was wanting to put a stock android rom on it that is stable, I see a couple of ROMs on here but not sure what to use or where to start if anyone can give me a guide and correct ROM to use, I'm in UK Scotland
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
If I were you I would definitely flash Lineage OS, its really solid, fast and has a good battery life.
Check this post for instructions. And give him a big thank
Spevky said:
Please help me my phone is in EDL mode and i can't flash anything on it. It does not turn on no led no light no display no response. Just Qualacomm QDLoader 9008
Everytime i flash it gives me an error.
Max buffer sector is 256.
Errors and so on.....
How to fix please
I have reinstalled all drivers and programs , tried a lot of miflash versions , fastboot roms like 6-8. Many pc restarts
Click to expand...
Click to collapse
I had the exact same problem, it happened randomly after a normal reboot. I was considering taking it apart to disconnect the battery, try a deepflash cable and EDL but then I solved it.
The problem is your Windows driver. That's why you can't flash anything. Read up on Xiaomi forums about the problem. I can't remember exactly how I solved it, but I think I uninstalled the driver, plugged the phone back in, wait for the automatic install on Device Manager, then for it to update, do a roll back and then flash it via MiFlash.
xdadevet said:
I had the exact same problem, it happened randomly after a normal reboot. I was considering taking it apart to disconnect the battery, try a deepflash cable and EDL but then I solved it.
The problem is your Windows driver. That's why you can't flash anything. Read up on Xiaomi forums about the problem. I can't remember exactly how I solved it, but I think I uninstalled the driver, plugged the phone back in, wait for the automatic install on Device Manager, then for it to update, do a roll back and then flash it via MiFlash.
Click to expand...
Click to collapse
Thanks. THat must be the problem. But i tried on my friends pc too and it did not work. Maybe Windows 7 is the problem? Im installing Windows 10.
Which OS do you have?
Spevky said:
Thanks. THat must be the problem. But i tried on my friends pc too and it did not work. Maybe Windows 7 is the problem? Im installing Windows 10.
Which OS do you have?
Click to expand...
Click to collapse
I don't think Windows 7 is the problem, but I've been using Windows 10 for 3 years (as Beta user) so I can't tell. Boot into EDL (Phone must be powered off, then hold both "Volume UP" and "Volume Down" as you plug it into the computer, only then do you let go) and tell me what driver your phone is seen as in Device Manager.
xdadevet said:
I don't think Windows 7 is the problem, but I've been using Windows 10 for 3 years (as Beta user) so I can't tell. Boot into EDL (Phone must be powered off, then hold both "Volume UP" and "Volume Down" as you plug it into the computer, only then do you let go) and tell me what driver your phone is seen as in Device Manager.
Click to expand...
Click to collapse
It is detected as QDLoader 9008 version of QDLoader 9008
im trying to follow the guides but im not understanding what to do I have downloaded adb and fastboot I extracted the files to a folder and im now stuck, whats this mean
•Append ;%USERPROFILE%\adb-fastboot\platform-tools to the end of the existing Path definition (the semi-colon separates each path entry)
that's were im am so far and im basically lost and need so help if anyone is kind enough to go through the steps with me
thanks
Ok I've unlocked the phone but i can seem to be able to root it
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 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.