Database Develop

help to unbrick

i have just rooted my tf701
but i messed up the bootanimation.zip
and want to revert the stock
i have downloaded WW_epaduser_10_14_1_47_UpdateLauncher
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot reboot boo
tloader
< waiting for device >
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot flash boot
boot.img
< waiting for device >
target reported max download size of 643825664 bytes
sending 'boot' (5936 KB)...
OKAY [ 0.806s]
writing 'boot'...
OKAY [ 0.200s]
finished. total time: 1.006s
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot flash syst
em blob
target reported max download size of 643825664 bytes
erasing 'system'...
OKAY [ 1.580s]
sending 'system' (1379 KB)...
OKAY [ 0.193s]
writing 'system'...
OKAY [ 0.057s]
finished. total time: 1.830s
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot flash syst
em WW_epaduser_10_14_1_47_UpdateLauncher.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 348226856 is not a multiple of t
he block size 4096
erasing 'system'...
OKAY [ 1.108s]
sending sparse 'system' (628732 KB)...
error: write_sparse_skip_chunk: don't care size 348226856 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 348226856 is not a multiple of t
he block size 4096
OKAY [ 86.138s]
writing 'system'...
OKAY [ 17.136s]
sending sparse 'system' (340068 KB)...
OKAY [ 46.638s]
writing 'system'...
OKAY [ 9.278s]
finished. total time: 160.298s
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.021s
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
but i am still stuck in the asus logo
someone help
now fastboot wont even work someone help

D3LTA-V said:
i have just rooted my tf701
but i messed up the bootanimation.zip
and want to revert the stock
i have downloaded WW_epaduser_10_14_1_47_UpdateLauncher
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot reboot boo
tloader
< waiting for device >
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot flash boot
boot.img
< waiting for device >
target reported max download size of 643825664 bytes
sending 'boot' (5936 KB)...
OKAY [ 0.806s]
writing 'boot'...
OKAY [ 0.200s]
finished. total time: 1.006s
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot flash syst
em blob
target reported max download size of 643825664 bytes
erasing 'system'...
OKAY [ 1.580s]
sending 'system' (1379 KB)...
OKAY [ 0.193s]
writing 'system'...
OKAY [ 0.057s]
finished. total time: 1.830s
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot flash syst
em WW_epaduser_10_14_1_47_UpdateLauncher.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 348226856 is not a multiple of t
he block size 4096
erasing 'system'...
OKAY [ 1.108s]
sending sparse 'system' (628732 KB)...
error: write_sparse_skip_chunk: don't care size 348226856 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 348226856 is not a multiple of t
he block size 4096
OKAY [ 86.138s]
writing 'system'...
OKAY [ 17.136s]
sending sparse 'system' (340068 KB)...
OKAY [ 46.638s]
writing 'system'...
OKAY [ 9.278s]
finished. total time: 160.298s
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.021s
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
but i am still stuck in the asus logo
someone help
now fastboot wont even work someone help
Click to expand...
Click to collapse
First I would retry >fastboot flash staging blob
also that updateLauncher.zip you have has to be extracted once more to get a UL-K00C-WW-10.14.1.47-user.zip then flash that. You will get the parse errors but let it finish. Gonna take awhile.

schmeggy929 said:
First I would retry >fastboot flash staging blob
also that updateLauncher.zip you have has to be extracted once more to get a UL-K00C-WW-10.14.1.47-user.zip then flash that. You will get the parse errors but let it finish. Gonna take awhile.
Click to expand...
Click to collapse
flash drgravy's recovery.img, the v47 blob, start recovery, sideload update 47 zip (this works without errors)

Well now I can't even go into fastboot.
I press and hold vol down and power button. My tf701 justremain stuck at the device is unlocked

so you can't enter the bootloader selection screen?
what does your pc detect when connecting it?

i can only get into APX mode thats all

what firmware version was it when you rooted? was it WW 47?

26 ww

D3LTA-V said:
26 ww
Click to expand...
Click to collapse
so you had root and a running V10.26.1.7
and did this?
WARNING: DO NOT FOLLOW THESE STEPS!
fastboot flash boot boot.img (of the 10_14_1_47)
fastboot flash system blob (of the 10_14_1_47)
fastboot flash system WW_epaduser_10_14_1_47_UpdateLauncher.zip
fastboot reboot
If you did, you bricked it at the point where you flashed the old boot.img (remember, 47 is the old one) and misflashed the blob to system (blob goes to staging...).
all I know can help here, is nvflash (apx), but I have not seen one supporting the TF701...

