Let me start off with the basics...
Nexus 7 (2013) - Stock Rooted 5.0.2
Variant: flo 16G
HW Version: rev_e
Bootloader Version: FLO-04.04
Tried MTP on/off - Doesn't work
Tried USB Dev on/off - Doesn't work
Tried on Windows 7/8.1 - Doesn't work
Tried on Ubuntu 14.04/14.10/Linux Mint 17/17.1 - Doesn't work
EVERYTHING WORKS on Mac OSX Maveric and Yosemite!!!
MTP and ADB and Fastboot do not work at all. In linux, lsusb shows nothing. In Windows, Device manager shows no changes (also, never plugged it in before this and followed Wug's toolkit howto exactly).
When I plug the device into my girlfriend's MacBook Pro (10.10 Yosemite as well as when she was on Maverics) everything works. On her Mac, ADB works, Fastboot works, and MTP (using the android transfer tool) works flawlessly. This is using the same exact USB cable that I used on all other systems. I tried this on my Linux laptop and a Windows desktop. Triend all USB ports. It seems my tablet will only work with a Mac.
Any ideas??
Does the laptop or desktop recognize the tablet? Is the Android SDK up to date?
I don't use the full SDK. I use android-tools-adb and android-tools-fastboot which is a cross platform toolset. This works for 2 of my phones, my ouya, and her phone so I know its just the tablet. The 3 phones and the ouya work on the windows desktop and laptop but not my tablet. As soon as I plug the tablet into her Mac, it is detected right away. I really wish I can solve this... I hate taking her MacBook from her every time I want to tinker with things.
Related
Hey guys, I have been trying to get Windows 7 Drivers to work properly with adb on my A100. I have a Virtual Machine of Windows 7 and I have manually added the USB device ID's to the VBox settings for the VM client, Windows 7 sees the device ok and will mount the device fine via MTP. I can even get the drivers to say that they are working properly for the device, but when it all comes down to it they aren't.
I have tried using the ADB driver from the Android SDK which of course won't work out of the box since the device ID's aren't made for the Iconia A100, however I modified them to match the vendor/device IDs, but still - no go. I can do ' adb devices' and it will either show the device as offline or will just say the name and serial#, but when I try to connect it either says 'device offline' or it will give me a adb protocol error.
I don't know what else to really try, and at this point I am really thinking Virtualbox isn't passing the USB properly to the Guest OS, but what is odd, is my HTC WildFire S will work fine with adb (same binary).
I have also tried the Acer drivers that are available on the Acer Website, as well as a few other device drivers that I can't recall off the top of my head.
I guess some people are wondering if this is working in Linux why am I so concerned about getting it to work in a Virtual Machine running Windows. In short the answer is: I am developing kernels and recovery for the A100 as many may already know, and I am working on some automated installers that are cross platform compatible and I need to test the Windows side of things before I make releases, yet it's a bit hard to do when Windows is such a PITA when it comes to anything Android.. Yea, I'm a Linux person I know it's obvious - but I need this working somehow in a Virtual Machine because I'm not willing to do a native install of Windows on any of my machines, simple as that lol..
Anyone who may have a Virtualbox install of Windows 7 (or vista) that has adb working with their A100, please let me know the adb drivers you used and if at all possible attach them here, or give me a direct link. I greatly appreciate the help guys!
Here is a snippet of the troubles:
Code:
List of devices attached
037c624643a033d7 device
C:\Users\Lance\Downloads\godmachine81-Acer-A100-TWRP-Installer\godmachine81-Acer
-A100-TWRP-Installer-c8ccd42>adb shell
error: protocol fault (status 72 6f 6f 74?!)
**Edit: I kinda found a solution to my own problem, but not a great one. The problem was with EHCI 2.0 in VirtualBox, when this setting is disabled it will allow adb to work correctly, however on Windows 7 it will break the USB host so there is no possible way to use the tablet period, with Windows XP however it works fine. Windows XP has the exact same issue, but the USB Hub will actually work without EHCI 2.0, not really sure if there is a workaround to the Windows 7 problem, but I didn't really mess with it long - I'd say one might be able to uninstall the USB adapter and reinstall it after disabling EHCI and then also reinstall the Acer drivers. I got tired of fooling with windows 7 and just installed a copy of XP, wrote the batch script for windows, and will soon be uninstalling most likely haha.. Hope this might be some good info for others who run into a similar issue
Hi
Windows 8.1 fresh install.
Added Minimal ADB & Fastboot and Google USB Drivers.
Nexus 5 is detected by ADB & Fastboot and works fine using same cable and Windows 8.1 machine.
Nexus 7 2013 is detected by ADB, but not by fastboot.
When I plug the 7 in when booted into bootloader, Windows plays the connected, then disconnected sounds.
Nothing appears in device manager so I can't update the driver.
Connect the 7 to my other PC and it works fine.
Any ideas how I can get the 7 detected correctly in fastboot ?
Thanks
Do you have the Android SDK installed?
Hi
Thanks fro the reply.
On either the windows 8.1 machine I don't have the SDK installed.
I downloaded the minimal adb / fastboot setup which does work fine for the nexus 5..just not the 7 flo in bootloader mode.
Same setup on the other windows PC and they both work !!
I'm going to double check the drivers on both and if there is a any difference. If there is I'll update the fastboot drivers when the nexus 5 is plugged in and detected OK.
See if that helps
Any other ideas ?
If you have a USB 2.0 port, use it. USB 3.0 ports sometimes don't work right with ADB/fastboot.
When I connect the Pixel C for PTP it shows up in Nemo and I can transfer photos. USB debugging is selected on the tablet. adb and fastboot are installed in Linux. Switching to MTP removes the tablet from Nemo and I won't be able to transfer media.
An old Galaxy Note 10.1 and the One+one connect to my Linux PC without problems. Does anyone here has a clue as to what might be causing this problem.
I got some help on the Google forum but until now I had no luck in solving this problem.
My PC is running Linux Mint 17.3 Rosa 64-bit with the latest 3.19.0-49 kernel.
Pixel C build# MXB48T with feb 1st security patch.
Oshin_ said:
When I connect the Pixel C for PTP it shows up in Nemo and I can transfer photos. USB debugging is selected on the tablet. adb and fastboot are installed in Linux. Switching to MTP removes the tablet from Nemo and I won't be able to transfer media.
An old Galaxy Note 10.1 and the One+one connect to my Linux PC without problems. Does anyone here has a clue as to what might be causing this problem.
I got some help on the Google forum but until now I had no luck in solving this problem.
My PC is running Linux Mint 17.3 Rosa 64-bit with the latest 3.19.0-49 kernel.
Pixel C build# MXB48T with feb 1st security patch.
Click to expand...
Click to collapse
not much help I'm afraid but I can at least report a similar issue.
I have had exactly he same problem running with Ubuntu 14.04 x64.
I have a Nexus 10 which connects quite happily using MTP.
I can quite happily use MTP between the Pixel and Windows 7x64.
I have worked round the issue by using FTP transfers - as I think there must be some incompatibility between the Linux MTP and the Pixel C!
Oshin_ said:
When I connect the Pixel C for PTP it shows up in Nemo and I can transfer photos. USB debugging is selected on the tablet. adb and fastboot are installed in Linux. Switching to MTP removes the tablet from Nemo and I won't be able to transfer media.
An old Galaxy Note 10.1 and the One+one connect to my Linux PC without problems. Does anyone here has a clue as to what might be causing this problem.
I got some help on the Google forum but until now I had no luck in solving this problem.
My PC is running Linux Mint 17.3 Rosa 64-bit with the latest 3.19.0-49 kernel.
Pixel C build# MXB48T with feb 1st security patch.
Click to expand...
Click to collapse
Hi
I have Mint 17.3 Cinnamon 3.19.0-32 kernel
My Pixel C is also on MXB48T
I just plugged the tablet in, it defaulted to PTP. Switched to MTP and Nemo shows Pixel C as a device and I can browse internal content.
Looking at my installed packages, I have libmtp etc. It looks like they got installed when I installed VLC
Maybe try installing the tools package ? https://apps.ubuntu.com/cat/applications/precise/mtp-tools/
MTP has always been a pain in the a$$ in Linux, mostly because it's a Microsoft technology, MTP on Linux has always been hit or miss with me on Linux, after hours of installing different packages or getting it to finally show up but transfers slowing to a crawl, I would just boot back into Windows and have it done in a few seconds. Take a look at dmesg (dmesg|tail in the terminal) after you plug in your Pixel and switch it to MTP to see if there's any issues. I have Arch Linux on my desktop, but I'm in Windows now so I'll give it a try later and report back if I have any odd issues. As acrickie stated above, bypassing MTP in favor of some other protocol is your best bet, I usually use ES File Explorer since you can enable FTP in it and transfer things over wifi or simply connect to your box via SFTP/SMB from within ES and go about your business.
hey guys...
it sucks so hard.
My setup:
Ubuntu 14.04 x64
Windows 10 in Virtualbox
LG G3 (stock 5.0)
My goal:
Flash latest kdz (marshmallow) with a tool available for linux.
-or-
Update my phone to Marshmallow using LG Mobile Support Tool / LGUP / LG PC Suite in a Windows10-VM on Ubuntu host.
My status:
Linux: Did not find any flashing tool which works with Linux.
VM:
Windows 10 - check.
LG tools - up and running.
But... Neither Windows nor - of course - the different LG tools recognize my phone.
It seems that Ubuntu will correctly recognize the G3 when it's connected as PTP-device.
Same with "adb devices". The celly is only recognized when connected via ptp.
Strange: Though not listed with adb devices I can access my files over mtp...
Unmentionable that the whole bunch of the windows tools seem only to work when device is connected correctly via mtp.
Is really the only way to run this update finding a windows-buddy?
Solutions, anyone? #desperate
"Work-Around":
Today the ota-update was rolled out. Next problem was that my phone is encrypted and the update can only be installed when the phone isn't encrypted. So: Decryption in progress.
But: I'm still interested in a solution for the ones who a working with linux.
I've tried to upgrade an (old) LG D605 using the windows Flash Tool under a VirtualBox VM (running Windows 10) and using the drivers linked in that website (after setting UP VBox to use the phone USB device in the guest), worked as expected.
Try vmware or parallels
Hi, I am trying to connect my 1P7T to Windows 7 and 10, both in Virtualbox guests. But I cannot get the prompt to come up on the phone. It connects just fine to the Linux host, but not to Windows, it has worked before when I had my system on a different version of Linux but not now. Unless there is some better way to run fastboot commands on my phone in Linux, I am all ears. But I would really like to just use the All in one tool in windows.
Thanks
Got it all figured out, first I had the wrong Virtualbox extension pack installed. I still could not get it to work when set to USB 3.0. I set it to USB 2.0 and the phone is now connected and authorized.
Glad I figured it out on my own, but also good for someone else to know.