Ok I spent a few days searching and I just can't seem to find anyone with the same problem!
I got a used T-mobile G1, can't bypass the activation screen (touching the 4 corners in the a certain order doesn't work, believe me i tried!) so I thought of installing the recovery through adb, except adb doesn't see it!
The only thing i see in Device manager or usbdeview is "HTC Android Phone Device" "K:\" under Portable Devices. I cannot update it to the Google drivers, not from here or from the SDK. I tried un-installing it, from device manager and from usbdeview.
I thought it might have been the data cable, so I ordered another one from a different seller off of ebay.
I think i should note that when in fastboot mode, pluging in the usb does not change where it says Serial0 to anything else. I would of thought it change to USB if cable is connected like the older HTC devices.
What am I doing wrong? You're help is appreciated.
Follow this guide, it should help you fix your problem.
Thanks for the reply. But I already tried this guide, every step.
First, this phone doesn't have a custom recovery, so I can't do any fastboot updates.
Second, windows does not accept replacing the HTC Android Phone USB Device with the usb drivers from the guide. It just says "The folder you specified doesn't contain a compatible software driver...". I'm using 64bit Win7 so obviously I'm using the 64 bit drivers. I tried 3 different downloads from different sites just to be sure the drivers weren't corrupt. The other odd thing is that the HTC ANdroid Phone USB Device is under Disk Drivers in the device manager...
Third, I tried uninstalling using USBDeview, but still Windows automatically installs drivers back as soon as i replug.
Fourth, I cannot bypass the Activation screen, so I can't set USB to debuggin mode.
I know it's hard to suspect that it could be the cable, but I ordered another one from different site just in case.
Most peeps say I should see 3 HTC devices in the device manager, but I don't. Only thing that pops up in there is HTC Android Phone USB Device under Disk drivers and "K:\" under Portable Devices.
Got another cable today and it still doesn't show any other device other then the one in Device Manager... I ran of out of things to try. Anyone can advise? It's possible that my device is defective even though it boots normally.
After playing around for a few days, ended up somehow rooting and flashing Amon's latest recovery and then BAM windows detected new device and install the ADB interface.
Related
I've flashed 6-8 ROMS on a couple different phones, so not a total noob, but I bow to the vastly superior knowledge here:
My Captivate was running CM7.1 stable from October with no further mods since. I hadn't flashed anything or really messed with the phone in awhile. I was just using the same phone in the same config I had been for 6 months.
A few days ago, CM7 started to force close all my programs. Annoying, but not a problem that rebooting wouldn't probably fix. Rebooted into bootloop (skater logo). 3 Button didn't put me into CWM Recovery, nor would any button combos get me to download mode.
Homemade a jig and got the phone into Download mode, with Odin One Click up and ready to flash to stock. Odin read the phone and I started the flash, but it hung at DO NOT TURN OFF TARGET for a couple hours. I checked on this forum to see what was next. All the previous posts just said to pull battery, re-jig, and start again.
This time, I didn't get the skater, I got the comp!phone. All button & USB combos I've read here bring me comp!phone (even the "hold until two blank screens" one). My PC won't recognize the phone now (so neither will Odin or Heimdall), even after I've reinstalled the Samsung drivers. I've read here that you can flash from the comp!phone screen, but the PC has to see your phone first, obviously.
So I guess I want to know how screwed I am. Magic tips on a easy fix would be just outstanding, too! Is the fact that I wasn't flashing or anything when it bombed interesting to anyone? Thanks in advance...
not sure it's identical but this worked for me: http://forum.xda-developers.com/showthread.php?p=15330252#post15330252
OP,
Check out the "Connection Issues..." Stickied Thread in this forum.
Sent from my SAMSUNG-SGH-I777 using xda premium
Zadig won't load drivers for Heimdall 1-click
I'd tried Heimdall 1-Click Unbrick, but the problem again seems to be with the phone not being recognized. Unbrick runs, fails, and asks if the phone is plugged in.
It refers me to the Resolution Center, where Zadig tries to load the driver, for Captivate, but can't. Zadig provides a dropdown list of devices (my cam, printer, mass storage devices, wireless mouse/keyboard etc.), but the phone isn't listed, and I've tried every USB port. Which is too bad, because that seems like a great tool.
macbuckets said:
I'd tried Heimdall 1-Click Unbrick, but the problem again seems to be with the phone not being recognized. Unbrick runs, fails, and asks if the phone is plugged in.
It refers me to the Resolution Center, where Zadig tries to load the driver, for Captivate, but can't. Zadig provides a dropdown list of devices (my cam, printer, mass storage devices, wireless mouse/keyboard etc.), but the phone isn't listed, and I've tried every USB port. Which is too bad, because that seems like a great tool.
Click to expand...
Click to collapse
If you are still stuck...
Did you actually load a full version of Heimdall? Once I used unbrick as a mini-program. Another time I had to install a full version on my computer in order to get my phone and computer to communicate (that may be the missing driver step).
I know you have probably already done so but search the threads for AdamOutler and his work with Heimdall.
If you're using windows, windows update might be installing the drivers automatically. You might want to disable this feature, uninstall the current drivers and install new ones.
You can also try another pc that doesn't have any installed drivers - just to make sure...
Sent from a Captivate using XDA
macbuckets said:
I'd tried Heimdall 1-Click Unbrick, but the problem again seems to be with the phone not being recognized. Unbrick runs, fails, and asks if the phone is plugged in.
It refers me to the Resolution Center, where Zadig tries to load the driver, for Captivate, but can't. Zadig provides a dropdown list of devices (my cam, printer, mass storage devices, wireless mouse/keyboard etc.), but the phone isn't listed, and I've tried every USB port. Which is too bad, because that seems like a great tool.
Click to expand...
Click to collapse
Did you try manually installing the Samsung/Google usb drivers ? That's the usual culprit since stock are Samsung drivers and roms ( if its Aosp/Cyanogen) the Google drivers prime in that case.
Nearly Identical Problem
I've got the same problem with my Captivate...tried everything I've found in the forums but nothing works.
Background:
I had connection issues before trying to flash, but thought it was a driver issue with my Windows 7 machine. Which is why I had loaded the file onto the SD card when I attempted to upgrade to ICS. During the flash the phone hung and I eventually removed the plug and battery to see if I could reboot. I can get up to the Galaxy S I9000 screen, or the "Downloading..." screen, but I cannot get to the recovery menu or past the initial boot screen. My wife's captivate (same batch) IS recognized by the computer in "download mode" and in the USB transfer mode.
Attempts:
- Installed/uninstalled Kies many times
- Bought and tried a new data cable
- Installed/uninstalled the Galaxy S driver and the Captivate driver many times
- Tried Zadig, Odin, Heimdale, and Adb
- Used programs to remove USB devices and clean registry
- Installed Linux and tried within that OS
- Re-installed Windows 7
- Tried most of the above on my Windows XP system
Has anyone been successful in getting the computer to recognize a Captivate in this circumstance?
macbuckets said:
I'd tried Heimdall 1-Click Unbrick, but the problem again seems to be with the phone not being recognized. Unbrick runs, fails, and asks if the phone is plugged in.
It refers me to the Resolution Center, where Zadig tries to load the driver, for Captivate, but can't. Zadig provides a dropdown list of devices (my cam, printer, mass storage devices, wireless mouse/keyboard etc.), but the phone isn't listed, and I've tried every USB port. Which is too bad, because that seems like a great tool.
Click to expand...
Click to collapse
if u r still facing the problem..and problem isnt solved then just clean the pin of usb connector pin of ur phone...with a thin metal pin..or something like that...
and then u r good to go...
If all else fails...
I managed to brick my Captivate trying to get MUIU off my phone and flash back to Cognition. After many frustrating hours, I contacted Josh at mobiletechvideos.com. He fixed my phone and upgraded me to ICS for $50.00. I mailed my phone to him on a Thursday and received it back the following Friday.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
Hi there so I today truied to update to Eagles Blood custom Rom using Rom Manager to flash the new rom onto my O2x. The rom supposedly installed correctly but then when it booted it just gets to the unlock screen you unlock it then it reboots after a couple of seconds.
I can't get into recovery mode by the usual power on volume down technique as this just results in the phone continuing to load. I have tried different combos of power button reboots with volume button up, volume down and both together none work the only difference is that one of those results in just the LG logo rebooting.
I read a few posts about using nvflash or even the lg recovery tool using imei number etc but still no dice basically when I do the connect to the pc with both volume buttons pressed and the battery out it connects but doesn't recognise the device. I try the device manager and updating or removing the driver but regardless of how and what I try it either tells me it's using the most current driver or that no driver is actually installed.
This the same when using NV Flash i can't apx drivers installed and the device if I try to skip that step and go straight to the flash.bat command i just get usb device not found or connected or something like that.
Please help i am willing to try anyrhing and i really don't have the money for a new phone. I only have to get it working long enough or far enough so i can reinstall my backup i did before attempting the rom install this morning.
try connecting to different usb port(I suggest the backport of your PC)
and if that didn't work, must be a faulty cable.
genemini said:
try connecting to different usb port(I suggest the backport of your PC)
and if that didn't work, must be a faulty cable.
Click to expand...
Click to collapse
Unfortunately the cable is fine as if I'm not holding the power or volume keys I'm charging the batteries. I'm thinking there's something wrong with windows and the way it detects it possibly as i've trawled a fair amount of forums and tried a lot of what others have managed to get working with exception to someone else who had the same problem but couldn't get a resolution (that he posted about).
May be your USB port was broken.
Have you actually installed the apx drivers required for nvflash to work?
http://www.modaco.com/topic/335416-nvflash-setup-instructions-drivers-links-active/
Sent from my LG-P990 using Tapatalk 2
you're not on Hard Brick, right?
can you try Smartflashing?
you need to install LG united drivers first.
APX won't install
So the problem is that my PC will pick up the unknown device. But it will not allow the install of the drivers. I can install the LG universal driver. The phone will connect as a unknown device only with error code 43 (device has been stopped) you try installing the APX drivers and the install of those drivers fail with error code 10 (can't start the device) this happens on both my stuffed phone and the brand new replacement so I am at a loss I have tried this on Windows 7 pc and also a Win 7 laptop (64 bit and 32 bit respectively).
The whole affair is frustrating as hell as I an't get my new O2x recognised either I can't root that to put my nandroid backup on and I am stuck on Froyo that I can't seem to root at all or even use lg update tool to update it to the latest stock firmware.
WHat about rooting apps
So with the obvious ways not working are there any actual apps I can install on my phone that will root it that way I am certain this is how I did it on my first O2x just can't remember what the name of the app was. So if anyone has apps or links to apps that may do this and or do do this please post back.
Have you actually tried a different USB cable? I notice you said the cable charges the phone, but this doesn't mean that other cores/pins other than the ones used for charging aren't damaged.
Sent from my LG-P990 using Tapatalk 2
different windows and different drivers
My suggestion would be try it on some other computer and different drivers. Or on same computer but reinstall Windows and ofc different drivers.
I'm suggesting this because I had experienced some what similar things on LG phones.
For whatever reason, when I'm trying to get my Token ID, I get as far as entering fastboot, and when trying to get the second command prompt to retrieve my token, it just gets stuck at "Waiting for Device".
I've made sure I'm using a USB 2.0 port ON THE BACKSIDE of my PC (I've tried 3.0, and front ports as well, all yield the same results)
USB debugging IS ENABLED.
I've tried with, and without fastboot disabled.
I've tried uninstalling ALL android related drivers on my PC, and re installing ONLY the HTC ones (I have a rooted nexus 7 2013 as well)
nothing seems to make a difference, everything works great right up until my device reboots into fastboot, then it becomes unrecognisable.
At the same time, windows shows a failed driver installation ONLY AFTER I unplug the device, and it shows it trying to install "HTC MTP DEVICE".
I've run out of ideas for a way to fix this by now, anyone have any other suggestions?
Install the driver from here and re try
However, i think is better unlock without a toolkit, but it's a choise
Toolkit's are usually just easier for me, I've only owned 3 different android devices.
My old Inspire which I rooted manually
My 2013 Nexus 7, rooted froma kit
and my HTC One, which is the only device I've encountered problems with so far.
Edit: I just attempted it yet again with the drivers you linked, still stuck at waiting for device.
Edit2: THANK GOD I FINALLY GOT IT WORKING!!!!!
When my phone boots into bootloade,r it runs on an "Android 1.0" driver. I went into my device manager, and updated that "Android 1.0 device" with the drivers you linked above, and everything magically connected, and I can now get my token ID!!!
I am having issues with my Nexus 6. I am unable to get it to connect to any computer. Windows says the device is malfunctioning, but it charges okay. Windows gives the error "Device descriptor request has failed." It doesn't matter if I'm booted, in fastboot, or have the phone off, it gives that error.
What I have tried:
Toggled USB debugging, MTP, and PTP.
Nexus Root Toolkit to try to install the drivers
15 Second ADB Installer by Snoop05
Alternate drivers (Naked, Generic, PDA).
Each time I have tried new drivers, I have checked to uninstall anything using USBDeview.
Tried "Updating drivers"
Tried three different Windows machines.
Tried different USB cables
USB 2.0 and USB 3.0 ports
Cleared cache partition
I think I am down to two things: Factory reset or draining my battery all the way and letting the hardware reset itself. I am not confident that factory resetting it will work since this same message pops up in the bootloader.
I have researched the hell out of this and one person in this section was having similar issues but got it working when plugging it into their USB 3.0 port. If those last two things do not work, then I don't know how the hell I'm going to lock the bootloader to get it worked on--that's the only thing I have done to it as far as modification wise (/system is stock, no root).
Any help is greatly appreciated. This is so frustrating since using USB is our way of working on these damn things. If I could get root without having to use USB, then I could easily lock the bootloader back.
Does anyone know how to re-lock the bootloader without root or using USB? At least I could have it locked so I can RMA it.
In your device manager see if you see the device with a yellow exclamation mark. If so right click it properties select update driver and then choose the driver option and it will give you a list of things to select.
bluh5d said:
In your device manager see if you see the device with a yellow exclamation mark. If so right click it properties select update driver and then choose the driver option and it will give you a list of things to select.
Click to expand...
Click to collapse
Doesn't work, I'm afraid. Windows says it already has the best drivers for the device. The device simply is not telling Windows what it is. Thanks for your reply.
dijit4l said:
Doesn't work, I'm afraid. Windows says it already has the best drivers for the device. The device simply is not telling Windows what it is. Thanks for your reply.
Click to expand...
Click to collapse
I've come to understand that USB problems are generally Windows' fault (i.e. Windows itself or poorly written drivers) rather than the device's fault. Not always, but the vast majority of the time.
See if anything in this article helps - installing the Google USB driver worked for me:
http://www.theandroidsoul.com/nexus-6-driver-adb-fastboot-mtp-windows-mac/
HTH...
right click the file then go to update driver than select browse my computer then at bottom select let me pick.
Tiptonian said:
I've come to understand that USB problems are generally Windows' fault (i.e. Windows itself or poorly written drivers) rather than the device's fault. Not always, but the vast majority of the time.
See if anything in this article helps - installing the Google USB driver worked for me:
http://www.theandroidsoul.com/nexus-6-driver-adb-fastboot-mtp-windows-mac/
HTH...
Click to expand...
Click to collapse
Thanks for your reply. However, I have a hard time thinking that three Windows machines are experiencing the same thing. I have successfully gotten it connected before the 5.0.1 update to transfer ringtones. I even booted into Linux Mint and couldn't get it to connect either. It's like the controller is bad but it can still charge.
Also, I have followed every direction on your link at least twice already.
bluh5d said:
right click the file then go to update driver than select browse my computer then at bottom select let me pick.
Click to expand...
Click to collapse
Thanks for your suggestion. I have tried this and Windows refuses to use the proper drivers. It argues they aren't for 64-bit OS, but they have worked in the past. I almost got it to use some Samsung drivers, but after it installed, no change. The device is not reporting the details it needs to convey to the computer to start a proper driver setup.
I have not been able to connect either. Tried 2 different Nexus 6 devices, numerous reboots, different cables, different USB ports and all the stuff you tried also to know avail. I updated drivers, went through device manager, but I can connect when I switch from MTP to pictures, however you don't get the same access.
HotInEER said:
I have not been able to connect either. Tried 2 different Nexus 6 devices, numerous reboots, different cables, different USB ports and all the stuff you tried also to know avail. I updated drivers, went through device manager, but I can connect when I switch from MTP to pictures, however you don't get the same access.
Click to expand...
Click to collapse
To me, it sounds like you have a glimmer of hope. Have you tried a different computer? If you don't have a different computer handy, boot Linux from a flash drive and install fastboot and adb.
I recently tried to install PureNexus 7.1.2 along with the latest version of GApps 20170610. There seems to be some sort of conflict with that version of Google Play Services that prevents my device from completing setup. Without completing setup, I'm not able to do anything with the phone.
In an attempt to save myself, I want to go back to the older version of the ROM and GApps that worked, but first they need downloaded. In the past, I could go into TWRP and mount my device to my PC and transfer the files I needed to install. Now, Windows is showing my device as Unknown USB Device (Device Descriptor Request Failed). Going through every thread I could find about updating drivers, etc, it still does not work. This used to work just fine in the past on the same PC (Windows 10).
Both adb and fastboot don't seem to work either. There is no device found. When I boot the phone into Bootloader mode and plug in the USB cable, it shows Transfer Mode: USB Connected but running fastboot on the PC still can't find anything.
I am not sure how else to go about getting the necessary files on the device to flash them.
For what it is worth, I was able to get the ROM booted enough to connect to my Mac via Bluetooth and am able to transfer a file that will hopefully work. It still doesn't explain why USB can't connect. I have tried it against (2) Windows 10 PCs and my Mac with 4 different USB cables, one of which I went out a purchased today because of the issue. I am beginning to think something internally has failed on the device.
tristanlee85 said:
For what it is worth, I was able to get the ROM booted enough to connect to my Mac via Bluetooth and am able to transfer a file that will hopefully work. It still doesn't explain why USB can't connect. I have tried it against (2) Windows 10 PCs and my Mac with 4 different USB cables, one of which I went out a purchased today because of the issue. I am beginning to think something internally has failed on the device.
Click to expand...
Click to collapse
It could be just a dirty usb port.
Where's answers
ktmom said:
It could be just a dirty usb port.
Click to expand...
Click to collapse
Unfortunately I do not think that is the case. I have used a number of different means to clean the connection with rubbing alcohol and electrical terminal cleaner, small utensils to get in there and clean the contacts, but no luck. I am to the point now where the phone won't boot up the OS. I can get into TWRP and the Bootloader, but from there I have no way to transfer files to the device.
Bluetooth was my option before, but that is when the device would boot. There's no way to enable BT from recovery right? I am trying to reset the phone back to stock to trade it in to Google, but I am afraid I am going to be out $100 since it seems to be as good as dead now.