Does this method require Shizuku or the Root My Pixel APK?

No. This GSM6 Pixel Tool Pro function uses the phone's authorized ADB connection and the tool's automated supported-build workflow. It does not require Shizuku pairing or manual Root My Pixel installation.

Does GSM6 Pixel Tool Pro support every build for Pixel 6 through Pixel 11?

No. Only exact codename and complete build combinations in the compatibility table are supported. A listed model running another monthly or carrier build must be treated as unsupported.

How long does the locked-bootloader root take?

The automated root stage normally takes about one to two minutes on a compatible device after detection and resource preparation. Network speed, driver state, and the phone's response can increase the total time.

Does this operation unlock the bootloader or intentionally wipe the phone?

The workflow is designed for listed builds while the bootloader remains locked and does not use the standard bootloader-unlock flow. Rooting is still a low-level modification, so important data should be backed up.

What should I do when my build is not listed?

Do not use a profile for a similar build and do not downgrade blindly. Record the codename and complete build ID, then wait for confirmed support or contact GSM6 Support.

How do I confirm my phone's codename and build?

You do not need to guess. Connect the phone, accept its USB debugging prompt, and let GSM6 Pixel Tool Pro read the codename and full build ID. Both values should match the same row in the compatibility table.

Can I root a Google Pixel without unlocking its bootloader?

GSM6 Pixel Tool Pro can root the exact locked-bootloader builds listed in this guide. Support depends on the phone's codename and complete build ID, so the same Pixel model on another update may not be compatible.

Do I need to download firmware or patch a boot image first?

Not for this supported-build workflow. The tool identifies the connected phone and prepares the matching resources automatically. You should not supply a boot image from another device or a similar-looking build.

Why does the tool say my Pixel build is unsupported?

Usually the complete build ID does not match an available profile, even if the model itself appears in the table. Check every character of the build number and do not force a profile intended for another monthly release.

Will a Google Pixel update remove root or change compatibility?

It can. An Android update changes the build and may remove root or require a new supported profile. Check the compatibility table before updating and again before trying the root operation on the new build.

What should I check if GSM6 Pixel Tool Pro cannot see my phone?

Make sure USB debugging is enabled, unlock the phone, accept the computer's authorization prompt, and use a data-capable cable. It also helps to confirm that the Google USB or ADB driver is working and that only one Android device is connected.

Is a paid GSM6 account required for locked-bootloader root?

Yes. Locked-bootloader root is a paid Tensor operation. You can create and sign in to an account normally, but the server will approve the operation only while the account has an active Pixel Tool Pro plan.

Can I use the same supported file on a different Pixel model?

No. Resources are matched to a specific codename and build. Even closely related Pixel models must use their own confirmed profile; using another model's files can leave the phone unstable or unable to start correctly.

Does the Android version alone tell me whether my Pixel is supported?

No. Android 17 is shown to make the table easier to understand, but compatibility still depends on the exact build ID, device codename, and matching Kernel KMI. All of those details should agree before you continue.

GSM6 Pixel Tool Pro: Pixel 6–11 Locked Bootloader Root

GSM6 Pixel Tool Pro can root the exact Android 17 builds listed below on Google Pixel 6 through Pixel 11 devices while the bootloader remains locked. Connect an authorized phone over ADB, let the tool identify its codename and complete build number, and start Root (Locked Bootloader) only when the server confirms an exact supported profile.

This is not the earlier Root My Pixel and Shizuku method. It does not require Shizuku pairing, installing the Root My Pixel APK or manually entering shell commands. On a compatible phone with a stable connection, the tool normally completes its automated stage in about one to two minutes. Detection, downloads and the phone’s response can make the total time longer.

Exact-build support is mandatory. A model appearing below does not mean that every firmware release for that model is compatible. The codename and complete build ID shown by the tool must match a listed entry exactly.

Quick compatibility answer

Question	Answer
Which phones are covered?	Listed Pixel 6, 7, 8, 9, 10 and 11 series phones, plus Pixel Fold and Pixel Tablet.
Is Android 17 alone enough?	No. The codename and complete build ID must also match one row below.
Does it unlock the bootloader?	No. This workflow is specifically for the listed builds with the bootloader still locked.
How does the phone connect?	Through an authorized USB debugging connection over ADB.
How long does it take?	The automated root stage normally takes about one to two minutes after detection and resource preparation.
Is there a tested example?	Yes. The first-party Pixel 7 Pro (`cheetah`) result is documented further down this page.

What you need before starting

A supported Google Pixel running one of the exact builds in the table below.
A Windows computer with the required Google USB/ADB driver working correctly. Google’s Android Debug Bridge documentation explains the standard ADB connection and authorization process.
Developer options and USB debugging enabled on your own or an authorized device.
The phone unlocked and the computer’s ADB authorization prompt accepted.
A reliable data cable, sufficient battery charge and a backup of important data.
A valid GSM6 Pixel Tool Pro account and paid access for this operation.

Rooting changes the device’s security state and can affect updates, banking applications, warranties and data availability. Google’s Play Integrity documentation explains that a rooted or otherwise compromised device may not receive a passing device-integrity verdict. A failed root attempt can also cause a reboot or kernel panic. Use this workflow only on a device you own or are authorized to service.

Direct ADB workflow

Open GSM6 Pixel Tool Pro and connect the powered-on phone by USB.
Accept the USB debugging authorization on the phone when Android asks.
Allow the tool to read the model, codename and full build ID.
Select Root (Locked Bootloader). The tool checks the connected device against the server-side compatibility profile before continuing.
If the exact build is supported, keep the phone connected while the tool prepares the matching resources, performs the operation and verifies the result.
Wait for the completion message, then confirm that the selected supported root manager is installed and opens normally.

