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] Help needed w/ rooting

i got the samsung drivers, adb, fastboot,
but when i boot to bootloader (vol up+down +power) adb doesnt find any device. is that normal? fastboot oem unlock doesnt work, i presume b/c adb isnt recognizing my phone.
Some help please. Thanks

David 617 said:
i got the samsung drivers, adb, fastboot,
but when i boot to bootloader (vol up+down +power) adb doesnt find any device. is that normal? fastboot oem unlock doesnt work, i presume b/c adb isnt recognizing my phone.
Some help please. Thanks
Click to expand...
Click to collapse
ADB will not find the phone in bootloader mode. If you type fastboot devices, it should show your phone. Check device manager and see if you have an unrecognized device showing. If you do, try manually installing the drivers by clicking the update driver button under the unrecognized device's properties window.

try reinstalling the drivers...or you may need to use the google drivers in the sdk/adb package instead. Also when you plug the device into pc, go into device manager and see if shows up as android device. If it comes up unkown, then manually push the driver update.
^Ninja'd lol

fastboot devices comes up blank.
in device manager my phone comes up as other devices - android 1.0
i guess my driver is bad. where can i get a good one?
(i just installed the one from samsung.. same thing.)
what have you used

Make sure to download the software from sdk that is for the newest update of android. I think it is 4.0.3 there is like 5 things in that folder. You will need all of them, and after they download type "adb devices" in the command window and it should show the serial #.
Sent from my Galaxy Nexus using XDA App

Randroidran said:
Make sure to download the software from sdk that is for the newest update of android. I think it is 4.0.3 there is like 5 things in that folder. You will need all of them, and after they download type "adb devices" in the command window and it should show the serial #.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
did that. i dont have any issues untill i am in the bootloader. adb works fine before i reboot.

I'm assuming your driver is not loaded properly. Download this driver and unzip it. Install it by using the update driver wizard in device manager. I used this same driver on my work laptop (windows 7) and have had zero issues.

thx ill try now
.
.
.
works!
thx a million

Trying to unlock the bootloader

I get through all the steps, adb setup recognizes my device is connected. When i try to unlock the bootloader <fastboot oem unlock> command line locks up at <waiting for device>.
can someone advise?
Verizon if that matters

What happens when you type in "fastboot devices"

Nothing happens. Tried it both before and after typing in adb reboot bootloader

You sure your pc is detecting the phone when it is in fastboot mode? To me it seems like your computer isn't detecting the phone or the drivers didn't get installed properly.

<deleted>
answered my own question

I had the same issue. Assuming you're using Windows, you need to find where the latest Samsung drivers for the GN were copied to when you installed them (you have installed them, right?) The next time you plug in your phone, it will probably ask you to setup a new device. Tell it you will install the drivers from a location you choose, navigate to the folder where the drivers are, let it install them, restart if it asks, and then try the process over.
FWIW, I used the directions and links from this tutorial and eventually got it working. They include alternate drivers here in case the one from samsung.com doesn't work.

im having the SAME PROBLEM AND HAVE TRIED TWO DIFFERENT COMPUTERS.TRING ADB METHOD

What's the ADB method? Why don't you just just hold the volume up, volume down and power to get into fastboot mode? When you plug it in, windows should see a new device that needs drivers. You need to make sure the drivers are installed before fastboot will work.

i am in fastboot "little android with chest opened". and i do have the driver installed but in fastboot windows thinks its a different device

robitron929 said:
i am in fastboot "little android with chest opened". and i do have the driver installed but in fastboot windows thinks its a different device
Click to expand...
Click to collapse
Is it saying that it couldn't install the drivers for Android 1.0 or something like that? What step are you at? Which tutorial are you using?
Read the driver installation part of this tutorial.
http://forum.xda-developers.com/showthread.php?t=1392310

i got it. it was this
TO GET DRIVER WORKING IN BOOTLOADER YOU MIGHT HAVE TO DO THIS, THIS TOOK ME FOREVER TO FIND!!!!!!!!!!!
I TAKE NO CREDIT!
READ CAREFULLY
THANKS TO KELLEX FROM DROIDLIFE
Tips:
-We know that many of you are running into a “waiting for device” issue when apply the fastboot oem unlock command. This is a driver issue and one that a reader has a suggestion for:
1. Open device manager on your PC.
2. Right click on Android 1.0 with the yellow ! mark on it.
3. Choose update driver.
4. Choose browse my computer.
5. Choose Let me pick from a list.
6. Scroll down and find the Samsung driver with newest date. Should be the driver you downloaded above. (Possibly dated 11/25/2011 ).
7. It will give you a warning about installing the driver, just click yes.

[Q] Phone not being recognized by computer in bootloader?

So I've been trying to root/unlock my CDMA nexus and I'm having a very frustrating problem that's preventing me from doing it with any of the toolkits available OR the manual method. I have the android SDK installed, samsung's USB drivers, and everything else I've been told to get. I can detect my phone when it's connected (and USB debugging is on) using adb commands but ONLY when the phone is booted as normal. If I reboot into the bootloader, my computer no longer detects it, and I can no longer act upon it via adb. This, of course, is preventing me from getting anywhere on the unlocking/root front. Anyone have any ideas? I'm fresh out.

