Database Develop

ADB access broken....beyond frustrated

This about as short as I could make it:
I haven't tried to use ADB with my G1 for about a month, so I'm not exactly sure when the problem started, but it's become a royal headache now. For whatever reason when I launched ADB shell today, I got an error saying 'device not found'. The first thing I did was check device manager where I noticed the phone showed as a 'USB composite device' with a yellow exclamation mark over it. I thought to myself "drivers." So I tried pointing it to the driver in the Android SDK folder. That just popped an error saying that Windows couldn't find a better driver match than the one I was already using.
From there I got the googling and came across this insanely long Google Groups thread. Following the advice listed, I started pulling some USB .sys files. I tried using an older copy of the USB driver from a previous SDK. I tried using Haruyko's modified USB driver. None would install.
Same error.
Reading down some more I saw that some people had success with with usinfg HTC Sync. It was worth a shot, right? Well it certainly made things different, but doesn't resolve the issue. Now in device manager I have an 'HTC Remote NDIS' listing under Network Connections. The old 'USB Composite Device' item is now gone. But still, I can't use ADB. "Device not found."
It's driving me nuts.
At this point I figured that it'd be best to try this on a different PC. Maybe my primary one is wonking out. These things happen. Well, that hope was quickly crushed when I discovered that NOT EVEN on a VANILLA XP SP3 setup, will Windows detect the G1. I downloaded a fresh copy of the SDK, plugged it in, pointed it to the USB driver....and nothing. Same error as PC number one:
"Windows can't find a better version of the driver than you're currently using."
Tried switching the USB cable. Same thing.
Back to PC number one, I removed all HTC software from 'Add/Remove Programs, then ran USBDeview. There, I removed the HTC NDIS device, unplugged the G1, and plugged it back in.
The HTC NDIS Remote device returned. **** my life.
SO.....before I throw this phone into traffic, does anyone have any clue as to what's going on here? All I want to be able to do is regain ADB access to my phone. I don't care about USB tethering (and toggling that option does nothing btw) or none of that. Just looking to regain ADB access. The only thing that's changed since the last time I used ADB is the version of Cyanogen's mod. I'm currently using v4.2.3.1. Maybe this broke shell access?
Thoughts?
**EDIT***
-Toggling USB debugging does nothing either.
-Ditto that for Fastboot

device not found has to do with the phone....make sure your cable is not messed up.

B-man007 said:
device not found has to do with the phone....make sure your cable is not messed up.
Click to expand...
Click to collapse
Tried switching the USB cable. Same thing.
Click to expand...
Click to collapse
Tried that already.

the.snks said:
Tried that already.
Click to expand...
Click to collapse
is the phones usb port ok? can you transfer files over it? if your about to throw the phone away....at least try flashing the RC29 image again

