Having searched for a long time for a solution in using Odin under Mac OSX environment, I've finally found a solution! A lot of people say can't , but here it is...
1. Load up VirtualBox's Windows session
2. Download the Samsung USB drivers in Windows from the attachment and extract in a folder.
3. Closes the Windows session
4. Go to the USB setting of the Windows session
3. Reboot SGS2 in download mode
4. Plug in the phone to USB
5. Add a new USB filter <SAMSUNG Gadget Serial [021B]>
- Note: There could be a error box showing up, ignore it
6. Unplug USB
7. Load up Windows session again
8. Once loaded, plug in the phone again and wait for new hardware prompt
9. Add the required drivers from the downloaded file
10. Unplug USB
11. Load Odin
After Odin is loaded inside the Windows session and the phone is plugged in, the COM box will turn yellow and you can flash whatever you want!
My setup is like this:
Mac OS: 10.7.2 Lion
Win OS: Win XP SP3 32 bit
VirtualBox: 4.1.6 (with USB extension pack)
For those who are using difference OS versions, please report the results and help others! I'll try to generate a list from the feedback.
Thanks, I've been looking for a way to do this forever.
Working on my setup:
OSX (Host) - 10.7.2
Win (Guest) - XP SP3 32bit
VBox - 4.1.8 (USB extention pack)
Virtualbox Odin crash
I actually managed to work out who to get as far as getting Odin to recognise my phone (after ages of fiddling, i found the usb filters in virtual box).
HOWEVER, when I START odin to flash a rom, it reboots my VM. Anyone got any ideas what might cause this?
FYI:
I am trying to flash a previous rom version onto my Galaxy Note (LA4 back down to KKA [United Kingdom]) so that I can run the one-click CF-Root.
NB:
Running OSX Lion
Virtualbox version 4.1.8
Windows XP with service pack 3
davidgood89 said:
I actually managed to work out who to get as far as getting Odin to recognise my phone (after ages of fiddling, i found the usb filters in virtual box).
HOWEVER, when I START odin to flash a rom, it reboots my VM. Anyone got any ideas what might cause this?
FYI:
I am trying to flash a previous rom version onto my Galaxy Note (LA4 back down to KKA [United Kingdom]) so that I can run the one-click CF-Root.
NB:
Running OSX Lion
Virtualbox version 4.1.8
Windows XP with service pack 3
Click to expand...
Click to collapse
check the "enable usb 2.0 (ehci) controller" into machine configuration. that solves the OS reboot for me.
May have to try this cause it sure isn't working with VMWare
You legend
I have been looking for the samsung device drivers for ages. Working great with virtual box. Good bye boot camp, you were only there for odin these days anyway! Thank you.
Thank you !!!
Thank you very much !!!
Thanks!
dj_ghosie = gentleman + scholar
wow. awesome find here.
this worked for me as well. however, I used the drivers and odin and recovery files found here in the 2nd post:
http://forum.xda-developers.com/showthread.php?t=1275031
(drivers http://devphone.org/files/gtab7/Sprint_P100_Samsung_GALAXY_Tab_USB_Drivers.msi)
OSX 10.8.2
WindowsXP SP2
VirtualBox 4.2.4
THANK YOU SO MUCH!!!
OKAY, very interested in this.
I have the Galaxy s3. Would I download this..
http://download.virtualbox.org/virtualbox/4.2.6/VirtualBox-4.2.6-82870-OSX.dmg
and then follow the directions listed in OP?
Want to eventually do this...
http://forum.xda-developers.com/showthread.php?t=2046439
Good stuff!!!
Works in my setup:
Mac OS: 10.8.3
Win OS: Win XP SP3 32 bit
VirtualBox: 4.2.10 (with extension pack)
Stuck at last step when I boot into Odin
Hi,
Thanks for the awesome guide. I'm on a Mac (10.7.5) using VirtualBox with Win7. I installed all the drives and Odin and VirtualBox has no trouble picking up my phone (GS3) when I plug in in BEFORE going to Odin mode.
Then I follow the last set of instructions (unplug USB, boot into Odin, plug phone back in) and then VirtualBox won't find the phone. Any ideas? I've Googled all over the place and haven't found anyone with this exact issue yet.
Wrong forum. Post in S3 Q&A/similar.
Experience with os Mavericks and windows xp virtualized in vmware
dj_ghosie said:
Having searched for a long time for a solution in using Odin under Mac OSX environment, I've finally found a solution! A lot of people say can't , but here it is...
1. Load up VirtualBox's Windows session
2. Download the Samsung USB drivers in Windows from the attachment and extract in a folder.
3. Closes the Windows session
4. Go to the USB setting of the Windows session
3. Reboot SGS2 in download mode
4. Plug in the phone to USB
5. Add a new USB filter <SAMSUNG Gadget Serial [021B]>
- Note: There could be a error box showing up, ignore it
6. Unplug USB
7. Load up Windows session again
8. Once loaded, plug in the phone again and wait for new hardware prompt
9. Add the required drivers from the downloaded file
10. Unplug USB
11. Load Odin
After Odin is loaded inside the Windows session and the phone is plugged in, the COM box will turn yellow and you can flash whatever you want!
My setup is like this:
Mac OS: 10.7.2 Lion
Win OS: Win XP SP3 32 bit
VirtualBox: 4.1.6 (with USB extension pack)
For those who are using difference OS versions, please report the results and help others! I'll try to generate a list from the feedback.
Click to expand...
Click to collapse
just my experience:
Mac os Mavericks, vmware, windows xp virtualized in vmware, last version of samsung kies installed inside the windows xp virtualized machine. install Odin3 3.10, put your phone in download mode, connect the usb cable and when operating system ask for connection with osx or vmware obviosly choose vmware, Odin3 recognize immediatly the phone and you can update everything you want. I have updated my bootloader e my CMW and after installed the rom "android revolution hd" without any problem
Method still works. macOS Big Sur host, Windows 10 guest.
You need to make sure you have VirtualBox Extension Pack installed, otherwise in VB USB settings you'll only see USB 1.1 controller.
May need to create different filters for connecting your phone in normal mode vs download/adb/whatever.
Also I didn't need any Samsung drivers (for my S10e Exynos). Everything "just worked".
Related
In order to get ODIN running for rooting I tried installing Kies under Windows. I tried two VMware sessions on my Mac : On both occasions I used the original cable and turned USB debugging OFF (required for Kies). I assigned the USB port to the VMware session of course.
Windows XP SP3 : It did install normally but drivers install of Samsumg MTP device failed
Installing went OK.
Windows 7: Same problem and Kies appeared in a red window.
On the Mac native (OSX 10.7) Kies installed and connected normally, but cannot use it for rooting as ODIN is for Windows only.
Adre these device drivers really required for ODIN ?
i think u need the drivers. forget kies. just download the samsung drivers and install them. u have to put the phone into download mode to install firmware via odin -> VOL_Down+Home+Power
the drivers u will get here (will work for sgs2 too):
64bit Windows (all versions): http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x64.shtml
32bit Windows (all versions): http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml
Yea it doesn't work on Mac. Got 10.7 running here too, but I only flash through my CWM directly now. When I need odin, I just use my mom's laptop.
Hope not too late, here's the link for downloading Odin, Kies, Kies3, Smart Switch, and all needed drivers for Samsung phones: http://www.droidviews.com/android-usb-drivers-samsung-motorola-sony-lg-zte-htc-asus-huawei-acer/ Thank me if this helped
Hi there,
I got a really nasty problem here: when I connect my Sony Xperia T to my home computer, the ADB driver will be installed properly. When I connect the same phone to my work computer, Windows just doesn't want to accept the drivers. The following things are equal:
- USB debugging is always on on the phone
- Both computer are running Windows 7 64bit
- On both computers I am pointing the Windows driver installation at the same folder with drivers downloaded from Sony.
The thing that is different is the device ID that Windows reports in the Details dialogue from Device manager:
On the home PC it is:
USB\VID_0FCE&PID_5182&REV_0228&MI_01
USB\VID_0FCE&PID_5182&MI_01
On the other PC where things go wrong it is:
USB\VID_0FCE&PID_5182&REV_0228
USB\VID_0FCE&PID_5182
So it seems Windows is not recognizing the phone as a composite device (MI is it multiplexing identifier?). I double checked that USB debugging is always on and also rebooted Windows.
What could could be causing this strange problem?
Android version is 4.1.2 (original Sony firmware).
Thanks
Tom
You could search for the adb drivers for your phone on Sony's website, maybe they are available there
Sent from my Nexus 4 running Android 4.2.2
mihahn said:
You could search for the adb drivers for your phone on Sony's website, maybe they are available there
Sent from my Nexus 4 running Android 4.2.2
Click to expand...
Click to collapse
This is exactly what I did! Downloaded the adb driver from Sony's website. Installed them on one computer - works. Transferred exactly this driver package to the second computer with a USB Stick.
On the second computer, Windows does not find a matching driver for the same phone in the same driver package.
The reason apparently is that the phone reports a slightly different USB id when connected to the second computer (missing the MI at the end of the ID, see my original post).
Hello,
my laptop has the operating system GNU/Linux (Debian Testing) and I installed Windows XP Professional on VirtualBox. Virtualized XP recognizes USB devices mounted on the host. After, I installed the drivers for my smartphone Star S7589 and it is recognized by XP.
The problem begins with Flash Tools. When I want to start the process, after giving the button "Download" and I insert the phone without battery, then VirtualBox not recognize it and It doesn't start the installation of the ROM.
How could you recognize the phone connected to USB when it's turned off?
Thanks.
luface2000 said:
Hello,
my laptop has the operating system GNU/Linux (Debian Testing) and I installed Windows XP Professional on VirtualBox. Virtualized XP recognizes USB devices mounted on the host. After, I installed the drivers for my smartphone Star S7589 and it is recognized by XP.
The problem begins with Flash Tools. When I want to start the process, after giving the button "Download" and I insert the phone without battery, then VirtualBox not recognize it and It doesn't start the installation of the ROM.
How could you recognize the phone connected to USB when it's turned off?
Thanks.
Click to expand...
Click to collapse
I had a very similar problem. Ubuntu 13.04, virtualbox and Windows Vista. My tablet could be recognized as a mass storage device but I could never get it into APX mode because it wouldn't recognize it.
I ended up finding flash tools for my tablet for Linux.
I would suggest you see if there are flashing tools that work on Linux instead.
TomTcom said:
I had a very similar problem. Ubuntu 13.04, virtualbox and Windows Vista. My tablet could be recognized as a mass storage device but I could never get it into APX mode because it wouldn't recognize it.
I ended up finding flash tools for my tablet for Linux.
I would suggest you see if there are flashing tools that work on Linux instead.
Click to expand...
Click to collapse
Thank you for your advice.
I will look for Flash Tools for GNU\/Linux.
Hi, frist post here.
I'm from Venezyela, sorry for my english first to all.
My problem is that: I want the ClockRecoveryMod for my Samsung Galaxy 550, but I can with Odin, because my PC (Windows 8.1) dont run the Drivers on the "Downloading Mode", The Kies recognizes the phone and I made the Root with SuperOneClick, but with DonloadMode the PC just say me "Windows dont recognizes" so, Odin dont recognizes it too.
If someone can help me or maybe know another way to install a RecoveryMod to the Phone, I will be grateful
Waiting for your help, bye bye.
Google "Samsung drivers", download them and then right-click the (driver's) installer and go to properties -> compability and select windows 7. Finally, install them.
That should do it.
Sent from my GT-I5500 [CM11]
AdriaMRios,
This is the link to download for drivers.
http://d-h.st/iPk
As you use windows 8.1 then you will have to extract the file you download from the link above and then right click on the .exe file and go to 'properties', in that go to 'compatibility' and in that choose your operating system as "WINDOWS 7" and check the option below 'always run as administrator' and there you go. Double click on .exe file and follow steps. Install drivers. No need to restart the pc also. (if your phone also do not detect after installing these drivers only then restart). These are the most stable and perfect drivers I have found.
If these drivers Don't work...! Then...read below.
Windows 8.1 has a bug in the Microsoft USB stack affecting many devices using Qualcomm chipsets. The bug prevents the OS from being able to enumerate any of these devices in download mode (fastboot, Odin, Sony flashtool - they're all buggy).
You can downgrade your PC to Windows 8.0, flash on another PC, or wait for Microsoft to release the fix. See here:
http://blogs.msdn.com/b/usbcoreblog...ode-43.aspx?CommentPosted=true#commentmessage
Don't spam their comments section. They have the information needed to fix the Galaxy 5 already, so just be patient.
Hello,
after a few days I successfully unrooted & unbricked my LG-D605. I read a lot of articles and asked lot of questions and tried a lot of unsuccessfull ways. Here is my successfull solution.
My PC configuration
HP 650 (2,4 GHZ, 4 GB RAM, 500 GB drive)
OS openSUSE 13.2 64bit - software.opensuse.org
Oracle Virtualbox from oracle official repository - www.virtualbox.org
Downloaded Windows 7 home premium EN 32bit (very important - it was unsuccessfull with xp / 8.1 and czech localization xp / 7 / 8.1) - Windows 7 32-bit Home Premium x86 English on techverse.net
LG-D605 preparation - HARD RESET (form off-state Vol- & Power, when prompted Power, when prompted Power), next off
Needed downloads - tested
LG mobile drivers - attachment
LG Flash tool - attachment
ROM in .bin and LGUP_L9II.dll (extracted from kdz file) - file in google drive
Install process
Unpack and install LG mobile drivers
Unpack and install LG Flash Tool without run it
Overwrite file c:\\lg\lgfllashtool\megalock.dll with file megalock.dll in archive lg-flash-tool.zip
Connect phone in download mode (remove battery - connect phone to usb -> hold Vol+ -> insert battery)
After phone detection and installation in PC run Windows Device Manager and set LG device to port COM41
Run LG Flash Tool
Mark checkbox "Manual" and set in Model Config path to LGUP_L9II.dll and *.tot file (archive extracted kdz)
Click on OK
In PortSetting window leave marked only port 1
Click on Right Arrow
If you see in small window Port 1 "Ready", disconnect phone on 5sec and reconnect (if you on virtualbox, remember on reactivation usb port)
Done
hi, other flash metod is turn phone in download mode, and flash the kdz file with KDZ_FW_UPD.exe.
also downgrade or upgrade firmware very easy, open the software, select tipe 3gqtc, mode diag, open te kdz file, conect the phone in download mode and launch software update.
Note: in windows device manager disable lg modem device.
no problem in win xp.
sorry for my english.
I tried this metod but it gets stuck at 54%, jumps to 100 and it gives me a download failed error. What could it be?
Thanks man! It worked for me.
I had a slightly different configuration though...
Host OS: Fedora 21 64bit
Oracle VirtualBox 5.0
Guest OS: Windows 7 Professional EN 64bit with corresponding VirtualBox Additions installed
Installation of LG drivers and Flash Tool went well. But after connecting phone in Download Mode it took long time time install drivers which ultimately ended with fail - "drivers were not successfully installed" in yellow bubble. But the phone was shown in device manager so I continued.
Another thing is that I do not have enabled reactivation on usb port so I quickly pluged it in manually after phone rebooted. It worked too.
Only bad thing is that now I have Android 4.1 and have to upgrade back to 4.4. But this is much better situation than bricked phone so thanks again.
When I click right arrow, nothing is happening