Question Bootloop while trying to revert from the December update - Google Pixel 6

And yeah, despite the fact that I'm flashing phones since a long time,
I've tried to flash my Pxl6 to the November factory image with adb and fastboot coming from a 2 years old tools pack (adb, fastboot)
- unlock bootloader
- flash recovery image was done
- fastboot reboot ok
- flash radio was done
- fastboot reboot failed
- fastboot reboot restarted
- flash system image fails every time I try trough command line or online with Android Flash Tool (whetever wiping option I choose with the online tool)
when the process reboots to Fasbootd
Code:
Writing 'vendor_boot_a' OKAY [ 0.079s]
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
or
Code:
Writing 'vendor_boot_a' OKAY [ 0.112s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Sending 'super' (4 KB) FAILED (Status read failed (Too many links))
fastboot: error: Command failed
the update process fails despite that fasbootd initiates and appears.
When trying to boot fastboot manually with the device, it's difficult to make it appear but possible.
Bootlooping on starting the OS otherwise.
I've updated to the latest commandline tools from Google but the issue remains.
The driver works ok, the usb cable allows flashing the recovery and the radio, so should not be the issue.
SDK is not installed on the PC.
I'm blocked, can someone help me to even reinstall the december or whatever version ?
I fear it's bricked this time

---

cAnArdtichAud said:
And yeah, despite the fact that I'm flashing phones since a long time,
I've tried to flash my Pxl6 to the November factory image with adb and fastboot coming from a 2 years old tools pack (adb, fastboot)
- unlock bootloader
- flash recovery image was done
- fastboot reboot ok
- flash radio was done
- fastboot reboot failed
- fastboot reboot restarted
- flash system image fails every time I try trough command line or online with Android Flash Tool (whetever wiping option I choose with the online tool)
when the process reboots to Fasbootd
Code:
Writing 'vendor_boot_a' OKAY [ 0.079s]
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
or
Code:
Writing 'vendor_boot_a' OKAY [ 0.112s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Sending 'super' (4 KB) FAILED (Status read failed (Too many links))
fastboot: error: Command failed
the update process fails despite that fasbootd initiates and appears.
When trying to boot fastboot manually with the device, it's difficult to make it appear but possible.
Bootlooping on starting the OS otherwise.
I've updated to the latest commandline tools from Google but the issue remains.
The driver works ok, the usb cable allows flashing the recovery and the radio, so should not be the issue.
SDK is not installed on the PC.
I'm blocked, can someone help me to even reinstall the december or whatever version ?
I fear it's bricked this time
Click to expand...
Click to collapse
You definitely have to wipe to go back. Did you remove the -w from the install bat file?

---

You should update your platform tools and you'll need to format data to go back to the November factory image.

---

Tulsadiver said:
You definitely have to wipe to go back. Did you remove the -w from the install bat file?
Click to expand...
Click to collapse
Uh no, it was the 1st time I was trying to use directly the flash-all script, so no I used the fastboot -w parameter.
Later I tried the flash online tool from Google and I ticked wipe.
Yeah sorry that's not the exact code I used, so yes..w was used.
What are my options? Fastbootd seem broken because flashing fails when rebooting to fastbootd.

---

Edmontonchef said:
You should update your platform tools and you'll need to format data to go back to the November factory image.
Click to expand...
Click to collapse
Yeah thanks I updated them after I had the issue and retried without working.

---

cAnArdtichAud said:
Uh no, it was the 1st time I was trying to use directly the flash-all script, so no I used the fastboot -w parameter.
Later I tried the flash online tool from Google and I ticked wipe.
Yeah sorry that's not the exact code I used, so yes..w was used.
What are my options? Fastbootd seem broken because flashing fails when rebooting to fastbootd.
Click to expand...
Click to collapse
Perhaps you didn't get a good download of your firmware. Try downloading it again.
Edit: usual things, try a different usb port on your pc, try a different pc, use a different cable. Check version. fastboot -- version

---

Tulsadiver said:
Perhaps you didn't get a good download of your firmware. Try downloading it again.
Edit: usual things, try a different usb port on your pc, try a different pc, use a different cable. Check version. fastboot -- version
Click to expand...
Click to collapse
This. Make sure you're using the latest Platform Tools - current version is 31.0.3, Aug '21.

---

I am going to take a wild guess that the reason for the rollback. Is because of the data issues.
If so,
Just flash the November radio image on top of the December update.
"Fastboot flash radio radio.img"
The above is what I did. And it has worked well for me.

---

vandyman said:
I am going to take a wild guess that the reason for the rollback. Is because of the data issues.
If so,
Just flash the November radio image on top of the December update.
"Fastboot flash radio radio.img"
The above is what I did. And it has worked well for me.
Click to expand...
Click to collapse
Yeah but I've already flashed back recovery and radio the OS part is failing

---

V0latyle said:
This. Make sure you're using the latest Platform Tools - current version is 31.0.3, Aug '21.
Click to expand...
Click to collapse
thx. I tried several images but will retry on another port, another cable same PC (only one...)
I have 31.03 command tools

---

funkin' love you guys: ensuring I was on a powered usb port, changing cable made me flash the data/os files
funkin' pixel 6 reverted back to the entire previous rom
funkin Xmas to you guys , #heartWithFingers!

---

vandyman said:
I am going to take a wild guess that the reason for the rollback. Is because of the data issues.
If so,
Just flash the November radio image on top of the December update.
"Fastboot flash radio radio.img"
The above is what I did. And it has worked well for me.
Click to expand...
Click to collapse
I have the Dec update on my P6 unlocked on Verizon but would like to revert back to the Nov one without doing a complete wipe of my phone. Is this what you did?

---

sniff1 said:
I have the Dec update on my P6 unlocked on Verizon but would like to revert back to the Nov one without doing a complete wipe of my phone. Is this what you did?
Click to expand...
Click to collapse
You can't go back without a full wipe.

---

Tulsadiver said:
You can't go back without a full wipe.
Click to expand...
Click to collapse
Because when you unlock the bootloader prior to flashing, the phone is wiped.

---

cAnArdtichAud said:
Because when you unlock the bootloader prior to flashing, the phone is wiped.
Click to expand...
Click to collapse
Even if your bootloader is already unlocked.

---

sniff1 said:
I have the Dec update on my P6 unlocked on Verizon but would like to revert back to the Nov one without doing a complete wipe of my phone. Is this what you did?
Click to expand...
Click to collapse
No. I have the Dec. 15th update and the mid November radio.
If you would like to install the older radios. You will need to download the older factory image and extract the radio image.
Than flash the older radio image with fastboot on your PC.
You need to have the USB devloper checked to use adb/fastboot on your PC.

---

vandyman said:
No. I have the Dec. 15th update and the mid November radio.
If you would like to install the older radios. You will need to download the older factory image and extract the radio image.
Than flash the older radio image with fastboot on your PC.
You need to have the USB devloper checked to use adb/fastboot on your PC.
Click to expand...
Click to collapse
That is just the radio.....not the system.

---

vandyman said:
No. I have the Dec. 15th update and the mid November radio.
If you would like to install the older radios. You will need to download the older factory image and extract the radio image.
Than flash the older radio image with fastboot on your PC.
You need to have the USB devloper checked to use adb/fastboot on your PC.
Click to expand...
Click to collapse
This is exactly what I want to do. I know how to extract the radio image, but not too certain on the fastboot commands to do it

---

Tulsadiver said:
That is just the radio.....not the system.
Click to expand...
Click to collapse
Yes ,just the radio image from November on top of the complete December image.
What I did;
Flash-all (December factory image with the -w removed for no data wipe)
Next, I extracted the November radio image from the November factory image.
Than , fastboot flash radio radio.img.
I know it sounds confusing. Lol..

---

sniff1 said:
This is exactly what I want to do. I know how to extract the radio image, but not too certain on the fastboot commands to do it
Click to expand...
Click to collapse
Fastboot flash radio yourradio.img
Yes the radio command needs to be there after the flash command and before your radio.img.
Very similar to to flashing a boot image,
Example, fastboot flash boot boot.img