Develop Bugs

Stuck in Fastboot/No Download Mode

Hey guys !
So since i messed up with the recovery mode, i'm stucked in the fastboot with no Download mode (recovery doesnt work neither).
So after searching 3 days in the internet i found the acces to fast through adb by puting a new laf.img in order to restore the download mode and flash a stock firmware !
My problem is that when i try to enter the command on the cmd, i get severals errors, take a look :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device not found
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase laf
erasing 'laf'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.034s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash laf laf.img
target reported max download size of 2147483648 bytes
sending 'laf' (18432 KB)...
OKAY [ 0.581s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.615s
Also command : "fastboot boot laf.img" result to "Failed(remote: dtb not found) instead of flash write failure..
Of course i have my G3 855 32GB in download mode (but it goes into fastmode), so when i try a command, lines are added in the screen etc..
Does that mean that my laf.img don't work? I assumed that so i try several, but does it have to be the exact same one as the one who was in my phone before( v20a if i record correctly ) or could it be from any 855 32GB version ?
I also thought it could be a recognition problem as when i type "adb devices" or "adb shell" nothing is found..
If someone has any clue or a link to some guide i'll be more than joyful, thanks in advance !

Try adb fastboot when writing command hope it helps

Anik49 said:
Try adb fastboot when writing command hope it helps
Click to expand...
Click to collapse
Hey thank you so much for answering !
What do you mean by that, i already download the adb/fastboot driver and launch a cmd in the directory they are at, writing "adb fastboot" has no result neither, can you be more specific please ?

cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again: http://open-freax.fr/guide-unbrick-your-lg-g3/

BigsyBiggins said:
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again:
Click to expand...
Click to collapse
Well i hope my problem can be solved in a safer way, i dont like much to go on the hardware part, so I'll use it as my last hope, but thanks
Altought i think my device is recognized by fastboot in someway because it responds when i type commands in fastboot, and also when i reboot it.
But i'm getting this error :
Code:
error : command never completed
error : auto CMD12 error
error : command completed with errors
error : command timeout error
failed to send stop command
failed writing block @ 1
in the screen of my phone. Does that stand for Cyanogen mode which i was trying to put on my phone ?

I mean when you enter command in cmd use adb before any command also use cmd which one available on android sdk folder....also you can use this method if adb not workinhg properly http://forum.xda-developers.com/lg-g...-9008-t3072091

BigsyBiggins said:
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again: http://open-freax.fr/guide-unbrick-your-lg-g3/
Click to expand...
Click to collapse
Like @BigsyBiggins said, this is the guide which could fix your phone. HW Part is not too hard!

Anik49 said:
I mean when you enter command in cmd use adb before any command also use cmd which one available on android sdk folder....also you can use this method if adb not workinhg properly
Click to expand...
Click to collapse
Oh ok ! Also your link is not working :s
I understand that the method can work but I think that the method i'm trying to use is really close to succeed, over my search on the internet, i saw lots of people who manage to succeed with it.
But i guess i must do something wrong. I downloaded the kdz file according to my IMEI.
Then I extracted the .dz file with LG Firmware Extract. Then I extracted the file named laf_393216.bin from the dz file. Changed his name into laf.img , put it into the fastboot directory.
Then i typed
Code:
fastboot format cache
fastboot erase laf
fastboot flash laf laf.img
in a cmd from the directory.
It all seemed to work, but then when i remove the battery and restart into download mode, it goes into fastboot after the download mode charging animation..
Also when i try to boot with fastboot boot laf.img i get the error (remote: dtb not found) on the cmd.
And ERROR: Unable to find suitable device tree for device(194/0x0001001/112/0) ERROR: getting device tree adress failed DTB offset is incorrect, kernel image does not have appended DTB)
Am I doing something wrong, should I changed more file than just laf ?

SisGG said:
Oh ok ! Also your link is not working :s
I understand that the method can work but I think that the method i'm trying to use is really close to succeed, over my search on the internet, i saw lots of people who manage to succeed with it.
But i guess i must do something wrong. I downloaded the kdz file according to my IMEI.
Then I extracted the .dz file with LG Firmware Extract. Then I extracted the file named laf_393216.bin from the dz file. Changed his name into laf.img , put it into the fastboot directory.
Then i typed
Code:
fastboot format cache
fastboot erase laf
fastboot flash laf laf.img
in a cmd from the directory.
It all seemed to work, but then when i remove the battery and restart into download mode, it goes into fastboot after the download mode charging animation..
Also when i try to boot with fastboot boot laf.img i get the error (remote: dtb not found) on the cmd.
And ERROR: Unable to find suitable device tree for device(194/0x0001001/112/0) ERROR: getting device tree adress failed DTB offset is incorrect, kernel image does not have appended DTB)
Am I doing something wrong, should I changed more file than just laf ?
Click to expand...
Click to collapse
I don´t know what exactly is the problem, maybe something with your win-driver, some crashed or drifted partitions or some broken files...
I just can repeat my advice: I was in the same situation with my phone after a failed cm13 update and i was trying and reading about 2 days how to solve it - after the above mentioned method, your phone would get out of this "coma".
Maybe somebody else here in this forum could help you with your mentioned method, sorry.

