Database Users

ADB Device Not Found! :(

OK, posted this in the Q&A section with several responses but no real answers. Figured I'd post it here before another section where it might get locked or moved.
Anyway, ADB was working fine until a few days ago. Now it says "error: device not found." Fastboot still works just fine. I've tried everything I can think of to get it working again. I've uninstalled and reinstalled the usb drivers, removed the Android SDK from my PC and reinstalled, wiped and reflashed my device, made sure Debugging is on, and tried getting ADB to work on all 4 of my PC's. All running either Windows XP or Windows 7. No dice. Can anyone help? Thanks in advance.

The other day it took me about an hour to remember to just turn on usb-debugging and plug it in to the usb drive. I kept going to the fastboot screen instead. Maybe that's your problem too?

UnderCoverLover said:
The other day it took me about an hour to remember to just turn on usb-debugging and plug it in to the usb drive. I kept going to the fastboot screen instead. Maybe that's your problem too?
Click to expand...
Click to collapse
Thanks for the reply. If you read my OP you'll see that I've made sure debugging is on. In fact, debugging is also enabled by default after a wipe and clean flash. Unfortunately my problem isn't as simple as enabling usb debugging.

Have you gone from one phone to another? When I made the switch from a tmo->att n1 I had to remove ALL drivers before installing them again in order for my phone to work.
Perhaps try removing ALL drivers and starting fresh?
In Envrionmental Variables, create a System variable:
variable name: devmgr_show_nonpresent_devices
variable value: devmgr_show_nonpresent_devices
With your phone not plugged into your pc, go to device manager and under the View menu, select "show hidden devices".
Remove everything under ADB. Remove anything in unknown devices that says Nexus1 or Android, or Google. Remove the Composite Devices under USB (they will be added back upon reboot if the system uses them) as well as the Mass Storage Devices.
Reboot your system. Plug your phone in and update/install your drivers for your phone.
I used both the drivers from the sdk and from http://forum.xda-developers.com/showthread.php?t=613217 to have fastboot and adb functional.
Good luck!

deprecate said:
Have you gone from one phone to another? When I made the switch from a tmo->att n1 I had to remove ALL drivers before installing them again in order for my phone to work.
Perhaps try removing ALL drivers and starting fresh?
In Envrionmental Variables, create a System variable:
variable name: devmgr_show_nonpresent_devices
variable value: devmgr_show_nonpresent_devices
With your phone not plugged into your pc, go to device manager and under the View menu, select "show hidden devices".
Remove everything under ADB. Remove anything in unknown devices that says Nexus1 or Android, or Google. Remove the Composite Devices under USB (they will be added back upon reboot if the system uses them) as well as the Mass Storage Devices.
Reboot your system. Plug your phone in and update/install your drivers for your phone.
I used both the drivers from the sdk and from http://forum.xda-developers.com/showthread.php?t=613217 to have fastboot and adb functional.
Good luck!
Click to expand...
Click to collapse
Thanks for the response. I'll give this a shot when I get home. FYI, I didn't change devices. Same Nexus One I've had for the past month. Just one question: When you say,
"In Envrionmental Variables, create a System variable:
variable name: devmgr_show_nonpresent_devices
variable value: devmgr_show_nonpresent_devices"
I don't know what this means. Where can I access this? Thanks!

Just a thought but are you remembering to boot up the phone as normal?
As in not into fastboot, etc.
This stumped me for a few hours.
I kept trying to "adb" while the phone was in fastboot or recovery.
Sorry if I'm teaching you to suck eggs.

markouk said:
Just a thought but are you remembering to boot up the phone as normal?
As in not into fastboot, etc.
This stumped me for a few hours.
I kept trying to "adb" while the phone was in fastboot or recovery.
Sorry if I'm teaching you to suck eggs.
Click to expand...
Click to collapse
Yeah, I've had the phone booted up normally. Thanks though.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

MaximReapage said:
Click to expand...
Click to collapse
Thanks a lot.

deprecate said:
Have you gone from one phone to another? When I made the switch from a tmo->att n1 I had to remove ALL drivers before installing them again in order for my phone to work.
Perhaps try removing ALL drivers and starting fresh?
In Envrionmental Variables, create a System variable:
variable name: devmgr_show_nonpresent_devices
variable value: devmgr_show_nonpresent_devices
With your phone not plugged into your pc, go to device manager and under the View menu, select "show hidden devices".
Remove everything under ADB. Remove anything in unknown devices that says Nexus1 or Android, or Google. Remove the Composite Devices under USB (they will be added back upon reboot if the system uses them) as well as the Mass Storage Devices.
Reboot your system. Plug your phone in and update/install your drivers for your phone.
I used both the drivers from the sdk and from http://forum.xda-developers.com/showthread.php?t=613217 to have fastboot and adb functional.
Good luck!
Click to expand...
Click to collapse
Followed all of these directions, reinstalled the driver, and I still can't connect via adb. Still getting "error: device not found." Help!

Part Four said:
Followed all of these directions, reinstalled the driver, and I still can't connect via adb. Still getting "error: device not found." Help!
Click to expand...
Click to collapse
Try to download the latest Android SDK and have it installed again. Also download the USB drivers within that package...

myn1 said:
Try to download the latest Android SDK and have it installed again. Also download the USB drivers within that package...
Click to expand...
Click to collapse
Done and done, days ago. Still no dice. This is ridiculous.

Still having problems. Tried everything I can think of, and everything suggested to me by the XDA community. I don't know if this will help any of you guys help me, but when I type "adb devices" into a command prompt, it returns:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
And then shows nothing. So effing frustrating! EVERY computer I have (I actually have tried it on 6 different laptops and PCs) returns the same error and cannot find my Nexus One. WTF happened!? HELP!

Part Four said:
WTF happened!? HELP!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=613217

pvillasuso said:
http://forum.xda-developers.com/showthread.php?t=613217
Click to expand...
Click to collapse
I'm sure you're trying to be helpful but, if you've read through this thread, you'd know that I've already done all of that. OBVIOUSLY, I've done all of that because, like I said, ADB STOPPED working. In order for it to stop, it must have, at some point, worked just fine. And it did. It worked perfectly until recently. So, yes, I've installed all the damn drivers I need. But, no, it's still not working. It's infuriating.

debugging mode os on? did you open adb, delete all htc drivers then reinstall them from the sdk. not just install them but delete and then reinstall.

also once in bootloader your good, some instructions say go into hboot, not for me, just right in bootloader, not hboot.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk

temperbad said:
debugging mode os on? did you open adb, delete all htc drivers then reinstall them from the sdk. not just install them but delete and then reinstall.
Click to expand...
Click to collapse
Yes. *Sigh*

Do you see this device ( pic ) @ device manager :
If you do , there is no reason for adb commands under DOS prompt for not workig well ... really weird

temperbad said:
also once in bootloader your good, some instructions say go into hboot, not for me, just right in bootloader, not hboot.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
What do you mean, I'm "good?"

[GUIDE] Noob's Guide to setting up ADB

How to get working ADB-- The Expedient method
Since the release of the mtd ROMS the importance of being able to use ADB has greatly increased. This guide is designed to produce a working adb evironment in windows. It is designed be as simple as possible and to avoid command line as much as possible. This guide is not targeted towards advanced users who can set up a working adb environment on their own. If you can setup adb from Google's packages, please avert your eyes and read no further -- this guide will only bring out the elitist snob in you.
If you are still with me you have likely tried to set up adb and failed. Perhaps you have a bootloop in an mtd (cm7, miui, OMFGB) ROM and are trying to avoid losing everything with an Odin flash. Perhaps you are trying to troubleshoot in another way. Regardless, this guide will get you going.
Step 1: Install USB drivers.
A) If you are using a Touchwiz based ROM (COMROM, Evil Fascinate) you will need the Samsung Fascinate driver.
B) If you are using a MTD based ROM (ICS, CM7, MIUI, OMFGB) you will need to use the Nexus S drivers.
Step 2: After you install the appropriate driver, put your Fascinate into Debugging Mode by:
Gingerbread: Settings->Applications->Development then checking Debugging Mode.
ICS: debugging mode is found System Setting>Developer Options>USB Debugging.
Step 3: Connect your phone to your computer and open up Device Manager.
Step 4: DON'T SKIP THIS STEP. You will see Fascinate/Nexus S with possibly an exclamation mark, just double-click on it, Update Driver->Browse my computer for driver software->ADB Interface then choose Samsung Electronics Co., Ltd, then choose Samsung Android ADB Device.
Step 5: Download and install Droid Explorer. Please select the appropriate build for your PC architecture. Be sure to select "Set up the Android SDK For Me" during the setup.
Step 6: Launch Droid Explorer and select your phone.
To send ADB commands click the button in the red box in the image below.
To view logcats click the button in the blue box below.
Step 7: How to use Droid Explorer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Troubleshooting example:
You are on AOKP and set a bad overclock as boot settings. 3-fingering is a no-no and you get frozen during boot or a bootloop before entering the OS and therefore can't reach recovery. To get into recovery click the button in the red rectangle. Then type "reboot recovery" at any time during the phone boot process and press enter. Your phone should reboot and you should end up in recovery. Success!

