So im having trouble with updating my XM SINGLE
The two laptops I have both are on linux mint one of them is running windows in a virtual box. I have successfully mounted the phone but cant figure out how to ge the vitual box to see the phone
What I find puzzling is the lsusb command in terminal the phone is there
Im a beginner in terms of linux but learning fast
I reckon its the drivers for the phone are needed and from my research I have found very little
Gmtp is working and a couple of other ways ive tried but with no luck with the vb machine
Am I missing something obvious in the settings of the virtual box
hit thanks if I helped
sent from rooted xts thanks djrbliss
Related
Alright, so the issue is... I have the SDK... and it won't work on either of the operating systems I run. I am running Ubuntu 9.10 and Windows 7, both 64bit. There are two main aspects I am after with it. Using DDMS to take screenshots and mess with stuff on devices, and the virtual Android system. On Ubuntu, DDMS comes up, but it shows my device as just ?????? and I am unable to do anything. I have already tried putting in the rules thing I found all over google, and it has done nothing. The correct IDs were in as well. On Windows, why I try to use it... it pops up with a command prompt screen for a split second and does nothing. On both Ubuntu and Windows, when I try to use a virtual device, all it does is crashes. This is with all different settings. So, is there anyone that can help me out with these issues? I just spent 3 hours of google searching to no avail. None of the fixes or anything I have found made any difference. Well... that's not true... one of them made DDMS not work at all... but that just needed to be restored. Any help would be appreciated. Thanks!
Update: Doesn't work on the gf's laptop either which is running on Windows XP. So, it doesn't work on Ubuntu, Windows 7, or Windows XP. Wtf does this run correctly on?
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
Hello again, I am having a bit of trouble as of right now and i would like some feedback, now a little back story, I used to be into rooting and such, always dong it for my friends and i was quite good. Then came my hiatus of about a year or so and now im back and i guess i dont remember exactly how to do this and i have screwed up a friend of mines kindle
My dilemma
I have gone in with the rooting process with kfu and i went and changed the drivers to adb and then i went into bootload and changed it to fastboot, and i have forgotten that windows frowns upon such a thing and now the kindle is stuck in a bootload at the stock booting screen of the white and red "KindleFire" and every time i connect it i get and error message saying that the device isnt recognized by windows and it is probably malfunctioning (which we all know it isnt) and i want to change it back to normal bootload but kfu wont recognize it either because of windows. I have tried to re-install the drivers to get it to be recognized as an android device again but alas that dosent seem to work either. So it would most appreciated if i could get some help on this one.
well this post can be ignored because i figured it out
If its a windows problem try running a VitualMachine of a linux distro and try using fastboot there. Or create a live usb of a linux distro and temporarily run linux on your pc.
I used this to get Ubuntu on my laptop. http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/
tobiascuypers said:
If its a windows problem try running a VitualMachine of a linux distro and try using fastboot there. Or create a live usb of a linux distro and temporarily run linux on your pc.
I used this to get Ubuntu on my laptop. http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/
Click to expand...
Click to collapse
well i would like to avoid to using linux but if i really have to i will
is there any possible way to do it without linux
I've somehow managed to hardbrick my D855. I'm assuming that I'll have to use the shortpin method to get it working, but all the guides I've found so far use Windows, and I'm running Linux. I don't really feel like setting up Virtual Box on my crappy laptop, so can anyone help me out with doing this natively in Linux?
shockwaverider said:
I've somehow managed to hardbrick my D855. I'm assuming that I'll have to use the shortpin method to get it working, but all the guides I've found so far use Windows, and I'm running Linux. I don't really feel like setting up Virtual Box on my crappy laptop, so can anyone help me out with doing this natively in Linux?
Click to expand...
Click to collapse
As far as i know...You can't unbrick it with Linux. As you would need boarddiag tool which only comes as a windows executable.
I suggest you create some sort of On-The-Go windows installation and boot from a flash drive if u don't wanna through the whole VBox process or install Windows on ur physical machine.
mickeyasamoah said:
As far as i know...You can't unbrick it with Linux. As you would need boarddiag tool which only comes as a windows executable.
I suggest you create some sort of On-The-Go windows installation and boot from a flash drive if u don't wanna through the whole VBox process or install Windows on ur physical machine.
Click to expand...
Click to collapse
Thanks for the reply. Not sure what I'll end up doing, my laptop is on its last legs - only one working usb port and a fried keyboard. And the working usb port is usb3, and I've had bad luck installing Windows from that port in the past. There's also no dvd drive. And since I'm only interested in using the phone as a Plex receiver for my stereo anyway, there's no real rush.
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.