Related
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/
I installed the twrp 3.0.2.2 and after installed a kernel which made the phone stuck on zte logo.
I tried to flash to the stock files using this guide:
https://forum.xda-developers.com/axon-7/how-to/a2017g-nougat-b08-twrp-bootstack-t3696479v
but when i try to install the superSu the twrp stuck after extracing files, then the phone just shuts down.
what can I do?
Shakedbuk said:
I installed the twrp 3.0.2.2 and after installed a kernel which made the phone stuck on zte logo.
I tried to flash to the stock files using this guide:
https://forum.xda-developers.com/axon-7/how-to/a2017g-nougat-b08-twrp-bootstack-t3696479v
but when i try to install the superSu the twrp stuck after extracing files, then the phone just shuts down.
what can I do?
Click to expand...
Click to collapse
Update your twrp, there's no need to use that old version... my phone reboots when it wants when it has opd twrp versions
Download twrp 3.1.1-0
Put it on your phone, maybe via adb or through mtp if you have it
Go to Install -> hit the button on the right that says 'Install image'
Find the TWRP.img and install it, it will prompt you where to install it, put 'recovery'
Followed you instructions, but now i cant get into TWRP or the OS ):
Tried to flash it with axon7tool on pc, but got the same result, but when I tried to flash the 3.0.2. again, it worked.
Shakedbuk said:
Followed you instructions, but now i cant get into TWRP or the OS ):
Tried to flash it with axon7tool on pc, but got the same result, but when I tried to flash the 3.0.2. again, it worked.
Click to expand...
Click to collapse
Don't use axon7tool for this... you already have TWRP, the only thing you have to use axon7tool for is to install twrp when you have the stock recovery. after you have twrp on the phone just try not to use the PC except for maybe miflash
I tried both of this options.
Flashing new version of twrp through the old twrp resulted in black screen when i try to get to recovery.
So I flashed the old twrp from the pc, tried to flash the new one using the same method but it the same as i flashed it through the old twrp. (which mean that when i get to the recovery i get black screen)
ATM the situation is the same, system wont boot stuck on zte logo, twrp is 3.0.2.2 (there is another method to flash newer twrp?)
There is another option?
After wiping system in twrp i was able to install supersu, which means i completed this guide
https://forum.xda-developers.com/axon-7/how-to/a2017g-nougat-b08-twrp-bootstack-t3696479v
but still stuck on zte logo after i reboot , any help?
Shakedbuk said:
After wiping system in twrp i was able to install supersu, which means i completed this guide
https://forum.xda-developers.com/axon-7/how-to/a2017g-nougat-b08-twrp-bootstack-t3696479v
but still stuck on zte logo after i reboot , any help?
Click to expand...
Click to collapse
Wait, what did you do? Did you install everything again after wiping system?
Ya, afte i wiped the system it allowed me to install the supersu without interrupts, but it did not helped.
Anyway i manged to install purefusion os, system booted up, after that the new twrp updated successfully.
Shakedbuk said:
Ya, afte i wiped the system it allowed me to install the supersu without interrupts, but it did not helped.
Anyway i manged to install purefusion os, system booted up, after that the new twrp updated successfully.
Click to expand...
Click to collapse
You installed SuperSU without a system, and the phone did not boot up? Amirite?
what i did was wipe system dalvik cache, cache, after that install bootstack and the system files, and after that the supersu.
before i wiped the system, when i tried to install the supersu the twrp collapsed, after that it installed it but did not helped to make the system boot.
After I got my axon 7 it was on android 6 mm. I unlocked the bootloader, then installed twrp. With twrp I tried to flash a bootstack and a nougat. It didn't boot so I flashed stock recovery from twrp and installed official nougat update from there. Now when the phone opens there is that screen says "lock bootloader again, wait 5 seconds phone will boot". Everything is fine and phone really boots but when I try to install twrp again it gets stuck on that screen and doesn't boot in 5 seconds.
So right now:
I have unlocked bootloader and stock recovery
And I am looking for a way to install twrp and nougat rom
Thanks in advance :good::good:
ahalak said:
After I got my axon 7 it was on android 6 mm. I unlocked the bootloader, then installed twrp. With twrp I tried to flash a bootstack and a nougat. It didn't boot so I flashed stock recovery from twrp and installed official nougat update from there. Now when the phone opens there is that screen says "lock bootloader again, wait 5 seconds phone will boot". Everything is fine and phone really boots but when I try to install twrp again it gets stuck on that screen and doesn't boot in 5 seconds.
So right now:
I have unlocked bootloader and stock recovery
And I am looking for a way to install twrp and nougat rom
Thanks in advance :good::good:
Click to expand...
Click to collapse
Install TWRP, right after you install it boot to TWRP, format data (check that it formats with ext4) and install Magisk or SuperSU. Your problem may be dm-verity, and magisk or supersu patch the kernel to fix this.
What is weird is that usually if you install TWRP and just boot to system, the system should boot normally, but it should replace TWRP with the stock recovery... This doesn't happen, right?
Choose an username... said:
Install TWRP, right after you install it boot to TWRP, format data (check that it formats with ext4) and install Magisk or SuperSU. Your problem may be dm-verity, and magisk or supersu patch the kernel to fix this.
What is weird is that usually if you install TWRP and just boot to system, the system should boot normally, but it should replace TWRP with the stock recovery... This doesn't happen, right?
Click to expand...
Click to collapse
So much thx. It worked this time.
For your question; twrp was still there after I tried to boot into system.
ahalak said:
So much thx. It worked this time.
For your question; twrp was still there after I tried to boot into system.
Click to expand...
Click to collapse
Because it didn't actually boot, it failed to boot. But it should have booted afaik
Whatever, it works now
Choose an username... said:
Install TWRP, right after you install it boot to TWRP, format data (check that it formats with ext4) and install Magisk or SuperSU. Your problem may be dm-verity, and magisk or supersu patch the kernel to fix this.
What is weird is that usually if you install TWRP and just boot to system, the system should boot normally, but it should replace TWRP with the stock recovery... This doesn't happen, right?
Click to expand...
Click to collapse
Thanks bruh..just got this phone yesterday and just when I think it's all come together this happens..but all resolved thanks to you.:good:
I tried to update to the newest version of OxygenOS but I'm now stuck on boot circle animation and not sure what to do.
I was initially on OOS 4.5.10
Here is what I did to try to update:
1. Downloaded OOS 5.1.3 from Oneplus website and also downloaded Magisk v16
2. Downloaded TWRP twrp-3.2.1-1-cheeseburger.img and then flashed to my phone.
3. Rebooted back into TWRP, then flashed the OOS 5.1.3 .zip file. Immediately after that, I flashed the Magisk .zip.
4. I then rebooted. I'm now stuck at boot.
I am now able to access TWRP. I wanted to try and restore using a Nandroid I made, but all my files appear as gibberish. I'm assuming this is an encryption issue?
What are steps I can take to fix this?
Edit: Figured it out.
Boot using BLU Spark recovery, or any other Oreo compatible recovery. Official twrp seems to have some issues now and then
deleted
deep0d0 said:
Boot using BLU Spark recovery, or any other Oreo compatible recovery. Official twrp seems to have some issues now and then
Click to expand...
Click to collapse
Could you tell me the exact steps to take from where I am now? I don't want to break anything else.
Edit: Figured it out.
elitemeat said:
I tried to update to the newest version of OxygenOS but I'm now stuck on boot circle animation and not sure what to do.
I was initially on OOS 4.5.10
Here is what I did to try to update:
1. Downloaded OOS 5.1.3 from Oneplus website and also downloaded Magisk v16
2. Downloaded TWRP twrp-3.2.1-1-cheeseburger.img and then flashed to my phone.
3. Rebooted back into TWRP, then flashed the OOS 5.1.3 .zip file. Immediately after that, I flashed the Magisk .zip.
4. I then rebooted. I'm now stuck at boot.
I am now able to access TWRP. I wanted to try and restore using a Nandroid I made, but all my files appear as gibberish. I'm assuming this is an encryption issue?
What are steps I can take to fix this?
Edit: Figured it out.
Click to expand...
Click to collapse
1) First download twrp recovery from codeworkx (Make sure you have the latest one)
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
2) Boot to fastboot and flash the recovery.
3) Flash the rom zip file.
4) Flash magisk zip file.
5) Restart your phone.
##Note: If you want to flash the recovery file you can do that using twrp itself or using fastboot but what I've found that some apps (banking apps) don't work after replacing recovery.
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 ...