OpenWrt Forum Archive

Topic: Installing OpenWrt in Xiaomi Wifi Mini

The content of this topic has been archived between 8 Feb 2018 and 5 May 2018. Unfortunately there are posts – most likely complete pages – missing.

StrangeOrange wrote:

On an unrelated note, using the method I described above I made some changes to the filesystem inside PandoraBox binary image, making it basically like the vanilla OpenWrt (removing China-specific stuff, translations, not widely-used packages, reverting most of the interface changes to the OpenWrt defaults; basically making it more or less like the stock OpenWrt with their WiFi optimizations while keeping the more useful packages that were already installed). I can share the process, patch set and perhaps the result: if anyone is interested, let me know (otherwise I wouldn't want to clog up the forum).

StrangeOrange, I'd definitely be interested in getting your resulting customized firmware binary!

StrangeOrange wrote:

Long post. Scroll down to the first heading to skip the non-technical part.

As much as I'd love to use bleeding-edge OpenWrt proper on this router, I find the Wi-Fi performance too disappointing compared to Pandora Box, so I'm reluctantly warming up towards the idea of staying with the latter for the time being.

Pandora Box is a partly-relabeled, Chinese fork of an older OpenWrt release (Barrier Breaker 14.07) that apparently includes some changes to the Wi-Fi driver that make its performance better. To the extent that I know of, the source code has not been made available, so the driver changes cannot be ported back to OpenWrt proper.

Don't know if this is related to your work, do you already know the following stuff?
https://github.com/rssnsj/openwrt-xiaomi-mini
https://github.com/luyujun/pandorabox

StrangeOrange wrote:

On an unrelated note, using the method I described above I made some changes to the filesystem inside PandoraBox binary image, making it basically like the vanilla OpenWrt (removing China-specific stuff, translations, not widely-used packages, reverting most of the interface changes to the OpenWrt defaults; basically making it more or less like the stock OpenWrt with their WiFi optimizations while keeping the more useful packages that were already installed). I can share the process, patch set and perhaps the result: if anyone is interested, let me know (otherwise I wouldn't want to clog up the forum).

Yes please, share the result.

I'd love to try StrangeOrange's version of Pandora. I've basically use the router as CPE, 5ghz as backlink to main router, and 2ghz for local wifi access. Last time i set it with pandora, the 5ghz is very buggy when set as client.

Now I'm settled with Openwrt Trunk with lower-than-normal 2ghz signal which is acceptable in most cases.

StrangeOrange wrote:

On an unrelated note, using the method I described above I made some changes to the filesystem inside PandoraBox binary image, making it basically like the vanilla OpenWrt (removing China-specific stuff, translations, not widely-used packages, reverting most of the interface changes to the OpenWrt defaults; basically making it more or less like the stock OpenWrt with their WiFi optimizations while keeping the more useful packages that were already installed). I can share the process, patch set and perhaps the result: if anyone is interested, let me know (otherwise I wouldn't want to clog up the forum).

I would really like that!

Flashed openwrt latest as an upgrade from pandora's update section. But after flashing,my wan is stuck on collecting data.So, cant use internet on my pc connected to the router Also as this is a trunk,there should not be a gui but there is one when I access 192.168.1.1.why?Also my router is connected to an adsl modem if that helps.

(Last edited by akp.ajinkya on 3 Jan 2016, 22:12)

StrangeOrange wrote:

On an unrelated note, using the method I described above I made some changes to the filesystem inside PandoraBox binary image, making it basically like the vanilla OpenWrt (removing China-specific stuff, translations, not widely-used packages, reverting most of the interface changes to the OpenWrt defaults; basically making it more or less like the stock OpenWrt with their WiFi optimizations while keeping the more useful packages that were already installed). I can share the process, patch set and perhaps the result: if anyone is interested, let me know (otherwise I wouldn't want to clog up the forum).

I'd like to use your custom firmware as well : D

(Last edited by ramx2 on 5 Jan 2016, 09:52)

If I saw correctly, Witi Board has same chipset, same 2.4 and same 5.8 radio sa Xiaomi Mini router. Right?
Has annybody tried Xiaomi Mini device? Does it work with OpenWrt? Does 5ghz radio work?

I see on forums that Witi Board has working 2.4 and 5.8 Ghz radio... so if it works for Witi Board it should work also for Xiaomi becaues from datasheet it looks to use same components.

OpenWrt/PandoraBox for International Users

Scroll down for download link

As much as I would prefer to have the stock OpenWrt on Xiaomi WiFi Mini, the wireless networking performance is much better with a Chinese fork of it named PandoraBox. Although most of the stuff under the hood is still OpenWrt, PandoraBox has a heavily customized interface in Chinese, and includes by default numerous packages of limited use, in particular to people outside China.

Using the filesystem unpacking method I posted about before, I patched the latest version of PandoraBox to bring it back to the stock OpenWrt look and feel, which I prefer, while also removing China-specific and other niché packages. On top of that, later I also made some other optimizations. I intended this to be for my own personal use but since there are people interested in it I'd like to share it with the community.

There are two versions, called Minimal and Optimal. The former is essentially reverting as much as possible to the original, vanilla OpenWrt state. The latter builds up on top of that with the changes and additions I made for my own use, excluding any specific configuration files only applicable to my router. The differences are described in more detail below, and for complete information you can have a look at the patch source, which I encourage you to do.


Versions
Minimal

As close as possible and practical to stock OpenWrt installation. Generally without adding any files to the filesystem image:

  • Removed China-specific and other not widely-used packages, in particular: FTP server, Huawei modem drivers, tunnelling (incl. IPv6), traffic shaping, obsolete VPN technologies. See sources for full list.

  • Removed Chinese and other non-English translations as well as the LuciXEyE theme.

  • Kept the more widely-used pre-installed packages, in particular: IP filtering-related and other kernel modules, filesystem and USB-related software, SMB and UPnP support.

  • Removed PandoraBox branding in places such as login banner, default hostname and Wi-Fi ESSIDs and restored stock OpenWrt Barrier Breaker defaults where possible (in places such as the shell prompt), while retaining PandoraBox authors' text notices for parts they created or significantly modified.


Optimal

Based on the Minimal Version above, with further optimizations that require changes beyond patching the filesystem image such as adding new packages or other files and replacing existing ones. In particular:

  • Add LUA module to uhttpd to bypass the CGI interface for improved speed.

  • Add SSL module to uhttpd and only allow Web administration over HTTPS for improved security.

  • Add Midnight Commander shell (mc) and GNU Screen (screen) for improved administration through SSH.

  • Include pre-generated HTTPS certificates since the utility to generate them at run-time is missing from PandoraBox. The CA certificate file, available as a separate download, can be added to your trusted store to switch off any certificate warnings.

  • Provide optimized configuration defaults for the firewall and network settings. Enable NAT hardware acceleration by default. Disable HTTP CGI and only allow HTTPS traffic. Provide better defaults for DHCP, SMB, SSH, UPnP.

  • Include an interface alias and a firewall rule to access the private interface of a modem. Default settings are for a modem at 192.168.1.1, if yours has a different address edit it in the file /etc/firewall.user. To use, go to http://modem/.

  • IP address on local interface changed from 192.168.1.1 to 10.0.0.1 to make the modem private interface accessible.

  • Remove CGI-specific files from HTTP server web root and change the index page to use the LUA module.

  • Remove HTML footer version string from Luci for a little more security by obscurity.

  • Customize the shell prompt, provide optimal default settings for Midnight Commander and GNU Screen.

  • Rename "hd_idle" to "Hard Disk Idle" in Luci configuration.

  • Trim the default banner in /etc/banner and include a ridiculous pre-login SSH banner in /etc/banner.ssh to fend off potential infiltrators.

  • Replace the Luci favicon.


History

Update 0 (2016-01-08)

  • Initial public version.

Update 1 (2016-01-13)

  • [Fix] [All] Installation procedure simplified, no longer any need to check for possible JFFS2 issues. Images now include proper padding just like any standard OpenWrt distribution.

  • [Fix] [All] WPA options now showing correctly in Luci WiFi configuration, wifi.lua and wifi_add.lua restored to compiled PandoraBox version in /usr/lib/lua/luci/model/cbi/admin_network/. Thanks to joaomconde for spotting this bug.

  • [Fix] [All] Samba NetBIOS name no longer being reverted to "OPENWRT_XXXX" even when hostname was customized.

  • [Fix] [Opt] Remove unnecessary UCI defaults files as configuration files are already preloaded.

  • [Fix] [Opt] No longer necessary to manually copy over preloaded config files upon first boot.

  • [New] [Opt] HTTPS server's default LAN IP address (10.0.0.1) added to SSL certificate DNS names.

  • [New] [Opt] Another instance of HTTP server now listens on port 80 and redirects traffic to HTTPS.

  • [Meta] Scripted build environment for patched images. Much simpler to create your own images now for anyone that wishes to do so.

Update 2 (2016-01-16)

  • [Fix] [Opt] Prevent a likely JFFS2 initialization problem if flashed on top of a larger firmware image without erasing the partition that would prevent the /overlay partition from being mounted correctly. Thanks to FJorgeR for reporting this.

  • [Fix] [Opt] Prevent a boot loop if JFFS2 filesystem on /overlay not mounted properly on first boot. Thanks to FJorgeR for reporting this.

  • [Meta] Fix the generation of add_package_log.txt and rm_package_log.txt by patching scripts.


Update 3 (2016-01-19)

  • [New] [All] Updated PandoraBox base from release 1216 to release 1597 (2015-11-07). This bumps up the kernel version from 3.14.48 to 3.14.56. Still based on OpenWrt Barrier Breaker but apparently some parts were backported from newer branches. Some changes to the Wi-Fi setup suggest that performance might improve.

  • [New] [All] VFAT and exFAT kernel support modules were removed from the newer PandoraBox base, and they are accordingly not included in the patched versions. For Windows filesystem support through USB add the packages kmod-fs-vfat and kmod-fs-exfat from the repository.

  • [Fix] [All] Repository archive updated and changed from the original to remove unnecessary dependency of kmod-fs-vfat and kmod-fs-exfat on kmod-nls-cp936 (Simplified Chinese codepage).

  • [Fix] [All] No longer including plain-text replacement for *.lua files due to potential errors this may introduce, except /usr/lib/lua/luci/controller/admin/status.lua, which is necessary to remove the ip-bandwidth menu entry.

  • [Fix] [All] Workaround Samba fatal error due to confusion caused by the overlay filesystem over the file /etc/samba/secrets.tdb. Replaced this file with a symbolic link to /tmp/secrets.tdb. If you want it to persist between reboots, it also works when stored directly under /overlay.

  • [Fix] [Opt] Resolved the issue of double slashes appearing in self-referring URLs by patching  /usr/lib/lua/luci/view/themes/bootstrap/header.htm. There was a similar issue in OpenWrt trunk but the file from trunk could not be ported as it breaks per-interface real-time graphs.

  • [Fix] [Opt] Additional restart after first boot no longer necessary to apply preloaded configuration settings. As a result, the time from flashing to login readiness is shortened for the Optimal version. Note though that on first boot server keys need to be generated before you can login through SSH, so if your connection is refused initially it's due to this.

  • [Fix] [Opt] Fixed Midnight Commander "Cannot load codepage list" warning message upon startup.

  • [New] [Opt] Separately including the certificate files (HTTPS and CA) that can be added to your local trusted store to make any SSL warnings disappear when connecting to OpenWrt. The private key for this certification authority has been deleted, which means no further certificates can be signed with it, so it's safe to add it (if you trust my word on this one).

  • [Meta] Significant changes to patch source scripts.


Update 4 (2016-01-27)

  • [New] [All] Since PandoraBox keeps evolving to include more and more packages, as an experiment I have adjusted my approach this time and decided to keep most of them, only removing those that are China-specific, as well as non-English translations (because they were incomplete anyway), and also the MWAN functionality and FTP server.

  • [New] [All] This means that the current version now includes in particular: Aria2 Downloader, ARP Bind, CPU Limit, IP Bandwidth (traffic accounting), NGrok Client, SQM, Transmission BitTorrent Client, Wake-on-LAN, as well as all the kernel modules that were originally provided, except the Simplified Chinese codepage. Hopefully this change is in line with what (at least the most vocal) people wanted.

  • [New] [All] Original PandoraBox version also adds the Material theme and defaults to it. I have kept it and made it the default in the Optimal version too. You can still switch back to the default Bootstrap theme if you want to.

  • [Fix] [All] Fixed double slashes in self-generated URLs in the Material theme; while there, also removed the "Loading..." label, keeping only the animated circle, which is already self-explanatory.

  • [Fix] [All] Disable NAT hardware acceleration by default, identified as a potential source of problems.

  • [Fix] [Opt] Changed "aria2" to "Aria2 Downloader", "cpulimit" to "CPU Limit" and "ipbandwidth" to "IP Bandwidth" in the Web interface menu.

  • [Fix] [Opt] Improved the descriptive text on the "IP Bandwidth" page in the Web interface menu.

  • [New] [Opt] Since PandoraBox now includes OpenSSL command-line tools, include the OpenSSL configuration file I previously posted separately as the default /etc/ssl/openssl.cnf.

  • [Meta] Changed the name of edit and patch source script archives to Custom-Edit and Custom-Patch respectively for better clarity.

  • [Meta] Case adjustments to filenames in the downloads folder.

Before downloading, please make sure you understand that all this comes with no warranty whatsoever. While it works for me, I will not be responsible for any damage caused or assumed to be caused by whatever you decide to do with those files. If anything goes wrong you are on your own to fix it. Please make sure you are comfortable with this before proceeding. Thank you.


Downloads
  • <Version> is either "Minimal" or "Optimal"

  • Un is an update identifier, where n is a number that increases with every update.

  • rnnnn is the PandoraBox release identifier, which points to the version of the binary image this patch is based on.

XMWiFiMini-OpenWrt-PandoraBox-14.09rnnnn-StrangeOrange-<Version>-Un.bin
Firmware image. This is the flashable file you most likely want.

XMWiFiMini-OpenWrt-PandoraBox-14.09rnnnn-StrangeOrange-<Version>-Un.squashfs
Filesystem image. Use with the script below to make your own custom version based on this firmware.

XMWiFiMini-OpenWrt-PandoraBox-14.09rnnnn-StrangeOrange-Custom-Edit.tar.gz
Use this to make any changes you want to the filesystem, and rebuild it into a flashable firmware. More information.

XMWiFiMini-OpenWrt-PandoraBox-14.09rnnnn-StrangeOrange-Custom-Patch.zip
Full sources to re-create all the patched files, starting from the original PandoraBox firmware. More information.

XMWiFiMini-OpenWrt-PandoraBox-14.09rnnnn-Repository.zip
Complete mirror of PandoraBox package repository in case it ever goes offline.

XMWiFiMini-Bootloader-Breed-rnnn.zip
Mirror of a great bootloader for Xiaomi MiWiFi Mini. More information.

OpenSSL-Certificate-Generation-StrangeOrange.zip
Makes it easier to generate SSL certificates with OpenSSL for use with OpenWrt. More information.

OpenSSL-Certificate-XMWiFiMini-OpenWrt-PandoraBox-StrangeOrange.crt
OpenSSL-Certificate-XMWiFiMini-OpenWrt-PandoraBox-StrangeOrange-CA.crt
Server (HTTPS) and CA certificates that can be added on your system to make the certificate warning go away. With Chrome or IE on Windows, properly installing the second one should be enough.

Checksums-MD5-SHA1.txt
Use the information from this file to verify if the other files that you downloaded are intact.

The downloads are currently hosted at Mega.NZ. If you have a better idea where to put those files, feel free to let me know.


Instructions
  1. Flash from within any existing OpenWrt or PandoraBox installation through the Web interface or from the shell:
    jffs2reset -y
    sysupgrade -n <filename>.bin

    Or flash directly from the original Xiaomi firmware:
    jffs2reset -y
    mtd -r write <filename>.bin OS1

    Or use Breed bootloader.

  2. Connect to Wifi network OpenWrt-2.4GHz-XXXX or OpenWrt-5.0GHz-XXXX.

  3. SSH to hostname openwrt or point your browser to http://openwrt/.
    (You will be redirected to https://openwrt/ in the Optimal version.)

  4. Log in with username root and the default password admin.

  5. For easy navigation around the filesystem over SSH, after logging in type mc and press Enter (Optimal version only).


Usage Notes
  • When flashing the Optimal version your settings will not be retained. Please back them up manually if you wish to keep them.

  • Recent PandoraBox versions include Wi-Fi client separation by default. If you want to enable communication between clients on the same interface, please add the following two lines to /etc/rc.local:


    iwpriv ra0 set NoForwarding=0
    iwpriv rai0 set NoForwarding=0


Enjoy!

(Last edited by StrangeOrange on 26 Jan 2016, 19:38)

OpenWrt/PandoraBox for International Users: Patch Sources & Miscellanea

For downloads, scroll up to previous post

If you want to create your own version of the patch, you are of course most welcome to do so. This allows you to skip some of the changes I made or add your own. The whole process is scripted and easy to replicate. For background and more details about separating the filesystem from the rest of the image, see my previous post. The following is just the gist of it.


Complete Patch Sources

The full sources allow you to regenerate all the files, starting with the original PandoraBox image. You can of course make any adjustments along the way but in the most basic scenario:

  • Extract the sources and scripts into /tmp on the router

  • Run ./All_Patch_Build_Release.sh to perform all the steps in one go.

Please look into the source of the included shell scripts for customization and other ways of using them.


Edit Scripts

This is a much simpler version of the scripts above that allows you to simply unpack the filesystem image so that you can make changes to it and then build a flashable firmware from it. To use:

  • Extract the files and scripts into /tmp/edit/ on the router.

  • Place one of the filesystem images as /tmp/edit/fw_fs.bin.

  • In /tmp/edit/, run ./ExtractOriginalFilesystem.sh.

  • The filesystem will be unpacked into /tmp/edit/fw_fs. Make any changes you want.

  • Build the modified filesystem back with ./RebuildModifiedFilesystem.sh.

  • Build your modified flashable firmware with ./RebuildModifiedFirmware.sh.


Further Customization

Looking at the sources, you will notice the scripts can also build images for a third, "private" version, which is not included among the files above. This is basically the Optimal version with more customizations specific to my particular setup: it wouldn't be of much use if I posted it here, however, you might be interested in making changes in the same places I did, so here's a list of some other customization ideas:

  • Set-up custom DDNS script in /etc/config/ddns and /usr/lib/ddns/services.

  • Network settings: customize the hostname in /etc/config/samba, /etc/config/system, /etc/init.d/miniupnpd; change WAN interface to PPPoE, if that's your ISP's setup, in /etc/config/network; timezone in /etc/config/system; Wi-Fi ESSID and passphrase in /etc/config/wireless; UPnP bandwidth rates in /etc/config/upnpd.

  • Add own SSH key to /etc/dropbear/authorized_keys and include SSH host keys /etc/dropbear/dropbear_*_host_key so that they don't change with every re-installation.

  • Set a password different than the default "admin" for root in /etc/shadow.

  • Populate /etc/ethers and /etc/hosts with the addresses of local network devices to allow static IP allocation.

  • Replace the default HTTPS certificate and key to the ones matching the changed hostname in /etc/uhttpd.crt and /etc/uhttpd.key.

You can easily adapt the script for making your own version of a "private" firmware. See the sources for details.


Room for Improvement

Here are some ideas what could be improved about this project:

  • Instead of replacing the LUA files decompile the ones supplied with PandoraBox. The following procedure can be adapted: http://storypku.com/2015/07/how-to-deco … lua-files/

  • Port PandoraBox's Wifi drivers and setup so that stock OpenWrt can be used directly with comparable performance.


Acknowledgements

I would like to take this opportunity to express my gratitude to:

  • The authors of OpenWrt for providing a complete and well-engineered Linux distribution for embedded systems, on which this firmware is based.

  • The authors of PandoraBox for providing a fully functional build of OpenWrt for the Xiaomi WiFi Mini that takes  advantage of all its features.

  • Users on OpenWrt and MIUI message boards who provide feedback about their experiences, which allows continual bug fixes and enhancements.

(Last edited by StrangeOrange on 26 Jan 2016, 19:29)

arin wrote:

Don't know if this is related to your work, do you already know the following stuff?
https://github.com/rssnsj/openwrt-xiaomi-mini
https://github.com/luyujun/pandorabox

Thanks, I've seen them before. The second one is supposedly the source code of PandoraBox but from a much older release two years ago. The first one is, according to its author, a port of some OpenWrt CC code (from the time CC was the head/trunk/unstable) into the BB branch to make it work with Xiaomi WiFi Mini, it's unrelated to PandoraBox. It seems abandoned as well.

Hi StrangeOrange,

First Big Thanks for sharing your awesome tutorials with us. They are great help for openwrt newbies like myself.

I wanted to flash Breed to replace my stock u-boot, but I've encountered a problem.
Whenever I go the actual flashing I see:
"Could not open mtd device"

This happens on original developer firmware (miwifi_r1cm_firmware_ae50f_2.9.9.bin), PandoraBox and on your custom PandoraBox-Minimal. Is there a way to unlock mtd or am I forced to use hardware method?

mike3e wrote:

I wanted to flash Breed to replace my stock u-boot, but I've encountered a problem.
Whenever I go the actual flashing I see:
"Could not open mtd device"

Hi,

What is the exact command you are typing (mtd write ...), and what is the output of cat /proc/mtd? Since you didn't mention these, there's a slight chance it's caused by a typo somewhere. There's also mtd unlock u-boot which you can try as well. If it still doesn't work, then I have some bad news and some good news for you:

Bad news first: according to this discussion thread it appears that flashing the bootloader might indeed be locked under PandoraBox.

Good news though: it should definitely work with some other firmware: that's how I flashed it, although I can't remember if I had the Xiaomi development version or stock OpenWrt installed at the time. Maybe someone else who also flashed Breed has better memory and can confirm which firmware they were able to flash it from? Short of that, try going to stock OpenWrt just to change the firmware.

Some more good news: this will only be necessary once. Later the bootloader can be reflashed from within Breed itself.

Note: check that you are flashing the correct file and that the MD5 sum matches, there is no software way to recover from a badly flashed bootloader (once the device is rebooted). Also make sure the power supply is stable and the power plug is secure.

thanks for your effort, but this forum is about opensource firmware and wifi drivers, if you feel like you need to share your work which doesn't have much impact on what we are trying to accomplish here at least you could write it on your blog or pandorabox forum (if any exist) and post only a link here instead of flooding a thread with endless repacking tutorials.

Hi again,

Thanks for your prompt answer. I've arrived to the same conclusion after some browsing.
I've started by checking the firmwares you provided in your performance comparison and I had success on the 3 go wink
Bootloader partition was unlocked on the Padavan firmware but there are catches. I'll leave it here in case someone will have the same problems.

1) In my case I was unable to connect by the ssh so I had to use telnet.
2) Default login and password for this distribution is admin:admin
3) Instead of mtd command I had to use mtd_write and it does take device alias as the parameter:
instead of typing:
mtd write mtd write breed-mt7620-xiaomi-mini.bin mtd0
I had to use:
mtd_write write breed-mt7620-xiaomi-mini.bin Bootloader

@anarchy99:
From a political standpoint, or the standpoint of the "owner of this forum", you might be correct.
However, as a user of openwrt, I am happy to see somebody publishing workarounds for shortcomings in openwrt for officially supported devices.

anarchy99 wrote:

thanks for your effort, but this forum is about opensource firmware and wifi drivers, if you feel like you need to share your work which doesn't have much impact on what we are trying to accomplish here at least you could write it on your blog or pandorabox forum (if any exist) and post only a link here instead of flooding a thread with endless repacking tutorials.

That's why I asked if anyone was interested beforehand:

StrangeOrange wrote:

[...] I can share the process, patch set and perhaps the result: if anyone is interested, let me know (otherwise I wouldn't want to clog up the forum).

And only proceeded further after such interest was expressed:

bdonkey wrote:

StrangeOrange, I'd definitely be interested in getting your resulting customized firmware binary!

Badazdz wrote:

Yes please, share the result.

irwan6179 wrote:

I'd love to try StrangeOrange's version of Pandora. [...]

ramx2 wrote:

I'd like to use your custom firmware as well : D

I am not claiming to be doing some voodoo magic here but this "endless repacking" happens to be a simple, time-efficient way of obtaining the best working firmware for this device at the moment, which is the reason why I'm doing it. I think there are some other people here who realize that.

This is still open-source software by the way. Just because someone appears to be in breach of the licence at the moment due to up-to-date sources not being released does not suddenly make it proprietary.

I am perfectly fine with the moderators deleting my posts should they decide to do so. In fact, I believe either my posts or the one you just made should be deleted, as someone is clearly in breach of the rules here. I leave it at the moderators' discretion to decide who this is.

As a more personal comment, I am a member of a couple of other forums and even if had a strong opinion about a particular post I would never post anything like you just did, unless I were a moderator myself. The most I would do is to bring it to the attention of moderators using the Report button, inconveniently located in the lower right corner under each particular post. I am really sorry to be the one that has to tell you that but people like you give the free software community a bad name (not "open source," by the way, there is an important difference here). You could get away with this sort of attitude if you were Theo de Raadt or Linus Torvalds but that seriously still doesn't make it right.

I will refrain from further posting pending the moderators' decision. Thank you everyone for taking the time to read my posts so far, and have a great weekend.

[Update: Ending my self-imposed break so as not to leave users' questions unanswered, and assuming that since the moderators did not intervene, it's OK to go on.]

(Last edited by StrangeOrange on 11 Jan 2016, 08:00)

hi StrangeOrange i just updated my router via breed, but i cant access the web interface. im trying to reach it through 10.0.0.1 does your package includes luci or do i have to install it myself?

Thank you very much for your work!

(Last edited by joaomconde on 11 Jan 2016, 05:26)

discovered it! in ect/config/uhttpd, you should add "option 'listen_http' '80'"else you cant connect to luci!

joaomconde wrote:

hi StrangeOrange i just updated my router via breed, but i cant access the web interface. im trying to reach it through 10.0.0.1 does your package includes luci or do i have to install it myself?

Hi Joao,

In the Optimal version i only left the HTTPS (encrypted) connections on, so you should go to https://openwrt/. Sorry for not making it more intuitive. With the next update I will make it so that http://... redirects to https://... automatically.

StrangeOrange wrote:
joaomconde wrote:

hi StrangeOrange i just updated my router via breed, but i cant access the web interface. im trying to reach it through 10.0.0.1 does your package includes luci or do i have to install it myself?

Hi Joao,

In the Optimal version i only left the HTTPS (encrypted) connections on, so you should go to httpshmm/openwrt/. Sorry for not making it more intuitive. With the next update I will make it so that http://... redirects to httpshmm/... automatically.

Thanks fo r the fast answer! Another thing, what do i have to install to have WPA encription options? is it posssible?

Hi all,

I have a problem with my miwifi mini. Immediately after receiving it I went straigth to reflashing it with openwrt and breed bootloader. However I might have overwritten part of the flash which I probably shouldn't (arp perhaps?).
I'm able to flash any of the openwrt images just fine, but my 2.4G network interface does not work completely and 5G only works on Chaos Calmer.
Chaos Calmer won't allow me to setup anything for 2.4G and I cannot see any OpenWrt_XXXX network with my 2.4G devices.

On PandoraBox based images I cannot scan for APs neither on 2.4G nor 5G.
I'm able to see the OpenWrt_XXXX briefly on my 2.4G devices but I'm unable to actually connect to the router over WiFi.
Status page shows -256 dBm for the signal strength and SNR.

Could anyone PM full dump (16 MB) of their own FW? I could add my SN and MAC there and try to flash whole image.
Or maybe someone knows some other way to fix this?

joaomconde wrote:

Another thing, what do i have to install to have WPA encription options? is it posssible?

Good catch, it seems you found a bug: the WPA options are not showing in the Web interface. I'm guessing it's because I replaced the compiled PandoraBox LUA files with their text versions from another device's stock filesystem and there must be some incompatibility. I'll look into it. (The reason I replaced the files is that the compiled ones are uneditable.)

However, WPA itself works just fine, no need to install anything extra. For now, you can put the following settings in /etc/config/wireless:

config wifi-device 'rai0'
        option type 'mt7612'
        option hwmode '11a'
        option channel 'auto'
        option txpower '100'
        option htmode 'VHT80'
        option country 'CN'

config wifi-iface
        option device 'rai0'
        option network 'lan'
        option mode 'ap'
        option ssid 'NAME5'
        option encryption 'psk2'
        option key 'PASSWORD'

config wifi-device 'ra0'
        option type 'rt2860v2'
        option hwmode '11g'
        option channel 'auto'
        option txpower '100'
        option htmode 'HT40'
        option country 'CN'

config wifi-iface
        option device 'ra0'
        option network 'lan'
        option mode 'ap'
        option wps 'pbc'
        option ssid 'NAME2.4'
        option encryption 'psk2'
        option key 'PASSWORD'

That's why I didn't notice it in the first place, I set it up through the config file. To change the settings, log in through SSH and type mc to run Midnight Commander. You can the browse to the file and press F4 to edit it and F2 to save. Afterwards, type wifi and press Enter to apply the new config.

Replace NAME5 with the name of your 5GHz network, NAME for the 2.4GHz one, and PASSWORD with your passhprase (in plain-text).

mike3e wrote:

Or maybe someone knows some other way to fix this?

From the Breed FAQ:

Q: After replacing U-Boot with Breed there's no Wi-Fi.
A: Fix the MAC address(es) from within Breed.

Maybe you can try to go to that page in Breed and see what shows up, if the MAC addresses are correct.

Note: I never used this function, just happened to read about it. Be careful and make a backup first before changing anything. The word for 'backup' is "备份."

(Last edited by StrangeOrange on 11 Jan 2016, 20:28)

StrangeOrange wrote:
mike3e wrote:

I wanted to flash Breed to replace my stock u-boot, but I've encountered a problem.
Whenever I go the actual flashing I see:
"Could not open mtd device"

Hi,

What is the exact command you are typing (mtd write ...), and what is the output of cat /proc/mtd? Since you didn't mention these, there's a slight chance it's caused by a typo somewhere. There's also mtd unlock u-boot which you can try as well. If it still doesn't work, then I have some bad news and some good news for you:

I have some problem. Looks like bootloader locked under openwrt.

root@gw1:/tmp# cat md5sum.txt | fgrep xiaomi
d7c407dffa73362d7356cdf8d2fd5e2e  breed-mt7620-xiaomi-mini.bin
root@gw1:/tmp# md5sum breed-mt7620-xiaomi-mini.bin
d7c407dffa73362d7356cdf8d2fd5e2e  breed-mt7620-xiaomi-mini.bin
root@gw1:/tmp# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00030000 00010000 "u-boot"
mtd1: 00010000 00010000 "u-boot-env"
mtd2: 00010000 00010000 "factory"
mtd3: 00f80000 00010000 "firmware"
mtd4: 00115fee 00010000 "kernel"
mtd5: 00e6a012 00010000 "rootfs"
mtd6: 00c50000 00010000 "rootfs_data"
mtd7: 00010000 00010000 "crash"
mtd8: 00010000 00010000 "reserved"
mtd9: 00010000 00010000 "Bdata"
root@gw1:/tmp# mtd write breed-mt7620-xiaomi-mini.bin mtd0
Could not open mtd device: mtd0
Can't open device for writing!
root@gw1:/tmp# mtd unlock mtd0
Could not open mtd device: mtd0
Could not open mtd device: mtd0
root@gw1:/tmp# cat /etc/openwrt_release 
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='Chaos Calmer'
DISTRIB_REVISION='r48153'
DISTRIB_CODENAME='chaos_calmer'
DISTRIB_TARGET='ramips/mt7620'
DISTRIB_DESCRIPTION='OpenWrt Chaos Calmer 15.05'
DISTRIB_TAINTS='no-all'

Didn't help — i don't have 'openwrt/target/linux/ramips/files/drivers/mtd/tplinkpart.c'.

EDIT: Okay, i just do 'mtd write breed-mt7620-xiaomi-mini.bin u-boot'.

(Last edited by Althathwe on 11 Jan 2016, 21:39)