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

Help Fastboot stuck in 'sending'.

M

markprower

Newbie
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?
 
markprower said:
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?
Click to expand...
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?
 
ocnbrze said:
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?
Click to expand...
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)"
 
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.
 
James L said:
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.
Click to expand...
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.
 
ocnbrze said:
maybe try using a different cable? and are we sure you are using the correct twrp for your device?
Click to expand...
Yes, I've tried the original and other USB cables, tested all my computer's USB ports and the TWRP file is from the twrp website it self and it is the correct one for my model.
 
James L said:
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.
Click to expand...
Outdated fastboot files are not possible as I'm using the latest files from google themselves.
 
Same recovery just different sources. I would use the xda link, delete the other recovery.

Boot into fastboot, type fastboot flash recovery, drag the new recovery into terminal, press enter. I don't rename the .img files.
 
Just out of curiosity what happens if you use fastboot boot ( drag recovery into terminal) and press enter.

No harm no foul if it doesn't work but in theory you should be able to boot TWRP
 
James L said:
Same recovery just different sources. I would use the xda link, delete the other recovery.

Boot into fastboot, type fastboot flash recovery, drag the new recovery into terminal, press enter. I don't rename the .img files.
Click to expand...
I got this "fastboot: error: ANDROID_PRODUCT_OUT not set" when I typed fastboot flash recovery
 
James L said:
Just out of curiosity what happens if you use fastboot boot ( drag recovery into terminal) and press enter.

No harm no foul if it doesn't work but in theory you should be able to boot TWRP
Click to expand...
Sorry I understood it wrong, got it right now and it does the same thing...
sending recovery... forever
 
You must log in or register to reply here.
Back
Top Bottom