Database Info

Wont connect to PC and other odd issues

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???

[Q] Bricked worse than I thought? Help! (long)

Hey gang - I've been traveling for work and just have some crappy slow satellite wifi for access. The phone has been great because I can use wifi calling and all is good.
A few weeks ago my phone crashed. When I rebooted I was at the "touch android to begin" screen. Well... fix permissions and clear caches didn't work.
So next I restored a backup from CWM.
Unfortunately, after that the phone hangs at the initial Samsung splash screen.
Now, stupid me didn't go an a six-month trip with the Android software on my laptop - so I had to wait for my wife to mail me a thumbdrive that has SOC, HOC, drivers, & etc. on it in order to do anything.
In a previous thread from when this first happened, you all recommended I use HOC to flash the phone back to stock. Which now that (yesterday) I got the thumbdrive in the mail, I am happy to do.
My problem comes from the fact that the phone hangs at the Samsung splash screen seemingly no matter what I do... zadig.exe doesn't recognize the phone on the USB port (just "unknown device") and therefore HOC can't do anything (I think?) Furthermore, I can't even get back into recovery or download mode; at least not with the several techniques I've tried so far.
Recommendations? Or am I hosed?
Thanks in advance,

JaimeZX said:
Hey gang - I've been traveling for work and just have some crappy slow satellite wifi for access. The phone has been great because I can use wifi calling and all is good.
A few weeks ago my phone crashed. When I rebooted I was at the "touch android to begin" screen. Well... fix permissions and clear caches didn't work.
So next I restored a backup from CWM.
Unfortunately, after that the phone hangs at the initial Samsung splash screen.
Now, stupid me didn't go an a six-month trip with the Android software on my laptop - so I had to wait for my wife to mail me a thumbdrive that has SOC, HOC, drivers, & etc. on it in order to do anything.
In a previous thread from when this first happened, you all recommended I use HOC to flash the phone back to stock. Which now that (yesterday) I got the thumbdrive in the mail, I am happy to do.
My problem comes from the fact that the phone hangs at the Samsung splash screen seemingly no matter what I do... zadig.exe doesn't recognize the phone on the USB port (just "unknown device") and therefore HOC can't do anything (I think?) Furthermore, I can't even get back into recovery or download mode; at least not with the several techniques I've tried so far.
Recommendations? Or am I hosed?
Thanks in advance,
Click to expand...
Click to collapse
Interesting problem. I have bricked my phone a bunch of times and have always been able to get back to at least "download Mode". The method I use to go to "Download Mode" is With the usb cable plugged into the computer only, power off the phone. If phone wont power off, or stay powered off, pull battery, then put battery back in. Now hold vol down and vol up buttons only, keep holding these buttons as you plug the usb cable into the phone. In 3 seconds the download screen should appear. I hope this helps you get your phone back.

JaimeZX said:
Hey gang - I've been traveling for work and just have some crappy slow satellite wifi for access. The phone has been great because I can use wifi calling and all is good.
A few weeks ago my phone crashed. When I rebooted I was at the "touch android to begin" screen. Well... fix permissions and clear caches didn't work.
So next I restored a backup from CWM.
Unfortunately, after that the phone hangs at the initial Samsung splash screen.
Now, stupid me didn't go an a six-month trip with the Android software on my laptop - so I had to wait for my wife to mail me a thumbdrive that has SOC, HOC, drivers, & etc. on it in order to do anything.
In a previous thread from when this first happened, you all recommended I use HOC to flash the phone back to stock. Which now that (yesterday) I got the thumbdrive in the mail, I am happy to do.
My problem comes from the fact that the phone hangs at the Samsung splash screen seemingly no matter what I do... zadig.exe doesn't recognize the phone on the USB port (just "unknown device") and therefore HOC can't do anything (I think?) Furthermore, I can't even get back into recovery or download mode; at least not with the several techniques I've tried so far.
Recommendations? Or am I hosed?
Thanks in advance,
Click to expand...
Click to collapse
This sounds like a time where a jig would be helpful. Any chance you can have your wife order one, and send to you? http://www.youtube.com/watch?v=D7I4dFX_iJ4
This should put you straight into download mode, and you can then flash.

Thanks, guys. I continued fiddling and got the phone into DL mode.
I also noted that when plugging and unplugging the phone, it would show up in zadig as "unknown device."
I tried to load the drivers on that, but (a) it still shows up as "unknown device" and (b) when I run HOC it doesn't see the phone under the list of compatible devices.
So.... still kind of stuck.
Any more ideas?

Oop. duplicate post

It's been awhile since I've played with the one clicks, but, "serial gadget" is what I remember seeing when I used them.

Right. MORE messing around later and "Serial Gadget" is it.
That said, I still think I have a driver issue. I have tried uninstalling and reinstalling the zadig-recommended drivers for Serial Gadget several times. I also tried manually installing the drivers from Super One Click.
Anyway, now when I load up HOC I get the green <<connected>> at bottom; but then sometimes it wants me to install the drivers (again) and sometimes it gets past that part, but then goes to
Flashing Kernel: 0%
...hangs there for about 10 seconds and then
Failed!
So... driver thing you think?
Thanks again,

