Hello
I have a hAP ax lite LTE6 with 7.18.2 with 16121.1034.00.01.01.08
worked perfectly

I upgraded the firmware, to the 16121.1034.00.01.01.09 and the LTE dont work.
no packets received on the interface. dead.

can someone point me to the release 16121.1034.00.01.01.08?

thank you

I'd confirm it works with 7.19beta if you can before downgrading the firmware. Sometime these firmware bugs are carrier-specific, and if 7.19 did not work with ...1.09 firmware, it be good to report that to Mikrotik.

I think this post has the instructions to download using the manual-upgrade:
viewtopic.php?t=201412#p1035322

(which I think is the same modem, if not you have to change the modem type in url)

Also I'd make sure you're running the latest RouterBOARD firmware (/system/routerboard/upgrade) so it matches the release 7.18.2.

When version don't align that sometimes is the cause of LTE failures. Now the LTE firmware sometimes does have some implicit/un-enforced "minimum version" of both RouterOS and RouterBOOT, thus the suggestion to try the "testing" channel to know if it "just" versions not match & NOT a bug (which is also possible).

Hello, thank you for your prompt reply.
The unit was working flawlessy with 7.18.2 and the firmare 08.
Just before shipping the unit we upgraded the lte firmware. The upgrade went fine, but after that no incoming traffic anymore.
the LTE gest an IP address, but 0 incoming traffic.
I have tried with the link in the other post page but returns error 404.

/tool fetch https://upgrade.mikrotik.com/firmware/F ... 1.08/image

status failed
fetch error 404

Seemingly working 3 and 5:
https://upgrade.mikrotik.com/firmware/F ... 1.03/image
https://upgrade.mikrotik.com/firmware/F ... 1.05/image

4,6,7,8 and 9 are seemingly missing.

Seemingly working 3 and 5:
https://upgrade.mikrotik.com/firmware/F ... 1.03/image
https://upgrade.mikrotik.com/firmware/F ... 1.05/image

4,6,7,8 and 9 are seemingly missing.

exactly I have seen too that the release 3 is working but other are not working.
I have taken out another HAP AX LTE with a .8 firmware and it works perfectly with the very same basic configuration.
The .9 is not working. I tried updating to the latest beta with no resolution of the issue.
At the moment I have a non working LTE product.

exactly I have seen too that the release 3 is working but other are not working.
[...]
The .9 is not working. I tried updating to the latest beta with no resolution of the issue.

Do firmware upgrades of the LTE radio always get downloaded from the internet?

If yes, is it still possible for someone to upgrade to .9 even now?

If both are yes, then logically the .9 must be available on some public URL *somewhere*, otherwise it would not be possible to still upgrade to it. It's just a matter of discovering what that URL is. And if .9 is available, .8 is probably also available, and the issue is just the same: we simply don't know the correct URL.

If firmwares are also bundled in with RouterOS itself, then it's possible .8 and .9 are not available via public download and .9 is only getting distributed within RouterOS. If that's the case, it might be possible to find an older version of RouterOS that contained .8 and extract the firmware file from it.

There was some discussion of the scheme here:
viewtopic.php?t=198168#p1031333

...which implies it a diff upgrade scheme, but IDK.

I'd imagine trying the 7.19beta8 be easier to see if that works with .09 & be easier than trying unwind how the download works. The URL download scheme looks more complex than past modems, upgrading take a few a minutes. A lot of times the newer firmware requires something in RouterOS (and/or RouterBOOT), so that may be an alternative solution (if 7.19beta worked) & if it did NOT work, then there is bug.

There was some discussion of the scheme here:

Binary diffs?? Oooof.

If true, and if the only two files that are made available are the last full-flash release + the diff between that base version and the most recent version, then it would suggest that the only two choices that likely remain would be to stick with 09, or to go all the way back to 05.

