Samsung USB Connector Connected – Disconnected

So my Samsung A51 suddenly start giving me a silent notification USB Connector Connected – USB Connector Disconnected again. I tried restarting, clearing the cache, and connecting my USB cable back and forth but the issue persisted.

It would go constantly preventing it to go to sleep. I guess this was bad for the battery too.

The main culprit for this seems to be a corroded or damaged USB-C connector on the bottom of the phone.

Two types of fixes (probably third as well)

The first time it happened I sprayed alcohol and cleansed the connector using a toothbrush (on a turned-off phone). After turning it on everything seemed to be normal, but the issue returned back after a year and cleaning didn’t help anymore.

The second time I fixed it by activating USB debugging and restarting the phone and again the issue disappeared.

If it happens again it seems I will need to replace the charging port by resoldering.

1st Fix: Cleaning the USB charging port

  1. Turn off the phone
  2. Spray a small amount of alcohol on the charging port
  3. Brush the port with a clean toothbrush
  4. You can use a toothpick to remove larger debris if you see it
  5. Wait 10 minutes alcohol to evaporate
  6. Turn on the phone

2nd Fix: Activating USB Debugging

First, to activate USB debugging you need to activate the Developer options menu.

To activate the Developer options menu do the following:

  1. Go to “Settings”.
  2. Go to “About phone”.
  3. Go to “Software information”.
  4. On the “Build number” tap seven times.
  5. Now developer menu should be visible when you go back or open settings.

To active USB debugging do the following:

  1. Go to “Settings”
  2. Go to “Developer options”
  3. Enable the “USB Debugging”.

Now restart your phone by swiping down twice from the top of the screen to down, tap the turn off button, and tap the restart button,

3rd Fix: Replacing the charging port


By googling this error I ended up on a Samsung forum where all kinds of Samsung phones e.g. Samsung A51, Samsung A52, Samsung A53, Samsung A70, Samsung M51, and Samsung M52 were affected by this issue.

Here is video of some guy doing the same and fixing the same error: