Develop Bugs

[Q] Blinking Android Error Screen

I installed the new update on my rooted phone accidentally and it went into a bootloop. I went into recovery mode and clicked erase cache, but my phone died before it was done erasing. Now whenever I start my phone after the ASUS loading screen, and sleeping android with a red warning signal and the text 'ERROR' start flashing every three seconds. I can get to the bootloader screen fine, but when I click recovery mode and the phone restarts, its just shows the blinking android error screen and I can get the recovery mode option by pressing power+up.
When plugged into my computer, adb doesn't recognize a device is connected (I have all the drivers). So I'm stuck right now.
Please any help would be greatly appreciated!

Same thing happened to me, finally while in the bootloader I used fastboot to restore it, I used the big ZIP file from Asus website and did a fastboot sideload of it

fastboot?
How do I go into fastboot from bootloader?
Thanks!

You are in the bootloader, it should display "waiting for fastboot command" or something like this, in a command prompt on your PC type "fastboot devices" and your devive should appear there.

Next
Magister54 said:
You are in the bootloader, it should display "waiting for fastboot command" or something like this, in a command prompt on your PC type "fastboot devices" and your devive should appear there.
Click to expand...
Click to collapse
kk perfect it shows my device, what do I exactly type to sideload the zip? I placed the zip file in the adb folder. Do I type 'adb sideload xxx.zip' ?

argh no you can only sideload from ADB, you must go into recovery to use adb sideload, you cannot use it from fastboot
In recovery mode you have to select "apply update from ADB" first

Magister54 said:
argh no you can only sideload from ADB, you must go into recovery to use adb sideload, you cannot use it from fastboot
In recovery mode you have to select "apply update from ADB" first
Click to expand...
Click to collapse
From bootloader I go to recovery mode, it restarts goes to the error screen, but when I press power+up nothing happens. The error screen just keeps blinking. If I can just get into recovery mode ugh

G0BI said:
From bootloader I go to recovery mode, it restarts goes to the error screen, but when I press power+up nothing happens. The error screen just keeps blinking. If I can just get into recovery mode ugh
Click to expand...
Click to collapse
Ok, it took me a few minutes to get into stock recovery, too! From bootloader, boot into recovery. Wait for the "installing update" screen to turn to Android error bot. Then hold down power button and quickly press volume up and then release both buttons at the same time! If done correctly, you'll successfully boot into stock recovery. If not, keep trying! It can take a while to get the timing right. Stock recovery on this device is very annoying!

Blinking Error Screen
rlaw said:
Ok, it took me a few minutes to get into stock recovery, too! From bootloader, boot into recovery. Wait for the "installing update" screen to turn to Android error bot. Then hold down power button and quickly press volume up and then release both buttons at the same time! If done correctly, you'll successfully boot into stock recovery. If not, keep trying! It can take a while to get the timing right. Stock recovery on this device is very annoying!
Click to expand...
Click to collapse
So the blinking Error screen isn't a problem? I've gotten into stock recovery before pretty easily, but the error screen wasn't blinking when I got in.

G0BI said:
So the blinking Error screen isn't a problem? I've gotten into stock recovery before pretty easily, but the error screen wasn't blinking when I got in.
Click to expand...
Click to collapse
No, it's not a problem! I thought it was as well, no worries - easy mistake to make, especially since getting into recovery mode from that screen can be tricky!

Easy way
Works with problems regarding wipe cache sudden hang or reload and showing android robot with "error" message + no recovery options avilable.
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
get zenfone 2 into fastboot mode (volume + and power) and connect to your windows machine (usb)
install adb drivers and 15 sec package from the link
now go to c: drive and find the abd folder
in that drag fastboot and drop in command prompt *(administrator)
now type fastboot device
you sholud see a device
then type
1) fastboot erase cache
2) fastboot reload
now phone will restart and show error then remove usb cable and switch off the phone
after 10 sec turn on the phone and you will be back...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

@varunanduri.......... You are a GOD! Nothing from the web helped me except this comment.

