How To Guide April 17, 2024 AP1A.240405.002.B1 Global - Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet

[Fentadroid]

Yes, a wipe is required. Also, if you ever boot into the system without them disabled (e.g. after an update without the flags or if the device switches to an unpatched slot), you would be required to wipe to disable them.

So, editing flash-all.bat this way:

fastboot --disable-verity --disable-verification update image-cheetah-t1b3.221003.008.zip

is good only if you already have them disabled...

Maybe, if i want to disable verity and verification for the first time and wipe is mandatory, i can leave the "-w", right?
What happen if i don't wipe? system won't boot?

 

[capntrips]

So, editing flash-all.bat [...] is good only if you already have them disabled...

No, it works even the first time. I was simply noting that you have to remember to do it every time and that you might consider doing it on both slots the first time.

Maybe, if i want to disable verity and verification for the first time and wipe is mandatory, i can leave the "-w", right?
What happen if i don't wipe? system won't boot?

The system will prompt you to wipe data, so there's no need to leave the wipe flag (though it won't hurt anything).

 

[T.A.R.D.I.S.]

I saw your edit in your first post. Did you resolve this? If not, I just wanted to note another user had the exact same error message last month here. The issue ended up being an old version of fastboot on their PATH.

I have last pltforms tools (r33.0.3) , adb and google last drivers versions (on android studio sdk), on w11. I flash the last firmware, bl unlocked and i'm not a newbie too.
I've found a solution to bypass my uncapacity to flash on slot b, so i've posted my solution to help others members

 

[simplepinoi177]

I'm doing the flash-all.bat firmware update and I'm at the point where it's in FastbootD, but my command prompt (not powershell) is "waiting for any device". My phone is being detected in Device Manager as Android Bootloader Interface. I've even unplugged and replugged the cable on both ends. I even went through the trouble of Disabling it in Device Manager and Enabling it right back. I can't get it to detect it.

Should I manually end the script/process? It doesn't seem to have begun writing sparse product_b yet, so I can't imagine it wrecking anything as the phone could still be using the firmware "stuff" that's established still as it should be untouched. Should I reboot to bootloader using the manual selection option?
I've seen many people soft-brick there devices at this stage...

It's unfortunate because I just updated and flashed my wife's P7P so I know what it looks like to go without a hitch!


UPDATE
Okay...crisis resolved... PHEW!!! What a relief. I've seen it go pretty bad for people at that point....
My assumption was right and since no image was extracted and no sparse was read or written, I just manually ended the script/process (command prompt), rebooted directly back to the bootloader, and ran the flash-all.bat again. I gained a bit of confidence in that bet after seeing KyleSEES run into the same thing, but he seemed to just end it and try it again. I think the problem was that I was using the same old command prompt I had used to update my wife's P7P two days ago. I don't know why that freaked it out -- I was hoping by using the same command prompt that did everything without a hitch, I might be able to rub some luck off on this go as well; boy was I wrong -- but apparently when I opened a brand new command prompt, it also went without a hitch this time. Now I'm back up and running and am now re-enabling all the modules and hoping this fixes a lot of my carrier & wifi issues...

 

[badabing2003]

I'm doing the flash-all.bat firmware update and I'm at the point where it's in FastbootD, but my command prompt (not powershell) is "waiting for any device". My phone is being detected in Device Manager as Android Bootloader Interface. I've even unplugged and replugged the cable on both ends. I even went through the trouble of Disabling it in Device Manager and Enabling it right back. I can't get it to detect it.

Should I manually end the script/process? It doesn't seem to have begun writing sparse product_b yet, so I can't imagine it wrecking anything as the phone could still be using the firmware "stuff" that's established still as it should be untouched. Should I reboot to bootloader using the manual selection option?
I've seen many people soft-brick there devices at this stage...

It's unfortunate because I just updated and flashed my wife's P7P so I know what it looks like to go without a hitch!


