34306/vphone-aio

1 script run the vphone

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 29 minutes ago
Added to GitGenius on September 1st, 2026
Created on February 28th, 2026
Open Issues & Pull Requests: 32 (+0)
GitHub issues: Enabled
Number of forks: 1,134
Total Stargazers: 6,798 (+1)
Total Subscribers: 35 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.1 hours
Mean response time: 7.4 days
90th percentile: 22.8 days
Tracked items: 32

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 9% of issues opened in the past year have been closed. Three people close 50% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 30
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 137 days
Stale 30+ days: 24
Stale 90+ days: 21

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

vphone-aio is a shell script that sets up a virtualized iOS environment on macOS.

The tool automates the deployment of a pre-jailbroken iOS virtual machine with a complete bootstrap environment already installed. It handles the download and assembly of large disk image files split across multiple parts, automatically fetching any missing segments, then merges and extracts them to create a functional iOS installation. The setup process requires disabling System Integrity Protection and configuring kernel parameters before running the main script, after which the virtual machine becomes accessible via VNC for remote interaction.

Adoption suits developers who need a jailbroken iOS testing environment on macOS and have substantial disk space available. The tool requires at least 128GB of free storage and handles the complexity of assembling a large distributed image, making it practical for those who would otherwise need to manually download and reconstruct multiple file parts. The README recommends considering an alternative implementation for ongoing use and better support.

The project appears dormant, with the maintainer explicitly directing new users toward a maintained alternative rather than continuing active development on this version.