
The UNESCO-UNEVOC International Centre: Who We Are | What We Do | Donors and partners | Working With Us | Get in Touch
The UNEVOC Network: Learn About the Network | UNEVOC Network Directory | UNEVOC Network Spotlight
For Members: UNEVOC Centre Dashboard
Thematic Areas: Inclusion and Youth | Digital Transformation | Private Sector Engagement | SDGs and Greening TVET
Our Key Programmes & Projects: BILT: Bridging Innovation and Learning in TVET | Building TVET resilience | TVET Leadership Programme | WYSD: World Youth Skills Day | UNEVOC Network Coaction Initiative
Past Activities: COVID-19 response | i-hubs project | TVET Global Forums | Virtual Conferences | YEM Knowledge Portal
Publications & guides: Publications | Greening TVET guide | Entrepreneurial learning guide | Inclusion in TVET guide
Resources: TVET Forum | TVETipedia Glossary | Global Skills Tracker | TVET Country Profiles | Innovative and Promising Practices | Open Educational Resources | Digital Competence Frameworks | TVET Toolkits
Events: Major TVET Events | UNEVOC Network News
This led to the release of the —a simple one-click tool that allowed unsigned code to run. Without the Jailbreak, loading a Linux kernel (let alone Android) was impossible. The Linux Kernel Abstraction Android is not magic; it is a heavily modified Linux kernel running a Java-based (Dalvik/ART) userspace. The SoCs in Windows RT devices (Nvidia Tegra) had excellent open-source Linux support. Nvidia had released documentation for the Tegra line, and the mainline Linux kernel already supported the architecture.
In early 2013, the first crack appeared. A hacker known as discovered a flaw involving a specific, privileged Windows kernel driver. By chaining a series of privilege escalation exploits, developers achieved what seemed impossible: disabling Secure Boot on the fly.
While you will never replace your iPad with a Surface RT running Android, you can turn a $50 eBay paperweight into a fascinating conversation piece that dual-boots two rival operating systems. In a world of locked bootloaders and planned obsolescence, that tiny act of digital rebellion is its own reward.
In the annals of tech history, few products had a more confusing identity crisis than Microsoft Windows RT 8.1 . Launched alongside the revolutionary Windows 8, RT was the "walled garden" variant designed for low-power ARM processors (the same chips found in smartphones). It looked like Windows, felt like Windows, but crucially, it could not run traditional .exe applications—only "Modern UI" apps from the Microsoft Store.
The problem was Windows RT 8.1. Microsoft abandoned it quickly, leaving users with an obsolete OS, a defunct Store, and Internet Explorer (later patched) as their only lifeline. The desire to run Android wasn't just about apps—it was about . The Core Hurdle: Secure Boot Microsoft learned from the "jailbreak" culture of Windows Mobile. With Windows RT, they implemented a hyper-strict Secure Boot policy. The device would only boot software cryptographically signed by Microsoft.
This is the story of how developers broke the chains of Windows RT to unleash the green robot. The Surface RT devices were, on paper, excellent pieces of hardware. The original Surface RT featured a 10.6-inch ClearType HD display, a magnesium VaporMg case, USB port, and a battery life that crushed competing x86 tablets. The Tegra 3 (and later Tegra 4 in Surface 2) processors were powerful enough for web browsing, media consumption, and light productivity.
For users who bought the sleek (and expensive) Microsoft Surface RT or Surface 2, the reality was brutal: a beautiful tablet with a kickstand and a keyboard, crippled by a desert of software.
But the hacking community had a different question: What if it ran Android?