Guide for GL.iNet GL-MV1000 (Brume)

[hsimah]

Does anyone have instructions or a guide for installing OpenWRT on GL.iNet GL-MV1000 (Brume), I can't seem to find any clear set of instructions.

Techdata page can be found here [OpenWrt Wiki] Techdata: GL.iNet GL-MV1000 (Brume)

The Firmware OpenWrt Install URL is located here Index of /releases/19.07.7/targets/mvebu/cortexa53/ (openwrt.org) but after this step I am unsure what needs to be done next. Which file do I download? I can't find any files in the directory called 'factory' etc.

I have tried using this guide [OpenWrt Wiki] Factory install: First-time installation on a device.

I basically would like to install stock OpenWRT as the GL.iNet firmware is not enjoyable.

[slh]

mvebu: add support for GL.iNet GL-MV1000

While not overly verbose, there seems to be a recovery webinterface that takes OpenWrt images to flash.

Hint: the wiki would profit from some help.

[erdoukki]

GL.iNet installation instructions

And

https://docs.gl-inet.com/en/3/setup/brume_w/upgrade/

[hsimah]

So can I just upload a normal OpenWRT firmware and it should just revert to stock?

[erdoukki]

Yes, but not tested myself...

[felang]

Did this work for you?

[Flyinace2000]

Which file do you use for the MV1000? One of the Marvel?

[slh]

Correct subtarget, wrong release version, you'll need master or openwrt-21.02.

[Flyinace2000]

Thanks. I think glinet_gl-mv1000-squashfs-sdcard.img.gz is the one i use, right?

[slh]

https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=050c24f05c85268431515fb118a0710941473f2c

[Flyinace2000]

I saw that. I'm missing how that answers my question. Sorry.

[felang]

Let me know if you figure this out, I’m having problems with cake sqm using gl.inet provided firmware, would love to try stock openwrt.

[rp201]

https://firmware-selector.openwrt.org/?version=21.02.0-rc1&target=mvebu%2Fcortexa53&id=glinet_gl-mv1000

i see two sdcard images but not sure how they are utilized. I believe the

[glxwrt]

There is some info in the ToH at https://openwrt.org/toh/gl.inet/gl-mv1000

[glxwrt]

From https://openwrt.org/toh/gl.inet/gl-mv1000#uboot_method

• Download one of the glinet_gl-mv1000 OpenWRT images (21+ or snapshot). Choose either the ''ext4'' or ''squashfs'' filesystem.
  • The images are called “sdcard”, but this refers to the internal eMMC card; you don't need anything on the MicroSD slot.

[glxwrt]

Apologies for the triple post

I have gotten extroot working on the GL-MV1000 with the 21.02 release and wanted to mention it for others.

1. I used U-boot method to install the ext4 image from https://downloads.openwrt.org/releases/21.02.1/targets/mvebu/cortexa53/
2. I subsequently followed the extroot instructions at https://openwrt.org/toh/gl.inet/gl-mv1000#increasing_the_root_filesystem with a bit of extra detail to get extroot working and use the full 8GB of onboard flash:
   • after following the procedure in the ToH and generating /etc/config/fstab, I modified /etc/config/fstab to set the filesystems to enabled (see below)
   • I needed to reboot for the changes to take effect.

This is my /etc/config/fstab with uuids removed because I wasn't sure if there is a privacy concern. All you need to do is change the target as shown and set enabled to 1 for /rom and /overlay

More info on fstab: https://openwrt.org/docs/guide-user/storage/fstab

config global
	option anon_swap '0'
	option anon_mount '0'
	option auto_swap '1'
	option auto_mount '1'
	option delay_root '5'
	option check_fs '0'

config mount
	option target '/mnt/mmcblk1p1'
	option uuid '[redacted]'
	option enabled '0'

config mount
	option target '/rom'
	option uuid '[redacted]'
	option enabled '1'

config mount
	option target '/overlay'
	option uuid '[redacted]'
	option enabled '1'

PS I have no idea if /mnt/mmcblk1p1 should also be mounted but so far nothing seems broken??

