Develop Bugs

January security update?

I received the download on my 5x that's rooted. Will this break root for me?

Yes but you can easily re-root after re-installing TWRP

bg1906 said:
Yes but you can easily re-root after re-installing TWRP
Click to expand...
Click to collapse
I don't get this answer. I'm not able to install the security update on my rooted 5X, it reboots into TWRP and after I manually boot to system nothing happened. Tried it 3 times and still have root access.
Is the only way to get the security update by flashing an entire Android image? Or more specifically, can I update without wiping the phone?

Yeah OTA isn't going to work. You need to manually do it. You will need USB Drivers and ADB/Fastboot files. Create a folder on your desktop called Android and put the ADB files there. Now download the image. The image is an archive file. Extract the contents of archive files (there is one archive inside the original archive file you download), and after you have all the files extracted, modify the flash-all file (.bat if you are on Windows) with a text editor (Notepad) to remove the -w and save. This will prevent a wipe of your device. Connect your phone via USB and reboot to the bootloader. Open the folder you are in and if on Windows hold shift and right click and select Open Command Prompt. This will open a Command Prompt Window at the folder's location. Next type the command fastboot devices and press Enter. If everything is right, a device id will be returned. If that works, then go back to the folder and double click the flash-all.bat (Windows) and this will install the update. Root will be lost as will TWRP recovery. After the install, the phone will attempt to reboot. I always stop the reboot and go back to bootloader. Choose Recovery and go to the default recovery. You will see an Android figure with a red X. Simultaneously press the power and volume up & down buttons together repeatedly until you get the recovery menu (this may take a few times). Wipe Cache. Then reboot and you will have the update. You can then reinstall the latest version of TWRP by going to the TWRP website and downloading the latest version of TWRP. I usually put it in the same folder as the Android files and when it downloads rename it to twrp.img. Make sure you are in the bootloader and then at the command prompt all you need type is fastboot flash recovery twrp.img and this will install TWRP. You can then go to TWRP and flash SuperSU. I use the latest beta 2.66. But read here (http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3) for the details on the various versions of SuperSU Beta. *I take no responsibility for what may/may not happen to your phone as that depends on your level of comfort flashing/rooting etc*
Hope this helps. IF the flash-all gives you an error, you will need to flash the various parts of the update individually. If that happens, follow the instructions here for the update: https://www.androidpit.com/how-to-get-android-m-preview

This is exactly what I was looking for, thanks! Couldn't find it anywhere with Google which btw somehow returns mostly Nexus 5 results even when using "nexus 5x"...
I'll try this later on and reply with the results.

bosbeest said:
This is exactly what I was looking for, thanks! Couldn't find it anywhere with Google which btw somehow returns mostly Nexus 5 results even when using "nexus 5x"...
I'll try this later on and reply with the results.
Click to expand...
Click to collapse
Yes please let me know how this goes

Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Info taken from This thread with the help of dmudd

bosbeest said:
This is exactly what I was looking for, thanks! Couldn't find it anywhere with Google which btw somehow returns mostly Nexus 5 results even when using "nexus 5x"...
I'll try this later on and reply with the results.
Click to expand...
Click to collapse
It's the same process with both phones.

Tomyk89 said:
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Info taken from This thread with the help of dmudd
Click to expand...
Click to collapse
Tried it, worked. Thanks a bunch!
Yaz75 said:
It's the same process with both phones.
Click to expand...
Click to collapse
Still doesn't make sense that you can't search for "5X"

Tomyk89 said:
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Info taken from This thread with the help of dmudd
Click to expand...
Click to collapse
Does this wipe data?

ch.ch1 said:
Does this wipe data?
Click to expand...
Click to collapse
Nope. The fastboot command has to have "userdata" included to do that.
Sent from my Nexus 5X using Tapatalk

ch.ch1 said:
Does this wipe data?
Click to expand...
Click to collapse
No

ch.ch1 said:
Does this wipe data?
Click to expand...
Click to collapse
No
Sent from my Nexus 5X using Tapatalk

ch.ch1 said:
Does this wipe data?
Click to expand...
Click to collapse
Nope!

