i need help, i have tried everywhere and can't find anything and any help would be greatly appreciated
i'm on the road to root my samsung galaxy fascinate and have ran into a laundry list of problems. i have rooted many android phones coming from eclair, froyo, and gingerbread, but seem to be stuck at the slightest of problems when it comes to the fascinate.
i can not install the drivers to the fascinate. i have searched through the web for all the drivers and have tried every possible galaxy driver. the driver simply won't install on my windows 7 prof 64bit machine. i have never ran into this problem before with any other phone. every time i try to install the driver it gets to the very end of the install then pops up with the message "windows was unable to install the driver"
It also gave me the option to view the failed windows installation log, which after many successful steps, at the end the log shows this error:
Action ended 1:26:53: ShowMsiLog. Return value 0.
=== Logging stopped: 12/16/2011 1:26:53 ===
MSI (c) (0C:08) [01:26:53:750]: Product: SAMSUNG USB Driver for Mobile Phones -- Installation operation failed.
MSI (c) (0C:08) [01:26:53:750]: Windows Installer installed the product. Product Name: SAMSUNG USB Driver for Mobile Phones. Product Version: 1.3.550.0. Product Language: 1033. Manufacturer: SAMSUNG Electronics CO., LTD.. Installation success or error status: 1603.
i have also attached the entire log
the first thing i did was plug in the phone, which windows sensed this and automatically installed a driver, not sure which. after this i unplugged the phone and then checked "usb debugging" for rooting purposes and plugged the phone back into the computer which windows then installed another driver automatically, then following the steps from xda to root the phone, i downloaded the given drivers which is where the problem first occurred and the drivers were unable to download.
I'm simply trying to get root access to the phone and can't do anything with the phone with crappy drivers...i can't even mount usb sd card now to transfer data anymore. the drivers have completely been shot. i desperately need help. please
also what is the absolute easiest way to root the fascinate? is it with one click root or with Odin? Because the fascinate just updated itself from 2.2.2 EH05 to 2.3.5 EH03 and i'm not sure which program supports rooting which version of android. also all other android devices simply give root access to the stock rom, which is great cause i get to keep all my apps, messages, contacts...etc, then simply titanium backup everything and transfer it over to the new rom. is it different with the fascinate? will rooting the device simply flash a completely new rooted rom? therefore loosing everything? if anybody has any answers to any of these questions, please be my hero. thanks
Uninstall everything you previously installed in the way of Samsung drivers (in fact, you could use Windows 7 backup and restore to restore your PC to the state it was in the day before you installed the drivers as they are sometimes hard to uninstall completely). Reboot and simply plug your phone (with USB debugging of course), and let Windows automatically install the drivers for you like it did before you installed the ones linked to on XDA. This time, if your PC recognizes your phone, just keep the drivers you have and don't install the ones linked to. Those drivers from the guide are for those whose PC doesn't automatically install working drivers. From that point, just follow the rest of the guide and skip the install drivers part. You will not have to install any further drivers unless you flash an AOSP ROM, in which case you'll have to follow the instructions in the OP of the ROM thread. I hope this works for you.
Has anyone seen John Connor?
awesome thank you, i will try this out, and if this doesnt work i can always try another pc.
and as to the question of rooting the fascinate, like i said before i've never had a phone that has been wiped when i got root access initially, but it seems that everyone is saying that a rooted rom must be flashed from Odin in order to have root access. In other builds it seem that all is done is busybox and superuser are just pushed to the phone. will the fascinate be wiped when initial root is acquired?
bigwhat said:
awesome thank you, i will try this out, and if this doesnt work i can always try another pc.
and as to the question of rooting the fascinate, like i said before i've never had a phone that has been wiped when i got root access initially, but it seems that everyone is saying that a rooted rom must be flashed from Odin in order to have root access. In other builds it seem that all is done is busybox and superuser are just pushed to the phone. will the fascinate be wiped when initial root is acquired?
Click to expand...
Click to collapse
root is not flashed via odin, rather cwm is...then the root file su_2.6.3.1 is flashed via cwm. If you need directions section 5 of my guide in general section has it covered...everything needed is there including the correct recovery and root file.
I will tell you what...the Fascinate is probably the biggest pain in the ass phone...I tried forever to root my friends and couldn't get it done...need to try again I guess, but it was a driver issue as well..ODIN just wouldn't recognize the dam phone
Use Droidstyles guide. Very easy to follow. Also, the USB cable for some reason seams to be a bit finicky at times with this device. Unplug from phone and replug. Sounds odd but trust me, I have done this many times.
Sent from my SCH-I500 using XDA App
I am having a problem too and it's not covered anywhere i've seen to date. I've got an XP and a Win7 box at home. On both, I've tried with no drivers and i've tried with every other driver set I can find and every time I hook the phone up to the machine it pops up saying USB device couldn't be recognized or something. I'm going nuts! I've never had so much difficulty in my life, not even the first time changing ROMs on anything.
Droidstyle- I've seen your guide and unless I missed it doesn't cover this. Have you seen or heard of this and have any ideas at all?
Thanks!
Related
Posted this on the general discussion section but have had no replies, hopefully someone here can help?
Hi everyone, first, this is my first post, new to the forums, at least as a registered user. I have a problem with my phone. I know most of you are wondering why I have not just read the other posts on the forums, but I have. I have attempted every solution to the problem posted previously.
Background: Phone: Samsung charge.
I was being impatient and did not want to wait for the gingerbread update form Verizon. I flashed the leaked gingerbread 2.3.4 onto my phone using odin. Everything went great. I was able to use my phone with no problems except shortened battery life, but nothing major. About a month ago the battery life was impossible to maintain and there were some software bugs, like clicks during calls, startup taking forever, around 2 minutes on average!, and random restarts that never happened before. I decided to look up some fixes and found that verizon and samsung had released GB 2.3.6 for the charge. I got excited and decided I wanted to get that, but I could not via OTA. I read some forum posts and they mentioned attempting a factory reset on the phone then trying OTA update. I went ahead with factory reset and everything went fine. My startup time is around 25 seconds now and no random clicks or gliches, but still not on 2.3.6, which was the whole point. I then decided to just flash the stock 2.3.6 rom to the phone.
Problem: When I plug my phone in to multiple computers it will charge but not connect to the computer. This means on my Mac it does not show as an external drive, which it has in the past. On my windows 7 machine it says that drivers were installed but could not be used (I can get the exact quote if needed.) I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device". I have tried to enter download mode when hooked up to windows computers and no connection is found.
Possible solutions attempted and their outcomes:
1. As stated, I attempted the method shown in a thread on droid forums for installing the samsung drivers. I have attempted multiple times to install the drivers on my windows machine and the device remains "unknown".
2. I have attempted multiple cables on multiple computers, both mac and windows 7. No change.
3. I have installed adb and attempted to locate devices using adb devices command on mac. No devices found.
4. I have attempted all methods with both usb debugging checked and unchecked.
5. I have tried every possible usb port I have.
Ideas/questions I have had that I have no idea are possible or how to fix!
Would a factory reset take away the ability to connect to a computer from my phone. So, is there a piece of software in the build I have that controls the connection between the computer and the phone, an identifier of sorts, which is now missing, now that I have reset the leaked ROM.
Is there a way to flash a new ROM without connecting to a computer, via the sd card, and what is that? I have read some things in other posts but am too much of a n00b to understand most of them when using sdcards.
ANY help will be greatly appreciated. PLEASE PLEASE PLEASE!!! I have been at this for at least 6 hours, sifting through forums, searching google, attempting fixes that others have stated worked for them, only to fail every time. Thank you all.
have you try on a different pc?
maybe on your PC there is some problem with the drivers.
Moreover to connect via
adb u must enable Debug mode on your device in the application menu.
To flash kernel or other directly from your sd you can use the clockwordmode, but to install it you must before
install it and i fear you must use your cable connection
Sent from my GT-I9100 using XDA App
I have tried multiple PCs and a mac, even windows on bootcamp. I have installed drivers on every one, even uninstalled and reinstalled on one. One PC, my laptop was a fresh windows install (it was a linux box but I needed windows to use Odin). I was in debug mode and not in debug mode when attempting adb. Thanks for the suggestions though. As I said, I have tried numerous things and am completely stuck! so frustrating!
"I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device"
Exactly there... you can try to force device to install a different driver.
Double click the unknown device then driver then update driver then find software in your computer then choose manually from a list of device drivers in your computer then show all devices you should see "android adb interface" or something related to google or android.
Try it... i hope this can help you.
Anyone in here can help me please? I tried to root my samsung galaxy player 4.0. I read lots of topics about rooting using superoneclick V2.2. I enable USB debugging mode, unmount my SD, installed samsung kie on my computer, plug in the cable and click connecting. And I run superoneclick.exe as Admin and I click ROOT! But after few mins, few lines show up and the root not work.
Here is the picture of the rooting result after waited few mins, still nothing happen. Please Help, I dont wanna try again until I find out if I did anything wrong. It has something to do with ADB interface or something?
Have you loaded an insecure kernel using Odin?
SusieGalaxy880 said:
Anyone in here can help me please? I tried to root my samsung galaxy player 4.0. I read lots of topics about rooting using superoneclick V2.2. I enable USB debugging mode, unmount my SD, installed samsung kie on my computer, plug in the cable and click connecting. And I run superoneclick.exe as Admin and I click ROOT! But after few mins, few lines show up and the root not work.
Here is the picture of the rooting result after waited few mins, still nothing happen. Please Help, I dont wanna try again until I find out if I did anything wrong. It has something to do with ADB interface or something?
Click to expand...
Click to collapse
The easiest way to gain root would be to flash a ROM that has root already. Such as this stock ROM: http://forum.xda-developers.com/showthread.php?t=1512331
nop, duno what is that. Im new android user, I only have this device for few days. In youtube video, those ppl never mention any other step.
1) install samsung kie
2) enable USB debugging mode
3) unmount SD card
4) pluged in usb cable (i click connect on my device, it is in mass storage, or I shouldn't have to click anything? I Just plug in the cable and hit root on superoneclick?)
These kinda more difficul steps,, and i dont wanna mess any of those because if any step goes wrong, I duno how to fix it. Aren't most people use the easy way to superoneclick to root and successful? I just want to know which step I did wrong for my fail root. I dont wanna mess with any deeper or more diffiuclt stuff.
SusieGalaxy880 said:
nop, duno what is that. Im new android user, I only have this device for few days. In youtube video, those ppl never mention any other step.
1) install samsung kie
2) enable USB debugging mode
3) unmount SD card
4) pluged in usb cable (i click connect on my device, it is in mass storage, or I shouldn't have to click anything? I Just plug in the cable and hit root on superoneclick?)
Click to expand...
Click to collapse
You shouldn't have connected mass storage.
I think my problem is the driver not propertly installed + I click connect to mass storage on the device.
I heard we need
1) Microsoft.NET Framework 4+ (I have win 7, so already has)
2) Samsung USB driver to mobile phone (samsung Kies come with that usb driver.)
3) Do I also need to install the Android SDK/ADB driver?
SusieGalaxy880 said:
I think my problem is the driver not propertly installed + I click connect to mass storage on the device.
I heard we need
1) Microsoft.NET Framework 4+ (I have win 7, so already has)
2) Samsung USB driver to mobile phone (samsung Kies come with that usb driver.)
3) Do I also need to install the Android SDK/ADB driver?
Click to expand...
Click to collapse
From my experience just have Windows 7 doesn't ensure have framework 4+ so check for a download on that.
If your USB debugging mode is ON then you shouldn't get the "connect mass storage" option on the device at all, so double check that (uncheck and recheck it if necessary.
Personally I choose to skip Kies entirely and just download the drivers only, but the first time you plug the player in with Debugging on windows should do it driver search thing down by the clock and it installs (i think 3) different drivers for the player (different then the mass storage driver) if you jumped in to superoneclick before that finished that may have been part of the problem, if you didn't get those to install then sounds like a driver issue.
I just tried the 2nd time, the result is the same. FAILED!!!
I window update everything including the microsoft.NET framework 4+. Restart computer.
Uninstall samsung kies and the prior samsung driver, and I downloaded the newer V1.4 Samsung USB driver for mobile phone from XDA forum and installed, restarted computer.
I didnt press any key while on the device to get into mass storage mode.
I plug in the cable, on USB debugging mode + unmount SD card.
I wait for driver software installation "READY TO USE" as u can see in the new picture, with all the check mark on. This time i though I can make it throught, but as u can see the result on left side, almsot similar result. =(
"No such file or directory" not an single OK. If successuf rooting, i see people get 'OK' on each step. This time i really follow each every step, still fail!!!
I have no idea what is the problem? Everyone seem successful ROOT first time.
Did I miss an very important step or my device already mess up somehow?
I only didnt install ADB driver, but no one talk about needed to install that before ROOTING.
SusieGalaxy880 said:
I just tried the 2nd time, the result is the same. FAILED!!!
I window update everything including the microsoft.NET framework 4+. Restart computer.
Uninstall samsung kies and the prior samsung driver, and I downloaded the newer V1.4 Samsung USB driver for mobile phone from XDA forum and installed, restarted computer.
I didnt press any key while on the device to get into mass storage mode.
I plug in the cable, on USB debugging mode + unmount SD card.
I wait for driver software installation "READY TO USE" as u can see in the new picture, with all the check mark on. This time i though I can make it throught, but as u can see the result on left side, almsot similar result. =(
"No such file or directory" not an single OK. If successuf rooting, i see people get 'OK' on each step. This time i really follow each every step, still fail!!!
I have no idea what is the problem? Everyone seem successful ROOT first time.
Did I miss an very important step or my device already mess up somehow?
I only didnt install ADB driver, but no one talk about needed to install that before ROOTING.
Click to expand...
Click to collapse
have you tried resarting your player then enable usb debugging then plugging in the USB?
Also where did you get your Superoneclick?
I didnt restart my device before rooting.
I got the superoneclick from XDA main page the offical one with 500+ page of posts and reply. "Superoneclickv2.2 -shortfuse.zip"
Try using doomlords rooting toolkit, it worked for me.
http://forum.xda-developers.com/showthread.php?p=18805532
thanks for info, but I duno how to use the DooMLoRD's Easy Rooting Toolkit. Any instruction? I have no idea why my device is so diffiuclt to root, as other people rooted very easy
I used version 2.3.3 to root mine.
Got to shortfuse.org and scroll down to the 2.3.3 download link.
I tired the 3rd time today, failed again, same outcome. This time I follow each step carefully, and I used superoneclick v2.3.3 Before ROOT, I make sure all the "READY TO USE" check mark on. But still hang at Shell Rooting device step #5. I patient waited for 20mins, still hang at this step.
I shoulda try root when I got it first day. Is there possible some mess up app might cause this? I never heard anyone have any diffiuclty Rooting their galaxy player 4.0 YP-G1 US version with superoneclick after so many tried. I officially give up. I only have this device for 1 week..............
Kernal Version 2.6.35.7-G1UEKI8-CL562400 [email protected] #2
Build # Gingerbread.UEKI8
Firmware V2.3.5
Model Number: YP-G1
I found a very important issue might cause this failed. When I check the unzip folder, the Expoits folder IS NO FILE, EMPTY, but when I check the original zip file, it has 3 important files "GingerBreak,psneuter, zergRush" files (on the v2.2) I try unzip on desktop, pull out this Exploit folder, pull out the file, none work. I even uninstall winRAR and restall the newer version. These 3 files on the exploit folder in superoneclick v2.2 seem CANNOT pull out of the zip file no matter what I try. I think on shell Rooting device step #3 started the problem cuz cannot locate these few important exploit files. I just found out the unzip folder have no those file (psneuter,zergRush), while the original zip file has, and I cannoot pull out those file out of the zip folder NO MATTER WHAT I TRIED. Both superoneclick v2.2 and v2.3.3 exploit folder, i cannot get those file out of the zip folder.
Got rooted successful the 4th tired. Problem is my antiviurs always remove the psneuter & zergRush files in exploit folder when I extract everytime. And I didnt notice this problem. So I was rooting without these 2 important files in superoneclick folder. Now I disable antivirus, so i can extract those file and start rooting, after done rooting, i turn antivirus back on.
another problem
daniel644 said:
have you tried resarting your player then enable usb debugging then plugging in the USB?
Also where did you get your Superoneclick?
Click to expand...
Click to collapse
can someone help me i have the ``firmware uprade encountered....``
i can go to the the warning but
-if i press up to continue it return to firmware....
-if i press down the same thing
thanks.
THE PROBLEM HAS BEEN SOLVED!
If you have the MTP usb device driver error (code 10), then scroll down and try what worked for me.
Sparrow245 said:
So, I used Odin to reset my vibrant back to stock 2.1. I then tried to get it to 2.2 using Samsung Kies, but when ever I try to use it, MTP Device fails to install. Anyone know how to get the driver to install / work correctly so that I can use Kies? Thank you in advance.
Click to expand...
Click to collapse
You should really avoid using kies if possible. It is notorious for hard bricking phones, meaning they become paper weights if something goes wrong. You should install clockwork mod recovery and install a custom 2.2 ROM, there are literally tons to choose from and they are pre-rooted. Some of the custom ROMs have odin images so you could actually skip the clockwork recovery step. I'll link you to the 2.2 ROM I'm using or you can search for something different. Here is Axura 2.2, use the odin image in the 3rd post http://forum.xda-developers.com/showthread.php?t=1787267.
EDIT- if you also need drivers for your phone then go here http://forum.xda-developers.com/showthread.php?t=728929
Sent from my SGH-T959 using Tapatalk
If you want 2.2 (Froyo) installed on your Vibrant, like the other poster said, there are literally tons of great builds.
Here is a link to one that I really liked, it had great battery life, and overall good performance. Bionix V - http://forum.xda-developers.com/showthread.php?p=21324042
As stated above, please avoid using the Kies software, it generally creates many more problems than it is worth.
I've used Kies many times, so I know what I'm doing. But apparently this time something about the MTP driver isn't going alright. Could be that I have this fairly new computer? I've already tried installing the vibrant drivers, but for what ever reason I keep getting a code 10 error for the MTP usb device. :/
Well if your not doing so already, try running the program as administrator.
However, not sure why you are so hell bent on running the stock Froyo via Kies, when there are so many other amazing Froyo/GB/ICS/and now JB custom ROMs that work MUCH much better, and have way better support than Samsung could ever provide.
However, to each his own. Good luck to you with your endeavors!
Which ROM I want has nothing to do with my question. The problem is the MTP usb device, which apparently fails to start. (Code 10)? I've seen that it's a common problem, but there isn't any one definite answer. I was hoping maybe someone here knows how to fix it?
I know the thread is for a tablet, not sure which version of windows your running, but maybe something lime this is what you are looking for: http://forum.xda-developers.com/showthread.php?t=1150211
Sparrow245 said:
Which ROM I want has nothing to do with my question. The problem is the MTP usb device, which apparently fails to start. (Code 10)? I've seen that it's a common problem, but there isn't any one definite answer. I was hoping maybe someone here knows how to fix it?
Click to expand...
Click to collapse
Google code 10 error mtp
You should find a link that says fixed code 10 mtp error Samsung galaxy
It is a post on android forums or phandroid??? You should see it and it should fix your error.
sent from my magic box to yours
Ah! Finally found a solution! Not sure if this will work for everyone, but it worked for me.
1. Plug up your phone like usual. Connect with Samsung Kies. Obviously, you will get get MTP code 10 error.
2. Go to the device manager, and then uninstall the driver. Unplug your phone.
3. Go to c:\windows\system32\drivers and rename wudfrd.sys and winusb.sys to wudfrd1.sys and winusb1.sys respectively.
3. Plug your phone back in, and connect with Kies.
4. The computer will try and install the driver again, but fail.
5. Go to the device manager again, and attempt to update the driver. It should fail, and you should get a (code 28) error this time. Make sure you have a code 28 error!
6. Go back to c:\windows\system32\driver and rename the 2 files back to it's original names.
7. Go to c:\windows\inf and look for a file named wpdmtp.PNF. Take the file, and move it somewhere else (like your desktop) don't delete it.
8. Now go to the MTP usb device again, and attempt to update drivers. It should update, and recognize your device now.
This is what worked for me, I don't know if it will work for you. I'm not responsible for anything that goes wrong.
Sparrow245 said:
I've used Kies many times, so I know what I'm doing.
Click to expand...
Click to collapse
When kies hard bricks your phone I'll be here to say I told ya so. Its really an unnecessary risk but its your phone, good luck.
Sent from my SGH-T959 using Tapatalk
@sparrow, that's exactly what I read but it was to much to type.
sent from my magic box to yours
Please Help
hey man did you ever get the MTP driver to start? I am still at a loss with this myself.
Sparrow245 said:
Which ROM I want has nothing to do with my question. The problem is the MTP usb device, which apparently fails to start. (Code 10)? I've seen that it's a common problem, but there isn't any one definite answer. I was hoping maybe someone here knows how to fix it?
Click to expand...
Click to collapse
Sparrow245 said:
Ah! Finally found a solution! Not sure if this will work for everyone, but it worked for me.
1. Plug up your phone like usual. Connect with Samsung Kies. Obviously, you will get get MTP code 10 error.
2. Go to the device manager, and then uninstall the driver. Unplug your phone.
3. Go to c:\windows\system32\drivers and rename wudfrd.sys and winusb.sys to wudfrd1.sys and winusb1.sys respectively.
3. Plug your phone back in, and connect with Kies.
4. The computer will try and install the driver again, but fail.
5. Go to the device manager again, and attempt to update the driver. It should fail, and you should get a (code 28) error this time. Make sure you have a code 28 error!
6. Go back to c:\windows\system32\driver and rename the 2 files back to it's original names.
7. Go to c:\windows\inf and look for a file named wpdmtp.PNF. Take the file, and move it somewhere else (like your desktop) don't delete it.
8. Now go to the MTP usb device again, and attempt to update drivers. It should update, and recognize your device now.
This is what worked for me, I don't know if it will work for you. I'm not responsible for anything that goes wrong.
Click to expand...
Click to collapse
This is the steps used to fix.
Sent from my SCH-I535 using xda premium
Now is really solved.
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
Sparrow245 said:
Ah! Finally found a solution! Not sure if this will work for everyone, but it worked for me.
1. Plug up your phone like usual. Connect with Samsung Kies. Obviously, you will get get MTP code 10 error.
2. Go to the device manager, and then uninstall the driver. Unplug your phone.
3. Go to c:\windows\system32\drivers and rename wudfrd.sys and winusb.sys to wudfrd1.sys and winusb1.sys respectively.
3. Plug your phone back in, and connect with Kies.
4. The computer will try and install the driver again, but fail.
5. Go to the device manager again, and attempt to update the driver. It should fail, and you should get a (code 28) error this time. Make sure you have a code 28 error!
6. Go back to c:\windows\system32\driver and rename the 2 files back to it's original names.
7. Go to c:\windows\inf and look for a file named wpdmtp.PNF. Take the file, and move it somewhere else (like your desktop) don't delete it.
8. Now go to the MTP usb device again, and attempt to update drivers. It should update, and recognize your device now.
This is what worked for me, I don't know if it will work for you. I'm not responsible for anything that goes wrong.
Click to expand...
Click to collapse
Thanks a ton...saved my day.
Hello,
I am new to these forums, therefore I cannot post into a Development thread.
I rooted and flashed a ROM on my phone (Genome 2.0 to be specific.)
It was a fine ROM, but I actually prefer Sense 4.1+ for right now and wish to go back to stock due to support reasons for my company as well. I saw a thread where you can use RUU. However, I cannot get the program to detect my phone (the dreaded error 170.) I also am in the process of using the ZIP file method where you grab it from the temp while RUU is open (getting it on my SD card has been another story.)
However, in the event I cannot get this to work, can someone who has got their DNA back to stock from root/ROM please give me some troubleshooting for the drivers? HTC Sync isn't detecting my DNA when there are no drivers. I wish to know how to remove ALL drivers for this phone from the device manager so it is as if I never had this device connected to my PC. I believe if I had these removed, it may help a lot of the issues I am having.
After hours (about 5 hours total) of checking into this, I figured out that it was trying to install the windows USB drivers for whatever reason. I just manually uninstalled whatever drivers it was trying to install (in this case, it showed up as Android 1.0 in the device manager.) I reinstalled it and manually browsed to the HTC folder in x86 Program Files after downloading and installing HTC Sync. It installed these drivers, showed up as MyHTC Phone, and I profited from my bloated factory Sense 4.1+ phone
In case anyone else was wondering, here are the steps:
http://forum.xda-developers.com/showthread.php?t=2017525
Let me amend his steps:
1. When you boot back into your bootloader, go into Fastboot.
2. Make sure you uninstall any PDANet drivers or all drivers you had on your phone while rooted/ROM'd up.
3. Download HTC Sync Manager and install.
4. Disconnect your phone from USB and reconnect.
5. Install drivers manually from HTC folder in Program files x86.
6. Run RUU.
Going to attempt to unlock the bootloader again, shouldn't have any issues since I took care of that initially before I rooted this phone. I hope that I have solved a few people's issues who might have been like me scourging the internet hopelessly for help.
Hello everyone, I could not find a good title for my issue but I will try to explain as well as I can. I own a GT-I9300 (International), but since last official Samsung's firmware update(Jelly Bean 4.3) I am not able to get my phone recognized by my computer. Phone is connected and it charges, but neither Windows or Ubuntu recognizes it as a portable device. I am concerned about UMS is not available on device, but my phone it does not even get detected! I also own a Galaxy SII (4.1.2) and it does get detected by my PC. I think that flashing a custom ROM could solve the problem, since it appeared when I updated official firmware, but the thing is that I cannot root my phone! Tried ODIN but since my phone does not get detected, ODIN does not do its job. I also tried rooting with framaroot and towelroot, but no success: first one says "Failed , try another exploit" but there is only one. And the last one says my phone is not currently supported, even if I change modstrings.
So here is my question: how do I root my phone? I don't know what else I could try. I have already reinstalled Kies and Samsung USB drivers but still not working. Also hard-resetted but no luck.
Hope you guys can help me out because this is really getting on my nerves
Thanks in advance!
jalt96 said:
Hello everyone, I could not find a good title for my issue but I will try to explain as well as I can. I own a GT-I9300 (International), but since last official Samsung's firmware update(Jelly Bean 4.3) I am not able to get my phone recognized by my computer. Phone is connected and it charges, but neither Windows or Ubuntu recognizes it as a portable device. I am concerned about UMS is not available on device, but my phone it does not even get detected! I also own a Galaxy SII (4.1.2) and it does get detected by my PC. I think that flashing a custom ROM could solve the problem, since it appeared when I updated official firmware, but the thing is that I cannot root my phone! Tried ODIN but since my phone does not get detected, ODIN does not do its job. I also tried rooting with framaroot and towelroot, but no success: first one says "Failed , try another exploit" but there is only one. And the last one says my phone is not currently supported, even if I change modstrings.
So here is my question: how do I root my phone? I don't know what else I could try. I have already reinstalled Kies and Samsung USB drivers but still not working. Also hard-resetted but no luck.
Hope you guys can help me out because this is really getting on my nerves
Thanks in advance!
Click to expand...
Click to collapse
Try with other port and USB cable.
Have you Degugging Android activated in Deceloppers options ?
the other day i tried for hours to get my phone recognised. what did it in the end was trying it on a different pc and it worked
KeTuRr74 said:
Try with other port and USB cable.
Have you Degugging Android activated in Deceloppers options ?
Click to expand...
Click to collapse
I have already tried with every port on my PC. I'm using the USB cable that actually came with the device and it is working when I plug in another phones.
And yes, I have activated USB debugging
sosolid4u09 said:
the other day i tried for hours to get my phone recognised. what did it in the end was trying it on a different pc and it worked
Click to expand...
Click to collapse
The thing is that my phone is the only one that do not get detected every single time I connect it. I have already connected one GT-I9100 and GT-S6790L and both get detected. I already tried on 3 different Virtual Machines with Windows XP, Ubuntu, Windows 8.1 but no luck.
As I said in the first post, I think it's a firmware problem since it appeared when I did the official update, which was this one:
Model GT-I9300
Model name GALAXY S III
Country Argentina
Version Android 4.3
Build date Wed, 05 Nov 2014 20:33:08 +0000
PDA I9300UBUGNK1
CSC I9300UVOUGNK1
MODEM I9300UBUGNK1
jalt96 said:
Hello everyone, I could not find a good title for my issue but I will try to explain as well as I can. I own a GT-I9300 (International), but since last official Samsung's firmware update(Jelly Bean 4.3) I am not able to get my phone recognized by my computer. Phone is connected and it charges, but neither Windows or Ubuntu recognizes it as a portable device. I am concerned about UMS is not available on device, but my phone it does not even get detected! I also own a Galaxy SII (4.1.2) and it does get detected by my PC. I think that flashing a custom ROM could solve the problem, since it appeared when I updated official firmware, but the thing is that I cannot root my phone! Tried ODIN but since my phone does not get detected, ODIN does not do its job. I also tried rooting with framaroot and towelroot, but no success: first one says "Failed , try another exploit" but there is only one. And the last one says my phone is not currently supported, even if I change modstrings.
So here is my question: how do I root my phone? I don't know what else I could try. I have already reinstalled Kies and Samsung USB drivers but still not working. Also hard-resetted but no luck.
Hope you guys can help me out because this is really getting on my nerves
Thanks in advance!
Click to expand...
Click to collapse
I can see your frustration Now a few things technically it is a misconception that you need root to flash a custom rom you can actually flash a custom recovery with Odin full wipe and then flash a custom rom from custom recovery (only thing is you will lose all your data because you need root to back up your data)
Now I know the above statement is not very helpful because as you said Odin doesn't detect it (but I thought I would mention it anyway )
The reason framaroot and towelroot, didn't work is because at the moment the only way to root S3 is with Odin.:crying:
You may have tried this but I will mention it anyway first uninstal Kies and all Samsung drivers from your computer ( kies can interfere with Odin) Then try installing these drivers here >> http://developer.samsung.com/techni...Lhp1GqlWRy92Q60CX6PP1mF!80806326?v=T000000117 << If you have tried this then sorry.
Also when you connect the phone go to Device manager in Windows and try to look for your device ( it may say unkown device) it should have a warning triangle right click on it select update driver software and then select browse from my computer and point to the drivers that you have downloaded see if that works.
Another thing to note is if you are using Windows 8 you need to disable Driver signature in start up options ( Google it) for Windows to recognize the drivers.
tallman43 said:
I can see your frustration Now a few things technically it is a misconception that you need root to flash a custom rom you can actually flash a custom recovery with Odin full wipe and then flash a custom rom from custom recovery (only thing is you will lose all your data because you need root to back up your data)
Now I know the above statement is not very helpful because as you said Odin doesn't detect it (but I thought I would mention it anyway )
The reason framaroot and towelroot, didn't work is because at the moment the only way to root S3 is with Odin.:crying:
You may have tried this but I will mention it anyway first uninstal Kies and all Samsung drivers from your computer ( kies can interfere with Odin) If you have tried this then sorry.
Also when you connect the phone go to Device manager in Windows and try to look for your device ( it may say unkown device) it should have a warning triangle right click on it select update driver software and then select browse from my computer and point to the drivers that you have downloaded see if that works.
Another thing to note is if you are using Windows 8 you need to disable Driver signature in start up options ( Google it) for Windows to recognize the drivers.
Click to expand...
Click to collapse
I already tried uninstalling Kies and Samsung drivers. Also I tried looking for device on Device Manager but it does not appear when I plugin my S3, but it does appear when I connect other devices like S2 or Galaxy Fame Lite. They appear as portable devices.
I'm using Windows 7 on my PC and have already tried with different OS over Virtual Machines and still doesn't work.
And thanks for that note, didn't know there was possible to flash a Custom Recovery without root, but I can't since ODIN doesn't detect device :crying:
Then it looks like you are running out of options I would use another computer not Virtual Machines
Okay I'll give it a try but as I said before, looks like an firmware issue, not computer's. Why would my computer detects two another Samsung devices but not mine (which used to work until last update)
Me, too!
I'm having a similar problem. Last week my GS3 stopped working, and I bought another one from Ebay with a cracked screen and swapped out motherboards. The phone seems to work as well as a stock Verizon phone on Jellybean would, but I can't get my Linux, Win 8, or Win XP computers to even recognize that it's attached. Different cables, each and every one of the USB ports, not even a blip. Device Manager in Windows doesn't even see it, and yes I got the developer options unlocked and have enabled USB debugging.
I've got the Samsung drivers installed, and tried to install the CWM device drivers from the SAMSUNG GALAXY S3 TOOLKIT V9, but there was an error and that didn't work, either.
USB connection issues are usually due to Windows conflicts, driver problems or the lead itself. If all these have been excluded then you have either a firmware issue in the bootloader, which is very uncommon, or a hardware problem. The usb port is easily worn/damaged/dirty also the motherboard might be the cause.
There is no silver bullet to cure, test each possible thoroughly.
boomboomer said:
USB connection issues are usually due to Windows conflicts, driver problems or the lead itself. If all these have been excluded then you have either a firmware issue in the bootloader, which is very uncommon, or a hardware problem. The usb port is easily worn/damaged/dirty also the motherboard might be the cause.
There is no silver bullet to cure, test each possible thoroughly.
Click to expand...
Click to collapse
I'm 100 percent sure that it is not due a Windows issue, I have already test every option. I have not considered the usb port to be damaged or worn, which could be possible but phone charges every time I connect it to computer. It just does not get detected as a device. But in order to assume it is a motherboard issue I will have to put away my feeling that the problem is caused by last OTA official update, since this problem started there.
If it is a firmware update issue, is it any option to flash another ROM?
Sent from my GT-I9300 using XDA Free mobile app
try to install usb drivers on windows and factory reset the mobile before using odin but if u want to root there is al ot of program that dont need comp like root master and towel . search for them in google and if u want a rom i recommend cm rom resurrection
peter wagih said:
try to install usb drivers on windows and factory reset the mobile before using odin but if u want to root there is al ot of program that dont need comp like root master and towel . search for them in google and if u want a rom i recommend cm rom resurrection
Click to expand...
Click to collapse
Sorry but the only option that works to root the S3 international is Odin no apps work at the moment:crying:
tallman43 said:
Sorry but the only option that works to root the S3 international is Odin no apps work at the moment:crying:
Click to expand...
Click to collapse
no man how is it ?? believe me it works try frameroot.apk
peter wagih said:
no man how is it ?? believe me it works try frameroot.apk
Click to expand...
Click to collapse
Not on I9300 international version on other variants yes. Believe me if it worked it would be all over the forums post a link showing who it as worked for thanks..
peter wagih said:
try to install usb drivers on windows and factory reset the mobile before using odin but if u want to root there is al ot of program that dont need comp like root master and towel . search for them in google and if u want a rom i recommend cm rom resurrection
Click to expand...
Click to collapse
As I said on previous posts, I have already installed and reinstalled Samsung USB drivers and made a factory reset -one from config. option and another one from Android stock recovery 3e (since I cannot install any advanced recovery -or even root it- to flash a custom rom). Doing those factory reset did not downgrade my last firmware update (when all my problems started).
I also said on previous posts that I tried towelroot and framaroot with no success. As tallman43 says, seems like international version of S3 does not support those kind of one-click to root apps.
-----------------------------------------------------
So far the only options available (if my theory about latest firmware update is the problematic one) are:
● downgrade firmware: [Q] How? Odin is not working since my phone does not get detected;
● root my phone in order to install an advanced recovery and flash a new ROM: [Q] Any way of rooting phone without computer (apart from towelroot or framaroot because I have tried and do not work for me)? I read one XDA post from 2 years ago to root S3 via console apk but latest comments assumes that method stopped working.
● install an advanced recovery without odin or root: [Q] How?
● fix USB firmware issue: [Q] I have completely no idea how to do it. (Already played with *#7284# and *#0808# but did not get my phone detected)
Please I need help, this is really irritating me and I am running out of ideas
Sent from my GT-I9300 using XDA Free mobile app
I guess I have found out what the problem was. It was not firmware (as I thought). It was the micro USB port (as boomboomer said) which seems to not be firmly attached to the PCB. AC charging just seems to work okay, but not USB connections. I managed to figure it out by forcing the USB in a specific position to get it detected for 5 seconds, but then it disappeared.
Yeah, it was not as complex as I thought! I will try to replace that micro USB port as soon as possible, thanks everyone for your help!