Related
[FIXED] thanks guys
When I connect my Samsung Galaxy S, the computer doesn't do ANYTHING (it doesn't recognize that anything has been connected), and the SGS doesn't even recognize that it's connected to anything. All the phone does is charge...not even a notification drop down prompts me to enter USB mass storage or charge etc. I've factory reset the phone many times (plugged & unplugged), and nothing seems to fix it. I can't find my SGS in the Device manager to reinstall drivers either.
I am running Windows 7 64bit on a Sony Vaio, if that helps.
I've searched tons of sites & forums and none seems to have a working solution...Any ideas/fixes?
I think I found the problem I was having...I was using a Rocketfish CHARGING cable, and although it looks like a USB cable (it connects to the computer via usb), it does nothing but charge...so I took off the micro usb adapter that affixed onto the mini usb charging cable and re-affixed it onto a random mini usb cable I had lying around. And now it connects to the computer! I can now use all the other tutorials fixing the generic "usb driver not installed properly" problem.
UPDATE: I was following the tutorial on http://theunlockr.com/2009/12/02/how-to-root-the-samsung-behold-2-samsung-galaxy/ but when I get to the fastboot part, my phone won't boot into fastboot.... Can anyone help?
download 64-bit drivers here: http://forum.xda-developers.com/showthread.php?t=728929
turn on usb-debugging mode in settings. you have to manually choose to mount the volume on the SGS every time you plug it in.
should work.
you need to either install KIES, or install the drivers included in the Android SDK
AllGamer said:
you need to either install KIES, or install the drivers included in the Android SDK
Click to expand...
Click to collapse
I got my phone to connect & be recognized by my computer, but I can't seem to get my phone into fastboot. Can anyone tell me which keys to press...?
I had the exact same problem. Googled and found a forum post somewhere with the following solution:
Turn off Galaxy S. Connect to pc by USB. Turn on Galaxy S.
...
Yeah.
Worked for me, anyway. Ever since I did that it's been working fine even if I connect it while it's turned on.
EDIT: Gah, didn't notice you had it solved already, thought the second post was from someone else. Oh well.
Zavonn said:
I got my phone to connect & be recognized by my computer, but I can't seem to get my phone into fastboot. Can anyone tell me which keys to press...?
Click to expand...
Click to collapse
steps to get into those boot modes
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/GT-I9000M
I can't get mine to connect using the above methods to windows 7 - windows 7 says it cannot install the MTB drivers.
gladman said:
I can't get mine to connect using the above methods to windows 7 - windows 7 says it cannot install the MTB drivers.
Click to expand...
Click to collapse
Uninstall/reinstall kies.. Under kies, repair drivers.. Worked for me
Thanks. I didn't even know what kies was til after I wrote that.
Sent from my HTC Desire using Tapatalk
Spitfire128 said:
I had the exact same problem. Googled and found a forum post somewhere with the following solution:
Turn off Galaxy S. Connect to pc by USB. Turn on Galaxy S.
...
Yeah.
Worked for me, anyway. Ever since I did that it's been working fine even if I connect it while it's turned on.
EDIT: Gah, didn't notice you had it solved already, thought the second post was from someone else. Oh well.
Click to expand...
Click to collapse
didn't work
Use the cable that came with your phone. I had issues with a second cable I bought for my second pc. Changed the cable back and everything was fine.
thegangsta said:
Use the cable that came with your phone. I had issues with a second cable I bought for my second pc. Changed the cable back and everything was fine.
Click to expand...
Click to collapse
For all, there has always been a problem with sammy usb cables/ports, so when connected up to pc, always take care not to knock phone, this will become especially important when you connect to odin if you get into rom flashing
Insanity cm 014/glitch
Samsung Galaxy S EPIC not recognized by win 7 computers
Pls install Android SDK .It may require you to install java jdk .Then install the samsung drivers for 64 bit install 64 bit drivers ......32 bit won't work. & use the genuine samsung cable. No need of powered hubs or desktops instead of laptops. It will work. Thanks
Spitfire128 said:
I had the exact same problem. Googled and found a forum post somewhere with the following solution:
Turn off Galaxy S. Connect to pc by USB. Turn on Galaxy S.
...
Yeah.
Worked for me, anyway. Ever since I did that it's been working fine even if I connect it while it's turned on.
EDIT: Gah, didn't notice you had it solved already, thought the second post was from someone else. Oh well.
Click to expand...
Click to collapse
thanks a ton man !!
this issue was getting on my nerves and i googled alot but couldnt find a solution to it...and then i searched on xda ..saw few same issues but the solution didnt work and now when i came here and tried your method..it actually worked though i dont own this phone but your post helped..thanks man
Well to start out I have googled the drivers but still doesn't work... after bricking it pretty bad this happen and I fixed it by drivers while bricked to flash it to stock. But it has happened to me again after odin. Is it possible to just break it. Can someone link me working drivers maybe I've been trying ones that don't work or something
Sent from my SAMSUNG-SGH-I897 using XDA App
donk232 said:
Well to start out I have googled the drivers but still doesn't work... after bricking it pretty bad this happen and I fixed it by drivers while bricked to flash it to stock. But it has happened to me again after odin. Is it possible to just break it. Can someone link me working drivers maybe I've been trying ones that don't work or something
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
It's not recognized when the phone is on? Seeing as you posted this topic using your phone I assume so lol. Have you tried restarting your computer?
You can download the correct drivers here.
http://forum.xda-developers.com/showthread.php?t=731989
Make sure you are using the oem usb cable. I had the same problem, changed cables and it worked
some cheap cables are for charging ... bt headsets and other stuff the data cables dont connect, its just for power.
koreancanuck said:
It's not recognized when the phone is on? Seeing as you posted this topic using your phone I assume so lol. Have you tried restarting your computer?
You can download the correct drivers here.
http://forum.xda-developers.com/showthread.php?t=731989
Click to expand...
Click to collapse
deleted drivers restarted, installed drivers restarted and still not working. i am using the cord that came with the phone.
donks232 said:
deleted drivers restarted, installed drivers restarted and still not working. i am using the cord that came with the phone.
Click to expand...
Click to collapse
You gotta make sure that your usb port is directly connected to your motherboard (usually back of your computer).
same usb port that has always worked. ive tried them all by now anyway
now i cant tell you how this helped but... i downloaded drivers to a different computer odin crashed while flashing reflashed and im 100% stock atm. Didnt do ANYTHING to my computer plugged it in and its working.
donks232 said:
now i cant tell you how this helped but... i downloaded drivers to a different computer odin crashed while flashing reflashed and im 100% stock atm. Didnt do ANYTHING to my computer plugged it in and its working.
Click to expand...
Click to collapse
lolol
Duno what happened but I'm glad it worked out for you
I'm having the same problem with my captivate after flashing REDROM. It won't recognize it if I have USB debugging turned on...
i have a theory... were you on a GB or other i9000 based rom/kernel???
well, im still having a problem getting my computer to recognize the phone, i have to mess with it for a a while to get it to work. i really want to flash anew 2.3.3 rom but without being able to get everything working right im stuck in 2.1
is this a problem with my cord or the connection on my phone? or something weird with my phone after flashing it a lot. its currently back to odin stock, i have been trying to master clear it with no luck
TRusselo said:
i have a theory... were you on a GB or other i9000 based rom/kernel???
Click to expand...
Click to collapse
continiuum miui and cyanogen mod are the only things ive tried to flash
well it looks like i'm done. my phone will not show up on my computer and its currently bricked, although i have no issue getting it to download mode i cant do anything with it. unless someone knows some magic, looks like im downgrading to my gf's 4 year old busted up BB
Guys, this problem while connecting to the PC body is stupidly charging .... Even in the download mode Odin does not see a body that could be? Connect other Cappy-all OK.
donks232 said:
well it looks like i'm done. my phone will not show up on my computer and its currently bricked, although i have no issue getting it to download mode i cant do anything with it. unless someone knows some magic, looks like im downgrading to my gf's 4 year old busted up BB
Click to expand...
Click to collapse
it must be a powered usb hub, on my buddies laptop only 1 out of 4 usb ports saw his phone.
if you can get into download mode you arent bricked.
try installing i9000 drivers, or try another computer.
I came up with this a while back. Could very well be the same issue.
Let me start by saying I'm flash happy, and everyone that knows me personally, tells me to just quit jacking with my phone. NOT A CHANCE! I'm on my 3rd Cappy and shouldn't have ever exchange it again. I only had to in the beginning, because I was a newbie and had not know enough, but to get me in trouble.
I presume that this should work on all Windows OS's. I personally am running Vista Enterprise x86.
My symptoms:
Plug in phone to the usb and it there was about a 15% chance off being able to mount to usb, and Windows recognizing as a mass storage device. I tried un-installing drivers and re-installing and it would work some of the time, until the point came when parts of the driver install would fail. Then to the point when it was just completely unrecognizable. I thought I had it fixed because it seemed intermittent. In the middle of flashing to stock, something interrupted communication between the pc and my phone. Restarted the phone and attempted the flash again. Got a little farther and froze again. I had to use another pc that I had never connected my phone to before and I was able to use my jig to trigger download mode, because no buttons combinations would allow it into download mode.
This got me thinking that it was specific to my pc and not my cable or my phone.
My resolution:
I went straight to the registry and went to find. I deleted every entry that came up for "i897" and "i9000" excluding what was listed in the system volume information, as I didn't have permissions to remove any keys. I didn't keep count, but I probably deleted 300-400 registry keys that pointed to my phone. It seems as if with each developers rom that I had flashed, there was an entry for a different device. Don't quote me on that, because it is just my personal consensus. I also un-installed the samsung drivers, the unknown device driver, kies software, and anything associated with samsung. I noticed that next to all of the i9000 instances, the hex key for me started with 1000ee. So I also searched for the first part of that key trying to ensure that all instances of the device. Lastly, I deleted the samsung folder from program files.
I installed the samsung drivers package commonly listed in all of the other threads for x86 operating systems. I plugged in my phone and watched as each and every driver installed successfully. Keep in mind different drivers are installed depending on if you have usb debugging on/off, and the options for if the preferences on you phone are set to media, storage, or kies. I have multiple usb ports, however testing has shown me that, for me and my setup, I can plug into the port that I used when installing the drivers the final time, I am able to connect consistently. Earlier today, I tried to plug into a different usb port and it was an unknown device. I am led to believe, this is because I didn't un-install the unknown device on this particular port.
If you intend to work in the registry, please remember to always back it up first. You can always restore.
Hopefully my findings can help you as they did me. Happy flashing and I would like to thank the community for the dedication to assisting each other and the developers, for making flashing, better than crack cocaine. Flashing rom's doesn't make you twitch near as much as a crackhead.
Well since you can't use your phone you should sell it to me
Sent from my GT-I9000 using XDA Premium App
I didn't even install drivers, ubuntu got them for me
Sent from my SGH-I897 using XDA Premium App
ok first off I have searched and have yet to find a sollution. So if there is one please flame me and point me to it.
Problem : I have 2 computers, both win 7 x64 pro. my desktop does not detect any cell phone, my friends droid 1 or my samsung captivate..... Both have all the drivers installed. That is a small problem because i have a laptop that does ( DID)
Big problem : phone having problems, me flash captivate and flash fail ( i think i used odin 2.2 flasher which for some reason doesnt want to work, i tryed it a few times before... but anyways so I'm in download mode and now the computer wont detect my phone, just like my desktop, I get the UNKNOWN USB device or the usb device did not install correctly blah blah blah malfunction... SO now I'm able to get into DL mode but thats it.... so where is the fix for this? Please help . its so strange that no changes were made and it goes from having worked for months to not working at all suddenly...
Again neither odin v 2.1 or v 2.2 ( as in froyo and eclar) will detect phone nor will the hemdol program or what evs.... so i can not boot past download mode. Please help .
the answers are out there... itll just take a bit of reading... however sounds like there are program incompatibilities somewhere not allowing your drivers to install especially after you said drivers did not install blah blah. Also try changing usb ports when you plug it in and go through and check to make sure all you usb drivers and ports are functioning properly. Furthermore check to ensure your charging port isnt loose and or pins bent or broken same with your cable.
try this as well... says right click and run odin in admin etc.
http://forum.xda-developers.com/showthread.php?p=16936821#post16936821
xbadwolfx said:
try this as well... says right click and run odin in admin etc.
http://forum.xda-developers.com/showthread.php?p=16936821#post16936821
Click to expand...
Click to collapse
Also use XP service pack 2 mode. This helps also.
JJ133169 said:
ok first off I have searched and have yet to find a sollution. So if there is one please flame me and point me to it.
Problem : I have 2 computers, both win 7 x64 pro. my desktop does not detect any cell phone, my friends droid 1 or my samsung captivate..... Both have all the drivers installed. That is a small problem because i have a laptop that does ( DID)
Big problem : phone having problems, me flash captivate and flash fail ( i think i used odin 2.2 flasher which for some reason doesnt want to work, i tryed it a few times before... but anyways so I'm in download mode and now the computer wont detect my phone, just like my desktop, I get the UNKNOWN USB device or the usb device did not install correctly blah blah blah malfunction... SO now I'm able to get into DL mode but thats it.... so where is the fix for this? Please help . its so strange that no changes were made and it goes from having worked for months to not working at all suddenly...
Again neither odin v 2.1 or v 2.2 ( as in froyo and eclar) will detect phone nor will the hemdol program or what evs.... so i can not boot past download mode. Please help .
Click to expand...
Click to collapse
What rom are you on? CM7 MIUI?
Well huge problem... for some reason the phone wont charge now so now i cant even get in DL mode and before that i couldnt for the life of me no matter what i read find a fix for the USB issue. idk what the **** it is but its really annoying.... I was using OFFICAL 2.2 and was trying to reflash it and try it again or flash 2.1 because i was getting random restarts. then the flash failed for some reason first time ever I think ( i seriously have flashed about a dozen times since ive had my phone over 9 months, So i know alot and have read alot, have a jig and all that jazz) so i know what im doing... I just got my phone back from samsung about a month ago they fixed a random button pressing problem, and now the turning off on a Stock rom ( plus firefly prior, why i went back to stock) made me paranoid, plus i use it as a clock for work so i cant have it turn off randomly at all. So what am I to do? I possibly can use my friends battery for a bit or my womans... but im thinking maybe this has less to do with computer now and possibly that my phone fried or something that i should send it in to samsung for warranty repair...since obviously if it was restarting on a new 2.2 instalation obviously there were probably some problems...
I read a similar story of this randomly happening to another experienced user on google, and he sent it in to samsung and they just sent him a new phone... my AT&T warrianty is long gone on my refurb but i still got 3 months left with samsung... idk why it isnt even charging on wall outlet or computer...
what to do?
Did the phone go "dead" after a failed firmware flash? Or it literally just all of a sudden won't charge? If it was truly random then it's a hardware problem all the way and most likely an issue with the USB port or a trace routed through it. Only 2 lines control charging and the Captivate is notorious for a pretty solid port from my findings.
Well I left my phone in the wall for hours and I guess it does charge so its not completely dead. Now just the issue of reflashing stock on there... so getting the USB to work in my computer. I take it the USB in the phone isnt dead or the JIG wouldnt work... I just want to know if the Random shut off is hardware related or a bad flash / rom? Anyone know what has less problems? 2.1 or 2.2? I dont think my keyboard is in 2.1 so i dont think i could take it... but i just want a working phone with my gingerbread keyboard <3 I just dont want it to turn off on me...
and now randomly odin's will still not detect, but heimdol will, but it fails about 18% into factoryrfs or what evs. And Yes I have used it before and yes I am following all directions. WTF this is blowing my mind... and yes repartition is selected
Are you using an OEM Samsung Cable? Don't use knock off cable for anything more than charging...
just fyi if u rooted ur phone and samsung checks the programing to find out and trouble shoot it will void your warranty and youll have to pay for it... so um maybe try spending the 50 and go with a refurb thru insurance.
Yes I'm using stock cable...
ANd its not rooted, its not ANYTHING since there is no OS on the phone so no way to see anything to void anything...
now most things ( on different computers) will detect the phone and all odin and heimdol but they will both fail at the beginning of any flash... Its like nothing can be pushed through the phone.... ?
I have heard once hedimall is used on a computer it screws with odin and wont let it see ur phone
Sent from my Stock KH3/4 2.3.4 Captivate using the XDA Premium App!
b-eock said:
I have heard once hedimall is used on a computer it screws with odin and wont let it see ur phone
Sent from my Stock KH3/4 2.3.4 Captivate using the XDA Premium App!
Click to expand...
Click to collapse
It doesn't necessarily screw with it. Heimdall installs a custom WinLIB USB driver to operate with Samsung Composite USB devices. This driver is used for Samsung Download mode which ODIN doesn't recognize. To switch back to using ODIN, you just need to go into device manager and uninstall the device and be sure to DELETE DRIVER FOR THE DEVICE. Then just plug the phone back in when in DL mode and the Samsung driver will be re-installed. However, this is really beginning to sound more like a hardware problem. I emailed you back and would be happy to put a final diagnosis or repair on the devil phone.
So heres the thing.
I flashed some firmware on my phone (did it 100 times no problem) but i got fail in odin.
I said ok nothing is wrong i can fix it. but to my suprise Odin wont recognise my phone. I get a message that the Usb is unknown.
Now beacuse i reinstalled my drivers i think that the computer needs a first time plug of another galaxy s to install the driver from the phone is that correct? (Cause my phone can only go to download mode)
so all i need to do is to get another galaxy s plug it in and let the computer recognise it for the first time. and than use my broken phone phone and it will work?
what firmware was it ,if it was ics sometimes you lose usb connections and odin wont recoqnise the phone
TIGER 123 said:
what firmware was it ,if it was ics sometimes you lose usb connections and odin wont recoqnise the phone
Click to expand...
Click to collapse
@Topic started i have the same problem and have a similar thread.
as for tiger. . . does that mean ics users are screwed if that occurs to them?
http://forum.xda-developers.com/showthread.php?t=1431523
I used this one
Problem solved here. I hope this solution helps you
I've tried so much, seriously SO MUCH. At the end it turns out it was my usb cable. i ripped my old usb cable apart for making me go ape ****.
lesson? No matter how many times you install, change ports, etc. Always be sure to try a new usb cabel. If you don't have a second one, i'd suggest you go buy a second one, it's worth a try. The whole time it wasn't working it was my stupid usb cable, changed it and in an instance i was ready to roll.
Wish you good luck!
Ok so I purchased an i9000M that was advertised as broken (got it for cheap) to see if I could get it going for my step daughter. I turn it on.... I get the samsung boot screen and goes black when it should be booting OS.
Windows still recognizes it somewhat. If I look in device manager under "portable devices" It shows a "j" and "k" drive that are identified as i9000 and i9000 sd or something like that. Although Windows sees it.... It wont mount these drives unfortunately.
Things I've tried ( Before someone suggests I use a JIG............. It doesn't and will not work on this phone)
USB JIG (tested and working on my Hercules)
SD Card Partition (EXT4 and FAT32) because I suspect borked internal storage
SD Card Partition (ReiserFS and FAT32) Still nothing......... then I realized the phone probably wasnt rooted
3 button combos ( every single combination) nada
plugging in USB cable while holding volume up and down...
ADB Reboot recovery/download ( not recognized because I cant turn on debugging)
ETC ETC ETC........
I have been searching google for hours for some kind of clue as to what can be done other than JTAG repair and All I come up with (no matter what site im on) is " Use a USB JIG" duhhhh Its getting rather annoying.
Im no stranger to flashing ( no expert) but this one has me stumped. I was considering buying a RIFFbox anyways but I thought maybe some experienced users out there might be able to suggest something.
My hope is that something can be done with the J and K drive that was mentioned. Perhaps I can format and somehow push a rom straight to the internal storage without any assistance from the phone itself...... I know..... wishful thinking. or perhaps boot straight from external SD???? That would be interesting!
More to this.... I realize this question has probably been asked a million times because it seems to be a common issue on this phone but I suppose my long winded question really boils down to my last paragraph which I havent seen suggested yet.
EDIT: I have a Windows 7 AND kubuntu 12.04 dual boot if any suggestions require linux
Any help would be greatly appriciated.
kibosh1981 said:
Any help would be greatly appriciated.
Click to expand...
Click to collapse
My Android Solutions should get you started but FIRST ensure your battery is no malfunctioning and Battery contacts are good and not loose.
xsenman said:
My Android Solutions should get you started but FIRST ensure your battery is no malfunctioning and Battery contacts are good and not loose.
Click to expand...
Click to collapse
Thanks. i will have a look and experiment tomorrow.
I'll report back my progress
if it pops up when you plug it into the computer, check if it does in odin. if does in there too try to flash a stock rom. or better yet take this download and follow the read me intructions, except the dl mode part cause you said it doesnt work. try both with the phone on and off. no it isnt the bell version of the pom but it will work. you will problably want to root it then install galaxy s unlock tool from the market and use that to unlock the phone aswell.(cause it not the bell rom)
http://www.mediafire.com/download.php?34oxweahfpy53dj
taz0697 said:
if it pops up when you plug it into the computer, check if it does in odin. if does in there too try to flash a stock rom. or better yet take this download and follow the read me intructions, except the dl mode part cause you said it doesnt work. try both with the phone on and off. no it isnt the bell version of the pom but it will work. you will problably want to root it then install galaxy s unlock tool from the market and use that to unlock the phone aswell.(cause it not the bell rom)
http://www.mediafire.com/download.php?34oxweahfpy53dj
Click to expand...
Click to collapse
As I mentioned.... no download mode, therefore.... No ODIN. Unless someone has some magical way to make it work otherwise. The computer knows its an I9000 at least. Kies says its in the wrong mode and I have no UI so debugging is out of the question.
Also: Xsenmen. I was unable to get any of the tools to connect. In one section you mention that AndroPlatina attempts to connect while booting? I was unable to get this to happen. I even tried the "heat trick" to no avail