SlimSnoopOS said:
Nope. The fastboot command has to have "userdata" included to do that.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Not true- the -w flag will wipe userdata when flashing other partitions.
fastboot -w flash system system.img will wipe data
fastboot flash system system.img will not wipe data.

gee one said:
Not true- the -w flag will wipe userdata when flashing other partitions.
fastboot -w flash system system.img will wipe data
fastboot flash system system.img will not wipe data.
Click to expand...
Click to collapse
Oh, I learned something new
Sent from my Nexus 5X using Tapatalk

jhester1967 said:
I received the download on my 5x that's rooted. Will this break root for me?
Click to expand...
Click to collapse
I doubt it will install. The install will simply fail.

Im not so good at this...
So I just copy the 3 img files to the same folder adb is installed and I run the 4 commands? Do I have to install TWRP again? Do I have to root again?
I did the command "adb reboot bootloader" which rebooted my phone in the bootloader home page, but when I did the next command "fastboot flash boot boot.img" I got the msg "<waiting for any devices>"

ch.ch1 said:
Im not so good at this...
So I just copy the 3 img files to the same folder adb is installed and I run the 4 commands? Do I have to install TWRP again? Do I have to root again?
I did the command "adb reboot bootloader" which rebooted my phone in the bootloader home page, but when I did the next command "fastboot flash boot boot.img" I got the msg "<waiting for any devices>"
Click to expand...
Click to collapse
Keep this guide by Heisenberg for reference, it is very helpful when updating firmware or returning to stock. You want to refer to section 10 to update via fastboot.
If going from MMB29P to MMB29Q OTA, flash in fastboot: boot, system, and vendor. Radio and bootloader are unchanged if you are using MMB29P. Recovery does not need to be flashed since you want to keep TWRP.
Yes, you will need to root again in TWRP.

System using 19.9gb on a 32gb pixel xl

Last night i bricked my phone and accidently deleted system partitions i think from slot A and slot B when i was trying to install twrp. I always try to figure out how to fix it from reading helpful guides and without asking questions. I flashed full image a couple of times because i was getting bootloops everytime. In the last try, i flashed full image then gave me a bootloop again. So what i did, i adb sideload ota and it booted fine. Now im rooted and it seems i installed twrp correctly, i currently have nde63v build. At the moment i have supposedly used 22.71gb of 29.70gb.
So can someone let me know what i did wrong or point me out how to get those gbs back please.

ls2power said:
Last night i bricked my phone and accidently deleted system partitions i think from slot A and slot B when i was trying to install twrp. I always try to figure out how to fix it from reading helpful guides and without asking questions. I flashed full image a couple of times because i was getting bootloops everytime. In the last try, i flashed full image then gave me a bootloop again. So what i did, i adb sideload ota and it booted fine. Now im rooted and it seems i installed twrp correctly, i currently have nde63v build. At the moment i have supposedly used 22.71gb of 29.70gb.
So can someone let me know what i did wrong or point me out how to get those gbs back please.
Click to expand...
Click to collapse
I just did a factory reset and it fixed it. I also was stock without twrp though.

seshaz said:
I just did a factory reset and it fixed it. I also was stock without twrp though.
Click to expand...
Click to collapse
I tried factory reset already but still shows system using 19.9gbs.

Have you tried doing a complete full flash of nde63v without installing TWRP or root to see if it goes back to normal?

cambunch said:
Have you tried doing a complete full flash of nde63v without installing TWRP or root to see if it goes back to normal?
Click to expand...
Click to collapse
yes i did a few times, it would just bootloop. Until i sideloaded ota nde63v on top of full system img then it booted fine

ls2power said:
I tried factory reset already but still shows system using 19.9gbs.
Click to expand...
Click to collapse
Mine shows system using 19.9 gigs also. I posted this on another thread as I thought it seemed high but no one said weather it was high or was not so I assumed it was normal to use 19.9 gigs of space on my verizon pixel xl. I"am rooted on the x software but I couldnt get twrp working and I figured what good was TWRP if there was no supersu that was working with it and I decided to wait for TWRP to get out of beta to try again.

ls2power said:
yes i did a few times, it would just bootloop. Until i sideloaded ota nde63v on top of full system img then it booted fine
Click to expand...
Click to collapse
If you are getting a bootloop after flashing a factory image, I would assume it isn't flashing correctly. Can you post the output of what happens when you run the flashall.bat?

