Database Users

[Q] Recovering... recovery, after Lollipop official image installation

Hello everyone!
I used to have TWRP 2.8 and a custom rom installed on my Nexus 4. After the official Lollipop image came out, I installed it and everything works fine, except the fact that there seems to be no recovery at all. When I try to enter recovery and the phone reboots, I get the green-robot-error image. While installing the Lollipop image, I read the messages and it said that boot.sig and recovery.sig were not found. I tried installing TWRP over again, but nothing changed. Everything else works fine on the phone, fastboot, Lollipop, I even rooted with no problems. How do I properly reinstall TWRP on my device, without getting the green robot of death icon?

I have same problem, the OS reinstall default recovery every reboot, if you install TWRP via fastboot mode and directly reboot into TWRP recovery mode is there and it works, but after reboot to systen it's gone.
How have rooted Lollipop? SuperSU I install from TWRP and tells me that binary super are missing.
Here is the solution, but I dont have su
http://forum.xda-developers.com/nexus-4/help/guide-ultimate-nexus-4-root-guide-t2018179

common issue at this point. It appears recovery isnt sticking for some reason.

kokotron said:
Hello everyone!
I used to have TWRP 2.8 and a custom rom installed on my Nexus 4. After the official Lollipop image came out, I installed it and everything works fine, except the fact that there seems to be no recovery at all. When I try to enter recovery and the phone reboots, I get the green-robot-error image. While installing the Lollipop image, I read the messages and it said that boot.sig and recovery.sig were not found. I tried installing TWRP over again, but nothing changed. Everything else works fine on the phone, fastboot, Lollipop, I even rooted with no problems. How do I properly reinstall TWRP on my device, without getting the green robot of death icon?
Click to expand...
Click to collapse
I advise you to read more in future to keep yourself away from such troubles.
Installing a Factory Image sends your device back to completely stock, this includes all the partitions, i.e System, Data, Cache, Recovery. Just think of it resembling the newly bought device. The Red icon means you now have the stock recovery installed. You now need to Install the custom recovery (TWRP) again.
Download TWRP Recovery Image: Click here
Power Off Nexus 4
Boot into Bootloader/Fastboot mode. Press VolDown + Power buttons altogether to reboot into bootloader mode.
Connect the device to the PC via USB data cable
Open a new CMD window
"cd" the command line window to the location of the downloaded image and enter the following command thereafter:
Code:
fastboot flash recovery openrecovery-twrp-2.8.1.0-mako.img
And you'll be able to boot into recovery mode.

sidVici0us said:
I have same problem, the OS reinstall default recovery every reboot, if you install TWRP via fastboot mode and directly reboot into TWRP recovery mode is there and it works, but after reboot to systen it's gone.
How have rooted Lollipop? SuperSU I install from TWRP and tells me that binary super are missing.
Click to expand...
Click to collapse
For rooting, I used the file and the guide in the following thread, it doesn't require recovery, just fastboot mode.
http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274

kokotron said:
For rooting, I used the file and the guide in the following thread, it doesn't require recovery, just fastboot mode.
http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-4/help/guide-ultimate-nexus-4-root-guide-t2018179
A solution for auto swpan defualt recovery, the file is there only rename it

DJBhardwaj said:
I advise you to read more in future to keep yourself away from such troubles.
Installing a Factory Image sends your device back to completely stock, this includes all the partitions, i.e System, Data, Cache, Recovery. Just think of it resembling the newly bought device. The Red icon means you now have the stock recovery installed. You now need to Install the custom recovery (TWRP) again.
Download TWRP Recovery Image: Click here
Power Off Nexus 4
Boot into Bootloader/Fastboot mode. Press VolDown + Power buttons altogether to reboot into bootloader mode.
Connect the device to the PC via USB data cable
Open a new CMD window
"cd" the command line window to the location of the downloaded image and enter the following command thereafter:
Code:
fastboot flash recovery openrecovery-twrp-2.8.1.0-mako.img
And you'll be able to boot into recovery mode.
Click to expand...
Click to collapse
As I mentioned in my post, I did try to reinstall TWRP. I did it exactly the way you are describing. Still no recovery. The robot icon I'm describing is a common image when something's wrong on an android device and has nothing to do with stock recovery. Thanks a lot for taking the time to post all these info, though!

