From XDA ROM Kitchens to Locked Bootloaders — Why Right to Repair Must Include Software Freedom

There was a time when your phone actually felt like your device.

Not just physically yours because you paid for it, but architecturally yours. You could unlock it, rebuild it, replace parts of it, change how it behaved, and shape it around your own needs and preferences. Your phone was becoming a pocket computer, and many of us treated it exactly that way.

This article was not planned.

It started because a customer brought me a modern gaming phone wanting “global firmware” flashed onto it. Fifteen years ago that would have been a fairly straightforward conversation. Unlock it, back it up, flash it, tune it, test it, done.

Instead, the process now involves:

• cloud-bound unlock permissions
• region restrictions
• anti-rollback protection
• attestation systems
• encrypted partitions
• and carefully preserving calibration data so basic hardware functions continue working

And suddenly I found myself deep in nostalgia.

Long before I ran Norgan Technology, I was heavily involved in the XDA Developers community during the Windows Mobile, HTC HD2, and early Android era. I was not just flashing ROMs. I was cooking them, debugging them, rebuilding them, and releasing them publicly.

Back then, communities like XDA were full of people experimenting, learning, sharing fixes, porting drivers, improving battery life, replacing interfaces, debugging radios, and squeezing every last bit of performance and functionality out of devices manufacturers had often already abandoned.

I signed off on my first public ROM release back in 2010. Looking back at those old threads now feels like opening a time capsule from a very different era of computing.

Before Smartphones Became Appliances

I still remember sitting on the top floor at Granville TAFE back in 1997 while doing my diploma, experimenting with analogue mobile phones, modifying a Motorola Pocket Classic, jumping battery pins to manually access engineering and scanning functions, and discovering just how much functionality existed beneath the surface of early mobile systems.

This was before smartphones, before app stores, and long before locked-down mobile ecosystems became normal.

Years later, that same curiosity evolved into ROM cooking, firmware modification, radio tuning, and eventually active involvement in the XDA Developers community during the Windows Mobile and early Android era.

Communities like XDA Developers, early GSM forums, PDA communities, and embedded hardware groups were full of people learning collaboratively. People shared discoveries, fixes, tools, and techniques openly. A lot of us learned more practical systems engineering from those communities than from formal education.

Phones were becoming pocket computers, and for a brief period, it truly felt like users were allowed to own them.

We were not doing it because we hated the devices.

We were doing it because we loved them.

The Golden Era of Device Ownership

The HTC HD2 became legendary because the community refused to accept its official limitations. People managed to run Windows Mobile, Android, Linux, and Windows Phone on hardware that was never meant to support all of them — sometimes all on the same device.

You could:

• replace the operating system
• modify kernels
• tune radios
• optimise drivers
• customise interfaces
• recover failed flashes
• and extend the life of hardware manufacturers had already moved on from

That era created an entire generation of accidental engineers.

We learned by experimenting.

If your battery life was bad, you could investigate why.

If your phone lagged, you could replace the kernel.

If your manufacturer abandoned updates, the community stepped in.

Your phone was not a sealed appliance. It was a system you could learn from.

Ironically, that openness created some incredibly capable engineers, developers, technicians, and repair professionals. Many of today’s repair technicians and systems architects came from that exact ecosystem.

What Changed?

Modern phones are objectively more powerful, more secure, and more polished than those older devices ever were.

But they are also increasingly hostile to ownership.

Today we see:

• locked bootloaders
• cryptographic attestation
• region restrictions
• anti-rollback protection
• cloud-bound activation
• serialised components
• inaccessible calibration data
• and software locks tied to hardware replacement

Even replacing a battery or screen can trigger warnings, reduce functionality, or disable features entirely.

Installing a different operating system on your own device is now often treated as suspicious behaviour.

Manufacturers usually frame this entirely as a security issue. Some of it genuinely is. We do need secure devices. We do need protection from malware, fraud, and compromised firmware.

But somewhere along the line, the industry quietly shifted from:

“You own this device.”

to:

“You are permitted to use this device under our conditions.”

That is a very different relationship.

Right to Repair Is Not Just Hardware

When people hear “Right to Repair”, they usually think about:

• batteries
• screens
• screws
• glue
• spare parts
• and whether a device can physically be opened

Those things matter.

But software freedom matters too.

A truly repairable device should allow:

• operating system replacement
• bootloader unlocking
• community firmware
• access to diagnostics
• backup and restoration of calibration data
• and independent servicing without vendor approval

A phone should not become landfill because a company stopped supporting it.

A user should not lose ownership because a cloud server was turned off.

A repair technician should not need hidden corporate authorisation simply to restore functionality to hardware the customer legally owns.

Why This Matters Beyond Phones

This is not nostalgia for the sake of nostalgia.

This affects:

• sustainability
• e-waste
• digital sovereignty
• accessibility
• consumer rights
• cybersecurity resilience
• and education

Open systems create curious people.

Curious people learn.

People who understand systems are harder to manipulate through ecosystem lock-in, artificial restrictions, and opaque technology.

The old modding communities taught an entire generation:

• troubleshooting
• reverse engineering
• software architecture
• hardware interaction
• and systems thinking

Many of us accidentally became engineers because we wanted better battery life, smoother scrolling, cleaner interfaces, or simply a phone that worked the way we needed it to work.

Ownership should include the right to understand and modify your tools.

The Balance We Actually Need

This does not mean every phone should ship fully unlocked by default.

There is a balance.

Most people want devices that:

• just work
• stay secure
• receive updates
• and protect their data

That is fair.

But consumers should still have the choice to unlock, modify, repair, and extend the life of hardware they own, especially once warranties expire, official support ends, or devices become obsolete by policy rather than capability.

Security should protect users.

It should not become a permanent excuse to remove ownership.

What Consumers Should Demand

If we want real Right to Repair, we need to demand more than access to parts.

We should expect manufacturers to provide:

• clear bootloader unlock paths for out-of-warranty devices
• official firmware restoration tools
• access to diagnostic information
• reasonable parts pairing policies
• repair documentation for independent technicians
• security models that protect users without permanently locking them out
• and long-term software support or a clean handover path to community maintenance

This is not anti-security.

It is pro-ownership.

We can have secure devices and repairable devices. We can have consumer protection without treating every owner, technician, and community developer as a threat.

Why This Still Matters to Norgan Technology

At Norgan Technology, this history matters because it shaped how I think about repair.

I do not see devices as disposable sealed boxes.

I see them as systems.

Hardware, firmware, software, power, data, and user need all interact.

Good repair is not just swapping parts. It is understanding the system well enough to restore function, preserve value, and avoid unnecessary waste.

That mindset came from years of modifying phones, cooking ROMs, debugging obscure faults, recovering failed flashes, and learning how devices actually behave beneath the polished interface.

The old XDA culture taught a simple lesson:

If people are allowed to learn from their devices, they become more capable, not less.

We Should Not Accept Less Ownership Than We Had Fifteen Years Ago

Phones are more powerful than ever.

They are also more central to our lives than ever.

That means the right to repair, modify, restore, and understand them matters more, not less.

If we lose that entirely, we do not just lose modding culture.

We lose technological agency itself.

And once people stop understanding the systems they depend on, they become increasingly dependent on the companies controlling them.

That should concern anyone who believes ownership should still mean ownership.