Develop Bugs

Need Help Unbricking my Pixel XL

need help unbricking my pixel xl.
i downloaded the factory image from google and ran the flashall.bat but it keeps failing.
target reported max download size of 536870912 bytes
sending 'bootloadera' (32820 KB)...
OKAY [ 0.770s]
writing 'bootloadera'...
(bootloader) Valid bootloader version.
OKAY [ 1.038s]
finished. total time: 1.812s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.009s
target reported max download size of 536870912 bytes
sending 'radioa' (57048 KB)...
OKAY [ 1.302s]
writing 'radioa'...
OKAY [ 0.897s]
finished. total time: 2.201s
rebooting into bootloader...
OKAY [ 0.014s]
finished. total time: 0.016s
< 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........: HT69D0200852
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.049s]
checking version-baseband...
OKAY [ 0.048s]
sending 'boota' (26481 KB)...
OKAY [ 0.641s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.097s
Press any key to exit...

I had the same problem. You need to extract everything within the file you downloaded for the factory in same directory(there should be another zip in there)... and then flash everything individually like the flash all file would do. So flash bootloader... Radio... (Reboot bootloader after this****)... And then flash everything else individually.. then try and start phone

I thought I read that you need the latest SDK in order for flash-all to work. I ran into issues like this when trying to restore my Pixel C to stock. As mentioned, flashing each image separately will work as well.

Shacocka said:
I had the same problem. You need to extract everything within the file you downloaded for the factory in same directory(there should be another zip in there)... and then flash everything individually like the flash all file would do. So flash bootloader... Radio... (Reboot bootloader after this****)... And then flash everything else individually.. then try and start phone
Click to expand...
Click to collapse
What he said
Mike02z said:
I thought I read that you need the latest SDK in order for flash-all to work. I ran into issues like this when trying to restore my Pixel C to stock. As mentioned, flashing each image separately will work as well.
Click to expand...
Click to collapse
I have old sdk and still can flash. You just have to do each step manually.

SDK platform-tools 25 is required for fastboot to automatically recognize a partition being used as the default partition. It is the only version of fastboot that can handle the Pixel partition layout using "fastboot flash update.zip" or any flash scripts which rely on this automated process.

Running into a problem trying to go back to stock on Pixel 2 XL...

Hey all,
I recently got a Pixel 2 XL, and decided to unlock bootloader, and install Resurrection Remix. All went ok, until I got back a message stating, the stock images were incorrect. So, I decided to just go back to stock, and go back to it later. Well, I got the factory images from Google.
Im using Ubuntu 18.04. Within terminal I used ./flash-all.sh It kept coming back as, "Fastboot too old".
if ! grep -q dtbo.sig $(which fastboot); then
echo "fastboot too old"
exit 1
fi
fastboot flash bootloader bootloader-taimen-tmz12bb.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-taimen-g8998-00202-1802061358.img
fastboot reboot-bootloader
sleep 5
So, I removed the first bit of script, and it starts to download. But, it doesnt appear to download correctly. Still on RR when I restart? Heres the script that comes back:
target reported max download size of 536870912 bytes
sending 'bootloaderb' (36344 KB)...
OKAY [ 1.025s]
writing 'bootloaderb'...
OKAY [ 0.374s]
finished. total time: 1.399s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.201s
target reported max download size of 536870912 bytes
sending 'radiob' (60412 KB)...
OKAY [ 1.768s]
writing 'radiob'...
OKAY [ 0.588s]
finished. total time: 2.356s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.201s
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: 56946044928
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13902843
Block groups: 425
Reserved block group size: 1024
Created filesystem with 11/3481600 inodes and 264598/13902843 blocks
--------------------------------------------
Bootloader Version...: TMZ12bb
Baseband Version.....: g8998-00202-1802061358
Serial Number........: 712KPAE1212112
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.000s]
checking version-baseband...
OKAY [ 0.000s]
sending 'bootb' (40960 KB)...
OKAY [ 1.315s]
writing 'bootb'...
FAILED (remote: No such partition.)
finished. total time: 1.320s
I have never really run into this on a Google device. If anyone out there has any insight for me, id really appreciate it. Ill buy a beer to anyone who can help me out.

You could've just ignored that. It doesn't interfere with the device. Just reflash how you normally do then if you get that message again just flash the vendor image.
Sent from my SM-G965U using Tapatalk

Well, after much research, and experimenting, I found that using the oldest image, from Sept 2017, fixed my issue. This whole time I was using the newest April image. Defiantly different with the a & b partition. That threw me off. But, all is well in Pixel land now.

"Your device is corrupt" after flashing any system image

