Database Info

[Q] Pls help me recover bricked my xoom

dear all,
I have a MZ600 Xoom with original state (not yet unlocked or rooted)
Yesterday, it informed me upgrading new software (OTA). After rebooting, it asked me for a password to enter android (not the lock screen password, since I have not set any). I searched google for this case but didn't find any problem like that. So I decided to boot into Recovery Mode and did factory reset, but strangely the xoom would ask a password again.
Then I booted it into fastboot mode and do some command with HRI39 img. All command failed (except for flash userdata.img) Here is the result:
C:\Android\android-sdk\tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)...
OKAY [ 0.571s]
writing 'boot'...
FAILED (remote: (19000008))
finished. total time: 1.533s
C:\Android\android-sdk\tools>fastboot flash system system.img
< waiting for device >
sending 'system' (262144 KB)...
OKAY [ 17.376s]
writing 'system'...
FAILED (remote: (19000008))
finished. total time: 18.540s
the image
{
"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"
}
When I used Rsd Lite 5.0 with sbf HRI39 to flash the xoom. But the process failed, too
Any help would be most appreciated.
Thank in advance

Longshot here, but the SBF always says it fails, even when it works. Did you verify it actually failed?

I've verified already.
The HRI39 Sbf zip comes with two files. If i flash the smaller file, it will be ok. But when I flash the larger one, RSD Lite stuck at "...switching device to pass through..." and failed. Now my xoom could enter to RSD, Recovery, Fastboot mode and cannot boot into Android any more.
I try RSD Lite on WinXP 32bit, also Win7 Ult 32bit, all failed
I attach the log from RSD Lite here.
thank you

You could try downloading clockworkmod and installing it by doing:
fastboot flash boot recovery.img
This will get your device to boot to cwm. From there i have no idea what you can do. You could maybe download the stock images, create an MD5 for them, and try to nandroid restore them.

Have you tried RSD Life 4.9 yet? There's an SBF file for Verizon XOOMs floating around you can flash from RSD Life.

Strangely, I could not flash anything with fastboot except for userdata.img. All failed like the image i attached. So, I tried to flash the cwm recovery, but got failure again.
With RSD Lite 4.9 (and also 5.0), I flash HRI39 sbf from the topic http://forum.xda-developers.com/showthread.php?p=13077237 and got stuck at 2% of process.
Do I have to change some parameters in Rsd lite?

Userdata isn't vital though. Mostly Boot and
I see in your pics the Xoom has already been unlocked. Maybe try unlocking it again? Just do not lock it. It'll probably get bricked even worse.
I heard that setting Config > DeviceID options to First come first serve helped someone. Never tried myself.

thank you
in the pic, when I select accepted choice for unlocking, it said "Error: failed to format UDA", and if I do oem lock, i aslo said failed.
And how to set DeviceID for flashing the xoom?

XT1033 india. Tried to Lock the Bootloader but Bricked the Phone instead. Help.

Hey there, thanks for viewing. Before posting here, I have well enough spent 6+ effective hours (whole day yesterday) to find a solution for this. Unfortunately, I was not successful.
I own a Moto G (XT1033) Dual Sim India Version. Initially, I was running an android 5.02 stock (rooted) with unlocked bootloader when I get a notification about a system update (for 5.1.1). Exited, I downloaded the update and tried to install it, but the OTA wouldn't install. Later, I figured it may be because my phone had an unlocked bootloader. As a result, I tried to re-lock the bootloader by installing 5.0.2 stock again from this guide: http://forum.xda-developers.com/showthread.php?t=2700502 .
Everything was successful and the bootloader was locked again . But this time instead of OTA, I pasted this file Blur_Version.221.21.56.falcon_umtsds.AsiaRetail.en.03.zip which I found in some webpage I don't remember. The update was successfull. Now due to some stupid reason, I wanted to do the whole thing again and and do the OTA udpate this time. This is where the problem begin.
In the bootloader I typed the exact same commands and used the exact same files, but this time, this is what I got:
HTML:
C:\Users\Prasannjeet\Desktop\TWRP\Fastboot>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.103s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.425s
Attaching the screenshot, please have a look.
{
"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"
}
Also adding a pic of my phone's bootloader screen for the error message it receives.
Note that I get the same error for sparsechunk command which comes later. I have tried 10-20 guides, most of them from XDA for the same "Preflash Validatin Failed" error, but none of them fixes my problem.
Bottomline, whatever on earth I do, whatever recovery, stock ROM's, fastboot's I download and install, as soon as I type the command "mfastboot.exe flash partition gpt.bin", I get the same preflash validation failed error message again and again and again!!! :crying: I get the same error for the rest of the commands.
Note that if I try to flash any other custom ROM's via TWRP or any other recovery, I am easily able to do it, but that way I won't be able to lock the bootloader ever again. The only way we can lock the bootloader is something which is not working.
Is it really impossible for me to downgrade now?
Few posts which I have went through already but didn't work:
http://forum.xda-developers.com/moto-g/help/gpe-pre-flash-validation-failed-gpt-t2836073
http://forum.xda-developers.com/moto-g/help/bootloader-preflash-validation-failed-t2834023
I have tried more, but can't find the links now.
Please help :crying:
Thanks!

