Database Develop

Stuck on mi boot screen avec flashing boot and recovery using fastboot

Hello everyone,
I'm trying to install TWRP + Boot on my Mi5 in order to install Xiaomi.eu rom later.
I have been following these steps: https://xiaomi.eu/community/threads...r-xiaomi-mi5-unlocked-bl-only-released.31231/
All went well:
Code:
C:\Miflash_tool_gemini\Google\Android>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (40072 KB)...
OKAY [ 0.977s]
writing 'recovery'...
OKAY [ 1.815s]
finished. total time: 2.795s
C:\Miflash_tool_gemini\Google\Android>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (37248 KB)...
OKAY [ 0.918s]
writing 'boot'...
OKAY [ 0.341s]
finished. total time: 1.260s
C:\Miflash_tool_gemini\Google\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.995s]
booting...
OKAY [ 1.180s]
finished. total time: 2.177s
Until the moment to reboot to TWRP.
It just displays the mi logo forever and doesn't boot. It's been 10min now.
Is that normal?
Should I continue to wait?
Thx

After 30min with no progress I decided to stop the phone.
I pressed the power button for few seconds. The mi logo disappeared. I stopped pressing. But straight away the phone is trying to reboot and displays again the mi logo forever
F*********************ck!

Managed to enter in Fastboot mode! Don't ask me how.
No I guess, from what I read in various places I need to flash a fastboot DEV ROM using MiFlash?
Seem to be the procedure when you are in bootloop.
I guess I'll have to unlock again the phone once this ROM will be flashed?

Ok I'm back on track. I've downloaded the last Mi5 Global DEV fastboot ROM (gemini_global_images_6.5.30_20160516.0000.22_6.0_global_9cee9512c7.tgz)
I flashed it using MiFlash. But I kept the storage. I probably should have flashed all because now it keeps on say it can't find the device ID and I get some java stack trace errors complaining about SQLite access problems.
Tomorrow I'll try again to flash TWRP. We will see if it does the same :-/

That's it I've managed to flash TWRP + xiaomi.eu stable rom.
I think the part that generated the bootloop was the fact that I didn't run the following command after flashing TWRP:
Code:
fastboot reboot
I rebooted manually using power button + vol. up.
Now everything is working fine.

Foobrother said:
Hello everyone,
I'm trying to install TWRP + Boot on my Mi5 in order to install Xiaomi.eu rom later.
I have been following these steps: https://xiaomi.eu/community/threads...r-xiaomi-mi5-unlocked-bl-only-released.31231/
All went well:
Code:
C:\Miflash_tool_gemini\Google\Android>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (40072 KB)...
OKAY [ 0.977s]
writing 'recovery'...
OKAY [ 1.815s]
finished. total time: 2.795s
C:\Miflash_tool_gemini\Google\Android>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (37248 KB)...
OKAY [ 0.918s]
writing 'boot'...
OKAY [ 0.341s]
finished. total time: 1.260s
C:\Miflash_tool_gemini\Google\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.995s]
booting...
OKAY [ 1.180s]
finished. total time: 2.177s
Until the moment to reboot to TWRP.
It just displays the mi logo forever and doesn't boot. It's been 10min now.
Is that normal?
Should I continue to wait?
Thx
Click to expand...
Click to collapse
my phone also got stuck on the logo when i flashed supersu which i think was quite old..
i then flashed a newer zip and everything went back to normal.happy to see that you were able to fix your phone. iwas devastated for the 15min that my phone wasnt working
---------- Post added at 01:55 PM ---------- Previous post was at 01:54 PM ----------
Foobrother said:
Ok I'm back on track. I've downloaded the last Mi5 Global DEV fastboot ROM (gemini_global_images_6.5.30_20160516.0000.22_6.0_global_9cee9512c7.tgz)
I flashed it using MiFlash. But I kept the storage. I probably should have flashed all because now it keeps on say it can't find the device ID and I get some java stack trace errors complaining about SQLite access problems.
Tomorrow I'll try again to flash TWRP. We will see if it does the same :-/
Click to expand...
Click to collapse
have you figured out why this error came in the first place??

