Develop Bugs

Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"

Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"
Fixed flashing error "remote: unsupported command" when flashing a Pixel C back to stock
I used TWRP and SuperSU to root and modify the buildprops to enable and get an early look at the windowing in Android N beta on my Pixel C release 5 ahead of time.
When Release 5 NPD90G was available I decided to flash back to stock from Developer Preview 4 NPD56N rooted with SuperSU and flashed with TWRP. I like root - I run Ubuntu and Win 7. I don't mind running a rooted device if it doesn't have all my work and financial data. When the final N release is out, the Pixel C will become my work machine. It's almost there.
I'm naturally paranoid. I change my long passwords frequently and use 2 factor authentication for everything. So if I can, I'll take a stock release. See my instructions for wiping Android devices: How to wipe an Android Phone: the paranoid editon
I could not flash the NPD90G stock bootloader because of an error "remote: unsupported command"
Here's how I fixed it.
Updated the SDK manager including SDK Tools and USB drivers.
With the Pixel C in recovery mode, {hold the power key and volume down}
In TWRP mount System and reboot to recovery
>ADB Shell.
From ADB Shell I ran
>fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable Fast boot.
Then I changed from TWRP to Fastboot mode {power button plus hold the volume up button}
>fastboot erase userdata
>fastboot erase boot
>fastboot erase cache
>fastboot erase recovery
>fastboot erase system
See Note 1. Below
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
Note 1.
The first time through I flashed the following line items which resulted in the resting robot Andi. I don't think I needed to do this, but if the above instructions don't work, run the following before continuing for {flash bootloader bootloader-dragon-google_smaug.7900.27.0.img}
>flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot reboot-bootloader
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
>fastboot flash cache cache.img

Twrp can't flash
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command

Tugio said:
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command
Click to expand...
Click to collapse
When in fastboot mode, use:
Code:
fastboot boot twrp-local-file-on-computer.img

DanBUK said:
When in fastboot mode, use:
Click to expand...
Click to collapse
It's nice of you to help a fellow XDA user. But I suspect he's already solved his problem of three months ago.....

Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards

lllopa said:
Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards
Click to expand...
Click to collapse
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C

Make sure you have the latest version of fastboot and adb. I get these errors almost every month if I don't update.
https://developer.android.com/studio/releases/platform-tools.html

@stevep2007, thank you so much! I've been dealing with this "remote: unsupported command" nonsense for days now after trying to revert back to an older Oreo version of Lineage. This did the trick!

How can I solve the problem when my Pixel C is not unlocked? My Pixel made an update and after installing the Update I got the green little man. Now I have no Chance to activate USB debugging etc. Its also not possible to install twrp.img
How can I go to ADB shell with locked bootloader? Or isn't it possible?
Fastboot devices shows me my tablet. ADB devices also show my tablet with "sideload".
But every try to flash my Pixel fails. I alway get the message .... remote: unknown command.......fastboot error: command failed
flash-all.bat showes that all "*.img are missing" error: command failed... unknown command etc.......
So any idea to get my Pixel working again? ADB shell would make it I think. But how with locked bootloader.

_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
This did it for me!! Thanks much. I also updated platform-tools at the same time, who knows which did it

_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions

bernardomarx said:
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions
Click to expand...
Click to collapse
Sorry replied incorrectly

Pixel C - fastboot unsupported command

Hi everyone ! (I apologyze for my english)
I cant flash anything on my Pixel C because of this:
C:\Users\ykant\Desktop\Minimal ADB and Fastboot>fastboot flash recovery TWRP_dragon_3.0.2-23.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
finished. total time: -0.000s
Click to expand...
Click to collapse
No system to boot on and my TWRP is wiped !!
--> Cant do this:
fwtool vbnv write dev_boot_fastboot_full_cap 1
Click to expand...
Click to collapse
Is my pixel C bricked now ?
regards !

Did you unlock your device first with "fastboot oem unlock"?

redukt said:
Did you unlock your device first with "fastboot oem unlock"?
Click to expand...
Click to collapse
Yes i did this before, i was running on Remix OS

