Database Users

Erased phones recovery

Hi I have the XT1570, running unlocked and with rooted but stock 5.1.1. I have run in to some issues with the recovery part.
Firstly I wanted to go back to the recovery and flash a stock recovery so I could get the OTA for MM, i did that using fastboot, and the flash worked fine according to fastboot, however once i rebooted into recovery it would not load, got an error message, I forget now something about dumping back to bootloader.
Anyway i fixed it got TWRP back on again, then tried a different stock recovery, same thing same error, so i thought I would easily get back to TWRP by the same method, flash again. I was wrong, now fastboot told me , target reported max download size of 536870912 bytes
error: cannot load 'twrp-2.8.7.1-clark': No error
Remember this is the exact same TWRP image i have just flashed not 5 mins before.
So i thought ok then, maybe an old image is in there taking up space or something.
C:\Users\David\Desktop\Mfastboot\Mfastboot>fastboot erase recovery
erasing 'recovery'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.017s]
finished. total time: 0.019s
Now I get the message:
Invalid boot image header.
Error:failed to load kernel
Boot up failed.
I presume I have deleted everything in the recovery partition, and so messed it up good, but I dont know how to fix it at this point.
I also erased the cache along the way (via fastboot) as I tried to get the OTA update to work anyway just to see what would happen, so I had to erase the cache to cancel updates
I must reiterate, I can boot into Android and use my phone no issues, at all, just I have no recovery at all and this means updates arent going to work, also i cant seem to find a reliable source for a stock recovery.
Some step by step help would be appreciated, as I am not an expert by any means on this.
Thank you.

Also my device was bought in China as that is where I am, it does indeed have the code name XT1570, dual sim, I would assume it is basically the same as the XT1572 asian. I do also have an original backup of the phone after unlocking bootloader, before root, which was my next port of call after changing the recovery back to stock.

fixed it i was just being foolish, someone delete this thread it is of no use.

Can you explain how you fixed it? I too have deleted the recovery in an attempt to flash twrp, but now neither twrp nor the stock recovery are there?
Tapatalk'd from my Twisted, Racing Nexus 5

Recovery not working