XT1097 Marshmallow TWRP not loading

Hey everyone
I'm trying to root my XT1097 (Canadian on Wind Mobile) but I cant seem to get TWRP to install. Everytime I try to boot into recovery it just boots normally. I have been searching these forums (and the internet) for days and can't seem to find a solution. I did see one mention of some devices automatically replacing a custom recovery when trying to boot into recovery for the first time and needing to hold a specific key combo while booting to prevent this but as near as I can tell this device is not one of them. It sure seems to be acting that way though, am I missing something?
Here is the info
Moto X 2014 XT1097 on Wind Mobile in Canada
Unlocked bootloader
Dev options on with USB debugging enabled
"twrp-3.0.2-1-victara.img" is the file I am trying to use from the twrp website, which I believe is the correct one
I enter the following in cmd
E:\Programs\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.328s]
booting...
OKAY [ 0.251s]
finished. total time: 0.578s
and it reboots normally. If I try this:
E:\Programs\Android>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (9160 KB)...
OKAY [ 0.328s]
writing 'recovery'...
OKAY [ 0.407s]
finished. total time: 0.734s
Then select recovery on the phone, it just shuts off.
It says "Mismatched partition size (recovery)" in pink when I flash the recovery image but I read that that can be ignored if you use the first method.
Any help would be great!

Jackson604 said:
Hey everyone
I'm trying to root my XT1097 (Canadian on Wind Mobile) but I cant seem to get TWRP to install. Everytime I try to boot into recovery it just boots normally. I have been searching these forums (and the internet) for days and can't seem to find a solution. I did see one mention of some devices automatically replacing a custom recovery when trying to boot into recovery for the first time and needing to hold a specific key combo while booting to prevent this but as near as I can tell this device is not one of them. It sure seems to be acting that way though, am I missing something?
Here is the info
Moto X 2014 XT1097 on Wind Mobile in Canada
Unlocked bootloader
Dev options on with USB debugging enabled
"twrp-3.0.2-1-victara.img" is the file I am trying to use from the twrp website, which I believe is the correct one
I enter the following in cmd
E:\Programs\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.328s]
booting...
OKAY [ 0.251s]
finished. total time: 0.578s
and it reboots normally. If I try this:
E:\Programs\Android>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (9160 KB)...
OKAY [ 0.328s]
writing 'recovery'...
OKAY [ 0.407s]
finished. total time: 0.734s
Then select recovery on the phone, it just shuts off.
It says "Mismatched partition size (recovery)" in pink when I flash the recovery image but I read that that can be ignored if you use the first method.
Any help would be great!
Click to expand...
Click to collapse
You use Volume Up, not the power button to select Recovery. The mismatch is normal because you're flashing a non-stock recovery.

Wow I knew it was going to be something dead simple I was missing, thanks I'll give that a go when I get home!

Back to Stock Recovery in Huawei P10 VTR-L29C185B165

I recently installed TWRP recovery on my phone and unlocked the bootloader. However, I did not read that after this you can not install OTA updates, and I would like to be able to download them. So my question is how to effectively upload Stock Recovery on my phone? I downloaded my ROM and extracted the file RECOVERY.IMG from it and tried to upload it through ADB, but during the flash it appears to me in CMD:
"C:\minimal>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (35396 KB)...
OKAY [ 0.774s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.784s"
What can I do in this case? Will anyone help me? Thank you.

the recovery partition on oreo isn't called recovery! it's called ramdisk, BTW can you upload the recovery image please?

Unable to flash any recovery. Please help

I am on 12.5.4.0 stock ROM. I am unable to overwrite the stock MIUI recovery. I always get the error message:
FAILED (Status read failed (Too many links))
The recovery image that i am using is a lineage OS 18.1 recovery image that i obtained from a Telegram group on a new lineage 18.1 ROM. I also tried a TWRP image by wzsx, with the same result.
I also tried disabling vbmeta with the command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta\vbmeta_vd171--V12.5.3.0.RJOMIXM.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.016s]
Writing 'vbmeta' OKAY [ 0.000s]
Finished. Total time: 0.016s
But after reboot it goes back to MIUI recovery.
Previously i had flashed crDroid ROM with an SHRP recovery. I remember getting the same "Too many links" error that time too, but i have forgotten how i managed to flash SHRP that time.
I tried using SP FLash Tool , but here too i get an error message " Invalid scatter file name" or something like that for the scatter file in the 12.5.4.0 stock ROM. Then i tried MTK tool to create a scatter file for my Redmi Note 9 but this time i get an error saying it is unabke to read the ROM storage format. Can anyone please help?

