[BPI-R3 Mini] How to unbricked NAND and EMMC

frank-w · July 13, 2024, 6:15am

what is the output of

printenv bootconf

?

It should show name of this config

github.com

frank-w/BPI-Router-Linux/blob/6.6-main/bpi-r3.its#L95


      
          		};
          		conf-emmc {
          			description = "Boot Linux kernel with EMMC FDT blob";
          			kernel = "kernel-1";
          			fdt = "fdt-base", "fdt-ov-emmc";
          			//ramdisk = "ramdisk-1";
          			hash-1 {
          				algo = "sha1";
          			};
          		};
          		conf-emmc-mini {
          			description = "Boot Linux kernel with R3mini + EMMC FDT blob";
          			kernel = "kernel-1";
          			fdt = "fdt-base-mini", "fdt-ov-emmc";
          			//ramdisk = "ramdisk-1";
          			hash-1 {
          				algo = "sha1";
          			};
          		};
          		conf-sd-nand {
          			description = "Boot Linux kernel with SD+NAND FDT blob";

If not please set it like this (maybe with # before)

Amd you have downloaded bpi-r3.itb from 6.6-main release? Previous images have no r3mini support.

But it is possible that bootconf is overwritten by setbootconf as r3 has a detection of devices…So could you do

printenv setbootconf

And if there is the detection (checkmmc,checkspi) just change it to fixed bootconf

setenv setbootconf 'setenv bootconf "#conf-emmc-mini"'

Ufuk_Delibas · July 14, 2024, 1:43pm

Ok it works.

Do I have to put root as login and follow the link in the posting in a Linux terminal or UART console ?

frank-w · July 14, 2024, 1:55pm

Yes simply use username root…no pw in initrd

Ufuk_Delibas · July 14, 2024, 2:39pm

Ok and do I have to follow those steps on a Linux terminal ?

dd if=/tmp/openwrt-*-bananapi_bpi-r3-mini-emmc-preloader.bin of=/dev/mmcblk0boot0
dd if=/tmp/openwrt-*-bananapi_bpi-r3-mini-emmc-bl31-uboot.fip of=/dev/mmcblk0p3
dd if=/tmp/openwrt-*-bananapi_bpi-r3-mini-initramfs-recovery.itb of=/dev/mmcblk0p4
dd if=/tmp/openwrt-*-bananapi_bpi-r3-mini-squashfs-sysupgrade.itb of=/dev/mmcblk0p5

frank-w · July 14, 2024, 3:37pm

Yes,it is possible you have to disable boot0 readonly mode first

Ufuk_Delibas · July 14, 2024, 11:20pm

I think I did it. I just follow your guide for the BPI R3.

Ufuk_Delibas · July 14, 2024, 11:51pm

Now its asking me to do tftp for the recovery file but it dosn’t work.

frank-w · July 15, 2024, 5:31am

I cannot help much with openwrt specific stuff,but it looks it loads something from mmc first without error…only has error with the leds (missing config option in uboot?). You can try adding the uboot option to uboot (but i do not know how).

OCCaGO · January 23, 2025, 2:04am

Hello, can not flash nand or emmc, there is no even nand device listed by lsblk. But i have a programmer. Has anyone dump for bpi r3 mini, please?

Manivannan_Maran · August 18, 2025, 6:37pm

Hello, Frank-W

I have a Banana Pi R3 Mini (MT7986 SoC) that is now bricked. The problem started when I switched the boot source between eMMC and SNAND.

Now, when powering on, the serial log always stops at:


F0: 102B 0000
FA: 1040 0000
FA: 1040 0000 [0200]
F9: 103F 0000
F3: 0000 0000 [0200]
V0: 0000 0000 [0001]
00: 0000 0000
BP: 2400 0041 [0000]
G0: 1190 0000
EC: 0000 0000 [2000]
T0: 0000 016F [010F]
Jump to BL

NOTICE:  BL2: v2.6(release):
NOTICE:  BL2: Built : 20:16:38, May  7 2023
NOTICE:  WDT: disabled
NOTICE:  CPU: MT7986 (1998MHz)
NOTICE:  EMI: Using DDR4 settings
NOTICE:  EMI: Detected DRAM size: 2048MB
NOTICE:  EMI: complex R/W mem test passed
ERROR:   BL2: Failed to load image id 3 (-2)

The board has no SD card slot, only SNAND + eMMC + USB.
I tried to force USB Boot (BootROM) with mtkclient by holding the reset button while powering on, but there is no BootROM handshake.
The device always tries to boot SNAND/eMMC instead of entering BootROM.

I have access to:

Serial console (Waveshare FT232/CH343 USB-TTL).
mtkclient installed on PC.

I need your help to:

Force the board into BootROM mode (USB/UART download) — maybe via DIP switch, jumper, or shorting boot strap pins.
Reflash U-Boot / BL2 into SNAND or eMMC so the board can boot again.
Confirm if recovery via UART (X/Ymodem transfer) is possible if BootROM is not accessible.

Thank you.

frank-w · August 18, 2025, 6:46pm

The uartboot should work independ of bootswitch position.

You need a bl2 and fip for ramboot (you can find them in releases page of my uboot repo) and the mtk_uartboot binary (i have only tested in linux).

https://wiki.fw-web.de/doku.php?id=en:bpi-r3mini:start#fix_bricked_boot

Just start the mtk_uartboot application with parameters pointing to ram bl2+fip and then poweron your r3mini.

After mtk_uartboot exits start minicom or your preferered uart application on same device and you should have uboot console.

There you can reinstall your preferered os.

Manivannan_Maran · August 31, 2025, 2:18pm

Hello Frank-W,

I have a Banana Pi R3 Mini (MT7986 SoC) that is currently not booting properly. The problem started after switching the boot source between eMMC and SPI NAND.

I have mtk_uartboot working to load BL2 + FIP into RAM. Using this, I can reach the U-Boot console via serial.

However, when attempting to boot the board, the serial log shows the following BL2 error:

F0: 102B 0000
FA: 1040 0000
FA: 1040 0000 [0200]
F9: 0000 0000
V0: 0000 0000 [0001]
00: 0000 0000
BP: 2400 0041 [0000]
G0: 1190 0000
EC: 0000 0000 [1000]
T0: 0000 021F [010F]
Jump to BL

NOTICE:  BL2: v2.13.0(release): OpenWrt v2025.07.11~78a0dfd9-1 (mt7986-spim-nand-ubi-ddr4)
NOTICE:  BL2: Built : 19:55:48, Aug 14 2025
NOTICE:  WDT: Cold boot
NOTICE:  WDT: disabled
NOTICE:  CPU: MT7986 (2000MHz)
NOTICE:  EMI: Using DDR4 settings
NOTICE:  EMI: Detected DRAM size: 2048MB
NOTICE:  complex R/W mem test passed
NOTICE:  SPI_NAND parses attributes from parameter page.
NOTICE:  SPI_NAND Detected ID 0xef
NOTICE:  Page size 2048, Block size 131072, size 134217728
NOTICE:  UBI: scanning [0x200000 - 0x8000000] ...
NOTICE:  UBI: Bad VID magic in block 12 54000090
NOTICE:  UBI: Bad VID magic in block 13 4c520294
NOTICE:  UBI: Bad VID magic in block 14 e01f40f9
NOTICE:  UBI: Bad VID magic in block 15 2540052a
NOTICE:  UBI: Bad VID magic in block 16 ff0300b9
NOTICE:  UBI: Bad VID magic in block 17 fd7bc3a8
NOTICE:  UBI: Bad VID magic in block 18 00000000
NOTICE:  UBI: Bad VID magic in block 19 65747279
NOTICE:  UBI: Bad VID magic in block 20 00000000
NOTICE:  UBI: Bad EC magic in block 21 ffffffff
NOTICE:  UBI: Bad EC magic in block 22 ffffffff
NOTICE:  UBI: Bad EC magic in block 23 ffffffff
NOTICE:  UBI: Bad EC magic in block 24 ffffffff
NOTICE:  UBI: Bad EC magic in block 25 ffffffff
NOTICE:  UBI: Bad EC magic in block 26 ffffffff
NOTICE:  UBI: Bad EC magic in block 27 ffffffff
NOTICE:  UBI: scanning is finished
NOTICE:  UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
NOTICE:  UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
ERROR:   UBI error: No volume named fip could be found
ERROR:   io_dev_init failed for FIP image id 0 (-2)
ERROR:   Image id 3 open failed with -2
ERROR:   BL2: Failed to load image id 3 (-2)

I have attempted to write the OpenWrt SNAND image via U-Boot using RAM-loaded commands, but the board still fails to boot.

Could you please advise:

How to properly install OpenWrt on SNAND using RAM-loaded U-Boot.
Any necessary steps for creating/formatting UBI volumes on SPI NAND before flashing.
If there is a recommended sequence of writing BL2/FIP and OpenWrt images to ensure the board boots correctly.

Thank you for your guidance.

frank-w · August 31, 2025, 3:06pm

Your ubi does not have a partition with fip label

UBI error: No volume named fip could be found

As i do not use openwrt i have no exact instructions to write.

Creating ubi from uboot is bit complex,so better bootup an kernel with initrd (for example from my kernel and buildroot repo)

Bpi-r3.itb with bootconf conf-emmc-mini (bootm $loadaddr#conf-emmc-mini)

This is how i did for my image on R4

https://wiki.fw-web.de/doku.php?id=en:bpi-r4:start#ubi

This is for openwrt

github.com

openwrt/openwrt/blob/main/package/boot/uboot-mediatek/patches/442-add-bpi-r3-mini.patch#L344


      
          +part_default=production
          +part_recovery=recovery
          +reset_factory=mw $loadaddr 0xff 0x1f000 ; ubi write $loadaddr ubootenv 0x1f000 ; ubi write $loadaddr ubootenv2 0x1f000 ; ubi remove rootfs_data
          +snand_write_bl2=mtd erase bl2 && mtd write bl2 $loadaddr 0x0 0x40000 && mtd write bl2 $loadaddr 0x40000 0x40000 && mtd write bl2 $loadaddr 0x80000 0x40000 && mtd write bl2 $loadaddr 0xc0000 0x40000
          +ubi_create_env=ubi check ubootenv || ubi create ubootenv 0x1f000 dynamic ; ubi check ubootenv2 || ubi create ubootenv2 0x1f000 dynamic
          +ubi_prepare_rootfs=if ubi check rootfs_data ; then else if env exists rootfs_data_max ; then ubi create rootfs_data $rootfs_data_max dynamic || ubi create rootfs_data - dynamic ; else ubi create rootfs_data - dynamic ; fi ; fi
          +ubi_read_production=ubi read $loadaddr fit && iminfo $loadaddr && run ubi_prepare_rootfs
          +ubi_read_recovery=ubi check recovery && ubi read $loadaddr recovery
          +ubi_read_emmc_install=ubi check emmc_install && ubi read $loadaddr emmc_install
          +ubi_remove_rootfs=ubi check rootfs_data && ubi remove rootfs_data
          +ubi_write_fip=run ubi_remove_rootfs ; ubi check fip && ubi remove fip ; ubi create fip 0x200000 static ; ubi write $loadaddr fip 0x200000
          +ubi_write_en8811h_fw=ubi check en8811h-fw && ubi remove en8811h-fw ; ubi create en8811h-fw 0x24000 static ; ubi write $loadaddr en8811h-fw 0x24000
          +ubi_write_production=ubi check fit && ubi remove fit ; run ubi_remove_rootfs ; ubi create fit $filesize dynamic && ubi write $loadaddr fit $filesize
          +ubi_write_recovery=ubi check recovery && ubi remove recovery ; run ubi_remove_rootfs ; ubi create recovery $filesize dynamic && ubi write $loadaddr recovery $filesize
          +_init_env=setenv _init_env ; run ubi_create_env ; saveenv ; saveenv
          +_firstboot=setenv _firstboot ; run _switch_to_menu ; run _init_env ; run boot_first
          +_switch_to_menu=setenv _switch_to_menu ; setenv bootdelay 3 ; setenv bootmenu_delay 3 ; setenv bootmenu_0 $bootmenu_0d ; setenv bootmenu_0d ; run _bootmenu_update_title
          +_bootmenu_update_title=setenv _bootmenu_update_title ; setenv bootmenu_title "$bootmenu_title       [33m$ver[0m"
          --- /dev/null
          +++ b/defenvs/bananapi_bpi-r3-mini_emmc_env
          @@ -0,0 +1,59 @@

I found this here in forum: BPI-R3 Mini NAND Restore - #12 by nino_0

ericwoud · August 31, 2025, 4:07pm

If it helps, there is a way to get into Linux directly with mtk_uartboot, skipping uboot all together…

Also, perhaps it is easier to get emmc booting again first.

Manivannan_Maran · September 8, 2025, 9:12pm

BPi-R3 Mini Full Flashing Workflow — Detailed Guide Tools & Hardware

Essential Hardware

PC / Laptop (Windows or Linux)

USB-TTL serial adapter → UART console (for BL2, U-Boot, and OpenWrt shell)

USB Flash Drive (FAT32 formatted, for USB boot / sysupgrade)

Ethernet cable → PC ↔ BPi-R3 Mini WAN port

Software

Flashing & Console

MTK UART Boot Tool (mtk_uartboot.exe) → load BL2 + FIP into RAM via UART

Serial monitor → PuTTY, Tera Term, minicom → UART console

TFTP server → serve NAND/eMMC images (Windows: tftpd64 / Linux: tftpd-hpa)

Web browser → OpenWrt WebUI flash

Optional

Rufus → format USB flash drive to FAT32

scp / wget / curl → copy files to running OpenWrt shell

Firmware / Image Files

UART → RAM loader

bpi-r3mini_ram_bl2.bin → BL2 Preloader

bpi-r3mini_ram_fip.bin → BL31 + U-Boot FIP

Source: UART Loader Google Drive

Old / Official OpenWrt single-image

mtk-bpi-r3mini-mac80211-NAND-YYYYMMDD-single-image.bin → NAND flash

mtk-bpi-r3mini-mac80211-EMMC-YYYYMMDD-single-image.bin → eMMC flash

Source: Old OpenWrt Google Drive

Latest OpenWrt

openwrt-24.10.2-…-initramfs-recovery.itb → RAM boot for safe sysupgrade

openwrt-24.10.2-…-emmc.img → final sysupgrade for eMMC

Files for eMMC flash via old OpenWrt shell

openwrt-emmc-gpt.bin → GPT partition table

openwrt-emmc-preloader.bin → BL2 / preloader

openwrt-emmc-bl31-uboot.fip → BL31 + U-Boot FIP

Step-by-Step Flashing Workflow A. NAND Single-Image via UART Recovery

Boot BL2 + FIP into RAM

“C:\Program Files\mtk_uartboot\target\release\mtk_uartboot.exe” -s COM3 -p bpi-r3mini_ram_bl2.bin --aarch64 -f bpi-r3mini_ram_fip.bin

Temporary U-Boot console appears in RAM.

Configure U-Boot environment

setenv serverip 192.168.1.13 setenv ipaddr 192.168.1.1 setenv loadaddr 0x46000000 saveenv

Load NAND single-image via TFTP

tftpboot ${loadaddr} mtk-bpi-r3mini-mac80211-NAND-YYYYMMDD-single-image.bin

Prepare NAND

ubi detach mtd erase bl2 mtd erase factory mtd erase fip mtd erase ubi

Write the single-image

mtd write spi-nand0 ${loadaddr} 0 ${filesize}

Verify

mtd read spi-nand0 ${loadaddr} 0 0x10000 md ${loadaddr} 0x40

Reboot

reset

Board boots into OpenWrt NAND.

B. eMMC Single-Image via UART Recovery (Optional if NAND failed)

Boot BL2 + FIP into RAM (if eMMC corrupted) Configure U-Boot network Load eMMC single-image via TFTP Calculate block count and erase eMMC Write image to eMMC Verify Reboot

Board boots directly from eMMC.

C. Flash GPT / BL2 / BL31 via Old OpenWrt Shell (booted from NAND)

Goal: Write GPT, BL2, and BL31 + U-Boot FIP to eMMC without UART loader, using old OpenWrt shell from NAND.

Copy files to /tmp

cd /tmp tftp -g -r openwrt-emmc-gpt.bin 192.168.1.13 tftp -g -r openwrt-emmc-preloader.bin 192.168.1.13 tftp -g -r openwrt-emmc-bl31-uboot.fip 192.168.1.13

Flash GPT table

dd if=/tmp/openwrt-emmc-gpt.bin of=/dev/mmcblk0 bs=512 seek=0 count=34 conv=fsync fdisk -l /dev/mmcblk0

Flash BL2 / Preloader

echo 0 > /sys/block/mmcblk0boot0/force_ro dd if=/tmp/openwrt-emmc-preloader.bin of=/dev/mmcblk0boot0 bs=512 conv=fsync echo 1 > /sys/block/mmcblk0boot0/force_ro

Flash BL31 + U-Boot FIP

dd if=/tmp/openwrt-emmc-bl31-uboot.fip of=/dev/mmcblk0 bs=512 seek=13312 conv=fsync

Verify

dd if=/dev/mmcblk0 bs=512 skip=13312 count=2048 of=/tmp/bl31_readback.bin cmp /tmp/bl31_readback.bin /tmp/openwrt-emmc-bl31-uboot.fip

eMMC now bootable, U-Boot runs from eMMC.

D. Sysupgrade via USB → RAM → WebUI (booted from eMMC)

Boot into eMMC U-Boot

Power-cycle the board → board runs U-Boot from eMMC

Load Sysupgrade to RAM from USB

usb start fatload usb 0:1 0x46000000 openwrt-24.10.2-…-emmc.img bootm 0x46000000

Access OpenWrt WebUI

Navigate: System → Backup / Flash Firmware → Flash new firmware

Select the sysupgrade image (already in RAM or uploaded)

Reboot & verify

lsblk df -h

Confirm rootfs and partitions are correct. Acknowledgment Special thanks to Frank-W for the guidance and support during the BPi-R3 Mini flashing workflow.

Note: This guide was AI-assisted in its preparation. If you find any inaccuracies, typos, or procedural errors, please feel free to correct them. The author and contributors appreciate any feedback to improve clarity and safety.

Manivannan_Maran · September 30, 2025, 11:42pm

Hi Frank,

I’m encountering a problem on the BPI-R3 Mini while trying to back up the BL2 region of the SPI-NAND. When using sf read at any RAM address, the CPU triggers a Synchronous Abort, and the system resets. This happens even when splitting the read into smaller chunks.

Details:

Board: BPI-R3 Mini
SPI-NAND: Winbond 128 MiB, block 128 KiB, page 2048, OOB 64
Crash occurs during sf read 0x40000000 0x000000 0x40000 (and other addresses)
Similar behavior may occur on eMMC reads of low-level boot partitions
Using mtd read also fails unless careful RAM offsets are chosen

It looks like BL2 and other boot regions are protected or not directly accessible via SF read, and standard RAM addresses trigger a synchronous abort.

Could you advise the recommended procedure to safely back up BL2, FIP, factory, and UBI partitions on SPI-NAND and eMMC without causing CPU resets?

Thank you

frank-w · October 1, 2025, 5:30am

Use mtd read/write for nand/nor.

Try to use loadaddr of >0x4500000 as ram starts afaik at 0x40000000 and some regmaps (e.g.clock,pinctrl,…) are mapped to this region.

yodee13 · October 29, 2025, 10:39am

Dear Community!

I have bought an BPI-R3 mini, and I want to use it with my own compiled OpenWRT. At this moment, the device has the stock 21.05 SNAPSHOT version on the NAND and something on the EMMC. I have followed the tutorial, and the result is always the same, after the power remove, switch to EMMC boot this screen is welcome me in serial port, after the uboot menu:

What do i wrong?

Thank you!

frank-w · October 29, 2025, 11:21am

So you try to boot mainline openwrt from emmc after installing it with mainline instructions from pre-installed bpi-image on nand,right?

Looks like the fit does not contain the config name which is taken by the script. Either the fit image has changed or the script for booting specific configuration.

You can list your env variables with printenv. For available configurations i only know dumpimage in linux,but no uboot command. Afaik openwrt loads fit image itself from a storage block and not as file from partition you can only try get offset and size of fit from uboot and write this to file after booting linux.

this is the config-name which seems to be taken…but i do not know where openwrt creates the fit which has to include this config

github.com

openwrt/openwrt/blob/HEAD/package/boot/uboot-mediatek/patches/442-add-bpi-r3-mini.patch#L363


      
          +_bootmenu_update_title=setenv _bootmenu_update_title ; setenv bootmenu_title "$bootmenu_title       [33m$ver[0m"
          --- /dev/null
          +++ b/defenvs/bananapi_bpi-r3-mini_emmc_env
          @@ -0,0 +1,59 @@
          +ipaddr=192.168.1.1
          +serverip=192.168.1.254
          +loadaddr=0x46000000
          +console=earlycon=uart8250,mmio32,0x11002000 console=ttyS0
          +bootargs=root=/dev/fit0 rootwait
          +bootcmd=if pstore check ; then run boot_recovery ; else run boot_emmc ; fi
          +bootconf=config-mt7986a-bananapi-bpi-r3-mini
          +bootdelay=0
          +bootfile=openwrt-mediatek-filogic-bananapi_bpi-r3-mini-initramfs-recovery.itb
          +bootfile_bl2=openwrt-mediatek-filogic-bananapi_bpi-r3-mini-emmc-preloader.bin
          +bootfile_fip=openwrt-mediatek-filogic-bananapi_bpi-r3-mini-emmc-bl31-uboot.fip
          +bootfile_upg=openwrt-mediatek-filogic-bananapi_bpi-r3-mini-squashfs-sysupgrade.itb
          +bootfile_en8811h_fw=EthMD32.bin
          +bootled_pwr=green:status
          +bootled_rec=blue:status
          +bootmenu_confirm_return=askenv - Press ENTER to return to menu ; bootmenu 60
          +bootmenu_default=0

seems like fit is loaded this way:

github.com

openwrt/openwrt/blob/HEAD/package/boot/uboot-mediatek/patches/442-add-bpi-r3-mini.patch#L405


      
          +boot_tftp_recovery=tftpboot $loadaddr $bootfile && env exists replacevol && iminfo $loadaddr && run emmc_write_recovery ; if env exists noboot ; then else bootm $loadaddr#$bootconf ; fi
          +boot_tftp_write_fip=tftpboot $loadaddr $bootfile_fip && run emmc_write_fip
          +boot_tftp_write_bl2=tftpboot $loadaddr $bootfile_bl2 && run emmc_write_bl2
          +boot_tftp_write_en8811h_fw=tftpboot $loadaddr $bootfile_en8811h_fw && run emmc_write_en8811h_fw
          +boot_tftp=tftpboot $loadaddr $bootfile && bootm $loadaddr#$bootconf
          +mmc_write_vol=imszb $loadaddr image_size && test 0x$image_size -le 0x$part_size && mmc erase 0x$part_addr 0x$image_size && mmc write $loadaddr 0x$part_addr 0x$image_size
          +mmc_read_vol=mmc read $loadaddr $part_addr 0x100 && imszb $loadaddr image_size && test 0x$image_size -le 0x$part_size && mmc read $loadaddr 0x$part_addr 0x$image_size && setexpr filesize $image_size * 0x200
          +part_default=production
          +part_recovery=recovery
          +reset_factory=eraseenv && reset
          +emmc_read_production=part start mmc 0 $part_default part_addr && part size mmc 0 $part_default part_size && run mmc_read_vol
          +emmc_read_recovery=part start mmc 0 $part_recovery part_addr && part size mmc 0 $part_recovery part_size && run mmc_read_vol
          +emmc_write_en8811h_fw=mmc partconf 0 1 2 2 && mmc erase 0x0 0x120 && mmc write $fileaddr 0x0 0x120 ; mmc partconf 0 1 1 0
          +emmc_write_bl2=mmc partconf 0 1 1 1 && mmc erase 0x0 0x400 && mmc write $fileaddr 0x0 0x400 ; mmc partconf 0 1 1 0
          +emmc_write_fip=mmc erase 0x3400 0x2000 && mmc write $fileaddr 0x3400 0x2000 && mmc erase 0x2000 0x800
          +emmc_write_production=part start mmc 0 $part_default part_addr && part size mmc 0 $part_default part_size && run mmc_write_vol
          +emmc_write_recovery=part start mmc 0 $part_recovery part_addr && part size mmc 0 $part_recovery part_size && run mmc_write_vol
          +_init_env=setenv _init_env ; setenv _create_env ; saveenv ; saveenv
          +_firstboot=setenv _firstboot ; run _switch_to_menu ; run _init_env ; run boot_first
          +_switch_to_menu=setenv _switch_to_menu ; setenv bootdelay 3 ; setenv bootmenu_delay 3 ; setenv bootmenu_0 $bootmenu_0d ; setenv bootmenu_0d ; run _bootmenu_update_title
          +_bootmenu_update_title=setenv _bootmenu_update_title ; setenv bootmenu_title "$bootmenu_title       [33m$ver[0m"

looks like there is a partition production where all is loaded from and than a fit is extracted from it

fit itself seems to be created from here:

github.com

openwrt/openwrt/blob/main/target/linux/mediatek/image/filogic.mk#L501


      
            DEVICE_DTC_FLAGS := --pad 4096
            DEVICE_COMPAT_VERSION := 1.3
            DEVICE_COMPAT_MESSAGE := First sfp port renamed from eth1 to sfp1
          endef
          TARGET_DEVICES += bananapi_bpi-r3
          
          define Device/bananapi_bpi-r3-mini
            DEVICE_VENDOR := Bananapi
            DEVICE_MODEL := BPi-R3 Mini
            DEVICE_DTS := mt7986a-bananapi-bpi-r3-mini
            DEVICE_DTS_CONFIG := config-mt7986a-bananapi-bpi-r3-mini
            DEVICE_DTS_DIR := ../dts
            DEVICE_DTS_LOADADDR := 0x43f00000
            DEVICE_PACKAGES := kmod-eeprom-at24 kmod-hwmon-pwmfan kmod-mt7915e kmod-mt7986-firmware \
          		     kmod-phy-airoha-en8811h kmod-usb3 e2fsprogs f2fsck mkf2fs mt7986-wo-firmware
            KERNEL_LOADADDR := 0x44000000
            KERNEL := kernel-bin | gzip
            KERNEL_INITRAMFS := kernel-bin | lzma | \
              fit lzma $$(KDIR)/image-$$(firstword $$(DEVICE_DTS)).dtb with-initrd | pad-to 64k
            KERNEL_INITRAMFS_SUFFIX := -recovery.itb
            BLOCKSIZE := 128k

have you a production partition on emmc and executed these steps with the r3mini (not R3) files?

dd if=/tmp/openwrt-*-bananapi_bpi-r3-mini-initramfs-recovery.itb of=/dev/mmcblk0p4
dd if=/tmp/openwrt-*-bananapi_bpi-r3-mini-squashfs-sysupgrade.itb of=/dev/mmcblk0p5

yodee13 · October 29, 2025, 12:26pm

I’ve made a mistake at first time. At the first time Unfortunetly i was Inattentive, and i write the simple r3 Images, not the r3-mini. Is it problem? Since then i have wrote the r3-mini Images several time, but the result is the same every time.