If the tool reports that the build is unsupported, stop. Do not choose another model, substitute a nearby monthly build or downgrade blindly. Compatibility is tied to the listed build and kernel interface, not only to the marketing model name or Android version.

Supported models and builds

The following compatibility list applies to the locked-bootloader root function described on this page. It should not be used as a compatibility list for other root tools or other GSM6 Pixel Tool Pro operations.

This is a first-party compatibility record prepared from the profiles supplied for GSM6 Pixel Tool Pro. A Tested mark means that the developer’s test record identifies that exact profile as working; it does not extend to a different build on the same model. The photographed Pixel 7 Pro result below provides the on-device example available for this publication. This list was last reviewed on October 5, 2026.

Device	Codename	Supported builds (with links)	Android Version	Kernel KMI	Tested
Pixel 11	`cubs`	`CD1A.260618.001.C2`	Android 17	`android16-6.12`	✅
Pixel 11 Pro	`grizzly`	`CD1A.260618.001.C2`	Android 17	`android16-6.12`	✅
Pixel 11 Pro XL	`kodiak`	`CD1A.260618.001.C2`	Android 17	`android16-6.12`	✅
Pixel 11 Pro Fold	`yogi`	`CD1A.260618.001.C3`	Android 17	`android16-6.12`	✅
Pixel 10	`frankel`	`CP2A.260705.006`	Android 17	`android15-6.6`	✅
Pixel 10 Pro	`blazer`	`CP2A.260705.006`	Android 17	`android15-6.6`	✅
Pixel 10 Pro XL	`mustang`	`CP2A.260705.006` `CP2A.260805.005`	Android 17	`android15-6.6`	✅
Pixel 10 Pro Fold	`rango`	`CP2A.260705.006`	Android 17	`android15-6.6`	✅
Pixel 10a	`stallion`	`CP2A.260705.006` `CP2A.260805.005`	Android 17	`android14-6.1`	✅
Pixel 9 Pro Fold	`comet`	`CP2A.260705.006`	Android 17	`android15-6.1`	✅
Pixel 9 Pro	`caiman`	`CP2A.260705.006`	Android 17	`android15-6.1`	✅
Pixel 9 Pro XL	`komodo`	`CP2A.260705.006`	Android 17	`android15-6.1`	✅
Pixel 9	`tokay`	`CP2A.260705.006` `AD1A.240905.004` (unavailable)	Android 17	`android14-6.1`	✅
Pixel 9a	`tegu`	`CP2A.260705.006`	Android 17	`android14-6.1`	✅
Pixel 8 Pro	`husky`	`CP2A.260705.006`	Android 17	`android14-6.1`	✅
Pixel 8	`shiba`	`CP2A.260705.006`	Android 17	`android14-6.1`	✅
Pixel 8a	`akita`	`CP2A.260805.005`	Android 17	`android14-6.1`	✅
Pixel 7a	`lynx`	`CP2A.260705.006`	Android 17	`android14-6.1`	✅
Pixel 7 Pro	`cheetah`	`CP2A.260705.006`	Android 17	`android14-6.1`	✅
Pixel 7	`panther`	`CP2A.260705.006` `BP2A.250705.008`	Android 17	`android14-6.1`	✅
Pixel 6a	`bluejay`	`CP2A.260705.006` `CP1A.260405.005`	Android 17	`android14-6.1`	✅
Pixel 6	`oriole`	`CP2A.260705.006`	Android 17	`android14-6.1`	✅
Pixel 6 Pro	`raven`	`CP2A.260705.006`	Android 17	`android14-6.1`	✅
Pixel Fold	`felix`	`CP2A.260605.012` `CP2A.260705.006`	Android 17	`android14-6.1`	✅
Pixel Tablet	`tangorpro`	`BP1A.250405.007` `CP2A.260705.006`	Android 17	`android14-6.1`	✅

The tested marker records support for the listed profile; it is not a guarantee for a different build, modified system or damaged device. Check this page again after installing an Android update because a new build ID requires its own compatible profile.

The Android version and Kernel KMI columns describe different things. Android 17 is the user-facing operating-system release in this table. A KMI label such as android14-6.1 identifies the kernel interface branch used by that build, so its number does not need to match the Android version shown beside it.

Tested Pixel 7 Pro result

GSM6 Pixel Tool Pro completing locked-bootloader root on a Google Pixel 7 Pro cheetah — A successful Pixel 7 Pro (`cheetah`) run: the tool checks the connected build, obtains the matching resources, performs the root stage, verifies access and installs the selected supported manager.

The screenshot is an example of a successful test, not a promise that every Pixel 7 Pro is compatible. Confirm the build displayed on your own phone before starting.

When the tool refuses to continue

An unsupported response is a safety stop, not a connection shortcut to bypass. Check the following:

The phone’s codename and complete build string match the same table row.
USB debugging is enabled and the phone has authorized the current computer.
Only one target Android device is connected.
The cable supports data and the ADB driver is working.
The GSM6 account is signed in and has an active plan for paid Tensor operations.
Security software or a firewall is not blocking the tool’s required server request.

Do not flash or install a resource intended for another codename or build. If identification is correct but the build is not listed, wait for an explicitly compatible profile or contact GSM6 Support with the model, codename and complete build ID.

For downloads, feature access and Windows setup requirements, see the GSM6 Pixel Tool Pro product page.