So I've been tasked with unlocking and flashing my friends Sprint Evo over to Cricket wireless. The procedure looks simple enough and I'm sure I can get it done, Although I'm being halted before I can even start, due to the fact that my Windows * computer wont recognize the HTC Evo as a phone. it shows up as 'Unknown Device' most of the time, I've been at it for 7 hours now and still no success, looked up multiple guides (5 different guides from this site alone, on top of 7 other guides I found on the net) and still no success. i've downloaded the drivers and installed, but the best I can get my computer to see this phone as is " My HTC" device, with a warning icon and no connectivity. I've tried 3 cables, all 7 ports on my PC.. I'm honestly at a loss here. I can provide any tech specs or info needed. What can I do to fix this?
I've also explored adding a Linux boot so I can just use linux, but the install manager with linux asks me to partition my drive, and its not showing my 1tb HDD as a partitionable drive, only a few small partitions with nowhere near the amnt of space I'll be needing for ubuntu or Fedora.
Derpwood said:
So I've been tasked with unlocking and flashing my friends Sprint Evo over to Cricket wireless. The procedure looks simple enough and I'm sure I can get it done, Although I'm being halted before I can even start, due to the fact that my Windows * computer wont recognize the HTC Evo as a phone. it shows up as 'Unknown Device' most of the time, I've been at it for 7 hours now and still no success, looked up multiple guides (5 different guides from this site alone, on top of 7 other guides I found on the net) and still no success. i've downloaded the drivers and installed, but the best I can get my computer to see this phone as is " My HTC" device, with a warning icon and no connectivity. I've tried 3 cables, all 7 ports on my PC.. I'm honestly at a loss here. I can provide any tech specs or info needed. What can I do to fix this?
I've also explored adding a Linux boot so I can just use linux, but the install manager with linux asks me to partition my drive, and its not showing my 1tb HDD as a partitionable drive, only a few small partitions with nowhere near the amnt of space I'll be needing for ubuntu or Fedora.
Click to expand...
Click to collapse
sorry about hard times. that what you get for using windows. ok joking aside. what you need to do is install thr windows 7 64bit adb and fastboot drivers. then go to your device in device manager and browse to those drivers to install. thats all you need. you dont need any fancy htc sync device/portable media player/whatever else driver. it will show up in decice manager as my htc under android usb devices.. if this is giving you that much trouble wait till you have fun flashing it over to cricket. yay
Related
I already have my samsung usb and android modem drivers installed. but everytime i plug my phone in with usb debugging on, the "Found New Hardware" window keeps popping up, why?
im not sure, but it could be the problem to why it always says "waiting for device" on superoneclick
My day job is pc tech, I have seen this a few times but going to follow the steps, first give me some info
Which version of windows?
32 or 64 bit?
How proficient are you at driver maint. *add and removeal ov drivers*
When did this start?
windows xp - 32 bit - and im pretty proficient at maintenance. i think its always been like this.
Ok, Do you always use the same USB port? and have you tried a different cable? and have you tried it on other computers? if so did it do the same thing there?
First we got to get rid of the drivers on the pc.
http://download.cnet.com/DriverMax/3000-18513_4-10572602.html
This is a free program that has a few nice features but most important is that it can tell you the name of the files that are used as drivers. After you install and register (its free, they just want to know who you are.. name, email, that kind of stuff) there will be an entry on the right side called "Installed Drivers Report". Make sure you phone is connected before you click this as it scans active drivers. it will generate a report you can scroll through and find any samsung driver entrys. Write down those file names, we will need them in a moment.
Go to device manager and remove the device there. Windows XP was kinda lame about device removal it did not actually remove the device just broke the connection. Vista and 7 give you the option to actually delete the files which make this easier. Since your on XP after the devices have all been removed UNPLUG your phone from the PC then start a search for those files in the Windows directory. Delete (or move) those files and the rerun the driver install program from here
http://forum.xda-developers.com/showthread.php?t=728929
After that it may setup and find new hardware a few times. Mine did it 3 since there are multiple different methods it can connect with and each uses differnet hardware. Also each time you use a differnt USB port it sees it as new device in a new location so it also goes through new hardware setup again.
Report back and let me know if this helped any.
okay thanks for the quick response. i will try it when I have time and ill get back to you. first, imma try it on a different computer.
also, when its plugged in and i open device manager, theres 3 yellow exclamation marks, one on the android modem, device, and in the "OTHER devices" section, the USB controllers. if that means anything.
just turn off usb debugging... and it will stop. turn it back on if you need to use it for something.
Ok... first off im a noob to this forum but I know this is a legitimate issue not user error and ive spent the last 4 days scouring to get SOME information on this and the only thing ive found is remove battery and reset phone... HELLO!!!! thats step one on the list... sorry venting done...
Device: mytouch 4g
OS: Windows 7
When I got this phone i plugged it in and ran with no issues until i tried to root it without success... and when i tried the ADB method i found that the phone would no longer mount into windows 7 i have tried multiple computers and multiple cables so it's a device issue.
When I plug my phone into a computer it comes up with "searching for drivers" and fails... look in device manager and it says "Windows has stopped this device because it has reported problems. (Code 43)"
Tried manually finding drivers and can't...
Tried "repairing" the install of HTC drivers that came off the HTC website and didn't work...
Tried installing PDA net to get different drivers... didnt work
uninstalled devices and get the same issue...
deleted upper and lower filters from registry
Tried every combination of fastboot/USB debug
even tried desperatly deleting cookies/cache/web history(found on another forum)
AND NOTHING WORKS...
if you can think of anything I haven't tried it would be nice
Currently installed Apps that may be involved
Visionary
Super User
Terminal Emulator
I would like to help you out but need to what rom is on your device and what exactly your trying to do on windows
Sent from my HTC Glacier using XDA Premium App
It's running the complete stock rom... i believe it's called espresso... and all im trying to do with it right now is get it to show up in windows as a hard drive...
usually I would assume a driver issue (thats what windows thinks it is) but I've reinstalled the drivers around 10 times desperately and restored my computer to no avail so i think when i tried to root it the first time it flashed the usb firmware... if thats complete bs then just let me know... new to android... not new to computers...
sky2k-y2k said:
It's running the complete stock rom... i believe it's called espresso... and all im trying to do with it right now is get it to show up in windows as a hard drive...
usually I would assume a driver issue (thats what windows thinks it is) but I've reinstalled the drivers around 10 times desperately and restored my computer to no avail so i think when i tried to root it the first time it flashed the usb firmware... if thats complete bs then just let me know... new to android... not new to computers...
Click to expand...
Click to collapse
For a Hard Drive
1lug your phone into the computer
2:On your phone, drag the top slider bar down to the bottom
3:There should be a notification that says charge only. Click on that and select Disk Drive, Mount as disk drive. Click that
Try that and let us know what happens.
Edit: If you are trying to use ADB you want to be on charge only and have USB debugging on . To get to debugging
Menu-settings-applications-development-USB debugging
yeah that was one of the first things I tried(i actually have that as default)... The problem is that my computer thinks its an unknown device when plugged in and I can't point it to the correct driver...
USB Debugging is enabled, correct?
Seems strange... have you even tried installing the driver on another computer?
I've tried debugging on and off...
And yes I've tried a different computer that was one of the second things I tried
Sent from my HTC Glacier using XDA App
sky2k-y2k said:
Ok... first off im a noob to this forum but I know this is a legitimate issue not user error and ive spent the last 4 days scouring to get SOME information on this and the only thing ive found is remove battery and reset phone... HELLO!!!! thats step one on the list... sorry venting done...
Device: mytouch 4g
OS: Windows 7
When I got this phone i plugged it in and ran with no issues until i tried to root it without success... and when i tried the ADB method i found that the phone would no longer mount into windows 7 i have tried multiple computers and multiple cables so it's a device issue.
When I plug my phone into a computer it comes up with "searching for drivers" and fails... look in device manager and it says "Windows has stopped this device because it has reported problems. (Code 43)"
Tried manually finding drivers and can't...
Tried "repairing" the install of HTC drivers that came off the HTC website and didn't work...
Tried installing PDA net to get different drivers... didnt work
uninstalled devices and get the same issue...
deleted upper and lower filters from registry
Tried every combination of fastboot/USB debug
even tried desperatly deleting cookies/cache/web history(found on another forum)
AND NOTHING WORKS...
if you can think of anything I haven't tried it would be nice
Currently installed Apps that may be involved
Visionary
Super User
Terminal Emulator
Click to expand...
Click to collapse
sounds like a driver issue... i am not a 100% but thats what i sounds like.. download and install this program.. it uses the correct drivers.. just make sure u select "HTC" when prompted.. http://junefabrics.com/android/download.php goodluck report back
i tried that already and after trying again (just now) it failed again... i wish this was a simple driver issue...
I might be totally off but try changing your sd card and see whether your computer accepts it.
Also when installing drivers make sure your device is not connected to the computer.
Or try different USB port, or a factory reset.
Sent from my HTC Glacier using XDA Premium App
nope... different sd card/different usb port/factory reset didn't do it...
sky2k, I had some driver issues with my mt4g too.
Try this:
Download USBDeview - http://www.nirsoft.net/utils/usb_devices_view.html
Download the drivers for your phone from HTC - http://www.htc.com/us/support/t-mobile-mytouch-4g/downloads/
Run USBDeview AS ADMINISTRATOR. List all drivers in alphabetical order. Remove any and all associated with your mytouch 4g.
Reinstall drivers via HTC Sync software. Please let me know how this works for you.
Try to connect the phone with both the SD and SIM cards removed.
well guys im still having issues connecting via USB... but...
I found something to let me connect to ADB via WIFI so using it I got everything pushed and I am now S-off... so I am extremely pleased... that said i would "like" to be able to plug in and mount the sdcard/run adb but if I cant i can deal with my work arounds...
So I just bought a brand new Nook HD+ from best buy. It is in shrink wrap so looks factory new.
I first turn it on and it gives me the select the lanuage and country page (No wifi selected). I do not proceed. Press volume down and tap lower left hand corner. If gves me the Enable ADB button. I do not press it yet. Instead I plug it into computer, which then puts it in MTp mode.
I unplugged cable and now press the Enable ADB button. I plugged it back in and same MTP mode.
I then decided to skip OBE. So I press lower volume button and then lower left screen followed by lower right screen. Then I press the Factory button. Then the Skip OBE option.
Now I am at home screen, I go to settings, then developers, and I confirm the ADB status. just to be sure, I uncheck ADb and then rechecked it. Plugged it back in and same result. It puts it in MTP mode.
I then confirm by going to Device Manager and see no entry for Android Composite device.
I do notice out of the box, it is 2.0.2 not 2.0.0? Does this mean it is a customer return? Even though it was shrink wrapped?
Need Windows Driver for Nook
I believe you need a windows driver for the Nook HD and HD+ on Windows. On Ubuntu, I just do "android update device && adb kill-server && adb start-server && adb devices"
I can't post links. google usb_driver_r04-windows
superflysocal said:
I do notice out of the box, it is 2.0.2 not 2.0.0? Does this mean it is a customer return? Even though it was shrink wrapped?
Click to expand...
Click to collapse
They could be working now on out of the box 2.0.2 now. Don't know.
You are not telling us much about your PC, which we need to know to help you. What version of Windows are you running? Have you got ADB running on any other devices?
No other new devices are showing? Did you follow the B&N trouble shooting guide section 4.6 which I reference in my HD+ tips thread linked in my signature.
Sent from my Nook HD+ Running CM10 on SD
I have win xp, but I have also tried it on win 7 machine and win mce2005 machine.
I am not sure if i ever had adb working for other devices but I think i have. Actually pretty sure I have.
I do know for absolutely sure I have had multiple android phones connected to this machine and in usb debugging mode, they show up as Android Composite Device.
I also have Android SDk installed on this machine (but not in the win 7 machine)
superflysocal said:
I have win xp, but I have also tried it on win 7 machine and win mce2005 machine.
I am not sure if i ever had adb working for other devices but I think i have. Actually pretty sure I have.
I do know for absolutely sure I have had multiple android phones connected to this machine and in usb debugging mode, they show up as Android Composite Device.
I also have Android SDk installed on this machine (but not in the win 7 machine)
Click to expand...
Click to collapse
Well, since you had other devices using ADB, then go to device manager and look under USB controllers. Uninstall any USB composite device there, especially any that has the device id under properties and details listing 2080 as part of the number. That will force the system to re-recognize and reinstall the right driver you can get from my HD+ tips thread.
Sent from my Nook HD+ Running CM10 on SD
There was a usb composite but it was for my wintv usb, I uninstalled it anyways. Nothing else, still not doing anything. Any chance this is a new hardware version that has this locked down?
It did come with 2.0.2 instead of 2.0.0
I don't see a reason for a hardware revision, and there is no reason for 2.0.2 instead of 2.0.0 other than bug fix since you can still root with 2.0.0 - 2.0.4. The inability to ADB is on your part. Seriously I don't see why would B&N lock down people ability to ADB since it's a requirement for people to develop for Nook platform. It's not like B&N will make 2 different versions of each device, one for developers and the other for consumers. I can still see B&N may lock down ability to root with current method on future revision (say 2.0.5+) but as of now it's open. ADB will never be lock. I think the fact that ADB for Nook devices are hard to get to will not only deter people from root but people to develop for the platform as well. Personally I think it's a bad choice on B&N part to have it hard for people to ADB.
I do agree with you, but I am open to any suggestion.
I have a win7 64-bit laptop that I can use. Should I try that? I thought win xp machine would be easier.
Should I reset nook hd+ and NOT skip OOBE?
I was hoping to avoid wifi so that I don't update to 2.0.4 which was reported to have corrupt microsd card writes.
superflysocal said:
I do agree with you, but I am open to any suggestion.
I have a win7 64-bit laptop that I can use. Should I try that? I thought win xp machine would be easier.
Should I reset nook hd+ and NOT skip OOBE?
I was hoping to avoid wifi so that I don't update to 2.0.4 which was reported to have corrupt microsd card writes.
Click to expand...
Click to collapse
I just bought a HD+ from Walmart. It was 2.0.2 out of the box and I was able to root the device successfully after OOBE was completed. I don't remember if the device upgraded itself to 2.0.4, I'll check later. I did the all in one root process on a Win7 64bit lappy so try it and see if it works.
IMO the person who posted about the sdcard file corruption has hardware issues but who knows? No one else is reporting having this issue afaik.
There are people that report a success ADB driver install on win7 64bits via my method. Check the tips thread.
someone0,
just curious, what firmware are you on? 2.0.4? Are you having any sd card write issues?
So I reset the nook hd+, then registered (did not skip oobe) and it updated 2.0.4, but still same issue. It will not recognize device as Android Composite USB device, only as MTP media device.
i am beginning to think I got defective unit.
superflysocal said:
So I reset the nook hd+, then registered (did not skip oobe) and it updated 2.0.4, but still same issue. It will not recognize device as Android Composite USB device, only as MTP media device.
i am beginning to think I got defective unit.
Click to expand...
Click to collapse
No, I don't think so. If you read through the posts on the other threads you will see about half the users have a very difficult time making adb work. And it is never anything wrong with the HD, it is always something with your PC. There are so many different setups for windows that it is very hard to advise people. Just keep trying things others have. I still have problems and I have been doing it for weeks and each time it fails it is a different thing. The only thing I can advise you is to keep uninstalling things because something that is installed is blocking your PC from recognizing the new device. I would uninstall any device under portable devices, other, android phone and any device under USB controllers that has 2080 as part of the device id.
leapinlar said:
No, I don't think so. If you read through the posts on the other threads you will see about half the users have a very difficult time making adb work. And it is never anything wrong with the HD, it is always something with your PC. There are so many different setups for windows that it is very hard to advise people. Just keep trying things others have. I still have problems and I have been doing it for weeks and each time it fails it is a different thing. The only thing I can advise you is to keep uninstalling things because something that is installed is blocking your PC from recognizing the new device. I would uninstall any device under portable devices, other, android phone and any device under USB controllers that has 2080 as part of the device id.
Click to expand...
Click to collapse
Oh you are so rght. I never did figure out what is blocking it, too impatient to uninstall stuff.
BUT, I did find an old seldom used laptop with win 7 32-bit. When plugged in it gave me error that drivers could not be installed!. Went to device manager, found the device and updated driver. Adb achieved and all in one root done.
No, I'm on 2.0.0
Well guys I've been trying for hours now, whenever I try to install the USB drivers in order to unlock my bootloader, when I plug in my Nexus it installs the MTP drivers on it's own, if I try to install the google drivers downloaded from ADB all I get is a message saying the best drivers for my device are already installed and it doesn't let me overwrite them.
If I go with the use disk option it doesn't let me choose the usb_drivers folder because it just wants to use a .inf file, whener I follow the instructions the toolkit dictates I read the dead end with the "The best drivers for your device are already installed"
I'm so angry right now.... Please help me.
Are you on a Windows XP operating system by any chance? There are major issues with MTP mounting on WinXP regardless of the service pack you're on. Some people claim they've gotten things working by updating WMP, via a Naked Driver and even by installing the Android SDK. Let me know if you are indeed on WinXP & I'll get you some links
Did you try following Wug's Nexus Root Toolkit to install the drivers? That helped me. I cannot post a link so look around for it.
I'm running Windows 7 64 bit, thanks guys, I just gave up and did it in my sister's laptop, it worked on the first damn attempt, maybe the drivers of my N10 were screwing something up, that's my best guess.
Glad you got that sorted--just for future reference, a common recommendation for people having driver issues with their Nexus devices is to simply go into Win Device Manager, uninstall all your current Nexus & ADB drivers and restart. Then plug your phone in via USB and let the auto installation do its thing. Usually this fixes all issues w conflicting device drivers
I have no idea in which section to write this, so General seams like the best choice.
I have a Galaxy Y testing device with a broken boot.img. I am trying to get Odin working in Windows 7 in order to flash a new boot.img to this device, but I can't get the Samsung USB drivers to work and my Windows knowledge is now that great as I mostly work on Linux computers, but no fastboot on Samsung devices.
There are two drivers listed in the Device Manager. The Regular Samsung USB drivers, and something called Samsung USB CDC. It's the CDC I seam to have issues with. It just shows an error message that states "The device could not start (Code: 10)". I have already talked to Samsungs online support, but there is not much support to find there. They know nothing about Windows or how to get anything working on it. And google's search engine, which usually is the best friend for something like this, did not come up with much either.
I should mention that I run Windows in VirtualBox. However, I already have HTC Sync Manager fully working with an older HTC device, so this is not a VBox issue. Also, Windows do find the device just fine, it just can't start one of the drivers.
I have tried installing Kies. I have also tried installing other separate driver versions. Nothing is working.
Search the forums for Naked Drivers, its a complete driver package for a lot of android devices.
Give em a try.
I would post a link but my post count is as such that I cannot at this time.
WooHooGuy said:
Search the forums for Naked Drivers, its a complete driver package for a lot of android devices.
Give em a try.
I would post a link but my post count is as such that I cannot at this time.
Click to expand...
Click to collapse
I love the idea of a multi driver for all devices, much like on my linux boxes, so thanks for that. However, I get the same issue and same error message. I will try to reinstall windows and see if that will work. It has been many many years since I ran windows as my daily OS, but I do remember that formatting was the best way of fixing issues with it. If this is still no go, I will try to put windows directly on my netbook to see if this could be a Virtual problem anyways, but I don't think so. USB stuff is working fine on the Virtual OSX.
Will report back later
EDIT:
Nothing is working. All I have installed, is the naked driver. When I plug-in my HTC Desire or HTC Wildfire S, the driver is working fine. But when I plug-in the Galaxy S3 or the Galaxy Y, I get the "The device cannot start (Code: 10)".
So HTC devices are working, but Samsung is not. The same problem I had with separate HTC and Samsung drivers.
try the one from my link,its latest usb driver exe from kies,worx on win8 64bit too.
http://forum.xda-developers.com/showthread.php?t=1927769
-CALIBAN666- said:
try the one from my link,its latest usb driver exe from kies,worx on win8 64bit too.
http://forum.xda-developers.com/showthread.php?t=1927769
Click to expand...
Click to collapse
Thanks, but I have tried that version, and the one newer (1.5.23). I did manage, efter some reinstalls, to get 1.5.18 (I think is was) to work on the real installation. So maybe my issue is with virtualbox, I just can't see what. I have disabled everything in linux that could block something, I have disabled firewall and such on the virtual windows, I have tried checking and changing perms on the linux device nodes, and tried running VB as root.
At least I got the Galaxy Y running again, but I don't like having unresolved issues so VB is going down