HELP Can't flash system.img - Nexus 5X Q&A, Help & Troubleshooting

Hey
when i want to flash the factory image from google with the "flash-all.bat" i got this Error.
failed to allocate 2008772888 bytes
error: update package missing system.img
i tried to flash manualy dosent work too.
J:\fastboot\bullhead-mmb29p>fastboot flash system system.img
load_file: could not allocate 2008772888 bytes
error: cannot load 'system.img'
this comes when i run the "flash-all.bat"
sending 'bootloader' (4382 KB)...
OKAY [ 0.213s]
writing 'bootloader'...
OKAY [ 0.137s]
finished. total time: 0.352s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.012s
sending 'radio' (56614 KB)...
OKAY [ 1.807s]
writing 'radio'...
OKAY [ 0.506s]
finished. total time: 2.315s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 2008772888 bytes
error: update package missing system.img
Press any key to exit...
please help me:crying:

use newest fastboot. Had the same failure on Nexus 9 - flounder.

Donald Nice said:
use newest fastboot. Had the same failure on Nexus 9 - flounder.
Click to expand...
Click to collapse
many many thanks :good:
you safed the life from my 5x ♥

Donald Nice said:
use newest fastboot. Had the same failure on Nexus 9 - flounder.
Click to expand...
Click to collapse
Hello, sorry for my English, i've download the Minimal fastboot and adb file and i've installated it. but it styll doesn't work, when i try to type te command: fastboot flash system system.img, the result is error: cannot load system.img. what can i try to do?

Download and install SDK Manager. Later, install SDK tools, SDK Platform Tools, Android support library and Google USB driver. Then try again.

Related

[Q] Factory image failed? Bootloader success..

Was running latest slimkat for flo (2013) no problem.
Looking to start running with the Lollipop kids; figured a full wipe and start over would be great..
So far not much luck.
I couldn't get fastboot to recognize my device on linux (archlinux..)
Win 7 saw it just fine..
C:\Users\TempUser\Downloads\razor-lrx22c-factory-a9c6e55f>flash-all.bat
sending 'bootloader' (3911 KB)...
OKAY [ 0.140s]
writing 'bootloader'...
OKAY [ 1.643s]
finished. total time: 1.783s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 818480772 bytes
error: update package missing system.img
Press any key to exit...
adb version says 1.0.32 - can not find a way to get fastboot version..
Still have access to twrp 2.8.0.1, device still shows as unlocked, and it looks like slimkat still boots..
Should I just forego the system image?
Thanks in advance..
Just to share..
I've moved on from this..
Downloaded latest twrp (2.8.0.x) pushed that via fastboot.
Went into recovery, confirmed version.. attempted a quick adb push and adb sideload; sideload worked for small - failed for the 180MB Rom..
wiped device; rebooted recovery; adb push'd to /sdcard/, and installed from there.
Enjoying 5.0.2 with tons of space..
Thank you for reading.
Mystique said:
Was running latest slimkat for flo (2013) no problem.
Looking to start running with the Lollipop kids; figured a full wipe and start over would be great..
So far not much luck.
I couldn't get fastboot to recognize my device on linux (archlinux..)
Win 7 saw it just fine..
C:\Users\TempUser\Downloads\razor-lrx22c-factory-a9c6e55f>flash-all.bat
sending 'bootloader' (3911 KB)...
OKAY [ 0.140s]
writing 'bootloader'...
OKAY [ 1.643s]
finished. total time: 1.783s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 818480772 bytes
error: update package missing system.img
Press any key to exit...
adb version says 1.0.32 - can not find a way to get fastboot version..
Still have access to twrp 2.8.0.1, device still shows as unlocked, and it looks like slimkat still boots..
Should I just forego the system image?
Thanks in advance..
Click to expand...
Click to collapse
In case you run into the error again, a simple Google for this know problem: http://www.androidpolice.com/2014/1...-0-factory-images-heres-how-to-get-around-it/
Sent from my Nexus 5 using XDA Free mobile app

Flashing stock 5.0.2, boot.img "missing"

I'm trying to flash the stock ROM for 5.0.2, and when I try to run the flash-all script, I get an error saying that boot.img is missing. I looked into the zip file where the bat file is looking, and there is definitely a boot.img there. I just updated platform-tools through the SDK manager a few hours ago, so I'm using the newest version.
Full output from flash-all:
Code:
sending 'bootloader' (3911 KB)...
OKAY [ 0.132s]
writing 'bootloader'...
OKAY [ 1.553s]
finished. total time: 1.685s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.009s
error: update package missing boot.img
Press any key to exit...
Flash the files manually?
nhizzat said:
Flash the files manually?
Click to expand...
Click to collapse
Sorry for abandoning this thread. I flashed the boot and system images manually and it seemed to work. Thanks!

