{"id":2258,"date":"2026-02-18T09:10:16","date_gmt":"2026-02-18T09:10:16","guid":{"rendered":"https:\/\/www.digi4u.co.uk\/blogs\/?p=2258"},"modified":"2026-11-10T01:10:32","modified_gmt":"2026-11-10T01:10:32","slug":"why-your-phone-screen-shows-lines-black-spots-or-no-display-and-what-you-can-do","status":"publish","type":"post","link":"https:\/\/www.digi4u.co.uk\/blogs\/why-your-phone-screen-shows-lines-black-spots-or-no-display-and-what-you-can-do\/","title":{"rendered":"Phone Screen Lines, Black Spots or No Display: Causes & Fixes"},"content":{"rendered":"

Lines, black spots or a blank display on a phone screen are usually a hardware panel or flex fault once software glitches are ruled out. Restart and safe-mode checks come first; if the artefact remains during boot or recovery, plan a model-matched screen replacement or a professional diagnosis rather than endless soft resets.<\/p>\n

Last updated:

Digi4u is a Cardiff-based UK supplier of replacement screens, tools and related parts. This update keeps the original symptom \u2192 self-check \u2192 DIY decision flow, tightens the answer-first diagnosis, and removes vague \u201cbuy anywhere\u201d claims in favour of model-matched parts and clear refuse criteria.<\/p>\n

\n\"Phone
\n<\/figure>\n

1. Identify the symptoms<\/h2>\n

Name what you see before you order a part. Different artefacts often point to different layers of the display stack.<\/p>\n\n\n\n\n\n\n\n\n\n\n
What you see<\/th>\nCommon hardware meaning<\/th>\nSoft checks first?<\/th>\nTypical next step<\/th>\n<\/tr>\n<\/thead>\n
Vertical or horizontal coloured lines<\/td>\nPanel row\/column damage, cracked glass into the LCD\/OLED, or a stressed display flex<\/td>\nYes \u2014 restart \/ safe mode<\/td>\nIf lines survive boot: display assembly diagnosis<\/td>\n<\/tr>\n
Single bright green \/ pink line (often after drop or heat event)<\/td>\nFrequently an OLED panel failure that software cannot clear<\/td>\nYes \u2014 once<\/td>\nWarranty \/ service check, then screen replacement<\/td>\n<\/tr>\n
Black spots or expanding dark blotches<\/td>\nDead pixels, pressure damage, liquid under glass, or OLED burn\/delamination<\/td>\nLimited value if spots are stable<\/td>\nInspect for impact\/liquid; replace screen if hardware<\/td>\n<\/tr>\n
Flicker or colour shift<\/td>\nLoose connector, failing backlight\/OLED driver path, or software refresh bug<\/td>\nYes<\/td>\nIsolate software; then connector \/ panel test<\/td>\n<\/tr>\n
No display but phone vibrates \/ rings<\/td>\nPanel dead, backlight\/OLED rail fault, or cable unseated after impact<\/td>\nForced restart<\/td>\nConfirm power, then display path diagnosis<\/td>\n<\/tr>\n
Image OK but touch dead in zones<\/td>\nDigitizer damage (may be separate from image panel on some models)<\/td>\nAssistiveTouch \/ touch test apps<\/td>\nConfirm digitizer vs full assembly needs<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Persistent green or pink lines on AMOLED phones are widely treated as hardware damage that only a display assembly swap fixes \u2014 soft resets do not rewrite a failed panel row. That matches what owners see after drops, flex stress or some heat events.<\/p>\n

2. Self-diagnosis: what you can check<\/h2>\n

Even without opening the phone, you can separate many software glitches from panel damage.<\/p>\n

a) Soft reset and power cycle<\/h3>\n

Restart the phone. A temporary compositor or driver glitch can mimic lines for a short time. If the screen is black, try the manufacturer\u2019s forced-restart sequence. On Android, boot to safe mode when possible; on iPhone, use the forced restart for your model. If lines or spots remain on the boot logo or recovery screen, treat the fault as hardware until proven otherwise.<\/p>\n

b) Check for physical damage<\/h3>\n

Look for cracks, deep pressure marks, bent frame corners and liquid indicators. Impact can crack the glass without shattering it and still shear display rows. Liquid under the panel often shows as expanding dark patches rather than a single hairline crack.<\/p>\n

c) Inspect the screen connector (experienced users only)<\/h3>\n

Only open the device if you have a model-specific guide, the correct bits and a plan to disconnect the battery first. A partially seated display flex can cause flicker, lines or black bands. Do not force a connector or poke metal into the socket. If you are not ready for that level of work, skip to professional diagnosis \u2014 see our diagnose-before-DIY tools guide<\/a>.<\/p>\n

d) Test touch responsiveness<\/h3>\n

Use built-in tools (for example AssistiveTouch on iPhone) or a known touch-test pattern on Android. Dead touch zones with a perfect image can mean digitizer damage; dead image with working touch still points at the panel or backlight\/OLED path.<\/p>\n

e) Isolate software vs hardware<\/h3>\n

If artefacts appear in recovery, download mode or during boot before the OS UI loads, software settings are unlikely to be the root cause. If artefacts appear only inside one app, update or remove that app before ordering a screen.<\/p>\n\n\n\n\n\n\n\n\n
Test result<\/th>\nInterpretation<\/th>\nAction<\/th>\n<\/tr>\n<\/thead>\n
Lines vanish after restart \/ safe mode<\/td>\nLikely software or temporary glitch<\/td>\nUpdate OS; monitor; avoid opening the phone<\/td>\n<\/tr>\n
Lines visible on boot logo \/ recovery<\/td>\nHardware display path<\/td>\nPlan screen diagnosis \/ replacement<\/td>\n<\/tr>\n
Lines after a drop, even with tiny crack<\/td>\nImpact damage to panel or flex<\/td>\nDo not flex the chassis further; quote screen<\/td>\n<\/tr>\n
New screen still shows same lines<\/td>\nBoard, FPC socket or cable remaining on chassis<\/td>\nStop swapping panels; escalate diagnosis<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

3. Consider DIY screen replacement<\/h2>\n

DIY screen work is realistic when the model has a clear guide, the fault is isolated to the display assembly, and you accept seal and True Tone \/ calibration trade-offs on some brands. It is a poor first project when the phone has liquid damage, a bent frame or an uncertain board fault.<\/p>\n

a) Choosing the right replacement screen<\/h3>\n