WE826-T2 Kuwfi OEM firmware to GoldenOrb - about to replace firmware
Posted: Fri Aug 14, 2020 2:01 pm
Hello, I have WE836-T2 with the Quectel EP06 Modem currently connecting to AT&T soon to be changed to Verizon. The firmware is the factory OEM firmware as sold to me by Kuwfi. I am told by support at Kuwfi my firmware is upgradeable to one newer version but that it shouldn’t make much difference.
I have had countless issues with this firmware. I would have long ago abandoned the hardware in it’s entirety were it not for these forums exposing to me just how well the WE826 can actually perform if using a modern firmware. I am just about to bite the bullet and write the Golden Orb firmware, but given the routers precarious installation location I wanted to make sure I had the rough steps correct before I try to hit the reset button while balancing on a make shift step.
I am electing to skip the Kuwfi final firmware in favor of going directly to Golden Orb. Will this poses any problems to bypass the OEM and write your firmware immediately? I will not be logging into the Kuwfi firmware at all, as I believe trying to use their “upload firmware” feature is only a recipe for bricking the hardware? If I am correct I must absolutely use the boot loader. Is The boot loader is still an HTTP served set of administrative pages, and not like other firmware where I have had to set up a TFTP server and use Cisco or equivalent commands?
Once I have initially installed Golden Orb will it be okay to use the firmware update feature or perhaps even auto update features within Golden Orb to do future updates? Or is there something unique about the WE826-T2 that mandates using the boot loader from this point forward.
I noticed that it is suggested to static IP the address to the computer I will using to install the new firmware. Kuwfi also has instructions to do the same, however they have defaulted to a different local allocation than what Golden Orb is. I should not use the Kuwfi IP allocation and use the address allocation listed for Golden Orb?
I will be performing this using a ChromeBook, which I’m sure most of you are aware, do not have internal Ethernet on them. I purchased an ANKER USB 3 Ethernet hub, and until now assumed these were low level enough standards that drivers and such would just fall back on kernel support. I now see on the ANKER site there are MacOS, Windows, and Linux drivers. The Linux drivers of course won’t do any good for a ChromeBook. If the hub works and I’m able to load anything through tcp/ip on the Ethernet Port, should that suffice for this upgrade? It’s a significant pain to hunt down a laptop with built in networking, though if bricking is at risk, I’ll find a way to get ahold of a laptop.
URL to ANKER: https://www.anker.com/products/variant/ ... b/A7514041
Currently I am barely hanging on with the KuWfi firmware. It is barely configurable, has a logging ability that doesn’t work, and will get very confused if it determines signal strength to be less than 50% average. Even under the best of circumstances the longest uptime I have personally seen is 6 hours and some minutes. After that it freezes up and luckily, there’s some kind of watchdog and kickoff ability to auto reboot the device after which it comes up working for a handful of hours again.
Having never seen nor configured Golden Orb and guessing it will be a unique experience compared to the current firmware I am familiar with, how hard is it going to be to get back up and running? It need not be ideal at first. It is enough to gain a connection to the AT&T tower I was able to connect to before. I can slowly fine tune settings over time as I learn more about them.
Any other I information you think would be relevant is appreciated.
Thanks.
I have had countless issues with this firmware. I would have long ago abandoned the hardware in it’s entirety were it not for these forums exposing to me just how well the WE826 can actually perform if using a modern firmware. I am just about to bite the bullet and write the Golden Orb firmware, but given the routers precarious installation location I wanted to make sure I had the rough steps correct before I try to hit the reset button while balancing on a make shift step.
I am electing to skip the Kuwfi final firmware in favor of going directly to Golden Orb. Will this poses any problems to bypass the OEM and write your firmware immediately? I will not be logging into the Kuwfi firmware at all, as I believe trying to use their “upload firmware” feature is only a recipe for bricking the hardware? If I am correct I must absolutely use the boot loader. Is The boot loader is still an HTTP served set of administrative pages, and not like other firmware where I have had to set up a TFTP server and use Cisco or equivalent commands?
Once I have initially installed Golden Orb will it be okay to use the firmware update feature or perhaps even auto update features within Golden Orb to do future updates? Or is there something unique about the WE826-T2 that mandates using the boot loader from this point forward.
I noticed that it is suggested to static IP the address to the computer I will using to install the new firmware. Kuwfi also has instructions to do the same, however they have defaulted to a different local allocation than what Golden Orb is. I should not use the Kuwfi IP allocation and use the address allocation listed for Golden Orb?
I will be performing this using a ChromeBook, which I’m sure most of you are aware, do not have internal Ethernet on them. I purchased an ANKER USB 3 Ethernet hub, and until now assumed these were low level enough standards that drivers and such would just fall back on kernel support. I now see on the ANKER site there are MacOS, Windows, and Linux drivers. The Linux drivers of course won’t do any good for a ChromeBook. If the hub works and I’m able to load anything through tcp/ip on the Ethernet Port, should that suffice for this upgrade? It’s a significant pain to hunt down a laptop with built in networking, though if bricking is at risk, I’ll find a way to get ahold of a laptop.
URL to ANKER: https://www.anker.com/products/variant/ ... b/A7514041
Currently I am barely hanging on with the KuWfi firmware. It is barely configurable, has a logging ability that doesn’t work, and will get very confused if it determines signal strength to be less than 50% average. Even under the best of circumstances the longest uptime I have personally seen is 6 hours and some minutes. After that it freezes up and luckily, there’s some kind of watchdog and kickoff ability to auto reboot the device after which it comes up working for a handful of hours again.
Having never seen nor configured Golden Orb and guessing it will be a unique experience compared to the current firmware I am familiar with, how hard is it going to be to get back up and running? It need not be ideal at first. It is enough to gain a connection to the AT&T tower I was able to connect to before. I can slowly fine tune settings over time as I learn more about them.
Any other I information you think would be relevant is appreciated.
Thanks.