Cannot install stock rom: FAILED (remote: data too large)

I tried installing Cyanogenmod on a Nexus 5X, and it didn't work, so now I'm trying to install the stock rom from this site: https://developers.google.com/android/images#bullhead.
I'm doing this on Ubuntu 15.10. When I run the flash-all.sh script (on any of them), I get this output:
target reported max download size of 536870912 bytes
sending 'bootloader' (4382 KB)...
OKAY [ 0.195s]
writing 'bootloader'...
OKAY [ 0.077s]
finished. total time: 0.272s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.008s
target reported max download size of 536870912 bytes
sending 'radio' (56614 KB)...
OKAY [ 1.715s]
writing 'radio'...
OKAY [ 0.338s]
finished. total time: 2.052s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: BHZ10i
Baseband Version.....: M8994F-2.6.22.0.56
Serial Number........: 00a9164559592811
--------------------------------------------
checking product...
OKAY [ 0.020s]
checking version-bootloader...
OKAY [ 0.020s]
checking version-baseband...
OKAY [ 0.020s]
sending 'boot' (11469 KB)...
OKAY [ 0.406s]
writing 'boot'...
OKAY [ 0.073s]
sending 'recovery' (12521 KB)...
OKAY [ 0.393s]
writing 'recovery'...
OKAY [ 0.092s]
erasing 'system'...
OKAY [ 0.089s]
sending 'system' (1950236 KB)...
FAILED (remote: data too large)
finished. total time: 1.210s
I'm not seeing many resources online about this error. The only thing I've seen is to update fastboot, but I've already got the latest installed with this ppa: http://askubuntu.com/questions/34702/how-do-i-set-up-android-adb
Is there anything that I can do to get it working correctly?
adanedhel728 said:
I tried installing Cyanogenmod on a Nexus 5X, and it didn't work, so now I'm trying to install the stock rom from this site: https://developers.google.com/android/images#bullhead.
I'm doing this on Ubuntu 15.10. When I run the flash-all.sh script (on any of them), I get this output:
target reported max download size of 536870912 bytes
sending 'bootloader' (4382 KB)...
OKAY [ 0.195s]
writing 'bootloader'...
OKAY [ 0.077s]
finished. total time: 0.272s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.008s
target reported max download size of 536870912 bytes
sending 'radio' (56614 KB)...
OKAY [ 1.715s]
writing 'radio'...
OKAY [ 0.338s]
finished. total time: 2.052s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: BHZ10i
Baseband Version.....: M8994F-2.6.22.0.56
Serial Number........: 00a9164559592811
--------------------------------------------
checking product...
OKAY [ 0.020s]
checking version-bootloader...
OKAY [ 0.020s]
checking version-baseband...
OKAY [ 0.020s]
sending 'boot' (11469 KB)...
OKAY [ 0.406s]
writing 'boot'...
OKAY [ 0.073s]
sending 'recovery' (12521 KB)...
OKAY [ 0.393s]
writing 'recovery'...
OKAY [ 0.092s]
erasing 'system'...
OKAY [ 0.089s]
sending 'system' (1950236 KB)...
FAILED (remote: data too large)
finished. total time: 1.210s
I'm not seeing many resources online about this error. The only thing I've seen is to update fastboot, but I've already got the latest installed with this ppa: http://askubuntu.com/questions/34702/how-do-i-set-up-android-adb
Is there anything that I can do to get it working correctly?
Click to expand...
Click to collapse
the system image always is too large and usually it gets transferred in smaller pieces automatically. I'd try to flash all the images manually on a Windows mashine, following this guide (section 10).
I did it many times this way without issues.
ulxerker said:
the system image always is too large and usually it gets transferred in smaller pieces automatically. I'd try to flash all the images manually on a Windows mashine, following this guide (section 10).
I did it many times this way without issues.
Click to expand...
Click to collapse
Well, I can't get it working on Windows at all, because the driver won't install. (At least I assume that's the reason why-- The driver won't install and fastboot won't show any devices.)
I tried fixing that, but with no luck.
I did also try section 10 from Ubuntu, with the same results for the system part:
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.284s]
sending sparse 'system' (514493 KB)...
OKAY [ 12.333s]
writing 'system'...
OKAY [ 3.149s]
sending sparse 'system' (514543 KB)...
OKAY [ 12.427s]
writing 'system'...
OKAY [ 3.117s]
sending sparse 'system' (524291 KB)...
FAILED (remote: data too large)
finished. total time: 31.327s
Fastboot is too old. Remove it from system. apt remove android-tools-fastboot . Place fastboot from dl link into a folder where is your system img. Change permissions if needed and exexute it with ./fastboot
https://mega.nz/#!CYYjHYSK!yjhPZ-OYQNhFxq-0JXVibtUps7AwoFDtvk0yPu_194s
Even better is to place fastboot file into a system /bin folder from where you can execute command in any folder.
Best regards.
icrunchbanger said:
Fastboot is too old. Remove it from system. apt remove android-tools-fastboot . Place fastboot from dl link into a folder where is your system img. Change permissions if needed and exexute it with ./fastboot
https://mega.nz/#!CYYjHYSK!yjhPZ-OYQNhFxq-0JXVibtUps7AwoFDtvk0yPu_194s
Even better is to place fastboot file into a system /bin folder from where you can execute command in any folder.
Best regards.
Click to expand...
Click to collapse
My gosh, that finally worked, and I didn't believe it would. I had thought that the one I had gotten from that PPA was the newest, but, apparently not. I actually got it directly from Google (which was a chore in itself, but outside the scope of this thread).
Thank you very much. Now, let's see if I can find out how to mark this as solved...
adanedhel728 said:
My gosh, that finally worked, and I didn't believe it would. I had thought that the one I had gotten from that PPA was the newest, but, apparently not. I actually got it directly from Google (which was a chore in itself, but outside the scope of this thread).
Thank you very much. Now, let's see if I can find out how to mark this as solved...
Click to expand...
Click to collapse
Your welcome. Never trust PPA ?
I got issuse
icrunchbanger said:
Fastboot is too old. Remove it from system. apt remove android-tools-fastboot . Place fastboot from dl link into a folder where is your system img. Change permissions if needed and exexute it with ./fastboot
https://mega.nz/#!CYYjHYSK!yjhPZ-OYQNhFxq-0JXVibtUps7AwoFDtvk0yPu_194s
Even better is to place fastboot file into a system /bin folder from where you can execute command in any folder.
Best regards.
Click to expand...
Click to collapse
Bro link doesnt work, can you sent me app via email: [email protected]
suleymanov5 said:
Bro link doesnt work, can you sent me app via email: [email protected]
Click to expand...
Click to collapse
You can download android tools from Google
https://dl.google.com/android/repository/platform-tools-latest-linux.zip
Also you can check my github for some nifty scripts .
https://github.com/icrunchbanger/android

