EDIT: FIXED
hi everyone, ive already rooted an essential phone in that past so i was a bit overconfident i guess, i followed all the steps in the main post https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976 but when i went to twrp to install the boot img and magisk zip i got an error that i couldnt mount to system, i realized that i had forgotten to set my mount to system so i rebooted into twrp to re instally but through system mount. it just went into a bootloop, so i decided to return my phone back to stock and redo..... well now i can wipe the device or use a flashall, my phone has no data at all, is still recognized in fastboot but it just wont work. i get errors:
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (No error))
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: 0.006s
and:
when trying to use fastboot -w, phone still dosent boot and flashall fails because the phone hasnt been wiped, any help please? im phoneless right now, an yes i have tried different usb cords and ports. thank you so much!
edit: not sure if its working yet but i just wiped everything through twrp so that twrp uninstalled and now the back to stock flashall seems to be working, fingers crossed!
edit 2: it goes through the whole back to stock script with everything in adb but when its done it restarts and keeps doing that. ive stopped it the second it says done as well (after it finished writing all of system b) but when i start my phone it just immediately reboots into recovery or bootloader.....
nominath654 said:
hi everyone, ive already rooted an essential phone in that past so i was a bit overconfident i guess, i followed all the steps in the main post https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976 but when i went to twrp to install the boot img and magisk zip i got an error that i couldnt mount to system, i realized that i had forgotten to set my mount to system so i rebooted into twrp to re instally but through system mount. it just went into a bootloop, so i decided to return my phone back to stock and redo..... well now i can wipe the device or use a flashall, my phone has no data at all, is still recognized in fastboot but it just wont work. i get errors:
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (No error))
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: 0.006s
and:
when trying to use fastboot -w, phone still dosent boot and flashall fails because the phone hasnt been wiped, any help please? im phoneless right now, an yes i have tried different usb cords and ports. thank you so much!
edit: not sure if its working yet but i just wiped everything through twrp so that twrp uninstalled and now the back to stock flashall seems to be working, fingers crossed!
edit 2: it goes through the whole back to stock script with everything in adb but when its done it restarts and keeps doing that. ive stopped it the second it says done as well (after it finished writing all of system b) but when i start my phone it just immediately reboots into recovery or bootloader.....
Click to expand...
Click to collapse
"fastboot -w" is the command to wipe all user data.
Why are you trying to wipe things through twrp?
Back to stock and add?
The script is run vis fastboot.
Which ROM are you trying to install?
Get either the latest 8.1 or P Beta from the ROM threads.
Try flashing one of those.
Did you unlock_critical?
tech_head said:
"fastboot -w" is the command to wipe all user data.
Why are you trying to wipe things through twrp?
Back to stock and add?
The script is run vis fastboot.
Which ROM are you trying to install?
Get either the latest 8.1 or P Beta from the ROM threads.
Try flashing one of those.
Did you unlock_critical?
Click to expand...
Click to collapse
hi, i had soft bricked so i tried to wipe everything to flash back to stock, anyway i got it to work, was being stupid. ill update the thread. TY!
Related
So i just saw the new Oxygen OS 3.1.0 is out in OTA form. Me being rooted i tried flashing it through twrp, which i had installed before. (i should also note that i had Xposed installed too, on Oxygen OS 3.0.2) now i think i might have gotten my zip file wrong and installed a previous version. The boot animation is the square, triangle and circle one. It just goes through my apps and tries to update them for eternity. When i try putting the device into recovery (power+vol down) it just freezes on the oneplus logo. I later discovered that i can use fastboot when in that mode. I tired flashing twrp but i couldnt boot into it. fastboot boot recovery.img didnt work either, giving me this:
downloading 'boot.img'...
OKAY [ 0.746s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.011s
Now i have no idea what to do. I'm sure I've made SOME kind of mistake along the way, but i cant find a way to fix this. I have a nandriod backup of just before flashing if that might help.
fastboot reboot-bootloader puts me in fastboot mode but it doesnt change anything.
also, ADB naturally wont detect the phone whatsoever.
Ill be very glad for any help! Thanks!
Are the drivers accurate? Does your PC recognize your device as it should in Device Manager? That's usually what I check first when I have fastboot errors. I think the only way to fix this is through fastboot... so I would focus on trying to get that to work first.
SynderBlack said:
So i just saw the new Oxygen OS 3.1.0 is out in OTA form. Me being rooted i tried flashing it through twrp, which i had installed before. (i should also note that i had Xposed installed too, on Oxygen OS 3.0.2) now i think i might have gotten my zip file wrong and installed a previous version. The boot animation is the square, triangle and circle one. It just goes through my apps and tries to update them for eternity. When i try putting the device into recovery (power+vol down) it just freezes on the oneplus logo. I later discovered that i can use fastboot when in that mode. I tired flashing twrp but i couldnt boot into it. fastboot boot recovery.img didnt work either, giving me this:
downloading 'boot.img'...
OKAY [ 0.746s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.011s
Now i have no idea what to do. I'm sure I've made SOME kind of mistake along the way, but i cant find a way to fix this. I have a nandriod backup of just before flashing if that might help.
fastboot reboot-bootloader puts me in fastboot mode but it doesnt change anything.
also, ADB naturally wont detect the phone whatsoever.
Ill be very glad for any help! Thanks!
Click to expand...
Click to collapse
**** man. I'm in the same boat as of a few hours ago. I was having a ProxyController wakelock and the few Google results I saw told me I should reflash the modem. I accidentally flashed the old modem (OOS2, I believe). I can't boot into my rom OR TWRP. BUT fastboot does work. I also get the "remote: dtb not found" error when trying to boot from the recovery image.
As long as we have fastboot, we can always go back to OOS 3 using the various unbrick methods. I'm trying to avoid having to go through that whole mess of re-rooting/unlock the bootloader etc etc. I'll post on here if I'm successful.
Update: I NEED a functional phone so I just went and erased everything. Sorry I couldn't be of much help to you man. What I did:
I went here and downloaded the fastboot version of OOS3 and converted the bat scripts into bash scripts (I only have Linux computers near me right now...; the commands in that bat script are exactly the same as they would be in bash, I just had to rename the ".bat" to ".sh" and make it executable). I'm back in OOS 3 now, unfortunately. There IS a way mentioned on the page below that talks about how you can prevent userdata from being formatted, but I didn't really care too much. Hope that helps.
http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
When I try to wipe internal it says
Code:
Wiping internal storage -- /data/media...
Error opening: '/data/media' (No such file or directory)
When I try to format instead - I get even more errors:
Code:
Formatting Data using make_ext4fs...
Failed to mount '/data' (Device or resource busy)
Failed to mount '/data' (Device or resource busy)
Unable to recreate /data/media folder.
You may need to reboot recovery to be able to use /data again.
Updating partition details...
Failed to mount '/data' (Device or resource busy)
...done
Is this because of encryption? And if so - this is weird because I never encrypted my device. I currently have no OS and just trying to unsoftbrick my phone.
specialk00 said:
...Is this because of encryption? And if so - this is weird because I never encrypted my device. I currently have no OS and just trying to unsoftbrick my phone.
Click to expand...
Click to collapse
Use fastboot and make sure you are using the latest binaries. Format system, userdata and cache. Upon booting for the first time, the 6P automatically defaults to encryption- unless you intervene and stop it from doing so.
v12xke said:
Use fastboot and make sure you are using the latest binaries. Format system, userdata and cache. Upon booting for the first time, the 6P automatically defaults to encryption- unless you intervene and stop it from doing so.
Click to expand...
Click to collapse
Yep, I just fixed it somehow, I think it was related to MTP in TWRP. However now I'm stuck with a different issue. No matter what I flash in fastboot - I get
Code:
C:\Users\Nexusflip\AppData\Local\Android\sdk\platform-tools>fastboot flash recovery D:\Downloads\angler\twrp-3.1.1-0-angler.img
target didn't report max-download-size
sending 'recovery' (16948 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
I always get this weird "No error" thing.
specialk00 said:
Yep, I just fixed it somehow, I think it was related to MTP in TWRP. However now I'm stuck with a different issue. No matter what I flash in fastboot - I get
Click to expand...
Click to collapse
Are you sure you are using the latest binaries? Hash checked the TWRP file? Put TWRP img in your fastboot folder? Format/erase recovery partition?
v12xke said:
Are you sure you are using the latest binaries? Hash checked the TWRP file? Put TWRP img in your fastboot folder? Format/erase recovery partition?
Click to expand...
Click to collapse
Yes I'm using the latest binaries - I got them via Android SDK and updated everything. I checked the ones you linked and they are exactly the same.
Regarding the hash check - this has nothing to do with the file being corrupted. This happens with ANY file I try to flash.
I tried putting the TWRP img in my fastboot folder and the results are the same.
Erasing the recovery partition gives the same error.
Code:
C:\Users\username\AppData\Local\Android\sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
FAILED (command write failed (No error))
finished. total time: 0.009s
specialk00 said:
Yes I'm using the latest binaries - I got them via Android SDK and updated everything. I checked the ones you linked and they are exactly the same. Regarding the hash check - this has nothing to do with the file being corrupted. This happens with ANY file I try to flash. I tried putting the TWRP img in my fastboot folder and the results are the same. Erasing the recovery partition gives the same error.
Click to expand...
Click to collapse
Were you able to successfully fastboot format userdata, system and cache with no errors? Did you get the same error using format as you did erase recovery? Is your phone bootlooping ? If yes, then your phone may have the BLOD. There are a few instances of users still having access to recovery mode, but not being able to flash anything. If you flash a full stock image with flash-all.bat, it finishes but the phone still loops then you likely have the BLOD.
v12xke said:
Were you able to successfully fastboot format userdata, system and cache with no errors? Did you get the same error using format as you did erase recovery? Is your phone bootlooping ? If yes, then your phone may have the BLOD. There are a few instances of users still having access to recovery mode, but not being able to flash anything. If you flash a full stock image with flash-all.bat, it finishes but the phone still loops then you likely have the BLOD.
Click to expand...
Click to collapse
I tried minimal adb & fastboot (bit older version) and got this.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.1.1-0-angler.img
target didn't report max-download-size
sending 'recovery' (16948 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.007s
Then I tried another old version of fastboot - got one from july 2016 (23.0.1) and nothing happened when executing flash or format commands.
Then I tried normal, latest fastboot and both (new & old) versions of fastboot gave me this error.
Code:
C:\Users\Nexusflip\AppData\Local\Android\sdk\platform-tools>fastboot erase userdata
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: 0.023s
Then I tried to format (instead of erase)
Code:
C:\Users\Nexusflip\AppData\Local\Android\sdk\platform-tools>fastboot format userdata
FAILED (command write failed (No error))
I don't know if my phone is bootlooping because I don't have OS installed and my internal storage is squeaky clean. All this crap didn't just start out of nowhere - I flashed 8.0.0 dev preview 2 images through TWRP. I know I'm not the brightest. When I launch flash-all.bat it's just blank and does nothing at all.
specialk00 said:
I don't know if my phone is bootlooping because I don't have OS installed and my internal storage is squeaky clean. All this crap didn't just start out of nowhere - I flashed 8.0.0 dev preview 2 images through TWRP. I know I'm not the brightest. When I launch flash-all.bat it's just blank and does nothing at all.
Click to expand...
Click to collapse
It sounds to me like your internal storage (memory) is bad. Bottom line is that if you can't format your basic partitions successfully, you will not be able to flash a full ROM. If you don't believe your memory is bad, you can search the 6P forums for the Qualcomm Flash Image Loader (QFIL) & EDL mode. There is a rescue binary for the 6P floating around that some people have been successful in using restoring corrupt partitions, presumably because it works at the hardware level.
v12xke said:
It sounds to me like your internal storage (memory) is bad. Bottom line is that if you can't format your basic partitions successfully, you will not be able to flash a full ROM. If you don't believe your memory is bad, you can search the 6P forums for the Qualcomm Flash Image Loader (QFIL) & EDL mode. There is a rescue binary for the 6P floating around that some people have been successful in using restoring corrupt partitions, presumably because it works at the hardware level.
Click to expand...
Click to collapse
What should I do from now on? I have no idea what to do. The device has been bricked for 24 hours now.
This is the closest I've found to my problem. Also on a Nexus 6P. https://forum.xda-developers.com/nexus-6p/help/zip-file-signature-verification-error-t3561054
I tried adb reboot edl and it says error: closed. So not even that works.
specialk00 said:
What should I do from now on? I have no idea what to do. The device has been bricked for 24 hours now. This is the closest I've found to my problem. Also on a Nexus 6P. https://forum.xda-developers.com/nexus-6p/help/zip-file-signature-verification-error-t3561054
I tried adb reboot edl and it says error: closed. So not even that works.
Click to expand...
Click to collapse
Stock fastboot does not support boot to EDL. You need a modified fastboot, BUT getting to EDL mode won't help you until you have all the proper tools and 6P specific files. I don't want to get your hopes up. I think your device is not recoverable due to a hardware issue (bad memory). If you are looking for a learning project to keep you busy with very little hope of success, keep digging. If you need a working phone, you need to buy another one, or a 6P replacement motherboard from a screen damaged parts phone. Unfortunately, there have been many onboard memory failures on the 6P.
I fixed the problem. It turned out to be a faulty USB-C to USB-A cable. The only problems were with file transfer-related commands. I then tried transferring a 1 kb file, then 1 mb (failed) then 200kb, then 300kb (failed). So it turns out the cable is ****ty. Wow. And nothing is corrupted. I'm typing this from my phone now.
My bootloader is off the rocker right know and I can't seem to get anything done.
Cant access recovery, multiple bootloops, etc. EVEN after flashing stock images from the Dump thread.
Now I cant even do that because nothing wants to flash to the partitions, e.g.
Code:
FAILED (remote: Error flashing partition.)
Code:
c:\tools>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (No error))
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: 0.000s
I'm at a loss here, is there anyway I can fix this?
Thanks guys
jAm-0 said:
My bootloader is off the rocker right know and I can't seem to get anything done.
Cant access recovery, multiple bootloops, etc. EVEN after flashing stock images from the Dump thread.
Now I cant even do that because nothing wants to flash to the partitions, e.g.
I'm at a loss here, is there anyway I can fix this?
Thanks guys
Click to expand...
Click to collapse
I'm sure you've already tried this but, what about the other USB ports? I had this very same issue and it took me about an hour to get my phone to recognize "fastboot -w" again.
If I recall correctly, I had to power off the PC and phone, then downgraded my Minimal ADB and Fastboot and everything started working again surprisingly, commands were recognized and I could wipe and flash with no issues.
Welcome to the club. There are a few of us now. I had this happen when trying to flash TWRP after installing the 8.1 beta. AFAIK there's nothing you can do. I've tried every combination of USB port, cable and OS. Its either a hardware error or somethings ****ed with the bootloader. Essential isn't claiming any responsibility and its just offering a $200 out of warranty replacement to US customers.
Dear everyone,
I am stuck in fastboot. I installed the greek TWRP, and cleaned my data by typing ''yes''.
I connected my phone to my PC to put a ROM zip on it, but it only glitched out (it showed multiple storages in Windows)
I restarted my phone, and it won't boot in recovery. When I try to boot to recovery via adb, it just shows
PS C:\adb> fastboot boot recovery.img
Downloading 'boot.img' OKAY [ 0.616s]
booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
I am really scared now that my phone is hard bricked. Not sure why though.
Flashing a fastboot ROM wont work either, it just says flash done instantly.
I have done this so many times on my other Xiaomi phones I had without any problems.
And also, is it possible to turn the phone off for now? Because I dont want to have the fastboot screen burned in.
Regards
Jordytjes said:
Dear everyone,
I am stuck in fastboot. I installed the greek TWRP, and cleaned my data by typing ''yes''.
I connected my phone to my PC to put a ROM zip on it, but it only glitched out (it showed multiple storages in Windows)
I restarted my phone, and it won't boot in recovery. When I try to boot to recovery via adb, it just shows
PS C:\adb> fastboot boot recovery.img
Downloading 'boot.img' OKAY [ 0.616s]
booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
I am really scared now that my phone is hard bricked. Not sure why though.
Flashing a fastboot ROM wont work either, it just says flash done instantly.
I have done this so many times on my other Xiaomi phones I had without any problems.
And also, is it possible to turn the phone off for now? Because I dont want to have the fastboot screen burned in.
Regards
Click to expand...
Click to collapse
Did you try flashing the fixed russian twrp? When I flashed the greek twrp on my phone and rebooted through adb it didn't reboot so I rebooted manually and it rebooted into stock recovery. I rebooted into fastbood and flashed the fixed twrp and it worked. If you can get into fastbood you have a chance of reflashing twrp or flashing stock rom so I don't think its bricked yet
Aserar said:
Did you try flashing the fixed russian twrp? When I flashed the greek twrp on my phone and rebooted through adb it didn't reboot so I rebooted manually and it rebooted into stock recovery. I rebooted into fastbood and flashed the fixed twrp and it worked. If you can get into fastbood you have a chance of reflashing twrp or flashing stock rom so I don't think its bricked yet
Click to expand...
Click to collapse
You are my hero! Thank you so much!
this is soft brick, try to flash another twrp as the above user mentioned.
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.