Ernesto0023 said:
I don´t know what exactly is the problem, maybe something with your win-driver, some crashed or drifted partitions or some broken files...
I just can repeat my advice: I was in the same situation with my phone after a failed cm13 update and i was trying and reading about 2 days how to solve it - after the above mentioned method, your phone would get out of this "coma".
Maybe somebody else here in this forum could help you with your mentioned method, sorry.
Click to expand...
Click to collapse
Well I think i'm still under warranty, so i dont wanna touch to much on the hardware.
So do you think, if i send it back without touching anything, saying i put it on charge one night and the next morning it was like this, the warranty could work?

If they found it's rooted or they understand you did something with your software your warrenty is void ?

SisGG said:
Well i hope my problem can be solved in a safer way, i dont like much to go on the hardware part, so I'll use it as my last hope, but thanks
Altought i think my device is recognized by fastboot in someway because it responds when i type commands in fastboot, and also when i reboot it.
But i'm getting this error :
Code:
error : command never completed
error : auto CMD12 error
error : command completed with errors
error : command timeout error
failed to send stop command
failed writing block @ 1
in the screen of my phone. Does that stand for Cyanogen mode which i was trying to put on my phone ?
Click to expand...
Click to collapse
Remove the battery, put it, press the volume + and connect to PC USB, if like entering download, what happens to us not to go, will leave the ****ing LoGo, Well, hold down the volume + and not let go, I think it is less for 2 minutes more. After a while, the computer tells us that something was connected, the phone will tell you who is in fastboot as I said before, if not let me fastboot flash boot files and the LAF, recovery ect, nothing happens, there is still a magic command.
fastboot boot laf.img
Keep it in the ****ing heart

miguexneox said:
Remove the battery, put it, press the volume + and connect to PC USB, if like entering download, what happens to us not to go, will leave the ****ing LoGo, Well, hold down the volume + and not let go, I think it is less for 2 minutes more. After a while, the computer tells us that something was connected, the phone will tell you who is in fastboot as I said before, if not let me fastboot flash boot files and the LAF, recovery ect, nothing happens, there is still a magic command.
fastboot boot laf.img
Keep it in the ****ing heart
Click to expand...
Click to collapse
I dont quite understand what u meant there :s
I already have acces on the fastboot, actually now, my phone goes instantly on fastboot whatever i do.. Though i cannot boot a laf.img downloaded and flashed .. :'(

SisGG said:
I dont quite understand what u meant there :s
I already have acces on the fastboot, actually now, my phone goes instantly on fastboot whatever i do.. Though i cannot boot a laf.img downloaded and flashed .. :'(
Click to expand...
Click to collapse
were u able to resolve this issue. I am in your shoes at the moment.
I have tried the qualcomm. The drivers doesnt seem to work for my phone .
I can't flash or the laf.img . the fastboot commands doesnt seem to work.
and I'm stuck in fastboot .
What can be done

datrmon said:
were u able to resolve this issue. I am in your shoes at the moment.
I have tried the qualcomm. The drivers doesnt seem to work for my phone .
I can't flash or the laf.img . the fastboot commands doesnt seem to work.
and I'm stuck in fastboot .
What can be done
Click to expand...
Click to collapse
You have several options:
- find your phone firmware, extract recovery.img and flash it back through fastboot(do exactly the same for the LAF partition to restore download mode)
- flash a custom recovery for your phone model, if it doesn't work try an older version of TWRP, also it can be that your phone is not d855 but d850 model, so try to flash a d850 custom recovery and see if it works(that was exactly my problem and why i got stuck in fastboot mode, because my phone is d850 model and in settings it says d855, so I flashed wrong TWRP)

