[GH-ISSUE #5] QuecDeploy 1.06?

kerem commented

2026-02-27 06:00:12 +03:00

Owner

Originally created by @forzic on GitHub (Jul 27, 2025).
Original GitHub issue: https://github.com/iamromulan/QuecDeploy/issues/5

Hi, is version 1.0.6 planned? With new A04 firmware?

Originally created by @forzic on GitHub (Jul 27, 2025). Original GitHub issue: https://github.com/iamromulan/QuecDeploy/issues/5 Hi, is version 1.0.6 planned? With new A04 firmware?

kerem referenced this issue

2026-02-27 06:00:12 +03:00

[GH-ISSUE #4] New update release RM551 #5

kerem closed this issue

2026-02-27 06:00:12 +03:00

kerem commented

2026-02-27 06:00:12 +03:00

Author

Owner

@bkvargyas commented on GitHub (Jul 29, 2025):

I've noticed that over a period of two weeks on this firmware, there is a slow memory leak. When the usable memory is around 100MB left, 5G speed is decreased significantly. Using T-Mobile Band 41. A reboot restores speed again. Have to do this about every two weeks. Hoping FW A04 may fix this issue.

@bkvargyas commented on GitHub (Jul 29, 2025): I've noticed that over a period of two weeks on this firmware, there is a slow memory leak. When the usable memory is around 100MB left, 5G speed is decreased significantly. Using T-Mobile Band 41. A reboot restores speed again. Have to do this about every two weeks. Hoping FW A04 may fix this issue.

kerem commented

2026-02-27 06:00:12 +03:00

Author

Owner

@forzic commented on GitHub (Jul 29, 2025):

Ho notato che, dopo due settimane di utilizzo di questo firmware, si verifica una lenta perdita di memoria. Quando la memoria utilizzabile è di circa 100 MB, la velocità 5G diminuisce significativamente. Utilizzo la banda 41 di T-Mobile. Un riavvio ripristina la velocità. Bisogna farlo circa ogni due settimane. Spero che il firmware A04 possa risolvere questo problema.

what firmware are you talking about, A02 custom iamromulan?

@forzic commented on GitHub (Jul 29, 2025): > Ho notato che, dopo due settimane di utilizzo di questo firmware, si verifica una lenta perdita di memoria. Quando la memoria utilizzabile è di circa 100 MB, la velocità 5G diminuisce significativamente. Utilizzo la banda 41 di T-Mobile. Un riavvio ripristina la velocità. Bisogna farlo circa ogni due settimane. Spero che il firmware A04 possa risolvere questo problema. what firmware are you talking about, A02 custom iamromulan?

kerem commented

2026-02-27 06:00:12 +03:00

Author

Owner

@bkvargyas commented on GitHub (Jul 29, 2025):

The current firmware released for 551E-GL, My understanding there is a new update for it. However, the memory leak issue may be related to OpenWRT, not the radio firmware. Either way, it doesn't appear to be stable beyond two weeks and requires a reboot.

@bkvargyas commented on GitHub (Jul 29, 2025): The current firmware released for 551E-GL, My understanding there is a new update for it. However, the memory leak issue may be related to OpenWRT, not the radio firmware. Either way, it doesn't appear to be stable beyond two weeks and requires a reboot.

kerem commented

2026-02-27 06:00:12 +03:00

Author

Owner

@iamromulan commented on GitHub (Jul 31, 2025):

The current firmware released for 551E-GL, My understanding there is a new update for it. However, the memory leak issue may be related to OpenWRT, not the radio firmware. Either way, it doesn't appear to be stable beyond two weeks and requires a reboot.

You experience the memory leak on A02, A03, or A04?

@iamromulan commented on GitHub (Jul 31, 2025): > The current firmware released for 551E-GL, My understanding there is a new update for it. However, the memory leak issue may be related to OpenWRT, not the radio firmware. Either way, it doesn't appear to be stable beyond two weeks and requires a reboot. You experience the memory leak on A02, A03, or A04?

kerem commented

2026-02-27 06:00:12 +03:00

Author

Owner

@iamromulan commented on GitHub (Jul 31, 2025):

Hi, is version 1.0.6 planned? With new A04 firmware?

Yes. I should probably test A04 first though 🤣
Been super busy with stuff.
Hopefully 1.0.6 will have a new custom firmware based off of A04 and a new custom 520 firmware as well. I've been hard at work creating an overlayed OpenWRT subsystem on sdxlemur. 😁

@iamromulan commented on GitHub (Jul 31, 2025): > Hi, is version 1.0.6 planned? With new A04 firmware? Yes. I should probably test A04 first though 🤣 Been super busy with stuff. Hopefully 1.0.6 will have a new custom firmware based off of A04 and a new custom 520 firmware as well. I've been hard at work creating an overlayed OpenWRT subsystem on sdxlemur. 😁

kerem commented

2026-02-27 06:00:12 +03:00

Author

Owner

@forzic commented on GitHub (Jul 31, 2025):

Ciao, è prevista la versione 1.0.6? Con il nuovo firmware A04?

Sì. Probabilmente dovrei prima testare A04 🤣 Sono stato super impegnato con delle cose. Spero che la versione 1.0.6 abbia un nuovo firmware personalizzato basato su A04 e anche un nuovo firmware 520 personalizzato. Ho lavorato duramente per creare un sottosistema OpenWRT overlay su sdxlemur. 😁

Thanks number one

@forzic commented on GitHub (Jul 31, 2025): > > Ciao, è prevista la versione 1.0.6? Con il nuovo firmware A04? > > Sì. Probabilmente dovrei prima testare A04 🤣 Sono stato super impegnato con delle cose. Spero che la versione 1.0.6 abbia un nuovo firmware personalizzato basato su A04 e anche un nuovo firmware 520 personalizzato. Ho lavorato duramente per creare un sottosistema OpenWRT overlay su sdxlemur. 😁 Thanks number one

kerem commented

2026-02-27 06:00:12 +03:00

Author

Owner

@bkvargyas commented on GitHub (Jul 31, 2025):

The current firmware released for 551E-GL, My understanding there is a new update for it. However, the memory leak issue may be related to OpenWRT, not the radio firmware. Either way, it doesn't appear to be stable beyond two weeks and requires a reboot.

You experience the memory leak on A02, A03, or A04?

A02, Your Custom Firmware: [RM551EGL00AAR01A02M8G_iamromulan_basic_eth (2025-4-21]

Also, please incorporate the 4CA fix (if needed in A04) for TMO, or maybe an easy on-modem script that can be run...

@bkvargyas commented on GitHub (Jul 31, 2025): > > The current firmware released for 551E-GL, My understanding there is a new update for it. However, the memory leak issue may be related to OpenWRT, not the radio firmware. Either way, it doesn't appear to be stable beyond two weeks and requires a reboot. > > You experience the memory leak on A02, A03, or A04? A02, Your Custom Firmware: [RM551EGL00AAR01A02M8G_iamromulan_basic_eth (2025-4-21] Also, please incorporate the 4CA fix (if needed in A04) for TMO, or maybe an easy on-modem script that can be run...

kerem commented

2026-02-27 06:00:12 +03:00

Author

Owner

@forzic commented on GitHub (Jul 31, 2025):

Is there a guide on how to install the 4CA patch?

@forzic commented on GitHub (Jul 31, 2025): Is there a guide on how to install the 4CA patch?

kerem commented

2026-02-27 06:00:12 +03:00

Author

Owner

@bkvargyas commented on GitHub (Aug 1, 2025):

Is there a guide on how to install the 4CA patch?

https://www.reddit.com/r/tmobileisp/comments/1k3tvj2/sdx75_rm551e_users_anyone_getting_4xca_without/

@bkvargyas commented on GitHub (Aug 1, 2025): > Is there a guide on how to install the 4CA patch? https://www.reddit.com/r/tmobileisp/comments/1k3tvj2/sdx75_rm551e_users_anyone_getting_4xca_without/

kerem commented

2026-02-27 06:00:12 +03:00

Author

Owner

@bkvargyas commented on GitHub (Aug 1, 2025):

I should note, I've been having "TCP Reset" issues on this release, and randomly I'll loose my TCP connection and it will re-establish. I've recently gone back to a T-Mobile Home Router device within the last couple of days, and all my TCP issues are gone. So something is going on with memory usage and TCP Session reset's with the built in OpenWRT image. I have not tried to just image the device with a non-openwrt firmware to see if it's related to OpenWRT or the Firmware directly. Unfortunately, I don't have a lot of debugging time these days, so until Iamromulan has time to upload a new firmware, I'll continue with my t-mobile router. I have 4 RM551E-GL modules to build and deploy once we get a stable release working.

@bkvargyas commented on GitHub (Aug 1, 2025): I should note, I've been having "TCP Reset" issues on this release, and randomly I'll loose my TCP connection and it will re-establish. I've recently gone back to a T-Mobile Home Router device within the last couple of days, and all my TCP issues are gone. So something is going on with memory usage and TCP Session reset's with the built in OpenWRT image. I have not tried to just image the device with a non-openwrt firmware to see if it's related to OpenWRT or the Firmware directly. Unfortunately, I don't have a lot of debugging time these days, so until Iamromulan has time to upload a new firmware, I'll continue with my t-mobile router. I have 4 RM551E-GL modules to build and deploy once we get a stable release working.

kerem commented

2026-02-27 06:00:12 +03:00

Author

Owner

@iamromulan commented on GitHub (Aug 1, 2025):

It's on the wiki lol

https://github.com/iamromulan/cellular-modem-wiki/blob/main/quectel/sdxpinn/T-Mobile_RM551EGL_patches.md

By the way, A04 testing so far so good.

4xCA working on default T-Mobile MBN

4xCA working on ROW_Commercial on some towers no need for patch. I just added the first NV file mentioned in the above guide only and then rebooted and got 4xCA on a tower that was 3xCA without. More testing in progress.

Btw even though A04 isn't in QuecDeploy yet you can still download it from my mega. It's linked on the front page of the wiki lol

@iamromulan commented on GitHub (Aug 1, 2025): It's on the wiki lol https://github.com/iamromulan/cellular-modem-wiki/blob/main/quectel/sdxpinn/T-Mobile_RM551EGL_patches.md By the way, A04 testing so far so good. 4xCA working on default T-Mobile MBN 4xCA working on ROW_Commercial on some towers no need for patch. I just added the first NV file mentioned in the above guide only and then rebooted and got 4xCA on a tower that was 3xCA without. More testing in progress. Btw even though A04 isn't in QuecDeploy yet you can still download it from my mega. It's linked on the front page of the wiki lol

kerem commented

2026-02-27 06:00:12 +03:00

Author

Owner

@bkvargyas commented on GitHub (Aug 1, 2025):

Totally missed that document in your wiki! --- The A04 image in Mega, is that a factory image or one with OpenWRT installed inside set to ethernet mode? It looks like once A04 is deployed, we loose the ability to get back into the module to put the OpenWRT image back in I assume?

@bkvargyas commented on GitHub (Aug 1, 2025): Totally missed that document in your wiki! --- The A04 image in Mega, is that a factory image or one with OpenWRT installed inside set to ethernet mode? It looks like once A04 is deployed, we loose the ability to get back into the module to put the OpenWRT image back in I assume?

kerem commented

2026-02-27 06:00:12 +03:00

Author

Owner

@iamromulan commented on GitHub (Aug 1, 2025):

Totally missed that document in your wiki! --- The A04 image in Mega, is that a factory image or one with OpenWRT installed inside set to ethernet mode? It looks like once A04 is deployed, we loose the ability to get back into the module to put the OpenWRT image back in I assume?

All 551 firmware is OpenWRT

The RM551E-GL runs an OpenWRT system with an Android kernel. There are no non-OpenWRT versions. From factory though the init scripts that start the built in Webserver uhttpd that serves Luci was missing along with the script that starts the built in ssh server dropbear.

You can still run the toolkit script from the SDXPINN branch to deploy my edits via ADB on any factory firmware including this new one.

@iamromulan commented on GitHub (Aug 1, 2025): > Totally missed that document in your wiki! --- The A04 image in Mega, is that a factory image or one with OpenWRT installed inside set to ethernet mode? It looks like once A04 is deployed, we loose the ability to get back into the module to put the OpenWRT image back in I assume? All 551 firmware is OpenWRT The RM551E-GL runs an OpenWRT system with an Android kernel. There are no non-OpenWRT versions. From factory though the init scripts that start the built in Webserver uhttpd that serves Luci was missing along with the script that starts the built in ssh server dropbear. You can still run the toolkit script from the SDXPINN branch to deploy my edits via ADB on any factory firmware including this new one.

kerem commented

2026-02-27 06:00:12 +03:00

Author

Owner

@bkvargyas commented on GitHub (Aug 1, 2025):

Totally missed that document in your wiki! --- The A04 image in Mega, is that a factory image or one with OpenWRT installed inside set to ethernet mode? It looks like once A04 is deployed, we loose the ability to get back into the module to put the OpenWRT image back in I assume?

All 551 firmware is OpenWRT

Assumed the 551 was like the 520N, but I guess I was wrong.

You can still run the toolkit script from the SDXPINN branch to deploy my edits via ADB on any factory firmware including this new one.

Can you build a new A04 image with your edits included or is the one on your mega already include those edits? Or is this planned, and if so, I'll just wait.

@bkvargyas commented on GitHub (Aug 1, 2025): > > Totally missed that document in your wiki! --- The A04 image in Mega, is that a factory image or one with OpenWRT installed inside set to ethernet mode? It looks like once A04 is deployed, we loose the ability to get back into the module to put the OpenWRT image back in I assume? > > All 551 firmware is OpenWRT Assumed the 551 was like the 520N, but I guess I was wrong. > You can still run the toolkit script from the SDXPINN branch to deploy my edits via ADB on any factory firmware including this new one. Can you build a new A04 image with your edits included or is the one on your mega already include those edits? Or is this planned, and if so, I'll just wait.

kerem commented

2026-02-27 06:00:13 +03:00

Author

Owner

@iamromulan commented on GitHub (Aug 1, 2025):

Totally missed that document in your wiki! --- The A04 image in Mega, is that a factory image or one with OpenWRT installed inside set to ethernet mode? It looks like once A04 is deployed, we loose the ability to get back into the module to put the OpenWRT image back in I assume?

All 551 firmware is OpenWRT

Assumed the 551 was like the 520N, but I guess I was wrong.

You can still run the toolkit script from the SDXPINN branch to deploy my edits via ADB on any factory firmware including this new one.

Can you build a new A04 image with your edits included or is the one on your mega already include those edits? Or is this planned, and if so, I'll just wait.

Just flashed stock A04 today and deployed everything via my toolkit script. I plan to release a modified version but I want to make sure it's at least better than A02 first.

@iamromulan commented on GitHub (Aug 1, 2025): > > > Totally missed that document in your wiki! --- The A04 image in Mega, is that a factory image or one with OpenWRT installed inside set to ethernet mode? It looks like once A04 is deployed, we loose the ability to get back into the module to put the OpenWRT image back in I assume? > > > > All 551 firmware is OpenWRT > > Assumed the 551 was like the 520N, but I guess I was wrong. > > > You can still run the toolkit script from the SDXPINN branch to deploy my edits via ADB on any factory firmware including this new one. > > Can you build a new A04 image with your edits included or is the one on your mega already include those edits? Or is this planned, and if so, I'll just wait. > > Just flashed stock A04 today and deployed everything via my toolkit script. I plan to release a modified version but I want to make sure it's at least better than A02 first.

kerem commented

2026-02-27 06:00:13 +03:00

Author

Owner

@forzic commented on GitHub (Aug 1, 2025):

Mi è sfuggito completamente quel documento nel tuo wiki! --- L'immagine A04 in Mega, è un'immagine di fabbrica o una con OpenWRT installato all'interno e impostato in modalità Ethernet? Sembra che una volta implementato A04, perdiamo la possibilità di tornare al modulo per reinserire l'immagine OpenWRT, suppongo?

Tutti i firmware 551 sono OpenWRT

Ho dato per scontato che il 551 fosse come il 520N, ma credo di sbagliarmi.

Puoi comunque eseguire lo script del toolkit dal ramo SDXPINN per distribuire le mie modifiche tramite ADB su qualsiasi firmware di fabbrica, incluso questo nuovo.

Puoi creare una nuova immagine A04 con le tue modifiche incluse o quella sul tuo mega include già quelle modifiche? Oppure è in programma, e in tal caso, aspetterò.

Ho appena installato la versione stock A04 oggi e ho distribuito tutto tramite il mio script del toolkit. Ho intenzione di rilasciare una versione modificata, ma prima voglio assicurarmi che sia almeno migliore della A02.

When do you plan to release the new A04 custom?

@forzic commented on GitHub (Aug 1, 2025): > > > > Mi è sfuggito completamente quel documento nel tuo wiki! --- L'immagine A04 in Mega, è un'immagine di fabbrica o una con OpenWRT installato all'interno e impostato in modalità Ethernet? Sembra che una volta implementato A04, perdiamo la possibilità di tornare al modulo per reinserire l'immagine OpenWRT, suppongo? > > > > > > > > > Tutti i firmware 551 sono OpenWRT > > > > > > Ho dato per scontato che il 551 fosse come il 520N, ma credo di sbagliarmi. > > > Puoi comunque eseguire lo script del toolkit dal ramo SDXPINN per distribuire le mie modifiche tramite ADB su qualsiasi firmware di fabbrica, incluso questo nuovo. > > > > > > Puoi creare una nuova immagine A04 con le tue modifiche incluse o quella sul tuo mega include già quelle modifiche? Oppure è in programma, e in tal caso, aspetterò. > > Ho appena installato la versione stock A04 oggi e ho distribuito tutto tramite il mio script del toolkit. Ho intenzione di rilasciare una versione modificata, ma prima voglio assicurarmi che sia almeno migliore della A02. When do you plan to release the new A04 custom?

kerem commented

2026-02-27 06:00:13 +03:00

Author

Owner

@iamromulan commented on GitHub (Aug 1, 2025):

Mi è sfuggito completamente quel documento nel tuo wiki! --- L'immagine A04 in Mega, è un'immagine di fabbrica o una con OpenWRT installato all'interno e impostato in modalità Ethernet? Sembra che una volta implementato A04, perdiamo la possibilità di tornare al modulo per reinserire l'immagine OpenWRT, suppongo?

Tutti i firmware 551 sono OpenWRT

Ho dato per scontato che il 551 fosse come il 520N, ma credo di sbagliarmi.

Puoi comunque eseguire lo script del toolkit dal ramo SDXPINN per distribuire le mie modifiche tramite ADB su qualsiasi firmware di fabbrica, incluso questo nuovo.

Puoi creare una nuova immagine A04 con le tue modifiche incluse o quella sul tuo mega include già quelle modifiche? Oppure è in programma, e in tal caso, aspetterò.

Ho appena installato la versione stock A04 oggi e ho distribuito tutto tramite il mio script del toolkit. Ho intenzione di rilasciare una versione modificata, ma prima voglio assicurarmi che sia almeno migliore della A02.

When do you plan to release the new A04 custom?

Well, I could in theory release one pretty quick. However, I haven't long term tested the base firmware yet so I don't know what little fixes to add that would be beneficial yet. I'll try to have one out today or tomorrow but we'll see.

@iamromulan commented on GitHub (Aug 1, 2025): > > > > > Mi è sfuggito completamente quel documento nel tuo wiki! --- L'immagine A04 in Mega, è un'immagine di fabbrica o una con OpenWRT installato all'interno e impostato in modalità Ethernet? Sembra che una volta implementato A04, perdiamo la possibilità di tornare al modulo per reinserire l'immagine OpenWRT, suppongo? > > > > > > > > > > > > Tutti i firmware 551 sono OpenWRT > > > > > > > > > Ho dato per scontato che il 551 fosse come il 520N, ma credo di sbagliarmi. > > > > Puoi comunque eseguire lo script del toolkit dal ramo SDXPINN per distribuire le mie modifiche tramite ADB su qualsiasi firmware di fabbrica, incluso questo nuovo. > > > > > > > > > Puoi creare una nuova immagine A04 con le tue modifiche incluse o quella sul tuo mega include già quelle modifiche? Oppure è in programma, e in tal caso, aspetterò. > > > > Ho appena installato la versione stock A04 oggi e ho distribuito tutto tramite il mio script del toolkit. Ho intenzione di rilasciare una versione modificata, ma prima voglio assicurarmi che sia almeno migliore della A02. > > When do you plan to release the new A04 custom? Well, I could in theory release one pretty quick. However, I haven't long term tested the base firmware yet so I don't know what little fixes to add that would be beneficial yet. I'll try to have one out today or tomorrow but we'll see.

kerem commented

2026-02-27 06:00:13 +03:00

Author

Owner

@iamromulan commented on GitHub (Aug 2, 2025):

Ok here it is, enjoy.

https://mega.nz/file/nAtHiIBY#BaAgvPXRDcdnpMXq0To6OBkzLwdehGLmih7N7dbFFXo

@iamromulan commented on GitHub (Aug 2, 2025): Ok here it is, enjoy. https://mega.nz/file/nAtHiIBY#BaAgvPXRDcdnpMXq0To6OBkzLwdehGLmih7N7dbFFXo

kerem commented

2026-02-27 06:00:13 +03:00

Author

Owner

@bkvargyas commented on GitHub (Aug 4, 2025):

Ok here it is, enjoy.

https://mega.nz/file/nAtHiIBY#BaAgvPXRDcdnpMXq0To6OBkzLwdehGLmih7N7dbFFXo

Installed and running, thanks! Cannot get the package sdxpinn-quecmanager-beta or non-beta version to work on this version. It looks like it installs, but the GUI never comes up after a reboot.

Brian

@bkvargyas commented on GitHub (Aug 4, 2025): > Ok here it is, enjoy. > > https://mega.nz/file/nAtHiIBY#BaAgvPXRDcdnpMXq0To6OBkzLwdehGLmih7N7dbFFXo Installed and running, thanks! Cannot get the package sdxpinn-quecmanager-beta or non-beta version to work on this version. It looks like it installs, but the GUI never comes up after a reboot. Brian

kerem commented

2026-02-27 06:00:13 +03:00

Author

Owner

@iamromulan commented on GitHub (Sep 21, 2025):

1.0.6 release imminent. Stand-by.
Issue closed.

@iamromulan commented on GitHub (Sep 21, 2025): 1.0.6 release imminent. Stand-by. Issue closed.

kerem commented

2026-02-27 06:00:13 +03:00

Author

Owner

@forzic commented on GitHub (Sep 21, 2025):

I am confidently awaiting the video upgrade to version R02 because in my case it is complicated thanks to the work done iamromulan....

@forzic commented on GitHub (Sep 21, 2025): I am confidently awaiting the video upgrade to version R02 because in my case it is complicated thanks to the work done iamromulan....

Rows
Columns

[GH-ISSUE #5] QuecDeploy 1.06? #4