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.
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ยข
OK, so here's the issue. I have an HTC Desire C. It's my girlfriends so I don't know the OS version. I replaced the Touch Digitizer because it was shattered (it did respond to touches though). Now that its replaced it seems to respond to touches but not correctly. I can't get it to swipe the lock screen out of the way. It's as if it is not calibrated correctly. So I'm stuck on the lock screen.
I want to run ADB so I can figure out if its registering touch events correctly, and also try and send them over ADB. But, being my girlfriends phone, she never enabled "USB Debugging". When I hook the phone to the computer, I don't see it showing up as a unknown device in windows Device manager (VISTA). I know it works, cause I tried it with my Nexus S and that shows up. I know the steps are first find it in device manager then manually select the driver as the ADB interface, I've had this working on my Nexus S. But the issue is that it doesn't show up at all in Device manager, and I assume its because USB debugging is off. I tried turning off USB debugging on my Nexus S, hooked it to my computer, and it doesn't show up either. So it seems like that is the issue.
I tried to boot into recovery (power button + volume down), then went into fastboot, connected the phone to the comp again, but it still does not show up.
Below are some of the other things I have tried, but they still brought me no luck:
I have tried installing HTC sync so I get the HTC drivers on my computer, but it doesn't even show up in HTC's software (In fact, it does not show up as a storage device either, I assume cause you have to accept the notification on the phone, but I can't use the phones UI at all). I tried moving the HTC drivers into c:\windows\system32 and it still does not show up. I then tried rebooting the phone and my computer. Still does not show up. It seems like windows isn't even reading the phone as a USB device. Tried swapping USB cables (both work with my nexus s), and still nothing. Is there something I am missing?
Any help would be much appreciated, this is driving me crazy.
Also, after replacing the digitizer, if I first boot into the phone and then hit the power button, I don't get the content window that allows you to choose "reboot", "shutdown", etc. The only thing I can do is hold it for 15 seconds and the thing turns off. I'm hoping this is because I never passed the lock screen for the first time. I'm hoping this is not an indicator that I screwed something up when I opened the phone. I've had my Nexus S open plenty of times.
Another guy had same issue. here
Try that.
life!
Yea let us know if it works
Lifehacker7 said:
Another guy had same issue. here
Try that.
life!
Click to expand...
Click to collapse
I can't get the phone to show up when I type "fastboot devices" or "adb devices". I have tried this from the lock screen, from the bootloader, from the bootloader and in fastboot mode. That is my critical problem now. Cable is actual data cable, and I'm using USB port on back of a desktop computer. Is there anything else that could be causing the phone to not be recognized?
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???
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?
Hello, I have a Samsung A51 through T-Mobile. Recently my phone has only been charging and won't do any data transfer or bring up the menu to select what to do with the connection. After trying many different things I found out it will connect with data transfer only when I restart the phone while it's plugged in. Once I unplug the phone and plug it back in nothing. But if I leave it plugged in and restart it again it shows up.
Any ideas? All help would be greatly appreciated. I've looked around and cannot find anything regarding my issue.
Thank you
Try a known good cable.
Make sure the phone pop up enabling the data connection is enabled. Without permission each time access will be denied... at least on my Samsung.
Access the drive directly in Device Management; hit scan for new devices.
Check Event Viewer for errors logged.
Reload the drivers on the PC.
blackhawk said:
Try a known good cable.
Make sure the phone pop up enabling the data connection is enabled. Without permission each time access will be denied... at least on my Samsung.
Access the drive directly in Device Management; hit scan for new devices.
Check Event Viewer for errors logged.
Reload the drivers on the PC.
Click to expand...
Click to collapse
I can do all that. But only after restarting my phone while it's plugged in. It's not a cable issue or a USB port issue. Ive tried multiple cables and ports. And also tried same cable with different phone. The port on my phone is fine. If I plug it in, restart my phone it shows up as it should. Once I disconnect the phone and plug it back in, nothing. It's very odd. I think it may be an update issue from t mobile. But figured I'd check here.
Thank you for your response
Also, the pop up to allow access only shows up when phone is plugged in and I restart it. I unplug it and plug it back in. And it will only show thats charging and there isn't a prompt or selection of what to do with usb (transfer files, images, MTP, tethering etc.
Shadow42 said:
Hello, I have a Samsung A51 through T-Mobile. Recently my phone has only been charging and won't do any data transfer or bring up the menu to select what to do with the connection. After trying many different things I found out it will connect with data transfer only when I restart the phone while it's plugged in. Once I unplug the phone and plug it back in nothing. But if I leave it plugged in and restart it again it shows up.
Any ideas? All help would be greatly appreciated. I've looked around and cannot find anything regarding my issue.
Thank you
Click to expand...
Click to collapse
Try this troubleshooting steps https://www.wikihow.com/Clear-the-Record-of-USB-Plug-in-Equipment and that https://www.partitionwizard.com/disk-recovery/the-last-usb-device-malfunctioned-windows-10.html from time to time my Samsung devices have some kind of issues with Windows 10.
Also you should try with adb commands pairing both and allow the access always when the prompt appears, it could be some kind of permission denied or malfunctioning that either Samsung is not asking correctly to PC or the permission from PC is not coming properly to device, this should happen due to some old logs or a filled directory in the USB hub in Windows that needs some cleaning.
Shadow42 said:
Also, the pop up to allow access only shows up when phone is plugged in and I restart it. I unplug it and plug it back in. And it will only show thats charging and there isn't a prompt or selection of what to do with usb (transfer files, images, MTP, tethering etc.
Click to expand...
Click to collapse
Check Developer options>USB default configuration
Try clearing system cache on the phone.
Try a hard reboot on the phone.
If you unplug the phone from the PC you need to reauthorize it via the phone pop up after you reconnect it... each time.
If you always leave the PC on, reboot it.
blackhawk said:
Check Developer options>USB default configuration
Try clearing system cache on the phone.
Try a hard reboot on the phone.
If you unplug the phone from the PC you need to reauthorize it via the phone pop up after you reconnect it... each time.
If you always leave the PC on, reboot it.
Click to expand...
Click to collapse
Like I've said. There is no prompt unless I restart my phone while plugged in. This isn't my first phone. I understand how it "should" be working. And it only acts as it should when I plug it in and restart the phone. Once I unplug it and plug it back in its as if I'm using a charg only cable.
Thanks for the response
Shadow42 said:
Like I've said. There is no prompt unless I restart my phone while plugged in. This isn't my first phone. I understand how it "should" be working. And it only acts as it should when I plug it in and restart the phone. Once I unplug it and plug it back in its as if I'm using a charg only cable.
Thanks for the response
Click to expand...
Click to collapse
Meh then play with it... you know the drill.
Goggle it and look at other models/OS's that had the same issue as well. A lot of the same issues keep reoccurring so this tactic is helpful with newer models too.
Either it's settings, the load got screwed up or it's hardware maybe the port. Worse case... a mobo failure.
Try it in safe mode.
I probably do a factory reset* especially if it's an old load. If that fixes it but the issue returns latter, it's a setting or 3rd party app causing it.
*if it persists after a factory reset it's possible the firmware version is the problem or the firmware got corrupted during the flash. Reflash firmware.
blackhawk said:
Meh then play with it... you know the drill.
Goggle it and look at other models/OS's that had the same issue as well. A lot of the same issues keep reoccurring so this tactic is helpful with newer models too.
Either it's settings, the load got screwed up or it's hardware maybe the port. Worse case... a mobo failure.
Try it in safe mode.
I probably do a factory reset* especially if it's an old load. If that fixes it but the issue returns latter, it's a setting or 3rd party app causing it.
*if it persists after a factory reset it's possible the firmware version is the problem or the firmware got corrupted during the flash. Reflash firmware.
Click to expand...
Click to collapse
Thank you. I'll start with safe mode and go from there. I appreciate your response.
It's frustrating. Find a usable work around for the time being if you can.
Most times the solution is staring you in the face, step back and rethink it. When did it start? What was done before it started?
Try clearing the data in the Android Setup apk (Android Setup com.google.android.setupwizard Android).
Use a 3rd party app like Package Disabler PD MDM to clear it as doing it in Settings leaves a Null* (presumably) and can't fix it sometimes. I know this particular app (PD MDM) works because I had it happen to me with a USB popup issue a while back.
Clearing Android Setup apk data completely resolved it. If you see Android Setup as a cache app it is the culprit; normally it never runs except during initial setup.
*when data is reported as zero, Nulls are apperantly not reported but still there screwing things up.