If you reboot the phone after the 0% hanging for 10 seconds, does it go to the yellow exclamation mark screen? If so, just reflash again and you should be back to working... both my and my wife's phone always did that when I had to flash a kernel.

That's just another download screen that theraze is describing.

Exacatly. But the alternate download screen always came up after restarting the phone after a 'failed' flash where it stayed at 0% where it was successfully communicating through the cable. That just meant to not break the drivers or unplug anything... just reboot fast and finish up quickly.

Okay - I can definitely try that! It had not occurred to me to try and reboot the phone right then.
Question, though - when I get the "Failed!" Then HOC essentially hangs, when it says something along the lines of "ending session..." and never progresses from there. So how do you "restart quickly?" Because I have to like, close and reopen HOC. I guess I will see if it succeeds at ending the session when I reboot.
I will try it again. Strange though, sometimes HOC accepts the existing driver (I managed to DL the Samsung driver installer) and sometimes it wants to reinstall "WinUSB." does that make sense? Is the WinUSB an acceptable one?

The winusb is the right driver for heimdall, it doesn't like the Samsung driver.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Samsung drivers and the one click drivers clash. Yes, uninstall Samsung completely if you want to use the one click.

Hm. Thanks for that - might be part of the problem.
Dunno what I did differently, if anything, but last night I tried flashing again and this time it went through! I was very glad to see the whole HOC process completed successfully!
So anyway - thanks so much for the help, guys.

Hard Brick (possible hardware failure)

I was wondering if I've encountered a common failure mode with my Verizon Galaxy S3 and if there are any possible solutions.
A week before it bricked, the phone was acting rather odd, rebooting itself spontaneously and at random; I didn't really think much of it until the following week. Applications on the phone had been running VERY slow and would often crash or hang; in addition, the phone was rebooting itself several times an hour at this point.
The last reboot hung for a while at the "Samsung Galaxy S3" screen before going to the home screen. At this point I realize there may be something serious going on, so I attempt to SSH into it and retrieve important information off it. Unfortunately, it proved to be too late; login attempts failed with "Argument list too long". A few minutes after my ill-fated attempt to save data, the phone crashed in the app launcher and initiated a reboot again; only this time, the Samsung logo never came up. Since then, I have been unable to power it on, enter recovery, or otherwise get any life out of it.
It's long out of warranty so I'm basically wondering what my options are to revive it and possibly get important info off it. Reinserting the battery does not work and neither does plugging it in. All options to enter recovery or any other sort of mode fails; it essentially acts like there's no battery inside and does nothing. Is this a common failure state for S3 units and is there a known solution? Has anyone ever used JTAG to retrieve information off the storage inside?

WildZontar said:
I was wondering if I've encountered a common failure mode with my Verizon Galaxy S3 and if there are any possible solutions.
A week before it bricked, the phone was acting rather odd, rebooting itself spontaneously and at random; I didn't really think much of it until the following week. Applications on the phone had been running VERY slow and would often crash or hang; in addition, the phone was rebooting itself several times an hour at this point.
The last reboot hung for a while at the "Samsung Galaxy S3" screen before going to the home screen. At this point I realize there may be something serious going on, so I attempt to SSH into it and retrieve important information off it. Unfortunately, it proved to be too late; login attempts failed with "Argument list too long". A few minutes after my ill-fated attempt to save data, the phone crashed in the app launcher and initiated a reboot again; only this time, the Samsung logo never came up. Since then, I have been unable to power it on, enter recovery, or otherwise get any life out of it.
It's long out of warranty so I'm basically wondering what my options are to revive it and possibly get important info off it. Reinserting the battery does not work and neither does plugging it in. All options to enter recovery or any other sort of mode fails; it essentially acts like there's no battery inside and does nothing. Is this a common failure state for S3 units and is there a known solution? Has anyone ever used JTAG to retrieve information off the storage inside?
Click to expand...
Click to collapse
Plug it into your computer, or a wall outlet with the battery out. See if it mounts as a strange drive or the led light flashes for a second.

Oh wow. Yes it does have the red light when I plug it into the wall outlet without battery. Haven't tried the PC as I'm leaving for work and my USB wire is in the car but I'll assume that will work when I try it.

WildZontar said:
Oh wow. Yes it does have the red light when I plug it into the wall outlet without battery. Haven't tried the PC as I'm leaving for work and my USB wire is in the car but I'll assume that will work when I try it.
Click to expand...
Click to collapse
At least it isn't completely fried, this method should work:
http://forum.xda-developers.com/showthread.php?t=2581166
Make sure it has no other sign of life first.
If you were on 4.1 then make sure you don't use a 4.3 file and lock your phone. Might have to do some digging around to find them, but they are around here somewhere.

Samsung J7 Prime G610M - FAP Lock + weird usb problem - Urgent

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.

Troubleshooting USB problems

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.