Database Develop

Troubles reinstalling TWRP [Failed to load/authenticate boot image: Load Error]

I dirty flashed a new version of xiaomi.eu stable build, and it caused TWRP to uninstall itself.
Whenever I hold power on and volume up it just goes to fastboot.
Now I tried reinstalling TWRP like I've done many times before, but it keeps throwing an error. The error I get is when trying to boot without flashing the img. When I do this, I get the error:
Code:
fastboot boot TWRP.img"
downloading 'boot.img'...
OKAY [ 1.609s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.675s
Anyone gotten any ideas on what could be going on here? I'm scared to try anything as my phone currently works, but I need TWRP back to update my phone to a different versions and to install the clock mod again.
Thanks!

Got it to load once, but now back to square one. Throwing same error.

Now when running the command fastboot reboot recovery it's saying
Code:
fastboot: usage: unknown reboot target recovery
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.

Try on a computer with a USB 2.0 port, or a different usb cable, had the same issue once

Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.

I have the same error. How can I fix this pls?

MrkoZino said:
I have the same error. How can I fix this pls?
Click to expand...
Click to collapse
Flash the latest official rom then start all over again. Follow the post above you about miflash.

Hello, I've had the same problem, then flashed latest dev rom via MiFlash and it booted, but now after I flash any custom ROM in TWRP i have this issue again and need to reflash chinese ROM. How can I flash any custom rom?

i'm stuck in the same issue. stuck in fastboot and it would not load recovery. any fix?

Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
greendra8 said:
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.
Click to expand...
Click to collapse
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?

DJPlaya said:
Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?
Click to expand...
Click to collapse
long time ago now. but i remember at one point having to flash the stock firmware using the mi unlock tool. i also remember trying every single version of twrp and rom until one finally worked. sorry i can't help much but i believe that's how i eventually fixed it.

hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp

Marihot said:
hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp
Click to expand...
Click to collapse
Where do you get these .img files?

iconoclasthero said:
Where do you get these .img files?
Click to expand...
Click to collapse
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder

Marihot said:
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder
Click to expand...
Click to collapse
Please tell the details for this method

greendra8 said:
Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.
Click to expand...
Click to collapse
BROOOOOOOOOO HAHAHAHAHAHA I LITERALLY JUST READ YOUR COMMENT AND 10 SECONDS LATER I FLASH THE ROM WITH "CLEAN ALL AND LOCK" Im a f-king dumb bro

Marihot said:
你好，我也经历过同样的事情。
这个方法帮助我摆脱它。
尝试使用 adb 从要在 hh 中安装的 rom 中重新刷新一些文件映像。
将下面的文件从 rom 映像复制到 adb 文件夹
1.system.img（adb >> fastboot flash system system.img中的命令）
2. boot.img（adb 中的命令，如#1，更改 img 文件的名称）直到 #6
3. 供应商.img
4.dtbo.img
5. 自定义.img
6. 杂项.img
7. 现在用adb刷twrp/recovery.img（选择twrp与你要安装的rom兼容）
8. adb 的“fastboot boot recovery.img”
9. twrp刷入rom
Click to expand...
Click to collapse
Thank you, brother

try fastboot set_active a
or fastboot set_active b

Device is corrupt. It can't be trusted and will not boot

Can't even fastboot flash boot recovery system...and thats all folks...waste of money.

Failed attempt to unlock the bootloader and instal TWRP ?

Hi guys, visit this link. We had similar problems and we could solved that.
Read all and you would get the solution
https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page9

roadworker said:
Failed attempt to unlock the bootloader and instal TWRP ?
Click to expand...
Click to collapse
No I installed Chinese v2.27.... Well it's absolute mess like I never seen Android before. Then attempted to flash global again, problems to the point of corruption. I have fastboot flashed all key elements of working Android phone multiple times. Can only get to fastboot after boot screen that I have to do manually. Recovery system is toast.... Guess it's back to Poco F1.... Learned my lesson from junk.

Just flash the ROM again..It will be back lm

mhex said:
Just flash the ROM again..It will be back lm
Click to expand...
Click to collapse
Trying to NA Global original rom, problem is no recovery at all....I can only flash within fastboot.....which is not a problem, but phone is not taking it flashing all images individually and modem. And I know it's flashing cause fastboot is saying okay and bootloader showing unlocked

SuperDroidMe said:
Trying to NA Global original rom, problem is no recovery at all....I can only flash within fastboot.....which is not a problem, but phone is not taking it flashing all images individually and modem. And I know it's flashing cause fastboot is saying okay and bootloader showing unlocked
Click to expand...
Click to collapse
Every time you restart back to the bootloader you need to do: "fastboot oem nubia_unlock NUBIA_NX629J" first

SuperDroidMe said:
No I installed Chinese v2.27.... Well it's absolute mess like I never seen Android before. Then attempted to flash global again, problems to the point of corruption. I have fastboot flashed all key elements of working Android phone multiple times. Can only get to fastboot after boot screen that I have to do manually. Recovery system is toast.... Guess it's back to Poco F1.... Learned my lesson from junk.
Click to expand...
Click to collapse
So YOU mess up your phone by trying to flash sh!t and you blame the MANUFACTURER? Yeah ok. Lmao. Enjoy the new paperweight that YOU CREATED.

xphyle1971 said:
So YOU mess up your phone by trying to flash sh!t and you blame the MANUFACTURER? Yeah ok. Lmao. Enjoy the new paperweight that YOU CREATED.
Click to expand...
Click to collapse
LMAO if you can't go from stock global to stock Chinese and reverse from the manufacturer with their recovery, you haven't got a prayer for custom roms or mods.

SuperDroidMe said:
LMAO if you can't go from stock global to stock Chinese and reverse from the manufacturer with their recovery, you haven't got a prayer for custom roms or mods.
Click to expand...
Click to collapse
if you stuck in the Device is corrupt. It can't be trusted and will not boot and you are in the Chinese or global rom then flash the stock boot image via adb. well I am using a Chinese v2.27 rom with rooted +gapps and then realized that most of the google apps wont work correctly because of the unlocked bootloader. I tried to lock the bootloader via adb then the message "Device is corrupt. It can't be trusted and will not boot" show up. so I try to use adb to flash the stock boot image then it work. first place the stock boot image to the "Minimal ADB and Fastboot" folder which located in the local drive under program file(x86) then run the command
fastboot flash boot boot.img
fastboot reboot

mswl04 said:
if you stuck in the Device is corrupt. It can't be trusted and will not boot and you are in the Chinese or global rom then flash the stock boot image via adb. well I am using a Chinese v2.27 rom with rooted +gapps and then realized that most of the google apps wont work correctly because of the unlocked bootloader. I tried to lock the bootloader via adb then the message "Device is corrupt. It can't be trusted and will not boot" show up. so I try to use adb to flash the stock boot image then it work. first place the stock boot image to the "Minimal ADB and Fastboot" folder which located in the local drive under program file(x86) then run the command
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Bud I put so much effort in last 13 hours to no avail....fastboot erased all partitions, reformatted, reflashed to no avail. Right now it just boots loops on Chinese 2.27 boot splash, I do have Chinese recovery though, but the same otg adapter and pen drive that works on 5 different devices, this damn phone won't read it so even that is out of the question. I wipe my hands clean of it, some things just best to put a bullet through it.

SuperDroidMe said:
Bud I put so much effort in last 13 hours to no avail....fastboot erased all partitions, reformatted, reflashed to no avail. Right now it just boots loops on Chinese 2.27 boot splash, I do have Chinese recovery though, but the same otg adapter and pen drive that works on 5 different devices, this damn phone won't read it so even that is out of the question. I wipe my hands clean of it, some things just best to put a bullet through it.
Click to expand...
Click to collapse
btw did you rooted the phone?

mswl04 said:
btw did you rooted the phone?
Click to expand...
Click to collapse
No BS, all I did was flash CN 2.27 over NA Global, after a look at the mess it was I proceeded to flash NA Global back.....no TWRP No Root with SuperSU or Magisk. But in fastboot it does say Root=1, so I guess the CN 2.27 rooted it by default cause I sure as hell didn't. One thing that is bothering me while in fastboot unlock bootloader I can't turn Secure Boot off which I believe is why it won't boot system.

SuperDroidMe said:
No BS, all I did was flash CN 2.27 over NA Global, after a look at the mess it was I proceeded to flash NA Global back.....no TWRP No Root with SuperSU or Magisk. But in fastboot it does say Root=1, so I guess the CN 2.27 rooted it by default cause I sure as hell didn't. One thing that is bothering me while in fastboot unlock bootloader I can't turn Secure Boot off which I believe is why it won't boot system.
Click to expand...
Click to collapse
don't give up I know how do you feel did you download this update from the official red magic website http://ui.nubia.cn/rom/detail/62 after you download the update and it will be in a zip file extract the boot image. then try to follow the root guild https://forum.xda-developers.com/red-magic-3/how-to/red-magic-3-root-guide-t3933148 in the website download the adb and then run the command which I reply earlier
seem to me it is like a soft brick

mswl04 said:
don't give up I know how do you feel did you download this update from the official red magic website http://ui.nubia.cn/rom/detail/62 after you download the update and it will be in a zip file extract the boot image. then try to follow the root guild https://forum.xda-developers.com/red-magic-3/how-to/red-magic-3-root-guide-t3933148 in the website download the adb and then run the command which I reply earlier
seem to me it is like a soft brick
Click to expand...
Click to collapse
I got CN version 2.27 images, am I supposed to be using one of the other versions off the official site?

SuperDroidMe said:
I got CN version 2.27 images, am I supposed to be using one of the other versions off the official site?
Click to expand...
Click to collapse
all you need to do is to fix the corrupt image so later once you finish the first step of booting to the phone then you can flash to global rom. if you have the cn version 2.27 boot.img then you can download the adb and use the command to fix the phone

Shouldn't have messed with something that wasn't broken. Now you have a nice brick to use as a paperweight. Hope you get it fixed tho. Good luck.

Solved Instructions:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot bootloader
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot flash dsp dspso.bin
fastboot oem nubia_lock NUBIA_NX629J
fastboot reboot
*****as soon as boot screen appears hold volume + button, now in recovery...navigate to wipe data and then wipe cache....then plug in otg usb pen drive (formatted FAT32) with Rom package .zip....navigate to update otg in recovery select it let it do its thing and walla your phone is fixed.
*****if you ever go from CN rom to Global rom you must Wipe Data and Cache through recovery, it is not enough to do it in fastboot and your device will remain soft bricked.

SuperDroidMe said:
Solved Instructions:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot bootloader
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot flash dsp dspso.bin
fastboot oem nubia_lock NUBIA_NX629J
fastboot reboot
*****as soon as boot screen appears hold volume + button, now in recovery...navigate to wipe data and then wipe cache....then plug in otg usb pen drive (formatted FAT32) with Rom package .zip....navigate to update otg in recovery select it let it do its thing and walla your phone is fixed.
*****if you ever go from CN rom to Global rom you must Wipe Data and Cache through recovery, it is not enough to do it in fastboot and your device will remain soft bricked.
Click to expand...
Click to collapse
Congrat you finally fix it

Hows your phone?..Did it work.

MI9 can't boot and stucked in fastboot

Hello all.
Here is my problem
I successfully unlocked my bootloader and I flashed latest maunofrio twrp v35
In TWRP, I did a full wipe in TWRP and formatted data partition to remove encryption
But now, I can't boot again in twrp and I'm stucked in fastboot.
Vol UP + power does not boot in twrp but still in fastboot..
When I hit the command : fastboot flash recovery recovery.img, it says OK
But fastboot boot recovery.img no longer workos now, failed
( before wiping and formatting all it worked )
I don't know what to do now to access twrp..
Any help is very appreciated
Greetings

Try another recovery and if it failed try full flash latest stable rom

Well, I have been warning so many times that use any TWRP in MI9:
1. format data partition
2. reboot TWRP and then enter twrp. Make twrp mount data partition
3. wipe everything BUT please keep system partition only
4. reboot twrp and then enter twrp again
5. Now wipe system partition and then flash any rom you want
6. reboot
How to save your phone now ? Please try fastboot ROM and use miflash app to save your phone !
Kris
ManuBBXX said:
Hello all.
Here is my problem
I successfully unlocked my bootloader and I flashed latest maunofrio twrp v35
In TWRP, I did a full wipe in TWRP and formatted data partition to remove encryption
But now, I can't boot again in twrp and I'm stucked in fastboot.
Vol UP + power does not boot in twrp but still in fastboot..
When I hit the command : fastboot flash recovery recovery.img, it says OK
But fastboot boot recovery.img no longer workos now, failed
( before wiping and formatting all it worked )
I don't know what to do now to access twrp..
Any help is very appreciated
Greetings
Click to expand...
Click to collapse

@Kris Chen I am in similar situation here... Can you please help?
First of all - which TWRP should we use for Mi9T? IS this one good? https://mifirm.net/model/davinci.ttt#other-twrp
After flashing recovery-TWRP-3.3.1-0607-REDMI_K20-CN-wzsx150.img - fastboot boot twrp.img goes okay
And then after "fastboot boot twrp.img" the phone restarts and is just stuck on the "semitransparent" MI logo...
I can press Vol+- and power buttons and boot into Mi 3 recovery, wipe data, set up the phone again. And then it is all over again. I am new to this and probably making some basic mistake?
EDIT. I think the mistake was to trying to use a wrong TWRP...

Some questions here:
1. Is Redmi K20 CN the same as Mi9T?
If yes, that twrp is correct and the best one
2.After flashing twrp, can you enter twrp by general
method : power + volume up to enter twrp?
If yes, I think the problem is coming from your data
partition. Please format your data partition first and
then reboot to Twrp again. Then copy your rom in your
phone and then wipe cache/ dalvik cache/system. Next
to flash rom. Always Remeber not to reboot your
phone if you haven't flashed rom under twrp after
flashing system partition.
Kris
Ardysan said:
@Kris Chen I am in similar situation here... Can you please help?
First of all - which TWRP should we use for Mi9T? IS this one good? https://mifirm.net/model/davinci.ttt#other-twrp
After flashing recovery-TWRP-3.3.1-0607-REDMI_K20-CN-wzsx150.img - fastboot boot twrp.img goes okay
And then after "fastboot boot twrp.img" the phone restarts and is just stuck on the "semitransparent" MI logo...
I can press Vol+- and power buttons and boot into Mi 3 recovery, wipe data, set up the phone again. And then it is all over again. I am new to this and probably making some basic mistake?
EDIT. I think the mistake was to trying to use a wrong TWRP...
Click to expand...
Click to collapse

Thank you Kris!

Download the fastboot rom (Google it )then flash it with miflashtool just make sure the archive of the ROM is "tgz"before you unzip it .

Failykun said:
Download the fastboot rom (Google it )then flash it with miflashtool just make sure the archive of the ROM is "tgz"before you unzip it .
Click to expand...
Click to collapse
This is what I had to do both times this happened.

I have the same exact problem
I used the same TWRP and I also wiped system.
Did you fixed it already?

RebornCheiko said:
I have the same exact problem
I used the same TWRP and I also wiped system.
Did you fixed it already?
Click to expand...
Click to collapse
As i understand, you wiped system and then restarted? And now you can enter only fastboot?
When you wipe system you must flash a ROM without restart or after restart, only fastboot available. TWRP version has nothing to do with this.
Now you must use mi flash or adb and fastboot utility. Download fastboot version of ROM, then open archive and flash it using mi flash or flash_all.bat script. flash_all_lock.bat will also lock your bootloader and mi flash has that option too, so check twice what option you choose
After flashing ROM you can flash TWRP again and it will be available, because by flashing ROM you restored system

I had the same problem.
Try to flash vbmeta.img via fastboot (fastboot --disable-verity flash vbmeta vbmeta.img) and then flash recovery then boot recovery.
Or try to flash boot.img (fastboot flash boot boot.img) then flash recovery.

ManuBBXX said:
Hello all.
Here is my problem
I successfully unlocked my bootloader and I flashed latest maunofrio twrp v35
In TWRP, I did a full wipe in TWRP and formatted data partition to remove encryption
But now, I can't boot again in twrp and I'm stucked in fastboot.
Vol UP + power does not boot in twrp but still in fastboot..
When I hit the command : fastboot flash recovery recovery.img, it says OK
But fastboot boot recovery.img no longer workos now, failed
( before wiping and formatting all it worked )
I don't know what to do now to access twrp..
Any help is very appreciated
Greetings
Click to expand...
Click to collapse
I got you chief. Make sure you have adb and fastboot installed.
No you don't need Mi flash tool for this. All you need is a computer.
Go to fastboot mode, plug in your device and expand cepheus.tgz file you downloaded. Link below
https://xiaomifirmwareupdater.com/
Now open the folder. You have the flash_all files in there. Any .bat file is for Windows only. Any .sh files are for Mac and Linux.
Make sure the device is recognized in fastboot via cmd or terminal
WINDOWS ONLY: Open Command prompt and drag flash_all.bat into the cmd window and press enter
MAC/LINUX: Open terminal and drag flash_all.sh into the terminal window and press enter.
This part requires some patience. Wait until everything is finished.
Reboot using power button and it should be back to normal.

Mi A2 has not slot b

As I say in the tittle, my phone has not slot b. It means that when I try to flash any .img or .zip I have an error message telling my that "XXX_b not accesible".
How can I create the partition? I have android one and everything locked as I flashed the stock image vía COM because I have no idea how to solve the partition problem.

gfpablo_ said:
As I say in the tittle, my phone has not slot b. It means that when I try to flash any .img or .zip I have an error message telling my that "XXX_b not accesible".
How can I create the partition? I have android one and everything locked as I flashed the stock image vía COM because I have no idea how to solve the partition problem.
Click to expand...
Click to collapse
You say you are trying to flash something but then you also say that everything is locked. You can't flash anything other than the stock firmware (in EDL mode) if your bootloader is locked.

Catsonvi said:
You say you are trying to flash something but then you also say that everything is locked. You can't flash anything other than the stock firmware (in EDL mode) if your bootloader is locked.
Click to expand...
Click to collapse
I tried to flash it when i have everything unlocked. I tried to flash ASOP v6.6 and the result was a bricked phone. However I flashed the android one stock ROM and locked everything with the Xiaomi flash program.

You need to flash stock through EDL

Nebrassy said:
You need to flash stock through EDL
Click to expand...
Click to collapse
That's what i've done. Although, if I try to flash TWRP from fastboot I have an error message telling me that I have no slot b

gfpablo_ said:
That's what i've done. Although, if I try to flash TWRP from fastboot I have an error message telling me that I have no slot b
Click to expand...
Click to collapse
You can't flash the TWRP image from fastboot, since our phone does not have a seperate recovery partition and you also cannot flash ANYTHING (other than stock via EDL) if your phone's bootloader is locked.
Now since it seems that your bootloader is locked, you need to enable developer options first and then in developer options enable the "OEM unlocking" option. After that you need to go to fastboot in order to unlock the bootloader and use these commands one at the time:
fastboot flashing unlock
fastboot flashing unlock_critical
Keep in mind that after using these commands you will get a prompt on your phone to confirm that you want to unlock the bootloader and doing so will erase everything (basically like doing a factory reset).
After you fully unlock the bootloader, in order to flash TWRP with stock you need to go to the official TWRP website and find the .img and the .zip installer for the Mi A2. You need to boot the .img via fastboot with fastboot boot *location to the .img* (without the asterisks) and then transfer and flash the TWRP .zip installer with TWRP. After that you can boot into TWRP normally without fastboot booting.
If you want to flash a custom ROM you will still need to fastboot boot into the TWRP .img because the .zip you flashed is tied to the system, and since you need to wipe the system before flashing a custom ROM you will also wipe the flashed TWRP.
I still recommend reading this guide: https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375

[SOLVED]
Catsonvi said:
You can't flash the TWRP image from fastboot, since our phone does not have a seperate recovery partition and you also cannot flash ANYTHING (other than stock via EDL) if your phone's bootloader is locked.
Now since it seems that your bootloader is locked, you need to enable developer options first and then in developer options enable the "OEM unlocking" option. After that you need to go to fastboot in order to unlock the bootloader and use these commands one at the time:
fastboot flashing unlock
fastboot flashing unlock_critical
Keep in mind that after using these commands you will get a prompt on your phone to confirm that you want to unlock the bootloader and doing so will erase everything (basically like doing a factory reset).
After you fully unlock the bootloader, in order to flash TWRP with stock you need to go to the official TWRP website and find the .img and the .zip installer for the Mi A2. You need to boot the .img via fastboot with fastboot boot *location to the .img* (without the asterisks) and then transfer and flash the TWRP .zip installer with TWRP. After that you can boot into TWRP normally without fastboot booting.
If you want to flash a custom ROM you will still need to fastboot boot into the TWRP .img because the .zip you flashed is tied to the system, and since you need to wipe the system before flashing a custom ROM you will also wipe the flashed TWRP.
I still recommend reading this guide: https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Click to expand...
Click to collapse
Thank you! I have to admit that I have no idea of whats wrong earlier. This guide solved the problem tho.

Question The partion doesn't exist

I am trying to flash custom recovery via fastboot method and i face en error after i enter this commond {fastboot flash recovery recovery location and enter then it show me :- remote (The partion doesn't exist)
I change multiple laptop and try again and again stil face this error.
Someone please help me to fix this problem

Awnish said:
I am trying to flash custom recovery via fastboot method and i face en error after i enter this commond {fastboot flash recovery recovery location and enter then it show me :- remote (The partion doesn't exist)
I change multiple laptop and try again and again stil face this error.
Someone please help me to fix this problem
Click to expand...
Click to collapse
Shouldn't it be "fastboot flash recovery.img recovery"?
Edit: sorry, mixed it up myself "flash recovery recovery.img"

fastboot flash recovery recovery.img

jjsan said:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
It doesn't work after enter commond i show this error (the partion doesn't exist) and recovery not install

bmwdroid said:
Shouldn't it be "fastboot flash recovery.img recovery"?
Click to expand...
Click to collapse
Yes

can you try to boot recovery without flashing?
in bootloader mode:
fastboot boot recovery.img

jjsan said:
can you try to boot recovery without flashing?
in bootloader mode:
fastboot boot recovery.img
Click to expand...
Click to collapse
Can you explain it

it will try to bood it without flash. i was using it like this for a long time. and you will see if the recovery is ok

Cn yo
jjsan said:
it will try to bood it without flash. i was using it like this for a long time. and you will see if the recovery is ok
Click to expand...
Click to collapse
Can you explain the complete method or any video or Photo

do you guys even know that fastboot flash boot boot.img works with TWRP?
this is the only way to flash TWRP

Bro after this i face black screen only. Phone doesn't boot even phone doesn't boot in stock recovery.phone boot only fastboot mode.

you need to patch both boot partitions
fastboot flash boot_a file.img
fastboot flash boot_b file.img
then
fastboot reboot

jjsan said:
you need to patch both boot partitions
fastboot flash boot_a file.img
fastboot flash boot_b file.img
then
fastboot reboot
Click to expand...
Click to collapse
Can you provide.img files

you can get one from image using tool
its the same for both
this one is for 12.5.18.0

Thanks buddy i will try it.

Awnish said:
Thanks buddy i will try it
Click to expand...
Click to collapse
i updated today to 13.0.8.0 and remember about this.
were you successful?