Related
Hi,
I had earlier opened a thread regarding this issue. But that was having more than one query and was misleading.
I need to install Froyo JP6 (the official one - no custom ROMs). Currently I'm having JF3.
Kies is not working for me (The MTP application in the mobile opens up, but gets restarted while getting connected to kies, so kies is not recognizing my mobile).
How shall I install JP6 without Kies?
Is it possible to install from mobile itself? (like installing apk file?)
nandihno had told me to install using odin. But i couldn't find it in dev section. Can anybody provide me the link for odin foryo JP6?
Thanks in advance!
Install latest version of Kies - 1.5.3.10093_82.
You can go in setting and Upgrage..
Once the latest version is installed, go into Program Files - Samsung
Delete USD Drivers directory here.
Now go in Program Files - Samsung - Kies - USB Driver
Install the drivers from here.
Once the installation is complete, go to settings in SGS (Galaxy) and unmount Internal SD card.
Connect SGS using USB Key and wait till system detects your SGS.
Once it is done you can use Kies to upgrade to Froyo... However as of today Froyo is not out for India... though there are work around to fool Kies and still download, though I will suggest to wait...
thanks I will try this as well. Well this also work with my issue? I tried to upgrade my firmware using kies, but it failed because of some file missing. I installed kites again, and now it detects my phone when I connect it, but it never seems to make the connection
It just says that it is trying to connect and this goes on forever.
So now I cannot repair my firmware using kies. Can this solution help with that as well?
Shurdus said:
thanks I will try this as well. Well this also work with my issue? I tried to upgrade my firmware using kies, but it failed because of some file missing. I installed kites again, and now it detects my phone when I connect it, but it never seems to make the connection
It just says that it is trying to connect and this goes on forever.
So now I cannot repair my firmware using kies. Can this solution help with that as well?
Click to expand...
Click to collapse
Same problem here. It detects my phone. But freezes in "connecting your device".
@shurdus - when this is happening (connecting ur device), did you notice your phone restarting the MTP application.
I mean, the MTP application will be displaying "installing kies" but after some time, it disappears and appears again in a fraction of a second..
I have to try the solution said by satyawali.
Another doubt - unmounting internal SD card will affect the data?
emmarbee said:
@shurdus - when this is happening (connecting ur device), did you notice your phone restarting the MTP application.
I mean, the MTP application will be displaying "installing kies" but after some time, it disappears and appears again in a fraction of a second..
Click to expand...
Click to collapse
I have a similar problem. I just downloaded the newest version of Kies, but can't get Windows/Kies to recognize my phone. I unchecked "Automatically start monitoring for device..." and "Start Kies automatically..." in the Settings box, and I did the Driver Recovery and rebooted, all recommended in another thread. Still nothing. All I get is some very quick flashing of MTP Application and my home screen opening and closing. Then Windows (Win 7, 32 bit) tells me it couldn't do something and to contact the device manufacturer.
Have you found a solution?
Sent from my GT-I9000 using XDA App
SlowRain said:
I have a similar problem. I just downloaded the newest version of Kies, but can't get Windows/Kies to recognize my phone. I unchecked "Automatically start monitoring for device..." and "Start Kies automatically..." in the Settings box, and I did the Driver Recovery and rebooted, all recommended in another thread. Still nothing. All I get is some very quick flashing of MTP Application and my home screen opening and closing. Then Windows (Win 7, 32 bit) tells me it couldn't do something and to contact the device manufacturer.
Have you found a solution?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I haven't found the solution yet.
I guess the only solution is to format the SD card and then try. But I'm not willing to do that So no froyo for me... If only there was an OTA or froyo installer it'd be great
1. Uninstall KIES
2. Uninstall "SAMSUNG USB Driver For Mobile Phones".
3. Reboot your PC
4. Brows to "Program Files" (windows 32bit) or "Program Files (x86)"(windows 64bit) and remove the folder "Samsung".
5. Run "regedit" from Command Prompt and look in HKEY_CURRENT_USER\Software and delete the "Samsung" folder.
6. Right click your C-drive and choose "Properties", click "Disk Cleanup" and check "Temporary Files" and hit "OK".
7. Install KIES and reboot your PC.
8. When booted, don't start KIES yet, just connect the phone and let windows install the drivers for it, unplug the device when done, start KIES and connect the phone.
That should work out for you..
^ thanks. gonna try it now. Will let u know
@[Ramad] - even this didn't work.
The problem is in the phone - i can clearly see it. I guess, a factory reset will do it. Is there any backup software that can backup including the application data/caches ?
isn't there a download link for the new and original Froyo? there are too many pages and it's quite hard to find what you want (I've found Froyo but not the original one, I think, and I've found plenty of advices for kies but I don't want to do all that unistall-delete traces-install again, when there's a simpler way with odin)
Kies problem is related to the ammound of MP3's on your SGS!
Because MTP is a MP3 player connection protocol it's using some MTP Windows media player driver to connect. If you have all MP3 on an external SD card, just remove it and Kies will work fine. Otherwise remove or rename your MP3s to make it work.
Seriously this worked for me, credits to a user of some forum (can't find the post).
Force close all d launchers before connecting d phone to kies its very necessary step hope it will work
It's unbelievable... the best Android phone has the crappiest PC companion. Seems everyone has exactly the same problem with kies.
As far as I've read it's related to files with longer names stored inside the internal memory. Come on! The old Palm Hotsync didn't suffer from such stupid things!
I think we should start a global petition for Samsung to fix that. My wife has a 10 bucks nokia that has a far leaner/better/functional PC companion.
@nagash1979 - by saying remove it - u mean "all mp3/flac and media" in the external card?
@ srajoria - did that. In fact. uninstalled laucnher pro and then tried. no use.
@c3p9 - i don't think its a deal breaker for this phone. As there are alternatives for kies (like es file explorer for wireless transmission of files). But if only there was an OTA update, then no need of kies at all
@nagash1979 - i couldn't find any windows media player application running in the background. thanks anyway....
Finally I got the solution for the KIES problem.
I had recently downloaded winamp beta from android market. And when connected the phone in usb storage mode when winamp was open in PC and phone, my phone was detected as mass storage. And when I opened Kies, it also detected my phone (finally!), but asked me to connect to kies mode. I removed the cable and connected again in kies mode. And it worked like a charm! WOW!
But it's not working everytime!
Edit: The Mass Storage worked 4/10 times. Kies worked only once out of 10 tries. Everytime a alert message to turn off the SD card is popping up which is very irritating. Dunno how to fix that....
Atleast I was able to connect my phone with the PC using USB Mass Storage mode after a very long time - took the backup of all camera files
If you have latest version of Kies installed and drivers working and experiancing MTP crashing issue on phone then it is long file name issue.
To solve this, connect your phone in media mode and mount the card on system. Use attached utility and search long file names on phone and delete them.
Now connect Kies you should not get MTP issues.....
However this does mean this crappy software (Kies) will still detect your phone...
Try to use Antroid Manager will be satiafied. I have uaed it works fine over Wifi.
Sent from my GT-I9000 using XDA App
Hey guys,
I'm trying to update my gf's Galaxy S to JP6 via the latest Kies 2. The program connects initially and notifies about a firmware update.. accepting this brings up some T&C nonsense, choosing 'accept' brings up a box asking what to backup, at this point whether I backup or skip it will bring up an error about failed update, i9000 disconnected etc...
I've uninstalled & reinstalled Kies, no difference, can anyone suggest what the issue is and how to fix it?
It's UK O2 Branded, currently running JP5 (which was updated by an older version of Kies v1.5 that worked on Win XP). The PC in question this time is running Windows 7 64bit. I rooted the phone using SuperOneClick and had installed RyanZA's OCLF v2 from the market.. i've undone the OCLF now though.
Kies and Win 7 x 64 i have never got it working . But have on Win 7 x32 .
jje
viva.fidel said:
Hey guys,
I'm trying to update my gf's Galaxy S to JP6 via the latest Kies 2. The program connects initially and notifies about a firmware update.. accepting this brings up some T&C nonsense, choosing 'accept' brings up a box asking what to backup, at this point whether I backup or skip it will bring up an error about failed update, i9000 disconnected etc...
I've uninstalled & reinstalled Kies, no difference, can anyone suggest what the issue is and how to fix it?
It's UK O2 Branded, currently running JP5 (which was updated by an older version of Kies v1.5 that worked on Win XP). The PC in question this time is running Windows 7 64bit. I rooted the phone using SuperOneClick and had installed RyanZA's OCLF v2 from the market.. i've undone the OCLF now though.
Click to expand...
Click to collapse
Try to run Kies as "administrator" with "windows xp compatibility mode".
viva.fidel said:
Hey guys,
I'm trying to update my gf's Galaxy S to JP6 via the latest Kies 2. The program connects initially and notifies about a firmware update.. accepting this brings up some T&C nonsense, choosing 'accept' brings up a box asking what to backup, at this point whether I backup or skip it will bring up an error about failed update, i9000 disconnected etc...
I've uninstalled & reinstalled Kies, no difference, can anyone suggest what the issue is and how to fix it?
It's UK O2 Branded, currently running JP5 (which was updated by an older version of Kies v1.5 that worked on Win XP). The PC in question this time is running Windows 7 64bit. I rooted the phone using SuperOneClick and had installed RyanZA's OCLF v2 from the market.. i've undone the OCLF now though.
Click to expand...
Click to collapse
Could you fix it?
End to the Noob Bashing...
Just realised that i was looking at the wrong post when i posted this data so the reasons for posting bit at the top of this will make no sense....sentiment still true though. Hope it helps either way.
Ok, i'm a Techie. I know without a shaddow of a doubt that my Laptop is fine in every respect and yet it was doing this to me also.
Believe me when i say, you're not insane, and despite what others say you DO have a valid question which DOES deserves a valid answer...ENOUGH of the trollish Noob bashing 'non answers'.
If you are having the EXACT same issue as the original poster, heres what you do:
With your phone unplugged....
Update Kies:
Make sure you have updated Kies to the most recent version. Either do this by going to your mobile phone opperators website and downloading the updated software version directly or by using the help --> Check for Updates option. Latest version at time of writing is: 2.0.2.11071_128.
Once up-to-date, close Kies. Although probably not essential, use 'Task Manager' to end any Kies related processes.
Uninstall Samsung USB Driver Software:
1) Navigate to Control Panel and open either (Windows 7/Vista) 'Programs and Features' or (Windows XP/2000) 'Add Remove Programs'
2) Scroll through the list of programs to find one called 'SAMSUNG USB Driver for Mobile Phones'. If it is installed, right click it and select 'Uninstall'
3) Run through the process of uninstalling the software.
Tidy up Devices:
1) Right Click 'My Computer' select properties
2) On windows 7 (possibly Vista also...dont know as I skipped that generation) ONLY, select the 'Advance System Settings' option over to the left of the window.
3) Select the 'Advance' tab in the 'System Properties' window that appears.
4) Click 'Environmental variables'
5) In the 'System Variables' section of the window that appears, click 'New...'
6) In 'Variable Name:' type 'DEVMGR_SHOW_NONPRESENT_DEVICES' without the quotes
7) In 'Variable Value:' type '1' without the quotes
8) Click 'OK' times 3 to exit the windows you opened
9) If Windows 7 (or Vista) close the 'View basic information about your computer' window also.
10) Open 'Control Panel' and navigate through to 'Device Manager'
11) Click the 'View' menu and select 'Show Hidden Devices'. This will display all mothballed devices i.e. those devices which have previously been plugged in but then removed. Windows stores a record of the drivers in the background of the system to speed up the process of installing the device drivers when you next plug in said device. Sometimes, in the case of Network Cards for example, not only will it store the drivers but it will also store its settings. This can cause a problem as if you were to plug in a replacement Network Card and set it to use the same static IP address, the mothballed device will clash with the current device. Without the environmental variable setting being configured as above, even when you show hidden devices, mothballed devices remain hidden.
12) Starting from the top, expand each of the branches in the tree to see the devices within them.
13) Look for anything with a 'Samsung', 'MTP', 'GT-I9000' prefix. If found, right click and select 'Uninstall' and confirm at the prompt. BE CAREFUL NOT TO UNINSTALL ANYTHING YOU ARE UNSURE ABOUT. Google it if need be to figgure out what it is and if its not a Samsung or android related device then leave it well alone.
14) Close Device Manager once you have assessed the final branch.
Re-Install Samsung USB Driver Software:
1) Open Kies
2) Expand the 'Tools' menu and select the 'Install Driver' option.
3) Click ok to any prompts to fire off the process.
4) Wait for it to complete.
5) On completion click 'Ok' to acknowledge if required.
At this stage, it may be worth turning off your Windows Firewall and AV scanners just to be on the safe side. Probably not an essential step but may make a difference. If you're not confident enough with computers to do this then dont bother.
Re-Connect Samsung Galaxy Device:
1) Plug the Micro USB cable that came with your device in to ANY of your most trust worthy USB sockets.
2) Plug the other end into the Micro USB socket of your Samsung Galaxy S.
3) Allow Kies to pickup your device and display the storage information proving it is properly connected.
4) If an update is avaialble for your device, Kies should prompt you. If you are confident that you have all the data backed up onto your computer, then proceed with the Firmware update.
5) Click either the Backup or Skip Backup option.
6) Panic a little when the device appears to disconnect YET AGAIN!
7) Chuckle to yourself knowingly once it blasts through this onto the update.
8) Once completed unplug from and re-plug your Samsung into your computer again.
9) Upload your backed up data.
10) Get rid of the God-Awful default dasktop layout that your Mobile provider forces onto you.
SORTED!
Dont know what causes this but what i have noticed is that once you have tidied the mothballed system devices related to your phone and re-installed the device drivers again, it appears as if there isn't any devices named with the prefix of 'MTP' in the device list but there are a few more labelled with a 'Samsung' prefix.
I suspect this is something to do with Samsung at long last fully qualifying their own drivers but not bothering to tidy up the mess that the old devices left behind as part of the Kies update process. Either that or Windows prevents the Samsung USB Driver installer software from being able to delete/update existing Samsung devices.
Enjoy!
I wish I could say this worked for me... but alas, it has not...
This is from a post I entered earlier today... (no change from this either)
ghosty_uk said:
... steps that worked for me
1, downloaded MyBackup (free version)
2, did backup of both apps and data (put both on ext memorycard)
3, used the restore to factory option under privacy in the settings menu
4, unmounted internal sd card and formated it (to remove the mtp loop issue)
5, run kies,
6, select update firmware,
7, at the box where it says no device connected, put into test mode (ctrl + alt + U + P)
8, connected phone
9, detected thaqt there was an update to JM1 available
10, started update,
Click to expand...
Click to collapse
I have yet to do any of this (other than get a backup using MyBackup), but have some questions... (noob here)
Step 3: Will this remove all the definitions for my phone number and/or provider as well?
Step 7: the CTRL+ALT+U+P thing doesn't work with Kies 2.0.2 so if I am unable to do an update, will the phone be at Froyo (2.2) as it is now? or does it revert to 2.1 (which it was when I bought the unit)?
I also got this "Informational" record from the Event Manager... (I could hear the system connect, then drop the Kies connection)
Fault bucket 17725111, type 5
Event Name: PnPGenericDriverFound
Response: Not available
Cab Id: 0
Problem signature:
P1: x64
P2: USB\MS_COMP_MTP
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
These files may be available here:
D:\Dad\AppData\Local\Microsoft\Windows\WER\ReportArchive\NonCritical_x64_d1b8bb6482961a133bbee52e8072f0433f363959_21d02bae
Analysis symbol:
Rechecking for solution: 0
Report Id: 5ebfff60-c94e-11e0-948f-005056c00008
Report Status: 0
Well had to go through Samsung Support... they got me to reset to factory default (since I had a backup) then do the Kies update...
All is better although it would be nice to know what had gone wrong...
Hello folks,
I'm facing this "please insert a disk" issue when connecting my Note to computer via USB Debugging mode / Mass Storage Mode.
I'll let screenshots in the attachment explain itself. #1 shows the screenshot of devices menu when the phone is plugged into the computer in DEBUG mode; #2 shows the screen after I've clicked "connect USB storage" from the drop-down list of the phone; #3 shows what happens when I try to open one of the two "removable disks".
MTP mode works fine, as well as Kies connection. As I finally started exploring the potential of Android platform, I realized that MTP and Kies connection are the most useless connection options for me, and I'd rather leave it in debug mode all day. So has anybody experienced this issue, or had any suggestion on the solution?
As always, many thanks in advance, and many thanks button clicks afterward!
p.s.,
Desktop OS: Win7 Pro X64 SP1
Note: 2.3.6 Stock LB1 Open Germany Firmware, CF rooted LB1 kernel.
Also, I should have all the latest official device driver from Samsung, as I have the latest version of Kies installed (and I discovered a driver folder under Kies' installed location). I'm not so sure about adb driver, but I was able to find the Note to be listed under devices by typing "adb devices". So.. I don't know where could've gone wrong.
Help anyone?
This really sounds weird... I was facing problems of the Galaxy Note not being detected on several Windows7 32/64-Bit SP1 computers as well but this was gone after I installed SAMSUNG_USB_Driver_for_Mobile_Phones.
You are right - from all that i know all required drivers should be available when KIES is installed on your system. Whatis even more strange is that your device seems to be detected as two partitions are available and are displayed in Explorer...
So I would test the following:
- check if your device manager lists any unknown devices
- Uninstall KIES and try to find the SAMSUNG_USB_Driver_for_Mobile_Phones and install those
- check all available USB ports and see if this solves the problem
- try another USB cable
- make sure your (external) SD card is formatted with a Windows compatible file-system e.g. FAT32
Hope this is helpful and helps solving your problem.
Thanks for your reply!
My device manager basically listed all the drivers/devices associated with the phone:
My Device manager shows devices:
Samsung Android Composite ADB interface
Android UMS Composite USB device (x2)
SAMSUNG Android USB Modem
USB Mass Storage Device
USB Mass Storage Device (Android)
I've attached the screenshot when all the drivers being installed when the phone is firstly connected to the computer. Also in the device manager, everything shows "this device is working properly"
I then decided to test with another Note of my friend's (On the same computer). Her Note has no SD card in it, and is completely stock ROM non-rooted LA4 Open Germany firmware. The same thing happened.
One thing worth mentioning: Yesterday, this worked only for once. When I initially encountered this issue, I restarted my computer, and boom, my phone was connected in Debugging mode! However, once disconnected, and I tried to connect it to the computer again, this issue came back. And afterward, no matter how I restart my computer, the phone won't get connected.
I also tried all USB port (USB 2.0 and 3.0), three different cables (2 of them are Samsung OEMs) and failed to address the issue.
I'm nearly exhausted but I will never give up, as this is my only computer and my only phone (haha), and without solving this issue, I'm never gonna be able to view the phone as a USB storage and easily transfer the file from my computer to the phone.
I'm going to try the last thing that I haven't done from the list you posted:
- Uninstall KIES and try to find the SAMSUNG_USB_Driver_for_Mobile_Phones and install those
I believe that I can keep the driver folder in the Kies' folder, as I believe those are the newest Samsung driver, given that the Kies was the latest release version.
So far, I can only conclude that this issue is not related to specific phone but the Windows 7.
And thank you for your help btotaku!
If anyone has any insight into this issue, please help me. Thumbs up for you!
BTW, I was able to extract both SAMSUNG_USB_Driver_for_Mobile_Phones.exe from under Kies' installation path under Program Files x86 folder, and an uncompressed folder of all kinds of drivers for Samsung device, called "USB Drivers".
And looks like I was wrong. The newest version of SAMSUNG_USB_Driver_for_Mobile_Phones I had was 1.4.8. While the driver that came with the newest Kies was 1.4.103
I'll post back soon
Reinstal Windows on your PC bro.
Problem fixed.
is that your internal memory or the sd card?
Same thing happens either with SD card in the phone or not
avetny said:
Reinstal Windows on your PC bro.
Problem fixed.
Click to expand...
Click to collapse
That's the last thing I would do
Hi guys!
I have a problem with the application QPST, Start the 'Software Download' application but get the following error: could not connected to the pc QPST server.
The application runs but does not detect my phone
The phone displays a message: can not find software on your PC to recognize your device. You must install Service Pack 3, Windows Media Player version 10 or higher for Windows XP. You can download and install Samsung Kies to synchronize data with your device.
My PC is Windows 7, I have installed the drivers and Samsung Kies.
PS: Excuse for my Inglés but I'm using the Google Translator.
thanks
b3tico said:
Hi guys!
I have a problem with the application QPST, Start the 'Software Download' application but get the following error: could not connected to the pc QPST server.
The application runs but does not detect my phone
The phone displays a message: can not find software on your PC to recognize your device. You must install Service Pack 3, Windows Media Player version 10 or higher for Windows XP. You can download and install Samsung Kies to synchronize data with your device.
My PC is Windows 7, I have installed the drivers and Samsung Kies.
PS: Excuse for my Inglés but I'm using the Google Translator.
thanks
Click to expand...
Click to collapse
Hi,
I had same problem when lounching app from explorer, look for icon of running server in your try and then right click ... software download..
It worked for me. Of course, you need to run config before and it should find your phone.
Hope this helps you and maybe some others.
BR
N
b3tico said:
Hi guys!
I have a problem with the application QPST, Start the 'Software Download' application but get the following error: could not connected to the pc QPST server.
The application runs but does not detect my phone
The phone displays a message: can not find software on your PC to recognize your device. You must install Service Pack 3, Windows Media Player version 10 or higher for Windows XP. You can download and install Samsung Kies to synchronize data with your device.
My PC is Windows 7, I have installed the drivers and Samsung Kies.
PS: Excuse for my Inglés but I'm using the Google Translator.
thanks
Click to expand...
Click to collapse
Try to reinstall Kies or Samsung USB Driver? Or run QPST as administrator? Did you switch your phone into "RNDIS+DM+MODEM" mode?
Hope I can help you. But I am only a newbie here
This How-To is best viewed in a web browser as many of the forum readers strip out the formatting.
The obligatory warning:
"I take no responsibility for what happens to your device if you follow this guide. Flashing with Odin carries risk no matter the platform/OS used. This procedure has worked multiple times with 100% success in the test environment detailed below. It should work for any device, but I can't confirm, so feedback please if it works for your device."
- 3DSammy
Test Environment:
This method has been successfully used to flash stock Samsung firmware to a Samsung Tab S 10.5 (SM-T800) tablet. The SM-T800 Knox counter was "0 0x0000" before the Odin flash and remained as "0 0x0000" after the Virtualbox Odin flash of the Samsung stock 4.4.2 firmware and subsequently a Samsung stock 5.0.2 bootloader.
Distro: Ubuntu 14.04
Virtualbox: v4.3.10_Ubuntu r93012 along with extension pack (scroll down)
Windows Virtual machines: XP with all updates applied and Win7 with all updates applied except IE 11 cumulative update
Odin: v3.10
ADB, Fastboot and drivers: 15 second ABD Driver install (maybe the best solution for MS-XP)
KIES3: Samsung KIES3 and download link
Samsung stock 4.4.2 firmware *(XAC - Canadian): T800XXU1ANF8_T800XAC1ANF5_HOME.tar.md5
Samsung stock 5.0.2 bootloader
Tablet model: SM-T800NTSAXAC (Tab S 10.5)
*Samsung device firmware
Configuring a MS-Windows Virtualbox VM to use with KIES3 and ODIN:
1) Install/Upgrade to the latest Virtualbox for your Linux Distro and make sure you have a matching extension pack
2) Install a Microsoft XP or higher OS from an ISO image or your DVD player via Virtualbox. ISO's can be downloaded but unless you have a valid license key it can only be used for 30 days, which may be all you need.
Note: make sure to configure the memory and disk space to match the minimum requirements for the Windows version, KIES3 and Odin
3) Install the extension pack in the new Windows VM
4) Apply all available Windows Updates in the new VM. This can take a very long time depending on the Windows DVD/ISO you started with.
5) Take a VM snapshot as you do not want to waste the set up time again..
6) For the VM to have access to the PC's USB devices your user account must join the "vboxusers" user group. You need root access
for this step. In a terminal session:
> echo $USER # This will display your user id if you are unsure
> FOOUSER # For example
> sudo usermod -G vboxusers -a FOOUSER # "FOOUSER" should be your user ID as this is only an example
7) Reboot Linux (that is what I did but a log out may work as well)
8) Connect your POWERED ON Samsung Device to the PC
9) Start Virtualbox access the new Window VM's settings and click on USB to get the USB filter list
Check both "Enable USB Controller" and "Enable USB 2.0 (EHCI) Controller"
Press ALT+INS and a pop-up list of all connected USB devices should display.
Select the one starting with "SAMSUNG_Android".
Click OK
Disconnect your Samsung device and power it off
Reboot your Samsung device into Download mode (button combination is specific to your model)
Connect the device to your PC
Open the Virtualbox USB pop-up again
Press ALT+INS and a pop-up list of all connected USB devices should display.
Select the one starting with "SAMSUNG Gadget Serial".
Click OK
Disconnect your Samsung device from the PC and reboot the device (button combination is specific to your model)
NOTES:
I never modified any of the internal USB filter values leaving them exactly like Virtualbox added them to the filter list
The USB filter list should look like the screen shot attached to the bottom of this post
You can ignore any scary warnings on your device when invoking "Download mode" as no device connection or downloads are occurring.
Both USB filters are required as the "SAMSUG_Android" works with KIES3 while "SAMSUNG Gadget Serial" works with Odin.
10) Start the Windows VM and log in
11) ADB, Fastboot and drivers:
At this point you can attempt to let Windows recognize and install the necessary drivers or you can download and install them yourself. See 15 second ADB installer.
NOTES:
Despite installing the drivers manually on Windows 7 the VM recognized and downloaded and installed the drivers a second time when I attached my SM-T800. The driver discovery, download and install took way longer than I expected but eventually completed.
With the XP VM I manually installed the necessary drivers with the 15 second ADB installer script
12) Download and install KIES3 and Odin per their web page instructions. The downloads can be done within the VM. XP may need Internet Explorer upgraded as some web sites no longer support old versions of IE. Upgrading in XP can be a major hassle. Alternately (recommended) download the KIES3 and Odin software outside of the VM and set up a Virtualbox share or use a network share that is attached to the VM. I found that you could not install the executable directly from the share but could after you copied the install file into a Window's directory such as "Downloads".
13) KIES3 validation:
Start the Windows VM and log on
Start KIES3
Connect your booted Samsung device to your computer
After a while (up to a couple minutes) the KIES3 should connect to the device
Check that the device information is accurate (e.g. Internal storage used value)
Attempt a backup but the first time un-check the item for backup up your apps as that can take a very long while for a validation test.
NOTE:
App backups will skip some of the apps, I have no idea why. This is not a fail condition. KIES3 highlights that condition.
Check if the backed up data is accurate, I like to check wallpaper, pictures, music ... etc.
14) Odin validation:
Start the Windows VM and log on
Start Odin (run as administrator)
Power off your device and disconnect from the PC
Reboot your Samsung device into the bootloader and start Download mode (button combination is specific to your model)
Connect your download ready Samsung device to your computer
After a while (up to a couple minutes) the Odin log should show that your device is connected
NOTE: At this point you can use Odin normally.
WARNING: Odin is powerful and can brick your device so read the Odin instructions carefully
As I do not own any Apple products, I could not test this Odin solution on a Mac but maybe someone can see if these instructions can be tailored to Virtualbox on a Mac. Steps 6 and 9 are the only steps unique to KIES3 and Odin use of a VM and are likely similar across both Linux and MAC in regards to Virtualbox's VMs.
Here is an article describing how to use cross-platform JODIN3 as an alternate to Windows and Odin. You may find it a viable alternative to the solution described above..
I hope this helps someone and if you have issues/successes please post in this thread.
Screen shots:
USB filter pop-up settings and required Samsung device (SM-T800) USB filters
Odin after successfully flashing the Samsung 4.4.2 stock firmware to a Tab S 10.5 SM-T800 tablet
Odin after successfully flashing the Samsung 5.0.2 stock bootloader to a Tab S 10.5 SM-T800 tablet
Sent from my SM-T580 using XDA Labs
This is a message for everyone who has been troubled with Odin and VirtualBox. It worked for me that way, but took some time and errors. Finally I found out that the connection in the VM can be established by first opening Odin and then connect the mobile phone in download mode to the VM which requires a click on "devices". Puhhh, took some time, but finally after a week I found that out.