UPDATE
Okay...crisis resolved... PHEW!!! What a relief. I've seen it go pretty bad for people at that point....
My assumption was right and since no image was extracted and no sparse was read or written, I just manually ended the script/process (command prompt), rebooted directly back to the bootloader, and ran the flash-all.bat again. I gained a bit of confidence in that bet after seeing KyleSEES run into the same thing, but he seemed to just end it and try it again. I think the problem was that I was using the same old command prompt I had used to update my wife's P7P two days ago. I don't know why that freaked it out -- I was hoping by using the same command prompt that did everything without a hitch, I might be able to rub some luck off on this go as well; boy was I wrong -- but apparently when I opened a brand new command prompt, it also went without a hitch this time. Now I'm back up and running and am now re-enabling all the modules and hoping this fixes a lot of my carrier & wifi issues...

I'm surprised (although happy for you), that aborting at that stage it worked,
By that point all of the following are already overwritten

bootloader
radio
boot
init_boot
dtbo
pvmfw
vbmeta
vbmeta_system
vbmeta_vendor
vendor_boot
vendor_kernel_boot

I suppose they were still compatible with the older system / product ...

Considering that the script was expecting the phone to be in fastbootd mode, yet the phone was still in bootloader mode, I suspect if you issued the command:

fastboot reboot fastboot

The phone would have been put to fastbootd mode and the script continued.

Of course this is only a speculation.

I personally don't think the issue is at all related to using the same command prompt again.
Unless somehow in that command prompt, path to another Android platform tools was added.

In any case, great that you got it all sorted out.

 

[simplepinoi177]

I'm surprised (although happy for you), that aborting at that stage it worked,
By that point all of the following are already overwritten

bootloader
radio
boot
init_boot
dtbo
pvmfw
vbmeta
vbmeta_system
vbmeta_vendor
vendor_boot
vendor_kernel_boot

Yeah...it still hadn't done the product, system, system_dlkm, system_ext, vendor, & vendor_dlkm that it does in fastbootd. I think I might have been in trouble if it did any of those before crapping out...

I suppose they were still compatible with the older system / product ...

This is exactly what I was worried about! I was only fairly concerned at ending the process at that point since it wasn't in the middle of doing all the multi-part sparse writing, but I was panicking at the thought that what had already been written wasn't "paired" with the proper accompanying images that is installed in fastbootd and it wouldn't like the older revision versions that were still in place...

Considering that the script was expecting the phone to be in fastbootd mode, yet the phone was still in bootloader mode, I suspect if you issued the command:

fastboot reboot fastboot

The phone would have been put to fastbootd mode and the script continued.

I might have considered that, but I was already in fastbootd mode, not bootloader mode. I was there when roirraW "edor" ehT saw a whole lot of people bootlooping their phone because of messing around in fastbootd mode (they would manually select to reboot while flash-all was still flashing the sparse parts or disconnecting device when in that mode while it was writing) and he thus made that big print warning in the OP. I'm even credited in the OP for the info that flash-all flashes in fastbootd, because when up to the Pixel 5, it wasn't flashing in that mode and it surprised newbies like me.
I never considered you could run any commands in fastbootd mode...! when I first learned of adb/fastboot commands, things were only done in bootloader mode where there weren't any real manual button commands; so, for whatever reason, I had the preconceived misconception that you could only do it in that state. I mean it makes sense one should be able to do in fastbootd mode since you could run adb commands in recovery and TWRP environment...
If I knew, I would certainly have tried to run the fastboot command to reboot directly back into fastbootd instead. It might've been tricky since I had to manually close/stop the command prompt because it was stuck at "waiting for any device", but I might've pulled it off opening a second command prompt and attempting that way...

I personally don't think the issue is at all related to using the same command prompt again.

hmmm...I wonder. I've never dealt with such a fickle phone like the Pixels; initial problems could be out-of-date drivers, if not then it could be out-of-date platform tools, if not then it could be USB-C and it's better to use USB2.0 for some reason, if not then it could be the factory image and bad "partitioning" (why it validates partitions) and that's why you should check the checksum (glad Google includes it.). Something so randomly fickle, I wouldn't be surprised if, for whatever reason, it was re-using an old, already-completed, different adb-server running command prompt that caused the "hiccup". I didn't think much of it because I've done similar in the past (may be not days later necessarily), but