sidVici0us said:
I have same problem, the OS reinstall default recovery every reboot, if you install TWRP via fastboot mode and directly reboot into TWRP recovery mode is there and it works, but after reboot to systen it's gone.
How have rooted Lollipop? SuperSU I install from TWRP and tells me that binary super are missing.
Here is the solution, but I dont have su
http://forum.xda-developers.com/nexus-4/help/guide-ultimate-nexus-4-root-guide-t2018179
Click to expand...
Click to collapse
Just Install a Custom Kernel with modified ramdisk. Install Hellscore kernel and then install SuperSU. You will be able to experience Root.
I think unleashed kernel has also been updated with the same, but I can only confirm it with Hellscore.

It's the new bootloader. Flash an older bootloader version, reboot the bootloader, then flash TWRP again and it will stick.

kokotron said:
As I mentioned in my post, I did try to reinstall TWRP. I did it exactly the way you are describing. Still no recovery. The robot icon I'm describing is a common image when something's wrong on an android device and has nothing to do with stock recovery. Thanks a lot for taking the time to post all these info, though!
Click to expand...
Click to collapse
It is weird. I am pretty much sure you're either missing something or using a corrupted img file. Confirm that the file has been downloaded completely by verifying the md5 checksum and I am sure it will mismatch

hp420 said:
It's the new bootloader. Flash an older bootloader version, reboot the bootloader, then flash TWRP again and it will stick.
Click to expand...
Click to collapse
In that case, could it mean that TWRP could probably release an update based on the new bootloader that would solve the issue?

kokotron said:
In that case, could it mean that TWRP could probably release an update based on the new bootloader that would solve the issue?
Click to expand...
Click to collapse
It is not the bootloader, I already achieved that TWRP left there and not deleted, these are the steps to Reproduce.
Download the latest TWRP 2.8.1
restart in bootloader mode
fastboot flash recovery twrp-recover.zip
After the fast boot menu select to boot into recovery and went to boot the TWRP.
Go to Mount ands mount system partition
The go to TWRP file manager and rename the file /system/etc/install-recovery.sh /system/etc/install-recovery.bak
And ready the recovery.
To root I used http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Work fine in L.

sidVici0us said:
It is not the bootloader, I already achieved that TWRP left there and not deleted, these are the steps to Reproduce.
Download the latest TWRP 2.8.1
restart in bootloader mode
fastboot flash recovery twrp-recover.zip
After the fast boot menu select to boot into recovery and went to boot the TWRP.
Go to Mount ands mount system partition
The go to TWRP file manager and rename the file /system/etc/install-recovery.sh /system/etc/install-recovery.bak
And ready the recovery.
To root I used http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Work fine in L.
Click to expand...
Click to collapse
It is the bootloader. I had the exact same thing happen to me. The only thing I did was flash the last bootloader released before lollipop (30d, i think?) and reflashed twrp, and it stuck. I tried several times reflashing before I rolled back to the legacy bootloader and every time I rebooted the stock recovery was reinstalled. Now you tell me, if the only thing I changed was the bootloader, then reflashed twrp and it worked, how is it not the new bootloader?

sidVici0us said:
It is not the bootloader, I already achieved that TWRP left there and not deleted, these are the steps to Reproduce.
Download the latest TWRP 2.8.1
restart in bootloader mode
fastboot flash recovery twrp-recover.zip
After the fast boot menu select to boot into recovery and went to boot the TWRP.
Go to Mount ands mount system partition
The go to TWRP file manager and rename the file /system/etc/install-recovery.sh /system/etc/install-recovery.bak
And ready the recovery.
To root I used http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Work fine in L.
Click to expand...
Click to collapse
Ok thank you, this seems to have worked. When I booted back into Android though root didn't work any more. I re-rooted using your link (which was what I used the first time as well), and I guess I'll know how it goes the next time I reboot the phone.