what can i do now?
i cant access fastboot
only can access apx

D3LTA-V said:
what can i do now?
i cant access fastboot
only can access apx
Click to expand...
Click to collapse
if that's what you did, I can't help you.

so the only thing i can do is to send to the service center?

D3LTA-V said:
so the only thing i can do is to send to the service center?
Click to expand...
Click to collapse
well it's "wait until someone leaks a newer nvflash", or "try sending it back". but I'm pretty sure they're going to charge you a fair amount of cash to fix it, as you voided the warranty (the unlocker app calls home, that's a fact). But I might be wrong. If I were you, I'd wait for a fix. But I'm rather patient. Maybe someone else has better idea...

D3LTA-V said:
so the only thing i can do is to send to the service center?
Click to expand...
Click to collapse
Well send it back in to a service center or Asus is the only thing you can do now.
Since you are rooted and unlocked (do you have some more experience with this?) it is possible to brick your device,
Especially when you make a mistake by flashing the wrong files.
Sad but **** happens.

[Q] Error when flashing system.img

Im currently following a guide to update my encrypted N6 to 5.0.1 and it is all working well up until i go to flash the system.img that i got from 5.0.1 where i get an error.
Code:
C:\Users\Chris\Desktop\android-sdk-windows\platform-tools>fastboot flash system
system.img
target reported max download size of 536870912 bytes
sending 'system' (457800 KB)...
OKAY [ 14.332s]
writing 'system'...
(bootloader) Invalid sparse image
FAILED (status read failed (Too many links))
finished. total time: 14.353s
Im not sure where to go from here, any tips?

Chris_Krz said:
Im currently following a guide to update my encrypted N6 to 5.0.1 and it is all working well up until i go to flash the system.img that i got from 5.0.1 where i get an error.
Code:
C:\Users\Chris\Desktop\android-sdk-windows\platform-tools>fastboot flash system
system.img
target reported max download size of 536870912 bytes
sending 'system' (457800 KB)...
OKAY [ 14.332s]
writing 'system'...
(bootloader) Invalid sparse image
FAILED (status read failed (Too many links))
finished. total time: 14.353s
Im not sure where to go from here, any tips?
Click to expand...
Click to collapse
Your device won't override. So you can erase the system
fastboot erase system -w
then flash
fastboot flash system system.img

Need help rooting At&t Asus Memo Pad 7 LTE (ME375CL) aka K00X, Please Help!

SOLVED!!!
Here is a link to the modified script by me. Thanks to shakalaca for the original script for asus phones. This has only been proven to work on devices running 4.4.4 and below. Please hit the thanks button if this helped you.
http://www.filedropper.com/attasusmemopadlteroot

Solved! I figuired it out!!! I have the method to root the at&t asus memo pad 7 lte!!!

If anyone on XDA needs help rooting this tablet, just reply here and I will assist.

I have been looking for a working root as well to get rid of bloat!

Need help
I need help rooting mine. Please help me!

johnkirchner said:
I have been looking for a working root as well to get rid of bloat!
Click to expand...
Click to collapse
Hello John. Yea I scoured the internet and had no luck finding the ROOT. I used a script I written by "shakalaca", so many thanks to him and his hard work. The script just was hitting on the wrong partition, but everything else was written perfectly. After some trial and error I got it. Now my daughter is super happy, she can enjoy her new tablet. I am busy getting all files in a nice and neat folder, and zipping them up. Then I have to find a place to upload, and after I do will link that up to here for you guys to enjoy! :good::good::good::highfive:

[email protected] said:
I need help rooting mine. Please help me!
Click to expand...
Click to collapse
I will be posting the TOOL up here shortly. I got you broski

Looking forward to it :thumbup:

Can I please get some help with rooting this tablet? I can't find anything other than this thread! HAha HELP!
Skype= brenton.hurt

johnkirchner said:
Looking forward to it :thumbup:
Click to expand...
Click to collapse
_HURT_ said:
Can I please get some help with rooting this tablet? I can't find anything other than this thread! HAha HELP!
Skype= brenton.hurt
Click to expand...
Click to collapse
Ok guys. Here it is. Download the file here www-filedropper-com/attasusmemopad7lteroot
Just replace the (-) with the dots (.)
Hope you guys enjoy, and please SMASH THE THANKS BUTTON!!! Thanks

