Develop Bugs

Cannot flash Google Factory Images (MOB30D, MMB29V, MMB29Q, MMB29O)

Tried flashing this just now:
https://developers.google.com/android/nexus/images#razor
6.0.1 (MOB30D)
via https://dl.google.com/dl/android/aosp/razor-mob30d-factory-15169856.tgz
Terminal result:
Code:
MBP:android-platform-tools $ ./flash-all.sh
sending 'bootloader' (3911 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
OKAY [ 1.764s]
finished. total time: 1.893s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
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.05
Baseband Version.....: none
Serial Number........: 091aafd9
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7440 KB)...
OKAY [ 0.242s]
writing 'boot'...
OKAY [ 0.707s]
sending 'recovery' (8184 KB)...
OKAY [ 0.268s]
writing 'recovery'...
OKAY [ 0.338s]
erasing 'system'...
OKAY [ 0.175s]
sending 'system' (843529 KB)...
OKAY [ 26.422s]
writing 'system'...
FAILED (remote: Unknown chunk type)
finished. total time: 63.936s
I also verified MD5:
MBP:android-platform-tools $ md5 /Volumes/Data/Downloads/Android/razor-mob30d-factory-15169856.tgz
MD5 (/Volumes/Data/Downloads/Android/razor-mob30d-factory-15169856.tgz) = 701bc5f47b4919294968995a52ab5c76
Click to expand...
Click to collapse
I had previously tried this with a few others such as MOB30D, MMB29V, MMB29Q, MMB29O with same results. Thoughts?

You are using an obsolete version of 'fastboot'. Get another one or try fastboot on Windows.

k23m said:
You are using an obsolete version of 'fastboot'. Get another one or try fastboot on Windows.
Click to expand...
Click to collapse
How can I check fastboot version? I just went through and downloaded what I thought was the latest version. Afterwords, I tried flashall again. I did 2 seconds further down into the install:
Code:
sending 'bootloader' (3911 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
OKAY [ 1.522s]
finished. total time: 1.652s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
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.05
Baseband Version.....: none
Serial Number........: 091bbfd9
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7440 KB)...
OKAY [ 0.244s]
writing 'boot'...
OKAY [ 0.468s]
sending 'recovery' (8184 KB)...
OKAY [ 0.268s]
writing 'recovery'...
OKAY [ 0.338s]
erasing 'system'...
OKAY [ 0.175s]
sending 'system' (843529 KB)...
OKAY [ 26.570s]
writing 'system'...
FAILED (remote: Unknown chunk type)
finished. total time: 65.996s

Need Help Unbricking my Pixel XL

