I do not "ever" have it checked in settings, however, when I load a custom ROM-any one and every one I have ever tried--resulted in the same scenario.
1. Check settings to make sure debugging is unchecked.
2. Connect usb cable.
3. Watch my laptop crash.
It would be funny if I had my laptop longer than 3 months but since it is fairly new it is horrifying to watch. Not too mention, having what you are working on go down with the ship. Good thing I make it a habit to save work while working.
I know, I know--I need a test dummy laptop, but I don't have one. Any other suggestions?
Related
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
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.
tl;dr - Computer does not even acknowledge the phone exists, factory reset doesn't work. The cyan colored recovery is recognized by the computer though.
So yesterday I went on a hike, and before you start assuming "Oh he dropped his phone in the water or dirt or something" no I didn't. The hike is more of a tourist attraction really, with a man made path that you really can't miss... more of a stroll in the forest than a hike. So as I reached the end of the trail, I put my phone into Ultra Power Saving Mode as I needed the battery. While I was texting, the phone started acting up. The charging sound kept on coming on kind of like when a charging connection is sh**. Then the screen went black. The weird thing was though, that the screen was "on". I could attempt to capture a screenshot,and it would say "Unable to capture screenshot" in a message box on the bottom, and the ringtones would still go off. The phone stayed like this for a while, when I got into my car I noticed it seemed like the phone was charging from the car port, but the charging light was still on when the charger was unplugged from the car (which shouldn't happen normally). After I stopped in town, the phone worked again, but I had to rechoose my keyboard, theme, and wallpaper. I thought all was fine. However when I got home I noticed I couldn't connect my phone to my laptop. It would say charging, but Windows doesn't acknowledge the phone and I can't choose MTP or PTP on my phone.. it just says charging. I am 99.9% sure it has to do with what happened on the hike because it was working fine before. I tried a factory reset/cache wipe and going back to stock ROM (from CleanROM). Still not recognized. I tried toggling USB debugging, pretty much everything the Internet has thrown at me... I'm past my 14-day return period so I hope this isn't a problem over the next two years?
Yes... different USB and computers don't work. Samsung drivers installed. Kies and SmartSwitch don't recognize the phone. Tried rebooting both phone and computer. Using original cable that came with phone. I've pretty much exhausted everything... If I didn't list it you can suggest to see if I didn't try that.
Cant access device from Windows
kaipolygon said:
tl;dr - Computer does not even acknowledge the phone exists, factory reset doesn't work. The cyan colored recovery is recognized by the computer though.
So yesterday I went on a hike, and before you start assuming "Oh he dropped his phone in the water or dirt or something" no I didn't. The hike is more of a tourist attraction really, with a man made path that you really can't miss... more of a stroll in the forest than a hike. So as I reached the end of the trail, I put my phone into Ultra Power Saving Mode as I needed the battery. While I was texting, the phone started acting up. The charging sound kept on coming on kind of like when a charging connection is sh**. Then the screen went black. The weird thing was though, that the screen was "on". I could attempt to capture a screenshot,and it would say "Unable to capture screenshot" in a message box on the bottom, and the ringtones would still go off. The phone stayed like this for a while, when I got into my car I noticed it seemed like the phone was charging from the car port, but the charging light was still on when the charger was unplugged from the car (which shouldn't happen normally). After I stopped in town, the phone worked again, but I had to rechoose my keyboard, theme, and wallpaper. I thought all was fine. However when I got home I noticed I couldn't connect my phone to my laptop. It would say charging, but Windows doesn't acknowledge the phone and I can't choose MTP or PTP on my phone.. it just says charging. I am 99.9% sure it has to do with what happened on the hike because it was working fine before. I tried a factory reset/cache wipe and going back to stock ROM (from CleanROM). Still not recognized. I tried toggling USB debugging, pretty much everything the Internet has thrown at me... I'm past my 14-day return period so I hope this isn't a problem over the next two years?
Yes... different USB and computers don't work. Samsung drivers installed. Kies and SmartSwitch don't recognize the phone. Tried rebooting both phone and computer. Using original cable that came with phone. I've pretty much exhausted everything... If I didn't list it you can suggest to see if I didn't try that.
Click to expand...
Click to collapse
Same problem but no previous reasoning behind it. I have installed the samsung galaxy S6 driver for windows and I get a beep on my PC when I connect it but no detection of device. I have enabled USB Debugging and clicked on connect device as Mass storage device.
AAAArrgghhhh.
WHY?
So, something very weird started happening to my phone. Out of nowhere, about 7 hours ago, it would stop charging whenever it was on, charging only when it was off and connected to my laptop. However, I thought it was just something wrong in the dev options, and I went to change whatever was the USB option to "charge phone". With this, I did accidentally forgot to activate the OEM option, and had to reboot not long after. You can probably see where this is going now.
Now I have a phone that bootloops on the FAP Lock message, and whenever I go to download mode to fix it, my PC just doesn't recognize the Phone. I've tried different USB cables, all of them are only recognized when the phone is shut down. So it isn't a hardware problem, because the Phone actually charges when it's shut down, and it isn't a problem with my USB ports or cables, as anything else I use with it works fine. And the worst part is, I need this phone today for a serious bank matter, and I can't afford to lose any data on it either, there's some very personal important stuff from yesterday that wasn't backed up yet. And keep in mind that paying for it to be fixed is the last option for me, as I can't afford it (besides, I fear they might end up getting the phone in factory reset mode, and I can't lose that data as I said).
Any kind of suggestions on how to get either the PC to recognize the phone, or flashing in a different way that doesn't need the PC to recognize the device? Thanks in advance.
Edit: Whenever I try to connect the phone via USB, it doesn't even make the Windows "USB connected" sound, it's just like it isn't there at all. One time, I got it to show, but it was as a "unrecognized usb device", and I haven't been able to replicate it yet.
So there's an app I'd like to sync between my phone and tablet, however I can't figure out whats the best way to sync it.
So the idea is the following, I'm using the app on my phone, i put it on the charger and pick up my tablet, while swapping them it syncs my data so I can pick up exactly where I've left it on my phone (Its some sort of book app).
I've been thinking about the following since I have root:
Using Syncthing, i've set it to "/system/data/user/0/(app)", however while I'm not completely sure about it there is a risk in it syncing the old files (wrong device) over the correct one. I'm not feeling to confident about this one so I guess i'm keeping this as a last option.
I've also been looking into Titanium Backup, though it kinda is what im looking for the problem is that within the tasks i can only select the days and a static time, it does not trigger when I'm putting the device on a charger so it back-ups the app. (There is a condition about charging, but it seems to be for the day/time you can put whenever it should activate at that moment)
Is there a way to tackle this?