I have a fully Functional adb, android skd, java, eclipse, all the stuff needed for a proper build environment, and I still use Droid explorer and Android Commander, for some things. Once you get used to these programs they are very useful especially for a simple app swap or adding an app to your system file. Good of you to share the process with others.

Nice guide, would have been easier than setting up a full adb environment on my work pc in addition to my home pc. Where was this 6 months ago?

Dude thank you so much for that nexus driver. I have not been able to get my ADB to work until now with that driver. Every other one I got wouldn't work and no one really could help me. Just kept saying install driver. Now ADB finally works. The Droid Explorer program is pretty cool too. Thanks very much!!

I've edited the guide a bit to make it easier to follow. This should be the final version of it unless someone has an issue or suggestion. I'm glad this has helped some folks and I hope it will continue to do so.

ok somethings wrong because i have followed every freaking guide there is including the wiki for cyanogenmod and this one and adb is still "not a valid command" or whatever in the command prompt......freaking hell
**now all of a sudden it's kinda working, if i choose reboot into recovery from the application it just reboots the phone, not into recovery.....and if i choose the log icon it says it cant connect to device even though the device is clearly shown as connected in the main screen......sheesh
THANK YOU MAKE THIS STICKY NOW OR I WILL PUNCH BABIES

Have went through the process three times all with the same result. Explorer doesn't see my phone. Any ideas?
Using the Nexus drivers (running CM7)
Drivers installed properly.
Using the 64 bit explorer (running Windows 7)
debugging checked

Just passing along a thanks for this guide in a world where OC/UV is so easy to screw up.

sfobrien said:
Have went through the process three times all with the same result. Explorer doesn't see my phone. Any ideas?
Using the Nexus drivers (running CM7)
Drivers installed properly.
Using the 64 bit explorer (running Windows 7)
debugging checked
Click to expand...
Click to collapse
During the DroidExplorer setup process did you tell it to "setup adroid sdk environment for me"? It should have been a blue link.

