Develop Bugs

Epic 4g Not recognized on Windows 7 64 bit

I'm from the Evo 4G section of xda and just bought an Epic 4G from a friend to play around with. I've rooted and fully customized my Evo 4G and my uncle's Samsung Infuse. So I am not new to the rooting side of these phones. However, I just can't seem to get this to work no matter how hard I try.
Ok so I have done Google searches and sifted through the various "fixes" here on xda....I cannot, no matter what I do, get my epic 4g to be recognized on my Windows 7 64 bit.
I've downloaded and installed about 3 or 4 different USB driver files. I've gone through 2 different cables. I've uninstalled and even updated drivers via Windows. And I've installed and updated Kies. I bought the phone from a friend of mine who had done a full system restore before he gave it to me. So if there were any system issues they should be gone. When I plug in one of the cables the phone shows that the USB cable is connected and I have USB debugging on. But my computer shows "Uknown Device." Does anyone have any suggestions for me please?
I've included screenshots of what my computer shows me. Any help, or reference literature that I may have overlooked, that you guys can provide would be extremely helpful.

There's a few reasons this could be happening. You may want to try different USB ports on your computer or connecting through a USB hub. Also, make sure you're using the official Samsung drivers (you can search for them on XDA).
Otherwise, go to the dialer on the phone and punch in ##8778# and under USB make sure PDA is checked instead of modem. Hope that helps.

I too could never get win7x64 to work but had no problem on other pc running win7x86. I wasted hours trying. Uninstalled everything, removed all references in registry, used usbdevview, device manager, different usb ports, win update, and on and on and on. Gave up since I had other computer and it just worked 1st try. Please pm me if u find the solution. Would still like it to work on 64 bit. My thought is the 64 bit driver, but I hear others are working. :-O
Sent from my SPH-D700 using XDA App

BillyBob3 said:
I too could never get win7x64 to work but had no problem on other pc running win7x86. I wasted hours trying. Uninstalled everything, removed all references in registry, used usbdevview, device manager, different usb ports, win update, and on and on and on. Gave up since I had other computer and it just worked 1st try. Please pm me if u find the solution. Would still like it to work on 64 bit. My thought is the 64 bit driver, but I hear others are working. :-O
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Mine works fine on my 64bit Laptop. I had to update drivers once though since going to GB leak broke it. On my desktop it will only work if connected in the rear USB port.
Sent from my SPH-D700 using XDA App

I've used atleast 3 different computers with 64 bit windows 7, I never did anything special except for download the drivers from samsungs website...

I don't know what it is because I couldn't get the computer to recognize my phone on my uncle's laptop (which runs Vista 32). It kept giving me the same "Unknown Device" message when I went to look at the drivers.

Concordium said:
I don't know what it is because I couldn't get the computer to recognize my phone on my uncle's laptop (which runs Vista 32). It kept giving me the same "Unknown Device" message when I went to look at the drivers.
Click to expand...
Click to collapse
Where it says unknown device double click on that then go to update driver then browse to location of unzipped samsung drivers.
Sent from my SPH-D700 using xda premium

Welcome to the Epic 4g xda section! It just so happens I was looking for Windows 7 64-bit drivers earlier today.
Here's where I found them: http://forum.xda-developers.com/showthread.php?t=798067
Then scroll down to the section "2.3 – ROOTING" and you'll find the listed drivers there.

jdawg101 said:
Welcome to the Epic 4g xda section! It just so happens I was looking for Windows 7 64-bit drivers earlier today.
Here's where I found them: http://forum.xda-developers.com/showthread.php?t=798067
Then scroll down to the section "2.3 – ROOTING" and you'll find the listed drivers there.
Click to expand...
Click to collapse
That post and those drivers are old...
Go here and get the drivers from Samsung:
http://www.samsung.com/us/support/downloads/SPH-D700ZKASPR
AFAIK, that package should install the correct drivers for the OS.
GL
=]

I install 32 and 64 bit drivers for the i9000
Sent from my SPH-D700 using Tapatalk

I have literally the same problem, phone was reconized and connected fine when i was running xp 32 bit, installed windows 7 64 bit and nothing i do will work. Was your problem ever resolved?

All i can say is try extracting the drivers thru 7zip
then extract the files it gives you
then u should see like a folder and then copy and paste the
folder in the c: program files
and then go back to device manager and then actually manaually search for
drivers and that should work cuz it worked for me im using Windows 8

unfortunately that is one of the exact ways I tried to do it, thanks for the input tho. Just incase I over looked something searching for the driver manually, what sub category should my phone be under in device manager? thx