Did not work on mine...Got the following:

I am getting same errors. I am a newb to the forum so it won't let me paste log. (sees it as an outside link!)
But same error, FAILED remote flash_cmds errors

I'm new to the site and tried other ways of rooting this tablet(had no luck there either). I got the same problems as the other people who tried. Any reasoning why?

johnkirchner said:
Did not work on mine...Got the following:
Click to expand...
Click to collapse
Please attach full log. Also what firmware version are you running? Sorry for the delayed response, been really busy with so many phones like this Droid Turbo 2 thats bricked. I will fix the script if I can figure out the errors. Shouldn't be too hard. Lmk

Hey guys. Sorry i've been so busy. I think I found the reason for the errors and fixed it. Please erase the old zip and folders/files I gave you before. Download this here and voila! Done and Rooted!!!
www-filedropper-com/attasusmemopadlteroot :good::good::good::victory:

The Tech Xperts said:
Hey guys. Sorry i've been so busy. I think I found the reason for the errors and fixed it. Please erase the old zip and folders/files I gave you before. Download this here and voila! Done and Rooted!!!
www-filedropper-com/attasusmemopadlteroot :good::good::good::victory:
Click to expand...
Click to collapse
Please report back and let me know if it works or any errors you may have. Thanks

Firmware is AT&T 12.30.2.10. New file failed with same errors as before.

Same here, not working with new files I just downloaded.
Firmware is ATT_12.30.2.10
I still cannot post logs, but the errors are the same:
Remote: flash_cmds error
in multiple folders.

' Device detected, processing ..
'
'
remote object '/system/bin/asusrmdir1.sh' does not exist
assets\inject.sh
asusrmdir1.sh.bak
1 file(s) copied.
'
'
' Rooting, please be patient ..
'
'
...
FAILED (remote: unknown OEM command)
finished. total time: 0.062s
target reported max download size of 536870912 bytes
sending '/mnt/system/xbin/su' (245 KB)...
OKAY [ 0.109s]
writing '/mnt/system/xbin/su'...
FAILED (remote: flash_cmds error!
)
finished. total time: 0.234s
target reported max download size of 536870912 bytes
sending '/mnt/system/etc/install-recovery.sh' (0 KB)...
OKAY [ 0.094s]
writing '/mnt/system/etc/install-recovery.sh'...
FAILED (remote: flash_cmds error!
)
finished. total time: 0.203s
target reported max download size of 536870912 bytes
sending '/mnt/system/app/Superuser.apk' (5735 KB)...
OKAY [ 0.296s]
writing '/mnt/system/app/Superuser.apk'...
FAILED (remote: flash_cmds error!
)
finished. total time: 0.406s
target reported max download size of 536870912 bytes
sending '/mnt/system/xbin/supolicy' (29 KB)...
OKAY [ 0.094s]
writing '/mnt/system/xbin/supolicy'...
FAILED (remote: flash_cmds error!
)
finished. total time: 0.218s
target reported max download size of 536870912 bytes
sending '/mnt/system/lib/libsupol.so' (290 KB)...
OKAY [ 0.094s]
writing '/mnt/system/lib/libsupol.so'...
FAILED (remote: flash_cmds error!
)
finished. total time: 0.203s
target reported max download size of 536870912 bytes
sending '/mnt/system/bin/asusrmdir1.sh.bak' (2 KB)...
OKAY [ 0.094s]
writing '/mnt/system/bin/asusrmdir1.sh.bak'...
FAILED (remote: flash_cmds error!
)
finished. total time: 0.203s
target reported max download size of 536870912 bytes
sending '/mnt/system/bin/asusrmdir1.sh' (5 KB)...
OKAY [ 0.078s]
writing '/mnt/system/bin/asusrmdir1.sh'...
FAILED (remote: flash_cmds error!
)
finished. total time: 0.187s
'
'
' All done, enjoy your ROOTED device
' by XDA member TheTechXperts, please hit thanks
'
'
rebooting...
finished. total time: 0.062s
Press any key to continue . . .

