Related
Hey there.
I got my 3t in the day, 4.0.0 was released. So I unlocked my bootloader after upgrading.
At the time, dm-verity was new to me and so I ignored it.
By now I read up on it and guess I get it. What doesn't fit to what I read is the fact, that I modified my system in many ways. By flashing TWRP, by modifying system with super su and things like ad blockers (hosts file) and pixel launcher.
Yet I never installed the verity fix. I also use encrypted data partition.
How can that be?
My only guess is, I never installed a custom kernel yet or another Rom. But then again verity should be triggered way earlier. Did 4.0 not fully implement it?
mad-murdock said:
Hey there.
I got my 3t in the day, 4.0.0 was released. So I unlocked my bootloader after upgrading.
At the time, dm-verity was new to me and so I ignored it.
By now I read up on it and guess I get it. What doesn't fit to what I read is the fact, that I modified my system in many ways. By flashing TWRP, by modifying system with super su and things like ad blockers (hosts file) and pixel launcher.
Yet I never installed the verity fix. I also use encrypted data partition.
How can that be?
My only guess is, I never installed a custom kernel yet or another Rom. But then again verity should be triggered way earlier. Did 4.0 not fully implement it?
Click to expand...
Click to collapse
They say (in twrp thread and in oneplus forums) if you flash supersu, you are fine...
ram4ufriends said:
They say (in twrp thread and in oneplus forums) if you flash supersu, you are fine...
Click to expand...
Click to collapse
When am I not fine? Protection only triggers if kernel is exchanged?
It's not that I don't want to flash it, but I am eager to know.
*bump* - trying a last time, to see if anyone knows details
The whole point of dm verity is to make sure phone is not rooted or modified in any way that could compromise app security, luckily it doesn't work quite 100% as we can still root without triggering it, even though it should.
I guess, the answer to my question is, TWRP automatically applies the dm-verity patch on first install. I overlooked that feature to be honest, but it makes total sense to do so and protect custom recovery users from locking out of your phone
I have this questions too. And I can't decrypt Data even if I input the right password. I can't use recovery anymore with TWRP or the stock rec.
Here is some details about the dm-verity. https://source.android.com/security/verifiedboot/verified-boot.html
I only know Android N will encrypt Data by using f2fs file system.........
If you have some effective methods, please tell me. Thanks a lot!
mad-murdock said:
I guess, the answer to my question is, TWRP automatically applies the dm-verity patch on first install. I overlooked that feature to be honest, but it makes total sense to do so and protect custom recovery users from locking out of your phone
Click to expand...
Click to collapse
It's my understanding that SuperSU applies the dm-verity patch when it's installed.
napetost said:
I have this questions too. And I can't decrypt Data even if I input the right password. I can't use recovery anymore with TWRP or the stock rec.
Here is some details about the dm-verity. https://source.android.com/security/verifiedboot/verified-boot.html
I only know Android N will encrypt Data by using f2fs file system.........
If you have some effective methods, please tell me. Thanks a lot!
Click to expand...
Click to collapse
flash TWRP 3.0.3-1-beta1 and try again
I have found the right way!
First, you should flash back to OOS3.5 6.0, then set the pin password. And then copy OOS4.0 to /sdcard ,then using system update.Then you will update to OOS4.0 and you won't see any dm-verity problems.
napetost said:
I have found the right way!
First, you should flash back to OOS3.5 6.0, then set the pin password. And then copy OOS4.0 to /sdcard ,then using system update.Then you will update to OOS4.0 and you won't see any dm-verity problems.
Click to expand...
Click to collapse
That's one way. Using the TWRP beta is another. It's in the TWRP post, page 55, bottom. Post 550. Actually the last few pages of that post discuss this issue right now. Might be worth reading.
oos 4.0.3 rooted - but can't rid of dm-verity and bootload unlocked warnings.
Any help to remove this nagging warning would be appreciated.
-Thanks.
And by the way, besides the irritating warnings, what are the real implications of having this two situations? thanks.
That's the point of these warnings, to let you know that your device is compromited. There is no official way to turn them off.
You would think that if someone stole your phone, you wouldn't want them to know about any vulnerabilities by simply turning it off and rebooting...
Bootloader warning is going to remain there as long as your bootloader is unlocked. The dm-verity comes from allowing the system partition to be modifiable. There's a flashable script you can use, or you can run a couple of commands through fastboot:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
That just make the verity problem go away.
tzbigworm said:
Bootloader warning is going to remain there as long as your bootloader is unlocked. The dm-verity comes from allowing the system partition to be modifiable. There's a flashable script you can use, or you can run a couple of commands through fastboot:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
That just make the verity problem go away.
Click to expand...
Click to collapse
The script no longer works on OOS 4.0.3. The command was patched out due to the "security flaw".
Wow so neither of those are usable on 4.0.3 now?
Nope, you're stuck with the dm-verity message at boot now, in addition to the bootloader unlocked message. There is apparently a way to replace the OOS 4.0.3 fastboot commands with those from OOS 4.0.2 to remove the message, but mixing system components from different versions is pretty dangerous. It works for now, thought who knows what'll happen if you try it on future updates.
So flashing a kernel/supersu doesn't work anymore, either, to get rid of dm_verity?
tzbigworm said:
So flashing a kernel/supersu doesn't work anymore, either, to get rid of dm_verity?
Click to expand...
Click to collapse
Those still work. The fastboot commands don't work anymore since the update.
Sent from my OnePlus 3T using XDA Labs
I am rooted with SuperSU and have the latest Franco kernel installed, yet the dm-verity message still persists on boot.
Can someone explain what dm-verity is and how it affects us? Sorry for my ignorance.
SlimJ87D said:
Can someone explain what dm-verity is and how it affects us? Sorry for my ignorance.
Click to expand...
Click to collapse
TL;DR Dm-verity is a security feature that was flawed before OOS 4.0.3. Oneplus fixed it with the latest update, but it means that we can't get rid of an annoying message on boot.
DM-verity is an optional security feature in linux (therefore android). When initially activated, it essentially remembers the state of your phone's integral system files. If at any point after enabling, something changes in the critical system files, it will assume that something has gone wrong (for example, malware with root access) and prevent the phone from booting. The critical system files that it checks aren't the normal system files for your ROM, but rather important files in the boot partition, where an average user would generally not have access to.
Enabling certain features in TWRP will modify some of these monitored files, causing dm-verity to suspect malware and prevent the phone from booting. Rooting your phone after making these modifications can prevent dm-verity from bricking your phone, but it still trips the alert, resulting in an annoying, but harmless message at boot. Another method of circumventing dm-verity is to deactivate it and reactivate it, whereby it would assume your modified partitions is the default version. This was how people got rid of the boot message before, as dm-verity wouldn't be able to detect any changes. Being able to deactivate and reactive dm-verity is a security flaw though, as a feature like this would be pointless if any attacker could just turn it off with a fastboot command. This is why Oneplus patched out the commands.
Most people who install custom recoveries are likely going to root their phones anyways, so it's not going to affect the phone's functionality if dm-verity is tripped. The main gripe I have with it is that now there's a second warning message at boot (after the unlocked bootloader message), which, to be honest, is at most a mild inconvenience.
Delete
https://forum.xda-developers.com/oneplus-3t/how-to/fix-dm-verity-warning-final-fix-4-0-3-t3555094
I have the problem of not being able to disable dm-verity on my 3T since 4.0.3, but it's made for a much bigger problem than the "popup" on boot, I now cannot pass SafetyNet (for Android Pay), if I flash back to Sultan CM13, or LOS14.1 (with 4.0.2 firmware and disable and reenable dm verity) it works fine, but even flashing the 4.0.2 firmware and doing the disable enable stuff, SafetyNet still doesn't pass, which is a nightmare.
Anova's Origin said:
I am rooted with SuperSU and have the latest Franco kernel installed, yet the dm-verity message still persists on boot.
Click to expand...
Click to collapse
Can you please start the file you used to root?
ddaharu said:
Can you please start the file you used to root?
Click to expand...
Click to collapse
It was the one included in the OnePlus 3/3T toolkit (v4.5U). I tried rooting with the one on chainfire's website a while back when I was on OOS 4.0.2, but I kept getting stuck in a bootloop. The one from the toolkit worked fine while I was using it.
Anova's Origin said:
It was the one included in the OnePlus 3/3T toolkit (v4.5U). I tried rooting with the one on chainfire's website a while back which I was on OOS 4.0.2, but I kept getting stuck in a bootloop. The one from the toolkit worked fine while I was using it.
Click to expand...
Click to collapse
Hmmmmm. I don't have a pc..... I'll look to see if I can find another. Thanks bro
You can use this one https://forum.xda-developers.com/oneplus-3t/how-to/fix-dm-verity-warning-final-fix-4-0-3-t3555094
I suggest you to use chainfire SuperSU to get root..I personally use this .I also tried phh superuser but it's not working properly so use SuperSU
do i need to install dm verity if I'm installing custom rom
No
sakumaxp said:
No
Click to expand...
Click to collapse
So i just unlock bootloader, install twrp and boot it, and just do a full wipe then install my rom. So dm verity is for oos only?
I mean DM verity doesn't do much really, it's just an extra push of the power button or extra 5 seconds.
You really should learn a little more before diving down the rabbit hole. You'll save yourself some trouble (and probably some money too) if you learn what it is you're doing before you make a mistake and break your phone.
DM-verity is a security feature implemented by Google to verify the integrity of the system before it allows the device to boot. While it's a little more complicated than that, that's dm-verity in a nutshell. The reason Google implemented dm-verity is because of Android Pay. If dm-verity is triggered, then it may allow a device to boot, but it will disable Android Pay among other things for security reasons.
HampTheToker said:
You really should learn a little more before diving down the rabbit hole. You'll save yourself some trouble (and probably some money too) if you learn what it is you're doing before you make a mistake and break your phone.
DM-verity is a security feature implemented by Google to verify the integrity of the system before it allows the device to boot. While it's a little more complicated than that, that's dm-verity in a nutshell. The reason Google implemented dm-verity is because of Android Pay. If dm-verity is triggered, then it may allow a device to boot, but it will disable Android Pay among other things for security reasons.
Click to expand...
Click to collapse
I just want to flash a bunch of roms when my phone gets delivered, but before flashing my first rom should i flash the dm verity zip? or do you only flash that zip with oos.
Rebel7022 said:
I just want to flash a bunch of roms when my phone gets delivered, but before flashing my first rom should i flash the dm verity zip? or do you only flash that zip with oos.
Click to expand...
Click to collapse
Like I said, do some reading. There are more than a couple threads dealing with dm-verity in the Guides, News, and Discussion subforum. You don't have to flash anything to do with dm-verity in order to flash roms.
I promise you, eventually you'll do something you shouldn't if you don't educate yourself and familiarize yourself with these things. Save yourself the trouble and read, read, read!!! If you still have questions, then ask. You'll get better responses if you at least take the time to understand these things just a little bit.
HampTheToker said:
Like I said, do some reading. There are more than a couple threads dealing with dm-verity in the Guides, News, and Discussion subforum. You don't have to flash anything to do with dm-verity in order to flash roms.
I promise you, eventually you'll do something you shouldn't if you don't educate yourself and familiarize yourself with these things. Save yourself the trouble and read, read, read!!! If you still have questions, then ask. You'll get better responses if you at least take the time to understand these things just a little bit.
Click to expand...
Click to collapse
I've been reading pages of forums for two days now, I'm coming from a oneplus two, I like to flash roms allot. I'm trying to educate my self. So i install twrp and my rom and forget dm verity? So if I never plan to run oxygen I never have to worry about dm verity? thanks for your help,
You don't have to worry about it all, really. Unless you use Android Pay, then ignore it.
Install dm-verity and download more ram.
Sent from my OnePlus 3T using XDA Labs
dustin_b said:
Install dm-verity and download more ram.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
how do you download more ram?
dude, just get yourself an iphone.. you've missed the boat.. roflmao
Apparently, you guys forgot how awkward you were when you first started rooting your phones. Give the noobie a break.
Sent from my ONEPLUS A3000 using Tapatalk
Jr173 said:
dude, just get yourself an iphone.. you've missed the boat.. roflmao
Click to expand...
Click to collapse
Bro I'm not a noob I just want to know can i skip installing the dm verity zip if I'm gonna install a custom rom as soon as I can boot twrp for the fist time, or do i install that dm verity zip and then install custom rom? I'm waiting for my phone in the mail. I'm not a noob don't ever call me that again . lol I'm just playing.. lol :fingers-crossed:
Rebel7022 said:
I've been reading pages of forums for two days now, I'm coming from a oneplus two, I like to flash roms allot. I'm trying to educate my self. So i install twrp and my rom and forget dm verity? So if I never plan to run oxygen I never have to worry about dm verity? thanks for your help,
Click to expand...
Click to collapse
And also buy yourself an otg cable and a USB flash drive in case your get encrypted and have to wipe your full system like, at least you'll have a back up or firmware you can flash
sakumaxp said:
And also buy yourself an otg cable and a USB flash drive in case your get encrypted and have to wipe your full system like, at least you'll have a back up or firmware you can flash
Click to expand...
Click to collapse
You can backup over MTP on your computer with TWRP 3.1.0-1. Much more convenient IMO.
Some noob questions to which i can't find answers here
1)What is vox and eas? I see it on many ROM titles..
2) what is this dm-verity issue? Is it just a warning message that appears if you enable system partition amendment in twrp? Or this dm-verity issue makes the device unbootable ?
3) what is blob? Is it the same as firmware?
I hope i am not sounding stupid.. I am new to opt3...
google.com knows it
Sorry, but these questions are answered so many times here on XDA and on other sites
phoberus said:
google.com knows it
Sorry, but these questions are answered so many times here on XDA and on other sites
Click to expand...
Click to collapse
I tried google before posting here..
Read many threads on xda.. But i can read each and every post of every thread..
And instead of typing that reply, you could have typed the answer.. Thanx anyways...
Sent from my Redmi Note 3 using XDA Labs
EAS: https://www.linaro.org/blog/core-dump/energy-aware-scheduling-eas-project/
Vox: Read first few posts from the supported Roms, example: https://forum.xda-developers.com/showpost.php?p=71394499&postcount=4
(about both you can read much in threads)
dm-verity issue: newer had this. I think this is if twrp can't decrypt your phone
blobs: parts of the firmware
phoberus said:
EAS: https://www.linaro.org/blog/core-dump/energy-aware-scheduling-eas-project/
Vox: Read first few posts from the supported Roms, example: https://forum.xda-developers.com/showpost.php?p=71394499&postcount=4
(about both you can read much in threads)
dm-verity issue: newer had this. I think this is if twrp can't decrypt your phone
blobs: parts of the firmware
Click to expand...
Click to collapse
Thanks a lot.. That solved my doubts..
Only doubt left is dm-varity thing...
Sent from my Redmi Note 3 using XDA Labs
a.broken.star said:
Thanks a lot.. That solved my doubts..
Only doubt left is dm-varity thing...
Sent from my Redmi Note 3 using XDA Labs
Click to expand...
Click to collapse
You know, there's a pretty good search feature right here on XDA: https://forum.xda-developers.com/sitesearch.php?q=dm-verity
The first hit should be an article (pretty old, but still relevant) about dm-verity and the implication it has for those of us who like to tinker with our devices.
Most custom kernels and root solutions disable dm-verity. Otherwise there are zips around you can use as well.
Dm verity is a security measure that check the os and kernel for any tamperments ,it is usually triggered by Twrp or by rooting process as they changes the default recovery with different one ,in some cases DM verity won't let your mobile boot ,in order to prevent the unauthorized tamperment to run in os ,but DM verity and force encryption can be disabled by flashing DM verity remover zip ,but it leaves the red warning message
smarter than newton said:
Dm verity is a security measure that check the os and kernel for any tamperments ,it is usually triggered by Twrp or by rooting process as they changes the default recovery with different one ,in some cases DM verity won't let your mobile boot ,in order to prevent the unauthorized tamperment to run in os ,but DM verity and force encryption can be disabled by flashing DM verity remover zip ,but it leaves the red warning message
Click to expand...
Click to collapse
I read that if you give the permission that's asked when you first load twrp "allow system partition modification", then that triggers dm-varity.. But if flash supersu in the same session in twrp, it makes the dm-varity issue OK... But if it's just a warning message just like unlocked bootloader warning, then i am OK with it....
Sent from my Redmi Note 3 using XDA Labs
a.broken.star said:
I read that if you give the permission that's asked when you first load twrp "allow system partition modification", then that triggers dm-varity.. But if flash supersu in the same session in twrp, it makes the dm-varity issue OK... But if it's just a warning message just like unlocked bootloader warning, then i am OK with it....
Sent from my Redmi Note 3 using XDA Labs
Click to expand...
Click to collapse
But you need to remove the force encryption in order for device to boot properly or else it may need to reset your data including SD storage ,To force remove the encryption you can flash azip file and you can also remove the DM verity warning using adb commands
smarter than newton said:
But you need to remove the force encryption in order for device to boot properly or else it may need to reset your data including SD storage ,To force remove the encryption you can flash azip file and you can also remove the DM verity warning using adb commands
Click to expand...
Click to collapse
Okay.. I found the zip file and adb commands.. Thanx a lot...
Sent from my Redmi Note 3 using XDA Labs
phoberus said:
EAS: https://www.linaro.org/blog/core-dump/energy-aware-scheduling-eas-project/
Vox: Read first few posts from the supported Roms, example: https://forum.xda-developers.com/showpost.php?p=71394499&postcount=4
(about both you can read much in threads)
dm-verity issue: newer had this. I think this is if twrp can't decrypt your phone
blobs: parts of the firmware
Click to expand...
Click to collapse
exactly
Use Magisk, you can stay encrypted.
Galactus said:
Use Magisk, you can stay encrypted.
Click to expand...
Click to collapse
So..
Unlock bootloader
Flash twrp
Flash magisk
Reboot...
No problems related to encryption and passwords etc?
Sent from my Redmi Note 3 using XDA Labs
a.broken.star said:
So..
Unlock bootloader
Flash twrp
Flash magisk
Reboot...
No problems related to encryption and passwords etc?
Sent from my Redmi Note 3 using XDA Labs
Click to expand...
Click to collapse
Yep, same steps I took. I did have to delete my password key files in twrp the first time I rebooted after flashing magisk, but it's a simple fix. Been good ever since.
Currently running OOS 4.1.3, magisk V12 rooted, Franco kernel, encrypted, no issues.
a.broken.star said:
Okay.. I found the zip file and adb commands.. Thanx a lot...
Click to expand...
Click to collapse
You're welcome
I'm currently on a stable build of Oxygen OS 5.0.2 Oreo and I was thinking of rooting my phone using Magisk.Most of the guides that I've seen had users root using a nougat based version of OOS or they were on beta. I'll have to unlock the bootloader and flash TWRP but this is where the confusion comes in - Can I root a stable build of OOS? Will I have to switch to beta to root? Also, I'm a little scared about whether this DM-Verity issue will arise or not if I try to root or flash TWRP. So can someone please explain what that Issue really is and will it arise in my case? And if someone can just give me a guide on how to root it, I'll really appreciate it. And are there any known issues which arise after successfully rooting OOS 5.0.2?
No obstacles in rooting stable OOS and no problems should arise after doing it. You just need to make a backup of all your data, unlock bootloader, flash TWRP, flash Magisk and go.
If you trigger dm-verity, tyou have two choices - either ignore it on every reboot or follow a guide about removing it.
anshikohri said:
I'm currently on a stable build of Oxygen OS 5.0.2 Oreo and I was thinking of rooting my phone using Magisk.Most of the guides that I've seen had users root using a nougat based version of OOS or they were on beta. I'll have to unlock the bootloader and flash TWRP but this is where the confusion comes in - Can I root a stable build of OOS? Will I have to switch to beta to root? Also, I'm a little scared about whether this DM-Verity issue will arise or not if I try to root or flash TWRP. So can someone please explain what that Issue really is and will it arise in my case? And if someone can just give me a guide on how to root it, I'll really appreciate it. And are there any known issues which arise after successfully rooting OOS 5.0.2?
Click to expand...
Click to collapse
All things that you are mentioning show clearly that you didn't pay attention to all the basic info for rooting a 3/3T.
Why do u need a guide for Oreo, when you have a guide for nougat?
It's exactly the same method.
Also DM verity is just a warning, so why to be scared.
Maybe you should avoid doing something that you don't understand.
Unleashed by my rooted OP3T on 8.0
RASTAVIPER said:
All things that you are mentioning show clearly that you didn't pay attention to all the basic info for rooting a 3/3T.
Why do u need a guide for Oreo, when you have a guide for nougat?
It's exactly the same method.
Also DM verity is just a warning, so why to be scared.
Maybe you should avoid doing something that you don't understand.
Unleashed by my rooted OP3T on 8.0
Click to expand...
Click to collapse
Well I had a Redmi 2 before this and when I tried to root my lineage Os based on oreo with magisk using the same method I used with Nougat, i bricked my device. So that's why i was a little apprehensive. But thank you for your response.
przemcio510 said:
No obstacles in rooting stable OOS and no problems should arise after doing it. You just need to make a backup of all your data, unlock bootloader, flash TWRP, flash Magisk and go.
If you trigger dm-verity, tyou have two choices - either ignore it on every reboot or follow a guide about removing it.
Click to expand...
Click to collapse
Will I run into trouble with xposed or substratum on OOS?
anshikohri said:
Will I run into trouble with xposed or substratum on OOS?
Click to expand...
Click to collapse
No, if you use compatible modules and themes. I had no problems using both on OOS. Please note that if you install Xposed, you won't be able to use SafetyNet protected apps (Android Pay, Pokemon Go, Snapchat (you have to login before installing Xposed to make it work) etc.).
anshikohri said:
Well I had a Redmi 2 before this and when I tried to root my lineage Os based on oreo with magisk using the same method I used with Nougat, i bricked my device.
Click to expand...
Click to collapse
You aren't being specific enough when you say "same method". The general method is often similar. But you will virtually never use the exact same steps when rooting different Android builds (such as Nouget vs. Oreo). In particular, you always need to use updated versions of files for TWRP and Magisk. By definition, the root exploits will change between Android versions. So using old version Magisk is basically asking for a "soft brick". Not a real brick. It usually just means you need to use the correct version Magisk in order to recover. Or at worst, flash recovery image (or restore TWRP backup - which you should always have a backup of the stock ROM before rooting) then root with the proper files. Don't know anything about your old phone - but I'll guess this is what happened (which is a common enough scenario).
Similarly, you should also use the most current version TWRP. Older versions may sometimes work, depending on the situation. But Oreo (vs. Nougat) in particular, TWRP had to be updated to be compatible. Meaning you must use a Oreo-compatible version of TWRP to avoid problems. Short story, use current version TWRP to avoid problems.
Current versions are:
TWRP 3.2.1-0
Magisk v16.0
Also proceed with the knowledge that this device is very hard to brick. Just flashing TWRP and Magisk will not brick it (not a true brick anyway - a "soft" brick is easy to recover from as already described). Just make sure you are using Magisk for the OP3/3T (not some other device) and the risk is virtually zero. Even in the case of a brick, this device has an unbricking tool. Just be sure to take the following precautions:
- Make a TWRP backup of the stock ROM before you flash Magisk (always amazed at how many folks skip this!) or otherwise have the stock recovery image available in case anything happens. Basically always have a backup plan!
- Find the unbrick tool, and again have it available (at least bookmarked) in case you need it.
- Most importantly, read and understand all the steps and concepts before you begin. As another already mentioned, it seems your knowledge about some of the concepts is a bit lacking.
---------- Post added at 10:30 AM ---------- Previous post was at 10:06 AM ----------
anshikohri said:
Most of the guides that I've seen had users root using a nougat based version of OOS or they were on beta.
Click to expand...
Click to collapse
Beta or Stable doesn't matter. I don't know if I've ever seen a root guide specific to the Beta version, so I'm not even sure what you are talking about.
As far as the guides being for Nougat, I've already addressed that above. Basically, everything is the same, except the file versions (use updated TWRP, Magisk) so that is why nobody has bothered posting new guides for every OOS build.
anshikohri said:
Also, I'm a little scared about whether this DM-Verity issue will arise or not if I try to root or flash TWRP.
Click to expand...
Click to collapse
DM-verity is just a warning screen that appears when you reboot or power-on the phone. It will go away and continue to boot normally after 5 seconds, or just press the power button to dismiss the warning.
Once the phone has TWRP and rooted, you will have the DM-verity warning screen. If you like, you can flash a patched boot image, so you don't see the DM-verity warning screen on reboot/power-on.
You will also have a very similar (but separate) warning screen once the bootloader is unlocked. Unlike the DM-verity screen, the bootloader unlocked warning is impossible to be removed. The only way to remove it is to relock the bootloader, which I would strongly warn you not to do on a modified (TWRP and root) device! The bootloader unlock warning screen is just something you live with if you are rooted (just wait the 5 seconds or press the power button to skip it).
There is also the unlikely event that DM-verity will outright prevent the OS from booting. But this shouldn't happen just from flashing TWRP and Magisk (at least not if you've done it properly). Even if this happens, just restore your TWRP backup, or flash recovery image, and start over - checking what you did (cause you probably did something wrong).
anshikohri said:
And are there any known issues which arise after successfully rooting OOS 5.0.2?
Click to expand...
Click to collapse
This is so vague, as to make it hard to figure out what you are even asking.
In short, No.
Long answer: Some apps will not work with root, such as banking apps and Netflix. But the Magisk "Hide" feature should work to conceal root and make these apps work. It's a whole topic in itself, so read up in existing threads if this applies to you, and you want more info.
Other than that, there isn't anything with Magisk root that I would consider an "issue" and make me want to unroot.
redpoint73 said:
You aren't being specific enough when you say "same method". The general method is often similar. But you will virtually never use the exact same steps when rooting different Android builds (such as Nouget vs. Oreo). In particular, you always need to use updated versions of files for TWRP and Magisk. By definition, the root exploits will change between Android versions. So using old version Magisk is basically asking for a "soft brick". Not a real brick. It usually just means you need to use the correct version Magisk in order to recover. Or at worst, flash recovery image (or restore TWRP backup - which you should always have a backup of the stock ROM before rooting) then root with the proper files. Don't know anything about your old phone - but I'll guess this is what happened (which is a common enough scenario).
Similarly, you should also use the most current version TWRP. Older versions may sometimes work, depending on the situation. But Oreo (vs. Nougat) in particular, TWRP had to be updated to be compatible. Meaning you must use a Oreo-compatible version of TWRP to avoid problems. Short story, use current version TWRP to avoid problems.
Current versions are:
TWRP 3.2.1-0
Magisk v16.0
Also proceed with the knowledge that this device is very hard to brick. Just flashing TWRP and Magisk will not brick it (not a true brick anyway - a "soft" brick is easy to recover from as already described). Just make sure you are using Magisk for the OP3/3T (not some other device) and the risk is virtually zero. Even in the case of a brick, this device has an unbricking tool. Just be sure to take the following precautions:
- Make a TWRP backup of the stock ROM before you flash Magisk (always amazed at how many folks skip this!) or otherwise have the stock recovery image available in case anything happens. Basically always have a backup plan!
- Find the unbrick tool, and again have it available (at least bookmarked) in case you need it.
- Most importantly, read and understand all the steps and concepts before you begin. As another already mentioned, it seems your knowledge about some of the concepts is a bit lacking.
---------- Post added at 10:30 AM ---------- Previous post was at 10:06 AM ----------
Beta or Stable doesn't matter. I don't know if I've ever seen a root guide specific to the Beta version, so I'm not even sure what you are talking about.
As far as the guides being for Nougat, I've already addressed that above. Basically, everything is the same, except the file versions (use updated TWRP, Magisk) so that is why nobody has bothered posting new guides for every OOS build.
DM-verity is just a warning screen that appears when you reboot or power-on the phone. It will go away and continue to boot normally after 5 seconds, or just press the power button to dismiss the warning.
Once the phone has TWRP and rooted, you will have the DM-verity warning screen. If you like, you can flash a patched boot image, so you don't see the DM-verity warning screen on reboot/power-on.
You will also have a very similar (but separate) warning screen once the bootloader is unlocked. Unlike the DM-verity screen, the bootloader unlocked warning is impossible to be removed. The only way to remove it is to relock the bootloader, which I would strongly warn you not to do on a modified (TWRP and root) device! The bootloader unlock warning screen is just something you live with if you are rooted (just wait the 5 seconds or press the power button to skip it).
There is also the unlikely event that DM-verity will outright prevent the OS from booting. But this shouldn't happen just from flashing TWRP and Magisk (at least not if you've done it properly). Even if this happens, just restore your TWRP backup, or flash recovery image, and start over - checking what you did (cause you probably did something wrong).
This is so vague, as to make it hard to figure out what you are even asking.
In short, No.
Long answer: Some apps will not work with root, such as banking apps and Netflix. But the Magisk "Hide" feature should work to conceal root and make these apps work. It's a whole topic in itself, so read up in existing threads if this applies to you, and you want more info.
Other than that, there isn't anything with Magisk root that I would consider an "issue" and make me want to unroot.
Click to expand...
Click to collapse
That certainly cleared all my doubts and my inhibitions. Thank you so much for taking the time to address my questions.
anshikohri said:
That certainly cleared all my doubts and my inhibitions. Thank you so much for taking the time to address my questions.
Click to expand...
Click to collapse
You're certainly welcome. There is a "Thanks" button you can click for any posts that you found helpful, if you care to do so.
And a constructive criticism on forum etiquette: please don't quote a whole huge long post, like you did for my response. I know it's the default when responding to include a quote. But simply delete what isn't directly relevant (maybe keep a few lines, as appropriate) in the interest of keeping the forum free of clutter; and avoid folks have having to scroll down a whole screen/page which is just my post in duplicate. You can still edit the previous post, if you like.
Good luck on rooting. I'm sure it will go fine. Welcome to the dark side.
redpoint73 said:
And a constructive criticism on forum etiquette: please don't quote a whole huge long post, like you did for my response. I know it's the default when responding to include a quote. But simply delete what isn't directly relevant (maybe keep a few lines, as appropriate) in the interest of keeping the forum free of clutter; and avoid folks have having to scroll down a whole screen/page which is just my post in duplicate. You can still edit the previous post, if you like.
As you can see, I'm new to this, so forgive me. I'll keep this in mind the next time I post something and Thank You for your advise and your help.
Click to expand...
Click to collapse
redpoint73 said:
You aren't being specific enough when you say "same method". The general method is often similar. But you will virtually never use the exact same steps when rooting different Android builds (such as Nouget vs. Oreo). In particular, you always need to use updated versions of files for TWRP and Magisk. By definition, the root exploits will change between Android versions. So using old version Magisk is basically asking for a "soft brick". Not a real brick. It usually just means you need to use the correct version Magisk in order to recover. Or at worst, flash recovery image (or restore TWRP backup - which you should always have a backup of the stock ROM before rooting) then root with the proper files. Don't know anything about your old phone - but I'll guess this is what happened (which is a common enough scenario).
Similarly, you should also use the most current version TWRP. Older versions may sometimes work, depending on the situation. But Oreo (vs. Nougat) in particular, TWRP had to be updated to be compatible. Meaning you must use a Oreo-compatible version of TWRP to avoid problems. Short story, use current version TWRP to avoid problems.
Current versions are:
TWRP 3.2.1-0
Magisk v16.0
Also proceed with the knowledge that this device is very hard to brick. Just flashing TWRP and Magisk will not brick it (not a true brick anyway - a "soft" brick is easy to recover from as already described). Just make sure you are using Magisk for the OP3/3T (not some other device) and the risk is virtually zero. Even in the case of a brick, this device has an unbricking tool. Just be sure to take the following precautions:
- Make a TWRP backup of the stock ROM before you flash Magisk (always amazed at how many folks skip this!) or otherwise have the stock recovery image available in case anything happens. Basically always have a backup plan!
- Find the unbrick tool, and again have it available (at least bookmarked) in case you need it.
- Most importantly, read and understand all the steps and concepts before you begin. As another already mentioned, it seems your knowledge about some of the concepts is a bit lacking.
---------- Post added at 10:30 AM ---------- Previous post was at 10:06 AM ----------
Beta or Stable doesn't matter. I don't know if I've ever seen a root guide specific to the Beta version, so I'm not even sure what you are talking about.
As far as the guides being for Nougat, I've already addressed that above. Basically, everything is the same, except the file versions (use updated TWRP, Magisk) so that is why nobody has bothered posting new guides for every OOS build.
DM-verity is just a warning screen that appears when you reboot or power-on the phone. It will go away and continue to boot normally after 5 seconds, or just press the power button to dismiss the warning.
Once the phone has TWRP and rooted, you will have the DM-verity warning screen. If you like, you can flash a patched boot image, so you don't see the DM-verity warning screen on reboot/power-on.
You will also have a very similar (but separate) warning screen once the bootloader is unlocked. Unlike the DM-verity screen, the bootloader unlocked warning is impossible to be removed. The only way to remove it is to relock the bootloader, which I would strongly warn you not to do on a modified (TWRP and root) device! The bootloader unlock warning screen is just something you live with if you are rooted (just wait the 5 seconds or press the power button to skip it).
There is also the unlikely event that DM-verity will outright prevent the OS from booting. But this shouldn't happen just from flashing TWRP and Magisk (at least not if you've done it properly). Even if this happens, just restore your TWRP backup, or flash recovery image, and start over - checking what you did (cause you probably did something wrong).
This is so vague, as to make it hard to figure out what you are even asking.
In short, No.
Long answer: Some apps will not work with root, such as banking apps and Netflix. But the Magisk "Hide" feature should work to conceal root and make these apps work. It's a whole topic in itself, so read up in existing threads if this applies to you, and you want more info.
Other than that, there isn't anything with Magisk root that I would consider an "issue" and make me want to unroot.
Click to expand...
Click to collapse
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery nd super su root but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide
mannulko said:
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery nd super su root but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide
Click to expand...
Click to collapse
Please don't include page-long quotes in your post. For that matter, don't quote my posts at all, if you aren't going to refer to it, or read it.
And please only post your problem to one thread, per forum rules. It will be answered. Making more posts, will NOT get your question answered any faster. It will just confuse those trying to help you, and confuse you; jumping around to 4 different threads.