Help: sending 'system' (1550356 KB)... FAILED (remote: data too large)

Help: sending 'system' (1550356 KB)... FAILED (remote: data too large) - Google Pixel Questions & Answers

I have tried to flash a new system on my new Pixel but I am getting the above message.
I am using Ubuntu Linux with the stock android-tools-adb and andoid-tools-fastboot installed.
The same tools are working fine on my nexus5 phones.
Yes I enabled USB debugging and unlocked the bootloader.
Can anyone tell me what is different with Pixel phones?
adb version gives: Android Debug Bridge version 1.0.31

Have you tried the latest version of Android tools? I haven't used adb or fastboot with the pixel yet but know with past nexus devices I have experienced this error because I wasn't using the latest Android tools

I can't remember the exact specifics since I do not have a factory image available to me atm...
BUT, I believe you extract the contents of the image.zip and then use a text editor to individually add the flash commands for the content found inside the image.zip to the flash-all.sh (i.e. "fastboot flash system system.img.")

metricusa said:
...
adb version gives: Android Debug Bridge version 1.0.31
Click to expand...
Click to collapse
Update your ADB tools. The latest version is 1.0.36, I believe.

sn0warmy said:
Update your ADB tools. The latest version is 1.0.36, I believe.
Click to expand...
Click to collapse
This version of ADB is the latest in the ubuntu repositories. I did not find a newer version there.
Can anyone tell me how I can get a newer ADB and fastboot? It's not in the Android SDK package.
I want only the binary not the whole SDK as I have nothing to do with it.

metricusa said:
This version of ADB is the latest in the ubuntu repositories. I did not find a newer version there.
Can anyone tell me how I can get a newer ADB and fastboot? It's not in the Android SDK package.
I want only the binary not the whole SDK as I have nothing to do with it.
Click to expand...
Click to collapse
Here Download the Portable Version it worked great for me
http://forum.xda-developers.com/showthread.php?t=2317790

McMarius11 said:
Here Download the Portable Version it worked great for me
http://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
I have Ubuntu Linux. The link seems to have only windows executables.

OK so I upgraded fastboot and adb. Actually upgraded my ubuntu to latest version.
fastboot getvar version prompts version 0.5 for fastboot.
I managed to load the latest version NMF26Q onto the pixel but I am still getting an error. The Pixel appears to boot and work OK.
I am worried about the error though and wondered if anyone can figure out what it means and how I could mitigate it. See below output from flash-all.sh
Again, please remember I use Linux (ubuntu)
+++++++++++
~/Downloads/sailfish-nmf26q$ sudo ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (32728 KB)...
OKAY [ 0.831s]
writing 'bootloader'...
(bootloader) Valid bootloader version.
OKAY [ 0.709s]
finished. total time: 1.541s
rebooting into bootloader...
OKAY [ 4.155s]
finished. total time: 4.255s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (57192 KB)...
OKAY [ 1.422s]
writing 'radio'...
OKAY [ 0.564s]
finished. total time: 1.986s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.147s
< waiting for 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'
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
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
--------------------------------------------
Bootloader Version...: 8996-012001-1610061102
Baseband Version.....: 8996-012511-1611190200
Serial Number........: FAxxx
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.051s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boot' (24821 KB)...
OKAY [ 0.642s]
writing 'boot'...
(bootloader) Flashing active slot "_a"
OKAY [ 0.311s]
sending sparse 'system' (516463 KB)...
OKAY [ 12.712s]
writing 'system'...
OKAY [ 5.004s]
sending sparse 'system' (520623 KB)...
OKAY [ 12.805s]
writing 'system'...
OKAY [ 7.138s]
sending sparse 'system' (517483 KB)...
OKAY [ 12.772s]
writing 'system'...
OKAY [ 5.491s]
sending 'vendor' (235186 KB)...
OKAY [ 5.806s]
writing 'vendor'...
OKAY [ 3.796s]
erasing 'userdata'...
OKAY [ 1.805s]
sending 'userdata' (138957 KB)...
OKAY [ 3.451s]
writing 'userdata'...
OKAY [ 1.301s]
erasing 'cache'...
(bootloader) Erasing active slot "_a"
FAILED (remote: Partition table doesn't exist)
finished. total time: 73.441s

Follow Method 2 here - it worked for me, as i had the same issue as you:
http://www.theandroidsoul.com/flash-firmware-factory-image-google-pixel/

OK I finally figured it out.
To clarify, the purpose was to burn a factory image and start from scratch. (no sideload). All without having to install Android studio or the SDK manager or whatever. This is a guide for Linux but I believe this method works in Windows as well with appropriate syntax.
1. First rule is to NEVER try to use a version of fastboot other than the one "prescribed" for the image you want to burn. To learn what version to use check Google's SKD Platform release Notes here: https://developer.android.com/studio/releases/platforms.html (my major mistake was to think that ubuntu would have the latest fastboot available in its repositories. Don't even try!)
2. Find the SDK Platform Tools version indicated on the above page. (In my case: Android SDK Platform-Tools 25.0.1 as I wanted to burn Android 7.1.1.). Google does not make them available AFAIK but other people do. I found them here: http://androidsdkoffline.blogspot.com/p/android-sdk-platform-tools.html OR do a Google Search.
3. Unpack the platform tools and the Factory image you wish to burn. Then copy fastboot from the Platform Tools directory to the image directory.
4. run fastboot from inside the directory. You can do this in at least 2 ways:
4a- manually run one-by-one the commands listed in the flash-all.sh script making sure you add sudo ./ in front of each fastboot command
4b- edit flash-all.sh and add sudo ./ in front of each fastboot command. Then run the flash-all script by typing ./flash-all.sh
There are of course more ways but I found this to be the simplest method as it doesn't involve installing any package and/or modifying your system variables. Plus, after you are done you can simply delete all files and directories you created.
Hope this helps other people too.
A final observation: It appears to me that starting with pixel the phones have 2 bootable sectors "slot a" and "slot b". See output below:
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-1610061102
Baseband Version.....: 8996-012511-1611190200
Serial Number........: FAxxxx
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.051s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boot_a' (24821 KB)...
OKAY [ 0.642s]
writing 'boot_a'...
OKAY [ 0.299s]
erasing 'system_a'...
OKAY [ 0.415s]
sending sparse 'system_a' 1/3 (516463 KB)...
OKAY [ 12.799s]
writing 'system_a' 1/3...
OKAY [ 5.009s]
sending sparse 'system_a' 2/3 (520623 KB)...
OKAY [ 14.101s]
writing 'system_a' 2/3...
OKAY [ 7.052s]
sending sparse 'system_a' 3/3 (517483 KB)...
OKAY [ 12.818s]
writing 'system_a' 3/3...
OKAY [ 5.449s]
erasing 'system_b'...
OKAY [ 0.354s]
sending sparse 'system_b' 1/4 (522362 KB)...
OKAY [ 12.856s]
writing 'system_b' 1/4...
OKAY [ 3.890s]
sending sparse 'system_b' 2/4 (514082 KB)...
OKAY [ 12.758s]
writing 'system_b' 2/4...
OKAY [ 4.302s]
sending sparse 'system_b' 3/4 (524026 KB)...
OKAY [ 12.967s]
writing 'system_b' 3/4...
OKAY [ 3.839s]
sending sparse 'system_b' 4/4 (88446 KB)...
OKAY [ 2.260s]
writing 'system_b' 4/4...
OKAY [ 0.842s]
erasing 'vendor_a'...
OKAY [ 0.153s]
sending 'vendor_a' (235186 KB)...
OKAY [ 5.804s]
writing 'vendor_a'...
OKAY [ 3.846s]
Setting current slot to 'a'...
OKAY [ 0.099s]
erasing 'userdata'...
OKAY [ 1.806s]
sending 'userdata' (138957 KB)...
OKAY [ 3.451s]
writing 'userdata'...
OKAY [ 1.301s]
rebooting...
finished. total time: 129.610s

