[GL-MT6000 / Flint 2] Bricked (GPT Corruption?) & Physically Obstructed UART (2026 EU Model) - Seeking Web UI Recovery Files

Router
1

Hello everyone,

I am writing to share my experience trying to recover a bricked GL-MT6000 (Flint 2) and to seek assistance from the GL.iNet support team.

I recently bricked my Flint2 router after some partition operation that was not well planned. The device is now unresponsive to standard recovery methods. I can access the U-Boot Web UI by connecting my Ethernet cable to Port #3 (LAN2). However, recovery via uploading relevant file from GLi.NET via this option, fails

My next step was Serial Console Recovery via the UART pins. However, upon opening my unit (purchased in Germany in February 2026), I found that the UART pins are practically inaccessible, obstructed by plastic channels/cable guides glued or placed directly over the area with no easy way to dismantle.

I am curious about why this is the situation with the pins. I suspect this might possibly be a response to regulatory compliance in Europe which, as a consequence may push manufacturers into this direction to pass regional audits.

Whether this is indeed a regulatory requirement or just a manufacturing revision, I leave open to discussion and I would like to know more. Practically speaking, it means that recovering a bricked Flint 2 via UART is incredibly difficult, if not impossible, for standard users in 2026 without risking physical damage to the board. I do not wish to destructively cut into the board and am reaching my technical limits here.

Request for Help (@GL.iNet Support) I have seen in other threads, such as https://forum.gl-inet.com/t/making-an-mt6000-flint2-router-work-again/61507, that official support can provide specific low-level files like uboot.fip and art partitions to help resolve deep brick scenarios.

However, if flashing those specific files requires an active Serial/UART connection, this method is simply out of my reach due to the physical obstruction. Therefore, my highly preferred and possible only next option is: is it possible to receive a special .bin image or a GPT Dump Image that restores the full eMMC partition structure directly via the U-Boot Web UI? Since my U-Boot web interface is still accessible, a single file that rebuilds the partition map blindly without needing UART access would be a lifesaver.

If this is possible, I can provide my router's MAC address via private Message.

Thank you in advance for your time and support!

2

There might be a way to do this although I think you sit on ice here.

Serial is however the safest approach, but since this router is using a Mediatek chip, there is a certain tooling which can be used to flash back emmc partitions I think.

Please look here:

It requires you first to get into failsafe so that you can run OpenWrts initramfs, which loads OpenWrt purely on the ram so that partitions can be altered.

You also need mtd to write.

Now the question what I'm not so sure about is if this specific emmc layout file can also be flashed with these tools I think uart serial is still needed, I have done this twice for the T-56 which has the same cpu as the Flint 2, but that was the BL2 image, but you talk about the emmc file which often is only something GL-iNet has.

I gonna post this T-56 guide, but I recommend to wait for GL support and also look in if this tool even can help or only cause more damage.

1 Like
3

Hi

Please check your private messages; we have sent you the GPT EMMC file for the MT6000.
This file can be imported into U-Boot.

1 Like
5

Thank you @xize11 I will try with the file shared by GLI-iNET.

1 Like
6

I would follow @will.qiu advise with U-boot, this MTK-uart tool is mostly a hack to work on mtk chips but more tricky than if there is a official way such as U-boot.

2 Likes
7

same problem，send a copy of gpt emmc file to me, thanks a lot

8

Hi,

It has already been sent via private message. Please check.

9

Hello, Piggy backing on this thread: I have also managed to brick my almost new Flint2 while messing with the partitions table and fail to factory restore, and are seeking the uboot.fip and a way to restore partitions table. :folded_hands:

10

Hi,

We have sent it via private message. Please check.

12

same problem，can you send a copy of gpt emmc file to me, thanks a lot

13
14

Hi,

My new Flint 2 has also bricked (trying to add a vlan) and cannot be recovered through uboot.

16

Hi,

Under normal circumstances, configuring a VLAN only changes the network settings and should not damage the GPT or flash partition table.

Could you please clarify why the U-Boot recovery cannot be completed? Are you unable to access the U-Boot Web UI, unable to upload the firmware, or does the device still fail to boot after the firmware is uploaded?

If convenient, please also provide details of the firmware file used for recovery, along with any error messages or LED behavior observed during the process.

Once we receive this information, we will further assist you in determining the appropriate recovery steps.
Thank you for your cooperation.

17

Hi,

The U-Boot menu can be accessed and I am able to upload firmware and update. The process reaches the point of the router trying to restart, but hangs when doing so.

The light continuously flashes blue and the router is inaccessible. I have left it in this state for ~45 minutes with no change to this behaviour.

I have tried this process with both the 4.8.4 and 4.9.0 firmware. I confirmed checksums on each before upload. (The router was on firmware 4.9.0 when the issue first occurred).

Before trying to install firmware through U-Boot, I had attempted power cycling and full factory reset (10 second reset button press). Neither fixed the issue of the router being inaccessible and the light continuously flashing blue.

Thanks for your help

18

Hi,

Any further guidance on this?

Thanks

19

Hi,

Sorry for the delayed reply.

After the U-Boot recovery process is completed, the continuously flashing blue LED may indicate that the router has already started normally.
Could you please change your computer’s Ethernet settings back to obtaining an IP address automatically, reconnect it to LAN 2, LAN 3, or LAN 4, and then check whether it receives a 192.168.8.x address and can access 192.168.8.1 . You may also check whether the router’s default Wi-Fi network appears.

If the router is still inaccessible after these checks, please let us know, and we will send you the GPT recovery file for further testing.

Thank you for your patience and cooperation.

20

Hi Charles,

I was being an idiot and hadn’t cleared the manual network settings correctly after recovery. Thanks for your help :+1:

1 Like