Related
Hello folks.
I'm working on custom kernel & ramdisk on Linux and was tired to plug/deplug the phone from my Linux workstation to a Windows netbook to flash it...
..Before I realized that Odin works perfectly well on a XP VM on a Ubuntu 10.4 host / Linux 2.6.35.2 !
Big bonus of this setup is that the software virtual USB switch allow you to plug/deplug the phone without touching any hardware.
Odin re-discover the phone and you can flash next millisecond
PS : this has maybe already has been reported, but I know few people who thought it did not work.
I never had any issues flashing my old Hermes through a VM XP machine on my hackingtosh back in the day, as long as I selected the correct USB port to stop OSX trying to grab hold of it.
Not quite "off topic" but thought it would put a few minds at rest
FlanFlinger said:
I never had any issues flashing my old Hermes through a VM XP machine on my hackingtosh back in the day, as long as I selected the correct USB port to stop OSX trying to grab hold of it.
Not quite "off topic" but thought it would put a few minds at rest
Click to expand...
Click to collapse
VMWare 3 on a Mac, no go for Odin. Can't get the USB to hold onto the phone, only device I ever had trouble with.
Gonna try VB...
distortedloop said:
VMWare 3 on a Mac, no go for Odin. Can't get the USB to hold onto the phone, only device I ever had trouble with.
Gonna try VB...
Click to expand...
Click to collapse
I thought that Vmware was better than VirtualBox for USB tweaks, maybe this is history !
Tell us aware of your tests on Mac
In download mode, SGS appears as Gadget Serial [021B] in VirutalBox.
Pretty good news, I should really clean the dust off my XP virtual machine!
Is Samsung Kies working too?
VMWare 7 in Ubuntu is fine too...
thunderteaser said:
Pretty good news, I should really clean the dust off my XP virtual machine!
Is Samsung Kies working too?
Click to expand...
Click to collapse
Kies in VirtualBox fine...VMWare fail MTP driver...
I finally just installed Windows 7 in Boot Camp. VM would never see the phone
braintheboss said:
Kies in VirtualBox fine...VMWare fail MTP driver...
Click to expand...
Click to collapse
Thanks for your feedback! I replaced VMWare with VirtualBox many years ago and this kind of issues was the main reason, you should stick to VirtualBox!
Can someone tell me how to prevent my mac to grab my phone on usb? I always get an error from my virtualbox, thay device is used by someone else.
Sent from my GT-I9000 using XDA App
Can't get the Galaxy S i9000 to connect to VirtualBox either.
I select Gadget Serial, it waits a minute or so, then pops up this error message:
Failed to attach the USB device Unknown device to the virtual machine XP.
Could not find a USB device with uuid (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
Callee RC: NS_ERROR_INVALID_ARG (0x80070057)
Click to expand...
Click to collapse
After that, sometimes the phone still appears as available to connect, others it doesn't. Very similar to the VMWare problem.
This is on my Late 2009 MacBook Pro with Snow Leopard. Doesn't matter which USB port I select. I might try a powered hub in between the phone and the laptop. Connecting the SGS to the laptop USB is always a bit of hit and miss for both adb sessions and even mounting the sdcards. I frequently have to unlplug and replug the phone to get a connection. I've seen a few others report the same.
Must be an issue with OS X itself, but to make sure I'll have to try this on my Mac Pro desktop.
I'll report back any success, but I'm not hopeful, I've yet to read a report of someone successfully using Odin in a vm on a Mac.
I'll pile on with my test results. Thus far, under Mac OS X 10.6.4, I have not successfully connected the Vibrant to a VM USB in any Windows virtual machine with the Samsung USB drivers installed. I tried vmware fusion 3.1.1 and the latest virtualbox, 3.2.8. Both failed to recognize the phone when attempting to mount it. No issues in the Mac host environment or Bootcamp. The problem is limited to the VM environments under the Mac host environment.
If anyone has successfully connected the Vibrant to a Windows virtual machine running under vmware fusion or virtual box for Mac please report your results. I did quite a bit of searching and found no successful results with this combo. Thanks.
UK
Appears to be a lost cause for Mac owners who won't boot camp.
ukchucktown said:
I'll pile on with my test results. Thus far, under Mac OS X 10.6.4, I have not successfully connected the Vibrant to a VM USB in any Windows virtual machine with the Samsung USB drivers installed. I tried vmware fusion 3.1.1 and the latest virtualbox, 3.2.8. Both failed to recognize the phone when attempting to mount it. No issues in the Mac host environment or Bootcamp. The problem is limited to the VM environments under the Mac host environment.
If anyone has successfully connected the Vibrant to a Windows virtual machine running under vmware fusion or virtual box for Mac please report your results. I did quite a bit of searching and found no successful results with this combo. Thanks.
UK
Click to expand...
Click to collapse
Thanks to fresh discovering, you will be able to flash from the phone itself soon
supercurio said:
Thanks to fresh discovering, you will be able to flash from the phone itself soon
Click to expand...
Click to collapse
This is exciting.
this thread is definitely NOT what I had hoped to find after trying to use odin under VMWare/Win7 (MBP 2009)
I'll report back if I figure out anything. I've had similar battles with activesync/WMC under VMWare as well, and I've got things playing nice after some tinkering
Was a little worried about using virtual machines to flash my favorite toy, but this thread was the push I needed to give it a shot. Plus, seems like there's a fix to get out of almost any brick you manage to install on your phone, even if you have to build a JIG its not expensive.
So gave it a shot and it worked like a charm, Mint/Ubuntu 10.10 host using Virtualbox. One less reason to ever use Windows 7. Even when I don't boot it Windows breaks, I swear its a scheme to keep people who fix Microsoft products employed......
Supercurio that mean "Odin in Recovery" ? or im think in a false way? to flash tar files in recovery..
Sent from my GT-I9000 using XDA Premium App
Wow, you might become an archaelogist if you managed to bring back this thread from the ashes! We now have Heimdall, which is GNU/Linux native. Give that a shot.
I ever used Odin in a VM of Windows 7 over Ubuntu 11.04.
Heimdall is only for 64bit system and i user a 32bit version.. so...
But..Every flashed i did went good
I keep encountering a problem when I try to connect using PC MODE. The driver never installs any which way that I try. Reinstalling drivers restarting computers... blah blah blah. I have tried different roms and they all have the same problem. It seems that only the stock rom works with the existing drivers. Does anyone else have this issue??? Any Help???
I recommend looking around for the drivers. They can be found all over the forums and the internet. I'll see if I can locate them and post a link.
Sent from my DROIDX using XDA App
If there are different drivers than the original ones I would appreciate the link. Thank you in advance.
zillahakzor said:
I recommend looking around for the drivers. They can be found all over the forums and the internet. I'll see if I can locate them and post a link.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
this needs to be in general
btw: try taking of usb debugging before connecting it in pc mode
Tried that already and I still have the same issue. Come on.. I can't be the only one out there with this problem. Also why should this be in "general" when it pertains to running custom roms. It's not like I am asking about how something works.
I think this is a legitimate issue with running custom roms i which i am surprised no one has addressed. Its not like I have not searched the forums. So if this problem is resolved then show me the sticky please!!
Funnyface19 said:
this needs to be in general
btw: try taking of usb debugging before connecting it in pc mode
Click to expand...
Click to collapse
Takiyon said:
Tried that already and I still have the same issue. Come on.. I can't be the only one out there with this problem. Also why should this be in "general" when it pertains to running custom roms. It's not like I am asking about how something works.
I think this is a legitimate issue with running custom roms i which i am surprised no one has addressed. Its not like I have not searched the forums. So if this problem is resolved then show me the sticky please!!
Click to expand...
Click to collapse
General because i just hooked mine up perfectly on windows using pc mode running liberty 1.5 therefore it isnt the ROM's fault making ANDROID development the wrong forum choice
try here
and read this and the following comments
also restart your computer and keep pressing F8 until a menu comes up press arrow down and click the one about not requiring signatures for drivers
Funnyface19 said:
this needs to be in general
btw: try taking of usb debugging before connecting it in pc mode
Click to expand...
Click to collapse
Agreed and done.
Thanks for the help guys. I'm not trying to be a ****. I will give it one more shot. At this point I don't know what to do. I have been pulling my hair out. I wanna use the liberty 1.5 rom but without the ability to dock my phone in PC mode it will be of no use.
Takiyon said:
I keep encountering a problem when I try to connect using PC MODE. The driver never installs any which way that I try. Reinstalling drivers restarting computers... blah blah blah. I have tried different roms and they all have the same problem. It seems that only the stock rom works with the existing drivers. Does anyone else have this issue??? Any Help???
Click to expand...
Click to collapse
http://www.verizon-phones.org/verizon-motorola-droid-x-usb-drivers-pc-charging-drivers-download.html
well i turned off debugging. and nothing turned it on and nothing. Tried the drivers from that link that you guys posted and same thing. Could it be that I am using Windows 7? It's a clean install of Liberty 1.5 and I uninstalled the newer 4.8 drivers and installed the 4.6 drivers from the link. Restarted and still nothing. What am I doing wrong? if I restore my ROM back to the original stock everything works fine and I can sync with windows media and all that. The other way is a nogo. Help?
kdkinc said:
http://www.verizon-phones.org/verizon-motorola-droid-x-usb-drivers-pc-charging-drivers-download.html
Click to expand...
Click to collapse
The information below is what comes out of the event viewer. Maybe it is just a windows error. But after uninstalling and reinstalling the drivers why would it not work? Do I need to start deleting crap? I will try to install on another PC see if I have the same issue.
Edit--- Just tried it on another pc with a Fresh install if windows 7 x64. Installed drivers and same issue as below. What is so special about the stock ROM that allows the driver to function. is there an apk that the custom roms are missing? something must communicate with this driver and allow it to initialize. HELP!??
Log Name: System
Source: Microsoft-Windows-DriverFrameworks-UserMode
Date: 2/10/2011 4:14:44 AM
Event ID: 10111
Task Category: User-mode Driver problems.
Level: Critical
Keywords:
User: SYSTEM
Computer: TRAVELDESK
Description:
The device MTP USB Device (location MB810) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DriverFrameworks-UserMode" Guid="{2E35AAEB-857F-4BEB-A418-2E6C0E54D988}" />
<EventID>10111</EventID>
<Version>1</Version>
<Level>1</Level>
<Task>64</Task>
<Opcode>0</Opcode>
<Keywords>0x2000000000000000</Keywords>
<TimeCreated SystemTime="2011-02-10T09:14:44.126129800Z" />
<EventRecordID>14712</EventRecordID>
<Correlation />
<Execution ProcessID="1028" ThreadID="1456" />
<Channel>System</Channel>
<Computer>TRAVELDESK</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<UmdfDeviceOffline lifetime="{3DA815A7-8803-4B06-936F-03E4D74D1746}" xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/DriverFrameworks/UserMode/Event">
<DeviceInfo>
<FriendlyName>MTP USB Device</FriendlyName>
<Location>MB810</Location>
<InstanceId>USB\VID_22B8&PID_41D8&MI_03\6&321BCAFE&4&0003</InstanceId>
</DeviceInfo>
<RestartCount>5</RestartCount>
</UmdfDeviceOffline>
</UserData>
</Event>
im not exactly sure whats wrong with just usb mode? you can move files on and off it fine and if anything is wrong it is probably some drive/code that is written in with blur/bloat that is removed, idk if it is just saying, maybe you can revert to stock delete moto drivers hook ur phone back up let it install and then root and maybe itll work then
I think you are on the right track. Considering that when I restore the stock rom from backup everything works fine. Drivers install and I can sync my music. Perhaps there is a part of blur that we can put back to fix this issue. I will experiment by taking the blur apks and installing one by one see how far I get. If anyone any better ideas please let me know.
Sent from my DROIDX using Tapatalk
Possible Solution - Help Needed
I think I may have stumbled onto something. While running the stock OS I disabled the StorageMonitorService.apk by renaming it and rebooting. Afterwards I get the same results. I think this apk controls/talks to the MTP Drivers. How do I get this apk from the stock rom to install on the liberty rom. How do I make sure it runs on startup. If this works I think we will be able to put it into all of the AOSP roms. I know it is one of the blur apps but for the extra functionality hardware wise I think it would be worth it. Has anyone even thought about doing this? If not then why?
Also another work around is to use Linux cuz it doesn't need any special drivers lol
Sent from my DROIDX using XDA App
I wish I could. Hard to break away from windoze. got too much invested in it.
Sent from my DROIDX using Tapatalk
I suspect you have the same problem as I do...there doesn't appear to be a 64 bit diag mode driver for the Droid X. If u try this on 32 bit Windows it will likely work.
Sent from my EVO on Cricket using XDA App
I'm so confused here, what seems to be the issue again? LoL. OP- you want to hook up PC mode from your phone but your computer seems to not want to. At least that's what I have gathered from all the posts and no one has suggested the Moto drivers lol
Motorola Drivers; every computer needs them for their Droid X to communicate properly with their PC. I use Moto Connect and why? Because any Motoroa device you hook will be auto-updated once the program is opened up and it also keeps all the drivers up to date.
Download Motorola 4.9.0 Driver with MotoConnect, download it, run the middle option on the bottom left hand corner and you should be all done. Your phone should now sync with your PC. I have used this with 32 and 64 bit Windows 7 computers. All older Windows based OSs' should work fine.
If that does not work, without reflashing the maderstock .340 and starting with a clean slate, the problem might be easy or hard to diagnose both pc and phone side.
Same here!!!!
I'm definitely encountering the same issues. I have installed the latest Motorola 4.9.0 drivers and even doing cleans and reinstalls to no avail.
What's even more odd is that I had recently replaced my phone because of rebooting issues. When I first got it and ran stock... no problems, it would install MTP just fine on both my desktop and laptop both running Win7x64. Once I restored a nandroid to my customized Liberty v1.0... it goes sour.
I even recently reformatted my desktop on a fresh install of Win7x64 and the problem occurs right away after installing the 4.9.0 drivers.
I'm pretty sure that it has something to do with the version being .340 since it only appeared after that. And possibly with ROMs that are based on .340.
I'm going to try Liberty v1.5 to see if it fixes it.
Ok I have found out that there is something in the blur stuff that is part of the stock rom that needs to be running otherwise the drivers on the pc side will not initialize. I have tried liberty 1.5 and it does not work however apex rom seems to have it working. I guess apex may solve me problem. Also for those that keep suggesting that the drivers are the issue. I appreciate it but that is not the issue when using custom roms. The issue is the blur software on the phone. It seems that you need some parts of it to make sure the phone hardware works 100%
If you want to test for yourself take the stock rom and disable blurstoragemanager.apk I think its called the motorola storage manager.
Sent from my DROIDX using Tapatalk
I'm probably going to get flogged for posting such a dumb question but I need to because all my search results have given me a mine field of information and I'm still no further forward.
I've had the S2 for a little while now. I'm familiar with it - so now I want to get it rooted!
I seem to be falling at the first hurdle though. Thing is.............. when i try to open the .exe odin file - the odin box flashes up very quickly but then disappears! It's driving me mad! I'm using windows XP.
Any help would be MASSIVELY appreciated.
Cheers
Tanya
Do you have the Samsung USB drivers installed, and has Kies (if you've installed it) been terminated?
KG56 said:
I'm probably going to get flogged for posting such a dumb question but I need to because all my search results have given me a mine field of information and I'm still no further forward.
I've had the S2 for a little while now. I'm familiar with it - so now I want to get it rooted!
I seem to be falling at the first hurdle though. Thing is.............. when i try to open the .exe odin file - the odin box flashes up very quickly but then disappears! It's driving me mad! I'm using windows XP.
Any help would be MASSIVELY appreciated.
Cheers
Tanya
Click to expand...
Click to collapse
have you tried to run it as administrator and/or compatibility mode ?
Sent from my GT-I9100 using Tapatalk
It works fine on my XP PC. It sounds as though it was a corrupted download. Download again.
I've managed it - at last.
I followed the one step root guide from this forum and opened odin3 not 5 - and it worked perfectly.
My only problem now is that I'm on the last step - I need to start S2 root and click root device - only thing is................... where/how do i start S2root?
Thanks guys
Tanya
well if you have downloaded follow the instructions from the post where you downloaded it from. you have to install Kies so you have the USB drivers, then make sure USB debugging is turned on on your phone, (Go to Settings > Applications > Development > USB Debugging and click yes)
then plug your phone in and run the program by double clicking on the .exe file
doesnt odin reboot your phone once you done the rooting? it should do really..think there is option on there were you can do it....
I have no idea in which section to write this, so General seams like the best choice.
I have a Galaxy Y testing device with a broken boot.img. I am trying to get Odin working in Windows 7 in order to flash a new boot.img to this device, but I can't get the Samsung USB drivers to work and my Windows knowledge is now that great as I mostly work on Linux computers, but no fastboot on Samsung devices.
There are two drivers listed in the Device Manager. The Regular Samsung USB drivers, and something called Samsung USB CDC. It's the CDC I seam to have issues with. It just shows an error message that states "The device could not start (Code: 10)". I have already talked to Samsungs online support, but there is not much support to find there. They know nothing about Windows or how to get anything working on it. And google's search engine, which usually is the best friend for something like this, did not come up with much either.
I should mention that I run Windows in VirtualBox. However, I already have HTC Sync Manager fully working with an older HTC device, so this is not a VBox issue. Also, Windows do find the device just fine, it just can't start one of the drivers.
I have tried installing Kies. I have also tried installing other separate driver versions. Nothing is working.
Search the forums for Naked Drivers, its a complete driver package for a lot of android devices.
Give em a try.
I would post a link but my post count is as such that I cannot at this time.
WooHooGuy said:
Search the forums for Naked Drivers, its a complete driver package for a lot of android devices.
Give em a try.
I would post a link but my post count is as such that I cannot at this time.
Click to expand...
Click to collapse
I love the idea of a multi driver for all devices, much like on my linux boxes, so thanks for that. However, I get the same issue and same error message. I will try to reinstall windows and see if that will work. It has been many many years since I ran windows as my daily OS, but I do remember that formatting was the best way of fixing issues with it. If this is still no go, I will try to put windows directly on my netbook to see if this could be a Virtual problem anyways, but I don't think so. USB stuff is working fine on the Virtual OSX.
Will report back later
EDIT:
Nothing is working. All I have installed, is the naked driver. When I plug-in my HTC Desire or HTC Wildfire S, the driver is working fine. But when I plug-in the Galaxy S3 or the Galaxy Y, I get the "The device cannot start (Code: 10)".
So HTC devices are working, but Samsung is not. The same problem I had with separate HTC and Samsung drivers.
try the one from my link,its latest usb driver exe from kies,worx on win8 64bit too.
http://forum.xda-developers.com/showthread.php?t=1927769
-CALIBAN666- said:
try the one from my link,its latest usb driver exe from kies,worx on win8 64bit too.
http://forum.xda-developers.com/showthread.php?t=1927769
Click to expand...
Click to collapse
Thanks, but I have tried that version, and the one newer (1.5.23). I did manage, efter some reinstalls, to get 1.5.18 (I think is was) to work on the real installation. So maybe my issue is with virtualbox, I just can't see what. I have disabled everything in linux that could block something, I have disabled firewall and such on the virtual windows, I have tried checking and changing perms on the linux device nodes, and tried running VB as root.
At least I got the Galaxy Y running again, but I don't like having unresolved issues so VB is going down
I am new on XDA, and I am not sure what is the most appropriate place for my question, so I am asking it here.
I tried to install Samsung drivers on a 64 bit Windows 7 SP1 box, but it always BSODs at the end of the procedure. After this happens, Windows 7 starts to fail, and I have to go back to a restore point, so I don't even know if something got installed. I tried a few different versions of the drivers, but always got the same problem. I tried with a couple of different downloads, one is a file named Samsung-Usb-Driver-v1.5.49.0.exe, and another is a zip archive called usb_drivers_GalaxyS_x64.zip, which I think had been extracted from Samsung Kies installation.
From Windows Properties, I can see an entry SAMSUNG_Android marked with an error, saying that the device drivers were not installed (code 28). There are similar entries for "CDC serial" and "Video controller".
I did a lot of googling, but didn't find anybody who had exactly the same problem.
I am not sure whether this is related to the 64 bit OS, or if there is a more specific version of the drivers I should use, and the Samsung site is not of much help. Any idea will be appreciated.
Hi
Thanks for writing to us at XDA Assist. Even though this seems more like a Windows issue than an Android issue I'm going to have your thread moved to the S3 Neo q&a section here:
Galaxy S3 Neo Q&A, Help & Troubleshooting
Hopefully someone with the same device as you can help you out with exactly which drivers you should be using for your phone. Please standby while we move your thread.
Good luck!
This is really weird. I tried to solve my problem by installing Samsung Kies. Installation goes fine, Kies starts, but when I attach the phone to USB Windows crashes with a BSOD. Unless I disable USB debugging, in which case nothing happens. Needless to say, "adb devices" lists nothing.
Ok, I finally managed to connect my device and run application on it from Android Studio, which was my main concern.
To do so, I installed the latest version of Samsung Kies3. When I connected the phone after the first installation, the PC crashed with a BSOD, and at next start the drivers for my phone were uninstalled. Reinstalling them from Device manager fixed all issues, now I can see the phone both from Kies and from Android Studio.
Maybe somebody will benefit from my experience