Have officially 5.1 ROM, you try to flash it again.
And why did you want to re-lock bootloader? Still update OTA when unlocked bootloader.

thuybang said:
Have officially 5.1 ROM, you try to flash it again.
And why did you want to re-lock bootloader? Still update OTA when unlocked bootloader.
Click to expand...
Click to collapse
Thanks for replying! Can you share the link of 5.1 ROM, if you have?
I tried to OTA when bootloader unlocked, but it didn't happen

Link ROM :http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
OTA fail because root or you modified system. You only flash stock ROM then update OTA ok. No need relock B.L

Stucked on Initial Settings

I got this Moto G 2015 (XT1453) and it is stucked on the following screen:
{
"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 doesn't allow me to connect to any wifi network and doesn't skip the initial configuration.
I've tried reinstalling the stock rom doing this http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
I can't access any of the phone settings, so I had to reboot the phone into Bootloader mode using hardware,
but when I type the command "fastboot flash partition gpt.bin" I got this message:
" sending 'partition' <32 KB>...
OKAY [-0.000s]
writing 'partition'...
<bootloader> Preflash validation failed
FAILED <remote failure>
finished. total time: 0.438s"
This is the first time I try to use Fastboot, so I assume this isn't right. Even with this message I did all the following steps but I got stuck on the same screen again.
I would be really grateful if someone helps me on this.

r_gomes said:
I got this Moto G 2015 (XT1453) and it is stucked on the following screen:
It doesn't allow me to connect to any wifi network and doesn't skip the initial configuration.
I've tried reinstalling the stock rom doing this http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
I can't access any of the phone settings, so I had to reboot the phone into Bootloader mode using hardware,
but when I type the command "fastboot flash partition gpt.bin" I got this message:
" sending 'partition' <32 KB>...
OKAY [-0.000s]
writing 'partition'...
<bootloader> Preflash validation failed
FAILED <remote failure>
finished. total time: 0.438s"
This is the first time I try to use Fastboot, so I assume this isn't right. Even with this message I did all the following steps but I got stuck on the same screen again.
I would be really grateful if someone helps me on this.
Click to expand...
Click to collapse
Preflash Validaton Errors occur when you are trying to flash newer and older bootloaders. In that case,what you have to do is, skip the following commands and flash everything else:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
If you haven't discovered it, the best way to flash is copy all the commands and just paste them into the cmd window instead of typing them one at a time.

Tel864 said:
Preflash Validaton Errors occur when you are trying to flash newer and older bootloaders. In that case,what you have to do is, skip the following commands and flash everything else:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
If you haven't discovered it, the best way to flash is copy all the commands and just paste them into the cmd window instead of typing them one at a time.
Click to expand...
Click to collapse
Thank you. I made what you said and it worked, but now I got the message:
"This device was reset. To continue, sign in with a Google Account that was previously synced on this device."
I've looked in many forums and it seems like there is no way to pass this screen without the first email used in the phone. My friend bought this phone from a guy, so I have no idea who was his first owner or the first email account. What should I do?

Have you ever been able to log in with this phone? Was the phone purchased used and what version of Lollipop came on the phone. If 5.0 came on it, then you may have to flash back to 5.0 and log in with a new account. If it was purchased used with 5.1 then the seller will need to provide you with the login so the old Google account on the phone can be removed. Maybe someone else has an idea but since 5.1 it's harder to get into a phone that was purchased used.

Lineage os 17.x, 18.x GSI

Hello, someone have bootloader unlocked and Is willing to try Lineage OS?
Here is the roms: Lineage OS 16.x, 17.x, 18.x
Download the a/b versión (treble_arm64_bv)
no root needed or twrp, just bootloader unlocked and a pc.
If someone tried, please let me know!

Did you try to install any GSI rom ???

works with all gsi? so I test

Niick.Ok said:
works with all gsi? so I test
Click to expand...
Click to collapse
Yes, should work with any GSI roms, please Let me know if you tried!

Someone tried this? I dont know how to install the rom, but i've already installed twrp

CæsarAM said:
Someone tried this? I dont know how to install the rom, but i've already installed twrp
Click to expand...
Click to collapse
For install roms, you need the stock recovery.
Here is a mini tutorial If anyone want yo try it!
start the phone in fastboot mode, then connect to the computer via USB.
enter at the PC: fastboot reboot fastboot
when the phone is restarted, fastbootd (look for the “d” at the end of fastboot) should appear.
now type: fastboot flash system image-name.img (e.g. lineage-17.1-20210615-UNOFFICIAL-treble_arm64_bvS.img)
when all this is finished, type: fastboot reboot recovery
in the original recovery, go to delete all data, then restart the phone.
The first start take while, please be patient! Enjoy!

SaocMc said:
For install roms, you need the stock recovery.
Here is a mini tutorial If anyone want yo try it!
start the phone in fastboot mode, then connect to the computer via USB.
enter at the PC: fastboot reboot fastboot
when the phone is restarted, fastbootd (look for the “d” at the end of fastboot) should appear.
now type: fastboot flash system image-name.img (e.g. lineage-17.1-20210615-UNOFFICIAL-treble_arm64_bvS.img)
when all this is finished, type: fastboot reboot recovery
in the original recovery, go to delete all data, then restart the phone.
The first start take while, please be patient! Enjoy!
Click to expand...
Click to collapse
Don't works for this phone, when I flash the system image it says "FAILED (remote: 'Not enough space to resize partition')". I think it's because this device has dynamic partitions

CæsarAM said:
Don't works for this phone, when I flash the system image it says "FAILED (remote: 'Not enough space to resize partition')". I think it's because this device has dynamic partitions
Click to expand...
Click to collapse
yes, because of it, you need to flash via fastbootd
After some research, this could be a posible solution:
flash the stock vbmeta with fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
deleted product partition with fastboot delete-logical-partition product
flash the rom with fastboot flash --u system lineage-17.1-20210615-UNOFFICIAL-treble_arm64_bvS.img
Factory reset from recovery
you can extract the vbmeta file from stock rom, https://mirrors.lolinet.com/firmware/moto/astro/official/

{
"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"
}
same error

I tried to install the gsi roms with the new recovery that they released for this phone and it didn't let me erase the system partition, I couldn't install the gsi image either, none of the three recovery variants that they released worked for me

Niick.Ok said:
I tried to install the gsi roms with the new recovery that they released for this phone and it didn't let me erase the system partition, I couldn't install the gsi image either, none of the three recovery variants that they released worked for me
Click to expand...
Click to collapse
because this device has dynamic partitions, can't install rom via recovery, only via fastbootd, but seems the lineage OS is larger than the system partition of our device, so we need to find a lighter rom or keep searching a solution

What size would the rom need? And another query, how is fastboot mode different from fastbootd mode? I see that the D is attached to the end many

Niick.Ok said:
What size would the rom need? And another query, how is fastboot mode different from fastbootd mode? I see that the D is attached to the end many
Click to expand...
Click to collapse
Basically, Fastbootd is a newer version of fastboot.
fastboot -w (warning : this will wipe all your data)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
This steps are how fusion+ flash GSI roms(Copied from here: https://forum.xda-developers.com/t/rom-11-official-omnirom-liber.4232413/), the boot, dtbo and vmeta files are from stock rom, If anyone wants to try this, please let me know! Remember you need stock recovery and a factory reset after flashing the rom

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system Havoc-OS-v4.1-20210208-arm64-ab-Official.img
target reported max download size of 536870912 bytes
sending sparse 'system_a' 1/6 (458752 KB)...
OKAY [ 14.145s]
writing 'system_a' 1/6...
OKAY [ 2.422s]
sending sparse 'system_a' 2/6 (458752 KB)...
OKAY [ 14.199s]
writing 'system_a' 2/6...
OKAY [ 2.429s]
sending sparse 'system_a' 3/6 (458752 KB)...
OKAY [ 14.093s]
writing 'system_a' 3/6...
FAILED (remote: Operation not permitted)
finished. total time: 47.854s

Niick.Ok said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system Havoc-OS-v4.1-20210208-arm64-ab-Official.img
target reported max download size of 536870912 bytes
sending sparse 'system_a' 1/6 (458752 KB)...
OKAY [ 14.145s]
writing 'system_a' 1/6...
OKAY [ 2.422s]
sending sparse 'system_a' 2/6 (458752 KB)...
OKAY [ 14.199s]
writing 'system_a' 2/6...
OKAY [ 2.429s]
sending sparse 'system_a' 3/6 (458752 KB)...
OKAY [ 14.093s]
writing 'system_a' 3/6...
FAILED (remote: Operation not permitted)
finished. total time: 47.854s
Click to expand...
Click to collapse
Can you double check that your bootloader is unlocked and you are flashing vía fastbootd?
Some users report that error is caused by the bootloader locked, maybe, somehow your bootloader got locked again.

That's what I thought, when I got that error yesterday I tried to unlock the bootloader again, I tried via fastbootd and it didn't let me, I had to do it from the bootloader menu and there it left me, from fastbootd it told me that it did not know the commands, (summarizing I tried to unlock the bootloader again from the fastbootd menu and it wouldn't let me, so I tried from bootloader and it left me, but it told me that it was already unlocked, any other solution?

I think I already found the problem yesterday when trying to install gsi, yesterday wn fastbootd it appeared (secure boot = yes) I flashed the vbmeta of the official rom and I did not deactivate it, I would need you to pass me a modified vbmeta to flash it and deactivate the secure boot, from there I try to flash again, 2- another possible solution I think would be flashing magisk, see if it manages to pass that verification (secure boot = yes) by modifying the boot. In any case, I would need your help to achieve the modified vbmeta

Niick.Ok said:
I think I already found the problem yesterday when trying to install gsi, yesterday wn fastbootd it appeared (secure boot = yes) I flashed the vbmeta of the official rom and I did not deactivate it, I would need you to pass me a modified vbmeta to flash it and deactivate the secure boot, from there I try to flash again, 2- another possible solution I think would be flashing magisk, see if it manages to pass that verification (secure boot = yes) by modifying the boot. In any case, I would need your help to achieve the modified vbmeta
Click to expand...
Click to collapse
I found this tutorial: https://forum.hovatek.com/thread-32719.html
Method 3 is for flash a empty vmeta and disable verification.
You can try with both, the stock vmeta or the empty one.

I tried everything and I could not, I will wait for a developer to find a way, or for a rom to come out for this cell phone, I already tried the three methods that you sent me and more

SaocMc said:
Can you double check that your bootloader is unlocked and you are flashing vía fastbootd?
Some users report that error is caused by the bootloader locked, maybe, somehow your bootloader got locked again.
Click to expand...
Click to collapse
I get the exact same error no matter the GSI I try, bootloader is unlocked, flashing using fastbootd, I already hate this device...

Fastboot boot TWRP doesn't do anything

I'm trying to flash a custom ROM to my Xiaomi Redmi Note 7 Pro (Unlocked Bootloader)
Here's what i've done so far:
1) Entered Fastboot successfully
2) Typed: C...\platform-tools>fastboot flash recovery twrp-3.5.2_9-0-violet.img
And gotten the respone:
Sending 'recovery' (65536 KB) OKAY [ 1.878s]
Writing 'recovery' OKAY [ 0.462s]
Finished. Total time: 2.357s
3) Typed: C...\platform-tools>fastboot boot twrp-3.5.2_9-0-violet.img
And gotten the response:
Sending 'boot.img' (65536 KB) OKAY [ 1.968s]
Booting OKAY [ 0.143s]
Finished. Total time: 2.172s
This is the part where the phone is supposed to be booted into TWRP Custom Recovery, but instead, nothing happens. The phone is still in fastboot. If I try to reboot it and then reboot into recovery, it boots in the default xiaomi recovery. I've tried older versions of twrp.img files, and nothing works. What am I doing wrong?
Thanks in Advance

