TWRP recovery does not install correctly - Xiaomi Poco X3 NFC Questions & Answers

I have a problem, when I install twrp on my poco x3, when I restart it in recovery mode, the factory recovery appears and not the twrp.
Any solution?

JeSs Cy said:
I have a problem, when I install twrp on my poco x3, when I restart it in recovery mode, the factory recovery appears and not the twrp.
Any solution?
Click to expand...
Click to collapse
Which recovery are you trying to install and how?

Noter2017 said:
Which recovery are you trying to install and how?
Click to expand...
Click to collapse
ltwrp recovery through ADB,but when I restart the phone after having installed twrp, I get the factory recovery

JeSs Cy said:
ltwrp recovery through ADB,but when I restart the phone after having installed twrp, I get the factory recovery
Click to expand...
Click to collapse
When you restart into TWRP through ADB, install the recovery once again inside TWRP.
Click on install and select TWRP from your phone storage or memory card.
Then it will stick even after a reboot

Noter2017 said:
Cuando reinicie en TWRP a través de ADB, instale la recuperación una vez más dentro de TWRP.
Haga clic en instalar y seleccione TWRP desde el almacenamiento de su teléfono o la tarjeta de memoria.
Entonces se mantendrá incluso después de reinici
Click to expand...
Click to collapse
Noter2017 said:
When you restart into TWRP through ADB, install the recovery once again inside TWRP.
Click on install and select TWRP from your phone storage or memory card.
Then it will stick even after a reboot
Click to expand...
Click to collapse
I appreciate it, I just tried this method and I no longer have the problem, I could not find the solution but when I did what you told me now, the recovery was maintained

Related

Bootloop

HELP!
My phone got stuck at MI logo after i tried to update it to the latest update.
I tried my luck, with wiping cache and cleared the data.
PS: I did root my phone before Updating Mi 4i!
derrick28 said:
HELP!
My phone got stuck at MI logo after i tried to update it to the latest update.
I tried my luck, with wiping cache and cleared the data.
PS: I did root my phone before Updating Mi 4i!
Click to expand...
Click to collapse
Reflash your Rom via fastboot
You tried to update your phone with root, there's your problem. You need to refresh your room with fastboot.
rob rich said:
Reflash your Rom via fastboot
Click to expand...
Click to collapse
The Mi PC suite will download ROM automatically if i connect my phone in fast-boot right?
derrick28 said:
The Mi PC suite will download ROM automatically if i connect my phone in fast-boot right?
Click to expand...
Click to collapse
or u could just download fastboot rom just in case
Cheers~
Always remember, flash the TWRP recovery also for the Mi4i. Just in case something goes wrong like this. Whenever you root your MIUI phone, NEVER update using the OTA. Download the update package from the site and flash manually.

[Guide] How to Avoid Bricking your Device and Fix Boot Issues

There seems to be a lot of confusion concerning how to flash, root, and update these new a/b devices, with a lot of adventurous users bootlooping or even bricking their devices. Thought it might help to provide some basic guidelines some of you might find useful. Not intended to be exhaustively inclusive...
1. Know what you are doing before you do it, not after. Ask before try.
2. Unless you are an expert, do not be first in line to try untested procedures. Have some patience and wait for the definitive guide.
3. Do not flash images from a different model device to yours.
4. Keep your current active slot on the same version of firmware as it is your fall back when things go wrong in the inactive slot. Simply put, flash new firmware to the inactive slot, otherwise you risk bootloops.
5. Only when you have successfully booted an updated firmware, then the inactive slot becomes your current active slot, and the now inactive slot becomes your backup of the previous version.
6. Do not reboot your device out of frustration unless you are sure the active slot has a uncorrupted current system boot image. Otherwise you risk the device not booting into system.
7. Do not relock your bootloader unless you have just flashed a complete stock firmware. Otherwise you risk bricking your device.
8. Do not mod beyond your skills until you have a custom recovery installed, such as TWRP, and an nandroid backup of a working system.
9. Do not update your system or Magisk without a nandroid backup to restore when things inevitably go wrong.
10. Do not flash or OTA update a ROM without first enabling USB Debugging for ADB and Fastboot access, plus creating a TWRP nandroid backup of your working system to restore when it goes wrong. Also, an ADB or Titanium backup of your apps and data, plus phone databases to restore if successful.
How to fix a bootloop or booting directly into recovery:
1. When you are stuck on the boot screen, you can turn off by holding the power button until it shuts down.
2. From phone off, press & hold Power + Volume Down button for a few seconds to boot your phone into bootloader mode.
3. Reflash a current system stock boot image to the active slot and reboot. You can test it first...
fastboot boot stockboot.img
4. If that doesn't work, see if you can go back to your previous system in the inactive slot. In bootloader mode...
fastboot set_active other
and reboot.
5. If all else fails and you do not have a nandroid backup to restore, flash-all stock firmware removing the “-w” from the script to preserve apps, settings, and data.
Helpful Guides:
Android Backup Types...
https://android.stackexchange.com/tags/backup/info/
A/B Seamless Updates & Commands...
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
Magisk Docs...
https://topjohnwu.github.io/Magisk/
Magisk-MagiskHide Install & Troubleshooting Guide...
https://www.didgeridoohan.com/magisk/
Pixel Firmware Images...
https://developers.google.com/android/images
duh1 said:
There seems to be a lot of confusion concerning how to flash, root, and update these new a/b devices, with a lot of adventurous users bootlooping or even bricking their devices. Thought it might help to provide some basic guidelines some of you might find useful. Not intended to be exhaustively inclusive...
1. Know what you are doing before you do it, not after. Ask before try.
2. Unless you are an expert, do not be first in line to try untested procedures. Have some patience and wait for the definitive guide.
3. Do not flash images from a different model device to yours.
4. Keep your current active slot on the same version of firmware as it is your fall back when things go wrong in the inactive slot. Simply put, flash new firmware to the inactive slot, otherwise you risk bootloops.
5. Only when you have successfully booted an updated firmware, then the inactive slot becomes your current active slot, and the now inactive slot becomes your backup of the previous version.
6. Do not reboot your device out of frustration unless you are sure the active slot has a uncorrupted current system boot image. Otherwise you risk the device not booting into system.
7. Do not relock your bootloader unless you have just flashed a complete stock firmware. Otherwise you risk bricking your device.
8. Do not mod beyond your skills until you have a custom recovery installed, such as TWRP, and an nandroid backup of a working system.
9. Do not update your system or Magisk without a nandroid backup to restore when things inevitably go wrong.
10. Do not flash or OTA update a ROM without first enabling USB Debugging for ADB and Fastboot access, plus creating a TWRP nandroid backup of your working system to restore when it goes wrong. Also, an ADB or Titanium backup of your apps and data, plus phone databases to restore if successful.
How to fix a bootloop or booting directly into recovery:
1. When you are stuck on the boot screen, you can turn off by holding the power button until it shuts down.
2. From phone off, press & hold Power + Volume Down button for a few seconds to boot your phone into bootloader mode.
3. Reflash a current system stock boot image to the active slot and reboot. You can test it first...
fastboot boot stockboot.img
4. If that doesn't work, see if you can go back to your previous system in the inactive slot. In bootloader mode...
fastboot set_active other
y reiniciar.
5. Si todo lo demás falla y no tiene una copia de seguridad de nandroid para restaurar, actualice todo el firmware original y elimine la "-w" del script para conservar las aplicaciones, la configuración y los datos.
Guías útiles:
Tipos de copia de seguridad de Android ...
https://android.stackexchange.com/tags/backup/info/
Actualizaciones y comandos A / B perfectos ...
https://www.xda-developers.com/how-ab-partitions-and-seamless-updates-affect-custom-development-on-xda/
Magisk Docs ...
https://topjohnwu.github.io/Magisk/
Guía de instalación y solución de problemas de Magisk-MagiskHide ...
https://www.didgeridoohan.com/magisk/
Imágenes de firmware de píxeles ...
https://developers.google.com/android/images
Click to expand...
Click to collapse
ninguno de tu métodos sirve da error help me please.

twrp replaced by lineageOS recovery

