Well, I spent the last week or so having all sorts of creative fun with my new Captivate. Unfortunately, I was having the random shutdown issue, so I decided to remove SRE, SU, etc, using ODIN to restore my phone back to stock and get it exchanged for a new one.
I came home with my new phone today and proceeded to start the customization process all over. Before I did anything serious, I connected my new Captivate to my desktop, to both charge the battery and to sync with outlook using Kies.
With a full battery and my contacts loaded, I moved on the rooting and installing SRE. I then installed a bunch of apps, including ADW, ShopSavvy, and a bunch of games.
I then tried to get on the Market to download a few more apps. I forgot to 'emulate' T-Mobile to get around the AT&T censorship, so I fired up MarketAccess. I got an error message saying that MarketAccess couldn't get SU privs. That made no sense, since the phone was rooted, and SRE installed SuperUser. I downloaded the latest copy of Superuser and installed that. The SU problem was now fixed. (Turns out there was a glitch in the SRE I used. Designgears quickly fixed the zip file, but I was already using the glitchy one.)
Anyway, after loading a slew of apps/games, I plugged the phone back into the desktop to charge the battery some more. I got two error messages, one on the phone, and one on the desktop.
The phone complained that it was not on an 'idle' screen, since ADW was running. Since I had set ADW to be the default launcher, I used TitaniumBackup to temporarily uninstall ADW. (I couldn't figure out how to stop ADW and set TW back to the default.)
The desktop is more or a serious problem. I am now getting an info bubble saying that the USB DEVICE IS NOT RECOGNIZED.
The correct USB drivers are installed. I've used them to ODIN my previous phone back to stock. And they were working fine before I added SRE, ADW, etc.
I've uninstalled and reinstalled the drivers. Didn't help.
I tried USB Debugging, on and off. Didn't help.
I tried the age-old trick of unplugging the desktop and leaving it unplugged for 30 minutes. Didn't help.
So, here are my questions:
1) Does anyone know how to correct the DEVICE NOT RECOGNIZED error?
2) If not, is there anyway for me to restore the phone to stock without USB connectivity?
The phone still functions fine, just no USB. I was able to download the new SRE (with SuperUser fixed) using Dolphin browser. I then used My Files to rename and move the zip file to the root directory, and was able to install it fine. Is this same approach possible to restore to stock?
Thanks in advance...
Uninstall the usb drivers. Not sure what there called when kies installs it
fivebraids said:
Well, I spent the last week or so having all sorts of creative fun with my new Captivate. Unfortunately, I was having the random shutdown issue, so I decided to remove SRE, SU, etc, using ODIN to restore my phone back to stock and get it exchanged for a new one.
I came home with my new phone today and proceeded to start the customization process all over. Before I did anything serious, I connected my new Captivate to my desktop, to both charge the battery and to sync with outlook using Kies.
With a full battery and my contacts loaded, I moved on the rooting and installing SRE. I then installed a bunch of apps, including ADW, ShopSavvy, and a bunch of games.
I then tried to get on the Market to download a few more apps. I forgot to 'emulate' T-Mobile to get around the AT&T censorship, so I fired up MarketAccess. I got an error message saying that MarketAccess couldn't get SU privs. That made no sense, since the phone was rooted, and SRE installed SuperUser. I downloaded the latest copy of Superuser and installed that. The SU problem was now fixed. (Turns out there was a glitch in the SRE I used. Designgears quickly fixed the zip file, but I was already using the glitchy one.)
Anyway, after loading a slew of apps/games, I plugged the phone back into the desktop to charge the battery some more. I got two error messages, one on the phone, and one on the desktop.
The phone complained that it was not on an 'idle' screen, since ADW was running. Since I had set ADW to be the default launcher, I used TitaniumBackup to temporarily uninstall ADW. (I couldn't figure out how to stop ADW and set TW back to the default.)
The desktop is more or a serious problem. I am now getting an info bubble saying that the USB DEVICE IS NOT RECOGNIZED.
The correct USB drivers are installed. I've used them to ODIN my previous phone back to stock. And they were working fine before I added SRE, ADW, etc.
I've uninstalled and reinstalled the drivers. Didn't help.
I tried USB Debugging, on and off. Didn't help.
I tried the age-old trick of unplugging the desktop and leaving it unplugged for 30 minutes. Didn't help.
So, here are my questions:
1) Does anyone know how to correct the DEVICE NOT RECOGNIZED error?
2) If not, is there anyway for me to restore the phone to stock without USB connectivity?
The phone still functions fine, just no USB. I was able to download the new SRE (with SuperUser fixed) using Dolphin browser. I then used My Files to rename and move the zip file to the root directory, and was able to install it fine. Is this same approach possible to restore to stock?
Thanks in advance...
Click to expand...
Click to collapse
I had a similar problem and it turn out that Kies hosed up all my drivers...The only way I got it fix was by totally removing any trace of Kies and then uninstalled all my samsung drivers and usb drivers and then rebooted my pc. Then I reinstalled the samsung drivers and win 7 did the rest...
Well, I haven't uninstalled Kies yet. Although I have uninstalled and reinstalled the drivers from the ODIN thread. No difference.
I even uninstalled the ODIN referred drivers and tried the drivers directly from the Samsung site. Still no difference.
I'll go ahead and try uninstalling Kies and then the ODIN drivers, reinstall the ODIN drivers and see if that helps.
I've also ordered a new cable, since I've read a few threads on other forums where the problem was bad cables. I was going to go to AT&T and get a new cable, but they want $24.99. I just ordered a pair from Amazon at $3.99 each, with free shipping!!
Thanks...off to try ridding myself of Kies...
Well, deleting Kies (and associated drivers) didn't help!
After deleting Kies, I tried both the ODIN referenced drivers, as well as those from the Samsung site. Still not working!
I guess I'll wait on a new cable and see if that helps...
Okay, I think I'm in BIG TROUBLE here!!!
New cables arrived today, but they made no difference at all! Still getting the USB Device Not Recognized message. Doesn't matter if I plug the cable in while the phone is on and select any of the connection options (Kies, Mass Storage, etc.). It gives me the same message when I have Odin running and plug the phone in while holding the volume keys.
To further add to the problem, I tried installing the Odin referenced USB drivers on my wife's laptop which has never seen this phone or Kies. SAME PROBLEM!
I'm thinking there might actually be something wrong with the physical port on the phone. But this highlights my actual problem...
How can I return the phone (for the second time) when this phone has been rooted and is running SRE 1.2.1a ?!?!?
Apparently, there's no way for me to restore this thing to stock without USB.
Any ideas/suggestions?
Relax dude--I just got a captivate a few weeks ago, and have it working on tmobile.
For the drivers, when you plug your phone in, you're getting some errors. I know you uninstalled the drivers, but to double-check, open up device manager and see if there are any ! marks for the phone. Right-click and uninstall the entries. Also, you might try using a different USB port. I can only get my phone to connect using one of the 6 usb ports i've tried. Finally, and I don't know if these are the drivers for Odin, but I downloaded these drivers: SGH-i897_Captivate_USB_Drivers_5_02_0_2
When the phone connects, you might want to go to device manager, find the device(s), righ-click and and select 'update driver'. then, in the driver update window, pick 'manual' or 'let me specify location' and navigate to the unzipped SGH-i897_Captivate_USB_Drivers_5_02_0_2 file. Then, it should work.
Like I said, I have no idea if those are the drivers for odin...but I'm about to find out
I'd like to relax, but I think I'm dealing with a phone with a bad usb port...and since I've rooted, SRE'ed, etc., I won't be able to return it.
Anyway...
The driver you're using is the 'direct from Samsung' version, not the one for Odin.
Regardless, I've been through the exercise you propose...both with the Samsung and Odin drivers. When you attempt to manually install drivers, you need to point the installer to the ".inf" setup information file to use. The Samsung driver has three: SSADADB2.inf, SSADBUS.inf, and SSADMDM2.inf.
I get the following message when trying to use any of these three setup files:
The specified location does not contain information about your hardware.
Oh, and I've tried several different USB ports on the computer...both on my external hub and directly into the back of the machine.
Thanks for the suggestions, but still not working...
I'm really thinking I have a bad port on the phone...especially since trying the connection on my wife's laptop produces the exact same error.
Dam...
Still trying to find a way to restore the phone to stock without a USB connection...
i also have this "DEVICE NOT RECOGNIZED" on my sony x1.
Drivers
I was having trouble using the USB drivers from Samsung the one's you were using SGH-i897_Captivate_USB_Drivers_5_02_0_2. The computer didn't recognize the phone. If you havn't tryed these already give these a try. Well since I am new I can't post the url. Put these words together (forum.xda-developers com archive index.php t-730638)
superdog404 said:
I was having trouble using the USB drivers from Samsung the one's you were using SGH-i897_Captivate_USB_Drivers_5_02_0_2. The computer didn't recognize the phone. If you havn't tryed these already give these a try. Well since I am new I can't post the url. Put these words together (forum.xda-developers com archive index.php t-730638)
Click to expand...
Click to collapse
Not sure different USB drivers would help, but I went to the thread you show and tried to download the 32bit drivers. This is what I get:
{"error": "Invalid access attempt for this token"}
Oh well, thanks anyway.
I'm still thinking that the problem is hardware on the phone. I've tried four different cables, and three different computers. All show same problem of DEVICE NOT RECOGNIZED.
Still trying to figure out how to restore to stock without USB connection for ODIN so I can exchange for a new phone...
What are your USB settings on the device? Do you have debug mode enabled or maybe you've set the device to connect to kies right away which is producing errors on your PC. What versions of windows have you been trying to connect to? This sounds like a windows problem more than anything else.
No modifications, same error
I didn't make any modifications to my new AT&T Captivate, and I too am getting USB Device not recognized under any of the following conditions:
- drivers installed, no Kies
- drivers installed after Kies
- Kies installed after drivers
No response to any USB connection mode (Kies, mass storage, media player, PC INternet).
Only way to exchange files is to physically remove the SD card and plug it into my PC. Windows XP Professional.
By the way, which of the three drivers is the correct one: ssadadb2.inf, ssadbus.inf, or ssadmdm2.inf? Pardon my ignorance as to how this is supposed to work.
mukherji said:
I didn't make any modifications to my new AT&T Captivate, and I too am getting USB Device not recognized under any of the following conditions:
- drivers installed, no Kies
- drivers installed after Kies
- Kies installed after drivers
No response to any USB connection mode (Kies, mass storage, media player, PC INternet).
Only way to exchange files is to physically remove the SD card and plug it into my PC. Windows XP Professional.
By the way, which of the three drivers is the correct one: ssadadb2.inf, ssadbus.inf, or ssadmdm2.inf? Pardon my ignorance as to how this is supposed to work.
Click to expand...
Click to collapse
You should return your phone if it's new if you can't get your computer to recognize it when you have the correct settings and drivers.
Choose, mass storage. I use the drivers from ODIN, I also have to ones from Samsung's site but they are for Windows 7 64bit. Before you plug any Captivate into a PC for the first time you need to first change the settings to USB Mass storage or Kies will attemp to download drivers. Once you get your phone to mass storage windows should find the drivers. I am not sure, I am running Windows 7, I have an old desktop that runs XP, I could plug my phone in and check for you.
FiveBraids
Settings--developement-- check debugging mode, this will allow you to open a command shell. Using SDK and ADB commands.
Download SDK online.
http://developer.android.com/sdk/index.html
Follow the installation instructions. This will allow you to use the command ADB download to get your phone into download mode. Kies screws my drivers so I don't use it.
Rhiannon224 said:
You should return your phone if it's new if you can't get your computer to recognize it when you have the correct settings and drivers.
Choose, mass storage. I use the drivers from ODIN, I also have to ones from Samsung's site but they are for Windows 7 64bit. Before you plug any Captivate into a PC for the first time you need to first change the settings to USB Mass storage or Kies will attemp to download drivers. Once you get your phone to mass storage windows should find the drivers. I am not sure, I am running Windows 7, I have an old desktop that runs XP, I could plug my phone in and check for you.
FiveBraids
Settings--developement-- check debugging mode, this will allow you to open a command shell. Using SDK and ADB commands.
Download SDK online.
http://developer.android.com/sdk/index.html
Follow the installation instructions. This will allow you to use the command ADB download to get your phone into download mode. Kies screws my drivers so I don't use it.
Click to expand...
Click to collapse
The 2 folders I found that have the drivers are /program files/android/, .... and /program files/samsung. Delete these subfolders that have drivers in them.
Download this : http://www.megaupload.com/?d=N4GC49JL and unzip. In the folders inside (i386 and amd) there are uninstallers. Run whichever version is appropriate for you. If you have no drivers or it doesn't say to reboot, the main folder has a setup program. Run that to install the proper drivers. When you plug in to usb, it will now find these drivers.
Also, for me, ONLY the REAR usb ports work properly with this. Top, front, and ext hub ALL give issues.....
JayPhill89 said:
What are your USB settings on the device? Do you have debug mode enabled or maybe you've set the device to connect to kies right away which is producing errors on your PC. What versions of windows have you been trying to connect to? This sounds like a windows problem more than anything else.
Click to expand...
Click to collapse
USB is set to Ask on connection
Debug off or on makes no difference
All tests have been done on XP machines (3 different ones)
I'm all but positive this is hardware...
Thanks for trying to help!
Rhiannon224 said:
<snip>
FiveBraids
Settings--developement-- check debugging mode, this will allow you to open a command shell. Using SDK and ADB commands.
Download SDK online.
http://developer.android.com/sdk/index.html
Follow the installation instructions. This will allow you to use the command ADB download to get your phone into download mode. Kies screws my drivers so I don't use it.
Click to expand...
Click to collapse
I haven't tried ADB, but I'm not understanding how ADB would be able to connect when the connection to the computer is failing at the driver level. I guess I can give it a try tomorrow.
Thanks for trying to help!
What would REALLY help me is for someone to post a backup taken of a completely stock (ODIN'ed) phone using ROM manager. I'm thinking I could load that on the phone and then be able to return it for a new phone!
Any volunteers...please?
techmik67 said:
The 2 folders I found that have the drivers are /program files/android/, .... and /program files/samsung. Delete these subfolders that have drivers in them.
Download this : http://www.megaupload.com/?d=N4GC49JL and unzip. In the folders inside (i386 and amd) there are uninstallers. Run whichever version is appropriate for you. If you have no drivers or it doesn't say to reboot, the main folder has a setup program. Run that to install the proper drivers. When you plug in to usb, it will now find these drivers.
Also, for me, ONLY the REAR usb ports work properly with this. Top, front, and ext hub ALL give issues.....
Click to expand...
Click to collapse
Big thanks!
Just got my first Android device a couple hours ago (went from ATT Bold to Captivate), and could not get the phone to mount to my PC.... followed your instructions here and BAM! Perfect-o! I have now rooted....
OK, not sure where to go next... was thinking about just getting a new ROM flashed since I am totally stock at this point.... the fun begins!!!
jaxf250 said:
Big thanks!
Just got my first Android device a couple hours ago (went from ATT Bold to Captivate), and could not get the phone to mount to my PC.... followed your instructions here and BAM! Perfect-o! I have now rooted....
OK, not sure where to go next... was thinking about just getting a new ROM flashed since I am totally stock at this point.... the fun begins!!!
Click to expand...
Click to collapse
Great!! Glad it all worked for you. My next advice is, before adding anything READ A LOT!!! =) Decide what you want from the descriptions and issues you will see in the threads....
Happy modding!!
I didn't see, I just skimmed through bit did you try to put the phone in download mode and see if windows sees that (different drivers come in to play in download mode and none of the touch wiz stuff is running)? it would test the idea of a bad port.
then you can still always install linux and use adw from there, linux and macs don't need drivers. if that doesn't work, put insurance on the phone if you haven't already then drop it in the sink and get another one.
also I think although I don't know but I think adw may have something to do with it. and incorrectly uninstalling it. first put the phone in download mode then you can work from there on ways to fix that.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Ok, I've given up trying to get this to work. I'm 100% convinced this is a hardware problem with the phone!
I had another thread going, looking for a way to restore this phone (remove SRE, SU, etc.) without usb/ODIN so I could return it to AT&T. I've figured out how to restore it to stock and will be heading to AT&T in the morning.
Thanks to everyone for their patience and assistance!
Sorry guys, I am new here and am having a problem getting ubuntu to work on my NC. I am trying to get it to boot using adb but it will not show up on my PC. I have tried 3 different PCs (2 win7 64bit and 1 vista 32bit), installed the nook drivers but it will never show up in the command prompt. I have tried enabling and disabling development mode and I disabled USB mount. I don't know what else to try. I am on 1.1.0 of the system software if that matters. I got ubuntu to work once using terminal emulator but am having problems getting the script to work. But my main objective is getting adb to see my nook. If you could help, I'd appreciate it. Thanks
I dont follow you very well, what's your problem? Your PC doesn't see NC or something else?
Sent from my HTC Vision using XDA App
ADB does not see it is what I'm saying. I will say that I am not using the stock USB cable that came with the nook as I don't have that cable anymore. Could it be that the cable I'm using doesn't work properly? It see's everything fine when I tell it to mount the SD card. I just using a froyo card in it and adb saw it although it said offline. Could the cable be a reason why it wouldn't work?
It's possible, but not likely as I am using diiferent cable for communication between PC and NC all the time... My original is connected to a charger from the purchase of NC...
did you install the right drivers for it? It depends which OS flavor you have on your nook. Honeycomb uses different drivers vs Froyo
edein said:
did you install the right drivers for it? It depends which OS flavor you have on your nook. Honeycomb uses different drivers vs Froyo
Click to expand...
Click to collapse
I'm having the same issues. I'm on a Windows 7 Box and I can not see the NC.
In Device Drivers under <Other> I find the NC but the driver is invalid. I have DL'ed the Android SDK with the USB drivers and I have tried pointing to the driver manualy. No Joy.
Any Help would be greatly apreciated.
TY
-NJ
have you tried this? http://forum.xda-developers.com/showthread.php?t=882751 ...run the .bat and follow it's instructions.
Also: it's very important that you reboot your Nook at least once after your first OS installation.
Just made the switch from ubuntu 10.10 to windows 7, didnt have issues using my cappy as a mass storage device on ubuntu
On win7 x64 if I try to transfer a file thats just more than a few mb's either from the cappy to the pc or vice versa, the transfer just gets stuck, the loading bar is flashing but it doesnt get anywhere. I have to unplug my phone from the computer in order for it to go away, this causes windows explorer(not the internet browser) to restart as well.
-my other usb devices work without a problem
-have tried all six usb ports on my computer, same thing
-even weirder, i reformatted, installed win7 x86 just to see, transfers work fine on it. Reformatted again and installed x64 with fingers crossed, transfers didnt work on it again.
-I have tried transferring files with no windows updates installed on x64 as well as all updates installed, file transfers still get stuck both ways.
-im using the x64 captivate drivers from the odin3 thread on xda. running andromeda3 ROM.
anyone know what this could possibly be?
JBLogic said:
Just made the switch from ubuntu 10.10 to windows 7, didnt have issues using my cappy as a mass storage device on ubuntu
On win7 x64 if I try to transfer a file thats just more than a few mb's either from the cappy to the pc or vice versa, the transfer just gets stuck, the loading bar is flashing but it doesnt get anywhere. I have to unplug my phone from the computer in order for it to go away, this causes windows explorer(not the internet browser) to restart as well.
-my other usb devices work without a problem
-have tried all six usb ports on my computer, same thing
-even weirder, i reformatted, installed win7 x86 just to see, transfers work fine on it. Reformatted again and installed x64 with fingers crossed, transfers didnt work on it again.
-I have tried transferring files with no windows updates installed on x64 as well as all updates installed, file transfers still get stuck both ways.
-im using the x64 captivate drivers from the odin3 thread on xda. running andromeda3 ROM.
anyone know what this could possibly be?
Click to expand...
Click to collapse
sounds like bad drivers from samsung or windows is not using the newest driver version, maybe downloading drivers from samsung and manually installing would help
32 bit version of windows will have different drivers
I installed .net 4 and that seems to have fixed my problem, if that makes any sense.
makes sense. i keep forgetting about that but it is something you should have for alot of things in windows, thought it was one of the required things for adb and odin as well. not sure though
JBLogic said:
Just made the switch from ubuntu 10.10 to windows 7
Click to expand...
Click to collapse
I'm lucky enough to have a roomate with a dual boot ubuntu/windows so I can keep my Ubuntu and borrow his windows machine when I need it. Definately sounds like driver/ .net 4 issues though.
My nook use to be able to connect to my fedora computer at home and my windows computer (had to install Motorola drivers for that) at work.
I had no troubles connecting either with my rooted stock nook or with running CM7 from the SD card.
I installed CM7 internally and really messed that up. Eventually I got it working and everything works fine except I cannot get it to connect via usb on either my linux machine nor my windows.
What information can I provide?
Windows sees it but the driver fails according to device manager (explorer shows the drive letters but when I select it, it tells me to insert a disk.) Linux shows nothing in kde but I can run lsusb when I get home to see if it even sees it.
I tried pugging it into my fedora machine.
The only new line between when it is plugged in and not is
Bus 002 Device 004: ID 2080:0002
What version of CM7 are you running? My USB connectivity stopped working with nightly 69. It worked fine with 7.0.2.
That must be it. I have been updating hoping the problem would be resolved. I'll try downgrading to a build pre-69.
I am at 75 right now. I couldn;t get 76 to boot and the comments said that 77 suffered the same affliction.
I had to wipe my nook and start over so I really didn;t notice the version change otherwise I would have started there.
Thanks for the heads up.
I'll post back tonight on weather downgrading solved this issue.
At home, I ssh into my nook, but this isn't possible at work since I can't get the nook on a network there.
I used the usb apk to get around this issue.
Thank you
I just upgraded from CM7 nightly 76 to nightly 87, and now usb storage works perfectly. The internal emmc partition and my sd card pop right up in Windows.
I just installed nightly 87 today & I am still having no USB connectivity at all. Did you also install an OC kernel?
christoophat said:
I just installed nightly 87 today & I am still having no USB connectivity at all. Did you also install an OC kernel?
Click to expand...
Click to collapse
Nope, stock kernel that came with CM7.
Alright...looks I have some work to do tonight, thanks
Hi everyone,
I have an AT&T Captivate SGH-i897 (2nd hand) and i can't mount the phone to my laptop (winXP 32bit). When i plug in the cable to the phone and then the PC i get the "device not recognized".I've donwloaded the Samsung drivers from the xda wiki page and extracted them and tried to update the driveres via Device Mng ,but didn't work.Also dl'ed the Samsung drivers 5.0.x instaled ,and still nothing.USB Debugging is on...
So to recap,my top can't recognize the phone('s internal sd card) so plz help ???????
Try this, go into usb settings and choose "mass storage"
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
install kies
I would also recommend trying to fully uninstall all the drivers that associated on your pc with your phone (samsung or otherwise), and then reinstall the drivers before you plug in your phone. Then try to reconnect.
Just covering the basics. Assuming your phone is working correctly.
You have tried multiple USB ports on your computer, particularly those on the back if it's a desktop.
You have installed correct drivers (x86 or x64)
" for the correct operating system.
You have uninstalled the drivers before trying to reinstall.
You've tried to get Windows/ Mac to find them online (assuming you're using versions of OS that support doing that)
You've first tried Kies mini before full version, uninstalling in between. (Kies full version isn't supported for US, there are workarounds, but that's a different discussion)
On the phone you tell the phone to connect 'USB storage' (from the pull down menu after connected or in the settings)
I too am having problems with USB connectivity on a notebook with Win7/64. The usual failure mode is Windows not recognizing the USB device. I have followed ZBigT's basics, step by step and still cannot connect.
FWIW, my registry is awash with Samsung entries, some of which cannot be deleted.
I've even tried the AIO Toolbox application (to install the 64 bit drivers) to no avail.
Any other tips?
Is usb debugging turned off?
o hey guys sry for keeping u waiting,
i menaged to install ginger ,
the problem was my lap....rusty old bucket!!!!
had my friend come over with his lap and it worked like a charm ,
the problem is now i need a new one ;(,
damn
mrhaley30705 said:
Is usb debugging turned off?
Click to expand...
Click to collapse
Yes. Still no love. Have tried:
usb_drivers_GalaxyS_x64
SGH-i897_Captivate_USB_Drivers_5_02_0_2
mini-KIES
Kies
AIO
uninstalling reinstalling each time
When I plug in the Captivate, any of 3 USB ports on the laptop, Windows gives the "Unrecognized Device..." message.
Go to settings/about phone. Look at the very bottom to see what rom you are running.
mrhaley30705 said:
Go to settings/about phone. Look at the very bottom to see what rom you are running.
Click to expand...
Click to collapse
Paragon RC6.0
FWIW, I also have a Win7/64 desktop with the usb_drivers_GalaxyS_x64 installed and that works fine; can connect see "drives", use ODIN, adb commands etc.
It just the notebook, which I would like to be able to use to connect, especially when I travel, which has issues.
mabovalu said:
Paragon RC6.0
FWIW, I also have a Win7/64 desktop with the usb_drivers_GalaxyS_x64 installed and that works fine; can connect see "drives", use ODIN, adb commands etc.
It just the notebook, which I would like to be able to use to connect, especially when I travel, which has issues.
Click to expand...
Click to collapse
Check in program files for a Samsung folder. There may be remnants from old drivers that need to be manually deleted.
mrhaley30705 said:
Check in program files for a Samsung folder. There may be remnants from old drivers that need to be manually deleted.
Click to expand...
Click to collapse
Thanks for sticking with this. I was able to connect. I as focused on the Registry remnants, but your advice to clear out the Samsung folder in Programs worked. Thank you.
Additional comments: I am now running the Dlev ROM, it's OK, but when I plugged in the USB cable, just to the phone, it launched the Alarm Clock app! So I deleted that.
Then on the first of my four USB ports I got a USB driver failure to install, then the Windows Unrecognized USB device on ports 2 & 3. On port 4 it worked. (This is a Lennovo/Thinkpad notebook.)
I used the usb_drivers_GalaxyS_x64 package as that also worked on my desktop.
Thank you very much.