I don't know if this is of relevance but there were new fastboot commands introduced from Android M (?) and I have recollection about "partial unlock" - two flags required to be set and if only one was set it could be reported that the bootloader was unlocked but fastboot saw it as locked. Above may be totally wrong.
Here's the difference between old and current fastboot commands. Note the new lock/unlock commands
Code:
************************ OLD **************************************
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
************************ NEW **************************************
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> Reflash device from update.zip.
Sets the flashed slot as active.
flashall Flash boot, system, vendor, and --
if found -- recovery. If the device
supports slots, the slot that has
been flashed to is set as active.
Secondary images may be flashed to
an inactive slot.
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
flashing lock_critical Prevents flashing bootloader-related
partitions.
flashing unlock_critical Enables flashing bootloader-related
partitions.
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
erase <partition> Erase a flash partition.
format[:[<fs type>][:[<size>]] <partition>
Format a flash partition. Can
override the fs type and/or size
the bootloader reports.
getvar <variable> Display a bootloader variable.
set_active <slot> Sets the active slot. If slots are
not supported, this does nothing.
boot <kernel> [ <ramdisk> [ <second> ] ] Download and boot kernel.
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ]
Create bootimage and flash it.
devices [-l] List all connected devices [with
device paths].
continue Continue with autoboot.
reboot [bootloader] Reboot device [into bootloader].
reboot-bootloader Reboot device into bootloader.
help Show this help message.

-Yazh- said:
Hi everyone ! (I apologyze for my english)
I cant flash anything on my Pixel C because of this:
C:\Users\ykant\Desktop\Minimal ADB and Fastboot>fastboot flash recovery TWRP_dragon_3.0.2-23.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
finished. total time: -0.000s
Click to expand...
Click to collapse
No system to boot on and my TWRP is wiped !!
--> Cant do this:
fwtool vbnv write dev_boot_fastboot_full_cap 1
Click to expand...
Click to collapse
Is my pixel C bricked now ?
regards !
Click to expand...
Click to collapse
Hi, I'm just wondering if you were able to fix your tablet. I ran into the same problem as you here and am not able to find a solution to it.

Hi !!
Sorry for bad news, but i didn't found any solution since my Pixel C was bricked. Maybe there is a solution, but I dropped it before finding it.
I hope you find something to fix it !

@viii_xvi Are you using "Minimal ADB and Fastboot" as shown in the post you quoted by -Yazh- ? The current (?) version that I can find is 1.4.3 and that looks to be "2015".
For the current versions of adb and fastboot and the revision history, 12 since October 2016, see https://developer.android.com/studio/releases/platform-tools.html

peterk-1 said:
Are you using "Minimal ADB and Fastboot" as shown in the post you quoted by -Yazh- ? The current (?) version that I can find is 1.4.3 and that looks to be "2015".
Click to expand...
Click to collapse
No. I used the 15 second ADB and Fastboot installer. I'm pretty sure it works fine as I can use fastboot commands.
peterk-1 said:
For the current versions of adb and fastboot and the revision history, 12 since October 2016, see https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
I don't really know what to do with the files found in the zip. If I'm doing it wrong, can you tell me what I should be doing?

viii_xvi said:
No. I used the 15 second ADB and Fastboot installer. I'm pretty sure it works fine as I can use fastboot commands.
I don't really know what to do with the files found in the zip. If I'm doing it wrong, can you tell me what I should be doing?
Click to expand...
Click to collapse
There are Youtube videos on installing Android Platform Tools and a web search for installing Android Platform Tools with your o/s will find many hits. You need to know you are installing just the platform tools - some of the guides assume you are installing or have installed the full Android Software Development Kit (SDK).
Assuming you are using Windows then the simplest method is to copy the contents of the zip file into the current location of your "15 second" files. This ensures that you can run the new version of fastboot with the folder path you have used previously. In file manager "find" fastboot.exe and that will give you the folder to unzip ALL of the platform tools files. You will know if you have done it correctly if you get requests to overwrite existing files when you unzip the files.

peterk-1 said:
There are Youtube videos on installing Android Platform Tools and a web search for installing Android Platform Tools with your o/s will find many hits. You need to know you are installing just the platform tools - some of the guides assume you are installing or have installed the full Android Software Development Kit (SDK).
Assuming you are using Windows then the simplest method is to copy the contents of the zip file into the current location of your "15 second" files. This ensures that you can run the new version of fastboot with the folder path you have used previously. In file manager "find" fastboot.exe and that will give you the folder to unzip ALL of the platform tools files. You will know if you have done it correctly if you get requests to overwrite existing files when you unzip the files.
Click to expand...
Click to collapse
I've followed the instructions so I'm confident I did it correctly. Despite this, nothing has improved. I still can't flash the stock ROM or a custom recovery in fastboot.
What I've noticed from updating the fastboot version are some new commands I found when I entered "fastboot -h"
Code:
fastboot -h
commands:
reboot [bootloader|emergency]
stage <infile>
get_staged <outfile>
options:
--skip-secondary
--skip-reboot
--disable-verity
--disable-verification
--unbuffered
--version
From what I've tried, all the commands in options returns
fastboot: usage: no command
Click to expand...
Click to collapse