So, I previously had a custom ROM but I wanted to switch to the new Dev Preview of P.
Running flash_all.bat gives no unusual error.
target reported max download size of 536870912 bytes
sending 'bootloader' (36380 KB)...
OKAY [ 0.107s]
writing 'bootloader'...
OKAY [ 0.382s]
finished. total time: 0.495s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
target reported max download size of 536870912 bytes
sending 'radio' (60388 KB)...
OKAY [ 0.165s]
writing 'radio'...
OKAY [ 0.574s]
finished. total time: 0.742s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
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'
Creating filesystem with parameters:
Size: 56946044928
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13902843
Block groups: 425
Reserved block group size: 1024
Created filesystem with 11/3481600 inodes and 264598/13902843 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: TMZ20i
Baseband Version.....: g8998-00223-1804021619
Serial Number........: 711KPAE0759488
--------------------------------------------
checking product...
OKAY [ 0.009s]
checking version-bootloader...
OKAY [ 0.007s]
checking version-baseband...
OKAY [ 0.004s]
sending 'boot' (40960 KB)...
OKAY [ 0.119s]
writing 'boot'...
OKAY [ 0.368s]
sending sparse 'system' (524284 KB)...
OKAY [ 2.889s]
writing 'system'...
OKAY [ 2.435s]
sending sparse 'system' (524284 KB)...
OKAY [ 2.701s]
writing 'system'...
OKAY [ 2.427s]
sending sparse 'system' (524284 KB)...
OKAY [ 2.773s]
writing 'system'...
OKAY [ 2.440s]
sending sparse 'system' (521196 KB)...
OKAY [ 2.728s]
writing 'system'...
OKAY [ 2.420s]
sending sparse 'system' (107872 KB)...
OKAY [ 0.545s]
writing 'system'...
OKAY [ 0.504s]
sending 'vendor' (384712 KB)...
OKAY [ 1.080s]
writing 'vendor'...
OKAY [ 1.790s]
erasing 'userdata'...
OKAY [ 0.286s]
sending 'userdata' (140898 KB)...
OKAY [ 0.399s]
writing 'userdata'...
OKAY [ 1.488s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 27.493s
Press any key to exit...
Click to expand...
Click to collapse
And manually flashing using this tutorial gives the same result.
After the "device is corrupt" message I get a Google logo with the unlocked lock at the bottom. So before the ROM boots.
I've tried the May System Image also, but it returns the exact same result. What should I do?
(It is critically unlocked)

I have the same problem!!!
OK guys I'm lost.
I was on TWRP and SELFISH ROM.
But then today due to ANDROID P Beta I want to go to Beta.
I did put the phone into bootloader.
and installed previous IMAGE : walleye-opd1.170816.010-factory-63083164
After that I put new image : walleye-ppp2.180412.013-factory-6406b348
Instaled like below.
But I can not boot. It always goes to bootloader. even recovery does not work.

I done like,this:
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 09/03/2018 10:38 2604257 adb-linux
-a---- 09/03/2018 10:37 2581412 adb-mac
-a---- 09/03/2018 10:30 1784320 adb.exe
-a---- 09/03/2018 10:30 97792 AdbWinApi.dll
-a---- 09/03/2018 10:30 62976 AdbWinUsbApi.dll
-a---- 28/09/2017 12:38 39657472 bootloader-walleye-mw8998-002.0059.00.img
-a---- 09/03/2018 10:38 1265485 fastboot-linux
-a---- 09/03/2018 10:37 1380616 fastboot-mac
-a---- 09/03/2018 10:30 853504 fastboot.exe
-a---- 28/09/2017 12:38 990 flash-all.bat
-a---- 28/09/2017 12:38 861 flash-all.sh
-a---- 28/09/2017 12:38 808 flash-base.sh
-a---- 28/09/2017 12:38 1571219263 image-walleye-opd1.170816.010.zip
-a---- 02/06/2017 23:07 541322 mfastboot-linux
-a---- 02/06/2017 23:07 225100 mfastboot-mac
-a---- 02/06/2017 23:07 533353 mfastboot.exe
-a---- 28/09/2017 12:38 61878272 radio-walleye-g8998-00122-1708311414.img
PS C:\11> fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
PS C:\11> fastboot flash bootloader bootloader-walleye-mw8998-002.0059.00.img
target reported max download size of 536870912 bytes
sending 'bootloader' (38728 KB)...
OKAY [ 0.919s]
writing 'bootloader'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
(bootloader) Updating: partition:1 @0000D000 sz=0000B000
(bootloader) Updating: partition:2 @00018000 sz=0000B000
(bootloader) Updating: partition:3 @00023000 sz=0000B000
(bootloader) Updating: partition:4 @0002E000 sz=0000B000
(bootloader) Updating: partition:5 @00039000 sz=0000B000
(bootloader) Updating: cmnlib64 @00044000 sz=00049000
(bootloader) Updating: cmnlib @0008D000 sz=00038000
(bootloader) Updating: devcfg @000C5000 sz=0000F000
(bootloader) Updating: hyp @000D4000 sz=00040000
(bootloader) Updating: keymaster @00114000 sz=00046000
(bootloader) Updating: lockbooter @0015A000 sz=00016000
(bootloader) Updating: pmic @00170000 sz=0000D000
(bootloader) Updating: rpm @0017D000 sz=0003A000
(bootloader) Updating: tz @001B7000 sz=001DB000
(bootloader) Updating: xbl @00392000 sz=003A2000
(bootloader) Updating: apdp @00734000 sz=00004000
(bootloader) Updating: msadp @00738000 sz=00004000
(bootloader) Updating: hosd @0073C000 sz=01E31000
(bootloader) Updating: abl @0256D000 sz=00065000
OKAY [ 1.062s]
finished. total time: 1.985s
PS C:\11> fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
PS C:\11> fastboot flash radio radio-walleye-g8998-00122-1708311414.img
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.364s]
writing 'radio'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.290s]
finished. total time: 1.814s
PS C:\11> fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
PS C:\11> fastboot flash image image-walleye-opd1.170816.010.zip
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
PS C:\11> fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
PS C:\11> fastboot -w update image-walleye-opd1.170816.010.zip
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'
Creating filesystem with parameters:
Size: 121043398656
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 29551611
Block groups: 902
Reserved block group size: 1024
Created filesystem with 11/7389184 inodes and 511894/29551611 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00122-1708311414
Serial Number........: FA79G1A07951
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot' (32768 KB)...
OKAY [ 0.773s]
writing 'boot'...
OKAY [ 0.161s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.709s]
writing 'system'...
OKAY [ 17.550s]
sending sparse 'system' (524284 KB)...
OKAY [ 13.020s]
writing 'system'...
OKAY [ 15.830s]
sending sparse 'system' (524284 KB)...
OKAY [ 13.551s]
writing 'system'...
OKAY [ 17.529s]
sending sparse 'system' (322300 KB)...
OKAY [ 7.849s]
writing 'system'...
OKAY [ 8.635s]
sending 'vendor' (346964 KB)...
OKAY [ 8.022s]
writing 'vendor'...
OKAY [ 10.314s]
erasing 'userdata'...
OKAY [ 1.559s]
sending 'userdata' (145005 KB)...
OKAY [ 3.188s]
writing 'userdata'...
OKAY [ 2.210s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 133.102s
PS C:\11> fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s

I have tried, to put sideload OTA.zip (my file walleye-opd1.170816.010-factory-63083164.zip)
But it says NULL found, and will still not work. Can not go above bootloader.
Wanted to install twrp and device not found.
Any ideas., I'm lost.

cvenk said:
I have tried, to put sideload OTA.zip (my file walleye-opd1.170816.010-factory-63083164.zip)
But it says NULL found, and will still not work. Can not go above bootloader.
Wanted to install twrp and device not found.
Any ideas., I'm lost.
Click to expand...
Click to collapse
Shouldn't you be flashing the taimen image? walleye is for the P2, taimen is P2XL.

Hello,
Use the last version of adb ( I had this message with the old one ), second, use Taimen if you have the "2 XL"

Update your fastboot and try again

Personally I use Deuce script. Download the latest images and unzip them to the folder. Then run the Deuce batch file. It will clean/wipe/format everything and put it back to scratch/stock every time on my phone, no matter how fubar my phone like corrupt boot etc..
Then, developer/debug mode. Copy files over after you do a basic setup of the Rom. Then, do whatever are normal steps to run the Beta or a custom Rom from there.
I could never on two computers get fastboot to work with the Flash all bat without errors like that.
Deuce has always worked for me...and I've always had the latest fastboot/adb every time...so thank goodness for Deuce.
---------- Post added at 07:46 PM ---------- Previous post was at 07:38 PM ----------
lorax70 said:
Shouldn't you be flashing the taimen image? walleye is for the P2, taimen is P2XL.
Click to expand...
Click to collapse
Uh..yeah...the Words Taimen should be in the file...not walleye....haha
Anyway..use Deuce and try that method. Had same issues months ago and could never get flash all bat to work from Google without using Deuce to save the day.

OK, thanks. will try, also try the different computer that I had previous luck with it,
Have Pixel 2. But you guys are more active on XL forum, and at the end, it is the same phone.
The only trouble that I can find now is all my flashes worked without errors and nothing happened.
Will report back , hope with a good news.
---------- Post added at 06:17 AM ---------- Previous post was at 06:10 AM ----------
OK, some good news,
Did deuce script on the different computer.
And after restart, it went directly to TWRP. <I don't get it. didn't I just reformatted the phone with stock rom
Now I don't know where to continue.
Will probably install some custom ROM just in case, that I can get the normal boot? But want to go to android P and would appreciate any steps hot to get from custom rom and TWRP to original BETA.
Thank you again guys, you saved me this time.

I installed again TWRP just in case. TWRP installes on both slots, But when I but on SLOT A I can boot to recovery.
If I sellect SLOT B it gives me error and it is all over, can not get anywhere.
Than I fastboot --set-active=a
And again went to twrp.
Any IDEAS what is going on.

OK, did it. Did the fastboot flash all after new drivers new adb install and new computer.. after that it went through., Now I'm on BETA.
Thanks, everybody.

Bootloop after Android 10 OTA uodate!

I just received my Android 10 update and after the update when it asked to reboot I tapped reboot and now it has been stuck in a continuous bootloop. My phone was not rooted or modded in any way. I was able to boot into the recovery selection menu but cant go into the actual recovery (it just says "no item" when I select recovery).
Any help/suggestions?

You can reflash the ROM using the full OTA package, as is stated by Google in https://developers.google.com/android/ota : This page contains full OTA update packages that allow you to restore your Nexus or Pixel device's original factory firmware. You will find these files useful if you have experienced a failure to take an OTA. This has the same effect as flashing the corresponding factory image, but without the need to wipe the device or unlock the bootloader." You also have in that page instructions of the whole process.
All you need to do is reboot into recovery, enter adb sideload mode from whitin it and send the zip OTA file using your PC and adb. Download QP1A.190711.020 version under Pixel 2 XL.
In order to boot into recovery, when you see the Android robot with the "no item" message keep pressed the power button and then short-press volume up until the recovery options show up.
It after that it's still failing, just format within recovery or flash the full firmware stock package.

fdgd1998 said:
You can reflash the ROM using the full OTA package, as is stated by Google in https://developers.google.com/android/ota : This page contains full OTA update packages that allow you to restore your Nexus or Pixel device's original factory firmware. You will find these files useful if you have experienced a failure to take an OTA. This has the same effect as flashing the corresponding factory image, but without the need to wipe the device or unlock the bootloader." You also have in that page instructions of the whole process.
All you need to do is reboot into recovery, enter adb sideload mode from whitin it and send the zip OTA file using your PC and adb. Download QP1A.190711.020 version under Pixel 2 XL.
In order to boot into recovery, when you see the Android robot with the "no item" message keep pressed the power button and then short-press volume up until the recovery options show up.
It after that it's still failing, just format within recovery or flash the full firmware stock package.
Click to expand...
Click to collapse
thank you for the helpful reply
i had already started the process and have already downloaded all the files
but i cant unlock the bootloader as it says in the tutorial
am i doing something wrong? or is there any way to flash without unlocking the bootloader?
Edit: I dont have the "oem unlock" option turned on.
PLZ HELP

areebiqbal said:
thank you for the helpful reply
i had already started the process and have already downloaded all the files
but i cant unlock the bootloader as it says in the tutorial
am i doing something wrong? or is there any way to flash without unlocking the bootloader?
Edit: I dont have the "oem unlock" option turned on.
PLZ HELP
Click to expand...
Click to collapse
Are you flashing the OTA or the full firmware? For the OTA bootloader unlock isn't necessary.
And in the instructions are stated the opposite, you must have misread it.

fdgd1998 said:
Are you flashing the OTA or the full firmware? For the OTA bootloader unlock isn't necessary.
And in the instructions are stated the opposite, you must have misread it.
Click to expand...
Click to collapse
hi, so luckily i had oem unlocking checked before this happened, but after the october update ive been stuck in bootloop.
ive tried both sideloading the ota in recovery, and also full firmware flash via fastboot.
after several attempts at both, i can't seem to access the recovery and bootloop persists.
any ideas?
[pixel sailfish never been rooted]

ku81na said:
hi, so luckily i had oem unlocking checked before this happened, but after the october update ive been stuck in bootloop.
ive tried both sideloading the ota in recovery, and also full firmware flash via fastboot.
after several attempts at both, i can't seem to access the recovery and bootloop persists.
any ideas?
[pixel sailfish never been rooted]
Click to expand...
Click to collapse
Have you looked into the Dueces recovery scrip?
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

no dice. appreciate the suggestion though

ku81na said:
no dice. appreciate the suggestion though
Click to expand...
Click to collapse
if you can confirm a couple things for me....
Are you actually getting into the recovery, but not seeing any "items"; because in stock recovery, you just see a broken/dead android image, and only get selections revealed/not-hidden but holding the volume-up & power button at the same time momentarily.
But, then again, you claim that you have attempted to "sideload the ota in recovery", so I imagine you already did this…but then, again again, you don’t describe what “error” or outcome actually happened and it could possibly be that, when you attempted, you just couldn’t or didn’t know how to get into the stock recovery…
Also, the recovery resides in the boot partition; I suggest you download the Full Factory image file (from the Google Developers site), extract it until you can find the boot.img, then manually flash it to overwrite and maybe fix the boot & recovery; to further explain, copy the extracted “boot.img” file to platform-tools folder where adb and fastboot reside, then run the command “fastboot flash boot boot.img” – although, if the flash-all is successfully executed, it would be doing this anyways…..
Which brings me to my next thing…if you could edit the “flash-all.bat” file and remove the word “exit” at the end – and for that matter, if you wish to save your data, remove the -w as well – and if you could please copy the output/log of you running the flash-all; usually this resolves everything & it all, so maybe it’s here that something is going wrong…
And running Deuce’s famous rescue script has saved/recovered countless people and their device (taimen)…it definitely is a good idea to attempt it…
But, then again, this is assuming that you made sure to run (and successfully execute) the fastboot command “fastboot flashing unlock” and/or (depending on your bootloader version) “fastboot flashing unlock_critical”.
Good luck, hopefully you can get back to me/us on some of this stuff, and hopefully all this ends up being helpful…

simplepinoi177 said:
if you can confirm a couple things for me....
Are you actually getting into the recovery, but not seeing any "items"; because in stock recovery, you just see a broken/dead android image, and only get selections revealed/not-hidden but holding the volume-up & power button at the same time momentarily.
But, then again, you claim that you have attempted to "sideload the ota in recovery", so I imagine you already did this…but then, again again, you don’t describe what “error” or outcome actually happened and it could possibly be that, when you attempted, you just couldn’t or didn’t know how to get into the stock recovery…
Also, the recovery resides in the boot partition; I suggest you download the Full Factory image file (from the Google Developers site), extract it until you can find the boot.img, then manually flash it to overwrite and maybe fix the boot & recovery; to further explain, copy the extracted “boot.img” file to platform-tools folder where adb and fastboot reside, then run the command “fastboot flash boot boot.img” – although, if the flash-all is successfully executed, it would be doing this anyways…..
Which brings me to my next thing…if you could edit the “flash-all.bat” file and remove the word “exit” at the end – and for that matter, if you wish to save your data, remove the -w as well – and if you could please copy the output/log of you running the flash-all; usually this resolves everything & it all, so maybe it’s here that something is going wrong…
And running Deuce’s famous rescue script has saved/recovered countless people and their device (taimen)…it definitely is a good idea to attempt it…
But, then again, this is assuming that you made sure to run (and successfully execute) the fastboot command “fastboot flashing unlock” and/or (depending on your bootloader version) “fastboot flashing unlock_critical”.
Good luck, hopefully you can get back to me/us on some of this stuff, and hopefully all this ends up being helpful…
Click to expand...
Click to collapse
yes i've tried everything you've suggested (flashing boot separately/removing exit from flash-all/running deuces script), however i haven't been able to access the recovery since i last messaged so i haven't been able to retry an ota flash from recovery. (the screen is all black and a green line of fuzz blinks across the middle of the screen when holding power and volume up) i did however get into it successfully once, and when i did there were no errors at all.
the strange thing is there are no errors when flashing either. it just does not get passed "Google" without rebooting. i just tried another flash-all after flashing unlock & unlock_critical so here is the full log in case im missing something:
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32480 KB)...
OKAY [ 0.847s]
writing 'bootloader_b'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 4.107s]
finished. total time: 4.965s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.051s
target reported max download size of 536870912 bytes
sending 'radio_b' (57156 KB)...
OKAY [ 1.434s]
writing 'radio_b'...
OKAY [ 0.458s]
finished. total time: 1.903s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.055s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1908071822
Baseband Version.....: 8996-130361-1905270421
Serial Number........: FXXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.046s]
checking version-baseband...
OKAY [ 0.046s]
sending 'boot_b' (30793 KB)...
OKAY [ 0.797s]
writing 'boot_b'...
OKAY [ 0.294s]
erasing 'system_b'...
OKAY [ 0.316s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 13.692s]
writing 'system_b' 1/4...
OKAY [ 3.460s]
sending sparse 'system_b' 2/4 (524284 KB)...
OKAY [ 13.802s]
writing 'system_b' 2/4...
OKAY [ 3.481s]
sending sparse 'system_b' 3/4 (524284 KB)...
OKAY [ 13.816s]
writing 'system_b' 3/4...
OKAY [ 3.451s]
sending sparse 'system_b' 4/4 (461052 KB)...
OKAY [ 11.950s]
writing 'system_b' 4/4...
OKAY [ 3.087s]
erasing 'system_a'...
OKAY [ 0.246s]
sending 'system_a' (298348 KB)...
OKAY [ 7.005s]
writing 'system_a'...
OKAY [ 2.036s]
erasing 'vendor_b'...
OKAY [ 0.112s]
sending 'vendor_b' (259272 KB)...
OKAY [ 6.400s]
writing 'vendor_b'...
OKAY [ 1.747s]
Setting current slot to 'b'...
OKAY [ 0.081s]
erasing 'userdata'...
OKAY [ 1.853s]
sending 'userdata' (138957 KB)...
OKAY [ 3.089s]
writing 'userdata'...
OKAY [ 1.293s]
rebooting...
finished. total time: 92.497s
Press any key to exit...

