Android Systems and Software Repair

≈ 5 min read · Print / save as PDF

Boot modes

Firmware flashing — the responsible approach

1. Identify the exact model number (e.g. Samsung SM-A556E — not just “A55”), region/CSC, and current firmware version (Settings → About phone; or the label/sticker). The model number determines which firmware is correct.
2. Use official firmware only from the manufacturer (Google publishes factory images for Pixel; Samsung firmware is distributed through official channels and widely mirrored — verify file integrity and version).
3. Never downgrade across a bootloader/security version that the device does not allow — anti-rollback protection can hard-brick the phone or the flash will simply fail.
4. Explain data loss: most full flashes erase data. Samsung’s Odin has a “HOME_CSC” file option that attempts to preserve data; “CSC” erases. Even HOME_CSC is not a guaranteed data-safe operation — back up first if the phone boots.
5. Charge the phone to over 50% before flashing.

Samsung Odin procedure (overview)

1. Install Samsung USB drivers on the PC.
2. Extract the firmware: files labelled BL, AP, CP, CSC (and HOME_CSC).
3. Put the phone in Download Mode, connect; Odin shows a COM port.
4. Load BL, AP, CP, and CSC or HOME_CSC into the matching slots.
5. Start; wait for PASS. Do not disconnect.

Google Pixel

Pixel devices can be restored with Google’s web-based Android Flash Tool or with fastboot using the factory image. Flashing factory images requires an unlocked bootloader, and unlocking the bootloader erases the device. On a device where “OEM unlocking” is disabled and the phone won’t boot, use Google’s official rescue/repair routes.

ADB basics

With USB debugging enabled (Settings → About phone → tap Build number 7 times → Developer options → USB debugging):

Diagnostic menus and codes

These are built into many devices. Availability varies by manufacturer, carrier and software version:

Factory Reset Protection (FRP) — ethics and procedure

After a factory reset, a phone with a Google account previously added will ask for that Google account before it can be used. This is FRP — an anti-theft feature.

Shop policy:

• The legitimate solution is for the owner to sign in with their Google account (they can recover the password via Google account recovery), or to provide proof of purchase to the manufacturer’s service centre.
• Do not bypass FRP on devices whose ownership is not verified. “Bypass” tools and services are widely advertised; using them for unverified devices makes the shop part of the stolen-phone trade.
• Prevention: Before accepting a phone for a repair that might need a reset, ask the customer to confirm they know their Google account credentials, or to remove the account themselves.

Network, IMEI and blacklisting

• The IMEI identifies the device on mobile networks. Changing an IMEI (“IMEI repair”) is illegal in many jurisdictions and is a strong indicator of trafficking in stolen phones. Do not offer it.
• If an IMEI is missing/“null” after a board repair (e.g. after damaged EFS/NV data), the legitimate route is the manufacturer’s authorised service.
• In the Philippines, SIM registration is mandatory under the SIM Registration Act (RA 11934). Customers having signal problems should be checked for SIM registration status, the SIM itself, and APN settings before any hardware diagnosis.

Common Android software faults

Watch and read

Review questions

1. Why must you identify the exact model number before downloading firmware?
2. What is anti-rollback protection?
3. Explain the difference between CSC and HOME_CSC in Odin.
4. What is FRP and what is the legitimate way to remove it?
5. Why should a shop never offer IMEI changes?

Lab exercises

Lab 14.1 — Flash official firmware on a Samsung test device with Odin and verify.

Lab 14.2 — Use ADB to read battery data and collect a logcat from a crashing app.

Lab 14.3 — Run the full hardware diagnostics on three Android phones and record results.