Hello.
I need your help.
I bought this phone (Asus Zenfone 2 ZE551ML 4GB/32GB 1.8Ghz) recently on online store. It is CN version but it already came with WW firmware, but not the latest (I believe it was WW 2.20.40.90 but I'm not sure).
Then I tried to update to the latest WW version 2.20.40.139 by putting firmware zip file from asus site in internal memory. The phone recognized this update and started to upgrade. When it reboot, I got an error of a blinking droid with the word "Error" below, and the phone doesn't boot anymore.
I can get to fastboot mode, but no to recovery mode. When trying to enter recovery, I got some errors (cannot mount /cache...) and it goes back to the blinking droid.
I cannot insert images and urls so the text errors include E:failed to mount /cache (Invalid Argument) various times
In fastboot mode I tried erase cache, format cache, format userdata, flashing latest WW recovery, boot, fastboot and system, but nothing resolved issue of blinking droid with error.
I tried other how to that uses a CWM recovery and I can get to that recovery, can clean and wipe, tried installing asus zip firmware from external sd (WW and CN) but without success (I believe it had CN recovery SKU but WW firmware -is this possible?). After rebooting the phone is still in the same error (blinking droid).
Here is fastboot messages (format userdata gave an error):
Code:
C:\adb>fastboot devices
F5AZFG27Z395 fastboot
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11882 KB)...
OKAY [ 0.610s]
writing 'recovery'...
OKAY [ 0.470s]
finished. total time: 1.080s
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (11870 KB)...
OKAY [ 0.610s]
writing 'boot'...
OKAY [ 0.450s]
finished. total time: 1.060s
C:\adb>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14824 KB)...
OKAY [ 0.700s]
writing 'fastboot'...
OKAY [ 0.460s]
finished. total time: 1.170s
C:\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 1.220s]
sending sparse 'system' (524056 KB)...
OKAY [ 18.310s]
writing 'system'...
OKAY [ 11.970s]
sending sparse 'system' (517822 KB)...
OKAY [ 17.540s]
writing 'system'...
OKAY [ 12.340s]
sending sparse 'system' (520627 KB)...
OKAY [ 17.560s]
writing 'system'...
OKAY [ 10.890s]
sending sparse 'system' (522703 KB)...
OKAY [ 17.630s]
writing 'system'...
OKAY [ 10.910s]
sending sparse 'system' (154528 KB)...
OKAY [ 5.450s]
writing 'system'...
OKAY [ 3.500s]
finished. total time: 127.320s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.110s
C:\adb>fastboot devices
F5AZFG27Z395 fastboot
C:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.490s]
finished. total time: 0.490s
C:\adb>fastboot format cache
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.390s]
sending 'cache' (6248 KB)...
OKAY [ 0.410s]
writing 'cache'...
OKAY [ 0.390s]
finished. total time: 1.190s
C:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.400s]
finished. total time: 0.410s
C:\adb>fastboot devices
F5AZFG27Z395 fastboot
C:\adb>fastboot format userdata
Creating filesystem with parameters:
Size: 27984359424
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6832119
Block groups: 209
Reserved block group size: 1024
Created filesystem with 11/1708784 inodes and 151285/6832119 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 4.290s]
sending 'userdata' (139033 KB)...
OKAY [ 4.600s]
writing 'userdata'...
FAILED (remote: flash_cmds error!
)
finished. total time: 9.180s
C:\adb>fastboot format cache
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.370s]
sending 'cache' (6248 KB)...
OKAY [ 0.420s]
writing 'cache'...
OKAY [ 0.380s]
finished. total time: 1.170s
C:\adb>fastboot format userdata
Creating filesystem with parameters:
Size: 27984359424
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6832119
Block groups: 209
Reserved block group size: 1024
Created filesystem with 11/1708784 inodes and 151285/6832119 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 4.050s]
sending 'userdata' (139033 KB)...
OKAY [ 4.490s]
writing 'userdata'...
FAILED (remote: flash_cmds error!
)
finished. total time: 8.840s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.108s
C:\adb>
Is there a way to get the phone working again?
Thank you very much.

After flashing the recovery image, you should be able to get into the recovery mode, and sideload the full zip file. Don't flash the system image.

KillerNo2 said:
After flashing the recovery image, you should be able to get into the recovery mode, and sideload the full zip file. Don't flash the system image.
Click to expand...
Click to collapse
Before flashing WW 2.20.40.139 recovery, boot, fastboot and system, I tried flashing only recovery, boot and fastboot from WW 2.20.40.90 but couldn't also get into recovery mode. Always the same error.
Maybe the firmware zip file I copied previously (when the phone was working) to the internal memory was somehow corrupted and it remains there?
Is there anything more I could do?
Thank you very much.

cdiogooliveira said:
Before flashing WW 2.20.40.139 recovery, boot, fastboot and system, I tried flashing only recovery, boot and fastboot from WW 2.20.40.90 but couldn't also get into recovery mode. Always the same error.
Maybe the firmware zip file I copied previously (when the phone was working) to the internal memory was somehow corrupted and it remains there?
Is there anything more I could do?
Thank you very much.
Click to expand...
Click to collapse
I think you should've updated to version .97 first. So download .97 recovery from here,and try it again.

Hello KillerNo2
Could you please share another link, because the one you posted in not working?
Thank you.

cdiogooliveira said:
Hello KillerNo2
Could you please share another link, because the one you posted in not working?
Thank you.
Click to expand...
Click to collapse
It works now.

KillerNo2 said:
It works now.
Click to expand...
Click to collapse
Hello. Recovery .97 didn't work also. It has always the blinking droid and doesn't boot.
I could run tethered (without install) TWRP recovery and tried to install full zip rom, but TWRP couldn't also access /cache partition. TWRP cannot mount cache and system partitions.
Anyone can help?
Thank you very much.

Can't flash system.img (TWRP/FASTBOOT)

Hi xda!
I can't flash system with TWRP or Fastboot
Fastboot:
Code:
C:\Users\manager\Desktop\coils\Nexus>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.741s]
sending sparse 'system' 1/4 (516666 KB)...
OKAY [ 17.776s]
writing 'system' 1/4...
FAILED (remote: size too large)
finished. total time: 18.557s
TWRP:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I try fastboot erase system
I try repair partition in TWRP
I try change filesystem to ext2 and back to ext4
I try in TWRP
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/system
and
Code:
make_ext4fs /dev/block/mmcblk0p41
Can any body help me with this problem?

Your fastboot is old. Get the latest one from the SDK.
Sent from my Nexus 5X using Tapatalk

PiousInquisitor said:
Your fastboot is old. Get the latest one from the SDK.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I have the latest version, I use this fastboot early and everything was fine

bzz11g said:
I have the latest version, I use this fastboot early and everything was fine
Click to expand...
Click to collapse
Obviously not. The error you are getting is due to an out of date fastboot.
Sent from my Nexus 5X using Tapatalk

piousinquisitor said:
obviously not. The error you are getting is due to an out of date fastboot.
Sent from my nexus 5x using tapatalk
Click to expand...
Click to collapse
IT'S LATEST VERSION
Code:
Microsoft Windows [Version 6.1.7601]
(c) Корпорация Майкрософт (Microsoft Corp.), 2009. Все права защищены.
C:\Users\manager\Desktop\Nexus>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.532s]
sending sparse 'system' 1/4 (516666 KB)...
OKAY [ 17.605s]
writing 'system' 1/4...
FAILED (remote: size too large)
finished. total time: 18.178s
C:\Users\manager\Desktop\Nexus>fastboot --version
fastboot version 8f855a3d9b35-android
C:\Users\manager\Desktop\Nexus>

When i had this problem, i had a bad download. Go redownload the image you are attempting to flash, make sure to check MD5. And where are you getting your fastboot drivers from?

I try redownload firmware and verifi сhecksum, all is good, but I continue to watch same error, can any body help?