Unless somehow in that command prompt, path to another Android platform tools was added.

I know for sure I have no other platform tools because I've seen too many people (since way back from the Pixel 2 XL days) that have unzipped it in multiple places and gotten confused. Now I only keep one set/folder of it extracted, in one specific location (not in documents, desktop, program files, root C is a good idea but i like mine in a specific place because I organize all my phone stuff in a specific spot [ocd mindset]), and I delete it whenever I update platform tools and/or when I want peace of mind and want to extract a fresh folder of it.

I'm surprised (although happy for you)....In any case, great that you got it all sorted out.

Thank you. I am too...it's such a relief because I hate dealing with soft-bricks; I go into panic mode. At least it's better than back with the original Motorola Droids & Galaxy S's.... When I came to the Pixel, I was so happy to see how Google set up bootloader mode and the ability to apply factory images without wiping the device! You could even resize/reflash specific partitions/images! All you could do with the og Motorola Droids and old Samsung Galaxy's were to apply the whole factory images and hope you backed everything up and can apply the backups because everything would be wiped!

 

[slubgob]

I have a Google unlcoked phone. Previously rooted on the October update.

Went to update to November, and flashed the Verizon update rather than the unlocked because I'm on Verizon and wasn't thinking. Followed the guite, including removing -w, turning off Magisk modules etc. Booted up fine. Did not apply the patched boot image as I realized my mistake before that step.

So, I'm guessing it's probably a good idea to use the non-branded factory image. And I'm guessing if I booted OK, I'm probably good to just flash again using the correct images.

But I wanted to check in first and see if anyone has made a similar error in the past and make sure that I haven't really made a big mistake, or would be making a big mistake if I flashed again.

 

[Homeboy76]

I have a Google unlcoked phone. Previously rooted on the October update.

Went to update to November, and flashed the Verizon update rather than the unlocked because I'm on Verizon and wasn't thinking. Followed the guite, including removing -w, turning off Magisk modules etc. Booted up fine. Did not apply the patched boot image as I realized my mistake before that step.

So, I'm guessing it's probably a good idea to use the non-branded factory image. And I'm guessing if I booted OK, I'm probably good to just flash again using the correct images.

But I wanted to check in first and see if anyone has made a similar error in the past and make sure that I haven't really made a big mistake, or would be making a big mistake if I flashed again.

What mistake?
You have a Google Pixel 7 Pro with an unlockable bootloader, and the bootloader is unlocked.

Your carrier is Verizon.

You can use the Verizon or Global November 2022 factory image.

You've already flashed the Verizon November 2022 factory image, so just stay with it this month. If you want to root it, just patch the init_boot.img and flash it: fastboot flash init_boot magisk_patched...img

Next month flash the Global factory image. Then you'll know which factory image works best for you.

 

[simplepinoi177]

I have a Google unlcoked phone. Previously rooted on the October update.

Went to update to November, and flashed the Verizon update rather than the unlocked because I'm on Verizon and wasn't thinking. Followed the guite, including removing -w, turning off Magisk modules etc. Booted up fine. Did not apply the patched boot image as I realized my mistake before that step.

So, I'm guessing it's probably a good idea to use the non-branded factory image. And I'm guessing if I booted OK, I'm probably good to just flash again using the correct images.

But I wanted to check in first and see if anyone has made a similar error in the past and make sure that I haven't really made a big mistake, or would be making a big mistake if I flashed again.

Normally you want to use the firmware that's made for the carrier you're on, so yes, the Verizon version of the firmware. They're interchangeable, just usually some tweaks/optimizations for particular carriers that they weren't able to integrate into a single global image this month.


It will affect it while it's unhidden. Always re-hide it when done. Of course, I don't unhide mine the way I update.

