I've ran this multiple times on multiple stock images (8.0, 8.1, 9.0), (Bootloader is unlocked on fastboot mode but in developer area it shows greyd out )
But after flashing, I reboot and see my old rom booting up. Can anyone tell me why is it not flashing?
My output
sudo ./flash-all.sh
Sending 'bootloader_a' (32248 KB) OKAY [ 1.111s]
Writing 'bootloader_a' (bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.041s]
Finished. Total time: 3.274s
rebooting into bootloader OKAY [ 0.007s]
Finished. Total time: 0.058s
< waiting for any device >
Sending 'radio_a' (57272 KB) OKAY [ 2.063s]
Writing 'radio_a' OKAY [ 0.489s]
Finished. Total time: 2.683s
rebooting into bootloader OKAY [ 0.008s]
Finished. Total time: 0.058s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: 8996-012001-1709121620
Baseband Version.....: 8996-013053-1706271859
Serial Number........: HT6A10203511
--------------------------------------------
Checking product OKAY [ 0.050s]
Checking version-bootloader OKAY [ 0.050s]
Checking version-baseband OKAY [ 0.050s]
extracting boot.img (29 MB) to disk... took 0.156s
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 'odm.img'
archive does not contain 'product.img'
archive does not contain 'recovery.img'
extracting system.img (1808 MB) to disk... took 37.338s
archive does not contain 'system.sig'
extracting system_other.img (780 MB) to disk... took 16.314s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (251 MB) to disk... took 1.702s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
/home/danish/Downloads/marlin-opr3.170623.013/mke2fs failed with status 1
fastboot: error: Cannot generate image for userdata
~/Downloads/marlin-opr3.170623.013 took 1m 20s
➜ sudo ./fastboot --set-active=other
Setting current slot to 'b' OKAY [ 0.101s]
Finished. Total time: 0.184s
~/Downloads/marlin-opr3.170623.013
➜ sudo ./flash-all.sh
Sending 'bootloader_b' (32248 KB) OKAY [ 1.352s]
Writing 'bootloader_b' (bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 1.760s]
Finished. Total time: 3.221s
rebooting into bootloader OKAY [ 0.036s]
Finished. Total time: 0.086s
Sending 'radio_b' (57272 KB) OKAY [ 2.303s]
Writing 'radio_b' OKAY [ 0.499s]
Finished. Total time: 2.940s
rebooting into bootloader OKAY [ 0.010s]
Finished. Total time: 0.060s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: 8996-012001-1709121620
Baseband Version.....: 8996-013053-1706271859
Serial Number........: HT6A10203511
--------------------------------------------
Checking product OKAY [ 0.050s]
Checking version-bootloader OKAY [ 0.050s]
Checking version-baseband OKAY [ 0.050s]
extracting boot.img (29 MB) to disk... took 0.215s
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 'odm.img'
archive does not contain 'product.img'
archive does not contain 'recovery.img'
extracting system.img (1808 MB) to disk... took 29.163s
archive does not contain 'system.sig'
extracting system_other.img (780 MB) to disk... took 23.849s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (251 MB) to disk... took 2.097s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
/home/danish/Downloads/marlin-opr3.170623.013/mke2fs failed with status 1
fastboot: error: Cannot generate image for userdata
Manually use terminal to enter the commands. From the looks of it, everything but the system img updated. Open the bat file to use as a reference for the commands. It should be 'fastboot flash -w update (system zip)'. Easiest way would be to drag and drop the system zip into terminal after the 'update' part of the command. If you wish to not have the update erase your sd memory, leave out the '-w'. Have fun.
Opps! Deleted.
Related
I rooted my phone near the launch of the Pixel 2 so I could get wifi tether to work with my gUDP Verizon plan (device is from Google). I am still on 8.0 and having issues updating to 8.1. I'm having a lot of issues with crashing apps etc so I'm hoping updating will help.
I've tried a few methods unsuccessfully. I tried to do the uninstall with Magisk but it stated that the boot files weren't there. I deleted Magisk per another set of instructions and attempted to sideload and failing there as well.
I can get the phone connected with ADB. The bootloader is unlocked still. After that, I'm at a loss at what to do next. Any assistance would be appreciated its been a few years since I've messed around this stuff and obviously, things have changed and/or I've gotten dumber.
Download the full factory image, the latest.
Unzip it into your platform tools folder.
Find the flash-all.bat file and open it with notepad and edit out the -w and save it. Removing that saves your data apps and settings.
Open a command prompt in your platform tools folder
Connect the phone to the PC
Adb reboot bootloader
flash-all.bat
Reboot, redo your root and wifi tether haxk
I attempted this and the following occured. I attempted to use the Dec update and got the same errors. Do I have to start from the Nov update, then do Dec, then Jan?
Code:
target reported max download size of 536870912 bytes
sending 'bootloader_b' (36344 KB)...
OKAY [ 6.458s]
writing 'bootloader_b'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 6.461s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target reported max download size of 536870912 bytes
sending 'radio_b' (60428 KB)...
OKAY [ 4.517s]
writing 'radio_b'...
OKAY [ 0.572s]
finished. total time: 5.091s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.228s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.029s
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... took 21.596s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 6.476s
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 3.851s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
--------------------------------------------
Bootloader Version...: TMZ10n
Baseband Version.....: g8998-00164-1710262031
Serial Number........: 711KPED0781084
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
FAILED
Device version-bootloader is 'TMZ10n'.
Update requires 'TMZ12b'.
finished. total time: 0.016s
Press any key to exit...
jdougal11 said:
I attempted this and the following occured. I attempted to use the Dec update and got the same errors. Do I have to start from the Nov update, then do Dec, then Jan?
Click to expand...
Click to collapse
Did you first unlock your bootloader critical partition?
fastboot flashing unlock_critical
Same here, my apps crash like crazy and i factory reset like 3 times but still same problem except that now is only social apps and a couple games that keeps crashing and not even reinstalling and fixes the problem
Trying to return to stock but for some reason it keeps failing. Any help is appreciated! Using Ubuntu.
Terminal out is:
sudo ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32424 KB)...
OKAY [ 1.193s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 4.603s]
finished. total time: 5.795s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.147s
target reported max download size of 536870912 bytes
sending 'radio_a' (57140 KB)...
OKAY [ 2.304s]
writing 'radio_a'...
OKAY [ 0.488s]
finished. total time: 2.792s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.100s
extracting android-info.txt (0 MB)...
extracting boot.img (30 MB)...
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 (1953 MB)...
archive does not contain 'system.sig'
extracting system_other.img (312 MB)...
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (259 MB)...
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.44.4 (18-Aug-2018)
/tmp/TemporaryFile-vc741h: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
I had the same issue yesterday. Fixed it by downloading the latest SDK platform tools here https://developer.android.com/studio/releases/platform-tools and extracting all the files into the same folder as the factory image with the flash-all script.
christanya99 said:
Trying to return to stock but for some reason it keeps failing. Any help is appreciated! Using Ubuntu.
Terminal out is:
sudo ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32424 KB)...
OKAY [ 1.193s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 4.603s]
finished. total time: 5.795s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.147s
target reported max download size of 536870912 bytes
sending 'radio_a' (57140 KB)...
OKAY [ 2.304s]
writing 'radio_a'...
OKAY [ 0.488s]
finished. total time: 2.792s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.100s
extracting android-info.txt (0 MB)...
extracting boot.img (30 MB)...
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 (1953 MB)...
archive does not contain 'system.sig'
extracting system_other.img (312 MB)...
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (259 MB)...
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.44.4 (18-Aug-2018)
/tmp/TemporaryFile-vc741h: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
Click to expand...
Click to collapse
The problem is "/usr/lib/android-sdk/platform-tools/mke2fs"
* Check that you have a mke2fs in that directory. If yes, install the latest platform-tools
* If you don't, install the full platform-tools (not the small pack containing only fastboot, adb, and a few other stuff...)
The fix from the other answer will work, but you shouldn't have the install platform-tools in every stock image you want to install...
I was having similar errors with my google Pixel C. Its stock .zip file has again another .zip file.I also extracted that .zip file and manually flashed each .img one by one and it did worked for me.
sudo fastboot flash bootloader bootloader_dragon-google-smug.img
sudo fastboot reboot bootloder
sudo fastboot devices
sudo fastboot flash boot boot.img
sudo fastboot flash cache cache.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash system system.img
sudo fastboot flash vendor vendor.img
(I used sudo to be extra safe.)
hello i have unlocked google pixel 2xl and i can't flash twrp because my phone didn't have recovery and i also can't fastboot boot twrp this go back to bootloader screen after warning message with phone is unlocked warning
product name taimen
variant - MSM UFS:SAMSUNG(128) DDR:HYNIX
secure boot yes
device state unlocked
Official factory image
HTML:
[email protected]:~/taimen factory image$ ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader_a' (36356 KB)...
OKAY [ 0.123s]
writing 'bootloader_a'...
OKAY [ 0.699s]
finished. total time: 0.822s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.251s
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'radio_a' (60372 KB)...
OKAY [ 0.206s]
writing 'radio_a'...
OKAY [ 1.114s]
finished. total time: 1.320s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.251s
extracting android-info.txt (0 MB)...
extracting boot.img (40 MB)...
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB)...
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2226 MB)...
archive does not contain 'system.sig'
extracting system_other.img (321 MB)...
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB)...
archive does not contain 'vbmeta.sig'
extracting vendor.img (351 MB)...
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.44.1 (24-Mar-2018)
Varování: šířka pruhu RAIDu 1 není sudý násobek kroku (stride) 2.
/tmp/TemporaryFile-Rc3eqB: Neimplementovaná funkce knihovny ext2 při nastavování superbloku
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
Twrp
HTML:
[email protected]:~$ fastboot flash recovery twrp-pixel2-installer-taimen-3.3.0-0.zip
target reported max download size of 536870912 bytes
sending 'recovery' (10826 KB)...
OKAY [ 0.048s]
writing 'recovery'...
FAILED (remote: No such partition.)
finished. total time: 0.051s
heavyblack said:
hello i have unlocked google pixel 2xl and i can't flash twrp because my phone didn't have recovery and i also can't fastboot boot twrp this go back to bootloader screen after warning message with phone is unlocked warning
product name taimen
variant - MSM UFS:SAMSUNG(128) DDR:HYNIX
secure boot yes
device state unlocked
Official factory image
[email protected]:~/taimen factory image$ ./flash-all.sh target reported max download size of 536870912 bytessending 'bootloader_a' (36356 KB)...OKAY [ 0.123s]writing 'bootloader_a'...OKAY [ 0.699s]finished. total time: 0.822srebooting into bootloader...OKAY [ 0.000s]finished. total time: 0.251s< waiting for any device >target reported max download size of 536870912 bytessending 'radio_a' (60372 KB)...OKAY [ 0.206s]writing 'radio_a'...OKAY [ 1.114s]finished. total time: 1.320srebooting into bootloader...OKAY [ 0.000s]finished. total time: 0.251sextracting android-info.txt (0 MB)...extracting boot.img (40 MB)...target reported max download size of 536870912 bytesarchive does not contain 'boot.sig'archive does not contain 'boot_other.img'extracting dtbo.img (8 MB)...archive does not contain 'dtbo.sig'archive does not contain 'dt.img'archive does not contain 'recovery.img'extracting system.img (2226 MB)...archive does not contain 'system.sig'extracting system_other.img (321 MB)...archive does not contain 'system.sig'extracting vbmeta.img (0 MB)...archive does not contain 'vbmeta.sig'extracting vendor.img (351 MB)...archive does not contain 'vendor.sig'archive does not contain 'vendor_other.img'wiping userdata...mke2fs 1.44.1 (24-Mar-2018)Varován
---------- Post added at 04:47 PM ---------- Previous post was at 04:40 PM ----------
Badger50 said:
heavyblack said:
hello i have unlocked google pixel 2xl and i can't flash twrp because my phone didn't have recovery and i also can't fastboot boot twrp this go back to bootloader screen after warning message with phone is unlocked warning
product name taimen
variant - MSM UFS:SAMSUNG(128) DDR:HYNIX
secure boot yes
device state unlocked
Official factory image
[email protected]:~/taimen factory image$ ./flash-all.sh target reported max download size of 536870912 bytessending 'bootloader_a' (36356 KB)...OKAY [ 0.123s]writing 'bootloader_a'...OKAY [ 0.699s]finished. total time: 0.822srebooting into bootloader...OKAY [ 0.000s]finished. total time: 0.251s< waiting for any device >target reported max download size of 536870912 bytessending 'radio_a' (60372 KB)...OKAY [ 0.206s]writing 'radio_a'...OKAY [ 1.114s]finished. total time: 1.320srebooting into bootloader...OKAY [ 0.000s]finished. total time: 0.251sextracting android-info.txt (0 MB)...extracting boot.img (40 MB)...target reported max download size of 536870912 bytesarchive does not contain 'boot.sig'archive does not contain 'boot_other.img'extracting dtbo.img (8 MB)...archive does not contain 'dtbo.sig'archive does not contain 'dt.img'archive does not contain 'recovery.img'extracting system.img (2226 MB)...archive does not contain 'system.sig'extracting system_other.img (321 MB)...archive does not contain 'system.sig'extracting vbmeta.img (0 MB)...archive does not contain 'vbmeta.sig'extracting vendor.img (351 MB)...archive does not contain 'vendor.sig'archive does not contain 'vendor_other.img'wiping userdata...mke2fs 1.44.1 (24-Mar-2018)Varován
Click to expand...
Click to collapse
Wow! That was weird, my initial post didn't go through..strange
Are your platform-tools up to date? Have had this problem before? Are you using a Mac I take it?
Also, command line for twrp is incorrect. It should read...fastboot boot twrp-3.3.0-0-taimen.img
And, you need to fastboot the twrp.img file, not the zip file.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Badger50 said:
heavyblack said:
hello i have unlocked google pixel 2xl and i can't flash twrp because my phone didn't have recovery and i also can't fastboot boot twrp this go back to bootloader screen after warning message with phone is unlocked warning
product name taimen
variant - MSM UFS:SAMSUNG(128) DDR:HYNIX
secure boot yes
device state unlocked
Official factory image
[email protected]:~/taimen factory image$ ./flash-all.sh target reported max download size of 536870912 bytessending 'bootloader_a' (36356 KB)...OKAY [ 0.123s]writing 'bootloader_a'...OKAY [ 0.699s]finished. total time: 0.822srebooting into bootloader...OKAY [ 0.000s]finished. total time: 0.251s< waiting for any device >target reported max download size of 536870912 bytessending 'radio_a' (60372 KB)...OKAY [ 0.206s]writing 'radio_a'...OKAY [ 1.114s]finished. total time: 1.320srebooting into bootloader...OKAY [ 0.000s]finished. total time: 0.251sextracting android-info.txt (0 MB)...extracting boot.img (40 MB)...target reported max download size of 536870912 bytesarchive does not contain 'boot.sig'archive does not contain 'boot_other.img'extracting dtbo.img (8 MB)...archive does not contain 'dtbo.sig'archive does not contain 'dt.img'archive does not contain 'recovery.img'extracting system.img (2226 MB)...archive does not contain 'system.sig'extracting system_other.img (321 MB)...archive does not contain 'system.sig'extracting vbmeta.img (0 MB)...archive does not contain 'vbmeta.sig'extracting vendor.img (351 MB)...archive does not contain 'vendor.sig'archive does not contain 'vendor_other.img'wiping userdata...mke2fs 1.44.1 (24-Mar-2018)Varován
---------- Post added at 04:47 PM ---------- Previous post was at 04:40 PM ----------
Badger50 said:
Wow! That was weird, my initial post didn't go through..strange
Are your platform-tools up to date? Have had this problem before? Are you using a Mac I take it?
Also, command line for twrp is incorrect. It should read...fastboot boot twrp-3.3.0-0-taimen.img
And, you need to fastboot the twrp.img file, not the zip file.
Click to expand...
Click to collapse
i am using ubuntu adb is from apt repo because is hard to setup on win and if you do still you get weird messages like
and i using newest version
```powershell
PS C:\Users\heavyblack> adb devices
adb server version (40) doesn't match this client (41); killing...
could not read ok from ADB Server
* failed to start daemon
adb.exe: failed to check server version: cannot connect to daemon
PS C:\Users\heavyblack>
```
i tried boot twrp.img and working now but i still can't install official rom or flash lineage os
```
[email protected]:~/taimen factory image$ ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader_b' (36356 KB)...
OKAY [ 0.949s]
writing 'bootloader_b'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.950s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.201s
target reported max download size of 536870912 bytes
sending 'radio_b' (60372 KB)...
OKAY [ 1.556s]
writing 'radio_b'...
OKAY [ 0.932s]
finished. total time: 2.488s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.203s
extracting android-info.txt (0 MB)...
extracting boot.img (40 MB)...
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB)...
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2226 MB)...
archive does not contain 'system.sig'
extracting system_other.img (321 MB)...
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB)...
archive does not contain 'vbmeta.sig'
extracting vendor.img (351 MB)...
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.44.1 (24-Mar-2018)
Varování: šířka pruhu RAIDu 1 není sudý násobek kroku (stride) 2.
/tmp/TemporaryFile-d6fC4B: Neimplementovaná funkce knihovny ext2 při nastavování superbloku
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
```
Click to expand...
Click to collapse
Click to expand...
Click to collapse
heavyblack said:
Badger50 said:
heavyblack said:
hello i have unlocked google pixel 2xl and i can't flash twrp because my phone didn't have recovery and i also can't fastboot boot twrp this go back to bootloader screen after warning message with phone is unlocked warning
product name taimen
variant - MSM UFS:SAMSUNG(128) DDR:HYNIX
secure boot yes
device state unlocked
Official factory image
[email protected]:~/taimen factory image$ ./flash-all.sh target reported max download size of 536870912 bytessending 'bootloader_a' (36356 KB)...OKAY [ 0.123s]writing 'bootloader_a'...OKAY [ 0.699s]finished. total time: 0.822srebooting into bootloader...OKAY [ 0.000s]finished. total time: 0.251s< waiting for any device >target reported max download size of 536870912 bytessending 'radio_a' (60372 KB)...OKAY [ 0.206s]writing 'radio_a'...OKAY [ 1.114s]finished. total time: 1.320srebooting into bootloader...OKAY [ 0.000s]finished. total time: 0.251sextracting android-info.txt (0 MB)...extracting boot.img (40 MB)...target reported max download size of 536870912 bytesarchive does not contain 'boot.sig'archive does not contain 'boot_other.img'extracting dtbo.img (8 MB)...archive does not contain 'dtbo.sig'archive does not contain 'dt.img'archive does not contain 'recovery.img'extracting system.img (2226 MB)...archive does not contain 'system.sig'extracting system_other.img (321 MB)...archive does not contain 'system.sig'extracting vbmeta.img (0 MB)...archive does not contain 'vbmeta.sig'extracting vendor.img (351 MB)...archive does not contain 'vendor.sig'archive does not contain 'vendor_other.img'wiping userdata...mke2fs 1.44.1 (24-Mar-2018)Varován
---------- Post added at 04:47 PM ---------- Previous post was at 04:40 PM ----------
i am using ubuntu adb is from apt repo because is hard to setup on win and if you do still you get weird messages like
and i using newest version
```powershell
PS C:\Users\heavyblack> adb devices
adb server version (40) doesn't match this client (41); killing...
could not read ok from ADB Server
* failed to start daemon
adb.exe: failed to check server version: cannot connect to daemon
PS C:\Users\heavyblack>
```
i tried boot twrp.img and working now but i still can't install official rom or flash lineage os
```
[email protected]:~/taimen factory image$ ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader_b' (36356 KB)...
OKAY [ 0.949s]
writing 'bootloader_b'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.950s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.201s
target reported max download size of 536870912 bytes
sending 'radio_b' (60372 KB)...
OKAY [ 1.556s]
writing 'radio_b'...
OKAY [ 0.932s]
finished. total time: 2.488s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.203s
extracting android-info.txt (0 MB)...
extracting boot.img (40 MB)...
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB)...
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2226 MB)...
archive does not contain 'system.sig'
extracting system_other.img (321 MB)...
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB)...
archive does not contain 'vbmeta.sig'
extracting vendor.img (351 MB)...
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.44.1 (24-Mar-2018)
Varování: šířka pruhu RAIDu 1 není sudý násobek kroku (stride) 2.
/tmp/TemporaryFile-d6fC4B: Neimplementovaná funkce knihovny ext2 při nastavování superbloku
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
```
Click to expand...
Click to collapse
It seems you may need to run the command: fastboot flashing unlock_critical
Which is very unusual, since Pixel's shouldn't really need to do this if fresh unlocking in the last couple of months...
Then, again making sure you have the most up to date platform-tools, it's best if you be sure to use USB-A to USB-C cords (not USB-C if possible) and/or various different usb ports as well. Usually "max download size" and "daemon" issues can be followed back to these reasons...
But, if anything and most concerning, is the error/line "adb server version (40) doesn't match this client (41); killing...
could not read ok from ADB Server"
You would be better served figuring out what's wrong with adb and how to get that working. You won't be getting any further until adb and adb server is running better or flawlessly. As I recall, isn't it that MacOS and Linux have different syntax where you have to include/add more into a command...? I'll try to check on that....
good luck and hope this ends up being helpful...
P.S. yeah...don't you have to include & start with "./" for commands...? I'm unsure if it relates to this situation or to your OS, but just something that popped into my mind...
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Hello,
I was trying to flash the factory image via fastboot and I am getting a failed message in the part where it says "sending product". I have pasted the last part of the information from the CMD prompt below. Now I cannot boot into anything. I was trying to restore the same factory image that the phone was already on which was Android 10 005 update. Bootloader is unlocked. Phone had Magisk Root before I tried to do this. I tried switching to slot B and still same error. I can't seem to find anything on google about this error.
Anyone know what I can do? I need to get the phone back up and running, I don't care about losing any data.
--------------------------------------------
Bootloader Version...: b1c1-0.2-6085603
Baseband Version.....: g845-00096-200114-B-6134206
Serial Number........: 91PY17NNE
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.057s]
Checking 'version-bootloader' OKAY [ 0.058s]
Checking 'version-baseband' OKAY [ 0.057s]
Setting current slot to 'a' OKAY [ 0.068s]
extracting boot.img (64 MB) to disk... took 0.237s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 0.332s]
Writing 'boot_a' OKAY [ 0.364s]
extracting dtbo.img (8 MB) to disk... took 0.021s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.129s]
Writing 'dtbo_a' OKAY [ 0.100s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (4 KB) OKAY [ 0.112s]
Writing 'vbmeta_a' OKAY [ 0.060s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.057s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 0.006s]
Deleting 'system_b' OKAY [ 0.005s]
Deleting 'vendor_b' OKAY [ 0.005s]
Resizing 'product_a' OKAY [ 0.005s]
Resizing 'system_a' OKAY [ 0.006s]
Resizing 'vendor_a' OKAY [ 0.006s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (1980 MB) to disk... took 12.201s
archive does not contain 'product.sig'
Sending 'product' (2027860 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
sharky17 said:
Hello,
I was trying to flash the factory image via fastboot and I am getting a failed message in the part where it says "sending product". I have pasted the last part of the information from the CMD prompt below. Now I cannot boot into anything. I was trying to restore the same factory image that the phone was already on which was Android 10 005 update. Bootloader is unlocked. Phone had Magisk Root before I tried to do this. I tried switching to slot B and still same error. I can't seem to find anything on google about this error.
Anyone know what I can do? I need to get the phone back up and running, I don't care about losing any data.
--------------------------------------------
Bootloader Version...: b1c1-0.2-6085603
Baseband Version.....: g845-00096-200114-B-6134206
Serial Number........: 91PY17NNE
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.057s]
Checking 'version-bootloader' OKAY [ 0.058s]
Checking 'version-baseband' OKAY [ 0.057s]
Setting current slot to 'a' OKAY [ 0.068s]
extracting boot.img (64 MB) to disk... took 0.237s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 0.332s]
Writing 'boot_a' OKAY [ 0.364s]
extracting dtbo.img (8 MB) to disk... took 0.021s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.129s]
Writing 'dtbo_a' OKAY [ 0.100s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (4 KB) OKAY [ 0.112s]
Writing 'vbmeta_a' OKAY [ 0.060s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.057s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 0.006s]
Deleting 'system_b' OKAY [ 0.005s]
Deleting 'vendor_b' OKAY [ 0.005s]
Resizing 'product_a' OKAY [ 0.005s]
Resizing 'system_a' OKAY [ 0.006s]
Resizing 'vendor_a' OKAY [ 0.006s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (1980 MB) to disk... took 12.201s
archive does not contain 'product.sig'
Sending 'product' (2027860 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Click to expand...
Click to collapse
Normally, it is nothing more than a dodgy cable. Try using a new A>C cable and a different port. To get yourself up and running immediately, when the error happens (you are in fastbootd), keep your command prompt or terminal up and go to recovery from fastbootd. Download the OTA, and from fastbootd>recovery start an ADB sideload of the downloaded OTA file.
sharky17 said:
Hello,
I was trying to flash the factory image via fastboot and I am getting a failed message in the part where it says "sending product". I have pasted the last part of the information from the CMD prompt below. Now I cannot boot into anything. I was trying to restore the same factory image that the phone was already on which was Android 10 005 update. Bootloader is unlocked. Phone had Magisk Root before I tried to do this. I tried switching to slot B and still same error. I can't seem to find anything on google about this error.
Anyone know what I can do? I need to get the phone back up and running, I don't care about losing any data.
--------------------------------------------
Bootloader Version...: b1c1-0.2-6085603
Baseband Version.....: g845-00096-200114-B-6134206
Serial Number........: 91PY17NNE
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.057s]
Checking 'version-bootloader' OKAY [ 0.058s]
Checking 'version-baseband' OKAY [ 0.057s]
Setting current slot to 'a' OKAY [ 0.068s]
extracting boot.img (64 MB) to disk... took 0.237s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 0.332s]
Writing 'boot_a' OKAY [ 0.364s]
extracting dtbo.img (8 MB) to disk... took 0.021s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.129s]
Writing 'dtbo_a' OKAY [ 0.100s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (4 KB) OKAY [ 0.112s]
Writing 'vbmeta_a' OKAY [ 0.060s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.057s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 0.006s]
Deleting 'system_b' OKAY [ 0.005s]
Deleting 'vendor_b' OKAY [ 0.005s]
Resizing 'product_a' OKAY [ 0.005s]
Resizing 'system_a' OKAY [ 0.006s]
Resizing 'vendor_a' OKAY [ 0.006s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (1980 MB) to disk... took 12.201s
archive does not contain 'product.sig'
Sending 'product' (2027860 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Click to expand...
Click to collapse
The exact same thing has happened to me BUT if I kept repeating the process it would finally work. Try flashing 3 or 4 more times. This has happened to me the last 2 or three updates I tried to flash. Don't think it was the cable in my case because I tried different ones. I just keep trying and finally it'll work.
Same experience as @sliding_billy, its usually a cable issue or port issue, assuming your download isnt corrupted.
Daisymae said:
The exact same thing has happened to me BUT if I kept repeating the process it would finally work. Try flashing 3 or 4 more times. This has happened to me the last 2 or three updates I tried to flash. Don't think it was the cable in my case because I tried different ones. I just keep trying and finally it'll work.
Click to expand...
Click to collapse
I originally tried a few times before I posted this. But today I came back and tried again and it worked . SMH, that is weird. Thanks!!!
Update: Problem fixed as @Lughnasadh said: flash.android.com fixes the issue a buggy fastboot version can create.
=======
DISCLAIMER:
this might look like a double post.
if I could change the topic, i would have continued the old thread. I saw the topic doesnt reflect that problem very well anymore. I hope I dont break any rules by this.
So, for the history of all this, you can check this post which contains lots of logs: https://forum.xda-developers.com/t/flash-all-sh-vendor-partition-non-existing.4570905/
It also contains the Tip from @Lughnasadh solving the first huddle: fastboot 34+ is flawed, i downgraded to fastboot 33.0.1 and all the inital problems were gone.
=========
PROBLEM
=========
I dont talk about the why. If you want to know, look at the outdated post.
Situation: Vendor partition missing. Flashing firmware image isnt possbile because fastbootd cannot be started, because there is no vendor partition. Plus you can only create or modify partitions in fastbootd, not in fastboot.
Is this a classical hen-egg problem and I have a soft bricked phone, or is there any way around I dont see?
Here is some log for you:
Bash:
┬─[[email protected]:~/D/raven-tq2a.230305.008.e1]─[03:50:35]─[I]
╰─>$ fastboot update image-raven-tq2a.230305.008.e1.zip
--------------------------------------------
Bootloader Version...: slider-1.2-9465321
Baseband Version.....: g5123b-112825-230302-B-9675756
Serial Number........: 23041FDEE005AM
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.000s]
Setting current slot to 'b' OKAY [ 0.124s]
extracting boot.img (64 MB) to disk... took 0.339s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 2.116s]
Writing 'boot_b' OKAY [ 0.116s]
archive does not contain 'init_boot.img'
extracting dtbo.img (16 MB) to disk... took 0.065s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB) OKAY [ 0.522s]
Writing 'dtbo_b' OKAY [ 0.028s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.009s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_b' (1024 KB) OKAY [ 0.034s]
Writing 'pvmfw_b' OKAY [ 0.003s]
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (12 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' OKAY [ 0.002s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_b' OKAY [ 0.002s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_vendor_b' OKAY [ 0.002s]
extracting vendor_boot.img (64 MB) to disk... took 0.367s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_b' (65536 KB) OKAY [ 2.130s]
Writing 'vendor_boot_b' OKAY [ 0.116s]
archive does not contain 'vendor_kernel_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.001s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Hmm, while copying this I wonder, if I can supply a vendor_kernel_boot.img, add it to the update zip and then start fastbootd this way. where do i get an up to date vendor_kernel_boot.img though?
Starting googling now. Dont hessitate to meanwhile answer
mad-murdock said:
DISCLAIMER:
this might look like a double post.
if I could change the topic, i would have continued the old thread. I saw the topic doesnt reflect that problem very well anymore. I hope I dont break any rules by this.
So, for the history of all this, you can check this post which contains lots of logs: https://forum.xda-developers.com/t/flash-all-sh-vendor-partition-non-existing.4570905/
=========
PROBLEM
=========
I dont talk about the why. If you want to know, look at the outdated post.
Situation: Vendor partition missing. Flashing firmware image isnt possbile because fastbootd cannot be started, because there is no vendor partition. Plus you can only create or modify partitions in fastbootd, not in fastboot.
Is this a classical hen-egg problem and I have a soft bricked phone, or is there any way around I dont see?
Here is some log for you:
Bash:
┬─[[email protected]:~/D/raven-tq2a.230305.008.e1]─[03:50:35]─[I]
╰─>$ fastboot update image-raven-tq2a.230305.008.e1.zip
--------------------------------------------
Bootloader Version...: slider-1.2-9465321
Baseband Version.....: g5123b-112825-230302-B-9675756
Serial Number........: 23041FDEE005AM
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.000s]
Setting current slot to 'b' OKAY [ 0.124s]
extracting boot.img (64 MB) to disk... took 0.339s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 2.116s]
Writing 'boot_b' OKAY [ 0.116s]
archive does not contain 'init_boot.img'
extracting dtbo.img (16 MB) to disk... took 0.065s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB) OKAY [ 0.522s]
Writing 'dtbo_b' OKAY [ 0.028s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.009s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_b' (1024 KB) OKAY [ 0.034s]
Writing 'pvmfw_b' OKAY [ 0.003s]
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (12 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' OKAY [ 0.002s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_b' OKAY [ 0.002s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_vendor_b' OKAY [ 0.002s]
extracting vendor_boot.img (64 MB) to disk... took 0.367s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_b' (65536 KB) OKAY [ 2.130s]
Writing 'vendor_boot_b' OKAY [ 0.116s]
archive does not contain 'vendor_kernel_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.001s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Hmm, while copying this I wonder, if I can supply a vendor_kernel_boot.img, add it to the update zip and then start fastbootd this way. where do i get an up to date vendor_kernel_boot.img though?
Starting googling now. Dont hessitate to meanwhile answer
Click to expand...
Click to collapse
Try Android Flash Tool. You can force flash partitions with it.
Also, did you try with Platform Tools 33.0.3 as I mentioned in your other post? That version doesn't have a problem booting into fastbootd like 34+ does.
For future notice, just report your post, asking that it be recatogorized.
Lughnasadh said:
Try Android Flash Tool. You can force flash partitions with it.
Also, did you try with Platform Tools 33.0.3 as I mentioned in your other post? That version doesn't have a problem booting into fastbootd like 34+ does.
Click to expand...
Click to collapse
Oh yes, all this new stuff is based on your super good tip with using 33.0.3 over 34+...
I use arch linux, I am an seasoned linux admin, I accidentally installed a non-stable fastboot and that was the reason the first flash-all.sh was breaking.
Thanks for pointing this out, @Lughnasadh , that totally solved the first part. Sorry I didnt make this clear. I will update the OP to more clearly reflect this.
Its late here in germany, I will try tomorrow morning what you said. I guess it will work.
P.S.: Do you agree the original topic was misleading?
Arealhooman said:
For future notice, just report your post, asking that it be recatogorized.
Click to expand...
Click to collapse
Thanks. Thats the better solution and is noted for next time. I am not very active here anymore, but this is still the best place to get information if something goes wrong. XDA or nagging one of my old android os developers I had the honor to work with in my life...
Thanks for showing me a cool use of the report button, too
Lughnasadh said:
Try Android Flash Tool. You can force flash partitions with it.
Also, did you try with Platform Tools 33.0.3 as I mentioned in your other post? That version doesn't have a problem booting into fastbootd like 34+ does.
Click to expand...
Click to collapse
Sorry it took a while, my life is wonderful and full of people... sooo...
I think i got it working with flash.android.com
I confess the flash.android.com is new to me. I lost close contact with the android open source scene a few years back (sorry steve kondik ... and so in some regards I am a noob, while in others i got the needed background info.
to me the flash.android.com flasher seems to only detect phones in adb while booted to the system. but from what you say, there should be a way to force the flash also while not having anything than fastboot. But, i cannot find that anywhere. I am probably blind, but can you explain the process a bit more detailed. I tried a few google searches, but couldnt find a guide.
Cheers
Update: Problem fixed as @Lughnasadh said: flash.android.com fixes the issue a buggy fastboot version can create.