Daniel Golle

The wizard when first connecting to the device Web-UI actually forces you to set a password for the admin login on the Web-UI. **That very same password is then also...

Please edit README.md (e.g. in Github's web editor) and make a pull request, I will review and accept your change.

Yet another reason to *not* carry out that full backup and rely on the minimal backup which the installer does automatically. The minimal backup is sufficient to restore the device...

> BTW, this might be useful to add to the README. It was not clear that the minimal backup is sufficient to restore the stock fw. Done by commit https://github.com/dangowrt/owrt-ubi-installer/commit/8f02aed4a8a83494ff03e41ddfc4b0b7a3fb0dc7

Strange, I always thought that signature checking is only active in version 1.0.02.*, but it looks like signature check is now enabled also in this firmware you got there already....

Most likely you are missing firmware files. If you were are using snapshot builds, this can happen because the firmware was previously included in `kmod-mt7915e` package and now was moved...

If you use OpenWrt 22.03 the firmware for MT7915 is part of `kmod-mt7915e` which you have installed. Please share the complete system log, so I can see why the 5...

``` [ 8.830075] mtk-snand 1100d000.snfi: ECC: Uncorrectable bitflips in page 907 sect 3 [ 8.837751] mt7915e 0000:01:00.0: reading EEPROM from mtd factory failed: -74 [ 8.881036] mt7915e 0000:01:00.0: eeprom load...

@wit-know What you are seeing is the (expected) result of having used the v1.1.x installer and then trying to use an older OpenWrt release. That can't work. And it's not...

@wallrik Neither `kmod-mt7915e` nor missing firmware files are the problem here. The problem is that OP has moved the factory data into a UBI volume (instead of a raw flash...