For those having trouble getting the drivers installed in Win7(x64/x86).
A workaround could be to use WUBI (Ubuntu's windows based installer that adds an option to boot to Ubuntu, while allowing it [Ubuntu] to be uninstalled from windows like a "normal" program).
Install WUBI, boot to Ubuntu, problem solved!
If the point of installing the drivers it to get Odin working...
The WUBI workaround would still work, you would just replace Odin with Heimdall (which is 100x better/more stable than Odin anyway).
I realise this is a lot to do for resolving a driver install problem, but... Heimdall pwns Odin anyway.
GL
;]

apugslovesxda said:
unfortunately that is one of the exact ways I tried to do it, thanks for the input tho. Just incase I over looked something searching for the driver manually, what sub category should my phone be under in device manager? thx
Click to expand...
Click to collapse
It will show up under USB.
Sent from my SAMSUNG-SGH-I717 using xda premium

kennyglass123 said:
It will show up under USB.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
and if your in download mode when you hook your phone up
it will show up under modem it wil not show until you connect your phone

Ok I had to do the following inorder for it to work on my windows 7 x64 bit
I download the samsung epic 4g driver samsung_mobile_driver_v1.3.800.0.msi
I then used 7zip to extract the file
I then used the msi file and installed it
I then used 7 zip and extracted the samsung_mobile_driver_v1.3.800.0.msi file to a directory
I then DISABLE ALL INTERNET ACCESS ON THE LAPTOP BY TURNING OFF WIFI AND OR PULLING THE LAN CABLE OUT THE PC.
I then plug the phone into the pc usb slot
let the pc find the drivers
if it does not find them point to the extracted directory you did above and it will be good.
now do ##8778# and place the bottom into pda and if it cant find drivers point it to the extracted directory.
now turn phone off and go into download mode 1 key and power button and let windows find the drivers

jmuru said:
There's a few reasons this could be happening. You may want to try different USB ports on your computer or connecting through a USB hub. Also, make sure you're using the official Samsung drivers (you can search for them on XDA).
Otherwise, go to the dialer on the phone and punch in ##8778# and under USB make sure PDA is checked instead of modem. Hope that helps.
Click to expand...
Click to collapse
Oh... my... god. I spent hours today trying to figure out how to get this phone I picked up to show me its sd card as a drive. Everyone on the internet seemed to be saying it was the lack of the right drivers, though they all disagreed on what the right drivers were. I tried so many different drivers, no luck.
That above, that I quoted: all it took. Why would it possibly be misconfigured out of the box in such a weird, impossible-to-locate way? Jeez.
(Anyway, I know I'm bumping a super old thread with this first post, but I felt compelled not just to thank this person for restoring my sanity, but also to bump up this thread's relevance for future googlers going as crazy as I was going.)

[SOLVED] Phone Not Recognized by Computer

Hello everyone. My E4GT is unable to connect my computer after I install the drivers. I tried reinstalling them, used different usb ports, and different cables to find out that it still wouldn't work. The weird think is when I connect my phone to another computer after installing the drivers, it works. I'm hoping that someone knows of a fix to this.
OS: Windows XP SP3 32-bit
Edit: I solved this problem. What the problem was that I was missing usb.inf in WINDOWS/INF . To get this file, I got it from the other computer. At the time of me doing this, my only goal was to fix my webcam because I was getting an error about a missing .inf file.

cuber268 said:
Hello everyone. My E4GT is unable to connect my computer after I install the drivers. I tried reinstalling them, used different usb ports, and different cables to find out that it still wouldn't work. The weird think is when I connect my phone to another computer after installing the drivers, it works. I'm hoping that someone knows of a fix to this.
OS: Windows XP SP3 32-bit
Click to expand...
Click to collapse
Is your computer a "company" computer? Friend of mine had the same issue due to security settings on the laptop.
Sent from my SPH-D710 using XDA

lambohoos said:
Is your computer a "company" computer? Friend of mine had the same issue due to security settings on the laptop.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
No, it is a home computer.

cuber268 said:
Hello everyone. My E4GT is unable to connect my computer after I install the drivers. I tried reinstalling them, used different usb ports, and different cables to find out that it still wouldn't work. The weird think is when I connect my phone to another computer after installing the drivers, it works. I'm hoping that someone knows of a fix to this.
OS: Windows XP SP3 32-bit
Click to expand...
Click to collapse
Try downloading the kies , sp?, program for your PC, it installs Samsung drivers and may solve the issue
sent from my SGS2 running AOKP, eh...

Venomusdragon said:
Try downloading the kies , sp?, program for your PC, it installs Samsung drivers and may solve the issue
sent from my SGS2 running AOKP, eh...
Click to expand...
Click to collapse
SP3 means Service Pack 3.
Kies did not solve my issue. Thanks for your help so far.