Ghikya said:
You have several options:
- find your phone firmware, extract recovery.img and flash it back through fastboot(do exactly the same for the LAF partition to restore download mode)
- flash a custom recovery for your phone model, if it doesn't work try an older version of TWRP, also it can be that your phone is not d855 but d850 model, so try to flash a d850 custom recovery and see if it works(that was exactly my problem and why i got stuck in fastboot mode, because my phone is d850 model and in settings it says d855, so I flashed wrong TWRP)
Click to expand...
Click to collapse
Thanks for the response .
I am unable to flash files at all.
This is the error
D:\mfastboot-v2>fastboot flash laf laf.img
target max-download-size: 2048MB
sending 'laf' (18432 KB)...
OKAY [ 0.646s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.726s
D:\mfastboot-v2>

datrmon said:
Thanks for the response .
I am unable to flash files at all.
This is the error
D:\mfastboot-v2>fastboot flash laf laf.img
target max-download-size: 2048MB
sending 'laf' (18432 KB)...
OKAY [ 0.646s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.726s
D:\mfastboot-v2>
Click to expand...
Click to collapse
It seems that your phone's bootloader is locked, you can try to execute this command: "fastboot oem unlock", and then check state with "fastboot oem device-info". But some people says that it does nothing, so you can try and check for yourself.
You can also try to boot directly an image from fastboot for eaxmple:
Code:
fastboot boot laf.img
or
Code:
fastboot boot twrp.img
So if you could successfully boot a laf image you would be able to access download mode, and if you could boot a custom recowery then you could access ADB and to try to flash other partitions, or even flash a custom rom...

I can't unlock bootloader on Lenovo zuk 2 plus

i can't unlock bootloader on my lenovo z2 plus.Every time i tried to flash bootloader.img in fastboot mode it shows "waiting for device"... please tell me what should i do?

Emraan01 said:
i can't unlock bootloader on my lenovo z2 plus.Every time i tried to flash bootloader.img in fastboot mode it shows "waiting for device"... please tell me what should i do?
Click to expand...
Click to collapse
Its because you don't have drivers installed properly.
I m using minimal abb and fastboot.
Install zuk usb drivers then enable usb debugging connect phone to usb.
Type in cmd
adb devices.
Give permission and tick allow always on prompt.
Then adb reboot bootloader.
Fastboot devices.
If u see your device proceed ahead otherwise install drivers properly.

Emraan01 said:
i can't unlock bootloader on my lenovo z2 plus.Every time i tried to flash bootloader.img in fastboot mode it shows "waiting for device"... please tell me what should i do?
Click to expand...
Click to collapse
if you have installed drivers properly, then this is happening due to permission issues ,
use this tool : drive.google.com/file/d/1WHHKKhs3pI4m9jNHhHmFL1fQeqtNS-3X/view
steps ;
1. click on run it will fix the permission issue (phone automatically boots to fastboot mode)
2. use fastboot provided in the tool to unlock, it should work ..

Its easy bro.mere saath bhi ho raha tha pehle ye batao ki aap computer se kar rahe ho ya laptop se .

Haider** said:
Its easy bro.mere saath bhi ho raha tha pehle ye batao ki aap computer se kar rahe ho ya laptop se .
Click to expand...
Click to collapse
Hp laptop sae

Emraan01 said:
i can't unlock bootloader on my lenovo z2 plus.Every time i tried to flash bootloader.img in fastboot mode it shows "waiting for device"... please tell me what should i do?
Click to expand...
Click to collapse
Check out your drivers, it's your drivers issue pc/laptop not detecting the phone in fastboot mode

Emraan01 said:
i can't unlock bootloader on my lenovo z2 plus.Every time i tried to flash bootloader.img in fastboot mode it shows "waiting for device"... please tell me what should i do?
Click to expand...
Click to collapse
update the drivers using pda.net

Emraan01 said:
Hp laptop sae
Click to expand...
Click to collapse
Just do it with another laptop.

Boot loader unlock issue on zui 2.5.104st naugat based os it will not unlocked properly

I can't unlock either, my devices is detected in the command window but following error occurs after the flash unlock bootloader command
Mine says 'writing unlock FAILED < remote: partition doesn't exist >'

Emraan01 said:
i can't unlock bootloader on my lenovo z2 plus.Every time i tried to flash bootloader.img in fastboot mode it shows "waiting for device"... please tell me what should i do?
Click to expand...
Click to collapse
http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/3/
follow this guide to fix driver issues on windows 10 devices. I was having this issue yesterday and manually selecting the drivers fixed my problem.
Press thanks if i helped

Unable to unlock bootloader
Hi
Boot loader unlock issue on zui 2.5.104st nugat based os it will not unlocked properly
That message will be appeared like this
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
target reported max download size of 1610612736 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.028s]
writing 'unlock'...
FAILED (remote: unlock failed)
finished. total time: 0.061s"
Any one know this issue please help me how to solve this issue
Thankyou

phanikumar07 said:
Hi
Boot loader unlock issue on zui 2.5.104st nugat based os it will not unlocked properly
That message will be appeared like this
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
target reported max download size of 1610612736 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.028s]
writing 'unlock'...
FAILED (remote: unlock failed)
finished. total time: 0.061s"
Any one know this issue please help me how to solve this issue
Thankyou
Click to expand...
Click to collapse
Did you get partition doesn't exist issue? because I got that recently

