Database Develop

Cannot update from cyanogen recovery to twrp recovert

Hello,
I am trying to update from the old cyanogen recovery to the TWRP recovery in this post: https://forum.xda-developers.com/showthread.php?t=3557606
I have enable to write the cyanogen recovery in the developer options.
I have rebooted into flashboot and executed:
----
[email protected]:/tmp/xperia/TWRP# adb reboot bootloader
[email protected]:/tmp/xperia/TWRP# fastboot flash recovery twrp-3.1.1-0-z3c_V02.img
target didn't report max-download-size
sending 'recovery' (14296 KB)...
OKAY [ 0.572s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.502s
[email protected]:/tmp/xperia/TWRP# fastboot reboot
rebooting...
----
Unfortunately the system boots in the cyanogen recovery anyhow.
does anyone knows what am I doing wrong ?
Many thanks in advance

There's an app called NDR Utils that lets you choose which recovery to boot to, but I don't know of a clean link where you can get it.
I got it with Nut's Dual Recovery:
http://nut.xperia-files.com/path/XZDualRecovery/XZDualRecovery_2.8.26

I mean you have to unlock your bootloader with:
Code:
fastboot -i 0x0fce oem unlock 0xhex_unlock_key
(see here)
also you have to erase the old recovery with:
Code:
fastboot erase recovery
(claimed in this guide here)
Edit: I forgot you used a CyanogenMod Recovery, which is stored in FOTAkernel,
so you have to use also :
Code:
fastboot erase boot
fastboot erase FOTAKernel
I did read it here
Hope that does help you

Thanks a lot !

imascara said:
Thanks a lot !
Click to expand...
Click to collapse
I updated my last posting

Can't install TWRP on my X2 Pro Fastboot Error

Hello I have this problem with my realme X2 Pro
I wanted to install TWRP on my phone using ADB and Fastboot after unlocking with success my bootloader The problem Is I first intalled with success TWRP BUT the touch was not working so I decieded to try a newer version but now this error apears
Sending 'recovery' (98304 KB) OKAY [ 2.354s]
Writing 'recovery' FAILED (remote: 'Error flashing partition : Volume Full')
fastboot: error: Command failed
I Tried to do adb push twrp-3.4.0-0-RMX1931-mauronofrio.img /dev/block/bootdevice/by-name/recovery but i did not work It got me this error
adb: error: failed to get feature set: no devices/emulators found
If anyone could help me it would very apreciated

I though it was (from Fastboot mode):
Code:
fastboot flash recovery <your recovery image here>
and then
Code:
fastboot flash vbmeta vbmeta.img

Uqbar said:
I though it was (from Fastboot mode):
Code:
fastboot flash recovery <your recovery image here>
and then
Code:
fastboot flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Hello when I try to use fastboot flash recovery twrp.img that is creating the Volume full error
How can I solve it ?

Farchyk said:
Hello when I try to use fastboot flash recovery twrp.img that is creating the Volume full error
How can I solve it ?
Click to expand...
Click to collapse
Are you really really sure the twrp image is the right size?
Mauronofrio's one is exactly 81920 KB, not 98304 KB.
Also the official TWRP has the same size, AFAIK.
I would re-download it and maybe checksum it.

[HELP FİNDİNG TWRP]P SMART FİG-LX1 C432

I am trying to install lineageos for 2 days now twrp keeps giving error would anyone could send me hak86's twrp image I couldnt find on telegram sourceforge and github thanks and it is now stuck on formatting data

there is (now) a functioning link in the "main" topic forum:
see https://forum.xda-developers.com/t/...for-huawei-p-smart-2018.3980019/post-84237985
@haky 86 : thnx for that

Bokkahontas said:
there is (now) a functioning link in the "main" topic forum:
see https://forum.xda-developers.com/t/...for-huawei-p-smart-2018.3980019/post-84237985
@haky 86 : thnx for that
Click to expand...
Click to collapse
I can remake it, but I need some testers as I don't have the device right now.

@haky 86 : that would be nice, since installing the twrp failed:
$ fastboot flash recovery twrp-3.4.0.0-v1-figo-haky86.img
> Sending 'recovery' (10734 KB) OKAY [ 0.382s]
> Writing 'recovery' FAILED (remote: 'partition length get error')
> fastboot: error: Command failed
device is properly connected, I also doublechecked that bootloader is still unlocked after upgrade from emui 8 to 9.1 (Build is 9.1.0.216(C432E22R1P5))
Can we merge this topic with the following, so there is no parallel discussion in two different topics within the forum?! ;-)
=> https://forum.xda-developers.com/t/...for-huawei-p-smart-2018.3980019/post-84237985

switch recovery with recovery_ramdisk