Related

[Q] Nexus 5 BootLoop SDCARD wont mount PLZ help..

Hi all,plz plz Help!!:crying:
I got my nexus 5 and tried rooting + custom recovery installation.
Found this tool on XDA
http://forum.xda-developers.com/showthread.php?t=2517802
after installing drivers and unlocking the bootloader I moved to download twrp + flash
(did not boot between steps)
the flash was successful when done, it booted into a boot loop, went back to recovery to do some wipe (dalvick, cache, data) got msg saying unable to mount storage. (pic 1,1-2)
Trying to backup got me the same result (I can tell it recognized sys partition (pic 2) , going to file manager and to sdcard showed empty folder (pic 3).
I can browse the root dir (pic 4) and can still send adb/fastboot commands to device.
Tried flashing stock using the image on Google's site
https://developers.google.com/android/nexus/images?hl=iw&csw=1#hammerheadkrt16m
using this manual
http://www.droid-life.com/2013/11/05/how-to-flash-nexus-5-factory-images/
and got this
C:\nexus 5\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030
\sdk\platform-tools>fastboot flash bootloader bootloader-hammerhead-HHZ11d.img
sending 'bootloader' (2506 KB)...
OKAY [ 0.290s]
writing 'bootloader'...
OKAY [ 0.479s]
finished. total time: 0.769s
C:\nexus 5\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030
\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
C:\nexus 5\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030
\sdk\platform-tools>fastboot flash radio radio-hammerhead-M8974A-1.0.25.0.17.img
sending 'radio' (42033 KB)...
OKAY [ 1.566s]
writing 'radio'...
OKAY [ 2.894s]
finished. total time: 4.461s
C:\nexus 5\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030
\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
C:\nexus 5\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030
\sdk\platform-tools>fastboot -w update image-hammerhead-krt16m.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ11d
Baseband Version.....: M8974A-1.0.25.0.17
Serial Number........: 0317e48a213e71ea
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.030s]
sending 'boot' (8620 KB)...
OKAY [ 30.240s]
writing 'boot'...
OKAY [ 0.740s]
sending 'recovery' (9202 KB)...
OKAY [ 33.380s]
writing 'recovery'...
OKAY [ 0.770s]
erasing 'system'...
OKAY [ 1.270s]
sending 'system' (692940 KB)...
OKAY [ 23.312s]
writing 'system'...
OKAY [ 47.394s]
erasing 'userdata'...
OKAY [ 17.182s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
critical error: extent_create_backing: calloc: Not enough space
sending 'userdata' (0 KB)...
FAILED ()
finished. total time: 156.080sa
I don’t know what else to do
Also tried flashing stock back using
[TOOLKIT] Wug's Nexus Root Toolkit v1.7.5 [Updated 11/08/13]: Nexus 5 Thread
http://forum.xda-developers.com/showthread.php?t=2517778
tiking the soft-bricked/bootloop and flashing got me this
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
and times out..
plz help me mount the internal storage (sdcard)
and flash stock once again on my device.

eyalinc said:
Hi all,plz plz Help!!:crying:
I got my nexus 5 and tried rooting + custom recovery installation.
Found this tool on XDA
http://forum.xda-developers.com/showthread.php?t=2517802
after installing drivers and unlocking the bootloader I moved to download twrp + flash
(did not boot between steps)
the flash was successful when done, it booted into a boot loop, went back to recovery to do some wipe (dalvick, cache, data) got msg saying unable to mount storage. (pic 1,1-2)
Trying to backup got me the same result (I can tell it recognized sys partition (pic 2) , going to file manager and to sdcard showed empty folder (pic 3).
I can browse the root dir (pic 4) and can still send adb/fastboot commands to device.
Tried flashing stock using the image on Google's site
https://developers.google.com/android/nexus/images?hl=iw&csw=1#hammerheadkrt16m
using this manual
http://www.droid-life.com/2013/11/05/how-to-flash-nexus-5-factory-images/
and got this
C:\nexus 5\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030
\sdk\platform-tools>fastboot flash bootloader bootloader-hammerhead-HHZ11d.img
sending 'bootloader' (2506 KB)...
OKAY [ 0.290s]
writing 'bootloader'...
OKAY [ 0.479s]
finished. total time: 0.769s
C:\nexus 5\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030
\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
C:\nexus 5\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030
\sdk\platform-tools>fastboot flash radio radio-hammerhead-M8974A-1.0.25.0.17.img
sending 'radio' (42033 KB)...
OKAY [ 1.566s]
writing 'radio'...
OKAY [ 2.894s]
finished. total time: 4.461s
C:\nexus 5\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030
\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
C:\nexus 5\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030
\sdk\platform-tools>fastboot -w update image-hammerhead-krt16m.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ11d
Baseband Version.....: M8974A-1.0.25.0.17
Serial Number........: 0317e48a213e71ea
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.030s]
sending 'boot' (8620 KB)...
OKAY [ 30.240s]
writing 'boot'...
OKAY [ 0.740s]
sending 'recovery' (9202 KB)...
OKAY [ 33.380s]
writing 'recovery'...
OKAY [ 0.770s]
erasing 'system'...
OKAY [ 1.270s]
sending 'system' (692940 KB)...
OKAY [ 23.312s]
writing 'system'...
OKAY [ 47.394s]
erasing 'userdata'...
OKAY [ 17.182s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
critical error: extent_create_backing: calloc: Not enough space
sending 'userdata' (0 KB)...
FAILED ()
finished. total time: 156.080sa
I don’t know what else to do
Also tried flashing stock back using
[TOOLKIT] Wug's Nexus Root Toolkit v1.7.5 [Updated 11/08/13]: Nexus 5 Thread
http://forum.xda-developers.com/showthread.php?t=2517778
tiking the soft-bricked/bootloop and flashing got me this
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
and times out..
plz help me mount the internal storage (sdcard)
and flash stock once again on my device.
Click to expand...
Click to collapse
Try to reflash the factory image from here https://developers.google.com/android/nexus/images in fastboot, read this http://forum.xda-developers.com/showthread.php?t=2513701 for a how to and DO NOT USE TOOLKITS ANYMORE!

The missing .Sig files is normal when flashing the stock images and nothing to be concerned about
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 01:39 PM ---------- Previous post was at 01:36 PM ----------
Do you have a 16gb or a 32.
It looks like it's trying to create a 32gb and erroring because there isn't enough free space
Sent from my Nexus 4 using xda app-developers app

10x guys so solved!
Sent from my Nexus 5 using Tapatalk

what did you end up doing?
eyalinc said:
10x guys so solved!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have same problem but the thread doesn't seem to have the solution on it. Can you tell me how you fixed the problem please?
I'm freakin losing it!!!!
Thanks

roguecomic said:
I have same problem but the thread doesn't seem to have the solution on it. Can you tell me how you fixed the problem please?
I'm freakin losing it!!!!
Thanks
Click to expand...
Click to collapse
gee2012 said:
Try to reflash the factory image from here https://developers.google.com/android/nexus/images in fastboot, read this http://forum.xda-developers.com/showthread.php?t=2513701 for a how to and DO NOT USE TOOLKITS ANYMORE!
Click to expand...
Click to collapse
guess its hard to read.

How can i flash the factory image without encrypting?

Hi all,
I recently rooted my Pixel and was plagued by the 15% battery issue. I found in the Pixel XL forum to fix it i should flash boot_a boot.img but that erased all my data.
I figured I'd start fresh and looked up a few websites who had instructions (androidcentral being one of them) and it seems like any other google phone, except i started getting FAILED to flash. so i ended up doing the following and now my device is encrypted.
fastboot flash bootloader bootloader-img
fastboot reboot bootloader
fastboot flash radio radio-img
fastboot reboot bootloader
fastboot flash boot_a boot.img
fastboot flash system_a system.img
fastboot flash userdata userdata.img
fastboot flash vendor_a vendor.img
fastboot format userdata (have to do this in order to get phone to read as 128GB)
---
so now when i boot up, it goes through the setup but it's encrypted.
I guess my question is, with the way Pixel's will be handling updates, what are all of the extra .img files from the factory image and should i be flashing them in a particular order?
here are the contents:
aboot.img
apdp.img
boot.img
bootlocker.img
cmnlib32.img
cmnlib64.img
devcfg.img
hosd.img
hyp.img
keymaster.img
modem.img
pmic.img
rpm.img
system_other.img
system.img
tz.img
userdata.img
vendor.img
xbl.img
Any assistance would be greatly appreciated!
Thanks!

EDIT #1: I just locked and then unlocked the bootloader to see if that allows me to setup as unencrypted. It's taking a while to boot so I doubt it.
EDIT #2: Still encrypted after set up.
Wellp... i wonder what flashing these after the initial order above will do...
EDOT#3:
lock / unlock botloader
fastboot flash system_a system.img
fastboot flash system_b system_other.img
... still encrypted, it booted up a bit quicker (or maybe i'm going nuts)
EDIT #4:
lock / unlock botloader
fastboot flash system_a system.img
fastboot flash system_b system_other.img
fastboot flash keymaster_a keymaster.img
andddd.... still encrypted... can anyone help out?

updating android sudio/sdk

So on the newest SDK, the fastboot flash system system.img will automatically detect and erase system_a.
probably a good idea to be on the latest sdk platform-tools

lockd / unlocked bootloader
bash update-all.sh
CRUD... still encrypted.
here's the output if anyone would like:
Code:
Marcs-MacBook-Pro:sailfish-nde63p root# bash flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32820 KB)...
OKAY [ 1.404s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
OKAY [ 1.040s]
finished. total time: 2.444s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
target reported max download size of 536870912 bytes
sending 'radio_a' (57048 KB)...
OKAY [ 2.457s]
writing 'radio_a'...
OKAY [ 0.869s]
finished. total time: 3.326s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
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: 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........: NOPE :)
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.051s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boot_a' (25073 KB)...
OKAY [ 0.982s]
writing 'boot_a'...
OKAY [ 0.600s]
erasing 'system_a'...
OKAY [ 1.201s]
sending sparse 'system_a' 1/4 (518936 KB)...
OKAY [ 29.084s]
writing 'system_a' 1/4...
OKAY [ 5.336s]
sending sparse 'system_a' 2/4 (506887 KB)...
OKAY [ 28.523s]
writing 'system_a' 2/4...
OKAY [ 13.352s]
sending sparse 'system_a' 3/4 (491777 KB)...
OKAY [ 28.733s]
writing 'system_a' 3/4...
OKAY [ 6.808s]
sending sparse 'system_a' 4/4 (32756 KB)...
OKAY [ 1.732s]
writing 'system_a' 4/4...
OKAY [ 0.619s]
erasing 'system_b'...
OKAY [ 1.181s]
sending sparse 'system_b' 1/4 (517263 KB)...
OKAY [ 30.183s]
writing 'system_b' 1/4...
OKAY [ 4.555s]
sending sparse 'system_b' 2/4 (513954 KB)...
OKAY [ 25.261s]
writing 'system_b' 2/4...
OKAY [ 5.386s]
sending sparse 'system_b' 3/4 (523846 KB)...
OKAY [ 33.335s]
writing 'system_b' 3/4...
OKAY [ 4.485s]
sending sparse 'system_b' 4/4 (88422 KB)...
OKAY [ 7.907s]
writing 'system_b' 4/4...
OKAY [ 1.348s]
erasing 'vendor_a'...
OKAY [ 0.520s]
sending 'vendor_a' (234137 KB)...
OKAY [ 7.342s]
writing 'vendor_a'...
OKAY [ 6.647s]
Setting current slot to 'a'...
OKAY [ 0.400s]
erasing 'userdata'...
OKAY [ 28.688s]
sending 'userdata' (145102 KB)...
OKAY [ 4.998s]
writing 'userdata'...
OKAY [ 2.393s]
rebooting...
finished. total time: 282.030s
Marcs-MacBook-Pro:sailfish-nde63p root#

tried factory reset and flashing some of the other images... no luck, still encrypted. guess i'll need to wait for TWRP to come out and figure out how to decrypt :-/

spunks3 said:
tried factory reset and flashing some of the other images... no luck, still encrypted. guess i'll need to wait for TWRP to come out and figure out how to decrypt :-/
Click to expand...
Click to collapse
Thanks friend!:laugh:

Modifiy the kernel

omegear said:
Modifiy the kernel
Click to expand...
Click to collapse
How?

Hey spunks, I'm in the same boat with you. Cant decrypt. I don't even remember encrypting in the first place!

Oface82 said:
Hey spunks, I'm in the same boat with you. Cant decrypt. I don't even remember encrypting in the first place!
Click to expand...
Click to collapse
I think it'll just be a waiting game... This happened to me when I flashed the original boot image using an out of date SDK.

Can you point me in the direction of the factory images? I need to start over

Why are you so desperate to decrypt? It's encrypted by default, and stops you from nothing at this moment, and likely won't be a road block in the future either.
Sent from my Pixel using Tapatalk

I had a similar issue. I tried to unroot in order to install the new OTA, because it failed. So I tried to flash the factory boot image via
Code:
fastboot flash boot boot.img
fastboot flash boot_b boot.img
After the next boot I got the nice "erasing" screen...
My phone was unencrypted before (dunno why) and now all my data is gone and it is encrypted... Maybe there are some devices, which are not encrypted by default and factory resetting after updates...

fastboot error messages, are these serious? [solved]

Yesterday I flashed the NMF26U factory image on my Pixel using flash-all. I didn't remove the '-w' because I wanted a clean install. I saved the terminal output and there are several things that have me quite concerned even though my phone appears to be working fine.
Note the two places where it says "FAILED". Am I in trouble but don't know it yet?
Code:
E:\MobileDevices\Minimal ADB and Fastboot>flash-all
target reported max download size of 536870912 bytes
sending 'bootloader' (32980 KB)...
OKAY [ 1.154s]
writing 'bootloader'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 16.255s]
finished. total time: 17.410s
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.047s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (57192 KB)...
OKAY [ 1.919s]
writing 'radio'...
OKAY [ 1.092s]
finished. total time: 3.026s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
< waiting for 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'
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
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
--------------------------------------------
Bootloader Version...: 8996-012001-1611091517
Baseband Version.....: 8996-012511-1611190200
Serial Number........: FA6C10300677
--------------------------------------------
checking product...
OKAY [ 0.047s]
checking version-bootloader...
OKAY [ 0.031s]
checking version-baseband...
OKAY [ 0.047s]
sending 'boot' (24821 KB)...
OKAY [ 0.889s]
writing 'boot'...
(bootloader) Flashing active slot "_a"
OKAY [ 0.655s]
sending sparse 'system' (516459 KB)...
OKAY [ 18.018s]
writing 'system'...
OKAY [ 6.802s]
sending sparse 'system' (520631 KB)...
OKAY [ 18.470s]
writing 'system'...
OKAY [ 10.998s]
sending sparse 'system' (517487 KB)...
OKAY [ 18.096s]
writing 'system'...
OKAY [ 7.597s]
sending 'vendor' (235186 KB)...
OKAY [ 7.956s]
writing 'vendor'...
OKAY [ 6.599s]
erasing 'userdata'...
OKAY [ 6.848s]
sending 'userdata' (138957 KB)...
OKAY [ 4.696s]
writing 'userdata'...
OKAY [ 1.342s]
erasing 'cache'...
(bootloader) Erasing active slot "_a"
FAILED (remote: Partition table doesn't exist
)
finished. total time: 109.403s
Press any key to exit...

because flash all is bat file, it contains many items which maybe not included in the factory image to be fashed.
Almost, I got same information.
by the way, how can we save or input the flash all results. I am on windows

bush911 said:
by the way, how can we save or input the flash all results. I am on windows
Click to expand...
Click to collapse
Right click the menu bar in the command box and select edit then 'selec all's. Right click again, edit then copy. Paste it into a document.

I had to re-flash back to 7.1.0, then upon setting up the phone, it began taking the OTA 7.1.1 update, which is fine. Now that the phone is unlocked and updated, what is the best method to gain root access from this point? boot-to-root or install the latest SU or ?? Thanks.

Your fastboot binary is out of date. Make sure you're using the latest version.

wbxp99 said:
Your fastboot binary is out of date. Make sure you're using the latest version.
Click to expand...
Click to collapse
Thank you! It's nice to receive a definitive answer on this. I flashed again with the latest fastboot version and the log output is very different from the first time. I am confident now that everything is in its proper place.

pstgh said:
I had to re-flash back to 7.1.0, then upon setting up the phone, it began taking the OTA 7.1.1 update, which is fine. Now that the phone is unlocked and updated, what is the best method to gain root access from this point? boot-to-root or install the latest SU or ?? Thanks.
Click to expand...
Click to collapse
This a thread about fastboot error messages. There are guide in the SU and TWRP threads. Very easy I don't personally think you need anything like boot to root. Just follow the instructions and make sure you use TWRP RC1 and SU 2.79 SR 2

Unable to update to 8.1 in anyway

Hi all. it's been a while since I've posted on xda
I'm having a problem with my newly acquired Pixel,
Today, I received an OTA notification for Android 8.1, tried to have it install but the when the phone restarts to install, it just flash to google logo like 3 times and them boot back to 8.0.
I looked it up on google, people say I should factory reset before restarting and install 8.1. Tried that but same thing happens.
Then I decided to download the factory image and flash it myself. With OEM unlocking and Android debugging enabled, the 8.1 image flashed successfully. However, the phone doesn't boot, it shows a dead Android and a "No command" error. Same thing happen when I try to sideload the OTA file...
I had to flash the 8.0 factory image for the phone to boot successfully again...
Now I have no idea how to get 8.1... Do you guys have any idea of what can be done or what's happening?
Thanks in advance!

Did you update your fastboot tools? That is needed for 8.1

TonikJDK said:
Did you update your fastboot tools? That is needed for 8.1
Click to expand...
Click to collapse
I used the latest version of minimal adb and fastboot:
https://forum.xda-developers.com/showthread.php?t=2317790
It flashed successfully without any error, so I assume my fastboot is fine...

If 8/28/15 is the latest minimalist platform tools, it's too old. I don't have the link handy but Google provides a direct link to the latest at all times now, so you don't have to install the developer tools or download someone else's repackaged to get the latest.
They updated it yet again the day they released 8.1.
Edit: here it is
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
The link stays the same and is always the latest version. Just extract it to where the firmware is extracted to.

Thanks, I'll try and report back

roirraW "edor" ehT said:
If 8/28/15 is the latest minimalist platform tools, it's too old. I don't have the link handy but Google provides a direct link to the latest at all times now, so you don't have to install the developer tools or download someone else's repackaged to get the latest.
They updated it yet again the day they released 8.1.
Edit: here it is
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
The link stays the same and is always the latest version. Just extract it to where the firmware is extracted to.
Click to expand...
Click to collapse
Just tried the latest platform tools, and the same issue persists... any idea?
Edit: Tried sideloading 8.1 OTA from 8.0, however, it boots back to 8.0 eventually.

cnkhanh said:
Just tried the latest platform tools, and the same issue persists... any idea?
Edit: Tried sideloading 8.1 OTA from 8.0, however, it boots back to 8.0 eventually.
Click to expand...
Click to collapse
how about not doing an ota update but using the full firmware image instead?
you would have two options;
1. edit the flash-all script, removing the -w flag, so it doesn't wipe your data partition
2. or do a full system wipe backup anything important first...

nine7nine said:
how about not doing an ota update but using the full firmware image instead?
you would have two options;
1. edit the flash-all script, removing the -w flag, so it doesn't wipe your data partition
2. or do a full system wipe backup anything important first...
Click to expand...
Click to collapse
I already tried flashing the 8.1 factory image, wiping data, still have the same issue though...

cnkhanh said:
I already tried flashing the 8.1 factory image, wiping data, still have the same issue though...
Click to expand...
Click to collapse
I don't see how that would be possible, if u had run the flash-all script it would've replaced the bootloader, all of your devices partitions with the new firmware...
there would be no 8.0 to boot back into, at all.
please write your steps down and some of thevrelevant output you see on your phone, when the script runs...

nine7nine said:
I don't see how that would be possible, if u had run the flash-all script it would've replaced the bootloader, all of your devices partitions with the new firmware...
there would be no 8.0 to boot back into, at all.
please write your steps down and some of thevrelevant output you see on your phone, when the script runs...
Click to expand...
Click to collapse
Sorry, I meant the issue was that in my original post, the phone doesn't boot and stuck on the "No command" screen...
When the flash all script runs, my phones was on fastboot mode, rebooting to bootloader several times during the process (this is expected i guess). When the script finishes successfully, the phone tries to boot into the OS, but it shows a google logo and turns off, several times (like a bootloop), then eventually shows the "No command" screen.

Currently, I'm on 8.0, build number OPR3.170623.013

cnkhanh said:
Currently, I'm on 8.0, build number OPR3.170623.013
Click to expand...
Click to collapse
Are u using the right firmware package for your model?
Sent from my Google Pixel using XDA Labs

Sgace said:
Are u using the right firmware package for your model?
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Just to clarify, there's only one 8.1 firmware package for the Pixel Sailfish, but I think @Sgace is pointing out that you could've downloaded the full firmware for the Marlin (XL) or any of the other Pixels.
Last ditch effort is a different PC and/or cable.
I'm out of ideas otherwise. Is it under warranty?

roirraW "edor" ehT said:
Just to clarify, there's only one 8.1 firmware package for the Pixel Sailfish, but I think @Sgace is pointing out that you could've downloaded the full firmware for the Marlin (XL) or any of the other Pixels.
Click to expand...
Click to collapse
Sgace said:
Are u using the right firmware package for your model?
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Thanks for pointing out, but the version I was trying to flash was correct, sailfish 8.1.0 (OPM1.171019.011, Dec 2017)
I'll try another PC and cable later, I'm running on Windows 10 Fall Creator Update.
I don't think warranty is a viable option for me

Here is the cmd lines when installing 8.1, seems fine with me.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32248 KB)...
OKAY [ 0.888s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.059s]
finished. total time: 2.951s
rebooting into bootloader...
OKAY [ 0.051s]
finished. total time: 0.052s
target reported max download size of 536870912 bytes
sending 'radio_a' (57320 KB)...
OKAY [ 1.499s]
writing 'radio_a'...
OKAY [ 0.486s]
finished. total time: 1.989s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.051s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (28 MB) to disk... took 0.410s
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 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1751 MB) to disk... took 18.393s
archive does not contain 'system.sig'
extracting system_other.img (551 MB) to disk... took 6.660s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (250 MB) to disk... took 2.662s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 6509568 4k blocks and 1630208 inodes
Filesystem UUID: 657305e6-e288-11e7-8b52-538b74cf9ac7
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: 8996-012001-1710040120
Baseband Version.....: 8996-130091-1710201747
Serial Number........: FA6960306426
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.048s]
checking version-baseband...
OKAY [ 0.049s]
sending 'boot_a' (28945 KB)...
OKAY [ 0.750s]
writing 'boot_a'...
OKAY [ 0.296s]
erasing 'system_a'...
OKAY [ 0.320s]
sending sparse 'system_a' 1/4 (524284 KB)...
OKAY [ 13.651s]
writing 'system_a' 1/4...
OKAY [ 3.451s]
sending sparse 'system_a' 2/4 (524284 KB)...
OKAY [ 13.604s]
writing 'system_a' 2/4...
OKAY [ 3.488s]
sending sparse 'system_a' 3/4 (524284 KB)...
OKAY [ 14.015s]
writing 'system_a' 3/4...
OKAY [ 3.446s]
sending sparse 'system_a' 4/4 (220660 KB)...
OKAY [ 5.700s]
writing 'system_a' 4/4...
OKAY [ 1.494s]
erasing 'system_b'...
OKAY [ 0.261s]
sending sparse 'system_b' 1/2 (524284 KB)...
OKAY [ 13.702s]
writing 'system_b' 1/2...
OKAY [ 3.451s]
sending sparse 'system_b' 2/2 (40660 KB)...
OKAY [ 1.083s]
writing 'system_b' 2/2...
OKAY [ 0.355s]
erasing 'vendor_a'...
OKAY [ 0.142s]
sending 'vendor_a' (257004 KB)...
OKAY [ 6.358s]
writing 'vendor_a'...
OKAY [ 1.758s]
Setting current slot to 'a'...
OKAY [ 0.088s]
erasing 'userdata'...
OKAY [ 1.705s]
sending 'userdata' (4412 KB)...
OKAY [ 0.196s]
writing 'userdata'...
OKAY [ 0.100s]
rebooting...
finished. total time: 89.845s
Press any key to exit...

