I know with the recent jellybean update to the S3 the root functionality has been changed around a bit to require odin....but i've ran into a hiccup with my phone that's keeping it from even connecting to a PC. The phone charges just fine but the PC doesn't even see the connection attempt. Is it possible to root/rom the phone through wifi/sd card transfers? I've already done a hard reset, changed cables out multiple times, even verified the cables worked on my friend's GS3 with no issues, his detected fine.
Any help would be much appreciated.
There isn't any even the old method of rooting required a computer just not Odin mode. I do hope that the devs come up with a new way to root this phone.
Related
First of all, my wife and I have the same phones, both stock infuse, bought the same day. I can connect her's to computer via usb and computer immediately will recognize it as an additional drive, including the sd card as another. I am able to do anything I want with it (with or without debugging enabled). So drivers and everything else is ok. When I plug mine in, (same cable, same port), it only charges and does not even acknowledge it is there, even in device manager, not there, with or without debugging enabled). I have disabled my Lookout and AVG. Any suggestions on changing any of the setting on the phone that I could have tinkered with and not realized it? Both are stock unrooted phones. I called ATT who advised to do a master reset. I would really like to try about anything else first. Any help appreciated. Thanks.
emrmcrn said:
First of all, my wife and I have the same phones, both stock infuse, bought the same day. I can connect her's to computer via usb and computer immediately will recognize it as an additional drive, including the sd card as another. I am able to do anything I want with it (with or without debugging enabled). So drivers and everything else is ok. When I plug mine in, (same cable, same port), it only charges and does not even acknowledge it is there, even in device manager, not there, with or without debugging enabled). I have disabled my Lookout and AVG. Any suggestions on changing any of the setting on the phone that I could have tinkered with and not realized it? Both are stock unrooted phones. I called ATT who advised to do a master reset. I would really like to try about anything else first. Any help appreciated. Thanks.
Click to expand...
Click to collapse
Is everything on the two phones the same?
Is there an app that you are running that did something to USB recognition?
Sometime a simple reboot may clear the issue. I did not see you listed that.
Have you tried taking our a microSD and reboot to see if that fixes the problem?
You can also boot into Samsung 3e recovery (see my sig link) and clear just the cache, then reboot.
Obviously, if you do a master reset, take off your photos and important data by copying then using my files to a microsd and take it out before the reset. Reseting in the phone will erase everything.
I think yours may be a hardware issue though, try brushing the USB contact with a toothbrush or some sort of minimal rubbing alcohol
If nothing works, i think you'll be getting a new phone
I do have some extra apps that she doesn't, handcent, flashlight, scanner radio slacker, soundhound, and a few more, but nothing that should affect the usb. I have tried rebooting with and without sd card. Even tried to reboot while holding in vol up and down button at same time and cleared cache that way then rebooted. I searched for Samsung 3e recovery, but didn't find anything that really relates to what I'm looking for. All I found dealt with if phone was rooted. I did try cleaning out the port also. So far, no luck. But thanks for the suggestions.
I am sure this will sound odd... but have you tried it on another PC? It may be a recognition issue with the device drivers and the phone that isn't working.
Just my 2ยข
I may have found one more thing you could try...
After trying EVERYTHING I could find here on XDA, as well as across the web, I still couldn't get my S3 to connect to my computer. While trying to get mine to work, I discovered that my husband's S3 connected just fine, nixing the thought that it was computer related. I exchanged mine for a new phone, got it home, and it still didn't connect.
Several hours of troubleshooting later, I had it narrowed down that it worked immediately after a factory reset (while still connected to the computer), but BEFORE the setup wizard got to the Backup Assistant (where it was no longer visible in My Computer). SO, I reset it again, skipped out of the setup wizard as soon as I could, and bada-bing! It works! I discovered after the fact that my husband (whose connected so beautifully from the get go) had backed out of his setup wizard during initial setup, so it definitely could be more than just a one phone fix.
I'll be the first to admit that I'm a total newb to pretty much everything in this forum, so there may be a more knowledgeable person who could be able to pinpoint exactly why the setup wizard would prevent the MTP driver from working properly. At this point, I'm just happy it works, and wanted to put this out there in case there may be anyone else at their wits end.
I had to install kies before it worked properly for me and now i still have to plug in phone then unplug and plug back in before pc see's my phone.
Sent from my SPH-L710 using xda premium
jbadboy2007 said:
I had to install kies before it worked properly for me and now i still have to plug in phone then unplug and plug back in before pc see's my phone.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Yeah, installing, uninstalling and re-installing Kies did nothing for my phones (first or second). I tried it all -- different usb ports on the computer, battery pull, reboot the phone, reboot the computer, install the drivers, uninstall the drivers, try it with usb debugging checked, try it all again with usb debugging unchecked, with an sd card, without one, with a sim card, without one, factory reset not connected and then factory reset connected. Even tried it all again on a separate computer running Windows 7 vs Vista. Finally, in the middle of a factory reset, I saw the magic words "Installed Successfully", but then it stopped working after I finished the setup wizard. Again, I have NO idea why the setup wizard would cause it not to work, but that was what I had narrowed it down to. I'm just glad to have it working!
Verizon Galaxy S3 USB Solution for Win 7 32bit
Micheliu said:
I may have found one more thing you could try...
After trying EVERYTHING I could find here on XDA, as well as across the web, I still couldn't get my S3 to connect to my computer. While trying to get mine to work, I discovered that my husband's S3 connected just fine, nixing the thought that it was computer related. I exchanged mine for a new phone, got it home, and it still didn't connect.
Several hours of troubleshooting later, I had it narrowed down that it worked immediately after a factory reset (while still connected to the computer), but BEFORE the setup wizard got to the Backup Assistant (where it was no longer visible in My Computer). SO, I reset it again, skipped out of the setup wizard as soon as I could, and bada-bing! It works! I discovered after the fact that my husband (whose connected so beautifully from the get go) had backed out of his setup wizard during initial setup, so it definitely could be more than just a one phone fix.
I'll be the first to admit that I'm a total newb to pretty much everything in this forum, so there may be a more knowledgeable person who could be able to pinpoint exactly why the setup wizard would prevent the MTP driver from working properly. At this point, I'm just happy it works, and wanted to put this out there in case there may be anyone else at their wits end.
Click to expand...
Click to collapse
Well, after reading about a dozen posts and so-called fixes. It all boiled down to uninstalling the Samsung Driver & Kies (if you installed separately). This def works for Verizon SCH-I535 Galaxy S3 16MB with 4.0.4 load.
1. Uninstall Kies, Uninstall Samsung Driver, reboot. Reboot your phone just to be safe.
2. On your S3 select Settings-->Developer-->Enable USB Debugging (hit ok at the prompt). Don't tweak anything else here. You MUST have the Debugging turned on for phone to connect to PC.
3. Plug-in the Samsung USB cable to PC (there was some discussion on which USBs work and which don't ... so you can try different USB ports if #4 fails to work below)
4. Windows will then install whatever driver(s) it needs and whala, you can now access your S3 via Explorer...it will show up as a phone, not an actual drive.
Hope this helps and saves you the time and frustration I experienced. I never saw the little USB icon on the S3 until I wiped all the Samsung and Kies drivers from my Win 7 system & enabled debugging on phone. So the issue lies with Samsung and their crappy Kies tool...their driver does not work for S3 (i.e., the standalone download that Version posts on their site). Go with the Windows Update driver (which is auto) and you should now be able to connect via USB to your S3. Again, this works for Win 7 32bit with Android 4.0.4.
-Cheers!
I have an old pc running xp. Nothing worked until I installed kies on both the phone and the pc. YMMV.
Sent from my SCH-I535 using xda app-developers app
Ok, so I have been having a very annoying issue(s) recently with my SGH-I997R, ( Firmware version 2.3.3, Baseband version I997RUXKG3, Kernel Ver: 2.6.32.7-I997RUXKG3-CL366622)
This all started out of the blue about a month ago, I used to connect my phone to my PC all the time for transferring items via Mass Storage, and then on day when I went to connect it to my same PC, I got " USB Device Not Recognized". It will charge the phone but will not connect or show any option on the phone to connect. I have tried 2 Samsung cables and a generic Micro USB cable, No change. I tried connecting to my laptop, same issue. I re-downloaded the drivers from Samsung onto both my usual PC and Laptop, no change. Very very frustrating.
Other issues, I don't know if their related in any way but they all started at the same time.
a) if I place my phone in airplane mode i cannot get it out of that mode without rebooting my phone
b) if i shut my phone down (doesn't matter if battery shows 100% or 25%) I cannot get the phone to turn on without plugging in the USB cable.
c) When I leave my phone charging overnight and look at it in the morning, battery shows 100% but also shows "NO SERVICE" , I reboot the phone with the cable still connected, service restored.
IF anyone has had these issues Especially the connecting to PC issue, Please PLEASE help. I am going nuts. And of course this all happened 3 months after the warranty expired, so both Rogers and Samsung will not help without $$$$$.
have you tried to back up your data, take out any micro sd card and perform a factory reset under /settings/privacy/reset ?
or open it up and look inside for any problems like corrosion?
qkster said:
have you tried to back up your data, take out any micro sd card and perform a factory reset under /settings/privacy/reset ?
or open it up and look inside for any problems like corrosion?
Click to expand...
Click to collapse
I have done a factory reset numerous times from both the /settings/privacy/reset, and from booting it up holding the volume keys and doing a reset that way.
And I have had my phone since day one in a Ballistic Hard Core Series case, I take it out once a week to ensure its clean and free of dust/moisture (I work in construction so I try to keep it a clean as possible.) and my phone still looks like its brand new.
Thanks for the response though,
Update:
So just as an update for anyone out there who may be able to assist me with this very annoying issue, the Phone is still doing the same things, and since the last post i've also replaced the battery to see if for some strange reason it might help.
But to no avail.
As well I dont think i mentioned that this phone is rooted. I want to try unrooting it to see if that will correct the issue, but with not being able to connect the phone via usb to the computer, I have NO IDEA on how I can accomplish this. Any help???
Hello,
I have a Verizon S3 (SCH-I535) which I've been using for over a year now. I decided to root the phone about a month ago with TowelRoot and everything seemed fine. But just a few days after I had rooted my phone, Verizon issued their KitKat update for my phone (I dont know why I received the update a few months late). I didn't want to update because I knew that if I did, it would just soft-brick my phone. So I thought I would just connect my phone to Odin and load the stock 4.3 firmware back onto my phone (since deleting the root files won't really have any effect). But when I tried connecting my phone to the computer, the computer won't even recognize it (I had the drivers installed). It charges, but it won't get recognized on any computer I plug it into. After this, I realized that the micro USB module got messed up.After my phone wouldn't connect to the computer, I thought that if I had just soft-bricked the phone by trying to install the update and then restarted the phone from recovery, I could just boot up my phone regularly and I wouldn't get the update anymore. I didn't want the update constantly bugging me every single time I used my phone. But to my dismay, the update downloads once every 24 hours. So I used my phone for a few days, but then I realized I that had another problem, none of the Google apps (Play Store, Google+, Hangouts, etc.) were working. So I decided to clear the cache and memory of all of them and sign out and into Google services again. When I tried signing back in, it would say that I couldn't establish a reliable connection to the server, even if I had really fast internet. Along with these problems, I don't receive notifications from any app even if I turn them on and some apps are starting to crash when I open them up, such as the camera app. I've tried a number of solutions, such as trying to install CyanogenMod through Clockwork, but none of that works because of Verizon's locked bootloader. I've even tried factory resetting, and it still soft-bricks that way. Could anyone please help me with this? Thanks.
Hey guys, let me just start off by saying I have spent almost 8 hours straight today trying to figure this out and dig myself out of a hole I've created for myself, that being said, I'm going to try and be as detailed as possible so you guys know EXACTLY where I am and what I've tried. This post looks long but that's because it is. It's pretty much my entire day's worth of trouble typed out. So just bare with me and see if you guys can help me out here!
I have a T-Mobile Galaxy S4 model: SGH-M919 it has Android 4.4.2. Now on to the problem: I've had this phone for almost a year now and a few months ago I rooted it. Did a simple Youtube tutorial and used Odin to do the work and everything worked out fine. A couple months down the road (yesterday), after using the phone like a teenager, downloading apps and cluttering it up it started to slow down and not run some apps. After thinking about it I decided to factory reset it. All of my contacts, photos, and videos were backed up on Google so I thought "why not?" Well, this is where $#!% hit the fan.. being rooted then factory reset, right before the phone came online it had me answer two questions about the root. Something to the effect of "Do you want to keep root? (This option is not reversible)" I thought since I wasn't using the features I originally rooted the phone for I figured nah just get rid of the root. So the phone did its T-Mobile boot up and started the Initial setup.
Everything up to to this point was fine until I wanted to log in to my Google account during the setup. Please understand that where I am I have full 4G LTE coverage and have access to a pretty fast and sturdy wifi connection. Well, when it came to the google sign in I entered my email and password and it came up with a message reading "Can't Sign in - Can't establish a reliable connection to the server" (believe me i wish that was the only issue) so after reading that, I thought I'd try with my wifi.. nope. Same thing. Since neither my 4g or wifi worked I thought it was Google's servers so I tried again this morning, same thing. (keep in mind at this point i think my phone isn't rooted anymore.) I call the t mobile store and they give me a technical support number, so I call it and I tell them i cant sign into Google. The gentleman told me he cant do anything because he can tell my phones been rooted. Only thing he suggests is to contact Google, well, the customer care number just tells you go to google.com/support and there's nothing there about my problem.
This is where I dig my hole even deeper. I tried another factory reset and up in the top left corner i still see that root text. Even the rooted android symbol pops up before the Samsung logo or t mobile. Since I saw that I thought "ohh it just didn't get unrooted all the way." I look up ways to completely remove a root and a lot of them require plugin your phone into the computer and using Odin to flash a stock firmware on to the device. I went to plug my phone into the usb port but my computer didn't recognize the usb device, having experienced this a long time ago I searched around for the latest Samsung usb drivers and I installed those. Device still isn't recognized. Let me just note before people tell me to use MTP mode or Developer tools> usb debugging or connection mode.. The only thing that happens when plugging my phone via usb is the phone starts charging and my computer makes the trumpet noise like something is plugged in. Other than that, there is NO notification of it being plugged in. The reason i stress this is because I called Samsung technical support at this point and the guy (not gentleman) treated me like a 5 year old and ran me through all of these options after i told him I already did everything he was suggesting, including downloading Samsung Kies 3 and having it install the drivers. It does not pick up the device either.. at this point I looked up ways to remove the root without the computer. I found out you can just go into the root app "SU" or something and theres a remove root option. I jumped on that opportunity and had it removed. I restarted the phone and all the problems still persist, it even still has the root text on the top left when you factory reset it again. However now, even if you factory reset and select the option "keep root," thinking it would bring back the"SU" app it does NOT.
So lets recap. I have a phone that thinks its rooted and even appears rooted to t mobile but doesn't have any of the root apps or privileges or capabilities to fix my Google log in issue (like the host file in filemanager). And I can't re-root to get that app back because none of my 3 usb ports, 3 different usb cables (one being the cord that came with the phone), or any of the ports/cables on someone else's computer will recognize the darn thing to work on that way! I have all these issues that are supposed to fix each other but I can't do any fixing because they cancel each other out too... I'm at a dead end.
In case this isn't the right forum/website/thread/post area etc.. I have this whole message saved in Microsoft Word document so I can repost it anywhere you guys might suggest better results. Any help/advice will be much appreciated.