• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help [Solved] usb-bricked

yodude01

Newbie
hello guys,

i've usb bricked my htc desire s. how can i fix it? i have desire s with android v2.3.5 and sense 3.0.

thank you
 
Is it totally bricked, i.e. no power connection and no data connection? If so, it's probably best to send it in to be repaired.

If you get a power connection (via the mains and or PC), make sure you have the HTC device drivers installed on your computer. If you do, first uninstall, then reinstall them on your PC, just in case they've become corrupted. Also, if you haven't already, try connecting with a different USB cable.

Unless you're happy to have a go using adb (Android Debug Bridge) and Fastboot, you'll find first trying a factory reset and then, if that doesn't work, sending it back to your network provider or HTC to be the quickest way to fix it.

adb and Fastboot involve downloading software to your PC, then running commands from your PC to your phone via the USB. When people report bricked USBs, it's often the case that not all the USB connectivity is bricked, which is why sometimes these things can be fixed with adb. However, if your USB is totally bricked, then adb/Fastboot won't work.

If you choose to go the adb/Fastboot route, either continue in this thread or over at xda-developers.com. Keep in mind that it's possible to brick your phone with adb if you enter the wrong commands or make a typo, which may invalidate your warranty. Only use such tools if and when you're confident to do so.
 
Is it totally bricked, i.e. no power connection and no data connection? If so, it's probably best to send it in to be repaired.
No it's not. I can charge through laptop or ac power but the usb icon and the connect to pc menu dosen't appear.

If you get a power connection (via the mains and or PC), make sure you have the HTC device drivers installed on your computer. If you do, first uninstall, then reinstall them on your PC, just in case they've become corrupted. Also, if you haven't already, try connecting with a different USB cable.
Tried other computers. I've ordered an oem cable from ebay, will see if that makes any difference. previously i was using nokia cable to connect to pc.

Unless you're happy to have a go using adb (Android Debug Bridge) and Fastboot, you'll find first trying a factory reset and then, if that doesn't work, sending it back to your network provider or HTC to be the quickest way to fix it.

adb and Fastboot involve downloading software to your PC, then running commands from your PC to your phone via the USB. When people report bricked USBs, it's often the case that not all the USB connectivity is bricked, which is why sometimes these things can be fixed with adb. However, if your USB is totally bricked, then adb/Fastboot won't work.

If you choose to go the adb/Fastboot route, either continue in this thread or over at xda-developers.com. Keep in mind that it's possible to brick your phone with adb if you enter the wrong commands or make a typo, which may invalidate your warranty. Only use such tools if and when you're confident to do so.
The phone is not under warranty. I don't want to get into risk of bricking the phone but is it safe to follow the procedure and by not making any typos fixing the problem? If so, could you please guide me on how to do it? i'll be trying this method after that cable doesn't work. I've tried many nokia and other cables but all don't seem to work.

And thanks for detailed reply.
 
From the symptoms you describe your phone could be fixed, although it's by no means guaranteed. But, if you're happy trying adb/Fastboot, then it's worth a shot. You'll soon know one way or the other.

If it doesn't work, the other thing people have tried is to flash an RUU (a different or same ROM over the existing one.)

My knowledge of adb/Fastboot is pretty limited, but there are only two commands to use in trying to fix the 'bricked USB' problem, which are straightforward.

To download the software you need, follow this link and read the instructions there.

Once installed and connected to your phone, the commands you need are:

fastboot oem enableqxdm 0

fastboot oem eraseconfig


The first frees up the SD card; the second will reset the 'misc partition'.

As always when doing these kind of things, ensure you have backed-up what you need on your phone.
 
From the symptoms you describe your phone could be fixed, although it's by no means guaranteed. But, if you're happy trying adb/Fastboot, then it's worth a shot. You'll soon know one way or the other.

If it doesn't work, the other thing people have tried is to flash an RUU (a different or same ROM over the existing one.)

My knowledge of adb/Fastboot is pretty limited, but there are only two commands to use in trying to fix the 'bricked USB' problem, which are straightforward.

To download the software you need, follow this link and read the instructions there.

Once installed and connected to your phone, the commands you need are:

fastboot oem enableqxdm 0

fastboot oem eraseconfig


The first frees up the SD card; the second will reset the 'misc partition'.

As always when doing these kind of things, ensure you have backed-up what you need on your phone.