hp420 said:
It is the bootloader. I had the exact same thing happen to me. The only thing I did was flash the last bootloader released before lollipop (30d, i think?) and reflashed twrp, and it stuck. I tried several times reflashing before I rolled back to the legacy bootloader and every time I rebooted the stock recovery was reinstalled. Now you tell me, if the only thing I changed was the bootloader, then reflashed twrp and it worked, how is it not the new bootloader?
Click to expand...
Click to collapse
Not the boot loader because I have the new bootloader that came with L and TWRP working perfectly, so both can coexist.
The problem comes from within the rom as I said, the file is in /system/etc/install-recovery.sh is responsible to clear the custom recovery and return to default android recovery. The solution is to remove (or rename) that file, what I saw is that the TWRP and SuperSU (both try to) can not rename it, and the solution was to rename it manually from the file manager included in the TWRP (mounting /system as explained before).
The same problem to can not overwrite files (should be modified in any command in library ) prevents install from a flashable zip SuperSU, so the solution http://forum.xda-developers.com/nexu...- root-t2025274 initiating its own operating system booting own image solves the problem that can not be overwritten (or modified) files from the TWRP (at least until a specified version for L see the light).
Probably whoever the new bootloader prevents TWRP modify files in /system, but bootloader not erases the custom recovery. Surely people of TWRP is working to fix this issue (or sleeping sometimes you have to sleep) but the problem can be solved by keeping the new booloader.
Conclucion, I have stock L Last bootloader, root and TWRP everything working perfectly and hellsCore Kernel

sidVici0us said:
Download the latest TWRP 2.8.1
restart in bootloader mode
fastboot flash recovery twrp-recover.zip
After the fast boot menu select to boot into recovery and went to boot the TWRP.
Go to Mount ands mount system partition
The go to TWRP file manager and rename the file /system/etc/install-recovery.sh /system/etc/install-recovery.bak
And ready the recovery.
To root I used http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Work fine in L.
Click to expand...
Click to collapse
I did exactly what you just wrote and It worked partially. My TWRP now sticks but I am not able to install supersu. I did install supersu and it was successful but the issue is that when i use root checker it still shows my phone is not rooted and also when i open supersu app it says "supersu binaries are not installed....". Any suggestion?

you installed via the SuperSU binaries from flashable zip in TWRP or use the method http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274 ?
With the CF-auto-root you should have no problems, I did so and I read that many people do so, use this method to root.
On the other hand, I was thinking that having a recovery that can not flash zip is not something useful
---------- Post added at 03:16 PM ---------- Previous post was at 02:52 PM ----------
samvid1992 said:
I did exactly what you just wrote and It worked partially. My TWRP now sticks but I am not able to install supersu. I did install supersu and it was successful but the issue is that when i use root checker it still shows my phone is not rooted and also when i open supersu app it says "supersu binaries are not installed....". Any suggestion?
Click to expand...
Click to collapse
You can not use the superSU flasheable zip, the recovery is not working to modify /system partition, use the other method.

samvid1992 said:
I did exactly what you just wrote and It worked partially. My TWRP now sticks but I am not able to install supersu. I did install supersu and it was successful but the issue is that when i use root checker it still shows my phone is not rooted and also when i open supersu app it says "supersu binaries are not installed....". Any suggestion?
Click to expand...
Click to collapse
CF autoroot works perfectly!! http://www.xda-developers.com/android/chainfire-releases-cf-auto-roots-for-nexus-line/

TWRP Stuck after upgrade to Nougat

Hello everyone,
i just flashed the newest Pure Nexus Rom and everything went fine.
I forgot to flash the SuperSU Zip so i tried to got back into TWRP, but now it stuck.
The System boots normally, only TWRP wont boot.
Anyone had that problem too?

if anyone else has the same issue, here is the answer:
I forgot to erase the userdata or cache.
If you have the same problem use fastboot!
fastboot format cache
fastboot format userdata
Then it should work again.
(Everything on your own risk)

If you dont flah SuperSU asap, TWRP will not stick on reboot (w nougat). That was the issue.

No SuperSU was not the problem.
It happened before i flashed the SuperSU zip.
As far as i know, there is a problem if you upgrade to Nougat and dont format the userdata and cache because of the encryption or sth like that.

kaufikauf said:
No SuperSU was not the problem.
It happened before i flashed the SuperSU zip.
As far as i know, there is a problem if you upgrade to Nougat and dont format the userdata and cache because of the encryption or sth like that.
Click to expand...
Click to collapse
Exactly. It happened before you flashed SuperSU zip. Not flashing SuperSU caused your problem. It needs to be flashed the first time you go into TWRP or you won't be able to boot back into TWRP. The previous poster is correct.