bobloblaw1 said:
During the DroidExplorer setup process did you tell it to "setup adroid sdk environment for me"? It should have been a blue link.
Click to expand...
Click to collapse
Yes and it appeared to install correctly.

+1 for sticky

sfobrien said:
Have went through the process three times all with the same result. Explorer doesn't see my phone. Any ideas?
Using the Nexus drivers (running CM7)
Drivers installed properly.
Using the 64 bit explorer (running Windows 7)
debugging checked
Click to expand...
Click to collapse
I have a different but similar issue. It sees my device when connected and disconnected but I can't do anything. If I choose reboot it rebooted. If I choose reboot recovery it just rebooted, no recovery. I can see the devices tree directory but if I try to access any of them I get an error. Also if I click the logcat button it opens the terminal window but has an error, says it can't connect or something. If I click on the terminal button it opens the terminal but no commands are recognized. But when I connect and disconnect my device it shows up and in device manager there are no errors.

Hmm are you sure that the USB cable you are using is still good? will it mount for data transfer?
Also, this generally shouldn't be necessary but it is possible that something is messed up in your PC USB install. At one point I had to clear off and reinstall all of my USB drivers. Everything worked fine after the drivers reinstalled.
There's a lot of places where errors come in. I'd like to try and figure out your guys' problem(s) so that I can update the guide and potentially save other people some time.

I just set up adb on my arch linux box, I think it was easier to set up this vs windows.
Sent from my I500 using XDA Premium App

allcity187 said:
I just set up adb on my arch linux box, I think it was easier to set up this vs windows.
Sent from my I500 using XDA Premium App
Click to expand...
Click to collapse
Probably. But that requires you to have a linux box setup and handy; which many people do not have.

Well you can always dual boot your computer. I have windows 7 and arch linux set up. I'm usually on linux but I still have software that I use on windows, so that's why I kept it.
Sent from my I500 using XDA Premium App

bobloblaw1 said:
Hmm are you sure that the USB cable you are using is still good? will it mount for data transfer?
Also, this generally shouldn't be necessary but it is possible that something is messed up in your PC USB install. At one point I had to clear off and reinstall all of my USB drivers. Everything worked fine after the drivers reinstalled.
There's a lot of places where errors come in. I'd like to try and figure out your guys' problem(s) so that I can update the guide and potentially save other people some time.
Click to expand...
Click to collapse
My USB cable is fine. Went back uninstalled the drivers and explorer. Downloaded fresh copies of both and same thing????
Giving up for now. In the event of a crash I can Odin back,rebuild,restore apps, etc. in about an hour. Less time than I have spent trying to get this to work! LOL. For now I'm back on the stock CM7 kernel and not doing any tweaking that might cause a crash. All is good thanks guys.

sfobrien: Sorry I couldn't get thisto work for you.
jamesandmandy: Did you ever flash anything in red recovery? Are you able to get into blue recovery by the normal method? Your issue sounds like something on the phone recovery end if You are able to send commands to it successfully over adb.

bobloblaw1 said:
sfobrien: Sorry I couldn't get thisto work for you. /QUOTE]
Hey no problem. I think it is some kind of glitch between Windows 7 and the explorer program. CM7 is an awesome upgrade so no complaints here.
Click to expand...
Click to collapse

Thanks for this. I've always avoided adb because it seemed to complicated to setup/learn. I'm up and running.
Sent from my GT-P7510 using XDA Premium App

[Tool][Windows Only][Root] Android Reverse Tethering 3.19