well thanks i'll surely try this. But I've a question, I've seen this command for usb-bricked simple htc desire, do you think it will work on my Desire S as well?
 
It's an Android command, so it will work on all Android phones.

However, it may not solve your USB problem, which is why some people then resort to flashing a ROM with an RUU.exe to fix things.
 
It's an Android command, so it will work on all Android phones.

However, it may not solve your USB problem, which is why some people then resort to flashing a ROM with an RUU.exe to fix things.

Thanks. I've tried the commands. The first one worked fine but the second one gave an error
Code:
... INFO[ERR] Command error !!!

It didn't solve the problem :( is it because my phone is not rooted? does this command work on s-on unrooted phone?
 
Yes, very likely because your phone is S-Off. (I thought it might be as your phone isn't under warranty.)

You could try using the Bootloader Unlocker at HTCDev.com to access the system. It won't make your phone 100% S-Off, but it will unlock the recovery, boot and system, meaning the second Fastboot command should then work. If it doesn't, you then have the option to try flashing a ROM, although you should install a recovery mod and root your phone first. (Read all the info on the HTCDev site before unlocking.)

Alternatively, you could try flashing an RUU, instead of using the Bootloader Unlocker.

(Or send it in for repair.)
 
Yes, very likely because your phone is S-Off. (I thought it might be as your phone isn't under warranty.)

You could try using the Bootloader Unlocker at HTCDev.com to access the system. It won't make your phone 100% S-Off, but it will unlock the recovery, boot and system, meaning the second Fastboot command should then work. If it doesn't, you then have the option to try flashing a ROM, although you should install a recovery mod and root your phone first. (Read all the info on the HTCDev site before unlocking.)

Alternatively, you could try flashing an RUU, instead of using the Bootloader Unlocker.

(Or send it in for repair.)

my phone's not in their list. Will try ruu method someday. Thanks.
 
The Unlocker works with the Desire S on 2.* software versions. I know there's no mention of it on the website, but many people, including myself, have used it to unlock version 2.* stock and branded ROMs. See this forum and the Desire S section on xda-developers.com for many examples.

(The copy under 'Supported Devices' doesn't make much sense, anyway. It states the 'following devices', which all appear in green, are supported. It then states all those listed in green, which is every phone on that list, are unlockable!)
 
Voila!!

Problem Solved. As the bootloader unlocked and the phone restarted, the usb icon appeared again :) and on android 2.3.5 it's more cool :-)

Thank you so much for your help.

Bootloader unlock thing worked for me. Should i re-lock the bootloader again as it is mentioned on htcdev site?
 
Assuming all is well and you're content with the software you have, and don't want to try custom ROMs, or apps that require root, then you could lock it again. Your phone will also be more secure, although having an anti-virus/malware app should cover things there.

HTC do warn about FOTAs while unlocked - the general rule is not to accept any when your phone is S-Off. So, if you do keep it unlocked, remember that advice.

Thanks for the report. I wonder if it was the 'fastboot' command that was waiting in a queue that fixed things as soon as it could access the system, or if it was solely down to the unlock? Anyway, congrats on fixing your USB-brick problem!
 
Assuming all is well and you're content with the software you have, and don't want to try custom ROMs, or apps that require root, then you could lock it again. Your phone will also be more secure, although having an anti-virus/malware app should cover things there.

HTC do warn about FOTAs while unlocked - the general rule is not to accept any when your phone is S-Off. So, if you do keep it unlocked, remember that advice.

Thanks for the report. I wonder if it was the 'fastboot' command that was waiting in a queue that fixed things as soon as it could access the system, or if it was solely down to the unlock? Anyway, congrats on fixing your USB-brick problem!

Well. After a day. I see sometimes the usb icon appears and disappears. I think it's because of the cable. Anyways, thanks. Does that mean i cannot update ota anymore? And could you please tell if its possible to root v2.3.5? Also the second command eraseconfig one still doesnt work even though thr phone shows unlocked and s-off. What could be the thing?
 
HTC seem to be saying that having unlocked the bootloader with their tool, it is possible to update with OTAs, but they cannot guarantee that in an unlocked state this may cause problems.

It is possible to root 2.3.5. You can do this with SuperOneClick or similar. Or flash SuperUser zip from recovery.

As to why the second command doesn't work, I have no idea. It won't work in every case of their being a bricked USB. Bricked USB symptoms may be similar, but there could be several different causes.
 
Back
Top Bottom