Develop Bugs

Fastboot issues.

So through a series of attempts to root the latest MM software ive found myself with nothing but fastboot to boot into, but whenever i try to use a command such as boot for example i get:
C:\android>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.560s]
booting...
And it just hangs at booting forever. It does this every command. If i unplug the phone i get:
FAILED (status read failed (Too many links))
Any idea why it's doing this?
I'm on windows 7 with the drivers for my device along with google drivers installed. I've tried two different computers with the same results.

boho555 said:
So through a series of attempts to root the latest MM software ive found myself with nothing but fastboot to boot into, but whenever i try to use a command such as boot for example i get:
C:\android>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.560s]
booting...
And it just hangs at booting forever. It does this every command. If i unplug the phone i get:
FAILED (status read failed (Too many links))
Any idea why it's doing this?
I'm on windows 7 with the drivers for my device along with google drivers installed. I've tried two different computers with the same results.
Click to expand...
Click to collapse
Do you have access to download mode?if yes, flash back to kit Kat.bit If you are stuck at this Fastboot,you are left with only option of getting to Qualcomm 9008 mode.and flash from that.because this Fastboot fail has no solution.

Jahanzaibawan said:
Do you have access to download mode?if yes, flash back to kit Kat.bit If you are stuck at this Fastboot,you are left with only option of getting to Qualcomm 9008 mode.and flash from that.because this Fastboot fail has no solution.
Click to expand...
Click to collapse
Thanks, I'll try the qualcom fix.

Fastboot stuck, no recovery

Hello,
i have big problem wiht my D855. I'm trying to install recovery on my device via fastboot, because flashify method failed resulting in lack of recovery on my phone... When i enter "the place where recovery should be" boot certification error shows up and the only way to get rid of it is to re-insert the battery. Unfortunatelly fastboot is not working somehow. Command where it stuck while flashing says:
Code:
C:\adb\fastboot flash recovery reco.img
target reported max download size of 214743648 bytes
sending 'recovery' (15382 KB)...
OKAY [ 0.557s]
writing 'recovery'...
device:
Code:
[132740] fastboot: flash:recovery
Ive been already waiting about 40 minutes for this process to continue but of course nothing happened. After removing USB cable it says:
Code:
FAILED (status read failed (Too many links))
finished. total time: 649.362s
Other commands also do not work, they crash almost the same way but with sh.. i called "three dot bug"
Code:
C:\Users\Dom\Desktop\2>fastboot flashing unlock
...
It even dont reboot after typing:
Code:
C:\Users\Dom\Desktop\2>fastboot reboot-bootloader
rebooting into bootloader...
I have tried different cables, USB ports, different PC. I have lates LG drivers installed. What can I do. My OS is running but has many issues like not working wifi, crashing camera or random reboots (on new battery), so I cant use this phone anymore. It is impossible to revert it back to factory because recovery, which is used for this process is not working, so do fastboot...
Please help, I'm not android expert (and poor english user).
Cheers

Flash the latest TWRP onto it, it should let you boot. I had this problem a few days ago on a samsung tablet. I used odin on that. But you are going to have to match up the TWRP version and the android version you are running.
If you get TWRP working you wont have any problems, you can fix everything from there. Flash fulmics, unroot, what ever you want. Wipe the whole device ect. Make your goal trying to get TWRP on it.

Well, the problem is that I'm trying to flash TWRP now, it is the "reco.img" file, because I was trying to resolve the recovery instalation problem by changing name of file, which could be a problem somehow.
I found adb method to flash recovery:
Code:
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/yourrecovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Will it work? ADB is working fine, I already tried similar method when removing and reinstalling laf.

can't unlock bootloader

Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2​) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.

amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2​) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Just a shot in the dark but have you enabled oem unlocking in developer options?

Xceeder said:
Just a shot in the dark but have you enabled oem unlocking in developer options?
Click to expand...
Click to collapse
no unfortunately not , thats the problem

amans90 said:
no unfortunately not , thats the problem
Click to expand...
Click to collapse
Okay well I hope you can get your phone sorted now , if I've helped then please leave a thumbs up on my post I really appreciate it...

amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2​) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Hi i have the same problem like you did you solve it ?

Dsn Fouad said:
Hi i have the same problem like you did you solve it ?
Click to expand...
Click to collapse
see below.
Xceeder said:
Just a shot in the dark but have you enabled oem unlocking in developer options?
Click to expand...
Click to collapse

Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Sent from my ONEPLUS A3003 using Tapatalk

n1kos said:
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Click to expand...
Click to collapse
I dont know i flashed the lastest os and the old with sideload but it stuck on 45%

n1kos said:
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Click to expand...
Click to collapse
Here

Dsn Fouad said:
Here
Click to expand...
Click to collapse
You are trying to flash TWRP with a locked bootloader and it obviously fails. Download the full official ROM from OnePlus site and the corresponding recovery also. First flash the recovery and reboot to bootloader and then flash the OS and reboot. If you are successful, you can enable Developer Options and from there OEM unlock and USB debugging. Thereafter you can try TWRP, Magisk and other ROMs.

Hmm, I thought he said he can enter bootloader and recovery. If so, reboot the phone in stock recovery and flash full Rom from local update.
Sent from my ONEPLUS A3003 using Tapatalk