bzz11g said:
I try redownload firmware and verifi сhecksum, all is good, but I continue to watch same error, can any body help?
Click to expand...
Click to collapse
Have you updated your platform tools? This new 7.0 system.img takes a while to flash and updating that helped me.
Sent from my Nexus 5X using Tapatalk

Try with:
fastboot flash -S 512M system system.img
i had this error with the nexus 5, fixed by flashing with -s 512m.

Make sure to download the latest platform-tools, pal
That'll fugure out your problem for sure. The do the fastboot and you're just gonna be fine. No reason to go around bushes. Follow the Root 5x thread.

SlimSnoopOS said:
Have you updated your platform tools? This new 7.0 system.img takes a while to flash and updating that helped me.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I try system.img from 7.0 and 6.0.1 and always get the same error
AtField said:
Try with:
fastboot flash -S 512M system system.img
i had this error with the nexus 5, fixed by flashing with -s 512m.
Click to expand...
Click to collapse
yes i try it in first time, without results...
2 All,
please look at the screenshot in first message with TWRP log, I think problem in system partition, other img (vendor, userdata, cache etc.) installed without problems
may be some body know how I can repair system partition across ADB Shell?

bzz11g said:
I try system.img from 7.0 and 6.0.1 and always get the same error
yes i try it in first time, without results...
2 All,
please look at the screenshot in first message with TWRP log, I think problem in system partition, other img (vendor, userdata, cache etc.) installed without problems
may be some body know how I can repair system partition across ADB Shell?
Click to expand...
Click to collapse
You tried with the added -S 512M ?
Because in the first screenshot i dont see that part of the command.
Anyway, if you already tried with -s 512m I'm sorry but I cant help you.

AtField said:
You tried with the added -S 512M ?
Because in the first screenshot i dont see that part of the command.
Anyway, if you already tried with -s 512m I'm sorry but I cant help you.
Click to expand...
Click to collapse
yes, i try this key's
if you look in log
Code:
target reported max download size of 536870912 bytes
it already 512 Mb
536870912 bytes / 1024 = 524288 kB / 1024 = 512 Mb

@bzz11g Issue the following command (after updating your fastboot, lol) and try again.
Code:
fastboot format system
note that there is a difference between erase and format.
Have you tried using the flash-all script?
If nothing else works use the TOT method to fix your phone.

@PiousInquisitor thank you for your note, I already try it..
I try install full stock with flash-all.bat and NRT, and always see the same error
Yesterday I can flash system.img with ADB shell and DD command:
Code:
ADB shell dd if=/sdcard/system.img of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/system
and everything went well, but I still in bootloop and see Google logo..
Can anybody make TWRP backup of system 6.0.1 for me?

bzz11g said:
@PiousInquisitor thank you for your note, I already try it..
I try install full stock with flash-all.bat and NRT, and always see the same error
Yesterday I can flash system.img with ADB shell and DD command:
Code:
ADB shell dd if=/sdcard/system.img of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/system
and everything went well, but I still in bootloop and see Google logo..
Can anybody make TWRP backup of system 6.0.1 for me?
Click to expand...
Click to collapse
You can't flash system.img that way. It isn't a standard .img file.
I don't know what is wrong with your setup, but if you want you can try fastboot from here
http://forum.xda-developers.com/nexus-5x/general/psa-fix-adb-doesnt-winxp-t3403955
I know for sure it has no problems flashing the NRD90M system.img as I did it a few days ago.
If that doesn't work, then the problem is not with fastboot or the usb dll that uses.

sfhub said:
You can't flash system.img that way. It isn't a standard .img file.
Click to expand...
Click to collapse
I know, I want try to restore System with TWRP
sfhub said:
I don't know what is wrong with your setup, but if you want you can try fastboot from here
http://forum.xda-developers.com/nexus-5x/general/psa-fix-adb-doesnt-winxp-t3403955
Click to expand...
Click to collapse
I try it now, thank you

@sfhub
Code:
C:\Users\manager\Desktop\platform-tools-v23.1>fastboot devices
0106fb608bc03dee fastboot
C:\Users\manager\Desktop\platform-tools-v23.1>fastboot -S 512M flash system syst
em.img
erasing 'system'...
OKAY [ 0.556s]
sending sparse 'system' (516666 KB)...
OKAY [ 17.587s]
writing 'system'...
FAILED (remote: size too large)
finished. total time: 18.170s

bzz11g said:
@sfhub
Code:
C:\Users\manager\Desktop\platform-tools-v23.1>fastboot devices
0106fb608bc03dee fastboot
C:\Users\manager\Desktop\platform-tools-v23.1>fastboot -S 512M flash system syst
em.img
erasing 'system'...
OKAY [ 0.556s]
sending sparse 'system' (516666 KB)...
OKAY [ 17.587s]
writing 'system'...
FAILED (remote: size too large)
finished. total time: 18.170s
Click to expand...
Click to collapse
So it isn't related to fastboot.
Are any of your partitions on the remote device full? cache or userdata?
If you can boot into stock recovery, you might want to try the FULL OTA from the nexus factory image site which you can try installing over adb sideload.
---------- Post added at 11:44 AM ---------- Previous post was at 11:42 AM ----------
bzz11g said:
I know, I want try to restore System with TWRP
Click to expand...
Click to collapse
Is that system.img from a factory image or is it from twrp backup?
If it is from factory image, I am not sure if TWRP does what is necessary to restore it either.
---------- Post added at 11:55 AM ---------- Previous post was at 11:44 AM ----------
You didn't mention you were at Qualcomm loader.
You need to use LGUP and the TOT file in the other thread.

I got the same error message a while back - I solved it by re-installing SDK on my computer. I know you have previously said that you have the most recent version of SDK, and I thought I did as well. But I went ahead and uninstalled everything related to SDK on my computer and reinstalled a fresh version. Once I tried flashing system.img after that, it worked perfectly. I'd suggest that you try the same.

Can't Get Partitions to Mount After TWRP/Root

