Develop Bugs

Bricked - Can I save my phone??

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?

[Q] Help with ADB....Question

I am trying to get ADB to work so I can do the unlock bootloader. ADB recognizes my phone while booted up with usb debugging enabled, but when I reboot to fastboot, it does not recognize it.
I've tried different drivers, uninstalling and reinstalling.... no luck.....
Is there anyone that is knowledgeable in this area to assist me? Is there any kind of IRC channel available to get real-time answers?
Please help,
Thanks,
Bob

i am in the same boat. Using windows 7(64 bit). Cannot get the phone recognized in boot loader mode.

diablonyc2 said:
i am in the same boat. Using windows 7(64 bit). Cannot get the phone recognized in boot loader mode.
Click to expand...
Click to collapse
Yeah, im on 7 64 bit also..... i've tried disabling digital driver thing at bootup...
device manager see its just fine.... I can access it with adb while the phone is booted up.... as soon as I reboot to fastboot screen the phone cannot be seen by adb devices..... still shows up just fine with no ! in device manager....
... is there anyway to push a stock image and load a factory stock image from the stock recovery? says it needs to be in /cache folder.... i tried pushing a stock image there but it tells me access is denied.... i tried enabling root.... says root not available on production builds..... im lost....

I just tried it on my xp machine and it worked just fine..... weird.. something with 7 64 bit? i tried pda net drivers, samsung, samsung naked 1.7.... all said they were working fine....

adb is for android or recovery
fastboot is for bootloader
adb won't recognise the device when it's in fastboot mode.
Try:
Code:
fastboot devices
And you don't need adb to unlock the bootloader, the command is:
Code:
fastboot oem unlock
So not entirely sure why you're chasing adb...

I am in the same boat, what happens for me is that fastboot doesnt even recognize the device. So all in all I can't oem unlock my device.
Using win7 64bit

j1mmyg88 said:
I am in the same boat, what happens for me is that fastboot doesnt even recognize the device. So all in all I can't oem unlock my device.
Using win7 64bit
Click to expand...
Click to collapse
The usual recommendation (and what worked for me) is to install PDANet first, just for the drivers. Then fastboot will see your device. You can remove PDANet afterwards and the drivers will remain.

copkay said:
The usual recommendation (and what worked for me) is to install PDANet first, just for the drivers. Then fastboot will see your device. You can remove PDANet afterwards and the drivers will remain.
Click to expand...
Click to collapse
fyi - this is what I did, with 64 bit windows 7 - the driver install didn't complete 'til I actually connected the GN in fastboot mode, then win7 installed the driver and I was able to run fastboot successfully.

device not found

adb devices returns no listed devices,
One_X_All-In-One_Kit says device not found.
Tested with different drivers (HTC drivers from One_X_All-In-One_Kit,and Universal_Naked_Driver_0.72), phone is detected by Windows, in bootloader it says fastboot usb, but I can't do sh*t And it used to work just fine a month ago.
Tested on 2 different computers with different USB cables... (Win 7 and 8 run as admin).
One strange thing is that I remember updating TWRP to 2.6.0.0 and now it's 2.4.something. What happened, what can I do?
Just want to update boot.img so I can install CM10.2, currently on CM10.1.

No ideas?
I can connect adb over WiFi, but ofcourse it says offline.

USB debugging ticked?
A

Adb doesn't work in the bootloader. Only fastboot commands

Iceax123 said:
USB debugging ticked?
A
Click to expand...
Click to collapse
Yes, I did this a few times before, I know how to do it. But now, there is no way to flash boot.img from PC.
I reboot phone in to Bootloader, connect it to PC (phone says fastboot USB), I can see ADB device in device manager, if I 'adb device' in Command Prompt there are none (except when I connect it with WiFi adb).

kbal said:
Yes, I did this a few times before, I know how to do it. But now, there is no way to flash boot.img from PC.
I reboot phone in to Bootloader, connect it to PC (phone says fastboot USB), I can see ADB device in device manager, if I 'adb device' in Command Prompt there are none (except when I connect it with WiFi adb).
Click to expand...
Click to collapse
adb does not work in bootloader...
of that doesnt help, try another USB port... I know this sounds ridiculous but trust me, it helped me once before.

Well, i managed to get my phone be detected in adb and fastboot, by manually installing Nexus adb drivers (have a disk option).
Drivers that used to work- HTC drivers, won't do anymore. Don't know why.

[Q] ADB not recognizing device

I just bought a new computer yesterday, after installing the lightweight adb/fastboot program to my dell inspiron windows 8.1 laptop. I realized when I try to see the devices connected to adb by the command : adb devices, the only that pops up is list of devices attached, but show nothing. Here's the guide I followed http://forum.xda-developers.com/showthread.php?t=2778239
I'm guessing it has something to do with the drivers.....any help appreciated......
Here's the link I used to installed minimal adb and fastboot http://forum.xda-developers.com/showthread.php?t=2317790

Try uninstalling HTC Sync and any HTC drivers, then try to re-install, and see if that helps.
If no, uninstall any HTC software and drivers. Connect phone, go to Device Manager, and see if the device shows up. If so, select the option to manually select drivers (ignore any prompts to automatically install HTC Sync, etc.) and pick the Generic Android MTP drivers.
See if that works, although Win 8.1 has been known to be more problematic connecting to this device than previous Win builds.

Well I finally got it to work..I never installed the HTC sync software. I found a good link of compatible drivers for my 8.1. I didn't realize the phone had to be in bootloader mode to use fastboot commands though. That's a new thing forbme. If I remember correctly, I could use fastboot commands while the android was in its GUI/ROM format...

I've already switched cid yo gpe cod, but I'm probably going yo switch to dev edition

jxcorex28 said:
Well I finally got it to work..I never installed the HTC sync software. I found a good link of compatible drivers for my 8.1. I didn't realize the phone had to be in bootloader mode to use fastboot commands though. That's a new thing forbme. If I remember correctly, I could use fastboot commands while the android was in its GUI/ROM format...
Click to expand...
Click to collapse
Fastboot commands only work in fastboot mode. Its always been this way.
adb commands work in the OS or recovery, but not in bootloader or fastboot.

For some reason I was thinking the opposite...god, I'm retarded. I went ahead,and downloaded the entire SDK anyhow. Everything's up to speed

adb devices: no device found, why ?

Just a quick question.
Im unable to access fastboot or bootloader mode through adb command line.
I turned on usb debugging, connected phone to usb cable with my pc, run command line in platform-tools - adb devices and nothing happens.
I think i know the answer, but i want to be sure. Is it because i dont have unlocked bootloaded (OEM Unlock, still 6 days to wait)

Do you have the proper drivers? Try downloading the universal ADB drivers.
Sent from my Lenovo P2a42 using Tapatalk

Switch USB mode to PTP instead of MTP. I don't know why, but it works like that after Android KitKat/Lollipop release. Used this trick on LG G2 mini and now on my P2

I dont know if i have correct drivers, but i think so
https://dl.google.com/android/installer_r24.4.1-windows.exe
http://download.oracle.com/otn-pub/...m=1498221676_80503fd7b283f64cfa8ae7825b0021e2
My Xiaomi Redmi phopne is detected correctly, but its rooted and OEM unlocked
edit:
It's fine now. Its unbelivable what a mess is with adb files/usb drivers and similar. There is so much that can go wrong.
I wiped everything and installed minimal adb and fastboot + lenovo usb/mtp drivers
Now pc detects my phone.