Hi, I recently changed to a Custom ROM (Resurrection Remix) and stupid me forgot to backup before unlocking the bootloader, meaning I don't have a stock image. Here's the whole thing:
Resurrection Remix is based on LOS, so I have Lineage recovery atm.
I don't have TWRP flashed, but even when I used fastboot boot twrp.img it booted into TWRP and kept flashing the TWRP logo you see when you boot into it. If you have a TWRP backup I can try and use, that would be great. When I try flashing the official factory image, it just flashes a few things, says it can't find the file 'userdata' and says it failed, here's what happens:
HTML:
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32424 KB)...
OKAY [ 2.031s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 1.949s]
finished. total time: 3.985s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.054s
target reported max download size of 536870912 bytes
sending 'radio_a' (57140 KB)...
OKAY [ 3.132s]
writing 'radio_a'...
OKAY [ 0.461s]
finished. total time: 3.601s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.055s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (30 MB) to disk... took 0.998s
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 (1938 MB) to disk... took 127.844s
archive does not contain 'system.sig'
extracting system_other.img (311 MB) to disk... took 104.834s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (260 MB) to disk... took 13.234s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
CreateProcess failed: The system cannot find the file specified. (2)
error: Cannot generate image for userdata
Press any key to exit...
My Pixel XL is in bootloader mode and I do have an OS installed, so I still can access the phone.
Please help, thanks!
Lol. Why do you try to flash stock image using minimal ADB/Fastboot? Did you try following the Google way?
Basically: unzip the factory image and double click flash-all.bat script ?
Here is a proper how-to:
https://developers.google.com/android/images
Good luck...
Agree with @5.1's thoughts. Update to latest/greatest platform tools from Google Developers site...then ensure you have downloaded the proper Factory Image. Then flash per the instructions on the Google site.
---------- Post added at 09:09 AM ---------- Previous post was at 09:07 AM ----------
Agree with @5.1's thoughts. Update to latest/greatest platform tools from Google Developers site...then ensure you have downloaded the proper Factory Image. Then flash per the instructions on the Google site.
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
Hi guys,
Please help me with my phone.
I have my pixel XL rooted and accidentally upgraded to android 10 and lost my root.
However, when i was in the process of trying to re-root the phone, i probably did something stupid and got my phone soft bricked with the phone turning into to a bootloop showing the Google sign and the screen on booting up.
I am able to enter the bootloader screen and tried to flash the Factory Stock image, from the old version such as 7.1.0 to the new version 10.0.0 but failed.
This is the message i got every time i flash the factory image.
============================================================
Microsoft Windows [版本 10.0.18362.720]
(c) 2019 Microsoft Corporation. 著作權所有，並保留一切權利。
D:\Program Files (x86)\Android\Minimal ADB and Fastboot\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32480 KB)...
OKAY [ 0.888s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.060s]
finished. total time: 2.950s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.051s
target reported max download size of 536870912 bytes
sending 'radio_a' (57156 KB)...
OKAY [ 1.550s]
writing 'radio_a'...
OKAY [ 0.498s]
finished. total time: 2.052s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.053s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (30 MB) to disk... took 0.325s
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 (1998 MB) to disk... took 9.441s
archive does not contain 'system.sig'
extracting system_other.img (293 MB) to disk... took 1.527s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (253 MB) to disk... took 1.275s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
CreateProcess failed: 蝟餌絞?曆??唳?摰?瑼???(2)
error: Cannot generate image for userdata
Press any key to exit...
;urgently need your help.
sam
samsam2020 said:
Hi guys,
Please help me with my phone.
I have my pixel XL rooted and accidentally upgraded to android 10 and lost my root.
However, when i was in the process of trying to re-root the phone, i probably did something stupid and got my phone soft bricked with the phone turning into to a bootloop showing the Google sign and the screen on booting up.
I am able to enter the bootloader screen and tried to flash the Factory Stock image, from the old version such as 7.1.0 to the new version 10.0.0 but failed.
This is the message i got every time i flash the factory image.
============================================================
Microsoft Windows [版本 10.0.18362.720]
(c) 2019 Microsoft Corporation. 著作權所有，並保留一切權利。
D:\Program Files (x86)\Android\Minimal ADB and Fastboot\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32480 KB)...
OKAY [ 0.888s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.060s]
finished. total time: 2.950s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.051s
target reported max download size of 536870912 bytes
sending 'radio_a' (57156 KB)...
OKAY [ 1.550s]
writing 'radio_a'...
OKAY [ 0.498s]
finished. total time: 2.052s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.053s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (30 MB) to disk... took 0.325s
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 (1998 MB) to disk... took 9.441s
archive does not contain 'system.sig'
extracting system_other.img (293 MB) to disk... took 1.527s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (253 MB) to disk... took 1.275s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
CreateProcess failed: 蝟餌絞?曆??唳?摰?瑼???(2)
error: Cannot generate image for userdata
Press any key to exit...
;urgently need your help.
sam
Click to expand...
Click to collapse
You installed an Android 10 factory image, please DO NOT try installing an Android 7xx factory image.
If your bootloader is unlocked try this using this Guide:
- First, remove (uninstall) Minimal ADB from your computer.
- Second, download and install SDK Platform-tools r29.0.6 on your computer. There is a link in the guide: Prerequisites c.
- You are on Android 10 Factory Image (10.0.0 (QP1A.191005.007.A3, Dec 2019)) so just do # 9 in the guide to root/reroot.
Note: Check your bootloader and radio version.
Why? You tried to flash an Android 7xx factory image and it look like the Android 7xx bootloader and radio replaced the Android 10 bootloader and radio.
If your bootloader and radio are not:
- bootloader-marlin-8996-012001-1908071822.img
- radio-marlin-8996-130361-1905270421.img
Open a command prompt #1 in the guide and flash them:
Code:
fastboot flash bootloader bootloader-marlin-8996-012001-1908071822.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-130361-1905270421.img
fastboot reboot-bootloader
Homeboy76 said:
You installed an Android 10 factory image, please DO NOT try installing an Android 7xx factory image.
If your bootloader is unlocked try this using this Guide:
- First, remove (uninstall) Minimal ADB from your computer.
- Second, download and install SDK Platform-tools r29.0.6 on your computer. There is a link in the guide: Prerequisites c.
- You are on Android 10 Factory Image (10.0.0 (QP1A.191005.007.A3, Dec 2019)) so just do # 9 in the guide to root/reroot.
Note: Check your bootloader and radio version.
Why? You tried to flash an Android 7xx factory image and it look like the Android 7xx bootloader and radio replaced the Android 10 bootloader and radio.
If your bootloader and radio are not:
- bootloader-marlin-8996-012001-1908071822.img
- radio-marlin-8996-130361-1905270421.img
Open a command prompt #1 in the guide and flash them:
Code:
fastboot flash bootloader bootloader-marlin-8996-012001-1908071822.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-130361-1905270421.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
:good::good::good:
Very GOOD man!
Just tried and i was able to restore the factory image
also rooted my phone again!!
Million thanks for your help.
pics, pardon the **** quality
Tried rooting it, fastboot works but ADB doesn't seem to recognise my device. I went to the link it gave me and followed the tutorial it gave me clicked on it hopes of at least getting back to stock, but at the step were I run the bash script (flash-all.sh) it errors out.
Spoiler: flash-all.sh output
Code:
target reported max download size of 536870912 bytes
sending 'bootloader' (4610 KB)...
OKAY [ 0.212s]
writing 'bootloader'...
OKAY [ 0.154s]
finished. total time: 0.366s
rebooting into bootloader...
OKAY [ 0.019s]
finished. total time: 0.069s
target reported max download size of 536870912 bytes
sending 'radio' (56630 KB)...
OKAY [ 1.463s]
writing 'radio'...
OKAY [ 0.535s]
finished. total time: 1.998s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.070s
extracting android-info.txt (0 MB)...
extracting boot.img (11 MB)...
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (17 MB)...
archive does not contain 'recovery.sig'
extracting system.img (1909 MB)...
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (185 MB)...
archive does not contain 'vendor.sig'
wiping userdata...
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
mke2fs 1.44.5 (15-Dec-2018)
/tmp/TemporaryFile-QFwJ4m: 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
Where/how can I fix my mess via fastboot or something else?
Extract Android 10 rom and flash the images.
jjgvv said:
Extract Android 10 rom and flash the images.
Click to expand...
Click to collapse
Wouldn't Android 10 run like crap on the Nexus 5X, though? I've only tried some of the 8.1 ROMs, that's the highest it goes on the official page.
seething_n00b said:
Wouldn't Android 10 run like crap on the Nexus 5X, though? I've only tried some of the 8.1 ROMs, that's the highest it goes on the official page.
Click to expand...
Click to collapse
It will not run like crap but will also not be very fast.
seething_n00b said:
Wouldn't Android 10 run like crap on the Nexus 5X, though? I've only tried some of the 8.1 ROMs, that's the highest it goes on the official page.
Click to expand...
Click to collapse
custom rom, 8.1 is Google Offical firmware, offical firmware wont extract ot so
Solved on my own by realising I could just flash TWRP via fastboot. Duh.
jjgvv said:
custom rom, 8.1 is Google Offical firmware, offical firmware wont extract ot so
Click to expand...
Click to collapse
"8.1 won't work, so try 10!" You're even more of an idiot than me.
nope,8.1 is offical ota and can not be flashed in fastboot but only in recovery.