Skip to content

Post-Root Procedures


Do not follow any post-root procedure unless explicitly told to.

Bank Planning

We are now going to prepare an optimal bank plan for the same firmware version you have now booted.

Run the following command to look at your Gateway's bank state:

find /proc/banktable -type f -print -exec cat {} ';'

Take note of active and booted banks:

<take note of this>
<take note of this>

At the end of this guide your Gateway will boot the same firmware you are now running as per optimal bank plan:


We will now check the current state and move to the above one, such that it will boot from the recommended bank on every reboot.

On which bank should I stay to be safe?

It's strongly recommended to stick to the optimal bank plan (listed above) before modding your device further. The bigger picture description can be found here. The short thing is that you should really consider modding your preferred firmware version (not necessarily of Type 2) while booted from bank_2 keeping bank_1 as the active one.
Key Point: it's unsafe to deeply mod firmware settings of any firmware booted from bank_1.

Notable exception: Missing RBI

In the unfortunate case that there are no RBI firmware files available for your model, you are not in a safe position because you can't exploit BOOTP recovery options. In such a situation whatever bank you boot is the same. Your best option is to keep a copy of your current rooted Type 2 firmware on both banks. Skip bank planning for optimality.

Run the following commands:

# Copy firmware into bank_2 if applicable
[ "$(cat /proc/banktable/booted)" = "bank_1" ] && mtd write /dev/mtd3 bank_2
# Make a temp copy of overlay for booted firmware
cp -rf /overlay/$(cat /proc/banktable/booted) /tmp/bank_overlay_backup
# Clean up overlay space by removing existing old overlays
rm -rf /overlay/*
# Use the previously made temp copy as overlay for bank_2 firmware
cp -rf /tmp/bank_overlay_backup /overlay/bank_2
# Activate bank_1
echo bank_1 > /proc/banktable/active
# Erase firmware in bank_1
mtd erase bank_1
# Reboot to first valid firmware
# please wait for device to reboot...

You should now be in the previously mentioned optimal bank plan. On each reboot, your device will try booting active bank first. Since we set bank_1 as active and we also erased bank_1 firmware, it will boot from bank_2.

Upgrade now!

Would you like to upgrade to a newer firmware? This is the perfect moment for doing it. It is now safe to also install non-Type 2 firmwares. Just follow the Safe Firmware Upgrade guide for this. You could also upgrade later in future and continue tweaking the current firmware. Once you did install the updated firmware, come back here and continue reading.

At this point, you now need to check if your SSH server setup is permanent.

Setting up Permanent SSH Server

Are you connected to SSH on port 6666? In most cases, the answer is "No, I didn't need to specify port 6666, I've got connected on default port 22". You don't need to run the below commands if you can already connect on default port 22, your SSH setup is permanent already.

If the answer is "Yes", run these commands to setup a permanent SSH access on port 22 by defining a new dropbear instance:

uci -q delete dropbear.afg
uci add dropbear dropbear
uci rename dropbear.@dropbear[-1]=afg
uci set dropbear.afg.enable='1'
uci set dropbear.afg.Interface='lan'
uci set dropbear.afg.Port='22'
uci set dropbear.afg.IdleTimeout='600'
uci set dropbear.afg.PasswordAuth='on'
uci set dropbear.afg.RootPasswordAuth='on'
uci set dropbear.afg.RootLogin='1'
uci commit dropbear
/etc/init.d/dropbear enable
/etc/init.d/dropbear restart

Now proceed to changing your root password, this is mandatory.

Change the Root Password

Serious hint!

Do not ignore this step! Your firmware was probably designed to work only on certain specific ISP network. Some kind of remote SSH access could be left open by design in such a way only that same ISP could access. Connecting to some different ISP network could lead to this open access to be exposed on the internet.



Now you must harden your access, to prevent it from being lost because of unwanted automatic firmware upgrades in future. See Hardening Root Access page.