cambunch said:
If you are getting a bootloop after factory a factory image, I would assume it isn't flashing correctly. Can you post the output of what happens when you run the flashall.bat?
Click to expand...
Click to collapse
im able to flash every single img, but when i try to flash flashall.bat it doesnt seem to work. I will give it a try once i get home from work. The only thing bugging me is that the system shows using 19.9gb of space.

Mine is only using 6.79GB. Something is definitely off with yours.
Sent from my Pixel XL using XDA-Developers mobile app

Neomage84 said:
Mine is only using 6.79GB. Something is definitely off with yours.
Click to expand...
Click to collapse
yes there is. When you reboot your phone, which slot does it have? And do you have twrp installed and root?

M9guy said:
Mine shows system using 19.9 gigs also. I posted this on another thread as I thought it seemed high but no one said weather it was high or was not so I assumed it was normal to use 19.9 gigs of space on my verizon pixel xl. I"am rooted on the x software but I couldnt get twrp working and I figured what good was TWRP if there was no supersu that was working with it and I decided to wait for TWRP to get out of beta to try again.
Click to expand...
Click to collapse
I fixed it, i flashed full system image while i was on slot A. Now system is using 5.39gb, im on V build.

i have the same problem with a 128GB version not sure whats up but to fix it i just flashed over and over and one of them just worked would be nice to know the cause so i dont have to flash many times to get it to show full space again.

How do you select slot a while stock? I can select it in twrp but need to know how to get stock images to flash to a

theycallmerayj said:
How do you select slot a while stock? I can select it in twrp but need to know how to get stock images to flash to a
Click to expand...
Click to collapse
I figured out how to fix it by selecting slot a through twrp, booting into fastboot and flashing stock images. However, I am curious how it even ended up on slot b when I went from stock to unlocked and simply flashed the factory images. I never intended to switched from a to b.