Good Afternoon,
I got the Google Pixel XL from Google's Play Store. I unlocked the bootloader, installed TWRP, and tried to root the phone. I'm not sure what happened, but TWRP is now not asking me for my pin and not of my partitions /data /system /vendor are mounting. I'm thinking because the device is encrypted. Is there a way to force the pin unlock on TWRP?
Not sure what to do here...
Thanks,
Chris

The following is what TWRP is displaying when I try to select slot A or B for rebooting.
E:Unable to find partition size for '/boot'
E:Unable to find partition size for '/system_image'
E:Unable to find partition size for '/vendor_image'
E:Unable to find partition size for '/misc'
E:Unable to find partition size for '/efs2'
E:Unable to find partition size for '/efs2'
Erimary block device '/dev/block/bootdevice/by-name/userdata' for mount point '/data' is not present!
E:Unable to set bootloader message
Updating partition details...
Failed to mount '/system' (Invalid Argument)
Failed to mount '/vendor' (Invalid Argument)
Failed to mount '/data' (Invalid Argument)

Nobody has anything? .... Am I just screwed?

Flash stock images and start over.
If you set a pin in rom it will ask for it to decrypt your data. If you dont have the pin it wont decrypt and have issues like your having.
Nexus's or excuse me pixels are forgiving phones ha.

TWRP is not asking me for a PIN but I set a PIN. I was asking me for a PIN, then I tried to flash the stock rom and it booted into twrp w/o prompting for a PIN.
How can I flash a stock ROM if the phone doesn't have a partition for me to push the file to? It's showing 0mb available on the internal storage. I tried a USB OTG and it didn't recognize it either.

Cause your not gonna be using twrp to flash stock images. You need to go through bootloader and use fastboot.

Any good walkthroughs on flashing stock back on the phone then? Sorry for being a complete noob on this.