viii_xvi said:
I've followed the instructions so I'm confident I did it correctly. Despite this, nothing has improved. I still can't flash the stock ROM or a custom recovery in fastboot.
What I've noticed from updating the fastboot version are some new commands I found when I entered "fastboot -h"
Code:
fastboot -h
commands:
reboot [bootloader|emergency]
stage <infile>
get_staged <outfile>
options:
--skip-secondary
--skip-reboot
--disable-verity
--disable-verification
--unbuffered
--version
From what I've tried, all the commands in options returns
Click to expand...
Click to collapse
Hi, Did you tried to flash with the oldest stock rom of the pixel C ? Because it uses older version of fastboot so maybe it will work. I has also the same problem as you but hopefully twrp still worked so i could flash another system image.

rhmanoa said:
Hi, Did you tried to flash with the oldest stock rom of the pixel C ? Because it uses older version of fastboot so maybe it will work. I has also the same problem as you but hopefully twrp still worked so i could flash another system image.
Click to expand...
Click to collapse
I have now tried to flash the earliest factory image and am disappointed to say the bootloader did not flash and so I wasn't able to complete the flashing.
I don't think the problem is the fastboot version. It may be the bootloader itself. I've read someone describe this problem as "Broken fastboot (bootloader) security." I think the problem is that, when unlocked, the bootloader would return the same messages as if it was locked. The security of the bootloader still thinks it's locked and not allow flashing of any images. Also that locking and reunlocking does not improve the situation. This would explain why, when bootloader is unlocked, I get "remote: unsupported command" and "remote: image verification failed", the same as when I try the same commands when the bootloader is locked.

viii_xvi said:
I have now tried to flash the earliest factory image and am disappointed to say the bootloader did not flash and so I wasn't able to complete the flashing.
I don't think the problem is the fastboot version. It may be the bootloader itself. I've read someone describe this problem as "Broken fastboot (bootloader) security." I think the problem is that, when unlocked, the bootloader would return the same messages as if it was locked. The security of the bootloader still thinks it's locked and not allow flashing of any images. Also that locking and reunlocking does not improve the situation. This would explain why, when bootloader is unlocked, I get "remote: unsupported command" and "remote: image verification failed", the same as when I try the same commands when the bootloader is locked.
Click to expand...
Click to collapse
Just bought today, same issue, have you solved it?

mansonstein said:
Just bought today, same issue, have you solved it?
Click to expand...
Click to collapse
No, I didn't manage to fix it.

did you found a solution yet？
I got a same problem,cant flash anything but ordinary using.
I got the problem caused by flashed twrp3.2.3,cant get into system,just always get into twrp.
cant flash any official firmware with "flash-all.bat",no matter which platform tool or firmware.but the twrp were installed before can flash anything.
finally,I flashed newest OTA firmware,then device can be booted. but got the unsupported command

richardwia said:
did you found a solution yet？
I got a same problem,cant flash anything but ordinary using.
I got the problem caused by flashed twrp3.2.3,cant get into system,just always get into twrp.
cant flash any official firmware with "flash-all.bat",no matter which platform tool or firmware.but the twrp were installed before can flash anything.
finally,I flashed newest OTA firmware,then device can be booted. but got the unsupported command
Click to expand...
Click to collapse
I'm assuming you have the latest version of TWRP installed. IIRC, there should be "Fix Fastboot" in advanced options. If indeed you have the same problem I had, pressing this should fix the problem. I don't know anything beyond this as I never got to find out what happens afterwards.

viii_xvi said:
I'm assuming you have the latest version of TWRP installed. IIRC, there should be "Fix Fastboot" in advanced options. If indeed you have the same problem I had, pressing this should fix the problem. I don't know anything beyond this as I never got to find out what happens afterwards.
Click to expand...
Click to collapse
really？where I can find the“fix fastboot in advanced options”？