theycallmerayj said:
How do you select slot a while stock? I can select it in twrp but need to know how to get stock images to flash to a
Click to expand...
Click to collapse
theycallmerayj said:
I figured out how to fix it by selecting slot a through twrp, booting into fastboot and flashing stock images. However, I am curious how it even ended up on slot b when I went from stock to unlocked and simply flashed the factory images. I never intended to switched from a to b.
Click to expand...
Click to collapse
whenever you flash a factory img or an OTA, or any firmware, the slots will switch unless told not to, i believe this is to keep them in sync aka the seamless updates. here is some info on that - http://www.androidpolice.com/2016/1...-partition-changes-and-new-fastboot-commands/
Quick Tip - while in cmdlne for ADB and Fastboot, and fully updated, just type
Code:
adb
to get all the ADB commands available, and likewise for fastboot, just type
Code:
fastboot
And to switch active slots type
Code:
fastboot set_active -a
or
Code:
fastboot set_active -b
. Then to activate slot
Code:
fastboot reboot bootloader
I believe with TWRP installed you have to switch slots in TWRP.
Click to expand...
Click to collapse
Moving on, I found this to be pretty helpful, it's not the exact answer you are looking for, but i think it will come in handy.
All dual-booting credit in this thread goes to hucqym, this wasn't my idea, im just a messenger.
hucqym said:
so I successfully have the dual boot running on my pixel (verizon edition) with the same configuration you are trying (one is NDE63X image rooted and one is NDE63X image stock/unrooted). Here were my steps:
-> dePixel8 to unlock bootloader (because verizon edition pixel)
-> download NDE63X image from google and modified flash_all.sh to flash stock images to both slots manually
using the --slot _a/_b and --skip-secondary flags. Modified scripts below. At this point I confirmed that I could boot to both slots. I also verified bootloader lock/unlock again to make sure it was stock image on both slots
-> TWRP alpha2 to get recovery on both slots
-> with slot _b selected as active in TWRP, i installed the SuperSU v2.78 SR4 zip
-> with slot _a as active in TWRP, installed ElementalX-P-1.00 zip for the kernel patch to pass SafetyNet
voila, I now have non-rooted on slot _a and rooted on slot _b
Note that TWRP is not really a requirement for doing this. I had the same dual boot configuration working with SuperSU v2.78 SR3 rooting one slot directly. The only reason I needed TWRP is so that I can switch slots easily on the device and don't need a cable and a laptop just to switch the bootloader flag
Although, I got this to work it still falls short of what I really wanted to do. For my use-case I would really want an isolated userdata for the two slots so I can use the rooted slot as a complete sandbox. and then perhaps have a shared folder mechanism between the two. ...so if somebody has an idea on this, I'm all ears.
[UPDATE]: Note that the unrooted slot is still limited in the sense that safetynet checks fail and so AndroidPay etc.. that use that API will still not work. This, however, has little to do with the dual boot setup and more because SafetyNet now fails on just unlocked bootloader and we do need it unlocked. On Conchors' suggestion, I installed ElementalX kernel on slotA from TWRP and now my 'otherwise-stock' non-rooted image on slotA passes SafetyNet while slotB is successfully rooted
flash_all_slot-a.sh
Code:
fastboot flash --slot _a bootloader bootloader-sailfish-8996-012001-1608281716.img
fastboot reboot-bootloader
sleep 5
fastboot flash --slot _a radio radio-sailfish-8996-012511-1609191801.img
fastboot reboot-bootloader
sleep 5
#fastboot -w update image-sailfish-nde63x.zip
fastboot update --slot _a --skip-secondary image-sailfish-nde63x.zip
flash_all_slot-b.sh
Code:
fastboot flash --slot _b bootloader bootloader-sailfish-8996-012001-1608281716.img
fastboot reboot-bootloader
sleep 5
fastboot flash --slot _b radio radio-sailfish-8996-012511-1609191801.img
fastboot reboot-bootloader
sleep 5
#fastboot -w update image-sailfish-nde63x.zip
fastboot update --slot _b --skip-secondary image-sailfish-nde63x.zip
Click to expand...
Click to collapse
I switched it up a bit, and to be perfectly honest, the script is easier, this is just an alternate way of doing it
I did this for both slot_a and slot_b (not sure if it is needed for the flrst one, but that is what i did), both ways are correct, this way is much longer, but it gives some control, plus it's a nice learning process as it is pretty easy going.
If you are going to erase, erase first before you start anything, because you know...science.
Code:
fastboot erase boot
fastboot erase cache
fastboot erase system
fastboot erase vendor
the cache partition, i dont remember if this worked or not, I'm too tired to verify
Code:
fastboot flash --slot _b --skip-secondary bootloader "name-of-bootloader.img"
fastboot reboot-bootloader
fastboot flash --slot _b --skip-secondary radio "name-of-radio.img"
fastboot reboot-bootloader
fastboot flash --slot _b --skip-secondary system system.img
fastboot flash --slot _b --skip-secondary boot boot.img
fastboot flash --slot _b --skip-secondary vendor vendor.img
If you want to wipe everything, use the following commands next:
Code:
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot reboot
system.img and userdata.img take time to flash— the command prompt appears to stop. Let it do it's thing, when it's done the cursor will begin blinking again.
All dual-booting credit goes to hucqym; again, not my idea.
Slightly Off Topic -
Has anyone tried this on a specific slot, does it make any difference?) I haven't actually even thought of this till now
something like:
Code:
fastboot erase --slot _(a/b) --skip-secondary userdata
fastboot flash --slot _(a/b) --skip-secondary userdata userdata.img[/B]
theycallmerayj said:
I figured out how to fix it by selecting slot a through twrp, booting into fastboot and flashing stock images. However, I am curious how it even ended up on slot b when I went from stock to unlocked and simply flashed the factory images. I never intended to switched from a to b.
Click to expand...
Click to collapse
ls2power said:
Last night i bricked my phone and accidently deleted system partitions i think from slot A and slot B when i was trying to install twrp. I always try to figure out how to fix it from reading helpful guides and without asking questions. I flashed full image a couple of times because i was getting bootloops everytime. In the last try, i flashed full image then gave me a bootloop again. So what i did, i adb sideload ota and it booted fine. Now im rooted and it seems i installed twrp correctly, i currently have nde63v build. At the moment i have supposedly used 22.71gb of 29.70gb.
So can someone let me know what i did wrong or point me out how to get those gbs back please.
Click to expand...
Click to collapse
I was noticing quite a bit of space missing as well. what i did was boot into the slot I wanted as secondary (do this in TWRP), and i wiped just the system (which includes cache) and reflashed the system.img directly pulled from factory.zip. I noticed twice as much space had been gained then what was actually said to be there. I was a little surprised...it was over 5 gb I had gained while the system only said 2.5ish gb. (perhaps there was a second other_system.img wrapped up in it, I don't know. Then i went back to the primary slot and booted back up.
It's possible I got off course, I'm tired.

flashing a factory image

Can anyone tell me what parts of the factory image should be flashed? Before anyone says use the flash all script, that just doesn't work for me. I use a 5 year old Mac air with terminal for all my adb and fastboot commands. I use the ./ before every fastboot command (required for Mac) and my fastboot is up to date. The flash all.sh command has never worked dating back to my nexus 6p. Not looking to trouble shoot why I can't flash all..... Just want to know which parts are vital to flash as there are a good 20 files in the zip folder when expanded. I know boot, system, and radio are some of the most important. Probably going to flash 7.1.2 and then grab the OTA for 8.0 for it.

318sugarhill said:
Can anyone tell me what parts of the factory image should be flashed? Before anyone says use the flash all script, that just doesn't work for me. I use a 5 year old Mac air with terminal for all my adb and fastboot commands. I use the ./ before every fastboot command (required for Mac) and my fastboot is up to date. The flash all.sh command has never worked dating back to my nexus 6p. Not looking to trouble shoot why I can't flash all..... Just want to know which parts are vital to flash as there are a good 20 files in the zip folder when expanded. I know boot, system, and radio are some of the most important. Probably going to flash 7.1.2 and then grab the OTA for 8.0 for it.
Click to expand...
Click to collapse
There's a great guide Stickied in the general 6p forum by Heisenberg. I always reference that when I'm flashing via fastboot to make sure I'm doing it correctly. I'd start there!
Sent from my Pixel XL using Tapatalk

smallsmx301 said:
There's a great guide Stickied in the general 6p forum by Heisenberg. I always reference that when I'm flashing via fastboot to make sure I'm doing it correctly. I'd start there!
Click to expand...
Click to collapse
Damn....been out of the forums too long and when I'm back it's all pixel stuff. Totally forget about Heisenberg. Thanks

Does the Pixel XL flash the same way in ADB with the same fastboot commands as the Nexus 6P does(boot, recovery, system, radio, bootloader, etc)?

dcillusions77 said:
Does the Pixel XL flash the same way in ADB with the same fastboot commands as the Nexus 6P does(boot, recovery, system, radio, bootloader, etc)?
Click to expand...
Click to collapse
Yes...use latest SDK

galaxys said:
Yes...use latest SDK
Click to expand...
Click to collapse
Ty sir

dcillusions77 said:
Does the Pixel XL flash the same way in ADB with the same fastboot commands as the Nexus 6P does(boot, recovery, system, radio, bootloader, etc)?
Click to expand...
Click to collapse
Yes, they flash the same way, but there are a decent bit of variances. There are many (and duplicate) partitions in the pixel, when comparing it to the older nexus devices.
Besides manually fastboot flashing each image to each partition, you can use the same format that the flash-all.(bat/sh) uses. Here is in short how the script would run......
fastboot flash bootloader bootloader.img
fastboot reboot bootloader
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot -w update image.zip
of course, the names of the files are dependent upon which image you are flashing, but all files names will be in the factory image archive.

noidea24 said:
Yes, they flash the same way, but there are a decent bit of variances. There are many (and duplicate) partitions in the pixel, when comparing it to the older nexus devices.
Besides manually fastboot flashing each image to each partition, you can use the same format that the flash-all.(bat/sh) uses. Here is in short how the script would run......
fastboot flash bootloader bootloader.img
fastboot reboot bootloader
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot -w update image.zip
of course, the names of the files are dependent upon which image you are flashing, but all files names will be in the factory image archive.
Click to expand...
Click to collapse
Ok simple enough thanks??

noidea24 said:
Yes, they flash the same way, but there are a decent bit of variances. There are many (and duplicate) partitions in the pixel, when comparing it to the older nexus devices.
Besides manually fastboot flashing each image to each partition, you can use the same format that the flash-all.(bat/sh) uses. Here is in short how the script would run......
fastboot flash bootloader bootloader.img
fastboot reboot bootloader
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot -w update image.zip
of course, the names of the files are dependent upon which image you are flashing, but all files names will be in the factory image archive.
Click to expand...
Click to collapse
It really is true if you don't use it you lose it. Used to know these commands like my childhood beat friends phone number. Now I suffer from CRS. What makes it worse is on top of heisenburgs tutorials (which I'm back to my N6P) if you just open the flash all file with text editor..... It friggin spells out all the commands you need. Not really sure I felt the need to flash system, boot, modem etc when I could flash update image.zip. Grrrr. I need to start playing around more again.
Anyway the wife gave her S7 to our daughter so she took my pixel (had to set it back to stock for her) and I'm back to my N6P until the pixel 2 comes out.

