Archive update: Phandroid reported Android 2.1-era EVO 4G source availability on December 3, 2010, after the handset’s move to Android 2.2. That is the dated media record, not independently verified timing for HTC’s upload.
- Source code is not a complete retail firmware package.
- Publication does not grant root access on a handset.
- A source archive is not an OTA update for ordinary users.
| Record | Evidence and scope | Review status |
|---|---|---|
| December 3, 2010 | Phandroid report that source was available | Media publication date; HTC upload date: NA |
| Android 2.1 source / Android 2.2 handset background | Versions described in the same report | Historical media account; not package inspection |
| Original package version and filename | Original HTC download not obtained | NA |
| Original package checksum | Cannot calculate without the original file | NA |
NA means not obtained in this review. Source records were rechecked October 8, 2026.
What exactly was released?
The contemporary report called it Android 2.1 source for the EVO 4G. Without the original HTC package, this review cannot verify its exact component list, revision or completeness. The page discusses the kernel-source context rather than certifying the contents of a particular archive.
Linux kernel licensing documentation identifies GPL-2.0-only, and GPLv2 section 3 sets conditions for providing corresponding source when distributing covered binaries. Publication can serve those source-provision obligations; availability of one download does not by itself establish full compliance.
Which parts of an Android phone were open source?
Android devices combined several software layers with different licenses and owners. The Linux kernel formed the low-level core that managed hardware, processes, memory and power. Android platform components sat above it, while a manufacturer added device-specific changes, interface software and bundled applications. Radio firmware and some hardware-supporting binaries could remain proprietary.
GPLv2’s source-provision conditions apply to distribution of covered kernel binaries, through the mechanisms set out in section 3. That duty did not automatically apply to every program shipped on the phone. As a result, a manufacturer source page could be legally important and technically useful without containing enough material to reproduce the complete retail firmware.
This layered view prevents two common misunderstandings. “Android is open source” does not mean every byte on every handset is available, and a kernel archive is not merely optional sample code. The scope depends on the component and its license. The reported EVO 4G release belongs to that source-provision and development context; this archive is not a compliance audit.
Why did developers care about kernel source?
Kernel code helps experienced developers understand how hardware support, power management and device-specific changes were implemented. In the custom ROM era, timely source publication could make it easier to build compatible kernels and diagnose low-level problems.
| Source release can help with | Source release does not automatically provide |
|---|---|
| Reviewing vendor kernel changes | Proprietary HTC applications |
| Building compatible kernel variants | Carrier radio firmware |
| Understanding device drivers | A one-click consumer update |
| Providing source for covered components | Proof of complete license compliance |
What could a developer do with the source?
An experienced developer could compare HTC’s changes with the upstream kernel, inspect configuration choices and study code related to device hardware. Building a usable replacement still required the correct compiler, build configuration and supporting binary components. The resulting kernel then had to match the phone’s software expectations closely enough to boot and operate.
Source was particularly valuable when diagnosing behavior that ordinary Android application logs could not explain. Power management, scheduling, storage and device drivers operate below the app layer. A developer investigating battery drain or hardware compatibility could look for vendor modifications rather than treating the phone as an unexplained black box.
The archive should not make that work sound routine. A build that compiles can still fail on hardware, and flashing low-level software can make a device unusable until it is recovered. Community development depended on documentation, testing devices and shared expertise in addition to the code release itself.
Why was the timing criticized?
Phandroid’s December 3 report emphasized that the EVO 4G was already on Android 2.2 while this release concerned Android 2.1. That mismatch is the documented basis for the timing criticism; it does not establish HTC’s exact upload date.
Editorial analysis: Source matching the software under investigation is more useful than an older base when debugging current behavior. Older code can still support historical study. Record the binary version and corresponding source revision before drawing conclusions from a vendor archive.
How did source releases differ from rooting tools?
A kernel source archive gives developers code they are entitled to inspect and, with the right toolchain and device knowledge, rebuild. It does not itself grant administrator access on a consumer phone. The Easy Root story describes the other side of the era: an exploit-based app attempted to change a shipping device’s privileges directly.
The distinction is useful when reading about “open Android.” Google’s Android 2.1 SDK and compatibility work supported application development across devices; HTC’s source archive addressed licensed low-level components for one model; rooting changed what an owner could do on a particular phone. Each involved openness, but at a different layer.
Why preserve an obsolete source release?
Old code helps researchers understand how manufacturers adapted Android to the first generation of high-profile devices. It can help investigate hardware support, license obligations and engineering decisions that later disappeared from live download pages. Preservation also lets future developers verify which source corresponded to a particular binary release.
A useful archive needs more than a filename. It should retain the original version description, documented publication date, license notices and a checksum that can detect accidental changes. Those records do not make the software safe for daily use, but they make historical analysis reproducible. The EVO 4G is no longer a supported handset; its source remains part of the record of how Android hardware and open-source obligations developed together.
Does this affect an EVO 4G today?
This is a historical development record, not a recommendation to install old firmware. The EVO 4G no longer receives modern Android security support, and ancient builds should not be used for sensitive daily tasks. Collectors and researchers should work offline where possible and preserve original files and checksums. Explore the 2010 Android archive for the surrounding timeline, or see our current Android guides for supported-device advice.
Archive method and revision
Original URL date: December 3, 2010. Rechecked October 8, 2026 against the same-day Phandroid report and kernel license documentation. This revision separates media and vendor dates, marks missing package metadata NA, replaces the earlier compliance conclusion and combines timing analysis. It is a restored explanation, not an inspection of the original source archive.
