I have a pixel XL Verizon , i want to flash the latest firmware for this device. Which factory package should i download ?coz there are many packages on the official site for this device, should i download the latest package or the package that has Verizon written on its name, forgive me if I'm taking nonsense, i am noob in this kind of things, ( my phone's bootloader is unlocked ). Help me out.
mushi_ami said:
I have a pixel XL Verizon , i want to flash the latest firmware for this device. Which factory package should i download ?coz there are many packages on the official site for this device, should i download the latest package or the package that has Verizon written on its name, forgive me if I'm taking nonsense, i am noob in this kind of things, ( my phone's bootloader is unlocked ). Help me out.
Click to expand...
Click to collapse
March 2019 factory image 9
0.0 (Pie)
Homeboy76 said:
March 2019 factory image 9
0.0 (Pie)
Click to expand...
Click to collapse
Thnx , will try.
flashing did not work, i got this error while flashing, what to do ? pls help me.
./flash-all.sh
target reported max download size of 536870912 bytes
Sending 'bootloader_a' (32424 KB)...
OKAY [ 1.241s]
Writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 13.523s]
Finished. Total time: 14.975s
rebooting into bootloader
OKAY [ 0.049s]
Finished. Total time: 0.136s
target reported max download size of 536870912 bytes
Sending 'radio_a' (57140 KB)...
OKAY [ 1.902s]
Writing 'radio_a'...
OKAY [ 0.903s]
Finished. Total time: 3.044s
rebooting into bootloader
OKAY [ 0.050s]
Finished. Total time: 0.139s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: 8996-012001-1812132253
Baseband Version.....: 8996-130181-1811270246
Serial Number........: HT71H0200154
--------------------------------------------
Checking product
OKAY [ 0.050s]
Checking version-bootloader
OKAY [ 0.049s]
Checking version-baseband
OKAY [ 0.050s]
extracting boot.img (30 MB) to disk... took 0.270s
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 'odm.img'
archive does not contain 'product.img'
archive does not contain 'recovery.img'
extracting system.img (1953 MB) to disk...W/ziparchive( 8609): Zip: unable to allocate 2048663784 bytes at offset 0: No space left on device
error:
failed to extract 'system.img': I/O error
mushi_ami said:
flashing did not work, i got this error while flashing, what to do ? pls help me.
Click to expand...
Click to collapse
Follow Homeboy's guide.........all the info you need is there
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3825866
mushi_ami said:
flashing did not work, i got this error while flashing, what to do ? pls help me.
./flash-all.sh
target reported max download size of 536870912 bytes
Sending 'bootloader_a' (32424 KB)...
OKAY [ 1.241s]
Writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 13.523s]
Finished. Total time: 14.975s
rebooting into bootloader
OKAY [ 0.049s]
Finished. Total time: 0.136s
target reported max download size of 536870912 bytes
Sending 'radio_a' (57140 KB)...
OKAY [ 1.902s]
Writing 'radio_a'...
OKAY [ 0.903s]
Finished. Total time: 3.044s
rebooting into bootloader
OKAY [ 0.050s]
Finished. Total time: 0.139s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: 8996-012001-1812132253
Baseband Version.....: 8996-130181-1811270246
Serial Number........: HT71H0200154
--------------------------------------------
Checking product
OKAY [ 0.050s]
Checking version-bootloader
OKAY [ 0.049s]
Checking version-baseband
OKAY [ 0.050s]
extracting boot.img (30 MB) to disk... took 0.270s
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 'odm.img'
archive does not contain 'product.img'
archive does not contain 'recovery.img'
extracting system.img (1953 MB) to disk...W/ziparchive( 8609): Zip: unable to allocate 2048663784 bytes at offset 0: No space left on device
error:
failed to extract 'system.img': I/O error
Click to expand...
Click to collapse
"extracting system.img (1953 MB) to disk...W/ziparchive( 8609): Zip: unable to allocate 2048663784 bytes at offset 0: No space left on device
error:
failed to extract 'system.img': I/O error"
Looks like you do not have enough space on your Pixel XL phone.
Pixel Phone Help or Pixel™, Phone by Google - Check Memory
crackerjack1957 said:
Follow Homeboy's guide.........all the info you need is there
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3825866
Click to expand...
Click to collapse
i did follow his guide and ended up with the error.
Homeboy76 said:
"extracting system.img (1953 MB) to disk...W/ziparchive( 8609): Zip: unable to allocate 2048663784 bytes at offset 0: No space left on device
error:
failed to extract 'system.img': I/O error"
Looks like you do not have enough space on your Pixel XL phone.
Pixel Phone Help or Pixel™, Phone by Google - Check Memory
Click to expand...
Click to collapse
to make sure that i have enough space i factory reset my phone, nd still the same error.
what should i do ?
Some history of the phone?
Maybe hardware issue.
mushi_ami said:
i did follow his guide and ended up with the error.
to make sure that i have enough space i factory reset my phone, nd still the same error.
what should i do ?
Click to expand...
Click to collapse
So when you 'Factory Reset' your Pixel XL It didn't boot?
If, it booted go to Settings > System > About phone > Android version. What is the Android version date?
crackerjack1957 said:
Some history of the phone?
Maybe hardware issue.
Click to expand...
Click to collapse
Homeboy76 said:
So when you 'Factory Reset' your Pixel XL It didn't boot?
If, it booted go to Settings > System > About phone > Android version. What is the Android version date?
Click to expand...
Click to collapse
I was using Linux. performing the same steps using Windows 10 solved it, thanks everyone for your support !
Related
So I'm pretty accustomed to flashing system images and sideloading OTAs, but for some reason things are just not working for me on my Pixel XL.
Every time I run the "flash-all.bat" script (with the -w removed to preserve data) I can never seem to update properly, I get the following:
Code:
target reported max download size of 536870912 bytes
sending 'bootloadera' (32820 KB)...
OKAY [ 0.776s]
writing 'bootloadera'...
(bootloader) Valid bootloader version.
OKAY [ 1.064s]
finished. total time: 1.844s
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.356s]
writing 'radioa'...
OKAY [ 0.952s]
finished. total time: 2.322s
rebooting into bootloader...
OKAY [ 0.014s]
finished. total time: 0.015s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609191801
Serial Number........: [removed]
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.049s]
checking version-baseband...
OKAY [ 0.048s]
sending 'boota' (26405 KB)...
OKAY [ 0.680s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.139s
Press any key to exit...
I am on the original stock NDE63L, and I have had failures trying to flash both NDE63P (a few weeks ago) and NDE63X (today's build).
Additionally, ever since this process has failed for me, I am unable to boot into recovery, I just get the picture of the dead Android guy. So because of this I can't adb sideload the OTA as an alternative.
My bootloader is unlocked and I have rooted just fine, boot_a is listed as my active boot slot, but I have no idea why the system flash keeps failing.
Any thoughts as to why this is happening? Alternatively, is there a way to restore my recovery so I can try adb sideloading the OTA?
ChrisG683 said:
So I'm pretty accustomed to flashing system images and sideloading OTAs, but for some reason things are just not working for me on my Pixel XL.
Every time I run the "flash-all.bat" script (with the -w removed to preserve data) I can never seem to update properly, I get the following:
Code:
target reported max download size of 536870912 bytes
sending 'bootloadera' (32820 KB)...
OKAY [ 0.776s]
writing 'bootloadera'...
(bootloader) Valid bootloader version.
OKAY [ 1.064s]
finished. total time: 1.844s
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.356s]
writing 'radioa'...
OKAY [ 0.952s]
finished. total time: 2.322s
rebooting into bootloader...
OKAY [ 0.014s]
finished. total time: 0.015s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609191801
Serial Number........: [removed]
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.049s]
checking version-baseband...
OKAY [ 0.048s]
sending 'boota' (26405 KB)...
OKAY [ 0.680s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.139s
Press any key to exit...
I am on the original stock NDE63L, and I have had failures trying to flash both NDE63P (a few weeks ago) and NDE63X (today's build).
Additionally, ever since this process has failed for me, I am unable to boot into recovery, I just get the picture of the dead Android guy. So because of this I can't adb sideload the OTA as an alternative.
My bootloader is unlocked and I have rooted just fine, boot_a is listed as my active boot slot, but I have no idea why the system flash keeps failing.
Any thoughts as to why this is happening? Alternatively, is there a way to restore my recovery so I can try adb sideloading the OTA?
Click to expand...
Click to collapse
update ADB and Fastboot to latest version 1.0.3.6 release
Try the steps in my restore-to-stock thread?
I've used these steps twice for "L" and once for "V" builds.
No issues yet.
http://forum.xda-developers.com/pix...stock-soft-t3494478/post69476498#post69476498
---------- Post added at 03:09 PM ---------- Previous post was at 03:07 PM ----------
Oh, I remember getting that "boota does not exist".
I think I edited the script file somehow to fix that.
Can't remember what it was just now.
---------- Post added at 03:10 PM ---------- Previous post was at 03:09 PM ----------
Yours says "sending 'bootloadera'"
But mine that work says "sending 'bootloader_a'".
That may be the edit I did at one point.
But I have not had to edit anything while using the steps listed in my thread I linked to.
Taebom said:
update ADB and Fastboot to latest version 1.0.3.6 release
Click to expand...
Click to collapse
That seems to have done the trick, thank you so much!
Hey guys, I've Pixel 2 XL and I'm trying to flash the factory images on the phone using flash-all.bat. I had 8.1 earlier and was doing some tests with custom ROM and then wanted to start afresh. So I did these steps:
1. downloaded the factory image [taimen-opm1.171019.011-factory-2df1c1cb] from here.
2. Extracted it in a folder
3. Downloaded latest platform tools from here and extracted it to same folder
4. Opened command prompt and ran flash-all.bat
5. It flashed radio, bootloader and then while flashing system.img, it gave this error:
extracting system.img (1936 MB) to disk...W/ziparchive( 4084): Zip: unable to truncate file to 2030555488: File too large
Here is the full log:
Code:
The system cannot find message text for message number 0x2350 in the message fil
e for Application.
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
Not enough storage is available to process this command.
D:\Pixel 2 XL\nitin>fastboot --version
fastboot version 0.0.1-4500957
Installed as D:\Pixel 2 XL\nitin\fastboot.exe
D:\Pixel 2 XL\nitin>fastboot devices
710KPJP0210052 fastboot
D:\Pixel 2 XL\nitin>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (36344 KB)...
OKAY [ 1.170s]
writing 'bootloader_a'...
OKAY [ 0.379s]
finished. total time: 1.551s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target reported max download size of 536870912 bytes
sending 'radio_a' (60428 KB)...
OKAY [ 1.967s]
writing 'radio_a'...
OKAY [ 0.571s]
finished. total time: 2.540s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.226s
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.037s
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...W/ziparchive( 4084): Zip: unable to truncate file to 2030555488: File too large
error:
failed to extract 'system.img': I/O error
Press any key to exit...
Any clues? I tried running the command prompt as an Admin to no avail. I know I can flash all imgs manually (and it works without any problems) but why am I getting that error?
Edit:
This was occuring due to low space on C:\drive (it seems it extracts the system.img before sending it to phone). Thanks to @stevexyz0 for the solution!
Is the disk on your PC out of space? Looks like it's trying to unzip the image before sending it to the phone.
Sent from my Pixel 2 XL using Tapatalk
stevexyz0 said:
Is the disk on your PC out of space? Looks like it's trying to unzip the image before sending it to the phone.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Man, you are awesome! :laugh::laugh::highfive::highfive:
I had the factory images on D:\ drive which had 70GB free; but the C:\ drive had only 1 GB. And I think as you rightly said, it extracts the system.img on PC and that too on C:\ drive (may be in Temp older)
I made the space on C:\ drive and it worked like a charm. Thanks once again!
Nitin
A custom ROM sounds yummy!
nitin.chobhe said:
Hey guys, I've Pixel 2 XL and I'm trying to flash the factory images on the phone using flash-all.bat. I had 8.1 earlier and was doing some tests with custom ROM and then wanted to start afresh. So I did these steps:
1. downloaded the factory image [taimen-opm1.171019.011-factory-2df1c1cb] from here.
2. Extracted it in a folder
3. Downloaded latest platform tools from here and extracted it to same folder
4. Opened command prompt and ran flash-all.bat
5. It flashed radio, bootloader and then while flashing system.img, it gave this error:
extracting system.img (1936 MB) to disk...W/ziparchive( 4084): Zip: unable to truncate file to 2030555488: File too large
Here is the full log:
Code:
The system cannot find message text for message number 0x2350 in the message fil
e for Application.
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
Not enough storage is available to process this command.
D:\Pixel 2 XL\nitin>fastboot --version
fastboot version 0.0.1-4500957
Installed as D:\Pixel 2 XL\nitin\fastboot.exe
D:\Pixel 2 XL\nitin>fastboot devices
710KPJP0210052 fastboot
D:\Pixel 2 XL\nitin>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (36344 KB)...
OKAY [ 1.170s]
writing 'bootloader_a'...
OKAY [ 0.379s]
finished. total time: 1.551s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target reported max download size of 536870912 bytes
sending 'radio_a' (60428 KB)...
OKAY [ 1.967s]
writing 'radio_a'...
OKAY [ 0.571s]
finished. total time: 2.540s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.226s
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.037s
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...W/ziparchive( 4084): Zip: unable to truncate file to 2030555488: File too large
error:
failed to extract 'system.img': I/O error
Press any key to exit...
Any clues? I tried running the command prompt as an Admin to no avail. I know I can flash all imgs manually (and it works without any problems) but why am I getting that error?
Edit:
This was occuring due to low space on C:\drive (it seems it extracts the system.img before sending it to phone). Thanks to @stevexyz0 for the solution!
Click to expand...
Click to collapse
I'm getting this error if U try with manual command,
{ H:\taimen-pq1a.181105.017.a1\platform-tools> fastboot update H:\taimen-pq1a.181105.017.a1\platform-tools\image-taimen
-pq1a.181105.017.a1.zip
error: failed to load 'H:\taimen-pq1a.181105.017.a1\platform-tools\image-taimen-pq1a.181105.017.a1.zip': Not enough space }
I'm getting this error if U try with flash-all command,
target reported max download size of 536870912 bytes
sending 'bootloader' (36336 KB)...
OKAY [ 0.789s]
writing 'bootloader'...
OKAY [ 0.375s]
finished. total time: 1.164s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 536870912 bytes
sending 'radio' (60388 KB)...
OKAY [ 1.304s]
writing 'radio'...
OKAY [ 0.569s]
finished. total time: 1.878s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
error: failed to load 'image-taimen-pq1a.181105.017.a1.zip': Not enough space
Press any key to exit...
My drives are enough empty to perform this action as you can see below screen shot. I've kept these files in drive H:/
Please help here. @stevexyz0
I'm rooted from oct patch, and want to update to nov patch full OTA.
wow thank you
stevexyz0 said:
Is the disk on your PC out of space? Looks like it's trying to unzip the image before sending it to the phone.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
sheesh i tried flashing the new android 10 update and got the same error error above and man you saved me!!! omg thank you. spent hrs trying to see whats wrong and came across this post. i couldnt even get passed the google logo thought i bricked my pixel 3 xl!! thank you!!
nitin.chobhe said:
Man, you are awesome! :laugh::laugh::highfive::highfive:
I had the factory images on D:\ drive which had 70GB free; but the C:\ drive had only 1 GB. And I think as you rightly said, it extracts the system.img on PC and that too on C:\ drive (may be in Temp older)
I made the space on C:\ drive and it worked like a charm. Thanks once again!
Nitin
Click to expand...
Click to collapse
hi ...i am getting this error while flashing ruu through my pc.....
sending 'zip'... (2426128 KB) FAILdata too large, 2484355788 > 1973424128
FAILED (data size is too large(2426128 KB) for device to download ZIP file 'rom.zip'
)
please helpppppppppppppp
Execution time is 2(s)
Novair said:
hi ...i am getting this error while flashing ruu through my pc.....
sending 'zip'... (2426128 KB) FAILdata too large, 2484355788 > 1973424128
FAILED (data size is too large(2426128 KB) for device to download ZIP file 'rom.zip'
)
please helpppppppppppppp
Execution time is 2(s)
Click to expand...
Click to collapse
Other than making sure you have enough space on your PC drives, we can't really help you. You'll need to ask your question in the HTC forums. Google devices don't use RUUs.
Novair said:
hi ...i am getting this error while flashing ruu through my pc.....
sending 'zip'... (2426128 KB) FAILdata too large, 2484355788 > 1973424128
FAILED (data size is too large(2426128 KB) for device to download ZIP file 'rom.zip'
)
please helpppppppppppppp
Execution time is 2(s)
Click to expand...
Click to collapse
A simple google search showed this as fist result: https://forum.xda-developers.com/t/q-cannot-flash-failed-remote-download-size-too-large.1286751/
Strephon Alkhalikoi said:
Other than making sure you have enough space on your PC drives, we can't really help you. You'll need to ask your question in the HTC forums. Google devices don't use RUUs.
Click to expand...
Click to collapse
I have 500gb free space on pc .......
But i think this error is because of allocated partition in device [(htv 10) htv32]
If I was paranoid my pixel has a undetectable virus/rootkit how could I get ride of it?
Is there away to flash both room locations to factory reset and lock bootloader?
Sent from my Pixel 2 XL using Tapatalk
https://developers.google.com/android/images#flashable-images
Well I knew there is dual partitions and curious if those images will take care of both sides how much can I rely on that? Seeing they are factory should be pretty high.
Sent from my Pixel 2 XL using Tapatalk
gjkrisa said:
Well I knew there is dual partitions and curious if those images will take care of both sides how much can I rely on that? Seeing they are factory should be pretty high.
Click to expand...
Click to collapse
Flash it once, run the fastboot command to switch active slots and flash it again. If you are that worried, you most certainly should let it flash the user partition. Anything bad is most certainly going to be there.
Locking the bootloader is going to flash that too right?
gjkrisa said:
Locking the bootloader is going to flash that too right?
Click to expand...
Click to collapse
Not on it's own. NEVER RE-LOCK THE BOOTLOADER UNLESS YOU ARE 101% SURE YOU ARE BACK TO STOCK. I think there is an older thread here where someone did that and that device is now bricked permanently.
raynan said:
Not on it's own. NEVER RE-LOCK THE BOOTLOADER UNLESS YOU ARE 101% SURE YOU ARE BACK TO STOCK. I think there is an older thread here where someone did that and that device is now bricked permanently.
Click to expand...
Click to collapse
I am the one ...Yes, never relock bootloader because you don't need to
ram4ufriends said:
I am the one ...Yes, never relock bootloader because you don't need to
Click to expand...
Click to collapse
Haha, well, sorry to bring up those painful memories, but at least you'll never do it again...Live and learn.
raynan said:
Haha, well, sorry to bring up those painful memories, but at least you'll never do it again...Live and learn.
Click to expand...
Click to collapse
Yeah lessons learnt...good thing is I did RMA to Google and got a replacement...
gjkrisa said:
Well I knew there is dual partitions and curious if those images will take care of both sides how much can I rely on that? Seeing they are factory should be pretty high.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
It is not necessary to switch the active slot as someone else here suggested. The flash script included with the factory image flashes both slots.
TheSt33v said:
It is not necessary to switch the active slot as someone else here suggested. The flash script included with the factory image flashes both slots.
Click to expand...
Click to collapse
I think I just read in the carbon thread that is not the case, only part of the install goes to both slots. ??
TheSt33v said:
It is not necessary to switch the active slot as someone else here suggested. The flash script included with the factory image flashes both slots.
Click to expand...
Click to collapse
I don't think this is the case either. Afaik partitions such as system will only flash to the active slot (i.e. I've seen the script say something like "writing system_a"). When I manually switch slots, it will say "writing system_b" - this is what leads me to believe it doesn't flash to both slots.
I have a bit of OCD so I manually switch slots and flash-all to both. It's also to be on the safe side, avoiding any potential issues by having one slot have older factory images.
ram4ufriends said:
Yeah lessons learnt...good thing is I did RMA to Google and got a replacement...
Click to expand...
Click to collapse
Do you have a thread that leads to how you bricked yours or willing to share here?
I really want to relock the bootloader but I don't want to need to send spend $ on a rma
Sent from my Pixel 2 XL using Tapatalk
rickysidhu_ said:
I don't think this is the case either. Afaik partitions such as system will only flash to the active slot (i.e. I've seen the script say something like "writing system_a"). When I manually switch slots, it will say "writing system_b" - this is what leads me to believe it doesn't flash to both slots.
I have a bit of OCD so I manually switch slots and flash-all to both. It's also to be on the safe side, avoiding any potential issues by having one slot have older factory images.
Click to expand...
Click to collapse
I stand corrected. This is what happens when you flash a factory image:
target reported max download size of 536870912 bytes
sending 'bootloader_a' (36344 KB)...
OKAY [ 0.807s]
writing 'bootloader_a'...
OKAY [ 0.371s]
finished. total time: 1.181s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'radio_a' (60428 KB)...
OKAY [ 1.344s]
writing 'radio_a'...
OKAY [ 0.578s]
finished. total time: 1.924s
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.144s
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.020s
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 7.975s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 2.816s
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 1.626s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
--------------------------------------------
Bootloader Version...: TMZ12b
Baseband Version.....: g8998-00164-1710262031
Serial Number........: 710KPXV0398618
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot_a' (40960 KB)...
OKAY [ 0.909s]
writing 'boot_a'...
OKAY [ 0.374s]
sending 'dtbo_a' (8192 KB)...
OKAY [ 0.182s]
writing 'dtbo_a'...
OKAY [ 0.076s]
erasing 'system_a'...
OKAY [ 0.072s]
sending sparse 'system_a' 1/4 (524284 KB)...
OKAY [ 12.120s]
writing 'system_a' 1/4...
OKAY [ 2.454s]
sending sparse 'system_a' 2/4 (524284 KB)...
OKAY [ 12.086s]
writing 'system_a' 2/4...
OKAY [ 2.423s]
sending sparse 'system_a' 3/4 (524284 KB)...
OKAY [ 12.027s]
writing 'system_a' 3/4...
OKAY [ 2.422s]
sending sparse 'system_a' 4/4 (410176 KB)...
OKAY [ 9.397s]
writing 'system_a' 4/4...
OKAY [ 1.894s]
erasing 'system_b'...
OKAY [ 0.051s]
sending sparse 'system_b' 1/2 (524284 KB)...
OKAY [ 12.007s]
writing 'system_b' 1/2...
OKAY [ 2.452s]
sending sparse 'system_b' 2/2 (57588 KB)...
OKAY [ 1.322s]
writing 'system_b' 2/2...
OKAY [ 0.257s]
sending 'vbmeta_a' (4 KB)...
OKAY [ 0.001s]
writing 'vbmeta_a'...
OKAY [ 0.003s]
erasing 'vendor_a'...
OKAY [ 0.014s]
sending 'vendor_a' (357912 KB)...
OKAY [ 7.952s]
writing 'vendor_a'...
OKAY [ 1.818s]
Setting current slot to 'a'...
OKAY [ 0.008s]
rebooting...
finished. total time: 82.364s
Press any key to exit...
So it looks like the only time it touches the inactive slot is when it flashes system, in which case it flashes something different to the inactive system partition. Weird.
gjkrisa said:
Do you have a thread that leads to how you bricked yours or willing to share here?
I really want to relock the bootloader but I don't want to need to send spend $ on a rma
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-2-xl/help/brick-device-t3720735
Ok so go to stock before locking bootloader check
Sent from my Pixel 2 XL using Tapatalk
gjkrisa said:
Ok so go to stock before locking bootloader check
Click to expand...
Click to collapse
And wait for one OTA to work.
I'm on mac so i ran flash-all.sh but ran into issue anyone have an idea?
Downloads/pixel/flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader_a' (36344 KB)...
OKAY [ 0.944s]
writing 'bootloader_a'...
OKAY [ 0.507s]
finished. total time: 1.451s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 536870912 bytes
sending 'radio_a' (60428 KB)...
OKAY [ 1.596s]
writing 'radio_a'...
OKAY [ 2.108s]
finished. total time: 3.704s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.213s
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.031s
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 11.488s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 3.995s
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 2.308s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
/usr/local/bin/mke2fs failed with status 1
error: Cannot generate image for userdata
Click to expand...
Click to collapse
gjkrisa said:
I'm on mac so i ran flash-all.sh but ran into issue anyone have an idea?
Click to expand...
Click to collapse
I got the same error and could not find a way around it. I ended up downloading the Skipsoft toolkit and flashing factory images from there, in Windows.
rickysidhu_ said:
I got the same error and could not find a way around it. I ended up downloading the Skipsoft toolkit and flashing factory images from there, in Windows.
Click to expand...
Click to collapse
Did you have to remove password on phone first?
Sent from my Pixel 2 XL using Tapatalk
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.