It appears you are using firmware that is not from the official OpenWrt project.
When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.
Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).
If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.
My method of learning is to establish the departure point with least overall friction. OpenWRT requires config of the cellular modem at the outset. There are a couple of forks that do not require my configuring the modem to use and therefore speed the trial and error process.
I understand you can simplify your work by excluding support for folks running a fork. Ok, I guess I have to wear it.
Switching back to owrt for me to then have to nut out modem config takes me offline.
This forum does not support 3rd party forks. Full stop. We have no way to know what changes have been made to a given fork, and in some cases those changes may be numerous and can materially change the fundamental workings of the system including syntax and so many other things.
It is the responsibility of the vendor/maintainer of those forks to provide support for their users.
We do, of course, happily support official OpenWrt.
FWIW, you can build a custom image of official OpenWrt that contains the necessary packages for extroot so you don't have to worry about configuring your cellular modem prior to perform the extroot process.
Right, but my point is that you can build the image so that everything that you need is ready to go on your device -- no chicken or egg situation to get online. Do this on the firmware selector.
If the fork is somewhat close to Openwrt you could at least copy the relevant part(s) of the config file(s) and (try to) reuse them, in this case the config of the modem.
One would have expected most people to have phones with internet sharing features in 2026, but I guess it's still not the case.
While this is fine as a method it’s a not insubstantial complication given the other things I’m trying to work out (much of the labour involved would also be solved here too with a working backup feature).
I’ll come back to vanilla owrt at some point but right now I think a firmware that connects from go with a clean install’s greater utility for me