BPI-R3 Mini Bricked, cannot boot to NAND or eMMC and no Handshake with UART

Banana Pi Router design BPI-R3/R3 Mini(MT7986)
1

Hi All,

Thanks to everybody who has posted solutions in other threads but I’m totally stumped here. I don’t know what happened but my R3 Mini just stopped booting a while ago. I’ve tried all of the following to recover:

FT232RL UART device - No Handshake on both Linux and Windows using mtk_uartboot CH340 UART device - no Handshakre on both Linux and Windows using mtk_uartboot USB-C Serial device - no output. Boot from NAND - nothing Boot from eMMC - nothing

the PWR LED and W2G and W5G LEDs come on but no SYS.

I’ve tried all the settings on both of my serial adapters. I’ve tried using power from both a PC and a USB power brick. I’ve tried multiple different USB 2.0 and 3.0 ports.

Can anybody help me out please?

2

I guess there are no ways when uart is broken too…have You used external ch340? Be careful as the are mostly 5v.

3

definitely used an external CH340 device. the one I have has both 5v and 3v3 options

4

Any update? I have same problem

5

Nothing. And no response to my email to sinovoip directly either. Very disappointing.

1 Like
6

You should see some codes after switching on the board, with 3.3v uart connected.

Otherwise, board or uart is dead.

Or uart is connected wrong…

7

uart is connected correctly, previously it was running without problems. is it possible that the board died due to overheating? but the pwr and wifi led are on

8

Same here. Leds on, no codes.

9

There are many boards with a dead SOC (R3/R4). Is it possible to buy SOC chip from @sinovoip?

10

Hi,

My BPI-R3 Mini stopped booting after a power cycle. I was working with a Quectel RM530N-GL modem in the M.2 B-key slot and power-cycled the board. After that, the board no longer boots.

Symptoms:

  • Only red PWR LED comes on
  • No SYS LED, no W2G/W5G LEDs
  • Fan does not spin
  • No serial output at all on debug UART (115200 baud)
  • Same behavior on both eMMC and NAND boot switch positions
  • Board does heat up, suggesting SoC is getting power

What I’ve tried:

  • CP2102 USB-to-TTL adapter (3.3V) on the 3-pin debug header (GND/RX/TX)
  • Tried both TX/RX orientations
  • Tried with only TXD disconnected (RXD + GND only) to check for boot strap interference
  • Used two different CP2102 adapters — zero UART data from both
  • mtk_uartboot v0.1.1 (both compiled from source and pre-built macOS binary) — stays on “Handshake…” indefinitely
  • Stripped board completely — no M.2 card, no USB devices, no ethernet, just power + UART
  • Tried different boot switch positions (eMMC / NAND)
  • Power supply is USB-C PD, same one that worked before

Hardware:

  • BPI-R3 Mini (MT7986A)
  • 2GB DDR4, 8GB eMMC
  • Was running ROOter/OpenWrt (GoldenOrb 2026-03-11)
  • M.2 slot is now empty

Questions:

  1. Could the CP2102 be holding the UART TX boot strap pin high and preventing BROM from starting? I’ve ordered an FTDI (FT232RL) adapter to test this.
  2. Is there any other way to trigger BROM recovery on the R3 Mini?
  3. Has anyone seen this exact symptom (PWR LED only, zero UART output) and recovered from it?

Any help would be greatly appreciated. Thanks!

@frank-w tagging you as you seem to be the expert on R3 Mini recovery.

11

You should see at least bootrom on uart else i fear your board/soc is damaged. Make sure your uart is 3.3v and your power supply is ok.

12

The bear minimum:

GND - GND and TX(R3mini) - RX(usb-adapter)

When powering on, you should always see hexadecimal numbers.

Double check connectors and voltage setting (3.3v) if applicable. Check your terminal settings, make sure handshake software and hardware are disabled. Etc.

Not usefull to try anything else, until you see the numbers.

Don’t swap GND with TX/RX, you’re pins will be subjected to -3.3v, which they cannot handle. So actually the GND connection is most important to double-check before any usage.