Android Reverse Tethering for windows users.
Tethering is the ability to surf on your pc using the 3g of your phone
Reverse tethering is the opposite : surf on your phone using the ADSL of your PC. No Wifi or 3G connection required.
==>Troubleshooting (FAQ) <==
Since a lot of users don't read the full article before asking for help, I will start by this section !
Not yet compatible with Android 5. Work on progress. Don't ask me when it will be available
Android 4.3 and upper : You must install the Connectivity hack (see Connectivity hack section) before connect .
Android 4.3 and upper : You must connect your phone/tablet to a working wifi or 3g once after each boot before using reverse tethering !!!
This work only for rooted users and with Windows. Don't ask for linux or for some fruit operating systems !!!
The tool is not compatible with "CrossBreeder" , "adaway" or other tools that change the host file (removing localhost)
Tethering and reverse tethering (this tool) are not compatible at the same time, it's then not possible to turn your android phone as a wifi hotspot.
If your device is not listed in the "select a device" dropdow list:
Ensure Usb debugging is enabled. See "Before starting the tool" section
The ADB subsystem is sometimes not working properly. Click the "Kill ADB" button (on Tools)
Your device is perhaps not installed properly. See your device manufacturer. You can download a generic driver from google here : http://developer.android.com/sdk/win-usb.html.
Windows can detect your device as a "Media Transfer Protocol" (MTP) or "Picture Transfer Protocol" (PTP). When you connect the usb cable, you can receive an "Usb" notification. Click the notification to change this parameter. If one don't work, take the another one...
Click refresh or restart the tool to detect your device.
If the connection shutdown often, try another usb cable
Proxies problems :
Corporte proxy. The windows application is not able to traverse proxies.
The good news is that you can use some applications like FreeCap , sockscap and proxifier.
You must start the androidTool from one of these launchers, giving proxy adress and port.
Thanks "edgd1er" for the information.
Android 3G proxy. Even if 3g is desactivated, your provider (APN) proxy may still be used by applications.
The windows tool is not able to communicate with your provider proxy.
Note that only a few providers include a proxy. You must remove it manually.
The tool will give you informations on how to do it when detected.
Installation :
Unpack the zip file. This zip files contains the windows part, ADB and the android APK.
Before starting the tool :
You must install drivers for your device.
If you don't find drivers for your phone/tablet, check the Universal Naked Driver
Other interesting tool to install Adb and drivers (32/64) : [TOOL] ADB, Fastboot and Drivers - 15 seconds ADB Installer .
Some screenshots are availables in this thread to install the driver.
Ensure you have debugging enabled on your phone :
Settings > Applications > Development > USB Debugging > Turn On
Ensure you have root access AND SuperUser application installed.
Change the superuser settings (Menu -> Preferences -> Notifications part) :
Uncheck "Notifications" label to display "Do not show notification when an app is granted Su Permissions"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AndroidTool
The AndroidTool.exe is the windows part
The low level communication tool (ADB) is included in the zip file.
AndroidTool will try to find ADB in c:\android-sdk-windows\platform-tools\adb.exe
If not found he will use the provided one.
The first time you use the program :
If you want to use another version of ADB, clik "config" and in the first tab enter the path to the ADB
Select the DNS server to use in the right list. On complex system, some dns can be detected.
Start reverse tethering
Just click “Connect”.
If it's the first time you use the program, This will install the latest android package and the dependencies (busybox and redsocks).
The SuperUser process may ask you to allow “Usb tunnel”
If the android process crash after receiving superuser rights, close the windows program and start again.
The android interface (first tab) will show connections forwarded to windows.
Others tabs are just for debugging. Send the log on this thread in case of problem.
Start your browser
Google chrome will complain that no connection is available. Don’t care. That work.
Firefox , opera and dolphin don’t have problem with that !!!
The current version of the application can’t forward low level ICMP packet (PING).
From Android Os point of vue, there is no internet connection.
Command line prompt :
The windows tool is a "One click" application. Just click the "Connect" button.
But you can add parameters to directly connect when the program start.
Here are the supported commands : Device:xxxx (where xxxx is the device id), Connect, Disconnect, KillAdb, LogToClipboard, Show, Hide, Quit
Parameter sample : Device:123465789 Connect Hide
Create a second shortcut with Disconnect Quit parameters to stop connection and close the application.
Connectivity hack :
This will install some low level program to install a "fake" Wifi for browsers and google play market.
Don't worry, I didn't brick my phone and tablet during the development.
The Xposed framework author and me are not responsible for anything you do with your phone/tablet/rice cooker.
This work for android 4.X, but an experimental version of the Xposed framework for Gingerbread made by liudongmiao can be found here: http://forum.xda-developers.com/showthread.php?p=44034334#post44034334 (no support from my side)
On the windows program, go to tools tab and click "install hack"
Launch the Xposed Installer (you just installed) on your android and click on "Install/Update"
Go to the module tab and check the HackConnectivityService (see screenshot below)
Reboot the phone
Done!
This work for market but also for some other programs (some games,skype,hangouts...)
For older android 2.x or 3.x version :
The application want to have an active 3G or Wifi network interface.
Some market applications are tagged "Wifi" only.
To get around this problem, you can activate the 3G BEFORE starting reverse tethering,all the data will goes to the usb.
Tips : You can connect to some wifi hotspot not protected by a key.
It's only when you want to surf that the hotspot ask you a user/password.
But, at this point, we have an 'active' connection. Market download should work after starting reverse tethering.
Not fully working application but work if you install the HackConnectivityService on android 4.x:
Market download
Spotify
Skype. (not checked yet)
If someone know another one, post a reply !
History :
Version 3.19
Added some rights for sdcard access.
New windows icons.
Version 3.18
Fixed Xposed HackConnectivityService module. You must click "install hack" to update it
Small bug fix.
Version 3.17
Updated Xposed framework installer 2.4.1
Small bug fix.
For Linux ,Mac OS X , I recommand this guide (from @phamthanhnam ) : http://forum.xda-developers.com/showthread.php?t=2287494 .
This required entering a lot of manual commands on both android and the PC each time you want to connect (reserved to power "geek" users).
This work also for windows, but much more complicated, compared to this "One click" connect tool. I let user chose the solution he want...
I will not respond to email or private message. If you want support, post a reply on this forum.
Do you like this program ? Want to make a donation ? Send any amount to my paypal account (click the donate button on left)
Please read FAQ on top of the page before asking for help.
Older versions were removed (416611 downloads)

capslock66 said:
Unpack the zip file. This zip files contains the windows part, ADB and the android APK.
You MUST uninstall previous version. If you don’t find it, run a dos command prompt on the installation folder and enter this command : Adb uninstall service.tracetool
Ensure you have debugging enabled on your phone :
Settings > Applications > Development > USB Debugging > Turn On
Run the windows program : AndroidTool.exe
The first time you use the program, click on “Show Android interface”. This will install the package and the dependencies (busybox and redsocks).
The SuperUser process may ask you to allow “Usb tunnel”
To start tethering click “Connect”.
Again, The SuperUser process may ask you to allow “Usb tunnel”
If the android process crash after receiving superuser rights, close the windows program and start again. (It’s a beta)
The android interface will show connections forwarded to windows.
Start your browser
Google chrome will complain that no connection is available. Don’t care. That work.
Firefox , opera and dolphin don’t have problem with that !!!
The current version of the application can’t forward low level ICMP packet (PING).
From Android Os point of vue, there is no internet connection.
Market :
The search market work, but due to the same connection problem, it’s not possible to download. I hope Google will fix the market.
Click to expand...
Click to collapse
I was looking to get some internet access on alpha build of ics for galaxy tab... Hope this works..will try and let you know..thanks for the good work...
Sent from my GT-P1000 using XDA App

