Related
Hello guys,
Frank is writing. Sorry for disturbing, but i´m in big trouble right now. I made a Factory reset, wipe Dalvik etc. and flashed the PA Aosp Mako 4.0 + latest Gapps.. Nothing special so far, but now my Nexus is still in a bootloop. If i go to the recovery mode, i have no access to TWRP just have the possibility to choose between Start, Start bootloader, Power off, or Recovery Mode. But if i go to the recovery mode the bugdroid is there and nothing happens further. After connecting the device to my mac there is a message on the screen that it´s in download mode?! i didn´t seen this before.. So if you have any solution, it would be great. a factory reset to if possible or even necessary.
Right now I am at my wits end. May someone has an advice for me what to do? i can´t imagine christmas without my beloved smartphone.. ;(
Thanks for your attention!
cheers
Frank
You need fastboot working on your computer, not sure of the exact steps for a mac, but if you download the Android SDK it will be in there. Then you can directly flash a factory image for your phone from the fastboot screen. (The one you describe with start, start bootloader, etc)
You can download the factory images here https://developers.google.com/android/nexus/images#occam
Android sdk for mac http://dl.google.com/android/android-sdk_r22.3-macosx.zip
hey.. thank you for your reply. i downloaded the required files but how to get the access with terminal when it´s still not possible to start the phone? If i type in ./adb devices in terminal just following popped up but nothimg else:
-bash: /Users/frankherrmann/Desktop/adt-bundle-mac-x86_64-20131030: is a directory
do u know what to do now?
At the dead android screen, hold the power button and press vol+. Does it get you to stock recovery?
unfortunately nothing happens the screen turns off, that´s all... ;(
You should try flashing a stock 4.4.2 occam image using fastboot. This would return you to stock and you can then root and install TWRP or CWM.
endxpen tyrants
ok, thanks...meanwhile i did a factory reset with in the recovery mode, but after reboot the same thing happens, still bootloop.. now i just downloaded the adt bundle with sdk inside and the latest factory image. but anyway, it seems that i can´t get the access to the phone. if i go in the adt folder and use the command adb services in the terminal my device will not be recognized.
Frank-iMac:adt-bundle-mac frankherrmann$ ./adb devices
List of devices attached
Frank-iMac:adt-bundle-mac frankherrmann$
Do i type in something wrong? maybe it´s just a thinking error by myself
thanks againfor your help!
FrankHPunkt said:
ok, thanks...meanwhile i did a factory reset with in the recovery mode, but after reboot the same thing happens, still bootloop.. now i just downloaded the adt bundle with sdk inside and the latest factory image and put it in the same folder that i named as adroid tools. i got the access to the folder and after type in the command ./fastboot devices my devices has been recognized and the number too. but if i try to flash the stock image it will not work. i typed in ./fastboot flash and the image name but the failure message -bash: ./flash: No such file or directory
so... i suggest that it´s been just a problem that i typed not the correct command, isn´it?
Franks-MacBook-Pro:Android Tools leherman$ ./fastboot flash /Users/leherman/Desktop/android\ tools/image-occam-kot49h.zip
unknown partition '/Users/leherman/Desktop/android tools/image-occam-kot49h.zip'
error: cannot determine image filename for '/Users/leherman/Desktop/android tools/image-occam-kot49h.zip'
Franks-MacBook-Pro:Android Tools leherman$
Click to expand...
Click to collapse
Sorry, I can't help you with flashing on Mac. Do you have access to a PC?
FrankHPunkt said:
FrankHPunkt said:
ok, thanks...meanwhile i did a factory reset with in the recovery mode, but after reboot the same thing happens, still bootloop.. now i just downloaded the adt bundle with sdk inside and the latest factory image and put it in the same folder that i named as adroid tools. i got the access to the folder and after type in the command ./fastboot devices my devices has been recognized and the number too. but if i try to flash the stock image it will not work. i typed in ./fastboot flash and the image name but the failure message -bash: ./flash: No such file or directory
so... i suggest that it´s been just a problem that i typed not the correct command, isn´it?
Click to expand...
Click to collapse
Yes you got 2 options,run the flash-all script or flash the files manually for example typing fastboot flash recovery recovery.img or fastboot flash radio radio.img, you didn't specified the partition to flash
Click to expand...
Click to collapse
Hey Frederico,
thanks for your reply i did it as you told me and typed this in terminal : as you can see something should work, but it was not possible to flash the image.
Franks-MacBook-Pro:android tools leherman$ ./fastboot flash radio-mako-m9615a-cefwmazm-2.0.1700.98.img radio-mako-m9615a-cefwmazm-2.0.1700.98.img
sending 'radio-mako-m9615a-cefwmazm-2.0.1700.98.img' (45537 KB)...
OKAY [ 1.715s]
writing 'radio-mako-m9615a-cefwmazm-2.0.1700.98.img'...
FAILED (remote: partition table doesn't exist)
finished. total time: 1.718s
Franks-MacBook-Pro:android tools leherman$ ./fastboot flash image-occam-kot49h.zip image-occam-kot49h.zip
sending 'image-occam-kot49h.zip' (429746 KB)...
OKAY [ 15.845s]
writing 'image-occam-kot49h.zip'...
FAILED (remote: partition table doesn't exist)
finished. total time: 15.848s
do u have an idea whats still not right. Seems to be on the right way!
thank you very much so far!
Federico_96 said:
FrankHPunkt said:
Yes you got 2 options,run the flash-all script or flash the files manually for example typing fastboot flash recovery recovery.img or fastboot flash radio radio.img, you didn't specified the partition to flash
Click to expand...
Click to collapse
Click to expand...
Click to collapse
FrankHPunkt said:
Hey Frederico,
thanks for your reply i did it as you told me and typed this in terminal : as you can see something should work, but it was not possible to flash the image.
Franks-MacBook-Pro:android tools leherman$ ./fastboot flash radio-mako-m9615a-cefwmazm-2.0.1700.98.img radio-mako-m9615a-cefwmazm-2.0.1700.98.img
sending 'radio-mako-m9615a-cefwmazm-2.0.1700.98.img' (45537 KB)...
OKAY [ 1.715s]
writing 'radio-mako-m9615a-cefwmazm-2.0.1700.98.img'...
FAILED (remote: partition table doesn't exist)
finished. total time: 1.718s
Franks-MacBook-Pro:android tools leherman$ ./fastboot flash image-occam-kot49h.zip image-occam-kot49h.zip
sending 'image-occam-kot49h.zip' (429746 KB)...
OKAY [ 15.845s]
writing 'image-occam-kot49h.zip'...
FAILED (remote: partition table doesn't exist)
finished. total time: 15.848s
do u have an idea whats still not right. Seems to be on the right way!
thank you very much so far!
Click to expand...
Click to collapse
The right command is ./fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.98.img, so it is ./fastboot flash <generic name of partition> <exact name of the file> hope this will work, but my suggestion is to run the flash-all script,it will do it authomatically for you, if you want do it manually,here at step D there are all the commands
Thanks a lot, you made may day! the phone is rebooting....
merry christmas!
cheers
Frank
Nexus 7 (grouper) doesn't boot - Bootloader says "FAILED (remote: (FileWriteFailed))"
Hi,
My Nexus 7 (grouper) won't boot Android anymore. It automatically boots into the bootloader and when I select 'Start' or 'Recovery Mode' it just says "Booting failed".
When I try to flash a new recovery Image over fastboot I get the following Output:
[[email protected] Downloads]$ sudo fastboot flash recovery twrp-2.8.7.0-grouper.img
sending 'recovery' (11850 KB)...
OKAY [ 1.409s]
writing 'recovery'...
FAILED (remote: (FileWriteFailed))
finished. total time: 1.441s
Click to expand...
Click to collapse
It's the same, when I try to flash anything else. So I have no chance to flash a Stock-Image. I also get the same error when I try to format a partition. I'm pretty much out of ideas now. Can anybdoy help me?
yeah this same thing kept happening to me (I have no idea why) Once you get into the bootloader make sure your device shows up IE fastboot devices, then flash bootloader, then fastboot reboot-bootloader then between each succeding flash use the volume buttons to select reboot bootloader on the device. I had to flash individual partitions it would'nt do a -w update, so flash system, then reboot bootloader on device, then flash, then reboot bootloader, ect
Also booting into Android takes a bit so be patient, like 10/15 min. Maybe there's an easier way but after screwng around with it for an hour this is the only way I could get 5.1.1 on it.
productofusa said:
yeah this same thing kept happening to me (I have no idea why) Once you get into the bootloader make sure your device shows up IE fastboot devices, then flash bootloader, then fastboot reboot-bootloader then between each succeding flash use the volume buttons to select reboot bootloader on the device. I had to flash individual partitions it would'nt do a -w update, so flash system, then reboot bootloader on device, then flash, then reboot bootloader, ect
Also booting into Android takes a bit so be patient, like 10/15 min. Maybe there's an easier way but after screwng around with it for an hour this is the only way I could get 5.1.1 on it.
Click to expand...
Click to collapse
When I try to flash the bootloader I get:
[[email protected] Downloads]$ sudo fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.263s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.403s
Click to expand...
Click to collapse
And when flashing other partitions it says "FAILED (remote: (FileWriteFailed))".
Something seems to be really screwed up with my storage. Is there a way to repartition the device from fastboot? Maybe that would be help.
I'm willing to try out everything, by now.
Is it possible the files your trying to flash are somehow corrupt? try downloading again. My problem was fastboot kept crashing, not really sure what you got going on.
I will say that i've just finished flashing nexus 6,7,7, and 9 and for some reason the nexus 7 (2012) was a real pain in the butt, didn't have issues with any of the others.
Maybe someone else with another idea will chime in, good luck!
productofusa said:
Is it possible the files your trying to flash are somehow corrupt? try downloading again. My problem was fastboot kept crashing, not really sure what you got going on.
I will say that i've just finished flashing nexus 6,7,7, and 9 and for some reason the nexus 7 (2012) was a real pain in the butt, didn't have issues with any of the others.
Maybe someone else with another idea will chime in, good luck!
Click to expand...
Click to collapse
I already downloaded them multiple times. And even if they are corrupt, formatting the partitions should still work. I'm guessing on corrupt storage now, as I can't find any other explanation. Maybe I can find a cheap Motherboard somewhere on the internet. Thanks, anyways
Hi,
I am currently flashing my Nexus 6P with OS 7.1.1
After executing flash-all.bat as suggested on Android factory images i get the below error:
"sending 'bootloader' (3532 KB)...
OKAY [ 0.103s]
writing 'bootloader'...
OKAY [ 0.202s]
finished. total time: 0.317s
rebooting into bootloader...
OKAY [ 0.081s]
finished. total time: 0.084s
sending 'radio' (48728 KB)...
OKAY [ 1.086s]
writing 'radio'...
OKAY [ 2.175s]
finished. total time: 3.267s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.018s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate -1473177068 bytes
error: update package missing system.img
Press any key to exit..."
Can anyone help out in this? Not sure what does failed to allocate -1473177068 bytes means? How can I solve this.
Try flashing each IMG file manually.
Don't use the flash-all.bat program. Manually type in your fastboot commands.
Extract that big ZIP you have in the same folder with your flash-all.bat. You'll see a bunch of img files called vendor.img, system.img, etc.
Once extracted, run the following commands in order. Replace "partition" with the img file name. Example: fastboot format system
fastboot format partition (if it gives an error, try fastboot erase partition).
fastboot flash partition imgfile
fastboot format cache
fastboot reboot-bootloader
Examples of what things should look like:
fastboot format system
fastboot flash system system.img
fastboot format cache
fastboot reboot-bootloader
<once rebooted, shouldn't take more than 2 seconds>
fastboot format vendor
fastboot flash vendor vendor.img
fastboot format cache
fastboot reboot-bootloader
<again, reboot, ~2 seconds>
If at any time it says it can't format memory type or something similar, usually this is for bootloader, radio and boot partitions, use fastboot erase boot (fastboot erase bootloader, fastboot erase radio).
Do this for each of the files, except for userdata - don't even flash that, just format userdata and skip the flash userdata part.
Also, flash your recovery of TWRP, the latest, and make sure that you boot to recovery first, before you boot the phone all together.
Did you verify the checksum of the image?
DON'T DO THAT...
Wiltron said:
fastboot erase bootloader
Click to expand...
Click to collapse
This will be your last fastboot command... Phone bricked.
To the OP, you should solve your flash-all problem as this script is the recommended way to flash factory images. You need some disk space (like 4 or 5GB)
rchtk said:
DON'T DO THAT...
This will be your last fastboot command... Phone bricked.
Click to expand...
Click to collapse
As long as you flash the bootloader again prior to rebooting you're fine.
I do this weekly with new builds of various ROMs.
Wiltron said:
As long as you flash the bootloader again prior to rebooting you're fine.
I do this weekly with new builds of various ROMs.
Click to expand...
Click to collapse
I find it way too risky tbh and don't see any added value in doing this.
rchtk said:
I find it way too risky tbh and don't see any added value in doing this.
Click to expand...
Click to collapse
Yeah, no reason to advise this. Especially in a thread of someone who may or may not be comfortable using fastboot. Risk > Reward 100%
Not like any 'gremlins' get left behind when updating a bootloader.
OP, just read and follow the beginner sticky thread and you'll do just fine. This one.
RoyJ said:
Yeah, no reason to advise this. Especially in a thread of someone who may or may not be comfortable using fastboot. Risk > Reward 100%
Not like any 'gremlins' get left behind when updating a bootloader.
OP, just read and follow the beginner sticky thread and you'll do just fine. This one.
Click to expand...
Click to collapse
Thank you RoyJ.....it worked
I did the "fastboot flash system system.img" and it says "FAILED <remote: data too large>. Never have any problem with the monthly updates before.
wormbaby11 said:
I did the "fastboot flash system system.img" and it says "FAILED <remote: data too large>. Never have any problem with the monthly updates before.
Click to expand...
Click to collapse
Googling wasn't much help in this case, found threads mostly for old HTC phones around 2013. However I did find one user trying to install 7.1 on his 5X which was able to solve his own issue by updating his Android tools in the SDK.
If you don't already have it, download and install the Android SDK. Follow the link I posted above and there's a section about how to install it.
Open the SDK Manager and under the section named "Tools" you should see; "Android SDK Tools" & "Android SDK Platform-tools".
Check to see if there's an update. I just noticed there is an available update on my PC. SDK Tools & SDK Platform-tools updated versions are 25.2.3 & 25.0.1, respectively. Update and reboot your PC and that should solve your issue. Let us know if that works for you.
Edit: Also, this is more than just a monthly security update. It was a bump up from 7.0.0 to 7.1.1. In any version bump like that, it never hurts to make sure the SDK is up to date.
Thanks Roy, that did the trick.
RoyJ said:
Googling wasn't much help in this case, found threads mostly for old HTC phones around 2013. However I did find one user trying to install 7.1 on his 5X which was able to solve his own issue by updating his Android tools in the SDK.
If you don't already have it, download and install the Android SDK. Follow the link I posted above and there's a section about how to install it.
Open the SDK Manager and under the section named "Tools" you should see; "Android SDK Tools" & "Android SDK Platform-tools".
Check to see if there's an update. I just noticed there is an available update on my PC. SDK Tools & SDK Platform-tools updated versions are 25.2.3 & 25.0.1, respectively. Update and reboot your PC and that should solve your issue. Let us know if that works for you.
Edit: Also, this is more than just a monthly security update. It was a bump up from 7.0.0 to 7.1.1. In any version bump like that, it never hurts to make sure the SDK is up to date.
Click to expand...
Click to collapse
Glad to hear you got it working!
[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexu...talls-t3518311
try this clean install should work
When I try to wipe internal it says
Code:
Wiping internal storage -- /data/media...
Error opening: '/data/media' (No such file or directory)
When I try to format instead - I get even more errors:
Code:
Formatting Data using make_ext4fs...
Failed to mount '/data' (Device or resource busy)
Failed to mount '/data' (Device or resource busy)
Unable to recreate /data/media folder.
You may need to reboot recovery to be able to use /data again.
Updating partition details...
Failed to mount '/data' (Device or resource busy)
...done
Is this because of encryption? And if so - this is weird because I never encrypted my device. I currently have no OS and just trying to unsoftbrick my phone.
specialk00 said:
...Is this because of encryption? And if so - this is weird because I never encrypted my device. I currently have no OS and just trying to unsoftbrick my phone.
Click to expand...
Click to collapse
Use fastboot and make sure you are using the latest binaries. Format system, userdata and cache. Upon booting for the first time, the 6P automatically defaults to encryption- unless you intervene and stop it from doing so.
v12xke said:
Use fastboot and make sure you are using the latest binaries. Format system, userdata and cache. Upon booting for the first time, the 6P automatically defaults to encryption- unless you intervene and stop it from doing so.
Click to expand...
Click to collapse
Yep, I just fixed it somehow, I think it was related to MTP in TWRP. However now I'm stuck with a different issue. No matter what I flash in fastboot - I get
Code:
C:\Users\Nexusflip\AppData\Local\Android\sdk\platform-tools>fastboot flash recovery D:\Downloads\angler\twrp-3.1.1-0-angler.img
target didn't report max-download-size
sending 'recovery' (16948 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
I always get this weird "No error" thing.
specialk00 said:
Yep, I just fixed it somehow, I think it was related to MTP in TWRP. However now I'm stuck with a different issue. No matter what I flash in fastboot - I get
Click to expand...
Click to collapse
Are you sure you are using the latest binaries? Hash checked the TWRP file? Put TWRP img in your fastboot folder? Format/erase recovery partition?
v12xke said:
Are you sure you are using the latest binaries? Hash checked the TWRP file? Put TWRP img in your fastboot folder? Format/erase recovery partition?
Click to expand...
Click to collapse
Yes I'm using the latest binaries - I got them via Android SDK and updated everything. I checked the ones you linked and they are exactly the same.
Regarding the hash check - this has nothing to do with the file being corrupted. This happens with ANY file I try to flash.
I tried putting the TWRP img in my fastboot folder and the results are the same.
Erasing the recovery partition gives the same error.
Code:
C:\Users\username\AppData\Local\Android\sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
FAILED (command write failed (No error))
finished. total time: 0.009s
specialk00 said:
Yes I'm using the latest binaries - I got them via Android SDK and updated everything. I checked the ones you linked and they are exactly the same. Regarding the hash check - this has nothing to do with the file being corrupted. This happens with ANY file I try to flash. I tried putting the TWRP img in my fastboot folder and the results are the same. Erasing the recovery partition gives the same error.
Click to expand...
Click to collapse
Were you able to successfully fastboot format userdata, system and cache with no errors? Did you get the same error using format as you did erase recovery? Is your phone bootlooping ? If yes, then your phone may have the BLOD. There are a few instances of users still having access to recovery mode, but not being able to flash anything. If you flash a full stock image with flash-all.bat, it finishes but the phone still loops then you likely have the BLOD.
v12xke said:
Were you able to successfully fastboot format userdata, system and cache with no errors? Did you get the same error using format as you did erase recovery? Is your phone bootlooping ? If yes, then your phone may have the BLOD. There are a few instances of users still having access to recovery mode, but not being able to flash anything. If you flash a full stock image with flash-all.bat, it finishes but the phone still loops then you likely have the BLOD.
Click to expand...
Click to collapse
I tried minimal adb & fastboot (bit older version) and got this.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.1.1-0-angler.img
target didn't report max-download-size
sending 'recovery' (16948 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.007s
Then I tried another old version of fastboot - got one from july 2016 (23.0.1) and nothing happened when executing flash or format commands.
Then I tried normal, latest fastboot and both (new & old) versions of fastboot gave me this error.
Code:
C:\Users\Nexusflip\AppData\Local\Android\sdk\platform-tools>fastboot erase userdata
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: 0.023s
Then I tried to format (instead of erase)
Code:
C:\Users\Nexusflip\AppData\Local\Android\sdk\platform-tools>fastboot format userdata
FAILED (command write failed (No error))
I don't know if my phone is bootlooping because I don't have OS installed and my internal storage is squeaky clean. All this crap didn't just start out of nowhere - I flashed 8.0.0 dev preview 2 images through TWRP. I know I'm not the brightest. When I launch flash-all.bat it's just blank and does nothing at all.
specialk00 said:
I don't know if my phone is bootlooping because I don't have OS installed and my internal storage is squeaky clean. All this crap didn't just start out of nowhere - I flashed 8.0.0 dev preview 2 images through TWRP. I know I'm not the brightest. When I launch flash-all.bat it's just blank and does nothing at all.
Click to expand...
Click to collapse
It sounds to me like your internal storage (memory) is bad. Bottom line is that if you can't format your basic partitions successfully, you will not be able to flash a full ROM. If you don't believe your memory is bad, you can search the 6P forums for the Qualcomm Flash Image Loader (QFIL) & EDL mode. There is a rescue binary for the 6P floating around that some people have been successful in using restoring corrupt partitions, presumably because it works at the hardware level.
v12xke said:
It sounds to me like your internal storage (memory) is bad. Bottom line is that if you can't format your basic partitions successfully, you will not be able to flash a full ROM. If you don't believe your memory is bad, you can search the 6P forums for the Qualcomm Flash Image Loader (QFIL) & EDL mode. There is a rescue binary for the 6P floating around that some people have been successful in using restoring corrupt partitions, presumably because it works at the hardware level.
Click to expand...
Click to collapse
What should I do from now on? I have no idea what to do. The device has been bricked for 24 hours now.
This is the closest I've found to my problem. Also on a Nexus 6P. https://forum.xda-developers.com/nexus-6p/help/zip-file-signature-verification-error-t3561054
I tried adb reboot edl and it says error: closed. So not even that works.
specialk00 said:
What should I do from now on? I have no idea what to do. The device has been bricked for 24 hours now. This is the closest I've found to my problem. Also on a Nexus 6P. https://forum.xda-developers.com/nexus-6p/help/zip-file-signature-verification-error-t3561054
I tried adb reboot edl and it says error: closed. So not even that works.
Click to expand...
Click to collapse
Stock fastboot does not support boot to EDL. You need a modified fastboot, BUT getting to EDL mode won't help you until you have all the proper tools and 6P specific files. I don't want to get your hopes up. I think your device is not recoverable due to a hardware issue (bad memory). If you are looking for a learning project to keep you busy with very little hope of success, keep digging. If you need a working phone, you need to buy another one, or a 6P replacement motherboard from a screen damaged parts phone. Unfortunately, there have been many onboard memory failures on the 6P.
I fixed the problem. It turned out to be a faulty USB-C to USB-A cable. The only problems were with file transfer-related commands. I then tried transferring a 1 kb file, then 1 mb (failed) then 200kb, then 300kb (failed). So it turns out the cable is ****ty. Wow. And nothing is corrupted. I'm typing this from my phone now.
I wanted to get on the latest developer preview release, downloaded the system image, and flashed it to my phone, when done i tried to reboot it, but it stayed on the white google logo screen infinitely. Eventually rebooted, and now won't even attempt to boot. It just goes back to fastboot.
Any attempt to go to recovery, boot the system, or anything - gives an error "Your device is corrupt. It can't be trusted and may not work properly". It offers a link to g.co/ABH then an option to press the power to continue, when I do, it briefly flashes the google logo, then back to the bootloader. Where it has a reason shown as "error booting boot.img"
It doesn't respond to any adb or fastboot commands, but does show in the device manager as LeMobile Android Device (Android Bootloader Interface). And that's about it.
I seem to be stuck in a loop here, and would appreciate if anyone has any advice to offer.
I've managed to get it responding to fastboot commands, but it fails while flashing the system image, it seems to fail at exactly the same point each time though, and I just can't seem to get it to finish the install, and therefore can't boot up.
It flashes the radio, and recovery without any problem, goes through a large portion of the system flash process before failing.
Below is the text from where it fails, does anyone know a way around this?
Sending sparse 'vendor_b' 1/3 (262140 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
Ohiostyle said:
I've managed to get it responding to fastboot commands, but it fails while flashing the system image, it seems to fail at exactly the same point each time though, and I just can't seem to get it to finish the install, and therefore can't boot up.
It flashes the radio, and recovery without any problem, goes through a large portion of the system flash process before failing.
Below is the text from where it fails, does anyone know a way around this?
Sending sparse 'vendor_b' 1/3 (262140 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
Click to expand...
Click to collapse
Is it going from fastboot to fastbootd?
Yeah it was, it completed a lot of other read/write actions after moving over to fastbootd, before failing.
I was able to get it working by sideloading the ota file. Any system image (always factory images) that I would try to flash would fail at the same point. I have no idea why.
Ohiostyle said:
I've managed to get it responding to fastboot commands, but it fails while flashing the system image, it seems to fail at exactly the same point each time though, and I just can't seem to get it to finish the install, and therefore can't boot up.
It flashes the radio, and recovery without any problem, goes through a large portion of the system flash process before failing.
Below is the text from where it fails, does anyone know a way around this?
Sending sparse 'vendor_b' 1/3 (262140 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
Click to expand...
Click to collapse
you need to extract the other zip within the image and make sure you extract it where your adb tools are
tmoore3496 said:
you need to extract the other zip within the image and make sure you extract it where your adb tools are
Click to expand...
Click to collapse
Yes, I had that problem time ago (I think with the OG Pixel).
Doing what you described fixed it, now I always do it just in case.
Also updating to the latest platform tools.
Can you go into recovery? If so try sideloading an OTA file.