Adding OpenWrt support for Zyxel EX5601-T0

Because not every method works for everyone. For example, the non-serial method does not work on my UK version. For me, it is preferable to have a web based method if possible.

Then you need to do some detective work, or send an unit to someone who can do the work for you.

Use Incognito or inPrivate mode on your browser when overriding the javascript.

If you still can’t get it to work, then you can pm me.

EDIT: Isn't V5.70(ACDZ.3.2)C0 basically stock firmware? It shouldn't be locked down.
But it might be possible that Zyxel has fixed some vulnerabilities in these updates.
You should sitll be able to use mtk_uartboot without any issues.

EX5601/EX5600-T: Wireless AX6000 Routers | EMEA | Zyxel

Yeah perhaps I should wait.

1 Like

I’ve tried Firefox via Private Window and am also not having luck with a serial connection, so PM sent & hope it makes sense!

I personally think that allot of volunteers invest xxxx hours for free in this great project. An end user that can use this project for free should invest the time to learn the serial method. (± 8 hour average)

Why risk the working method with an easier route.

Well, we are all welcome to have our personal opinions but not all of us (myself for example) are as smart as some of the others on here, and so need a bit of help along the way especially if they have a box with different firmware. I remember years ago when a newer version of the WRT54G router was released, the initial method to install OpenWRT involved installing an intermediate OS, a few months later someone else worked out a simpler way to do it… evolution through iterations of solutions..

1 Like

It's okay. I am not smart either but I try to help people where possible.

It's not an issue for me.

If you look at my first posts in this topic you will see I had no clue what i was doing. Eventually I learned it just by trial and error and some (little) help from people.

2 Likes

Serial is the most foolproof method of flashing, no matter which firmware it's running, unless your device has been locked down.

2 Likes

So, when editing and overriding the javascript files I ran into certificate problems (according to console) all the time. I guess it's some kind of built-in protection that stops the router page from functioning when you mess with it. It works again after opening a new private tab with new cookies and files reverted to original.. It usually happened instantly if i edited too much. It also happened when doing small changes, usually not instantly but after clicking around a few times.

The same issue is happening to @cancunia

So i've found a way around this on the Odido firmware. It's possbile that it might not work on other firmwares as they keep getting updated for security vulnerabilites by Zyxel.

The router always redirects us to https and the problerm lies there. With a few changes we can stop the redirections and the certificate issues will be gone. You'll also be able to use http://192.168.1.1 instead of the forced redirection.

The changes are easily made in the app.js file

Search for HTTP_Redirect_HTTPS in app.js

and change the https: protocols to http:
It will look like this below.

                            window.location.href = "http://" + location.hostname + ":" + s.HttpsPort),
                            me.a.state.guiFlag.STARRY_GUI_Customization && (me.a.dispatch("getLangJson", me.a.state.basicInfo.CurrentLanguage),
                            "" == me.a.state.themeColor && (_ = "starry",
                            me.a.commit("updateThemeColor", _),
                            (h = document.getElementById("app")).className = "",
                            h.classList.add(_))),
                            t.ZYXEL_TT_CUSTOMIZATION && s.Redirect_To_HTTPS && "" != s.Redirect_Port && (m = "",
                            m = "http://" + location.hostname + ":" + s.Redirect_Port + location.pathname + location.search + location.hash,
                            location.href = m));

Also sometimes i get errors about CrossSiteTesting not being enabled.

For this you can change zyxel.js and change the 2nd line.

from
var enableCrossSiteTest = false;

to
var enableCrossSiteTest = true;

1 Like

I’m trying to flash another unit that i’ve sourced from wifilinks, but i can’t seem to be able to get serial working

I soldered the header and wires to my serial interface, tried both 115200 and 9600 speeds, swapped over tx/rx but im not getting any serial output.

What i did find interesting is that this device is missing R15 and R559 resistor which appear to be present in the device pictured in the wiki?

Any ideas if perhaps these missing resistors might be the culprint? Any other way to flash ? The device seems to be running firmware V5.70(ACEA.0)T56C_b7_1006 if that helps

If it's Odido branded, try the firmware hacks.

Yes, it’s odido branded with an old firmware it seems. I’d like to use ubootmod partition layout if possible to have an unified setup with all other T-56s i have.

Is it possible to do ubootmod without serial?

I might just check what resistance value these are and solder them on. Other units i have should still have these. After further inspection, they do appear to be related to rx/tx pins via contiunity test.

Yes it is

I went with serial method anyway. Bridged the two missing resistors with a bit of solder and it worked just fine.

2 Likes

That's useful info, thnx for reporting back.

Any chance you could post a photo ?

1 Like

Marked pins need to be bridged.

4 Likes

Firstly a massive Thank You to @thehybrid1337 for helping me through the learning curve!

I’ve discovered that the ā€˜sys’ command used to expose the root password (see here) will work when using the restricted shell in the ā€˜admin’ account via a serial link. It also turns out that using the root password works with the ā€˜supervisor’ account on the web GUI, at least on firmware version V5.70(ACDZ.3.2)C0

I went down this route as I could not get the web gui app.js hack to work on my UK sourced EX5601-T0, it may be just that my js editing was not up to it.

Once logged in as supervisor, all of the Maintenance menu options appeared, including the ability to enable SSH. It is also worth looking at the TR-069 settings while you’re logged in as supervisor.

So, it should now be possible to follow the sys commands & the rest of the ā€˜non serial’ recipe documented by @carlicious ->here

I’ve not tried to follow the recipe yet as I’m still looking at the stock firmware options.

are they the pullups for serial pins? so you could probably try with external pullups.. (better than shorting lines up :))

They appear to be, yeah. Not too sure about the values they used; could be checked on a router tha has them. In any case, for the few minutes it takes to flash openwrt on it, it shouldn’t matter.

I just bought an unused Odido T-56 / EX5601-T1 with this older firmware version: V5.70(ACEA.0)T56C_b7_1006

I'm getting a bit confused on the different instructions for installing OpenWrt 24.10 on this device. Should of shouldn't I first let the router update to the latest Odido firmware?

Could anyone please point me to the best guide for flashing OpenWrt 24.10 without using a serial connection?