[Solved] Error while flashing factory images - Zip: unable to truncate file

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]

Stuck in the Fastboot/ Recovery

I was trying to root and install a custom rom. When I installed the rom and reboot the device it said no OS installed. I have been trying to send the taimen-opm1.171019.018-factory-e96a86ae.zip file over I realized I have never done that and don't know if there is a fastboot command for push. Any help will be very nice. thanks
matthew.bridell said:
I was trying to root and install a custom rom. When I installed the rom and reboot the device it said no OS installed. I have been trying to send the taimen-opm1.171019.018-factory-e96a86ae.zip file over I realized I have never done that and don't know if there is a fastboot command for push. Any help will be very nice. thanks
Click to expand...
Click to collapse
You don't send it to the phone but instead you unzip it in a folder with your adb/fastboot files and flash it.
CyberpodS2 said:
You don't send it to the phone but instead you unzip it in a folder with your adb/fastboot files and flash it.
Click to expand...
Click to collapse
flash the zip? Would I just use fastboot flash image-taimen-opm1.171019.018.zip ?
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
CyberpodS2 said:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Click to expand...
Click to collapse
when I do that I get
C:\Users\matth\Downloads\fastboot>flash-all
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 0.003s
< waiting for device >
And the phone phone goes into bootloop with twrp recovery poping up with errors.
I was able to install Lineage-15.1-20180219 and boot into it. Tried to restore from that point and it now when I run flash-all it now says
C:\Users\matth\Downloads\fastboot>flash-all
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.006s
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.003s
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
error: cannot load system.img from flash
Press any key to exit...
matthew.bridell said:
when I do that I get
C:\Users\matth\Downloads\fastboot>flash-all
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 0.003s
< waiting for device >
And the phone phone goes into bootloop with twrp recovery poping up with errors.
Click to expand...
Click to collapse
You need to update your platform-tools.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
just tried the zip and no luck
C:\Users\matth\Downloads>cd "platform-tools-latest-windows (2)"
C:\Users\matth\Downloads\platform-tools-latest-windows (2)>cd platform-tools
C:\Users\matth\Downloads\platform-tools-latest-windows (2)\platform-tools>flash-all
target didn't report max-download-size
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.005s
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.221s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
I do now have default Recover but don't know why it won't work.
I feel dumb. I got it to work with using a usb-a to usb-c cord. was trying to use the usb-c to usb-c cord thanks for all the help.

Categories

Resources