Great work. Tested this and it works pretty well (on HTC Aria CM7).

do you mean we need to connect the tablet to the PC using the USB cable then we can use reverse thethering thingy ?

Wouldn't the PC app like Connectify Me do this thing without all this?
☞★sent from drajax's Galaxy SL!!! *♂ツ

Wow thanks a million!, i hope we can download apps as well but i'll settle for apks for now, <3
---------- Post added at 08:14 PM ---------- Previous post was at 07:55 PM ----------
drajax said:
Wouldn't the PC app like Connectify Me do this thing without all this?
☞★sent from drajax's Galaxy SL!!! *♂ツ
Click to expand...
Click to collapse
it would, but this program uses a USB cable, connectify uses WiFi, so for us who don't have wifi routers or connectify we can use this

Galaxy S II (GT-I9100) on CyanogenMod 7.1, using SiyahKernel 2.2b6, doesn't work. Using Windows 7 x86, with correct drivers installed. Can't get past the step of clicking 'Show Android Interface'. Clicks, but nothing happens. No devices are listed within the program.

screamworks said:
Galaxy S II (GT-I9100) on CyanogenMod 7.1, using SiyahKernel 2.2b6, doesn't work. Using Windows 7 x86, with correct drivers installed. Can't get past the step of clicking 'Show Android Interface'. Clicks, but nothing happens. No devices are listed within the program.
Click to expand...
Click to collapse
If the device is not listed, it's not a problem related with reverse tethering. It's a driver or installation problem !

ldloh2 said:
do you mean we need to connect the tablet to the PC using the USB cable then we can use reverse thethering thingy ?
Click to expand...
Click to collapse
Yes, you just need to install the windows program then click connect.
It's a beta, market is not able to download.

capslock66 said:
If the device is not listed, it's not a problem related with reverse tethering. It's a driver or installation problem !
Click to expand...
Click to collapse
Elaborate? On your post it says:
Tested under:
Acer Iconia A500 (Taboonay 2.1)
Galaxy S (Cyanogen 7)
Galaxy S II
HTC Aria (CM7)
Click to expand...
Click to collapse
The device is listed. And I've got all appropriate drivers for my device installed?

Inspire 4G CM7, works
As a side note, I had ADB running when I started it & it didnt work. Killed all ADB sessions & relaunched, after that it worked like a charm.

screamworks said:
Elaborate? On your post it says:
The device is listed. And I've got all appropriate drivers for my device installed?
Click to expand...
Click to collapse
Did you enabled USB Debugging ?
Run a dos command prompt then enter this command :
Code:
cd\instfolder
adb devices
instfolder is the folder where you unzipped ReverseTethering.zip
Ensure you have adb.exe in that folder
You should see :
Code:
List of devices attached
xxxxxxxxxxx device
If not, try to re-install driver or test on another PC.

combustiblemonkey said:
As a side note, I had ADB running when I started it & it didnt work. Killed all ADB sessions & relaunched, after that it worked like a charm.
Click to expand...
Click to collapse
Better is to configure the application to use the already installed ADB program on your computer :
button config -> ADB sheet -> update path -> button save
Then restart the tool.

Working on Nexus S with MIUI. Opera browser and Market both work.
I was hoping to use it to avoid using my data while playing games or when installing games with huge downloads after installing, but that doesn't seem to be the case yet. I see I can add ports for forwarding, but how can I tell what port a game uses?

This was something i was waiting but i could not use the internet from pc.
I have SGS1, 2.3.6. I dont get any error messages. Clicking connect makes it connect but status column always not connected.
Im on company network. Which IP i will use? Which port i will use?

Kolero said:
I was hoping to use it to avoid using my data while playing games or when installing games with huge downloads after installing, but that doesn't seem to be the case yet. I see I can add ports for forwarding, but how can I tell what port a game uses?
Click to expand...
Click to collapse
Next version will detect automatically ports.
But it's still not possible do download from Market

yken said:
This was something i was waiting but i could not use the internet from pc.
I have SGS1, 2.3.6. I dont get any error messages. Clicking connect makes it connect but status column always not connected.
Im on company network. Which IP i will use? Which port i will use?
Click to expand...
Click to collapse
Beta 2 (+- 15 decembre) will be more stable. With automatic port detection.

serves to moto defy?

Why not just use virtual router on your pc?

Works like a charm on My Ideos X5 U8800.. Thx!

[Q] MTP XP Driver

I attempted to search for this issue, and while there are many similar issues, I haven't actually seen a resolution for this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I need the MTP driver for Windows XP. I've gotten the other 2 drivers up & running, but not the MTP. Anyone able to provide a link for a working MTP driver for my Nexus 7?

