• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Fastboot stuck in 'sending'.

markprower

Newbie
Dec 6, 2020
13
3
Hey guys, last week I've got my hands on a brand new Redmi Note 5 Pro and wanted to install twrp on it so I can do the good stuff ( root, adblocking, custom roms, etc... ). The bootloader is unlocked. OEM Unlocking is turned on in Developer options and also is USB Debbuging. But fastboot simply doesn't do anything, when I try to flash something it just shows me this:

Sending 'recovery' (42452 KB)

And that stays there forever, until I'm forced to unplug the device and it returns with this:

FAILED (Status read failed (No such device))

Simply nothing happens, I tried flashing it, booting it, tried the orangefox image instead but it always does this, can someone help me here?
 
Hey guys, last week I've got my hands on a brand new Redmi Note 5 Pro and wanted to install twrp on it so I can do the good stuff ( root, adblocking, custom roms, etc... ). The bootloader is unlocked. OEM Unlocking is turned on in Developer options and also is USB Debbuging. But fastboot simply doesn't do anything, when I try to flash something it just shows me this:

Sending 'recovery' (42452 KB)

And that stays there forever, until I'm forced to unplug the device and it returns with this:

FAILED (Status read failed (No such device))

Simply nothing happens, I tried flashing it, booting it, tried the orangefox image instead but it always does this, can someone help me here?
are you sure you are in the right directory where your fasboot and adb files are in? is there a way you can post a screenshot of your commands?
 
  • Like
Reactions: MrJavi and James L
Upvote 0
are you sure you are in the right directory where your fasboot and adb files are in? is there a way you can post a screenshot of your commands?
2020-12-06_17-00.png

The commands are being made inside the adb/fastboot folder, all the files are in there, and my phone is being detected. But it gets stuck forever in "Sending 'recovery' (42452 KB)"
 
  • Like
Reactions: MrJavi and ocnbrze
Upvote 0
As mentioned above a cable & or usb port. Or possibly outdated fastboot files. Try this type ./fastboot then drag the recovery into terminal and press enter.

I've seen Macs that don't like the ./fastboot try just fastboot flash etc. Linux and Mac as far as terminal commands are about the same.
Just fastboot doesn't work on linux because you need to adress the script/file itself with ./
I'll try the drag n' drop thingy.
 
Upvote 0
As mentioned above a cable & or usb port. Or possibly outdated fastboot files. Try this type ./fastboot then drag the recovery into terminal and press enter.

I've seen Macs that don't like the ./fastboot try just fastboot flash etc. Linux and Mac as far as terminal commands are about the same.
Outdated fastboot files are not possible as I'm using the latest files from google themselves.
 
Upvote 0
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones