My phone won't seem to connect to my PC and Mac, The only other time it connected was when I had MIUI, I recently flashed AOKP ICS ROM from Task, but I can't seem to connect to my PC for File transfers, I have airdroid but sometimes I might not have wifi,
Help me Please
If this thread was already made Sorry about that
You need an app for that
dirtbikerr450 said:
You need an app for that
Click to expand...
Click to collapse
Which app would that be?
It should be under "my computer", listed as a phone instead of a drive, atleast for windows, don't know bout macs. You have drivers installed, correct?
twiggums said:
It should be under "my computer", listed as a phone instead of a drive, atleast for windows, don't know bout macs. You have drivers installed, correct?
Click to expand...
Click to collapse
With some ics roms it is broken and need an app
twiggums said:
It should be under "my computer", listed as a phone instead of a drive, atleast for windows, don't know bout macs. You have drivers installed, correct?
Click to expand...
Click to collapse
Last time I checked I did, Do you know where I can get them if I don't have them?
dirtbikerr450 said:
With some ics roms it is broken and need an app
Click to expand...
Click to collapse
I'm running the AOKP ROM ref in OP, and it's working fine for me, no additional apps.
vi3tl4 said:
Last time I checked I did, Do you know where I can get them if I don't have them?
Click to expand...
Click to collapse
Can't remember tbh, I installed them ages ago, I'll look when I get home if I've got a chance.
Can't remember tbh, I installed them ages ago, I'll look when I get home if I've got a chance.[/QUOTE]
Thanks, It'll help alot
Yeah so i'm not sure which has the drivers needed, only that it's something i obviously installed a while ago since i haven't installed anything new lately on my PC. I've got Kies installed (never really use, but it has some sort of drivers i think), i've got Android SDK tools (again, might contain some drivers), and i believe i downloaded the drivers via the samsung site as well.
The one thing i do notice is that it shows up as "GT-I9100" instead of our model under My Computer. So perhaps the drivers for the i9100 need to be installed as well?
Sorry, wish i had a more concrete answer for ya . does anything show up under your computer's device manager when the phone is plugged in? (likely something with a question mark next to it)
twiggums said:
Yeah so i'm not sure which has the drivers needed, only that it's something i obviously installed a while ago since i haven't installed anything new lately on my PC. I've got Kies installed (never really use, but it has some sort of drivers i think), i've got Android SDK tools (again, might contain some drivers), and i believe i downloaded the drivers via the samsung site as well.
The one thing i do notice is that it shows up as "GT-I9100" instead of our model under My Computer. So perhaps the drivers for the i9100 need to be installed as well?
Sorry, wish i had a more concrete answer for ya . does anything show up under your computer's device manager when the phone is plugged in? (likely something with a question mark next to it)
Click to expand...
Click to collapse
It shows up as unrecognized device, and it always says it malfunctioned, it has never worked even when I had the original samsung rom
I was kind of having the same thing happen. Computer wouldnt see my phone. Did a little research and came up with this. I deleted KIES (from what I read on here somewhere LOL) and did a search for this( used bing.com)...Samsung USB Drivers for Mobile Phones v1.4.8.0 After I loaded that everything went back to normal. Took me awhile to find that info but now Im glad I did!! Hope this helps!!
Try uninstalling Samsung drivers, reboot, and installing it again. Also be sure that the USB port is functioning. It sometimes could be the USB cable (HTC USB cable doesn't work very well with my i777 whereas Motorola's USB cable works great).
Heres the app you need
Related
Well Some of you guys will be surprised that i am writing about an actual concern of mine. BOOBIES!!! Now that that is out of the way.. I currently operate a Samsung Vibrant T-959 with (ROM)(PORT)Simply Galaxy 2.7XE SweeyHoney.ZSJPJ W/OverStock-v2.2.1 And a Ka7 Kernel Wich is a port from the Samsung International series I9000.
My problem is that every computer i connect to, doesnt recognize my device. Ive tried installing new drivers as well as re-flashing the rom, and still my device is not recognized. I have noticed that within the rom im using, there is a ".prop Editor" in SGHToolS. I see that if i knew what i was doing i might be able to change everything that says I9000 to T-959 (which every computer recognized)
Ive done some researching about "prop Editor" and i havent left feeling confident about messing with it. Im sorry if there was a post that expressed this concern in the past, i haven't found one but that doesnt mean its not here. So in closing, Thank you And HELP ME PLEASE!!... And remember, we all where noobs at some point
You need to download the AIO toolbox on the computer you are using and Install the drivers that program gives you. Its an actual button the the program that says "Install Drivers"....the drivers needed on the computer are not included in the classic driver install when you connect the phone. Even if you search the internet for the drivers (the option it gives you) it wont find the right ones.
also make sure you enable debugging (duh)
::if i helped, thank me::
rubbamade said:
You need to download the AIO toolbox on the computer you are using and Install the drivers that program gives you. Its an actual button the the program that says "Install Drivers"....the drivers needed on the computer are not included in the classic driver install when you connect the phone. Even if you search the internet for the drivers (the option it gives you) it wont find the right ones.
also make sure you enable debugging (duh)
::if i helped, thank me::
Click to expand...
Click to collapse
I'll try it out!.. Pressing thanks button.... Now!
Sent from my GT-I9000 using XDA Premium App
I think the toobox installs drives also.
http://forum.xda-developers.com/showthread.php?t=954509
wasscomedy said:
Well Some of you guys will be surprised that i am writing about an actual concern of mine. BOOBIES!!! Now that that is out of the way.. I currently operate a Samsung Vibrant T-959 with (ROM)(PORT)Simply Galaxy 2.7XE SweeyHoney.ZSJPJ W/OverStock-v2.2.1 And a Ka7 Kernel Wich is a port from the Samsung International series I9000.
My problem is that every computer i connect to, doesnt recognize my device. Ive tried installing new drivers as well as re-flashing the rom, and still my device is not recognized. I have noticed that within the rom im using, there is a ".prop Editor" in SGHToolS. I see that if i knew what i was doing i might be able to change everything that says I9000 to T-959 (which every computer recognized)
Ive done some researching about "prop Editor" and i havent left feeling confident about messing with it. Im sorry if there was a post that expressed this concern in the past, i haven't found one but that doesnt mean its not here. So in closing, Thank you And HELP ME PLEASE!!... And remember, we all where noobs at some point [/QUOTE
First make sure it not in Debugging mode
Then try something as simple as Settings/ Wireless and Networks/USB Settings/ask on connection or just enable Mass storage/ and it will pop up with a selection of accepting it and then your phone will be mounted!
I have a T959 Vibrant just like you,and Im running about the same ROM as you, and Im having no problems using WIN XP PRO 32 bit OS on my lappy! The ROM detects the phone as a GT-I9000 but I still can still mount it, or have a port appear if i use ODIN, or BayWolfs program etc!
Click to expand...
Click to collapse
First make sure it not in Debugging mode
Then try something as simple as Settings/ Wireless and Networks/USB Settings/ask on connection or just enable Mass storage/ and it will pop up with a selection of accepting it and then your phone will be mounted!
I have a T959 Vibrant just like you,and Im running about the same ROM as you, and Im having no problems using WIN XP PRO 32 bit OS on my lappy! The ROM detects the phone as a GT-I9000 but I still can still mount it, or have a port appear if i use ODIN, or BayWolfs program etc![/QUOTE]
WoW!.... Somthing inside tells me to just agree with the first so i can blame my computer and not the noob... But sure as **** it just worked for me... In my defence i swear ive done that... but probs not... Thanks again
nomadrider123 said:
I think the toobox installs drives also.
http://forum.xda-developers.com/showthread.php?t=954509
Click to expand...
Click to collapse
Thanks dude, my buddies computer will probs need this and not just the obvious step i just preformed. I absolutly love the knoledge of everyone on this site!! I feel dumb sometimes, but im learning
Everything worked great!!!
That being said, this morning while i was pluging mu usb in the computer, my finger touched the other end of the usb cable(that plugs into phone) Ever since then my computer doesnt even recognize that its pluged in...
Whe its in "debuggin" the computer and usb icon go on the phone
But when i plug into computer all my phone does is says its charging
Any ideas?
when its plugges in and you see the icons on your phone...pull down the menu and click the one that says 'connect USB' on your phone...then click ok when it asks you if you want to connect...should work
rubbamade said:
when its plugges in and you see the icons on your phone...pull down the menu and click the one that says 'connect USB' on your phone...then click ok when it asks you if you want to connect...should work
Click to expand...
Click to collapse
Thats what i would normaly do... but when i plug it in, my phone doesnt even give me the option of that.. My phone just thinks its charging while in computer :/
This happened to my girlfriends phone last week...she is running bionix 1.3.1.....i thought something was wrong so i re-installed the ROM to no avail. I gave up for the night.
The next day i plugged it in to the computer...and boom....worked fine. I dont know what caused it...but after a day it worked fine for me after doing essentially nothing.
maybe try going into recovery and reflashing your Kernel (tigersblood overstock whatever) then fix the permissions and wipe cache partition. and reboot.
just an idea but it may work.
rubbamade said:
This happened to my girlfriends phone last week...she is running bionix 1.3.1.....i thought something was wrong so i re-installed the ROM to no avail. I gave up for the night.
The next day i plugged it in to the computer...and boom....worked fine. I dont know what caused it...but after a day it worked fine for me after doing essentially nothing.
maybe try going into recovery and reflashing your Kernel (tigersblood overstock whatever) then fix the permissions and wipe cache partition. and reboot.
just an idea but it may work.
Click to expand...
Click to collapse
will try.. time is all i have..lol
So, trying to install the driver exe file from Samsung's website and it won't work. Keeps saying that it failed to install drivers. And, if I have the phone as USB Debugging enabled, it'll pop up with 2 out of 4 that says it failed to install.
My roommate was able to install the .exe file on his Windows 8 beta laptop (I'm running Windows 7 64-bit) without a problem. And, the phone installed fine on his laptop as well. For me, no.
If USB Debugging is not enabled, then yeah, the phone is fine. But, since I want to root this thing, it won't accept the drivers. And, nowhere on Google, searching or Samsung's website provides me any answers whatsoever.
I've done:
Going through regedit and deleting all things Samsung related
Deleted every Samsung folder on my hard drive
Rebooted the computer
Uninstalled the drivers
Reinstalled multiple times
Downloading and installing Kies (did not install any drivers, still failed)
I've done everything I can possibly think of. Couldn't find any answers on here, either. And, doesn't help that the search function is broken.
So, anyone have any idea on how to fix this? And, please do not say "Reinstall Windows" because that's just ridiculous and I shouldn't have to do that for a simple phone driver install. I had my Epic 4G before and that all went smoothly.
Go do something in control panel and uninstall the samsung drivers that you already have on your comp
Then try installing
But I reccomend reinstalling windows
Sent from my SPH-D710 using xda premium
gtuansdiamm said:
Go do something in control panel and uninstall the samsung drivers that you already have on your comp
Then try installing
But I reccomend reinstalling windows
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
+1
I had the same issue with mine on xp. Uninstalled my et4g drivers and installed the gs3 drivers. After a restart, the pc finally recognized my phone as a mass storage.
gtuansdiamm said:
Go do something in control panel and uninstall the samsung drivers that you already have on your comp
Then try installing
Click to expand...
Click to collapse
I already said that I did that.
Volknochi said:
I've done:
Uninstalled the drivers
Reinstalled multiple times
Click to expand...
Click to collapse
And, I'm not reinstalling Windows all over again just for this phone, as I also said. But, it doesn't matter, I already got it rooted through the roommate's laptop.
EDIT: I managed to get it to work. My other half had similar problems with device drivers so just had to have me remove the phone from USB, uninstall driver and then plug the phone back in. And, it actually worked.
I've looked all around for this - I got ADB drivers to install just fine so that's no issue. It's just... for some strange reason my phone works completely fine while plugged in, but the minute you go into fastboot my computer rejects it. I get a pop up saying:
The last USB device you connected to this computer malfunctioned, and Windows does not recognize it.
Click to expand...
Click to collapse
So, of course, I do a little digging and find where my DNA in Fastboot should show up in device manager.. and it says:
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
Should I reinstall HTC Sync or something (I uninstalled it)? I'm lost. Can't think of anything to do. Shuffling around the drivers that come with the SDK doesn't help any - and my Windows 7 machine didn't have any of these issues. Too bad it's dead now
[TSON] said:
I've looked all around for this - I got ADB drivers to install just fine so that's no issue. It's just... for some strange reason my phone works completely fine while plugged in, but the minute you go into fastboot my computer rejects it. I get a pop up saying:
So, of course, I do a little digging and find where my DNA in Fastboot should show up in device manager.. and it says:
Should I reinstall HTC Sync or something (I uninstalled it)? I'm lost. Can't think of anything to do. Shuffling around the drivers that come with the SDK doesn't help any - and my Windows 7 machine didn't have any of these issues. Too bad it's dead now
Click to expand...
Click to collapse
Alright, so you're going to want to have HTCSync installed, then after thats done, go to your device manager and select your device (not sure what it will be under, but it will have a (!) sign next to it). Download these drivers and use the "have disk" thing when looking for drivers in device manager. Make sure your DNA isn't plugged into a USB3 port, and then fastboot should work for you.
inexplicability said:
Alright, so you're going to want to have HTCSync installed, then after thats done, go to your device manager and select your device (not sure what it will be under, but it will have a (!) sign next to it). Download these drivers and use the "have disk" thing when looking for drivers in device manager. Make sure your DNA isn't plugged into a USB3 port, and then fastboot should work for you.
Click to expand...
Click to collapse
Ran into this yesterday. My computer ONLY has USB3 so I was unable to get it to work. Tried on a Win7x64 machine and did it first time no problem. Sigh...
Whoops, thought I posted this already... But yeah, that didn't fix the problem. Same two errors no matter what drivers I use.
[TSON] said:
Whoops, thought I posted this already... But yeah, that didn't fix the problem. Same two errors no matter what drivers I use.
Click to expand...
Click to collapse
I don't have any tips for you, other than to say that I've had fastboot work with my DNA on 2 different win 8 64 machines.
I *think* I got my drivers from HTCSync, and then uninstalled HTCSync, but not the drivers afterwards.
I did have problems with fastboot and adb when I was playing around with the CM10 build that is available here. Maybe try switching your rom and kernel?
[TSON] said:
Whoops, thought I posted this already... But yeah, that didn't fix the problem. Same two errors no matter what drivers I use.
Click to expand...
Click to collapse
I ran into the same exact issue on my win8 64-bit machine. luckily i have a couple usb2 ports and they work just fine. i wonder if using a usb hub that is compatible with usb2 or lower would work.
Did you try disabling driver signing in Windows 8 pretty sure thats the problem.
Here
Yeah you have to do that in order to install the universal driver or any other unsigned drivers - but once the drivers are installed you're good to go. No matter which drivers I pick I have this problem, I've tried probably 7 different ones.
Works fine on my Vista laptop but that things about to creak... Just used it to S-OFF and it took over an hour to turn on :crying:
EDIT: And for what it's worth, doesn't matter if it's a USB 3.0 or 2.0 - same error. Doesn't work on stock or on Cubed/Viper (though this is fastboot so kernel/ROM shouldn't have anything to do with 'em).
Computer wont recognize my device anymore. I have downloaded every set of drivers from this forum, from the samsung website, I even tried downloading kies but it wouldnt recognize it either.
It worked before I did the following and now it doesnt.
First I rooted my phone with route 66 everything was going fine until I made the huge mistake (not knowing) and downloaded rom manager so that I could do a nandroid backup. Well as we all know now, you cant do that. So I got the deadly uellow verizon triangle saying unauthorized software bring it to the store. So I went through the xda forums and found the one that told me how to fix it. I used odin with the alternate restore and got it back up and running. So I wanted to go back and use adams one click unlock and root. I got everything downloaded and ready. I put my phone in developer mode and plugged it in. It starts trying to find the drivers and then it flips from debugger mode to media mode everytime. It starts seeing it as everything but a samsung phone. It says found camera and even cd rom but not the phone. I have read through everything and tried everything I could think of but I am at a loss. PLEASE HELP
Sent from my SCH-I605 using xda app-developers app
brandi1693 said:
Computer wont recognize my device anymore. I have downloaded every set of drivers from this forum, from the samsung website, I even tried downloading kies but it wouldnt recognize it either.
It worked before I did the following and now it doesnt.
First I rooted my phone with route 66 everything was going fine until I made the huge mistake (not knowing) and downloaded rom manager so that I could do a nandroid backup. Well as we all know now, you cant do that. So I got the deadly uellow verizon triangle saying unauthorized software bring it to the store. So I went through the xda forums and found the one that told me how to fix it. I used odin with the alternate restore and got it back up and running. So I wanted to go back and use adams one click unlock and root. I got everything downloaded and ready. I put my phone in developer mode and plugged it in. It starts trying to find the drivers and then it flips from debugger mode to media mode everytime. It starts seeing it as everything but a samsung phone. It says found camera and even cd rom but not the phone. I have read through everything and tried everything I could think of but I am at a loss. PLEASE HELP
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Turn off your phone, connect to your computer with the USB cord and turn back on your phone. It should start the drivers and connect to your device.
smalk said:
Turn off your phone, connect to your computer with the USB cord and turn back on your phone. It should start the drivers and connect to your device.
Click to expand...
Click to collapse
I tried that, it is still not seeing it like it is supposed to. I was able to get Odin to recognize it so that I could flash the rooted stock again but I can't get Casual Jailbreak to work. I'm not sure if it is because the drivers or not but I am guessing it has something to do with it. Every time I plug it in, it starts searching for drivers and then always switches from usb debugging mode to media mode. The checkmark is still in usb debugging but I don't think it actually is. You can watch it go from device as installer to media.
Are you using the driver install app (zadig i think its called) to install the heimdall driver on top of "gadget serial". Looking at your other post it seems like a driver issue. One thing ive noticed is, if odin can see the device then heimdalll cant and vice/versa. So if odin can see it you have the wrong driver, if you are infact installing the heimdall driver my second question is, does windows xp x64 use driver sig enforcement like win7 x64 does? if so you probably need to disable it. Just throwing my $0.02 out there.
Are you using the official USB cable? I had an aftermarket cable that had worked for months, then decided to quit working. It works with other devices just not the Note2. Changed to my original cable and all is well.
nunyazz said:
Are you using the official USB cable?
Click to expand...
Click to collapse
Also try plugging it in to the PC and not through a hub/keyboard/monitor port
Sent from my SCH-I605 using xda app-developers app
If it sees the device in the dumb verizon cd mode thing and ptp than it can see adb. Its not the cable. however i would try setting the usb debugging first than set it to camera mode. adb should still be able to pick it up
Thank you everyone for your help, I finally got the drivers working and the bootloader unlocked
brandi1693 said:
Thank you everyone for your help, I finally got the drivers working and the bootloader unlocked
Click to expand...
Click to collapse
How? Fixing to unlock my spanking new note also. I had the drivers issues late last night. When installing drivers through the Z app I never could get it to install Samsung usb drivers nor did I see serial gadget option. Running Windows Vista 64bit. I know I have Java.
Sent from my SCH-I605 using xda premium
I rooted my phone a while back with a one click root process that rooted it to a rooted version of the stock rom. Recently I recieved notification that Jelly Bean is now available for my phone and that I need to connect to my computer via usb to update. But, my computer keeps getting a "device not recognized" error. I tried to install Kies for the drivers with no luck, uninstalled the drivers from Kies and installed the others straight from the Samsung website with no luck. I have tried 2 different computers and three different usb cables, including 2 oem usb cables. I have windows 7 which may be the problem. Are there any work arounds like going to stock from my sd card? My phone is no longer rooted, but for some reason still has Superuser which i can uninstall still. I brought my phone to Sprint which the guy was really cool and informed me that its not the usb port on the phone and that odin is recognizing it, but odin on my computers doesn't even see it.
Sent from my SPH-D710 using xda app-developers app
ultimate_reconx said:
I rooted my phone a while back with a one click root process that rooted it to a rooted version of the stock rom. Recently I recieved notification that Jelly Bean is now available for my phone and that I need to connect to my computer via usb to update. But, my computer keeps getting a "device not recognized" error. I tried to install Kies for the drivers with no luck, uninstalled the drivers from Kies and installed the others straight from the Samsung website with no luck. I have tried 2 different computers and three different usb cables, including 2 oem usb cables. I have windows 7 which may be the problem. Are there any work arounds like going to stock from my sd card? My phone is no longer rooted, but for some reason still has Superuser which i can uninstall still. I brought my phone to Sprint which the guy was really cool and informed me that its not the usb port on the phone and that odin is recognizing it, but odin on my computers doesn't even see it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Did you have the Android drivers installed previously? I'm assuming that you're trying to install the drivers for the first time on that your computer and that you have USB Debugging enabled. I'll also be assuming you disabled driver verification, which can be a problem in some computers.
First you need to boot your phone normally, and plug it into the computer. Press Win+R to open the "Run" dialog and run "devmgmt.msc," which is the Device Manager. Look up the "Unknown Device" that is your phone and double click it. Click on the Event tab and check the Hardware ID in the drop-down box. It should look something like this (sorry mine is Android Composite ADB Interface because I've installed it already, but that's what it should look like in the end):
Now you have to make a new section in the driver inf. It should be in the google adt bundle and in the extras\google directory. The file name is android_winusb.inf. In the picture below my tablet is the iDeaUSA CT702. You need to add one of these sections in both the x86 and x64 section if you have a 64 bit computer. If not, just put it in the x86 section. The %USB stuff needs to match that in the Device Manager Hardware ID.
Now you should have a device called Android Composite ADB Interface or anything like that is fine.
It says there are no drivers and that there is no hardware id. All there is are device instance id. Im not quite sure where the driver.inf is located. This has been a pain for the past week. Hopefully we can figure this out. Lol.
Sent from my GT-N8013 using xda app-developers app
I think there may have been something wrong with the rom. If i could just reinstall stock i think it would work. Just need to get the USB to read to the computer.
Sent from my GT-N8013 using xda app-developers app
ultimate_reconx said:
It says there are no drivers and that there is no hardware id. All there is are device instance id. Im not quite sure where the driver.inf is located. This has been a pain for the past week. Hopefully we can figure this out. Lol.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
If you don't know where the driver is, then download a new one. I've uploaded the official Google USB driver to mediafire here: Mediafire - usb_driver.zip
You need to modify this driver, then when asked to select the inf file for driver installation choose the android_winusb.inf inside. After installation your phone should be recognized. Please tell me if there's any uncertainties you have.
Have you tried connecting the device with usb dev mode disabled? I know its strange but I've a few devices that use different drivers if the usb dev mode is enabled. I've also devices where I need to enable usb mass storage setting every time (settings menu or slide down notification). Also it never hurts to try a new cable, usb wires do tend to wear out and are very cheaply manufactured so they break inside with the slightest tug of the wire. I know most of this stuff is uber basic but I've made things much worse on countless occasions by overlooking simple stuff like this.
ultimate_reconx said:
I think there may have been something wrong with the rom. If i could just reinstall stock i think it would work. Just need to get the USB to read to the computer.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
Cha1n5aW said:
I know most of this stuff is uber basic but I've made things much worse on countless occasions by overlooking simple stuff like this.
Click to expand...
Click to collapse
Good point. If you don't have developer mode usb debugging enabled, then there will be no "unknown device" as shown above in the device manager. Be more detailed about "no luck" please.