Skip to content

Rooting path for units where 'fastboot oem unlock' is vendor-locked (mtkclient/BROM route) + the stage-2 DRAM-hang fix #11

Description

@haohowareyou

The wiki's Getting Root assumes fastboot oem unlock succeeds — which it does on some LoopDL units (sounds like yours included). On other units the fastboot/UI bootloader is vendor-locked and both fastboot oem unlock and fastboot flashing unlock are refused. The good news: on those units the BROM is fully unauthenticated (SLA/SBC/DAA off), so they're still rootable over BROM with mtkclient:

  1. Confirm the BROM is open: mtk printgpt succeeds with no auth/crypto errors.
  2. mtk_guiFlash Tools → Unlock bootloader, then erase userdata + metadata.
  3. Resume the wiki's normal flow: flash the Magisk-patched init_boot over fastboot (bootloader is unlocked now).

The gotcha that cost me hours: mtkclient's stage-2 hangs at "DRAM config" if you connect the device in BROM mode. The fix is to connect in PRELOADER mode instead — power the device fully off and plug in the USB cable with no buttons held. Stage-2 then loads its DA and proceeds normally.

Full step-by-step (plus an A2DP-sink + dual dumb-speaker / full-phone setup built on top) is in my repo: https://github.com/haohowareyou/loopdl-speaker — happy to PR this into the Getting Root wiki page if it'd be useful.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions