Confirming this bug on my own LilyGo T-Beam v1.2 (ESP32-D0WDQ6-V3, AXP2101 PMU, MAC 34:98:7a:6c:08:94).
Flashed T-Beam SX1276 Companion BLE, v1.16.0 (merged bin, via esptool directly at 0x0, hash verified) — board boots past the ROM bootloader fine, but display stays black and BLE pairing never shows a PIN (nor does it accept the documented default 123456 for screenless devices).
Tried T-Beam SX1262 Companion BLE — resulted in ERROR: radio init failed: -2, confirming this board's radio is indeed SX1276, not SX1262.
Tried downgrading to v1.9.0 (oldest available in the flasher) — same black screen / no PIN behavior.
Confirmed the hardware itself is fine: restoring the original (non-MeshCore) firmware works perfectly, display and all.
This matches the original report's I2C init hypothesis — AXP2101 (v1.2) vs AXP192 (v1.0/v1.1) handling likely needs a fix in the display/PMU init sequence for this board.
Confirming this bug on my own LilyGo T-Beam v1.2 (ESP32-D0WDQ6-V3, AXP2101 PMU, MAC 34:98:7a:6c:08:94).
Flashed T-Beam SX1276 Companion BLE, v1.16.0 (merged bin, via esptool directly at 0x0, hash verified) — board boots past the ROM bootloader fine, but display stays black and BLE pairing never shows a PIN (nor does it accept the documented default 123456 for screenless devices).
Tried T-Beam SX1262 Companion BLE — resulted in ERROR: radio init failed: -2, confirming this board's radio is indeed SX1276, not SX1262.
Tried downgrading to v1.9.0 (oldest available in the flasher) — same black screen / no PIN behavior.
Confirmed the hardware itself is fine: restoring the original (non-MeshCore) firmware works perfectly, display and all.
This matches the original report's I2C init hypothesis — AXP2101 (v1.2) vs AXP192 (v1.0/v1.1) handling likely needs a fix in the display/PMU init sequence for this board.