Related
Shows up on my laptop but not on my desktop, have tried back and front USB ports
have uninstalled USB drivers, reinstalled USB drivers (universal adbdriversetup6 downloaded from xda sources)
downloaded android SDK manager and installed whatever USB stuff it had there
used USBdeview to remove any nexus 7 related things and then re-install USB drivers
Cannot for the life of me figure out what's going on... can anyone help me please
When I plug it in my desktop it makes the sound like something got connected... even has the safely remove hardware thing with nexus 7 there, but nothing in my computer
also have tried with/without USB debugging
tried removing my rom and flashing stock etc
Nothing has worked so far
and yes forgot to put in the title but this is for the Nexus 7FHD 2013
Is there a chance you are using usb3.0 port and can switch to usb2.0?
I would suggest you backup, flash stock, and redo your driver deinstall/install on stock. Try to get it working there first. Make sure USB debugging is disable on stock.
sfhub said:
Is there a chance you are using usb3.0 port and can switch to usb2.0?
I would suggest you backup, flash stock, and redo your driver deinstall/install on stock. Try to get it working there first. Make sure USB debugging is disable on stock.
Click to expand...
Click to collapse
tried USB 3.0 as well as 2.0 on desktop doesnt work, shows up as a device on safely remove hardware, and I can also see it under other devices in hardware manager or whatever but doesnt display in computer
USB debugging enabled or disabled on stock doesn't work.. tried going back to stock and doing driver installation etc as well
In device manager are there any unknown devices?
Did you remember to
Originally Posted by Geodude074 View Post
When you uninstall the driver, make sure you check the option to DELETE the driver as well. Otherwise when you try to reinstall it, it will just reinstall the old driver again
Driver instal with WinXP
I went around with this problem after both my Win7 laptop and WinXP desktop both recognized my N7 2013 the first time I connected to them. I had no problem dragging and dropping files.
I had then returned the tab back to BB for a exchange for another. This time after setting up the tab and setting the MTP file toggle and USB settings correctly......The Win7 laptop worked find and recognized the N7 just like it did on the first tab. But now the WinXP desktop did not work and only saw the N7 as a ABD device.
You may already have the correct drivers (if not those are available here in several posts). You just have to direct windows driver update to the correct place for the MTP driver. Here is how i did it.
1. Open up the Device Manager on your PC and locate the Android device it sees. Select the update driver option and you get to the "Welcome to the Hardware Update Wizard" screen.
2. In this window it asks "Can Windows connect to Windows Update to search for software?" Select the 3rd option ' No, not at this time"
3. In the next window "This wizard helps you install software for...." Select the 2nd option "Install from a list or specific location (Advanced)
4. In the "Please choose your search and installation options" window... go down to the bottom and select "Don't search, I will choose the driver to install" option.
5. Now finally the window we need..... "Select the device driver you want to install for this hardware" The "show compatible hardware" button should be selected...if not check that box. You should see 2 choices in the "Model" area..... Google Nexus ADB Interface" and what we need to select " MTP Device" click on the MTP Device and hit next......it should install and your Nexus 7 should then show up properly.
Hope this works for all that have had a hard time as I did....I just found it odd after getting a replacement N7 my XP desktop did not recognize it as it did to the original one I used the day prior.
un1bomber said:
Shows up on my laptop but not on my desktop, have tried back and front USB ports
have uninstalled USB drivers, reinstalled USB drivers (universal adbdriversetup6 downloaded from xda sources)
downloaded android SDK manager and installed whatever USB stuff it had there
used USBdeview to remove any nexus 7 related things and then re-install USB drivers
Cannot for the life of me figure out what's going on... can anyone help me please
When I plug it in my desktop it makes the sound like something got connected... even has the safely remove hardware thing with nexus 7 there, but nothing in my computer
also have tried with/without USB debugging
tried removing my rom and flashing stock etc
Nothing has worked so far
Click to expand...
Click to collapse
Just go in settings then storage and then computer usb connection by opening preferences in storage and then make sure mtp is checked.
Thank you guys SO MUCH for the help... I actually just returned my unit to staples because those POS wont give me a price adjustment vs google play
Will buy another one from google play and follow steps in the thread!
un1bomber said:
Thank you guys SO MUCH for the help... I actually just returned my unit to staples because those POS wont give me a price adjustment vs google play
Will buy another one from google play and follow steps in the thread!
Click to expand...
Click to collapse
We are always here to help.
I remember few years back I installed miui ROM on my xperia n couldn't connect to PC , only to realise USB wasn't turned to mtp by default. I thought it was a bug, tried everything even to fix it only to realise this.
Thanks a lot !!! This solution worked perfectly for me
You saved lots of time for me
Thanks a ton :good::good::good:
Best regards,
RR215 said:
I went around with this problem after both my Win7 laptop and WinXP desktop both recognized my N7 2013 the first time I connected to them. I had no problem dragging and dropping files.
I had then returned the tab back to BB for a exchange for another. This time after setting up the tab and setting the MTP file toggle and USB settings correctly......The Win7 laptop worked find and recognized the N7 just like it did on the first tab. But now the WinXP desktop did not work and only saw the N7 as a ABD device.
You may already have the correct drivers (if not those are available here in several posts). You just have to direct windows driver update to the correct place for the MTP driver. Here is how i did it.
1. Open up the Device Manager on your PC and locate the Android device it sees. Select the update driver option and you get to the "Welcome to the Hardware Update Wizard" screen.
2. In this window it asks "Can Windows connect to Windows Update to search for software?" Select the 3rd option ' No, not at this time"
3. In the next window "This wizard helps you install software for...." Select the 2nd option "Install from a list or specific location (Advanced)
4. In the "Please choose your search and installation options" window... go down to the bottom and select "Don't search, I will choose the driver to install" option.
5. Now finally the window we need..... "Select the device driver you want to install for this hardware" The "show compatible hardware" button should be selected...if not check that box. You should see 2 choices in the "Model" area..... Google Nexus ADB Interface" and what we need to select " MTP Device" click on the MTP Device and hit next......it should install and your Nexus 7 should then show up properly.
Hope this works for all that have had a hard time as I did....I just found it odd after getting a replacement N7 my XP desktop did not recognize it as it did to the original one I used the day prior.
Click to expand...
Click to collapse
If nothing else here has helped you solve this issue, check my thread, it should be of some help to you...
I'm having an issue where I can connect to my laptop in debug mode, but I'm not able to connect in the MTP mode with debug turned off. I expected to be able to mount the device storage in either mode.
Is that correct? If so, any ideas? I do notice I can't seem to get the MTP driver to stay in device manager.
Rick
If anyone can give advice it would be appreciated.
So I bought an Ouya from a friend that had CM11 on it and still some of their apps ect
I plugged it in, I noticed the screen over cast but the device was working, I went into CM11 and did a factory wipe (for a fresh start)
CM11 booted back up, but the controller wasnt working anymore. Took me a while to access the menus with the keyboard but I got the controller working.
I got fed up with the screen issue and the hassle and thought it was CM11s problem so I wanted to see what stock ouya was like
I alt + print scrn + i and flashed stock Ouya
now all I see when turning on the Ouya is the Orange Ouya logo, and alt + print scrn + i does NOT longer take me into recovery.
What can I do here? Thanks in advance.
Can you turn on the ouya, then plug in a usb cable and test whether your pc sees the ouya? If so, you should be able to use a tool like ouya toolbox to flash cwm, then boot into recovery. I would highly recommend installing the latest boot menu, so you don't have to time the alt-ps-i in the future.
jerry, thanks for your reply
My pc recognizes the ouya but I haven't been able to get the drivers properly installed
I've tried win xp, win 7 and 8
it loads as a mtp device. I've got android sdk installed but that's as far as I've got
well it's been a few days and I can't figure it out
when I plug the ouya into my pc it tries to install drivers for "MTP device"
it fails. tried diff ports. sdk installed. windows 7 and windows xp. no luck
anyone know what I can do? I can't get the Google usb drivers to install at all
Can you check the USB ID of the ouya when it's connected to your PC? Under linux you can do a simple lsusb, but under Windows, I think you'll need to install a little utility to list all of the devices on the USB bus.
Edit: You can get the ID in Windows using the Device Manager. Under the Details tab Hardware Ids
The Ouya vendor id is 2836. The device ID will be different depending on what state the Ouya is in. That might give us a clue as to what's happening.
Edit2: There are a number of threads out there about adding the Ouya hardware ID to android-sdk\extras\google\usb_driver\android_winusb.inf in order to get the Ouya to be recognized by the Google drivers
jerryfath said:
Can you check the USB ID of the ouya when it's connected to your PC? Under linux you can do a simple lsusb, but under Windows, I think you'll need to install a little utility to list all of the devices on the USB bus.
Edit: You can get the ID in Windows using the Device Manager. Under the Details tab Hardware Ids
The Ouya vendor id is 2836. The device ID will be different depending on what state the Ouya is in. That might give us a clue as to what's happening.
Edit2: There are a number of threads out there about adding the Ouya hardware ID to android-sdk\extras\google\usb_driver\android_winusb.inf in order to get the Ouya to be recognized by the Google drivers
Click to expand...
Click to collapse
Hi jerry, Ive tried editing the google usb driver inf file but no luck. theres a 2nd inf file in most steps but I dont have the other android folder.
here is the device instance ID in windows xp
USB\VID_2836&PID_0012\015D8CA2FD2BF006
the steps ive done are.
download android sdk
install google usb driver
download google usb driver stand alone
edit inf file
try to detect drivers - fail
When you say "try to detect drivers - fail" what are you actually doing?
If you haven't already, you should go into Device Manager, right click on the ouya, select the driver tab, choose update driver, choose have disk, then navigate to the folder with the usb driver .inf that you've edited.
When you do that, it should either install the driver or tell you no driver was found for the device.
I'm sure you tried lots of times and I apologize if this is no help, but I just kept banging on alt + prn scrn on mine until it finally went into recovery and a factory reset fixed it. I would imagine that's all that yours needs...just need to find a way to kick it into recovery.
Edit - I did have to install the newest Google driver from the Android SDK Manager as well, and did not need to modify like you used to need to do IIRC.
I have tried very hard to get USB Diag mode to work, but haven't managed to find a way.
Things I've tried:
echo 1 > /sys/devices/platform/lg_diag_cmd/diag_enable
Looking through the hidden menu for USB diag
Whatever I do, I don't get the diag device in Windows Device Manager, and can't connect with QPST and friends.
So if anyone knows a way, I'd be grateful! I want to enable Band 12 and AWS on my H815.
in the hidden menu (2776434#*#) scroll to bottom to Port Test check (very last thing on T-MO version), on the next screen touch to enable it. Plug it in and it should be enabled, thats I did it on my T-MO version
FWIW, it is "277634#*#" on my T-Mobile LG G4
I hope this video help you to enter qualcomm diag mode https://www.youtube.com/watch?v=DGCU9oDu43g, personally I had the wrong drivers installed, make sure you have usb tethering enabled, usb debugging and port enabled too!, If you are on an aosp may not work. You can found drivers in this video https://www.youtube.com/watch?v=Vh52x5_1FMg
Is there a trick to make MTP work under Windows 10? I used it once (via the swipe down, hitting the USB Mode and changing to MTP) before enabeling develper mode.
Now in Developer mode I changed it under Network --> USB Configuration --> MTP but my tablet does not show up on my PC. Do I need to change anything else? Already tried switching between the USB configurations, rebooting the device and so on, but nothing seems to work...
May be wrong but:-
W10 out of the box doesn't support MTP. You may need to install the Android Debug Bridge USB driver on your Windows machine and then connect that driver to your Android device. With the tablet disconnected open W10 Device manager, now connect the tablet to the USB port. Device Manager screen should immediately refresh and show 2 lines at the top of the screen:
Android Device
Android Composite ADB Interface.
Assuming your cable is ok then the absence of these two lines indicates you need the driver installed. The driver is installed as part of Google's Android Studio in the Platform Tools sub directory. If you just want the drivers then they are available to download (no links ) There are automated methods , see http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 or Nexus Root Toolkit does it. ( You should have usb debugging enabled in the tablets Developer menu)
Once the drivers are installed then when you enable MTP via the Notification or your menu "path" then Device manager will show the tablet under the "Portable Devices" line.
I originally got my laptop to work with the Pixel C using Window 8.1. I had trouble at first finding a driver that would work. I tried various drivers, but I eventually got it to work with PDANet. I believe that the trick for me was to first use PTP to get the correct drivers installed. You should be able to switch from PTP to MTP once PTP is working correctly.
I have subsequently upgraded from Windows 8.1 to Windows 10. I had a similar issue again with the drivers. I first used PTP to get the proper driver installed and then switched to MTP.
I always use the pull down menu on the Pixel C to change from charging to PTP once working and then to MTP.
With PTP, you should be able to see the Pixel C drive on the computer but only able to access the photos. Once you switch to MTP, you should see all the folders.
For fastboot, you need to use PTP and not MTP.
Found this post via Google, it's an issue for me with the Pixel phone, too. Photo mode works normally, MTP doesn't.
For others who also find this post, I read that supposedly the Pixel phones install ADB drivers automagically, but this isn't happening for me, and @SmokinCharger's fixes haven't worked either.
Hey all,
Just wondering if there is a way to manually update drivers for Fire TV/Stick/Android in general? I know this is an odd build of Android TV, but it just occurred to me after all my years of using Android, I have never had to try to update drivers. Recently I purchased two classic SNES controllers (USB) to use with my Fire stick via OTG adapter. I was unable to map or recognize X,Y,L, and R buttons. All other buttons were recognized and functional (select, start, A, B, D-Pad). I checked on my android phone (Note 4) and same issue. I then checked on my PC and the buttons were recognized. I then checked on my Nvidia Shield TV and it was again recognized, making me think it was a driver specific issue. Thanks in advance.