Maybe we talk about different problems
Ive formatted cache and userdata yesterday,
now i can go back into twrp.
(SuperSU is not flashed now).
Just tried it, works perfectly!

kaufikauf said:
No SuperSU was not the problem.
It happened before i flashed the SuperSU zip.
As far as i know, there is a problem if you upgrade to Nougat and dont format the userdata and cache because of the encryption or sth like that.
Click to expand...
Click to collapse
I never, ever flash userdata, and never had an issue.
We can agree to disagree. Either the other poster and I arent understanding your question, or you arent understanding our reply. It's cool, it happens.
But TWRP not sticking is due to not running SuperSU at the end of the install process. It wont stick.

And now i know the misunderstanding!
My sentence was a little bit silly formulated:
It didnt stuck by flashing SuperSU. I just forgot to do that and when i recognized this, i want to boot into recovery. Then i recognized the bootloop.
So SuperSU as itself was not involved. By the way BeansTown wrote in the Thread for PureNexus Rom that you have to format your userdata (normally over TWRP).
Shame on me that i didnt read before start flashing

kaufikauf said:
And now i know the misunderstanding!
My sentence was a little bit silly formulated:
It didnt stuck by flashing SuperSU. I just forgot to do that and when i recognized this, i want to boot into recovery. Then i recognized the bootloop.
So SuperSU as itself was not involved. By the way BeansTown wrote in the Thread for PureNexus Rom that you have to format your userdata (normally over TWRP).
Shame on me that i didnt read before start flashing
Click to expand...
Click to collapse
You should take a look at this post in the official TWRP thread for a clearer reason why.

SlimSnoopOS said:
You should take a look at this post in the official TWRP thread for a clearer reason why.
Click to expand...
Click to collapse
So I followed the guide and updated to 7.1.1 and did the normal "fastboot flash recovery xxx" then "fastboot reboot bootlader" then rebooted it via phone I go to "Recovery" from my phone and I get a screen saying "No Command" I tried to flash twrp-3.0.3-0-angler.img
Did I miss something?

USFguy said:
So I followed the guide and updated to 7.1.1 and did the normal "fastboot flash recovery xxx" then "fastboot reboot bootlader" then rebooted it via phone I go to "Recovery" from my phone and I get a screen saying "No Command" I tried to flash twrp-3.0.3-0-angler.img
Did I miss something?
Click to expand...
Click to collapse
After flashing TWRP from the bootloader, go directly into recovery and flash SuperSU 2.78 or newer to make it stick permanently.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
After flashing TWRP from the bootloader, go directly into recovery and flash SuperSU 2.78 or newer to make it stick permanently.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
It won't boot into recovery, I flash recovery, unplug device hit recovery boot and it boot loops once then boots normally....

USFguy said:
It won't boot into recovery, I flash recovery, unplug device hit recovery boot and it boot loops once then boots normally....
Click to expand...
Click to collapse
Hmm. If you are on stock, reflash the boot, system, recovery, and vendor from the factory image that matches your stock, security update. Restart the phone and boot into Android. Restart into the bootloader then fastboot flash recovery TWRP-angler.img. See if it lets you boot into TWRP then. If not, try an older version of TWRP and see if that will flash and allow you to boot into it.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Hmm. If you are on stock, reflash the boot, system, recovery, and vendor from the factory image that matches your stock, security update. Restart the phone and boot into Android. Restart into the bootloader then fastboot flash recovery TWRP-angler.img. See if it lets you boot into TWRP then. If not, try an older version of TWRP and see if that will flash and allow you to boot into it.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Tried that, ended up going down an update in TWRP and it worked, weird....

I had a similar issue and I had to go back in and reflash Recovery image to recovery partition and all was well

TWRP Not working

Hi, I have a essential phone running Oreo 8.1, just recently I have rooted the phone with magisk v16 an twrp 3.2.1, I successfully flashed it with twrp but after the flash whenever I want to get into twrp it just freezes up on the mount data screen and I have to force reboot it, does anyone know a solution to this problem

Make sure you're following the exact steps from this post. Every step is crucial (except #3, because you have to disable your screen lock before booting twrp.
You shouldn't have to manually mount anything in TWRP either. The magisk installer might give you an error about mounting system but it doesn't seem to make any difference.