try this
trout_of_death said:
Any good walkthroughs on flashing stock back on the phone then? Sorry for being a complete noob on this.
Click to expand...
Click to collapse
Go to "https://developers.google.com/android/ota" and download the OTA you need. (X for Verizon)
Copy the OTA zip file to the same folder that ADB/Fastboot is in.
Reboot phone to the bootloader (Hold Power and Volume Down while powering on the phone) Use the volume keys and choose recovery.
Or at the No Command screen hold power and while holding power press and hold volume up for about 5 seconds, let go of volume up and power and it should take you to Recovery.
Choose "Update from ADB" in Recovery.
Open command prompt on your pc in folder that has fastboot and adb.
enter: adb sideload name_of_ota.zip (Replace name_of_ota with the correct file name.) (Don't have two " .zips" at end of name)
This will take a few minutes and will fix you up.

trout_of_death said:
Any good walkthroughs on flashing stock back on the phone then? Sorry for being a complete noob on this.
Click to expand...
Click to collapse
Actually, best bet is following directions here:
https://developers.google.com/android/images
because OTA is for updating, where factory image flash-all may be a more complete method.
Sent from my sailfish using XDA Labs

Thanks, but I keep getting "Could not find 'META-INF/com/google/android/update-binary' in the zip file." for every OTA zip. I didn't try the verizion one as this is not a verizon phone.
Best way to learn how to fix a device is to break it first right? haha...
I downloaded the factory NDE63P image from this link (https://developers.google.com/android/images) and ran the flash-all.bat. Below is what was ran and now I'm stuck at the loading screen.
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all
target reported max download size of 536870912 bytes
sending 'bootloadera' (32820 KB)...
OKAY [ 0.825s]
writing 'bootloadera'...
(bootloader) Valid bootloader version.
OKAY [ 1.139s]
finished. total time: 1.965s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.005s
target reported max download size of 536870912 bytes
sending 'radioa' (57048 KB)...
OKAY [ 1.434s]
writing 'radioa'...
OKAY [ 0.948s]
finished. total time: 2.383s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.015s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 122633060352
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 29939712
Block groups: 914
Reserved block group size: 1024
Created filesystem with 11/7487488 inodes and 518062/29939712 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609191801
Serial Number........: HT6AW0201XXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.049s]
checking version-baseband...
OKAY [ 0.049s]
sending 'boota' (26481 KB)...
OKAY [ 0.691s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.150s
Press any key to exit...

trout_of_death said:
Thanks, but I keep getting "Could not find 'META-INF/com/google/android/update-binary' in the zip file." for every OTA zip. I didn't try the verizion one as this is not a verizon phone.
Best way to learn how to fix a device is to break it first right? haha...
I downloaded the factory NDE63P image from this link (https://developers.google.com/android/images) and ran the flash-all.bat. Below is what was ran and now I'm stuck at the loading screen.
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all
target reported max download size of 536870912 bytes
sending 'bootloadera' (32820 KB)...
OKAY [ 0.825s]
writing 'bootloadera'...
(bootloader) Valid bootloader version.
OKAY [ 1.139s]
finished. total time: 1.965s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.005s
target reported max download size of 536870912 bytes
sending 'radioa' (57048 KB)...
OKAY [ 1.434s]
writing 'radioa'...
OKAY [ 0.948s]
finished. total time: 2.383s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.015s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 122633060352
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 29939712
Block groups: 914
Reserved block group size: 1024
Created filesystem with 11/7487488 inodes and 518062/29939712 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609191801
Serial Number........: HT6AW0201XXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.049s]
checking version-baseband...
OKAY [ 0.049s]
sending 'boota' (26481 KB)...
OKAY [ 0.691s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.150s
Press any key to exit...
Click to expand...
Click to collapse
When you flashed/fastbooted the twrp image did you install the two you flashed/fastbooted?

I'm not sure I understand the question?

In rereading the TWRP instructions, yes I booted to the img and ran the zip.

I fixed the issue with not being able to decrypt my partitions by fastbooting to the twrp image again.

So.... I tried to install the factory image.... now my phone is bricked and I have the Qualcomm HS-USB QDLoader 9008 in device manager.... anyone have the BoradDiag for Pixel Xl or the Image Files?

trout_of_death said:
So.... I tried to install the factory image.... now my phone is bricked and I have the Qualcomm HS-USB QDLoader 9008 in device manager.... anyone have the BoradDiag for Pixel Xl or the Image Files?
Click to expand...
Click to collapse
Is your bootloader still unlocked. Can you still boot to bootloader.

Bootloader is still unlocked, not I can't boot to bootloader.

I'm within my return window, I'm thinking about returning the phone to Google. Thoughts?

trout_of_death said:
Bootloader is still unlocked, not I can't boot to bootloader.
Click to expand...
Click to collapse
trout_of_death said:
I'm within my return window, I'm thinking about returning the phone to Google. Thoughts?
Click to expand...
Click to collapse
You can't boot bootloader with power and volume buttons? Does the phone turn on at all.

toknitup420 said:
You can't boot bootloader with power and volume buttons? Does the phone turn on at all.
Click to expand...
Click to collapse
No, it's bricked. When I plug it into my computer I get the chipset as a device, no ADB or anything.

[ROM][10.0][XZ2c] Pixel Experience for Xperia XZ2 compact (apollo) [AOSP][2020/02/21]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience for the Sony Xperia XZ2 Compact apollo
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 10.0
Whats working?
Wifi
RIL
Volte
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint reader
NFC
Lights
Sound / vibration
Known issues
Sony Open Devices bug tracker
DON'T FLASH GAPPS, ALREADY INCLUDED
Download from Pixel Experience website (Xperia XZ2 Compact Single Sim)
Download from Pixel Experience website (Xperia XZ2 Compact Dual Sim)
Flash instructions and special recovery coming on Monday 24/02/2020
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Sony Specified Telegram channel
Our blog​
Android OS version: 10.0.0_r27
Security patch level: February 2020
Build author/Device Maintainer: fastbooking
Device Source code: https://github.com/PixelExperience-Devices/device_sony_customization
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
​

Hello. What about Tama/Akari? Does it stable on XZ2? What about bugs or work/not work things? Sorry for bad eng.

[email protected]+ said:
Hello. What about Tama/Akari? Does it stable on XZ2? What about bugs or work/not work things? Sorry for bad eng.
Click to expand...
Click to collapse
Hey ! I think the thread you're searching is this one : https://forum.xda-developers.com/xp...om-pixel-experience-xperia-xz2-akari-t4054671
Anyway, to answer your question, it's pretty much stable, I have users testing it and it seem to be rock solid, I'm working hard with the Sony Open Devices on new features and great performance optimizations.

Does this ROM have the same issues as the android 10 stock rom ?

Looking forward to install it

fastbooking said:
Flash instructions and special recovery coming on Monday 24/02/2020
[/LEFT]
Click to expand...
Click to collapse
Where is the instructions?
Noob to flashing on Xperia. Coming from oneplus where everything is pretty straightforward, I'm not very confident trying unlocking the bootloader on my xz2.
Also I've read conflicting accounts of drm issues if you try to go back stock. Is there any truth to this?

Any screenshots or install instructions?

Is there any flashing guide? Or I can simply flash it without any other files in twrp? PS: Pls forgive my poor Eng.:laugh:

is it worth it

Where are the recovery and the instructions?

Not Good
Doesnt charge properly and the camera takes pink photos
Which kernel would you recommend for this rom

I found the instructions
AntonioBiscuit said:
Where are the recovery and the instructions?
Click to expand...
Click to collapse
go check this website
https://sites.google.com/d/1EhBdYBO...KEXb/p/1oI8WuIQKz4rVj2d5Og7p6TYgh60o31Aa/edit

Does not work for me...
logan123456 said:
go check this website
Click to expand...
Click to collapse
I followed the instructions on the website but it does not work for me.
I get stuck in a bootloop where at first I see a message saying that the bootloader is onulocked and cannot verify the device, then the Sony logo for a few times.
After what I get a red warning saying that my device is corrupt and will poweroff in 5 seconds.
I used Kernel 4.14 v5a Tama binaries and tried with the Pixel Experience Plus build from March 30, 2020 and the normal Pixel Experience build from the same date.
My XZ2C is a Dual-SIM one, Revision 6.
I verified that I had the right build (H8324) and verified that I had correctly downloaded the files.
I tried flashing the binaries only on "oem" the first time and another time with "oem_a" + "oem_b".
Maybe I'm doing something wrong or I forgot to flash some file.
I'm worried about the "Invalid sparse file format at header magi" message, I don't know if it may somewhat be the issue.
(I am able to flash and boot from the latest stock ROM without any trouble)
Code:
>fastboot flash vbmeta vbmeta.img
target reported max download size of 805306368 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.005s]
writing 'vbmeta'...
OKAY [ 0.003s]
finished. total time: 0.011s
>fastboot flash boot boot.img
target reported max download size of 805306368 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.943s]
writing 'boot'...
OKAY [ 0.376s]
finished. total time: 2.321s
>fastboot flash dtbo dtbo.img
target reported max download size of 805306368 bytes
sending 'dtbo' (8192 KB)...
OKAY [ 0.254s]
writing 'dtbo'...
OKAY [ 0.050s]
finished. total time: 0.306s
>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.249s]
sending sparse 'system' (759566 KB)...
OKAY [ 24.189s]
writing 'system'...
OKAY [ 0.003s]
sending sparse 'system' (724540 KB)...
OKAY [ 23.036s]
writing 'system'...
OKAY [ 0.002s]
sending sparse 'system' (738077 KB)...
OKAY [ 23.506s]
writing 'system'...
OKAY [ 0.002s]
sending sparse 'system' (62664 KB)...
OKAY [145.908s]
writing 'system'...
OKAY [ 0.003s]
finished. total time: 216.907s
>fastboot flash vendor vendor.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
sending sparse 'vendor' (55600 KB)...
OKAY [ 1.747s]
writing 'vendor'...
OKAY [ 0.003s]
finished. total time: 1.755s
>fastboot flash oem SW_binaries_for_Xperia_Android_10.0.7.1_r1_v5a_tama.img
target reported max download size of 805306368 bytes
sending 'oem' (320708 KB)...
OKAY [ 9.513s]
writing 'oem'...
OKAY [ 9.232s]
finished. total time: 18.748s