Do:
fastboot flash vbmeta vbmeta_vd171--V12.5.3.0.RJOMIXM.img
Is same to do:
fastboot --disable-verity --disable-verification flash vbmeta original_stock_vbmeta.img

It seens a problem with typing.
Did you try to use quotes?
Like
fastboot flash recovery "here is the place/of/image.img"

VD171 said:
It seens a problem with typing.
Did you try to use quotes?
Like
fastboot flash recovery "here is the place/of/image.img"
Click to expand...
Click to collapse
Thanks for the reply. No i don't think it's a problem with typing:
fastboot flash recovery recovery.img
Sending 'recovery' (65536 KB) OKAY [ 1.992s]
Writing 'recovery' OKAY [ 0.881s]
Finished. Total time: 2.878s
Now i tried going back to 12.0.6.0 stock ROM with TWRP-RedmiNote9-V12.0.6.0.QJOMIXM-20201213-wzsx15-sanja56. This time success:
C:\Users\iamam\Downloads\TWRP>fastboot flash recovery recovery.img
Sending 'recovery' (34076 KB) OKAY [ 0.855s]
Writing 'recovery' OKAY [ 0.453s]
Finished. Total time: 1.340s
fastboot boot recovery.img
Sending 'boot.img' (34076 KB) OKAY [ 1.017s]
Booting OKAY [ 0.051s]
Finished. Total time: 1.103s
But IT STILL BOOTS INTO MIUI stock RECOVERY!! I can't understand it. Just for fun i changed recovery.img in the fastboot ROM to the recovery.img that i wanted but MiFlash fails (obviously!!!!). Is there a way to check recovery partition on the phone?

12Frodo said:
Thanks for the reply. No i don't think it's a problem with typing:
fastboot flash recovery recovery.img
Sending 'recovery' (65536 KB) OKAY [ 1.992s]
Writing 'recovery' OKAY [ 0.881s]
Finished. Total time: 2.878s
Now i tried going back to 12.0.6.0 stock ROM with TWRP-RedmiNote9-V12.0.6.0.QJOMIXM-20201213-wzsx15-sanja56. This time success:
C:\Users\iamam\Downloads\TWRP>fastboot flash recovery recovery.img
Sending 'recovery' (34076 KB) OKAY [ 0.855s]
Writing 'recovery' OKAY [ 0.453s]
Finished. Total time: 1.340s
fastboot boot recovery.img
Sending 'boot.img' (34076 KB) OKAY [ 1.017s]
Booting OKAY [ 0.051s]
Finished. Total time: 1.103s
But IT STILL BOOTS INTO MIUI stock RECOVERY!! I can't understand it. Just for fun i changed recovery.img in the fastboot ROM to the recovery.img that i wanted but MiFlash fails (obviously!!!!). Is there a way to check recovery partition on the phone?
Click to expand...
Click to collapse
Are you sure are not booting into MIUI after flashing? because MIUI installs back the default recovery.

