How to flash factory image? - Google Pixel XL Questions & Answers

I'm not new to flashing the images... But Jesus Christ there's a lot going on with the pixel... There's not just a system, vendor, boot, recovery, and cache IMG now... There's a ****load and I'm not sure how to flash them... And when I run the flash all.bat I keep getting an error during the flash and it just pauses... Same goes for the skipsoft tool. Anyone know how to flash these?

Drivers. Search on how to verify your drivers are up to date and installed.

Am I able to flash the images separately though? I do I have to use the flash all script?

swapavi said:
Am I able to flash the images separately though? I do I have to use the flash all script?
Click to expand...
Click to collapse
Not usually.
And some dev's hate the bat due to Windows being stupid sometimes.
Many folks will flash individual files one at a time.
I however, am unfamiliar with the Pixel XL partition setup too, so I would totally wait for a higher level dev to come along and answer before I do anything.
I actually posted a similar question in the factory images thread over on the development sub forum for Pixel XL.

I am also having issue flashing the marlin-nde63p using the flash-all.bat with the 128GB Pixel XL phone from google. It keeps erroring out with the following [FAILED (remote: partition [boota] doesn't exist)]. Anyone know how to fix this?
C:\pixelxl\marlin-nde63p>
C:\pixelxl\marlin-nde63p>flash-all
target reported max download size of 536870912 bytes
sending 'bootloadera' (32820 KB)...
OKAY [ 0.823s]
writing 'bootloadera'...
(bootloader) Valid bootloader version.
OKAY [ 1.046s]
finished. total time: 1.877s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.018s
target reported max download size of 536870912 bytes
sending 'radioa' (57048 KB)...
OKAY [ 1.349s]
writing 'radioa'...
OKAY [ 0.895s]
finished. total time: 2.251s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.018s
< 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........:XXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.047s]
checking version-baseband...
OKAY [ 0.046s]
sending 'boota' (26481 KB)...
OKAY [ 0.689s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.156s
Press any key to exit...

Ok I literally just did this because I messed up my pixel xl 128gb after rooting it today.
First off I had my luck with minimum adb and fastboot, install it and go to your computer and find where its downloaded. (Ex. Mine was in C:> programs x86> minimal adb and fastboot folder). After you have located, find you image you just downloaded from Google and extract the files there should be 6 (I am a Verizon user and used the H update from the Google site). Copy all those 6 extracted files into that folder you located earlier (minimal adb and fastboot) and just click on the flash-all file you just dropped in there an sit back and let it do its thing

jscharf10 said:
Ok I literally just did this because I messed up my pixel xl 128gb after rooting it today.
First off I had my luck with minimum adb and fastboot, install it and go to your computer and find where its downloaded. (Ex. Mine was in C:> programs x86> minimal adb and fastboot folder). After you have located, find you image you just downloaded from Google and extract the files there should be 6 (I am a Verizon user and used the H update from the Google site). Copy all those 6 extracted files into that folder you located earlier (minimal adb and fastboot) and just click on the flash-all file you just dropped in there an sit back and let it do its thing
Click to expand...
Click to collapse
------------------------------
hi all semi-noob here... pls excuse any silly comments i make
background - i have twrp installed on my vzn pixel xl... bootloader is unlocked
so i copied all the 6 extracted files into the minimal adb and fastboot folder
i ran the flash-all file
cmd window popped up and just says "< waiting for any device >"
my phone is plugged into my pc via usb cable
question - what mode do i need to be in to flash the factory image?

@peterlee928
2 simple things to make sure one you have all your drivers installed and two that you are in bootloader mode!
---------- Post added at 04:55 PM ---------- Previous post was at 04:54 PM ----------
[/COLOR @peterlee928
2 simple things to make sure one you have all your drivers installed and two that you are in bootloader mode!

jscharf10 said:
@peterlee928
2 simple things to make sure one you have all your drivers installed and two that you are in bootloader mode!
---------- Post added at 04:55 PM ---------- Previous post was at 04:54 PM ----------
[/COLOR @peterlee928
2 simple things to make sure one you have all your drivers installed and two that you are in bootloader mode!
Click to expand...
Click to collapse
thx jscharf

Use The Unified Android Toolkit
swapavi said:
I'm not new to flashing the images... But Jesus Christ there's a lot going on with the pixel... There's not just a system, vendor, boot, recovery, and cache IMG now... There's a ****load and I'm not sure how to flash them... And when I run the flash all.bat I keep getting an error during the flash and it just pauses... Same goes for the skipsoft tool. Anyone know how to flash these?
Click to expand...
Click to collapse
I had the exact same issue that you are having, another user on here recommended that I use the Unified Android Toolkit to flash the factory image. It works perfectly, and also has a bunch of other useful features (some will be more useful as the community figures out this system partition thing).
The toolkit is great and no necessary features must be paid for. This will solve your error issue. Best of luck!
Find the toolkit here: https://skipsoft.net/

Related

[Q] Tried to come back from the Android L preview, now I have a bricked tablet

I was trying out the Android L preview, and decided that I've had my fun and wanted to go back to the ROM I was using. I booted into recovery, and noticed that the stock recovery had been flashed. So, I downloadeed the lasted TWRP and flashed it through fastboot. When I tried to boot into recovery again, it froze at the Google screen. Since I already had everything backed up, I decided to just flash the stock image and try again. This is where the real trouble begins. The flash failed (output below), and now I can't boot into android as well as recovery. I tried a few different images (all from the official site, all marked razor), as well as the Nexus Root Toolkit, and all give me the same error(s).
So, how bad did I mess up?
Code:
C:\Android\razor-ktu84p>fastboot flash bootloader bootloader-flo-flo-04.02.img
sending 'bootloader' (3911 KB)...
OKAY [ 0.135s]
writing 'bootloader'...
FAILED (remote: Signature mismatched!!!)
finished. total time: 1.024s
C:\Android\razor-ktu84p>fastboot -w update image-razor-ktu84p.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'tos.img'
Creating filesystem with parameters:
Size: 13052653568
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3186683
Block groups: 98
Reserved block group size: 783
Created filesystem with 11/798112 inodes and 90699/3186683 blocks
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 09f8f0db
--------------------------------------------
checking product...
OKAY [ 0.004s]
checking version-bootloader...
OKAY [ 0.006s]
sending 'boot' (7050 KB)...
OKAY [ 0.234s]
writing 'boot'...
OKAY [ 0.308s]
sending 'recovery' (7598 KB)...
OKAY [ 0.256s]
writing 'recovery'...
OKAY [ 0.340s]
erasing 'system'...
OKAY [ 0.126s]
sending 'system' (736772 KB)...
OKAY [ 23.632s]
writing 'system'...
FAILED (remote: Unknown chunk type)
finished. total time: 25.676s
That error is usually due to an incompatible fastboot, first try doing a: fastboot erase system
...then try to flash system.img manually again.
Make sure you have the newest fastboot, one that is new as Android L bootloader.
NOTE: DO NOT erase bootloader! This will hardbrick you.
BTW, this is one of the reasons why I use multirom!
mdamaged said:
That error is usually due to an incompatible fastboot, first try doing a: fastboot erase system
...then try to flash system.img manually again.
Make sure you have the newest fastboot, one that is new as Android L bootloader.
NOTE: DO NOT erase bootloader! This will hardbrick you.
BTW, this is one of the reasons why I use multirom!
Click to expand...
Click to collapse
The only img file I have is the bootloader. Is what what you mean?
Also, that seems like a tool I should really have.
StormConjurer said:
The only img file I have is the bootloader. Is what what you mean?
Also, that seems like a tool I should really have.
Click to expand...
Click to collapse
I assume you have the factory image for your old rom, in that package there is a zip file, if you extract it, you will find, among others, a img file named system.img. This is one of the files that is failing to flash.
The bootloader image is failing to flash because it is older than the one that is on there now (the Android L one), so fastboot does not recognize that new Android L bootloader because it expects one of the pre-L bootloaders, so you may have to grab the developers SDK and use that fastboot so it will recognize the newer bootloader.
mdamaged said:
I assume you have the factory image for your old rom, in that package there is a zip file, if you extract it, you will find, among others, a img file named system.img. This is one of the files that is failing to flash.
The bootloader image is failing to flash because it is older than the one that is on there now (the Android L one), so fastboot does not recognize that new Android L bootloader because it expects one of the pre-L bootloaders, so you may have to grab the developers SDK and use that fastboot so it will recognize the newer bootloader.
Click to expand...
Click to collapse
I installed the SDK platform for Android L through the SDK manager, but I'm still getting the exact same error.
I suppose it's also worth mentioning that even if I try to flash the L preview, I still get the same error.
StormConjurer said:
I installed the SDK platform for Android L through the SDK manager, but I'm still getting the exact same error.
I suppose it's also worth mentioning that even if I try to flash the L preview, I still get the same error.
Click to expand...
Click to collapse
Well, have you tried this? http://forum.xda-developers.com/showthread.php?t=2381582
Read the whole OP, you can and should obviously skip the relocking of the bootloader.
Try the Recovery_Nexus7.bat first, if that fails then goto the Dead_Nexus7.bat.
It probably will get you nowhere, but it's worth a shot, obviously if it works, it will wipe everything and put it back to factory.
I solved this simply... By using Nexus Root Toolkit and using Flash Stock and Unroot. Went back to 4.4.4, but you can flash back to any version this way. It will download the ROM you want and flash it with you I having to do basically nothing.
If you are in a boot loop, there's an option for that right under the flash stock and unroot option.
Sorry for the absence. Had a busy few days.
mdamaged said:
Well, have you tried this? http://forum.xda-developers.com/showthread.php?t=2381582
Read the whole OP, you can and should obviously skip the relocking of the bootloader.
Try the Recovery_Nexus7.bat first, if that fails then goto the Dead_Nexus7.bat.
It probably will get you nowhere, but it's worth a shot, obviously if it works, it will wipe everything and put it back to factory.
Click to expand...
Click to collapse
Nope, same results as before.
mhannigan said:
I solved this simply... By using Nexus Root Toolkit and using Flash Stock and Unroot. Went back to 4.4.4, but you can flash back to any version this way. It will download the ROM you want and flash it with you I having to do basically nothing.
If you are in a boot loop, there's an option for that right under the flash stock and unroot option.
Click to expand...
Click to collapse
Like I said in the first post, Nexus Root Toolkit is one of the methods I tried. There's an option to force flash, but I've been trying to avoid that, since it warns of hard bricking the device. I'm quickly running out of options though.
Update: Tried again with force mode turned on. No change in the results.

Bootloader Reports Unlocked, Unable to Flash Custom Recovery/Re-Lock Bootloader

Greetings,
So I suppose I made the mistake of not locking the bootloader before flashing the factory NRD91D image. Current situation is that my Pixel C is reporting unlocked bootloader but I can't flash TWRP. Fastboot indicates a successful recovery flash but when booting into recovery it comes up with the sad little dead android and "No command".
My goal is to get rooted N, obviously. TWRP would be nice.
I think I read somewhere that I can:
1. Flash factory 6.0.1
2. Flash TWRP
3. Wipe everything
4. Root
5. Lock bootloader
6. Flash factory OTA to N using Flashfire with SuperSU Injection.
I've been trying adb fastboot and I sprung for skipsoft hoping it could magically bail me out but no luck.
Anybody else stuck in this situation? Does anybody have 7.0.0 rooted with TWRP? If so what steps did you use?
Thanks in advance for any help or advice.
I been using Skipsoft and its saying the device is unlocked. The bootloader screen says its unlocked at the bottom, but also says no recovery OS is corrupted. I've tried to lock it with oem lock/unlock as well as flashing unlock. The system does not report errors while unlocking/locking, but I'm unable to flash anything.
sending 'bootloader' (16384 KB)...
OKAY [ 0.423s]
writing 'bootloader'...
FAILED (remote: unsupported command)
or
$ fastboot boot twrp.img
creating boot image...
creating boot image - 13035520 bytes
downloading 'boot.img'...
OKAY [ 0.388s]
booting...
FAILED (remote: image verification failed)
finished. total time: 0.391s
This happens on my Mac and Windows machine (in case someone thinks its a driver issue)
type fastboot flashing/flash lock ( try flash or flashing)
wait that user data partition is regolar formatted
and now you are able of unlock and wait for userdata formatted
now you can flash rom
Alessandro999 said:
type fastboot flashing/flash lock ( try flash or flashing)
wait that user data partition is regolar formatted
and now you are able of unlock and wait for userdata formatted
now you can flash rom
Click to expand...
Click to collapse
Thank for replying.
Keep in mind When I click [Reboot into Android Recovery] it only reboots to the bootloader I've included a picture of that.
jatilq$ ./fastboot flashing lock
...
OKAY [ 3.963s]
finished. total time: 3.963s
jatilq$ ./fastboot flashing unlock
...
OKAY [ 2.306s]
finished. total time: 2.306s
jatilq$ ./fastboot boot twrp.img
< waiting for any device >
creating boot image...
creating boot image - 13035520 bytes
downloading 'boot.img'...
OKAY [ 0.369s]
booting...
FAILED (remote: image verification failed)
finished. total time: 0.372s
jatilq$ ./fastboot oem lock
...
OKAY [ 23.284s]
finished. total time: 23.284s
jatilq$ ./fastboot oem unlock
...
OKAY [ 2.683s]
finished. total time: 2.683s
jatilq$ ./fastboot flash bootloader bootloader-dragon-google_smaug.7900.67.0.img
target reported max download size of 268435456 bytes
sending 'bootloader' (16384 KB)...
OKAY [ 0.480s]
writing 'bootloader'...
FAILED (remote: unsupported command)
finished. total time: 0.482s
It finishes about 5 min after 'archive does not contain system.sig
jatilq$ ./fastboot -w update image-ryu-n2g48b.zip
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 57825820672
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14117632
Block groups: 431
Reserved block group size: 1024
Created filesystem with 11/3530752 inodes and 267682/14117632 blocks
wiping cache...
Creating filesystem with parameters:
Size: 419430400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1600
Label:
Blocks: 102400
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/25600 inodes and 3310/102400 blocks
--------------------------------------------
Bootloader Version...: Google_Smaug.7900.50.0
Baseband Version.....: N/A
Serial Number........: unknown variable
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking partition-size:system...
OKAY [ 0.016s]
erasing 'boot'...
FAILED (remote: unsupported command)
finished. total time: 0.029s
./fastboot flash boot recovery.img
target reported max download size of 268435456 bytes
erasing 'boot'...
FAILED (remote: unsupported command)
finished. total time: 0.001s
These are most of the commands I've tried. This is on my mac. The windows machine SKipSoft will say it's unlocked, but during flashing will throw back that it's locked (bootloader reports unlocked)
I included photos to show it does say it locks/unlocks.
I contacted Google and that was a disturbing experience. Both times you can tell support is reading from a script. They both promised someone from 2 tier would contact me, so far nothing. I'm willing to pay to have the thing repaired, but sadly you need the 2nd tier person to call you to even find out if that's possible.
ok but you must wait that after lock/unlock bootloader the userdata is formatted automaticcaly!
reboot into fastboot
type fastboot flashing/flash lock and waith that userdata is auto formatted
flash stock firmware
if you dont do this the error still persist due to damaged userdata partition
---------- Post added at 10:17 AM ---------- Previous post was at 10:07 AM ----------
i want help you .... i ve got this error last month and i fixed with this.... follow this tut:
- use a pc with windows 7 installed
-download google usb driver ( adb and fastboot) latest
reboot device into bootloader mode , connect it and open terminal and use fastboot flash/ flashing lock ( now pixel c will automatic format userdata partition corrupted)
after the process is ended( 5/10 minutes) you are able to back to stock ... dont try to flash tpwr , first i reccomend factory image 7.1.2 august for pixel c
after flash stock reboot configure the sofware , go on setting and if the device is already unlock reboot info fastboot and flash tpwr ( fastboot flash recovery recoveryname.img)
i reccoment latest stable tpwr
actually i have this and i have resurrection remix latest + f2fs data cache+ xceed foolowsi kernel with fsync off, zen scheduler
very smooth and fast
every time you lock/unlock bootloader you must wait that userdata is formatted by device ( this during 5/10 minutes usually)
I pasted the output before to show that I've done as you suggested several times. It says its unlocked after the lock/unlock process (look at my previous commands). Once you input those commands, you hit power to say yes and the device will reboot. The below process is from SkipSoft Android Toolkit to better explain the issue as explained in the title of this thread.
Are you ready to start? Type y[yes] or n[no]:y
Device mode detected: Fastboot Mode
Device Serial Number:
Device Bootloader State: Locked
When prompted, Press the Power button on the device to Unlock the Bootloader.
If it is already unlocked then this will just be skipped and your device will not
be wiped. After unlocking the device will reboot to recovery to erase the device.
Sending flashing unlock command to device..
Device bootloader is already unlocked so no data will be wiped
Rebooting back to Android..
rebooting...
finished. total time: -0.000s
Press any key to return to the Main Menu..
jatilq said:
erasing 'boot'...
FAILED (remote: unsupported command)
Click to expand...
Click to collapse
I had this issue and fixed it with fwtool
boot into recovery, then
Code:
adb shell
fwtool vbnv write dev_boot_fastboot_full_cap 1
jatilq said:
Thank for replying.
Keep in mind When I click [Reboot into Android Recovery] it only reboots to the bootloader I've included a picture of that.
jatilq$ ./fastboot flashing lock
...
OKAY [ 3.963s]
finished. total time: 3.963s
jatilq$ ./fastboot flashing unlock
...
OKAY [ 2.306s]
finished. total time: 2.306s
jatilq$ ./fastboot boot twrp.img
< waiting for any device >
creating boot image...
creating boot image - 13035520 bytes
downloading 'boot.img'...
OKAY [ 0.369s]
booting...
FAILED (remote: image verification failed)
finished. total time: 0.372s
jatilq$ ./fastboot oem lock
...
OKAY [ 23.284s]
finished. total time: 23.284s
jatilq$ ./fastboot oem unlock
...
OKAY [ 2.683s]
finished. total time: 2.683s
jatilq$ ./fastboot flash bootloader bootloader-dragon-google_smaug.7900.67.0.img
target reported max download size of 268435456 bytes
sending 'bootloader' (16384 KB)...
OKAY [ 0.480s]
writing 'bootloader'...
FAILED (remote: unsupported command)
finished. total time: 0.482s
It finishes about 5 min after 'archive does not contain system.sig
jatilq$ ./fastboot -w update image-ryu-n2g48b.zip
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 57825820672
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14117632
Block groups: 431
Reserved block group size: 1024
Created filesystem with 11/3530752 inodes and 267682/14117632 blocks
wiping cache...
Creating filesystem with parameters:
Size: 419430400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1600
Label:
Blocks: 102400
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/25600 inodes and 3310/102400 blocks
--------------------------------------------
Bootloader Version...: Google_Smaug.7900.50.0
Baseband Version.....: N/A
Serial Number........: unknown variable
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking partition-size:system...
OKAY [ 0.016s]
erasing 'boot'...
FAILED (remote: unsupported command)
finished. total time: 0.029s
./fastboot flash boot recovery.img
target reported max download size of 268435456 bytes
erasing 'boot'...
FAILED (remote: unsupported command)
finished. total time: 0.001s
These are most of the commands I've tried. This is on my mac. The windows machine SKipSoft will say it's unlocked, but during flashing will throw back that it's locked (bootloader reports unlocked)
I included photos to show it does say it locks/unlocks.
I contacted Google and that was a disturbing experience. Both times you can tell support is reading from a script. They both promised someone from 2 tier would contact me, so far nothing. I'm willing to pay to have the thing repaired, but sadly you need the 2nd tier person to call you to even find out if that's possible.
Click to expand...
Click to collapse
Hello,
I have the exact error that you show in the screenshots. I follow your steps and I´m stuck with the same problem. Finally you can solve the problem? I´m totally frustrated withg this tablet and need some help.
Thanks in advance.
Istvan_86 said:
Hello,
I have the exact error that you show in the screenshots. I follow your steps and I´m stuck with the same problem. Finally you can solve the problem? I´m totally frustrated withg this tablet and need some help.
Thanks in advance.
Click to expand...
Click to collapse
Unfortunately I jumped through many hoops with Google before then sent me a one time replacement. I sold the tablet and now I'm on a Samsung Galaxy Tab3.
jatilq said:
Unfortunately I jumped through many hoops with Google before then sent me a one time replacement. I sold the tablet and now I'm on a Samsung Galaxy Tab3.
Click to expand...
Click to collapse
Hello and thanks for your answer. So basically I must contact Google as you did?
I think that I'm totally done with this tablet......
Istvan_86 said:
Hello and thanks for your answer. So basically I must contact Google as you did?
I think that I'm totally done with this tablet......
Click to expand...
Click to collapse
As I said you will have to jump through many hoops. They will want you to email support, then you have to wait for a call back. Expect no one to be able to help you, even though they will keep bouncing you around. I'm not sure if its 100% guarantee they will send a replacement after a few contacts. If they do send you one, prepare to have them hold around $550 for the refurbished unit to be sent and the old one returned to them. I sold the new one as fast as I could on swappa, because of the lack of recovery options for the device and the messed up unlock/lock flag error that this thread is talking about.
Using fwtool command worked beautifully
xavierbutt said:
I had this issue and fixed it with fwtool
boot into recovery, then
Code:
adb shell
fwtool vbnv write dev_boot_fastboot_full_cap 1
Click to expand...
Click to collapse
I had a situation where I locked and unlocked in fastboot and still had TWRP recovery installed so the OS protection kicked in and prevented me from booting up normally.
I booted into TWRP recovery where TWRP has built in root access.
I copied the fwtool to the SDcard while the tablet was booted up normally using the PC but, if you can't boot up, ADB push command from a PC would have also placed the fwtool onto the tablet sdcard (adb push fwtool /sdcard).
I used the command adb shell and thus was sitting on the sdcard root where the fwtool was placed. I issued the fwtool command directly from the sdcard location. I did not copy the fwtool to any place else.
adb shell
fwtool vbnv write dev_boot_fastboot_full_cap 1
The command was successful and, I was then able to have full flash access back.
Regards galearned
Thanks @galearned your instruction saved me! Because I didn't get adb to work I used the terminal of TWRP and it worked!
---------- Post added at 09:54 PM ---------- Previous post was at 09:54 PM ----------
Thanks @galearned your instruction saved me! Because I didn't get adb to work I used the terminal of TWRP and it worked!
Thanks @galearned greatful my pixel c is worked again
---------- Post added at 03:36 PM ---------- Previous post was at 03:36 PM ----------
Thanks @galearned greatful my pixel c is worked again
Sorry for the Resurrection. Can somebody explain how they fixed this, I have the same situation exactly. Access to TWRP and fastboot etc, but the dreaded FAILED (remote: unsupported command) stops me in my tracks. I can only lock and unlock the bootloader.

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.

Cannot flash factory images to Google Pixel 2 XL

I'm trying to root my phone, but I can't flash any boot or recovery images to it, whether that's the patched boot.img, TWRP, or even the stock factory images themselves. I've already unlocked the bootloader, using
Code:
fastboot flashing unlock_critical
.
I am running the newest version of adb and fastboot, downloaded yesterday:
Code:
$ fastboot --version
fastboot version 0.0.1-4500957
Installed as [REDACTED]
$ adb version
Android Debug Bridge version 1.0.39
Version 0.0.1-4500957
Installed as [REDACTED]
When I try to flash the stock factory images, downloaded straight from Google, I get this series of errors:
Code:
$ adb reboot bootloader
$ ./flash-all.sh
target didn't report max-download-size
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.000s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.201s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.000s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.201s
extracting android-info.txt (0 MB) to RAM...
Warning: Could not determine slot for secondary images. Ignoring.
extracting boot.img (40 MB) to disk... took 0.289s
target didn't report max-download-size
archive does not contain 'boot.sig'
extracting dtbo.img (8 MB) to disk... took 0.039s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1936 MB) to disk...
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (349 MB) to disk... took 4.445s
error: Failed to identify current slot
Other fastboot commands also fail with inconsistent error messages and failure modes:
Code:
$ fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (40960 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.000s
If I try with the -S flag:
Code:
$ fastboot -S 512K flash boot boot.img
Invalid sparse file format at header magic
sending sparse 'boot' 1/51 (508 KB)...
which hangs indefinitely, never sending even the first segment.
I can try booting directly, which yields the same problem:
Code:
$ fastboot boot boot.img
downloading 'boot.img'...
# hangs indefinitely
Similarly,
Code:
$ fastboot --set-active=_a
hangs indefinitely as well. I have to restart the bootloader to kill it, at which point it just prints the confusing error:
Code:
Device does not support slots
(the Pixel 2 XL does support slots!).
The error messages aren't always consistent; sometimes the first fastboot flash boot boot.img command will appear to hang (requiring a restart, similar to
Code:
--set-active
) instead of printing the error message about max-download-size. I've let that run for about fifteen minutes before having to kill it. Unlike system.img, boot.img is only about 40MB, so it shouldn't take that long to flash - something is clearly wrong.
I've also tried this with multiple cables on different USB ports, with the same sorts of results each time.
Am I missing a step? How can I flash the factory images and the patched boot.img?
Most likely not model specific issue but the Pixel-2XL forum:
https://forum.xda-developers.com/pixel-2-xl/help
i have the same problem, and it seems nothing works, tried every single solution on the internet i could find, multiple cables, adb/fastboot up to date
exact same problem as OP
chimeracoder said:
I'm trying to root my phone, but I can't flash any boot or recovery images to it, whether that's the patched boot.img, TWRP, or even the stock factory images themselves. I've already unlocked the bootloader, using
Code:
fastboot flashing unlock_critical
.
Click to expand...
Click to collapse
You're in the wrong forum, using the wrong unlock command, depending on whether you have Pixel 2 or Pixel 2 XL and likely using the wrong factory image too.
You're in the Pixel 2 forum (5" model), not Pixel 2 XL (6" model). You need to go here; https://forum.xda-developers.com/pixel-2-xl/help
You need to make sure you enable developer option on phone first - then in developer option, tick - allow OEM Unlocking, and USB debugging
then it should allow you to go ahead as you have.
Check this out here. Your issue happens when you play around with the bootloader settings and something gets borked. This tool saved me from having to RMA.
EDIT: Never mind, the culprit was the USB C x USB C cable I was using at the office. Back home, I used my USB A x USB C cable and was able to recover the device.
I'm having the exact same problem! I have a Pixel 2, at January 8.1.0 version (OPM1.171019.013). It was rooted with Magisk latest version. Today I decided to reflash the firmware, without wipe, and the flashing was not successful. Now I'm afraid I have a small brick in my hands.
I'm now using the latest fastboot (0.0.1-4500957) and adb (1.0.39 / 0.0.1-4500957) versions. I don't know if I was on the latest versions when I tried to flash the firmware.
I always flashed the firmware using a USB A port on my Dell XPS 9560 notebook. Today I flashed from a USB C port, I don't know if this was the cause for the failed flash. I'm at the office, and I don't have a USB A x USB C cable available.
My Pixel 2 is stuck at the bootloader. Recovery mode and Download mode options don't do anything, it just goes back to the bootloader screen. Bootloader version is mw8998-002.0059.00. It tells me I'm on slot b, and I can't change slots, issuing fastboot --set-active=a either returns:
Code:
error: Device does not support slots
OR:
Code:
FAILED (remote: unknown command)
When I issue fastboot flash bootloader bootloader-walleye-mw8998-002.0066.00.img either one of these messages is displayed:
Code:
error: Failed to identify current slot
OR:
Code:
target didn't report max-download-size
sending 'bootloader' (38644 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.000s
Has anyone found a solution?
same problem。
could you solve it?
opooi said:
same problem。
could you solve it?
Click to expand...
Click to collapse
As the post above yours suggests, swap out USB cables.
If that doesn't resolve the issue, try these:
-make sure your SDK tools are up to date
-make sure your files are in the correct "platform tools" folder for using fastboot
-make sure your fastboot commands are correct
There is a link to a Pixel 2 XL "guide" in my sig, it covers most issues and processes for the 2 XL.
Az Biker said:
As the post above yours suggests, swap out USB cables.
If that doesn't resolve the issue, try these:
-make sure your SDK tools are up to date
-make sure your files are in the correct "platform tools" folder for using fastboot
-make sure your fastboot commands are correct
There is a link to a Pixel 2 XL "guide" in my sig, it covers most issues and processes for the 2 XL.
Click to expand...
Click to collapse
yes,i use platform-tools_r28.0.0-linux to fastboot,but it still failed.
I compiled AOSP to run "fastboot flashall -w" for pixel 2 xl.it showed:
target reported max download size of 536870912 bytes
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Warning: RAID stripe-width 1 not an even multiple of stride 2.
Creating filesystem with 13902843 4k blocks and 3481600 inodes
Filesystem UUID: e8137926-c3cb-4ddc-bdd1-311c79ed416c
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done
Bootloader Version...: TMZ12a
Baseband Version.....: g8998-00164-1710262031
Serial Number........: 710KPCA0244667
checking product...
OKAY [ 0.000s]
sending 'boot_b' (40960 KB)...
FAILED (data write failure (Protocol error))
finished. total time: 0.162s
Click to expand...
Click to collapse
i feel sad to cry,but i can't solve it
@opooi have you made any progress on fixing it? I've had the exact same issue even with the commands hanging. I fixed it somehow, I don't remember how. I think I booted stock recovery and factory reset. I also tried different images and cleaning my driver's and starting fresh. I was going crazy trying everything I could ever think of and then it just flashed. I'm so scared about it happening again. Also another thing to try, try to reboot bootloader a couple times back to back and see if it helps.
Some guy on Reddit just said he uninstalled magisk, then ran the flash-all and his phone started having this issue. It happened to me when I booted twrp, wiped system data cache and then booted to bootloader and tried to flash.

Google Pixel XL - Soft Brick

Hi all!
I'm not so called an "expert" on android. (I work normally on Linux ) so, my *final* goal is to install a custom rom on Google Pixel XL (marlin).
For the moment i'm trying to install the official google 8.1.0 (OPM1.171019.016, Feb 2018).
I carefully followed these 4 links:
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
https://forum.xda-developers.com/pixel-xl/development/rom-pixeldust-marlin-t3581750
https://developers.google.com/android/images#marlin
https://forum.xda-developers.com/pi...stock-soft-t3494478/post69476498#post69476498
I unlocked and rooted the "marlin" with no problems.
I installed TWRP (twrp-3.2.1-0-marlin): it works but seems do not persist and every time i want to use it i have to reinstall via fastboot (strange... what i missed?).
This is the guide followed: https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
I downloaded the official rom google 8.1.0 (OPM1.171019.016, Feb 2018) following these guides:
https://forum.xda-developers.com/pixel-xl/development/rom-pixeldust-marlin-t3581750
https://developers.google.com/android/images#marlin
https://forum.xda-developers.com/pi...stock-soft-t3494478/post69476498#post69476498
With flash-all-sh and OPM1.171019.016, Feb 2018 give me this error " fastboot too old " ( adb version revision 1:7.0.0+r33-2 )
If i write into shell this procedure at a certain point all stops and an error appears:
.......
sending 'boota' (30149 KB)...
OKAY [ 1.391s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist) <----this
finished. total time: 1.801s
Please, what i did wrong?
how to recover this error?
how to make persistent TWRP?
Anyway, is it possible that the 8.1.0 version is too new for my configuration?
Thanks a lot for any advice!
Lele
Log
[email protected]:/home/lele/Documenti/G Pixel XL/marlin-opm1.171019.016# fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (30149 KB)...
OKAY [ 1.404s]
writing 'boot_a'...
OKAY [ 0.695s]
finished. total time: 2.100s
[email protected]:/home/lele/Documenti/G Pixel XL/marlin-opm1.171019.016# fastboot flash boot_b boot.img
target reported max download size of 536870912 bytes
sending 'boot_b' (30149 KB)...
OKAY [ 1.381s]
writing 'boot_b'...
OKAY [ 0.694s]
finished. total time: 2.076s
[email protected]:/home/lele/Documenti/G Pixel XL/marlin-opm1.171019.016# fastboot flash bootloader bootloader-marlin-8996-012001-1711291800.img
target reported max download size of 536870912 bytes
sending 'bootloadera' (32248 KB)...
OKAY [ 1.505s]
writing 'bootloadera'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 15.811s]
finished. total time: 17.317s
[email protected]:/home/lele/Documenti/G Pixel XL/marlin-opm1.171019.016# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.045s]
finished. total time: 0.145s
[email protected]:/home/lele/Documenti/G Pixel XL/marlin-opm1.171019.016# fastboot flash radio radio-marlin-8996-130091-1710201747.img
target reported max download size of 536870912 bytes
sending 'radioa' (57320 KB)...
OKAY [ 2.613s]
writing 'radioa'...
OKAY [ 1.053s]
finished. total time: 3.666s
[email protected]:/home/lele/Documenti/G Pixel XL/marlin-opm1.171019.016# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.045s]
finished. total time: 0.145s
[email protected]:/home/lele/Documenti/G Pixel XL/marlin-opm1.171019.016# fastboot -w update image-marlin-opm1.171019.016.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'
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-1711291800
Baseband Version.....: 8996-130091-1710201747
Serial Number........: HT69H0207206
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.050s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boota' (30149 KB)...
OKAY [ 1.391s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.801s
UPDATE:
At the moment it's working with Android 7.1.2..... But i can't install Android 8.1...
Someone can help me?
bye
lele
Chancellor said:
UPDATE:
At the moment it's working with Android 7.1.2..... But i can't install Android 8.1...
Someone can help me?
bye
lele
Click to expand...
Click to collapse
Make sure you have the latest fastboot and ADB.
To get TWRP permanently, you have to fastboot boot the twrp.img, booting into a temporary TWRP, then flash the twrp.zip.
borxnx said:
Make sure you have the latest fastboot and ADB.
Click to expand...
Click to collapse
adb version revision 1:7.0.0+r33-2 it's the latest version?
To get TWRP permanently, you have to fastboot boot the twrp.img, booting into a temporary TWRP, then flash the twrp.zip.
Click to expand...
Click to collapse
ok i will do it
Thank you
Here is a link to the latest ADB and fastboot tools, which is what I've been using without issue on my Pixel XL on 8.1
https://www.androidpolice.com/2017/...ble-without-full-sdk-android-studio-download/
Sent from my Pixel XL using Tapatalk
Hi There.
After you installed fastboot and adb on linux (I installed adbLink for my aftv from https://www.jocala.com/ and that brings the necessary files, too. It creates a directory called adbfiles, where you can use ./adb and ./fastboot devices - worked for me), you can boot into recovery and install the 8.1.0 version for the pixel from here:
https://developers.google.com/android/ota -- you need marlin and 8.1.0 (OPM1.171019.016, Feb 2018). mv the image to the directory with the adbfiles. I find this way the easiest.
The update can easily be installed if you boot into fastboot and there chose apply update from adb and then follow the instructions on your mobile or steps 2 - 8 from the download page.
That is to update your firmware to 8.1.0 - twrp install comes after that.
OK friend, i will try !!! Thank you
borxnx said:
Here is a link to the latest ADB and fastboot tools, which is what I've been using without issue on my Pixel XL on 8.1
https://www.androidpolice.com/2017/...ble-without-full-sdk-android-studio-download/
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse

Categories

Resources