Flash Question

I rooted my Unlocked xl 2 using a method I found online. Used it a couple of days rooted and decided to go back to stock so....
I downloaded the factory image, ran the flash -all.bat and everything was good. Next I went back to my boot loader to re lock it, ran the command , selected yes.
After I hit yes to re lock the boot loader I got the following error. COULD NOT FIND A VALID OPERATING SYSTEM.
Any help would be greatly appreciated.

skullymullins said:
I rooted my Unlocked xl 2 using a method I found online. Used it a couple of days rooted and decided to go back to stock so....
I downloaded the factory image, ran the flash -all.bat and everything was good. Next I went back to my boot loader to re lock it, ran the command , selected yes.
After I hit yes to re lock the boot loader I got the following error. COULD NOT FIND A VALID OPERATING SYSTEM.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
1. fastboot flashing unlock
2. fastboot flashing unlock_critical
3. Reboot the phone if prompted
4. flash firmware using flash-all script again. Read the results and watch for errors that might explain the problem and which partition (a or b) it is flashing to.
5. fastboot --set-active=b (or a. Just set it to whichever partition the script was not flashing to.)
6. flash firmware with flash-all script again to flash the alternate partition

Ok Thanks Ill give that a try..

skullymullins said:
Ok Thanks Ill give that a try..
Click to expand...
Click to collapse
And don't relock until you are 100 percent certain it is ok. I suggest waiting until you get the next update to be sure. Actually I suggest not relocking it but if you insist then wait and make sure the next update goes ok.