cuber268 said:
Hello everyone. My E4GT is unable to connect my computer after I install the drivers. I tried reinstalling them, used different usb ports, and different cables to find out that it still wouldn't work. The weird think is when I connect my phone to another computer after installing the drivers, it works. I'm hoping that someone knows of a fix to this.
OS: Windows XP SP3 32-bit
Click to expand...
Click to collapse
Looks like you tried different USB cables (hopefully NEW ones), and different ports too. Along with Kies.
Try going into device manager (check show hidden devices too!) and uninstall ANY Samsung drivers or software you have installed. And reboot.
Download and install the latest drivers for the Epic 4GT [ http://org.downloadcenter.samsung.c...342248/Sprint_d710_USB_Driver_v1_3_2360_0.exe ]
Reboot your system. Then try to connect again.
If you have some type of Antivirus/Antispyware application you may also want to try and temporarily disable it too. I've seen this happen before.

leaderbuilder said:
Looks like you tried different USB cables (hopefully NEW ones), and different ports too. Along with Kies.
Try going into device manager (check show hidden devices too!) and uninstall ANY Samsung drivers or software you have installed. And reboot.
Download and install the latest drivers for the Epic 4GT [ http://org.downloadcenter.samsung.c...342248/Sprint_d710_USB_Driver_v1_3_2360_0.exe ]
Reboot your system. Then try to connect again.
If you have some type of Antivirus/Antispyware application you may also want to try and temporarily disable it too. I've seen this happen before.
Click to expand...
Click to collapse
I'm pretty sure it is not my antivirus because the other computer has the exact same antivirus. Also, in Device Manager, I enabled hidden devices and I do not see any drivers that seem like they have to do with Samsung.

Cool, but did you uninstall, reboot and then reinstall? And did you also disable the AV just in case?
Sent from my SPH-D710 using xda premium

I Use usbdeview to remove the devices
Sent from my SPH-D710 using xda app-developers app

leaderbuilder said:
Cool, but did you uninstall, reboot and then reinstall? And did you also disable the AV just in case?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Uninstalling Kies right now. I will post after I reboot my computer.

I rebooted my computer, installed the drivers, and it still did not work. It's like my computer does not know how to use the drivers for my phone.

cuber268 said:
I rebooted my computer, installed the drivers, and it still did not work. It's like my computer does not know how to use the drivers for my phone.
Click to expand...
Click to collapse
Wow not sure what else to try. If you've tried removing all drivers and re-installing them, using brand new USB cable(s), using different USB ports and disabling AV software and if it does connect and show up on other PCs yet it still wont show on one PC, then something is amiss with that machine.
When you're connecting your device you do have it on too right? I'm sure you do but just checking.
Did you install any ROM on this device already? There are some international versions that if installed on this device disable the USB port.
And does it show up on other machines just not this one?
If it shows up on other machines than it there is something amok with that PC.
If it doesn't then..
One last thing you might want to attempt is to download sfhub's One-click FF18 http://forum.xda-developers.com/showthread.php?t=1721229 download the 'reset data' and extract the exe.
Make sure you phone is off and NOT attached to the PC.
Run the One-click application.
Simultaneously Press and Hold [Power] [VolDn] until confirmation screen appears
Press [VolUp] to enter Download mode
Then Attach your phone via USB to the PC and see if it shows up on a COM Port (anyone is OK).
IF it does you can then at least flash the stock rooted FF18 and get the device to probably work correctly next time you plug it in after of course the entire Odin/Update finishes and your phone restarts.
Just reaching here but hope that helps.

leaderbuilder said:
Wow not sure what else to try. If you've tried removing all drivers and re-installing them, using brand new USB cable(s), using different USB ports and disabling AV software and if it does connect and show up on other PCs yet it still wont show on one PC, then something is amiss with that machine.
When you're connecting your device you do have it on too right? I'm sure you do but just checking.
Did you install any ROM on this device already? There are some international versions that if installed on this device disable the USB port.
And does it show up on other machines just not this one?
If it shows up on other machines than it there is something amok with that PC.
If it doesn't then..
One last thing you might want to attempt is to download sfhub's One-click FF18 http://forum.xda-developers.com/showthread.php?t=1721229 download the 'reset data' and extract the exe.
Make sure you phone is off and NOT attached to the PC.
Run the One-click application.
Simultaneously Press and Hold [Power] [VolDn] until confirmation screen appears
Press [VolUp] to enter Download mode
Then Attach your phone via USB to the PC and see if it shows up on a COM Port (anyone is OK).
IF it does you can then at least flash the stock rooted FF18 and get the device to probably work correctly next time you plug it in after of course the entire Odin/Update finishes and your phone restarts.
Just reaching here but hope that helps.
Click to expand...
Click to collapse
This shows up on other computers but not this one. I did install CM9 onto my phone, but when I was on stock, this problem was still happening. This is most likely something with this PC. Thanks for you help.

Well then that's it. PC is the issue it won't show. Something is pooped.
Good luck.

Just to be clear, when someone says, 'try different usb ports' make sure you only use the ports on the motherboard and not the ones on the front of the case or door.
It's the difference between powered and un powered.
That one the threw me for a loop on my win7 when I usually use my laptop with xp.

Problems Windows not recognizing GNex

Let me start by first saying I'm brand new to the forum and have never rooted, unlocked, or flashed anything, so I'm a total novice. Any help is therefore greatly appreciated! I have a VZW Galaxy Nexus, and I've decided to manually install a Jelly Bean Rom, rather than waiting for Verizon's slow ass. I'm trying to use Wug Fresh's Nexus Root Toolkit to do so, but I can't even get started because I can't get Windows to recognize the device when connected via USB. I know there are many other threads about this, but I can't seem to get a straightforward answer for my exact situation. I've installed all the drivers I can find - the official Samsung drivers, the drivers included in the toolkit, and some naked drivers found here on XDA. Nothing seems to work. I've tried it on three different machines - XP, Visa, and W7. The message I get when I try to manually configure/select the drivers is something to the effect that the most current software/driver is already installed, despite the fact Windows says there's no driver and doesn't recognize the device. Oh, and one last thing, I've now tried this on two different GNex's - Verizon just replaced mine for signal loss issues, and the new one has the new build number IMM76Q. I'm at a complete loss and extremely frustrated. Help!!!

mojo1633 said:
Let me start by first saying I'm brand new to the forum and have never rooted, unlocked, or flashed anything, so I'm a total novice. Any help is therefore greatly appreciated! I have a VZW Galaxy Nexus, and I've decided to manually install a Jelly Bean Rom, rather than waiting for Verizon's slow ass. I'm trying to use Wug Fresh's Nexus Root Toolkit to do so, but I can't even get started because I can't get Windows to recognize the device when connected via USB. I know there are many other threads about this, but I can't seem to get a straightforward answer for my exact situation. I've installed all the drivers I can find - the official Samsung drivers, the drivers included in the toolkit, and some naked drivers found here on XDA. Nothing seems to work. I've tried it on three different machines - XP, Visa, and W7. The message I get when I try to manually configure/select the drivers is something to the effect that the most current software/driver is already installed, despite the fact Windows says there's no driver and doesn't recognize the device. Oh, and one last thing, I've now tried this on two different GNex's - Verizon just replaced mine for signal loss issues, and the new one has the new build number IMM76Q. I'm at a complete loss and extremely frustrated. Help!!!
Click to expand...
Click to collapse
Lol just be forewarned, a lot of douchebags may come in here and make fun of you. Ignore them, they don't represent XDA
I'm getting the Galaxy Nexus in a few days (mine's the Sprint one), but I'm going to be using mskip's GNex Toolkit. No worries, he has one for the Galaxy Nexus on Verizon too:
http://forum.xda-developers.com/showthread.php?t=1400871
I would download that and use it to install the drivers. If that doesn't work, mskip has a pretty extensive FAQ and I believe drivers on Windows is answered in the 1st solution in post 3...so follow the link, download THAT toolkit, see if the drivers install properly and if not, go to post 3 and follow the instructions for "fastboot drivers".
Next time, try to use the search bar please. It is a rule around here to do so because it's XDA, which means every question has been asked and answered a million times lol no big deal, just be more weary in the future!
**edit**
first post, huh? Welcome to XDA

The Universal Naked Driver is the one you want, it include the ADB FastBoot drivers required to do flashings (link in my sig). The Samsung driver from Samsung Kies is a different driver so the computer could recognize the phone storage.
Make sure you use the official USB cable or a quality one to get good connection. Uninstall all unncessary Android drivers from other devices and the Nexus too, reboot, connect the Nexus, when it ask for a driver poing it to the Universal Naked Driver folder. If the installation still fail, try a different computer.
Sometimws the Nexus might be attached to the wrong ADB driver, when you connect it, you can go to Device Manager and uninstall the ADB driver, but also selecting the option to delete the driver from the system.

eksasol said:
The Universal Naked Driver is the one you want, it include the ADB FastBoot drivers required to do flashings (link in my sig). The Samsung driver from Samsung Kies is a different driver so the computer could recognize the phone storage.
Make sure you use the official USB cable or a quality one to get good connection. Uninstall all unncessary Android drivers from other devices and the Nexus too, reboot, connect the Nexus, when it ask for a driver poing it to the Universal Naked Driver folder. If the installation still fail, try a different computer.
Sometimws the Nexus might be attached to the wrong ADB driver, when you connect it, you can go to Device Manager and uninstall the ADB driver, but also selecting the option to delete the driver from the system.
Click to expand...
Click to collapse
Thanks both of you for your help so far. I tried installing these naked drivers but no still luck. I don't have any preexisting Android drivers on the computer, but how would I uninstall drivers on the Nexus? The message I get when I try to update the drivers to these is that Windows could not find a better match for the hardware than you currently have installed. I checked the Driver Details and the driver it has listed is C:\WINDOWS\system32\DRIVERS\klfltdev.sys. I've tried numerous times "uninstalling" the driver, rebooting the computer, and starting the process over again but still no luck. I'm unable to actually remove this system file from my computer. I've been trying to do this on a work computer running XP, but I tried the naked drivers on a Vista machine as well, and I still get a similar message about the software already being the best match when I try to point Windows to these drivers (again, no other drivers installed on that machine). I'm so frustrated...

PoorCollegeGuy said:
Lol just be forewarned, a lot of douchebags may come in here and make fun of you. Ignore them, they don't represent XDA
I'm getting the Galaxy Nexus in a few days (mine's the Sprint one), but I'm going to be using mskip's GNex Toolkit. No worries, he has one for the Galaxy Nexus on Verizon too:
http://forum.xda-developers.com/showthread.php?t=1400871
I would download that and use it to install the drivers. If that doesn't work, mskip has a pretty extensive FAQ and I believe drivers on Windows is answered in the 1st solution in post 3...so follow the link, download THAT toolkit, see if the drivers install properly and if not, go to post 3 and follow the instructions for "fastboot drivers".
Next time, try to use the search bar please. It is a rule around here to do so because it's XDA, which means every question has been asked and answered a million times lol no big deal, just be more weary in the future!
**edit**
first post, huh? Welcome to XDA
Click to expand...
Click to collapse
I have done all of this, including following the complete instructions and trying all options at http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
Still nothing seems to work. I am at a complete and total loss, and am entirely discouraged. For the life of me, I can't believe it's so utterly difficult just to properly install device drivers on a developer phone.

