Like it says my display is completely broken :'(
The phone starts up and I hear the Samsung tune start and then it connects to computer.
However it connects as a fresh install. I'm almost certain USB Debugging is on, but I don't believe I had hooked it up to a pc on the Rom yet so I have not selected Mtp mode yet. Its modified Touchwiz kk not cm.
Is there an easy method to command it to connect through mtp before or with simple adb commands?
Or do I have to download Android sdk and go full adb everything?
Sent from my SPH-D700 using XDA Free mobile app
Related
Ok so I want to root my epic, there's just one problem... ADB doesn't see my phone. It is listed in my device manager and is showing as working. but when i try and list adb devices it shows nothing. My phone is in USB Debugging mode. I have the Samsung drivers installed. I just cannot figure out why this is not working for me. I have looked everywhere and have been unable to find anything that has helped my problem at all. Tried to upload a pic showing my device manager but i guess i cant yet because i haven't made enough posts yet. Device manager show my device in three different sections one under USB Controllers as SAMSUNG USB Composite Device, One under Ports (COM & LPT) as SAMSUNG Mobile Modem Diagnostic Serial Port (WDM) (COM4) , and one under Modems as SAMSUNG Mobile Modem.Thanks for any ideas.
jarmour05 said:
Ok so I want to root my epic, there's just one problem... ADB doesn't see my phone. It is listed in my device manager and is showing as working. but when i try and list adb devices it shows nothing. My phone is in USB Debugging mode. I have the Samsung drivers installed. I just cannot figure out why this is not working for me. I have looked everywhere and have been unable to find anything that has helped my problem at all. Tried to upload a pic showing my device manager but i guess i cant yet because i haven't made enough posts yet. Device manager show my device in three different sections one under USB Controllers as SAMSUNG USB Composite Device, One under Ports (COM & LPT) as SAMSUNG Mobile Modem Diagnostic Serial Port (WDM) (COM4) , and one under Modems as SAMSUNG Mobile Modem.Thanks for any ideas.
Click to expand...
Click to collapse
Try different USB port, switch data cable and also uninstall - reboot- reinstall driver - reboot - reboot phone - try again.
If you are using a laptop sometimes it's flaky. Reboot often and remember that you may have to kill that exe process... Think it was adb.exe a few times and just screw with it until you trick it to work. Trial and error
Sent from my SPH-D700 using XDA App
Ok so I wated a video on rooting samsung epic and one thing that I noticed was that when he hooked up his epic it showed up in the device manager under ADB Devices and mine shows up in 3 other locations. Is this where my problem is... am I just having issues with my drivers?
Sent from my SPH-D700 using XDA App
Turn off any security and uninstall the samsung drivers. reinstall drivers and watch and make sure your phone is detected by your pc. Now run your rooting app.
Sent from my SPH-D700 using XDA App
Hello. I am having the same problem as described above. The Epic is installing as a modem (on my Win7 PC) instead of an Android Composite ADB Interface. I cannot connect at all to the Epic (cannot connect via adb with debugging turned on and it I try and mount the Epic no folders show up on the PC). I have reinstalled the drivers and checked all of my serial ports. Also, I have a Samsung Captivate that works fine using the same system. Incidentally my wife took the Phone into Sprint to get the latest android version and they gave her a hard time cause it was rooted. I think they may have done something to the phone cause I pulled pictures off her phone to the PC last week. Help please!!
OK, so I got the Eipc to work. I still do not know the root cause but here are the steps I took to "fix it":
1) Unplugged USB cable and disabled usb debugging
2) Plugged in phone to USB and selected Mass storage. The drivers were installed correctly
3) Unplugged phone and turned on USB debugging)
4) Plugged in phone and the proper devices were detected but windows hung on installation of a "strange" unkown ADB device
5) Unplugged phone and plugged back into the USB port and all was working!
Hope this helps.
I've never had a problem with android file transfer up till I rooted today. My wife has a stock Nexus 7 and I can plug her Nexus into my computer and the file transfer app will start. I have usb debugging turned on and the usb connection on my tablet is set to Media device.
Now as I'm typing this my Nexus has been connect to my mac for about an hour. I just went to the USB settings to make sure I had Media device selected and the file transfer window popped up out of nowhere. I killed it and tried again and it won't come up. Maybe in an hour or so if it does the same thing.
Any ideas as to what's going on? Very strange behavior.
Disable USB debugging.
Unplug/plug in your nexus.
The USB IDs change for some reason when you have USB debugging turned on and the MTP device isn't recognized as such. PTP (camera) mode continues to work for both cases though.
Thanks for the suggestion but It still fails. I disabled debugging and still can't connect. Switching USB modes didn't help either.
If that doesn't work uninstall the adb driver & then plug your tablet back in so it will reinstall
My next suggestion would to reboot the tablet with USB debugging turned off.
If that doesn't work, my next suggestion would be to delete the existing drivers and force reinstall.
All with USB debugging turned off.
johnnyninja said:
I've never had a problem with android file transfer up till I rooted today. My wife has a stock Nexus 7 and I can plug her Nexus into my computer and the file transfer app will start. I have usb debugging turned on and the usb connection on my tablet is set to Media device.
Now as I'm typing this my Nexus has been connect to my mac for about an hour. I just went to the USB settings to make sure I had Media device selected and the file transfer window popped up out of nowhere. I killed it and tried again and it won't come up. Maybe in an hour or so if it does the same thing.
Any ideas as to what's going on? Very strange behavior.
Click to expand...
Click to collapse
Make sure after you plug in your device you're looking at your tab and click OK on the pop up........
Sent from my Nexus 7
Thanks for all the suggestions. It's working now. I was just about ready to delete the driver and the tablet started to be recognized consistently. I was in the settings screen and toggled debugging on and off while plugging in the tablet. I noticed the info bar at the top alternating between showing "debugging" and "media device" and I selected each one a couple of times when they came up. I think that it finally worked through the ID confusion that was mentions. I'll follow the the rest of the instructions if the problem comes back.
Thanks again.
It's acting up again so I'm going to try deleting the drivers. I thought I knew what to do but I can't find any information. What's the procedure to delete the driver? I'm running os x lion
I've tried every suggestion in all of these threads so far & nothing worked. Even after I deleted the ADB drivers, windows 7 would automatically reinstall them. When I tried to update the drivers, win7 said they already had the best drivers (ADB).
Here's what worked for me:
I had to turn off USB debugging, delete the ADB drivers in Device Manager, then reboot the device while it's still plugged in. Windows recognized the device as an MTP device & installed the drivers before it even fully booted.
I'm not sure how I finally resolved the problem on my mac. I toggled debugging on and off and rebooted a couple of times. That may have done it. I also ran the adb script in the SDK platform-tools folder. I don't know what that script does exactly but possibly it reinitialized the driver and ID.
Anyway, hopefully these workflows will work for others.
johnnyninja said:
I'm not sure how I finally resolved the problem on my mac. I toggled debugging on and off and rebooted a couple of times. That may have done it. I also ran the adb script in the SDK platform-tools folder. I don't know what that script does exactly but possibly it reinitialized the driver and ID.
Anyway, hopefully these workflows will work for others.
Click to expand...
Click to collapse
Rooted my nexus 7 (2012) last night and struggling with my laptop not recognizing it. This thread solved it!
Delete the ADB on my window, toggle off debugging and restart the nexus 7 with usb connected to laptop. works like a charm.
Thank you!
Guys, my N4 got this problem too.. until just a few minute ago
I read somewhere ini goge groups (i think N5 group), and found explanation that we can change ADB or MTP "mode" on device manager. On "Androoid ADB Device" right click and select "Update Driver Software". Click "Browse My Computer for Driver Software" and then "Let me pick from blablabla...." And then select MTP USB Device, "next" and my N4 detected on Windows Explorer.
Hope it will be usefull for you guys.
After recently flashing the new aosp kit kat, I have now lost the ability to link between my computer and phone. usb debugging is checked and all it does is slow charge. I have restored previous roms and debugging still does not work. Anyone else having this issue?
what operating system does your computer have? ive heard on windows 8 your have to reinstall the usb drivers, and some people have lost connectivity after upgrading.
Maestertk said:
what operating system does your computer have? ive heard on windows 8 your have to reinstall the usb drivers, and some people have lost connectivity after upgrading.
Click to expand...
Click to collapse
I am still running windows 7
RESOLVED
Set debug mode on, connect your phone. When you get the prompt for File Storage, MTP, or Charge mode click on the back arrow on the top left corner. This will take you back one screen to where you can see USB Tethering. Turn it on and debug will be enabled.
I hope it works for you.
----------------------------------------------------------------------------------------------------
Same here. I have stock unroot LS970ZVC. I want to root but debug won't work.
With Debug on, all I get are the options of Charge Only, File Transfer, and MTP.
Without nothing happens.
Windows 7 and the LG Android Driver from LG's Website.
Unfortunately the screen to choose between,charge only, mtp, or pics. No longer even comes up. Just slow charges.
Sent from my LG-LS970 using xda app-developers app
I'm having an issue where I can connect to my 64 bit Win 7 laptop in debug mode, but I'm not able to connect in the MTP mode with debug turned off. I expected to be able to mount the device storage in either mode.
Is that correct? If so, any ideas? I do notice I can't seem to get the MTP driver to stay in device manager unless I activate device mode. I have verified I have the Google Nexus ADB interface installed.
Thanks,
Rick
I had the same problem. Go into the device manager. Don't just remove, also delete the current drivers. Once they reinstall it solved the problem for me.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
I was having an issue with my i9250, my phone would not be recognised in windows when switched on normally, so I replaced the USB flex inside,and I'm still having the same problem.
My computer will detect my phone in fastboot mode, or in odin mode, but I will not be detected normally, nothing appears, not even unknown device, and I have enabled usb debugging, flashed mutiple stock images but I still have the same problem, have you got any more ideas for me?
Thanks.
what windows you using? did you enable usb conection on phone? if you are on windwos 8 look at softwere update to install new usb driver for our phone
Make sure you have the right drivers installed. There is a stickied thread that contains all the steps of returning to stock 4.3. I believe the first step deals with getting the right drivers and installing them correctly. I would suggest following those steps.
Connect phone in usb debugging mode and then Try to manually install the drivers from device manager.
Had the same problem
Sent from my Galaxy Nexus using xda premium
MPT PTP
seriousia said:
Connect phone in usb debugging mode and then Try to manually install the drivers from device manager.
Had the same problem
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Switching between MTP/PTP have fixed some issues for me.