Mobile › Module 4 › Lesson 1
adb Literacy
adb names Android Debug Bridge — shell, install, logcat literacy on YOUR $MOB_LAB device; not unauthorized access to stranger hardware.
Visual · t27_adb_literacy
adb literacy. $MOB_LAB only. Original Cyberlium.
Opening
adb is root-like on debug builds — literacy names commands and risks before you plug in unknown USB.
adb devices lists authorized hosts. adb install pushes lab APKs. adb shell opens device shell — dangerous on misconfigured devices. adb logcat streams logs — redact PII in notes. USB debugging authorization prompt must be on YOUR $MOB_LAB emulator or enrolled lab phone only. Cyberlium treats adb as tool literacy on YOUR $MOB_LAB — verify serial matches inventory — never adb into found or borrowed daily-driver phones without owner test consent. Next: Frida Named.
1. adb commands (named, lab device only)
adb devices -l: list connected emulators/serials. adb install -r: reinstall lab APK. adb shell pm list packages: inventory — use only on $MOB_LAB. adb logcat: runtime logs for debugging YOUR app — truncate sensitive lines in notes.
On $MOB_LAB, list five adb commands you may use on lab device and one you refuse on stranger hardware.
Command guide
Try these commands — adb commands (named, lab device only)
═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)
ADB docs — https://developer.android.com/tools/adb (lab emulator literacy) OWASP MASTG dynamic — https://mas.owasp.org/MASTG/0x05e-Testing-Code-Quality-and-Build-Settings/ Android emulator — https://developer.android.com/studio/run/emulator
═══ INSTALL ═══
Linux (Debian/Ubuntu):
Command — copy this
sudo apt install adb # or Android platform-tools
macOS:
Command — copy this
brew install android-platform-tools
Windows: Install Android platform-tools / SDK
═══ LINUX / macOS ═══
Command — copy this
export MOB_LAB=${MOB_LAB:-$HOME/cyberlium-lab/t27-mob}
command -v adb >/dev/null && adb version | head -3 || echo 'adb not installed — see Android platform-tools docs'
command -v adb >/dev/null && adb devices -l || true
grep -E 'emulator|NEVER|stranger' "$MOB_LAB/notes/no-stranger-phones.txt" "$MOB_LAB/roe.txt"═══ WINDOWS ═══
Command — copy this
adb version adb devices -l Get-Content $HOME/cyberlium-lab/t27-mob/notes/no-stranger-phones.txt | Select-String NEVER
Primary tools to practice this lesson: adb, grep. Reference sites: ADB docs (https://developer.android.com/tools/adb); OWASP MASTG dynamic (https://mas.owasp.org/MASTG/0x05e-Testing-Code-Quality-and-Build-Settings/); Android emulator (https://developer.android.com/studio/run/emulator). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. adb security posture
USB debugging off on personal daily drivers when not testing. Wireless adb requires pairing on modern API — still scope-bound. Never leave adb open on internet-exposed ports.
Defenders monitor unauthorized adb-enabled devices in enterprise — students learn why MDM restricts debugging.
3. Tool literacy boundary
Forbidden: adb shell on stranger phone, pulling /data/data from production apps without scope. Allowed: adb card — five commands, lab serial, authorized use sentence.
Ship: adb literacy card for $MOB_LAB device. Next: Frida Named.
4. What you ship: adb literacy card for $MOB_LAB
Five commands, lab serial, authorized use note. $MOB_LAB named. NO stranger devices. chmod 600.
5. What you record before the next lesson
Date. adb card. $MOB_LAB named. File t27-m04-l01-adb-literacy.txt chmod 600.
6. Wrong vs right: stranger phones vs lab emulator apps
Worked failure — same MSF word, opposite target. Right never needs a café Wi-Fi or classmate laptop.
Wrong
adb pull data from classmate phone. Leave wireless adb open to LAN.
Right
Write adb literacy card for YOUR $MOB_LAB device. Next: Frida Named.
Mission: document adb on YOUR lab device
1) List five safe lab adb commands. 2) Record lab serial or emulator name. 3) Write one refusal for stranger hardware. 4) chmod 600.
Stuck? Ask Cyberlium AI Mentor
adb devices serial must match M1 inventory before every session.
Knowledge Check
APPLY: adb literacy on Cyberlium means:
Multiple choice
Knowledge Check
APPLY: True or False: USB debugging should be enabled only on lab devices under YOUR control.
True or False
Knowledge Check
APPLY: Before adb you should:
Multiple choice