Hello
Posted this over in Pauls MoDaCo forum as well but not had any replies yet so thought it best to try here as well.
I've bricked my Desire, phone loads up but the sim and sd card aren't recognised (though I can still use wi fi).
When connecting the phone to my PC (tried windows 7 and XP) the drivers fail to install and I get various faults like the device being recognised as android 1.0 usb to a Qualcomm device.
The phone is still rooted (I can install rooted apps from the market) however after following various unbricking guides I always get stuck at stage 2 (i.e. enable sd card), if the PC won't recognise the device how can i run the 'fastboot oem enableqxdm 0' command?
I've also tried running fastboot using a terminal app on the phone but it doesn't recognise fastboot, should i be in a specific directory on the phone when running this command?
Any help greatly appreciated.
Cheers
Have you tried using a different jab port? I had to use one at the back of my pc front ports wouldn't install drivers properly.
Sent from my HTC Desire using XDA App
You need to follow the guide on modaco for unbricking your device. You have the usb brick, and it can easilly be fixed.
Follow the steps religiously and you will be up n running in no time again.
I've followed the guide lots of time, it's not that long winded so it shouldn't be to hard to follow.
I get stuck on step two, using the fastboot command.
My PC and also tried laptop (Win XP and 7), different USB ports (front and back) but each time it attempts to load drivers and I end up with it either being recognised as an Android 1.0, Android Bootloader Interface or a Qualcomm device. I then run fastboot, and get the device not recognised error.
I've now tried to connect my phone to a windows Xp and 7 PC and a laptop, a Linux laptop and tried using the Tiny Linux root guide to see if that would work, but each time the PC/laptop fails to recognise the phone so can't get into recovery or run the fastboot command.
celticone said:
I've now tried to connect my phone to a windows Xp and 7 PC and a laptop, a Linux laptop and tried using the Tiny Linux root guide to see if that would work, but each time the PC/laptop fails to recognise the phone so can't get into recovery or run the fastboot command.
Click to expand...
Click to collapse
You don't need to get into recovery for this.
You have sdk installed, so boot your phone by pressing power while holding down the volume down button.
Use a command prompt on your pc and cd to the tools directory in the sdk. If the sdk is saved to the root of your C: drive on the pc you would type
Code:
cd C:\android-sdk-windows\tools
When in there type
Code:
fastboot oem enableqxdm 0
This will re-enable your sd card and allow you to continue.
That doesnt work, just stops on the waiting for device line and doesnt continue.
Also using the cmd 'adb devices' shows nothing so I'm guessing my phone isn't recognised on my PC. At the moment it's in fastboot usb (on phone) and in devices on the PC I've got Android Bootloader Interface with the yellow problem sign against it.
thanks for your help, it's appreciated, tried a few forums but no one is that interested in helping.
Cheers
celticone said:
That doesnt work, just stops on the waiting for device line and doesnt continue.
Also using the cmd 'adb devices' shows nothing so I'm guessing my phone isn't recognised on my PC. At the moment it's in fastboot usb (on phone) and in devices on the PC I've got Android Bootloader Interface with the yellow problem sign against it.
thanks for your help, it's appreciated, tried a few forums but no one is that interested in helping.
Cheers
Click to expand...
Click to collapse
It definitely sounds like the old usb brick problem, so that's a good thing! When you tried the commands were you booted into fastboot? When you connect the phone to the computer does the phone display change from saying fastboot to fastboot usb? I think thats what it should say, can't remember to be honest!
Have you tried another usb port, and a different cable too?
Edit: I'd also try rebooting the computer to ensure any running process etc are closed.
Got it fixed, final throw of the dice this morning I connected the phone to a Vista laptop and it was recognised straight away, so downloaded HTCSync then ADB tools on to the laptop and finally got the re enable command to work.
Jeez that took for ever, strange that Xp, Win7 and Linux PCs couldn't recognise the phone but Vista did.
Still got it sorted, thanks for the help.
No worries. Glad you got it sorted.
I have almost the same problem.
but with the legend.
SD is not recognized.
Can´t Call,
Can´t connect via USB.
Is there something I can do in the built in terminal in the ROM?
My computer recognized my phone in debugging mode before I rooted it. Now it doesn't recognize the phone. Any ideas?
I don't need them, but i've heard that sometimes drivers need to be reinstalled..
After install cwm 6, probably i got the wrong file or corrupt file then my phone cant boot to cwm mode, then i tried to flash with odin, it can boot to download mode but problem is PC through ODIN cant detect my phone, when i plug PC showed unknown device, i did install driver properly and its ok when i test it with other same galaxy W..
Now my phone cant start up, cant enter cwm, it can enter download mode but PC can detect the port..
need help guys thanks..
NOTE : PC can detect my phone when my phone is turn on but it just not work in download mode
If Im right understand, you plug phone to pc and open your device. Did you try opposite combination? I mean, first open your phone with download mode, then plug your device to pc. Maybe it works.
rawmad said:
After install cwm 6, probably i got the wrong file or corrupt file then my phone cant boot to cwm mode, then i tried to flash with odin, it can boot to download mode but problem is PC through ODIN cant detect my phone, when i plug PC showed unknown device, i did install driver properly and its ok when i test it with other same galaxy W..
Now my phone cant start up, cant enter cwm, it can enter download mode but PC can detect the port..
need help guys thanks..
NOTE : PC can detect my phone when my phone is turn on but it just not work in download mode
Click to expand...
Click to collapse
is samsung driver installed? boot ur phone to download mode first then connect to pc. do the manual download mode procedure.
dec0der said:
is samsung driver installed? boot ur phone to download mode first then connect to pc. do the manual download mode procedure.
Click to expand...
Click to collapse
Driver had been installed.. I have tried with with another galaxy w and its work.. Just for my device computer shows unknown device
Sent from my GT-I8150 using Tapatalk 2
i have the same problem
anyone help me..
"""""""""""""""""""""""""''Help Help Help Help"""""""""""""""""'''''''''’'''''
I am having Moto M XT1663 phone I bought was already boot unlocked so i decided to Install recovery and Root so that I can enjoy rooted things.
The problem is that the phone not detectable in Fastboot mode phone can only be detected in ADB mode. When I write command "ADB devices" it shows my device.
If I want to reboot into boat loader and use fastboot devices after hitting enter it shows nothing and no error appears.
I google about my phone's drivers that should be installed in order to use fastboot mode. So I installed them but no success.
One thing I notice that In fast boot mode my laptop giveys USB detection error and also tells me ADB interface failed.
Tried below mentioned things in order to get my phone detected in fastboot mode:
1) tried 3 different laptops(my Nexus 6p is detectable on all three laptops).
2) changed USB cable.
3) FDR using recovery.
EDIT: Problem solve by install Mediatek driver from windows update
Fastboot devices won't show anything etc..
I am trying to unlock the phone.
I don't have an OS etc. and also have formatted my PC, since the last time I was able to detect my phone on fastboot.
I have tried installing drivers on windows but it won't change anything (I have one more HTC M9 which will be detected by fastboot)
Doesn't get detected on ubuntu too...
i was able to find *hard* an OTA that works.
turned out to be a hardware issue.