ZTE MF910 / MF910B / MF910V / Telstra MF910v & MF90: ADB, Root & Persistent Shells

ZTE MF910 / MF910B / MF910V / Telstra MF910v & MF90: ADB, Root & Persistent Shells

Lineage note: the MF910 techniques in this guide didn't come from nowhere — they're the direct descendants of the [ZTE MF65 series on this blog](/2016/06/zte-mf65-mode-switch.html) (June 2016 onward). The MF65 is where the mode-switch trick and the zte_conf-script persistence approach were pioneered; this guide ports them forward to the Android-based MF910 generation and the MF90. Full list of the MF65 predecessors in the credits below.

The ZTE MF910 family (including the Telstra-branded MF910v) is an Android device in disguise — Qualcomm SoC running a Linux build with an OEM web UI on top, and the whole thing is reachable over ADB once you flip one hidden switch. The MF90 does the same trick with telnet instead of SSH. Here's the full workflow, Linux and Windows.

Default credentials

DeviceAccountPassword
MF910 / MF910B / MF910V / Telstra MF910vroot (shell)oelinux123
MF910 family (web UI)—password
MF90 (web UI)adminadmin (also blank/admin on some firmware)

Note: the `oelinux123` root password is baked into the firmware image — it's the same across units and firmware revisions.

Getting set up

1. Get ADB (Android Debug Bridge):
• Linux: `https://dl.google.com/android/repository/platform-tools-latest-linux.zip`
• Windows: `https://dl.google.com/android/repository/platform-tools-latest-windows.zip`
2. Plug the device into your computer via USB — it enumerates as an RNDIS gadget. Let drivers install.

Sanity check (same on both OSes, from the platform-tools folder):

adb start-server

adb devices

Starting the ADB listener on the router

The web UI hides an ADB mode switch. Open the local `tools.html` mode-switch page, tick the ADB checkbox, submit — the device flashes and reboots into ADB mode.

**Or skip the file entirely.** The checkbox just POSTs to a goform endpoint, and on the MF910 one variant of it works with **no authentication at all**:

http://192.168.0.1/goform/goform_set_cmd_process?isTest=false&goformId=SET_DEVICE_MODE&debug_enable=1

Post-auth variants that also flip the USB mode into ADB:

http://192.168.0.1/goform/goform_process?isTest=false&goformId=MODE_SWITCH&switchCmd=FACTORY

http://192.168.0.1/goform/goform_set_cmd_process?isTest=false&goformId=USB_MODE_SWITCH&usb_mode=6

(Worth knowing: `usb_mode` is read but never sanitized — Pentest Partners later showed it's directly injectable on the MF910.)

Shell access

Back on the host:

adb devices

List of devices attached

PXXXXXXXXD000000 device

adb shell

Root shell, no password asked. Now build a proper login path — create a user, set a password, and punch port 22 through the firewall:

adduser -s /bin/sh -S

passwd

iptables -t filter -I INPUT -p tcp --dport 22 -j ACCEPT

iptables -t filter -I INPUT -p udp --dport 22 -j ACCEPT

Persistent root, surviving factory reset

Everything in `/usr/zte/zte_conf/scripts/` re-runs at boot and is regenerated from the carrier config on reset — so that's where persistence lives. Generate a password you'll remember, then:

vi /usr/zte/zte_conf/scripts/firewall_init.sh

1. Comment out lines 92–93 (the rules that drop inbound 22):

#iptables -t filter -I INPUT -p tcp --dport 22 -j DROP

#iptables -t filter -I INPUT -p udp --dport 22 -j DROP

2. Further down the script, add:

echo "password

password

" | passwd

(replace `password` with yours — this sets root's password at every boot)

Save, close, reboot. ADB mode drops off, the device boots normally, and SSH comes up listening with your root password.

ssh root@192.168.0.1

Caveats: this persistence does **not** lock out ADB root — anyone with the web UI password (`password` by default) can re-enable ADB the same way we did and walk straight back in. Change the web UI password first if the device is ever on an untrusted network.


MF90 (telnet variant)

Same flow, telnet instead of SSH. Web UI password: `password` (admin/admin on some firmware).

1. Enable ADB via the mode-switch page (or the SET_DEVICE_MODE URL above).
2. `adb shell` for root.
3. Create the user and open the firewall as above, but for port 23 — then set up persistence in **two** scripts:

**`/usr/zte/zte_conf/scripts/firewall_filter_init.sh`** — near the end, before `echo "firewall init done"`:

echo "

" | passwd

telnetd -F -p 23 &

**`/usr/zte/zte_conf/scripts/firewall_init.sh`** — add the ACCEPT rules:

iptables -t filter -I INPUT -p tcp --dport 23 -j ACCEPT

iptables -t filter -I INPUT -p udp --dport 23 -j ACCEPT

iptables -t filter -I OUTPUT -p udp --dport 23 -j ACCEPT

iptables -t filter -I OUTPUT -p tcp --dport 23 -j ACCEPT

Reboot and telnet in:

telnet 192.168.0.1

login:


Credits & lineage

This guide stands on the MF65 work published right here on frankhacks, in chronological order:

• [ZTE MF65 mode switch](/2016/06/zte-mf65-mode-switch.html) (Jun 2016) — the original mode-switch trick that the MF910's ADB enable is a direct port of
• [ZTE/Telstra MF65 remote file include](/2016/06/zte-telstra-mf65-remote-file-include.html) (Jun 2016)
• [ZTE MF65 local file listing/include](/2016/06/zte-mf65-local-file-listinginclude.html) (Jun 2016)
• [ZTE MF65 local exec / file include](/2016/06/zte-mf65-localexec-file-include.html) (Jun 2016)
• [ZTE MF65 EFS access method](/2017/05/zte-mf65-efs-access-method.html) (May 2017) and [unlocking a few more features](/2017/07/zte-mf65-unlocking-few-more-features.html) (Jul 2017)

Later entries in the same line, for the MF910 itself: [MF910v mode switch / ADB enable](/2019/02/zte-mf910v-mode-switch-adb-enable-at.html), [MF910v LFI http_share exploit](/2019/02/zte-mf910v-lfi-httpshare-exploit.html), [MF910v root exploit](/2019/02/zte-mf910v-root-exploit.html), [Telstra MF910v exploit scripts](/2024/07/telstra-ztemf910v-exploit-scripts.html) (2024).

External references:

• [kristrev/zte-mf910-scripts](https://github.com/kristrev/zte-mf910-scripts) — independent confirmation (Jan 2016) that ADB shell = root on the MF910, plus host-side helper scripts
• [Pentest Partners](https://www.pentestpartners.com/security-blog/zte-mf910-an-end-of-life-router-running-lots-of-vivacious-hidden-code/) (2019) — reversing the `zte_topsw_goahead` web binary: the pre-auth `SET_DEVICE_MODE` endpoint, the injectable `usb_mode` param, and the syslog goform API. Their ZTE PSIRT exchange is worth a read — ZTE "fixed" the MF920 by removing `nc` from the image and assumed the MF910 PoC didn't apply. It did.
Tested on MF910, MF910V and Telstra MF910v firmware current at time of writing; MF90 steps verified on the BD_HDV6MF90V1 line. Your mileage may vary on carrier-branded firmware.

Comments

Popular Posts