I've got an MR90X(EU) v1.2.
The web interface shows this info:
Firmware Version: 1.0.2 Build 20230808 rel.59994(4555)
Hardware Version: MR90X v1.0
When I run fw_printenv
I don't see tp_boot_idx
at all in the output. Other than that, I've successfully followed the steps up to 12, right before Delete old and create a new one kernel volume.
My question is: Should I go ahead applying changes to the kernel volume or should I attempt to apply the previous stock firmware - rel57784 - first and redo the steps?
I imagine that if I apply the change, worst case scenario I'll be able to follow the debricking procedure, but not 100% sure.
Here's more info.
Firmware versions
The Mercusys MR90X firmware page has the following firmware options:
- For v1.2, MR90X(EU)_V1.20_230808
- For v1.0, MR90X(EU)_V1_1.0.1 Build 20230808. This one and the one above contain the same
.bin
file. The file's got20230808-rel59994
in the name and the file contents are the same. - For v1.0, MR90X(EU)_V1_1.1.0 Build 20220916. This one has a
.bin
file with20220916-rel57784
in the name. It's the same one as the Firmware OEM Stock URL on the MR90X OpenWrt page.
MTD
cat /proc/mtd
dev: size erasesize name
mtd0: 00200000 00020000 "boot"
mtd1: 00100000 00020000 "u-boot-env"
mtd2: 03200000 00020000 "ubi0"
mtd3: 03200000 00020000 "ubi1"
mtd4: 00800000 00020000 "userconfig"
mtd5: 00400000 00020000 "tp_data"
ubinfo
ubinfo --all
UBI version: 1
Count of UBI devices: 3
UBI control device major/minor: 10:62
Present UBI devices: ubi0, ubi1, ubi2
ubi0
Volumes count: 3
Logical eraseblock size: 126976 bytes, 124.0 KiB
Total amount of logical eraseblocks: 400 (50790400 bytes, 48.4 MiB)
Amount of available logical eraseblocks: 175 (22220800 bytes, 21.1 MiB)
Maximum count of volumes 128
Count of bad physical eraseblocks: 0
Count of reserved physical eraseblocks: 20
Current maximum erase counter value: 1
Minimum input/output unit size: 2048 bytes
Character device major/minor: 250:0
Present volumes: 0, 1, 2
Volume ID: 0 (on ubi0)
Type: static
Alignment: 1
Size: 6 LEBs /tmp(761856 bytes, 744.0 KiB)
Data bytes: 747152 bytes (729.6 KiB)
State: OK
Name: uboot
Character device major/minor: 250:1
-----------------------------------
Volume ID: 1 (on ubi0)
Type: static
Alignment: 1
Size: 26 LEBs (3301376 bytes, 3.1 MiB)
Data bytes: 3216284 bytes (3.0 MiB)
State: OK
Name: kernel
Character device major/minor: 250:2
-----------------------------------
Volume ID: 2 (on ubi0)
Type: static
Alignment: 1
Size: 169 LEBs (21458944 bytes, 20.4 MiB)
Data bytes: 21450752 bytes (20.4 MiB)
State: OK
Name: rootfs
Character device major/minor: 250:3
===================================
ubi1
Volumes count: 1
Logical eraseblock size: 126976 bytes, 124.0 KiB
Total amount of logical eraseblocks: 32 (4063232 bytes, 3.8 MiB)
Amount of available logical eraseblocks: 0 (0 bytes)
Maximum count of volumes 128
Count of bad physical eraseblocks: 0
Count of reserved physical eraseblocks: 10
Current maximum erase counter value: 2
Minimum input/output unit size: 2048 bytes
Character device major/minor: 249:0
Present volumes: 0
Volume ID: 0 (on ubi1)
Type: dynamic
Alignment: 1
Size: 18 LEBs (2285568 bytes, 2.1 MiB)
State: OK
Name: tp_data
Character device major/minor: 249:1
===================================
ubi2
Volumes count: 2
Logical eraseblock size: 126976 bytes, 124.0 KiB
Total amount of logical eraseblocks: 64 (8126464 bytes, 7.7 MiB)
Amount of available logical eraseblocks: 0 (0 bytes)
Maximum count of volumes 128
Count of bad physical eraseblocks: 0
Count of reserved physical eraseblocks: 20
Current maximum erase counter value: 2
Minimum input/output unit size: 2048 bytes
Character device major/minor: 248:0
Present volumes: 0, 1
Volume ID: 0 (on ubi2)
Type: dynamic
Alignment: 1
Size: 20 LEBs (2539520 bytes, 2.4 MiB)
State: OK
Name: user_data1
Character device major/minor: 248:1
-----------------------------------
Volume ID: 1 (on ubi2)
Type: dynamic
Alignment: 1
Size: 20 LEBs (2539520 bytes, 2.4 MiB)
State: OK
Name: user_data2
Character device major/minor: 248:2