← Next Door Tech Academy

Module 04BeginnerWeek 3 · 16 min read

Android & iOS Operating Systems

Two philosophies, two repair strategies

Module 4 of 1225%
01

Welcome

Welcome to Module 4. Android and iOS fail in different ways because they are built on different assumptions. Understanding those assumptions tells you which repairs are even possible.

02

Learning Objectives

  • Describe the Android partition layout.
  • Describe how iOS restores differ from Android flashing.
  • Explain OTA updates and why they fail.
  • Identify which faults are repairable in software.
  • Explain activation locks and ownership checks.
03

Prerequisite Knowledge

  • Foundation level complete

If any of these are unfamiliar, review the Foundation level first.

04

Vocabulary

A/B partitions
Two copies of system slots allowing seamless updates and rollback.
OTA
Over-the-air update delivered by the manufacturer.
IPSW
Apple's signed firmware package for iPhone and iPad.
Signing window
The period Apple's servers will approve installing a given iOS version.
FRP
Factory Reset Protection, Google's anti-theft ownership check.
05

Why This Matters

Quoting a customer for a repair that Apple's signing servers will not allow costs you money and reputation. Knowing the platform rules is commercial knowledge, not trivia.

06

Lesson Content

Lesson 1Android partitions6 min

boot, system, vendor, userdata, recovery, modem and persist each hold a distinct role. A fault usually maps to one of them.

Modern devices use A/B slots plus dynamic super partitions, which changes what a tool can safely write.

Lesson 2How iOS restores work6 min

You do not flash an iPhone the way you flash an Android. You request a restore, and Apple's server signs the request in real time.

If the version is no longer signed, the restore fails at the verification step regardless of your tools.

Lesson 3Why OTA updates fail4 min

OTA patches assume untouched partitions. A rooted device, a modified recovery or a full storage volume will abort the update — often into a boot loop.

07

Visual Explanation

┌──────────────┬───────────────────────────┐
│ bootloader   │ starts everything          │
│ boot         │ kernel + ramdisk           │
│ recovery     │ maintenance environment    │
│ super/system │ Android itself             │
│ vendor       │ chipset-specific drivers   │
│ modem        │ radio firmware             │
│ userdata     │ CUSTOMER DATA — protect it │
└──────────────┴───────────────────────────┘
Android storage map
08

Real-World Example

A customer says: “It died in the middle of a system update.”

Which partitions are suspect?

boot and system/super — an interrupted OTA leaves an inconsistent slot.

Possible causes

  • Power loss during update
  • Insufficient storage
  • Modified system
  • Failing flash memory
09

Technician Tips

Technician Tip

Check the signing status before promising an iOS downgrade.

Technician Tip

On A/B devices, try booting the other slot before flashing anything.

Did You Know?

userdata is encrypted on virtually all modern devices, so a wipe is irreversible even at chip level.

10

Common Mistakes

Common Mistakes

  • Flashing a full package when a single partition was faulty
  • Assuming iOS behaves like Android
  • Wiping userdata as a first step
11

Safety Notice

Safety Notice

  • Confirm ownership before removing any lock.
  • Never bypass FRP or Activation Lock on a device you cannot prove belongs to the customer.
12

Hands-on Practice

Exercise 4 — Map a real device

  1. List partitions on a test Android device
  2. Identify which hold customer data
  3. Record the Android and build version
  4. Note whether the device uses A/B slots
13

Knowledge Check

Question 1 of 2

Why can an iOS restore fail even with a perfect IPSW?

14

Mini Project

Mini Project — Platform comparison sheet

  1. Build a two-column comparison of Android vs iOS repair paths
  2. Include tools, limits, and ownership checks
  3. Add three faults that are NOT software-repairable
15

Reflection

  • Which platform feels riskier to you and why?
  • Where would you refuse a job on ethical grounds?
16

Module Summary

Today you learned:

  • Android partitions
  • A/B slots
  • iOS signing
  • OTA failure modes
  • Ownership and locks
17

Resources

18

Assignment

Explain in one page why an interrupted OTA can cause a boot loop, referencing specific partitions.

Beginner - First flashing tools — stage assignment

Flash a Samsung device with sample firmware and record the PASS/FAIL result.

19

Tools for this Stage

Your first two utilities: one that writes Samsung firmware, one that walks an iPhone into DFU reliably.

Samsung Flashing Utility

Windows - Samsung

Odin-class firmware writer for Galaxy devices

What it does. Writes signed Samsung firmware packages (BL, AP, CP, CSC) to a Galaxy device sitting in Download mode over USB.

Why it matters. Most Samsung software faults - boot loops, failed updates, corrupt system partitions - are resolved by writing a matching firmware set. This is the workhorse of an Android bench.

Risks & precautions

  • Firmware for the wrong model or region can hard-brick the device.
  • HOME_CSC preserves data, CSC wipes it - choosing wrong destroys customer photos.
  • Disconnecting mid-write leaves the device unbootable.

Best practices

  • Match the model code and CSC exactly to the label or Settings entry.
  • Use a rear USB 2.0 port and the original cable.
  • Never downgrade below the bootloader binary version in the model string.
⇩ Samsung USB driver download

Assignment

Flash a test Galaxy with a full four-file firmware set and screenshot the PASS message.

iAndroFix DFU Helper

Windows/macOS - iOS

Guided DFU and recovery-mode entry for iPhone/iPad

What it does. Times and guides the button sequence that places an iPhone into DFU mode, and confirms the workstation sees the device before a restore starts.

Why it matters. DFU timing is unforgiving. A helper removes the guesswork so a failed restore points at the device, not at your thumbs.

Risks & precautions

  • A DFU restore erases the device completely.
  • Activation Lock survives the restore - confirm ownership before wiping.

Best practices

  • Check the Apple Account / Activation Lock status before any restore.
  • Use a certified cable; DFU is intolerant of flaky cables.
  • A black screen means DFU; a logo means recovery mode.
⇩ Apple recovery & DFU documentation

Assignment

Put an iPhone into DFU, confirm detection on the workstation, then exit without restoring.

See all tools by stage ↗
20

Module Test

Complete the 2-question knowledge check above plus the assignment. Passing score: 80%.