• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help I am literally at my wits end, please help before i toss it!

How about did the op put the drivers on the PC/laptop and when installing all the correct drivers she reboot the PC/laptop this will kill all background running process and also set drivers so they are ready when u plug the USB cord to the PC/laptop when she reboots
 
iowabowtech said:
If your devices still aren't being recognized, open windows device manager and while watching it, plug your device into the PC in USB debugging mode. We next need to verify that its at least being recognized as plugged in...even if its an unknown device. Look for any new entry to show up directly after being plugged in. Unknowns will show up as a yellow question mark most likely.
Click to expand...

one of the many times i have done this there was an exclamation yellow to pop up...that meant it was the wrong driver, yes?
 
Right. So earlier you mentioned you had another driver package. Was it zipped with a bunch of actual driver files inside? Or was it also an executable (.exe) file?
 
jujubeads said:
i have and have both.. which one is best? or right i should say
Click to expand...

Well, the .exe is easier but it seems you've already tried that without success right? If so, let's try to go the more manual route. We'll use the zip file that has all the driver files inside. Here's the plan:

-Unzip the whole works into a regular folder on your desktop. You can either unzip it into a folder of the same name or make a new folder with a name of your choosing.

-Now while watching device manager, plug in the phone while in USB debugging mode. Note the device that pops up as a yellow exclamation point. Then, right click on that unknown device and choose the option to update driver > update manually with your a file of your choosing. (I'm paraphrasing there, can't remember the exact Windows wording). Then navigate to the new folder (not the zip) on your desktop with all the driver files inside. Choose the ENTIRE folder as the destination of your driver(s). Windows will search the whole folder for the correct driver so you don't have to select a single driver file inside.

-If all goes will, it will apply the correct driver for adb/fastboot usage which, in device manager, should then show up as "adb interface" (or similar wording).
 
iowabowtech said:
Well, the .exe is easier but it seems you've already tried that without success right? If so, let's try to go the more manual route. We'll use the zip file that has all the driver files inside. Here's the plan:

-Unzip the whole works into a regular folder on your desktop. You can either unzip it into a folder of the same name or make a new folder with a name of your choosing.

-Now while watching device manager, plug in the phone while in USB debugging mode. Note the device that pops up as a yellow exclamation point. Then, right click on that unknown device and choose the option to update driver > update manually with your a file of your choosing. (I'm paraphrasing there, can't remember the exact Windows wording). Then navigate to the new folder (not the zip) on your desktop with all the driver files inside. Choose the ENTIRE folder as the destination of your driver(s). Windows will search the whole folder for the correct driver so you don't have to select a single driver file inside.

-If all goes will, it will apply the correct driver for adb/fastboot usage which, in device manager, should then show up as "adb interface" (or similar wording).
Click to expand...


YOU ARE SO INCREDIBLY AWESOME IM TRYING IT OUT NOW... I will message with the results!
 
iowabowtech said:
Well, the .exe is easier but it seems you've already tried that without success right? If so, let's try to go the more manual route. We'll use the zip file that has all the driver files inside. Here's the plan:

-Unzip the whole works into a regular folder on your desktop. You can either unzip it into a folder of the same name or make a new folder with a name of your choosing.

-Now while watching device manager, plug in the phone while in USB debugging mode. Note the device that pops up as a yellow exclamation point. Then, right click on that unknown device and choose the option to update driver > update manually with your a file of your choosing. (I'm paraphrasing there, can't remember the exact Windows wording). Then navigate to the new folder (not the zip) on your desktop with all the driver files inside. Choose the ENTIRE folder as the destination of your driver(s). Windows will search the whole folder for the correct driver so you don't have to select a single driver file inside.

-If all goes will, it will apply the correct driver for adb/fastboot usage which, in device manager, should then show up as "adb interface" (or similar wording).
Click to expand...



i forgot to ask... should i try this out on my phone or the gear? or does it matter? Positive end result lies in the gear though...:)
 
jujubeads said:
i forgot to ask... should i try this out on my phone or the gear? or does it matter? Positive end result lies in the gear though...:)
Click to expand...

Whatever u have driver files for and want a working adb connection with. You can use that method to install drivers for any device...just so you have the correct driver somewhere in that folder of course. :)
 
iowabowtech said:
Well, the .exe is easier but it seems you've already tried that without success right? If so, let's try to go the more manual route. We'll use the zip file that has all the driver files inside. Here's the plan:

-Unzip the whole works into a regular folder on your desktop. You can either unzip it into a folder of the same name or make a new folder with a name of your choosing.

-Now while watching device manager, plug in the phone while in USB debugging mode. Note the device that pops up as a yellow exclamation point. Then, right click on that unknown device and choose the option to update driver > update manually with your a file of your choosing. (I'm paraphrasing there, can't remember the exact Windows wording). Then navigate to the new folder (not the zip) on your desktop with all the driver files inside. Choose the ENTIRE folder as the destination of your driver(s). Windows will search the whole folder for the correct driver so you don't have to select a single driver file inside.

-If all goes will, it will apply the correct driver for adb/fastboot usage which, in device manager, should then show up as "adb interface" (or similar wording).
Click to expand...

ok... drivers are installed and reflect so in the DM.... im so flustered i forgot what to do next...lol ive spent so many days just trying to get the drivers installed...lol i feel like a moron!
 
:D

Well, if it's showing up now as "adb interface" or similar wording, then go ahead and open up cmd (command prompt) and enter the adb devices command from earlier. At that time, you MAY have to accept a prompt on your device's screen to allow authorization of the interface with the PC.
 
iowabowtech said:
well, the .exe is easier but it seems you've already tried that without success right? If so, let's try to go the more manual route. We'll use the zip file that has all the driver files inside. Here's the plan:

-unzip the whole works into a regular folder on your desktop. You can either unzip it into a folder of the same name or make a new folder with a name of your choosing.

-now while watching device manager, plug in the phone while in usb debugging mode. Note the device that pops up as a yellow exclamation point. Then, right click on that unknown device and choose the option to update driver > update manually with your a file of your choosing. (i'm paraphrasing there, can't remember the exact windows wording). Then navigate to the new folder (not the zip) on your desktop with all the driver files inside. Choose the entire folder as the destination of your driver(s). Windows will search the whole folder for the correct driver so you don't have to select a single driver file inside.

-if all goes will, it will apply the correct driver for adb/fastboot usage which, in device manager, should then show up as "adb interface" (or similar wording).
Click to expand...


it worked,
it worked,
it worked,
it worked,
it worked,
it worked,
it worked,
it worked,
it worked,
it worked,
it worked,

i am all good now!!!! Can i pay you somehow!!!!
 
You must log in or register to reply here.
Back
Top Bottom