Module 02FoundationWeek 1 · 12 min read
Set up a workstation that never loses a customer's data
Welcome to Module 2. A disorganised workstation is the number one cause of wrong-firmware disasters. In this module you'll build a clean, repeatable folder system and learn how Windows handles the large archives you'll download every week.
If any of these are unfamiliar, review the Foundation level first.
A technician who cannot instantly find last month's firmware for an A15 will re-download 6 GB while the customer waits. Organisation is a billable skill.
Use one root folder, then Brand / Model / Region-Version. Example: Firmware\Samsung\SM-A155F\INS-A155FXXU1AWK2.
Never rename downloaded files. The filename encodes model, region and build — the exact three things you must verify.
Every job gets a folder named Date_Customer_Model. Inside: Backup, Screenshots, Notes.txt.
Backups go in before any write operation. No exceptions, no matter how routine the flash looks.
Compare the published MD5 with the one you compute locally using certutil -hashfile file.zip MD5.
A half-downloaded firmware will flash happily for two minutes and then brick the device at the system partition.
C:\Repair
├── Firmware
│ └── Samsung\SM-A155F\...
├── Drivers
├── Tools
│ ├── platform-tools
│ └── Odin
└── Jobs
└── 2026-07-30_Ade_SM-A155F
├── Backup
├── Screenshots
└── Notes.txtA customer says: “You flashed my phone last month, can you just do the same thing again?”
How fast can you answer?
Instantly — if your Jobs folder is named by date, customer and model.
Possible causes
Technician Tip
Keep at least 60 GB free. Firmware archives triple in size when extracted.
Technician Tip
Extract to a short path. Deeply nested folders break older flashing tools.
Did You Know?
Odin refuses many firmware files simply because the path contains a space or a non-Latin character.
Common Mistakes
Safety Notice
Exercise 2 — Build the tree
Question 1 of 2
What does an MD5 checksum prove?
Today you learned:
Document your workstation layout with screenshots and explain each folder's purpose in one paragraph.
Foundation - Basics — stage assignment
Perform a hard reset on any phone and document the exact key combination you used.
Before any flashing utility you master the device itself: hard reset, boot modes, force restart, software fundamentals and how AI now assists diagnosis.
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
Best practices
Assignment
Boot one Android and one iPhone into their diagnostic mode and photograph each screen.
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
Best practices
Assignment
Take one real error code, run it through an AI assistant, then verify or disprove the answer with a primary source.
Complete the 2-question knowledge check above plus the assignment. Passing score: 80%.