TonikJDK said:
And don't relock until you are 100 percent certain it is ok. I suggest waiting until you get the next update to be sure. Actually I suggest not relocking it but if you insist then wait and make sure the next update goes ok.
Click to expand...
Click to collapse
When I tried the command . fastboot --set-active b i got the unknown command error

skullymullins said:
When I tried the command . fastboot --set-active b i got the unknown command error
Click to expand...
Click to collapse
You rooted your phone with a method you found online??? Hmmmm, that's curious. Hope that didn't do any internal damage. Anyways, when your in fastboot mode, and type in "fastboot devices" do you get your device ID number??

TheSt33v said:
1. fastboot flashing unlock
2. fastboot flashing unlock_critical
3. Reboot the phone if prompted
4. flash firmware using flash-all script again. Read the results and watch for errors that might explain the problem and which partition (a or b) it is flashing to.
5. fastboot --set-active b (or a. Just set it to whichever partition the script was not flashing to.)
6. flash firmware with flash-all script again to flash the alternate partition
Click to expand...
Click to collapse
I told one person that was having trouble also to instead of doing step 4 instead download Deuces bootloop kit and allow it to flash your phone for you because I noticed a few people were not flashing in fastboot properly the pixel is different from the prior phones they are used to there are many more Sig files that were not all getting flashed thoroughly causing issues. Deuces kit does it all perfect and it's pretty easy to set up and go

skullymullins said:
When I tried the command . fastboot --set-active b i got the unknown command error
Click to expand...
Click to collapse
Maybe that command works also. I use
Fastboot --set-active=b

skullymullins said:
When I tried the command . fastboot --set-active b i got the unknown command error
Click to expand...
Click to collapse
Sorry, the previous post is right. You need an = in there.

Pixel 3xl Encryption issue.

