πŸ“± Free Twoyi: Android 13 boots in a browser tab, no install

A WHOLE ANDROID 13 IN A TAB β€” AND THE URL IS PULL-PROOF

 

It boots on your own CPU in about ten seconds β€” nothing installed, nothing streamed, nothing rented. One URL works in desktop Chrome on a laptop, a Chromebook, even an Android phone.

 

:link: run.twoyi.app β€” the tab that boots Android Β· :link: twoyi.app β€” the maker’s page, IPA + APK

Quick start β€” 60 seconds:

  1. Open the door above in desktop Chrome β†’ press Start β€” the presets are pre-loaded

  2. The command box takes your own argv: toybox sha256sum /system/build.prop β†’ Android runs it and prints the hash

  3. Hit Boot GPU β†’ a real home screen, 720x1280, hardware-rendered

  4. Hand-roll the boot line: /system/bin/sh -c 'echo hello from mksh; toybox seq 3'

  5. Frame nerd? Add ?framestats to the URL β†’ per-frame stats

  6. Browser menu β†’ Install (or Add to Home Screen on a phone) β†’ a full-screen icon, no store, no signature

Three flavours, one engine β€” Android’s code gets AOT-translated to real native code ahead of time, so nothing is emulated and no JIT ever runs:

where what you get boot
:globe_with_meridians: browser tab AOSP 13 arm64 Β· WebGL2 Β· a fresh system every run ~10s
:red_apple: iPhone / iPad full Android 13 Β· no jailbreak Β· 120fps ProMotion ~2s
:robot: Android phone Android 8.1 / 13 / 17 inside one app Β· no root needed ~1s

Every run is a clean room β€” detonate a sketchy link, park a burner account, fake a location β€” the host device never touches any of it.

The street tricks β€” argv, clean rooms, spoofing, the AI worker
  • :test_tube: The detonation chamber β€” every run starts factory-fresh: open the sketchy download page or APK there first, close the tab, nothing survives

  • :ghost: Burner identity β€” a throwaway Google account inside the tab keeps a separate fingerprint from your real machine; the whole identity dies when the tab closes

  • :compass: GPS, camera, sensors β€” all virtual β€” the maker’s architecture docs give the container a fake location, camera feed and sensor data while your real hardware stays silent (twoyi/twoyi)

  • :robot: Twoyi Twin β€” the AI phone worker β€” one sentence and it opens apps, taps, types inside the sandbox; bring your own key (Gemini, DeepSeek, Qwen, Kimi…) and it asks before paying, deleting or posting

  • :microscope: The X-ray twin β€” Vetro boots unmodified AOSP 15 + microG in a tab the same way and records everything: every request in clear text, drop an APK, read its network behaviour, export HAR/pcap

  • :toolbox: Root inside, soon β€” the maker literally wrote KernelSU; root + a module ecosystem for the sandbox is on the roadmap (β€œForget SuperSU and Magisk β€” you’re talking to the right guy”)

  • :gear: Tuned boots β€” the page ships boot / boot-gpu modes and a 720x1280@240 display config; the GPU path struggles? plain boot still works

The iPhone door today β€” sideloads, sizes, the Android 17 rival
  • :inbox_tray: IPA verified live β€” twoyi.app/ios/ β†’ twoyi_1.2.0_933.ipa (~590 MB β€” the whole Android rides inside) Β· Android 13 Β· iOS/iPadOS 15+

  • :package: The APK door β€” twoyi.app/android/ Β· Android 8.1 / 13 / 17 inside Β· needs ~4 GB free Β· no root, no ADB

  • :key: Install lanes β€” TrollStore = permanent on iOS ≀17.0 Β· SideStore = signs on-device, no computer Β· AltStore = free cert, re-signs every 7 days

  • :thinking: Why β€œno JIT” is the whole trick β€” QEMU/UTM translate code piece by piece at run time (a debugger attached or StikDebug); Twoyi pre-translates everything at build time β†’ seconds to boot on chips from years back

  • :crossed_swords: The Android 17 rival β€” kernarium/releases ships the real-kernel LineageOS 24 IPA on GitHub β€” A14+ chips, two entitlements, heavier boots

  • :brain: The maker β€” github.com/tiann, creator of KernelSU + VirtualXposed; the original container repo lives on, archived (MPL-2.0)

App Store said no. The URL says yes β€” and it always will.