tnsmani said:
You are trying to flash TWRP with a locked bootloader and it obviously fails. Download the full official ROM from OnePlus site and the corresponding recovery also. First flash the recovery and reboot to bootloader and then flash the OS and reboot. If you are successful, you can enable Developer Options and from there OEM unlock and USB debugging. Thereafter you can try TWRP, Magisk and other ROMs.
Click to expand...
Click to collapse
You mean flash twrp in fastboot and stock rom in recovery adb sideload i tried all of that i downloaded the lastest stock and lastest twrp it fails it's okay thanks for everything im just going to sell it, it's completely bricked because of that oem and usb debugging locked small things can be dangerous.

Dsn Fouad said:
You mean flash twrp in fastboot and stock rom in recovery adb sideload i tried all of that i downloaded the lastest stock and lastest twrp it fails it's okay thanks for everything im just going to sell it, it's completely bricked because of that oem and usb debugging locked small things can be dangerous.
Click to expand...
Click to collapse
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb and boot.

tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
Oh i see now where can i find the lastest recovery and by how i need to flash it, in adb sideload (recovery.img) or fastboot flash recovery (oneplus recovery.img)?

tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
I tried again but failed with official oneplus 3 recovery

Dsn Fouad said:
I tried again but failed with official oneplus 3 recovery
Click to expand...
Click to collapse
Here

Dsn Fouad said:
I tried again but failed with official oneplus 3 recovery
Click to expand...
Click to collapse
Here

tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
...

amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2​) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Make sure you are using the latest version of adb and fastboot, had some trouble myself with this:
https://developer.android.com/studio/releases/platform-tools

jeffrey268 said:
Make sure you are using the latest version of adb and fastboot, had some trouble myself with this:
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Nah it will still fail, all because of that oem and device state locked, lol i buy a new phone used it 1 month i was having a update available i updated it and then boom 370€ gone just like that, it took me 4 month to got it, i just want to kill people now im very depressed right now god bless people like you thanks for your help.

[Q] Can't get bootloader unlocked?

I've got the lastest sdk tools and google usb driver installed and still get a fail when trying to run fastboot flashing unlock. I also have allow oem unlocking checked. Is there something I'm missing?
C:\Android>adb reboot bootloader
C:\Android>fastboot devices
7xxxxxxxxxxxx5 fastboot
C:\Android>fastboot flashing unlock
...
FAILED (command write failed (No error))
finished. total time: 0.003s

xxnirvana69xx said:
I've got the lastest sdk tools and google usb driver installed and still get a fail when trying to run fastboot flashing unlock. I also have allow oem unlocking checked. Is there something I'm missing?
C:\Android>adb reboot bootloader
C:\Android>fastboot devices
7xxxxxxxxxxxx5 fastboot
C:\Android>fastboot flashing unlock
...
FAILED (command write failed (No error))
finished. total time: 0.003s
Click to expand...
Click to collapse
sorry delete!!! try fastboot flashing unlock_critical

lucky_strike33 said:
did you go to developer and tick on to unlock bootloader?
Click to expand...
Click to collapse
Sure did. OEM unlocking is ticked.

lucky_strike33 said:
sorry delete!!! try fastboot flashing unlock_critical
Click to expand...
Click to collapse
Same thing.
C:\Android>fastboot devices
7xxxxxxxxxxxxxxxx5 fastboot
C:\Android>fastboot flashing unlock_critical
...
FAILED (command write failed (No error))
finished. total time: 0.003s

xxnirvana69xx said:
Same thing.
C:\Android>fastboot devices
7xxxxxxxxxxxxxxxx5 fastboot
C:\Android>fastboot flashing unlock_critical
...
FAILED (command write failed (No error))
finished. total time: 0.003s
Click to expand...
Click to collapse
Try a different cable?

Unfortunately I am at work and only have the C to C cable that was in the box.

My sdk/platform tools files are the same ones I've used with my 6P since 11-2015, and unlocking the 2 XL bl worked on the first attempt.
my process:
pow button + vol down
open cmd prompt in platform tools folder
fastboot devices (recognized my device)
fastboot flashing unlock
use vol up to select UNLOCK MY BOOTLOADER
power, to confirm
erases everything,
restarts
profit

Az Biker said:
My sdk/platform tools files are the same ones I've used with my 6P since 11-2015, and unlocking the 2 XL bl worked on the first attempt.
my process:
pow button + vol down
open cmd prompt in platform tools folder
fastboot devices (recognized my device)
fastboot flashing unlock
use vol up to select UNLOCK MY BOOTLOADER
power, to confirm
erases everything,
restarts
profit
Click to expand...
Click to collapse
Tried with a slightly older version I had for my og pixel and it worked. Wonder what was up with the other version.

xxnirvana69xx said:
Tried with a slightly older version I had for my og pixel and it worked. Wonder what was up with the other version.
Click to expand...
Click to collapse
I have the latest adb and fastboot files and can not get my device to be recognized by adb can anyone help me with this?

canemaxx said:
I have the latest adb and fastboot files and can not get my device to be recognized by adb can anyone help me with this?
Click to expand...
Click to collapse
Pm instead

xxnirvana69xx said:
Found this to possibly get you an older version of the platform tools...
"Well, you could use direct link, like
Click to expand...
Click to collapse
I started off with what I was using with my pixel XL and that didn't work and I have installed about 10 different version thus far and still nothing

I basically ended up using another cable, different version of adb, and another computer. Hard to tell what the problem exactly was since I changed 3 things at the same time between it not working and working. My guess is the cable and/or the computer.

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!