A recently updated GitHub repository, hatsunemiku-ai/google-one-tools, enables users to probe and trigger Google One subscription offers not publicly available in their region — including AI Plus, AI Pro, and Ultra 30TB plans. The toolkit uses Frida-based code injection into the Google One app process on rooted Android emulators to scan available subscription offers and launch Google Play billing screens. It does not automate purchases or bypass payments. While technically sophisticated, its use may consume free trial eligibility, and it operates outside Google’s intended access model.
The project is not an exploit of Google’s infrastructure but leverages debug-level access to Android’s in-app billing system. It is designed for use with emulators such as MuMu (Android 12, x86_64), requiring root access, a logged-in Google account, Google One and Play Store apps installed, and strict Frida versioning (16.7.19 recommended).
How the toolkit works
The toolkit injects JavaScript code via Frida into the Google One app process on an Android emulator, using the Play BillingClient API to query available subscription offers — including free trials, introductory pricing, and region-locked SKUs. Scripts such as scan_all.py scan all 70 candidate SKUs, returning structured JSON data on pricing, trial availability, and tokens. The launch_checkout.py script can trigger the native Google Play billing interface for any valid SKU, but does not confirm the subscription.
All scripts are self-contained and require only Python 3.9+ and Frida 16.x. The core logic is abstracted into ultra0_core.py, making the toolkit portable across machines. Diagnostic tools like probe_env.py verify Frida stability, Java bridge functionality, and Play Store liveness — critical because Frida 17.x breaks Java interoperability on MuMu and similar emulators.
Users must run scripts via py (not python) on Windows, as the default python command may be a Microsoft Store placeholder. The toolkit connects to devices via ADB, with automatic root retry and frida-server version matching.
Targeted subscriptions and regional availability
The documented SKUs reveal a tiered structure beyond standard Google One storage. These include:
- AI Plus (400GB):
g1.play.helium, often with 12/6/3/1-month free trials - AI Pro (5TB):
g1.2tb.ai.subs_variant, with multi-phase trials (e.g., 12+6+6+6 months) - Ultra 20TB:
g1.play.20tb, available based on account eligibility - Ultra AI Pro (30TB):
g1.play.ai.proorg1.30tb, rarely available for trial - Discounted annual plans: e.g.,
g1.2tb.3months_ip_85p.acq, offering reduced pricing for the first three months
Free trials are typically tied to SKUs with play prefixes or .eft suffixes. The g1.30tb SKU has been withdrawn from most regions, though users may still attempt to access it via the toolkit. Availability varies by region, account history, and backend entitlements.
The repository includes multi-region scan results (scan_result_*.json) and a generated SKU-清单.md with price comparisons, including RMB conversion.
What it means
For UK, UAE, US, and Kazakhstan-based developers and businesses, this toolkit reveals how regional feature rollouts in cloud services can be probed using client-side debugging tools. Google controls access via backend entitlements and SKU availability, but client apps may contain latent functionality accessible through instrumentation.
The method does not breach Google’s payment systems but repurposes legitimate Android debugging capabilities. It operates at the edge of permitted API use — launching billing flows without completing them. This raises questions about how cloud providers enforce access control when client apps include unused or region-gated features.
Organisations using Google Workspace or Google One should note that while the toolkit does not compromise data, it could lead to unauthorised trial usage or billing if applied to shared or managed accounts. Enterprises should restrict rooted environments, emulator usage, and ADB access, particularly on devices with corporate accounts.
The toolkit also reflects growing interest in AI-integrated cloud storage. Google appears to be testing these tiers selectively, and unofficial tools like this offer early visibility into product direction — though not a path to cost savings.
Its primary utility is reconnaissance: mapping Google’s subscription architecture across regions. It cannot grant permanent free access or bypass payment requirements. The repository maintainers do not claim affiliation with Google, and the project remains a community-driven exploration of Android’s billing ecosystem.