Software, Firmware and Flashing Procedures
What this domain tests
Software, Firmware and Flashing Procedures tests safe recovery of software faults: boot modes, firmware matching, backup, flashing and post-flash verification.
Core rules
- Know the layers: bootloader, kernel, Android/system, baseband/modem. A corrupt bootloader or wrong firmware can hard-brick.
- Recovery, fastboot, download/EDL and DFU modes are model-specific. Confirm the exact model code and region before downloading firmware.
- Charge the battery above 50%, use a reliable USB cable and do not interrupt flashing.
- Back up user data where possible; warn that unlocking or flashing may erase data.
- After flashing, verify IMEI/baseband, network, sensors, camera and charging. Never promise to bypass security or change IMEI; those are illegal or unauthorized in many contexts.
Worked example
A phone bootloops after an update. First try recovery and clear cache; if it still loops, flash the same or newer stock firmware for the exact model. Do not downgrade unless the bootloader allows it. Use the vendor tool, let it verify checksums, and keep the cable connected. After boot, check baseband and IMEI; if they are missing, the firmware or modem partition is wrong. The reasoning: same-version firmware repairs corrupted system files without changing the security version, while a mismatched image can destroy calibration data.
Traps
Flashing a similar model's firmware; using a low battery; pulling the cable during write; using 'custom ROM' files from unknown sources; forgetting to verify network after repair.