richardwia said:
really？where I can find the“fix fastboot in advanced options”？
Click to expand...
Click to collapse
I believe I'm not qualified to help you as I disposed of my tablet months ago. All the advice I've given is off of memory and may not be accurate. That being said, I won't help you anymore in fear of giving inaccurate information that may lead to bricking of your tablet.

I have a pixel C, flashed with latest 3-rd pixel experience before, someday i tried to flash back to factory image, hit the same trouble like this topic, i came here several times before, no solution, today, i found another article about this , it's solved my trouble.
sorry i am new here, i couldn't share the outside article link.
would like to share what i did on my pixel c.
1. root your pixel c
2. adb shell //this command could be executed under recovery mode too.
3. su
4. fwtool vbnv write dev_boot_fastboot_full_cap 1
5. adb reboot fastboot
then you could flash anything you want.

I had this just now - I finally got fed up of my Pixel C being so laggy and also chrome opening up as blank pages (I switched to brace to fix this, but it's abit crashy).
Anyhow I found that after
adb reboot bootloader
that
fastboot flash recovery twrp.img
was failing for me in the "Writing" stage
I discovered that the fix was to use
adb flashing unlock
then it will ask you a question (power button to confirm and one of teh volume keys to cancel).
after this it spins with erasing for a while and then comes back to fastboot after which
fastboot flash recovery twrp.img
Worked, after this you get an annoying 30s delay for each restart, I think that can be fixed by
adb flashing lock
I'll verify this when I've finished flashing a usable ROM to my Pixel C...

[Help] Pixel 3 xl stuck in twrp

i have unlocked bootloader, fastboot mode on and can boot into recovery just fine. If i just let it 'boot' it boots into twrp automatically. From twrp i try to sideload, but adb does not recognize there being anything connected (adb devices returns empty) and adb sideload fails. Im on windows 10.
Update: solved. I had to run the command window and admin and it flashed just fine. Thanks spotmark!

superbean83 said:
i have unlocked bootloader, fastboot mode on and can boot into recovery just fine. If i just let it 'boot' it boots into twrp automatically. From twrp i try to sideload, but adb does not recognize there being anything connected (adb devices returns empty) and adb sideload fails. Im on windows 10.
Click to expand...
Click to collapse
Download whatever build you're on and extract the boot image. Then fastboot flash the boot image.

superbean83 said:
i have unlocked bootloader, fastboot mode on and can boot into recovery just fine. If i just let it 'boot' it boots into twrp automatically. From twrp i try to sideload, but adb does not recognize there being anything connected (adb devices returns empty) and adb sideload fails. Im on windows 10.
Click to expand...
Click to collapse
Try flashing Magisk again in TWRP.

spotmark said:
Download whatever build you're on and extract the boot image. Then fastboot flash the boot image.
Click to expand...
Click to collapse
Code:
c:\adb>fastboot flash boot bl.img
Sending 'boot_a' (8489 KB) OKAY [ 0.310s]
Writing 'boot_a' (bootloader) Flashing Pack version b1c1-0.1-5034669
FAILED (remote: '(boot_a) No such partition')
Finished. Total time: 0.564s
thats what it doesn when i try to flash boot image

superbean83 said:
i have unlocked bootloader, fastboot mode on and can boot into recovery just fine. If i just let it 'boot' it boots into twrp automatically. From twrp i try to sideload, but adb does not recognize there being anything connected (adb devices returns empty) and adb sideload fails. Im on windows 10.
Click to expand...
Click to collapse
.
Plz read line #1 on post #1 for twrp . . . ( hint ) it'll tell you that the twrp team has "not" yet got adb sideload working. . We all have to be patient !
.
And the good News is . . . if you use the usb-C adapter in the box and plug in a usb-A thumb drive into the pixel when running twrp . . . . you can see and grab stuff off that thumb drive. . . . . it worked for me 1

superbean83 said:
Code:
c:\adb>fastboot flash boot bl.img
Sending 'boot_a' (8489 KB) OKAY [ 0.310s]
Writing 'boot_a' (bootloader) Flashing Pack version b1c1-0.1-5034669
FAILED (remote: '(boot_a) No such partition')
Finished. Total time: 0.564s
thats what it doesn when i try to flash boot image
Click to expand...
Click to collapse
You need to flash the boot.img not the bootloader.

superbean83 said:
thats what it doesn when i try to flash boot image
Click to expand...
Click to collapse
Fastboot flash boot --slot all boot.img

airmaxx23 said:
You need to flash the boot.img not the bootloader.
Click to expand...
Click to collapse
Do you have the latest sdk platform tools?
Sent from my [device_name] using XDA-Developers Legacy app

Failing install twrp in fastboot mode

I recently purchased redmi note 5 pro.
I'm using miui 10 Oero version, but I want to install recovery such as twrp for installing custom ROMs.
So, I searched for the process on the Internet.
I think that adb driver and fastboot driver are installed well in my PC (Window 10) .
That's because I can control my phone in adb mode.
I can find my phone in "adb devices" command and reboot it in "adb reboot bootloader" command
Also, I can find my phone by entering "fastboot devices" in fast mode, which shows the same serial number as that in adb mode.
However, I cannot flash or boot using downloaded twrp.img in fastboot mode, showing as follows.
=======================================
>fastboot boot twrp.img
downloading 'boot.img'
FAILED (command write failed (Invalid argument))
finished. total time: 0.016s
=======================================
I also used "fastboot flash recovery twrp.img" the command, but there is no response.
Could anyone tell me the solution for this problem? :crying:

You have to unlock bootloader as well

Bricked? Bootloop to TWRP > Stuck on TWRP Logo > Fastboot not recognized > No way out?

Hope you guys can give me a hand and get me out of this situation...
What I am using
Xiaomi Redmi Note 5 Pro with:
- Pixel Experience Rom
- TWRP 3.5.2_9
Windows 10 21H1 x64
What happend
- Updating Pixel Experience Rom failed
Downloaded update
Booted into Recovery (battery 85%)
Recovery stuck on Logo
After 30m I tried to reboot to system (thinking update failed or never started)
Reboot in to Recovery
Stuck on Logo
What I tried
- I tried XiaomiFastBootADBTools (latest version)
Device is recognized in Recovery mode
In recovery I can't do anything
Rebooting to System from here results in reboot into Recovery
Booting to fastboot works, but device is not recognized
Re-installed drivers, but no luck
Still recognized in Recovery mode
Still NOT recognized in Fastboot mode
Windows Device Manager > The drivers for this device are not installed. (Code 28)
And turning of phone is not possible, just goes back to Recovery
Don't know what else to do. I have installed all the drivers I could find. Even used Snappy Driver, but nothing seems to do the trick when the phone goes into Fastboot mode. PC just doesn't recognize it.
So can't do anything in Recovery mode; just watching the TWRP logo.
And device is not recognized in fastboot mode; forgot usb debugging?
And can't boot into system to change that, because of bootloop to Recovery.
So, am I **** out of luck and bricked my phone?

While in Recovery mode (when the phone is still recognized) type in adb window the command - adb reboot bootloader. Phone should boot to Fastboot mode and see if it's still recognized.

zaqm said:
While in Recovery mode (when the phone is still recognized) type in adb window the command - adb reboot bootloader. Phone should boot to Fastboot mode and see if it's still recognized.
Click to expand...
Click to collapse
Yeah, that works. Same as with XiaomiADBFastbootTools. But after that the problem starts (remains).
When I get into Fastboot the Device Manager shows the phone as Other Devices > Android with an exclamation mark and the message that the drivers are not installed. I'm missing a driver, but I don't know which one. Guessing Xiaomi USB driver? Finally fixed that issue with another round of googling. I read that you just need net "Mi unlock Tool". So tyring to find that one:
- https://en.miui.com/unlock/download_en.html
results in a download that doesn't contain the files needed.... No driver_install and no miflash_unlock.exe etc.
pretty weird, found another page https://c.mi.com/thread-2262302-1-0.html with previous versions
- 4.5.813.51 won't download... really xiaomi, your site sucks.
- 4.5.707.49 finally downloads and seems to work.
So updated the driver by pointing to that folder. Worked like a charm.
Opening Minimal ADB and Fastboot (XiaomiADBFastboottools didn't recognize phone once in fastboot).
- adb reboot bootloader > success
- fastboot flash recovery 'recovery_file_location' > error
target reported max download size of 536870912 bytes
sending 'recovery' (47140 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Tried both latest TWRP and Orangefox. Same message each time.
Tried an older/smaller TWRP 3.3.1 and got a different but still similar message
target didn't report max-download-size
sending 'recovery' (38924 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Tried it with Platform-Tools
- adb reboot bootloader
- fastboot boot 'recovery_file_location'
Which results in
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
OR
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
AND eventually
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
2 hours in, calling it a day for now.

FlashyDuck said:
Yeah, that works. Same as with XiaomiADBFastbootTools. But after that the problem starts (remains).
When I get into Fastboot the Device Manager shows the phone as Other Devices > Android with an exclamation mark and the message that the drivers are not installed. I'm missing a driver, but I don't know which one. Guessing Xiaomi USB driver? Finally fixed that issue with another round of googling. I read that you just need net "Mi unlock Tool". So tyring to find that one:
- https://en.miui.com/unlock/download_en.html
results in a download that doesn't contain the files needed.... No driver_install and no miflash_unlock.exe etc.
pretty weird, found another page https://c.mi.com/thread-2262302-1-0.html with previous versions
- 4.5.813.51 won't download... really xiaomi, your site sucks.
- 4.5.707.49 finally downloads and seems to work.
So updated the driver by pointing to that folder. Worked like a charm.
Opening Minimal ADB and Fastboot (XiaomiADBFastboottools didn't recognize phone once in fastboot).
- adb reboot bootloader > success
- fastboot flash recovery 'recovery_file_location' > error
target reported max download size of 536870912 bytes
sending 'recovery' (47140 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Tried both latest TWRP and Orangefox. Same message each time.
Tried an older/smaller TWRP 3.3.1 and got a different but still similar message
target didn't report max-download-size
sending 'recovery' (38924 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Tried it with Platform-Tools
- adb reboot bootloader
- fastboot boot 'recovery_file_location'
Which results in
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
OR
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
AND eventually
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
2 hours in, calling it a day for now.
Click to expand...
Click to collapse
What about trying to flash latest fastboot rom with MiFlash since fastboot now works?

Absolutely awesome! We did it!
I'm no expert in all this, so I had to use a guide to flash a fastboot rom with the Mi Flash Tool. I used this guide: https://www.thecustomdroid.com/install-miui-fastboot-rom-using-miflash-tool-xiaomi/
That was all straight forward untill I came to step 6; flashing the actual rom with the Mi Flash Tool.
The tool just wouldn't recognize my phone when in Fastboot mode. Even after the driver install popup.
- after pressing refresh phone disconnected.
- tried 3 different usb ports (read online that this could be the issue)
- tried 3 different cables...
The third cable (Ugreen cable) worked! Although it only worked on a usb 3.0 port strangely enough.
I used the "clean all" option and flashed the latest MIUI global fastboot rom for the RMN5.
Flashing process was a bit strange, because the tool didn't provide me with the same information shown in the guide, but it flashed a couple of things to 100% completeness and after that it kept counting up and showing $pause. Not much later the phone started to boot into MIUI and everything was normal.
Enabled dev options and usb debugging.
Re-flashed latest twrp recovery just to be sure.
And it's all working fine again.
Really, thank you for your help! It's much appreciated!

FlashyDuck said:
Absolutely awesome! We did it!
I'm no expert in all this, so I had to use a guide to flash a fastboot rom with the Mi Flash Tool. I used this guide: https://www.thecustomdroid.com/install-miui-fastboot-rom-using-miflash-tool-xiaomi/
That was all straight forward untill I came to step 6; flashing the actual rom with the Mi Flash Tool.
The tool just wouldn't recognize my phone when in Fastboot mode. Even after the driver install popup.
- after pressing refresh phone disconnected.
- tried 3 different usb ports (read online that this could be the issue)
- tried 3 different cables...
The third cable (Ugreen cable) worked! Although it only worked on a usb 3.0 port strangely enough.
I used the "clean all" option and flashed the latest MIUI global fastboot rom for the RMN5.
Flashing process was a bit strange, because the tool didn't provide me with the same information shown in the guide, but it flashed a couple of things to 100% completeness and after that it kept counting up and showing $pause. Not much later the phone started to boot into MIUI and everything was normal.
Enabled dev options and usb debugging.
Re-flashed latest twrp recovery just to be sure.
And it's all working fine again.
Really, thank you for your help! It's much appreciated!
Click to expand...
Click to collapse
Glad that it worked out. Sometimes even the most untraditional methods work like usb 3.0 and the third cable.
Still all went good and that's the good news. Enjoy

--double, woops--

zaqm said:
Glad that it worked out. Sometimes even the most untraditional methods work like usb 3.0 and the third cable.
Still all went good and that's the good news. Enjoy
Click to expand...
Click to collapse
Unfortunately, the problem has returned.
The first time flashing Orange Fox Recovery was no problem. I could boot to Recovery. I installed Pixel Experience Plus again. That all worked fine.
Today I wanted to try out ArrowOS. And this is what I did:
- loaded the .zip file on the phone
- turned off the phone
- booted into recovery
- stuck on recovery logo screen...
- after this the phone bootloops to recovery again as before...
In Recovery and Fastboot the phone is still recognized by the PC. But in Recovery I can't do anything.
So in Fastboot mode I tried re-flashing Orange Fox , but same result. Flashing seems successful but can't get past the Recovery logo. I even tried flashing TWRP, but also same result.
I can probably redo all the steps in my previous post, but once I boot to recovery the phone is done for it seems.
Any ideas?

FlashyDuck said:
Unfortunately, the problem has returned.
The first time flashing Orange Fox Recovery was no problem. I could boot to Recovery. I installed Pixel Experience Plus again. That all worked fine.
Today I wanted to try out ArrowOS. And this is what I did:
- loaded the .zip file on the phone
- turned off the phone
- booted into recovery
- stuck on recovery logo screen...
- after this the phone bootloops to recovery again as before...
In Recovery and Fastboot the phone is still recognized by the PC. But in Recovery I can't do anything.
So in Fastboot mode I tried re-flashing Orange Fox , but same result. Flashing seems successful but can't get past the Recovery logo. I even tried flashing TWRP, but also same result.
I can probably redo all the steps in my previous post, but once I boot to recovery the phone is done for it seems.
Any ideas?
Click to expand...
Click to collapse
Hmm, I don't know why is that happening. It's usually the custom recovery's fault in such case except if Pixel rom comes with its own prebuilt recovery that overwrites the one you installed.
I suggest you first to try to boot into system to see if it will work - in fastboot mode type the command fastboot reboot.
If this doesn't work then flash again fastboot rom to get the phone in working condition and after installing twrp FORMAT DATA in twrp Wipe section. Then install rom again.
Good luck, zaqm!

zaqm said:
Hmm, I don't know why is that happening. It's usually the custom recovery's fault in such case except if Pixel rom comes with its own prebuilt recovery that overwrites the one you installed.
I suggest you first to try to boot into system to see if it will work - in fastboot mode type the command fastboot reboot.
If this doesn't work then flash again fastboot rom to get the phone in working condition and after installing twrp FORMAT DATA in twrp Wipe section. Then install rom again.
Good luck, zaqm!
Click to expand...
Click to collapse
It worked!
Don't know why, but it's working. Here's what I did:
- In Fastboot Mode > fastboot reboot > booted to recovery, so no luck there
- Used MiFlash to flash the fastboot rom again (clean all)
- Setup the phone etc. and activated usb debugging
- Flashed TWRP
- Booted to TWRP
- Format Data
- Rebooted to TWRP
- Mounted Storage, uploaded ArrowOS.zip and installed it
- Wiped Dalvik/Cache
- Booted ArrowOS, and success!
Have done several reboots to (and from) system/recovery and it just works again, as it should.
I think the Format Data in TWRP did the trick. I remember in Orange Fox this all was a bit unclear; I'm just not used to Orange Fox, always used TWRP. So my bad for not correctly flashing the rom probably.
Again, thank you very much for your help! Have a great day! And let's hope this is the end of this issue haha.

FlashyDuck said:
It worked!
Don't know why, but it's working. Here's what I did:
- In Fastboot Mode > fastboot reboot > booted to recovery, so no luck there
- Used MiFlash to flash the fastboot rom again (clean all)
- Setup the phone etc. and activated usb debugging
- Flashed TWRP
- Booted to TWRP
- Format Data
- Rebooted to TWRP
- Mounted Storage, uploaded ArrowOS.zip and installed it
- Wiped Dalvik/Cache
- Booted ArrowOS, and success!
Have done several reboots to (and from) system/recovery and it just works again, as it should.
I think the Format Data in TWRP did the trick. I remember in Orange Fox this all was a bit unclear; I'm just not used to Orange Fox, always used TWRP. So my bad for not correctly flashing the rom probably.
Again, thank you very much for your help! Have a great day! And let's hope this is the end of this issue haha.
Click to expand...
Click to collapse
Maybe some glitch of OrangeFox recovery and yeah, let's hope that this issue won't appear anymore.
All the best, zaqm!