Mobile Phone Software, Firmware and Flashing
The Software, Firmware and Flashing domain tests the boot chain, flashing tools, file formats and the locks you must respect. Questions ask which tool or file fits a chipset and what to do before and after a flash.
Boot chain and modes
- Power-on runs the bootloader (fastboot or download mode), then the kernel, then Android or iOS. Recovery is a separate small OS for wiping data and applying updates.
- Qualcomm Emergency Download (EDL, 9008) and MediaTek BootROM mode are low-level recovery paths; Apple uses DFU and recovery mode.
- ADB handles apps, logs and file transfer on a booted phone; fastboot handles partitions.
Tools, files and matching
- Samsung: Odin with a .tar.md5 package that must match model and region/CSC. MediaTek: SP Flash Tool with a scatter file. Qualcomm: QFIL with .mbn and .xml files. Apple: iTunes or Finder with the correct IPSW.
- Firmware must match the exact model number, and normally the baseband and CSC or region; a different variant can kill the modem.
Locks and data
- FRP (Google account) and iCloud Activation Lock protect a wiped phone. Only the lawful owner's credentials or an official unlock route may clear them.
- Back up EFS/NV (IMEI) partitions before any risky operation; rooting or unlocking the bootloader normally voids warranty.
Worked example
A phone bootloops after an update. Reasoning: try recovery and wipe cache first because it is non-destructive; if it persists, factory reset; if it still loops, flash the same or newer stock firmware for the exact model and region. Charge above 50 percent and use a good USB cable to avoid a mid-flash brick.
Traps that cost marks
- Flashing another model's firmware to fix a bootloop.
- Unplugging during a flash.
- Using a flashing tool to bypass FRP instead of refusing the job.
- Forgetting that a wrong CSC breaks OTA updates.