Edit 2: I used opkg install kmod-rtl8812au-ct hostapd to get an Alfa AWUS036ACS wifi dongle driver and associated software, which is one recommended by GL-inet for use with their own firmware, but looks like this device requires patches from GL-inet which haven't made it in to mainstream yet because it doesn't yet support AP (access point) mode yet in 21.02.

[jcizzo]

So, has anyone come up with a straight-forward set of step by step instructions for loading openwrt onto the mv1000 brume? i ordered one yesterday, it just arrived and i really want to load base openwrt on it, and get around gl.inet's version.

can it be installed onto the device or does it have to be installed on a microsd card?

thanks!

[glxwrt]

Installing OpenWRT 23.05 on Brume 1

This guide requires use of the command line, and covers using the extroot method of expanding storage to Brume's entire 8GB flash.

Firmware image

The following instructions contain useful info if you are building your own firmware (beyond the scope) or downloading it (full instructions included).

Package list

Regardless of how you get your firmware image, you will need some packages on it.

Here are the packages I added to the default list provided in Firmware Selector in order to have a basic install out of the box along with tools to accomplish this guide. Because Brume 1 has 8GB of space, you don't need to be too afraid of installing a few things.

luci luci-ssl luci-app-firewall luci-app-opkg luci-app-vnstat2 luci-app-ttyd rsync vim-full nano htop kmod-usb-storage kmod-usb-storage-uas kmod-fs-ext4 usbutils block-mount cfdisk

Download a custom build

You can request that the OpenWRT Firmware Selector make you a custom build with the following packages (plus whatever else you may want). Note that Luci is not included if you just download the default image without requesting a custom build.

1. Visit https://firmware-selector.openwrt.org/

2. Navigate to the page for the GL-MV1000 Brume

3. Click 'Customize installed packages and/or first boot script'

4. Paste the list of packages above at the end of the 'Installed Packages' list, plus add any others you want (dependencies will be satisfied)

5. Click 'Request Build'

6. When the build finishes, download the 'SDCARD (EXT4)' version. Note that in this case 'sdcard' is a misnomer: the image will be installed to internal flash, and no microSD is needed or used.

7. Decompress the .gz file you receive!! Firmware images are uploaded uncompressed.

Flashing

1. Plug a computer set to 192.168.1.2/24 into one of the LAN ports.

2. Power up the router with the reset button held down, and hold it til the lights come on, turn off, and then just WAN turns back on. Release the reset button at this point (don't wait too long!)

3. Ping 192.168.1.1 to verify connectivity.

4. Open an incognito browser window (UBoot has bugs related to browser cache) and go to http://192.168.1.1/ where you should see the UBoot interface.

5. Upload the decompressed firmware .img file.

6. After a few minutes, the router should reboot and be alive at 192.168.1.1, Luci visible on SSL (assuming you installed those packages) at https://192.168.1.1, etc.

Note that if UBoot consistently fails, it may be outdated and you may need to update UBoot itself in order to install newer firmware images. Updating UBoot is possible by obtaining a UBoot firmware image (currently beyond the scope of this guide) and then visiting http://192.168.1.1/uboot.html in an incognito browser window when connected to the router in UBoot mode as below.

extroot (using the 8GB eMMC)

If you want to have full use of Brume's 8GB storage to install gobs of packages, you must expand the root filesystem.

These instructions assume that you've installed appropriate tools (the packages are listed in the package lists above).

1. connect to the router on the command line, e.g. ssh root@192.168.1.1

2. # cfdisk /dev/mmcblk1

3. create a new primary partition in the big empty space, should end up as mmcblk1p3

4. # mkfs.ext4 -L extroot /dev/mmcblk1p3

5. # mkdir /mnt/extroot; mount /dev/mmcblk1p3 /mnt/extroot

6. # block detect | uci import fstab

7. copy the root filesystem to /mnt/extroot, e.g. rsync -a -x / /mnt/extroot

8. edit /etc/config/fstab:

   1. change the old root / filesystem to mount on /rom

   2. change the new filesystem mount point from /mnt/extroot to /overlay

   3. set enabled to 1 on both /rom and /overlay

9. Reboot.

[Beniamin]

Nice! Good work!