Related
Hello
I have a stock Vodaphone Magic and I'm looking to root it, but to do this I need to get adb to see it, which I'm having problems with.
When I plugged it in first to charge it used window's default drivers for the SD card etc. Trying to update the drivers with the ones included in the SDK dosn't seem to work as Windows says that they're less recent.
Also, I can't see any sort of "ADB" section in the device manager, even with USB debugging turned on in the phone.
Any help? I'd really like to root my phone so I can use WPA Enterprise!
Edit: Already read the wiki page, no help.
I remember having this problem when I first set up the Android SDK.
However in my device manager I did have a device, it wasn't called Android or Magic or anything similar. From what I remember it was a bunch of random letters and numbers.
From there I right clicked it, went to Properties, Update Driver and then pointed it to the directory with the drivers.
Thats how I did it in Windows 7, if that doesn't work for you then I'm not sure sorry.
Hi,
I recently had the same problem as you. The first time you plug in your phone sometimes Windows will assign USB drivers to the device instead of the ADB interface. To correct this, I uninstalled the drivers and pointed the computer to the ADB files as the new drivers. After those install it should be labelled correctly and work.
Does anyone use the micro usb port? I have yet to find a use for it. I can't transfer files with it, charge with it nor are there any peripherals (that I know of) that can use it. I searched around but couldn't find much useful stuff on the port. All I found was this useless video:
**Ok I can't post the video because of more stupid forum rules but just go to youtube.com and append this after the url: /watch?v=1xBVu-IatDQ **
Anyway, if someone has ideas on how this port can be used I'm all ears... Thanks.
dq
It is a file transfer port. you plug a cable into it and into your PCs usb port. works like the ones on your phone.
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
don quixada said:
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
Click to expand...
Click to collapse
What OS are you using on your computer, and have you installed the drivers for it?
don quixada said:
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
Click to expand...
Click to collapse
Computer OS? i just plugged it into my Win7 system and it was there instantly. 3.0 shows up as a media device, which allows both the tablet and the computer to talk to the sdcard at the same time. So you won't see a mount prompt on the tablet. BTW my Incredible2 is running 2.3 and also lets me access the SD card on it and the computer at the same time.
I'm still using an old tiny xp and it worked fine for me just plugged it in and there it was
I tried Gentoo Linux and XP and neither worked. What drivers do I need to install?
I also have access to a Win7 system so I'll try that.
dq
Drivers from acer website.
I have adb installed should this not be enough?
You need none installed. ADB if its running in some form might be interfering. its just a basic driver in windows it uses.
I only run adb-server when I need it and not all the time. I thought that any needed drivers would have been installed when I installed adb.
For my Gentoo machine what should I do? It's not detected at all if I plug it in. My x10 mini and Nexus One are detected no problem and I can mount them and everything so what's up? Is there a kernel module that I need to build?
Thanks.
dq
I had to download these drivers for my xp netbook ,,
http://global-download.acer.com/GDF...A Tab&Step3=A500&OS=a05&LC=en&BC=Acer&SC=PA_6
I agree with Nova 5. The Windows drivers for USB come with the SDK and while you might not think you will have use for the SDK you will. It makes the process of installing custom ROM,s and Recovery Kernels a breeze. You download your zip flashes or recovery images to Win 7 and then you adb push your downloads to the tablet. The alternatives, unless soneone was nice enough to compile you an apk, which most advanced system developers don,t bother with, unless their app is destined for the massees throug Andriod market, is to install a terminal emulator and enter native Unix/Linux shell commands manually. If you aren't a shell cmd expert I suggest you immediatly download the latest Android SDK for Windows and start learning what it can do for you with just 2 or 3 adb push commands which can help you advoid 10's of lines of manually entered Linux shell commands that can do some real damage to your system if you are copying someone elses terminal emulator sh install instructions, don't understand what they do and make 1 simple typing mistake. With adb push you don't even have to get involved in Linux's complicated bit based permission changes to install something at the system level.
Sent from my A500 using xda premium
Yes, well I only really use adb in the same capacity as what you describe-- to root a device. After that busybox can be installed and I can either ssh into the device (which I prefer) or use the terminal on the device itself.
But my problem is the detection of the device once it is plugged into my Linux box. I'm not sure if I need a special driver for that and I'd rather not aimlessly search through the kernel config in order to build one (I've done that before and it's painful!). It's good to know that one can mount it on an external device and still use it simultaneously though. That will save me time in trying to fiddle around with settings in the tablet itself...
dq
don quixada said:
I have adb installed should this not be enough?
Click to expand...
Click to collapse
If you are not able to transfer files Try enabling usb debugging before connecting to pc.
If the tab is not in the usb devices list and it doesn't show up as an unknown device, you might want to try another usb cable. Or another port if you have the Windows and Linux on the same machine and you are trying to connect on the same port.
Sent from my A500 using XDA Premium App
gradyzero said:
I agree with Nova 5. The Windows drivers for USB come with the SDK and while you might not think you will have use for the SDK you will. It makes the process of installing custom ROM,s and Recovery Kernels a breeze. You download your zip flashes or recovery images to Win 7 and then you adb push your downloads to the tablet. The alternatives, unless soneone was nice enough to compile you an apk, which most advanced system developers don,t bother with, unless their app is destined for the massees throug Andriod market, is to install a terminal emulator and enter native Unix/Linux shell commands manually. If you aren't a shell cmd expert I suggest you immediatly download the latest Android SDK for Windows and start learning what it can do for you with just 2 or 3 adb push commands which can help you advoid 10's of lines of manually entered Linux shell commands that can do some real damage to your system if you are copying someone elses terminal emulator sh install instructions, don't understand what they do and make 1 simple typing mistake. With adb push you don't even have to get involved in Linux's complicated bit based permission changes to install something at the system level.
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Not nearly what I was saying. Not even close enough that a bomb would touch it.
Simple answer is my vista and win7 systems accessed the iconia as a media player device requiring no drivers as they are a common system driver. My only comment about ADB was that it might be interfering if it somehow was left running in the background.
I'm not sure what the problem is, but I had to play around with the settings and plug it in several times and finally it showed up. Now I plug it in and the dialog for auto play shows up instantly. When I choose to view files, I get a window with two drives. One is the internal storage and the other is the sd card.
sandiegoan said:
I'm not sure what the problem is, but I had to play around with the settings and plug it in several times and finally it showed up. Now I plug it in and the dialog for auto play shows up instantly. When I choose to view files, I get a window with two drives. One is the internal storage and the other is the sd card.
Click to expand...
Click to collapse
Sometimes mine gets a bit wonky as well. Every now and then, I'll plug it in, get the windows dialogue box asking me what I want to do. I open it up and the box is blank, no drives, nothing. Unplug it, wait a few seconds, pop it back in, and everything is OK. No rhyme or reason, and it doesn't happen all the time.
Quick trick for win7 .
Plug in the device.go into device manager delete its entry and the USB controller it resides on.unplug device.install driver from acer web site.then try the device again.
This works on several USB type issues
Good luck if you don't understand don't try
When I connect my Nexus 7 to my Windows XP (SP3) PC via USB, it's obvious the computer recognizes it and it tries to install ADB drivers. Whether I choose to install those drivers or not, I still can't locate my device in the Windows Explorer Tree. I checked Disk Management for the hell of it and nothing but my PC's harddrives were there. There's an attempt to install drivers for "MTP" but that fails and I'm pretty sure that's the cause; however, I'm unable to replicate it, even as I uninstall/reinstall applicable drivers from the device manager the MTP failure never happens anymore. I did some googling and found a thread with someone who had a similiar experience. In turn, I downloaded https://www.box.com/s/2c25e8bc42ecce400afd to try a different set of drivers. Same problem. Driver install is fine for ADB, but still unable to see my device in Windows Explorer. I'm able to successfully connect the device to the PC with PTP for the camera. I can access DCIM and cache which can serve as a work around, but I'm hoping you can provide any ideas you might have. Thank you!
edit - ***resolution***: Ok, I figured it out...I had to disable USB debugging. I don't know if this helped either, but I installed these drivers as an alternative to the drivers that were originally installed: https://www.box.com/s/2c25e8bc42ecce400afd
While connected to PC, I switched to PTP mode because I was about to give up and just use that
I then disabled usb debugging and switched back to MTP at which point the drivers successfully installed and I could now view my device in Windows Explorer. I also believe downloading the drivers in the link above helped since the first crack I took at this was unsuccessful with existing drivers.
install pdanet on pc and it will install drivers for u so it will be recognized
Ok, I figured it out...I had to disable USB debugging. I don't know if this helped either, but I installed these drivers as an alternative to the drivers that were originally installed: https://www.box.com/s/2c25e8bc42ecce400afd
Been battling with this on my XP machine since yesterday. I couldn't even get debugging to work until I installed NakedDriver. And even still, there seems to be no way to get MTP to work without turning debugging off. On my Win7 machine everything worked perfectly, both ADB and MTP, right out of the box. I have the Galaxy Nexus drivers installed on both machines (which I've read are compatible with the N7). I also have the latest version of Windows Media Player (I've read that some older versions have issues with MTP). Is anyone else able to run ADB and MTP on XP?
*edit*
A: Does PDAnet let you use MTP and ADB simultaneously? Because I really don't want to install it if I don't have to. I got rid of it ages ago (too many things starting up at boot time).
B: I have a Galaxy Nexus also, and I have no issues on the XP box.
I wouldn't bother with MTP, it's not always showing the contents of the internal storage properly when viewed in Windows Explorer.
Earlier today when I was trying to set up a backup profile for it, it didn't copy all the files off. On closer inspection I found folders like TitaniumBackup to be completely empty, which is not true according to ES File Explorer on the tablet.
I tried connecting MTP again, with USB Debugging on and off but this made no difference. Also I'm only seeing the Notifications folder instead of 36 folders on the internal storage now, really random how it's working.
asus site now has a usb driver for N7
try that
Nordendorf said:
asus site now has a usb driver for N7
try that
Click to expand...
Click to collapse
Updated with ASUS drivers, still doesn't view internal storage fully.
Salty Wagyu said:
Updated with ASUS drivers, still doesn't view internal storage fully.
Click to expand...
Click to collapse
Same here. No change with the Asus drivers. Still can't use MTP when ADB is turned on.
poo. how do I transfer my audiobooks to this stupid device without working drivers?
1. Please disconnect Nexus7
2. Remove drivers on PC.
3. Toggle ON : Settings->Wireless&Networkings->More->NFC.
4. Re-connect device
Good luck !
GotLoveForAll said:
poo. how do I transfer my audiobooks to this stupid device without working drivers?
Click to expand...
Click to collapse
1. Uncheck MTP, check the one next to it (Camera)
2. Unplug USB
3. Turn off USB Debugging (Uncheck it)
4. Plug in USB
5. Should say connected as camera, then a new window will pop-up allowing you to see your files.
Tell me if it works!
im having trouble too, is there any way to make the device to be recognised as a flash drive?
Internal memory partly invisible from Windows 7 Explorer
Salty Wagyu said:
I wouldn't bother with MTP, it's not always showing the contents of the internal storage properly when viewed in Windows Explorer.
Earlier today when I was trying to set up a backup profile for it, it didn't copy all the files off. On closer inspection I found folders like TitaniumBackup to be completely empty, which is not true according to ES File Explorer on the tablet.
I tried connecting MTP again, with USB Debugging on and off but this made no difference. Also I'm only seeing the Notifications folder instead of 36 folders on the internal storage now, really random how it's working.
Click to expand...
Click to collapse
Same observation here (a few months later) on stock Android 4.1.1 rooted.
It seems that new files in the internal memory remain invisible for a long time, but so far they have become visible eventually, sometimes a day or two later. I have no clue what could possibly cause this, and I have not found any trick or workaround that makes them visible, not even rebooting. Any hint is welcome.
SE4GT said:
1. Uncheck MTP, check the one next to it (Camera)
2. Unplug USB
3. Turn off USB Debugging (Uncheck it)
4. Plug in USB
5. Should say connected as camera, then a new window will pop-up allowing you to see your files.
Tell me if it works!
Click to expand...
Click to collapse
Didn't work. Just shows up as a camera with the limited folder access one would expect.
Workaround
I now use the following workaround.
Install SDrescan from Google Play.
Run it.
If you already had your phone connected to a computer as a media device (MTP) and are watching the contents of your SD card or internal memory in Windows Explorer, press F5 to refresh your view. If not, connect it now.
I'd be curious whether this works for you as well. If it does, press the THANKS button below.
Same issue with an old ibm x40 udated to windows xp pro SP3.
I've installed mtp driver, without success
I've "tried" to install asus driver, without success
I've tried to do as above with the help of the nexus toolkit, without success.
Everytime, the laptop recognize the device as android ADB interface.
Someone could help me?
Thank you in advance
mistershark said:
Everytime, the laptop recognize the device as android ADB interface.
Click to expand...
Click to collapse
Disable USB debugging in your phone.
Same problem with my moto xoom...files not showing in MTP using windows xp...still have not found any solution
hgmichna said:
Disable USB debugging in your phone.
Click to expand...
Click to collapse
+1 have to toggle USB debugging in winXP
hgmichna said:
I now use the following workaround.
Install SDrescan from Google Play.
Run it.
If you already had your phone connected to a computer as a media device (MTP) and are watching the contents of your SD card or internal memory in Windows Explorer, press F5 to refresh your view. If not, connect it now.
I'd be curious whether this works for you as well. If it does, press the THANKS button below.
Click to expand...
Click to collapse
It works! THANKS A LOT!!!
My nexus 7 isnt showing up on my Windows 7 x64 machine... any help on what I can do?
numus said:
My nexus 7 isnt showing up on my Windows 7 x64 machine... any help on what I can do?
Click to expand...
Click to collapse
This is part "bump" and part assistance. You can at least get the Nexus 7 connected via ADB using these steps:
enable USB debugging
install the Android SDK (from Android's developer site)
from the SDK manager install the latest version of the USB driver too.
Make sure your Nexus 7 is hooked up.
Go into your device manager (Start > Control Panel > Device Manager)
navigate to the right Nexus device (not MTP in this case),
right click it,
click Update Device Drivers.
Choose your own driver manually.
When asked for a folder, navigate to C:\[your username]\AppData\Local\Android\android-sdk\extras\google\usb_driver
make sure searching in folders is checked
...that should at least get the ADB driver running. From there you can PUSH or PULL files or open the SHELL, but I don't know of a client-side file manager that makes those things easy yet. This is just one step of many, I bet...
2 things
Have you the latest win media player installed on PC? If not, update it.
Is n7 USB debugging on? If so, turn it off.
That should allow MTP to begin. If not, try the previous post
Sent from my Nexus 7 using xda app-developers app
If your using a N or KN version of Windows 7, you can't use MTP. N and KN versions of Windows have media foundation and other media-specific features stripped from it; and MTP itself does not work.
If you are on such an OS, then this media pack may help:
http://www.microsoft.com/en-us/download/details.aspx?id=16546
espionage724 said:
If your using a N or KN version of Windows 7, you can't use MTP. N and KN versions of Windows have media foundation and other media-specific features stripped from it; and MTP itself does not work.
If you are on such an OS, then this media pack may help:
http://www.microsoft.com/en-us/download/details.aspx?id=16546
Click to expand...
Click to collapse
Other MTP devices show up... I have my epic 4g touch hooked up right now and it shows MTP... just the google nexus 7 wont...
primetechv2 said:
This is part "bump" and part assistance. You can at least get the Nexus 7 connected via ADB using these steps:
enable USB debugging
install the Android SDK (from Android's developer site)
from the SDK manager install the latest version of the USB driver too.
Make sure your Nexus 7 is hooked up.
Go into your device manager (Start > Control Panel > Device Manager)
navigate to the right Nexus device (not MTP in this case),
right click it,
click Update Device Drivers.
Choose your own driver manually.
When asked for a folder, navigate to C:\[your username]\AppData\Local\Android\android-sdk\extras\google\usb_driver
make sure searching in folders is checked
...that should at least get the ADB driver running. From there you can PUSH or PULL files or open the SHELL, but I don't know of a client-side file manager that makes those things easy yet. This is just one step of many, I bet...
Click to expand...
Click to collapse
ADB works without a problem.. it is just hte MTP that wont show up
I have the same issue. If I select PTP, the camera shows. Once I switch back to MTP, it goes away and no disks are displayed. In Device Manager I see Android Phone, I installed Google drivers and adb works. I have a Google Nexus also and is OK.
You're not alone, Sir.
http://forum.xda-developers.com/showthread.php?t=1821536
Anyone who found a fix for this? Couldn't get it to work on W7, on Windows 8 still no MTP. I can use it for debugging with the ADB, but everything I tried failed. Now I'm using AirDroid, but this option is the way slower.
reemprive said:
Anyone who found a fix for this? Couldn't get it to work on W7, on Windows 8 still no MTP. I can use it for debugging with the ADB, but everything I tried failed. Now I'm using AirDroid, but this option is the way slower.
Click to expand...
Click to collapse
Either the PDAnet or official Asus drivers work for me.
Sent from my Nexus 7 using Tapatalk HD
on 4.4.2
Here's the official documentation from Google for enabling this protocol.
"Transfer files through USB" (Google this** and click the link by support.google.com)
Relevant Info:
On your device, make sure that the USB computer connection is set to “Media device (MTP).”
Go to Settings > Device > Storage. Then open Menu > USB computer connection.
MTP should be selected by default, but you may have to uncheck MTP, check and uncheck Camera (PTP), and then recheck MTP.
** Unfortunately I'm not able to post external links having fewer than 10 posts, so I'll update this when I'm able. If I forget, just ping me.
Hi,
Trying to get my Nexus 7 connected to my laptop running Windows XP (32bit), SP3, to allow me to root it.
I've downloaded the Nexus Root Toolkit and I've tried installing all the different drivers from there (USB Debugging is OK), and even the Samsung drivers.
Every time, I get a error on the android ADB interface (can't install). I can't post a picture yet (need 10 posts on here), but I get the following in device manager:
Android Device
Nexus (!)
Other Devices
MTP (!)
Any ideas where I'm going wrong? I think I've read somewhere that XP is difficult to get communicating.
Cheers.
Oh, and it tries to install wdtCoinstaller01007 as standard for a driver.
Have also tried *01009
I have the same problem.
I guess the MTP while in debugging mode is not important