GSM6 Community

📌 Please login or register to view this link.

wrote:

📌 Please login or register to view this link.

Tue Feb 24, 2026 2:12 pm

📌 Please login or register to view this link.

wrote:

📌 Please login or register to view this link.

Mon Feb 23, 2026 11:46 am

@am

Bro if I downgrade to the July 2025 build, does that mean I need to stay on this build to keep my modified IMEI? Is it not possible to update to latest after that?

you can upgrade later (pixel 7,8 & 9 series only) & you will not lose your imei / cpid

Can I safely update to the latest build (e.g., March 2026 or whatever is current) and if so should I be using manual methods like PixelFlasher OTA or factory image with keep data. Which way should I go so I dont lose my CPID?

Yes you can update by using any method you like. No issues

📌 Please login or register to view this link.

wrote:

📌 Please login or register to view this link.

Mon Mar 09, 2026 7:30 pm

Yes you can update by using any method you like. No issues

Bro I think i have messed something up I was able to keep the changed IMEI after update, however I wanted to make changes to IMEI again on the March 2026 firmware so what i did was I ran the IMEI tool and modified the IMEI again but it failed to change it during process and now both my IMEI are showing 0000000000 and no signal showing.

How can I fix this should I downgrade to July 2025 firmware and try again or something else? And also do I need to apply original IMEI again or can I use the new ones for fixing this IMEI 0000000 and no signal. Please help

My phone is rooted and on march 2026 firmware at the moment I am writing this.

sorry we do not provide help regarding any illegal activity..
though if your imei is 000 you can downgrade to july 2025 build, cpid with original imei from the box.. & then you are good to relock the bootloader & update firmware to 2026 without any issues.

Is it possible to relock the Bootloader after CPID so that I might be able to use banking apps? Please advice

hey which version of android id required for cpid for pixel 9 pro xl or cpid can be performed on latest version 16.0.0 (CP1A.260505.005, May 2026)

i tried everything on the video but my imei is turning 000 and cant fix that

it shows it is okey but i cant fix that; can anyone help?

📌 Please login or register to view this link.

wrote:

📌 Please login or register to view this link.

Sun Mar 22, 2026 12:07 pm

Is it possible to relock the Bootloader after CPID so that I might be able to use banking apps? Please advice

Yes! & its recommended

📌 Please login or register to view this link.

wrote:

📌 Please login or register to view this link.

Sun May 24, 2026 11:24 am

hey which version of android id required for cpid for pixel 9 pro xl or cpid can be performed on latest version 16.0.0 (CP1A.260505.005, May 2026)

July 2025 or older build… you can flash latest after cpid

📌 Please login or register to view this link.

wrote:

📌 Please login or register to view this link.

Mon May 25, 2026 9:11 pm

i tried everything on the video but my imei is turning 000 and cant fix that

► Show Spoiler

IMEIs saved to C:\Users\usetc\Downloads\Pixel Cpid all\imei_list.txt.
Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\adb devices
List of devices attached
57101JEBF05877 device
Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\adb shell su -c dd if=/dev/block/bootdevice/by-name/devinfo of=/data/local/tmp/devinfo.img

Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\adb pull /data/local/tmp/devinfo.img C:\Users\usetc\Downloads\Pixel Cpid all\devinfo.img

Starting flashing process...
Checking connected ADB devices...
Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\adb.exe devices
List of devices attached
57101JEBF05877 device
Rebooting device to bootloader...
Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\adb.exe reboot bootloader

Waiting for device to enter fastboot mode...
Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\fastboot.exe devices

Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\fastboot.exe devices
57101JEBF05877 fastboot
Device is now in fastboot mode.
Flashing devinfo with: C:\Users\usetc\Downloads\Pixel Cpid all\modified_devinfo.img...
Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\fastboot.exe flash devinfo C:\Users\usetc\Downloads\Pixel Cpid all\modified_devinfo.img

Rebooting the device...
Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\fastboot.exe reboot bootloader

Waiting for device to enter fastboot mode...
Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\fastboot.exe devices

Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\fastboot.exe devices

Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\fastboot.exe devices
57101JEBF05877 fastboot
Device is now in fastboot mode.
Setting device configuration...
Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\fastboot.exe oem set_config bootmode factory

Rebooting the device...
Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\fastboot.exe reboot