After flashing the recovery, try typing fastboot reboot recovery instead. That works without fail for me.

camperbh said:
After flashing the recovery, try typing fastboot reboot recovery instead. That works without fail for me.
Click to expand...
Click to collapse
didn't work, it just rebooted my phone

{
"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"
}
Well this is what happens when I type it. You could also try booting to system after flashing and type "adb reboot recovery" instead. Or you could just turn off the phone and go into recovery with power+vol up.

camperbh said:
View attachment 5313135
Well this is what happens when I type it. You could also try booting to system after flashing and type "adb reboot recovery" instead. Or you could just turn off the phone and go into recovery with power+vol up.
Click to expand...
Click to collapse
the same message gets displayed to me, but it doesnt work. Even when I do power+vol up, it just reboots and doesnt go to recovery at all

What about the adb method? Does that work?

camperbh said:
What about the adb method? Does that work?
Click to expand...
Click to collapse
nope

That's all the methods I know of. As a last resort, maybe try flashing your stock rom using miflash and repeat the process to see if it works I guess. This is all the help I can offer, sorry.

camperbh said:
That's all the methods I know of. As a last resort, maybe try flashing your stock rom using miflash and repeat the process to see if it works I guess. This is all the help I can offer, sorry.
Click to expand...
Click to collapse
considering that it doesnt go to twrp neither when typing fastboot boot twrp.img nor when i type fastboot reboot recovery nor when rebooting and typing adb reboot recovery, i feel like the issue is that for some reason it cannot flash the twrp.img file. What's weird though is that it says it successfully flashes it. Anyway, thank you for your time, have a good one