Hi,
I flashed the binaries "SW_binaries_for_Xperia_Android_10.0.7.1_r1_v4c_tama" on oem_a and oem_b. This works fine.
Greets Duke

duke864 said:
I flashed the binaries "SW_binaries_for_Xperia_Android_10.0.7.1_r1_v4c_tama" on oem_a and oem_b. This works fine.
Click to expand...
Click to collapse
Seems not to work even if I'm using this version of the binaries, I still have the same issue.
(tested with oem_a and oem_b with the binaries version you advised me and with the March 30, 2020 build of regular Pixel Experience, following the flashing instructions from the website)
There's definetly something that I'm either doing wrong, a file or step which is missing in my case.
I also heard about a bootloader bug or some kind of security, maybe it's messing up with my installation...
I would be glad to have a tutorial from someone who has succeeded with the latest version

Did you have this issue
duke864 said:
Hi,
I flashed the binaries "SW_binaries_for_Xperia_Android_10.0.7.1_r1_v4c_tama" on oem_a and oem_b. This works fine.
Greets Duke
Click to expand...
Click to collapse
did you have any battery problems in pixel experience like not accurate battery percentage
---------- Post added at 04:01 AM ---------- Previous post was at 03:58 AM ----------
AntonioBiscuit said:
Seems not to work even if I'm using this version of the binaries, I still have the same issue.
(tested with oem_a and oem_b with the binaries version you advised me and with the March 30, 2020 build of regular Pixel Experience, following the flashing instructions from the website)
There's definetly something that I'm either doing wrong, a file or step which is missing in my case.
I also heard about a bootloader bug or some kind of security, maybe it's messing up with my installation...
I would be glad to have a tutorial from someone who has succeeded with the latest version
Click to expand...
Click to collapse
maybe try formatting your phone completely and try again
---------- Post added at 04:12 AM ---------- Previous post was at 04:01 AM ----------
AntonioBiscuit said:
I followed the instructions on the website but it does not work for me.
I get stuck in a bootloop where at first I see a message saying that the bootloader is onulocked and cannot verify the device, then the Sony logo for a few times.
After what I get a red warning saying that my device is corrupt and will poweroff in 5 seconds.
I used Kernel 4.14 v5a Tama binaries and tried with the Pixel Experience Plus build from March 30, 2020 and the normal Pixel Experience build from the same date.
My XZ2C is a Dual-SIM one, Revision 6.
I verified that I had the right build (H8324) and verified that I had correctly downloaded the files.
I tried flashing the binaries only on "oem" the first time and another time with "oem_a" + "oem_b".
Maybe I'm doing something wrong or I forgot to flash some file.
I'm worried about the "Invalid sparse file format at header magi" message, I don't know if it may somewhat be the issue.
(I am able to flash and boot from the latest stock ROM without any trouble)
Code:
>fastboot flash vbmeta vbmeta.img
target reported max download size of 805306368 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.005s]
writing 'vbmeta'...
OKAY [ 0.003s]
finished. total time: 0.011s
>fastboot flash boot boot.img
target reported max download size of 805306368 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.943s]
writing 'boot'...
OKAY [ 0.376s]
finished. total time: 2.321s
>fastboot flash dtbo dtbo.img
target reported max download size of 805306368 bytes
sending 'dtbo' (8192 KB)...
OKAY [ 0.254s]
writing 'dtbo'...
OKAY [ 0.050s]
finished. total time: 0.306s
>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.249s]
sending sparse 'system' (759566 KB)...
OKAY [ 24.189s]
writing 'system'...
OKAY [ 0.003s]
sending sparse 'system' (724540 KB)...
OKAY [ 23.036s]
writing 'system'...
OKAY [ 0.002s]
sending sparse 'system' (738077 KB)...
OKAY [ 23.506s]
writing 'system'...
OKAY [ 0.002s]
sending sparse 'system' (62664 KB)...
OKAY [145.908s]
writing 'system'...
OKAY [ 0.003s]
finished. total time: 216.907s
>fastboot flash vendor vendor.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
sending sparse 'vendor' (55600 KB)...
OKAY [ 1.747s]
writing 'vendor'...
OKAY [ 0.003s]
finished. total time: 1.755s
>fastboot flash oem SW_binaries_for_Xperia_Android_10.0.7.1_r1_v5a_tama.img
target reported max download size of 805306368 bytes
sending 'oem' (320708 KB)...
OKAY [ 9.513s]
writing 'oem'...
OKAY [ 9.232s]
finished. total time: 18.748s
Click to expand...
Click to collapse
i am not sure if you are supposed flash it on both slots fastboot flash oem_a
fastboot flash oem_b

was there any battery problem
like severe battery drain
if there was a problem how did you fix it

