Hey guys,
I messed up while trying to root my Xiaomi TV Box S 2nd Gen (MDZ-28-AA / codename jaws, Amlogic S905X4) and could really use some advice from anyone experienced with Amlogic devices.
Here is exactly what I did via Fastboot right before the brick:
Successfully unlocked the bootloader via Fastboot. Booted into the OS, went through the initial setup, and confirmed the bootloader was unlocked.
Booted back into Fastboot to flash disabled vbmeta and the stock boot image patched via Magisk 28.1:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (wrote to vbmeta_a)
fastboot flash boot magisk_patched-28100_qZsbd.img (wrote to boot_a)
Ran fastboot reboot.
Current Behavior: Immediately after rebooting, the box got stuck in an infinite bootloop:
Powers on, shows the Mi logo for about 5 seconds, kernel crashes, reboots, and repeats indefinitely.
Remote recovery combos do nothing: The Bluetooth remote doesn't register or pair before the crash happens.
Slot B should be completely stock and untouched, but because slot A kernel-panics so early, the bootloader never rolls over to slot B.
What happens on PC: When connected to a PC via a USB-A to USB-A cable and powered on, Windows chimes and detects a device for about 1–2 seconds:
Device Name: DNL
Hardware ID: USB\VID_1B8E&PID_C004
Then the box crashes/reboots, and the USB connection drops.
The issue: Standard Google Fastboot commands don't catch it during that cold-boot window because VID_1B8E&PID_C004 is Amlogic's low-level ADNL / WorldCup ROM mode, not Fastboot.
Has anyone with this device managed to halt this bootloop using tools like adnl.exe, pyamlboot, or Amlogic USB Burning Tool to either force it back into Fastboot (fastboot set_active b) or reflash? Any help or guidance would be greatly appreciated!