UFI-TOOLS: web management and plugin platform for Zxe mobile WiFi devices
A functional tools for z*e devices (F50 | U30 Air)
At a glance
- What is it?
- UFI-TOOLS provides remote management, real-time signal monitoring, SMS handling and a downloadable plugin store for Zxe mobile WiFi hardware (F50, U30 Air and compatible Unisoc-based models). Two editions cover different deployment targets: Pocket Edition runs on a phone, Full edition installs on the device.
- Who is it for?
- UFI-TOOLS suits owners of Zxe mobile WiFi hardware (F50, U30 Air and compatible Unisoc-based models) who need more than the stock interface offers. PE covers phone-side remote management; the Full edition is the one to deploy for the plugin store, AT command terminal and advanced features.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 23 days ago.
- What is it written in?
- Mainly JavaScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on October 6, 2026, and from our analysis. They are not legal advice.
Editorial analysis
Zxe mobile WiFi management through a web server at port 2333
UFI-TOOLS targets owners of Zxe mobile WiFi hardware who need operations the stock firmware interface does not provide. F50 and U30 Air are the named primary targets; compatibility extends to any Zxe unit with a Unisoc CPU running Zxe MyOS 13. After installation, the tool exposes a web interface at port 2333 on the device IP, and ships as an Android application on the management side.
Four functional categories define the scope. System and device control covers performance modes, CPU core selection and battery charge limits. Network management handles band and cell locking, 3G/4G/5G switching and real-time signal metric visualization. Communication features include SMS sending, receiving and auto-forwarding alongside a built-in AT command terminal for direct modem interaction. A plugin store rounds out the set with downloadable add-ons for security, automation and remote access.
The standard alternative is the stock management page most mobile WiFi hardware ships with, supplemented by ADB for operations that page does not expose. That combination handles basic network configuration but provides no plugin ecosystem, no real-time cellular metric charting and no SMS forwarding from the device SIM.
PE edition connects from a phone; Full edition installs on the device and ships from the http-server-version branch
UFI-TOOLS comes in two editions aimed at different deployment scenarios. Pocket Edition (PE) runs on an Android phone, connects to the mobile WiFi unit over the local network and handles remote management without modifying the device. Full edition installs directly on the target hardware and delivers the complete capability set.
http-server-version is the default branch and holds Full edition code; main holds PE, so cloning without a branch flag delivers the Full edition rather than PE.
Plugin store access is the sharpest practical distinction between editions. PE cannot reach the store at all; Full edition users get all catalog entries including ADGuardHome, EasyTier and Crontab. PE targets users who want quick phone-side remote control without device-side installation.
Magisk module serves phone users; F50 and U30 Air have a one-click and a screen-mirroring path
Detailed installation steps are in User_Doc.md in the repository. Two Bilibili video tutorials are linked: one covering the F50 and U30 Air path generally, a second dedicated specifically to Magisk module installation on the 畅行60 and 云电脑 tablet models.
Two methods cover the platform split: phones and tablets use the Magisk module path, while mobile WiFi devices such as the F50 and U30 Air support two documented options, one-click install and screen-mirroring install.
The default access address after installation is http://[device IP]:2333. No default login credentials appear in the README. API_Doc.md is listed alongside User_Doc.md as a linked reference document, but neither file's contents are summarized in the README itself, making User_Doc.md the first stop before attempting any installation.
No-reboot band locking and real-time RSRP, SINR, PCI monitoring take effect immediately
Band and cell locking applies immediately, without a device restart, and both operations are grouped under the network management feature category, distinct from 3G/4G/5G mode switching.
Nine signal metrics update in real time: RSRP, SINR, PCI, Band, QCI, SNR, QoS, IPv6 status and network throughput, with a rate chart for the last item. RSRP (Reference Signal Received Power) measures signal strength; SINR (Signal to Interference and Noise Ratio) measures quality relative to interference. PCI (Physical Cell ID) identifies the attached cell, and QCI (QoS Class Identifier) reflects the carrier-assigned traffic class, with all nine displaying live without a page refresh.
Cell locking and band locking together give users direct control over which specific cell and frequency band the device attaches to, a capability that 3G/4G/5G mode selection alone does not provide.
The plugin store catalogs ten entries including ADGuardHome, EasyTier, EasyConnect and Crontab
Ten plugins fill the store, organized under seven functional categories. ADGuardHome handles ad filtering and DNS management. A traffic status card displays throughput in real time. An AI dashboard provides monitoring visualization. SSH tools open remote command-line access. CPU core control configures which cores stay active. A theme and layout editor adjusts the interface. A battery charging threshold control limits the maximum charge level. EasyConnect provides campus VPN access. Crontab manages scheduled task execution. EasyTier handles cross-network remote connections between devices.
Some entries require advanced features mode to be enabled before they can be installed, though the plugin table does not identify which specific ones carry that requirement.
The AT command terminal is a built-in function, not a plugin store entry, and supports direct interaction with the modem's AT interface for signal queries, frequency testing and custom command sequences.
Advanced features require explicit enablement and grant root-level access; the notes section warns to back up data first
Advanced features is a mode that is off by default and must be explicitly enabled, at which point it delivers root-level system permissions, access to hidden interfaces and low-level management modules, all plugin store plugins, a zero-wait fast update channel, remote SSH access, file push capability and system-level debugging.
A warning in the notes section is specific: back up important data before using advanced features. This appears as a distinct item, separate from the capability list, framing the backup step as a prerequisite rather than an afterthought. Root access to system partitions and hidden interfaces can produce configuration changes that require reflashing to reverse.
Six hardware configurations appear in the test environment. Four carry the Rooted annotation: 畅行60, 畅行60Plus, 远航60 and 云电脑平板. U30Air_SSVB14 and MU300 are listed without it.
Full and PE editions maintain separate codebases on different branches, with independent version numbering
The repository splits the two editions across separate branches: Full edition on http-server-version, PE on main. Each branch carries its own version sequence. V4.0.0 and v3.9.5 are separate-branch outputs published five days apart in early 2026; neither supersedes the other, and neither is a revision of the same codebase.
Without that context, scanning the repository's tags produces an unexpected order: a three-series number appearing after a four-series one. Both editions are current on their own branches. Checking http-server-version and main separately gives the correct picture for each.
The project is distributed under the MIT licence. API_Doc.md is listed as a reference document alongside User_Doc.md in the README.
Editorial conclusion
UFI-TOOLS suits owners of Zxe mobile WiFi hardware (F50, U30 Air and compatible Unisoc-based models) who need more than the stock interface offers. PE covers phone-side remote management; the Full edition is the one to deploy for the plugin store, AT command terminal and advanced features. Avoid it on devices outside the documented compatibility list: some features depend on the specific model and firmware, and before enabling advanced features, back up important data as the notes section explicitly warns.
Frequently asked questions
What devices does UFI-TOOLS support?
F50 and U30 Air are the named primary targets. Broader compatibility covers Zxe devices with a Unisoc CPU running Zxe MyOS 13. Six configurations were used in testing: U30Air_SSVB14, MU300, 畅行60, 畅行60Plus, 远航60 and 云电脑平板, with the last four in rooted configurations.
What is the difference between UFI-TOOLS PE edition and the Full edition?
PE runs on an Android phone and connects remotely to the device, offering management with a reduced feature set and no plugin store. Full edition installs on the target device and provides the complete capability set including all ten plugin store entries.
What port does UFI-TOOLS use for the web interface?
Port 2333. The default access address is http://[device IP]:2333. No alternate port setting is documented.
Does UFI-TOOLS require root access?
Basic features work without root. Advanced features mode requires root-level system access and delivers hidden interfaces, SSH, all plugins and system-level debugging. The notes section warns to back up data before enabling it.
Where are the UFI-TOOLS installation instructions?
User_Doc.md in the repository. The README links to Bilibili video tutorials for the F50 and U30 Air path and separately for Magisk module installation on 畅行60 and 云电脑 tablet models.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/kanoqwq-ufi-tools)