Hi,
So i have a one year old GT-i9100 and with it came a USB-cable.
At first the Cable worked perfectly fine and i could gladly copy files from my internal/external storage to my PC and vice versa. But now, all of a sudden, my phone doesn't get recognized by the PC. This causes problems such as if i want to upgrade my software (when official stock JB is released) i wont be able do it. and this is also a major issue since i copy files very often for safe keeping and add ZIP files (with ROM or Kernel information) to my phone.
I've tried different ports but still no recognisation. I removed the drivers and completely uninstalled KIES and then reinstall it. The drivers got installed but KIES don't recognize my phone and neither does my phone appear as an external storage device.
As said this just happened all of a sudden, it was working good before. I have used a total of three USB cables which i've tried on both of my PCs but still no recognition on either one.
Please help me solve this problem.
(i will call Samsung support when i actually get home from school before the support closes )
Thank you for the time and extra thanx for replies
Oh, and it's rooted with Siyah Kernel and AllianceICS ROM
the problem may exist with the usb port on your device. It may need to be replaced.
You can buy a replacement on ebay but need to confident of your skills to replace it as it requires taking the phone apart.
In the mean time, try it out in other people's PC and laptops; can't hurt.
Related
So after searching the vast horizons of XDA I haven't found an answer that really helped me. Nor have I found someone with this distinct issue. I have an unlocked Samsung Vibrant. I have not rooted it. I updated to J16 with that P.O.S. Kies Mini a few months ago. I hadn't noticed this problem until the last month or so but I haven't had time to sit down and curse at my computer long enough or offer supplications to Google until now. I've just been using Awesome Drop to get what few files I wanted onto my phone. I've had enough of that now. And...I also want to update it to Froyo but I can't do that if I can't get my computer to see my phone. I'm running a Toshiba Satellite A205 with Windows Vista 32bit.
I have checked the drivers and as far as I can tell, I'm using the right ones. I downloaded Kies Mini again today (I deleted it after I was finished with J16 because I wanted it as far away from me as possible) and it seemed to say something about downloading drivers as well. I tried plugging in my phone. Nothing new. So, I went in search of drivers again. I have searched and tried a few different ones but nothing has solved my problem.
The phone charges fine from my laptop. It hooks up immediately and charges without a problem. Unfortunately, my phone seems to regard the PC as a complex wall-wart. Debugging on/off, USB Settings on Mass Storage, Kies, or Ask on connection, it doesn't matter. It doesn't give me the option to "mount" as it has in the past. It doesn't do anything except charge. I've seen some people say it's a problem with their cables (I've only got one at the moment) but since my phone charges fine, how can it be a problem with the cable?
Only thing I hadn't tried was a factory reset. So, I sucked it up and tried that. Nope. No change. At this point I'm wondering if it's a hardware problem, not a software problem.
I'm out of ideas. Anybody else?
Well you can always root it, install ROM manager from the market, install clockwork recovery, download the ROM you want to install in flashable .zip format from your phone and flash away. A new ROM might fix your USB issue.
If you don't want to root it, see if you can get into download mode, and flash a new ROM using Odin. I would check with a different cable first, just to be sure that's not the problem though. It might save you some headaches.
If it was me, I would just root it and load a custom 2.2 ROM. I would also get Titanium Backup from the market and backup my apps and would do a nandroid backup from recovery before flashing anything new just to be on the safe side.
There's some good info on how to do most of that in this sticky post.
http://forum.xda-developers.com/showthread.php?t=849028
I flashed a custom rom a couple of months back. That rom was android version 2.3.5.
Now when I try and connect my phone to my pc using the standard usb cable, it only charges but no connection.
I did some reading before I posted and found several methods to try out
1.Use kies, download drivers
2.Enable USB Debugging mode
3.Go to settings-wireless and network-usb utilities and connect it through there.
None of the methods mentioned above worked.
So my questions to you guys are
1. Does this problem have to do with the custom rom?
2. Can I degrade to the stock rom without the use of an USB cable?
2b Can I update to another custom rom (because the phone charges when it is connected to the pc, even though I cant see it on "my computer", it should still be considered as connected?) ?
3. Which is the best custom rom out right now (Speed and performance wise)
*Side note - I know people prefer different custom roms based on their taste, but I really want to think what you guys think about which one I should upgrade to!!! I also might want to overclock to 1.6 and root the phone in the coming week if I can solve my usb problem!
Have you tried using SwiFTP app on your phone and Filezilla on your pc, then you can transfer files wirelessly
killall said:
Have you tried using SwiFTP app on your phone and Filezilla on your pc, then you can transfer files wirelessly
Click to expand...
Click to collapse
Yes I have but it wasn't what I was looking for. My phone randomly gets usb connected and starts charging without the cable being connected???
I went to the retail store I bought it from and he said you should degrade your firmware and see if the problem goes away, if it doesnt we send it in for repair.
But how can I do that if my usb only charges when I connect to the pc?
There is a Mobile Odin apk. Perhaps you could install that then flash stock firmware with it. You would have to get the .tar onto your phone though.
Unfortunately, if I´m not wrong your trobule seems to be a hardward issue.
My cell phone began a couple of weeks ago with the same problem, and it became even rather serious. Some days ago it didn´t charged if I connected the charger when it was on. I should switch it off and then connect the charger, having done this, the cell rebooted by itsefl and then began charging.
But, just seeking and testing I bought a "charger block replacement" in ebay and replaced it by myself. It is not complex to do it on your own... today I am happyy.. cause I fixed it..
If your problem continue.. I hope you will remember my words!
Hey guys just wanted to say thanks for all the help you provide on a daily basis, for all the people trying to unlock the potential in their phones. However with that being said I might have tried too hard and messed up my phones. I have a Samsung Vibrant SGH-T595 with 2.1 (update 1) updated officially by Samsung.
I rooted the phone, used clock work recovery mod and then downloaded and installed cyanogenmod 7.1 RC. However in the end I did not like so I tried to go back using my backed up copy created by clockwork mod. Doing this has now what you would call "soft bricked" my phone.
The phone is currently stuck on the Samsung boot screen when trying to power on the device. I am unable to put it into download mode via the three button setup, but I bought a USB jig and it sets it into download mode.
Everything seems great at this point but the Odin program is unable to recognize my phone. I have downloaded the official Samsung Kies, and 64 bit drivers as well for my windows 7 system but it is unable to detect my phone. I believe it maybe a defective USB issue with this phone but not sure since it can be charged through USB but I can't remember the last time I was able to connect it to the PC and transfer files via the USB cable.
My question is what else can I do other then sell it for scrap?
Try another USB cable and different ports. It will recognize it eventually.
As you have a windows 7 x64 bit version i guess Odin may need to be opened by giving Administrator permissions.
Try right clicking odin and click Run as administrator. I guess this should work.
Ran into this issue last night with my wife's Nook Color and moving some file and driver issues. Guess what? It was a bad cord. Actually used my Vibrant cord and it was instantly recognized. Yes sometimes it IS actually THAT simple.
I also suggest you go to the Dev section and download the AIO Toolbox (links are live again and don't forget the .Net files too). Uninstall the drivers you have installed and run to toolbox. It has all the correct drivers, pit/tar files and Odin. It is an invaluable tool.
Sidenote: Kies is notorious for hardbricking devices. You should stay away from it altogether.
Woodrube said:
Sidenote: Kies is notorious for hardbricking devices. You should stay away from it altogether.
Click to expand...
Click to collapse
Exactly. And that is how i tried updating my vibrant to froyo and ended up hard bricking it..
Yeah like someone in here said, download aio vibrant toolkit.. its a surefire way to know your drivers are good and right.. once youve ruled them out, try a diff usb port and cable (mentioned above as well). If nothing works, then you may begin to entertain the idea that your phone is in difficult position.
Probably not hardbricked tho, vibrants are very resilient; just keep trying.
Then ttheres jtag and unbrickable mod if youre absolutely sure lifes over
Sent from a cell tower to the XDA server to you.
Thanks guys I ended up recycling my phones cause nothing I did worked. I did try AIO toolbox got the drivers, tried different cables. My SG II is able to be recognized by odin 1.85 with no issues but not my vibrant. I believe it is an issue with the vibrant's usb port. I originally rooted it by doing the update.zip fix from its external sd card, did not use my usb cable at that time. My other vibrant is completely hard bricked since it wont power on with two different fully charged batteries. Anyway thanks again and next time I will research more before modding my phones.
Hey OP,
I did the same exact thing as you and soft bricked it in the same manner. Then when I tried to get Odin to recognize the phone it wouldn't with my Samsung cable. I thought I was out of luck but I went and bought a USB cable made my Belkin from Meijer and Odin recognized it! I looked at the Samsung cable and the Belkin cable and the black plastic inside the microUSB in the Belkin is thicker than the Samsung. I think that helps create a tighter contact between phone microUSB and the cable. I thought I was screwed like you and I fixed the issue with a new cable!! That simple
I used the Samsung Galaxy S II usb cable which looks like it has a very tight connection with the contacts like you said. Thanks anyway I will try that brand of cable, if I ever run into that issue.
Hey guys, well my note got thrown into a puddle last may. Everything has been working fine up until now. Two weeks ago my computer was recognizing my note just fine. In the last couple of days I've been trying to figure out why my computer isn't recognizing my phone.
So far I have:
-Uninstalled/reinstalled USB drivers
-Troubleshooted kies to see if that would recognize my phone
-Started up droid explorer to see if that would recognize it either.
-Have disabled/enabled usb debugging to see if that made a difference.
Is there anything left I can do to determine if it's a hardware issue or not? The phone charges just fine.
I've been paying warranty monthly.
If it's indeed a hardware issue, how am I supposed to revert from my custom rom back to stock and remove personal files without usb?
Thanks for the input everyone.
tonomon said:
Hey guys, well my note got thrown into a puddle last may. Everything has been working fine up until now. Two weeks ago my computer was recognizing my note just fine. In the last couple of days I've been trying to figure out why my computer isn't recognizing my phone.
So far I have:
-Uninstalled/reinstalled USB drivers
-Troubleshooted kies to see if that would recognize my phone
-Started up droid explorer to see if that would recognize it either.
-Have disabled/enabled usb debugging to see if that made a difference.
Is there anything left I can do to determine if it's a hardware issue or not? The phone charges just fine.
I've been paying warranty monthly.
If it's indeed a hardware issue, how am I supposed to revert from my custom rom back to stock and remove personal files without usb?
Thanks for the input everyone.
Click to expand...
Click to collapse
Have you tried a new "factory" cable ??
That is the next place to look..IMHO...g
tonomon said:
Hey guys, well my note got thrown into a puddle last may. Everything has been working fine up until now. Two weeks ago my computer was recognizing my note just fine. In the last couple of days I've been trying to figure out why my computer isn't recognizing my phone.
So far I have:
-Uninstalled/reinstalled USB drivers
-Troubleshooted kies to see if that would recognize my phone
-Started up droid explorer to see if that would recognize it either.
-Have disabled/enabled usb debugging to see if that made a difference.
Is there anything left I can do to determine if it's a hardware issue or not? The phone charges just fine.
I've been paying warranty monthly.
If it's indeed a hardware issue, how am I supposed to revert from my custom rom back to stock and remove personal files without usb?
Thanks for the input everyone.
Click to expand...
Click to collapse
Have you tried Kies whilst your Note is in recovery and download mode?
If not...
If I recall correctly, the stock recovery has an OTA firmware install option.
If I am right, you can use a WiFi FTP connection, Dropbox, Google Drive, Skydrive, Box, etc to get the CWM/TWRP installable stock recovery package onto your phone, flash that, then restore to stock firmware via the OTA option.
Hi guys I'm having an issue with my GS2 i9100 after installing Cyanogenmod 10.2 using the installer on their site, I thought everything was great until i realised for some reason my phone refuses to display its storage on my windows PC, I've tried changing the different modes in the storage settings on the phone, such as MTP/PTP/Mass Storage and i've tried uninstalling and reinstalling the samsung usb driver via Kies but I still can't get it to work, is there an option I'm missing out here or is the rom at fault?
It charges perfectly fine but I am not getting any kind of prompt from either the phone or PC to activate the storage so I can copy files too/from it, it's getting quite annoying as their is alot of music/pictures/videos I want to put on the phone.
Clean install of stock to test before anything else.
MistahBungle said:
Clean install of stock to test before anything else.
Click to expand...
Click to collapse
Would it be safe to flash the stock rom using CWM6 recovery? as any tool that relies on a USB connection to the phone won't work.
Wanam has a thread in one of the Development sections with CWM flashable stock roms. I'd also be testing it with another PC to rule in/out something PC-side (if you haven't done so already). You need to be methodical with stuff like this - try stuff that rules in/out different causes.
Edit - You could also just take the punt it is the USB board in the phone on the fritz & replace it regardless, which is very cheap & easy to do if you're somewhat handy. KeithRoss39 has a guide in General (search for 'Replacing USB charger board') which has all the info you need if you decide to do this (will cost you a tenner).
In trying the things I've mentioned so far, that's what we're trying to ascertain; whether the board is faulty or not (common S2 fault, almost always shows a few faults but works OK in other ways). Put it this way, if you try those things I've suggested and you're still seeing the same, it's almost certainly the USB board.
In the meantime, use WiFi to get stuff off/on the phone if you need to (plenty of apps on GP enable this if you've never used it).
Sorry for the incredibly late reply, I've changed phones since, but I wanted to update this thread anyway, it turns out re-flashing cyanogenmod after replacing the pcb fixed the issue completely, installing it when i had the dodgy usb pcb must have made it not properly install the USB drivers or something