13-06-2025 07:51 AM
Hi everyone,
I'm having the same issue that many others have reported. I bought a Galaxy S25 about three months ago. For the past few weeks, I’ve been unable to charge it with a cable due to the persistent moisture/debris alert, so I’ve had to rely solely on wireless charging.
Here’s what I’ve tried so far:
Dried out the charging port with cool air
Swapped out different cables and chargers (including brand new ones)
Used official Samsung cables and chargers
Tried charging in Safe Mode
Reset all settings via: Settings > General Management > Reset > Reset all settings
Cleared USBSettings cache: Settings > Apps > Filter & Sort (Show System Apps) > USBSettings > Storage > Clear Cache
Interestingly, after a Samsung update a week or two ago, the issue temporarily disappeared and I was able to charge by cable again—but only for a few days. Then the alert returned. I’ve now installed the latest update from 1 June 2025, but the problem is still there, and I'm stuck with wireless charging only.
I also ran the Diagnostics tool, which simply told me: "Cable charging is not working."
What’s even more curious: my husband, who has a different Samsung model, started having the same issue a few weeks after mine began. His issue also briefly resolved itself after a software update.
Is this a software bug? A hardware issue? Is anyone else still facing this even after the June update?
Would love to hear if anyone has a long-term fix. Thanks!
Solved! Go to Solution.
13-06-2025 08:50 AM
Contact Samsung support via Members app and let them deal with it
13-06-2025 09:38 AM
I have now done this: "Hold the Power button and volume down for 15 seconds to force a power off. It's like pulling the plug on a computer"
as suggested by @arianwen27 and this seems to have solved it, for now!
14-06-2025 03:42 PM
Unfortunately, the problem started again today. Despite doing a force power off 😪
23-06-2025 11:30 AM
4 weeks ago
3 weeks ago
Yup I was getting the moisture issue too. Now my phone won't charge via cable unless I put the cable in a specific orientation. It didn't start until I updated to the June 1st update about a week ago. I've tried 6 different cables, clearing the USB Cache, etc. It's 100% a software update issue with the USB port, but good to know its something they can presumably fix if we keep reporting it.