2

I am trying to flash twrp to my ZTE Axon 7 but until now I just keep getting errors every time I try to flash something.

Device is already wiped and bootloader unlocked.

I am in fastboot mode, I also get some unknown error in MiFlash. So basically I haven't really been able to flash anything.

Already tried different ports and cables, don't have any other cables lying around. PC does have a ryzen 5800x, some maybe that is the problem?

enter image description here

D:\ZTE Axon 7>fastboot devices
a773911d        fastboot

D:\ZTE Axon 7>fastboot flash recovery "D:\ZTE Axon 7\twrp-3.5.2_9-0-ailsa_ii.img"
Sending 'recovery' (16104 KB)                      FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed

I also tried some commands like "clear cache" and "reboot bootloader" but they produce the same kind of error.

Really running out of ideas on this one, i've already tried numerous things and keep getting a variation of these "Write to device failed" errors all the time.

When I look at any guides/videos online it just works, but not for me.

Trying to use fastboot boot (different usb ports):

C:\adb-platform-tools>fastboot boot twrp-3.5.2_9-0-ailsa_ii.img
Sending 'boot.img' (16104 KB)                      FAILED (Status read failed (Too many links))
fastboot: error: Command failed

C:\adb-platform-tools>fastboot boot twrp-3.5.2_9-0-ailsa_ii.img
Sending 'boot.img' (16104 KB)                      FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed

C:\adb-platform-tools>fastboot boot twrp-3.5.2_9-0-ailsa_ii.img
Sending 'boot.img' (16104 KB)                      FAILED (Status read failed (Too many links))
fastboot: error: Command failed
2
  • Instead of actually flashing you could try to directly boot TWRP using fastboot boot "<path_to_img>" (TWRP image will only be copied to RAM).
    – Robert
    Jun 24 at 11:32
  • I keep getting the same kind of failures no matter what usb port I am using. Added them to the main post.
    – Aseliot
    Jun 24 at 13:07
1

Ok the solution is pretty weird.

I was reading this: https://mrnoob.net/data-transfer-failure-too-many-links-fix/

Which mentions something about the Windows 10 drivers being problematic, so it is suggested to use a USB 2.0 adapter or something similar.

So I have one of those and tried a command, and it worked.

Next I tried flashing

fastboot flash boot twrp.img

But it still didn't work and got the "Couldn’t parse partition size ‘0x’". But I thought to myself how can this be, one command works and the next just fails like that all of a sudden.

Then I read through this: https://www.droidwin.com/fix-fastboot-error-couldnt-parse-partition-size-0x/

I guess you can skip the root requirements for now and look at the flash command used:

fastboot flash:raw boot twrp.img

However this still didn't work and I have tried it before, you know why? I my case it's really f-ing weird.

One thing I must mention before this is that I also installed the "QDLoader HS-USB Driver_64bit" drivers, on W10 this will now display some "Test Mode" text on the lower right because these drivers are not signed by Microsoft.

    • Connect phone to USB 2.0 adapter with proper cable
    • Make sure the device shows up in fastboot devices
    • The weird thing, DO NOT use any peripherals like a wireless mouse on the same USB adapter the phone is connected to. It probably interferes with it somehow...
    • Now run the command and it should work (you can use fastboot reboot-bootloader just to make sure it's ok and commands work)

Might have to repeat these steps if the commands stops working again... Took me a long time to figure this out for some reason, always got frustrated with being unable to execute some simple commands and gave up on it...

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.