i followed steps to root phone as best i could.
i installed lineageos with twrp.
lineageos is working fine.
but when i boot into recovery i get the lineageos recovery and not the TWRP
(i also don't have Magisk, and actually not sure i need it.. i don't know waht the heck it's for .. but every installation says to install it)
csmooth2001 said:
i followed steps to root phone as best i could.
i installed lineageos with twrp.
lineageos is working fine.
but when i boot into recovery i get the lineageos recovery and not the TWRP
(i also don't have Magisk, and actually not sure i need it.. i don't know waht the heck it's for .. but every installation says to install it)
Click to expand...
Click to collapse
Just boot the twrp img and flash the twrp zip for it to stick, Magisk is for Superuser access and modules etc you can learn more here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Omeu está com o mesmo problema

[Resolved] I'm a noob, and I bricked my phone trying to install LineageOS

Hi, yea, yet another noob who bricked his phone...
I have a ulefone note 7 (Android 8.1 Go original OS), I was trying to follow a tutorial for my phone on getdroidtips (I would post the like but it doesn't let me as I have a new account, but it is easy to find if you google it)
so I installed TWRP and downloaded the correct LineageOS image (one of the GSI ones as my device supports Project Treble) and I flashed it and it booted fine.
I then tried to install Open GApps and TWRP said that there was not enough space.
It turns out that flashing the LineageOS image resized my system partition to the size of the files within it and the data partition expanded to fill the space.
I then used TWRP to try and format the partitions to the right size but as I have no clue what I am doing I just broke it further, now if I try to install LineageOS it seems to work but then boots back to TWRP.
So I believe basically I need a way to set the partition sizes back to what they should be, and then a way to flash LineageOS without it resizing them again.
And no I did not make a TWRP recovery image and yes I realize now that I am dumb.
Any help would be appreciated, thanks in advance.
BTW: I am using windows 10 as host PC, LineageOS 17.1 GSI .img version, and an unofficial TWRP that was made for my device.
EDIT: I have figured out what the problem was and have now made another post concerning the main issue
How did you manage to install twrp? i tried in every way i found nothing worked! here I can even flash the recovery but it does not open in any way
Como você conseguiu instalar o twrp? eu tentei de todas as formas que encontrei nada funcionou! aqui consigo até flashear o recovery mas ele nao abre de nenhuma forma
GatoLouco67 said:
Como você conseguiu instalar o twrp? eu tentei de todas as formas que encontrei nada funcionou! aqui consigo até flashear o recovery mas ele nao abre de nenhuma forma
Click to expand...
Click to collapse
How did you manage to install twrp? i tried in every way i found nothing worked! here I can even flash the recovery but it does not open in any way
Click to expand...
Click to collapse
Please use english in next time (post with native languague and use translator too).
The device must have the bootloader unlocked!!
Install the recovery.img file with fastboot or SPFT.
After installing the file: hold both buttons of the volume+ and the power / then use the volume+ button to select the recovery item / and press the volume- button.
You need to install Magisk otherwise the stock recovery will return when the system is booted.

Question Recovery in TWRP

Hello. I have a problem and no matter what I do, I can't recover in TWRP. I have downloaded the 182MB vTVRP package. After several pitfalls, TWRP finally tells me that the recovery was successful. No red field. However, after rebooting the system, a bootloop appeared and the ROM no loaded. Can anyone advise? Thanks
Benoni1 said:
Hello. I have a problem and no matter what I do, I can't recover in TWRP. I have downloaded the 182MB vTVRP package. After several pitfalls, TWRP finally tells me that the recovery was successful. No red field. However, after rebooting the system, a bootloop appeared and the ROM no loaded. Can anyone advise? Thanks
Click to expand...
Click to collapse
What TWRP?
What rom are you flashing?
TWRP Hello. I have a problem and no matter what I do, I can't recover in TWRP. I have downloaded the 182MB vTVRP package. After several pitfalls, TWRP finally tells me that the recovery was successful. No red field. However, after rebooting the system, a bootloop appeared and the ROM loaded. Can anyone advise? Thanks
TWRP (boot) 3.6.2_12-Mi12_v5.1_A12-cupid-skkk.img 192MB and recovery ROM 13.0.24.0.SLCEUXM
Benoni1 said:
TWRP (boot) 3.6.2_12-Mi12_v5.1_A12-cupid-skkk.img 192MB and recovery ROM 13.0.24.0.SLCEUXM
Click to expand...
Click to collapse
Download this Fastboot rom and use Miflash(Read the instructions carefully).
Package Name: cupid_eea_global_images_V13.0.24.0.SLCEUXM_20220927.0000.00_12.0_eea_ca9a294f46.tgz​
https://xiaomifirmwareupdater.com/miui/cupid/stable/V13.0.24.0.SLCEUXM/
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
NOSS8 said:
Stáhněte si tuto Fastboot rom a použijte Miflash (Přečtěte si pozorně pokyny).
Název balíčku: cupid_eea_global_images_V13.0.24.0.SLCEUXM_20220927.0000.00_12.0_eea_ca9a294f46.tgz​
https://xiaomifirmwareupdater.com/miui/cupid/stable/V13.0.24.0.SLCEUXM/
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Click to expand...
Click to collapse
Thank you

Categories

Resources