So for starters. I was on the latest Android 11 rooted with magisk and LSposed along with GB.
I decided to sideload the Android 12 DP. So i floashed the stock boot image to both slots and then sideloaded 12DP. Everything went fine and i was testing A12. Tried to root A12 with magisk by the standard patch boot.img and fastboot flash to both slots. The phone hung on the bootscreen for like 10 minutes so i figured it best to flash back to A11. Back to BL mode and flashed theboot.img to both slots and then flash-all A11. Hit start when finished and it just flashed the white google screen for a few seconds then back to bootloader. Strange. Tried again, while changing active slots to ensure its flashing the system to both slots. Will not boot. Straight back to bootloader.
I can flash individual partions and i have no errors other than when wiping data it says it cant. Cant remeber exactly the error. But this is where it gets even more weird. I can flash android 9 and have no issues, I can take OTA updates with not issue. I can and am rooted and my phone is back to A11 via OTA. It will not boot if i flash or sideload any other version of Android other than A9. I believe this has something to do with encrytion. My phone was encrypted when i started this whole proccess and i believe thats why i get the error when trying to wipe data. In A9 recovery, when i factory data reset. it wipes with no errors. If i try to factory data reset in A10 or A11 Recovery i get the error E: can't send spi message: Try again .
So in closing, my phone is working and running fine but i can not flash-all any Android version other than A9 and have the phone boot.
So if anyone knows the proper steps to get this phone right, I would greatly appreciate it.
If not, i guess i will only be taking OTA's until i can figure it out.
Happy flashing!
Quick edit
Yes i pass safetynet and all banking apps work.
so is doing anything at all really necessary. I will leave that for the community to decide.
My opinion is, There is something wrong that needs fixing here. But its not crucial.

On A10-11 did you try "fastboot erase userdata" ?

wangdaning said:
On A10-11 did you try "fastboot erase userdata" ?
Click to expand...
Click to collapse
I did and it gives an error. Wish I wrote down the error like I did the other one. It's the same error at the end of flash-all when I don't remove -w

Try fastboot format userdata.

Just to add.... I can flash PixelDust (custom rom) and it boots and works great but can not flash-all or sideload android 10 or 11. Can only flash Android 9 and take OTA's up to Android 11.

Damn, should have caught this before. Your Platform Tools are out of date. Update adb and fastboot to latest.

wangdaning said:
Damn, should have caught this before. Your Platform Tools are out of date. Update adb and fastboot to latest.
Click to expand...
Click to collapse
I wish it were that simple. Unfortunately i actually updated it and also added the Android S Preview SDK and restarted my PC before even attempting this whole thing. And to make sure, just now checked for updates and its up to date.

What do you get with "fastboot --version" ?
I have see it where people have multiple versions on their computer.

wangdaning said:
What do you get with "fastboot --version" ?
I have see it where people have multiple versions on their computer.
Click to expand...
Click to collapse
You may be onto something here.....thoughtts?

And i think i have fixed that part on my PC. This is now what i get. I had that all-in-one tool installed so it made my system wide fastboot/adb look at its program folder instead of my default installation folder. Thats uninstalled and all folders and registry keys associated with it and my system is looking at my android sdk installation folder as it should.
This may very well have been the issue. I haven't tried to flash anything yet as i'm a bit gun shy after this fiasco lol
Maybe i will try flash-all with -w removed to see what happens.

Fastboot erase data?

jjgvv said:
Fastboot erase data?
Click to expand...
Click to collapse
That may likely work now as one of my issues was my fastboot was the wrong version because of the all-in-one tool i had installed. Haven't tried it yet and may not need to loose data if the flash-all command will work past android 9 which it should now thats its using the proper fastboot/adb version.

wangdaning said:
Try fastboot format userdata.
Click to expand...
Click to collapse

jjgvv said:
Fastboot erase data?
Click to expand...
Click to collapse
that finishes wothout any error....good start

is this how -w should work......sidenote, i can now flash-all android 11 and boot to system

Thank you @wangdaning for suggesting checking my fastboot version! That lead me to see i had 2 version and was defaulting to the wrong version. Removing that version and fixing my system path in windows variables fixed my issues. It was fastboot version the whole time. Again thank you @wangdaning!!
Edit to thank all who replied to this thread. I used everyones ideas

Glad you got it working.