How to Fix SCRCPY Not Working After a Samsung Update

If SCRCPY suddenly stops working after a Samsung software update on your phone, you'll need to run through a few simple steps to get it working again. More often than not, SCRCPY will crash immediately after opening or display error messages in the console like this one: Server error: Exception on thread [main,5,main]. Thankfully, the fix is fairly easy, so follow along as we guide you through the process. This will work on any Android device.

What Exactly is Happening?

After installing a Samsung update, users may notice the following issues when launching SCRCPY:

The application window opens and closes immediately

Server error: Exception on thread [main,5,main]
job.Lang.assertionError
A bunch of other text and then just says at the bottom Warn: Device disconnected and the window closes immediately.

A warning appears stating "Device disconnected"

These problems typically indicate an issue with device compatibility, SCRCPY version, or USB debugging settings that were altered by the update.

How to Fix SCRCPY Not Working After a Samsung Update

One of the most common causes of this problem is using an outdated version of SCRCPY. Samsung updates may introduce changes that are incompatible with older builds of the tool.

Visit the official SCRCPY GitHub repository and download the latest version. As of this writing, version 3.2 is the most recent release. Installing the latest version ensures maximum compatibility with your device's updated firmware.

Check Developer Options on Your Samsung Device

Samsung updates can reset or enable new security settings that block USB access. In particular, a feature called "Auto-block" or "USB debugging restrictions" may have been turned on.

To check and adjust your settings:

Open the Settings app on your Samsung device
Go to Developer Options
Make sure "USB debugging" is enabled
Locate and disable any option labelled "Auto-block" or similar, which may block USB debugging

If auto-block was active, turning it off will disable USB debugging. You will need to return to Developer Options and re-enable USB debugging after disabling the auto-block feature.

Reconnect Your Device and Accept Permissions

Once debugging is re-enabled:

Unplug your phone from the computer
Plug it back in
When prompted, accept the "Allow USB debugging" request on your phone
You may optionally check "Always allow from this computer" to avoid future prompts

Launch SCRCPY Again

After updating SCRCPY and verifying your USB settings, relaunch the application. It should now function as expected without crashing or disconnecting.

A Few More Things to Check.

Always verify you are using the latest version of both SCRCPY and your Android platform tools
If problems persist, try restarting your computer and device, or testing with a different USB cable
Consider using a powered USB hub if connection issues remain.

Comments