you should consider keeping and continue flashing the Verizon images...
As stated by roirraW "edor" ehT above, there are "some tweaks/optimizations for particular carriers" that are included in them....it might be helpful...
it's why I went ahead and even dirty flashed the Verizon image over the global one I had inadvertently flashed first....

 

[masri1987]

so i disabled verity and flashed the kernel using kernel flasher now i'm getting system corrupt error msg.
been a while since i've been doing this so i know i messed up, not sure where, i flashed to the mounted slot :\

 

[capntrips]

so i disabled verity and flashed the kernel using kernel flasher now i'm getting system corrupt error msg.
been a while since i've been doing this so i know i messed up, not sure where, i flashed to the mounted slot :\

Did you disable both verity and verification? Do you have the kernel flash log?

 

[masri1987]

ah, i did not disable verification. just verity, thanks.

 

[n:o:more]

Hello.
If I only unlock the bootloader, do I stop receiving OTAs automatically?

Thnks

 

[Lughnasadh]

Hello.
If I only unlock the bootloader, do I stop receiving OTAs automatically?

Thnks

You should still receive them.

 

[amtrak23]

I just unlocked the bootloader and was about to download the factory image when I noticed I have the Verizon build on the phone (TD1A.221105.003). I bought the Unlocked version from the Google store, so did I get sent the wrong version or did it do an OTA and update it to that at some point?

I set the phone up when I initially received and used it for a few days, but wiped it soon after.

 

[simplepinoi177]

I just unlocked the bootloader and was about to download the factory image when I noticed I have the Verizon build on the phone (TD1A.221105.003). I bought the Unlocked version from the Google store, so did I get sent the wrong version or did it do an OTA and update it to that at some point?

I set the phone up when I initially received and used it for a few days, but wiped it soon after.

How long have you had the phone?
Do you run your phone on a Verizon line? Or run on their MVNO like Xfinity, Total Wireless, Spectrum Mobile, etc.?

I'm thinking, at the very least, you don't mistakenly have a Verizon Pixel that they give out on their contract as you would have their bloatware and would have been able to unlock the bootloader -- so at least there's that...! Depending on how long you've had your phone and when you unlocked your bootloader, maybe it did do the November OTA, and somehow recognized you were on Verizon's line and gave it that image -- although I can't imagine it being easy to miss your phone doing a full OTA update automatically without any prompt on your part.
But, if you are on a Verizon line, then being on TD1A.221105.003 would be more helpful and apply to your phone anyway. So I can't imagine there's anything to be concerned about. The only concern would be if you purchased your phone through the Google Store, and either they sent you a Verizon variant or somehow locked down your bootloader for being on Verizon's line -- which has never happened before -- and in any case you weren't able to unlock the bootloader on your phone. If that were the case, that would be the only drawback.
But if you're still curious/concerned, I would run your IMEI through IMEI checkers and/or Verizon's BYOD (Bring Your Own Device) IMEI checker and it should display what variant your IMEI is.

 

[whitewallman]

Hello,
This is probably a noob question, but what is the advantage of the optional flashing of 2nd slot? I never have in the past. I just flash the active slot and root.
Thanks.

 

[Lughnasadh]

Hello,
This is probably a noob question, but what is the advantage of the optional flashing of 2nd slot? I never have in the past. I just flash the active slot and root.
Thanks.

It just makes sure that the inactive slot is bootable in case something happens that makes your current slot unbootable. Also, if you flash the firmware to your inactive slot and boot into that, then you know your former current slot is also bootable.

 

[whitewallman]

It just makes sure that the inactive slot is bootable in case something happens that makes your current slot unbootable. Also, if you flash the firmware to your inactive slot and boot into that, then you know your former current slot is also bootable.

Thank you! And to clarify, I don't root the 2nd slot, correct?

 

[Lughnasadh]

Thank you! And to clarify, I don't root the 2nd slot, correct?

You don't need to. Some like to root both slots but I prefer to have my inactive slot unrooted just to eliminate any possibilities of a bootloop caused by a Magisk mod or the like.