Hi all,
I am getting a headached with my mix 2 ......
Bootloader is unlocked (shown in Developer Settings and as little text when entering Backup/Fastboot).. I tried different Versions of fastboot from an old version 1:7.0.0+r33-2 to an new one -> fastboot version 28.0.0-4797878.
MIUI Version: 9.6.1.0(ODEMIFD) (Stable)
And yes I did it like the manual here on xda for this mobile ...
I also changed the System from Windows 10 to an Kali....
There isn't a single line of output.
Trying to directly boot the TWRP Image stucks at the first line telleng me: Downloading 'boot.img'
Someone can help me?
Friend here who helped him:
Even just listing the variables didn't yield any output (download got stuck on the "getvar: stuff, too)
I´m getting the same, i have latest global beta 8.7.5, its working fine but i wanted to flash LOS and for some reason no fastboot command works, only fastboot devices. Please someone help
ernesto.ulloa said:
I´m getting the same, i have latest global beta 8.7.5, its working fine but i wanted to flash LOS and for some reason no fastboot command works, only fastboot devices. Please someone help
Click to expand...
Click to collapse
Maybe we should really trying Step 1. Disable driver signature enforcement in Windows from the all in one user guide .... (i didn'T tried it actually)
techler said:
Maybe we should really trying Step 1. Disable driver signature enforcement in Windows from the all in one user guide .... (i didn'T tried it actually)
Click to expand...
Click to collapse
Tried it....... no progress
Done in Windows:
.\fastboot.exe devices
9476f4d3 fastboot
and trying to flash
.\fastboot.exe -v flash recovery twrp-3.2.2-1-chiron.img
fastboot: verbose: sending command "getvar:has-slot:recovery"
fastboot: verbose: received FAIL "GetVar Variable Not found"
fastboot: verbose: sending command "getvar:max-download-size"
fastboot: verbose: received OKAY "536870912"
fastboot: verbose: target reported max download size of 536870912 bytes
Sending 'recovery' (26360 KB)
fastboot: verbose: sending command "download:019be000"
stucks there ........
and live boot too ...
.\fastboot.exe -v boot .\twrp-3.2.2-1-chiron.img
Downloading 'boot.img'
fastboot: verbose: sending command "download:019be000"
techler said:
Tried it....... no progress
Done in Windows:
.\fastboot.exe devices
9476f4d3 fastboot
and trying to flash
.\fastboot.exe -v flash recovery twrp-3.2.2-1-chiron.img
fastboot: verbose: sending command "getvar:has-slot:recovery"
fastboot: verbose: received FAIL "GetVar Variable Not found"
fastboot: verbose: sending command "getvar:max-download-size"
fastboot: verbose: received OKAY "536870912"
fastboot: verbose: target reported max download size of 536870912 bytes
Sending 'recovery' (26360 KB)
fastboot: verbose: sending command "download:019be000"
stucks there ........
and live boot too ...
.\fastboot.exe -v boot .\twrp-3.2.2-1-chiron.img
Downloading 'boot.img'
fastboot: verbose: sending command "download:019be000"
Click to expand...
Click to collapse
EDIT:
It worked, i changed to my laptop(win 10). I used a git bash(random used this), no usb devices are connected and no internet.
Just typed .\fastboot.exe flash recovery twrp.img
It worked
Warning: Only reboot to Recovery and install the .img with the "temporary" again, if you don't Xiaomi will place it's own bootloader again there.
Hi all,
I've seemed to have bricked my Pixel C. I tried flashing the stock ROM after installing LineageOS.
I wiped everything using fastboot (recovery, data, system, bootloader, cache, etc) and now I am just stuck with fastboot.
When I try and use
Code:
fastboot boot twrp.img
, I get the following:
Code:
creating boot image...
creating boot image - 12974080 bytes
Sending 'boot.img' (12670 KB) OKAY [ 0.320s]
Booting FAILED (remote: 'image verification failed')
fastboot: error: Command failed
If I try and flash recovery using
Code:
fastboot flash recovery twrp.img
, I get the following:
Code:
Sending 'recovery' (12668 KB) OKAY [ 0.347s]
Writing 'recovery' FAILED (remote: 'unsupported command')
fastboot: error: Command failed
I did have this error before, but I had TWRP and used fwtool to fix it. But I have no OS, no recovery and I am getting these issues with fastboot.
I have tried various cables, my drivers are up to date and my software is up to date. I have also tried flashing the stock image from Google but that just does the following:
Code:
Sending 'bootloader' (16384 KB) OKAY [ 0.445s]
Writing 'bootloader' FAILED (remote: 'unsupported command')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.016s
--------------------------------------------
Bootloader Version...: ***********************************************************
Baseband Version.....: N/A
Serial Number........: unknown variable
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.010s]
Checking 'version-bootloader' FAILED
Device version-bootloader is '***********************************************************'.
Update requires 'Google_Smaug.7900.139.0'.
fastboot: error: requirements not met!
Press any key to exit...
Is this tablet totally bricked or can anyone help me out?
Thanks
Vartom said:
I fixed such a lock by flashing a chip with a bootloader. To do this, I had to peel off the screen and buy a programmer on Ali. Risky operation.
Click to expand...
Click to collapse
Hi, can you give more details on how you proceeded
Have you tried this?
https://download.dirtyunicorns.com/?device=dragon
Google smaug vendor image
Gesendet von meinem Nexus 6P mit Tapatalk
Doesn't work. It's not the image that's the issue anyway, its the command being unrecognized:
Code:
Sending 'bootloader' (16384 KB) OKAY [ 0.438s]
Writing 'bootloader' FAILED (remote: 'unsupported command')
fastboot: error: Command failed
Bricked.
I solved same problem but I was able to boot system and used this in adb:
Code:
fwtool vbnv write dev_boot_fastboot_full_cap 1
You must somehow boot recovery and flash system. Without recovery you are screwed.
matonka007 said:
Bricked.
I solved same problem but I was able to boot system and used this in adb:
Code:
fwtool vbnv write dev_boot_fastboot_full_cap 1
You must somehow boot recovery and flash system. Without recovery you are screwed.
Click to expand...
Click to collapse
Yeah. I have been searching for hours but it seems impossible without recovery.
Tried this?
https://forum.xda-developers.com/pixel-c/help/bootloader-reports-unlocked-unable-to-t3483513
Gesendet von meinem Nexus 6P mit Tapatalk
---------- Post added at 06:13 PM ---------- Previous post was at 06:11 PM ----------
And this?
https://forum.xda-developers.com/pixel-c/help/flash-factory-image-t3599367/amp/
Gesendet von meinem Nexus 6P mit Tapatalk
Yes but with no joy.
Fastboot doesn't work at all so I cannot even boot to recovery. Therefore, I am unable to use ADB to fix fastboot
Sad, maybee this?
https://forum.xda-developers.com/pixel-c/help/flashing-to-stock-android-npd90g-twrp-t3424863
Gesendet von meinem Nexus 6P mit Tapatalk
Doesn't work. But AGAIN... I cannot access recovery for ADB
Sorry no more ideas
Gesendet von meinem Nexus 6P mit Tapatalk
Are you sure that your BL is unlocked? Try to lock it and unlock it again.
Code:
FAILED (remote: 'image verification failed')
This error looks like it can not boot unsigned image. But I do not know why.
Bootloader is definitely unlocked. I have tried locking and unlocking multiple times
JustDarren said:
Hi all,
If I try and flash recovery using
Code:
fastboot flash recovery twrp.img
, I get the following:
Code:
Sending 'recovery' (12668 KB) OKAY [ 0.347s]
Writing 'recovery' FAILED (remote: 'unsupported command')
fastboot: error: Command failed
[/code]
Click to expand...
Click to collapse
This is a longshot, but I was getting very similar errors trying to do anything. All this happened on a Windows 10 Laptop using the Google Drivers. I tried it again on a Mac Book Pro running Catalina and it worked just fine with latest platform tools.
Perhaps you want to try a Linux or Mac if you have access to one, or try a Linux live edition on your current machine, something like this:
https://ubuntu.com/tutorials/try-ubuntu-before-you-install#1-getting-started
Just worth a shot. Still an awesome tablet to lose just yet. Hope it is not too late for you.
TheInitialCommand said:
This is a longshot, but I was getting very similar errors trying to do anything. All this happened on a Windows 10 Laptop using the Google Drivers. I tried it again on a Mac Book Pro running Catalina and it worked just fine with latest platform tools.
Perhaps you want to try a Linux or Mac if you have access to one, or try a Linux live edition on your current machine, something like this:
https://ubuntu.com/tutorials/try-ubuntu-before-you-install#1-getting-started
Just worth a shot. Still an awesome tablet to lose just yet. Hope it is not too late for you.
Click to expand...
Click to collapse
Thanks for the suggestion. I'll give it a go and let you know what happens
Good luck!
TheInitialCommand said:
Good luck!
Click to expand...
Click to collapse
No joy. Still getting unknown command. Even tried manually erasing and formatting the partitions with no luck. Thanks for the suggestion though.
Really bummed out because I still love this tablet. Shame I bricked it ?
JustDarren said:
No joy. Still getting unknown command. Even tried manually erasing and formatting the partitions with no luck. Thanks for the suggestion though.
Really bummed out because I still love this tablet. Shame I bricked it
Click to expand...
Click to collapse
I have similar problem ..
you need to extract the rom zip file, inside you have img files ...
a) you need tablet in fastboot mode . i have made the process in linux. also i have downloaded this rom
ryu-opm8.190605.005-factory-25b457f3.zip downloaded from google.
b) Tablet needs to be unlocked .. for that you need to do fastboot oem unlock .. and after you return to fastboot mode.
And here you have my steps ..
All made in linux but if you use windows remove the command "sudo" it ahould work
1) sudo fastboot flash bootloader bootloader-dragon-google_smaug.7900.139.0.img
2) sudo fastboot reboot bootloader
3) sudo fastboot flash boot boot.img
4) sudo fastboot flash cache cache.img
5) sudo fastboot flash recovery recovery.img
6) sudo fastboot flash system system.img
7) sudo fastboot flash vendor vendor.img
8) restart the tabler pressing button.
Check if these works for you ..
bye
Thanks for your reply but as o have said many times, fastboot is unresponsive and returns "Command not found". This isn't an error on my part with inputting the commands but I think moreso, corrupt storage
Did you try to use fusée gelée like on the nintendo switch, i think it will may solve your problem.
rhmanoa said:
Did you try to use fusée gelée like on the nintendo switch, i think it will may solve your problem.
Click to expand...
Click to collapse
I don't think that will work. Unless you have a guide for using it on android devices other than the switch.
Okay, I've seen similar problems to mine but none of the suggested solutions seem to work out the problem. This seems to be the recommended solution, but it's not getting me anywhere:
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
My bootloader is unlocked. I unlocked it the second I got the phone to save pain down the road. I've now hit the fork. It's an unlocked phone, not Verizon, I'm not sure what the original carrier was, it was second-hand and under no warranty. I'm on Android 10 Marlin, I updated it to the latest about a month ago. I got up to do some laundry last night and came back to a spontaneously dead phone. For detail, I was transferring a movie to my phone via USB to internal storage so I could watch it later. No idea what happened while I was up, but the phone was in the exact same position as when I left. Developer options were on, USB debugging was on.
What I have now is this: It will enter fastboot. When I prompt it to boot to recovery, it shuts down, or it will go to the unlocked bootloader warning screen, allow me to pause/continue booting, at which point it will either go directly to black, or briefly show the Google bootloader and then shut off. When I leave it on a charge, either trickle or full, it will sometimes loop through the unlocked bootloader warning, flicking that screen on and off, but sometimes it's just off. I never see the charging battery screen. I've left it to charge for hours.
Sometimes windows acknowledges a USB device is connected and that it's android, but at no point can I access storage. When working through a command line prompt, acknowledges that the device is there, but trying to flash anything fails immediately. Here is a sample of some of my results.
When trying the flash-all solution:
PHP:
Sending 'bootloader_b' (32480 KB) OKAY [ 1.779s]
Writing 'bootloader_b' FAILED (remote: 'Verify bootloader image failed on production device.')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.040s]
Finished. Total time: 0.044s
The device goes black. I'll bring it back up to fastboot and the command line spits this out:
PHP:
< waiting for any device >
Sending 'radio_b' (57156 KB) OKAY [ 3.785s]
Writing 'radio_b' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.199s]
Finished. Total time: 0.207s
Using fastboot to try and boot factory bootloader, it says it's worked but then the phone again just goes to black and does nothing:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot boot bootloader-marlin-8996-012001-1908071822.img
< waiting for any device >
creating boot image...
creating boot image - 33261568 bytes
Sending 'boot.img' (32482 KB) OKAY [ 2.100s]
Booting OKAY [ 0.531s]
Finished. Total time: 2.944s
Flashing that factory bootloader, seems successful, again, back to black screen and nothing until going back to fastboot:
PHP:
>> PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot boot bootloader-marlin-8996-012001-1908071822.img
>> < waiting for any device >
>> creating boot image...
>> creating boot image - 33261568 bytes
>> Sending 'boot.img' (32482 KB) OKAY [ 2.100s]
>> Booting OKAY [ 0.531s]
>> Finished. Total time: 2.944s
And finally, trying to push an update image over fastboot:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot update image-marlin-qp1a.191005.007.a3.zip
--------------------------------------------
Bootloader Version...: N/A
Baseband Version.....: N/A
Serial Number........: HT6AD0202367
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.044s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'N/A'.
Update requires '8996-012001-1908071822'.
fastboot: error: requirements not met!
I am wondering if locking the bootloader would give this thing what it wants and let me boot into recovery, but I have a terrible feeling it would just further lock me out of saving this phone. Does anyone have any insight? Is this a shot motherboard? Sorry, I know my problem has a ton of commonalities with a lot of other people's but it seems for all my searching, reading and Googling that it's idiosyncratic to the point of every solution not working for me. Thank you so much.
Edit: For interest, I just saw the screen throw up an odd block of static, for lack of a better term. In the bottom right corner, it took up a little more than 1/4 of the screen. It looked lik there was cut off text at the top, too little showing to read. It disappeared before I could take a picture with a spare phone. It lasted maybe 5 seconds and then it was gone. It's on USB charge, not sitting on fastboot right now.
ekjean said:
Okay, I've seen similar problems to mine but none of the suggested solutions seem to work out the problem. This seems to be the recommended solution, but it's not getting me anywhere:
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
My bootloader is unlocked. I unlocked it the second I got the phone to save pain down the road. I've now hit the fork. It's an unlocked phone, not Verizon, I'm not sure what the original carrier was, it was second-hand and under no warranty. I'm on Android 10 Marlin, I updated it to the latest about a month ago. I got up to do some laundry last night and came back to a spontaneously dead phone. For detail, I was transferring a movie to my phone via USB to internal storage so I could watch it later. No idea what happened while I was up, but the phone was in the exact same position as when I left. Developer options were on, USB debugging was on.
What I have now is this: It will enter fastboot. When I prompt it to boot to recovery, it shuts down, or it will go to the unlocked bootloader warning screen, allow me to pause/continue booting, at which point it will either go directly to black, or briefly show the Google bootloader and then shut off. When I leave it on a charge, either trickle or full, it will sometimes loop through the unlocked bootloader warning, flicking that screen on and off, but sometimes it's just off. I never see the charging battery screen. I've left it to charge for hours.
Sometimes windows acknowledges a USB device is connected and that it's android, but at no point can I access storage. When working through a command line prompt, acknowledges that the device is there, but trying to flash anything fails immediately. Here is a sample of some of my results.
When trying the flash-all solution:
PHP:
Sending 'bootloader_b' (32480 KB) OKAY [ 1.779s]
Writing 'bootloader_b' FAILED (remote: 'Verify bootloader image failed on production device.')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.040s]
Finished. Total time: 0.044s
The device goes black. I'll bring it back up to fastboot and the command line spits this out:
PHP:
< waiting for any device >
Sending 'radio_b' (57156 KB) OKAY [ 3.785s]
Writing 'radio_b' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.199s]
Finished. Total time: 0.207s
Using fastboot to try and boot factory bootloader, it says it's worked but then the phone again just goes to black and does nothing:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot boot bootloader-marlin-8996-012001-1908071822.img
< waiting for any device >
creating boot image...
creating boot image - 33261568 bytes
Sending 'boot.img' (32482 KB) OKAY [ 2.100s]
Booting OKAY [ 0.531s]
Finished. Total time: 2.944s
Flashing that factory bootloader, seems successful, again, back to black screen and nothing until going back to fastboot:
PHP:
>> PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot boot bootloader-marlin-8996-012001-1908071822.img
>> < waiting for any device >
>> creating boot image...
>> creating boot image - 33261568 bytes
>> Sending 'boot.img' (32482 KB) OKAY [ 2.100s]
>> Booting OKAY [ 0.531s]
>> Finished. Total time: 2.944s
And finally, trying to push an update image over fastboot:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot update image-marlin-qp1a.191005.007.a3.zip
--------------------------------------------
Bootloader Version...: N/A
Baseband Version.....: N/A
Serial Number........: HT6AD0202367
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.044s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'N/A'.
Update requires '8996-012001-1908071822'.
fastboot: error: requirements not met!
I am wondering if locking the bootloader would give this thing what it wants and let me boot into recovery, but I have a terrible feeling it would just further lock me out of saving this phone. Does anyone have any insight? Is this a shot motherboard? Sorry, I know my problem has a ton of commonalities with a lot of other people's but it seems for all my searching, reading and Googling that it's idiosyncratic to the point of every solution not working for me. Thank you so much.
Edit: For interest, I just saw the screen throw up an odd block of static, for lack of a better term. In the bottom right corner, it took up a little more than 1/4 of the screen. It looked lik there was cut off text at the top, too little showing to read. It disappeared before I could take a picture with a spare phone. It lasted maybe 5 seconds and then it was gone. It's on USB charge, not sitting on fastboot right now.
Click to expand...
Click to collapse
First, do not repeat do not lock your boot loader.
Second, try this:
- Make sure you have the latest SDK Platform-tools installed on your computer r29.0.5.
There is a link for it in the guide below (Prerequisites c.).
- Make sure you plug the USB into a non charging USB port.
- Extract the boot.img (#6 in the guide brlow) from the Factory image you are currently using and flash it:
fastboot flash boot --slot all boot.img
or
fastboot flash boot boot.img --slot all
Guide
Homeboy76 said:
First, do not repeat do not lock your boot loader.
Second, try this:
- Make sure you have the latest SDK Platform-tools installed on your computer r29.0.5.
There is a link for it in the guide below (Prerequisites c.).
- Make sure you plug the USB into a non charging USB port.
- Extract the boot.img (#6 in the guide brlow) from the Factory image you are currently using and flash it:
fastboot flash boot --slot all boot.img
or
fastboot flash boot boot.img --slot all
Guide
Click to expand...
Click to collapse
Thank you thank you thank you for lending a hand. And for confirming that my temptation to lock the bootloader is a bad idea.
I have three ports on my laptop, I'm not sure any are non-charging. I'm selecting one that it wasn't attached to when the file transfer apparently went wrong.
Here goes nothing. I updated SDK tools last night during all this to be sure everything was kosher.
Unfortunately this was my result from all USB ports, testing both formats of the command:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.846s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.873s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 0.936s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 0.864s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.827s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.821s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.939s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3>
ekjean said:
Thank you thank you thank you for lending a hand. And for confirming that my temptation to lock the bootloader is a bad idea.
I have three ports on my laptop, I'm not sure any are non-charging. I'm selecting one that it wasn't attached to when the file transfer apparently went wrong.
Here goes nothing. I updated SDK tools last night during all this to be sure everything was kosher.
Unfortunately this was my result from all USB ports, testing both formats of the command:
PHP:
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.846s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.873s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 0.936s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 0.864s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.827s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.821s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.939s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3>
Click to expand...
Click to collapse
Are you using SDK Platform-tools r29.0.5?
Why? When you extract it it creates a Platform-tools folder.
Put this folder in PS C:\ so you have a
PS C:\Platform-tools folder.
Not: PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3>
That folder set up may be causing the to many links
error.
Then put the boot.img in the Platform-tools folder and do #6 in the guide.
Homeboy76 said:
Are you using SDK Platform-tools r29.0.5?
Why? When you extract it it creates a Platform-tools folder.
Put this folder in PS C:\ so you have a
PS C:\Platform-tools folder.
Not: PS C:\Google\marlin-qp1a.191005.007.a3-factory-bef66533\marlin-qp1a.191005.007.a3>
That folder set up may be causing the to many links
error.
Then put the boot.img in the Platform-tools folder and do #6 in the guide.
Click to expand...
Click to collapse
I was still working from the soft-bricked guide, where I had a copy of fastboot/platform tools pasted to everthing else. Not a problem at all to move Platform tools to C:/ Thank you!
I have noticed that what I have is r29.0.6. Should I roll it back? Assuming I should have the newest, I get the same result...
PHP:
PS C:\platform-tools> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 1.729s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\platform-tools> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.788s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\platform-tools>
ekjean said:
I was still working from the soft-bricked guide, where I had a copy of fastboot/platform tools pasted to everthing else. Not a problem at all to move Platform tools to C:/ Thank you!
I have noticed that what I have is r29.0.6. Should I roll it back? Assuming I should have the newest, I get the same result...
PHP:
PS C:\platform-tools> fastboot flash boot --slot all boot.img
Sending 'boot_a' (30969 KB) OKAY [ 1.729s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\platform-tools> fastboot flash boot boot.img --slot all
Sending 'boot_a' (30969 KB) OKAY [ 0.788s]
Writing 'boot_a' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
PS C:\platform-tools>
Click to expand...
Click to collapse
No, do not roll back you have the latest version.
At this point I really don't know what will fix the problem but here are three long shots that might help/work:
1. Try fastboot flash boot boot.img. If that works. Do fastboot flash boot boot.img --slot other.
2. Download the latest Pixel or Pixel XL OTA image (which ever phone you have) and sideload it.
3. Do a Factory Reset. Settings => System => Advanced => Reset options => Erase all data (factory reset)
Good luck.
If none of them work, it could be a hardwear problem. Pixel/Pixel XL are failing because of age or manufacturing. I don't know which.
Homeboy76 said:
No, do not roll back you have the latest version.
At this point I really don't know what will fix the problem but hear are three long shots that might help/work:
1. Try fastboot flash boot boot.img. If that works. Do fastboot flash boot boot.img --slot other.
2. Download the latest Pixel or Pixel XL OTA image (which ever phone you have) and sideload it.
3. Do a Factory Reset. Settings => System => Advanced => Reset options => Erase all data (factory reset)
Good luck.
If none of them work, it could be a hardwear problem. Pixel/Pixel XL are failing because of age or manufacturing. I don't know which.
Click to expand...
Click to collapse
Sadly, anything that requires ADB/recovery is cut off to me, and so is anything that requires the actual OS interface, so accessing settings and factory resetting is out, and so is sideloading. All I can work from is fastboot.
The final option you had gave me another write failure. Thank you for working with me on this - this is my favorite phone I've ever had, and it may be time to eulogize it. I appreciate all you ran me through. <3
ekjean said:
Sadly, anything that requires ADB/recovery is cut off to me, and so is anything that requires the actual OS interface, so accessing settings and factory resetting is out, and so is sideloading. All I can work from is fastboot.
The final option you had gave me another write failure. Thank you for working with me on this - this is my favorite phone I've ever had, and it may be time to eulogize it. I appreciate all you ran me through. <3
Click to expand...
Click to collapse
RIP Pixel/Pixel XL!
hey bruh, try to cooling it in the freezer, my pixel xl turned on that way, give it a shot
@mateodiaz802 said:
hey bruh, try to cooling it in the freezer, my pixel xl turned on that way, give it a shot
Click to expand...
Click to collapse
Maybe I will! Did it stay on?
it will stay on the enough time to recover your data
@mateodiaz802 said:
hey bruh, try to cooling it in the freezer, my pixel xl turned on that way, give it a shot
Click to expand...
Click to collapse
I'm afraid in my case this was the death blow. Let out a few buzzes when attempting to power into fastboot, flashed a red light at the top and then nothing. She was euthanized by freezer around 5PM, 3/2/20, went quietly into that good night surrounded by friends and family at home. RIP Pixel.
did you cover the phone holes like the charging port and aux jack? I forgot to mention because I thought it was obvious
@mateodiaz802 said:
did you cover the phone holes like the charging port and aux jack? I forgot to mention because I thought it was obvious
Click to expand...
Click to collapse
I wrapped 'er in plastic wrap before putting it in. So it would've been covered. Oh well, stuff happens. Funny thing, I tried it again just to see. It started vibrating and hasn't stopped. XD
i covered the holes with tape, it's more effective, also you should try booting it with "start" optino from the bootloader
I'm having trouble figuring out why I can't unlock in fastboot.
I'm SIM unlocked; I confirmed this in the settings.
I got my unlock token from oneplus' website via email eariler today
OEM unlocking is checked in the developer settings
USB debugging enabled
Running most recent adb/fastboot tools I could find
I boot into fastboot and run the command - fastboot flash cust_unlock unlock_code.bin - and get the following error:
PS C:\Users\juann\Desktop\Root\platform-tools> fastboot flash cust_Unlock unlock_code.bin
target reported max download size of 805306368 bytes
sending 'cust_Unlock' (0 KB)...
OKAY [ -0.000s]
writing 'cust_Unlock'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: -0.000s
Any ideas?
command your using is wrong..
"fastboot flash cust-unlock unlock_code.bin"
Libra420T said:
command your using is wrong..
"fastboot flash cust-unlock unlock_code.bin"
Click to expand...
Click to collapse
…
man I hate myself sometimes. Thank you so much. Fwiw I wear glasses but wasn’t using them last night. Do you have a PayPal so I can send you some dough for looking through this for me?