Video summary

I Installed Android on my iPhone (For Real)

Main summary

Key takeaways

Technology

Goal

Demonstrates installing Android on an iPhone 7 using Project Sandcastle, which enables running Android on some older iPhones via an iOS exploit + boot process.


Prerequisites & Platform Constraints

  • Required device/OS: An iPhone 7 with iOS 13.
    • Mentions there may be a path for iOS 15, but the speaker is unsure and suggests researching.
  • Host environment: The tooling for the Android “beta” workflow relies on macOS or Linux.

Step-by-Step Tech Workflow

  1. Rain jailbreak setup
    • Uses Checkra1n (jailbreak tool).
    • Puts the iPhone into DFU mode.
  2. DFU mode manual process
    • Requires a manual DFU-mode workflow, which the speaker finds frustrating.
  3. Get Cydia
    • Installs/uses Cydia to enable functionality needed for file transfer.
  4. Transfer boot components
    • Uses OpenSSH / SCP to transfer the Linux/Android boot components to the device.
  5. Boot into Pongo OS
    • Boots into Pongo OS (temporary environment) to apply the Android boot image.
  6. Retries and tooling/version changes
    • Initial attempts fail with “failed to transfer image.”
    • The setup eventually succeeds after changing tool/version combinations and retrying.
  7. Works on macOS
    • The final successful outcome happens on macOS, suggesting the procedure is highly sensitive to OS/tool versions.
    • The speaker notes needing to download “bizarre versions” of tooling across different systems.

Outcome: Android Runs, But Is Heavily Limited

  • Android 10 boots
    • The Android UI appears and is slightly customized (icon/layout quirks noted).
  • No Google Play / limited Google services
    • No Google Play Store.
    • Connectivity lacks full Google services.
  • App installation challenges
    • Apps require ADB side-loading.
    • Many installs fail with errors like “no matching ABIs” due to CPU/architecture incompatibility.

Compatibility Analysis: Why Many Apps Fail

  • The iPhone 7 CPU architecture differs from typical Android devices.
    • As a result, most Android ARM native binaries don’t run.
  • Two implied options to improve compatibility:
    • Recompile apps for the iPhone 7 CPU (the speaker does not do this).
    • Use Java-heavy apps, since the Android build includes a Java runtime and some Java apps can work.
  • Missing hardware acceleration
    • GPU-dependent apps, games, and emulators generally fail.

Hardware / Driver Coverage Observations (Many Missing)

  • Fingerprint sensor: not working (no driver support).
  • Camera: not working.
  • Sensors: unclear for accelerometer, but many fail:
    • light sensor, data/data-like sensors, proximity, magnetometer, gyroscope, barometer—reported as not working.
  • Audio / speakers: likely not working.
  • Storage: extremely limited (about 1 GB free).
  • Thermals: device heats quickly (repeatedly noted).

App Testing Results

  • Aurora Store
    • Works as an alternative APK downloader.
    • Described as buggy (e.g., loads forever, hard to browse).
  • General behavior
    • Many apps fail to install or crash.
    • Some apps lead to instability or the system becoming unresponsive.
    • The speaker strongly suspects failures relate to hardware acceleration / GPU usage.
  • Working subset
    • Some “basic” functionality apps work (e.g., simple web/basic behavior).
    • A non-GPU game like Flow Free works.
    • Chess works in the speaker’s “non-computer mode” scenario.

System Behavior & Persistence

  • Android behaves like an ephemeral/live-boot environment:
    • After rebooting, apps can disappear.
    • The speaker sometimes needs to reload Android from a PC after restarting.

In other words, it does not behave like a fully persistent Android installation.


Bottom-Line Review

  • Not recommended, due to:
    • outdated instructions,
    • fragile toolchain/setup requiring old versions,
    • widespread hardware/app breakage.
  • Still, the speaker calls it “pretty cool” because Android runs at all.

Main Speakers / Sources

  • Main speaker: The video presenter (single narrator; no named person provided in subtitles; first-person narration).
  • Primary referenced source/project: Project Sandcastle (developer names not shown in subtitles).

Original video