Can a Manufacturer Legally Brick Your Device After a Repair?

You replace a cracked screen with a third-party part, the phone works for a week, then an update lands and it refuses to boot. The question is whether that is the manufacturer enforcing its warranty, or the manufacturer breaking something you own. The honest UK answer is "it depends on three separate bodies of law, and none was written with this in mind".

This is general information, not legal advice. I will mark which bits are statute, which are interpretation, and which are me having an opinion.

First, how a device gets bricked by an update

The mechanism matters, because the law cares about intent and foreseeability. Roughly, there are three flavours:

• Parts pairing: the firmware stores serial numbers of components (screen, battery, fingerprint sensor) and refuses to run if they no longer match.
• Signature checks: the bootloader or a security chip validates a component, and a replacement fails the check.
• A deliberate kill switch: the update looks for evidence of third-party repair and disables a feature or the whole device.

The first two can be sold as security. The third is much harder to dress up. A court or regulator would probably treat them differently, though that is my reading, not a decided rule.

Quick detour: Error 53

Hang on, this has actually happened. In early 2016, some iPhones that had a Touch ID sensor replaced by a non-Apple repairer showed "Error 53" after an iOS update and became unusable. Apple said it was a security check, then issued a fix and apologised for the effect on customers. Nobody in the UK got a definitive court ruling out of it, as far as I know, so it is a useful case study but not a precedent.

The contract: what you actually agreed to

Start with the terms. Software licences usually say the vendor may update, and may disable features if the device has been "tampered with". That clause is where manufacturers hope the argument ends.

It does not end there. Under the Consumer Rights Act 2015, a term in a consumer contract has to be fair and transparent (Part 2), and it is not binding if it is unfair. A term letting a trader degrade a product you paid for, because of a repair that the law permits, is the sort of term a court would look at hard. Whether it is unfair depends on the wording and the facts.

The goods: satisfactory quality does not stop at delivery day

Goods must be of satisfactory quality, fit for purpose and as described. Software that ships on the device is generally treated as part of the goods, and the Act has separate rules for digital content. For the first 30 days you have a short-term right to reject; after that, repair or replacement, then a price reduction or final right to reject, within the usual time limits.

The catch: the Act protects against faults that were there at the time of supply. If the device was fine when sold and an update later disables it after a repair, the quality argument is weaker. It is stronger if the update was part of what the trader supplied or promised to keep working. Courts have not, to my knowledge, settled this for post-sale updates, so treat it as contested.

Where the Computer Misuse Act comes in

This is the interesting bit. Section 3 of the Computer Misuse Act 1990 covers unauthorised acts done with intent to impair the operation of a computer, or to prevent access to programs or data on it. An act is unauthorised where the person is not entitled to decide whether it may be done and has no consent from someone who is.

On paper, a deliberate kill switch aimed at repaired devices looks uncomfortably close to that. The manufacturer's defence is consent: you accepted the update and the terms. Whether that consent covers a hostile payload nobody told you about is an open question, and I know of no UK prosecution on these facts. Prosecutors also have little appetite for this kind of dispute. Treat it as a pressure point, not a remedy.

What you can do in practice

1. Keep the receipt for the device, the repair and the parts, and screenshots of any error message.
2. Write to the retailer first, not the manufacturer. Under the Consumer Rights Act your contract is with the seller.
3. If the retailer refuses, use the Section 75 route if you paid by credit card over £100 and up to £30,000, or ask your card provider about a chargeback.
4. Consider the small claims track in the county court, which exists for disputes like this one.
5. Report a suspected deliberate disabling to Trading Standards via Citizens Advice, since patterns matter more to regulators than single complaints.

What repairers and tinkerers should check

If you repair devices, avoid claims that parts are "official" or "genuine" unless they are. Tell customers when a part may trigger a warning. The Digital Markets, Competition and Consumers Act 2024 reworked the unfair commercial practices rules from April 2025, and misleading omissions are exactly the kind of thing it covers.

My opinion: a device that stops working because of a lawful repair is a defect the seller caused by design, and the law should say so plainly. At the moment it makes you assemble the argument from contract fairness, quality duties and a criminal statute from 1990. That is a lot of paperwork for a phone screen.