# GL-MT2500 upgrade from 4.6.8 to 4.7.0 fails **URL:** \ **Category:** Router\ **Created:** [December 15, 2024, 9:40pm UTC](https://forum.gl-inet.com/t/gl-mt2500-upgrade-from-4-6-8-to-4-7-0-fails/51912 "2024-12-15T21:40:15Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![hecatae](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/hecatae/32/20467_2.png) [@hecatae](https://forum.gl-inet.com/u/hecatae)\ **Post date:** [December 15, 2024, 9:40pm UTC](https://forum.gl-inet.com/t/gl-mt2500-upgrade-from-4-6-8-to-4-7-0-fails/51912/1 "2024-12-15T21:40:15Z")
This seems to be identical to [GL-MT3000 upgrade from 4.6.8 to 4.7.0 fails](https://forum.gl-inet.com/t/gl-mt3000-upgrade-from-4-6-8-to-4-7-0-fails/51817/) 30\_uboot-envtools does not exist on my GL-MT2500. The question is how is this possible to happen. While @berx has manually repaired this, I'd like a solution from GL staff please as I don't want to be instructing the average user to mess around with what is basically uboot environmental settings which could lead to multiple bricked devices. All I have done is try the 4.7 beta, Openwrt and Immortalwrt. I installed 4.6.8 over Openwrt without keeping settings. This can't have removed these files. ---
**Author:** ![bruce](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bruce/32/35649_2.png) [@bruce](https://forum.gl-inet.com/u/bruce)\ **Post date:** [December 16, 2024, 6:31am UTC](https://forum.gl-inet.com/t/gl-mt2500-upgrade-from-4-6-8-to-4-7-0-fails/51912/2 "2024-12-16T06:31:25Z")
Hi, the R&D is checking this issue. Including the berx's thread. ---
**Author:** ![hecatae](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/hecatae/32/20467_2.png) [@hecatae](https://forum.gl-inet.com/u/hecatae)\ **Post date:** [December 16, 2024, 10:42am UTC](https://forum.gl-inet.com/t/gl-mt2500-upgrade-from-4-6-8-to-4-7-0-fails/51912/6 "2024-12-16T10:42:42Z")
```auto /sys/module/boot_param/parameters/env_part ``` is empty. ```auto ls -la /dev/ubi* crw------- 1 root root 10, 62 Jan 1 1970 /dev/ubi_ctrl ``` ```auto ls -la /etc/config/ubootenv -rw-r--r-- 1 root root 0 Oct 17 13:17 /etc/config/ubootenv ``` ```auto cat /proc/mtd dev: size erasesize name mtd0: 00200000 00010000 "log" ``` difference to @berx ```auto root@GL-MT2500:/dev# ls -la /dev/mmcblk* brw------- 1 root root 179, 0 Jan 1 1970 /dev/mmcblk0 brw------- 1 root root 179, 8 Jan 1 1970 /dev/mmcblk0boot0 brw------- 1 root root 179, 16 Jan 1 1970 /dev/mmcblk0boot1 brw------- 1 root root 179, 1 Jan 1 1970 /dev/mmcblk0p1 brw------- 1 root root 179, 2 Jan 1 1970 /dev/mmcblk0p2 brw------- 1 root root 179, 3 Jan 1 1970 /dev/mmcblk0p3 brw------- 1 root root 179, 4 Jan 1 1970 /dev/mmcblk0p4 brw------- 1 root root 179, 5 Jan 1 1970 /dev/mmcblk0p5 brw------- 1 root root 179, 6 Jan 1 1970 /dev/mmcblk0p6 brw------- 1 root root 179, 7 Jan 1 1970 /dev/mmcblk0p7 crw------- 1 root root 249, 0 Jan 1 1970 /dev/mmcblk0rpmb ``` Anyway, now lost ```auto dmesg | grep "Kernel command line" [0.000000] Kernel command line: console=ttyS0,115200n1 loglevel=8 earlycon=uart8250,mmio32,0x11002000 root=PARTLABEL=rootfs rootwait rootfstype=squashfs,f2fs block2mtd.block2mtd=/dev/mmcblk0p1,65536,log ``` ---
**Author:** ![berx](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/berx/32/22460_2.png) [@berx](https://forum.gl-inet.com/u/berx)\ **Post date:** [December 16, 2024, 8:03pm UTC](https://forum.gl-inet.com/t/gl-mt2500-upgrade-from-4-6-8-to-4-7-0-fails/51912/7 "2024-12-16T20:03:31Z")
I have checked openwrt-mt2500-4.7.0-1205-1733363804 and openwrt-mt2500-4.7.0-1205-1733363804. in both the file `root~/etc/uci-defaults/30_uboot-envtools/30_uboot-envtools` exists. I have attached it here: [30\_uboot-envtools.zip](https://forum.gl-inet.com/uploads/short-url/gRXoELcLjHj0Ztg7I6qq1Lh5rCu.zip) (998 Bytes) You can try and manually execute each step. It helped me at the end to understand the requirements. Of course an "official" solution by GL is a long term solution. But even your analysis can speed up their work. Just please keep sharing here. ---
**Author:** ![J33Bee](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/j/a587f6/32.png) [@J33Bee](https://forum.gl-inet.com/u/J33Bee)\ **Post date:** [December 16, 2024, 9:51pm UTC](https://forum.gl-inet.com/t/gl-mt2500-upgrade-from-4-6-8-to-4-7-0-fails/51912/8 "2024-12-16T21:51:10Z")
Okay... another update which has issues? Not a good sign, based on my latest Slate AX experience. Before never had any issues with updates and now it looks like there are again people with issues. I will wait updating my Brume 2... > [@Slate AX Wireless Section inaccessible "Unknown error occurred" since updating](https://forum.gl-inet.com/t/slate-ax-wireless-section-inaccessible-unknown-error-occurred-since-updating/47408/1): > > Hello, not sure if it's related to the update, but I can no longer access the Wireless menu of my router. It says "Unknown error occurred. Please check the Network environment or reboot device" Rebooting doesn't work. How do I fix it? version is: 4.6.4 ---
**Author:** ![Renato](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/r/858c86/32.png) [@Renato](https://forum.gl-inet.com/u/Renato)\ **Post date:** [December 16, 2024, 11:15pm UTC](https://forum.gl-inet.com/t/gl-mt2500-upgrade-from-4-6-8-to-4-7-0-fails/51912/9 "2024-12-16T23:15:14Z")
> [@J33Bee](#): > > another update which has issues? It's quite normal, because just a few people did test their **Beta** and **Release Candidate** , so when the firmware becomes "Stable" it wasn't tested enough. ---
**Author:** ![hecatae](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/hecatae/32/20467_2.png) [@hecatae](https://forum.gl-inet.com/u/hecatae)\ **Post date:** [December 16, 2024, 11:50pm UTC](https://forum.gl-inet.com/t/gl-mt2500-upgrade-from-4-6-8-to-4-7-0-fails/51912/10 "2024-12-16T23:50:49Z")
I agree, GL need a testing beta firmware, a stable firmware and a long term support firmware. ---
**Author:** ![hecatae](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/hecatae/32/20467_2.png) [@hecatae](https://forum.gl-inet.com/u/hecatae)\ **Post date:** [December 17, 2024, 3:02pm UTC](https://forum.gl-inet.com/t/gl-mt2500-upgrade-from-4-6-8-to-4-7-0-fails/51912/11 "2024-12-17T15:02:10Z")
I could but I'm going to wait for GL response before I manually start changing key system files. ---
**Author:** ![hecatae](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/hecatae/32/20467_2.png) [@hecatae](https://forum.gl-inet.com/u/hecatae)\ **Post date:** [December 20, 2024, 12:35pm UTC](https://forum.gl-inet.com/t/gl-mt2500-upgrade-from-4-6-8-to-4-7-0-fails/51912/13 "2024-12-20T12:35:24Z")
> [@berx](#): > > 30\_uboot-envtools adding that folder and script and running it has done nothing. ---
**Author:** ![packetmonkey](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/packetmonkey/32/16711_2.png) [@packetmonkey](https://forum.gl-inet.com/u/packetmonkey)\ **Post date:** [December 20, 2024, 4:15pm UTC](https://forum.gl-inet.com/t/gl-mt2500-upgrade-from-4-6-8-to-4-7-0-fails/51912/14 "2024-12-20T16:15:02Z")
Just another data point, I "upgraded" my Brume2 last night from 4.6.8 to 4.7.0 and it is bricked now. Light stays on blue solid after flashing a couple of times when I first power it on. No response from any IPs I tested, 192.168.1, .8, .9, either port. Also a note - I have it connected only via WAN port typically, so the security defaults to disable WAN access would have caused me an issue anyway - leading me to plug into the LAN port to try to re-enable those settings - but LAN port is not working obviously. Luckily I have a backup of the wireguard server config file to help with recovery. everything else is easy to recover manually. Edited to add: LED turns on blue, then off, then solid blue. Only 1 flash on startup. ---
**Author:** ![hecatae](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/hecatae/32/20467_2.png) [@hecatae](https://forum.gl-inet.com/u/hecatae)\ **Post date:** [December 20, 2024, 6:14pm UTC](https://forum.gl-inet.com/t/gl-mt2500-upgrade-from-4-6-8-to-4-7-0-fails/51912/15 "2024-12-20T18:14:11Z")
@bruce shall I try uboot recovery mode or could I end up like @packetmonkey ? ---
**Author:** ![packetmonkey](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/packetmonkey/32/16711_2.png) [@packetmonkey](https://forum.gl-inet.com/u/packetmonkey)\ **Post date:** [December 20, 2024, 6:58pm UTC](https://forum.gl-inet.com/t/gl-mt2500-upgrade-from-4-6-8-to-4-7-0-fails/51912/16 "2024-12-20T18:58:13Z")
I was able to uboot my device and I am up and running on 4.7.0. I am still working through recovery. Just wanted to close the loop. Note, though, the uboot update process did not like Firefox for me, but switching to Edge it worked fine. ---
**Author:** ![berx](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/berx/32/22460_2.png) [@berx](https://forum.gl-inet.com/u/berx)\ **Post date:** [December 20, 2024, 8:06pm UTC](https://forum.gl-inet.com/t/gl-mt2500-upgrade-from-4-6-8-to-4-7-0-fails/51912/17 "2024-12-20T20:06:15Z")
from all I understand you need some reasonable value in `/etc/fw_env.config` or `/etc/config/ubootenv` - otherwise `30_uboot-envtools` also is missing its starting point. But it helped me **guess** what the proper content might be. ---
**Author:** ![bruce](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bruce/32/35649_2.png) [@bruce](https://forum.gl-inet.com/u/bruce)\ **Post date:** [December 23, 2024, 10:36am UTC](https://forum.gl-inet.com/t/gl-mt2500-upgrade-from-4-6-8-to-4-7-0-fails/51912/18 "2024-12-23T10:36:56Z")
🤔 the R&D are checking about this. ---
**Author:** ![hecatae](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/hecatae/32/20467_2.png) [@hecatae](https://forum.gl-inet.com/u/hecatae)\ **Post date:** [December 23, 2024, 3:26pm UTC](https://forum.gl-inet.com/t/gl-mt2500-upgrade-from-4-6-8-to-4-7-0-fails/51912/19 "2024-12-23T15:26:25Z")
Thank you for the update, tried 4.6.10 as well, cannot upgrade to this either. If R&D want access over Goodcloud drop me a message. ---
**Author:** ![Thomasshawn](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/t/e0b2c6/32.png) [@Thomasshawn](https://forum.gl-inet.com/u/Thomasshawn)\ **Post date:** [January 18, 2025, 12:42am UTC](https://forum.gl-inet.com/t/gl-mt2500-upgrade-from-4-6-8-to-4-7-0-fails/51912/20 "2025-01-18T00:42:45Z")
it's been a good while what is the status? i still cannot update my mt3000 unit 4.68 to 4.70 ---
**Author:** ![hecatae](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/hecatae/32/20467_2.png) [@hecatae](https://forum.gl-inet.com/u/hecatae)\ **Post date:** [January 18, 2025, 10:42am UTC](https://forum.gl-inet.com/t/gl-mt2500-upgrade-from-4-6-8-to-4-7-0-fails/51912/21 "2025-01-18T10:42:23Z")
Same here, I'm about to replace my Brume 2 with a Brume W as at least that's not got this issue. ---
**Author:** ![berx](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/berx/32/22460_2.png) [@berx](https://forum.gl-inet.com/u/berx)\ **Post date:** [January 18, 2025, 7:09pm UTC](https://forum.gl-inet.com/t/gl-mt2500-upgrade-from-4-6-8-to-4-7-0-fails/51912/22 "2025-01-18T19:09:13Z")
Hi @Thomasshawn , as you seem to struggle with your MT3000 - did you try follow my path which I documented here? > [@GL-MT3000 upgrade from 4.6.8 to 4.7.0 fails](https://forum.gl-inet.com/t/gl-mt3000-upgrade-from-4-6-8-to-4-7-0-fails/51817): > > I'm using my GL-MT3000 as a wifi repeater. right now it is on Version 4.6.8 and at every login it suggests to upgrade to 4.7.0. The download & verification seems fine - the device reboots but it stays on 4.6.8. I also tried downloaded FW openwrt-mt3000-4.7.0-1205-1733363917.tar and even openwrt-mt3000-4.6.9-1030-1730284273.tar - still the same effect. In case it's required I have bound my device in GoodCloud already. A hint how/where to find the upgrade log is very appreciated. If you struggle at any point, please create a new thread and tag me - so we can discuss your experience without any interference to others threads. ---
**Author:** ![Thomasshawn](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/t/e0b2c6/32.png) [@Thomasshawn](https://forum.gl-inet.com/u/Thomasshawn)\ **Post date:** [January 19, 2025, 12:42am UTC](https://forum.gl-inet.com/t/gl-mt2500-upgrade-from-4-6-8-to-4-7-0-fails/51912/23 "2025-01-19T00:42:55Z")
That's quite a bit of work for what should be an pretty simple update. I think I'll wait till they get it resolved. ---
**Author:** ![berx](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/berx/32/22460_2.png) [@berx](https://forum.gl-inet.com/u/berx)\ **Post date:** [January 19, 2025, 8:30am UTC](https://forum.gl-inet.com/t/gl-mt2500-upgrade-from-4-6-8-to-4-7-0-fails/51912/24 "2025-01-19T08:30:20Z")
> [@Thomasshawn](#): > > I think I'll wait till they get it resolved. From all I understand, the problem is not in the update but in `sysupgrade` (more specific in the checks it does to ensure the system is safe to upgrade). This means there is a change to your current installation required, but the tool to do this change fails. Kind of a vicious cycle. I'm interested if GL·Inet comes to similar conclusions. You always can use this method: **DO NOT use FIREFOX.** > **[Debrick via Uboot - GL.iNet Router Docs 4](https://docs.gl-inet.com/router/en/4/faq/debrick/)** > > Documentation for GL.iNet Router Productions [Next page](https://forum.gl-inet.com/t/gl-mt2500-upgrade-from-4-6-8-to-4-7-0-fails/51912.md?page=2)