[QRCODE][/QRCODE]
yellk20 said:
Hi, I have a essential phone running Oreo 8.1, just recently I have rooted the phone with magisk v16 an twrp 3.2.1, I successfully flashed it with twrp but after the flash whenever I want to get into twrp it just freezes up on the mount data screen and I have to force reboot it, does anyone know a solution to this problem
Click to expand...
Click to collapse
You cannot have TWRP installed with 8.x.
TWRP is not compatible.
You must flash the original boot image, then install magisk.
TWRP cannot remain.
You will boot loop.
Please read the instructions on rooting carefully.

Ok thank you

Why can't TWRP replace recovery instead of boot?

RawSlugs said:
Why can't TWRP replace recovery instead of boot?
Click to expand...
Click to collapse
No one has created a bit image with TWRP as the recovery.
Sent from my PH-1 using XDA Labs

RawSlugs said:
Why can't TWRP replace recovery instead of boot?
Click to expand...
Click to collapse
Because the partition layout of the Essential does not have a recovery partition.
Recovery is contained in the boot image.
So to have TWRP resident/permanent, the boot image must be patched.
It has been done for 7.x, but sense 8.x is still beta, there is no official TWRP for Oreo.
Once Oreo is final, I expect we will get a TWRP that works.
The current limitation, means you can't flash without a computer handy.

please help. tried to flash OTA and now i cant get back to OS

hey guys, so i used twrp to flash a OTA then flashed twrp again and rebooted and when i went to flash magisk i was just shown a list of all random numbers/letters. i booted into bootloader flashed twrp img, booted into recovery and all my files were there once again but i still cant get into the OS, can anyone please help?
why is flashing so complicated these days? even the recovery works different. the last time i rooted (4 years ago maybe) you could use twrp to make a backup and it was done simple as that (i did this on the oneplus 6t about 4 weeks ago and got the issue with my storage just being a list of numbers and letters and had to find a way to fully wipe and re install OOS) and the same for flashing, i could just flash something and it was fine, no issues.

Do you have an OTG adapter and pendrive? You can copy the full OTA zip, TWRP zip and Magisk zip on to that and flash from TWRP using that. Your internal storage is encrypted and you won't be able to access it until you can reboot OOS fully. If that didn't work, you may have to do a factory reset/wipe (including internal data) to get the phone to boot again. You will obviously lose any unbacked data.

Which version of TWRP are you using? Which version of OOS are you using? Most likely you just don't have the correct version, and you updated to the latest version OOS with the new security patch and it no longer can decrypt it.
Have you tried TWRP 3.3.1-7 from here? If you boot the .img file from fastboot, can you decrypt your data?
Most likely you just need to flash Magisk, and you will be fine. For updates, it's always as you did, flash the full OTA update, TWRP installer, reboot to recovery, Magisk. It is recommended to uninstall Magisk, however I usually don't do that personally. Official Instructions here. You just have to make sure you are using the correct version of TWRP, otherwise you can run into encryption issues, as you found out when there are updates.

OhioYJ said:
Which version of TWRP are you using? Which version of OOS are you using? Most likely you just don't have the correct version, and you updated to the latest version OOS with the new security patch and it no longer can decrypt it.
Have you tried TWRP 3.3.1-7 from here? If you boot the .img file from fastboot, can you decrypt your data?
Most likely you just need to flash Magisk, and you will be fine. For updates, it's always as you did, flash the full OTA update, TWRP installer, reboot to recovery, Magisk. It is recommended to uninstall Magisk, however I usually don't do that personally. Official Instructions here. You just have to make sure you are using the correct version of TWRP, otherwise you can run into encryption issues, as you found out when there are updates.
Click to expand...
Click to collapse
Latest twrp and latest full OOS OTA. If I fastboot the twrp. Img I can see all my data again. I've fixed it now, I flashed the twrp. Img in fastboot then rebooted system and it worked

After update to V11.0.4.0.QFJEUXM TWRP no longer available

Hi Guys,
yesterday the new update came out, great.
I of course immediately pulled the zip (source) and installed it with TWRP (source).
So far no problems.
After a while I realized that I no longer had root because the apps stopped working.
When I wanted to boot into the TWRP to reinstall Magisk, I unfortunately found that it was no longer available, but only stock recovery.
Well, I thought to myself and tried to reinstall TWRP (method-twrp-3.3.1-2-davinci-fix), which was fatal, because my cell phone only booted into the Fastboot.
Then I got my cell phone, set up again with the Fastboot method.
Now I'm back to 11.0.4.0 but unfortunately without TWRP and root.
Can someone please describe how I can get TWRP and root again on Android 10?
I am thankful for every help !!!

