Develop Bugs

Desire isn't being recognized by HTC Sync after update

Afternoon all,
I debranded my desire using an RUU flashing it to 1.15.405.4 but now HTC Sync isn't recognizing the phone, it is just coming up as 'Disconnected' yet it is still being recognized as a removable disk when in disk drive mode so it can't be a USB brick.
I can't get ADB working either since the phone isn't being recognized so it isn't installing the required ADB drivers for the phone. I can't go back to my stock firmware either because USB Debugging has to be installed correctly for the RUU to run. I had no problems initially, but after upgrading to this ROM I have seemed to have this problems.
I want to root, but if I can't have access to the ADB a root would not be possible? Please correct me if I'm wrong.
If anyone has any advice I would be glad to hear it. Thanks

I have the same problem with HTC Sync - just can't get it to see the phone. Hopwever to get ADB working make sure you have USB Debugging turned on in the settings under Applications / Development / USB Debugging.

sbdags said:
I have the same problem with HTC Sync - just can't get it to see the phone. Hopwever to get ADB working make sure you have USB Debugging turned on in the settings under Applications / Development / USB Debugging.
Click to expand...
Click to collapse
Thanks for the reply.
I have USB Debugging turned on in the menu, but it seems to not be recognized. I have done all the command prompts in cmd, but it doesn't list the device under ADB devices. Hmm.. :/

I had the same problem after all my updates, that worked for me, restart your pc and restart the phone, leave it plugged in by usb, it worked every time for me, hope that will help.

I restarted my computer then phone - leaving the USB plugged in, but it's still not being recognized. Am I doing the steps the wrong way round?
It's annoying because this is stopping me from rooting at the moment and I really want to get my hands on froyo!
Thanks

I'm not to sure I'm a newbie to all this, what I did was tun the phone and pc off, turn the phone back on first then turn the pc on as soon as the pc detects the phone put the phone on sync, and so far it always worked for me after a update, maybe you have a different problem maybe a proper dev can help you out.

fredhd said:
I'm not to sure I'm a newbie to all this, what I did was tun the phone and pc off, turn the phone back on first then turn the pc on as soon as the pc detects the phone put the phone on sync, and so far it always worked for me after a update, maybe you have a different problem maybe a proper dev can help you out.
Click to expand...
Click to collapse
Tried the above a couple of times, no luck. Thanks for the help though.
Hope someone knows a fix cause I'm eager to root my phone and get onto some froyo goodness! haha
Cheers

The HTC drivers are pretty damn bad with regards to Sync. I always do adb-related work in recovery for that very reason - I can almost never get Sync working.
Can you get adb working in recovery?

Ok here is what worked for me
1- Uninstall the HTC sync and the HTC drivers
2- open MSConfig and disable all non microsoft services
3- restart windows
4- install HTC sync
5- Connect the phone and it will connect
6- re enable the disabled services and restart Windows

Does it work normally every time after that, or do you have to go through that jazz every time?
Hopefully it works every time - I'll give that a shot if so.

Hi,
The ADB isn't being found in Command prompt it outputs 'list of devices' but there is no device listed. All drivers are installed as well.
I will try the above and see if that helps.
Cheers

Hi Matey, I had this exact same problem after rooting my desire last night - basically check task manager for any adb processes and kill em, if that still doesn't work re-run the htc sync install and select repair and it'll be ok again.
I had to do this on my home laptop which I used for the root, but also on my works laptop even though this was turned off and not used for rooting at all so think it's an issue with htc sync not seeing the same phone, but at the same time seeing the same phone and getting confused.....
so - reinstall using repair and reboot and all should be well matey...

Thanks for the help guys.
I had to reinstall Windows for other reasons, and after I reinstalled HTC Sync it still wouldn't recognize the phone but ADB is working so I can do all the shell commands.
Cheers for all the help.

I take my above post back. The phone is now not being recognized by ADB, it seems to have occurred after I have turned my computer back on. Windows installed some updates and I'm wondering whether they might have had an affect.
Anyone had any experiences in the same sense?

ADB: Device Offline

Okay, so here's my story. I have an HTC Desire. Bought it two days ago.
I've flashed and rooted with unrEVOked 3.32, then installed this ROM: http://forum.xda-developers.com/showthread.php?t=773997 (The stock ROM with radio)
It was working wonderfully, then I figured hey, why not install HTC's available update. So I did.
It installed, and now does nothing but reboot. I've tried to re-recover from the (now 3e) menu, but keep getting signature verification failures.
I've tried to create a GoldCard, got a spare 1GB MicroSD card that I'm using, but when trying to use ADB, I get a 'device offline' error, and therefore can't create a GoldCard. I have USB drivers installed from HTC Sync, and they worked fine for the flashing process itself. USB development was enabled the last time my phone booted, but I'm not sure whether that counts when I can't boot it.
I'm busy downloading and am going to reinstall HTC Sync for drivers, but have also tried the drivers included as a package in Android's SDK.
I've tried switching MicroUSB cables (although I only have 2 at the moment - HTC and SonyEricsson) with no luck, after reading stuff about some manufacturers' cables not playing well with ADB. Still get a device offline error.
I've got all I need to make a GoldCard, but ADB just won't work. I've also tried disabling firewalls/antivirus, to no avail.
Help?

Checkout this thread it has some good info
http://forum.xda-developers.com/showthread.php?t=831734
To make gold card use the gold card tool. If you can't find it here on XDA then PM me your email.
Sent with HTC Desire

When it said that my device was offline, I installed the Hboot drivers from unrEVoked and updated the SDK as well (might of used the SDK drivers instead) and it got sorted out.