ku81na said:
yes i've tried everything you've suggested (flashing boot separately/removing exit from flash-all/running deuces script), however i haven't been able to access the recovery since i last messaged so i haven't been able to retry an ota flash from recovery. (the screen is all black and a green line of fuzz blinks across the middle of the screen when holding power and volume up) i did however get into it successfully once, and when i did there were no errors at all.
the strange thing is there are no errors when flashing either. it just does not get passed "Google" without rebooting. i just tried another flash-all after flashing unlock & unlock_critical so here is the full log in case im missing something:
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32480 KB)...
OKAY [ 0.847s]
writing 'bootloader_b'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 4.107s]
finished. total time: 4.965s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.051s
target reported max download size of 536870912 bytes
sending 'radio_b' (57156 KB)...
OKAY [ 1.434s]
writing 'radio_b'...
OKAY [ 0.458s]
finished. total time: 1.903s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.055s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1908071822
Baseband Version.....: 8996-130361-1905270421
Serial Number........: FXXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.046s]
checking version-baseband...
OKAY [ 0.046s]
sending 'boot_b' (30793 KB)...
OKAY [ 0.797s]
writing 'boot_b'...
OKAY [ 0.294s]
erasing 'system_b'...
OKAY [ 0.316s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 13.692s]
writing 'system_b' 1/4...
OKAY [ 3.460s]
sending sparse 'system_b' 2/4 (524284 KB)...
OKAY [ 13.802s]
writing 'system_b' 2/4...
OKAY [ 3.481s]
sending sparse 'system_b' 3/4 (524284 KB)...
OKAY [ 13.816s]
writing 'system_b' 3/4...
OKAY [ 3.451s]
sending sparse 'system_b' 4/4 (461052 KB)...
OKAY [ 11.950s]
writing 'system_b' 4/4...
OKAY [ 3.087s]
erasing 'system_a'...
OKAY [ 0.246s]
sending 'system_a' (298348 KB)...
OKAY [ 7.005s]
writing 'system_a'...
OKAY [ 2.036s]
erasing 'vendor_b'...
OKAY [ 0.112s]
sending 'vendor_b' (259272 KB)...
OKAY [ 6.400s]
writing 'vendor_b'...
OKAY [ 1.747s]
Setting current slot to 'b'...
OKAY [ 0.081s]
erasing 'userdata'...
OKAY [ 1.853s]
sending 'userdata' (138957 KB)...
OKAY [ 3.089s]
writing 'userdata'...
OKAY [ 1.293s]
rebooting...
finished. total time: 92.497s
Press any key to exit..
.
Click to expand...
Click to collapse
Curious....
I would suggest you try Deuce's script -- again, it has assisted and recovered countless taimens. And, if that doesn't help, I would suggest you try temporarily booting into TWRP custom recovery. If you do not know how to do that, download the TWRP .img file from twrp.me (you'll have to direct yourself to the Google Pixel 2 XL [taimen] section), put it where you put the flash-all and other image files, then run the fastboot command "fastboot boot twrp.img" (replace "twrp.img" with the actual filename of the twrp image file). There you can erase/format the system and/or other partitions, or even "repair" the filesystem! You can also run adb commands, so you might have some luck and be able to install/flash an OTA image file as well....
Good luck and hope this helps...!

Flash a custom rom without recovery (using fastboot)

Are there roms to flash with fastboot ? Since I can't boot to recovery (local on my pc or on the phone).

robuser007 said:
Are there roms to flash with fastboot ? Since I can't boot to recovery (local on my pc or on the phone).
Click to expand...
Click to collapse
TrebleGSI - Browse /LiR/2022.03.25 at SourceForge.net
sourceforge.net

How do I flash this? I only find an img file
which one do I need?
How do I flash this? I only find an img file
which one do I need?
kirichen said:
TrebleGSI - Browse /LiR/2022.03.25 at SourceForge.net
sourceforge.net
Click to expand...
Click to collapse

robuser007 said:
which one do I need?
Click to expand...
Click to collapse
Install TrebleInfo.apk from google play and run, give me the screenshot
kirichen said:
Install TrebleInfo.apk from google play and run, give me the screenshot
Click to expand...
Click to collapse
<ARCH>_xyZ
<ARCH> can be arm, a64(arm32_binder64) or arm64
x can be a or b
y can be v, o, g or f
Z can be N, S or Z
b = a/b
a = a-only
g = gapps
o = gapps-go
v = vanilla (no built-in gapps)
f = floss (free & open source apps instead of gapps)
N = no phh-superuser and su (no root)
S = integrated with su, sometimes with phh-superuser
Z = extended dynamic root, su plus phh-superuser (you can enable/disable root without rebooting)
-vndklite, -lite = Android 11 builds for VNDK Lite vendors (view via Treble Info app)
that is, for example, "arm64_avN" is ARM64 A-only vanilla (without gapps) and without root
robuser007 said:
How do I flash this?
Click to expand...
Click to collapse
unzip systemA11.img
install fastboot for your platform
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
kirichen said:
unzip systemA11.img
install fastboot for your platform
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Click to expand...
Click to collapse
Install Android 11 GSI for App Testing | Android Developers
In this codelab, you will install Android 11 Generic System Image (GSI) to Android 9 (Pie) devices. After that, you can develop and validate your application with the new OS!
developer.android.com
robuser007 said:
How do I flash this?
Click to expand...
Click to collapse
In general, 3 things are needed to use Android GSI:
a device is fully Treble compliant (Treble support is mandatory for devices launched with Android 9 or later).
the device's bootloader could be unlocked.
the tools and procedures to update OS for the device.
robuser007 said:
Oneplus Nord
Click to expand...
Click to collapse
old phone!!! not this one

kirichen said:
In general, 3 things are needed to use Android GSI:
a device is fully Treble compliant (Treble support is mandatory for devices launched with Android 9 or later).
the device's bootloader could be unlocked.
the tools and procedures to update OS for the device.
adb devices
adb reboot bootloader
fastboot devices
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase system
fastboot flash system systemA11.img
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
Thanks, I'll try, can't boot to the system and booting to a recovery is crashing my phone (f.e
fastboot boot twrpname.img). I guess it's a hardbrick.
I get an error trying this command:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot --disable-verity --disable-verification flash vbmeta D:\P2a42_S244_170725_ROW_fastboot\P2a42_S244_170725_ROW_fastboot\SW\vbmeta.img
fastboot: unknown option -- disable-verity
https://sourceforge.net/projects/treblerom/files/LiR/2022.03.25/lir-v316-220325-arm64-bvZ.img.xz is ok to use?
It's my old backup phone that once crashed, not for the Nord I have.

robuser007 said:
How do I flash this? I only find an img file
which one do I need?
Click to expand...
Click to collapse
fastboot devices
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase system
fastboot flash system systemA11.img
fastboot -w
fastboot reboot
robuser007 said:
is ok to use?
Click to expand...
Click to collapse
it depends on screenshot of TrebleInfo.apk
robuser007 said:
my old backup phone that once crashed
Click to expand...
Click to collapse
what is the name of your phone? Have you backup? Can you give me the link to google disk with back up?
robuser007 said:
fastboot: unknown option -- disable-verity
Click to expand...
Click to collapse
fastboot --version
fastboot version 33.0.2-8557947 ?????
Did you unlock your bootloader?
fastboot getvar unlocked
(true OR false) (yes OR no) ?????

kirichen said:
fastboot --version
fastboot version 33.0.2-8557947 ?????
Did you unlock your bootloader?
https://www.getdroidtips.com/unlock-bootloader-mediatek-device/
fastboot getvar unlocked
(true OR false) (yes OR no) ?????
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar unlocked
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
unlocked: unlocked
finished. total time: 0.025s
It's a Lenovo p2 (Eu version). I don't have any backup anymore since I couldn,'t boot into recovery.

robuser007 said:
It's a Lenovo p2 (Eu version
Click to expand...
Click to collapse
forget about all we talk before....It was for Android 9 and higher A10, A11/ Your firmware is Android 6 or 7
Яндекс
Найдётся всё
disk.yandex.ru
I don't know what was your official firmware , here is the instruction to flash your phone
--------------------------------------------
Instruction to flash a firmware via fastboot
For unlocked devices!
Applies to firmware 6/62;7/232;7/233;7/244;7/251
1. Download the firmware, unpack it on a PC.
2. Install all drivers for ADB/FASTBOOT operation.
3. Download and unpack the attached archive- Attached file RESTORE_UNLOCK_DEVICES.zip ( 613.53 KB )
4. Move the files from the RESTORE_UNLOCK_DEVICES folder to the SW folder with the firmware files. In firmware 251, move the files to the Images folder.
5. Reboot the phone into FASTBOOT mode (disconnect the phone from the PC, turn off the phone, hold the power and volume down at the same time) and connect the phone to the PC.
6. Run the shortcut - START in the firmware folder.bat
Wait for the firmware installation to finish. The phone will reboot into the system .
7. After switching on, apply the regional code by dialing ###682 in the dialer#
Addition:
If there is a need to flash the phone without losing user data, then in the START file.bat you need to delete the line - fastboot flash userdata userdata.img
To do this, right-click on the file and open it using any text editor on a PC. Then save it.
robuser007 said:
since I couldn,'t boot into recovery.
Click to expand...
Click to collapse
May be simple
fastboot -w
help you? erase all your data( wipe, format) and you can boot into system.
Lenovo Vibe P2 - Получение ROOT прав
Получение ROOT прав на Lenovo Vibe P2 - Android 6.0 Установка TWRP и получение ROOT возможно только после разблокировки загрузчика! ...
lenovo--forums-ru.translate.goog

kirichen said:
May be simple
fastboot -w
help you? erase all your data( wipe, format) and you can boot into system.
Lenovo Vibe P2 - Получение ROOT прав
Получение ROOT прав на Lenovo Vibe P2 - Android 6.0 Установка TWRP и получение ROOT возможно только после разблокировки загрузчика! ...
lenovo--forums-ru.translate.goog
Click to expand...
Click to collapse
Tried, but didn't help
fastboot boot d:\recovery_kuntao.img f.e. crashes my fastboot and doesn't boot to recovery.
kirichen said:
forget about all we talk before....It was for Android 9 and higher A10, A11/ Your firmware is Android 6 or 7
Яндекс
Найдётся всё
disk.yandex.ru
I don't know what was your official firmware , here is the instruction to flash your phone
--------------------------------------------
Instruction to flash a firmware via fastboot
For unlocked devices!
Applies to firmware 6/62;7/232;7/233;7/244;7/251
1. Download the firmware, unpack it on a PC.
2. Install all drivers for ADB/FASTBOOT operation.
3. Download and unpack the attached archive- Attached file RESTORE_UNLOCK_DEVICES.zip ( 613.53 KB )
4. Move the files from the RESTORE_UNLOCK_DEVICES folder to the SW folder with the firmware files. In firmware 251, move the files to the Images folder.
5. Reboot the phone into FASTBOOT mode (disconnect the phone from the PC, turn off the phone, hold the power and volume down at the same time) and connect the phone to the PC.
6. Run the shortcut - START in the firmware folder.bat
Wait for the firmware installation to finish. The phone will reboot into the system .
7. After switching on, apply the regional code by dialing ###682 in the dialer#
Addition:
If there is a need to flash the phone without losing user data, then in the START file.bat you need to delete the line - fastboot flash userdata userdata.img
To do this, right-click on the file and open it using any text editor on a PC. Then save it.
Click to expand...
Click to collapse
Spoiler
PS D:\P2a42_S244_170725_ROW_fastboot\P2a42_S244_170725_ROW_fastboot\SW> .\start.bat
Active code page: 1251
ECHO is off.
...
OKAY [ -0.000s]
finished. total time: 0.016s
target reported max download size of 536870912 bytes
sending 'partition' (33 KB)...
OKAY [ 0.047s]
writing 'partition'...
OKAY [ 0.031s]
finished. total time: 0.079s
target reported max download size of 536870912 bytes
sending 'boot' (23381 KB)...
OKAY [ 0.655s]
writing 'boot'...
OKAY [ 0.186s]
finished. total time: 0.852s
target reported max download size of 536870912 bytes
sending 'recovery' (27119 KB)...
OKAY [ 0.736s]
writing 'recovery'...
OKAY [ 0.248s]
finished. total time: 1.000s
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.459s]
writing 'dsp'...
OKAY [ 0.129s]
finished. total time: 0.607s
target reported max download size of 536870912 bytes
sending 'system' (257817 KB)...
OKAY [ 6.948s]
writing 'system'...
OKAY [ 2.095s]
finished. total time: 9.073s
target reported max download size of 536870912 bytes
sending 'system' (257941 KB)...
OKAY [ 7.120s]
writing 'system'...
OKAY [ 1.784s]
finished. total time: 8.904s
target reported max download size of 536870912 bytes
sending 'system' (257344 KB)...
OKAY [ 7.215s]
writing 'system'...
OKAY [ 1.846s]
finished. total time: 9.061s
target reported max download size of 536870912 bytes
sending 'system' (257491 KB)...
OKAY [ 7.029s]
writing 'system'...
OKAY [ 1.832s]
finished. total time: 8.887s
target reported max download size of 536870912 bytes
sending 'system' (260519 KB)...
OKAY [ 7.220s]
writing 'system'...
OKAY [ 1.953s]
finished. total time: 9.185s
target reported max download size of 536870912 bytes
sending 'system' (257935 KB)...
OKAY [ 7.024s]
writing 'system'...
OKAY [ 1.890s]
finished. total time: 8.914s
target reported max download size of 536870912 bytes
sending 'system' (254719 KB)...
OKAY [ 7.045s]
writing 'system'...
OKAY [ 2.001s]
finished. total time: 9.047s
target reported max download size of 536870912 bytes
sending 'system' (261754 KB)...
OKAY [ 7.188s]
writing 'system'...
OKAY [ 2.119s]
finished. total time: 9.322s
target reported max download size of 536870912 bytes
sending 'system' (262142 KB)...
OKAY [ 7.140s]
writing 'system'...
OKAY [ 1.936s]
finished. total time: 9.077s
target reported max download size of 536870912 bytes
sending 'system' (261321 KB)...
OKAY [ 7.251s]
writing 'system'...
OKAY [ 1.841s]
finished. total time: 9.092s
target reported max download size of 536870912 bytes
sending 'system' (254468 KB)...
OKAY [ 7.046s]
writing 'system'...
OKAY [ 1.812s]
finished. total time: 8.873s
target reported max download size of 536870912 bytes
sending 'system' (262142 KB)...
OKAY [ 7.205s]
writing 'system'...
OKAY [ 1.841s]
finished. total time: 9.061s
target reported max download size of 536870912 bytes
sending 'system' (262140 KB)...
OKAY [ 7.234s]
writing 'system'...
OKAY [ 1.890s]
finished. total time: 9.139s
target reported max download size of 536870912 bytes
sending 'system' (260859 KB)...
OKAY [ 7.218s]
writing 'system'...
OKAY [ 1.927s]
finished. total time: 9.145s
target reported max download size of 536870912 bytes
sending 'system' (69256 KB)...
OKAY [ 1.910s]
writing 'system'...
OKAY [ 0.475s]
finished. total time: 2.394s
target reported max download size of 536870912 bytes
sending 'userdata' (297806 KB)...
OKAY [ 8.046s]
writing 'userdata'...
OKAY [ 2.155s]
finished. total time: 10.216s
target reported max download size of 536870912 bytes
sending 'fsg' (304 KB)...
OKAY [ 0.031s]
writing 'fsg'...
OKAY [ 0.016s]
finished. total time: 0.077s
erasing 'cache'...
OKAY [ 0.032s]
finished. total time: 0.032s
...
OKAY [ -0.000s]
finished. total time: 0.016s
Press any key to continue . . .
rebooting...
finished. total time: 0.016s
PS D:\P2a42_S244_170725_ROW_fastboot\P2a42_S244_170725_ROW_fastboot\SW>
Done, boot stays on Lenovo boot logo, I guess it's really hard bricked (something must be broken). Thanks for your help!