My Dell desktop does not recognized my Fascinate after upgrading to Windows 7 Service Pack 1.
I can't use ODEN any more, can't even mount the SD card anymore.
Really stuck big time.
HELP HELP HELP!!!
Still stuck and feel like getting rid of my phone and verizon all together.
Whats wrong with microsoft and samsung, I know another guy that couldn't print after upgrading to SP1.
its possible that the samsung drivers are not installed.
Sent from my SCH-I500 using XDA Premium App
Definitely start by uninstalling the drivers, and then reinstalling the latest version (for the extra paranoid, run something like driver sweeper before reinstalling). Also, try different ports on your computer/make sure you're using the official cable that came with your Fascinate.
If that doesn't work let us know (along with anything else you've tried, just to save us from telling you to do things you've already done!).
Also, just for future reference, this should go in the Q&A section- Development is meant for postings of ROMs and other similar things (there's a high probability your post could get rocketed off the front page before anyone even notices it in this section!).
Agreed, try upgrading your drivers. If that does not work initially, reboot into CWM with the phone plugged in, that usually forces Windows to detect the device drivers again and install them (always works for me when Windows *forgets* the Samsung drivers).
As the poster said above, this should have been posted in Q&A or General, and not development. I have reported the post so that a mod can move your thread to the appropriate section.
i have this problem before.
With debugging on, power phone off, plug into computer and power phone on. That should allow the computer to see your phone
Click to expand...
Click to collapse
androidcentral
Here another thing to try- shut down computer, and then unplug the power chord from the back. Let it sit, then plug it in and boot it up.
That's what worked for me.
Sent from my SCH-I500 using XDA App
I've run into this issue several times, and have found a few solutions.
Several times, it took completely removing the drivers and reinstalling them. By completely removing them, I mean uninstalling them through add/remove programs and then by searching through the registry for the many traces that the driver uninstall misses. And there are many... like hundreds. And there are all kinds of permission problems on those registry keys that you need to fix, one by one, before they can be deleted. It's a major PITA that takes hours to do. But once it's done, I was able to reinstall the drivers and the phone was recognized fine.
Another issue I ran into was a possibly faulty USB cable. Just recently, Windows just stopped recognizing the phone, and in trying different ports, I happened to notice Windows was detecting the bare cable (as in it wasn't plugged into the phone). I could plug the cable alone in, and Windows would recognize it as an "unrecognized USB device". I tried a different cable and it saw the phone fine.
So, first thing to check is your cable. Does Windows detect it when you just plug in the cable by itself? If so, try a different one.
If nothing else works, and you want to remove the drivers totally, let us know and I'll walk you through the steps to remove all those bloody registry keys, but it's not fun...
ChrisDDD said:
I've run into this issue several times, and have found a few solutions.
Several times, it took completely removing the drivers and reinstalling them. By completely removing them, I mean uninstalling them through add/remove programs and then by searching through the registry for the many traces that the driver uninstall misses. And there are many... like hundreds. And there are all kinds of permission problems on those registry keys that you need to fix, one by one, before they can be deleted. It's a major PITA that takes hours to do.
Click to expand...
Click to collapse
Revo Uninstaller is an ideal solution for totally cleaning stuff out. Pick the most aggressive sweep, and after the factory uninataller finishes, it isolates and removes all the leftover registry keys, files, and folders associated with the uninstalled item. Found it to be a godsend as a PC tech in a big school district with way more computers to manage than I had time.
The free version is more than adequate.
Materialized into existence through the act of observation.
Here is my observation, my USB mass storage doesn't get recognized on the computer hardly ever (it was a miracle and an event to be celebrated if it happened), and I talked to some people in IRC about it. GizmoDroid had me trying lots of different things. Eventually I just installed ADB, and to my surprise, ADB always sees the phone just fine. So, I think the Samsung drivers need tweaked a bit because they definitely work, but something about them just doesn't work correctly with Windows (or with anything, but has samsung ever put out any software that was up to our standards?).
My suggestion is to install and learn ADB, not hard at all with the given tutorials. Even easier if you have experience with Linux. It always, always works for me.
tbeas said:
My suggestion is to install and learn ADB, not hard at all with the given tutorials. Even easier if you have experience with Linux. It always, always works for me.
Click to expand...
Click to collapse
ADB would work as an alternative to USB mass storage for the most part (which shouldn't need the Samsung drivers), but it isn't an alternative to being able to use Odin!
agsded said:
Revo Uninstaller is an ideal solution for totally cleaning stuff out. Pick the most aggressive sweep, and after the factory uninataller finishes, it isolates and removes all the leftover registry keys, files, and folders associated with the uninstalled item. Found it to be a godsend as a PC tech in a big school district with way more computers to manage than I had time.
Click to expand...
Click to collapse
Cool, thanks, I'll definitely check that out. I had set up some macros to repeat the process of setting ownership of each key and deleting it, but it still took hours.
tbeas said:
Here is my observation, my USB mass storage doesn't get recognized on the computer hardly ever
Click to expand...
Click to collapse
The OP can correct me if I'm wrong, but this isn't just a mass storage problem, the phone itself isn't recognized as anything at all, so that means mass storage doesn't work, Odin won't pick it up, nor will ADB. Connect the phone, and at best, Windows sees an "unrecognized USB device", at worst, it sees nothing at all, as if the phone wasn't even connected.
Mine will go invisible to Odin at times, also. I will go to heimdall at that point and it will usually be visible there. I keep both programs around partially for that reason, and partially cause of how granular heimdall is.
Materialized into existence through the act of observation.
Delete
KitsuneKnight said:
ADB would work as an alternative to USB mass storage for the most part (which shouldn't need the Samsung drivers), but it isn't an alternative to being able to use Odin!
Click to expand...
Click to collapse
Adb 100% needs the Samsung drivers.
Sent from my SCH-I500 using XDA App
suppliesidejesus said:
Adb 100% needs the Samsung drivers.
Click to expand...
Click to collapse
The drivers might not be necessary if connecting to the phone with ADB over TCPIP, which you can set using a terminal emulator on the phone.
Don't know if you need to log in as SU or not, but these are the commands:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
These set the adb daemon to listen over the port 5555, then stop and restart the daemon.
Then on the computer, you'd type:
adb connect 192.168.1.xxx:5555
Then:
adb shell
And it should connect.
Not that this would solve the Odin issue, but it's at least one way to get stuff on/off the phone when the drivers crap out.
zzd4nzz said:
-Uninstall Samsung Drivers
-Uninstall USB Root Hub
-Restart Computer (On boot up, the computer will automatically install USB Root Hub)
-Install Samsung Drivers
-Hold down Vol - while plugging into phone to get into download mode
-Odin will hopefully recognize the phone.
Click to expand...
Click to collapse
Thanks to all you guys,
But! I tried every thing, uninstall samsung, uninstall usb hub, reinstall drivers.
I am ready to just sell my fascinate and get an Straight Talk phone to have peace of mind.
Please Help
http://forum.xda-developers.com/showthread.php?t=1065727
Which rom and kernel are you using?
Ive always gotten it to work on my devices. I had it working on my TB, then I got a replacement and now it doesnt work. I instaalled HTC sync, uninstalled it, let Windows install the drivers. That keeps failing. I have debug checked. I keep getting "error device not found"
i sort of ran into this problem myself.
i had to uninstall htc sync and then start the entire sdk/adb install all over. somehow htc sync messes with the other method of installing the drivers. this is what i used.
the files are in the video description.
http://www.youtube.com/watch?v=oKPSe12YDxQ
try checking interent passthrough and letting it install the drivers.
you need to install the drivers manually, its a pain to type but if u pm me ill help u...dont forget the thanks
astefanik said:
try checking interent passthrough and letting it install the drivers.
Click to expand...
Click to collapse
Yeah, B16 walked me through it yesterday. This was the issue all tough my disk drive doesnt work now.
I have a non-rooted, running CM7 from an SD card. I have the USB drivers from xboxexpert. My nook is in debug mode. I've tried both USB storage on and off. I used Droid Explorer and Sideload Wonder Machine 1.2 and neither will recognize the nook. I can't get any combination of the above items to side load apps.
I can see the proper USB show up in device manager. I've tried different cables and ports on the PC. Tried multiple PCs. If I had any hair it would've fallen out. Please point me in the right direction. Thanks.
Will
just tried this and still doesn't recognize nook.
http://nookdevs.com/NookColor_USB_ADB
What is it exactly that you are trying to accomplish? It doesn't sound like you are trying to side load an app.
Side loading an app is the easiest thing to do in the world and you don't need ADB to do so. Just make sure the install from "unknown sources" is checked under the applications settings page and install away.
Just use Dropbox to transfer the apk over... no need for adb... And fyi CM is rooted.
Sent from my NookColor using Tapatalk
I guess I was trying to do it the hard way. I got it now.
Use Windows file explorer to drop APK file to Nook. Use File manager on Nook to find APK file and click it. Install app.
Yes, like another posting says, "small kids are pointing at me and laughing".
Thanks guys
Will
For some weird reason I am unable to access files via Android File Transfer with usb cable. I never had any such problems with any other android device before. I just flashed S6 rom and still have same problem. Did anyone else face this? Any solution? Thanks.
/S
I'm having the same problem on my MacBook, but not my iMac. Both are on Yosemite 10.10.3. I have USB debugging enabled and all that, and still can't get Android File Transfer to work. I've toggled it to get it to reauthorize this mac, but still no luck. I'm going to have to play with the MacBook. On the iMac, I did have to complete remove Android File Transfer and all of it's preference files, reboot, reinstall AFT, and reauthorize the mac to get it working. I'm thinking since I have more users on my MacBook, that may have something to do with it, so I need to dig in both user files. I'll report back
Also, I can't use ADB. I'm getting that the device is offline on both macs.
i am having same issue with.
installed smart transfer and still same issue
I installed ADB and fastboot from http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378 and Bloater from http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294.
I have one KFHD6 that got the OTA 4.5.4 update prior to anything else. This one connects to my PC just fine and ADB works. It's the device I used to install PDANet, which helped me get the computer to recognize the Kindle in ADB.
I took another KFHD6 out of the box today (on 4.5.3), ADB was enabled by default, I did not setup Wi-Fi so I could keep 4.5.3. When I connect it to my PC, I get the Autoplay popup on my computer, but ADB does not connect. There's no prompt to trust the computer. I've tried the same cable. I've tried turning ADB off and back on. I've rebooted my devices.
I did notice that the Autoplay icon is different for the two Kindles. The 4.5.4 looks like a phone ( http://www.groovypost.com/wp-content/uploads/2012/09/Open-Device-to-View-Files-AutoPlay.png ). The 4.5.3 looks like a tablet like the icon here ( http://cnet1.cbsistatic.com/hub/i/r.../066e9701a8d91559092f149bd6b32516/drivers.jpg )
Does anyone have any suggestions? Thanks!
I figured it out. I don't have PDANet installed on the 2nd Kindle. Can someone tell me the path in the Silk Browser to execute the apk? For example,
file:///Download/PdaNet.apk
But that's not it. I don't have Internet on the Kindle yet, because I don't want OTA updates, so I can't install ES Explorer from the Store. I just need to be able to execute the APK file that I transferred to the Kindle via the USB cable. Thanks!
I figured THAT out. But Silk is not executing the file. It states that it has to download it and that it can be found in Downloads, but then the screen goes black and nothing happens. I hit home to get out of Silk, go back in and it's still black. If I reboot, and then open Silk, it asks if I want to restore my tabs. Yes, gives a black screen. No puts me back at the Silk browser again. The file doesn't show up in the Downloads section of Silk, so I'm unable to execute it. Surely there's a way to install APK files without ES Explorer (I'd actually like to install ES Explorer, but without Internet access).
Which came first--the chicken or the egg? Please help. Thanks!
I have yet to figure this out. I have several KFHD6's. The first one was a breeze to get ADB working. The second one had trouble, but it finally started working when I uninstalled the driver from the Device Manager and the ADB Driver installed. I have 3 more new Kindles which don't want to get on the ADB bus. Does anyone have any suggestions? Here's what I've done:
Installed Minimal ADB and Fastboot (http://forum.xda-developers.com/showthread.php?t=2317790)
Installed PdaNet (http://pdanet.co/)
Installed Android SDK (http://dl.google.com/android/installer_r24.3.3-windows.exe)
Updated an inf file and tried to update the driver (http://www.jayceooi.com/how-to-install-kindle-fire-adb-usb-driver/)
The first worked after the first 2 bullets. The second worked after the first 3 bullets and then uninstalling the driver in the Device Manager. Any input would be greatly appreciated.
Here's the solution if anyone has this problem:
Plug in the new device. Let it install the driver in Device Manager. Right-click --> Properties on it. Uninstall device and unplug it. Reboot your PC and you Kindle. Plug your Kindle back in.
It was that easy for me--on 2 new devices. The 3rd was literally plug-and-play. Very weird.