Hi guys
today was my waiting time over and so i opend the bootloader and flashed:
Twrp_3.3.0_Cepheusv11
xiaomi.eu_multi_MI9_9.5.23_v10-9
Magisk-v19.2
all with success.
The phone (Global version, 6gb+128gb) boots normal and everything works fine up to the point where i want to boot in TWRP. After starting the phone with power+Vol up i get the mi unlocked screen and then for 1 second a black screen, then its reboot and i'm on the mi unlock screen again. Fastboot and normal system boot works fine, i have root over magisk and everything.
Any ideas how to get into twrp again?
Longer version:
After unlocking the bottloader i followed this guide-how-flashed-twrp-xiaomi-eu-rom but with newer files. For TWRP i used the Twrp_3.3.0_Cepheusv11 version from here. The eu rom came from sourceforge and the magisk version from here.
I flashed twrp over terminal from my pc with "fastboot flash recovery twrp.img" and uploaded the rom and magisk with "adb push rom.zip /tmp/" + "adb push magisk.zip /tmp/" to the ram. After disconnection the usb cable i hold down power+vol up while still in the fastboot mode and the phone reboots into twrp. from there it was strait following the guid eg. wipe menu, format data, confirmed with "yes", wipe menu again, factory reset. Install rom.zip, install magaisk.zip both without any errors. Reboot menu and select "do not install" for the twrp app.
From now on the eu rom started up, i connected to my wlan and connected the phone to my mi account and after that to my google account. The rest was normal installation.
After installing everything i debloated the phone with this list. Instead of pasting the full list i chose just the follwing parts:
Android Stuff: none
Google Stuff: none
Xiaomi Stuff: all
Xiaomi Apps: all
Extra Stuff: none
To be Tested yet (try at your own risk):
com.miui.compass
com.miui.calculator
com.miui.cloudservice.sysbase
com.miui.gallery
com.miui.screenrecorder
com.mi.webkit.core
com.miui.providers.weather
Unfortunately is the android.providers.calendar app in the xiaomi app list and my calender didn't sync to google without it. So i read a bit about the com.android.providers.calendar app and learned that it is a specific app for every version of android and i cannot simply use the version from my other phone.
Okay, i thougt, my system is just about 2 hours old i reflash the eu rom and magisk and be done with it. So said, i wanted to boot into twrp, powerd the phone off, hold down power+vol up and got the miui unlocked screen, after that 1 second of black screen and than the miui unlock screen again with is followed by the normal system boot.
First i thought i missed the right moment for holding the buttons down so i installed apps which allowed me to directly reboot into recovery.
But with ervery app it was the same: miui unlocked screen, after that 1 second of black screen and than the miui unlock screen again with is followed by the normal system boot.
So i reflashed twrp over the terminal "fastboot flash recovery twrp.img" and it was stated a success. But again only: miui unlocked screen, after that 1 second of black screen and than the miui unlock screen again with is followed by the normal system boot.
Next i tried to reboot into recovery from adb but it was the same result.
Next i tried to just boot twrp from terminal with "fastboot boot twrp.img" but again, same result.
Next i tried to install different versions of twrp. From beta8 to beta11 i flashed every version but again, same result.
Now i'm sitting here happy with a new eu rom and fully rooted but unhappy with the knowing i cannot update anymore. Any ideas how to get into twrp again?
Edit: i reinstalled my android.providers.calendar after i read the "How to Re-Install an Uninstalled App" section again ^^
I read somewhere the Chinese recovery should work with latest Xiaomi.eu. TWRP is still in early stages.
Re-flash the recovery in fastboot mode. After flashing don't reboot recovery with a command but reboot recovery by pressing vol+ and power, keep both pressed untill you see twrp booting. Happened with me as well but than got sorted by flashing again after setting up the rom, enabling usb debugging and going back into fastboot and flash. And can I ask why did you use version 11 when the latest on that recovery is v17 beta and a final version but v17 is good and decrypts as well, hope this helps, cheers.
version 17 is on this page: click on the mega link
https://forum.xda-developers.com/Mi-9/how-to/recovery-unofficial-twrp-recovery-3-2-3-t3912118/page10
Also try this recovery,
https://forum.xda-developers.com/Mi-9/development/twrp-3-3-0-arm64-gapps-support-t3925728
Xiaomi.eu
k4win said:
Hi guys
today was my waiting time over and so i opend the bootloader and flashed:
Twrp_3.3.0_Cepheusv11
xiaomi.eu_multi_MI9_9.5.23_v10-9
Magisk-v19.2
all with success.
The phone (Global version, 6gb+128gb) boots normal and everything works fine up to the point where i want to boot in TWRP. After starting the phone with power+Vol up i get the mi unlocked screen and then for 1 second a black screen, then its reboot and i'm on the mi unlock screen again. Fastboot and normal system boot works fine, i have root over magisk and everything.
Any ideas how to get into twrp again?
[...]
Click to expand...
Click to collapse
Hello, i had the same pb, try this recovery: https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825 it's ok for me.
@++
Problem after flashing TWRP
This is what I did:
1. Unlocked the bootloader
2. Updated to stock android 5.1.1. (with sonys flashtool)
3. fastboot flash recovery twrpfilename.img (probably a bad idea)
4. fastboot flash boot twrpfilename.img (I did not install the TWRP FOTA zip)
5. adb shell dd if=/sdcard/twrpfilename.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
6. Installed Lineageos 15.1
This is the problem:
(1) I can not boot into recovery with power button+volume down, nor with LineageOS power off/restart/recovery; both ways result in a black screen. The command adb reboot recovery is the only way that work, to my knowledge. (2) The fastboot command does not work anymore (it is not a driver problem); the adb command still work, but not fastboot; I get "waiting for device". I have tested with an other phone (Motorola) and fastboot work as it should with that phone.
Solution?
Do anyone have any advice? What can one do to solve this problem?
@mungoAttack
I had same troubles that you comment. After fail install with Magisk 19, and install again 5.1.1 and LOS 15.1, it was impossible
to access recovering of any way. ADB worked but Fastboot not.
I followed the instructions of other members of this forum:
https://forum.xda-developers.com/xperia-z/orig-development/rom-lineageos-15-0-xperia-z-t3721749
Mainly in last messages from May and June, and now, I have LOS 15.1 with root (Magisk 18) and TWRP with full functionallity.
I hope they can help you.
ISPG said:
@mungoAttack
I had same troubles that you comment. After fail install with Magisk 19, and install again 5.1.1 and LOS 15.1, it was impossible
to access recovering of any way. ADB worked but Fastboot not.
I followed the instructions of other members of this forum:
https://forum.xda-developers.com/xperia-z/orig-development/rom-lineageos-15-0-xperia-z-t3721749
Mainly in last messages from May and June, and now, I have LOS 15.1 with root (Magisk 18) and TWRP with full functionallity.
I hope they can help you.
Click to expand...
Click to collapse
Thank you very much for the link. If I understand you correctly you now have a working fastboot and recovery. I will check you the link.
Well ... for some unknown reason, I am not able to connect the phone to the computer in fastboot mode.
In theory, all requirements are met, but when I reboot in this way, the blue LED is shown in the phone, but
the command "fastboot devices" doesn't give any answer. I have seen in different forum a lot of people with
the same problem. I think that in some moment, something changed in the phone, because in the computer
you can see the yellow triangle with a problem in SD1 device (in Control panel/ devices). And it only happens
with this phone, I have checked with other phones, and fastboot works perfectly.
Finally, I´ve considered that with TWRP recovery is enough for most of the operations with the device. I have
installed the last version, 3.3.1-0 and you can flash any file or Nightly. You can also use the ADB mode or Terminal
emulator in the phone.
HI there,
a few days ago I wanted to clean flash on my OP3T Havoc OS beta (the one based on Android 11) over the current stable Havoc OS based on Android 10. I ended up making a huge mistake wiping everything including system partition and data partition including Downloads and Personal Files. So now all I have left is a functioning TWRP recovery, an unlocked bootloader; the device is encrypted but has no OS on it! I don't have a backup. My main problem is I can't fastboot or adb the device - not on the black screen I get after the oneplus symbol during boot - and not in TWRP or Bootloader mode because the telephone is not recognized in device manager on my win 10 machine, same on another linux machine, the device is not recognized by adb or fastboot. Next thing I want to try is usb stick OTG and go from there.
Anyway, thanks for reading. Do you guys have any suggestions?
realtobman said:
...So now all I have left is a functioning TWRP recovery, an unlocked bootloader; the device is encrypted but has no OS on it! I don't have a backup. My main problem is I can't fastboot or adb the device - not on the black screen I get after the oneplus symbol during boot
...
Next thing I want to try is usb stick OTG and go from there.
Anyway, thanks for reading. Do you guys have any suggestions?
Click to expand...
Click to collapse
Using OTG is the way I'd go also if the phone isn't recognised by the PC.
You said your phone has an unlocked bootloader and that you get a black screen when the phone boots.
With an unlocked bootloader you should be getting the warning screen (see picture) which disappears after 5 seconds. And you should be able to select fastboot or recovery, etc by pressing the volume button.
Sent from my OnePlus 3T using XDA Labs
realtobman said:
HI there,
a few days ago I wanted to clean flash on my OP3T Havoc OS beta (the one based on Android 11) over the current stable Havoc OS based on Android 10. I ended up making a huge mistake wiping everything including system partition and data partition including Downloads and Personal Files. So now all I have left is a functioning TWRP recovery, an unlocked bootloader; the device is encrypted but has no OS on it! I don't have a backup. My main problem is I can't fastboot or adb the device - not on the black screen I get after the oneplus symbol during boot - and not in TWRP or Bootloader mode because the telephone is not recognized in device manager on my win 10 machine, same on another linux machine, the device is not recognized by adb or fastboot. Next thing I want to try is usb stick OTG and go from there.
Anyway, thanks for reading. Do you guys have any suggestions?
Click to expand...
Click to collapse
I'm having the same problem, did you manage to fix it?
My suggestion is that you purchase an OTG (bout $10++) then place any ROM inside. After that, flash it on your phone through TWRP. If that doesn't work and somehow your partitions are all messed up, there's always the unbrick method here: https://forum.xda-developers.com/t/op3t-latest-9-0-6-collection-of-unbrick-tools.3896765/
realtobman said:
HI there,
a few days ago I wanted to clean flash on my OP3T Havoc OS beta (the one based on Android 11) over the current stable Havoc OS based on Android 10. I ended up making a huge mistake wiping everything including system partition and data partition including Downloads and Personal Files. So now all I have left is a functioning TWRP recovery, an unlocked bootloader; the device is encrypted but has no OS on it! I don't have a backup. My main problem is I can't fastboot or adb the device - not on the black screen I get after the oneplus symbol during boot - and not in TWRP or Bootloader mode because the telephone is not recognized in device manager on my win 10 machine, same on another linux machine, the device is not recognized by adb or fastboot. Next thing I want to try is usb stick OTG and go from there.
Anyway, thanks for reading. Do you guys have any suggestions?
Click to expand...
Click to collapse
get a sd card please
Hello there.
Just like title says - I've got my hands on new Redmi 9 (lancelot) nfc 4/64 version. I've unlocked it from Mi stuff successfully yesterday and wanted to install there twrp, magisk and titanium backup to clean a bit and maybe to have foundations for further change of rom.
However, my phone gaves answers, that I do not understand correctly.
Firstly - after first instalation of twrp via adb it booted into this. However, after choosing option to boot to system from it, power off via ui and then another try to enter recovery...it gave me stock miui recovery again. When I've tried the same steps for second time, phone finished, but after restart it entered bootloop. I've followed steps from this guide - https://miui.blog/redmi-9/download-install-twrp-and-root-redmi-9-codename-lancelot/
After some time I've managed to make low-level rom instalation again (12.0.4 official lancelot rom, dated 31st of Mar, 21) to at least being able to communicate with it (done with usage of miflash 2018 version and rom in *.tgz file). This time, I've used help from this page - https://www.getdroidtips.com/guide-flash-miui-rom-xiaomi-devices/ - had some troubles with mediatek based phones before in my life, so it wasn't from scratch, but some time to understand it were needed.
Phone is working again, but this rom is based on Android 10 (which I would like to keep, if it won't cause too much trouble). And I think because of that fastboot mode changed now into fastbootD mode, where old commands from adb does not recognize the device, thus no flashing recovery action etc can be taken.
Is there a workaround here? I've stumbled across some articles about installing clean Generic System Image with Android 10 on this phone (since it has been released with android greater, than number 8), but again - this requires to have custom recovery, prefeably twrp. I cannot do anything about it, because I got back to stock recovery (which now at least works, yesterday phone was so twisted at one point, that he cannot even load this recovery, but somehow managed to open system and fastboot modes normally (!!!)).
Is there a way to work it out? Older miui version, older android version, then twrp, then update via twrp? Or an alternative method, since google changed something in partitions again (not sure, if I get it right, but it might be it)? I would actually like to stay somewhere around miui (at least let it be official with ota support without too much issues), but without twrp I cannot do anything. I also do know, that there aren't any official twrp/pbrp yet (just betas). Could it also be the issue with troubles with installing it and staying it on the phone?
buczek0711 said:
Hello there.
Just like title says - I've got my hands on new Redmi 9 (lancelot) nfc 4/64 version. I've unlocked it from Mi stuff successfully yesterday and wanted to install there twrp, magisk and titanium backup to clean a bit and maybe to have foundations for further change of rom.
However, my phone gaves answers, that I do not understand correctly.
Firstly - after first instalation of twrp via adb it booted into this. However, after choosing option to boot to system from it, power off via ui and then another try to enter recovery...it gave me stock miui recovery again. When I've tried the same steps for second time, phone finished, but after restart it entered bootloop. I've followed steps from this guide - https://miui.blog/redmi-9/download-install-twrp-and-root-redmi-9-codename-lancelot/
After some time I've managed to make low-level rom instalation again (12.0.4 official lancelot rom, dated 31st of Mar, 21) to at least being able to communicate with it (done with usage of miflash 2018 version and rom in *.tgz file). This time, I've used help from this page - https://www.getdroidtips.com/guide-flash-miui-rom-xiaomi-devices/ - had some troubles with mediatek based phones before in my life, so it wasn't from scratch, but some time to understand it were needed.
Phone is working again, but this rom is based on Android 10 (which I would like to keep, if it won't cause too much trouble). And I think because of that fastboot mode changed now into fastbootD mode, where old commands from adb does not recognize the device, thus no flashing recovery action etc can be taken.
Is there a workaround here? I've stumbled across some articles about installing clean Generic System Image with Android 10 on this phone (since it has been released with android greater, than number 8), but again - this requires to have custom recovery, prefeably twrp. I cannot do anything about it, because I got back to stock recovery (which now at least works, yesterday phone was so twisted at one point, that he cannot even load this recovery, but somehow managed to open system and fastboot modes normally (!!!)).
Is there a way to work it out? Older miui version, older android version, then twrp, then update via twrp? Or an alternative method, since google changed something in partitions again (not sure, if I get it right, but it might be it)? I would actually like to stay somewhere around miui (at least let it be official with ota support without too much issues), but without twrp I cannot do anything. I also do know, that there aren't any official twrp/pbrp yet (just betas). Could it also be the issue with troubles with installing it and staying it on the phone?
Click to expand...
Click to collapse
After to flash TWRP you have to flash the vbmeta.img and then boot to TWRP not through commands but manually with hardware buttons, don't allow device to boot to system before to boot to custom recovery otherwise this will be overwritten again.
I've done that with this vbmeta, one and only difference might be that I was trying to get into twrp by commands (however, it did not work XD). Overwritten isn't an issue in my opinion, since I do have booted to recovery after installing it yesterday and then from it choose option "reboot to system". After poweroff from system and then trying to get into recovery, then stock showed.
I'm currently trying this - https://c.mi.com/oc/thread-3312019-1-0.html
After putting this command to cmd - bcdedit /set testsigning on lancelot shows somewhere, but I cannot install it (most likely due to this issue about encrypted drivers). I'll try to overcome it now.
Yea, well, I've tried this method from link listed above, phone still enters fastbootd mode, still is not-visible from cmd started from google platform tools folder (which a subfolder to working adb). Not sure what to do now.
buczek0711 said:
I've done that with this vbmeta, one and only difference might be that I was trying to get into twrp by commands (however, it did not work XD). Overwritten isn't an issue in my opinion, since I do have booted to recovery after installing it yesterday and then from it choose option "reboot to system". After poweroff from system and then trying to get into recovery, then stock showed.
I'm currently trying this - https://c.mi.com/oc/thread-3312019-1-0.html
After putting this command to cmd - bcdedit /set testsigning on lancelot shows somewhere, but I cannot install it (most likely due to this issue about encrypted drivers). I'll try to overcome it now.
Click to expand...
Click to collapse
No, this is not the method to boot to recovery from what I pointed out, you don't have to firstly power off device but from fastboot commands you can type either fastboot or fastbootd reboot and inmediately press the volume up till the TWRP logo appears, the fastboot/d command will act same as it be the power button.
The thread explains how to install unsigned drivers in Windows, not to set it on your Redmi but is for your PC. If you succesfully get the drivers installed then you have to reboot your PC entering again in safe mode (not normal mode) and from there the commands through fastbootd are generally the same than those for fastboot.
buczek0711 said:
Yea, well, I've tried this method from link listed above, phone still enters fastbootd mode, still is not-visible from cmd started from google platform tools folder (which a subfolder to working adb). Not sure what to do now.
Click to expand...
Click to collapse
Just to be sure you are doing fine and not missing something the adb commands work while device is on and fastboot/d commands work only in fastboot mode.
Can you attach some SS to see what you are typing and the error that brings the cmd?
Hm, you say, that I can type fastbootd into cmd and this will be recognised? It seems that it cannot be recognised in this case, when I'm trying to type fastbootd powershell says "unknown command".
Typing fastboot /d devices results in "waiting for device", despite phone being in fastbootd all the time.
I'll attach ss tomorrow - it is time to sleep for me now, gotta wake up early. Then we will also know something else, when it comes to behavior after restart pc (once again, I've done it all in one sit, it might be an issue here).
PS. if you want english errors, I'll have to use powershell - cmd is in my native language (polish). Found out, that it doesn't really matter, which program you use, powershell simply can do more, while cmd dates back 30 years or so.
Anyway - phone is still booting to miui 12 and android 10 normally, I do not set there google acc or lock yet, so don't know if there's any issue with it (most likely no).
I've also stumbled across some dude from indonesia, who had the same phone, miui 12.0.1 with android 10 and he installed successfully twrp, then magisk, but he also put some small img - misc misc.img. Could it be the issue?
I'm giving link to this material on YT -
FROM WHAT I SEE IN THE THUMBNAIL, this version of twrp is even the same (code number and english translated from chinese), that once worked here (md5 of the file might be different, though).
There's also an option to reinstall again whole adb, platform tools, drivers from official miunlock app etc, but since I do not had ANY android-related problems on this pc with previous phones, I'm not sure if this is worth our time.
And I think that if I would misspell something in cmd program would give me error instantly, instead of behaving like it was nothing - i've made tons of errors before and cmd/powershell always informed me about it in first line of their texts.
buczek0711 said:
Hm, you say, that I can type fastbootd into cmd and this will be recognised? It seems that it cannot be recognised in this case, when I'm trying to type fastbootd powershell says "unknown command".
Typing fastboot /d devices results in "waiting for device", despite phone being in fastbootd all the time.
Click to expand...
Click to collapse
Yes, fastboot works normally while in cmd, this is intended for that, no problem to enter firstly toi Power Shell but you can switch to cmd from PS just typing cmd and all the commands from here will be for cmd, doesn´t matter at all how many old is, cmd can work inside PS keeping the same aspect.
buczek0711 said:
I'll attach ss tomorrow - it is time to sleep for me now, gotta wake up early. Then we will also know something else, when it comes to behavior after restart pc (once again, I've done it all in one sit, it might be an issue here).
PS. if you want english errors, I'll have to use powershell - cmd is in my native language (polish). Found out, that it doesn't really matter, which program you use, powershell simply can do more, while cmd dates back 30 years or so.
Anyway - phone is still booting to miui 12 and android 10 normally, I do not set there google acc or lock yet, so don't know if there's any issue with it (most likely no).
I've also stumbled across some dude from indonesia, who had the same phone, miui 12.0.1 with android 10 and he installed successfully twrp, then magisk, but he also put some small img - misc misc.img. Could it be the issue?
I'm giving link to this material on YT -
FROM WHAT I SEE IN THE THUMBNAIL, this version of twrp is even the same (code number and english translated from chinese), that once worked here (md5 of the file might be different, though).
There's also an option to reinstall again whole adb, platform tools, drivers from official miunlock app etc, but since I do not had ANY android-related problems on this pc with previous phones, I'm not sure if this is worth our time.
And I think that if I would misspell something in cmd program would give me error instantly, instead of behaving like it was nothing - i've made tons of errors before and cmd/powershell always informed me about it in first line of their texts.
Click to expand...
Click to collapse
You don't need to reinstall nothing, just from the downloaded SDK platform do all that you want to avoid misspelling path and folder directories, I mean place the files you need to use in the same directory and open terminal prompt (PS) in the same folder where adb/fastboot binaries are, pressing right mouse button and shift at same time.
I feel you are missing something simply here, not so hard to do.
The misc.img partition that you mentioned is just to restore something that went wrong in the process.
But if you are happy with this Miui ROM then great. No hurry to answer that, give your time to rest.
I also feel, that there is something simply to overcome, Only the fastbootd is new Stuff to me. However, any time I was doing something with Snap, i was long after finish by the current time (almost a month with It and 3rd day with fastbootd issue).
I don't get it. Now when I've tried to enter fastboot mode...phone entered it (fastboot, not fastbootD). Then I've installed pitch black recovery and sucessfully booted into it by restarting phone and then pressing vol up. Now I'm trying with magisk and another entry to pbrp.
Second try gave me stock recovery again. What is wrong with it XD?
something is wrong. Installing twrp resulting in nothing (stock recovery is still there), installing pitch black resulting in successfully boot into new recovery. However, this recovery does not see any zip (magisk zip, to be exact, that I've put there before it to root phone). After boot into system and then power it off to boot into recovery...phone boots into stock recovery. Should I downgrade system to miui 11 to be able to get over it? Or should I wait until miui 12.5 enters redmi 9?
My tries of installing it has been done by using cmd with admin rights, if it does make any difference.
buczek0711 said:
something is wrong. Installing twrp resulting in nothing (stock recovery is still there), installing pitch black resulting in successfully boot into new recovery. However, this recovery does not see any zip (magisk zip, to be exact, that I've put there before it to root phone). After boot into system and then power it off to boot into recovery...phone boots into stock recovery. Should I downgrade system to miui 11 to be able to get over it? Or should I wait until miui 12.5 enters redmi 9?
My tries of installing it has been done by using cmd with admin rights, if it does make any difference.
Click to expand...
Click to collapse
I think you are not following the right direction, if you want consider what I pointed out; you don't have to power off device prior to boot to recovery for first time but you have to type from fastboot (no matter fastbootd) and inmediately from there boot to the custom recovery, when you succesfully booted to custom recovery then flash the recovery zip if there is one (PBR and OFR have one) and if not a zip then flash the image again to the recovery partition, also check if there is some installer apart from the image that can fix it in the ramdisk partition, at this point your issue is solved, next step is to reboot device to system normally, if you don't have any issue on that then OK but if you can´t there some steps more that you should do, but let this for last.
Ok, let's group it.
I do not think that particular matter of how do I restart phone matters here (at least, I do not believe it, that it does anything).
Option to restart to recovery from adb still not working.
Trying to find magisk.zip in main directory of internal storage still fails under pitch black recovery project.
From new stuff - I now got an error message, while opening pbrp, most likely with the issues about system being read-only (not sure though, since I do not remember it now, might look into it once more). I have the options to mount partitions, available from main menu, but since I do not used it at all before, I do not know, how to deal with it.
Also - my system boots normally, it must have overwritten recovery (or at least header of it) sometime during boot, since custom recovery is unavailable to access after first full reboot.
I'll try now to install newer version of twrp from yt that I've posted days back. I would also try with orange fox (however, i cannot find img for it, just source code, don't get it).
Is there someone, who can and will to help me?
Situation looks this - on this 12.0.4 MIUI with android 10 I'm unable to install ANY recovery (either phone do not restart to recovery after proper command from cmd or it boots into it, but after visiting system and then to recovery again it shows stock (even without any operations or updates from ota).
I cannot force to work either twrp 3.4.2b, twrp 3.5.2, pitch black recovery 3.0.0 beta.
After trying to install magisk 21.4 zip from twrp 3.4.2b phone entered bootloop, because f**k you, user, I cannot even get it to fastboot mode now (btw, fastboot now works, fastbootD is luckily a long-gone crap).
All cmd's have been run with admin rights. There are NO SUCH THING, as misspelling (cmd and adb would not execute command ,if it is misspelled, either command or filename). I've installed drivers once again and used cmd from dedicated folder with adb fastboot portable version (runned as admin, of course).
Now I'm downloading older version of rom for fastboot (miui 11.0.9) with android 10. Something has to finally work on this piece of junk.
Writting each time is success (cmd says "OKAY" nad displays time, it took to do so), downloading recovery image to start from it also works, there aren't any errors in cmd, yet phone still isn't working.
Where's the issue with it? Apart from being mediatek, which seems to somehow enormously hardened any flashing? I did not encounter anything like this with qualcomm, yet mediatek still manages to pisses me off with their really weird implementations and working (???) of their stuff.
another update from battlefield. Managed to finally get mediatek verify bypass in smart phone flashing tool, however it ended with forcing me to format anything in the phone (if not, program would not let me install anything).
Second problem is forcing me to disable verify, yet command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img put in fastboot mode (yes, it works now) does not work, because adb says, that "--disable-verity" is not a recognised command.
SPFT cannot properly download images from phone and welcomes me with error about download exception, happening either in recovery part or in boot part. SInce I do have access to fastboot now, I can overcome it (I think).
Old miflash tool to install roms via fastboot says it cannot flash rom in locked stage (I might have lost unlocked status, but I'm not sure about it). Do you know ways to overcome it?
It is me again (inb4 use edit). Had to unlock phone again by using miphone unlocker (it went ok). Still cannot flash using SPFT, miflash started showing idiotic errors like "no file in directory" or "cannot access to directory" (it could before, I did not changed name of it). Will continue reporting of progress (or the so-called "progress").