{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
Features:
Android 11, 12 and 13 support
Supported Devices:
A505F
A505FN
A505G
A505GN
A505GT
Downloads:
https://twrp.me/samsung/samsunggalaxya505f.html
How to install:
Make sure your bootloader is already unlocked and OEM unlock is enabled, otherwise the installation will fail.
Download and install Samsung Drivers
Download the latest *.tar for your phone
Download Odin, from example from https://odindownload.com/
Turn off your phone, connect it to PC and reboot to download mode by holding down Volume up, Volume down and power button at the same time.
Open Odin and check if your device is detected
Put the tar file you downloaded into the AP tab
Click start and wait for the installation to finish, Odin will show PASS
Now press power and volume up to enter twrp
Kernel tree - Github
MTP is not working in this version
how to update twrp?
naansa said:
how to update twrp?
Click to expand...
Click to collapse
Just follow the installation steps
It flashes correctly but returns to download mode with an error (AVB Fail).
Error verifying vbmeta image: invalid vbmeta header
The model is an A505G
AntonioJaramillo said:
It flashes correctly but returns to download mode with an error (AVB Fail).
Error verifying vbmeta image: invalid vbmeta header
The model is an A505G
Click to expand...
Click to collapse
How are you installed?
This recovery does not boot on the A505FN. I've tried flashing through ODIN, didn't work, bricked the device until the AP image is reflashed. The app method also did not work, but it boots into the stock ROM fine if flashed through the app.
Root implementation: Magisk 26.1
TWRP: https://twrp.me/samsung/samsunggalaxya505f.html
I remember getting TWRP to work on this device at some point, is there something that I am missing? Do I need to flash an older version?
GiovanYCringe said:
How are you installed?
Click to expand...
Click to collapse
I flashed it with ODIN, I have already managed to install other unofficial versions, but I wanted to install some official one.
After flashing, it is not possible to back up system files
AntonioJaramillo said:
It flashes correctly but returns to download mode with an error (AVB Fail).
Error verifying vbmeta image: invalid vbmeta header
The model is an A505G
Click to expand...
Click to collapse
You have to flash vbmeta first, there's an unofficial TWRP on this forum that has it, I used that and then reflashed the official one and it booted
I have a A505FN. It gets into a boot-loop after flashing.
EDIT: Samsung introduced some "Security patch" that made it impossible to flash this TWRP. What I needed to do is use ODIN to downgrade to the old firmware (A505FNXXS9CVJ2, got it from here: https://samfrew.com/de/download/Galaxy__A50__/lisb/DBT/A505FNXXS9CVJ2/A505FNOXM9CVG2/) first. Then I could install vbmeta.img (which is in the lineage-OS zip https://forum.xda-developers.com/t/rom-13-0-unofficial-lineageos-20-for-galaxy-a50.4589679/) and after restarting into download mode again I could install this TWRP.
fran6325 said:
You have to flash vbmeta first, there's an unofficial TWRP on this forum that has it, I used that and then reflashed the official one and it booted
Click to expand...
Click to collapse
Don't just say "there's something here on this forum". Send the link!
So I got this phone as a gift and decided to load custom roms unto it. I upgraded to Android 11 before this. I followed your guide and unlocked bootloader etc but when I try flashing this recovery I am faced with "only official released binaries are allowed". I used samsung way back during the S2 days and enjoyed lot's of custom roms back then but for years I have been on Xiaomi phones and really do enjoy that more. Samsung really has lost it lol. Anyways can anyone help me out of this error?
fran6325 said:
You have to flash vbmeta first, there's an unofficial TWRP on this forum that has it, I used that and then reflashed the official one and it booted
Click to expand...
Click to collapse
Can you send a link pls?
I finally managed to get it working. I needed to use the latest twrp.tar from the github releases
Releases · GiovanYCringe/device_samsung_a505f
Contribute to GiovanYCringe/device_samsung_a505f development by creating an account on GitHub.
github.com
instead of the official one from the twrp website.
Incredible!
In the A505GT/DS gives the following error in TWRP how to solve ? failed to mount '/cpefs' (i/o error)
victorgbrmr said:
In the A505GT/DS gives the following error in TWRP how to solve ? failed to mount '/cpefs' (i/o error)
Click to expand...
Click to collapse
https://github.com/GiovanYCringe/device_samsung_a505f/releases/download/V2/recovery.img
Test this
Related
I couldn't unlock the bootloader_critical on my mi a3 phone, when I entered the command " Fastboot flashing unlock_critical"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I thought so I couldn't install any room stock, it was always stuck in Fastboot when I rebooted. I flashed the rom via Twrp, OrangeFox but failed, could only install the MIUI rom.
Can anyone help me, I like the stock rom and want to use it. please.
My English is not good, I used google to help me
Picture
https://photos.app.goo.gl/snH8FjKukY1YATPm6
You don't have OEM unlock and usb debugging enabled?
install twrp then flash the os
I can't turn it on, can you help me?
garylawwd said:
You don't have OEM unlock and usb debugging enabled?
Click to expand...
Click to collapse
Picture : https://photos.app.goo.gl/ayb6ToJTzwryWc9R6
ani_shawn said:
install twrp then flash the os
Click to expand...
Click to collapse
I installed twrp, but when I flashed the rom and rebooted, it always stuck in Fastboot
Sangkunho93 said:
I installed twrp, but when I flashed the rom and rebooted, it always stuck in Fastboot
Click to expand...
Click to collapse
Okay so your bootloader is obviously unlocked already if you have twrp installed.
Why are you trying to use those commands again?
You just are not installing the ROMs correctly that's the problem. Follow the installation steps of the ROM you are trying to flash which will be found in the op of that ROM thread
garylawwd said:
Okay so your bootloader is obviously unlocked already if you have twrp installed.
Why are you trying to use those commands again?
You just are not installing the ROMs correctly that's the problem. Follow the installation steps of the ROM you are trying to flash which will be found in the op of that ROM thread
Click to expand...
Click to collapse
" unlock bootloader critical failed ", I don't know if it's necessary?
-I followed the instructions to install the rom via twrp but it still failed, always stuck in Fastboot even though I changed the slot a / b
Sangkunho93 said:
" unlock bootloader critical failed ", I don't know if it's necessary?
-I followed the instructions to install the rom via twrp but it still failed, always stuck in Fastboot even though I changed the slot a / b
Click to expand...
Click to collapse
You still didn't explain what exactly you did and what fails in twrp or what error you get or anything..
You already did the flashing unlock critical if you have twrp you don't need to keep doing it every time unless you relock your bootloader.
Start from the very start and tell us exactly step by step what you did.
How did you get miui if you didn't already do flashing unlock critical?
garylawwd said:
You still didn't explain what exactly you did and what fails in twrp or what error you get or anything..
You already did the flashing unlock critical if you have twrp you don't need to keep doing it every time unless you relock your bootloader.
Start from the very start and tell us exactly step by step what you did.
How did you get miui if you didn't already do flashing unlock critical?
Click to expand...
Click to collapse
* This is what I did ( OEM, USB..: on) :
1. " fastboot flashing unlock " , ok
2. " fastboot flashing unlock_critical " , failed ( Picture : https://photos.app.goo.gl/74hv2ZyBRd9YVFGv7 )
3. "Fastboot set_active a (or b) " , ok
4. " Fastboot flash boot twrp.img " , ok
5. Fastboot reboot recovery
6. Flash rom :
- Rom MiUi, Stock : ok
- Rom Custom : Stuck in Fastboot, despite following the instructions
* * *
* OEM test: cannot turn on ( Picture : https://photos.app.goo.gl/uWXxK69zt7jEjPEw6 )
* I used to install PixelExperience rom successfully several times, but now I don't, it is always stuck in Fastboot
Where my problem is, I don't know. Can you help me. thank you. I use google to talk to you
Hi sorry if i post in bad section so i need help i downloaded an CWM ClockWorkMod Recovery for SM-G318H Samsung Galaxy Trend 2 lite i apply the update so it was almost done but an error marked in red and reboot after update failure.
Any suggestion it happens with any zip file for Temp Recovery i have here an picture :crying:
I Attached an picture with the failure so if you have any suggestion reply there.
P.S. I Don't trust changing permanent recovery and even download mode odin.
@AlinTecsan
You used phone's Stock Recovery to flash something other than the phone's signed Stock ROM. Hence you got "E: signatue verification failed" error.
Flashing CWM on stock recovery
jwoegerbauer said:
@AlinTecsan
You used phone's Stock Recovery to flash something other than the phone's signed Stock ROM. Hence you got "E: signatue verification failed" error.
Click to expand...
Click to collapse
This i know so i try flashing the CWM so this not work so to sign the custom recovery with signed stock rom so how i fix thanks for replying
@AlinTecsan
Look inside here.
Looked Here
jwoegerbauer said:
@AlinTecsan
Look inside here.
Click to expand...
Click to collapse
I Looked here so fastboot it flash and erase sorry so my phone will not support the advanced boot options and no match found for my model at all so thanks again for the link
Use TWRP instead of CWM
@AlinTecsan
It’s true that CWM Recovery is a widely used recovery, but it’s not anymore in the league, now it’s TWRP all the way up with no contender around!
Since the software company which developed CWM Recovery has stopped building its versions anymore, there are no new releases of CWM Recovery released within the last 5 years what are ready to be used on mainstream Android devices.
Take note that TWRP can get successfully flashed on A/B systems.
TWRP Will work for my device?
jwoegerbauer said:
@AlinTecsan
It’s true that CWM Recovery is a widely used recovery, but it’s not anymore in the league, now it’s TWRP all the way up with no contender around!
Since the software company which developed CWM Recovery has stopped building its versions anymore, there are no new releases of CWM Recovery released within the last 5 years what are ready to be used on mainstream Android devices.
Take note that TWRP can get successfully flashed on A/B systems.
Click to expand...
Click to collapse
Does have what have cwm?Like factory reset apply update from sdcard sideload cache wipe reboot and change theme i would like to try hope the file is compatibile with my device before to start i will backup the stock recovery :good:
AlinTecsan said:
Does have what have cwm?Like factory reset apply update from sdcard sideload cache wipe reboot and change theme i would like to try hope the file is compatibile with my device before to start i will backup the stock recovery :good:
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I Flash an 2.8.7.0 TWRP
jwoegerbauer said:
Click to expand...
Click to collapse
It work fine so i need to change to red if possible so work good so i sent pictures soon I like to know how i restore the stock recovery i backup the whole firmware so i like to change to red .TWRP Work with all devices?
@AlinTecsan
You have to re-flash device's Stock ROM to get device's Stock Recovery back.
Stock ROM And recovery
jwoegerbauer said:
@AlinTecsan
You have to re-flash device's Stock ROM to get device's Stock Recovery back.
Click to expand...
Click to collapse
I have to say i extract from my correctly firmware code the recovery.img so i will made an tar file or i guess to restore recovery stock in case of problem so i know with .tar.md5 backups.
I recently flashed my device with the latest firmware (Binary: 8) downloaded from sammobiles. The binary it had before flash was 6.
Now it is boot looping and would not boot up normally. It goes into recovery but it shows some errors. Please look into the attached images (both download mode and recovery mode) displaying and corresponding the exact problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OEM is OFF
FRP is OFF
Till now, I have diagnosed the problem to be DRK ERROR (dm-verity verification failed.)
This file: "J530F Binary U8 Android 9 Pie FIX DRK - dm-verity Failed Frp Off Oem Off (J530FXXS8CTK1).rar" may solve the problem but can't find this anywhere for free.
Please help!
zohaibahmedpk said:
I recently flashed my device with the latest firmware (Binary: 8) downloaded from sammobiles. The binary it had before flash was 6.
Now it is boot looping and would not boot up normally. It goes into recovery but it shows some errors. Please look into the attached images (both download mode and recovery mode) displaying and corresponding the exact problem.
View attachment 5221727View attachment 5221729
OEM is OFF
FRP is OFF
Till now, I have diagnosed the problem to be DRK ERROR (dm-verity verification failed.)
This file: "J530F Binary U8 Android 9 Pie FIX DRK - dm-verity Failed Frp Off Oem Off (J530FXXS8CTK1).rar" may solve the problem but can't find this anywhere for free.
Please help!
Click to expand...
Click to collapse
@hainguyenthao helped on discord step by step for installing a custom ROM for normal booting of the device. As the custom ROM was buggy (/e/ ROM), I flashed stock ROM using Odin, with TWRP+no verity script+root(magisk), and got my device working and boot up to the system. Thanks for your time @hainguyenthao.
zohaibahmedpk said:
@hainguyenthao helped on discord step by step for installing a custom ROM for normal booting of the device. As the custom ROM was buggy (/e/ ROM), I flashed stock ROM using Odin, with TWRP+no verity script+root(magisk), and got my device working and boot up to the system. Thanks for your time @hainguyenthao.
Click to expand...
Click to collapse
bro pls tell me how to fix this, i got the same sh*tty problem over here i would be so much thankful
Mitoww said:
bro pls tell me how to fix this, i got the same sh*tty problem over here i would be so much thankful
Click to expand...
Click to collapse
message me on discord: ZohaibPK#6207
zohaibahmedpk said:
message me on discord: ZohaibPK#6207
Click to expand...
Click to collapse
i already got it solved, thanks though
zohaibahmedpk said:
zohaibahmedpk said:
I recently flashed my device with the latest firmware (Binary: 8) downloaded from sammobiles. The binary it had before flash was 6.
Now it is boot looping and would not boot up normally. It goes into recovery but it shows some errors. Please look into the attached images (both download mode and recovery mode) displaying and corresponding the exact problem.
View attachment 5221727View attachment 5221729
OEM is OFF
FRP is OFF
Till now, I have diagnosed the problem to be DRK ERROR (dm-verity verification failed.)
This file: "J530F Binary U8 Android 9 Pie FIX DRK - dm-verity Failed Frp Off Oem Off (J530FXXS8CTK1).rar" may solve the problem but can't find this anywhere for free.
Please help!
Click to expand...
Click to collapse
bro pls tell me how to fix this, i got the same sh*tty problem over here i would be so much thankful
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
#SHRP A10/11
Download : https://mega.nz/file/gpgWmBwa#MqToq4Htapb4cd-nwzcBNbpAbuBD_TREbPvK9bFHsmI
Features :
-f2fs support(flash f2fs patcher from tweaks section and convert data and catch(optional) to f2fs to use f2fs).Must use f2fs supposed Kernel.
-Can flash and backup system,vendor and product.
-You can flash gsi and ub port image directly.
-Can resize system and vendor partition to flash Large image size ..
(Flash system vendor resize zip from tweaks and reboot to recovery
-system, vendor, product rw support (flash system rw zip from tweaks section)
Notes :
-After resize you can flash system up to 3.4 gb and vendor up to 900 mb.
-Disable shrp theme to prevent bootloop.
-If you are in miui you need to flash patch vbmeta from below link.
http://transfer.sh/e3LV0n/unipatchedvbmeta_twrp.zip
Flash it after flash the recovery..
Install :
Download and flash from any recovery or extract and flash recovery.img from pc
Sorce (twrp tree) : https://github.com/Arafattex/device_xiaomi_lancelot
Screen shot :
What is the solution to the problem of returning the official recovery after a reboot? Knowing that I tried flashing the Magisk, but the phone does not turn on (bootloop)
Az.az1 said:
What is the solution to the problem of returning the official recovery after a reboot? Knowing that I tried flashing the Magisk, but the phone does not turn on (bootloop)
Click to expand...
Click to collapse
It never happened which version of magisk you flash ? is you are miui if yes flash patch vbmeta...
http://transfer.sh/e3LV0n/unipatchedvbmeta_twrp.zip
how to disable theme?
EDIT: nvm I got it, although installing Magisk v23 from official site does bootloop the phone.
Removing it solved it and got my phone boot.
Shas45558 said:
Il n'est jamais arrivé quelle version de magisk vous flashez ? est-ce que vous êtes miui si oui flash patch vbmeta...
http://transfer.sh/e3LV0n/unipatche...sh/e3LV0n/unipatchedvbmeta_twrp.zip
[/QUOTE]
Click to expand...
Click to collapse
http://1- thanks for your reply
2- I have the latest version of Magisk 23.0
3-I'm on the official ROM
4- The link you sent does not work
64Timothy121 said:
how to disable theme?
EDIT: nvm I got it, although installing Magisk v23 from official site does bootloop the phone.
Removing it solved it and got my phone boot.
Click to expand...
Click to collapse
Theme is disabled no need
64Timothy121 said:
how to disable theme?
EDIT: nvm I got it, although installing Magisk v23 from official site does bootloop the phone.
Removing it solved it and got my phone boot.
Click to expand...
Click to collapse
How did you remove it? I got a bootloop too after installing Magisk from SHRP and I can only go to fastboot, but when I flash SHRP again the bootloop is still there and it won't go into recovery anymore.
ecvarts said:
How did you remove it? I got a bootloop too after installing Magisk from SHRP and I can only go to fastboot, but when I flash SHRP again the bootloop is still there and it won't go into recovery anymore.
Click to expand...
Click to collapse
I reflashed and booted into the img, yet the phone actually booted into the system. I hit the combo for recovery and somehow I got back in this time and it says Magisk is installed. Weird... But if it works...
Could someone re-upload the vbmeta patch?
This link no longer works... https://transfer.sh/e3LV0n/unipatchedvbmeta_twrp.zip
Thank you very much!
+1 vbmeta_twrp link is not working
+1 I‘d like to use this rom,but can you give me another recovery link?tks
Here is the detailes guide to install This recovery.
Go to Fastboot mode
Run the following commands.
fastboot flash recovery recoveryname.img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot reboot recovery
In the recovery install SHRP img file
then install vbmeta_patched img file
then reboot to recovery
All files are attached.
Don't forget to click Thanks button
rakesh.aggarwal said:
Here is the detailes guide to install This recovery.
Go to Fastboot mode
Run the following commands.
fastboot flash recovery recoveryname.img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot reboot recovery
In the recovery install SHRP img file
then install vbmeta_patched img file
then reboot to recovery
All files are attached.
Don't forget to click Thanks button
Click to expand...
Click to collapse
Hello, I followed this procedure and my phone (Redmi 9) got stuck in a bootloop, I can't even get into fastboot anymore. I might be able to recover it using EDL however, but most likely I will have to send it to authorized repair. RIP.
Update: Not even the guy I sent the phone to repair could fix it, RIP.
zerowhy said:
Hello, I followed this procedure and my phone (Redmi 9) got stuck in a bootloop, I can't even get into fastboot anymore. I might be able to recover it using EDL however, but most likely I will have to send it to authorized repair. RIP.
Update: Not even the guy I sent the phone to repair could fix it, RIP.
Click to expand...
Click to collapse
I have attached the unbricking tool here. It worked for me. If you just chose the correct CPU architecture, it will work for any mediatek phone.
The above guide was for Shiva(Poco M2) not for Redmi 9.
Hmm.. I can't seem to flash the official firmware with this recovery. It just shows an error when flashing it. I am on PixelPlus UI 12.1.
MaxisMan said:
Hmm.. I can't seem to flash the official firmware with this recovery. It just shows an error when flashing it. I am on PixelPlus UI 12.1.
Click to expand...
Click to collapse
What kind of errors?
Sorry for a stupid question. But is Flash button has the same function as Install button when installing *.zip patch file? This is the 1st time I'm using this recovery
Hi Folks,
I have a Xiomi Note 10 (camellian), unlocked and has USB Debugging switched on.
No matter what I do, I can't install TWRP or Orangefox because it fails with "FAILED: Too Many Links"
I've followed so many guides on how to fix this and they all fail. I tried to flash the stock rom with Mi Flash and that failed too (Constant "Unhandled exception" error as it doesnt seem to want to install drivers and wont continue without them). I've manually updated the ADB drivers for the Note and that worked fine. Mi Pc Suite doesnt recognise my phone unless i "Update your phone before you connect" (The phone is fully updated)
Please, for the love of the baby jesus and the little donkey, tell me what I can do to try and figure out what the smeg is going wrong
EDIT:
Ive changed ports/cables, tried compatibilty on programs, reinstalled ADB drivers
trying "fastboot flash boot recovery.img" (for orange fox) throws up "FAILED: remote: size too large"
hellfirehound said:
Hi Folks,
I have a Xiomi Note 10 (camellian), unlocked and has USB Debugging switched on.
No matter what I do, I can't install TWRP or Orangefox because it fails with "FAILED: Too Many Links"
I've followed so many guides on how to fix this and they all fail. I tried to flash the stock rom with Mi Flash and that failed too (Constant "Unhandled exception" error as it doesnt seem to want to install drivers and wont continue without them). I've manually updated the ADB drivers for the Note and that worked fine. Mi Pc Suite doesnt recognise my phone unless i "Update your phone before you connect" (The phone is fully updated)
Please, for the love of the baby jesus and the little donkey, tell me what I can do to try and figure out what the smeg is going wrong
EDIT:
Ive changed ports/cables, tried compatibilty on programs, reinstalled ADB drivers
trying "fastboot flash boot recovery.img" (for orange fox) throws up "FAILED: remote: size too large"
Click to expand...
Click to collapse
i see none TWRP and O.F for camellian, can you post the links +Miflash log?
The TWRP is unofficial https://forum.xda-developers.com/t/unofficial-twrp-camellia-camellian.4304717/
There is no MiFlash log anywhere. Sorry im new to this
I think I need to flash the original rom before trying to install a recovery rom
hellfirehound said:
The TWRP is unofficial https://forum.xda-developers.com/t/unofficial-twrp-camellia-camellian.4304717/
There is no MiFlash log anywhere. Sorry im new to this
Click to expand...
Click to collapse
The Mi Flash logs are in the Miflash Log folder (post the last + or - 20/22ko
This twrp seems not to work (closed thread).
Try the command: fastboot boot twrp.img
The phone will reboot in TWRP after that go to Advanced > Flash Current TWRP
And what do you want to do with the TWRP, your device has a Mediatek soc and there is little or no development for Xiaomi with a Mediatek soc.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It looks like a mediatek device.
Never Mind, ill keep the phone as is. Thanks for trying to help
Download and extract to the root of the disk.C:/platform....
https://developer.android.com/studio/releases/platform-tools
rename the Twrp to twrp.img
Put it in the Platform tools folder
Execute the command from this folder
Since no custom is available for your phone I guess you want to update or downgrade for these 2 cases use Miflash not TWRP.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
this error
is frequent with certain version of W10.
Disable driver verification.
.