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.
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
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.
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.
Hello forums,
I've done a lot of searching but can't seem to find someone with my combo of problems. Awesome.
So here's my set up.
Samsung Galaxy Tab 10.1
CM9 2012 06 13 Nightly
Windows 7
I want to update to the stock ICS offered from Samsung. I originally had 3.2 HC and couldn't wait for the Canadian update to roll around so I went CM. But I've been stuck on CM9 Since. Now I have several problems that make it impossible for me to update. Any help would be much appreciated.
1. ODIN and PC will NOT detect the tablet when connected via USB. I get a USB not recognized. MTP is enabled. This means I cannot ODIN flash.
2. I can't find a Canadian ODIN Flashable-build. I'd have to use the US one. That has it's own slew of political problems.
3. CWM will not mount my SD card. I have a CWM Backup with ICS (Someone else uploaded it) saved in CWM's backup dir. but I cannot restore it since CWM 5.5.1.4 will not mount the SD.
I've literally been doing this on and off for about 2 months now and I could really use some help. Any suggestions would be greatly appreciated.
I could care less if the whole thing were wiped clean if it means I can start using the cameras again.
Thank you.
NitesWhisper said:
1. ODIN and PC will NOT detect the tablet when connected via USB. I get a USB not recognized. MTP is enabled. This means I cannot ODIN flash.
Click to expand...
Click to collapse
When you view the tablet in Device Manager, what does it say? What specific error do you get when you plug it in?
Some of the cheap cables are poorly constructed to the point where just normal flexing of the cable breaks the wires going to the connector. If you lose one of the USB transmit/receive wires, the cable will still allow you to charge, but the OS won't recognize the device.
If you know the cable's good, try reinstalling the drivers.
I bought this Note 2 about a month ago and got unlocked and rooted pretty easy... So I'm Currently on liquid smooth v2.3 4.2.2 vrall4. I was attempting to flash back to stock but each time I connect phone to computer in download I get no "ID:COM" number showing connectivity with the device. My first smartphone was original Samsung Galaxy so I'm slightly familiar with this flash back to stock, too bad there is no one click recovery restore tool but anyways. I'm not sure what I did but I believe I have accidentally deleted a wrong folder. Phone still works perfectly except that it doesn't seem to want to flash ROMs from the Original Android Dev section of this phone's forum... such as Paranoid's 3.5x.
also it will not connect to computer as media device...only as camera. phone notifies me it is connecting as media device, but it does not appear in my computer. it won't even allow me to put zips on the internal storage.
bunnsguy said:
I bought this Note 2 about a month ago and got unlocked and rooted pretty easy... So I'm Currently on liquid smooth v2.3 4.2.2 vrall4. I was attempting to flash back to stock but each time I connect phone to computer in download I get no "ID:COM" number showing connectivity with the device. My first smartphone was original Samsung Galaxy so I'm slightly familiar with this flash back to stock, too bad there is no one click recovery restore tool but anyways. I'm not sure what I did but I believe I have accidentally deleted a wrong folder. Phone still works perfectly except that it doesn't seem to want to flash ROMs from the Original Android Dev section of this phone's forum... such as Paranoid's 3.5x.
also it will not connect to computer as media device...only as camera. phone notifies me it is connecting as media device, but it does not appear in my computer. it won't even allow me to put zips on the internal storage.
Click to expand...
Click to collapse
I've noticed this problem also after the update. C3 seems to be the culprit. Flash back to a stock rooted 4.1.1 rom and set radios back. Install Kies (again) and then you can keep or uinstall kies. This worked for me. The 4.1.2 update for some reason will not play nice with the drivers. Will only let me connect as camera on both windows and Ubuntu 13.04. Thats what led me to down grade and try again.
Also, it seemed that my phone got "stuck" in PTP for some reason after all that. Once i got it to work again. I was able to connect back to Ubuntu 13.04 in MTP mode using a new 4.1.2 rom. (this for those trying to figure out how to get MTP to work on Linux boxes after update. Use a computer to set phone back to MTP, and Linux will recognize it again.) If windows jogs the phone to PTP, for some reason it will not go back until you fix that on windows. Not a science, just what i've experienced in the last 2 weeks.
each time I connect phone to computer using odin in download I get no "ID:COM" number showing connectivity with the device
Sounds to me that your drivers arent installed. Youll need to update your drivers on your computer. That is what I do if odin is not seeing my device.
Sent from my SCH-I605 using xda premium
joeriv5692 said:
Sounds to me that your drivers arent installed. Youll need to update your drivers on your computer. That is what I do if odin is not seeing my device.
Click to expand...
Click to collapse
ive only tried this 10 times so far and no worky