fastboot/boot loader problem

hi,first post on this section . upgraded from the desire bravo,could do with some advice..
purchased a used dhd in good condition,changed housings etc,its running the latest htc 3.12.405.1 sense 3.0 android 2.3.5 .after a good search i realised i would have to downgrade to s-off etc.
my problem is i can't get into fast boot power down volume,pulled battery tried lots of times.
pc will not recognise dhd,installed drivers etc,should be able to sort that one out myself.
but i cant work out why i cant get into fastboot,the phone just restarts
thanks mark

Hi,
Download HTC Sync and install that, that contains all the required USB drivers needed.
As for getting into fastboot, have you disabled HTC "Fastboot"? Its in a setting somewhere. Possibly under Settings>Applications or Settings>Development. Make sure that is unticked.
If you take your battery out & reinsert, hold vol down then press power. That should do it for you. If not, enable USB Debugging and use adb to get into the bootloader with,
Code:
adb reboot bootloader
You will need the SDK or a thinned down adb package. Which you can grab from HERE.
You will need the USB drivers for that to work.
EDIT: Just re-read your post. If you have HTC Sync installed and you still cannot get it detected then there maybe an issue with either the handset or your computer. Check "Device Manager" when its plugged in to see if there is a conflict.

htc sinc was allready on pc from desire bravo,well just the drivers.have tried the htc fastboot uncheck earlier no good,re installed htc sinc as i thought it may be different for dhd,but its not.
pc will not pick up device,says drivers not installed.i know they are as the bravo worked fine.
i had read somewhere that unrooted dhd can be usb bricked,there is a fix by some french chap on here,but i cant do that because cant get into fastboot.
need to get into fastboot first i think,to see whats what,device could allready be s-off dont know.
strange
edit: volume button was not working correctly lol, s-on,now to sort out the drivers,downgrade and flash a nice rom

Device not detected in ADB, unable to boot into recovery

Hey guys,
So, I tried to turn my T-Mobile into a GPE. Everything went OK, pushed the RUU - and it hanged for a long time, so I quit out. Tried pushing it again, ADB not detecting the phone anymore - reinstalled drivers, rebooted everything - phone detected on pc as "My HTC", still no device detected in ADB. Rebooting the phone leads to the white HTC screen, booting into bootloader works but it's black for some reason, and I'm unable to boot into recovery - The OS text is red and reads "OS-3.32.531.2 (2.12.1700.1)". I've been trying to look for a solution for the past couple of hours but all the solutions require ADB to work, and all the solutions to get ADB to work are not solving it, so at this point I'm kinda stuck.
Any and all help would be appreciated greatly.
Thanks in advance!

I don't know if there's a t-mobile ruu available but if so, you can try and run that. I would simulate the battery pull first and then see if it recognizes it. From what you described for your os, mine would show that during the process of upgrading firmware

There is a T-mobile ruu in T-mobile one m8 general

Is it possible to run an RUU when the PC doesn't recognize the device properly?

Salabrin said:
Is it possible to run an RUU when the PC doesn't recognize the device properly?
Click to expand...
Click to collapse
Nope. It uses adb/fastboot.
Try uninstalling all HTC Sync and HTC drivers. Then plug the phone, go to Device Manager, find the device and select the option to manually select a driver, then pick Generic MTP Android Device (or something like that).
Also, bootloader screen on GPE is supposed to be black.

So I ran an RUU, it gives me an image error - I changed the CID earlier to install GPE, is that what might be causing the issue? If so, is there a way to change the CID without adb(Still can't get it to detect the phone)?

[Q] Driver problems

I have an HTC One M8 by T-Mobile, running the latest firmware, unlocked, rooted and on Android 5.0 Lollipop with the stock recovery. (I put the stock recovery back on because I had no need for the custom at the time and charging would bring me through the recovery and be real annoying).
I had no problem doing all of this but now (a few weeks later) I need to get the custom recovery back on in order to flash a new ROM.
Problem is, I'm connecting my phone to my computer and I can't get ADB to connect, HTC Sync Manager shows there's no device connected and windows explorer only shows a new CD Drive connected and mounted on (F that doesn't work and does not act as a storage platform for my phone.
What I have tried:
Disabling USB Debugging
Restarting Phone
Re-enabling USB Debugging
Un-installing HTC Sync Manager
Force installing "androidusb.INF"
uninstalling HTC Sync Manager, unplugging phone, disabling usb debugging, turning off phone and then going back through again, installing, plugging in turning on and enabling.
Really puzzled here, need to connect to ADB to flash custom recovery to go back to my stock ROM.

Try using the generic Android MTP drivers in Device manager. Of course you could also check all the basics as well.
Try a different port or a different cable. Try to kill the adb server and restart it. Can also try revoking the USB permissions and accepting again when prompted on the device.
Though you don't really need adb to flash the recovery, it needs to work in Fastboot mode. ADB will only work in a running OS or in a recovery, fastboot of course from fastboot mode, which is what you'll need in order to flash the recovery. You won't need USB debugging enabled for it either.
Try some of the stuff above, especially if maybe it's a cable or port issue.

I realize you may find a solution before even considering the option below ⬇
http://forum.xda-developers.com/showthread.php?t=2965030
If you have an extra rooted device and get the cable coming you will never have to worry about troubleshooting drivers again considering after an ruu or a conversion you will go through the possible issues of drivers more than once
I've changed my CID,MID,flashed recovery with this method.
Being S-OFF I've not needed to try an ruu through ruu mode but would guarantee it will do the job