johnkirchner said:
Firmware is AT&T 12.30.2.10. New file failed with same errors as before.
Click to expand...
Click to collapse
john12065 said:
Same here, not working with new files I just downloaded.
Firmware is ATT_12.30.2.10
I still cannot post logs, but the errors are the same:
Remote: flash_cmds error
in multiple folders.
Click to expand...
Click to collapse
Mtn.Dew said:
' Device detected, processing ..
'
'
remote object '/system/bin/asusrmdir1.sh' does not exist
assets\inject.sh
asusrmdir1.sh.bak
1 file(s) copied.
'
'
' Rooting, please be patient ..
'
'
...
FAILED (remote: unknown OEM command)
finished. total time: 0.062s
target reported max download size of 536870912 bytes
sending '/mnt/system/xbin/su' (245 KB)...
OKAY [ 0.109s]
writing '/mnt/system/xbin/su'...
FAILED (remote: flash_cmds error!
)
finished. total time: 0.234s
target reported max download size of 536870912 bytes
sending '/mnt/system/etc/install-recovery.sh' (0 KB)...
OKAY [ 0.094s]
writing '/mnt/system/etc/install-recovery.sh'...
FAILED (remote: flash_cmds error!
)
finished. total time: 0.203s
target reported max download size of 536870912 bytes
sending '/mnt/system/app/Superuser.apk' (5735 KB)...
OKAY [ 0.296s]
writing '/mnt/system/app/Superuser.apk'...
FAILED (remote: flash_cmds error!
)
finished. total time: 0.406s
target reported max download size of 536870912 bytes
sending '/mnt/system/xbin/supolicy' (29 KB)...
OKAY [ 0.094s]
writing '/mnt/system/xbin/supolicy'...
FAILED (remote: flash_cmds error!
)
finished. total time: 0.218s
target reported max download size of 536870912 bytes
sending '/mnt/system/lib/libsupol.so' (290 KB)...
OKAY [ 0.094s]
writing '/mnt/system/lib/libsupol.so'...
FAILED (remote: flash_cmds error!
)
finished. total time: 0.203s
target reported max download size of 536870912 bytes
sending '/mnt/system/bin/asusrmdir1.sh.bak' (2 KB)...
OKAY [ 0.094s]
writing '/mnt/system/bin/asusrmdir1.sh.bak'...
FAILED (remote: flash_cmds error!
)
finished. total time: 0.203s
target reported max download size of 536870912 bytes
sending '/mnt/system/bin/asusrmdir1.sh' (5 KB)...
OKAY [ 0.078s]
writing '/mnt/system/bin/asusrmdir1.sh'...
FAILED (remote: flash_cmds error!
)
finished. total time: 0.187s
'
'
' All done, enjoy your ROOTED device
' by XDA member TheTechXperts, please hit thanks
'
'
rebooting...
finished. total time: 0.062s
Press any key to continue . . .
Click to expand...
Click to collapse
Really sorry guys to hear you are having issues. My tablet is running build ATT_11.16.1.32. Im assuming if you updated past this, the security flaw was patched. You will have to find a different root method, or try downgrading. Neither one is easy, but if you are persistent you will figure out. I am very busy as I work at an Electronic Repair Facility and work on dozens of devices daily. My experience is mostly in Samsung devices, so I apologize as I am not a developer. But im sure this works, as I can prove it by sending my logs and posting screen shots. So good luck to you all, and God Bless!

please help me

hello iam just newer on xda , & i have probleme with my honor 9 lite is bricked whene iam downgrade my device used hisuite , the device fixed on fastboot mode and black screen , frp locked , bootloader locked
can anyone helpe me please
model : lld-l21

lilolahcen said:
hello iam just newer on xda , & i have probleme with my honor 9 lite is bricked whene iam downgrade my device used hisuite , the device fixed on fastboot mode and black screen , frp locked , bootloader locked
can anyone helpe me please
Click to expand...
Click to collapse
help meeeeeeee please

lilolahcen said:
help meeeeeeee please
Click to expand...
Click to collapse
Can you get into recovery?
Have you held power button for 10 seconds to reboot from fastboot if you can't use terminal

villapark75 said:
Can you get into recovery?
Have you held power button for 10 seconds to reboot from fastboot if you can't use terminal
Click to expand...
Click to collapse
no, i can't get into recovery because the device does'nt boot
i can use a terminal but , when i write fastboot reboot , the device reboots and returns to fastboot

What happens when you issue 'fastboot reboot' hit enter and immediately unplug USB from PC ?

Sparkrite said:
What happens when you issue 'fastboot reboot' hit enter and immediately unplug USB from PC ?
Click to expand...
Click to collapse
i didn' try it , But i flashed the device via adb fastboot
However, the flash does not pass , Just get me this error
failed (remote command not allowed )