vagelis199 said:
Are you sure are not booting into MIUI after flashing? because MIUI installs back the default recovery.
Click to expand...
Click to collapse
Exactly.
If you want to use custom recovery but without root/magisk, you need to flash my patched boot image.
This patched boot image does NOT install back the default recovery and does NOT install root/magisk.
[BOOT][IMG][PATCHED] Boot Image Partition without OVERWRITE OF RECOVERY for MERLIN (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)
PATCHED BOOT.IMG for MERLIN by VD171 For what do I need it ? At every boot, MIUI overwrites RECOVERY partition for stock rom recovery partition and replaces any custom recovery like TWRP. This patch disables this overwriting and keep any custom...
forum.xda-developers.com

VD171 said:
Exactly.
If you want to use custom recovery but without root/magisk, you need to flash my patched boot image.
This patched boot image does NOT install back the default recovery and does NOT install root/magisk.
[BOOT][IMG][PATCHED] Boot Image Partition without OVERWRITE OF RECOVERY for MERLIN (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)
PATCHED BOOT.IMG for MERLIN by VD171 For what do I need it ? At every boot, MIUI overwrites RECOVERY partition for stock rom recovery partition and replaces any custom recovery like TWRP. This patch disables this overwriting and keep any custom...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks to everybody who replied. But i am using the command "fastboot reboot recovery" after flashing the recovery. But you are right, i did realise that if you just reboot to a stock ROM it reinstalls the stock recovery. Mea Culpa. But i wish this was explained someplace like a general explainer to a newbie.
Anyway, i downloaded the "Platform tools SDK" and used that fastboot and it now installs SHRP and Lineaage OS 18.1 recovery. But TWRP is still a problem. But at least i can install any custom ROM that i want. And yes, thanks VD171, i won't forget to use your patched boot image from now on.

12Frodo said:
Thanks to everybody who replied. But i am using the command "fastboot reboot recovery" after flashing the recovery. But you are right, i did realise that if you just reboot to a stock ROM it reinstalls the stock recovery. Mea Culpa. But i wish this was explained someplace like a general explainer to a newbie.
Anyway, i downloaded the "Platform tools SDK" and used that fastboot and it now installs SHRP and Lineaage OS 18.1 recovery. But TWRP is still a problem. But at least i can install any custom ROM that i want. And yes, thanks VD171, i won't forget to use your patched boot image from now on.
Click to expand...
Click to collapse
You are welcome, my friend.
Enjoy
Sadly, no one says that to you.
But, if you want to enter in recovery, just type "fastboot reboot" and hold the Vol Up button.

remove TWRP and install Linageos recovery error.

I have a pixel 5, i installed linageos recovery and lineageos rom
however when i tried TWRP it now is frozen on splashscreen for recovery project 3.7.0_11.0
i tried flashing back lineage, it says it worked but when i restart recovery the same splash screen is there.
>fastboot flash vendor_boot vendor_boot.img
Sending 'vendor_boot_b' (98304 KB) OKAY [ 2.986s]
Writing 'vendor_boot_b' OKAY [ 2.071s]
Finished. Total time: 5.329s
Click to expand...
Click to collapse
When i try to simple boot recovery i get this error.
>fastboot boot vendor_boot.img
creating boot image...
creating boot image - 100665344 bytes
Sending 'boot.img' (98306 KB) OKAY [ 2.972s]
Booting (bootloader) boot.img missing cmdline or OS version
FAILED (remote: 'Error verifying the received boot.img: Unsupported')
fastboot: error: Command failed
Click to expand...
Click to collapse
And same error when i try booting TWRP
>fastboot boot twrp-3.7.0_11-0-redfin.img
Sending 'boot.img' (98304 KB) OKAY [ 2.936s]
Booting (bootloader) boot.img missing cmdline or OS version
OKAY [ 2.318s]
Finished. Total time: 5.343s
Click to expand...
Click to collapse
after trying to boot TWRP it does this error and then goes into recovery mode back to splash screen
How do i wipe recovery and get linageos recovery back in my pixel please?

if TWRP stuck on splash screen you can still use it from cmd line
https://twrp.me/faq/openrecoveryscript.html