For professional technicians
Built for trained repair teams handling customer-owned or otherwise authorized Google Pixel devices.
Authorized Google Pixel service platform
Professional Pixel service,
from one workspace.
GPixel Tool gives technicians a clear Windows workflow for Root, network service, MDM repair, and two-stage Repair Security - with live compatibility checks, credit protection, encrypted payloads, and verified results.
Latest Stable
27.7 MB SHA-256
458260b1f121…
G
Device connected
Pixel 9 Pro
AUTHORIZED DEVICEPixel workspace
OnlineP
Pixel 9 ProConnected · Identity verified
ReadyRRootDevice-bound
NNetworkGuided flow
S1Security 1Protected
S2Security 2Recovery
Compatibility confirmedApproved payload selected by server
100%✓
Verified deliveryEncrypted · device-bound
Pixel 6-1018 qualified targets
015 active servicesPricing is loaded from the live catalog.
0218 model targetsPixel 6 through Pixel 10 families.
03Protected creditsPaid work is captured after required verification.
04Private payloadsAccess is authorized for the job and device.
What is GPixel Tool?
A complete service workspace, not a collection of scripts.
The desktop tool, customer portal, service catalog, compatibility rules, encrypted artifacts, credit ledger, and operation history work together as one controlled system.
Guided from start to finish
The tool identifies the phone, quotes the operation, shows each stage, and records the verified outcome.
Controlled by compatibility
An operation runs only when the connected model, build, security patch, and authorized payload policy agree.
Authorized use only. Use GPixel Tool only on devices you own or have explicit permission to service. It is not intended to bypass ownership, account, or legal controls.
Available operations
One platform for the main Pixel service workflows.
Each operation has its own eligibility, price, progress stages, and verification rules. The desktop confirms the exact quote before work starts.
10 credits
Root
Apply the correct server-authorized Root package for the connected phone, with compatibility and result verification.
- Device-bound payload
- Verified before capture
- Same-device repeat entitlement
EligibilitySupported boot state and exact payload mapping required.
10 credits
Network Service
A guided network-service workflow with device identity checks, protected credit handling, and a recorded result.
- Identity snapshot
- Live operation stages
- Auditable outcome
EligibilityAvailability is confirmed from the connected device snapshot.
25 credits
MDM Repair
Authorized service for eligible devices using validated identifiers and protected operation records.
- Eligibility checks
- Protected identifiers
- Verified completion
EligibilityOnly available for eligible, customer-owned or authorized devices.
15 credits
Repair Security 1
The first security-repair stage: compatibility resolution, protected backups, encrypted RILD delivery, and verified device changes.
- Root required
- Backup before changes
- Optional MDM identity update
EligibilityTwo valid IMEIs and a supported rooted device are required.
20 credits
Repair Security 2
The recovery stage that validates the repair record, restores the protected modem backup, and requests the recovery wipe.
- Linked or standalone case
- Verified restore
- Recovery wipe requested
EligibilityRoot and a valid modem backup are required. User data is wiped.
Simple credit pricing
Know the service cost before you approve it.
Credits are service units held in your account. The connected device is checked and a final quote is shown before an operation can begin.
| Service | First run | Same-device repeat | Expected window |
|---|---|---|---|
| Root | 10 credits | Free | Up to 30 min |
| Network Service | 10 credits | 10 credits | Up to 15 min |
| MDM Repair | 25 credits | 25 credits | Up to 15 min |
| Repair Security 1 | 15 credits | 15 credits | Up to 15 min |
| Repair Security 2 | 20 credits | 20 credits | Up to 15 min |
Public prices are current catalog defaults. Customer-specific pricing may apply; your signed-in quote is authoritative. Explicit confirmation is required, including free repeat operations.
Supported models
Qualified Google Pixel families.
These devices are recognized by the current catalog. Final service availability is always checked against the exact model, build, Android version, security patch, and published mapping.
6
Google
Pixel 6 series
- Pixel 6
oriole - Pixel 6 Pro
raven - Pixel 6a
bluejay
7
Google
Pixel 7 series
- Pixel 7
panther - Pixel 7 Pro
cheetah - Pixel 7a
lynx
8
Google
Pixel 8 series
- Pixel 8
shiba - Pixel 8 Pro
husky - Pixel 8a
akita
9
Google
Pixel 9 series
- Pixel 9
tokay - Pixel 9 Pro
caiman - Pixel 9 Pro XL
komodo - Pixel 9 Pro Fold
comet - Pixel 9a
tegu
10
Google
Pixel 10 series
- Pixel 10
frankel - Pixel 10 Pro
blazer - Pixel 10 Pro XL
mustang - Pixel 10 Pro Fold
rango
!
Pixel 10a is not included in the current shared Pixel 10 Repair Security mapping.
Never use RILD_10.img on Pixel 10a. Run a service only when the desktop tool explicitly confirms an authorized mapping for the connected device.
Repair Security explained
A protected two-stage repair and recovery workflow.
Repair Security is intended for supported rooted devices and trained technicians. Both stages are independently priced and independently verified.
Stage01
Repair Security 1
Prepare, protect, and apply.
The tool checks root and compatibility, creates protected modem and device-information backups, obtains the approved encrypted RILD image, applies the authorized security changes, verifies the result, and reboots normally.
- Requires two valid IMEIs
- Optional MDM PSN/DSN update is included
- Existing approved phone file is accepted only after hash verification
→Linked case and verified backup
Stage02
Repair Security 2
Restore and request recovery wipe.
The tool validates the repair record or standalone backup, preserves recovery copies, restores the modem state, verifies critical changes, and requests the recovery data wipe.
- Can use a linked Stage 1 case or a standalone backup
- Standalone provenance receives a stronger warning
- Success means restore verified and wipe requested
Important: Repair Security 2 wipes user data. Back up the customer’s data before starting. Keep the USB connection stable and do not interrupt the phone after a destructive write begins.
A predictable operation
From USB connection to verified result.
The desktop shows the important decisions and stages while the server keeps a trustworthy job and credit record.
Access your customer portal →- 1Connect and authorizeEnable USB debugging, accept the ADB prompt, and let the tool identify the physical phone.
- 2Check compatibility and quoteThe live catalog checks the exact device snapshot, service policy, entitlement, and credits.
- 3Confirm and follow progressRead the service warnings, approve the quote, and keep the phone connected while stages run.
- 4Verify, record, and rebootMandatory checks determine the result and the portal retains the operation history.
Before you begin
What you need to use GPixel Tool.
Prepare the workstation and phone before reserving credits. A stable connection matters during device writes.
Windows workstation
Windows 10 or Windows 11, 64-bit, with sufficient free disk space for the tool and protected recovery backups.
Reliable data connection
A high-quality USB data cable, working port, Google USB/ADB drivers, and no unstable hub between the phone and PC.
Prepared Pixel device
USB debugging enabled and the workstation authorized on the phone. Some operations require root or a supported boot state.
Active customer account
Internet access, a permitted account, sufficient available credits, and authorization to service the connected device.
Customer data backup
Back up important data before any advanced repair. Repair Security 2 explicitly requests a full recovery wipe.
Exact eligibility match
Do not substitute files manually. The desktop must approve the model, build, patch level, and current artifact mapping.
Security and accountability
Sensitive service files are not ordinary public downloads.
Root and RILD artifacts use private server storage, encrypted delivery, compatibility policies, short-lived authorization, and job/device binding. Operation stages, administrator actions, and credit movements remain traceable.
Authenticated payload chunksDevice and job bindingRotating desktop sessionsImmutable credit ledgerProtected recovery backupsAudited administration
Desktop application
Download GPixel Tool 2.9.0-r22
Current stable release for Windows 10/11, 64-bit.
- File size
- 27.7 MB
- Published
- Jul 30, 2026
- SHA-256
458260b1f1216fbc425d31c148bf2869713551b920910edc3ab2ddf9303a1eeb
Publisher signing is in audit rollout for this build. Windows may show an unknown-publisher prompt; verify the SHA-256 value above before opening the file.
Frequently asked questions
Understand the tool before starting work.
Service availability and the final credit quote are confirmed from the connected phone inside the desktop tool.
What does GPixel Tool do?+
It is a Windows desktop and web platform for authorized Google Pixel Root, network service, MDM repair, and Repair Security operations. It combines device checks, compatible payload delivery, progress, billing, and service records.
Is every listed service available on every listed Pixel?+
No. The model list shows recognized targets. Each operation still requires an exact server match for device identity, build, Android version, security patch, client version, and an active compatibility mapping.
How do credits work?+
Your account has total, reserved, and available credits. The tool displays a quote and asks for confirmation, then reserves the amount during the operation. Required verification must pass before successful paid work is finalized.
Is repeat Root really free on the same device?+
Under the current policy, yes. A successfully rooted physical device receives a zero-credit repeat entitlement for the same Root policy version, even across customer accounts. It still creates a recorded operation and requires confirmation.
Does Repair Security require root?+
Yes. Repair Security 1 and 2 are advanced operations for supported rooted devices. Stage 1 also requires two valid IMEIs, and Stage 2 requires a suitable modem backup.
Will Repair Security 2 erase the phone?+
Yes. Stage 2 requests a recovery data wipe after the verified restore. Back up customer data first. The result records that the wipe was requested because the phone normally leaves ADB during recovery.
Can I use the Pixel 10 shared RILD image on Pixel 10a?+
No. Pixel 10a is excluded from the current shared RILD_10.img mapping. Never choose or copy RILD files manually; wait for an explicit compatibility approval from the desktop tool.
Do I need an internet connection?+
Yes. Authentication, current pricing, compatibility, operation authorization, and protected payload delivery depend on the server. Keep both internet and USB connections stable during work.
Who is allowed to use the platform?+
Professional users working on devices they own or have explicit authorization to service. GPixel Tool must not be used to defeat ownership, account, or legal controls.
Ready to get started?