Database Users

Help connecting Epic to pc (yes I used the search and my issue isn't resolved)

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!

Fix for adb not working because phone is stuck in "modem" mode

Just ran into a problem which took me some time to solve. Thought I would share it to save other people some frustration.
After an adb reboot the i5800 got stuck in "modem" mode. i.e. android booted fine but gave a modem and a serial port over usb rather than adb. Reboots did not solve the problem.
The solution is to enter recovery screen:
reboot recovery
OR
press proper buttons to get into recovery mode
And then perform a reboot from there

Is this the same as *#7284# and selecting "PDA" on UART and USB, or just on USB? Or is this a completely separate thing?

miki.antena said:
Is this the same as *#7284# and selecting "PDA" on UART and USB, or just on USB? Or is this a completely separate thing?
Click to expand...
Click to collapse
Thanks so much for this!!!! After helping hack a friends build.prop to enable Apparatus compatibility in the Market, I found USB wasn't working properly anymore. Resetting changes in the phone didn't help (I had to do this via the phone terminal) although I at least managed to buy Apparatus before the sale ended.
After initially getting confused due to a lack of drivers and the occasional 'nH' showing up devices without drivers which made me think something was borked, I worked out from the VID & PID it was just the lack of drivers making (well I'm not sure why it did the 'nH' sometimes it got serial something instead), once I installed the drivers all was fine.
Except still mass storage wasn't showing and the Samsung connect manager didn't show up on my phone when I connected USB, nor did ADB work at all. In fact, it didn't even show up in the phone menu as debugging mode if I didn't start phone with it connected (or something like that). Funnily enough when I did get it the debugging to show up I did get the USB mass storage to show up in the phone, but it didn't help (it just unmounted the card which I think is all it ever does).
Anyway after a bit more fooling around I eventuall came across http://forum.xda-developers.com/showthread.php?t=1215103 and the stuff about modem and mkasick's post which sounded a lot like it could be my problem. The code for that Samsung phone didn't work so I searched for the 5800 and came across this giving me the right code. Sure enough UART (but not USB) was set to modem instead of PDA. I was unsure whether that was wrong but changed it anyway and yep that fixed it!
I still have no idea what went wrong. I had thought may be the phone didn't like me rebooting via ADB but I've now done that several times. In fact most of the stuff except install a superuser update has been more or less repeated. I guess it was just some strange rare occurence that it somehow got changed. I did have to reconnect the USB while working the first time, not sure why but ADB lost connection then I found couldn't connect. Perhaps that's somehow related. Now that I know what to do, it's trivial but very annoying when I didn't. I still don't get why Samsung decided to make the connect manager (my phone doesn't have that) only to have some hidden option where it can be set to modem or USB.
Partially because of this, I never got to get Tilestorm HD become compatible in time for the sale although my friend wasn't so interested in that. (Eventually I worked out using the THC Tattoo modded market which reports a fake resolution enables it. Well, I also modified the build.prop but I don't know if that was necessary. I wasn't able to do it solely by the build.prop. But it was way too late by then to buy Tilestorm HD cheap.)

Nil Einne said:
I still have no idea what went wrong. I had thought may be the phone didn't like me rebooting via ADB but I've now done that several times.
Click to expand...
Click to collapse
This may sound like crazy idea, but is your USB port/connector clean?
(The USB port allows for dozens of different phone functions when using very specific resistance between data pins.)

i bought a LG D802 32gb last night as i was using a 16 gb before i wanted to flash cloudy g3.. so i tried to install custome recovery twrp...
now i am in fast boot mode..
it says :
[880]fastboot mode started
[910]udc_start()
when i attach usb cable
[1100]-reset-
[1110]-portchange-
[1120]-reset-
[1130]-portchange-
[1140]-fastboot: processing commands
i tried holding volume + and and attaching the usb cable but no luck ... so now i have NO RECOVERY, NO DOWNLOAD MODE, AND MY WINDOWS PICKING UP MY PHONE AS "USB MODEM PHONE ADB PORT"
please help

[Q] HELP with recovery, no usb access to nexus 7, not detecting with official cable.

Ok so long story short, i have a nexus 7 2012 which a rooted and installed cyanogen mod.
I was using it as a car install and works perfect, i'm using an otg cable to mount usb sticks, triggering soft shutdown and powering the nexus etc. So usb seems to be working fine.
Basically i removed the tablet it to modify the bootloader to turn on automatically with ac power applied, if the battery runs out i have to manually power on with button, but now i'm running into a problem.
Ever since taking the tablet out and trying to connect over usb, none of my computers detect the tablet.
I've tried different operating systems, drivers, cables etc etc.
Also changed from mtp to ptp in storage and also turned on usb debugging mode. If i connect an otg cable the nexus see's the otg and i can mount usb's etc.
So i thought i might try recover the nexus back to factory, maybe there was an issue with the rom corrupted etc, I've downloaded the original 4.2.2 firmware which is currently installed.
Booted into recovery and tried re-installing the 4.2.2 zip, it keeps aborting. A guy in work tried to use sideloader and connect via adb. no luck.
I'm not very familiar with the android platform so i've no other ideas what to do and other idea's how to recover now.
The guy i work with mentioned using a usb jig, would that be the way to go or can anyone else suggest some else that might help.
Thanks

Before you updated when was the last time you connected your N7 to your computer?
When you connect your N7 to your computer does it act like it is charging? Have you tried more than one computer? I had a similar problem with mine last year & sent it in 3 times. Asus replaced both the USB port board & the main board on different occassions. I suspect your mainboard might be faulty.

Does adb see the device

jadesse said:
Before you updated when was the last time you connected your N7 to your computer?
When you connect your N7 to your computer does it act like it is charging? Have you tried more than one computer? I had a similar problem with mine last year & sent it in 3 times. Asus replaced both the USB port board & the main board on different occassions. I suspect your mainboard might be faulty.
Click to expand...
Click to collapse
I last connected the nexus to the laptop a few monts back to load some music onto it, didn't have a problem. It's only been connected to a computer maybe 3 times. once to root/rom it then another few times to load music etc.
I can't see why the usb board maybe faulty as i can read data from a usb key when the otg cable is connected.
It's a strange one. You could be right, i might try pick up a broken nexus and swap some parts. Usb board etc.

crusrod said:
Does adb see the device
Click to expand...
Click to collapse
Yes adb is shown in device manager, but it's not recognizing the nexus, comes up with an error 10 , cannot start. etc etc

foster182 said:
Yes adb is shown in device manager, but it's not recognizing the nexus, comes up with an error 10 , cannot start. etc etc
Click to expand...
Click to collapse
I am having this same problem on my (unrooted) HTC One after attempting to "convert" it from an AT&T to a Google Play Edition device with the procedure described here.
As part of the procedure, I attempted to flash the stock Google Play Edition ROM using fastboot commands, but I got an error message. The instructions say to just try the flash again, but the phone no longer connects properly via USB (error 10) while in bootloader mode. While in bootloader mode, the phone indicates there is some sort of problem (a line showing the OS version is highlighted in red), and attempting to enter recovery mode does nothing but display a phone with a big red X in it. The phone seems to operate fine and responds to ADB commands when the phone is fully booted, albeit with the old OS (not Google Play Edition) still in place.
Any Android device could theoretically get in this state. We're sort of "paralyzed", because everything we want to do to regain control of the bootloader and fix the situation seems to require issuing fastboot commands from a computer connected to the phone while it's in bootloader mode. Yet entering recovery mode or getting a computer to connect to it via USB no longer seems possible.
I wonder if there's another way to issue fastboot commands without relying on the USB connection to a computer?

PC won't recognize Note 4

Have a note 4 on a custom rom- android kitkat. Was working fine, until i wiped data/cache a few times in TWRP recovery to do a clean install of the rom. Phone restarted without an OS, and then i couldn't get pass the boot logo screen. Couldn't flash any rom in recovery. So i did a restore thru TWRP from a backup. So now the phone boots, but it pc won't recognize it. Everytime i plug it, I get "One of the USB devices attached to your computer has malfunctioned, and Windows does not recognize it". Under device manager, I get "Unknown USB Device (device descriptor request failed)".
Things I have tried:
-Uninstalled usb drivers and let windows reinstall,
-at least 5 different usb cables
-at least 3 different Samsung oem usb cables
-other usb ports on the PC
-3 different pc (all with same- so im guessing its a problem with the phone)
-physically tried to push up the usb port on the phone- bad connection (someone recommended on google search)
- even when as far to reinstall windows OS
-*#0808# and set it to AP, MTP + ADB
-yes usb debugging is enabled
-download mode (odin does not see the phone, so cannot flash stock/custom rom
-diferent versions of odin
-different version of Samsung usb drivers
-have other samsung phones (note 5, and s6) and windows recognize those.
-phone does charge thru usb
need to get phone working again
-

Download stock rom from sammobile and flash it via odin.
Or else, flash the cf auto root file via odin, this reset all partitions.
Reporting Via N910G.

yashthemw said:
Download stock rom from sammobile and flash it via odin.
Or else, flash the cf auto root file via odin, this reset all partitions.
Reporting Via N910G.
Click to expand...
Click to collapse
You might try reading the whole post, rather than just replying.

JagDave said:
You might try reading the whole post, rather than just replying.
Click to expand...
Click to collapse
Sorry, my bad.
So, the author can try to repair partitions via twrp.
Go to wipe/advanced wipe and then select "Repair or change file system".
Select the partitions and repair them.
Reporting Via N910G.

Honestly man search my username ziggsta2 I had the same issue I had to buy another note 4 and even this used phone I got off eBay has the same problem when I wiggled the micro USB cord up and down I got it to connect, I don't suggest you doing this, but what might work is taking a very small piece of plastic and cleaning out your USB port on your phone, I believe these ports go bad after awhile as I have encountered this twice on two separate devices maybe you have a different issue but theres my two cents

ziggsta said:
Honestly man search my username ziggsta2 I had the same issue I had to buy another note 4 and even this used phone I got off eBay has the same problem when I wiggled the micro USB cord up and down I got it to connect, I don't suggest you doing this, but what might work is taking a very small piece of plastic and cleaning out your USB port on your phone, I believe these ports go bad after awhile as I have encountered this twice on two separate devices maybe you have a different issue but theres my two cents
Click to expand...
Click to collapse
i have tried. at this point i think it's hardware failure with the usb port. Stupid buying those cheap usb cables probably damaged the port because it seems to require a little more force than samsung cable. Planning ordering one and replacing. hopefully i don't do more damage. Had this phone for a long time and miss flashing roms on it.

i have still not fixed this problem....lol. had a new phone and been in drawer. did replace the usb port but it wasn't the problem. would like some solutions if anyone can help.

jxlee0215 said:
i have still not fixed this problem....lol. had a new phone and been in drawer. did replace the usb port but it wasn't the problem. would like some solutions if anyone can help.
Click to expand...
Click to collapse
Replace the battery

PC won't detect S7, all conventional fixes exhausted!!

I've got 5 S7s on my desk, all Canadian variant, all from the same manufacturer all the same model. - SM-G930W8
All are recognised by my PC but one and I can't work out why not!
Plugging the phone into the PC makes no noise from the PC but the phone seems to detect a regular charger not a PC.
I have plugged it in using different cables including the one in its box and the ones used on other devices that were recognised and only this phone doesn't work with any of them.
I have plugged in, unplugged and rebooted many times.
I have set the USB configuration to MTP (Media Transfer Protocol)/Transferring files.
USB Debugging is ON and OEM unlocking is ON.
I have tried booting into stock recovery and wiping cache AND factory resetting.
When phone is turned on "adb devices" returns nothing.
I have installed Samsung Kies and Samsung Smart Switch to reinstall the drivers.
NOTHING IS WORKING!
All threads I find tell me to do the things I have listed above and have people saying these have worked but all of them I had already tried and double tried and nothing is working.
The cables are correct and working with other S7s of the same model.
All the correct drivers are installed and have been uninstalled and reinstalled.
All the correct setting are selected and OEM unlock and USB debugging enabled.
Phone was fresh out the box as were the other four and all cables.
Samsungs apps installed on PC to ensure best drivers installed.
Would really appreciate some guidance or consolation that its not something stupid I'm doing! I work with these phones everyday and this has never happened! Just banging my head against a brick wall trying to resolve it

maybe faulty usb port, my nephew had S6 with the same issue, service replaced usb port and it started
to work with PC.
try download mode and see if odin see your phone.
try to move the cable a lil bit and see if sth appears for a second.

yaro666 said:
maybe faulty usb port, my nephew had S6 with the same issue, service replaced usb port and it started
to work with PC.
try download mode and see if odin see your phone.
try to move the cable a lil bit and see if sth appears for a second.
Click to expand...
Click to collapse
Thanks but unfortunately Odin doesn't recognise in download mode.
Could it be a USB port problem if I used the same port for the other 4 devices and have no issue?
I'm considering sending the phone back to manufacturer to be honest I think it may just be a faulty device or something!

I bet its microusb port fault

Had a similar issue on Windows 10 , if that's what your running let the phone be connected, uninstall the driver from device manager, and then install driver select have disk and select the basic mtp , if this doesn't help connect to Microsoft support and they'll guide you through it , worked for me , my phone used to detect on other laptops but mine , also I could connect other phones on mine but not my phone, hope this helps

same issue here