On Custom Firmware

[halgory]

Hello everyone, this is my first forum post, and I feel compelled to share some thoughts with the development team.

Dear devs (who are also end users),

I'm a computer engineering student with a passion for system design and security, though my professional experience is still in its early days. I've been exploring the limitations of the current Terramaster NAS firmware, and one thing is crystal clear: the lack of support for custom firmware loading—especially on ARM-based devices—is a missed opportunity. The present system, with its restrictive TOS, prevents the installation of even basic Linux utilities like nano. This not only stifles the potential for tailored system modifications but also limits what advanced users can achieve. Imagine a device that empowers you to extend its capabilities without compromising its integrity. That's what we deserve.

I understand the concerns about security and the risks of allowing custom firmware, yet we already have the technology and methodologies to create controlled environments that protect the core system while inviting user innovation. This approach would enable the technically inclined to optimize and personalize their systems while keeping a robust level of security for all users. The current locked-down firmware, perhaps designed with the average user in mind, ultimately restricts the kind of advanced interactions that drive true innovation and performance enhancements.

The truth is, novice users aren’t the ones buying these devices. I’m in a Systems Programming class, CIS340, and there are students interning at public utilities infrastructure in the real world who are learning SSH in class and genuinely don't understand it at all, period. So to think home users, are the ones buying these devices for their baby pictures, or to setup a photo indexing app you made, or to turn on a whole home VPN, and that they wouldn't obviously want to load other firmware is wild. This isn’t hyperbole—it's the reality. And the sentiment across the internet is clear: change is needed, and it isn’t just a fringe opinion.

To say that these features are missing to simplify and secure the devices seems like an excuse—either the development teams are avoiding the challenge, not fully acknowledging user feedback, or the design team believes that locking in a specific software package actually enhances the product's value. They assume that a controlled, unified ecosystem offers greater consistency (perhaps in the UI) than it does detract from the critical need for functionality.

Frankly, it feels as if the design team is applying a Human Interface Guidelines mentality to both the TOS and the devices, treating Terramaster NAS units like perfectly polished, prepackaged products such as something like an iPhone platform. But these are third-party home NAS solutions—not consumer gadgets that simply work out of the box without sacrifice. At least mine took 3 tries to setup, with NAS experience. When you invest in a NAS, you expect the level of customization and advanced functionality found on a PC. Instead, we see a sometimes clunky UI and limited support for software and tools that vary by model. When you buy a NAS, you expect to truly own it—to harness its full potential—and I believe most users share that vision.

Being locked to a specific firmware, with every app forced into a predetermined package, is absurd. I want the freedom to sideload firmware, to break free from the confines of bloated code and a buggy UI that tries too hard. I don’t want to be forced to sell my device, invest time programming apps specifically for this NAS, or listen to the excuse, “please research a product before buying”—because none of this was disclosed in the prepurchase materials. It comes with a TOS, but it never mentioned that you're locked in. I only chose this NAS because it was affordable and available on Amazon, and I've already had to rebuild my 'TRAID' in just six months, on a battery backup!

Warm regards,
– the end user (who is often a dev)

[TMroy]

Thanks for your feedback, and thanks for choosing Terramaster! I’m guessing you own an entry-level NAS from the 210 or 212 series. Let’s be real—this NAS is a budget-friendly, entry-level model aimed at regular home users, and it’s built on an ARM-based system architecture. Right now, TOS doesn’t have plans to open up the code for user customization. Plus, I don’t think you realize how tough it is to adapt a custom firmware for an ARM hardware platform. It’s not something just anyone can pull off—it usually takes a whole team, and without the development tools provided by the ARM chip manufacturer, it’s pretty much mission impossible. If you’re looking for a NAS that lets you tinker freely, you should probably go for an x86 model instead, run TOS 6 or install any other third party OS. I know what you’re thinking—you don’t want to sell your current device, and this answer might not sit well with you. But hey, that’s just the reality of the situation.

Anyway, thank you again.