roirraW "edor" ehT said:
Just to clarify, there's only one 8.1 firmware package for the Pixel Sailfish, but I think @Sgace is pointing out that you could've downloaded the full firmware for the Marlin (XL) or any of the other Pixels.
Last ditch effort is a different PC and/or cable.
I'm out of ideas otherwise. Is it under warranty?
Click to expand...
Click to collapse
Oops, yes that's what I meant.
Thnx for pointing that one out. I had to be more clear.
Cheers
Sent from my Google Pixel using XDA Labs
---------- Post added at 07:51 PM ---------- Previous post was at 07:47 PM ----------
cnkhanh said:
Here is the cmd lines when installing 8.1, seems fine with me.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32248 KB)...
OKAY [ 0.888s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.059s]
finished. total time: 2.951s
rebooting into bootloader...
OKAY [ 0.051s]
finished. total time: 0.052s
target reported max download size of 536870912 bytes
sending 'radio_a' (57320 KB)...
OKAY [ 1.499s]
writing 'radio_a'...
OKAY [ 0.486s]
finished. total time: 1.989s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.051s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (28 MB) to disk... took 0.410s
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 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1751 MB) to disk... took 18.393s
archive does not contain 'system.sig'
extracting system_other.img (551 MB) to disk... took 6.660s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (250 MB) to disk... took 2.662s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 6509568 4k blocks and 1630208 inodes
Filesystem UUID: 657305e6-e288-11e7-8b52-538b74cf9ac7
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: 8996-012001-1710040120
Baseband Version.....: 8996-130091-1710201747
Serial Number........: FA6960306426
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.048s]
checking version-baseband...
OKAY [ 0.049s]
sending 'boot_a' (28945 KB)...
OKAY [ 0.750s]
writing 'boot_a'...
OKAY [ 0.296s]
erasing 'system_a'...
OKAY [ 0.320s]
sending sparse 'system_a' 1/4 (524284 KB)...
OKAY [ 13.651s]
writing 'system_a' 1/4...
OKAY [ 3.451s]
sending sparse 'system_a' 2/4 (524284 KB)...
OKAY [ 13.604s]
writing 'system_a' 2/4...
OKAY [ 3.488s]
sending sparse 'system_a' 3/4 (524284 KB)...
OKAY [ 14.015s]
writing 'system_a' 3/4...
OKAY [ 3.446s]
sending sparse 'system_a' 4/4 (220660 KB)...
OKAY [ 5.700s]
writing 'system_a' 4/4...
OKAY [ 1.494s]
erasing 'system_b'...
OKAY [ 0.261s]
sending sparse 'system_b' 1/2 (524284 KB)...
OKAY [ 13.702s]
writing 'system_b' 1/2...
OKAY [ 3.451s]
sending sparse 'system_b' 2/2 (40660 KB)...
OKAY [ 1.083s]
writing 'system_b' 2/2...
OKAY [ 0.355s]
erasing 'vendor_a'...
OKAY [ 0.142s]
sending 'vendor_a' (257004 KB)...
OKAY [ 6.358s]
writing 'vendor_a'...
OKAY [ 1.758s]
Setting current slot to 'a'...
OKAY [ 0.088s]
erasing 'userdata'...
OKAY [ 1.705s]
sending 'userdata' (4412 KB)...
OKAY [ 0.196s]
writing 'userdata'...
OKAY [ 0.100s]
rebooting...
finished. total time: 89.845s
Press any key to exit...
Click to expand...
Click to collapse
Looks ok to me too. Are u able to manually boot to stock recovery after the flash and from there do a factory reset?
Cheers
Sent from my Google Pixel using XDA Labs