I`m having problems with booting into recovery on my OnePlus2.
This started after I did an update to OxygenOS 3.0 (beta) from my previously working TWRP.
OS itself is working, but I noticed that phone must be rerooted.. and here I found that Power + VolDown is not working anymore (phone is just stucked on 1+ logo).
OKay... I decided to reflash TWRP (who knows what may happened with it after update) but nothing helped. I tried different versions, even original OP2 recovery.. but result is always the same.
How I was trying to reflash:
Code:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (31700 KB)...
OKAY [ 0.702s]
writing 'recovery'...
OKAY [ 0.248s]
finished. total time: 0.950s
but booting is always giving DTB error:
Code:
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.713s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.781s
I saw in other posts that dtb means broken image/etc, but I tried several and all were with the same result.
What else I can try? Please note that regular booting is working with no problems. The only problem I have is booting into recovery (with buttons and with fastboot).

Posted in wrong section. Should be in Q&A.
However to answer your question.
This has the same bootloader as H2OS Marshmallow. So, please TWRP users flash the way as mentioned below. Else you won't be able to boot into old twrp.
DOWNLOADS :-
recovery.img :- https://www.androidfilehost.com/?fid=24459283995297945
Step 1 :- Clean flash the ROM with new boootloader.
Step 2 :- From TWRP,go to Install Menu,click on Images button.
Step 3 :- Select the recovery.img you just downloaded.Select Recovery.Swipe to flash.
Step 4 :- From TWRP Home,reboot to recovery.
Step 5 :- Clean flash ROM with new bootloader again.
Step 6 :- Reboot into system !!!

Thanks and sorry for the wrong section.
Can you please give a bit more info on step 1 ? what rom to flash and how (current recovery is not working) ?
taha198 said:
Posted in wrong section. Should be in Q&A.
However to answer your question.
This has the same bootloader as H2OS Marshmallow. So, please TWRP users flash the way as mentioned below. Else you won't be able to boot into old twrp.
DOWNLOADS :-
recovery.img :- https://www.androidfilehost.com/?fid=24459283995297945
Step 1 :- Clean flash the ROM with new boootloader.
Step 2 :- From TWRP,go to Install Menu,click on Images button.
Step 3 :- Select the recovery.img you just downloaded.Select Recovery.Swipe to flash.
Step 4 :- From TWRP Home,reboot to recovery.
Step 5 :- Clean flash ROM with new bootloader again.
Step 6 :- Reboot into system !!!
Click to expand...
Click to collapse

Follow guide this guide
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

Now it is clear. you gave me an instruction to what I should do to avoid the situation where I am now. but there is also another instruction how to fix my problem.
Thanks one again!
taha198 said:
Follow guide this guide
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Click to expand...
Click to collapse

It seems you are flashing the wrong version of TWRP. The version you are flashing isn't going to work on OOS 3.0 Beta. You need specifically the H2-MM TWRP 3.0.0-1 version, which, like the previous posters listed can be downloaded here:
https://www.androidfilehost.com/?fid=24459283995297945
If you are flashing a version that you downloaded direct from TWRP's website, it won't work.

I tested different versions, including 3.0.x mentioned by you. all of them gave the same result.
Btw, the recovery tool in the link above already fixed my problem.
madferretx said:
It seems you are flashing the wrong version of TWRP. The version you are flashing isn't going to work on OOS 3.0 Beta. You need specifically the H2-MM TWRP 3.0.0-1 version, which, like the previous posters listed can be downloaded here:
https://www.androidfilehost.com/?fid=24459283995297945
If you are flashing a version that you downloaded direct from TWRP's website, it won't work.
Click to expand...
Click to collapse

Delphir said:
I tested different versions, including 3.0.x mentioned by you. all of them gave the same result.
Btw, the recovery tool in the link above already fixed my problem.
Click to expand...
Click to collapse
Could you describe exactly what did you do? At the link that you mention there is 3 methods and different recovery tools.

I followed "Method 1" from the link and then flashed TWRP recovery on top of it - this way it worked with no problems. Flashing TWRP (different versions) without this recovery tool was always unsuccessful.

Well, as long as you flash the chinese HydrogenOS version of TWRP you should get a bootable recover system.
Best regards
Peter

I recently rooted my OnePlus 2.
The bootloader is unlocked.
The twrp recovery was working fine till I flashed to oxygen os 2.0.0
Now the OnePlus2 is not booting into recovery.
There is a oxygen os update (3.5.8) available which shows in the system updates section in settings.
Can I update to this without the recovery??!
Will that help to go back to twrp recovery?!
Please help

Nandish C said:
I recently rooted my OnePlus 2.
The bootloader is unlocked.
The twrp recovery was working fine till I flashed to oxygen os 2.0.0
Now the OnePlus2 is not booting into recovery.
There is a oxygen os update (3.5.8) available which shows in the system updates section in settings.
Can I update to this without the recovery??!
Will that help to go back to twrp recovery?!
Please help
Click to expand...
Click to collapse
Flashing stock firmware will overwrite twrp, so always flash OOS and twrp after it in case you want to keep it, twrp can flash the twrp.img file, not only zips, I never used OOS2 but actually you should have stock recovery back by flashing OOS, it seems that something went wrong. Just flash twrp again, like the first time you did it, if you want to go back to stock including recovery flash OOS full zip again and reboot...
Only OOS will overwrite twrp, custom roms won't
Sent from my OnePlus 2 using XDA Labs

Unable to flash TWRP (remote: dtb not found)

When I try to flash TWRP (via "fastboot flash recovery twrp.img" then "fastboot boot twrp.img") I receive the following error:
Downloading 'boot.img'
OKAY [1.477s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.534s
I've tried manually booting it into recovery with power button and volume down but it just freezes on the oneplus logo where I have to turn off and on again.
Any help is greatly appreciated!

I found the solution.
For anyone else with this problem
http://forum.xda-developers.com/showpost.php?p=66336492&postcount=3

that link just saved me!

I tried this recovery (I had the same problem as the OP) but although I can boot into twrp, I get stuck on the oneplus logo if I try a normal boot?
Sent from my Nexus 9 using XDA-Developers mobile app

I managed to get it working by flashing CM after flashing the recovery.
Sent from my Nexus 9 using XDA-Developers mobile app

Next time, correct command is the following:
Fastboot flash recovery twrp.img
You tried to flash the recovery image onto the kernel/boot partition, luckily it doesn't allow this, unless it's an actual kernel image fitting that partition. ?

pitrus- said:
Next time, correct command is the following:
Fastboot flash recovery twrp.img
You tried to flash the recovery image onto the kernel/boot partition, luckily it doesn't allow this, unless it's an actual kernel image fitting that partition. ?
Click to expand...
Click to collapse
Actually, fastboot boot twrp.img boots the TWRP image without flashing it.
fastboot flash recovery twrp.img flashes the TWRP image to the recovery partition.
Both are valid commands and have their uses.
fastboot flash boot twrp.img would be the command to try to flash the recovery image to the boot partition and shouldn't be used.

Spannaa said:
fastboot flash boot twrp.img would be the command to try to flash the recovery image to the boot partition and shouldn't be used.
Click to expand...
Click to collapse
That's exactly what I meant to convey.

Similar problem while flashing recovery
hi,
After OOS3.0 installation my OP2`s recovery is not working. i tried installing it again and it shows the error :
FAILED <data Transfer failure <unknown error>>
Please help