lilolahcen said:
i didn' try it , But i flashed the device via adb fastboot
However, the flash does not pass , Just get me this error
failed (remote command not allowed )
Click to expand...
Click to collapse
that my adb show when i am use it
C:\adb>fastboot devices
MKJNW18531002486 fastboot
C:\adb>
C:\adb>fastboot flash recovery_ramdisk recovery_ramdis.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.152s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 1.170s
C:\adb>fastboot flash recovery_vbmeta recovery_vbmeta.img
target reported max download size of 471859200 bytes
sending 'recovery_vbmeta' (6 KB)...
OKAY [ 0.004s]
writing 'recovery_vbmeta'...
FAILED (remote: Command not allowed)
finished. total time: 0.018s
C:\adb>fastboot flash recovery_vendor recovery_vendor.img
target reported max download size of 471859200 bytes
sending 'recovery_vendor' (16384 KB)...
OKAY [ 0.580s]
writing 'recovery_vendor'...
FAILED (remote: Command not allowed)
finished. total time: 0.597s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460796 KB)...
OKAY [ 28.857s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 28.889s
C:\adb>fastboot flash vbmeta vbmeta.img
target reported max download size of 471859200 bytes
sending 'vbmeta' (16 KB)...
OKAY [ 0.005s]
writing 'vbmeta'...
FAILED (remote: Command not allowed)
finished. total time: 0.017s
please can you help me :crying::crying::crying:

lilolahcen said:
that my adb show when i am use it
C:\adb>fastboot devices
MKJNW18531002486 fastboot
C:\adb>
C:\adb>fastboot flash recovery_ramdisk recovery_ramdis.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.152s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 1.170s
C:\adb>fastboot flash recovery_vbmeta recovery_vbmeta.img
target reported max download size of 471859200 bytes
sending 'recovery_vbmeta' (6 KB)...
OKAY [ 0.004s]
writing 'recovery_vbmeta'...
FAILED (remote: Command not allowed)
finished. total time: 0.018s
C:\adb>fastboot flash recovery_vendor recovery_vendor.img
target reported max download size of 471859200 bytes
sending 'recovery_vendor' (16384 KB)...
OKAY [ 0.580s]
writing 'recovery_vendor'...
FAILED (remote: Command not allowed)
finished. total time: 0.597s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460796 KB)...
OKAY [ 28.857s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 28.889s
C:\adb>fastboot flash vbmeta vbmeta.img
target reported max download size of 471859200 bytes
sending 'vbmeta' (16 KB)...
OKAY [ 0.005s]
writing 'vbmeta'...
FAILED (remote: Command not allowed)
finished. total time: 0.017s
please can you help me :crying::crying::crying:
Click to expand...
Click to collapse
Hello. Hope you have enough data on your plan. First download the firmware from this link https: // androidhost . ru / 9X9 (remove the spaces while pasting). Once downloaded extract the contents from the zip file to your pc. Before proceeding make sure your smartphone is charged. In the extracted contents you will have a folder named 'Software'. Inside that folder you will have a folder named 'dload'. Copy the 'dload' folder to the root directory of a formatted sd card. Once it is copied insert the sd card inside your honor 9 lite and press the power, volume up and down buttons simultaneously until your phone enters recovery mode. From there it will take a few minutes for the software installation to be completed. Once the installation is finished your phone will be rebooted and you will have to finish the initial setting up process. If you follow these steps you can recover your phone but you will loose all the data previously present in the phone. Hope this works for you. Please reply if this is successful.

Leeban Joseph said:
Hello. Hope you have enough data on your plan. First download the firmware from this link https: // androidhost . ru / 9X9 (remove the spaces while pasting). Once downloaded extract the contents from the zip file to your pc. Before proceeding make sure your smartphone is charged. In the extracted contents you will have a folder named 'Software'. Inside that folder you will have a folder named 'dload'. Copy the 'dload' folder to the root directory of a formatted sd card. Once it is copied insert the sd card inside your honor 9 lite and press the power, volume up and down buttons simultaneously until your phone enters recovery mode. From there it will take a few minutes for the software installation to be completed. Once the installation is finished your phone will be rebooted and you will have to finish the initial setting up process. If you follow these steps you can recover your phone but you will loose all the data previously present in the phone. Hope this works for you. Please reply if this is successful.
Click to expand...
Click to collapse
Very late to the party, but wanted to thank you for a comprehensive, helpful answer.
The fact lilolahcen didn't respond is hopefully because his phone is working once again.
Good post ?

Thanks. I myself have gone through many guides available here at xda. So I hope I can be of some use for someone who is facing the same problems I have faced.

Question Help restoring Stock ROM [SOLVED]

So... I tried to unlock/root my Redmi Note 11 (SPES), and something went wrong. So now I am trying to fix it, restore to the stock ROM to try again.
How I broke it:
1. Unlocked the bootloader.
2. Installed probably the wrong TWRP (I installed twrp-3.6.2-12.1-21.06.22.img from https://razaoinfo.dl.sourceforge.ne...ld/Recovery-Spes/twrp-3.6.2-12.1-21.06.22.img )
3. I tried flashing said img using fastboot (fastboot flash recovery_a <img>, followed by fastboot flash recovery_b <img>, then fastboot boot <img>
4. Got into TWRP, flashed Magisk.
5. Got into ROM. Everything seems to work, I have root. Next day, I realize my bluetooth is not working.
Next day, I tried flashing another TWRP that I found linked in this forum (twrp-3.6.2_12-0-spes-Jabiyeff.img, downloaded from https://forum.xda-developers.com/t/...-redmi-note-11-and-how-do-i-flash-it.4466177/ post #4).
6. After flashing, ROM no longer boots, and just sends me to fastboot.
7. I checked again with fastboot, and.. it seems the recovery partition isn't there?
Code:
C:\adb2>fastboot.exe devices
ff23ad4 fastboot
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.902s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 2.909s
C:\adb2>fastboot.exe flash recovery_a twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery_a' (131072 KB)...
OKAY [ 2.828s]
writing 'recovery_a'...
FAILED (remote: (recovery_a_b) No such partition)
finished. total time: 2.835s
C:\adb2>fastboot.exe flash recovery_b twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery_b' (131072 KB)...
OKAY [ 2.805s]
writing 'recovery_b'...
FAILED (remote: (recovery_b_b) No such partition)
finished. total time: 2.812s
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.849s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 2.857s
C:\adb2>fastboot.exe boot twrp-3.6.2_12-0-spes-Jabiyeff.img #NOTE: Here I changed the active partition in this TWRP from B to A.
downloading 'boot.img'...
OKAY [ 2.790s]
booting...
OKAY [ 0.367s]
finished. total time: 3.159s
C:\adb2>fastboot.exe devices
ff23ad4 fastboot
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.933s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 2.946s
C:\adb2>fastboot.exe flash recovery_a twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery_a' (131072 KB)...
OKAY [ 2.899s]
writing 'recovery_a'...
FAILED (remote: No such file or directory)
finished. total time: 2.918s
C:\adb2>fastboot.exe flash recovery_b twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery_b' (131072 KB)...
OKAY [ 2.931s]
writing 'recovery_b'...
FAILED (remote: No such file or directory)
finished. total time: 2.943s
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.874s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 2.887s
So, I wonder if I should be concerned about not finding a recovery/recovery_a/recovery_b partition (I am pretty sure recovery_a/b where there when I flashed TWRP the first time).
So, I am following now this guide to install the stock ROM: https://xiaomistockrom.com/xiaomi-redmi-note-11
Am I on the right path? I want to check before proceeding, because... right now I have fast boot and can boot into TWRP using it, but if I do things incorrectly from now on, I could brick the device. So I wanted to ask for advice on what I am doing first here.
TIA.

It's fairly difficult to hard brick a device. Most of the time you'll just end up soft bricking your device which is easy to fix as long as you can access bootloader mode. If you want to fully restore your device to default, you can download your stock rom (fastboot version) and flash using miflash.
Also yes, the guide you linked is correct.

Thanks, I managed to solve it.
The fastboot issue went away some time afterwards, and I could boot normally into the ROM, but... my bluetooth stopped working (which is really strange considering I only flashed the recovery partition). I tried flashing the bluetooth partition from the stock ROM's, but that didn't fix it.
So I tried flashing the stock ROM, following the previously linked guide (and that guide, not the guides that came bundled in the downloaded ROM, that one was for a different device, not a Xiaomi phone at all, weird!).
And now, I have bluetooth again. Thanks goodness for Migrate, I should be able to restore the rest of the device swiftly now.