Waiting for the device to fully boot...
Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\adb.exe shell echo 'ready'
Error: adb.exe: no devices/emulators found
Device is not ready yet, retrying...
Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\adb.exe shell echo 'ready'
Error: adb.exe: no devices/emulators found
Device is not ready yet, retrying...
Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\adb.exe shell echo 'ready'
ready
Device is ready for ADB commands.
Setting IMEI on the device...
Starting to set IMEI1 and IMEI2 via a single ADB shell session...
Opening ADB shell session...
Requesting root access via su...
Sending IMEI1 commands...
Executing: echo 'AT+GOOGSETNV="CAL.Common.Imei",0,"86"
' > /dev/umts_router
Executing: echo 'AT+GOOGSETNV="CAL.Common.Imei",1,"09"
' > /dev/umts_router
Executing: echo 'AT+GOOGSETNV="CAL.Common.Imei",2,"21"
' > /dev/umts_router
Executing: echo 'AT+GOOGSETNV="CAL.Common.Imei",3,"03"
' > /dev/umts_router
Executing: echo 'AT+GOOGSETNV="CAL.Common.Imei",4,"76"
' > /dev/umts_router
Executing: echo 'AT+GOOGSETNV="CAL.Common.Imei",5,"45"
' > /dev/umts_router
Executing: echo 'AT+GOOGSETNV="CAL.Common.Imei",6,"45"
' > /dev/umts_router
Executing: echo 'AT+GOOGSETNV="CAL.Common.Imei",7,"00"
' > /dev/umts_router
Executing: echo 'AT+GOOGSETNV="CAL.Common.Imei",8,"00"
' > /dev/umts_router
Sending IMEI2 commands...
Executing: echo 'AT+GOOGSETNV="CAL.Common.Imei_2nd",0,"35"
' > /dev/umts_router
Executing: echo 'AT+GOOGSETNV="CAL.Common.Imei_2nd",1,"90"
' > /dev/umts_router
Executing: echo 'AT+GOOGSETNV="CAL.Common.Imei_2nd",2,"14"
' > /dev/umts_router
Executing: echo 'AT+GOOGSETNV="CAL.Common.Imei_2nd",3,"09"
' > /dev/umts_router
Executing: echo 'AT+GOOGSETNV="CAL.Common.Imei_2nd",4,"31"
' > /dev/umts_router
Executing: echo 'AT+GOOGSETNV="CAL.Common.Imei_2nd",5,"08"
' > /dev/umts_router
Executing: echo 'AT+GOOGSETNV="CAL.Common.Imei_2nd",6,"09"
' > /dev/umts_router
Executing: echo 'AT+GOOGSETNV="CAL.Common.Imei_2nd",7,"80"
' > /dev/umts_router
Executing: echo 'AT+GOOGSETNV="CAL.Common.Imei_2nd",8,"00"
' > /dev/umts_router
Finalizing the session...
IMEI1 and IMEI2 successfully set on the device!
Starting complete modem operations...
Starting airplane mode toggle with root...
Checking connected ADB devices...
Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\adb.exe devices
List of devices attached
57101JEBF05877 device
Enabling airplane mode with root...
Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\adb.exe shell su -c settings put global airplane_mode_on 1

Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\adb.exe shell su -c am broadcast -a android.intent.action.AIRPLANE_MODE --ez state true
Broadcasting: Intent { act=android.intent.action.AIRPLANE_MODE flg=0x400000 (has extras) }
Broadcast completed: result=0
Disabling airplane mode with root...
Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\adb.exe shell su -c settings put global airplane_mode_on 0

Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\adb.exe shell su -c am broadcast -a android.intent.action.AIRPLANE_MODE --ez state false
Broadcasting: Intent { act=android.intent.action.AIRPLANE_MODE flg=0x400000 (has extras) }
Broadcast completed: result=0
Airplane mode toggled successfully with root!
Opening ADB shell session...
Requesting root access via su...
Sending AT+GOOGBACKUPNV command...
AT+GOOGBACKUPNV operation completed successfully!
Starting SHA operations...
Opening ADB shell session...
Requesting root access via su...
Fetching SHA hash using AT+GOOGGETIMEISHA command...
Received line: AT+GOOGGETIMEISHA
Received line: +GOOGGETIMEISHA:3dfcc61ed7d6341e23e4fbcec04fbff82ae5b817e69b1c865fcccf2446d14da0
Full output from AT+GOOGGETIMEISHA command: AT+GOOGGETIMEISHA
+GOOGGETIMEISHA:3dfcc61ed7d6341e23e4fbcec04fbff82ae5b817e69b1c865fcccf2446d14da0

Processing line: AT+GOOGGETIMEISHA
Processing line: +GOOGGETIMEISHA:3dfcc61ed7d6341e23e4fbcec04fbff82ae5b817e69b1c865fcccf2446d14da0
Retrieved SHA hash: 3dfcc61ed7d6341e23e4fbcec04fbff82ae5b817e69b1c865fcccf2446d14da0
Writing SHA hash to device: 3dfcc61ed7d6341e23e4fbcec04fbff82ae5b817e69b1c865fcccf2446d14da0
Resetting modem...
Rebooting device to bootloader...
Waiting for device to enter fastboot mode...
Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\fastboot.exe devices

Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\fastboot.exe devices

Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\fastboot.exe devices
57101JEBF05877 fastboot
Device is now in fastboot mode.
Setting device configuration...
Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\fastboot.exe oem set_config bootmode normal

Rebooting device from fastboot...
Executing: C:\Users\usetc\Downloads\Pixel Cpid all\platform-tools\fastboot.exe reboot

All SHA operations completed successfully!
All operations completed successfully.

it shows it is okey but i cant fix that; can anyone help?

You firmware build is not supported.. downgrade to july 2025 build or even older build.. & then fix cpid