vinitharmalkar said:
Did you get partition doesn't exist issue? because I got that recently
Click to expand...
Click to collapse
How to solve it

TWRP Not Installing or booting through fastboot (MIUI 10.2.2.0)

Hello everyone
I have been trying to install TWRP through every fastboot method that I can and it is failing everytime.
Code:
PS C:\adb> fastboot devices
******** fastboot
PS C:\adb> fastboot boot twrp.img
downloading 'boot.img'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.002s
PS C:\adb> fastboot flash antirbpass dummy.img
sending 'antirbpass' (8 KB)...
FAILED (status read failed (Too many links))
finished. total time: 2.032s
PS C:\adb>
After every failed command I get 'Switch off phone using power key' on top left of the bootloader screen and I have to reboot it into bootloader again. I have also tried 'fastboot flash recovery twrp.img' but nothing happens. I had this problem with MIUI 10.2.1.0 as well so I waited for an update thinking that might solve it. My phone is unlocked, all the drivers are properly installed and I have tried all different USB ports and original Mi cable but it fails everytime.
Does anyone have any solution?
Thank you

First of all, have you unlocked your device?

Please use other USB ports and Original mi cable

Ducatuca said:
First of all, have you unlocked your device?
Click to expand...
Click to collapse
Yes, it is unlocked and I have installed TWRP before using this method lot of times on this phone.

bhimrdx said:
Please use other USB ports and Original mi cable
Click to expand...
Click to collapse
I have used every different USB port, original Mi cable and other cable as well but it doesnt work. All the drivers are properly installed as well.

pawas99 said:
Yes, it is unlocked and I have installed TWRP before using this method lot of times on this phone.
Click to expand...
Click to collapse
Are you sure you have downloaded proper twrp.img file ?? Try using other custom recovery like orange fox

I have the same problem, updated to 10.2.2.0 I can't install the twrp

uninstall your adb drivers and then install them again and reboot your pc and try to run all commands again it will work

Same Problem with MIUI 12 on POCO F1
I too get a black screen whenever i try fastboot commands. please help.

pawas99 said:
Hello everyone
I have been trying to install TWRP through every fastboot method that I can and it is failing everytime.
After every failed command I get 'Switch off phone using power key' on top left of the bootloader screen and I have to reboot it into bootloader again. I have also tried 'fastboot flash recovery twrp.img' but nothing happens. I had this problem with MIUI 10.2.1.0 as well so I waited for an update thinking that might solve it. My phone is unlocked, all the drivers are properly installed and I have tried all different USB ports and original Mi cable but it fails everytime.
Does anyone have any solution?
Thank you
Click to expand...
Click to collapse
Try usb Hub
---------- Post added at 11:03 AM ---------- Previous post was at 11:02 AM ----------
Sidgup1998 said:
Try usb Hub
Click to expand...
Click to collapse
Or Type fastboot devices hit enter, then again type the same command, if it shows like this ???????? Then try usb hub

Redmi note 5 pro stuck in bootloop and cant access to recovery please help $$

