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
Related
I was on 4.4.2, rooted. I did a factory reset, flashed stock 4.4.2 (system, recovery, and boot), then got the 4.4.4 OTA.
Still says "unlocked bootloader."
I installed Titanium -- no root.
I rebooted to bootloader, tried flashing TWRP with:
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.1-ghost.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8220 KB)...
OKAY [ 0.774s]
writing 'recovery'...
OKAY [ 1.228s]
finished. total time: 2.002s
Rebooted to recovery -- got 'dead andy' with 'No Command' below.
Tried:
Code:
fastboot boot openrecovery-twrp-2.7.1.1-ghost.img
downloading 'boot.img'...
OKAY [ 0.775s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.875s
Also tried flashing `UPDATE-SuperSU-v1.94.zip` from stock recovery ... got
Code:
qe 0/1
-- Install /data/media/0 ...
Finding update package...
Opening update package...
Verifying update package...
Installation aborted.
I also then tried all of the above with `mfastboot` -- same result.
What do I do now?
d0g said:
I was on 4.4.2, rooted. I did a factory reset, flashed stock 4.4.2 (system, recovery, and boot), then got the 4.4.4 OTA.
Still says "unlocked bootloader."
I installed Titanium -- no root.
I rebooted to bootloader, tried flashing TWRP with:
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.1-ghost.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8220 KB)...
OKAY [ 0.774s]
writing 'recovery'...
OKAY [ 1.228s]
finished. total time: 2.002s
Rebooted to recovery -- got 'dead andy' with 'No Command' below.
Tried:
Code:
fastboot boot openrecovery-twrp-2.7.1.1-ghost.img
downloading 'boot.img'...
OKAY [ 0.775s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.875s
Also tried flashing `UPDATE-SuperSU-v1.94.zip` from stock recovery ... got
Code:
qe 0/1
-- Install /data/media/0 ...
Finding update package...
Opening update package...
Verifying update package...
Installation aborted.
What do I do now?
Click to expand...
Click to collapse
The issue is that you have to IMMEDIATELY reboot into custom recovery. Do this (from bootloader screen):
fastboot flash recovery twrp_file_name.img
fastboot reboot-bootloader
Now VOL DOWN to recovery, and VOL UP to select it.
If you don't do it this way, TWRP doesn't 'stick'. As long as you successfully boot into TWRP, click exit and it will offer to root for you.
samwathegreat said:
If you don't do it this way, TWRP doesn't 'stick'. As long as you successfully boot into TWRP, click exit and it will offer to root for you.
Click to expand...
Click to collapse
AHA! Thank you thank you!
samwathegreat said:
The issue is that you have to IMMEDIATELY reboot into custom recovery. Do this (from bootloader screen):
fastboot flash recovery twrp_file_name.img
fastboot reboot-bootloader
Now VOL DOWN to recovery, and VOL UP to select it.
If you don't do it this way, TWRP doesn't 'stick'. As long as you successfully boot into TWRP, click exit and it will offer to root for you.
Click to expand...
Click to collapse
I notice you help out on almost every thread and have helped me more then a few times. Just thought id say thanks from all us that are trying to lose are noob status lol
Sent from my XT1058 using Tapatalk
Hi there.. Am also using moto x and running stock 4.4.4... And i want to Unlock my bootloader and get Root... Can u pls guide me through the steps and file i need? Thank you
Hello guys
Sorry about my bad english.
I aready flashed twrp, philz,CM recovery but I still got the original recovery instead.
The CMD windows says OK.
My phone is stuck in the aqua splash logo, looping the splash.
"C:\Users\Guilherme\Downloads\New folder>fastboot flash recovery twrp-2.8.5.0-titan.img
target reported max download size of 536870912 bytes
sending 'recovery' (9694 KB)...
OKAY [ 0.329s]
writing 'recovery'...
OKAY [ 0.195s]
finished. total time: 0.527s"
ghtmiyashiro said:
Hello guys
Sorry about my bad english.
I aready flashed twrp, philz,CM recovery but I still got the original recovery instead.
The CMD windows says OK.
My phone is stuck in the aqua splash logo, looping the splash.
"C:\Users\Guilherme\Downloads\New folder>fastboot flash recovery twrp-2.8.5.0-titan.img
target reported max download size of 536870912 bytes
sending 'recovery' (9694 KB)...
OKAY [ 0.329s]
writing 'recovery'...
OKAY [ 0.195s]
finished. total time: 0.527s"
Click to expand...
Click to collapse
Download the latest TWRP: https://dl.twrp.me/titan/
Here is the link for the motorola fastboot: https://www.androidfilehost.com/?fid=95916177934532795
"TWRP Install (Requires TWRP 2.8.4 or higher already installed):
Download the latest TWRP image file (.img) from the download link and boot TWRP. Go to install and find and select the Images... button. Browse to the image that you downloaded and select it. Choose recovery and swipe to flash."
so boot to recovery: mfastboot.exe boot recovery twrp-2.8.6.0-titan.img Don't forget to run CMD as admin
then flash the .img recovery
I can't boot twrp.
tried flashing and boot directly from fastboot( mfastboot boot twrp.img) but got a flashing screen.
the only recovery i can boot from fastboot is the CM.
im stuck with this piece of sh*t phone and "waiting for any device". I flashed TWRP 142314 times on my phone, and today this bloody problem comes out and i cant f*king solve it. My drivers and everything is up to date, expect something named "S1 Boot Fastboot" (warning sing near that in device manager). I have no idea what the hell is that and i cant flash twrp and install custom rom. Any ideas, excpet that one about uninstalling win10 )))
yey, a new problem:
C:\Users\nevas\Desktop\sony\ADB\platform-tools-latest-windows\platform-tools>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (10704 KB)...
OKAY [ 0.350s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.356s
nevenx said:
yey, a new problem:
C:\Users\nevas\Desktop\sony\ADB\platform-tools-latest-windows\platform-tools>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (10704 KB)...
OKAY [ 0.350s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.356s
Click to expand...
Click to collapse
You can't flash TWRP to the recovery partition on the Xperia Z. It doesn't use the recovery partition; instead, it uses the FOTAKernel partition, which is inaccessible by Fastboot. If you want to destroy your old stock firmware and install custom ROM, flash TWRP to boot partition. The phone should not boot to the firmware and boots straight to TWRP.
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.
I'm trying to install custom recovery and ROM on my Redmi 9. I've used XiaoMiToolV2 (https://github.com/francescotescari/XiaoMiToolV2) built on my mac to unlock the boot loader.
But I seem to be stuck trying to replace the recovery.
I tried TWRP- this sent me into a boot loop,
so I tried orangefox from here: https://orangefox.download/device/garden which fixed the bootloop, but everytime I go into recovery it shows me the MIUI Recovery tool.
I also tried pitchblack recovery from here: https://pitchblackrecovery.com/lancelot/ which gives me the same problem.... booting into recovery always shows MIUI Recovery tool.
This is the command I've been using to flash the recovery:
adb reboot bootloader
fastboot flash recovery recovery.img
then a restart, then:
adb reboot recovery
Am I missing something?
supagu said:
I'm trying to install custom recovery and ROM on my Redmi 9. I've used XiaoMiToolV2 (https://github.com/francescotescari/XiaoMiToolV2) built on my mac to unlock the boot loader.
But I seem to be stuck trying to replace the recovery.
I tried TWRP- this sent me into a boot loop,
so I tried orangefox from here: https://orangefox.download/device/garden which fixed the bootloop, but everytime I go into recovery it shows me the MIUI Recovery tool.
I also tried pitchblack recovery from here: https://pitchblackrecovery.com/lancelot/ which gives me the same problem.... booting into recovery always shows MIUI Recovery tool.
This is the command I've been using to flash the recovery:
adb reboot bootloader
fastboot flash recovery recovery.img
then a restart, then:
adb reboot recovery
Am I missing something?
Click to expand...
Click to collapse
Unlock the bootloader before installing the Twrp.
https://miui.blog/any-devices/mi-unlock-tool-mac-linux/
https://www.xiaomitool.com/MiUnlockTool
Twrp:
https://androidfilehost.com/?w=files&flid=318235
.\fastboot flash recovery twrp.img
.\fastboot boot twrp.img
Yes I have unlocked my device using XiaoMiToolV2, I see a little unlocked padlock when booting my phone now.
I tried downloading twrp from the above url (thanks for that!)
I renamed it to recovery.img then:
[email protected] twrp % fastboot flash recovery recovery.img
Sending 'recovery' (65536 KB) OKAY [ 3.746s]
Writing 'recovery' OKAY [ 1.123s]
Finished. Total time: 4.874s
[email protected] twrp % fastboot boot recovery.img
Sending 'boot.img' (65536 KB) OKAY [ 3.733s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
[email protected] twrp % fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.001s
[email protected] twrp % fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache' OKAY [ 0.046s]
Finished. Total time: 0.047s
[email protected] twrp % fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
[email protected] twrp % adb reboot bootloader
[email protected] twrp % fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.001s
[email protected] twrp %
So your command to boot the image is incorrect, so I tried some other reboot commands but still when I did the reboot recovery it comes up with MIUIRecovery 5.0.... I should be seeing twrp here right instead?
supagu said:
Yes I have unlocked my device using XiaoMiToolV2, I see a little unlocked padlock when booting my phone now.
I tried downloading twrp from the above url (thanks for that!)
I renamed it to recovery.img then:
[email protected] twrp % fastboot flash recovery recovery.img
Sending 'recovery' (65536 KB) OKAY [ 3.746s]
Writing 'recovery' OKAY [ 1.123s]
Finished. Total time: 4.874s
[email protected] twrp % fastboot boot recovery.img
Sending 'boot.img' (65536 KB) OKAY [ 3.733s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
[email protected] twrp % fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.001s
[email protected] twrp % fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache' OKAY [ 0.046s]
Finished. Total time: 0.047s
[email protected] twrp % fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
[email protected] twrp % adb reboot bootloader
[email protected] twrp % fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.001s
[email protected] twrp %
So your command to boot the image is incorrect, so I tried some other reboot commands but still when I did the reboot recovery it comes up with MIUIRecovery 5.0.... I should be seeing twrp here right instead?
Click to expand...
Click to collapse
After flashing TWRP press volume+and power button
MIUI is automatically replacing TWRP with MIUI Recovery. So to fix this after flashing the recovery, you will need to flash the vbmeta image with the flag --disable-verity:
Code:
fastboot flash recovery recovery.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot recovery
This is the vbmeta image: https://forum.xda-developers.com/attachments/vbmeta_redmi9-img.5449805/
Also use this recovery: https://forum.xda-developers.com/t/recovery-twrp-unofficial-twrp-recovery-3-6-1_11-0.4421301/
Thanks guys!
Sergi, your combination of vbmeta and recovery has worked!
Proper url is here:
[RECOVERY][TWRP][UNOFFICIAL] TWRP recovery 3.6.1_11-0
TWRP recovery 3.6.1 for lancelot (redmi 9 | lancelot/galahad) I am not responsible for your brick devices. The recovery is fully working and has been tested. If you encounter a problem, write here, maybe they will help you. Before you accuse me...
forum.xda-developers.com
(you had a typo in your post)
supagu said:
Thanks guys!
Sergi, your combination of vbmeta and recovery has worked!
Proper url is here:
[RECOVERY][TWRP][UNOFFICIAL] TWRP recovery 3.6.1_11-0
TWRP recovery 3.6.1 for lancelot (redmi 9 | lancelot/galahad) I am not responsible for your brick devices. The recovery is fully working and has been tested. If you encounter a problem, write here, maybe they will help you. Before you accuse me...
forum.xda-developers.com
(you had a typo in your post)
Click to expand...
Click to collapse
No problem , and ahh I will correct the link . So glad it worked.