cnkhanh said:
sending 'boot_a' (28945 KB)...
OKAY [ 0.750s]
writing 'boot_a'...
OKAY [ 0.296s]
Click to expand...
Click to collapse
I would have to re-flash the firmware to check (which I'm not doing), but shouldn't the boot.img be flashed to both the slot_a and slot_b partitions?
your issue of it ending boot with the recovery "no command" makes me think that something isn't right with the flashed boot images....
one thing you could try is unzipping the fimeware update zip and manually using fast boot to flash the boot images, after flashing the firmware....
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
you could also try using twrp to manually flash the boot.img and system image (you would need to copy them to your device though).... I've bumped into the error you speak of; but not when doing a full flash of system firmware.... that _shouldn't_ happen.....

Sgace said:
Oops, yes that's what I meant.
Thnx for pointing that one out. I had to be more clear.
Cheers
Click to expand...
Click to collapse
You're welcome, hey, you can up with the good suggestion!
Another idea is at least on 8.0 with SuperSU, I was able to flash the entire 8.1 firmware with @Chainfire 's FlashFire app, every partition.

Sgace said:
Oops, yes that's what I meant.
Thnx for pointing that one out. I had to be more clear.
Cheers
Sent from my Google Pixel using XDA Labs
---------- Post added at 07:51 PM ---------- Previous post was at 07:47 PM ----------
Looks ok to me too. Are u able to manually boot to stock recovery after the flash and from there do a factory reset?
Cheers
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Yes, I still can boot in to stock recovery, I tried factory reset many times though...
nine7nine said:
I would have to re-flash the firmware to check (which I'm not doing), but shouldn't the boot.img be flashed to both the slot_a and slot_b partitions?
your issue of it ending boot with the recovery "no command" makes me think that something isn't right with the flashed boot images....
one thing you could try is unzipping the fimeware update zip and manually using fast boot to flash the boot images, after flashing the firmware....
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
you could also try using twrp to manually flash the boot.img and system image (you would need to copy them to your device though).... I've bumped into the error you speak of; but not when doing a full flash of system firmware.... that _shouldn't_ happen.....
Click to expand...
Click to collapse
Hmm, I think it only flashes the active slot. Mine is "a", shown in bootloader mode.
Btw, my device shows the OTA update is about 566 MB while the OTA zip for sideloading is 900+MB, is that normal?
Edit: Just tried flashing both boot slot "a" and "b", changing active boot slot to "b" still have the same issues

cnkhanh said:
Yes, I still can boot in to stock recovery, I tried factory reset many times though...
Hmm, I think it only flashes the active slot. Mine is "a", shown in bootloader mode.
Btw, my device shows the OTA update is about 566 MB while the OTA zip for sideloading is 900+MB, is that normal?
Edit: Just tried flashing both boot slot "a" and "b", changing active boot slot to "b" still have the same issues
Click to expand...
Click to collapse
My theory is that it is updating the secondary system partition but failing to switch partitions. I could be wrong.

Bricked OnePlus 6

Hello,
several weeks ago I bricked my oneplus 6 during the approach to install lineage 16.0. I also tried to fix it, based on some articles I found, but without success.
Error - most likely I have coincidently wiped the partitions a/b...
A) So, some weeks later I want to bring it back to life. Current status following the lineage instructions:
1) unlocking bootloader
is unlocked
2) temporarily booting a customer recovery using fastboot
- sudo ./fastboot devices
977d3806 fastboot
- sudo ./fastboot flash boot ~/Downloads/oneplus6/twrp/twrp-3.2.3-1-enchilada.img
target reported max download size of 536870912 bytes
sending 'boot_a' (28728 KB)...
OKAY [ 1.076s]
writing 'boot_a'...
OKAY [ 0.115s]
finished. total time: 1.192s
Result: power off, automatic reboot, nothing happens - only dark screen and white light close to front camera
Result: power off, volume down + power, same result
B) Alternative
- sudo ./fastboot boot ~/Downloads/oneplus6/twrp/twrp-3.2.3-1-enchilada.img
downloading 'boot.img'...
OKAY [ 1.037s]
booting...
OKAY [ 0.077s]
finished. total time: 1.114s
Result: automatic power off, automatic reboot, nothing happens - only dark screen and white light close to front camera
C) I also tried [ROM][STOCK][FASTBOOT][OP6] Stock Fastboot ROMs for OnePlus 6 – also without success. Basically everything seemed to be ok but after the end I had to manually reboot it: nothing happens - only dark screen and white light close to front camera.
Flashing looked good:
target reported max download size of 536870912 bytes
sending 'aop_a' (180 KB)...
OKAY [ 0.015s]
writing 'aop_a'...
OKAY [ 0.004s]
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'aop_b' (180 KB)...
OKAY [ 0.014s]
writing 'aop_b'...
OKAY [ 0.007s]
finished. total time: 0.021s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (748 KB)...
OKAY [ 0.030s]
writing 'bluetooth_a'...
OKAY [ 0.007s]
finished. total time: 0.037s
target reported max download size of 536870912 bytes
sending 'bluetooth_b' (748 KB)...
OKAY [ 0.029s]
writing 'bluetooth_b'...
OKAY [ 0.010s]
finished. total time: 0.039s
target reported max download size of 536870912 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 2.259s]
writing 'boot_a'...
OKAY [ 0.252s]
finished. total time: 2.511s
target reported max download size of 536870912 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 2.075s]
writing 'boot_b'...
OKAY [ 0.272s]
finished. total time: 2.347s
target reported max download size of 536870912 bytes
sending 'dsp_a' (32768 KB)...
OKAY [ 1.088s]
writing 'dsp_a'...
OKAY [ 0.143s]
finished. total time: 1.231s
target reported max download size of 536870912 bytes
sending 'dsp_b' (32768 KB)...
OKAY [ 1.178s]
writing 'dsp_b'...
OKAY [ 0.127s]
finished. total time: 1.305s
target reported max download size of 536870912 bytes
sending 'dtbo_a' (8192 KB)...
OKAY [ 0.279s]
writing 'dtbo_a'...
OKAY [ 0.045s]
finished. total time: 0.324s
target reported max download size of 536870912 bytes
sending 'dtbo_b' (8192 KB)...
OKAY [ 0.277s]
writing 'dtbo_b'...
OKAY [ 0.031s]
finished. total time: 0.308s
target reported max download size of 536870912 bytes
sending 'fw_4j1ed_a' (344 KB)...
OKAY [ 0.017s]
writing 'fw_4j1ed_a'...
OKAY [ 0.005s]
finished. total time: 0.022s
target reported max download size of 536870912 bytes
sending 'fw_4j1ed_b' (344 KB)...
OKAY [ 0.018s]
writing 'fw_4j1ed_b'...
OKAY [ 0.006s]
finished. total time: 0.024s
target reported max download size of 536870912 bytes
sending 'fw_4u1ea_a' (344 KB)...
OKAY [ 0.015s]
writing 'fw_4u1ea_a'...
OKAY [ 0.005s]
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'fw_4u1ea_b' (344 KB)...
OKAY [ 0.018s]
writing 'fw_4u1ea_b'...
OKAY [ 0.007s]
finished. total time: 0.025s
target reported max download size of 536870912 bytes
sending 'modem_a' (120916 KB)...
OKAY [ 4.347s]
writing 'modem_a'...
OKAY [ 0.598s]
finished. total time: 4.945s
target reported max download size of 536870912 bytes
sending 'modem_b' (120916 KB)...
OKAY [ 4.249s]
writing 'modem_b'...
OKAY [ 0.640s]
finished. total time: 4.889s
target reported max download size of 536870912 bytes
sending 'oem_stanvbk' (952 KB)...
OKAY [ 0.037s]
writing 'oem_stanvbk'...
OKAY [ 0.009s]
finished. total time: 0.046s
target reported max download size of 536870912 bytes
sending 'qupfw_a' (64 KB)...
OKAY [ 0.011s]
writing 'qupfw_a'...
OKAY [ 0.005s]
finished. total time: 0.016s
target reported max download size of 536870912 bytes
sending 'qupfw_b' (64 KB)...
OKAY [ 0.006s]
writing 'qupfw_b'...
OKAY [ 0.004s]
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'storsec_a' (24 KB)...
OKAY [ 0.003s]
writing 'storsec_a'...
OKAY [ 0.004s]
finished. total time: 0.007s
target reported max download size of 536870912 bytes
sending 'storsec_b' (24 KB)...
OKAY [ 0.010s]
writing 'storsec_b'...
OKAY [ 0.005s]
finished. total time: 0.015s
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
erasing 'system_a'...
OKAY [ 0.137s]
sending sparse 'system_a' 1/6 (460753 KB)...
OKAY [ 15.731s]
writing 'system_a' 1/6...
OKAY [ 0.003s]
sending sparse 'system_a' 2/6 (524285 KB)...
OKAY [ 21.336s]
writing 'system_a' 2/6...
OKAY [ 0.007s]
sending sparse 'system_a' 3/6 (508111 KB)...
OKAY [ 18.622s]
writing 'system_a' 3/6...
OKAY [ 0.007s]
sending sparse 'system_a' 4/6 (482530 KB)...
OKAY [ 18.322s]
writing 'system_a' 4/6...
OKAY [ 0.005s]
sending sparse 'system_a' 5/6 (481413 KB)...
OKAY [ 17.874s]
writing 'system_a' 5/6...
OKAY [ 0.006s]
sending sparse 'system_a' 6/6 (218712 KB)...
OKAY [ 9.743s]
writing 'system_a' 6/6...
OKAY [ 0.006s]
finished. total time: 101.799s
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'system_b' 1/6 (460753 KB)...
OKAY [ 16.083s]
writing 'system_b' 1/6...
OKAY [ 0.006s]
sending sparse 'system_b' 2/6 (524285 KB)...
OKAY [ 20.273s]
writing 'system_b' 2/6...
OKAY [ 0.006s]
sending sparse 'system_b' 3/6 (508111 KB)...
OKAY [ 18.702s]
writing 'system_b' 3/6...
OKAY [ 0.007s]
sending sparse 'system_b' 4/6 (482530 KB)...
OKAY [ 18.282s]
writing 'system_b' 4/6...
OKAY [ 0.017s]
sending sparse 'system_b' 5/6 (481413 KB)...
OKAY [ 17.782s]
writing 'system_b' 5/6...
OKAY [ 0.006s]
sending sparse 'system_b' 6/6 (218712 KB)...
OKAY [ 9.483s]
writing 'system_b' 6/6...
OKAY [ 0.007s]
finished. total time: 100.653s
target reported max download size of 536870912 bytes
sending 'vbmeta_a' (4 KB)...
OKAY [ 0.006s]
writing 'vbmeta_a'...
OKAY [ 0.005s]
finished. total time: 0.011s
target reported max download size of 536870912 bytes
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.011s]
writing 'vbmeta_b'...
OKAY [ 0.005s]
finished. total time: 0.016s
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'vendor_a' 1/2 (521885 KB)...
OKAY [ 17.719s]
writing 'vendor_a' 1/2...
OKAY [ 0.005s]
sending sparse 'vendor_a' 2/2 (265685 KB)...
OKAY [ 12.415s]
writing 'vendor_a' 2/2...
OKAY [ 0.006s]
finished. total time: 30.145s
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'vendor_b' 1/2 (521885 KB)...
OKAY [ 17.638s]
writing 'vendor_b' 1/2...
OKAY [ 0.006s]
sending sparse 'vendor_b' 2/2 (265685 KB)...
OKAY [ 12.434s]
writing 'vendor_b' 2/2...
OKAY [ 0.005s]
finished. total time: 30.083s
target reported max download size of 536870912 bytes
sending 'LOGO_a' (3160 KB)...
OKAY [ 0.100s]
writing 'LOGO_a'...
OKAY [ 0.028s]
finished. total time: 0.128s
target reported max download size of 536870912 bytes
sending 'LOGO_b' (3160 KB)...
OKAY [ 0.106s]
writing 'LOGO_b'...
OKAY [ 0.027s]
finished. total time: 0.133s
Any idea what I can do with my bricked OnePlus6?
Thanks Martin

