Can I update miui with TWRP?
Yes you can, if you never flashed dm verity disabler or magisk, twrp may be replaced by the stock recovery.
darkfrizzy said:
Yes you can, if you never flashed dm verity disabler or magisk, twrp may be replaced by the stock recovery.
Click to expand...
Click to collapse
Ok so I have Magisk installed (no DM Verity disabler though and my device is encrypted) and I assume I need the full image not just the update because that didn't work am I right?
What do you mean by "just the update"? Flash the full image.
Related
Has any of you guys tried the newest TWRP 3.2.0.0 for OnePlus 3T? Did you find a bug?
Thanks.
Info: http://www.androidpolice.com/2017/1...g-better-support-oreo-roms-pixel-2-bug-fixes/
Download TWRPfor OP3T from the official site: https://dl.twrp.me/oneplus3t/
I wonder if it triggers dmverity and how to avoid it if we just want to upgrade twrp...
jojlse said:
I wonder if it triggers dmverity and how to avoid it if we just want to upgrade twrp...
Click to expand...
Click to collapse
I assume you flash the updated Recovery followed by the patched firmware, which i assume you already have? I don't even know if the firmware is necessary but whenever i flash anything i also re-flash the patched firmware while I'm at it. No reason not to.
Alright, DM-Verity will be cleared if you flash the newest Magisk beta, and TWRP 3.2.X.X is working fine. I don't think Teamwin would release an official version of TWRP without making sure it's completely free of bugs. It flashes Oreo ROMs (Cardinal Xtended, N2Os) and also flashed OOS 5.0 very well. Add-ons such as Magisk and Magisk Modules flashed flawlessly.
I triggered dm verity on my Oneplus 3t (8.0 oreo 5.0.0 oxygen OS) while trying to root my device. Is there anyway i can fix this. I installed superSU on my phone thru TWRP but it didnt get rooted. And now an update is available but I it is just rebooting everytime i try to install the official update.
Afaik you have to downgrade to Nougat, disable and enable dm-verity and upgrade again to Oreo.
Don't use SuperSU, Magisk will be better solution.
do u mean u are getting the second screen during boot up about the dm_verity not in enforcing mode?
przemcio510 said:
Afaik you have to downgrade to Nougat, disable and enable dm-verity and upgrade again to Oreo.
Don't use SuperSU, Magisk will be better solution.
Click to expand...
Click to collapse
I cant find the proper files. Can you please link me a thread from which i can follow the step and find the files.
Bradl79 said:
do u mean u are getting the second screen during boot up about the dm_verity not in enforcing mode?
Click to expand...
Click to collapse
Yes
FOLLOW THIS GUIDE TO DISABLE DM-VERITY
READ POST 2 IN OP, I HAVE ALSO DESABLED DM-VERITY FOLOOWING THE GUIDE BELOW:
You will need to reinstall custom ROM+gapps package if you are using custom ROM but if your are using official oxygen OS or oxygenOS based OS like theOne3t, you will not need to reinstall the full ROM at the end of process.
Have a look and carefully proceed. It works..........
https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
usually happens when u install stock OxygenOS without root or no_dmverity, u can install 4.0.2 fw via twrp and go to fastboot and type via cmd
Code:
fastboot oem enable_dm_verity
then u can reflash current fw of what u r on.
malikahmed205 said:
I triggered dm verity on my Oneplus 3t (8.0 oreo 5.0.0 oxygen OS) while trying to root my device. Is there anyway i can fix this. I installed superSU on my phone thru TWRP but it didnt get rooted. And now an update is available but I it is just rebooting everytime i try to install the official update.
Click to expand...
Click to collapse
dm-verity should not (in itself) prevent the update from installing. I have dm-verity tripped (warning screen on boot) and have updated many times (maybe 5-6 updates) with no problems at all. I suspect something else is going on. What version TWRP, and how big is the update file?
When you try to update, how are you doing that, following the notification when the phone is booted to OS? Or are you in TWRP, and try to flash the update?
This happened to me as well when trying to root.
If you are getting warning that dm-verity is not enforcing, then see this thread: https://forum.xda-developers.com/on...e-red-warning-dm-verity-t3727959/post75022331
I also had to use the latest version of Magisk (15.3) for rooting to work properly.
Sent from my OnePlus3T using XDA Labs
I have a problem with SuperSU and magisk. I flash in twrp the root zip and then magisk, after that when I want to update it says this;
! Boot img patched by other programs
! please restore stock boot img
Click to expand...
Click to collapse
I don't have any custom rom, i'm actually oos 5.0.3. I first try to root but dm-verity was triggered and then followed all the steps to disable it.
Any solutions?
Nube420 said:
I have a problem with SuperSU and magisk. I flash in twrp the root zip and then magisk, after that when I want to update it says this;
Click to expand...
Click to collapse
Magisk is a root zip. It sounds like you are flashing SuperSU and Magisk. You can only use one or the other, not both!
Reflash stock ROM (or at least stock boot.img). Then flash Magisk. That's it.
Getting the error message that boot.img is modified is normal and expected in your case. SuperSU patched the boot image. Now Magisk is looking for the stock image to patch, and finding a patched one.
Hello guys,
Yesterday I flashed my Mi 8 to get root permissions with Global V10.2.1.0 with Magisk 17.3, including Disable DM-Verity and Force Encrypt. Everything was working perfect, Magisk notified me about updating to v18, so I did, and MIUI notified me about an update (if I'm not mistaken, for 10.2.2.0).
MIUI downloaded the update and asked me to reboot to install it. It booted into TWRP and did the whole installation, apparently without issues, but then I restarted and it goes straight to TWRP.
I tried clearing cache/dalvik but nothing.
Every time I reboot and gets to TWRP, when I press the menu button to see the log, the last lines say:
Full SELinux support is present.
set_policy_failed:/datamisc
I don't know if this is relevant, but seeing a "failed" is not nice.
As an observation, the folder /data/system is full of folders, but the /system directly in root folder only has /usr/share/zoneinfo (I don't know if this is normal or not),
If the system updated to 10.2.2.0, would flashing to 10.2.1.0 set the ARB or it's safe for me to flash it again? Any ideas?
Thanks!
You need to flash Magisk again. Installing an OTA means you flash the stock boot.img so flash dm verity and magisk.
ArmedandDangerous said:
You need to flash Magisk again. Installing an OTA means you flash the stock boot.img so flash dm verity and magisk.
Click to expand...
Click to collapse
Thanks for the answer! Do I need to wipe DATA too?
EDIT: I just flashed DM-Verity and then Magisk and all good. No need to wipe data. Thanks!!
So I've used TWRP r16 and it throws an "Image not signed or corrupt" error as suggested by other users I ignored it, but everytime I reboot to system and try to get to recovery "no command" show's up meaning TWRP was replaced by stock recovery all help will be appreciated.
Thanks
Akash731 said:
So I've used TWRP r16 and it throws an "Image not signed or corrupt" error as suggested by other users I ignored it, but everytime I reboot to system and try to get to recovery "no command" show's up meaning TWRP was replaced by stock recovery all help will be appreciated.
Thanks
Click to expand...
Click to collapse
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
Hey thanks that worked.
But everytime I boot to system and boot to twrp the data gets encrypted and I can't access the files do you happen to know any solution for this?
Akash731 said:
Hey thanks that worked.
But everytime I boot to system and boot to twrp the data gets encrypted and I can't access the files do you happen to know any solution for this?
Click to expand...
Click to collapse
If you are on stock Rom, according to my knoweldge it is not possible to remove encryption, if you format your date in twrp for removing encryption then reboot to system you can see that the phone is again encrypted.
But in custom roms this doesnt happen.
pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
pradeeppk said:
If you are on stock Rom, according to my knoweldge it is not possible to remove encryption, if you format your date in twrp for removing encryption then reboot to system you can see that the phone is again encrypted.
But in custom roms this doesnt happen.
Click to expand...
Click to collapse
I don't want to try custom rom's as this is my main device guess I'm stuck with the encryption then thanks for your help. :good:
Edit:-
Tried TWRP r20 it decrypts fine thanks
pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
You don't have to flash Magisk after flashing TWRP. The two are unrelated.
After flashing TWRP you have to boot into recovery, not system. Once TWRP was started, you can reboot into system. No need for Magisk (unless you want Magisk anyway).
gewe said:
You don't have to flash Magisk after flashing TWRP. The two are unrelated.
After flashing TWRP you have to boot into recovery, not system. Once TWRP was started, you can reboot into system. No need for Magisk (unless you want Magisk anyway).
Click to expand...
Click to collapse
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
pradeeppk said:
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
Click to expand...
Click to collapse
I am using stock ROM, and yes, also Magisk (installed later). IIRC Magisk is not needed for TWRP to work. When I receive the next OTA notification, I will test this.
The thread you are referring to is for a OnePlus 3T. For our device this is the thread: https://forum.xda-developers.com/moto-g5s-plus/development/recovery-twrp-3-1-1-r7-t3694910.
Since there is no official TWRP for the Moto G5S Plus, I took the following text from the TWRP page for the Moto G5S.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
Instead of that you can also use fastboot reboot-bootloader, and then from the bootloader start recovery.
pradeeppk said:
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
Click to expand...
Click to collapse
Two days ago I received a notification for an OTA update, containing the August 2019 security patches.
After going back to stock ROM, installing all the updates up to the latest, I installed TWRP. After booting into recovery, and then into system, and recovery again, TWRP was gone. Strange, I don't remember this happening before. Maybe I always installed Magisk before booting into system.
Bottom line: you were right, I was wrong. Thanks for pointing it out.
gewe said:
Two days ago I received a notification for an OTA update, containing the August 2019 security patches.
After going back to stock ROM, installing all the updates up to the latest, I installed TWRP. After booting into recovery, and then into system, and recovery again, TWRP was gone. Strange, I don't remember this happening before. Maybe I always installed Magisk before booting into system.
Bottom line: you were right, I was wrong. Thanks for pointing it out.
Click to expand...
Click to collapse
As like you said this is the first time in my life i need to flash magisk to stick twrp.
I usualy doesn't use root or custom roms, install twrp, remove unnecessary apps from stock system, replace host files with adaway hosts, replace or edit gps config files. and continue using stock.
This is the main routine from Android 1.5
(Samsung spica (i think it was the first Android phone from Samsung)).
It may be due to security reason stock kernel or system delete twrp.
When installing magisk it patch stock boot image, that may be the reason of twrp remains after flashing magisk.