Ok I am sure you have done this but thought I would check. USB debugging needs to be enabled so settings developer options then enable usb debugging.

ifly4vamerica said:
Ok I am sure you have done this but thought I would check. USB debugging needs to be enabled so settings developer options then enable usb debugging.
Click to expand...
Click to collapse
Yes, I turned debugging on. Never hurts to check, though. I'd love for the solution to be something so simple that I just overlooked.

http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735

First of all, DO NOT USE TOOLKITS!
I know it is easier for you, since you are new to this rooting stuff, but trust me on this, 2/3 people who said their phone's bricked used toolkit instead of adb and fastboot method
Now with that out of the way, you can check if you got any other drivers installed by going to Control Panel->Hardware and Sound->Device Manager
From there, connect your phone via USB and see driver pop up. If it's something like "Android 1.0", uninstall that, and then install naked driver. If you don't see any driver pop up after connecting, just install naked driver (for me, when I checked USB debugging, Windows automatically installed Samsung ADB driver that works well for me.). If you see something like "Samsung ADB Interface Driver", you should be able to use adb commands and such.
If you don't have fastboot and adb files, make sure you do this step!: After that, you should download adb files, fastboot files (adb and fastboot files can be found from Efrant's attachment from this thread: http://forum.xda-developers.com/showthread.php?t=1626895), and Android SDK (If you already have SDK for some reason, just download adb file and fastboot file ). After downloading Android SDK, put the folder in somewhere easy to find. (C:\ directory should do it). Now, put adb and fastboot files inside the platforms file (that can be found from SDK folder)
Now you got files set, go to the directory where you put adb and fastboot files, shift+right click and then click Open Command Prompt Here
Type "adb devices" and if you see one device from the cmd, you are good to go