Thinking about it, it could also be a driver issue. Try reainstalling your drivers and see if it works.

camperbh said:
Thinking about it, it could also be a driver issue. Try reainstalling your drivers and see if it works.
Click to expand...
Click to collapse
if you're referring to adb drivers, i tried that. It's updated to the latest version

maxccbvoe said:
I'm trying to flash a custom ROM to my Xiaomi Redmi Note 7 Pro (Unlocked Bootloader)
Here's what i've done so far:
1) Entered Fastboot successfully
2) Typed: C...\platform-tools>fastboot flash recovery twrp-3.5.2_9-0-violet.img
And gotten the respone:
Sending 'recovery' (65536 KB) OKAY [ 1.878s]
Writing 'recovery' OKAY [ 0.462s]
Finished. Total time: 2.357s
3) Typed: C...\platform-tools>fastboot boot twrp-3.5.2_9-0-violet.img
And gotten the response:
Sending 'boot.img' (65536 KB) OKAY [ 1.968s]
Booting OKAY [ 0.143s]
Finished. Total time: 2.172s
This is the part where the phone is supposed to be booted into TWRP Custom Recovery, but instead, nothing happens. The phone is still in fastboot. If I try to reboot it and then reboot into recovery, it boots in the default xiaomi recovery. I've tried older versions of twrp.img files, and nothing works. What am I doing wrong?
Thanks in A
Click to expand...
Click to collapse
maxccbvoe said:
I'm trying to flash a custom ROM to my Xiaomi Redmi Note 7 Pro (Unlocked Bootloader)
Here's what i've done so far:
1) Entered Fastboot successfully
2) Typed: C...\platform-tools>fastboot flash recovery twrp-3.5.2_9-0-violet.img
And gotten the respone:
Sending 'recovery' (65536 KB) OKAY [ 1.878s]
Writing 'recovery' OKAY [ 0.462s]
Finished. Total time: 2.357s
3) Typed: C...\platform-tools>fastboot boot twrp-3.5.2_9-0-violet.img
And gotten the response:
Sending 'boot.img' (65536 KB) OKAY [ 1.968s]
Booting OKAY [ 0.143s]
Finished. Total time: 2.172s
This is the part where the phone is supposed to be booted into TWRP Custom Recovery, but instead, nothing happens. The phone is still in fastboot. If I try to reboot it and then reboot into recovery, it boots in the default xiaomi recovery. I've tried older versions of twrp.img files, and nothing works. What am I doing wrong?
Thanks in Advance
Click to expand...
Click to collapse
The first method. I also had a problem after flashing "fastboot flash recovery twrp.img it says successfully but when I try to go to recovery by holding button + volume it cannot proceed it shows black screen but the phone did not get bootloop.
2nd method : I've also tried by using a command " fastboot boot recovery twrp.img " it shows the the command I use is invalid argument . For those who already root their phone Redmi 9t plsss reply about this issue plsss plssss