UPMSP High School Mobile-Phone Repair - Code 980 common mistakes
UPMSP High School Mobile-Phone Repair - Code 980 · Understand the traps and how to avoid them.
When asked to demonstrate ESD-safe handling of a phone, the candidate picks up the bare logic board by the edges with ungrounded hands, wears no wrist strap, and works on a wooden bench without a mat, treating the anti-static step as optional talk.
Candidates memorise 'use an ESD strap' as a sentence for the theory paper but never practise it, because during informal repair they have never seen a board fail immediately from static; the damage is latent (gate-oxide degradation) and shows up days later, so the habit never forms.
What to do instead
Drill a fixed entry routine: wrist strap clipped to a grounded point, dissipative mat under the work, board lifted only by the shielded frame or with insulated tweezers, battery disconnected first. Rehearse it aloud in mock practicals until it becomes automatic, and be able to state why CMOS inputs are damaged by as little as a few tens of volts of body charge.
The candidate holds a hot soldering iron by the barrel or cable, leaves it lying across the bench instead of in the stand, and reaches over the tip to move a wire; when asked about fume control they say 'I hold my breath'.
In real shops the iron is often a cheap unregulated one with a short or damaged cord, and speed is rewarded over safety, so the candidate has never been taught iron placement, tip orientation, or that flux fumes are a respiratory hazard needing extraction.
What to do instead
Adopt the standard sequence: iron always returned to the stand between joints, tip pointing away from the body, cable routed behind the bench, fume extractor or open ventilation at the tip, eye protection when clipping leads. For mains-powered irons, check the earth and cord before use and state the burn first-aid step (cool running water, no ice, no ointment).
Asked to measure a battery rail or a charging current, the candidate sets the multimeter to the current range and probes the supply points in parallel, or measures resistance on a live board, blowing the meter fuse or getting a false reading.
The dial positions look similar and the candidate has learned 'black on COM, red on V' without understanding that current must be measured in series and resistance only on a dead, unpowered circuit; the difference between voltage, current and resistance measurement topology was never practised.
What to do instead
Practise the three measurements on a battery-and-resistor breadboard until the probe placement is reflexive: volts in parallel with power on, amps in series with the circuit broken, ohms only with power removed and capacitors discharged. Before every measurement, say the mode, the expected value and the probe points out loud; verify the meter on a known source first.
When a phone is dead, the candidate immediately starts reballing or replacing the PMIC, or flashes firmware at random, instead of first checking charger, cable, battery voltage, charging-port continuity and current draw on a power supply.
Candidates equate 'advanced repair' with chip-level work and skip the free, fast checks; they also lack a mental model of the power-on sequence (charger detection, PMIC rails, clock, reset, boot), so they cannot localise the fault and guess instead.
What to do instead
Use a fixed triage ladder written on the bench card: visual and liquid-damage inspection, charger/cable/port, battery voltage and internal resistance, current draw pattern on a bench supply (no draw, short, boot loop), then voltage rails, then firmware, then rework. Justify each step by what its result rules out, and record readings so the diagnosis is evidence-based.
The candidate cannot distinguish a hardware fault from a software fault: a phone stuck on the logo is declared a 'motherboard failure' and sent for rework, while a genuinely shorted rail is 'fixed' by a factory reset that wipes the customer's data.
Both faults present as 'not booting', and the candidate has memorised symptoms rather than the decision criteria - recovery-mode behaviour, current-draw signature, whether the device responds to flashing tools, and whether the fault appeared after an update or after a drop.
What to do instead
Learn a two-column decision table: what a hardware fault does under each test versus what a software fault does. Practise on training handsets with deliberately corrupted firmware and with a pulled component, and always attempt non-destructive diagnostics (recovery mode, current draw, flashing-tool detection) before any data-destroying step, with customer consent recorded.
During SMD rework the candidate sets the hot-air station to maximum temperature, holds the nozzle still over one spot, and lifts the component before the solder has fully melted, tearing pads and cooking the board; flux is omitted entirely.
Higher temperature feels faster and the candidate has no feel for reflow; without flux they cannot see the moment of melting, and without preheating the board wicks heat away so they compensate by turning the temperature up further.
What to do instead
Fix a written profile: preheat the board area, air temperature in a moderate range with adequate airflow, nozzle moving in small circles, flux applied before heating, and the part lifted only when it floats free under light tweezer pressure. Practise on scrap boards with a timer and a temperature log until pad-lifting becomes rare, and know the reflow temperature range of leaded versus lead-free solder.
The candidate quotes an IMEI or writes a new one, or unlocks a network/SIM lock, without checking ownership documents or the law, and treats IMEI alteration as a routine repair task.
Shops in the informal market sometimes offer this work, so the candidate assumes it is normal service; they have not been taught that IMEI identifies the device on the network, that altering or cloning it is a criminal offence in most jurisdictions, and that a mismatched IMEI signals a stolen or rebuilt handset.
What to do instead
Learn the rule and the script: verify IMEI against the box and the customer's ID or purchase proof, explain that IMEI repair or cloning is illegal and refused, and record the refusal. Be able to explain what IMEI is, how to check it on the handset, and why a blacklisted IMEI cannot be 'fixed' by software. Know the legal SIM-lock and warranty boundaries in your own market.
The candidate explains a repair to a customer in jargon ('your PMIC rail is shorted, I'll reball the CPU'), gives no written estimate, keeps the phone without a job sheet or receipt, and does not state the data-backup risk before flashing.
Technical training rewards component knowledge and gives almost no practice in customer-facing language; candidates fear that plain language sounds unprofessional, and shops without paperwork culture treat the job sheet as bureaucracy.
What to do instead
Rehearse a three-part explanation: what is wrong in plain words, what you will do and what it costs, what could still go wrong (data loss, no fix, further fault). Always complete a job sheet with IMEI, accessories received, fault as reported, estimate, consent signature and data-backup acknowledgement, and give a receipt with a warranty period. Practise role-play with a 'difficult customer' scenario.
In the viva or project presentation the candidate can describe a repair but cannot explain the underlying principle - for example cannot say why a lithium-ion battery needs a charge-control IC, what the antenna does, or how the display and touch interfaces differ - and answers 'I saw it on a video'.
Practical skills are learned by imitation, and candidates never connect the block diagram to the fault they fixed; the project is treated as a formality to be submitted rather than a system to be understood.
What to do instead
For every repair, write a one-page fault note linking symptom, measurement, component function and block in the architecture. Build a hand-drawn block diagram of a smartphone (power, charging, RF, display/touch, audio, sensors, storage) and be able to place each replaced part on it. In the viva, answer with the principle first, then the observation, then the action.
The candidate prices repairs by copying a competitor or by gut feel, ignores the cost of parts, rent, electricity and their own time, keeps no record of jobs or stock, and cannot answer a question about working capital or break-even.
Entrepreneurship content is studied as definitions to be memorised for the paper, not as arithmetic applied to the candidate's own imaginary shop; the candidate has never built a cost sheet, so the concepts stay abstract.
What to do instead
Build a real one-page cost sheet for a sample repair: part cost, consumables, time at a stated hourly rate, overhead share, margin, and the price quoted. Work out monthly fixed costs, break-even number of jobs, and a simple cash-flow and stock register. Be ready to explain why under-pricing warranty returns and rework destroys profit, and keep a job register that supports the numbers.