twrp installation succeded with _ramdisk, thanks for the fast reply!
I followed then instructions from official lineage 16 wiki (https://wiki.lineageos.org/devices/figo/install) to install lineageOS 16. Sideload of the actual zip (lineage-16.0-20210115-nightly-figo-signed) in twrp also worked perfectly and I eagerly tipped on "reboot" in twrp hoping to see my new OS booting for the the first time... BUT:
Unfortunately I got stuck at a probably similar point as Capybar (see https://forum.xda-developers.com/t/...k-recovery-and-cant-boot-into-system.4126357/):
Phone stopped being able to enter any recovery at all. The system itself does not boot. The HUawei start screen "Your device has been unlocked and cannot be trustet (...) only tells me (...) "Your device is booting now...", the recovery option never appears (previously in the start screen with 'unlocked device' warning it used to suggest pressing volume UP to enter recovery, now it only shows "Your device is booting now").
Then it shows me the Teamwin Logo and at that point freezes.
I cannot acces the phone with adb oder fastboot from host machine..
=> Does anybody knows if there is a possibility to gain acces to recovery?

if stuck on Huawei splash screen, just run factory reset with stock recovery.
to boot into recovery on this crap;
* Keep pressing on vol up + vol down + power.
* Leave vol down button only and keep pressing other 2 buttons once huawei splash screen appears .
* you should able to boot into recovery.

thnx again haky !!!
Nevertheless feeling stupid now (or rather like my mum when I first modified our home-PC autoexec.bat on a 386DX machine in MS DOS to make the PC wish her a good morning on the VGA display) .Back to topic:
I managed to get the the phone start in recovery boot mode asking me
(1) Press Power key to continue
(2) Press Volume Uo key (...) to enter erecovery to restore aour device
(3) Vour device will continue to booot (...)
=> all options result in the same(?) everlasting bootloop
so I succesfully tried fastboot boot mode (error 64 message on screen) and flashed your stock recovery:
$ fastboot devices -l
> XEDDU*********** fastboot usb:2-2
$ fastboot flash recovery_ramdisk 9.1_stock_rec.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.156s]
writing 'recovery_ramdisk'...
OKAY [ 0.269s]
finished. total time: 1.425s
Rebooting phone again leads to bootloop
Edit: Not the very same bootloop since twrp-logo does not appear anymore but phone message is "Your device is booting now ... " and that's it
Got some ideas?
Edit#2 [SOLVED]: put fastboot option -w into command for flashing stock recovery => phone resurrected to stock software (at least)

Thanks for the update!
Im was stuck in the same situation. If you succeed in flashing LineageOS I would love to hear how.
Good luck!

without a phone I can't do a sh*t, try this recovery (3.5.0) and tell me if boots or not.

haky 86 said:
without a phone I can't do a sh*t, try this recovery (3.5.0) and tell me if boots or not.
Click to expand...
Click to collapse
While flashing it I get the following log:
.\fastboot flash recovery_ramdisk .\recovery.img -w
target reported max download size of 471859200 bytes
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
sending 'recovery_ramdisk' (13452 KB)...
OKAY [ 0.376s]
writing 'recovery_ramdisk'...
OKAY [ 0.102s]
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.068s]
finished. total time: 0.546s
I can boot into the recovery. My issue is, when I use wipe -> format data, it formats, says "done", but dosn't give me an option to proceed or go back. So I'm stuck there. After a hard reset I tried to boot into recovery again, but it gets stuck on the teamwin screen.
After flashing it again with the -w option, it works again.
An other issue I have is, when I try to wipe eg. cache, it works, but while trying to update the partition details, it "failed to mount '/data' (Invalid argument)". The same happens, when I install something.

Zet24 said:
While flashing it I get the following log:
.\fastboot flash recovery_ramdisk .\recovery.img -w
target reported max download size of 471859200 bytes
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
sending 'recovery_ramdisk' (13452 KB)...
OKAY [ 0.376s]
writing 'recovery_ramdisk'...
OKAY [ 0.102s]
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.068s]
finished. total time: 0.546s
I can boot into the recovery. My issue is, when I use wipe -> format data, it formats, says "done", but dosn't give me an option to proceed or go back. So I'm stuck there. After a hard reset I tried to boot into recovery again, but it gets stuck on the teamwin screen.
After flashing it again with the -w option, it works again.
An other issue I have is, when I try to wipe eg. cache, it works, but while trying to update the partition details, it "failed to mount '/data' (Invalid argument)". The same happens, when I install something.
[/QUOT]
can you pm me a screenshot?
Click to expand...
Click to collapse

1) @haky 86 : I can also boot into the (3.5.0) recovery
EDIT (fyi): could boot into that recovery, but after installation of stock rom (and likewise in official linage rom) my SIM Card was not detected.
Using "old" stock recovery [9.1_stock_rec.img] and SIM Card works fine. Still that Wifi-Password-Problem...
Zet24 said:
(...)
My issue is, when I use wipe -> format data, it formats, says "done", but dosn't give me an option to proceed or go back. So I'm stuck there. After a hard reset I tried to boot into recovery again, but it gets stuck on the teamwin screen.
(...)
Click to expand...
Click to collapse
2) @Zet24 : this looks rather to a twrp 3.4.0.0 error (?) because previously I got the same which finally ended in stucked teamwin screen and bootloop (see above)
3) @Zet24 : I managed to flash and boot into official figo lineage 16 ROM (lineage-16.0-20210122-nightly-figo-signed) by copying the zip file on sd card and install it directly in twrp (install >> from zip file) -- actually I don't know why sideload method doesn't work..
Unfortunately I couldn't not connect to wifi (see discussion in main topic Forum: https://forum.xda-developers.com/t/...for-huawei-p-smart-2018.3975303/post-83896865) even after wiping data and cache with stock recovery, but that is for another time/topic

