← Next Door Tech Academy

Module 01FoundationWeek 1 · 26 min read

Software & Hardware Fundamentals

The vocabulary every mobile technician is expected to own

Module 1 of 120%
01

Welcome

Welcome to Module 1. In this lesson you'll learn the fundamentals of mobile software repair. By the end of this module you'll understand what software is, how it differs from hardware, and why this knowledge is essential before working on Android and iPhone devices.

02

Learning Objectives

  • Define software in your own words.
  • Define hardware and give three mobile examples.
  • Explain the difference between the two layers.
  • Identify software-related problems from customer descriptions.
  • Recognise the five most common repair scenarios on the bench.
03

Prerequisite Knowledge

  • Basic computer usage (mouse, keyboard, windows)
  • How to use Windows File Explorer
  • How to create and rename folders
  • How to install and uninstall applications

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

04

Vocabulary

Driver
Software that allows communication between hardware and the operating system.
Firmware
Software permanently stored on a device's memory that controls the hardware directly.
Bootloader
A small program that starts the operating system when the device powers on.
Flashing
Installing or reinstalling firmware onto a device.
Operating System
The master program (Android, iOS) that manages apps, memory and hardware.
Partition
A named region of the device's storage, e.g. boot, system, userdata.
Kernel
The core of the operating system that talks directly to hardware.
Boot loop
A fault where the device restarts repeatedly instead of reaching the home screen.
05

Why This Matters

Imagine a customer brings in an iPhone that isn't recognised by your computer. If you don't know what a driver is, you'll waste hours troubleshooting a cable, a port, or a laptop that were never the problem. Understanding the software stack lets you find the real fault in minutes instead of guessing.

06

Lesson Content

Lesson 1What is Software?4 min

Software is a set of instructions that tells hardware what to do. You cannot touch it. You can only observe its effects: a screen lighting up, an app opening, a phone vibrating.

On a mobile device, software lives in flash memory. When you 'repair software', you are really replacing or correcting those instructions — you are not changing a single physical part.

That is the whole premise of this programme: a large share of devices declared dead are perfectly healthy machines running broken instructions.

Lesson 2Examples of Software3 min

Android and iOS themselves. WhatsApp and Chrome. The Samsung USB driver on your laptop. Odin, SP Flash Tool and iTunes. The recovery partition on a phone. All of these are software.

Notice that some of it lives on the phone and some of it lives on your workstation. A repair almost always involves both sides talking to each other.

Lesson 3Types of Software5 min

System software runs the machine: the operating system, drivers, and services. Application software does a job for the user: a browser, a camera app, a game.

Firmware sits underneath both, welded to the hardware. It is the layer a technician most often replaces.

Lesson 4System Software5 min

The operating system schedules tasks, manages memory, enforces permissions, and gives applications a safe way to reach the hardware.

Drivers are the translators. Windows does not natively know how to speak to a MediaTek phone in preloader mode; the driver teaches it. Without the driver, your flashing tool sees nothing at all.

Lesson 5Application Software3 min

Applications are the layer customers actually see, and the layer most customers blame. 'My phone is slow' is usually an application-layer complaint, not a firmware fault.

Part of your job is translating what the customer says into which layer is actually broken.

Lesson 6Firmware6 min

Firmware is the complete software package the manufacturer ships for one exact model and region. It contains the bootloader, kernel, system image, modem/baseband, and vendor partitions.

Firmware is model-specific. An A155F package is not an A155M package. Matching firmware exactly to the device is the single most important habit you will build in this programme.

07

Visual Explanation

Power Button
     │
     ▼
  BootROM
     │
     ▼
 Bootloader
     │
     ▼
   Kernel
     │
     ▼
Android Home Screen
The Android boot chain — memorise this order
08

Real-World Example

A customer says: “My Samsung is stuck on the logo.”

What type of problem is this?

A boot loop — the device fails somewhere between bootloader and kernel and restarts.

Possible causes

  • Corrupted firmware
  • Failed OTA update
  • Damaged system partition
  • Incompatible custom ROM or module