FINALLY! I got it to work. I turns out the problem was just the GD USB cord I was using. I had been using the OEM Samsung that came with the device the entire time, so I obviously had no reason to believe the problem was the cord, especially considering the device would still charge when plugged into the computer or the AC outlet. I just happened to purchase a cheapy Chinese charging station that came with a USB cord and that did the trick. I guess I just got a lemon of a cord the first time. I could've been saved so much aggravation, but oh well! I'm no running the latest BAMF Paradigm Jelly Bean ROM, and it's sweet! Thanks to everyone for the help and suggestions!

mojo1633 said:
FINALLY! I got it to work. I turns out the problem was just the GD USB cord I was using. I had been using the OEM Samsung that came with the device the entire time, so I obviously had no reason to believe the problem was the cord, especially considering the device would still charge when plugged into the computer or the AC outlet. I just happened to purchase a cheapy Chinese charging station that came with a USB cord and that did the trick. I guess I just got a lemon of a cord the first time. I could've been saved so much aggravation, but oh well! I'm no running the latest BAMF Paradigm Jelly Bean ROM, and it's sweet! Thanks to everyone for the help and suggestions!
Click to expand...
Click to collapse
lol nice.

mojo1633 said:
FINALLY! I got it to work. I turns out the problem was just the GD USB cord I was using. I had been using the OEM Samsung that came with the device the entire time, so I obviously had no reason to believe the problem was the cord, especially considering the device would still charge when plugged into the computer or the AC outlet. I just happened to purchase a cheapy Chinese charging station that came with a USB cord and that did the trick. I guess I just got a lemon of a cord the first time. I could've been saved so much aggravation, but oh well! I'm no running the latest BAMF Paradigm Jelly Bean ROM, and it's sweet! Thanks to everyone for the help and suggestions!
Click to expand...
Click to collapse
That's great! Make sure you give the guy who helped you Thanks