[halgory]

Firstly thank you for replying, and thanks for being so kind as to articulate the current team mindset.

Plenty of people have ripped open your boxes (the fancier ones with an internal USB port that is) and gotten CFW onto them.

I own a F4-212, and currently, of the three options you suggested: there's no material way for me to upgrade to a new NAS with my budget, there's no way to install TOS6, and there's no way to upgrade to CFW. I understand that the F4-212 is 'intended to be' an entry-level, budget-friendly device aimed at the average home user, but many of us who buy these NAS units are not complete novices, nor do they seem to be marketed as such explicitly. We’re engineers, developers, and enthusiasts who want the freedom to tinker, customize, and truly harness the full potential of our hardware. Locking down the firmware might make the device seem more polished, but it also stifles innovation and prevents users like me from adding even basic Linux utilities that would allow for more flexibility and control. I can't even use nano, bro, for f*ck's sake man.

I realize that developing custom firmware for ARM-based systems is more challenging, and that without direct support or the necessary development tools from the chip manufacturer, it might seem like an insurmountable task. And I'm not asking you to do it yourselves. However, there are plenty of communities around ARM devices—think of what’s been achieved with Raspberry Pi or certain router platforms (think projects like OpenWRT)—that demonstrate it’s not impossible to open up the system a bit for those who are willing to take on the challenge, and still have strong security. If TerraMaster provided even a developer mode, where I can do stuff on my OWN machine that I PAID for, or a partial firmware unlock, advanced users could extend the device's capabilities without risking the stability of the system for everyone else. I shouldn't be punished for being poor, when you can fix it with a patch, my friend.

It’s frustrating when marketing materials make it seem like these NAS devices are fully featured while leaving out the limitations of a locked-down firmware. I wasn’t aware of such restrictions until after I purchased my F4-212, and now I find myself with a device that, while affordable, offers very little room for growth or customization, or learning, OR development. For many of us, upgrading hardware isn’t a viable option, and the inability to install TOS6 or a custom firmware means we’re stuck with a system that limits what we can do. What I’m asking for isn’t a complete overhaul—just a bit more transparency and the option to unlock the device’s potential for those who are capable and willing to take on a bit of risk. Ultimately, a little more openness could go a long way in building trust and fostering a vibrant community of users who truly know how to make their NAS work for them.

I feel it's a bit unfair to say something like, "If you don't like it, just do better shopping next time, or suck it up and deal with the next (also flawed) version of our OS—TOS6! Or just save up and toss this one out or sell it. " Such a response dismisses genuine concerns and doesn't acknowledge the limited options available, especially for those of us working with tight budgets and existing hardware constraints.

This isn't like I bought the wrong phone, this is a piece of software with intentional, useless restrictions.

[crisisacting]

It is exactly like you "bought the wrong phone" analogy; you bought a closed source/walled garden Apple device in the 21× TNAS devices series, but you want the openness of Android that's afforded to the ×2×/×5× TNAS device series.

The device is marketed and sold for its intended purpose, exactly how TerraMaster has determined they'd like to offer it, but you are looking to do things outside that scope.

TerraMaster might be able to offer tools, documentation for accessing UART and/or some source code, at their discretion, but have zero obligation to do so.

[TMroy]

If you have the development skills, you could purchase an x.86 device, package about 20–30 community applications, and make them available for TerraMaster users. We would then reimburse you for the cost of the device. What are your thoughts on this?

Here is app development guide: viewtopic.php?t=6401

[halgory]

If you have the development skills, you could purchase an x.86 device, package about 20–30 community applications, and make them available for TerraMaster users. We would then reimburse you for the cost of the device. What are your thoughts on this?

Here is app development guide: viewtopic.php?t=6401

While I'm not CERTAIN that I have the skills (I'm surprised I can type in complete sentences). . .
You pose a challenge. And I'm far overconfident, think "being called chicken" in BTTF.

I will consider this, let me first plan it out, do a test, and consider the time commitment.