bhanuodin said:
hi,
After OOS3.0 installation my OP2`s recovery is not working. i tried installing it again and it shows the error :
FAILED <data Transfer failure <unknown error>>
Please help
Click to expand...
Click to collapse
Are you sure you flashed the correct OOS3 bootloader compatible version of TWRP? Latest official 3.0.0-2 should be compatible.

pitrus- said:
Are you sure you flashed the correct OOS3 bootloader compatible version of TWRP? Latest official 3.0.0-2 should be compatible.
Click to expand...
Click to collapse
how do i flash a bootloader? problem is that i am unable to flash/write on recovery partition. every time it gives the same error mentioned above.

bhanuodin said:
how do i flash a bootloader? problem is that i am unable to flash/write on recovery partition. every time it gives the same error mentioned above.
Click to expand...
Click to collapse
The bootloader (also called fastboot) comes with the original ROM. In your case you're already on the newer bootloader since you flashed OOS3 which means you will have to flash recoverys and ROMs compatible with this newer bootloader.
This TWRP should be compatible
https://dl.twrp.me/oneplus2/twrp-3.0.2-1-oneplus2.img.html
Also you can't run ROMs not compatible with this newer bootloader (which means pretty much any ROM that's not using the official Cyanogenmod source tree for building). That is except for OOS3 or newest HOS of course since these are made for the newer bootloader.
However I would say the error message you get might be caused by bad cable, faulty driver setup, faulty fastboot tool version or in worst case damaged partition layout on phone. The last one can be fixed by the Qualcomm OOS2 factory restore solution.

Hi, i am having the same problem.
some background: I was on Oxygen OS 2.x.x, i wanted to upgrade to Exodus 6. I had the older version of TWRP. So I tryed to install the new twrp image within twrp. When i rebooted i couldnt boot into twrp, receiving the same error message as in OP title, when using fastboot.
Using the tool all in one toolkit I was able to flash stock recovery.
But I still cant flash Twrp.
I can still boot into system though.
Any advice? Thanks.

That explains why you're having problems. You're doing it the wrong way.
First you must upgrade the bootloader by either flashing the convert to Marshmallow zip file which also installs the correct TWRP for the new bootloader (easiest way). Or you could flash the latest official OOS3, then fastboot flash the latest TWRP and from there format system and flash the ROM that's using the newer bootloader.

Does that Link work with oneplus x also? Having same problem as Higgings when trying to install twrp and cyanogenmod.

thnx a lot for sharing
:good:
Higgings said:
I found the solution.
For anyone else with this problem
http://forum.xda-developers.com/showpost.php?p=66336492&postcount=3
Click to expand...
Click to collapse

OnePlus 2 Permanently Screwed???

So I've been sick of the freezing and glitches of the stock non-rooted OnePlus 2. So I decided to root and install custom ROM. All went well, unlocked bootloader and installed TWRP, then installed ROM. Easy, or so I thought...
The ROM I selected I ended up not liking, so I wiped and tried to install another, which failed in TWRP. I went to flash yet another ROM and while wiping, accidentally wiped entire SDCard. With ADB side load I loaded the Oxygen 3.0 Beta onto my device (which is now how I am typing to you).
The Beta OS somehow corrupted my TWRP recovery and now no longer boots. I tried following many DIY articles on restoring my recovery. But now my bootloader is locked and will not unlock, so I tried the DIY Qualcomm Diagnosis recovery, which doesn't work. I disable windows driver signing, then plug in the device, enter Qualcomm mode, and attempt to install the drivers. They don't work, Windows 8.1 tells me they are already up to date. So I uninstall the device via Device Manager and attempt to reinstall Qualcomm driver, which fails again. Somehow Windows 8.1 assumes again that the now unrecognizable USB device is up to date.
I use my phone for work purposes. It's working so I'm not in any rush, but the only way to boot my device now is to use Windows to issue the command: fastboot continue
I'm extremely irritated with this device. Someone please help before I buy a Nexus and take this POS outback with my handgun, lol

wallacengineering said:
So I've been sick of the freezing and glitches of the stock non-rooted OnePlus 2. So I decided to root and install custom ROM. All went well, unlocked bootloader and installed TWRP, then installed ROM. Easy, or so I thought...
The ROM I selected I ended up not liking, so I wiped and tried to install another, which failed in TWRP. I went to flash yet another ROM and while wiping, accidentally wiped entire SDCard. With ADB side load I loaded the Oxygen 3.0 Beta onto my device (which is now how I am typing to you).
The Beta OS somehow corrupted my TWRP recovery and now no longer boots. I tried following many DIY articles on restoring my recovery. But now my bootloader is locked and will not unlock, so I tried the DIY Qualcomm Diagnosis recovery, which doesn't work. I disable windows driver signing, then plug in the device, enter Qualcomm mode, and attempt to install the drivers. They don't work, Windows 8.1 tells me they are already up to date. So I uninstall the device via Device Manager and attempt to reinstall Qualcomm driver, which fails again. Somehow Windows 8.1 assumes again that the now unrecognizable USB device is up to date.
I use my phone for work purposes. It's working so I'm not in any rush, but the only way to boot my device now is to use Windows to issue the command: fastboot continue
I'm extremely irritated with this device. Someone please help before I buy a Nexus and take this POS outback with my handgun, lol
Click to expand...
Click to collapse
Did you try the FirstAid kit ?

As far as I know, with OOS3 beta, it uses a different firmware which causes the official TWRP to not boot. I believe you have to use a customized version of TWRP (should be somewhere on XDA or OP Forums) with OOS3. You should be able to flash that version of TWRP. Then, reboot into TWRP, flash OOS2, and then the official TWRP from within the custom TWRP. Then reboot to recovery and flash whatever you wish besides OOS3 or H2OS 6.0. Good luck!

As said above, here is a modified TWRP for OOS3 https://www.androidfilehost.com/?fid=24459283995297945
But by all means use any TWRP listed as OOS3 compatible, then push the .img file using the fastboot flash recovery command.

jbw716 said:
As far as I know, with OOS3 beta, it uses a different firmware which causes the official TWRP to not boot. I believe you have to use a customized version of TWRP (should be somewhere on XDA or OP Forums) with OOS3. You should be able to flash that version of TWRP. Then, reboot into TWRP, flash OOS2, and then the official TWRP from within the custom TWRP. Then reboot to recovery and flash whatever you wish besides OOS3 or H2OS 6.0. Good luck!
Click to expand...
Click to collapse
Benoys-Air:fastboot benoyanthony$ ./fastboot-mac oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.078s]
finished. total time: 0.078s
Benoys-Air:fastboot benoyanthony$ ./fastboot-mac flash recovery OP2.img
target reported max download size of 536870912 bytes
sending 'recovery' (31501 KB)...
OKAY [ 0.710s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.727s
______________________
I am facing this issue, anybody pls help.

Follow this guide, you data would still be safe.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
for further help ping me.

Also, read up on OxygenOS 3 and HydrogenOS bootloader and compatible TWRP recovery.

jbw716 said:
As far as I know, with OOS3 beta, it uses a different firmware which causes the official TWRP to not boot. I believe you have to use a customized version of TWRP (should be somewhere on XDA or OP Forums) with OOS3. You should be able to flash that version of TWRP. Then, reboot into TWRP, flash OOS2, and then the official TWRP from within the custom TWRP. Then reboot to recovery and flash whatever you wish besides OOS3 or H2OS 6.0. Good luck!
Click to expand...
Click to collapse
Thank you very much I had no idea that 3.0 Beta used different firmware.Although the bootloader was still locked, I was able to finally get the damn drivers on my PC and used the full restore kit. That put me on Hydrogen OS, so I installed Oxygen 2.0 and stock recovery, it works again. Now Im re-updated to 3.0 Beta fully working and am now going to root it and back it up.

Phone stucks in fastboot

Hi guys,
i was on Miui Global 10.xxxx (dont know exactly)
bootloader was unlocked.
Rollback protection target was 1
my recovery was Orangefox recovery (https://forum.xda-developers.com/mi-9t/development/official-orangefox-recovery-project-t4037899)
I have made a full backup of all partitions before.
I wanted to flash Miui 11.0.4.0 global to flash a custom rom.
First i flashed recovery and installed the recovery.zip.
That worked fine.
Then i wanted to flash Miui 11.0.4.0 with this instructions for a clean flash:
1. If you're coming from another ROM or need to perform a clean flash:
Boot into Recovery
Wipe Data/Cache/System
Flash vendor/firmware (Global 11.0.4.0 recommended)
Flash ROM
(Optional) Flash Gapps (not included!)
(Optional) Flash the latest Magisk
Reboot
Enjoy
This instructions are from here: https://forum.xda-developers.com/mi-9t/development/rom-stagos-t4072637
So, i was in recovery, and deleted data, cache and system.
Then i restarted the phone to go to recovery, but that didnt work.
It stucked in bootloop.
I now reinstalled Adb and fastboot, and erased recovery and System partition.
There were much errors in time due old adb and fastboot version etc....
But now iam at this point here again.
wait for your answers how to continue.....
It looks like just flashing or booting recovery is not possible without system partition.

It's now too late and sorry I don't want to risk to give you the wrong instructions how to unbrick
But for the others to avoid similar brick:
1) You say you were on Global MIUI 10 and you wanted to update to MIUI 11.
If so, why didn't you simply update by OTA?
2) If for some reason you were not able to apply OTA, but if you were really on Global (not on custom ROM, Indian ROM or so) and wanted to update also to Global (not switching to EU weekly or so), then you shouldn't wipe anything
You had to flash the stock Recovery back, to download the Global recovery/zip package you wanted to update to, and to force update from System Update: (so called Local Update):
https://c.mi.com/oc/miuidownload/detail?guide=1
Now, once you wiped things and bricked, I don't know but you could check the Fastboot method:
https://c.mi.com/oc/miuidownload/detail?guide=2
If reading from mobile phone, force Desktop site in browser for the two links anove

1. When you make format data, than reboot in twrp again
2.when boot second time, wipe data, dalvick, cache, system...and flash new rom.
If you wipe system partition and reboot in twrp again without system, you get fastboot.

zgfg said:
It's now too late and sorry I don't want to risk to give you the wrong instructions how to unbrick
But for the others to avoid similar brick:
1) You say you were on Global MIUI 10 and you wanted to update to MIUI 11.
If so, why didn't you simply update by OTA?
2) If for some reason you were not able to apply OTA, but if you were really on Global (not on custom ROM, Indian ROM or so) and wanted to update also to Global (not switching to EU weekly or so), then you shouldn't wipe anything
You had to flash the stock Recovery back, to download the Global recovery/zip package you wanted to update to, and to force update from System Update: (so called Local Update):
https://c.mi.com/oc/miuidownload/detail?guide=1
Now, once you wiped things and bricked, I don't know but you could check the Fastboot method:
https://c.mi.com/oc/miuidownload/detail?guide=2
If reading from mobile phone, force Desktop site in browser for the two links anove
Click to expand...
Click to collapse
Sooo....after hours of reading with errors over errors and fixing, it still doesnt work.
First i tried to flash everything via mi flashtool.
There was an error: Antirollbackcheck Error.
https://www.reddit.com/r/Xiaomi/comments/d0xmbp/what_on_earth_is_miflash_antirollback_check_error/
https://xiaomi.eu/community/threads...nd-flashing-recovery-fails-please-help.51349/
To fix this i had to move the Tool and the rom into my C hard drive next to program etc folders...
Then i editet the flashall.bat file and removed the rollbackcheck lines.
Now after doing this, it flashed for 100 seconds, and then there was this error: Failed to flash dtbo.img
sooo....Then i tried to flash the dtbo.img and all the other ones via Minimal adb and fastboot.
https://forum.xda-developers.com/mi-9t/help/flash-stuck-fastboot-soft-brick-t3962662/page3
And this didnt work for me too. Everytime if i try to flash dtbo.img, this error comes:
target didnt report max-download-size
sending dtbo (32768KB)....
FAILED (command write failed (no error))
finished.
Now everything is like before....

Flash twrp and boot in twrp. After phone boot in twrp, make format data. After format, make reboot to recovery.
When booot in twrp, wipe data, dalvick, cache, system , copy Miroom to internal and flash ROM.
Use this twrp...
https://app.box.com/s/8lkfbft44vldtt0y8kwhe6un87b5ebzx
And this rom.
https://sourceforge.net/projects/mi...edmiK20_MIUI_20.3.26_MiRoom_10.0.zip/download
Sent from my MI 9T using Tapatalk

Kidence said:
Flash twrp and boot in twrp. After phone boot in twrp, make format data. After format, make reboot to recovery.
When booot in twrp, wipe data, dalvick, cache, system , copy Miroom to internal and flash ROM.
Use this twrp...
https://app.box.com/s/8lkfbft44vldtt0y8kwhe6un87b5ebzx
And this rom.
https://sourceforge.net/projects/mi...edmiK20_MIUI_20.3.26_MiRoom_10.0.zip/download
Sent from my MI 9T using Tapatalk
Click to expand...
Click to collapse
C:\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.3.1-12-davinci-mauronofrio.img
target reported max download size of 805306368 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.914s]
writing 'recovery'...
OKAY [ 0.151s]
finished. total time: 2.065s
C:\Minimal ADB and Fastboot>fastboot boot recovery
error: cannot load 'recovery': No such file or directory
C:\Minimal ADB and Fastboot>fastboot boot twrp-3.3.1-12-davinci-mauronofrio.img
downloading 'boot.img'...
OKAY [ 1.891s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.900s

When you flash recovery, hold volume up and type in adb
fastboot reboot
After that, phone will be boot in twrp
Sent from my MI 9T using Tapatalk

FINALLY it worked YES
FIRST: The Story for everybody who has the same problem like me:
Device: Xiaomi Mi 9T
Firmware: MIUI 10 GLOBAL
Antirollbackprotectioncounter: 1
Bootloader: Unlocked
Story:
At the beginning, everything was working, but i wanted to install a custom rom (STAGOS)
For this step, i had to Update my Miui firmware on 11.0.4.0.
But this step didnt work so well via device OTA (error), then i decided to install it via custom recovery.
I still had the stock recovery on my device, so i went in fastboot mode, and installed Orangefox recovery via ADB and Fastboot on Windows. That worked without problems.
In Orangefox, i wiped as sayed in instructions data, cache and System. then i rebooted.
But before realised that was the wrong way, i stucked in fastboot.
No tools helped. ADB and Fastboot didnt work as seen in screenshots.
I tried everything via fastboot....
fastboot flash recovery XXX.img
fastboot boot XXXX.img
Fastboot format.....etc
But NOTHING worked. Everytime there were the following errors:
Target didnt report Max download size
Error: Cannot load recovery
No such file or directory
Error: Download size is higher that allowed
Failed to load boot image (Load error)
Command write failed (no error)
and some other ones too.....
It looked like, some flashes worked and some not. Sometimes it worked, sometimes not.
After some new tries it just showed via the command: Fastboot devices
????????? fastboot
That problem has been solved. Just unplug the device and wait for 10 minutes until it shuts down automatically.
If that doesnt work, you can try to replug it to pc some times again.
It looked like replugging and using different USB Port (one user solved the problem via USB 2.0) helps to get a better connection and prevent errors.
Then i tried some tools, for example android all in one tool, but no one worked.
After this, i reinstalled the driver and installed MI Flash tool (https://mi-globe.com/download-xiaomi-mi-flash-tool-all-versions/)
It looks like there are some mi flash tools around here which are not working right, but THIS one worked for me.
After installing, i connected my device, choosed the fastboot firmware (.tgz), unpacked it and choosed the right location in mi Flash tool.
Firmware files are find here: https://c.mi.com/oc/miuidownload/detail?guide=2
(You should check you Antirollback counter before to avoid a brick. Here you find some informations: https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/)
DONT FORGET TO CHOOSE IN THE RIGHT DOWN CORNER: CLEAN ALL !!! (normally, clean all and lock is choosen, but that bricks your device)
After doing this, i started flashing, but there was an error: Antirollbackcheck error.
I solved it via moving the mi flashtool directly into my C hard drive, and deleted some lines in the flashall.bat, as seen in post history here.
Then....it worked for some seconds longer, but than: Error: Failed to flash dtbo.img
So i tried it via ADB and Fastboot. But nothing changed.
Then i tried flashing via mi Flash tool again, and this time the following error comes: Failed to flash system.img.
After this is thought: hmmm....something is very wrong with this device....lets try again, after a device restart.
So i tried again, let it running for ~360 seconds, and IT WORKED!
At the End: there was the following error: Error: Not catch checkpoint.
But this error (you can also see in a screenshot) it not necessary.
This is the result of removing some lines in flashall.bat.
After this my phone successfully booted im Miui 11.