Related
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.
Guys, I need a little help here. I've rooted my share of phones, and even some tablets, but the Evo i bought a few days ago has been a nightmare.
For some reason, and I can't tell why, this thing will not be recognized by Windows.
It always shows up as "Unknown Device" under the USB catagory on Device Manager.
I've tried different OS versions (Windows 7 64Bit, Vista 64bit, Even Mac). I've also pulled down every form of driver I can think of (SDK Orginal version, HTC Sync, Hboot Versions, etc.)
I just cannot get this thing to be recognized. And if I manually try to update the driver and point it to one that I've downloaded, Windows tells me that the most current driver is already installed.
The bottom line is that I need to be able to connect to the phone from the comp in order to push stuff via ADB and throw commands at it. The same unknown device situation happens when the phone is in bootloader or actually booted into Stock Froyo (2.2)
Has anyone ever seen anything like this? I know i haven't, and it's buggin me out.
buster3845 said:
Guys, I need a little help here. I've rooted my share of phones, and even some tablets, but the Evo i bought a few days ago has been a nightmare.
For some reason, and I can't tell why, this thing will not be recognized by Windows.
It always shows up as "Unknown Device" under the USB catagory on Device Manager.
I've tried different OS versions (Windows 7 64Bit, Vista 64bit, Even Mac). I've also pulled down every form of driver I can think of (SDK Orginal version, HTC Sync, Hboot Versions, etc.)
I just cannot get this thing to be recognized. And if I manually try to update the driver and point it to one that I've downloaded, Windows tells me that the most current driver is already installed.
The bottom line is that I need to be able to connect to the phone from the comp in order to push stuff via ADB and throw commands at it. The same unknown device situation happens when the phone is in bootloader or actually booted into Stock Froyo (2.2)
Has anyone ever seen anything like this? I know i haven't, and it's buggin me out.
Click to expand...
Click to collapse
I've never seen that before. Wish I had something for ya. Is the Evo brand new or used? Are you sure the usb cable is good? I've seen a bad cable cause some headaches before. Wish I had more for ya, sorry man.
Sent from my PC36100 using XDA App
EVO is not new. I bough it from cragslist a few days ago. It seems to work fine otherwise. Not rooted for sure, and running Sprint original 2.2.
I did try a couple of different USB cables just to be sure, and had the same results.
The funny thing is that even though I was never able to get it "recognized" on any of my machines, I was able to get ADB so "see" it for a while. I started the rooting process by pushing files to it via ADB and even sent a reboot command to it.
Once it rebooted, that's when it all went bad. It was still showing as unrecognized (just like before), but now ADB can't see it at all. Keeps telling me no devices are connected.
Even my friend's Mac Air (which supposedly doesn't need any kind of drivers to see the phone) can't see it either.
It's just weird...
perform a hard reset, maybe a rogue app or setting got messed up,
fastboot screen>clear storage>yes
Tried that as well. Sorry i didn't mention it in the original post.
I think I've pretty much tried everything that's somewhat logical at this point.
Now I'm looking for the "illogical" ideas.
Make sure usb debugging option is turned on in settings>applications>development and the phone is in charge only mode. Then it should be recognized and you should be able to use adb.
Debugging was turned on already. I made sure of that.
As for the mode of connection I've tried them all with mixed results.
Here's what I've seen so far...
Charge only - unrecognized device in Device manager, and ADB can't see it.
HTC sync - unrecognized device in Device manager, and ADB can't see it.
Disk Drive - unrecognized device in Device manager, and ADB can't see it.
Internet Sharing - never tried it.
Here's the weird part. If i uncheck Debugging and set the phone to HTC Sync, I am sometimes able to get ADB to see it.
This is just confusing...
What happens if you uninstall HTC Sync and just leave the drivers installed? Could work I suppose. I know unrevoked says to make sure you uninstall HTC Sync and install the ADB drivers.
try this. connect your evo to a machine running xp. i had the same problems rooting one evo using windows 7. connected to a machine running xp ,zipped right through without a hitch.
HOPE THIS HELPS YOU IN YOUR QUEST
Thats what I tried on the Vista box.removed HTC sync, and left the HTC drivers.when that failed I removed the drivers too and replaced them with several different ones I found online.none seemed to work.
The strangest part is that all guides seem to say that MAC OS should just see it without any drivers.
I borrowed friends MAC air and it didn't see it either.
I'm not sure which USB drivers you are using, but these work for me. Uninstall the drivers first, then install this. I hope it is legal to put these here and if not I am extremely sorry.
PS you could try a Linux Live CD and it will see it without drivers or go with Wubi which installs Ubuntu on your Windows hard drive and can be uninstalled just like any other program. It gives you the option to boot into Ubuntu or Windows on bootup. Neat little program and it is faster than using the live CD. Go to this link Wubi and click the Start Download button to download Wubi.
Those seem to be the same drivers I've tried (well those and a ton of others as well).
I'm gonna give that LiveCD idea a shot. Burning it now.
If not, I'm gonna try to find an XP machine somewhere.
I've got a couple of VM's on my machine running XP, but since the main Win7 Machine doesn't see it, it can't seem to pass the USB connection over to the XP VM.
Man, I have to say, this is just the most complicated rooting process I've ever seen. If this was my first root attempt, I'm pretty sure I'd leave Android forever
It usually is a painless operation to root the Evo. For some reason you are having a difficult time with driver installation. It seriously has to be something simple that has been missed, because I have rooted mine and several friends Evo's and it was very easy. I had a MyTouch 3g 3.5mm before this Evo and talk about a pain. Before the Universal Auto root app you had to make a gold card first and that in itself took over an hour. It was my first root and it was very difficult and time consuming, so to see how easy the Evo was no matter which way I do it made me very happy.
buster3845 said:
Thats what I tried on the Vista box.removed HTC sync, and left the HTC drivers.when that failed I removed the drivers too and replaced them with several different ones I found online.none seemed to work.
The strangest part is that all guides seem to say that MAC OS should just see it without any drivers.
I borrowed friends MAC air and it didn't see it either.
Click to expand...
Click to collapse
yes the mac doesn't require additonal drivers to run adb however u need to make sure the directory is properly set in terminal so adb knows where to pull commands from... on windows did u try uninstalling everything phone related? SDK, HTC Sync, the whole nine yards then try reinstalling only the sdk and the usb drivers? I know with the lastest SDK the usb driver is not included for some reason or at least it wasn't with mine... then one day my adb just randomly stopped working and a uninstall/reinstall cleared up everything... try this usb driver and see where it gets u. Don't know if it's any different that wat the guy above posted but worth a shot. Reinstall the appropriate SDK first then i would recommend plugging the evo into the pc with no usb drivers installed then when it cant automatically find the drivers direct it to the file u downloaded and it should pull the necessary drivers from there and see if that does the trick...
View attachment android-usb-driver.zip
No dice so far guys...but i have made progress in identifying the issue (sort of).
So here's the deal - the ONLY way the phone is recognized is if i toggle the "debugging" setting.
If i plug the phone in with the switch set on (meaning USB Debugging enabled) the phone is not recognized. Pointing the unknown device to the drivers (any drivers) does nothing.
However, if i plug the phone in with the switch set off, it finds a usb mass storage device. Then i turn the debugging switch on, and it finds the ADB Android phone with no issues. Then i can push commands via ADB without any problems.
The problem i have is that I cannot toggle that switch if i boot into HBOOT menu. So the comp never see's the phone.
I've tried this experiment on Win7-64bit, Vista-64bit, XP 32bit, and even MAC.
The same situation seems to apply everywhere, and with all of the drivers I've tried. None of them seem to allow the phone to be plugged in and automatically be found. The only way for the comp to see the phone is if i toggle the debugging switch off, then on.
At this point, I'm ready to put out a bounty on this. $20 via PayPal to anyone who can walk me through it. Bottom line is that I need to be able to see the phone without having to toggle the debugging switch. That will allow me to boot into HBOOT and still send commands to the phone via ADB.
Thanks for all the help guys. Hopefully, we can get this resolved.
**BUMP**
Anyone care to take a shot??
Hey guys, I have an HTC one vx. After searching for about a week about my problem, I am posting on here.
I have been trying to root so I can get the tethering app, and custom roms, etc. When I attempt to connect any computer in my house (windows 8,7) to my in fastboot mode HTC, windows pop up saying... The USB device that you have connected has malfunctioned. It shows up in device manager with a yellow arrow over it. I've tried installing HTC sync, uninstalling that, installing pdanet drivers, updating in device manager, manually updating in device manager from android SDK and pdanet directories, tried usbdevview, tried switching cables, USB ports, everything. Any suggestions? I'm at a loss of what to do. Adb works when booted up though. Most annoying problem ever.
Boot into windows 7 uninstall htc manager and it will ask "want to remove all drivers with it" or something like that, click yes then from there install latest HTC manager from HTC site, once installed plug in Phone and HTC manager should give proper drivers
Let me say beforehand that I am a lifetime lurker. I would not be posting here if I hadn't already spent at least two days scouring the web for an answer.
My HTC Desire HD cannot connect to HTC Sync, but it can connect as a storage device, and can be seen by adb. Whenever it connects while in hboot/fastboot, it will flicker "USB" a few times before Windows tell me it's not recognized (Device failed enumeration code 43). This includes using the RUU wizard from HTC. That will just make it stick on "RUU" in the bootloader.
I have tried every driver download suggested on this site. I have switched USB cables three times (all htc cables). I have used two seperate computers (Windows 8 and Windows 8.1).
I'll admit I'm a nooby specifically to Androids. All I want to do is flash new ROMs/root my device. As far as I know this is step one, and I can't go any further until I've unlocked my bootloader.
EDIT: SOLVED
HTC Desire HD drivers really hates Windows 8 and 8.1. Installed Windows 7 32-bit and it worked just fine.
That error can be a pain in the ass. I have it as well. I believe disabling griver signature enforcement in win8 (it's your OS, isn't it?) should allow installing adb drivers, but I was too lazy to check it. As a workaround I instead flash the boot.img in bootloader by putting it to PD98IMG.zip
I can upload you a template, leave the txt in it and replace the boot.img with your desired one, choose store (none) compression level, then put the zip directly (don't use folders) in sd card
EDIT: I didn't fully read your post before. If you don't have S-OFF most probably you can't get away without adb drivers..
Turned off device signing. No effect.
Have you tried now manually installing drivers in device manager while the phone is in unrecognized state? Does it still say the drivers are incompatible?
If your OS is 64bit, you need these http://d-h.st/23V
I have those drivers. I installed them manually. I tried the updating the drivers through device manager and pointing them directly to the drivers folder I need, and Windows is insistent that not having ANY drivers installed is the best driver to have installed for my device.
I am getting a pop up saying that the device is failing to to start. It's not like other usb devices I might have plugged in and they just sit there in at least their correct category in device manager.
The part that ticks me off most, is that this exact problem on this exact model has been solved on three different forums, and each time the OP just said "nvm I fixed it" and never even bothered to explain how for the rest of us.
It's really hard not to curse right now.
in device manager update dialog goto
browse my computer --> let me pick --> have disk --> choose the .inf from the drivers path.
Ya, I had tried that too. None of them will work. It says the file I chose doesn't have compatible software for my device.
Once again, this only happens in the hboot/fastboot/RUU. Once the phone has loaded the OS it works totally completely fine, save for HTC Sync not seeing the phone and vice versa. I don't understand why some drivers would only work sometimes unless something is wrong with my bootloader, and if so, how do i fix it?
have you tried un-installing HTC SYNC?
SuperMechaCow said:
Once again, this only happens in the hboot/fastboot/RUU. Once the phone has loaded the OS it works totally completely fine, save for HTC Sync not seeing the phone and vice versa. I don't understand why some drivers would only work sometimes unless something is wrong with my bootloader, and if so, how do i fix it?
Click to expand...
Click to collapse
Nothing is wrong with your phone, same thing happens to me, I just thought disabling driver signing should fix it, like I said I was too lazy to check it since I found workaround for my needs.
TheJokah said:
have you tried un-installing HTC SYNC?
Click to expand...
Click to collapse
It is currently uninstalled.
@smoger:
I would try your workaround, but I' m not sure where to obtain the boot image I need. Also, I thought you could only change the S-Off if your bootloader was unlocked anyways?
Power down DHD and connect it to PC. I realized, my win7 was installing drivers, while phone was off.
Sent from my HTC Desire HD using xda app-developers app
ammo12 said:
Power down DHD and connect it to PC. I realized, my win7 was installing drivers, while phone was off.
Click to expand...
Click to collapse
It appears to be the same device/drivers when powered off or when in the Android environment. While in the bootloader, it shows as an unknown device.
I also noticed that only when I am trying to update via RUU, it says instead "Device Descriptor Request Failed"
SuperMechaCow said:
@smoger:
I would try your workaround, but I' m not sure where to obtain the boot image I need.
Click to expand...
Click to collapse
The boot.img is in the ROM-zip-file packed. But I think, if its a RUU it is called PD98...img
Try this, I know its from Samsung, but this installs fastboot drivers and drivers used for ADB access
https://www.dropbox.com/s/vqfuv8fifmrkkxt/SAMSUNG_USB_Driver_for_Mobile_Phones.zip
For the set of Google Drivers, go here too http://d-h.st/23V
My drivers list does not show the Google or HTC drivers like yours does after installing all the things in your links. In fact, that's the fourth time I've downloaded those Google/HTC Win7 64x drivers from people around the web. They are not in my drivers list after installing them via the INF files. I must be doing something wrong.
SuperMechaCow said:
My drivers list does not show the Google or HTC drivers like yours does after installing all the things in your links. In fact, that's the fourth time I've downloaded those Google/HTC Win7 64x drivers from people around the web. They are not in my drivers list after installing them via the INF files. I must be doing something wrong.
Click to expand...
Click to collapse
Did you browse to the folder where the manual driver files reside?
Sent from my Desire HD using Tapatalk 4
SuperMechaCow said:
Ya, I had tried that too. None of them will work. It says the file I chose doesn't have compatible software for my device.
Click to expand...
Click to collapse
SuperMechaCow said:
I have those drivers. I installed them manually. I tried the updating the drivers through device manager and pointing them directly to the drivers folder I need, and Windows is insistent that not having ANY drivers installed is the best driver to have installed for my device.
Click to expand...
Click to collapse
To be exact I have:
Tried HTC Sync
Tried HTC Drivers Installer
Tried to Automatically search for drivers
Tried to install drivers by using the inf Install option
Tried to manually select drivers by pointing to the folder the Win7 64x drivers were placed
Tried to manually install by picking out the exact inf files
Tried to install from device drivers list, were they were not listed
Tried these steps with driver signing turned off
Tried all of these steps with another PC
I still think the issue is related to the fact that it only has problems in the bootloader menu
Ok, like u know I had this issue. Now I randomly managed to fix it when I needed adb drivers for my new toy (Sanei tablet for 40$ lol)
The mistake I was making is that I was trying to install the drivers while device was in fastboot, but apparently you can get away with casual "My HTC" drivers which can be installed when DHD is booted into Android. It looks likethe phone is not being detected from bootloader (it doesn't like any of the drivers I had tried), but I can fully use ADB while it's in recovery or starting/trying to boot OS, so it should be enough for rooting/unlocking bootloader.
I remember with HTC Wildfire I had drivers package with seperate drivers for Android and fastboot, so I had to install different driver after rebooting to fastboot, but with these new drivers and win8 it doesn't work out this way.
Solved. Used Windows 7 32-bit. Windows 8.1 was the culprit.
Similar issue
SuperMechaCow said:
Solved. Used Windows 7 32-bit. Windows 8.1 was the culprit.
Click to expand...
Click to collapse
I am facing the same problem and I too have tried different methods like you did. Am using Windows 8.
Gotta try on Windows 7. Shall update if that solves my problem too.
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