09

Technician Tips

Technician Tip

Always install the proper USB driver before opening any flashing software. This one step prevents most connection issues.

Technician Tip

Write the exact model number on the job sheet before you touch anything — not the marketing name the customer used.

Did You Know?

The first stage of the boot chain, BootROM, is burned into the chip at the factory and can never be rewritten. That is why a device with corrupted firmware can still enter emergency download mode.

10

Common Mistakes

Common Mistakes

  • Installing the wrong firmware for the model or region
  • Disconnecting the USB cable during flashing
  • Ignoring battery level before a long flash
  • Flashing without backing up customer data
11

Safety Notice

Safety Notice

  • Never erase customer data without written permission.
  • Verify the device model before flashing.
  • Use a stable, data-capable USB cable and a rear USB port.
12

Hands-on Practice

Exercise 1 — Read your own machine

  1. Open Device Manager on Windows.
  2. Connect an Android phone with a data cable.
  3. Locate the phone in the device tree.
  4. Identify the USB driver, the COM port, and the device name.
  5. Take a screenshot before proceeding.
13

Knowledge Check

Question 1 of 3

Which software allows Windows to recognise your Android phone?

14

Mini Project

Mini Project — Build your bench toolkit

  1. Install Android Platform Tools and add it to your PATH.
  2. Install the Samsung USB driver.
  3. Install the MTK VCOM driver.
  4. Verify that Windows recognises three different phones.
  5. Document each device name, driver and port in your repair log.
15

Reflection

  • What was the hardest concept in this module?
  • What surprised you about how phones start up?
  • How would you explain a driver to a friend who is not technical?
16

Module Summary

Today you learned:

  • Software vs hardware
  • System, application and firmware layers
  • Drivers and why they come first
  • The Android boot chain
  • Boot loops and their common causes
  • Safe bench habits
17

Resources

18

Assignment

Research and write a one-page explanation of the difference between ADB, Fastboot and Recovery Mode. Include when a technician would use each one.

Foundation - Basics — stage assignment

Perform a hard reset on any phone and document the exact key combination you used.

19

Tools for this Stage

Before any flashing utility you master the device itself: hard reset, boot modes, force restart, software fundamentals and how AI now assists diagnosis.

Hard Reset & Boot Mode Reference

Android & iOS

Key combinations for recovery, download and force restart

What it does. A reference of hardware key combinations that place a phone into recovery mode, download/Odin mode, fastboot, or trigger a forced restart with no software installed.

Why it matters. Every repair session begins with getting the device into the right mode. No cable, tool or licence helps if the phone never leaves the normal boot path.

Risks & precautions

  • A factory reset from recovery erases user data permanently.
  • On some Samsung models a wipe prompt is one keypress away from data loss.

Best practices

  • Confirm the exact model before choosing a key combination.
  • Attempt a backup before any reset while the device still boots.
  • Write the combination into the repair log so the next technician does not guess.
⇩ Bootloader & boot mode documentation

Assignment

Boot one Android and one iPhone into their diagnostic mode and photograph each screen.

AI Diagnostic Assistant Workflow

Workstation

Using AI models to triage error codes and firmware choices

What it does. A structured way to feed error strings, log excerpts and device identifiers into an AI assistant to shortlist likely causes and matching firmware before you touch the bench.

Why it matters. AI compresses the search phase of a repair. It does not replace judgement, but it turns a 40-minute forum hunt into a two-minute shortlist you then verify.

Risks & precautions

  • AI can invent firmware versions and file names that do not exist.
  • Pasting customer identifiers into public tools leaks private data.

Best practices

  • Verify every AI suggestion against the manufacturer or a known-good firmware source.
  • Redact IMEI, serial numbers and customer details before pasting logs.
  • Ask for the reasoning, not just the answer, so you learn the diagnostic path.
⇩ ADB & platform tools reference

Assignment

Take one real error code, run it through an AI assistant, then verify or disprove the answer with a primary source.

See all tools by stage ↗
20

Module Test

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