Related
I've been reading here at XDA, I can find the instructions - no problem.
However, in the WIKI there are a few things I don't understand.
The problem also is that all the posts assume you know what's going on and they start in the middle of a thread.
Then there's advice to use Odin, not to use Odin, use this, don't use this.
Some say unmount the SD card, some make no mention of SD card.
Then there's different backups. I've seen Titanium mentioned.
There's advice to get the latest drivers from Samsung - The phone isn't even in the dropdown list of phones, and the letters for the model don't match.
There's the custom ROM advice. Since there aren't many for this phone as yet - and all you want to do is remove crap, what do you look for?
I have to get rid of that stupid Doubletwist and airsync before I toss the phone!
Z
It is rather confusing isn't it...
In a simple answer....
Find the SuperOneClick zip file in one of those threads in the Dev forum & root the phone.Then go get TitaniumBackup ( Pro Recommended ) & you can remove the bloatware. I'd recommend the Pro Version so you can freez the apps you don't delete.
That's what i did on my SGS4G ( and i am not a experianced modder myself )
One problem. I downloaded superoneclick and NET can't find the runtime file.
I'm using XP and ver 4 of NET. I turned off NOD32 and Online Armor.
Z
zuben el genubi said:
One problem. I downloaded superoneclick and NET can't find the runtime file.
I'm using XP and ver 4 of NET. I turned off NOD32 and Online Armor.
Z
Click to expand...
Click to collapse
Uninstalled NET 4 and put in 3. I can open the file, but NOD32 keeps quarantining RAGE. Says it's a trojan.
I don't really want a custom ROM - but would like some more information on Titanium Backup. The Market won't download to the phone, but going to the market on the phone will let me download.
Thanks,
Zuben
Moved as not android development
zuben el genubi said:
Uninstalled NET 4 and put in 3. I can open the file, but NOD32 keeps quarantining RAGE. Says it's a trojan.
I don't really want a custom ROM - but would like some more information on Titanium Backup. The Market won't download to the phone, but going to the market on the phone will let me download.
Thanks,
Zuben
Click to expand...
Click to collapse
Let it scrub the RAGE file, you need the other one actually to make it work
Which one? PSneuter?
Also some confusion about the Samsung driver. I also have a Galaxy 3. I downloaded Kies and the driver. I downloaded the new driver (did not install it)and stuck it in a folder named Samsung on the Desktop. Kies is in the Samsung folder in programs and I assume that the original driver is in there, too. The driver is listed in Add/Remove programs.
I can either delete Kies or rename that file to something else, and stop Kies from running. So there's 2 drivers, and I suspect they are the same.
Since I can't send a download from the Market on the PC to the phone, I have to download from Market on the phone. I can't install Titanium unless I root, but can I get to Titanium from the phone if I do root?
Thanks
Z
I use linux... so i have no idea what Kies is or does..
zuben el genubi said:
Which one? PSneuter?
Also some confusion about the Samsung driver. I also have a Galaxy 3. I downloaded Kies and the driver. I downloaded the new driver (did not install it)and stuck it in a folder named Samsung on the Desktop. Kies is in the Samsung folder in programs and I assume that the original driver is in there, too. The driver is listed in Add/Remove programs.
I can either delete Kies or rename that file to something else, and stop Kies from running. So there's 2 drivers, and I suspect they are the same.
Since I can't send a download from the Market on the PC to the phone, I have to download from Market on the phone. I can't install Titanium unless I root, but can I get to Titanium from the phone if I do root?
Thanks
Z
Click to expand...
Click to collapse
So which phone are you trying to Root? Samsung Galaxy 3 or Samsung Galaxy S 4G? If your rooting the S 4G you can find the drivers here http://downloadcenter.samsung.com/c...728034640796/SGH-t959_Vibrant_USB_Drivers.zip
I have no experience with rooting with XP but I assume it would be essentially the same steps.
If your looking to do stuff on your Galaxy 3 then please go to this forum
http://forum.xda-developers.com/forumdisplay.php?f=868
and do your research over there.
It’s not that difficult to root the SGS 4G Phone. The first thing you need to do is make sure your phone is communicating with your computer. Install the Samsung USB drivers.(make sure you have the right drivers for your O.S. either 32bit or 64bit) In your phone go into Settings/Applications/Development and make sure you check “USB debugging”. Connect your Tethering cable to your phone. On your home screen you should see “USB Connected” popup on top of your screen. You should be able to press USB connected button from the drop-down menu on the home screen and see the external SD card on the computer now. If that works then Turn off USB storage. (leave “USB debugging” checked) Open NOD32 application from your system tray. Go to Settings and select “Temporarily disable antivirus,” put your password in if prompted. Then Download SuperOneClickv1.7-ShortFuse, expand the file and go to SuperOneClickv1.7-ShortFuse Directory. Run the SuperOneClick App. When it opens don’t change anything and just click “Root” and let it run. It should say rooted when done. Then go to the Market on your phone and get Titanium Backup and install it. It will ask for SuperUser permission and accept that on your phone. If that fails press “Problems” button, Then “Get Busybox”. Install the new Busybox. You may have to close and reopen Titanium Backup again. I would say to download and install ClockworkMod after rooting and before getting Titanium Backup, Except ClockworkMod currently does not work for the SGS 4G Yet. So, skip that step for now. You should be able to backup your phone after this.
nwpro3 said:
It’s not that difficult to root the SGS 4G Phone. The first thing you need to do is make sure your phone is communicating with your computer. Install the Samsung USB drivers.(make sure you have the right drivers for your O.S. either 32bit or 64bit) In your phone go into Settings/Applications/Development and make sure you check “USB debugging”. Connect your Tethering cable to your phone. On your home screen you should see “USB Connected” popup on top of your screen. You should be able to press USB connected button from the drop-down menu on the home screen and see the external SD card on the computer now. If that works then Turn off USB storage. (leave “USB debugging” checked) Open NOD32 application from your system tray. Go to Settings and select “Temporarily disable antivirus,” put your password in if prompted. Then Download SuperOneClickv1.7-ShortFuse, expand the file and go to SuperOneClickv1.7-ShortFuse Directory. Run the SuperOneClick App. When it opens don’t change anything and just click “Root” and let it run. It should say rooted when done. Then go to the Market on your phone and get Titanium Backup and install it. It will ask for SuperUser permission and accept that on your phone. If that fails press “Problems” button, Then “Get Busybox”. Install the new Busybox. You may have to close and reopen Titanium Backup again. I would say to download and install ClockworkMod after rooting and before getting Titanium Backup, Except ClockworkMod currently does not work for the SGS 4G Yet. So, skip that step for now. You should be able to backup your phone after this.
Click to expand...
Click to collapse
This is good information, but what about for Mac users? I was previously able to root my Samsung Vibrant just by installing the update.zip file via CWM. Should Mac users wait for this course or can we make it happen now?
Also, what's the benefit of rooting right now? Just to remove bloatware? There's no custom roms yet, right?
Look at the Unix instructions about associating the USB ID with the Mac. I haven't tried it, but I suspect that is the missing step.
Update: Nope -- According to Google, http://developer.android.com/guide/developing/device.html#setting-up
Setup your system to detect your device.
* If you're developing on Windows, you need to install a USB driver for adb. If you're using an Android Developer Phone (ADP), Nexus One, or Nexus S, see the Google Windows USB Driver. Otherwise, you can find a link to the appropriate OEM driver in the OEM USB Drivers document.
* If you're developing on Mac OS X, it just works. Skip this step.
* If you're developing on Ubuntu Linux, you need to add a rules file...
(Emphasis mine)
Sent from my SGH-T959V using XDA App
I'm wanting to root the 4G. The Galaxy3 was bought unlocked so it doesn't have the crap on it. Like I said, the ROM seems to be ok, it's just the stupid bloatware.
Chamgea said:
This is good information, but what about for Mac users? I was previously able to root my Samsung Vibrant just by installing the update.zip file via CWM. Should Mac users wait for this course or can we make it happen now?
Also, what's the benefit of rooting right now? Just to remove bloatware? There's no custom roms yet, right?
Click to expand...
Click to collapse
Macs are out of my Knowledge base. I've taught PC repair at LAUSD in Ca, but haven't studied the Mac thing. It's something I want to learn, just have not got around to it yet.
I've tried the drivers from Samsung, Keis, ODIN one click. None of them worked on 4 different machines, Windows 7 both x64 and x86(which was a fresh install), and two Windows XP machines. I tried it on Ubuntu(10.04 LTS) and that recognized the captivate.
Anyone know how to get one of those to correctly recognize my Captivate so I don't stuck on Samsung's/AT&T's 2.2
uninstall all of the driver that you downloaded. uninstall kies. then go to samsung.com search for the captivate, choose you phone, click the 'i own this' button. then go to get downloads, software. click on the .zip file icon next to usb drivers. if that didnt work uninstall them then download kies again. if it still doesn't install them, open kies, click menu, reinstall drivers
What is it that you're trying to do?
Sent from my SAMSUNG-SGH-I897 using XDA App
If it is coming up unknown device try another port. You may want to try another microusb cable as well.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
I've always had luck with the drivers in the captivate aio toolbox. Even on a fresh win7 64bit when I replaced my boot drive with a ssd a month ago.
Samsung really failed at the USB drivers for the Captivate. I would expect to be able to install the drivers from their website. Plug in my phone, and have it working.
trell959 said:
uninstall all of the driver that you downloaded. uninstall kies. then go to samsung.com search for the captivate, choose you phone, click the 'i own this' button. then go to get downloads, software. click on the .zip file icon next to usb drivers. if that didnt work uninstall them then download kies again. if it still doesn't install them, open kies, click menu, reinstall drivers
Click to expand...
Click to collapse
I tried that before, didn't work.
bornjamerican said:
What is it that you're trying to do?
Click to expand...
Click to collapse
I'm trying to:
1) connect as a mass storage devices. Yes I know turn on USB debugging and to mount the drive.
2) flash back to stock 2.1 or root my phone so I can install a custom ROM on it. Might go with CM7/MiUi or something from Team Phoenix. So use Odin3
shinji257 said:
If it is coming up unknown device try another port. You may want to try another microusb cable as well.
Click to expand...
Click to collapse
Tried all of the ports on the computers. I don't have another microusb cable to test to see if that's the problem, but I'll check that tomorrow.
Johnnie5000 said:
I've always had luck with the drivers in the captivate aio toolbox. Even on a fresh win7 64bit when I replaced my boot drive with a ssd a month ago.
Click to expand...
Click to collapse
I'm going to try a fresh install of windows 7 32-bit with aio toolbox see if that works.
Tried my friends brand new microUSB cable. It worked.
I have tried 4 known good cables know, 4 different computers and every USB port available on all 4 of the PCs I tried. Only once did it identify the device and install the drivers and I was able to root it but I still can't sideload because after the reboot after rooting it is back to device not recognized/unknown device. This has been a total pain. Any suggestions? I'm not with AT&T any more so I am out of luck for just bringing it into a store and asking them to take care of it.
Edit: Sorry for bumping an older post but I did it instead of starting a new thread.
rmriggin said:
I have tried 4 known good cables know, 4 different computers and every USB port available on all 4 of the PCs I tried. Only once did it identify the device and install the drivers and I was able to root it but I still can't sideload because after the reboot after rooting it is back to device not recognized/unknown device. This has been a total pain. Any suggestions? I'm not with AT&T any more so I am out of luck for just bringing it into a store and asking them to take care of it.
Edit: Sorry for bumping an older post but I did it instead of starting a new thread.
Click to expand...
Click to collapse
If you're just trying to transfer apk files to it for sideloading, you can use a wifi transfer app. I use Wifi File Explorer and it's great. You can connect to your phone via web browser and upload/download anything on the SD card.
Another option is to use an external SD card that you can remove and plug into your computer, transfer the files to it, then insert it back into the phone.
This won't work for connecting to PC apps like Odin, Heimdall, or Kies, but for simple file transfers it works like a charm.
Additionally, regarding other usb cables, you didn't mention what types of cables you used, so I'll throw in another thought. The cables that come with the Captivate don't work on some PCs (like my new iMac). Third-party, generic usb cables might not work, either (I tried some and got a whole lot of fail). The only cable that works for me is the one that came with my wife's Motorola phone. If you haven't tried one yet, I would recommend getting your hands on a Motorola cable and testing it out. You'll immediately notice the cable is much thicker. I don't know if that has anything to do with why it works when others don't, but there's something about that cable that others don't have.
Bad Phone?
Could it be the phone port is having issues?
I've had the same problem and it seems that the port on the Captivate is shot which may be your issue. it will always charge; but tends to cause a lot of profanity when trying to get a PC connection to transfer files or flash it. It will be seen, then immediately play the 'unplugged' sound from windows. I've sat there and had it play the tones of plugged in and un plugged over and over again just by tilting the phone from side to side. No matter what cables I use (tried several but they are all samsung due to the recessed port). If it establishes the connection; I have to be very still with it or it'll lose it. If it loses it; I get unknown device messages or not functioning messages on that port until I reboot the PC.
Trying to flash anything via ODIN takes a lot of patience.
Those same cables / USB ports are used on my wife's Focus without ever having a problem. I wrote it off as too much flashing / overclocking of my phone but am not sure.
hi i was having this issue as well. i solved it by:
1. download a good & stable miui rom, rename it to update.zip and place it into your sd card. i took the sd card out of the phone and used a adapter to connect the sd card to my PC since i can't access my sd card through the usb port.
2. put the sd card back into my phone, turn off my phone. press and hold volume up and down buttons, then press n hold the power button till the screen shows something.
3. select install from sd. wait until the installation finishes and select reboot the phone.
4. when you're in your new miui rom, try to connect your phone to the pc via usb port again.
this worked like charm for me.
about the miui rom, i suggest you to use the one from miuiandroid.com (the UK version)
after flashing the rom im able to connect via usb and use mass storage.
hope this helps
Also, when you uninstall drivers, don't forget to look in the program files for anything that may have been left behind and delete it.
From the description it sounds strongly like you are actually experiencing a port failure which is common on the Galaxy S devices. PM me if you need this repaired...
Only try another usb cable, i bricked my cappy with a bad contact cable on odin, unknown device too, new cable=i897 device on windows notifications
try and feedback!
strange, this only happened to my when i soft bricked my phone. try connecting it to your computer in download mode
I had this issue once before. Here is what I did which resolved the problem. I was using a windows 7 PC
1. Download the ADB kit and extract it to C drive.
2. Connect your mobile to the PC on USB port
3. Wait for the drivers to be installed automatically (it might give you a failed to install message)
4. Never mind that message. Open Device Manager
5. In Device Manager, if you expand the "Universal Serial Bus Controllers", you'll see a device that has yellow question mark against it. This is your phone and since drivers are not installed properly, it has the question mark.
6. Right click that device, and select "Update Driver".
7. IN the window that comes up, select "I'll select a driver".
8. Browse to the folder where you have extracted the ADB kit on C drive
9. Check include subfolders and click Next.
10. The drivers should be be installed and your device should be identified by the computer.
Let me know if it works for you.
I originally posted this inside the Glorious Overdose V2 thread, but decided to post here as well.
For some reason my computer won't recognize my Sidekick when I plug it in via usb. I do have the samsung drivers installed and it will read my friends Samsung Droid Charge just fine, but when I plug my Sidekick in it comes up saying "USB Device Not Recognized". So far I've tried uninstalling and reinstalling the drivers from the device manager to no avail. Wondering if anyone has an idea as to what it could be. I've also tried googling the solution and everyone says to just uninstall and reinstall the drivers and it should work. Now the phone is not plugged into a USB Hub, extender, or case, it is plugged directly into a usb port on the mother board.
PC Specs just in case:
Motherboard - Gigabyte GA-970A-D3
OS - Windows 7 Ultimate x64
CPU - AMD FX-4100
Memory - 8GB DDR3 1066
Phone:
T-Mobile Sidekick 4G running Glorious Overdose V2
Nothing added just the rom and some apps/games.
I have tried with USB Debugging on and off, either way does not work.
Update: I have since tried Kies mini, as well as the drivers found on Softpedia. Neither of those worked, so I just got done reformatting and reinstalling Windows hoping that would work. At first it did not, right now I am running windows update to see if that was the issue, I'll update of what the outcome is.
Update: After installing all available Windows updates it's still not recognizing the phone. Now no matter what it's saying it's an Unknown Device. Even after I try and do a manual driver update and tell it to look in the folder with the driver files from Softpedia. I'm at a complete loss now.
If anyone has any idea's please let me know.
What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.
Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA
Jax184 said:
What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.
Click to expand...
Click to collapse
It's set to USB Debugging. But even then, it should read as something else other then Unknown Device when I plug it in. I have tried plugging it in and selecting Mass Storage, still comes up as Unknown Device.
HewettBR said:
Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA
Click to expand...
Click to collapse
I've thought about that, and from everything I can see it's either the ROM or the drivers. So we'll see...I'll probably try a different ROM and see what happens.
I suggest turning USB debugging off and mass storage on, for how you'll be using it. And recall that you have to change this stuff with the USB cable unplugged.
I've tried that, and after talking with the T2 Technical Support from Samsung for 45min today, the only option left is to send the phone in to get worked on. Though, I'm going into the T-Mobile store and see if they can't replace the phone or give me a loner while this one is out getting repaired.
More info request.
Can you provide us with the names and links to the drivers you have tried?
DuctTapedGoat said:
Can you provide us with the names and links to the drivers you have tried?
Click to expand...
Click to collapse
Kies Mini - http://www.samsung.com/us/support/owners/product/SGH-T839HABTMB
Softpedia - http://drivers.softpedia.com/get/MOBILES/Samsung/SAMSUNG-USB-Driver-1480.shtml
As well as the Samsung Vibrant drivers from both of those sites.
Samsung SideKick 4G Drivers
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.
DuctTapedGoat said:
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.
Click to expand...
Click to collapse
Thank you, I tried unpacking them to a folder on C:\ went into Device Manager, right clicked on the Unknown Device, Update Driver Software..., Browse My Computer for Driver Software, Set the search to C:\, and still saying Unknown Device is the best driver software for it. No idea why it's doing this.
Proper Driver Update
What is going on is that Windows is seeing a more recent signature file attached to the SK4G drivers on your computer (I don't believe anything at all is wrong with your device) than the working ones there.
First, in Add/Remove Programs, uninstall the Samsung Kies and Samsung Driver pack you installed earlier. Now...
Go into on your PC:
://windows/system32
And locate the same file names, cut them all, and paste them in a temporary folder you create, preferably on the desktop or something similar. You may not find every file, and that's okay, just the ones you can find. Next, you will be wanting to paste the driver files from the package I uploaded. Now, turn off Automatic Updates, so it doesn't automatically install drivers upon connection. Reboot the computer, double check and make sure Automatic Upates are off when you log back on. Now, connect the device and see if it gives you the same results. By removing the old drivers which don't work, you'll be able to force it to the ones we know work, and you /should/ have success. As well - USB data debugging active and activating connection for data transfer via the notification pulldown menu would be the best way to do this initially.
Would I be looking in c:\windows\system32\drivers for the same file names as the ones you packed up?
Ok, so the only one I could find in the drivers folder was modem.sys. But it will not let me move/replace the one that's already in there. It's telling me access is denied, same thing when I try and set the permissions it will not let me. I am logged in as an Administrator, as well it says it when I log in as THE Administrator account. So yeah...
Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?
DuctTapedGoat said:
Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?
Click to expand...
Click to collapse
I tried plugging the phone in, still showing up as Unknown Device. Tried UnlockRoot.com's program, no change. Installing the Android SDK right now, as well as I tried deleting the INFCACHE.1 file, and no change with that either. Once I'm done installing the Android SDK I'll redelete the INFCACHE.1 file and restart and try the phone again.
I did go in and check the mounts in recovery and they were set to:
UNMOUNT CACHE
MOUNT DATA
UNMOUNT SDCARD
UNMOUNT SYSTEM
Thank you for your help so far.
UPDATE: So after installing the Android SDK, deleting the INFCACHE.1 file, restarting, and then plugging the phone in, comes up and says the USB Device is Not Recognized. Then goes to search the preconfigured driver folders, and fails to install the driver for Unknown Device. And ADB Devices shows no devices as well(didn't think it would, but yeah).
UPDATE: So after using my friends phone as a conduit to throw the Stock Odexed KJ2 w/ Root(http://forum.xda-developers.com/showthread.php?t=1328698) onto my SDCard and flashing that the phone seemed to go into a soft brick at pre-boot screen(where it says SAMSUNG T-Mobile blah blah blah). Mind you this would freeze before it was even able to get into recovery. So I took it into T-Mobile and they are doing a manufacturer warranty replacement. So hopefully this next phone will be able to connect to the computer and be read correctly.
I just got a S3 yesterday but was greeted with the dreaded MTP driver installation failed message on win 7 (32 bit)
I installed the regular verizon s3 drivers from samsung's site, did the same thing, uninstalled and tried Kies and let it install the drivers, same problem
tried a different usb port, same thing
restarted the comp and computer, still no go
im getting frustrated now
it seems samsung has known about this issue for over a month now but still hasnt been able to fix it
my a500 and galaxy nexus work fine with MTP so not sure why this would mess up
ive looked at other threads but there was no clear solution on how to fix it
I don't have any issues with mine
Sent from my SCH-I535 using Xparent Blue Tapatalk 2
thats nice but it doesnt exactly do anything for my problem
Joey22688 said:
thats nice but it doesnt exactly do anything for my problem
Click to expand...
Click to collapse
Did you try a factory reset?
Sent from my SCH-I535 using xda app-developers app
This happened to me too but I was running a CM10 ROM. What are you running and have you tried a different ROM?
Unfortunately, I cannot remember exactly what I did but I recall allowing Windows (I'm on W7) to find the drivers and install for me.
I'm not having any issues either, I'm using both 32/64 versions of Win 7...
These are the drivers I'm using:
http://downloadcenter.samsung.com/content/SW/201206/20120620051748445/Verizon_Wireless_I535_GSIII_Samsung_USB_Driver_v1_4_6_0.exe
Hope this helps..
I think I found the problem (its not the phone)
its the drivers that samsung issued
I plugged the phone on my win 7 64 bit desktop (not installing any drivers beforehand) and I got a few failed messages for drivers but I was able to access the file system fine
I then installed the driver pack posted and above then got the mtp driver installation failed message and was unable to access the file system
uninstalled the driver pack and connected the phone back up and I can access the file system (with some other drivers failing to install, I think relating to usb modem stuff ect...)
so until samsung fixes the driver problem I will have to deal with a few driver installation failed message every time I hook up the phone, but at least I can access the file system
im running the phone on the stock ics btw, didnt install cm10 or anything like that, the phone is rooted though but I rooted it after I found out about the mtp driver problem so it shouldnt mean anything
I have the same problem on Windows 7 32 bit. I rooted my phone and installed samba as a temporary fix.
Plus I just bought an external 32 GB SD card and I plan on using that as my workaround and just transfering files between the two.
Sent from my SCH-I535 using Tapatalk 2
Problem for me was the root.
Could you humor me and try this:
- go into the superuser app
- Select the 'temp unroot' checkbox from the first screen.
- unplug then replug the USB cable on your phone. The drivers should install on the first try this time (they did for me) and Kies should work too.
The problem seems to be that SuperUser exploits the USB Debug internally so, even though USB Debug is unchecked, it is still detected as checked by the connection and fails the install of the driver.
Solution #2 is the amazing script that transforms your MTP connection into a UMS one (look in this thread http://forum.xda-developers.com/showthread.php?t=1785243 and thank open1your1eyes0 ). Once in UMS, you don't need the MTP driver to see your device so that's another approach.
Good luck
I bought Samsung Galaxy S3 2 weeks ago. Windows installed the drivers for it when first connected to my Windows 7 64 bit PC. It came up in the list of Devices on the Explorer. I installed "Kies_2.5.0.12094_28_8" which installed USB driver on top of the Windows driver. At the end of the installation, it gave "failure to install Samsung MTP driver".
Saw a thread on other forum where it was suggested to remove the driver from System Driver window under Control Tab/System and reboot. To be cautious, uninstalled Kies. Rebooted PC. Windows installed the driver. As soon as Kies was installed the whole issue unfolded again.
Looks like ALL Kies versions (including previous version of Kies_v2.3.3.12085_7_5) have incompatible and wrong driver which is resulting in this unresolvable situation.
I removed the MTP driver (control panel/system/device manager - MTP driver has ? mark - this is the one). Then removed the phone and rebooted PC. After reboot, connected the phone back. Windows detected the device and automatically installed the driver. The device is listed in Explorer and is fully accessible. Started Kies. It showed the device as GT-I9300. It took a while and connected to the phone. All functions became useable. Sync'ed the contacts etc.
Day2. Booted the PC. Device is still shown in Explorer. Kies shows GT-I9300 and then displays "Connecting Device" - IT FAILS TO CONNECT and on pressing "Trouble shooting" button, it re-installs its own drivers and fails to install MTP driver AGAIN" - the Kies software SUCKS
Solved! For real!
For some reason, any of those options helped me to make it work:
- Reinstall Windows Media Player
- Remove registry key
- Clean up old usb drivers
- re-install 100 times drivers from Verizon, Samsung. Even old versions.
- Install from Windows Update. I tried to do that 1000 times. Gosh!
- enable UMT access (mass storage) on the phone.
The only thing that worked was, for some reason , getting the drivers from a random computer that was the only computer that worked.
Windows 7 x64
Attached the files. Go to the devices manager and update the drivers.
Israel Leite
How I solved it
Joey22688 said:
I just got a S3 yesterday but was greeted with the dreaded MTP driver installation failed message on win 7 (32 bit)
I installed the regular verizon s3 drivers from samsung's site, did the same thing, uninstalled and tried Kies and let it install the drivers, same problem
tried a different usb port, same thing
restarted the comp and computer, still no go
im getting frustrated now
it seems samsung has known about this issue for over a month now but still hasnt been able to fix it
my a500 and galaxy nexus work fine with MTP so not sure why this would mess up
ive looked at other threads but there was no clear solution on how to fix it
Click to expand...
Click to collapse
1. Un-install Samsung Kies and USB drivers
2. Then install the Install Samsung Usb driver for mobile phones version 1.4.6.0
3. with phone un-pluged from the usbcable Go into settings/Developer Options un-check Stay Awake un-check USB debugging un-check Allow mock locations Now hit the HOME button then plug in the USB cable and your are set..
This worked perfectly painless for me :laugh:
Solution x Win XP
This solution worked for me.
Install microsoft patch for usb and reinstall MTP driver
see:
http://forum.xda-developers.com/showthread.php?t=1150211
Hope this helps
***ONLY FOR RELAYS RUNNING ICS 4.0.4***
Samsung had just released the official Jelly Bean 4.1 update for this phone on April 22 or so and this root method only works for Ice Cream Sandwich devices.
I know there's already a thread of how to root the ICS Samsung Galaxy S Relay 4G which is right here: http://forum.xda-developers.com/showthread.php?p=34515281 but I thought that it may be hard for some people to do it without a visual tutorial. Here's my helpful tutorial video of how to root the Samsung Galaxy S Relay 4G: https://plus.google.com/u/0/108388305247615258469/videos <-- You can easily find the video because it's the only video on that album.
Files Needed:
Winrar: http://www.win-rar.com/download.html?&L=0
Odin v3.07: http://www.4shared.com/zip/CGo6TP1O/Odin307.html? or for the latest and updated versions: http://forum.xda-developers.com/showthread.php?t=1738841
Rooted System IMG: http://www.4shared.com/rar/nhGK59WR/SGHT699_rootedtar.html?
CWM File: http://www.4shared.com/zip/wLHTlktW/cwmtar.html?
If none of the links above work, message me at [email protected] or reply to this topic and I will reupload the files.
Steps:
1) On your phone, go to Settings-->Developer Options and turn on USB Debugging.
2) Turn off your phone and put it in Download Mode/Odin mode.
3) Download the odin307, sght699_rooted.tar, and that cwm.tar files from the links given above.
4) Extract all the files with WinRAR or other file extracting programs.
5) Open Odin v3.07
6) Make sure that it says "Added!" on the bottom left box. If it doesn't say Added, unplug and plug your phone from the computer.
7) Deselect/Uncheck "Auto Reboot" and "F. Reset Time"
8) Click on Phone and a pop up should come up.
9) Find the SGHT699_rooted folder that you extracted in Step 4 and open the file inside it.
10) Click Start. This will take a while but it should not take more than 14 minutes.
11) Once it's done, click Reset.
12) Unplug and plug your phone again. It should say "Removed!" when unplugged and "Added!" when plugged on the bottom left box.
13) Deselect/Uncheck "F. Reset Time" but this time, keep the "Auto Reboot" marked/checked.
14) Click on PDA and a popup should come up.
15) Find the cwm folder that you extracted in Step 4 and open the cwm.tar.md5 file.
16) Click Start.
Once it finishes, your phone should reboot and be rooted. To check if it is actually rooted, go on Applications and find Superuser. If it is there, then you are rooted. Enjoy!!
Very nice. You are missing information, need to add the original posts/threads for the files that you mirrored so we can get version numbers and dates associated with the downloads. Feel free to edit the wiki in my sig if you want to help!
Ok. Thanks, but there's a problem. The files I mirrored other than Odin v3.07 are gone. The original link where the original tutorial was is gone. I had the link in my bookmarks but when I click on it, the webpage is unavailable. Ive tried viewing it from other computers and devices and it still wont work. So I decided to make a new one. Thanks again! The links should be updated in a few.
Sent from my SGH-T699 using xda app-developers app
Thanks.
Version is UVAMA2?
Sent from my SGH-T699 using xda premium
XIAOSpider said:
Thanks.
Version is UVAMA2?
Sent from my SGH-T699 using xda premium
Click to expand...
Click to collapse
What's UVAMA2?
USB won't connect properly; want to un-root
You're rooting video was very helpful.
However, now that the phone is rooted, when I try to connect to my computer with USB cable, I get error message to the effect that the computer can't recognize the hardware ID of the device, so can't back-up the files on the phone or the SD card. I have all the latest Samsung USB drivers, and the computer recognizes that a Samsung device is connected, but the USB connection fails anyway.
How do I un-root the phone - do I have to boot up in download mode and use ODIN? Will this wipe my data, or just go back to the unrooted ROM and keep my data intact?
-----------
Chrizuki said:
I know there's already a thread of how to root the Samsung Galaxy S Relay 4G which is right here: http://forum.xda-developers.com/showthread.php?p=34515281 but I thought that it may be hard for some people to do it without a visual tutorial. Here's my helpful tutorial video of how to root the Samsung Galaxy S Relay 4G: http://www.youtube.com/watch?v=GKgemJTeRWo
Files Needed:
Winrar: http://www.win-rar.com/download.html?&L=0
Odin v3.07: http://www.4shared.com/zip/CGo6TP1O/Odin307.html? or for the latest and updated versions: http://forum.xda-developers.com/showthread.php?t=1738841
Rooted System IMG: http://www.4shared.com/rar/nhGK59WR/SGHT699_rootedtar.html?
CWM File: http://www.4shared.com/zip/wLHTlktW/cwmtar.html?
If none of the links above work, message me at [email protected] or reply to this topic and I will reupload the files.
Steps:
1) On your phone, go to Settings-->Developer Options and turn on USB Debugging.
2) Turn off your phone and put it in Download Mode/Odin mode.
3) Download the odin307, sght699_rooted.tar, and that cwm.tar files from the links given above.
4) Extract all the files with WinRAR or other file extracting programs.
5) Open Odin v3.07
6) Make sure that it says "Added!" on the bottom left box. If it doesn't say Added, unplug and plug your phone from the computer.
7) Deselect/Uncheck "Auto Reboot" and "F. Reset Time"
8) Click on Phone and a pop up should come up.
9) Find the SGHT699_rooted folder that you extracted in Step 4 and open the file inside it.
10) Click Start. This will take a while but it should not take more than 14 minutes.
11) Once it's done, click Reset.
12) Unplug and plug your phone again. It should say "Removed!" when unplugged and "Added!" when plugged on the bottom left box.
13) Deselect/Uncheck "F. Reset Time" but this time, keep the "Auto Reboot" marked/checked.
14) Click on PDA and a popup should come up.
15) Find the cwm folder that you extracted in Step 4 and open the cwm.tar.md5 file.
16) Click Start.
Once it finishes, your phone should reboot and be rooted. To check if it is actually rooted, go on Applications and find Superuser. If it is there, then you are rooted. Enjoy!!
Click to expand...
Click to collapse
nosch454 said:
You're rooting video was very helpful.
However, now that the phone is rooted, when I try to connect to my computer with USB cable, I get error message to the effect that the computer can't recognize the hardware ID of the device, so can't back-up the files on the phone or the SD card. I have all the latest Samsung USB drivers, and the computer recognizes that a Samsung device is connected, but the USB connection fails anyway.
How do I un-root the phone - do I have to boot up in download mode and use ODIN? Will this wipe my data, or just go back to the unrooted ROM and keep my data intact?
-----------
Click to expand...
Click to collapse
Oops, sorry. Forgot the part of your reply that said you've installed all the drivers. What do you mean by it can't recognize it? Does the SGH-T699 still show up on your My Computer?
If you want to unroot, go here: http://forum.xda-developers.com/showthread.php?t=2166242
Just follow the steps and no, it won't wipe out all your data (Well, it didn't wipe mine, but I'm sure it won't.)
Sent from my SGH-T699 using xda app-developers app
Problems connecting with USB (MTP driver install failure)
Chrizuki said:
Oops, sorry. Forgot the part of your reply that said you've installed all the drivers. What do you mean by it can't recognize it? Does the SGH-T699 still show up on your My Computer?
If you want to unroot, go here: http://forum.xda-developers.com/showthread.php?t=2166242
Just follow the steps and no, it won't wipe out all your data (Well, it didn't wipe mine, but I'm sure it won't.)
Sent from my SGH-T699 using xda app-developers app
Click to expand...
Click to collapse
When I connect the USB cable, Windows has a popup message that says:
" Hardware ID missing
Windows cannot identify the device plugged into the Samsung Mobile USB Composite Device.
For assistance, contact the hardware manufacturer"
Sometimes it tries - and fails - to install the MTP device driver.
However, when I go into Windows Device Manage, it does list SAMSUNG Android Phone | SAMSUNG Android ADB Interface, and when trying to update its drivers, it says I have the most up to date ones installed.
- What does "Hardware ID missing" mean? How do I get the phone to communicate with the computer using USB?
I thought it might have to do with Android Ice Cream Sandwich and the media device (MTP) protocol for USB, but, I had no problems getting the computer to recognize my son's (unrooted) Galaxy S 3, which also has ICS and is pretty similar to the Galaxy S Relay 4G. That's why I suspect the problem is with my rooted version.
Is there anything else I should try before un-rooting the phone?
nosch454 said:
When I connect the USB cable, Windows has a popup message that says:
" Hardware ID missing
Windows cannot identify the device plugged into the Samsung Mobile USB Composite Device.
For assistance, contact the hardware manufacturer"
Sometimes it tries - and fails - to install the MTP device driver.
However, when I go into Windows Device Manage, it does list SAMSUNG Android Phone | SAMSUNG Android ADB Interface, and when trying to update its drivers, it says I have the most up to date ones installed.
- What does "Hardware ID missing" mean? How do I get the phone to communicate with the computer using USB?
I thought it might have to do with Android Ice Cream Sandwich and the media device (MTP) protocol for USB, but, I had no problems getting the computer to recognize my son's (unrooted) Galaxy S 3, which also has ICS and is pretty similar to the Galaxy S Relay 4G. That's why I suspect the problem is with my rooted version.
Is there anything else I should try before un-rooting the phone?
Click to expand...
Click to collapse
Install kies or the USB driver directly from samsung.com. Try the USB driver first, then kies if it doesn't work.
Nocturin said:
Install kies or the USB driver directly from samsung.com. Try the USB driver first, then kies if it doesn't work.
Click to expand...
Click to collapse
Already tried both. USB driver is OK, the problem is with MTP. Kies only works via WiFi; does not recognize device with USB. I also tried Samsung tech support's suggestions, none of which changed the situation
nosch454 said:
Already tried both. USB driver is OK, the problem is with MTP. Kies only works via WiFi; does not recognize device with USB. I also tried Samsung tech support's suggestions, none of which changed the situation
Click to expand...
Click to collapse
Have you tried downloading the SDK Manager from "http://developer.android.com/sdk/index.html"? Open the big file that you just downloaded and open up SDK Manager. Install the Google USB Driver and as well as the Android SDK Tools and Android SDK Platform-tools. Once downloaded, go back to the android-sdk-windows folder and go to the "platform-tools" folder inside and hold Shift and right click on "adb" and select "Open Command Window Here" of something like that. The command prompt will open. Type in "adb devices" and tell me what comes up. If you see your device(It should be a bunch on numbers and letters) on there, it means it is recognizable. This might not solve your problem as I do not know what "Hardware ID missing" exactly is. But I will do some research.
I did as you suggested, and was able to see my phone when I ran "adb devices" from the command prompt. And, Windows, recognizes it too, because when I click on the button to remove attached USB devices, it lists SAMSUNG_Android_SGH-T699. But, I still get the hardware ID missing message whenever I connect the USB cable. Frustrating! But, thanks for trying to help me - you seem very knowledgeable.
What you can try and do to fix the USB hardware error is go to control panel then go to "uninstall a program" and uninstall the samsung driver once you uninstalled it reconnect your phone and let it reinstal the files and i believe it should fix your problem
Samsung Noob here with a question.
Ok, I know this is gonna sound kinda noobish, but I come from HTC phones, and this is my first Samsung. Do I need to flash ClockworkMod Recovery on this, or do I flash a rom to the 4G Relay using Odin? If I use Odin, can someone give a quick overview on how?
Gh0sTly said:
Ok, I know this is gonna sound kinda noobish, but I come from HTC phones, and this is my first Samsung. Do I need to flash ClockworkMod Recovery on this, or do I flash a rom to the 4G Relay using Odin? If I use Odin, can someone give a quick overview on how?
Click to expand...
Click to collapse
you'll need to install a recovery as you did on HTC as ROMs usually come as recovery-flashable zips.
there's a cwm recovery available here which can flashed using Odin. If you don't like the cwm on the relay you can flash TWRP from cwm over it. TWRP comes with more options and the touchscreen-control you might be used to.
from (any) recovery you can just install update zip-files just as you used to on your HTC.
I had used the "howto root the Galaxy S Relay" thread, and then realized, I should just SU and reboot recovery. :victory:
nosch454 said:
I did as you suggested, and was able to see my phone when I ran "adb devices" from the command prompt. And, Windows, recognizes it too, because when I click on the button to remove attached USB devices, it lists SAMSUNG_Android_SGH-T699. But, I still get the hardware ID missing message whenever I connect the USB cable. Frustrating! But, thanks for trying to help me - you seem very knowledgeable.
Click to expand...
Click to collapse
If anybody else got this error do the following:
- uninstall all samsung drivers / software
- connect your phone to the pc
- the driver installation should 'fail', but you can access the storage
- install the samsung drivers now while phone is plugged in
After the installation the phone will be recognized and everything is fine - this worked twice for me now, so I guess it should do it.