Related
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?
I just unrooted and installed the leaked radio update so i would have less bugs with the froyo ROMS.
I installed the radio perfectly fine, but now unrevoked isn't working for me.
I deleted all of the previous files and reinstalled them (sdk folder, usb drivers, reflash)
when i run the reflash tool, it gets stuck after rebooting, says "waiting for reboot..."
any help or ideas?
EDIT: as the phone rebooted, it changed to "Flashing recovery image. Do not touch your phone!" but instead of going into recovery, it just continued to restart the phone as usual
What exactly did you do to make yr phone reboot? Manually power cycle? Battery pull?
IIRC, something very similar happened to me with unrev 3.0. I was sure I had the google sdk drivers on my xp box, so I just plugged 'er in and ran the rooting tool. Later I found out the htc drivers were there the whole time, which as we all know interferes with rooting.
So the first thing would be to double-check your drivers, eliminate other USB devices from the setup, disable doubletwist or other apps that talk to the phone.
I did get rooted with the wrong driver in place, but I had to help the process along at one point. I believe I did that by opening a dos box and doing 'adb reboot recovery' from \sdk\tools when the unrevoked script appeared to be stuck waiting for a reboot.
You do have to make sure it reboots to recovery, not normal OS, as recovery boot sequence is where the root exploit takes place...
Do you have HTC Sync installed on your computer? Remove it if so.
cantare said:
What exactly did you do to make yr phone reboot? Manually power cycle? Battery pull?
IIRC, something very similar happened to me with unrev 3.0. I was sure I had the google sdk drivers on my xp box, so I just plugged 'er in and ran the rooting tool. Later I found out the htc drivers were there the whole time, which as we all know interferes with rooting.
So the first thing would be to double-check your drivers, eliminate other USB devices from the setup, disable doubletwist or other apps that talk to the phone.
I did get rooted with the wrong driver in place, but I had to help the process along at one point. I believe I did that by opening a dos box and doing 'adb reboot recovery' from \sdk\tools when the unrevoked script appeared to be stuck waiting for a reboot.
You do have to make sure it reboots to recovery, not normal OS, as recovery boot sequence is where the root exploit takes place...
Click to expand...
Click to collapse
i didn't do anything to get it to reboot, the reflash tool rebooted the phone for me.
i'm 99% sure all other drivers are gone and only the google ones are there. I checked under device manager, but maybe i missed it? is there some secret spot they hide in? (thats not sarcasm btw lol)
I'm gonna try rebooting the phone from a dos box. when typing the commands.....
1-cd\sdk\tool
2-adb reboot recovery??
just wanna make sure.
thanks for your help too
douger1957 said:
Do you have HTC Sync installed on your computer? Remove it if so.
Click to expand...
Click to collapse
nope, i got rid of it as far as i know
Make sure you delete the RUU file on the SD card. Something like pb456img (can't remember the exact file name, and tapatalk search sucks).
Also, make sure you turn usb debugging back on as ruu turns it off I believe.
Sent from Incredible using Tapatalk.
got it! i did it all on another computer from scratch and it worked!
thanks for all of your help
JWorth said:
got it! i did it all on another computer from scratch and it worked!
thanks for all of your help
Click to expand...
Click to collapse
ya i had the same problem, tried unrevoked from a new machine, it worked. must have been old drivers or possibly some sync software. didnt' spend enough time to narrow it down because honestly, once I got re-root, who cares?!
glad you got it rooted!
a couple notes for anyone reading: first, unrevoked has its own set of modified drivers for their root tool... not the same as stock google sdk drivers, at least where the Bootloader ADB driver is concerned.
JWorth said:
i'm 99% sure all other drivers are gone and only the google ones are there. I checked under device manager, but maybe i missed it? is there some secret spot they hide in? (thats not sarcasm btw lol)
Click to expand...
Click to collapse
for future reference, getting rid of drivers in windows can involve a bit of blind faith (unless you know the registry etc. like the back of your hand). Often Windows will auto-install a driver you don't want if you let it do the 'automatic' wizard thing.
if you have a restore point from before any drivers were loaded, it's simplest to use that provided it doesn't screw up other things.
or you can use the uninstaller tool that came with the old drivers, and then the installer that comes with the new ones, and pray it worked.
ultimately, if there are still problems, best practice is to run device manager, turn on the "view->show hidden devices" option, plug in the device if it's removable, and then right-click & uninstall ALL related device entries. For the DInc that would include entries under Android-anything, HTC-anything, possible entries under Modems and Other/Unknown.
Then reboot, run whatever driver installer package you have, plug in the device again, and check that nothing fell under Other/Unknown Devices. If there are such entries in dev mgr, right-click each one to "update driver", then browse to the proper .inf file in your driver package folder. If Windows ever pops up the Driver Install Wizard, you choose the manual options (don't search/not this time/choose from list/Have Disk...) and navigate to the appropriate .inf.
Hi guys!
Today I tried to get the rooted desire with Android 2.2 with unrevoked 3.21
Previosly I updated to 2.29.405.2 SW
When I run the unrevoked it (desire) freezed on "waiting for root" step. Desire freezed in boot progress (white screen with HTC logo on it)
I removed battery and inserted it again. But I cant boot it, desire freezes on the same white screen with HTC logo.
I can HBOOT, but when I go to recovery menu my device goes to reboot and freez.
So it seems that unrevoked spoiled my recovery and I do not know hot to fix it.
Please guide me, the working solution will be donated $20
--------------
Radio version: 5.11.05.27.
SPL/hboot version: 0.93.0001.
product: bravo.
mid: pb9920000.
security: on.
build-mode: ship.
Device model is not SAPPHIRE - flash old/new disabled.
This device does not have s-off nor eng hboot.
-------------
Thanks!
Flash a stock RUU and try again, you can get 2.29.405.2 from my signature. Remember to use a gold card if you had to in the past
How can I flash the RUU without access to recovery?
You should flash it via fastboot.
Hold the back button and turn on your phone to enter FASTBOOT, then connect your phone to the pc with the usb cable and then run the ruu.
3722 said:
You should flash it via fastboot.
Hold the back button and turn on your phone to enter FASTBOOT, then connect your phone to the pc with the usb cable and then run the ruu.
Click to expand...
Click to collapse
Did it as you said, result is the same
After the successful flash procedure thru RUU device went to reboot and freezed at the same white screen state.
Recovery is still unavailable to get into.
Now I will try to get the logged data thru Android SDK.
This thing is really mess me up =( I'm phoneless.
You, guys, are the one and only hope.
I have installed SDK, but I cant see anything in adb logcat but "waiting for device", thogh my device is conneted via fastboot usb.
Any clue?
I had that same issue, and it turns out it was a problem with the earlier version of clockworkmod (2.5.0.1) that had that issue, where freezing occurred at the HTC splash screen.
Try unrevoked again, with the 2.5.0.7 image here:
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.7-bravo.img
Make sure you select the image when you start unrevoked.
It might fail a few times (freezing at splash), but if it does, just pull the battery and keep trying....eventually it'll manage to go through.
Good luck =)
Latty said:
I had that same issue, and it turns out it was a problem with the earlier version of clockworkmod (2.5.0.1) that had that issue, where freezing occurred at the HTC splash screen.
Try unrevoked again, with the 2.5.0.7 image here:
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.7-bravo.img
Make sure you select the image when you start unrevoked.
It might fail a few times (freezing at splash), but if it does, just pull the battery and keep trying....eventually it'll manage to go through.
Good luck =)
Click to expand...
Click to collapse
Latty, how can I run unrevoked with a desired image if I cant boot the phone to get it recognized by unrevoked?
you have to start the flasher without the phone being connected, then you should be able to select the image (top left of window).
waebi said:
you have to start the flasher without the phone being connected, then you should be able to select the image (top left of window).
Click to expand...
Click to collapse
yes found it, but when I connect my phone via Hboot usb or fastboot usb - unrevoked does not recognize the connected device.
hellt said:
yes found it, but when I connect my phone via Hboot usb or fastboot usb - unrevoked does not recognize the connected device.
Click to expand...
Click to collapse
Follow the unrevoked guide to install the drivers. Also uninstall HTC drivers before that.
droidzone said:
Follow the unrevoked guide to install the drivers. Also uninstall HTC drivers before that.
Click to expand...
Click to collapse
Already done it. Installed drivers from unrevoked package. But still my phone doesnt get recognized by unrevoked.
hellt said:
Already done it. Installed drivers from unrevoked package. But still my phone doesnt get recognized by unrevoked.
Click to expand...
Click to collapse
It still is a driver issue.
Start from scratch..
Remove all HTC Drivers
Reboot
DC from internet
Connect phone in two modes-Android, Fastboot
It should get recognized but drivers shouldnt be installed and you should be prompted for driver location. If you arent prompted, get Device Manager, uninstall the driver which recognized the device.
Now install Unrevoked drivers as per guide.
Phone should be recognized..
droidzone said:
It still is a driver issue.
Start from scratch..
Remove all HTC Drivers
Reboot
DC from internet
Connect phone in two modes-Android, Fastboot
It should get recognized but drivers shouldnt be installed and you should be prompted for driver location. If you arent prompted, get Device Manager, uninstall the driver which recognized the device.
Now install Unrevoked drivers as per guide.
Phone should be recognized..
Click to expand...
Click to collapse
Ok, thanks will do it now.
But one more question, should it be recognized from hboot usb mode with "Android Bootloader interface" driver, or from fastboot mode?
Cant confirm that without my phone..
But, I believe drivers would recognize it in both..And seperate drivers too..
A small tip..If you have dual boot, try Unrevoked in another OS in which you havent installed HTC. Should work
droidzone said:
Cant confirm that without my phone..
But, I believe drivers would recognize it in both..And seperate drivers too..
A small tip..If you have dual boot, try Unrevoked in another OS in which you havent installed HTC. Should work
Click to expand...
Click to collapse
Faced with problems
1) I uninstalled HTC Drivers.
2) plugged phone and deleted Bootloader interface device then Boot Interface device.
3) rebooted
4) disconnected from internet
5) plugged and powered device and got Bootloader Interface driver installed without a single promt!!! And Boot interface as well.
So I had no chance to manually set the path to the drivers. And unrevoked still doesnt see the device =(
It turns out that I should try another OS???
PS and the key point, should it be recognized in hboot mode or unrevoked only works with booted to OS devices only?
Not really..But that's the easy way out..
Difficult to show you what exactly to delete..
Mostly these are driver clashes..When you uninstall the driver you should tick the option to delete the driver from system.
Try again and you know you've succeeded when it doesnt find any driver installed, and asks you for the location, when you can choose the unrevoked drivers..
Hm, I cant find any options prompting to delete driver from the system... But I will look into more carefully.
ADDED
Found it, trying now.
Tried, was promted to specify the path to the drivers, installed again and with no luck =( Unrevoked doesnt see the device.
I will try it tomorrow on another PC and with another OS.
Thanks for help, I really appreciate this, and I hope we will find a solution.
PS. Is this problem called USB brick?
I just purchased an HTC M8 running software number 1.55.631.4 and I am using Windows 7.
- I first tried plugging in the phone via usb, and Windows notified that the driver install failed.
- Then I tried installing the drivers manually using the All in one toolkit, tried plugging in the phone, and nothing happened.
- Then I uninstalled the driver, and tried installing the HTC Sync Manager (driver included), plugged in the phone, and still nothing happened.
- This problem occurred on an HP EliteBook, so I tried on another HP laptop I have at work, and the driver install failed when I plugged it in as well.
- Now I am here.
Does anyone have any possible ideas/solutions? Any feedback is appreciated.
bump
Install HTC Sync Manager, then uninstall it but leave the drivers. Should then work fine
http://www.htc.com/uk/support/software/htc-sync-manager.aspx
I'm running into the same problem. Have just unlocked bootloader and rooted the phone. I now want to achieve S-OFF. However when I get to the ADB push command nothing happens. I notice the error "HTC MTP Device - Failed" when it tries to update drivers after passing command adb reboot. Tried installing HTC Sync and uninstalling a few times but stuck in the same place. Any way around this?
Thanks
Running Windows 7 64bit. Software version 1.54.161.10
EddyOS said:
Install HTC Sync Manager, then uninstall it but leave the drivers. Should then work fine
http://www.htc.com/uk/support/software/htc-sync-manager.aspx
Click to expand...
Click to collapse
I just tried this, and it didn't work. When I plug in the phone via USB, my computer doesn't even make the notification sound that something has been detected. The red light on the phone shows its charging, but my computer doesn't even show that anything was plugged in or detected. Could this be a problem with my computer?
If another computer works, then yes
andrewjrr said:
I just tried this, and it didn't work. When I plug in the phone via USB, my computer doesn't even make the notification sound that something has been detected. The red light on the phone shows its charging, but my computer doesn't even show that anything was plugged in or detected. Could this be a problem with my computer?
Click to expand...
Click to collapse
what about device menager ?
Maybe you have some other drivers installed for android devices, try uninstalling them first.
wodzini said:
what about device menager ?
Maybe you have some other drivers installed for android devices, try uninstalling them first.
Click to expand...
Click to collapse
Nothing in device manager either.
I do have my Nexus drivers installed. Do you think that could be the problem? Should I uninstall everything previous?
I tried installing HTC sync manager on my work laptop (which has no other phone drivers installed), and it's still the same problem. One thing I've observed though is when I leave the phone plugged in to the computer USB and do a reboot on the phone, the computer detects it at the startup "htc one" screen, but the device disappears seconds later as the phone continues to boot. It's like it detects it initially, then some software with the phone is causing it to fail. Any ideas?
bump.. went through HTC customer service and they pretty much got me to try reinstalling drivers, sync manager, etc.. didn't work. Said they would push me to the next level tech support which would be as long as 7-10 business days and that was last Monday and still haven't heard anything
OMG... finally got it working. I installed HTC Sync Manager again and decided to run it and see what happened. While it was scanning for music on my computer windows installed the drivers. More than once it seems.
Now I need to know if I can uninstall Sync Manager but keep the drivers. It keeps opening up and I don't know if it's safe to flash recovery if that's going to happen.
Flashed TWRP successfully and made my back up.
--------------------------
OLD NEWS BELOW:
Here's the deal... I just flashed the 3.x RUU so I'm stock but I'm unlocked and s-off. I'm trying to flash TWRP via fastboot so I can get a custom ROM on here. I turned on USB debugging on the phone.
First of all, that stupid HTC Sync manager keeps trying to install and I don't know how to stop it. Googling has not helped with this.
Second, I can't get the device to be seen in adb, or at least not online. I seem to be going backwards with all the steps I have taken to try to get this to happen.
I'm using dotatt's adb package. When I attach the phone while it is off windows looks for drivers and usually fails. One time it seemed to work and adb saw the device but then when it boots up that Sync Manager wants to install so I decline. Then my phone was seen but listed as offline.
So I tried uninstalling all HTC things on my computer and reattach phone. Didn't help anything. I tried installing the HTC Sync then uninstalling it thinking I would get the drivers, no go.
I grabbed these Universal ADB drivers http://www.koushikdutta.com/post/universal-adb-driver linked to from a twrp page here https://twrp.me/devices/htconem9.html
Nothing lists as a device in ADB at all now.
My windows Device Manager shows "Unkown Device" under "Other Devices" with no driver listed.
Tried this:
[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
http://forum.xda-developers.com/showthread.php?t=2588979
Still not working.
ACK! Can anyone help me out?
Is there still an issue with using usb 3.0 ports? I feel like I heard something about that way back when.
That's pretty much how it's always been. Best way to get the appropriate drivers is to install HTC sync, let it do its thing, reboot the PC, then uninstall HTC sync without removing the drivers. To the best of my knowledge, been that way since at least the days of the Incredible, if not before. At least it's how I've always gotten the drivers to use adb.
Yeah I remember that from the Rezound, which is why I did that, but it seems that the drivers didn't actually get installed this time until I let HTC Sync Manager start running and scanning my computer. That's when I saw the message that it was looking for drivers and twice it told me it installed them.
I would think it would have them installed during the 'actual' installation process. So I guess I just uninstalled prematurely. Seems weird. But it's working now so all good.