Windows doesn't "see" note 2.

Good Evening folks,
I'm posting here after spending the better part of 2 days trying to figure out why this doesn't work.
So, i have the following:
model: GT-N7100
Version: 4.1.1
Build: JRo03C - ALJ1
I run a PC with windows 7 and also have a laptop with windows 8.
Now, initially i only wanted to root my device to install an addblocker on it and get rid of some bloatware. so i went and got samsung note2 toolkit here on XDA. (also tried others)
but no matter how i tried the pc (nor laptop) would see the note 2. it would plug in, it would charge... but windows ignored it otherwise.
i have tried al 8 of my USB ports on the desktop, and all 3 on the laptop. none of them work
3 different USB cables.
re-booted more then times then i can count.
i have manually installed the samsung drivers.
i have tried installing the windows MTP Porting kit
all to no avail.
So before i can even START to root... i need it to to play nice with my machines... anyone have ANY suggestions on what the hell is going on here.

If your main priority is to root then use exynos abuse
Sent From Samsung's Galaxy Note II Using Internet

UtkarshGupta said:
If your main priority is to root then use exynos abuse
Click to expand...
Click to collapse
hi,
Thanks for that! found the APK file and got it on the phone through email and it's rooted, so my mission is accomplished...
but my problem still persists:
why oh why wont windows just play nice with the phone?

Did you install Kies on your PC? That program needs to be open when you connect your phone and then it will install the needed drivers.
Sent from my GT-N7100 using xda app-developers app

el_roy1985 said:
Did you install Kies on your PC? That program needs to be open when you connect your phone and then it will install the needed drivers.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Or install the drivers using the Note Toolkit http://forum.xda-developers.com/showthread.php?t=1923956

Does it show as an unknown device in windows under device manager?
I'm having the same issue but I have a suspicion that its the USB port on the phone itself as my gnex can use the same cable/USB port and show up as mtp.
Sent from my GNote 2 using xda premium

my windows is same

My Note 2 N7100 is 'seen' by my windows 8 machine, but it doesnt seem to copy/ paste anything. Pops up with an error. The same happens on a Mac Lion machine. Installed the Android File Transfer app, but the moment I connect my phone, it pops up a message saying please restart your device so that it can be detected. I am tired of transferring individual files over AirDroid Any help?

anirudh412 said:
My Note 2 N7100 is 'seen' by my windows 8 machine, but it doesnt seem to copy/ paste anything. Pops up with an error. The same happens on a Mac Lion machine. Installed the Android File Transfer app, but the moment I connect my phone, it pops up a message saying please restart your device so that it can be detected. I am tired of transferring individual files over AirDroid Any help?
Click to expand...
Click to collapse
What's the error message?

Happened to me before, un install kies on your pc reboot, download from Samsung website and install again, should work
Sent from my GT-N7100 using xda app-developers app

first of all I forgot to mention that this should've been posted in Q&A section
for the problem try the following steps. after each one of them try connecting again. keep net disconnected while you follow the steps.
if it starts working then stop other wise continue.
1)use a diff comp, but you already did that , use a different cable, you didn't mention it
2)try uninstalling drivers via programs and features.
3)try installing drivers - preferably via mskip's toolkit
if you have windows 7, then directly install it
if you have windows 8, then first disable driver signature enforcement via this guide's last question.
4)try re installing windows. if you don't wanna do that then
open device manager
in view -> show hidden devices
delete each one that says samsung, note ii or note 2, android, google, adb, gt-n7100, n7100
this will ensure that you truly remove drivers
follow step 3) after this.
Hope I helped

All the usual and helpful ideas have been listed and you should definitely work thru those to make sure you are not missing something obvious but critical. I also use Win8 (64) and all was well with my Note2 showing up as an MTP device and wll working then one day, seemingly spontaneously, it suddenly didnt! When I would plug my Note2 in, Windows would give me a USB error telling me it could nto recognise the device! To cut a long story short, I tried my wife's S2 and IT appered fine as an MTP device happily enough, so that ruled out the cable, the port and the computer/OS.
I then tried my Note2 on my laptop, and once again it came up as USB error, so the problem was following the DEVICE around....
After a lot of googling, I tried on thing that fixed it instantly:
On the phone, go into Settings, Security and delete all the "Device Administrators" which in my case was just my Email app. That did delete my email account from my phone (contacts, email etc) but didnt matter as phone is just a dumb client to the mail server so no loss of any real data.
Once removed, I then plugged phone in and BOOM! MTP device happily appeared! I then went back in and just re-added my email account and re-activated Device Administrator when asked. Working ever since.
Not saying this is your problem, but it was an eye opener to me that the Device Administrator could 'lock out' the USB connection of the device....
Hope this helps.

