bootloader-lk-expert

Map Qualcomm LK fastboot issues to verified bootloader source paths.

40|7|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/jonaschen/Android-Software --skill bootloader-lk-expert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bootloader-lk-expert
Source: https://github.com/jonaschen/Android-Software/tree/main/skills/L2-bootloader-lk-expert
Command: npx skills add https://github.com/jonaschen/Android-Software --skill bootloader-lk-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires adb, fastboot, python3, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Prevents agents from misrouting Qualcomm LK fastboot and partition issues by providing authoritative bootloader knowledge tied to vendor BSP paths.

Core Features & Use Cases

  • Path-aware LK routing: Focuses diagnostics on bootloader/lk/, bootable/bootloader/, and device-specific bootloader trees while warning that these paths are vendor-supplied.
  • Fastboot and AVB intelligence: Explains fastboot variable handling, GPT partition XMLs, A/B slot metadata, and verified boot outcomes to inform decisions.
  • Use Case: When a device refuses to boot or fastboot commands fail, consult the glossary and tool calls to check partitions, AVB status, and LK handoff rules before escalating.

Quick Start

Ask the agent to diagnose bootloader fastboot state and partition layout for the connected Android device.

Frequently Asked Questions about bootloader-lk-expert

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose Qualcomm LK fastboot boot failures and partition layout issues?

Verifying AVB status in LK fastboot involves analyzing Android Verified Boot metadata and handoff rules within the little-kernel. Check the specific AVB outcomes and fastboot variable handling to ensure the bootloader correctly validates the boot images before handoff.

Why do my fastboot commands fail on an Android device with A/B slots?

Fastboot commands fail on A/B slot devices when LK bootloader slot selection metadata is misrouted or misinterpreted. Diagnose the issue by checking the GPT partition XMLs and the active slot variables to ensure the little-kernel targets the correct boot partition.

Do I need adb and fastboot tools to analyze little-kernel partition tables?

Yes, you need adb, fastboot, and python3 installed to analyze little-kernel partition tables. These dependencies provide the necessary command-line interfaces to read device fastboot variables, query GPT partition layouts, and process AVB metadata from the connected Android device.

What is the best way to prevent hallucinated fixes when debugging Android bootloader issues?

The best way to prevent hallucinated fixes for Android bootloader issues is to route diagnostics strictly through verified vendor-supplied LK source paths. By cross-referencing fastboot states and AVB metadata against authoritative BSP trees, you avoid cross-layer routing mistakes.

Can I use this approach to check GPT partition XMLs for any Android device?

You can check GPT partition XMLs and A/B slot metadata, but this diagnostic approach specifically applies to Qualcomm ABL and little-kernel BSP trees. It warns against cross-layer routing mistakes by focusing analysis on device-specific bootloader trees rather than generic Android implementations.