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
Posted this on the general discussion section but have had no replies, hopefully someone here can help?
Hi everyone, first, this is my first post, new to the forums, at least as a registered user. I have a problem with my phone. I know most of you are wondering why I have not just read the other posts on the forums, but I have. I have attempted every solution to the problem posted previously.
Background: Phone: Samsung charge.
I was being impatient and did not want to wait for the gingerbread update form Verizon. I flashed the leaked gingerbread 2.3.4 onto my phone using odin. Everything went great. I was able to use my phone with no problems except shortened battery life, but nothing major. About a month ago the battery life was impossible to maintain and there were some software bugs, like clicks during calls, startup taking forever, around 2 minutes on average!, and random restarts that never happened before. I decided to look up some fixes and found that verizon and samsung had released GB 2.3.6 for the charge. I got excited and decided I wanted to get that, but I could not via OTA. I read some forum posts and they mentioned attempting a factory reset on the phone then trying OTA update. I went ahead with factory reset and everything went fine. My startup time is around 25 seconds now and no random clicks or gliches, but still not on 2.3.6, which was the whole point. I then decided to just flash the stock 2.3.6 rom to the phone.
Problem: When I plug my phone in to multiple computers it will charge but not connect to the computer. This means on my Mac it does not show as an external drive, which it has in the past. On my windows 7 machine it says that drivers were installed but could not be used (I can get the exact quote if needed.) I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device". I have tried to enter download mode when hooked up to windows computers and no connection is found.
Possible solutions attempted and their outcomes:
1. As stated, I attempted the method shown in a thread on droid forums for installing the samsung drivers. I have attempted multiple times to install the drivers on my windows machine and the device remains "unknown".
2. I have attempted multiple cables on multiple computers, both mac and windows 7. No change.
3. I have installed adb and attempted to locate devices using adb devices command on mac. No devices found.
4. I have attempted all methods with both usb debugging checked and unchecked.
5. I have tried every possible usb port I have.
Ideas/questions I have had that I have no idea are possible or how to fix!
Would a factory reset take away the ability to connect to a computer from my phone. So, is there a piece of software in the build I have that controls the connection between the computer and the phone, an identifier of sorts, which is now missing, now that I have reset the leaked ROM.
Is there a way to flash a new ROM without connecting to a computer, via the sd card, and what is that? I have read some things in other posts but am too much of a n00b to understand most of them when using sdcards.
ANY help will be greatly appreciated. PLEASE PLEASE PLEASE!!! I have been at this for at least 6 hours, sifting through forums, searching google, attempting fixes that others have stated worked for them, only to fail every time. Thank you all.
have you try on a different pc?
maybe on your PC there is some problem with the drivers.
Moreover to connect via
adb u must enable Debug mode on your device in the application menu.
To flash kernel or other directly from your sd you can use the clockwordmode, but to install it you must before
install it and i fear you must use your cable connection
Sent from my GT-I9100 using XDA App
I have tried multiple PCs and a mac, even windows on bootcamp. I have installed drivers on every one, even uninstalled and reinstalled on one. One PC, my laptop was a fresh windows install (it was a linux box but I needed windows to use Odin). I was in debug mode and not in debug mode when attempting adb. Thanks for the suggestions though. As I said, I have tried numerous things and am completely stuck! so frustrating!
"I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device"
Exactly there... you can try to force device to install a different driver.
Double click the unknown device then driver then update driver then find software in your computer then choose manually from a list of device drivers in your computer then show all devices you should see "android adb interface" or something related to google or android.
Try it... i hope this can help you.
Hey.... A friend of mine has a problem. She has a Galaxy S2 and it is stuck in an endless boot loop. She said it's running a stock rom and nothing funny was done to that phone. Being the nice person I am, I said "sure, it's an easy fix...just have to reflash it". Well....not so easy.
I can get the phone into recovery mode, but there's nothing I'm able to do productive on there except wipe the user data, which I didn't want to do. I thought I could install CWM through it to back it up, but it only allows files that are on the internal sdcard, not the external one. Argh.
So, I put the phone into download mode, but the computer does not recognize the phone. I've installed Kies, uninstalled, reinstalled, etc. I am doing this on OSX that is running a virtual machine in parallels. On my S3, Parallels detects the phone being in download mode....on the S2, it does nothing. Odin doesn't recognize anything.
OK, next....try it on OSX with Heimdell. Did that, nothing. Tried Android SDK and did a adb detect, and it didn't find the phone. Tried it on Linux on another laptop. Linux at least recognized it in dmesg as a Samsung Phone when it is connected, but doesn't do anything else with Heimdell or Android SDK.
My next trick I might try the usb jig, but I'm not sure if it's going to get me anywhere if the phone will go into the download mode by me forcing it. Another oddity is that the phone shows it charging, but it doesn't charge. For example, the screen still shows the battery at the lowest level.
Before I break out the soldering iron, I was wondering if anybody had any suggestions. Who knows, the phone just may be fubar'ed.
What kinda S2 is it?
Sent from the little guy
Do you have samsung drivers installed on your computer?
You dont need a jig because you said the phone goes into download mode anyway.
Mistahbungle posted a checklist to do when your phones not recognized by pc.
Check his previous posts and see if that helps....
theunderling said:
You dont need a jig because you said the phone goes into download mode anyway.
Mistahbungle posted a checklist to do when your phones not recognized by pc.
Check his previous posts and see if that helps....
Click to expand...
Click to collapse
Yeah, I saw that list. Believe it or not, it's the usb port. I saw something later that said the usb port on these things can go bad. I've never ran into this before, but apparently, this is the problem.
After jiggling the connector around, I was able to reflash the stock on there, but unfortunately, it didn't fix the problem. I then put siyah on there and I was at least able to back everything up through CWM to the extsdcard.
So, I don't know if the flakey connector would prevent a boot, but who knows. I do know that it's not charging anymore and I can't get back into CWM, so maybe that was the last bit where I was able to get it backed up.
Hello,
I have a very big problem with my Samsung Galaxy S3 I9300.
The problem started when my battery ran down very very fast. I can use my phone for no longer than maybe 6 hours, and that is in stand by. If I want to charge my phone till it's completely full it might take two days on the charger as well, even when my phone is off. I tried to reset my phone to factory defaults, but that didn't fix the problem. I even bought a new battery, hoping that would solve the problem, but even no luck with that. The phone also becomes hot in the bottom. Now I wanted to bring it back to the store for warrenty but there lies the next problem, my phone is rooted.
I know it is possible to unroot the phone, and it's nog too hard to do. But every time I connect my phone with USB to my computer, my computer doesn't recognize it. I get the next error message "USB device not recognized". I tried different cables, I tried on an other computer, but still I get the same error. I also tried the S3 of a friend on my computer and with his phone I do get a connection. So I know there is nothing wrong with the drivers on my computer or something like that. There must be something wrong with my phone.
Now the problems won't stop here because there is even a third problem. Like I said before I have rooted my phone, but I can't use SuperUser. When I start SuperUser it says "The SU Binary needs to be updated. Continue?". Then when I press continue I get the message "Installation failed !". I can't use CWM as well. I wanted to use Triangle Away before bringing it back for warrenty, but I can't use it because I can't use SuperUser.
If some one would have an idea to unroot my phone without using USB so I can bring it in for warrenty. Or find a way to get my USB port running again, I think that would fix my problems.
I spend a few hours trying to fix these problems, but now I've come to a point I don't know what to do anymore, I hope anyone of you is willing to help me. I'll be for ever gratefull.
Grtz Nathan...
Hi.
If i was you, i would try to install a official version, using Odin.
Also, my advice is not to use the original charger, Even chinese have better one´s...
Did you install Kies and drivers on your PC? Check that too.
Consider install leaked 4.2.2 version of Rom, since it uses Odin to do it.
I hope i gave at least some clues....
Mord0rr said:
Hi.
If i was you, i would try to install a official version, using Odin.
Also, my advice is not to use the original charger, Even chinese have better one´s...
Did you install Kies and drivers on your PC? Check that too.
Consider install leaked 4.2.2 version of Rom, since it uses Odin to do it.
I hope i gave at least some clues....
Click to expand...
Click to collapse
Thanks for your reply,
I forgot to mention that I have the official ROM installed, I only rooted it. But even if I would want to install a new ROM, my computer doesn't recognize my phone throug USB. So I can't install a ROM using Odin unless my USB port is running again.
I tried several chargers already, I don't think the problem lies in the charger because the battery drains very fast when it's of the charger.
I did install Kies and drivers, I even uninstalled them and reinstalled them again a couple of times. I even tried it on different computers. And the Galaxy S3 of a friend of mine does make a connection. So I don't think the problem lies there.
droogje said:
Thanks for your reply,
I forgot to mention that I have the official ROM installed, I only rooted it. But even if I would want to install a new ROM, my computer doesn't recognize my phone throug USB. So I can't install a ROM using Odin unless my USB port is running again.
I tried several chargers already, I don't think the problem lies in the charger because the battery drains very fast when it's of the charger.
I did install Kies and drivers, I even uninstalled them and reinstalled them again a couple of times. I even tried it on different computers. And the Galaxy S3 of a friend of mine does make a connection. So I don't think the problem lies there.
Click to expand...
Click to collapse
Hummm....
Did you try hard reset? Definitely without USB recognition, you can`t go to next stage....
In setup did you check optinos like USB debugging?
At this moment im out of options....maybe a poweruser can help you better:highfive:
Mord0rr said:
Hummm....
Did you try hard reset? Definitely without USB recognition, you can`t go to next stage....
In setup did you check optinos like USB debugging?
At this moment im out of options....maybe a poweruser can help you better:highfive:
Click to expand...
Click to collapse
What exactly do you mean with hard reset? If you mean powering on with home button and volume up button pushed, and then select "wipe data/factory reset". Then yes, I tried that.
In setup I did check USB debugging. The thing is, when I power on with home button and volume down button, I enter download mode. But even in download mode my computer does not recognize my phone. I'm not sure, but I think the computer should.
I'm really stuck here :crying:
So... now that I think with hindsight, I did something pretty stupid, and I'm going to need some help, since I have no idea what to do.
I have a Nexus 9 tablet, and I never liked it. The OS is just so slow and laggy, and it overheats, and it has many other problems. Quite a couple of times, I installed custom ROM's and so on, and I never had a problem. Let me explain what I did now.
Around a month ago, while looking on the internet, I heard this thing that if I install the original software, but with no encryption, it would work better. It sounded cool at the time, so I downloaded the Nexus Root Toolkit, and did it.
Everything went well. But then I heard about a custom ROM that was apparently working even better, Dirty Unicorns, so using the same toolkit, I installed it. For the first time, my Nexus 9 actually worked the way it is supposed to work, but the custom ROM still had its problems, it crashed from time to time. I was thinking about possibly returning or selling the tablet, so that's why using the Toolkit, I reinstalled the original software. But, if I went all the steps, and also locked the OEM, my device then showed a flag saying that it was a development device, while booting up. So, after messing around with the settings of the Toolkit a little, I decided to reinstall the software, but leave the bootloader unlocked.
But after some time, I reinstalled my Windows, and I also reinstalled the Toolkit. But that's when I started to have problems. My tablet wouldn't connect to my laptop anymore. I used the toolkit and uninstalled drivers, reinstalling others quite a couple of times, and that's where I think that I messed something up. I managed to eventually connect my tablet, and I rooted it, after rooting it, I connected it again. But adb wasn't working for some reason. A little annoyed, I simply copy pasted the zip file of CM13 into my tablet's internal storage, and I rebooted it to the recovery, TWRP. But the recovery failed to flash it, saying something about an Error 7.
Now that I think about it, I was stupid, since after that, I performed a complete factory reset, resetting my TWRP backup too. I tried to connect it again, nothing. It didn't connect at all. I plug it in, my computer doesn't even recognize that something is plugged in. No Nexus 9, no Android Device, no anything. I booted it in fastboot mode, and it worked, my computer recognized it, and after I downloaded a ROM zip file again, I tried to connect the tablet back and flash it manually, but nothing. It didn't recognize anything anymore.
I tried to reinstall the drivers countless times. I deleted what I had, reinstalled it, nothing. I uninstalled and reinstalled the Toolkit. But strangely, now, even if I know that I installed the Google USB drivers, and the ADB drivers, as I even installed Android SDK, if I use USB Deview, it doesn't show me any of them. I can't see any Google or ADB drivers, although I tried installing them multiple times. So now, I'm stuck with a tablet with TWRP and no OS, which I can't connect to my PC, and I can't use ADB or fastboot.
Is it something from my laptop? I can't check to see if it will connect to another PC right now, so I don't know for sure. Is there any way to delete all the traces from my (failed) attempts at reinstalling the drivers, and to install them again properly? Or is it something from the tablet itself? I don't have an OS, so I can't enable USB debugging.
So, shortly, I have no idea what's happening. And I'm quite obviously a noob in all of these. Can anyone help me? Please?
If you boot into the bootloader and from a command prompt type fastboot devices you don't get anything?
Sent from my Nexus 9 using XDA-Developers mobile app
I still couldn't get ADB to work, but I managed to work out fastboot. It may be something from my USB cable, it works perfectly.
I flashed the original software back, and I'll go to check my cable, although I feel kinda stupid that I didn't think about that in the first place.
Thanks for the help anyway.
If fastboot is working and bootloader is unlocked, you can still install a factory image.
Depending of your device download for wifi Version:
https://dl.google.com/dl/android/aosp/volantis-mob30p-factory-2cb57a1b.tgz
If you habe the LTE variant:
https://dl.google.com/dl/android/aosp/volantisg-mob30p-factory-ae9ce05a.tgz
Extract the files and put them into the same directory link fastboot and execute the flash-all.bat
WARNING: Any data will be erased!!! Also TWRP
Now it should boot up with stock firmware.
If you want your device decrypted install twrp. format the internal storage and flash the pure nexus rom which i can highly recommend and is decrypted by default. Dont forget do flash gapps
my issue is same
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
rohanzakie said:
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
Click to expand...
Click to collapse
Use fastboot, not adb.
what if fastboot isn't working, either?
uberSkeptic said:
what if fastboot isn't working, either?
Click to expand...
Click to collapse
Is the tablet in fastboot mode?
madbat99 said:
Is the tablet in fastboot mode?
Click to expand...
Click to collapse
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
uberSkeptic said:
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Hi, uberSkeptic...
Just a quick thought... Have you tried a different USB cable?
Rgrds,
Ged.
Edit & Additional...
The command is not fastboot list devices... it's fastboot devices
One last point... Ensure your Nexus 9 is definitely booted into fastboot mode and not just HBOOT (the bootloader). Take a look at the two screenshots below - your Nexus 9 should look like the screenshot on the right, the one with my green explanatory text.
Apologies for the poor image quality; there's no way of taking a screenshot in the bootloader, so I had to take photographs instead.
Hope this helps and good luck.
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
uberSkeptic said:
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
Click to expand...
Click to collapse
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
GedBlake said:
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
Click to expand...
Click to collapse
Sadly, me too. I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Too bad, too - the tablet is otherwise in great condition and even has a custom-painted backplate (long story).
Thanks for trying to help, though!
uberSkeptic said:
...The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Mmm...
uberSkeptic said:
...I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Click to expand...
Click to collapse
Mmm... (scratches head, raises eyebrow quizzically)...
If I was Hercule Poirot and this was a murder case, and with all the suspects gathered in one room, prior to revealing a brilliant deduction... I'd be casting very dark glances in the direction of your Nexus 9's USB port right now as the likely culprit here.
Think about it. Different computers. Different USB cables. An OTG cable... And none of them work. What's the one thing they all have in common?
Answer: The USB port on the Nexus 9 itself, and where you've replaced the USB daughter-board.
Maybe, possibly, that replacement don't go so well. Maybe there's some unknown problem with it. I can't comment too much on this, 'cos it outside the scope of my knowledge - I'm a software guy; circuit boards and dismantling devices to fix 'em isn't something I'm comfortable with. I always think I'm going to damage something or rip a wire out somewhere, so I bow to your superior knowledge in this area, as I may be talking complete cobblers here. It certainly wouldn't be the first time.
Anyway... Sorry I wasn't able to help find a working solution for you. If anything occurs to me that might help, I'll be sure to let you know.
Rgrds,
Ged.
I would be suspect if the replacement as well if it weren't for the fact that I did it only AFTER the other symptoms/problems appeared. Hence the replacement (which is known good because the battery charges no problem). There cables and everything inside the tablet tests just fine... It feels like the firmware for USB is somehow corrupt or something.
Thanks for all the advice, though. ?
So I can't believe I didn't think of this before, but when I run "dmesg" from the terminal app included w/ TWRP, I see that there a TON of errors, mostly referencing problems accessing the recovery image. I could screenshot it, if anyone at all might be able to tell me a little more specifically what the dmesg log is trying to tell me...