Same thing happening to me, no matter what I do, stock recovery keeps overwriting TWRP

Oh dear, that doesn't sound good.
I hope there will be a solution to the problem soon.
I don't want to do without TWRP and root.
I wanted to try it according to these instructions "https://miui.blog/redmi-k20/twrp-mi-9t-redmi-k20-vbmeta-mauronofrio/". But don't trust me, I'm afraid that it won't work and I can start all over again.

Flash official TWRP this morning with fastboot commands without problem.
1. reboot in fastboot mode
2. Flash recovery with this command "fastboot flash recovery yourrecovery.img"
3. Reboot in recovery with this command "fastboot boot yourrecovery.img"
Any problems here.

The fact that twrp is lost when flashing official rom (even thought twrp itself) is normal. You just have to reboot into bootloader and flash twrp again and it will be back.
Your problem here is that you are using an old and unofficial twrp build, that has problems on newer roms. Flash official twrp and you'll be fine

houbaba said:
Flash official TWRP this morning with fastboot commands without problem.
1. reboot in fastboot mode
2. Flash recovery with this command "fastboot flash recovery yourrecovery.img"
3. Reboot in recovery with this command "fastboot boot yourrecovery.img"
Any problems here.
Click to expand...
Click to collapse
Can u share the twrp file, im unnable to flash the one i have without causing a bootloop

hounter17 said:
Can u share the twrp file, im unnable to flash the one i have without causing a bootloop
Click to expand...
Click to collapse
Download from the official twrp site here: https://twrp.me/xiaomi/xiaomimi9t.html

RedNas74 said:
Download from the official twrp site here: https://twrp.me/xiaomi/xiaomimi9t.html
Click to expand...
Click to collapse
Oh sorry it works? I read somewhere that the original causes also bootloops :good:

Found something on a Russian website.
Обновление TWRP Recovery от LR.Team для устройств на Android 10
Does anyone dare to test this?
Here is the link to the TWRP for our Mi9t
> TWRP-3.3.1-1109-DX (полный комплект для установки) <
Check it out...

I finally got it
I did the following.
"V11.0.4.0.QFJEUXM" flashed in the TWRP and booted into the system, TWRP will be overwritten.
Now flashed TWRP "twrp-3.3.1-0-davinci.img" in Fastboot and booted into Recovery (TWRP).
To be on the safe side, I had the cell phone booted again into the TWRP in the TWRP.
Then I flashed Magisk "Magisk-v20.3.zip".
Booted cell phone into the system and everything works.

frank808 said:
I finally got it
I did the following.
"V11.0.4.0.QFJEUXM" flashed in the TWRP and booted into the system, TWRP will be overwritten.
Now flashed TWRP "twrp-3.3.1-0-davinci.img" in Fastboot and booted into Recovery (TWRP).
To be on the safe side, I had the cell phone booted again into the TWRP in the TWRP.
Then I flashed Magisk "Magisk-v20.3.zip".
Booted cell phone into the system and everything works.
Click to expand...
Click to collapse
Where did you get the twrp file from?

You can use OrangeFox Recovery if you want a TWRP that can survive after flashing MIUI ROMs or updates :
https://forum.xda-developers.com/mi-9t/development/official-orangefox-recovery-project-t4037899

RedNas74 said:
Download from the official twrp site here: https://twrp.me/xiaomi/xiaomimi9t.html
Click to expand...
Click to collapse
Ok, I am on global 11.0.4.0 (QFJMIXM) and I used this latest twrp-3.3.1-0-davinci.img and I can confirm its working without bootloop.

ShiningScias said:
You can use OrangeFox Recovery if you want a TWRP that can survive after flashing MIUI ROMs or updates :
https://forum.xda-developers.com/mi-9t/development/official-orangefox-recovery-project-t4037899
Click to expand...
Click to collapse
To install TWRP, is it neccesary to wipe Data (or something else)?
And if Data must be wiped, does it mean that Data will no more be encrypted as originally by MIUI?
I have 11.0.4.0, rooted by Magisk (Magisk installed simply by patching and flashing boot.img, did not need TWRP for, did not wipe Data, etc) and I possibly want to have TWRP but don't want to loose encryption of Data, Widewine L1 and so