Follow this thread https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892 to recover your device and looks like the same as what it looks like when you first bought it.

I have had the same issue while trying to install LineageOS 17 and AOSiP, haven't tried any other rom. I booted to twrp, flashed rom and flashed twrp zip and I tried to reboot into twrp, it didn't boot instead gave black screen and white LED. I repeated the process after restoring using msmtool multiple times yet no solution.

I had a similar problem, I fixed it by flashing the "criticals" partitions from this thread. You need TWRP access to do it. The OP says they used that thread but it doesn't look like they flashed "criticals". I'm not sure if whatever msmdownloadtool flashes includes these critical partitions or not.
Also, one of my slots was working OK, the other one wasn't. Some low-level partitions had got corrupted on the other one and it was this one I was (initially) booting into, leading to the white LED, black screen. I was able to fix things temporarily by changing the active slot like this:
Code:
fastboot getvar current-slot
then you can change it to the other slot with
Code:
fastboot --set-active={"a" or "b" whichever isn't active}
fastboot reboot {recovery|bootloader}
That may get you TWRP or even full Android access. However you should be able to boot TWRP from fastboot anyway.

tiga016 said:
Follow this thread https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892 to recover your device and looks like the same as what it looks like when you first bought it.
Click to expand...
Click to collapse
Thank you, I will try this - after getting a Win pc.
PS Twrp is not working...

+1 for MSM Download Tool

martinforum said:
Thank you, I will try this - after getting a Win pc.
PS Twrp is not working...
Click to expand...
Click to collapse
Use blu_spark twrp 9.101

martinforum said:
Thank you, I will try this - after getting a Win pc.
PS Twrp is not working...
Click to expand...
Click to collapse
With a Win-PC it was working and the factory rom is working again. Now twrp (org and blue) are not working...
Again unbrick was successful!

I bought a used OP6 that bricked when I applied the latest OTA, so I had to figure out what was wrong and get it working again. This is my first A/B phone. I worked out the steps below to unbrick the phone and get it on the latest OxygenOS, so I thought I could share this process with others in the same dire situation I was in.
Current as of 2019-11-12
Based on https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Download:
MsmDownloadTool V4.0 International (with Oxygen OS 5.1.5) https://mega.nz/#F!CfBG0IgZ!Gmnu6B-a7yFyvMLNw_pz8w
Qualcomm driver: https://androidfilehost.com/?fid=24052804347798730
Latest full OS from OnePlus (Oxygen 9.09 currently): https://www.oneplus.com/support/softwareupgrade/details?code=8
Notes:
The MSM tool is for writing the base configuration, below recovery and fastboot.
These instructions worked on Win 7 x64 and Win 10 x64.
ADB and fastboot must be installed on PC.
OTA must bring phone to the same version as the downloaded OOS (for example, OTA must update to 9.09, and download must be OOS 9.09).
This process will return the phone to stock OOS (with stock recovery).
Unzip the Qualcomm driver and MSM Tool packages into their own folders on the PC
Install Qualcomm driver (only needed the 1st time on the PC):
Boot the phone into Bootloader
Go to Device Manager on PC and uninstall the Qualcomm entry under COM Ports
Unplug phone and power it down
Enter test mode on PC (to keep Win from installing default drivers): cmd prompt, enter "bcdedit /set testsigning on", reboot PC
Boot phone: press power and then Vol Up for at least 5 seconds (to enter basic config mode), plug into PC
Device Manager, look for "US8_BULK", Update Driver with extracted Qualcomm folder, new entry in Device Manager should be a Qualcomm COM port (YT video: https://www.youtube.com/watch?v=PpLvmID1wdI)Run MSM Tool as Administrator, click Start, let process run until Complete, reboot phone
Run OTA updates on phone
Reboot to System
Reboot to Bootloader
Check active slot:
Command: "fastboot getvar all", look for "(bootloader) current-slot:x" entry and note a or bReboot to System
Update other slot:
Copy downloaded OnePlus OS zip file to phone Internal Memory
Go to Settings > System > System Updates
Tap "gear" (settings) icon in upper-right corner, select "Local upgrade"
Select copied file, and "Install Now"Reboot to System
Reboot to Fastboot and verify that slot is different than previous check
Choose desired slot (optional):
Command: "fastboot set_active other"Reboot to System
Exit test mode on PC: Cmd prompt, enter "bcdedit /set testsigning off", reboot PC
Troubleshooting:
For "Sahara" error in MSM Tool, unplug, power on, power off, hold Vol Up for 5 seconds, plug in again

Database Info

welcome