Hi there, I'm presently attempting to unroot my Pixel C tablet but have encountered several issues with it. Any assistance would be greatly appreciated:
The issues encountered are that despite the initial success of it, it prompts the error:
target reported max download size of 268435456 bytes
sending 'bootloader' (16384 KB)...
OKAY [ 0.517s]
writing 'bootloader'...
(bootloader) writing flash
OKAY [ 88.301s]
finished. total time: 88.820s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.004s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate -1855313260 bytes
error: update package missing system.img
Press any key to exit...
I've also attempted to manually boot the failed files like 'boot.img' and etc. but it shows the following erorr
'The disc image file is corrupted' regardless of the file: cache.img, boot.img, recovery.img, system.img
Any help that you can provide is greatly appreciated as I'm in heavy need of assistance.
P.S: Please ignore the ****ty post quality. I'm not overly familiar with the format and layout of this forum
Are you using Nexus Rootkit?
You already upgraded to N?
What do you use to flash (source)?
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!
How is everyone else flashing the system images? On the Nexus 6 and Nexus 6p I would just fastboot flash the system, vendor, and boot images, but with the Pixel there are tons of different images so I don't want to manually flash and muff something up.. So I've been trying to run the flash-all.bat and It just keeps giving me errors
C:\android>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32820 KB)...
OKAY [ 0.753s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
OKAY [ 1.017s]
finished. total time: 1.770s
rebooting into bootloader...
FAILED (command write failed (No error))
finished. total time: -0.000s
target reported max download size of 536870912 bytes
sending 'radio_a' (57048 KB)...
OKAY [ 1.303s]
writing 'radio_a'...
OKAY [ 0.863s]
finished. total time: 2.166s
rebooting into bootloader...
OKAY [ 0.053s]
finished. total time: 0.069s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
and it just stalls there.....
I've updated everything... drivers, sdk, fastboot and whatnot..
My phone is fine, I just have elementalx and root and I want to revert to stock so I can use android pay and receive updates.
I bought my phone from Google Store and I'm trying to flash the V image if that makes a difference.
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]
I meet with problem of flashing. but flash failed.
here is the contain. Android 8.1
target reported max download size of 536870912 bytes
sending 'bootloader' (36344 KB)...
OKAY [ 1.113s]
writing 'bootloader'...
OKAY [ 0.357s]
finished. total time: 1.470s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.818s]
writing 'radio'...
OKAY [ 0.580s]
finished. total time: 2.398s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate 2030555488 bytes
error: update package missing system.img
Press any key to exit...
after I open the zip file, there is no recovery.img, boot.sig inside.
failed to allocate 2030555488 bytes
Click to expand...
Click to collapse
I had the same problem with my old Windows desktop which has only 4GB of RAM.
Used my notebook with 8 GB of RAM and it worked
i am facing the same issue
---------- Post added at 03:30 PM ---------- Previous post was at 02:53 PM ----------
check this it seems as normal worked for mw too but had a wait a lot
https://www.reddit.com/r/GooglePixel/comments/5zh8a6/archive_does_not_contain_systemsig/
Don't use this Q/A form, it is a pain in the a$$ and hard to follow. Next time just start a regular thread.
Those two errors are normal but what is not normal is that system was not found. Either you unzipped the 2nd nested zip file in the image (supposed to be left alone) or you are using outdated adb/fastboot binaries. They were updated for Pixel, so older ones won't work.
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 !