v17 — Heal the "device offline" adb transport on slow / low-end PCs

Fixes the device offline loop on slow / low-end PCs (#18). If blueStackRoot.cmd previously got stuck repeating waiting for adb … device offline and never finished rooting — even though BlueStacks itself booted to the home screen — this is the fix.

What changed

On a slow (multi-minute) boot the adb connection to the instance could wedge in offline (connected, but the handshake never finalizes), and a plain reconnect is a no-op on it — so the tool waited on a dead connection until it timed out. v17 now auto-recovers that connection (disconnect + connect to force a fresh handshake) and waits on the real Android boot signal, so it gets through even on a low-end machine.

• 🩹 Self-healing adb transport (the core fix), plus heal-on-drop during install.
• 📜 Boot detected from BlueStacks' own Player.log [Ready], independent of adb.
• 🧭 No more retrying launch spam from a mis-read process check.
• ⏱️ Reasonable timeouts: fail fast when nothing is starting, tolerate genuinely slow boots.
• No change to the Magisk APK, su, debugfs, or any disk step — only the host-side adb wait logic.

How to use

Download blueStackRoot.cmd, right-click → Run as administrator

If it still misbehaves

Grab debug.cmd below and run it — it tests the fix live and writes one bsr_debug_*.log to your Desktop that's enough to diagnose. (blueStackRoot.cmd itself logs only to the terminal — no files.)

Confirmed on the original reporter's 2013 low-end PC. See the CHANGELOG for details.