I posted a tutorial on how to flash Lineage OS on this phone on the other Thread... the Lineage OS thread.

Bokkahontas said:
twrp installation succeded with _ramdisk, thanks for the fast reply!
I followed then instructions from official lineage 16 wiki (https://wiki.lineageos.org/devices/figo/install) to install lineageOS 16. Sideload of the actual zip (lineage-16.0-20210115-nightly-figo-signed) in twrp also worked perfectly and I eagerly tipped on "reboot" in twrp hoping to see my new OS booting for the the first time... BUT:
Unfortunately I got stuck at a probably similar point as Capybar (see https://forum.xda-developers.com/t/...k-recovery-and-cant-boot-into-system.4126357/):
Phone stopped being able to enter any recovery at all. The system itself does not boot. The HUawei start screen "Your device has been unlocked and cannot be trustet (...) only tells me (...) "Your device is booting now...", the recovery option never appears (previously in the start screen with 'unlocked device' warning it used to suggest pressing volume UP to enter recovery, now it only shows "Your device is booting now").
Then it shows me the Teamwin Logo and at that point freezes.
I cannot acces the phone with adb oder fastboot from host machine..
=> Does anybody knows if there is a possibility to gain acces to recovery?
Click to expand...
Click to collapse
Hi, How did you manage to unlock bootloader?

Question How to install custom recovery TWRP?

I searched a lot of articles all flashed to the recovery partition
Code:
>fastboot flash recovery boot_twrp_UNOFFICIAL.img
Sending 'recovery' (65536 KB) OKAY [ 2.062s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I found some information that Android 11 uses Virtual A/B
Do I need to modify boot.img to install custom recovery in Android 11?

AceSheep said:
I searched a lot of articles all flashed to the recovery partition
Code:
>fastboot flash recovery boot_twrp_UNOFFICIAL.img
Sending 'recovery' (65536 KB) OKAY [ 2.062s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I found some information that Android 11 uses Virtual A/B
Do I need to modify boot.img to install custom recovery in Android 11?
Click to expand...
Click to collapse
fastboot boot twrp.img
Go ti advanced and install current twrp

Otherwise u can installiert it temporarly on boot, fastboot flash Boot twrp.IMG
Now you can Boot into it using hardwarebuttons....Herr u can flash it finaly
Did u find a working twrp....this one here doesnt work....also otg mouse not working in that one

bambamGN2 said:
Otherwise u can installiert it temporarly on boot, fastboot flash Boot twrp.IMG
Now you can Boot into it using hardwarebuttons....Herr u can flash it finaly
Did u find a working twrp....this one here doesnt work....also otg mouse not working in that one
Click to expand...
Click to collapse
I use a type-c hub to connect a wireless mouse and it works

I used this command and it didn’t work normally, it will enter the system normally after restart
Code:
>fastboot boot images\boot_twrp_UNOFFICIAL.img
Sending 'boot.img' (65536 KB) OKAY [ 1.735s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
This command can start to TWRP but cannot install it
Code:
>fastboot flash boot_b images\boot_twrp_UNOFFICIAL.img
>fastboot set_active b
>fastboot reboot
Do I still need to unpack boot.img and copy the ramdisk file

AceSheep said:
I used this command and it didn’t work normally, it will enter the system normally after restart
Code:
>fastboot boot images\boot_twrp_UNOFFICIAL.img
Sending 'boot.img' (65536 KB) OKAY [ 1.735s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
This command can start to TWRP but cannot install it
Code:
>fastboot flash boot_b images\boot_twrp_UNOFFICIAL.img
>fastboot set_active b
>fastboot reboot
Do I still need to unpack boot.img and copy the ramdisk file
Click to expand...
Click to collapse
fastboot boot twrp_UNOFFICIAL.img
This work for sure

This topic is great, but I'm afraid many of us would totally miss the information in here, do anyone has the will to turn the information here into a little "how to TWRP" guide as a topic here? That would be awesome!

My device is Redmi Note 10 5G China and the EEA rom flashed. Using twrp will get stuck in the logo and cannot enter.
Before that, I can start twrp using China rom. I'm still looking for reasons
----------
P.S. Does anyone know how to compile twrp for Android 11? I need a little help

AceSheep said:
----------
P.S. Does anyone know how to compile twrp for Android 11? I need a little help
Click to expand...
Click to collapse
No but maybe this helps????
Make A TWRP Tree For Your Device & Build.md
GitHub Gist: instantly share code, notes, and snippets.
gist.github.com

i suggest for now stay on stock recovery. you can root phone installing magisk via fastboot. and the only way to try custom rom is flashing the gsi ported generic rom. the nippon gsi telefram group have a lot of gsi. but my advice is wait miu13 update. most of gsi have audio incompatibility. but if you like aosp roms this is the only way. mtk full custom roms for our device dont exist

How do I get a recovery on my Redmi 9 (lancelot)?

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.