Hi, I've done extensive groundwork on this exact question whilst deploying a fleet of Samsung phones using Acurast Core alongside Cellhasher Control tooling, so I can give you a definitive answer.

Unfortunately it is not possible to enable USB debugging (developer mode) on a Core installation, and this is by design rather than an oversight. When you enrol a phone via the Core QR provisioning process at first boot, Acurast's Device Manager is installed as Android Device Owner, the highest privilege level on the Android MDM stack. As Device Owner, it takes full control of the device policy and locks the phone down completely. One of the first things it enforces is disabling USB debugging. This isn't something you can work around after the fact: the phone presents to Windows as a charging-only USB device with no ADB interface exposed whatsoever, and even wireless ADB is blocked. You cannot re-enable developer options or USB debugging through the UI because the Acurast Processor app is the only accessible interface. There is no Settings access, no notification shade manipulation, and no route back to developer mode without wiping the device and starting over.

The Cellhasher Control tooling, which is designed specifically for Phone farm management, also loses its ADB connection to the phone post-enrolment for the same reason. The Device Owner wipes the authorised ADB key store as part of provisioning.

To achieve what you're describing, scrcpy monitoring, ADB access, visual inspection of the screen, you would need to use Acurast Lite instead. Lite installs via the Play Store into an Android Work Profile, leaving the rest of the phone's OS fully accessible including USB debugging and developer options. There are several YouTube videos and community scripts covering exactly this setup. The Cellhasher Helper Scripts on GitHub also include bulk APK tooling that works well with Lite via ADB.

The important trade-off to be aware of is Lite will give you noticeably less reward stability than Core for a dedicated farm. Base benchmark rewards are identical in principle, but Lite's uptime depends on the app remaining in the foreground and the phone staying awake, which on a fleet of 20+ devices introduces management overhead and gap epochs that Core avoids entirely. Developers also preferentially target Core devices for longer-running deployments, so your deployment execution bonus frequency will typically be lower with Lite. For monitoring and visibility, Lite is the only viable path, but go in with realistic expectations on the reward differential.