How to View an Android Phone With a Broken Screen on PC
For a broken-screen Android, the best PC method depends on the failure mode: if USB debugging was already enabled, Scrcpy is usually the fastest way to view and control the phone on Windows; if the display still works well enough to approve prompts, ApowerMirror or FlashGet Cast may also fit; if the screen is black or the phone is frozen, a recovery tool is often better for extracting data than for live viewing. Android’s USB debugging permission lives in Android Developer options, which is why a dead or unusable screen can block setup so completely. This guide maps cracked, black, frozen, and touchless screens to the exact desktop method that fits each case and the prerequisite you must already have.
What a broken screen means
A broken display does not always mean the same failure. A phone can still boot, show an image, accept touch, or do none of those. The PC method changes with the symptom, because mirroring tools, control tools, and recovery tools do different jobs.
Use this split:
- Cracked but visible: image is still readable, so you can often approve permissions on the phone itself.
- Black screen but phone still powers on: the device may still be running, but you cannot see prompts.
- Touch works but display is damaged: live viewing is possible if you can still tap through setup.
- Touch is dead: you may need OTG input, prior USB debugging, or a recovery path.
Likely causes
Most often, the blocker is permission setup. Android’s USB debugging switch is what many desktop mirroring and control tools need, and Android requires you to approve the connection on the phone itself. Less commonly, the phone is recoverable only through extraction software, especially when the screen is black or the device is frozen. Brand limits matter too; Samsung support is often singled out by recovery tools, but model support can vary and should be checked on the vendor’s support pages before you begin.
Broken screen access methods
Screen mirroring software is the main category for viewing an Android phone on a Windows PC, and some tools also add mouse and keyboard control. scrcpy is a commonly used open-source option for many setups; it works over USB or TCP, does not require root, and its documentation explains the Android device authorization and USB debugging requirements. ApowerMirror supports Android and Windows or Mac, and its Android setup docs use USB debugging plus a USB cable with a Start Now flow on the phone. FlashGet Cast supports WLAN and USB, but it usually requires app installation and login.
For frozen, black, or non-responsive phones, broken Android recovery tools are different. They are built to extract data such as contacts, messages, photos, and WhatsApp, and some list Samsung model support. Aiseesoft lists Windows 11/10/8/7 support, a 1GB RAM or more requirement, and Samsung Galaxy Note 3, Note 4, Note 5, S4, S5, and S6 support. Dr.Fone includes Android Broken Screen Control and Android Screen Mirroring tools. Droid@screen is another technical option; it requires Android SDK Tool and Java on the PC and does not require a rooted phone.
| Broken-screen state | Scrcpy | ApowerMirror | FlashGet Cast | Recovery tools |
|---|---|---|---|---|
| Cracked but visible | Prerequisite: USB debugging already on. Need unlocked phone: usually yes for approval. Prior authorization required: yes, if the device has not been authorized before. Touch/visibility needed: yes, to approve the RSA prompt unless already authorized. Outcome: view and control. | Prerequisite: USB debugging plus USB cable. Need unlocked phone: usually yes. Prior authorization required: yes, to complete setup. Touch/visibility needed: yes, to tap Start Now and Allow. Outcome: view and control. | Prerequisite: app install and login. Need unlocked phone: usually yes. Prior authorization required: yes, for app sign-in and permissions. Touch/visibility needed: yes. Outcome: view and control, depending on configuration. | Prerequisite: accessible phone menus or supported model. Need unlocked phone: not always, but it helps. Prior authorization required: sometimes. Touch/visibility needed: usually yes. Outcome: recover data. |
| Black screen | Prerequisite: USB debugging already on, or prior TCP setup. Need unlocked phone: often yes for first authorization. Prior authorization required: yes, unless already authorized. Touch/visibility needed: not for existing authorization, yes for new prompts. Outcome: view and control if already set up. | Prerequisite: USB debugging already on. Need unlocked phone: usually yes. Prior authorization required: yes. Touch/visibility needed: yes, if approval is still pending. Outcome: view and control if the setup was completed before the failure. | Prerequisite: prior app setup and login. Need unlocked phone: usually yes. Prior authorization required: yes. Touch/visibility needed: yes, if reauthorization is needed. Outcome: view and control if already configured. | Prerequisite: supported brand or model. Need unlocked phone: not always. Prior authorization required: sometimes, depending on the tool and device state. Touch/visibility needed: often not. Outcome: recover data, not live viewing. |
| Touch works | Prerequisite: ability to tap permission prompts. Need unlocked phone: yes for most setups. Prior authorization required: yes, if not already trusted. Touch/visibility needed: yes. Outcome: view and control. | Prerequisite: ability to tap Start Now and Allow. Need unlocked phone: yes. Prior authorization required: yes. Touch/visibility needed: yes. Outcome: view and control. | Prerequisite: ability to finish app setup. Need unlocked phone: yes. Prior authorization required: yes. Touch/visibility needed: yes. Outcome: view and control. | Prerequisite: data-only goal. Need unlocked phone: not always. Prior authorization required: varies. Touch/visibility needed: less often. Outcome: recover data. |
| Touch dead | Prerequisite: USB debugging already on, or OTG mouse. Need unlocked phone: usually yes. Prior authorization required: yes, unless already authorized. Touch/visibility needed: yes, unless previously set up. Outcome: view and control if authorization already exists. | Prerequisite: USB debugging already on, or OTG mouse. Need unlocked phone: usually yes. Prior authorization required: yes. Touch/visibility needed: yes, unless previously set up. Outcome: view and control if authorization already exists. | Prerequisite: prior login plus a working touch workaround. Need unlocked phone: usually yes. Prior authorization required: yes. Touch/visibility needed: yes. Outcome: view and control is less reliable. | Prerequisite: supported device and recovery path. Need unlocked phone: not always. Prior authorization required: sometimes. Touch/visibility needed: often not. Outcome: recover data, sometimes without live access. |
Security matters here. Third-party mirroring tools can show the phone screen, notifications, and message previews on a computer, so only install software you trust on a Windows PC you control. Free or open-source options reduce cost, but they do not remove the need to grant device permissions. Android’s USB debugging guidance also makes clear that developer options are intended for trusted development workflows, not casual sharing.
How to view a broken phone on PC
Start with a cable and check whether USB debugging is already enabled. If it is, a mirroring tool can often show the phone on Windows right away. If it is not, and the screen cannot be used, the path gets much narrower. For live viewing, scrcpy is the first tool to try; for app-based setups, ApowerMirror or FlashGet Cast may fit better.
Use a cable first
- Connect the Android phone to the Windows PC with a known-good USB cable.
- Open Device Manager on Windows and confirm the phone appears under portable devices or Android-related entries.
- If the phone was previously authorized, launch Scrcpy and check for a mirrored window.
- If Scrcpy does not connect, open the mirroring tool you plan to use and look for a USB connection option.
Check whether USB debugging
USB debugging is the permission switch that many mirroring and control tools commonly need. It often blocks setup when the screen is unusable, because Android asks for a trust prompt on the device itself. If you can still read the screen, go to Settings > About phone > Build number and then Settings > Developer options > USB debugging. Android’s developer documentation explains that USB debugging must be enabled from Developer options before a computer can communicate with the device for debugging.
Pick a mirroring tool that matches your setup
- Choose Scrcpy if you want free viewing and control over USB or TCP and do not want root.
- Choose ApowerMirror if you need keyboard and mouse control and can complete the USB debugging flow.
- Choose FlashGet Cast if you already have the app installed and can log in.
- Use a Windows PC as the host, since these workflows are built around desktop control on that platform.
Say your phone has a spiderweb crack but the image still lights up. You can usually complete USB debugging approval on the handset, then move to Scrcpy for a faster desktop view. If the touch panel is the only damaged part, live viewing is the easiest path.
How to control Android from PC
Control requires more than viewing. You need a tool that sends mouse and keyboard input back to the phone, and the phone must accept the connection. Scrcpy and ApowerMirror are the main fit here. Scrcpy’s GitHub documentation states that it can control Android over USB or TCP without root in many setups. ApowerMirror’s Android setup uses USB debugging and a USB cable, and its Android flow includes a Start Now prompt.
Set up Scrcpy
- Install Scrcpy on the Windows PC.
- Connect the phone by USB.
- Enable USB debugging if it is already accessible on the device.
- Launch Scrcpy and use the PC mouse and keyboard for control.
Set up ApowerMirror
- Install the app on the Android phone and the desktop client on Windows.
- Connect the phone with a USB cable.
- Open Settings > Developer options > USB debugging if the phone screen still works.
- On the phone, tap the Start Now prompt and approve any permission dialog.
Use keyboard and mouse control
Once the mirror is live, a mouse can replace touch and a keyboard can handle text entry, code fields, and search boxes. That is useful for extracting photos, exporting contacts, or signing into a cloud app on the phone. It does not fix a dead display by itself; it only works after the connection exists.
Suppose the screen is visible but the touch panel does nothing after a drop. In that case, a USB cable plus Scrcpy can be enough to unlock the device, copy files, and shut down risky notifications without touching the glass again.
How to recover data from a black screen
If the screen is black but the phone still works, data recovery tools are often a better bet than live mirroring. They are designed for frozen, crashed, black-screen, and non-responsive devices, and they may extract contacts, messages, photos, and WhatsApp data. Check Samsung support first if that is your device family, because model support can be specific, and vendor support pages are the most reliable place to confirm it.
Use recovery software
- Install the recovery tool on a Windows PC that meets the stated requirements.
- Connect the phone with a USB cable, since many tools start with wired detection.
- Select the broken-screen or black-screen recovery option.
- Choose the data type you need first, such as contacts, messages, photos, or WhatsApp.
Check Samsung support first
- Look for your exact model in the tool’s support list before you begin.
- For Samsung, verify whether the model is named explicitly, not just the brand.
- If the tool lists your model, continue with the recovery workflow.
- If it does not, switch to another tool rather than guessing.
Look for contacts, photos, messages, and WhatsApp
Recovery tools are strongest when the goal is data, not live control. Aiseesoft’s broken Android extraction path is built for frozen, crashed, black-screen, and non-responsive phones, and its Samsung list includes Galaxy Note 3, Note 4, Note 5, S4, S5, and S6. Dr.Fone also includes broken-screen control and mirroring tools, which makes it a candidate when you need more than file extraction.
What if my Android screen is black but the phone still works?
Try a wired desktop method first. A black screen with a live phone often means the device is still responsive, but you cannot see prompts, so the best next step is a USB cable, then either an already-authorized mirror or a recovery tool. If USB debugging was never enabled, viewing is much harder than data extraction.
Try a different cable or port
- Swap to a known-good USB data cable, not a charge-only cable.
- Move the connection to a rear USB port on the Windows PC.
- Reconnect and wait for Windows to detect the phone again.
- Retry Scrcpy or the recovery tool after re-plugging.
Use a different desktop method
- Try Scrcpy first if USB debugging was already on.
- Try ApowerMirror if you can still approve Android prompts.
- Try FlashGet Cast if the app was already installed and logged in.
- If none connect, move to a recovery-only workflow.
If USB debugging is off, what works?
If USB debugging is off and the screen cannot be used, live viewing usually fails because Android cannot finish the trust prompt. In that case, your realistic options narrow to OTG input if touch is dead, a previously paired or already-authorized tool, or a recovery program that can pull files from a supported device without relying on a fresh debug authorization.
Step up from mirroring to data extraction. That means using a recovery tool with black-screen support, then selecting the files you need most. If the device is a Samsung model with explicit support in the tool, that path is often the fastest remaining option.
Prevention is simple: enable USB debugging before the screen fails, and keep a trusted USB cable in your kit. That one setting can turn a dead display from a wall into a manageable desktop session.
Still not working?
If the phone never appears on the PC, or the tool cannot get past permission prompts, stop forcing the same method. The next escalation is either a different recovery program, an OTG mouse if touch is dead, or professional data recovery if the data matters more than the handset.
- Try another USB port and another data cable.
- Use a second Windows PC to rule out driver issues.
- Switch from mirroring to recovery software if the screen is black.
- Use brand-specific support paths for Samsung when the tool lists your exact model.
- Seek vendor or repair support when the device will not enumerate over USB at all.
Frequently asked questions
How to control Android from PC with a broken screen
Control requires a mirroring tool with input support, not just screen display. Scrcpy can send mouse and keyboard input over USB or TCP, and ApowerMirror also supports keyboard and mouse control from PC. Without USB debugging or prior authorization, control usually stops at the permission screen.
Can I mirror a broken Android screen with USB debugging?
Yes. USB debugging is one of the main enablers for Android-to-PC mirroring and control tools. It is often required over USB, and it can block setup if the display cannot be used to approve the prompt. That is why a previously enabled setting matters so much.
Which tools work for Samsung phones with broken screens?
Samsung support is often strongest in recovery tools, but model support still matters. The same source lists Samsung Galaxy Note 3, Note 4, Note 5, S4, S5, and S6 support, and Dr.Fone includes broken-screen control plus screen mirroring tools. Check the exact model before you start.