I have a Flint 2 that boots normally and I can flash firmware images without issue. I would like to access uboot mode and I cannot do so. I am using a Win 11 PC (IP address set to 192.168.1.2, 255.255.255.0, 192.168.1.1), and here is the process:
Ethernet on LAN port (port 2), no other cables plugged in
Hold down reset while plugging in power
LED blinks 6 times and then turns solid white
The Flint 2 appears to be in uboot mode, but I cannot connect. Note that I also have a Flint 3 and I run the same procedure and I can connect to uboot and get the GUI to flash an image easily on Flint 3.
What I think what can also be a possibility is that the U-boot has been replaced by OpenWrts version.
^ can you remember if you used normal OpenWrt images with the factory naming?
The factory naming can be misleading to new users, because it may let you assume that it restores factory, but this is not true, in fact it replaces the factories U-boot with its own variant which do not have a web ui but tftp, always use the sysupgrade ones.
If this the case I'm afraid your best bet is using UART serial and ask GL-iNet for the flashing instructions for the fip file and for which offsets are needed, it is unknown to me if doing this over OpenWrts u-boots tftp works I won't advise this because I also read no mention about this on the OpenWrt forums, it needs to be done precise without a process you won't know what it is going to do, it can do much more harm.
Very odd because my other GL.iNet routers (like Flint 3) go into uboot mode easily using the same procedure.
With Flint 2, no ping replies. LEDs look correct and behave correctly for uboot. I do not believe I ever have used a factory upgrade image from OpenWRT. Only sysupgrade images.
But I cannot connect to Flint 2 in uboot. The router does boot normally and I can flash both OpenWRT and GL.iNet images. Any way to force a uboot update from the GUI as the router does boot normally?
Because this is how I used to do it, but I know that this port is a little different connected than the 1gb ports, it was also advised to use lan2 idd in case of negotiation problems but I did not experience this it just did it fine to a 1gb negotiation, if the wiring is a issue and don't fit by cable management you could use a key stone to make a temporary cable re-route.
Tried various ports and does not connect…. Ping does not get replies.. Really strange as the router boots fine and I can flash OpenWRT and GL.iNet images from the GUI. But I cannot reach uboot.
New cable, same problem. What we know is that the Uboot version on my Flint 2 looks to be the original one that came with the router. I can get the Flint 2 router easily in Uboot recovery mode, but cannot connect (192.168.1.2) to Uboot. My Flint 3 connects easily into Uboot recovery, so I believe the process and PC are working fine. Not sure what the issue is with my Flint 2.
For sanity what I would do is try to run a tftp server, and set upload with a sysupgrade image with a version which is not current.
When you do the u-boot process (starting the router) if it is tftp like OpenWrts it will upload it i don't think nmap can be successful because I believe this tftp server is happening before the actual boot,maybe im confusing fail safe mode but I think it is the same, then the tftp is closed.
The best situation would be if you could add a serial connection to it so that you can see the entire boot log.
Edit:
Maybe to be on the safe side try to use the initramfs image by OpenWrt, it is not clear to me if these sysupgrade images cause a brick, most tutorials show the sysupgrade command being used from the initramfs which was instanced via tftp.
