A phone that suddenly misbehaves does not tell you whether something inside it broke or whether the software is confused. Both look identical from the outside, and people replace working phones over problems a restart would have cleared.
There is a sequence that separates the two, and it takes about fifteen minutes. Work through it in order, because each step rules something out that the next one depends on. If you get to the end and the problem is still there, that is your answer, and you can bring the phone to either of our shops in Richmond or North Vancouver for a free look.
Why the same symptom can have two causes
Software failures interrupt how components talk to each other. When that happens, a healthy camera reports as missing, a healthy battery reports the wrong level, and a healthy screen stops registering touch. The part is fine. The message about the part is not.
Not sure what your repair should cost? Get a free estimate from Gadget Ali before any work starts, with no obligation.
Two patterns separate them more reliably than any single symptom. Software problems fluctuate. They come and go, change with what you are doing, and often clear temporarily after a restart. Hardware problems are consistent and repeatable, and they tend to get worse rather than better.
Neither pattern is proof on its own. A failing battery connector can look intermittent, and a corrupted system file can look permanent. That is why the tests below matter more than the symptom.
Start by asking what changed
Write down when it started and what happened just before. A system update, a new app, a drop, a wet pocket, a long charge in a hot car. This single question resolves more cases than every test that follows.
If it started right after an update, software is the first suspect. A jump in battery drain or heat in the days after a major release is usually background indexing settling down rather than a failing part. There is more on that in our guide to why phones overheat after a system update.
If it started right after an impact, stop testing. Something moved inside. Software checks will not fix that and delaying makes it worse.
If nothing changed at all, note that too. A fault that appears out of nowhere on a phone that has not been touched is more often age and wear than software.
The restart test, and what it rules out
Do a full restart, not a screen lock. Power the phone completely off, wait ten seconds, and start it again. This clears memory and reloads every background process from scratch.
If the problem disappears, it was software. Not necessarily fixed, but software. Note whether it comes back, and how long it takes.
If it disappears and returns within hours, something is relaunching. That is an app or a system process, and the next test finds it.
If nothing changes at all, that is meaningful. A fault that survives a clean restart is unlikely to be a passing glitch.
Safe mode: the fastest way to blame an app
Safe mode starts the phone with third party apps disabled. Everything you installed is switched off and only the system runs. If the problem vanishes in that state, one of your apps is responsible.
On Android, hold the power button, then press and hold Power off until safe mode is offered. A small safe mode label appears at the bottom of the screen once it starts.
iPhones have no equivalent, so remove instead. Uninstall anything added in the week before the problem started, one at a time, and watch what happens between each one.
A problem that persists in safe mode is either the system or the hardware. That narrows things considerably and takes about two minutes.
Built-in diagnostic codes most people never use
Samsung phones have a full hardware test menu behind a dial code. Open the phone dialler and enter *#0*#. A grid appears letting you test the display for dead pixels, each speaker, the microphone, the touch layer, the sensors and the vibration motor individually. It is the single most useful check on this page.
Many other Android phones respond to *#*#4636#*#. That opens an information menu with battery and network detail. Support varies by manufacturer, so it may simply do nothing.
iPhone has no user facing equivalent. The closest checks are Settings, then Battery, then Battery Health for capacity, and Apple’s own remote diagnostic run through their support team.
A component that fails its own test is hardware. If the speaker test produces no sound, no amount of software work will change that.
When a factory reset is worth doing
It is the last test, not the first. A reset wipes the phone back to a clean system. If a fault survives that, it is hardware in almost every case.
Back up first, and check the backup actually completed. Not started. Completed. This step gets skipped constantly and it is the one that costs people photos.
Make sure you know the account password before you wipe anything. Both iPhone and Android lock to the account that was signed in, and the phone will ask for that password on the first screen after a reset. Without it the device stays locked, and no repair shop can unlock it for you. This catches people out more than any other step here.
Test it before restoring your backup. Restoring immediately puts back whatever was causing the problem. Use the phone clean for an hour first.
Symptoms that skip the software checks entirely
A swollen battery. If the phone rocks on a flat table, the screen is lifting at an edge, or the back is bulging, stop using it and bring it in. That is a safety issue and testing it changes nothing.
Any smell of burning, or heat you cannot hold. Power it off and leave it off.
Liquid exposure, even if it seems fine. Corrosion works quietly for days before anything visible happens, and the phone brought in the same day fares far better than one that sat in a drawer.
Visible physical damage. Cracked glass, a bent frame, a loose port. Our guide on what to do about a cracked phone screen covers what to check on the display specifically.
What your symptom probably points to
It will not charge, or only charges at one angle. Usually the port or the battery, and telling those apart has its own method. See our guide on whether a charging problem is the port or the battery.
It will not turn on at all. Often power related rather than dead, and there is a sequence worth trying before assuming the worst. Our guide on an iPhone that will not turn on walks through it.
Battery health falling faster than it should. There is a normal rate of decline and a rate that indicates a problem. Our guide on battery health dropping fast explains the difference.
Running hot during light use. Almost always software when it starts after an update, more often hardware when it does not. Our guide on an overheating iPhone covers both.
Nobody can hear you on calls. If it began after a drop, the microphone assembly is the likely cause. See our guide on a microphone that stopped working after a drop.
Face ID has stopped recognising you. This one is worth diagnosing carefully because the sensor array is not a routine part. Our guide on Face ID that has stopped working explains what can and cannot be repaired.
The screen dims on its own. Usually a setting or thermal management rather than a failing display. Our guide on a screen that dims randomly goes through the causes.
Battery drain that started with a new iOS version. Usually temporary, with a point at which it stops being temporary. Our guide on battery drain after the iOS 26 update covers what to expect.
A laptop that will not charge while plugged in. Different device, same logic. See our guide on a laptop plugged in and not charging.
A Mac running hot with the fans constantly up. The first thing that matters is which chip is inside, because Intel and Apple silicon machines need completely different things. Our guide on a MacBook running hot with loud fans splits it along that line.
When to stop testing and get it looked at
When the fault survives a reset. At that point you have eliminated software as thoroughly as anyone can from the outside.
When it is getting worse week to week. Deterioration is a hardware pattern. Software faults tend to stay roughly where they started.
When two or three things are wrong at once. Multiple symptoms appearing together often share one physical cause, and a technician can identify that far faster than testing each one separately.
When you would rather not risk the reset. That is a reasonable position. Bring the phone in and we will run the checks without wiping anything. For the full range of what we work on, see our phone repair page.
Not sure what you are looking at?
Bring the phone into either shop and we will run the checks in front of you and tell you what we find. Nothing gets wiped, nothing gets opened, and nothing gets quoted until you know what is wrong. Walk in during business hours at 6551 No. 3 Rd in Richmond or 935 Marine Dr in North Vancouver.
You can also describe the symptom and tell us your model and we will tell you what it usually turns out to be. The inspection costs nothing either way.
Still deciding where to take your device?
Gadget Ali repairs phones, tablets, laptops and game consoles at two Metro Vancouver locations, Richmond and North Vancouver. Walk in without an appointment, or send us your device model and the issue and we will come back with a clear price range.
There is no charge for the diagnostic, and no obligation to proceed. Most screen and battery repairs are finished within a few hours.
Frequently Asked Questions
Can a software problem look exactly like a broken part?
Yes, and it regularly does. Overheating, rapid battery drain, unresponsive touch and a camera that will not open can all be caused by software. The tests above are what separate them, because the symptom alone will not.
Does a factory reset prove the problem is hardware?
It is the strongest evidence available without opening the phone. If a fault continues on a clean system with no apps installed, it is hardware in almost every case. Back up first and make sure you know the account password, or the phone will lock after the wipe.
Is there a way to test my phone's hardware myself?
On Samsung, dial *#0*# to open a built-in test menu covering the display, speakers, microphone, touch and sensors. Many other Android phones respond to *#*#4636#*#. iPhone has no user facing equivalent, though Battery Health under Settings shows capacity.
Why does my phone problem come and go?
Intermittent behaviour usually points to software, since background processes restart and conditions change. It is not conclusive though, because a loose internal connection produces the same pattern.
Can ignoring a software problem damage the phone?
It can. Sustained overheating from a process stuck in a loop puts real thermal stress on the battery and the board, and repeated heat cycles shorten battery life. A fault causing heat is worth resolving rather than living with.