ADB doesn't work in boot loader/fastboot. Adb only works in recovery or when Android is fully running.
You need to use fastboot commands in bootloader/fastboot.
"Fastboot devices" to see if it's detected.
Sent from my Galaxy Nexus

have you installed the hboot drivers?

As above, you have to use fastboot commands when the phone is in bootloader. Try "Fastboot devices" to see if your computer sees the phone.

Fastboot commands don't detect the phone either. Fastboot is installed, as I can get it via command prompt to show available commands and whatnot, it just does not detect a device to work on.

I am also having this exact problem when i try to install the new touch cwm beta that was just released. Its not detecting the device while in the bootloader, and when i try to fastboot flash recovery it just says <waiting for device> and does nothing.

I know this is a little late, but I figured I’d post here to help anyone else out that is having this problem. I was trying to update my Galaxy Nexus from 4.0.2 to 4.0.4 using fastboot when I ran into the problem you’re having. I did this from a Windows 7 machine, and the fix for me was as follows:
1. After booting into the bootloader and having your phone plugged into your computer, open Computer Management.
2. Under Device Manager, in Computer Management, you should see a listing for a device called “Android 1.0” and it’ll have the little yellow triangle with the exclamation point on it.
3. Right click on the Android 1.0 device and select “Update Driver Software…”
4. Click “Browse my computer for driver software”
5. Click “Let me pick from a list of device drivers on my computer”
6. If you installed the Samsung drivers for the phone, scroll down until you see a device listed as “SAMSUNG Android Phone”
7. Select it and click next
8. It should auto populate the driver information. Click next and it will install the device
9. Go back to your CMD prompt and fastboot devices should now list the phone.
Hope this helps!

Quicks man your the best!

...or use Linux #trolling
Sent from my Galaxy Nexus using xda app-developers app

[HELP] MI a2 lite Fastboot Exits aAutomatically

I have a mi a2 lite and i want to unlock its bootloader, i have alrready enabled oem unlocking on developer options, when i boot my device in fastboot and connect to computer, command window says waiting for device and after 15-20 seconds of connecting my device to my pc, fastboot mode automatically exits and shows charging animation. Please anyone can help?
My device is in andoid pie (stable).

Check if you have installed drivers and run "fastboot devices" to see if device is recognised.

Agree something with your PC.
Phone will automatically exit fastboot if no connection in timely manner.
Check drivers are installed, reboot your PC.
Also be sure USB debugging is on in Dev option and trust PC.
For me, I generally boot Android normal. Then plug into PC and from command line, "adb reboot bootloader". That should verify adb, If that doesn't work, your PC not talking to device.

hossman said:
Agree something with your PC.
Phone will automatically exit fastboot if no connection in timely manner.
Check drivers are installed, reboot your PC.
Also be sure USB debugging is on in Dev option and trust PC.
For me, I generally boot Android normal. Then plug into PC and from command line, "adb reboot bootloader". That should verify adb, If that doesn't work, your PC not talking to device.
Click to expand...
Click to collapse
I reinstalled the drivers and the command "adb reboot bootloader" works for me that means it boots to fastboot mode but when in fastboot mode, when i enter a command "fastboot devices" it does nothing and when i enter command "fastboot oem unlock" it again says waiting for any device.
i have attached a screenshot of it.

I've tried restarting my pc as well as my phone and after 5-6 attempts it is now unlocked.
Thanks guys for supporting and giving response to my post
Love ya'll

CherryFarmer8 said:
I reinstalled the drivers and the command "adb reboot bootloader" works for me that means it boots to fastboot mode but when in fastboot mode, when i enter a command "fastboot devices" it does nothing and when i enter command "fastboot oem unlock" it again says waiting for any device.
i have attached a screenshot of it.
Click to expand...
Click to collapse
same problem boss, did you already solved this? please help me out

Andrew.kathy said:
same problem boss, did you already solved this? please help me out
Click to expand...
Click to collapse
The solution for fastboot disconnecting after a few seconds are the windows drivers. There are different drivers for our phone, normal, bootloader and fastboot. Windows loads these drivers depending in which state the phone is.
If you still didn't find the correct drivers, you should try installing MiFlash, as it contains all the needed drivers for our phone
If you like to try the Linux way, there's a distro called FWUL linux here on XDA

capajga said:
The solution for fastboot disconnecting after a few seconds are the windows drivers. There are different drivers for our phone, normal, bootloader and fastboot. Windows loads these drivers depending in which state the phone is.
If you still didn't find the correct drivers, you should try installing MiFlash, as it contains all the needed drivers for our phone
If you like to try the Linux way, there's a distro called FWUL linux here on XDA
Click to expand...
Click to collapse
Yeah, just go to windows drivers, click update device driver, browse my computer, let me pick, choose android > next > and choose another version or try whatever you feel is appropriate

CherryFarmer8 said:
Yeah, just go to windows drivers, click update device driver, browse my computer, let me pick, choose android > next > and choose another version or try whatever you feel is appropriate
Click to expand...
Click to collapse
I also have this problem drivers are installed and fine but when I go to fastboot within like 15 sec it automatically turns off.

I fixed it with this https://forum.xda-developers.com/attachments/howto_driver-zip.2480396/