need help unbricking my pixel xl.
i downloaded the factory image from google and ran the flashall.bat but it keeps failing.
target reported max download size of 536870912 bytes
sending 'bootloadera' (32820 KB)...
OKAY [ 0.770s]
writing 'bootloadera'...
(bootloader) Valid bootloader version.
OKAY [ 1.038s]
finished. total time: 1.812s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.009s
target reported max download size of 536870912 bytes
sending 'radioa' (57048 KB)...
OKAY [ 1.302s]
writing 'radioa'...
OKAY [ 0.897s]
finished. total time: 2.201s
rebooting into bootloader...
OKAY [ 0.014s]
finished. total time: 0.016s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 122633060352
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 29939712
Block groups: 914
Reserved block group size: 1024
Created filesystem with 11/7487488 inodes and 518062/29939712 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609191801
Serial Number........: HT69D0200852
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.049s]
checking version-baseband...
OKAY [ 0.048s]
sending 'boota' (26481 KB)...
OKAY [ 0.641s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.097s
Press any key to exit...

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

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

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

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

[HELP] Pixel C don´t boot and can´t acces any partition after restore a backup

Hello,
I made a backup of my RR ROM by followmsi in my usb stick, after give a short try to AOSP OREO I decide go back to my old rom. So I reboot into TWRP (latest version) in order to restore my backup that it´s on my usb stick. After the restore I reboot to system but I never go into system, it get stuck on RR logo, so I go back to TWRP and now it asks for a password to decrypt data and I NEVER USE A PASSWORD/PATRON
I try to format every partition but TWRP is always unable to mount those partitions. Now I try to make a new install of the rom with no results.
So now my Pixel C is like a rock and I can´t get it boot. Anyone can help me bringing it back to life? Doesn´t matter if I must restore it to fully stock, this is the very last time that I try roms or similar in Pixel, I´m done and probably I sell it, I´m just tired and it´s insanely messy for me.
I never never have this kind of problems that I´m facing with Pixel C with any of my android phones/tablets, this is my fault probably at 100% just I can´t understand anything.....
Thanks in advance.

I try to flash latest Oreo factory image and latest Nougat factory image with no good results. Here is the log:
target reported max download size of 268435456 bytes
sending 'bootloader' (16384 KB)...
OKAY [ 0.420s]
writing 'bootloader'...
FAILED (remote: unsupported command)
finished. total time: 0.424s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
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'
Creating filesystem with parameters:
Size: 26557284352
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6483712
Block groups: 198
Reserved block group size: 1024
Created filesystem with 11/1622016 inodes and 145840/6483712 blocks
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.7132.295.0
Baseband Version.....: N/A
Serial Number........: unknown variable
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'Google_Smaug.7132.295.0'.
Update requires 'Google_Smaug.7900.67.0'.
finished. total time: 0.018s
Press any key to exit...
I also try to flash manually the bootloader with no results. In adition I try to lock and unlock the device to get it wiped also with no results.
Any ideas?? I´m totally desperated.
Thanks in advance.

I think you need to find the original firmware with the bootloader version the same as you have now(Device version-bootloader is 'Google_Smaug.7132.295.0'.) and install it. After that, I think it will be possible to update on OTA for a newer one.
Istvan_86 said:
I try to flash latest Oreo factory image and latest Nougat factory image with no good results. Here is the log:
target reported max download size of 268435456 bytes
sending 'bootloader' (16384 KB)...
OKAY [ 0.420s]
writing 'bootloader'...
FAILED (remote: unsupported command)
finished. total time: 0.424s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
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'
Creating filesystem with parameters:
Size: 26557284352
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6483712
Block groups: 198
Reserved block group size: 1024
Created filesystem with 11/1622016 inodes and 145840/6483712 blocks
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.7132.295.0
Baseband Version.....: N/A
Serial Number........: unknown variable
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'Google_Smaug.7132.295.0'.
Update requires 'Google_Smaug.7900.67.0'.
finished. total time: 0.018s
Press any key to exit...
I also try to flash manually the bootloader with no results. In adition I try to lock and unlock the device to get it wiped also with no results.
Any ideas?? I´m totally desperated.
Thanks in advance.
Click to expand...
Click to collapse

Another bricked Nexus 7

I've picked up a Nexus 7 cheap because it was stuck on the Google logo, apparently it wanted to do an update and it seems it wasn't successful and is now stuck at the Google screen
I got it to try and attempt to repair it but don't seem to be having much luck with it.
When I try flashing factory images using the flash-all.bat file I get
Code:
c:\adb>flash-all.bat
sending 'bootloader' (3915 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: -0.000s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.020s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 28521246720
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6963195
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1741488 inodes and 153337/6963195 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.04
Baseband Version.....: none
Serial Number........: 07be4417
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
FAILED
Device version-bootloader is 'FLO-04.04'.
Update requires 'FLO-04.08'.
finished. total time: 0.039s
Press any key to exit...
#
Trying to unlock the bootloader I get
Code:
PS C:\adb> fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
And it just sits there for ages and doesn't do anything.
I'm a bit stumped as to what more I can do?

Did you check the SHA-256 checksum?

No, not directly but I know when wugfresh downloads an image it does a hash check so I'm pretty sure the files are fine.
It is by the looks of it having troubles handling the erase commands so I'm guessing it's a problem with the emmc.
I've tried 2 different computers with different usb ports also.

Try sideload ota from recovery if this is working

I'd love to but I can't boot to recovery, just sits there doing nothing.

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

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

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

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