I'm not actually sure what's going on, though, or if the description from that thread is an accurate analysis of the situation, because if I try to grab 'latest' file from any valid subdirectory, it simply contains a version string within it. There's no actual binary data inside. What is even weirder is that /latest underneath the .05 subdirectory contains the string "16121.1034.00.01.01.04", which is identical to the /latest file from the .03 subdirectory. The .01 subdirectory's /latest says ".03".

Also, I had come away with the impression that OP had tried upgrading to 7.19beta, but re-reading things, it appears this isn't the case (or at least OP never actually said it).

Okay, I found the answer to why the "latest" file in the .05 directory returns ".04" in the contents, over in this thread.

You can read about how people had problems after upgrading to .05. They tried to downgrade themselves, but weren't able to...every image file they grabbed from the public URL and re-flashed did not cause the firmware version on their LTE modem to budge. It stayed at .05.

At one point, MT manually remotely downgraded somebody's modem who opened a ticket with them about this issue. It fixed their problem.

After that, MT pulled the .05 upgrade. The .05 subdirectory was created, which actually points to an image file that downgrades back to .04. This allowed anybody who had been bitten by the buggy .05 release to downgrade back to .04 using the normal means, rather than opening individual tickets with MT.

Based on this, I can surmise that...

• ...at least for modem model FG621-EA, the URL scheme for updates is /firmware/<model>/<current-version> (where <current-version> is the version that the modem is already running, NOT the most recent "current" version for download!)
• ...underneath /<current-version>, the "latest" file contains the version # of the image file that your modem will be upgraded TO
• ...and the "image" file contains the actual firmware that matches the version # contained within "latest"

So, ROS checks current running firmware, then tries to fetch /firmware/FG621-EA/<current-version>/latest. If this file exists, then it means there is an update FROM <current-version> TO whatever is in "latest". At this point, it pops up the "LTE Firmware Check" window showing you "Installed Version" (what I've been calling <current-version>) and "Latest Version" (the version number of the next upgrade available to your modem at /firmware/<model>/<current-version>/image, which it learned from /latest).

This would mean that *IF* /FG621-EA/16121.1034.00.01.01.08 existed, it would actually likely contain the update to .09 within it, not the image for .08. You would need to find the directory for the previous published version (.07 or possibly lower) in order to actually obtain the .08 image file.

That nothing past /FG621-EA/16121.1034.00.01.01.05/* seems to exist suggests that the URL schema must have changed at some point. And we still don't know what the new schema is.

I went ahead and checked Internet Archive / Wayback Machine, and they do have a copy of 16121.1034.00.01.01.05/image stored on their servers that was grabbed back in August 2024. Unfortunately, it appears that it has been truncated by about 16KB. However, from the bulk of it that I have been able to download, if I compare it to what is currently located at 16121.1034.00.01.01.05/image today, it is byte-for-byte identical. So they aren't simply changing/replacing that file in that directory with newer versions all the time.

EDIT: Found this interesting page which specifically states that the FG621-EA firmware cannot be downgraded to an earlier version, implying that this is so even if you retained a copy of an older image file that you had used to upgrade it to that same version in the past. I don't know if they got this info directly from MT or what, but it rather fits with what the other post you linked to hypothesizes about binary diffs/"deltas", and indeed what the structure of the image file seems to suggest. My guess is that when .05 proved to be buggy and MT pulled it, what they did was prepare a special downgrade "patch" image that will take a modem running .05 and patch it back to .04. This is likely only possible to do if such a specifically-prepared downgrade image is made by MT themselves. So if .09 is also buggy and somebody needs to downgrade to .08 again, it's probably going to take MT's involvement/intervention to make that happen. Honestly, this is a very crappy system and would discourage me from EVER updating my modem firmware, especially given the high rate of showstopping bugs that it seems like are constantly getting introduced in updates...why take the chance? You should ALWAYS be allowed to downgrade things, especially if the vendor has proven time and time again that they cannot be trusted to do proper Q/A.

I have found why it didnt work.
The coincidence was that that day the internet connection option expired on the sim.
The collegue forgot to renew it and the RB didnt connect again.
now it works flawlessy. False alarm, just a pure coincidence.