Page 1 of 1
Android and virtual box
Posted: 18. Feb 2012, 21:59
by markkirby
Hi
Im having a problem with virtual box and my samsung galaxy ace
The phone works fine except when I put it in downloading mode I get thiss error
Failed to attach the USB device Sasmsung MSM7x27 [0100] to the virtual machine xp.
Failed to create a proxy device for the USB device. (Error: VERR_READ_ERROR).
details
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Console
Interface:
IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}
Can anyone help im trying to flash a custom rom with odin
I have ubuntu host and xp quest
thanks
Re: Android and virtual box
Posted: 24. Feb 2012, 06:23
by nabeer75
I have the exact same problem! If anyone can help it would be much appreciated. Also running XP from Ubuntu 11.10, and trying to connect samsung galaxy ace in downloading mode for firmware flashing in odin.
Re: Android and virtual box
Posted: 24. Feb 2012, 07:47
by stefan.becker
Extension pack installed?! VBOX Version? Host? Log file?
Re: Android and virtual box
Posted: 24. Feb 2012, 08:30
by nabeer75
VBOX version 4.1.8 r75467 Extension pack is installed. I have no problems with other usb devices. My Host is ubuntu 11.10.
The error I receive:
Code: Select all
Failed to attach the USB device Sasmsung MSM7x27 [0100] to the virtual machine XPpro.
Failed to create a proxy device for the USB device. (Error: VERR_READ_ERROR).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Console
Interface:
IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}
Log file:
Hope that's alright.
Nick.
[mod edit] Please post log files and other bulky texts as zipped attachments. I have done it for you this time.
Re: Android and virtual box
Posted: 24. Feb 2012, 11:49
by mpack
@nabeer75, you may want to read
this discussion.
Re: Android and virtual box
Posted: 24. Feb 2012, 15:35
by nabeer75
I had a look through, and have indeed performed the steps such as adding the user to the vbox group, adding a filter to vbox, and disabling usb 2.0, but no joy. The last post, this:
For me, this turned out to be a permissions issue with a device node in the Linux host file system.
In my case (using a USB JTAG programmer in the guest OS, Win XP Pro SP3), chmod'ing the perms on /dev/usb/hiddev0 immediately solved the problem.
I haven't the first clue how to follow. I'm not all that linux literate yet! Of course any help would be appreciated, but please allow for some relative inexpertise on my part!
Thanks.