So i can get the phone detected by fast-boot just fine now but I cannot flash anything it keeps giving me errors like "To many links" or "FAILED (Write to device failed (Unknown error))" ?
Am I missing something that I should've done first, the errors are obviously not very descriptive of what the issue could be.
So the bootloader is already unlocked and I am trying to use "fastboot flash recovery twrp.img"
Fixed here: https://android.stackexchange.com/q...e-failed-no-link-unknown-error-too-many-links
Related
Hi everyone !
I searched for a case like mine on the forum, but didn't find a solution to my problem, so you're my last hopes !
I have a Nexus 7 (2012) WIFI for a while now and I wanted to return to stock, on Lollipop (I was on Paranoid Android ROM, 4.4.4).
So, l used the Nexus Root Toolkit and ran the "return to stock + unroot" feature.
I downloaded the last google image for my device (5.0.2) and let the thing began.
It erases all partitions like it has to do, but when it needs to write bootloader, it fails and says: "FAILED (command write failed (Unknown error))".
I tried severals time, but always same problem. So I tried to flash stock 4.4.4, but can't write bootloader too: "FAILED (No suck device)" or "FAILED (too many links)" errors appear, something like those.
So, in last hopes, I tried to do this manually and followed this thread: http://forum.xda-developers.com/showthread.php?t=1907796
I erased correctly all partitions, but when I need to flash bootloader with "fastboot flash bootloader bootloader-tilapia-4.23.img" command, I get "FAILED (command write failed (Unknown error))" too...
I can't flash recovery, get the same error as the bootloader one...
If someone had the same problem or if someone can help me to restore my Nexus 7, it would be very kind !
Thanks to everyone who'll read this
Also have the same problem generated by the very same software!!
Anyone have any further info please?
MiMilz said:
Hi everyone !
I searched for a case like mine on the forum, but didn't find a solution to my problem, so you're my last hopes !
I have a Nexus 7 (2012) WIFI for a while now and I wanted to return to stock, on Lollipop (I was on Paranoid Android ROM, 4.4.4).
So, l used the Nexus Root Toolkit and ran the "return to stock + unroot" feature.
I downloaded the last google image for my device (5.0.2) and let the thing began.
It erases all partitions like it has to do, but when it needs to write bootloader, it fails and says: "FAILED (command write failed (Unknown error))".
I tried severals time, but always same problem. So I tried to flash stock 4.4.4, but can't write bootloader too: "FAILED (No suck device)" or "FAILED (too many links)" errors appear, something like those.
So, in last hopes, I tried to do this manually and followed this thread: http://forum.xda-developers.com/showthread.php?t=1907796
I erased correctly all partitions, but when I need to flash bootloader with "fastboot flash bootloader bootloader-tilapia-4.23.img" command, I get "FAILED (command write failed (Unknown error))" too...
I can't flash recovery, get the same error as the bootloader one...
If someone had the same problem or if someone can help me to restore my Nexus 7, it would be very kind !
Thanks to everyone who'll read this
Click to expand...
Click to collapse
PaulG2000 said:
Also have the same problem generated by the very same software!!
Anyone have any further info please?
Click to expand...
Click to collapse
It's pretty well known that for some reason, the bootloader images included on many of the factory images for grouper are not valid, and Google has never corrected this. You'll need to grab a valid bootloader from a different factory image, and flash it manually.
Check this thread out, it's all been covered in great detail there: http://forum.xda-developers.com/showthread.php?t=2573015
Edit: Also, if you're already on a valid bootloader version 4.23, then there's no need to flash the bootloader again.
Hi @all,
i just messed something up while testing several custom roms for my Zenfone5 so actually i cant write system neither by "sideload" nor by "fastboot flash system". i always get the a mistake like:
Code:
FAILED (remote: flash_cmds error!)
Actually i cant find a mistake by myself. Is it located in my PC or in my phone? i already searched for an errorlist for fastboot but that doesn't get me any results...
and as we say in germany:
Vielen Dank im Vorraus!
Vere'Athor
You're trying to flash a wrong file.
What's the command you're running?
I get the same error running this command:
fastboot.exe flash recovery recovery.img
I cant erase this partition too. When i run this:
fastboot.exe erase recovery
I get this:
FAILED (remote: unable to format)
¨
Please Help
Waërloga666 said:
I get the same error running this command:
fastboot.exe flash recovery recovery.img
I cant erase this partition too. When i run this:
fastboot.exe erase recovery
I get this:
FAILED (remote: unable to format)
¨
Please Help
Click to expand...
Click to collapse
Can you post a link to recovery you are trying to flash? (I will test it)
Can anyone help me out? I tried to install CM 13.1 in Zenfone 5 but when it gets to "writing boot" the following message appears:
FAILED (remote: flash_cmds error!)
How could i solve this? txs everyone
(If any of you guys could text in Portuguese i would be very pleasant)
if u want to flash custom rom
all u need is to unlock bootloader
take a look on this thread using auto.bat for unlock bootloader!
https://forum.xda-developers.com/zenfone-5/general/recovery-twrp-2-8-6-0-asus-zenfone-5-t3136263
after unlocked try flash TWRP again
to confirm success unlocked not!
if fail it will show error failed
just follow step by step read thru!
hope it helps
good luck !
I am Having The Same Error (FAILED (remote: flash_cmds error!)
What To do
Hello
i have followed all the guides in order to install the latest version of TWRP in mi X Compact in order to Magisk, but im having this issue on the fastboot comand:
Sending 'recovery' (21552 KB) OKAY [ 0.724s]
Writing 'recovery' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
i have serched for solutions but nothing seems to work, its the first time i try to install TWRP on this phone so its never been rooted (Bootloader is not unlocked) and everyting has alredy been updated to the latest version, any help?
Thanks in advance!
i just unlocked the bootloader, and still gives me the "FAILED (remote: Command not allowed)" error when flashin TWRP trough fastboot HELP PLEASE
Black Swift said:
i just unlocked the bootloader, and still gives me the "FAILED (remote: Command not allowed)" error when flashin TWRP trough fastboot HELP PLEASE
Click to expand...
Click to collapse
Try fastboot boot twrp.img
just tried it, i got a message on my phone screen:
"your device has failed verification and will not work properly"
then phone restarts
in the windows power shell i get this message:
FAILED (Status read failed (Too many links))
I just seem to be unable to install TWRP on this phone :C
Help please!!!
i just tried a different cable, im still getting the "comand not allowed" message, can anyone help me please??
Hello, I'm new here so if I miss any Forum rules please let me know.
TL;DR: I unlocked the bootloader of my VNS-L31 with PotatoNV and now I get the Message FAILED (remote: 'image verification error')
So, i want to install a Custom ROM in order to get OTG Support for my Smartphone. I'm new to this but as I figured out I need to do the following Steps.
1. Unlock Bootloader using PotatoNV
2. Install TWRP
3. Root via SU
3. Install CustomRom via TWRP
I think I managed to unlock my bootloader as I get the "your device cant be trusted" message every time I boot. I can enter fastboot mode with ADB and my device is recognized when it's in fastboot mode. when I try now to install TWRP (i tried different versions) I get the following message:
J:\Smartphone\TWRP\platform-tools_r31.0.2-windows\platform-tools>fastboot flash recovery twrp-3.1.1-0-venus.img
Sending 'recovery' (24464 KB) OKAY [ 0.648s]
Writing 'recovery' FAILED (remote: 'image verification error')
fastboot: error: Command failed
Reading the Forums suggested to relock the Bootloader and then unlock it again in good old " did you turn it off and on again" manner. but when I googled how to relock and unlock I got the warning that a lot of devices cant be unlocked a second time. So should I try to relock it via fastboot ? if I do so, can I unlock it again with the new unlockcode i set in PotatoNV, or do I need to open my phone for Testpoint mode and unlock it with PotatoNV again?
so hopefully i didn't miss any necessary information and someone here can help me or point me in the right direction
greetings
Elfenfreund
PS: Pardon my Writing. It's late and my English is not very trained.
No need to relock. Just unlock it again using the code given by the Potato. Then try flashing again the image.
Running the command (on Linux)
Bash:
~/platform-tools/fastboot flash recovery recovery.img
I get:
Code:
Sending 'recovery' (21101 KB)
...and that's it. Fastboot hangs indefinitely, seemingly not sending anything, and can only be killed by unplugging the USB. The phone says "FASTBOOT MODE" in green. I've tried all 3 USB ports on my laptop, the paths and filenames are correct, i've tried a lot and using both twrp and LineageOS recovery images, but I never get beyond this, except for getting an error sometimes, "FAILED (Write to device failed (Protocol error))", "FAILED (remote: 'unknown command')", or "FAILED (Write to device failed in SendBuffer() (Protocol error))", which turns into this after rebooting fastboot mode or trying again. What am I missing? I've unlocked the bootloader with the app, I'm trying to install a recovery to install LineageOS.
Edit: Doesn't seem like there's a solution, but I tried another computer and it worked. Annoying how buggy it is, but there.