zgfg said:
To install TWRP, is it neccesary to wipe Data (or something else)?
And if Data must be wiped, does it mean that Data will no more be encrypted as originally by MIUI?
I have 11.0.4.0, rooted by Magisk (Magisk installed simply by patching and flashing boot.img, did not need TWRP for, did not wipe Data, etc) and I possibly want to have TWRP but don't want to loose encryption of Data, Widewine L1 and so
Click to expand...
Click to collapse
You don't need to wipe anything to install a custom Recovery (like TWRP).
TWRP can handle ROM encryption, you just need to install a correct TWRP, and version, for your current MIUI / Android version.
A custom Recovery doesn't change Widevine level.
And TWRP is useful in case of bootloop (because of an installed Magisk module, by example) or if you want to easily reinstall Magisk after ROM update.

RedNas74 said:
Download from the official twrp site here: https://twrp.me/xiaomi/xiaomimi9t.html
Click to expand...
Click to collapse
Micdu70 said:
You don't need to wipe anything to install a custom Recovery (like TWRP).
TWRP can handle ROM encryption, you just need to install a correct TWRP, and version, for your current MIUI / Android version.
Click to expand...
Click to collapse
Ok thanks, so starting from v11.0.4.0 QFJEUXM, rooted by Magisk (did not wipe Data or so, just patched and flashed boot img), is it ok just to flash (from Fastboot) twrp-3.3.1-0-davinci.img, downloaded from the official site https://twrp.me/davinci/twrp-3.3.1-0-davinci.img
Maybe I could test first by
fastboot boot twrp-3.3.1-0-davinci.img

zgfg said:
Ok thanks, so starting from v11.0.4.0 QFJEUXM, rooted by Magisk (did not wipe Data or so, just patched and flashed boot img), is it ok just to flash (from Fastboot) twrp-3.3.1-0-davinci.img, downloaded from the official site https://twrp.me/davinci/twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
Yes, it should work.
But I prefer OrangeFox Recovery.

zgfg said:
so starting from v11.0.4.0 QFJEUXM, rooted by Magisk (did not wipe Data or so, just patched and flashed boot img), is it ok just to flash (from Fastboot) twrp-3.3.1-0-davinci.img, downloaded from the official site https://twrp.me/davinci/twrp-3.3.1-0-davinci.img
Maybe I could test first by
fastboot boot twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
Micdu70 said:
Yes, it should work.
But I prefer OrangeFox Recovery.
Click to expand...
Click to collapse
Something is fishy. IMO, if that official TWRP is really ok for 11.0.4.0, then it should correctly boot by:
fastboot boot twrp-3.3.1-0-davinci.img
But phone rebooted into the dark.
TG, I didn't really flash with, so by long pressing Pow it rebooted to system.
Tried again, no avail
Edit:
Tried the same fastboot boot with
twrp-3.3.1-12-davinci-mauronofrio.img and also OrangeFox-R10.1_1-Stable-davinci.img (obtained by unzipping OrangeFox), but it also reboots to dark and I have to long press Pow to reboot to system

frank808 said:
Hi Guys,
yesterday the new update came out, great.
I of course immediately pulled the zip (source) and installed it with TWRP (source).
So far no problems.
After a while I realized that I no longer had root because the apps stopped working.
When I wanted to boot into the TWRP to reinstall Magisk, I unfortunately found that it was no longer available, but only stock recovery.
Well, I thought to myself and tried to reinstall TWRP (method-twrp-3.3.1-2-davinci-fix), which was fatal, because my cell phone only booted into the Fastboot.
Then I got my cell phone, set up again with the Fastboot method.
Now I'm back to 11.0.4.0 but unfortunately without TWRP and root.
Can someone please describe how I can get TWRP and root again on Android 10?
I am thankful for every help !!!
Click to expand...
Click to collapse
You can install twrp by All In One tool
You can find its thread here itself

I took the official TWRP. " Link "
Flashed in fastboat and then booted the phone with a key combination in TWRP.
With the Fastboot command it didn't work for me either, the cell phone remained black ...