B-man007 said:
is the phones usb port ok? can you transfer files over it? if your about to throw the phone away....at least try flashing the RC29 image again
Click to expand...
Click to collapse
As far as I know the USB port is ok. It charges fine. And to update everyone on where I am, I tried the following today:
-Removed all HTC software (Sync and Drivers).
-Used USBDeview to remove all instances of HTC, and Android devices.
-Tried downgrading my test machine (PC #2) to Service Pack 2.
-Tried a third USB cable.
And I'm still getting the same problem. So there's no doubt in my mind that it has to be the phone. Like I said, the only thing I've done lately is update the version of Cyanogen's ROM.
I know it definitely worked before I updated to v4.2.3.1. Also I noticed that I am no longer able to mount the sdcard as storage in Windows. I do not get a prompt on the G1 asking if I wish to mount it. However, the USB debugging notice still pops up (weird).
....and here I'm stuck once again.

Have you tried actually uninstalling the usb devices in device manager?
I was having a similar problem, I just unistalled all the usb instances in the device manager, and when I rebooted my computer, everything seemed to work fine.

rp1783 said:
Have you tried actually uninstalling the usb devices in device manager?
I was having a similar problem, I just unistalled all the usb instances in the device manager, and when I rebooted my computer, everything seemed to work fine.
Click to expand...
Click to collapse
Yes. Multiple times in fact. It can't be the computer if the same issue is happening across two different PC's, with three different USB cables.

At first I thought this was a definite driver issue with xp, I've had similar problems in the past that just won't go away.. xp is a c*nt when it gets a driver stuck in its head that it just doesn't want to part with... but if its persisting across several machines it could well be the phone..
Have you tried adb with the phone in recovery? Boot into recovery and leave it about 30 seconds, then plug in the usb and try to get an adb shell.. this should rule out any rom config issues

goldenarmZ said:
At first I thought this was a definite driver issue with xp, I've had similar problems in the past that just won't go away.. xp is a c*nt when it gets a driver stick in its head that it just doesn't want to part with... but if its persisting across several machines it could well be the phone..
Have you tried adb with the phone in recovery? Boot into recovery and leave it about 30 seconds, then plug in the usb and try to get an adb shell.. this should rule out any rom config issues
Click to expand...
Click to collapse
PROGRESS! I booted into recovery mode and plugged the G1 into the computer. I got the 'new hardware' prompt and was asked to install the driver. I did so using the one from the SDK. Now I have ADB access, and Windows tried to mount the sdcard but that failed. I'm guessing because there's no way for me to 'ok' that in the recovery console.
So what does this tell us? I'm not sure if I understand what's wrong here.
(Sidenote: Man I'm so tempted to try to install the new Google Maps now....)

the.snks said:
So what does this tell us? I'm not sure if I understand what's wrong here.
Click to expand...
Click to collapse
It tells us that something's cocked up with the usb support in your rom, but the phone itself is fine. wipe/reflash and you should be good to go.
There is a command you can type to mount the sd for windows when you're in recovery.. just type this in the console:
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file

goldenarmZ said:
It tells us that something's cocked up with the usb support in your rom, but the phone itself is fine. wipe/reflash and you should be good to go.
There is a command you can type to mount the sd as storage when you're in recovery.. just type this in the console:
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
Click to expand...
Click to collapse
Ah....that blows but you do what you gotta. I'll try wiping and report back in case this thread helps anyone else.
Thanks man.

Alright, here's what I did to get working again:
Doing a wipe did NOT resolve the issue. However, updating to v4.2.4 did (remember I was using v4.2.3.1 originally). For clarity, I wiped both before and after the update. And I had to use a sdcard reader to get v4.2.4 onto the phone. I can now ADB and mount the sdcard in Windows without issue. I'm not sure if this was a one off, or possibly a bug in v4.2.3.
Somebody may want to bounce that Cyanogen.
B-man007 and goldenarmZ, the help was much appreciated.

This probably is related to USB tethering Cyan put in his rom.
Also for future reference, if you want to mount your SD card in recovery and you have Cyan 1.3 or greater or RA recovery, you can just type
ums_enable
to mount and
ums_disable
to dismount
saves you from typing that hideously long line lol

[Q] Nook, ADB problems

For some reason my nook won't show up in windows 7 device manager as anything but a storage device (both the nook and sdcard). It doesn't show up under "other hardware" like all the tutorials show. I am at a loss?
Should I reset my device (unroot, wipe clean, etc)? And try again or am I missing something.
I am looking to get ad hoc working and am stuck in the mud

Depending on what ROM you're running... you may need to go into nook color tools and toggle usb debugging mode... it is a known issue in some ROMs....
You may also need to edit %userprofile$\.android\adb_usb.ini so the only line in it is:
0x2080

anyone have problems in ubuntu 10.04 can't get it :'(

I figuered it might be that I had tried some different kerenels recently. I did eventually return to stock. I have toggled debugging mode to no avail.
I will follow the other instructions you provided and if all else fails wipe her clean and try that.
Thanks.
Sent from my rooted nook color using Tapatalk

I have the same problem and am using the stock kernal. I have even tried two different computers (one with Win 7 and the other with XP) and get the same result. The first time it I tried with XP it showed "NookColor" under Other Devices with a ? mark. In just a second, it reloaded Device Manager and would never showed up again. I have tried all suggestions including the USB Debugging toggle with no positive results. By the way, I rooted using auto-nooter 3.0 for Nook Version 1.1. Everything seems to work well and I am using ADW Laucher EX. I am familiar with ADB as I used it root my Motorola Droid. In that case, I had no problems with it seeing my Droid.
Any suggestions would be helpful. I also have Ubuntu on a test computer that I may try if no solutions are found.

[email protected] said:
anyone have problems in ubuntu 10.04 can't get it :'(
Click to expand...
Click to collapse
I had the same issue in Ubuntu 10.04. My Evo would show up fine. My NookColor I could not get to show up though. No matter what I tried (I tried all the walk throughs on forums, Nookdevs.com, etc).
I finally just gave up. I've just been moving APK's from my Evo to my Nook to install them. There are many other things I'd wish to do through ADB other then install apps though so I may give it another shot sometime soon.

If it worked in some ROM versions and not in others... you need to check the device ID in windows device manager... get the PID for the device listed.... then you will need to add the device PID to the .inf file for the drivers so it will know to use the drivers that work for the "new" device (not really new.. just HWID change in some new kernels/ROMs

I had a world of trouble getting getting my computer to recognize the nook so that ADB would recognize the device. I mean HOURS of debugging.
However.. good news!... The answer that can help you is...: screw it and just download adbwireless app. All you do is run the app while connected to your home network and then on your computer run the the command "adb connect 192.168.1.xxx:5555" and you are connected and can run adb just like you were USB'd up
I hope this helps

Recommend installing the easy ADB install for Windows from the developers forum.
On Win7, sometimes you need to force the driver to use "USB Composite device" or "Android composite USB device", even after doing the easy ADB installer above.

Managed to get ADB working after Autonooker 3.0, Nook 1.1
Hi, All,
I had similar problems. I managed after a bit of fuss on my mac to get ADB up and running.
The main problem seemed to be getting USB debugging working. I went into nook color tools, from ADW launcher. I went to All Settings : Development, and saw that USB debugging was checked, but I didn't believe it was running.
So, I unchecked both Auto Mount (to simplify what the heck was going on over USB) and USB debugging, and hit back, to save the settings. Then I went back into debugging, and re-checked USB debugging.
Then, I made sure that ~/.android/adb_usb.ini contained the line:
0x2080
I killed the adb server and restarted it, and voila, ADB.
Hope this helps some folks.
Dave

I am in the same boat, adb works fine on my other android device, but won't see my nook for anything.
I have tried every permutation I have seen of the rules file, still nothing.

[Q] Captivate USB problems

Hi everyone,
I have an AT&T Captivate SGH-i897 (2nd hand) and i can't mount the phone to my laptop (winXP 32bit). When i plug in the cable to the phone and then the PC i get the "device not recognized".I've donwloaded the Samsung drivers from the xda wiki page and extracted them and tried to update the driveres via Device Mng ,but didn't work.Also dl'ed the Samsung drivers 5.0.x instaled ,and still nothing.USB Debugging is on...
So to recap,my top can't recognize the phone('s internal sd card) so plz help ???????

Try this, go into usb settings and choose "mass storage"
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

install kies

I would also recommend trying to fully uninstall all the drivers that associated on your pc with your phone (samsung or otherwise), and then reinstall the drivers before you plug in your phone. Then try to reconnect.

Just covering the basics. Assuming your phone is working correctly.
You have tried multiple USB ports on your computer, particularly those on the back if it's a desktop.
You have installed correct drivers (x86 or x64)
" for the correct operating system.
You have uninstalled the drivers before trying to reinstall.
You've tried to get Windows/ Mac to find them online (assuming you're using versions of OS that support doing that)
You've first tried Kies mini before full version, uninstalling in between. (Kies full version isn't supported for US, there are workarounds, but that's a different discussion)
On the phone you tell the phone to connect 'USB storage' (from the pull down menu after connected or in the settings)

I too am having problems with USB connectivity on a notebook with Win7/64. The usual failure mode is Windows not recognizing the USB device. I have followed ZBigT's basics, step by step and still cannot connect.
FWIW, my registry is awash with Samsung entries, some of which cannot be deleted.
I've even tried the AIO Toolbox application (to install the 64 bit drivers) to no avail.
Any other tips?

Is usb debugging turned off?

o hey guys sry for keeping u waiting,
i menaged to install ginger ,
the problem was my lap....rusty old bucket!!!!
had my friend come over with his lap and it worked like a charm ,
the problem is now i need a new one ;(,
damn

mrhaley30705 said:
Is usb debugging turned off?
Click to expand...
Click to collapse
Yes. Still no love. Have tried:
usb_drivers_GalaxyS_x64
SGH-i897_Captivate_USB_Drivers_5_02_0_2
mini-KIES
Kies
AIO
uninstalling reinstalling each time
When I plug in the Captivate, any of 3 USB ports on the laptop, Windows gives the "Unrecognized Device..." message.

Go to settings/about phone. Look at the very bottom to see what rom you are running.

mrhaley30705 said:
Go to settings/about phone. Look at the very bottom to see what rom you are running.
Click to expand...
Click to collapse
Paragon RC6.0
FWIW, I also have a Win7/64 desktop with the usb_drivers_GalaxyS_x64 installed and that works fine; can connect see "drives", use ODIN, adb commands etc.
It just the notebook, which I would like to be able to use to connect, especially when I travel, which has issues.

mabovalu said:
Paragon RC6.0
FWIW, I also have a Win7/64 desktop with the usb_drivers_GalaxyS_x64 installed and that works fine; can connect see "drives", use ODIN, adb commands etc.
It just the notebook, which I would like to be able to use to connect, especially when I travel, which has issues.
Click to expand...
Click to collapse
Check in program files for a Samsung folder. There may be remnants from old drivers that need to be manually deleted.

mrhaley30705 said:
Check in program files for a Samsung folder. There may be remnants from old drivers that need to be manually deleted.
Click to expand...
Click to collapse
Thanks for sticking with this. I was able to connect. I as focused on the Registry remnants, but your advice to clear out the Samsung folder in Programs worked. Thank you.
Additional comments: I am now running the Dlev ROM, it's OK, but when I plugged in the USB cable, just to the phone, it launched the Alarm Clock app! So I deleted that.
Then on the first of my four USB ports I got a USB driver failure to install, then the Windows Unrecognized USB device on ports 2 & 3. On port 4 it worked. (This is a Lennovo/Thinkpad notebook.)
I used the usb_drivers_GalaxyS_x64 package as that also worked on my desktop.
Thank you very much.

[Q] Computer not recognizing Tab in Download mode

Hey guys,
For some reason, my Windows 7 32bit laptop is not recognizing the Galaxy tab at all when in download mode. I have installed kies (which incidentally also doesn't recognize the tab), and installed the individual drivers, but cannot get my computer to even see the Tab.
When the Tab is in normal mode (debugging turned off), I can mount the Tab as a drive and it has no problems.
Has anybody else run into this issue? The Tab is not showing up in the device manager at all. I do have root, and my end desire is to connect with Heimdall, and continue to get the error message "Failed to detect compatible device."
Any help would be greatly appreciated.
Seth

Download and install drivers for your tab. Samsung website should have them, if not they shouldn't be too hard to find.

drivers
Hi,
Already tried that. Kies doesn't recognize the device at all (with USB debugging active and not active both), and the Device Manager doesn't show anything either. When I plug the tab in, it recognizes that it is connected, but mounting the SD card as a drive doesn't do anything either.
The worst part about it is that I'm not sure that I can even revert to stock without being able to get Heimdall working. I've searched a ton, and it seems to be the key to just about everything. Any other ideas?
Seth

have you tried to install the drivers that come with Heimdall? I've had to force install those a couple times to get my Tab recognized in download mode.

Heimdall drivers
pvtjoker42,
Can you explain a little about what you mean? I am running Heimdall 1.1.1 have done the following:
1. Browse from the main folder to the "Drivers" folder and run zadig as an Administrator.
2. Click on "Options" and select "List all devices"
3. Click on the dropdown menu and search for anything that might be related to Samsung Galaxy Tab or Android of which there are none.
Is there a different way to force the install of the Heimdall drivers that I'm unaware of?
Thanks for your help,
Seth

when you drop down the list of devices what all is listed? I've had it show up as just a serial device before, with no mention of samsung/tab/galaxy etc..

Devices
Cisco VT Camera II (Interface 0)
Cisco Microphone (VT Camera II) (Interface 2)
USB Receiver (Interface 0)
USB Receiver (Interface 1)
USB-Serial Controller D
Fingerprint Sensor
Optical Drive Controller
TOSHIBA Web Camera (Interface 0)
USB Multimedia Audio Device (Interface 0)
USB Multimedia Audio Device (Interface 3)
Those same entries can be found in Device Manager>Universal Serial Bus controllers even on first boot if the Tab is not connected. Even after connecting the Tab, this list does not change.
Thanks again for your help!
Seth

have you tried uninstalling everything related to the tab? Kies, the specific drivers etc, then trying the Heimdall drivers?
So all the devices listed above are there when the Tab isn't even plugged in? Odd.. I would have suggested trying it for the USB-Serial Controller D, but if it's there without the Tab plugged in it sound like a different system device.
Don't suppose you have access to a different pc to try it on? see if it even notices the Tab being plugged in and tries to install drivers..

Yeah, I have other computers to try. Tried plugging it in yesterday to a different computer (same brand and model) with no change. Computer didn't recognize the device at all and/or try to install drivers.
Usually when an unknown device is plugged into a computer, the computer registers that it's there - the Device Manager shows an "Unknown Device" somewhere in the list, but this isn't the case with this device. Not sure what happened, but it appears as though I goofed up the USB somehow in the rooting process or the port itself went bad.
I'll try other computers and write back.
Thanks again,
Seth

I've tried three different computers with the same outcome. They do not register the device at all, and I cannot mount the SD card to the computer. I'm definitely at a bit of a loss at this point. Without USB, I'm not sure how else to make this happen. Ideas?
Seth

Just to double check with hemidall ur opening the drivers folder and running zadig.exe in there going to options>list all devices

Yes, that is correct. I'm opening the Heimdall 1.1.1 folder, opening the drivers folder, and running zadig. Nothing pops up at all and nothing shows up in the device manager.
I cannot mount the SD card to my computer, but the Tab recognizes it when I plug it into the computer's USB port. That's as far as I can get, however, as the computer does not see the Tab at all.

Have you tried 'fix permisions' in recovery mode - usually under the advanced option?
Sent from my GT-P1000 using XDA App

There is no "Fix permissions" in this recovery mode. Tried to fix permissions from cwr (which only went through 2 lines), but it doesn't seem to make any difference. Still force closes Gallery when I try to mount the SD card. Also force closes gallery when I try to open gallery.
This is very strange. It continues to tell me that there is an update available. I might go ahead and take it to see if it takes me back to stock. I would be okay with this as long as I had USB connectivity again and could root.
Any other thoughts?
Seth
P.S. Tried to take the update, but it gets about 1/3 of the way through the install and fails.

Any other ideas on how to flash without Heimdall?

Seth, what about trying Odin3 and its drivers?
Sent from my GT-P1000 using XDA App

I'll look around and find Odin3 and give it a shot. I'm concerned that because my computer doesn't recognize it as a connected USB device, that no program will see it either. That said, it's worth the shot and I appreciate the suggestion.
Do you know whether I can use the same files for Odin that I would use with Heimdall? Do they need to be packaged differently?
Thanks in advance,
Seth

If you have GSM based tab you can try flashing Team Overcome's Kratos ROM (I had no issues with download mode following their excellent ROM flashing instruction here http://p1000.teamovercome.net/?page_id=64 ) which involves download mode + using Odin, which displayed that it's connected to a tab through a serial port emulation. At least you can confirm if your tab's download mode is working. I'm using Win 7 Home Premium 64 btw.

I downloaded Odin 3, but without knowing if I am able to flash a package designed for Heimdall, I'm not sure what Odin 3 would tell me. Thoughts? Can I use Odin3 to transfer one of the Heimdall-specific ROMs to the Tab?

I had this same problem some weeks back. I had to use the drivers that came with Heimdall, and most importantly, in order to get it to recognize in download mode, I had to install them while in download mode and plugged in.

I9305 usb connection/driver problem

I've added a few apps to my S3 and altered a few things on my PC and now I can't connect via mtp or ptp. It goes through the usual "installing drivers" and then fails. I've tried pulling the battery and removing the sim and micro sd card then putting everything back. Tried it without the card (currently having to transfer files via a card reader so - at least the card's fine) but to no avail.
I've had a go at uninstalling the drivers through the device manager, rebooting and scanning for hardware changes. I've tried downloading the drivers without kies but it didnt work out (I cant remember the site or the url, but ended up with the following file SAMSUNG_USB_Driver_for_Mobile_Phones) It didn't auto install but even when I tried to point Windows to the folder on my C drive, nothing.
I've spent a couple of hours trawling the net including on here and tried all sorts.
I'm rooted, using the stock 4.1.2 ROM with Windows 7.
I can't use Kies as when it was installed the first time it wrecked all my Synctoy sync's so I really could do with another option please guys.

Dial *#7284# on your phone to access PhoneUtil and select 'Qualcomm USB Settings' at the bottom.
Now select 'MTP + ADB' and press 'OK' to return to the previous screen. Now press your 'Back' key to exit PhoneUtil. Your phone is now back to default USB operation.

Raistlin1158 said:
Dial *#7284# on your phone to access PhoneUtil and select 'Qualcomm USB Settings' at the bottom.
Now select 'MTP + ADB' and press 'OK' to return to the previous screen. Now press your 'Back' key to exit PhoneUtil. Your phone is now back to default USB operation.
Click to expand...
Click to collapse
Thanks for the quick reply.I did that and it was set to mtp + adb...
When I then connected it it tried installing the driver and I got..
Driver device software was not installed.
Please consult with your device manufacturer for assistance getting this device installed
MTP USB Device X Failed
I tried updating the MTP drivers again from device manager but this time got
Windows encountered a problem installing the driver software for your device
Windows found driver software for your device but encountered an error while attempting to install it.
SAMSUNG Mobile MPT Device
This device cannot start (code 10)
From what I'm reading it's a computer error not the phone. Can anyone suggest a new set of drivers to download (that doesnt involve Kies) as I've had issues with picking up harmful software from random sites when I've been struggling to find drivers.
I tried using the suggestion at the bottom of here r.e.Portable Devices and deleting the Upperfilters string Link but also to no avail.
Oh, and yes I've tried different ports and cables.

Well that's me done for the evening! I've tried everything mentioned in this thread including updating java and windows media player and all the afformentioned stuff but still no dice.
Could it be the actual drivers or a random windows 7 setting that I haven't yet tweaked since my clean install of windows??

http://d-h.st/YpV
Here are the correct drivers, install then reboot your pc.

Raistlin1158 said:
Go here for drivers.
---------- Post added at 01:00 AM ---------- Previous post was at 12:57 AM ----------
http://d-h.st/YpV
Here sre the correct drivers, install then reboot your pc.
Click to expand...
Click to collapse
Sorry,I know I'm tired but I can't see a link on your post...

Highlighted in red

The newer drivers don't really wwork with the 9305 so find some older drivers. That works for me
Sent from my GT-I9305 using xda app-developers app

Thanks for the tip.any suggestions as to where I can download these older drivers? I'll try the previously mentioned ones first, but I'm starting to think it might be the drivers themselves

woldranger said:
Thanks for the tip.any suggestions as to where I can download these older drivers? I'll try the previously mentioned ones first, but I'm starting to think it might be the drivers themselves
Click to expand...
Click to collapse
The ones I posted work fine on my 9305 so you shouldn't have any issues and as you can see from the site they are nearly a year old.
Try them what have you got to loose, if they don't work you are no worse off

Raistlin1158 said:
The ones I posted work fine on my 9305 so you shouldn't have any issues and as you can see from the site they are nearly a year old.
Try them what have you got to loose, if they don't work you are no worse off
Click to expand...
Click to collapse
Cheers, yeah, I was going to try them but I wasn't at my pc at the time I wrote that. I've downloaded the exe package but now it seems there are still drivers to uninstall - I uninstalled the drivers through device manager and went into my C drive and removed the SAMSUNG folder with the USB drivers in it. I'll restart the pc and hope that helps with the removal....

woldranger said:
I've added a few apps to my S3 and altered a few things on my PC and now I can't connect via mtp or ptp. It goes through the usual "installing drivers" and then fails. I've tried pulling the battery and removing the sim and micro sd card then putting everything back. Tried it without the card (currently having to transfer files via a card reader so - at least the card's fine) but to no avail.
I've had a go at uninstalling the drivers through the device manager, rebooting and scanning for hardware changes. I've tried downloading the drivers without kies but it didnt work out (I cant remember the site or the url, but ended up with the following file SAMSUNG_USB_Driver_for_Mobile_Phones) It didn't auto install but even when I tried to point Windows to the folder on my C drive, nothing.
I've spent a couple of hours trawling the net including on here and tried all sorts.
I'm rooted, using the stock 4.1.2 ROM with Windows 7.
I can't use Kies as when it was installed the first time it wrecked all my Synctoy sync's so I really could do with another option please guys.
Click to expand...
Click to collapse
Having the same problem. but I am on 4.3 rom using carbon rom a few days then transferred to pac man rom. My cellphone is not detected in my computer but it is being detected in the safely remove usb options. I tried to use a usb otg cable and a flash disk. No notification is seen on my phone but I can access the files on the flash disk (using usb otg cable) in the file manager. Tried the *#7284# but error occurs and says connection problem or invalid MMI code. I found that MTP udb device says failed

Raistlin1158 said:
The ones I posted work fine on my 9305 so you shouldn't have any issues and as you can see from the site they are nearly a year old.
Try them what have you got to loose, if they don't work you are no worse off
Click to expand...
Click to collapse
It made no difference whatsoever. I used a utility to check for an remove the samsung drivers (USBDeview) as well as uninstalling through device manager and removing with windows "products and features" but even then, when I tried installing the new drivers it mentioned previous drivers. I restarted after each stage of the process.
I've even tried connecting it in download mode and it shows in device manager.
Could there be some remnant of the software I used to root that phone that might be causing the issue??
I'm due to leave the country in 5 days and have loads of things to sort (also have a family member going into hospital for major surgery tomorrow) so I can't just devote all my time to this - but I need to at least know that it's not the phone (I dont have another win 7 computer to try it on).

woldranger said:
It made no difference whatsoever. I used a utility to check for an remove the samsung drivers (USBDeview) as well as uninstalling through device manager and removing with windows "products and features" but even then, when I tried installing the new drivers it mentioned previous drivers. I restarted after each stage of the process.
I've even tried connecting it in download mode and it shows in device manager.
Could there be some remnant of the software I used to root that phone that might be causing the issue??
I'm due to leave the country in 5 days and have loads of things to sort (also have a family member going into hospital for major surgery tomorrow) so I can't just devote all my time to this - but I need to at least know that it's not the phone (I dont have another win 7 computer to try it on).
Click to expand...
Click to collapse
Just got the same problem. But my problem is already solved. Just flash a new rom. In my instance, I flash ripper rom