APK
Temko Firewing said:
hi,
Thanks for that! found the APK file and got it on the phone through email and it's rooted, so my mission is accomplished...
but my problem still persists:
why oh why wont windows just play nice with the phone?
Click to expand...
Click to collapse
Did the APK file automatically root your note2?

Arikara said:
Did the APK file automatically root your note2?
Click to expand...
Click to collapse
Yup it do
Sent from my GT-N7100 using xda premium

i have problem in xp .it doesnot install driver properly but gud in win 7.first uninstall all drivers then installed drivers without connecting phone.when instal done then connect phone

nabilsweet007 said:
i have problem in xp .it doesnot install driver properly but gud in win 7.first uninstall all drivers then installed drivers without connecting phone.when instal done then connect phone
Click to expand...
Click to collapse
I would also recommend checking your Windows Update log - especially if you have it set to automatic updates. After I installed the drivers off of the Samsung website, Windows Update tried to "Update" my drivers to an older version (I do manual Windows Updates). The first time it asked, I let it, and my phone couldn't connect anymore. Once I stopped that silliness I stopped having problems.

same problem usb not conecting with my pc windows7
all this is my same problem which I facing help me about how to slove this matter
Temko Firewing said:
Good Evening folks,
I'm posting here after spending the better part of 2 days trying to figure out why this doesn't work.
So, i have the following:
model: GT-N7100
Version: 4.1.1
Build: JRo03C - ALJ1
I run a PC with windows 7 and also have a laptop with windows 8.
Now, initially i only wanted to root my device to install an addblocker on it and get rid of some bloatware. so i went and got samsung note2 toolkit here on XDA. (also tried others)
but no matter how i tried the pc (nor laptop) would see the note 2. it would plug in, it would charge... but windows ignored it otherwise.
i have tried al 8 of my USB ports on the desktop, and all 3 on the laptop. none of them work
3 different USB cables.
re-booted more then times then i can count.
i have manually installed the samsung drivers.
i have tried installing the windows MTP Porting kit
all to no avail.
So before i can even START to root... i need it to to play nice with my machines... anyone have ANY suggestions on what the hell is going on here.
Click to expand...
Click to collapse

I was having the same problem, but I was using a USB cord that I had from my old phone. Switched to the white one that came with my Note 2 and it started working.

Does Odin work through Bootcamp or Parallels on a Mac?

Pretty straightforward question. I'm looking at going from a Windows laptop to a macbook and want to make sure some of the programs I use frequently work. Will Odin work via Windows on a Mac? Thanks.

Anyone? Really want to pull the trigger on this MBP, but want to ensure I can still tinker with my android devices...

i just used Odin and it would not work on my MBP with Parallels Win 7. I had to drag out my PC and then Odin worked fine

red321red321 said:
i just used Odin and it would not work on my MBP with Parallels Win 7. I had to drag out my PC and then Odin worked fine
Click to expand...
Click to collapse
How about boot camp? Do you think the issue has to do with drivers? Not familiar with Mac OS yet... My current laptop is the only windows machine I own and don't want to get rid of it in lieu of the MBP in case some of my programs don't work...

Haven't tried boot camp
Sent from my SM-P600 using XDA Premium HD app