I have a Redmi Note 5 Pro from last Saturday while uploading Instagram stories as usual, the phone decided to crash. So I turned it off and back on though got stuck with MI Logo and Bootloop. The device said it's unlocked but apparently seems not to.
I CANNOT go into recovery mode.
I CANNOT flash any recovery too.
I have connected the device to my laptop (Windows 10) through fastboot try to flash any recovery: OrangeFox, TWRP, no success.
I either run a powershell or run CMD as Admin
This is the error:
c:\adb fastboot flash recovery recovery.img
Sending 'recovery' (31161 KB) OKAY [ 0.669s]
Writing 'recovery' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
So I try this command: fastboot boot recovery.img
It loads the recovery either TWRP or OrangeFox but only the Logo nothing else.
It doesn't RUN any official MIUI recovery.
So, now I can use ADB commands.
The phone is seen connected to Windows 10 as USB but I guess not MTP mode but only as charging mode.
In the "Safely Remove Hardware" section I can see the device connected and its name as Redmi Note 5 Pro.
Of course I can't see the device in the Explorer and any folder as the OS hasn't loaded at all.
Now, though, I can run ADB commands, so I typed: run devices and it says it's in recovery mode, also with the number of the device.
Then with ADB SHELL LS command
I can see the folder tree
With Push and Pull commands, I can copy folders, but cannot access and copy the content of SDCARD and STORAGE.
I know those folders are protected even though my phone should be unlocked but apparently it is not then.
It's really ridiculous that there is no a way around this.
Why, if I am the owner the unlock process have to reset phone data?
It's so stupid! They should have developed a public/private key or a long key to unlock those folder by registering your phone with SN and IMEI number.
So surprised Google and any brand don't do that.
If I connect the device in fastboot mode, I have those details:
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.006s]
Finished. Total time: 0.006s
Is there a WAY with lower level commands or software to access to data with "write protected" inside the phone memory?
I would love to recover my Whatsapp folder and my DCIM folder with every files in those.
Or the only solution is to give the Device to experts and do the CHIP Off recovery data?
Will MiFlash with a MIUI rom with save user data option actually save my data and hence Whatsapp and DCIM folder and its content inside?
Please Help!
If anyone can HELP to successfully recover my data seriously I would be more than happy to give a compensation via PayPal cause I would truly appreciated the infinite effort and help!
Thanks in advance to anyone who can sponsor the cause!
I am so pissed as the phone should be under 2 years warranty but of course no brand would cover and help you through those issues!
Such A PITY!
Kind regard,
Michael

supermike23 said:
I have a Redmi Note 5 Pro from last Saturday while uploading Instagram stories as usual, the phone decided to crash. So I turned it off and back on though got stuck with MI Logo and Bootloop. The device said it's unlocked but apparently seems not to.
I CANNOT go into recovery mode.
I CANNOT flash any recovery too.
I have connected the device to my laptop (Windows 10) through fastboot try to flash any recovery: OrangeFox, TWRP, no success.
I either run a powershell or run CMD as Admin
This is the error:
c:\adb fastboot flash recovery recovery.img
Sending 'recovery' (31161 KB) OKAY [ 0.669s]
Writing 'recovery' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
So I try this command: fastboot boot recovery.img
It loads the recovery either TWRP or OrangeFox but only the Logo nothing else.
It doesn't RUN any official MIUI recovery.
So, now I can use ADB commands.
The phone is seen connected to Windows 10 as USB but I guess not MTP mode but only as charging mode.
In the "Safely Remove Hardware" section I can see the device connected and its name as Redmi Note 5 Pro.
Of course I can't see the device in the Explorer and any folder as the OS hasn't loaded at all.
Now, though, I can run ADB commands, so I typed: run devices and it says it's in recovery mode, also with the number of the device.
Then with ADB SHELL LS command
I can see the folder tree
With Push and Pull commands, I can copy folders, but cannot access and copy the content of SDCARD and STORAGE.
I know those folders are protected even though my phone should be unlocked but apparently it is not then.
It's really ridiculous that there is no a way around this.
Why, if I am the owner the unlock process have to reset phone data?
It's so stupid! They should have developed a public/private key or a long key to unlock those folder by registering your phone with SN and IMEI number.
So surprised Google and any brand don't do that.
If I connect the device in fastboot mode, I have those details:
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.006s]
Finished. Total time: 0.006s
Is there a WAY with lower level commands or software to access to data with "write protected" inside the phone memory?
I would love to recover my Whatsapp folder and my DCIM folder with every files in those.
Or the only solution is to give the Device to experts and do the CHIP Off recovery data?
Will MiFlash with a MIUI rom with save user data option actually save my data and hence Whatsapp and DCIM folder and its content inside?
Please Help!
If anyone can HELP to successfully recover my data seriously I would be more than happy to give a compensation via PayPal cause I would truly appreciated the infinite effort and help!
Thanks in advance to anyone who can sponsor the cause!
I am so pissed as the phone should be under 2 years warranty but of course no brand would cover and help you through those issues!
Such A PITY!
Kind regard,
Michael
Click to expand...
Click to collapse
Stop with same multiple threads!!!!
It's against XDA rules.
And I gave you and answer already in other thread, please check.

drnightshadow said:
Stop with same multiple threads!!!!
It's against XDA rules.
And I gave you and answer already in other thread, please check.
Click to expand...
Click to collapse
I haven't done any multiple threads sorry!
It was my first post, I realized later on someone post something similar to mine though not really the same issue.
I will check your answer.
Thanks.

Dear have you recovered your data ! I'm in the same problem pls help me

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!