Could I have dm-verify disabled, Magisk root with AP working, bootloader unlocked, and twrp all on OOS 4.0.3? What would be the best process for doing this on a brand new 3t with stock OOS 3.5.4?
What I was thinking was first disabling dm-verify on 3.5.4 with fastboot commands, then flash 4.0.3 as it is less than 1 GB, unlock the bootloader, and install magisk and twrp w/ fastboot. Am I missing anything?
Ulti2x said:
Could I have dm-verify disabled, Magisk root with AP working, bootloader unlocked, and twrp all on OOS 4.0.3? What would be the best process for doing this on a brand new 3t with stock OOS 3.5.4?
What I was thinking was first disabling dm-verify on 3.5.4 with fastboot commands, then flash 4.0.3 as it is less than 1 GB, unlock the bootloader, and install magisk and twrp w/ fastboot. Am I missing anything?
Click to expand...
Click to collapse
Just install FreedomOS, and judging by the performance and battery of 4.0.3 vs the new beta, get the CE version based on the beta. Im downloading it now. Some people are passing SafteyNet
Sent from my ONEPLUS A3000 using Tapatalk
uudruid74 said:
Just install FreedomOS, and judging by the performance and battery of 4.0.3 vs the new beta, get the CE version based on the beta. Im downloading it now. Some people are passing SafteyNet
Click to expand...
Click to collapse
What's CE?
Ulti2x said:
What's CE?
Click to expand...
Click to collapse
Not entirely sure what it stands for, but its based on the 7.1.1 beta. Running it now. Not passing safetynet, but it has a checker telling me why. Working on it..
Sent from my ONEPLUS A3000 using Tapatalk
To simplify this question, could I disable dm-verify and unlock the bootloader on OOS 3.5.4 and boot back into a wiped phone without any problems? After unlocking the bootloader and disabling dm verify, will I able to just update to 4.0.3 using the OTAs in settings?
Or does booting into the phone with an unlocked bootloader and no dm verify cause me to get stuck at boot? Thanks in advance.
Unlocking the bootloader does not trigger dm-verity or prevent you from installing via automatic OTA installs. Dm-verity is triggered if you flash TWRP and swipe to allow system modifications, which you will have to do if you intend to to root later.
You can use Oxygen OS's built-in OTA installer to update your phone as long as you have not rooted and have not installed TWRP yet. If you have either rooted or installed TWRP, it would be safer to flash the full ROM through TWRP for upgrades.
That said, everything you listed above can be accomplished. I would advise you take the following steps:
1) Use the phone's built-in OTA updater to upgrade to OOS 4.0.3*
*You can upgrade at a later step, though this way is more convenient as OOS will download and flash the patch automatically
2) Unlock bootloader (this will wipe everything)
3) Either move the Magisk.zip file to your internal storage at this point, or place it on a flash drive which you can access on your phone through USB OTG
4) Flash TWRP 3.0.4-1 through fastboot
5) Reboot to TWRP, swipe to enable system modifications (do not reboot until after you root)
6) Flash Magisk v11.1
7) Reboot into system, download Magisk Manager from the app store if the zip you flashed did not install the app automatically
8) Enable Magisk Hide in Magisk Manager, also hide Magisk from the play store app (prevents it from detecting root and labeling your device as uncertified).
9) Reboot phone for Magisk Hide to take effect.
Safetynet should be able to pass at this point. If you get a dm-verity message during boot, but everything else works perfectly, you can remove the message following this guide. I'm not sure if the stock kernel for OOS hides bootloader status, if you have problems with safetynet, you could try using a custom kernel.
At the moment, I am on OOS 4.0.3 with Franco's kernel and rooted with Magisk v11.1. My bootloader is unlocked and I have TWRP 3.0.4-1 as the recovery. Safetynet passes and my device is listed as certified in the Play Store. I can't test Android Pay as it hasn't been released here yet, though apps that checks safetynet like Pokemon GO work.
Anova's Origin said:
Unlocking the bootloader does not trigger dm-verity or prevent you from installing via automatic OTA installs. Dm-verity is triggered if you flash TWRP and swipe to allow system modifications, which you will have to do if you intend to to root later.
You can use Oxygen OS's built-in OTA installer to update your phone as long as you have not rooted and have not installed TWRP yet. If you have either rooted or installed TWRP, it would be safer to flash the full ROM through TWRP for upgrades.
That said, everything you listed above can be accomplished. I would advise you take the following steps:
1) Use the phone's built-in OTA updater to upgrade to OOS 4.0.3*
*You can upgrade at a later step, though this way is more convenient as OOS will download and flash the patch automatically
2) Unlock bootloader (this will wipe everything)
3) Either move the Magisk.zip file to your internal storage at this point, or place it on a flash drive which you can access on your phone through USB OTG
4) Flash TWRP 3.0.4-1 through fastboot
5) Reboot to TWRP, swipe to enable system modifications (do not reboot until after you root)
6) Flash Magisk v11.1
7) Reboot into system, download Magisk Manager from the app store if the zip you flashed did not install the app automatically
8) Enable Magisk Hide in Magisk Manager, also hide Magisk from the play store app (prevents it from detecting root and labeling your device as uncertified).
9) Reboot phone for Magisk Hide to take effect.
Safetynet should be able to pass at this point. If you get a dm-verity message during boot, but everything else works perfectly, you can remove the message following this guide. I'm not sure if the stock kernel for OOS hides bootloader status, if you have problems with safetynet, you could try using a custom kernel.
Click to expand...
Click to collapse
Thanks so much. I don't need to wipe cache after I flash Magisk right? And what's the big deal if the play store detects my device as uncertified?
Might as well wipe cache afterwards for good measure.
At the moment, Play Store certification does not seem to affect anything, though you never know when Google is going to start blocking uncertified devices from certain apps.
Just a small note but you should be able to root without modifying system. They modify boot image now and don't touch system.
Sent from my ONEPLUS A3000 using Tapatalk
Anova's Origin said:
Might as well wipe cache afterwards for good measure.
At the moment, Play Store certification does not seem to affect anything, though you never know when Google is going to start blocking uncertified devices from certain apps.
Click to expand...
Click to collapse
Can I use fastboot commands just by opening command prompt right?
EDIT: This link okay? https://forum.xda-developers.com/showthread.php?t=2588979
That tool should work fine.
Be sure to install the correct drivers for the OP3T as well.
Anova's Origin said:
That tool should work fine.
Be sure to install the correct drivers for the OP3T as well.
Click to expand...
Click to collapse
With this tool, I should be set for drivers right? https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Ulti2x said:
With this tool, I should be set for drivers right? https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Click to expand...
Click to collapse
Yep
uudruid74 said:
Not entirely sure what it stands for, but its based on the 7.1.1 beta. Running it now. Not passing safetynet, but it has a checker telling me why. Working on it..
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Ulti2x said:
What's CE?
Click to expand...
Click to collapse
CE stands for community edition
Anova's Origin said:
Unlocking the bootloader does not trigger dm-verity or prevent you from installing via automatic OTA installs. Dm-verity is triggered if you flash TWRP and swipe to allow system modifications, which you will have to do if you intend to to root later.
You can use Oxygen OS's built-in OTA installer to update your phone as long as you have not rooted and have not installed TWRP yet. If you have either rooted or installed TWRP, it would be safer to flash the full ROM through TWRP for upgrades.
That said, everything you listed above can be accomplished. I would advise you take the following steps:
1) Use the phone's built-in OTA updater to upgrade to OOS 4.0.3*
*You can upgrade at a later step, though this way is more convenient as OOS will download and flash the patch automatically
2) Unlock bootloader (this will wipe everything)
3) Either move the Magisk.zip file to your internal storage at this point, or place it on a flash drive which you can access on your phone through USB OTG
4) Flash TWRP 3.0.4-1 through fastboot
5) Reboot to TWRP, swipe to enable system modifications (do not reboot until after you root)
6) Flash Magisk v11.1
7) Reboot into system, download Magisk Manager from the app store if the zip you flashed did not install the app automatically
8) Enable Magisk Hide in Magisk Manager, also hide Magisk from the play store app (prevents it from detecting root and labeling your device as uncertified).
9) Reboot phone for Magisk Hide to take effect.
Safetynet should be able to pass at this point. If you get a dm-verity message during boot, but everything else works perfectly, you can remove the message following this guide. I'm not sure if the stock kernel for OOS hides bootloader status, if you have problems with safetynet, you could try using a custom kernel.
At the moment, I am on OOS 4.0.3 with Franco's kernel and rooted with Magisk v11.1. My bootloader is unlocked and I have TWRP 3.0.4-1 as the recovery. Safetynet passes and my device is listed as certified in the Play Store. I can't test Android Pay as it hasn't been released here yet, though apps that checks safetynet like Pokemon GO work.
Click to expand...
Click to collapse
My Play Store says uncertified after I did the whole process, and hid Magisk from it. Anyway to fix it?
Ulti2x said:
My Play Store says uncertified after I did the whole process, and hid Magisk from it. Anyway to fix it?
Click to expand...
Click to collapse
Go into settings, find Play Store and wipe cache. Then reboot.
Anova's Origin said:
Go into settings, find Play Store and wipe cache. Then reboot.
Click to expand...
Click to collapse
Still says it. Maybe I need to wait?
Forgot, I actually had to delete Play Store's app data last time before rebooting. Then it worked.
Thanks a lot everybody! I have never used fast boot before (have only flash w/ sammy phones) and now I know. Thanks again all for helping me.
I've just ordered the Mi Max 2 on Cyber Monday for $189.99 USD on GB, I've already applied and gotten approved for Xiaomi bootloader unlock.
While waiting for my phone to arrive I've been trying to do the necessary preperations for flashing Magisk.
I've never used Magisk before as my current Zenfone 5 uses SuperSU.
According to the release thread for Magisk the new Magisk Manager can patch the boot.img directly.
My question is, will the below steps work?
-unlock the bootloader
-install magisk manager
-download the full rom for the mi max 2 and patch it with the magisk manager
-flash the patched rom?
Would this work and would I be able to receive OTA updates using this method?
I'm asking because using TWRP means no OTA updates and that's a pain.
I want Magisk just for root, adblock, and camera api module to use google camera HDR+
I can't find any answers to my questions anywhere as all guides and threads talk about using the TWRP method and all say TWRP can't recieve OTA.
Chisame said:
I've just ordered the Mi Max 2 on Cyber Monday for $189.99 USD on GB, I've already applied and gotten approved for Xiaomi bootloader unlock.
While waiting for my phone to arrive I've been trying to do the necessary preperations for flashing Magisk.
I've never used Magisk before as my current Zenfone 5 uses SuperSU.
According to the release thread for Magisk the new Magisk Manager can patch the boot.img directly.
My question is, will the below steps work?
-unlock the bootloader
-install magisk manager
-download the full rom for the mi max 2 and patch it with the magisk manager
-flash the patched rom?
Would this work and would I be able to receive OTA updates using this method?
I'm asking because using TWRP means no OTA updates and that's a pain.
I want Magisk just for root, adblock, and camera api module to use google camera HDR+
I can't find any answers to my questions anywhere as all guides and threads talk about using the TWRP method and all say TWRP can't recieve OTA.
Click to expand...
Click to collapse
if you rooted forget about OTA updates.
u need to download recovery flashable update zip files against small size OTA's
this is a little hack for OTA updates.(if you have a stock recovery.img) ive not tried though
flash existing flashable rom. this removes (magisk / supersu / all system modification )
flash stock recovery
flash ota update via stock recovery
again u can flash magisk to get root.
u need to repeat the whole process whenever a ota is available (i would prefer to download the recovery flashable zip and flash it in TWRP)
Chisame said:
My question is, will the below steps work?
-unlock the bootloader
-install magisk manager
-download the full rom for the mi max 2 and patch it with the magisk manager
-flash the patched rom?
Click to expand...
Click to collapse
no need to patch rom/ boot.img just flash magisk.zip in twrp it patches automatically.
manual patching is required only for certain specific devices.
reversegear said:
if you rooted forget about OTA updates.
u need to download recovery flashable update zip files against small size OTA's
this is a little hack for OTA updates.(if you have a stock recovery.img) ive not tried though
flash existing flashable rom. this removes (magisk / supersu / all system modification )
flash stock recovery
flash ota update via stock recovery
again u can flash magisk to get root.
u need to repeat the whole process whenever a ota is available (i would prefer to download the recovery flashable zip and flash it in TWRP)
no need to patch rom/ boot.img just flash magisk.zip in twrp it patches automatically.
manual patching is required only for certain specific devices.
Click to expand...
Click to collapse
So, worst case scenario I'll still need to TWRP and install that way. Is the current TWRP compatible with MIUI 9 on the mi max 2?
MIUI 9 has been rolled out the the Max 2 locally.
Chisame said:
So, worst case scenario I'll still need to TWRP and install that way. Is the current TWRP compatible with MIUI 9 on the mi max 2?
MIUI 9 has been rolled out the the Max 2 locally.
Click to expand...
Click to collapse
Yes twrp is supported irrespective of miui version
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
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.