Sent via PM, but finally realized why it wasn't posting in the forum (links)
...So posting here since someone else may need/want this at some point:
1) You'll want vmware fusion; there's a trial. You can easily install and uninstall it on a mac if you don't want to pay. Vbox and parallels won't work.
2) You'll need the Samsung USB drivers for phones exe from Samsung's website. You'll probably also want to separately get the Kies binaries (both windows bins).
3) MS offers pre-made VMs in virtualbox format (ova's); these aren't activated and expire in 30 days, but will still sorta work after that (they'll shut down after about 30-60mins after that point). Easy enough to just reimport; not sure how often you plan on using Odin. Kies itself is generally ok on a mac, but nothing else is (aside from like graphics-tab apps, and generic usb file stuff). You'll want to get Win7 vm images. These should work but if not you can google; MS doesn't make a secret of their VMs, they're made for developers to check compatibility between different versions of IE. Get all of these and then decompress, and you'll get an .ova file (links to Win7-IE10 VM archive files removed as I don't have 10 posts yet).
4) In VMware Fusion, you'll want to import the .ova file (.ova's are technically virtualbox images, but vmware will easily convert them to its own format). Once you've imported it go into the VM's settings and allocate 2gb of ram or so to the VM (I wouldn't go much below that; if you have a later mac that shouldn't be a problem; you might be able to get by on 1.5gb though I haven't tried). You'll also want to go into the vmware usb settings and make sure to be prompted when you add a device instead of just attaching it to one or the other or you'll wind up with issues, possibly, later on.
5) Boot the Win7 vm, install VMware tools, reboot, install samsung drivers, and then install Kies if you want Kies as well (Kies may also bridge some driver gaps, I can't remember; I do remember I had a bit of trouble with correct device recognition; I'll keep an eye on this thread and if you have a problem post publicly and I can message you with the proper driver set otherwise this should work afair); the problem, if I recall, was in detecting the specific USB devices/hub, if anything. DO NOT plug in your tablet until all of these drivers have been installed and you have rebooted the VM. You've been warned.
6) Boot the VM, plug the cable into the tablet, and then the other end into the Mac. If you've set up the USB prompting properly (btw make sure you set it to 2.0 not 3.0), you should get a prompt asking if you want to attach it to the Mac or Windows; choose Windows. The drivers should do there thing in a few minutes and eventually recognize the tablet. You may or may not want to reboot the VM one last time at this point before opening Odin, but at this point it should all work.
* A note: you'll probably want to enable a shared folder via VMware with the contents of anything you want to flash and the exes to flash them with; this is pretty straightforward in the VM settings. You'll want to copy/paste from that shared folder to the VM, not run from it; Odin and other stuff tends to hang if you try to run it directly from the share. I just keep everything I need or might want to use in the future on the VM and suspend it til I need it again, but you can just as easily shut it down and it'll retain all of the data, etc; just be mindful of the 30 day limit if you're using one of the precompiled VMs (as I said, they'll still work, but it can get naggy and shut itself down if not in use (or maybe if it is, but I haven't had it bomb out on me mid-flash (yet, knock wood)).
Good luck and enjoy.

not a single problem with parallels windows 8 or xp. while i flash 4.4.2 via odin i surf the web on mac safari.

supremekizzle said:
Pretty straightforward question. I'm looking at going from a Windows laptop to a macbook and want to make sure some of the programs I use frequently work. Will Odin work via Windows on a Mac? Thanks.
Click to expand...
Click to collapse
VMware should do.
It works very well on Linux.

That's interesting...
jpl69 said:
not a single problem with parallels windows 8 or xp. while i flash 4.4.2 via odin i surf the web on mac safari.
Click to expand...
Click to collapse
Mind if I ask what release of OSX and hardware you're on? I know I was having some USB recognition problems with the other two, but that was 2 point releases ago on Mavericks (on 10.9.3 now, haven't tried again). It could be a MBP thing also. I wouldn't mind using Parallels (I have a licensed copy) if it worked for this; as it stands I use parallels for OSX, vbox for *nix and android, and vmware for windows OSes for various reasons.

Macbook Pro 13.3 2012. Mavericks updated, parallels updated with latest version. Windows 8.1 work fine with odin, but i use mainly windows xp. both configure with usb 3.0 driver.
12GB ram, 512GB SSD samsung evo (this is just for show off not relevant to update our tablet) .
i used vmware sideways with parallels but find that parallels it's more faster, reliable and more crash proof.
after you connect the tablet to mac you get the option to connect to mac or virtual machine. afterwards you allways have the option to connect/disconect the usb periferic.

rsd2000 said:
VMware should do. It works very well on Linux.
Click to expand...
Click to collapse
That's what I use; until Ben Dobell can fix Heimdall for Linux for the P60X series I've just been booting into Win7 via VMWare from my Linux machine.

jpl69 said:
Macbook Pro 13.3 2012. Mavericks updated, parallels updated with latest version. Windows 8.1 work fine with odin, but i use mainly windows xp. both configure with usb 3.0 driver.
12GB ram, 512GB SSD samsung evo (this is just for show off not relevant to update our tablet) .
i used vmware sideways with parallels but find that parallels it's more faster, reliable and more crash proof.
after you connect the tablet to mac you get the option to connect to mac or virtual machine. afterwards you allways have the option to connect/disconect the usb periferic.
Click to expand...
Click to collapse
I'm on a late 2013 13.3 MBP. I think back when I was trying to debug the problem I'd read that USB 3.0 and how it's handled on the latest MB might have something to do with it, but I can't recall correctly. I should probably retry just for sh*ts and giggles; was always on the most recent Parallels, VMware, and VirtualBox. That said, I've found VMware in general to be more stable on my particular machine, and quicker to boot/suspend/unsuspend. It could very well just be my imagination or preference though, nosing its way in.
And talking about hardware is never showing off, as long as you're making good use of it. OS wars, however, is another story.