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?

TF300 was brick after update to 4.2.2 with flash TWRP 2.4.4.0

TF300 was brick after update to 4.2.2 with flash TWRP 2.4.4.0
Hello, When used TWRP 2.4 update Android system to 4.2, then flash TWRP 2.4.4, but when I reboot system to TWRP, it asked for password to entry TWRP. Just think it should be used new android plantform-tools, install it. flash TWRP 2.4.4 again, TWRP still asked for PASSWORD, then wipe data used system provide(Not TWRP), after reboot the TF300, the machine go to TWRP 2.4.4 and still ask password, but can not loading Android system, not fastboot option, apx model does not work.
It should be "Final brick" the tablet. HELP!!!!!!
{
"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"
}
Does anybody know this situation?
Peter Du

peterdu88 said:
TF300 was brick after update to 4.2.2 with flash TWRP 2.4.4.0
Hello, When used TWRP 2.4 update Android system to 4.2, then flash TWRP 2.4.4, but when I reboot system to TWRP, it asked for password to entry TWRP. Just think it should be used new android plantform-tools, install it. flash TWRP 2.4.4 again, TWRP still asked for PASSWORD, then wipe data used system provide(Not TWRP), after reboot the TF300, the machine go to TWRP 2.4.4 and still ask password, but can not loading Android system, not fastboot option, apx model does not work.
It should be "Final brick" the tablet. HELP!!!!!!
Does anybody know this situation?
Peter Du
Click to expand...
Click to collapse
try CWM

peterdu88 said:
TF300 was brick after update to 4.2.2 with flash TWRP 2.4.4.0
Hello, When used TWRP 2.4 update Android system to 4.2, then flash TWRP 2.4.4, but when I reboot system to TWRP, it asked for password to entry TWRP. Just think it should be used new android plantform-tools, install it. flash TWRP 2.4.4 again, TWRP still asked for PASSWORD, then wipe data used system provide(Not TWRP), after reboot the TF300, the machine go to TWRP 2.4.4 and still ask password, but can not loading Android system, not fastboot option, apx model does not work.
It should be "Final brick" the tablet. HELP!!!!!!
Does anybody know this situation?
Peter Du
Click to expand...
Click to collapse
This happened to me when i was using 2.5.0.0. did you try hitting cancel?

Depending what version of Asus firmware you have installed you need to make sure you have the right recovery.
firmware 10.6.1.8= twrp 2.4.4.0-4.2.blob
firmware 10.6.1.15.3= twrp 2.5.0.0-4.2.blob
Each recovery is specific to the firmware version. Also note the -4.2 at the end of the file. That is important. It signifies that it will work on 4.2.1 bootloader.
If you do have the correct version for your firmware, you should be able to just press cancel when twrp asks for a password.
good luck

Hello,I have a problem very similar. A few days ago upgrading from 4.1.1 to 4.2.1 official (fastboot). After updating to official 4.2.1 version, i flashed TWRP 2.4.4.0. Everything worked well.
By mistake, I gave to "wipe data" from the bootloader (that's when you start with vol - and power), and from that moment everything is ****ed. Now when I turn enters the recovery directly without going through the fastboot, which seems to be fully operational.Investigating, I saw this log.
Saying that, to get to see the content of external sd, I had to enter under "mount" the recovery and give "mount system". In "file manager" if I go into system there is where the external sd.
The computer detects the tablet in nvflash mode and also when I enter the recovery is detected.
I can navigate to the "terminal comand" across the ROM memory, even move copy or delete files, and enter data from the SD.
I tried to install a rom from sd and has run the installer to finish, there has not been any kind of error, but on reboot .... nothing, as usual. During installation I saw that the partitions DATA, the internal SD and external SD not detected. I think this may be the solution to the problem, but not how it could create partitions.
Someone can help me?
Excuse my English.

I found this post 2 days ago, I tried to use adb reboot bootloader, It works.
The all of the files list over here.
1. Latest firmware:
2. Twrp:
Following the description as this link
http://forum.xda-developers.com/showthread.php?t=2425581
This is how I unbricked my TF300T that had no rom installed and a wrong bootloader/recovery combination. (4.2 bootloader with TWRP recovery JB version). Hope it helps.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB*
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot*
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster <----(credits to him) Go to this link --->
=
I saved my tablet.
:thumbup:
Sent from my Nexus 4 using Tapatalk 2

Why I got these, help!

I flash the factory image with the flash-all.bat, but I got these.
What shoule I do?
Code:
target didn't report max-download-size
sending 'bootloader' (38728 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.000s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: -0.000s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (32 MB) to disk... took 0.188s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
{
"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"
}

The bootloader that came with our phone is borked and doesn't allow flashing the new bootloader. Need to download the OTA image from Google and follow their steps for flashing it via recovery. Make sure to flash the stock boot.img for your current setup beforehand to unroot. The OTA will overwrite the bootloader and fix the issue so in the future you will be able to flash-all with the factory images as usual.

Ra6idr0y said:
The bootloader that came with our phone is borked and doesn't allow flashing the new bootloader. Need to download the OTA image from Google and follow their steps for flashing it via recovery. Make sure to flash the stock boot.img for your current setup beforehand to unroot. The OTA will overwrite the bootloader and fix the issue so in the future you will be able to flash-all with the factory images as usual.
Click to expand...
Click to collapse
if the bootloader is unlocked, the flash all command does not work ? If you are on a custom kernel, can't you just download the stock image then run the script then relock the bootloader ?

mikeprius said:
if the bootloader is unlocked, the flash all command does not work ? If you are on a custom kernel, can't you just download the stock image then run the script then relock the bootloader ?
Click to expand...
Click to collapse
The flash all command works fine on an unlocked bootloader. I've used it several times (I play around too much ) As for your second question, I haven't used a custom kernel but I have flashed Magisk which writes to the bootloader and I've never had a problem using the flash-all.bat file. Some people for some reason or another were able to use it (the flash all) for the December update but it would fail to write the bootloader for some reason or another. Some tried flashing the bootloader manually with fastboot and that would fail too. From what I've seen, the only way out for those with that problem was to flash the OTA. I don't know how many of them were using custom kernels so I can't really say if that's the problem or not. I can only tell you I flashed the December update using the flash all and had no problems at all.

Ra6idr0y said:
The bootloader that came with our phone is borked and doesn't allow flashing the new bootloader. Need to download the OTA image from Google and follow their steps for flashing it via recovery. Make sure to flash the stock boot.img for your current setup beforehand to unroot. The OTA will overwrite the bootloader and fix the issue so in the future you will be able to flash-all with the factory images as usual.
Click to expand...
Click to collapse
I have sloved this problem, I changed TYPE-C to TYPE-C cable to TYPE-C to TYPE-A cable and I flashed it.
I think it's google's cable's problem.

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