I guess you have to install Windows Media Player (this is only possible with a genuine Windows).
Personally I use AirDroid to transfer files. ( https://play.google.com/store/apps/details?id=com.sand.airdroid )

goebish said:
I guess you have to install Windows Media Player (this is only possible with a genuine Windows).
Personally I use AirDroid to transfer files. ( https://play.google.com/store/apps/details?id=com.sand.airdroid )
Click to expand...
Click to collapse
I already have Media Player 11 on there. No go.
AirDroid isn't an option as we only have WiFi at work on our outside LAN and our computers are all behind the firewall.

i had this issue recently.
do you have USB debugging turned on? if so, turn it off.

mrhomiec said:
i had this issue recently.
do you have USB debugging turned on? if so, turn it off.
Click to expand...
Click to collapse
Yeah. No luck.

@mrhomiec
Yes, I turn USB debugging off and try re-installing the driver again and it is working fine now. Many thanks.:good:

After ages trying to root my Nexus 7 and repeatedly un/re-installing of drivers using various 'toolkits' and then finally succeeding, I was upset to see this problem in Device Manager.
Seeing mrhomiec's excellent solution in the first thread I looked at was a great relief. Many thanks!

Media Transfer Protocol Porting Kit
I know this is super old but just in case anyone searched this for help, You might try downloading the Media Transfer Protocol Porting Kit
Heard this works. If you Google search "Microsoft MTP" it will be the first result. I can't post links so that's the best I can give you guys.

twista4004 said:
I know this is super old but just in case anyone searched this for help, You might try downloading the Media Transfer Protocol Porting Kit
Heard this works. If you Google search "Microsoft MTP" it will be the first result. I can't post links so that's the best I can give you guys.
Click to expand...
Click to collapse
It helped. Even if the posts are old, there's always someone looking for a solution. Thanks!

MTP working with XP
Here is what I had to do to get MTP working with XP SP3:
1: Download and install MTPPK12
2: Download and intall Media Player 11
3: Connect the N7 to the PC via the USB cable and set USB to MTP instead of "Camera".
4: Open "Settings" and turn off "USB debugging".
5pen "Device Manager" on the PC and look for "Android Device". If you find and entry for an "ADB" device, uninstall the driver. Unplug the N7 and plug it back in. The PC should now find a device titled "Nexus 7" and install the driver. Open "My Computer" and "Nexus 7" should now be listed and ready to transfer files.

A little something to get USB-Debugging working
Hey guys,
for those who want to use their precious Android with enabled USB-debugging at a Win XP system:
1. get some drivers that work fine without enabled debugging (for HTC disciples: http://forum.xda-developers.com/showthread.php?t=2191279 ) and install them.
2. switch your device to usb-debugging and look up the exact hardware-ID @ your device manager (device manager -> android device -> details -> hardware ID) - keep that window open for you'll need the exact key
3. Search the installed drivers (for me it was C:\Programme\HTC\HTC Driver\Driver Files\XP_x86) and edit the 'androidusb.inf'.
4. In the file, look for the 'Device Section' and scroll way down to the 'For XP and later' section. Here you copy the first entry and paste in your hardwareID.
For me, I took:
%USB\VID_0BB4&PID_0C01&MI_01.DeviceDescRelease%=HTCAND32.Dev, USB\VID_0BB4&PID_0C01&MI_01
Click to expand...
Click to collapse
and changed it to:
%USB\VID_18D1&PID_2D02&MI_01.DeviceDescRelease%=HTCAND32.Dev, USB\VID_18D1&PID_2D02&MI_01
Click to expand...
Click to collapse
5. Next scroll down until you find the '[Strings]' section. Here you do the same thing as before:
Copy the first entry and edit it according to your hardwareID.
For me, I took:
USB\VID_0BB4&PID_0C01.DeviceDescRelease="My HTC"
Click to expand...
Click to collapse
and changed it to:
USB\VID_18D1&PID_2D02.DeviceDescRelease="My HTC ONE"
Click to expand...
Click to collapse
(you are free to name it what ever you want )
Next you'll need to scroll down until the patten changes from
USB\VID_0BB4&PID_0C01.DeviceDescRelease="My HTC"
Click to expand...
Click to collapse
to
USB\VID_0BB4&PID_0C01&MI_01.DeviceDescRelease="My HTC"
Click to expand...
Click to collapse
here you'll need to copy the first entry again and edit it to match your needs. Just copy the device name you have entered before.
6. Finally you can install the drivers manually via your device manager. Just choose your pimped androidusb.inf as driver and you should be able to work with your android phone at usb-debugging (for example for MyPhoneExplorer).
Of cause I am not responsible if you wreck your Win XP / your drivers so don't overdo it. If you don't know what you are doing, do it like the Beatles and 'let it be'

doomhendi said:
Hey guys,
for those who want to use their precious Android with enabled USB-debugging at a Win XP system:
1. get some drivers that work fine without enabled debugging (for HTC disciples: http://forum.xda-developers.com/showthread.php?t=2191279 ) and install them.
2. switch your device to usb-debugging and look up the exact hardware-ID @ your device manager (device manager -> android device -> details -> hardware ID) - keep that window open for you'll need the exact key
3. Search the installed drivers (for me it was C:\Programme\HTC\HTC Driver\Driver Files\XP_x86) and edit the 'androidusb.inf'.
4. In the file, look for the 'Device Section' and scroll way down to the 'For XP and later' section. Here you copy the first entry and paste in your hardwareID.
For me, I took:
and changed it to:
5. Next scroll down until you find the '[Strings]' section. Here you do the same thing as before:
Copy the first entry and edit it according to your hardwareID.
For me, I took:
and changed it to:
(you are free to name it what ever you want )
Next you'll need to scroll down until the patten changes from to
here you'll need to copy the first entry again and edit it to match your needs. Just copy the device name you have entered before.
6. Finally you can install the drivers manually via your device manager. Just choose your pimped androidusb.inf as driver and you should be able to work with your android phone at usb-debugging (for example for MyPhoneExplorer).
Of cause I am not responsible if you wreck your Win XP / your drivers so don't overdo it. If you don't know what you are doing, do it like the Beatles and 'let it be'
Click to expand...
Click to collapse
The method in the prior post works fine and is much easier.

lewmur said:
The method in the prior post works fine and is much easier.
Click to expand...
Click to collapse
The method in the prior post works for the MTP device, which doesn't include the adb-interface for every power-user / dev tools and apps, dude
Plus I don't like to flood my system with .. sweet, useful and light-weight progs like MP11 /10 :laugh:
greetz

doomhendi said:
The method in the prior post works for the MTP device, which doesn't include the adb-interface for every power-user / dev tools and apps, dude
Plus I don't like to flood my system with .. sweet, useful and light-weight progs like MP11 /10 :laugh:
greetz
Click to expand...
Click to collapse
The question was how to connect MTP, not ADB. BTW, I'm 74 yrs old and find the appelation "dude" quite offensive.

lewmur said:
The question was how to connect MTP, not ADB. BTW, I'm 74 yrs old and find the appelation "dude" quite offensive.
Click to expand...
Click to collapse
MTP and ADB come hand in hand so if anyone wants to use the ADB-interface, he or she can do so by following this little tutorial and don't even need to spam their system with unnecessary bloatware.. sorry, but I don't see the problem you've got with that ?
And I'm very sorry, I don't understand the problem you've got with a useful tutorial but that doesn't mean that I've got any problem with you oO
So, no offense

doomhendi said:
MTP and ADB come hand in hand so if anyone wants to use the ADB-interface, he or she can do so by following this little tutorial and don't even need to spam their system with unnecessary bloatware.. sorry, but I don't see the problem you've got with that ?
And I'm very sorry, I don't understand the problem you've got with a useful tutorial but that doesn't mean that I've got any problem with you oO
So, no offense
Click to expand...
Click to collapse
My problem is that most people searching a thread like this aren't going to read every post. They go to the "last page" to see what the latest solution is. Your post was on the last page by itself and I was concerned that noobs reading it would think it was "the best" solution. I wanted to point out that the post previous to yours actually had an easier solution. And, IMO, Media Center takes a miniscule amount of disk space compared to what the vast majority of people have available.

lewmur said:
My problem is that most people searching a thread like this aren't going to read every post. They go to the "last page" to see what the latest solution is. Your post was on the last page by itself and I was concerned that noobs reading it would think it was "the best" solution. I wanted to point out that the post previous to yours actually had an easier solution. And, IMO, Media Center takes a miniscule amount of disk space compared to what the vast majority of people have available.
Click to expand...
Click to collapse
Well I have found this thread because I was looking for a solution for the MTP / ADB-problem and thought that other users might find this missing information useful. Your problem with my post would mean that you disagree any discussion or even better solutions to problems (threats) as soon as you posted your solution .. which truly isn't the way a community works.
And sorry, but I won't discuss the cancer-like spreading of MS products to any system with you in this threat. It's not as simple as disk space.
I suggest we now stop bloating up this topic, unless you've got more useful information concerning the problem.

doomhendi said:
Well I have found this thread because I was looking for a solution for the MTP / ADB-problem and thought that other users might find this missing information useful. Your problem with my post would mean that you disagree any discussion or even better solutions to problems (threats) as soon as you posted your solution .. which truly isn't the way a community works.
And sorry, but I won't discuss the cancer-like spreading of MS products to any system with you in this threat. It's not as simple as disk space.
I suggest we now stop bloating up this topic, unless you've got more useful information concerning the problem.
Click to expand...
Click to collapse
I didn't imply that your solution wouldn't work or wasn't valuable info. I merely referred readers back to the previous post so that they would realize they had a CHOICE!!!

lewmur said:
I didn't imply that your solution wouldn't work or wasn't valuable info. I merely referred readers back to the previous post so that they would realize they had a CHOICE!!!
Click to expand...
Click to collapse
.. If they want a truly working USB-interface, they don't have one :laugh:
But you get a 'thanks-click' from me for you intentions

worked like magic!
I followed each step exactly and the magic worked! I can now access my HTC internal storage and SD Card contents from Windows XP.!
Many many thanks!
lewmur said:
Here is what I had to do to get MTP working with XP SP3:
1: Download and install MTPPK12
2: Download and intall Media Player 11
3: Connect the N7 to the PC via the USB cable and set USB to MTP instead of "Camera".
4: Open "Settings" and turn off "USB debugging".
5pen "Device Manager" on the PC and look for "Android Device". If you find and entry for an "ADB" device, uninstall the driver. Unplug the N7 and plug it back in. The PC should now find a device titled "Nexus 7" and install the driver. Open "My Computer" and "Nexus 7" should now be listed and ready to transfer files.
Click to expand...
Click to collapse

[Q] SGS5 Not recognized by PC!

Whenever I connect my phone to my computer via USB, it says "USB Device not recognized". I look in my device manager and I see 4 devices come up called "Bluetooth Peripheral Device" show up under "Other devices", yet they got yellow warning symbols next to them.
My phone connects to my PC via Bluetooth fine, but the USB just wont work! I've searched the web but most things are outdated or just don't work...
I think this is due to using an OTG cable, making my phone act as the host device whenever I plug it in?
Extra detail:
-PC is running Windows 7 ultimate x64
-Samsung Galaxy S5 is on Android 5.0, but didn't work on previous versions either
-I use the samsung cable, but have also tried one other cable.
-Tried plugging it into another computer, does the exact same thing.

Install Samsung drivers / KIES3

*Detection* said:
Install Samsung drivers / KIES3
Click to expand...
Click to collapse
Already tried those, made no difference unfortunately

CheeseJuggernaut said:
Whenever I connect my phone to my computer via USB, it says "USB Device not recognized". I look in my device manager and I see 4 devices come up called "Bluetooth Peripheral Device" show up under "Other devices", yet they got yellow warning symbols next to them.
.
Click to expand...
Click to collapse
Have a look at this post I put up for someone with a similar problem to you, see if it helps, you need to use the USB cable that came with the phone, others will work but a lot don't work properly
Post

ag4751 said:
Have a look at this post I put up for someone with a similar problem to you, see if it helps, you need to use the USB cable that came with the phone, others will work but a lot don't work properly
Post
Click to expand...
Click to collapse
Thank you for the great help, I think that this is what needs to be done to fix it. There is still one problem though.
I have tried this before, but I ran into a problem where it would do this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you can see, it wont let me use the driver, saying that there is a "code 10" and that the driver wont start. I think that if I can get through this error, my phone will finally connect

CheeseJuggernaut said:
As you can see, it wont let me use the driver, saying that there is a "code 10" and that the driver wont start. I think that if I can get through this error, my phone will finally connect
Click to expand...
Click to collapse
Try these options,
1. Control Panel > Devices & Printers then plug in your phone and you should get an Unknown Device appear, right click on it and select Troubleshoot and run that process to see if that sorts out the problem.
2. Start your computer in safe mode then try installing the driver manually that way, then reboot your PC normally.
Registry solution if you want to try it as long as you understand Windows Registry
1. Go to the Registry Editor click Start > Run > and type in regedit then hit Enter
2. Expand the folder location HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\
3. Find EEC5AD98-8080-425f-922A-DABF3DE3F69A in the folder list and click on it, this should say Portable Devices in the right window
4. See if it contains a value called UpperFilters if so delete it
5. Before you delete it though make a backup of the EEC5AD98-8080-425f-922A-DABF3DE3F69A folder, right click on it and Export to a folder just in case you need to restore it.
6. To restore the key if you need to just go to the folder where you exported it to and click on it to install

ag4751 said:
Try these options,
1. Control Panel > Devices & Printers then plug in your phone and you should get an Unknown Device appear, right click on it and select Troubleshoot and run that process to see if that sorts out the problem.
2. Start your computer in safe mode then try installing the driver manually that way, then reboot your PC normally.
Registry solution if you want to try it as long as you understand Windows Registry
1. Go to the Registry Editor click Start > Run > and type in regedit then hit Enter
2. Expand the folder location HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\
3. Find EEC5AD98-8080-425f-922A-DABF3DE3F69A in the folder list and click on it, this should say Portable Devices in the right window
4. See if it contains a value called UpperFilters if so delete it
5. Before you delete it though make a backup of the EEC5AD98-8080-425f-922A-DABF3DE3F69A folder, right click on it and Export to a folder just in case you need to restore it.
6. To restore the key if you need to just go to the folder where you exported it to and click on it to install
Click to expand...
Click to collapse
Sorry for the late reply, ive been busy.
There is no UpperFilters value, and unfortunately the troubleshoot didnt resolve the problem.

CheeseJuggernaut said:
Sorry for the late reply, ive been busy.
There is no UpperFilters value, and unfortunately the troubleshoot didnt resolve the problem.
Click to expand...
Click to collapse
You are having a problem with this aren't you.
If you have Kies installed uninstall it also plug in your phone and find it in the list of USB Devices, then right click select properties and uninstall the driver, unplug the phone and reboot your PC.
Once rebooted Temporarily turn off any firewalls and Anti Virus scanners and try the below
Install Kies 3, start Kies and check for updates, if there are any updates then install them.
Restart Kies 3 after any update, once its running plug in your phone and let the drivers install
If its worked properly Kies will see it, if not then check the USB devices and try to install the driver manually again
Don't forget to use the USB cable that came with the phone

ag4751 said:
You are having a problem with this aren't you.
If you have Kies installed uninstall it also plug in your phone and find it in the list of USB Devices, then right click select properties and uninstall the driver, unplug the phone and reboot your PC.
Once rebooted Temporarily turn off any firewalls and Anti Virus scanners and try the below
Install Kies 3, start Kies and check for updates, if there are any updates then install them.
Restart Kies 3 after any update, once its running plug in your phone and let the drivers install
If its worked properly Kies will see it, if not then check the USB devices and try to install the driver manually again
Don't forget to use the USB cable that came with the phone
Click to expand...
Click to collapse
Unfortunately this hasnt worked. As always I plug my phone in (while unlocked) and nothing happens exept for the notification on my desktop about a usb device not recognised

CheeseJuggernaut said:
Unfortunately this hasnt worked. As always I plug my phone in (while unlocked) and nothing happens exept for the notification on my desktop about a usb device not recognised
Click to expand...
Click to collapse
I have run out of suggestions, your PC is just being difficult, I tried googling the problem but nothing really helpful there, but I did find this Link and a few people said it sorted it for them, have a look the solution for them was the links in post 18

ag4751 said:
I have run out of suggestions, your PC is just being difficult, I tried googling the problem but nothing really helpful there, but I did find this Link and a few people said it sorted it for them, have a look the solution for them was the links in post 18
Click to expand...
Click to collapse
Thanks for trying! I think im gonna go get my phone port checked out at the phone shop. Thanks again!

CheeseJuggernaut said:
Thanks for trying! I think im gonna go get my phone port checked out at the phone shop. Thanks again!
Click to expand...
Click to collapse
Are you using the OEM cable?

Rapunzl said:
Are you using the OEM cable?
Click to expand...
Click to collapse
Yes, and ive tried other cables. Its a problem that is most probably hardware though

CheeseJuggernaut said:
Thanks for trying! I think im gonna go get my phone port checked out at the phone shop. Thanks again!
Click to expand...
Click to collapse
Take the original USB cable as well so they can try another one against yours just in case it a faulty cable