It works !
I finally managed to install the ROM yesterday using differents instructions.
Here is how I did it if you are struggling to install like me at the beginning (or maybe there was just a fix in between, I don't know).
Before doing anything, the usual, you might want to take some precautions: do backups and remove the SD card from your device before loosing anything. What follows is going to format your internal storage.
Please respond if anything is wrong in here of if you have some details to add.
My installation was done from Android 10 stock 52.1.A.0.618. You can install it from a program called "Emma" from Sony.
You will first need to extract "payload.bin" from the .zip ROM file you have downloaded (Pixel Experience).
You will then need to use a program called "payload dumper" to get the files you'll be installing with fastboot afterwards from the payload.bin you just extracted. (expect around 6GB of files)
You will also need to extract "SW_binaries.img" from the most recent binaries .zip, which you can download on Sony's website.
In your command prompt you will need to do the following:
Code:
> fastboot flash boot boot.img
> fastboot flash dtbo dtbo.img
> fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
> fastboot flash system system.img
> fastboot flash vendor vendor.img
> fastboot flash oem_a SW_binaries_for_Xperia_Android_10.0.7.1_r1_v6_tama.img
> fastboot flash oem_b SW_binaries_for_Xperia_Android_10.0.7.1_r1_v6_tama.img
Some things to keep in mind and which I would have liked to be aware of :
If you can't use --disable-verity and/or --disable-verification, try to launch your terminal from the folder of your most recent platform tools. It seems like they don't exist in some adb installers.
Flashing the files to your phone may take a long while to start. Just be patient.
You may see a "Invalid sparse file format at header magi" message at some point. I am not sure what it means (tell me if you know) but I got it and my phone is working just fine right now.
If you see a Google logo after the Sony logo, it means you probably succeeded.
After installing, my phone bootlooped two times. It then showed me a menu where I could format some data. I did it and after that it took a while to boot the first time but finally worked.
Here are the builds I am currently testing on my Xperia XZ2 Compact (H8324 REV6):
PixelExperience_h8324-10.0-20200511-0435-OFFICIAL.zip
SW_binaries_for_Xperia_Android_10.0.7.1_r1_v6_tama.img
I will try to tell you about the bugs and issues I may face in the next few days, but right now the ROM is feeling way snappier than Sony's stock Android 10 ROM in my opinion and the animations are gorgeous.

AntonioBiscuit said:
I finally managed to install the ROM yesterday using differents instructions.
Here is how I did it if you are struggling to install like me at the beginning (or maybe there was just a fix in between, I don't know).
Before doing anything, the usual, you might want to take some precautions: do backups and remove the SD card from your device before loosing anything. What follows is going to format your internal storage.
Please respond if anything is wrong in here of if you have some details to add.
My installation was done from Android 10 stock 52.1.A.0.618. You can install it from a program called "Emma" from Sony.
You will first need to extract "payload.bin" from the .zip ROM file you have downloaded (Pixel Experience).
You will then need to use a program called "payload dumper" to get the files you'll be installing with fastboot afterwards from the payload.bin you just extracted. (expect around 6GB of files)
You will also need to extract "SW_binaries.img" from the most recent binaries .zip, which you can download on Sony's website.
In your command prompt you will need to do the following:
Code:
> fastboot flash boot boot.img
> fastboot flash dtbo dtbo.img
> fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
> fastboot flash system system.img
> fastboot flash vendor vendor.img
> fastboot flash oem_a SW_binaries_for_Xperia_Android_10.0.7.1_r1_v6_tama.img
> fastboot flash oem_b SW_binaries_for_Xperia_Android_10.0.7.1_r1_v6_tama.img
Some things to keep in mind and which I would have liked to be aware of :
If you can't use --disable-verity and/or --disable-verification, try to launch your terminal from the folder of your most recent platform tools. It seems like they don't exist in some adb installers.
Flashing the files to your phone may take a long while to start. Just be patient.
You may see a "Invalid sparse file format at header magi" message at some point. I am not sure what it means (tell me if you know) but I got it and my phone is working just fine right now.
If you see a Google logo after the Sony logo, it means you probably succeeded.
After installing, my phone bootlooped two times. It then showed me a menu where I could format some data. I did it and after that it took a while to boot the first time but finally worked.
Here are the builds I am currently testing on my Xperia XZ2 Compact (H8324 REV6):
PixelExperience_h8324-10.0-20200511-0435-OFFICIAL.zip
SW_binaries_for_Xperia_Android_10.0.7.1_r1_v6_tama.img
I will try to tell you about the bugs and issues I may face in the next few days, but right now the ROM is feeling way snappier than Sony's stock Android 10 ROM in my opinion and the animations are gorgeous.
Click to expand...
Click to collapse
please give the review about the performance for gaming use
i would like to change to use PE but still not sure if this form can significantly boost the performance on xz2c for gaming than the stock rom official
because since the android 10 on official stock rom, i feel it drop down the performance for gaming. it makes me struggle alot of time

Gaming performance
3D performance:
I used 3D Mark Sling Shot extreme in the hope that you will find what performance you can expect by running this ROM and binaries:
- PixelExperience_h8324-10.0-20200511-0435-OFFICIAL
- SW_binaries_for_Xperia_Android_10.0.7.1_r1_v6_tama
Stock Android for comparison: https://benchmarks.ul.com/en/hardware/phone/Sony+Xperia+XZ2+Compact+review
(You can test your device if you have stock Android to compare the results)
The scores presented here are averaged from 5 runs and are pretty much the same as what is in the database. There should not be a huge performance difference in games.
OpenGL ES 3.1:
Overall: 4,167.4 (~1% lower)
Graphics: 5,125 (=)
Physics: 2,522.6 (-24%)
Vulkan:
Overall: 3,973.2 (=)
Graphics: 4,664 (-5%)
Physics: 2,620 (+11%)
Detailled scores for the 5 runs:
Run 01:
Open GL ES 3.1
Overall score: 4,161
Graphics score: 5,149
Physics score: 2,490
Vulkan
Overall score 4,047
Graphics score: 4,664
Physics score: 2,767
----------
Run 02:
Open GL ES 3.1
Overall score: 4,250
Graphics score: 5,124
Physics score: 2,661
Vulkan
Overall score: 4,018
Graphics score: 4,668
Physics score: 2,701
----------
Run 03:
Open GL ES 3.1
Overall score: 4,093
Graphics score: 5,120
Physics score: 2,404
Vulkan
Overall score: 3,968
Graphics score: 4,679
Physics score: 2,591
----------
Run 04:
Open GL ES 3.1
Overall score: 4,094
Graphics score: 5,107
Physics score: 2,417
Vulkan
Overall score: 3,851
Graphics score: 4,657
Physics score: 2,398
----------
Run 05:
Open GL ES 3.1
Overall score: 4,239
Graphics score: 5,125
Physics score: 2,641
Vulkan
Overall score: 3,980
Graphics score: 4,652
Physics score: 2,643

[SOLVED] Need some help - can't access anything but fastboot - broken partition table

Hey all, hoping to get some help recovering my Pixel 2 XL.
I was testing Ubuntu Touch and was annoyed that I didn't have enough root space, so I tried to adjust the partitions and have ended up here.
Whats happening:
Phone only boots in bootloader / `fastboot` mode
When trying to boot into recovery it just takes me back to bootloader
When I try to start the phone it goes right back to bootloader
What works:
`fastboot devices` shows my phone connected
What I've tried:
Flashing recovery via fastboot
`fastboot flash system twrp-3.7.0_9-0-taimen.img`
Sending 'system' (40960 KB) OKAY [ 1.055s]
Writing 'system' FAILED (remote: 'No such partition.')
`fastboot flash recovery twrp-3.7.0_9-0-taimen.img`
Warning: skip copying recovery image avb footer (recovery partition size: 0, recovery image size: 41943040).
Sending 'recovery' (40960 KB) OKAY [ 1.051s]
Writing 'recovery' FAILED (remote: 'No such partition.')
`fastboot flash boot_a twrp-3.7.0_9-0-taimen.img`
Warning: skip copying boot_a image avb footer (boot_a partition size: 0, boot_a image size: 41943040).
Sending 'boot_a' (40960 KB) OKAY [ 1.060s]
Writing 'boot_a' OKAY [ 0.364s]
`fastboot flash boot_b twrp-3.7.0_9-0-taimen.img`
Warning: skip copying boot_b image avb footer (boot_b partition size: 0, boot_b image size: 41943040).
Sending 'boot_b' (40960 KB) OKAY [ 0.989s]
Writing 'boot_b' OKAY [ 0.360s]
All of the above (successful or not) end up just taking me back to `bootloader` when I try to boot `recovery`
I've basically tried any command I can find on any image I've been able to get my hands on with no success
Everything I've found around restoring the factory partition table needs `adb`, so I'm stuck right now with.
Would love any suggestions, thanks.

klimbot said:
Hey all, hoping to get some help recovering my Pixel 2 XL.
I was testing Ubuntu Touch and was annoyed that I didn't have enough root space, so I tried to adjust the partitions and have ended up here.
Whats happening:
Phone only boots in bootloader / `fastboot` mode
When trying to boot into recovery it just takes me back to bootloader
When I try to start the phone it goes right back to bootloader
What works:
`fastboot devices` shows my phone connected
What I've tried:
Flashing recovery via fastboot
`fastboot flash system twrp-3.7.0_9-0-taimen.img`
Sending 'system' (40960 KB) OKAY [ 1.055s]
Writing 'system' FAILED (remote: 'No such partition.')
`fastboot flash recovery twrp-3.7.0_9-0-taimen.img`
Warning: skip copying recovery image avb footer (recovery partition size: 0, recovery image size: 41943040).
Sending 'recovery' (40960 KB) OKAY [ 1.051s]
Writing 'recovery' FAILED (remote: 'No such partition.')
`fastboot flash boot_a twrp-3.7.0_9-0-taimen.img`
Warning: skip copying boot_a image avb footer (boot_a partition size: 0, boot_a image size: 41943040).
Sending 'boot_a' (40960 KB) OKAY [ 1.060s]
Writing 'boot_a' OKAY [ 0.364s]
`fastboot flash boot_b twrp-3.7.0_9-0-taimen.img`
Warning: skip copying boot_b image avb footer (boot_b partition size: 0, boot_b image size: 41943040).
Sending 'boot_b' (40960 KB) OKAY [ 0.989s]
Writing 'boot_b' OKAY [ 0.360s]
All of the above (successful or not) end up just taking me back to `bootloader` when I try to boot `recovery`
I've basically tried any command I can find on any image I've been able to get my hands on with no success
Everything I've found around restoring the factory partition table needs `adb`, so I'm stuck right now with.
Would love any suggestions, thanks.
Click to expand...
Click to collapse
Assuming your bootloader is unlocked, try flashing the stock firmware again using Android Flash Tool. Select "Force Flash Partitions".

Lughnasadh said:
Assuming your bootloader is unlocked, try flashing the stock firmware again using Android Flash Tool. Select "Force Flash Partitions".
Click to expand...
Click to collapse
Thanks for the suggestion, but not working :-(
Flash Failed: Fastboot command (erase:userdata) failed. 'Check device console'
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried all the options in there, but no luck

Maybe just run flash-all in the factory image? (I'm not really sure if that is what the flash tool does).
Check your USB connection. This phone usually fails if you use a USB C port on the computer.

Also, did you try fastboot boot twrp.img?

runekock said:
Maybe just run flash-all in the factory image? (I'm not really sure if that is what the flash tool does).
Check your USB connection. This phone usually fails if you use a USB C port on the computer.
Click to expand...
Click to collapse
I'm using the USB connection that I have used the entire time to successfully flash images before I stuffed up the partitions, so I'm confident it's not that. I am on a Mac so only have USB-C available unfortunately.
runekock said:
Also, did you try fastboot boot twrp.img?
Click to expand...
Click to collapse
Yep have tried flashing both boot and recovery with no luck.
I think I need to fix the partitions somehow, if that's even possible from where I am

I was thinking of the fastboot "boot" command that can boot twrp without flashing it

runekock said:
I was thinking of the fastboot "boot" command that can boot twrp without flashing it
Click to expand...
Click to collapse
I got in to TWRP!! Not sure why but `fastboot reboot recovery` got me to TWRP... progress! Thanks for your help @runekock
Now I guess I just need to work out how to restore the partition table

Got it going again!! So once I got from fastboot in to recovery, I was able to follow these instructions to remake the partition table:
[GUIDE] System partition too small? Installing Android 12, GApps & large GSIs on Pixel 2 XL!
SPECIAL THANKS TO @Lunarixus on XDA I wouldn't have figured out how to maneuver the pixel 2 XL partition table without him. WARNING! This tutorial only applies to Taimen (2XL). There's already another tutorial for Walleye, click here for link...
forum.xda-developers.com

Good to hear. Your persistence was rewarded!