Okay. Hi guys.
I'm having some horrible USB connection problems and I've no idea whether they are hardware/software. I'm leaning towards the former.
About a month ago I noticed while plugged into my charger, my phone wasn't charging. Wiggling the cable did little, if anything to help. But it only happened that one day, and after a few beeps and boops of connections coming and going, it had seemed to have fixed itself.
Yesterday I decided to upgrade from XtreStoLite KitKat to XtreStoLite Lollipop. I made a bit of a mess of it and accidentally wiped my entire OS/cache/data before even putting the ROM on the sdcard directory. Fortunately I had already upgraded the modem/bootloader and was able to sideload the ROM.
I say I was able to sideload the ROM successfully, but this is really where the issues started to resurface. The first dozen or so times I tried to sideload I got "ADB not recognized" errors in CMD. I tried all sorts of USB driver re-installations, and installing google USB drivers from the Android SDK etc and nothing was working. Lots of beeps and boops of drivers installing and USB connections being made. In a last ditch attempt, I went back to CMD and once again typed "sideload adb rom.exe" and by some random miracle it worked. But that was the LAST time. I tried again later and got the same error as previously.
Anyway... new ROM installed. I ran through the set-up process and plugged my phone in to transfer over the add-on pack so I could re-activate Samsung Kies connections in order to restore my apps/photos etc.
*B-beep-b-b-b-eep-boop-b-beep* The phone was wildly connecting and disconnecting. I unplug it, blow into the USB connector - try to see any bent pins, but can't see anything. After a few tries I get it to connect long enough for me to transfer the file. Kies reinstalled. Throughout this WHOLE process there has been FAR too many disconnects.
If I DO get my phone to connect - Kies is stuck eternally on "connecting". I have a feeling MTP mode is just broken - as NOTHING shows up in My Computer when in that mode. Odin 3.09 no longer sees my phone at all, and when I connect in Camera mode NONE of the .zip files I placed in the sdcard directory show in Windows at all. But they ARE there, as I can still install from .zip in recovery.
The phone seems to work fine. But I want to restore my Kies backup, add/remove the .zips in the main sdcard directory, and see my phone in Odin.
Please help me. I am scared.
Related
So I had my phone rooted, and removed some of the ATT apps using instructions from here: http://androidforums.com/samsung-captivate/124736-t-bloatware-getting-your-way-delete-some.html
After doing all this, the phone still worked fine, but as of today I can't seem to connect via USB. ADB doesn't see the phone, and even if I disable USB debugging and attempt to just connect as mass storage, the drives don't show up in my computer like they used to.
I attempted a windows rollback to just before I installed the drivers, then reconnected the phone, but I did not get any message about unknown devices, and the phone doesn't seem to be in my device manager.
Can anyone help me out here?
Edit: Running Windows 7 x64
you erased something you werent supposed to. dl the dump posted here & move it to an Micro SD. Put it in your phone and use a program to move it from external to internal memory then load back all the apps you deleted.
If I had deleted something, shouldn't USB connectivity have died right after I did that, and not after a night of doing nothing with the phone?
Either way, How exactly would I go about restoring from that stock dump that was posted?
Mine is doing the same thing. Had a hard time with the windows 7 drivers to begin with though.
I am going back to XP when I get home. Will see if it will recognize it then.
Sent from my SAMSUNG-SGH-I897 using XDA App
Hm, an update on my situation: 3g watchdog died on me a couple times (gave me the popup, asked me to force close), so I decided to reboot the phone, and now everything works like it used to. I had also restarted my PC since the last time I tried (and failed) to connect over USB.
So if anyone else is having similar problems, I guess try rebooting both the phone and your computer.
I'm going to be keeping a copy of that "Rooted Stock System Restore" update.zip on my phone from now on, just in case.
The first Captivate I got from AT&T did the exact same thing right out of the box. I actually had to return it for another unit. Hopefully that was just a freak thing though.
I had a similar issue with windows 7 when I was first trying to connect via usb. Not sure if this will work for you, but I had to plug it into my rear port, the front ones didn't work just for the captivate.
Sent from my SAMSUNG-SGH-I897 using XDA App
it seems im having the same probs too i removed the att stock apps that were in one of the posts, im downloading samsung kies atm to see if that will help...
Edit, it did...windows and ADB redetected it.
I also rooted my Captivate and removed all of the AT&T crap. USB connection is still working fine under Windows 7 x64. Didn't install Kies or drivers either.
Halleleujah!
I had the same problem. Got this file from Samsung, and it worked on my Win7Ultimate 64 bit machine.
Try making sure you are back to touch wiz and see if it works... Worked for me.
I had some issues trying to get my phone to connect also ...
Windows Vista64 Ult.
Initially the MTP driver would hang when the phone was connected, and then eventually it would indicate that the installation was successful, then it would re-install itself after about 5 minutes. This was an endless loop which was severely draining of my system resources causing other applications to hang as well. I removed the drivers and ...
I downloaded the USB drivers from Samsung and installed them, when I connected the phone the computer did not recognize it, nor did the display on the phone indicate that it was plugged in. I tried several different USB ports.
I then changed the mode to mass storage and the phone was recognized, but both the internal and my secondary memory cards displayed 0 bytes free of 0 bytes available.
I downloaded the UK version of Kies, this was an utter waste of time. The Kies utility was not able to connect to the phone at all. I mass storage mode Kies displays an alert that it is not compatible, and the same goes for media player mode. If left in Kies mode the phone displays "connected", but the Kies utility just displays "connecting" and never progresses. Uninstalled Kies, and re-installed the Samsung driver ...
Connected the phone in Media Player mode, which is allowing me to access both memory locations without difficulty. Though windows pisses me off every time I connect the phone because it wants to sync windows media center with the phone ... though this is easily ignored.
Has anyone gotten the Kies utility to work with the captivate?
Battlehymn said:
I downloaded the UK version of Kies, this was an utter waste of time. [...]
Has anyone gotten the Kies utility to work with the captivate?
Click to expand...
Click to collapse
Try the Canada version, that's been working great for me, in Kies mode and all.
I had the similar kind of issue, look for the thread with ODIN and windows drivers, that is what worked for me...
Ever since I rooted I can not get my Epic to connect to a computer period. I'm about to give up and just deal with what I got, hopefully someone can tell me what I'm doing wrong. Before anyone decides to be a smart ass I have used the search function literally for days and have tried tons of things recommended with no result. I am the first to admit I'm an idiot when it comes to anything involving computers but I'm pretty determained to learn.
This has to be the phone because I have tried to connect to 2 desktops (1 running Windows 00 and 1 running the most updated Ubuntu), and 3 laptops (Windows xp, Windows Vista and Ubuntu). When I rooted I used the Vista computer and connected fine (can't anymore). I didn't have the space on the C drive to install the Android SDK so I switched to Ubuntu (first time user btw lol). Somehow when I was backing my SD card I lost any access to it or the notification bar. I never got my SD back til I rebooted but I haven't been able to connect to any PC since. When I charge (even in the car) it always tries to stay in mass storage mode. I basically charge in my car with my phone off hoping it will just charge and not mount my sd card to my car or wall lol. Yes I wiped 3 times, partitioned sd, tried several different cables (but my husband used mine and no problems on his Motorola) I'm sure I've done something wrong when I rooted or mounted to Ubuntu.
I also can't use adb. I followed the directions to the t (a few times lol) but when I run any commands it says "no such file or directory" I didn't have adb on the windows pc when I di noobnl's one click so I never ran the (adb shell ect) commands. I now can't do jack. I am now running noobnl's DI18 ROM with modem.bin flashed thru Clockworkmod.
I have tried all the basics you will find wit 2 days of web search.
My goal is DK28 (dream on Erica lol)...Thanks for any help and for anyone sparing me a lashing ;-)
Sent from my SPH-D700 using Tapatalk
When you plug in on your windows pcs...in Device manager..do you see anything appear? also do you have USB debugging on the phone?
USB debugging on?
Have you tried reinstalling the drivers for the Epic?
Rebooted phone and PC? (Sometimes it helps)
Used Odin?
Something might have been screwed up during one of your downloads, bad file maybe. Try reinstalling your drivers first, use Odin (phone must be in download mode), and see if it recognizes te device. If it does then Odin the stock .tar file and go from there. It'll give you a fresh start.
That's all I can think of right now.
Sent from my SPH-D700 using XDA App
I bet your USB debugging is on since most root's requier it. Even tho it says connect to pc if usb debugging is on it wont connect to my windows 7 box
I would suggest, if you're really having this many issues, just boot into download mode (1 on the keyboard + power button) and odin back to di18.
Just for kicks have you tried Settings > Privacy > Factory data reset? I assume that wiping does the same thing if not more but it's worth it to see if it somehow resets a setting that might be the issue.
What's left - software issue or Hardware issue.
Software:
hmmm...yeah gotta try connecting through Odin which uses downloader mode instead of USB modes...
Can Odin see your phone? Run Odin as admin with antivirus off, and proper samsung drivers installed. Then boot phone holding down 1 key into downloader mode. Connect to computer through USB port on back of computer (i.e. directly to motherboard) - does Odin identify something attached to USB port?
Yes - flash the dk28!
No - with Odin still on, unplug the USB cable, pause, and reconnect it. Still No? Try a different USB port on computer. Also try uninstalling and reinstalling the drivers - be sure to reboot the PC. If still No, then try on another computer, and as you did before, try different cables. Still No?? --> hardware problem with phone.
Hardware problem with phone: Look at the usb port in the phone - is there any junk in there that might interefere with the connection?
Yes - clean it out
No: phone perhaps internally damaged:
Solution for hardware damage:
You and husband clean up and go to sprint store.
At store - tech will know phone is rooted, so:
--Tech more likely to like you? You handle it, maybe even blame husband. Husband can silently attend and look sheepish, playing the part of 'me man, me dominate environment, me break fancy tech of wife, me sorry." Try to get free replacement phone while simultaneously promising never to let your husband root the phone again, or even touch it.
--Tech more likely to like husband? He goes alone, cops to the true story of how you rooted it and then was backing stuff up when it suddenly stopped working [truth from men? so sincere!]. Try to get free replacement phone while simultaneously promising not to let you in the house should you even attempt to root again.
P.S. forgot to add you might turn off the PCs firewall while testing, as well.
quik99 said:
I bet your USB debugging is on since most root's requier it. Even tho it says connect to pc if usb debugging is on it wont connect to my windows 7 box
Click to expand...
Click to collapse
same here. I tried out the free tethering app the other day and with usb debugging on i coudl never get it to install the proper drivers. Without it on and the 64bit drivers installed Odin worked just fine.
I have seen many Galaxy S devices not connect to a computer because of a faulty USB cable. Had my girlfriends sister switch out 3 Vibrants only to accidentally try and connect it to a laptop with a different USB cable and I've seen two others not connect with the stock Samsung USB cable.
How I fixed the tethering issue
I've had the same problem with my galaxy s - connecting to the PC (Win7 32bit) just doesn't do anything. As a test, I had a friend with the same phone/rom (froyo, rooted) connect - and he was able to! It installed the drivers and it just worked. He disconnected, I connected, and now it's fine.
So, see if you can find someone with the same phone and see if they can connect. Makes no sense to me, but it worked.
I've had my Epic fail to mount before. Interestingly any time I had an issue it was with a Mac - it always mounts on a PC. I'll stop now before I open up a can of worms.
Best advice I have is get a Dropbox account. You can use that guy to move files from a computer to the SD card without having to mount to the computer. Perhaps you can get a factory ROM (with root of course) on your phone that way?
You can get a app from the market called SWIFTP (free) & connect to your sdcard via ftp server. This can be a temporary fix till you get your connection error resolved.
I have 1 USB port on my laptop that the Epic shows up as "unknown device" on. Works on every other port, and everything else works just fine on the same port. The factory USB cable is finicky!
A couple of weeks ago my N4 decided that it didn't want connect to my computer. I tried windows xp, 7, and osx. I tried 5 different usb cables that worked with other android phones just fine. I tried all usb ports on said computers. I've uninstalled and re-installed all drivers, using all the known methods. Then I noticed that I was getting terrible battery life. Like 5% gone in 20 minutes with all radios turned off and leaving it in my pocket. I was on the latest verison of PA with the latest verion of franco.kernel and I've had no previous problems with my phone.
So I thought maybe I did something to it like a bad flash, so i downloaded a stock 4.2.2 zip and flashed it (with gapps). The problem persisted. So I proceeded to wipe the phone in cwm in an act of desperation, and lo and behole I was then stuck with the same problem as before, but this time with no working os to boot to, and no way of connecting it to fastboot or adb in order to put any files on the sdcard/ flash it back to stock. I am, however, still able to boot into cwm and the bootloader. Then, thinking it might be a problem with the usb daughter board as whenever I tried to plug my phone into a computer it gave me this:"windows has stopped this device because it has reported problems. (code 43)", I ordered a replacement. Replacement came, I swapped them out, and absolutely nothing has changed. I tried uninstalling/deleting drivers and re-installing them just to make sure, but same results as before. Also, the N4 DOES charge when plugged into a power source like normal.
So the way I see it, I can either keep trying to replace parts, or one of you wonderful people know some crazy fix to my problem. If not, then I could go the other way, and attempt to brick the N4 even further in order to get it replaced (I.e. it's not possible to see whether or not it's unlocked/has a custom recovery). Also, I can enter "download mode" by holding down the volume buttons and connecting a usb cable, but windows still doesn't recognize the device.
Guys could anyone help me?
My phone is Samsung A8 variant A800i non-rooted and already 6.0.1.
Eversince I upgraded to MM thru ODIN I am encountering an error in my OTG as in it won't read any disk... the only resort to make the otg work again is to reflash my phone. However during the most recent otg failure, a "USBsettings has stopped" was shown. I factory reset my phone but still this notification appears everytime I start my phone. So when I decided to reflash my phone, I was shocked that my laptop only charges my phone. It can't even detect my files thru mtp connection.
I tried the following and my laptop still can't detect my phone:
1. At the Developers Option I tried to switch the USB Configuration from MTP to Charging to MTP and various other switching, while connected and unconnected to laptop.
2. Dialled *#0808# to reset USBsettings but I am only getting "USBsettings" has stopped.
3. I reinstalled the USBsettings.apk from the system folder (via total commander).
4. I have installed USBsettings.apk taken from another phone.
By the way before I tried the above methods I have already eliminated the cable and pc problems since using the same cable and laptop, I can connect my other samsung phone thru mtp and is detected by odin. I have also tried various other desktop on Windows 7 and 10 but still the same problem: these only charges my phone.
Moreover, there is no abnormality in my charging time eversince this happened.
Hope someone could help me make this work again.
Thank You.
So I plugged my phone in this morning to my work computer, to copy some files on to it, and the whole mtp storage thing didn't pop up. No sound or anything. I set it to MTP in developer options, still nothing. So I tried it on my laptop, same thing. Then went and borrowed another usb c cable from a coworker. Tried it on all the machines and still nothing. So I ran around the office trying it on every windows pc I could find. I stopped after it didn't work on the 7th.
So I am running LOS so I updated to the latest nightly. Still nothing. So I boot into recovery to back everything up and to flash stock. But I remember you can mount MTP from within TWRP. So I tried that and it still didn't work. Then I tried ADB while in recovery and THAT didn't work. Booted back into OS and tried ADB and it didn't work (this was working earlier this week). Tried this all on redundant pcs and cables. Not one machine made the sound you usually hear when you plug something into it. So I cancelled the back up and booted fastboot. THAT WORKS!
What do you guys think? Has anyone ever seen this behavior?
This is currently my 3rd Axon. I am not sheepish about getting this thing back to stock to do the warranty, as I've done it 2 times. Both times were hardware issues.
TL;DR My phone will not work when connected to any windows pc. I've tried MTP storage and adb. The PC doesn't even register that something was plugged in. Tried multiple cables/pcs. FASTBOOT DOES WORK HOWEVER.