is there any way to successfully root the op3t running 4.0.2 without the dm verity errors and everything?
milanexplorer said:
is there any way to successfully root the op3t running 4.0.2 without the dm verity errors and everything?
Click to expand...
Click to collapse
use the latest twrp and supersu had no problems with 4.0.1, I doubt 4.0.2 is different.
edit: according to the changelog only something with the play store has been fixed, so if it doesn't work. They need to tell us what has changed.
worked for me 4.0.2.
root working no problem on 4.02
I went from a rooted phone with twrp 3.0.3-1 started at OOS 3.54 then went to 4.0.1 then to 4.0.2 by flashing full zip files and reflashing supersu each time to maintain root.
I think it should be fine you just have to flash the latest supersu zip file.
I confirm dm-verity error with 4.0.2.
With or without root?
Related
I saw that the 4.0 version of Oxygen OS was available with a full version to flash. I have finally recieved my OP3T today, got TWRP installed with supersu root as well. Will I ruin anything if I flash the new 4.0 nougat version? I haven't gotten xposed installed yet (wanted to check out DPI scaling on nougat first), will that be possible after flashing 4.0 as well?
thanks in advance, so excited about this phone!
Hi
You can flash the zip using TWRP. Just flash SuperSU afterwards. Xposed won't work.
I've done that now, got nougat working fine, with twrp and SuperSU but I can't get the dm-verity warning to go away. I've tried flashing the stock recovery and then reflashing twrp and superSU, but no luck so far
OOS 4 just rolled out in Italy so I'd like to update asap, but I can't lose root privileges or twrp. What's the fastest way to do this?
Thanks
Update TWRP to 3.03-1. download the OTA and latest supersu and copy to phone.
Boot I to recovery flash OTA. And supersu then reboot
I followed links in this article
https://www.xda-developers.com/oxygen-os-4-0-2-and-new-open-betas-released-for-the-oneplus-3-and-3t/
Just reflashed 4.02 and instead of SuperSU installed Magiskv10 so can say this also works
Ok guys I figured it out, it simply has been a while since I last flashed roms...
I only dirty flashed 4.0.2 zip over 3.5, then flashed supersu again.
Everything good
Thanks guys!
Question for those you you way smarter than I'll ever hope to be. I randomly lost root and TWRP on my 3T and I have no idea how this happened.
Quick (or not so quick) background - I was stock rooted OOS 4.1.6. I disabled AdAway for a bit yesterday to gain access to something it was blocking (done it many times) and when I re-enabled it my phone was stuck in a boot loop afterwards. Weird, but not concerning. I booted into TWRP and restored a backup. OOS 4.1.3 was my latest backup, so after successfully loading that up, I flashed the full 4.1.6 OTA and SuperSu as I've done before to update. Worked fine. Was adding my preferred mods via Substratum and Magisk and I messed up. Couldn't get Substratum to work properly and couldn't get Magisk to update to 13.1. I verified I had root, which I did. Went back to TWRP and reflashed 4.1.6 and SuperSU. When my phone was up and running again I didn't have root. Weird, so I tried again, still couldn't get SuperSU to flash properly. Got frustrated and figured I haven't had a clean install since getting the device in January. Every update I've flashed via TWRP has been dirty. So, factory reset, blah, blah, blah. Done it plenty of times with many devices. Flashed the OTA and SuperSu again, but noticed SuperSu failed. Rebooted recovery to try again, but it went to the stock recovery. My phone is working fine now, but I'm without root and I no longer have TWRP.
What might have caused this to happen? And how can I avoid it in the future? I know how to get it back (I'll do it after work) but it's frustrating.
What version of TWRP are you using? A few of the past versions have been having problems.
If you're already using Magisk anyways, just flash the Magisk zip and use that as your rooting solution. IIRC, the more recent versions of Magisk are no longer compatible with SuperSU anyways.
Anova's Origin said:
What version of TWRP are you using? A few of the past versions have been having problems.
If you're already using Magisk anyways, just flash the Magisk zip and use that as your rooting solution. IIRC, the more recent versions of Magisk are no longer compatible with SuperSU anyways.
Click to expand...
Click to collapse
I was using 3.0.4-1. Never had an issue before. But after I factory reset my phone and clean flashed the 4.1.6 update I ended up with the stock recovery. Unless I'm mistaken, I can't flash Magisk until I have TWRP again. I know how to get it back, I was more curious as to how this may have happened in the first place. What would have caused my root and custom recovery to disappear?
Rodeojones said:
I was using 3.0.4-1. Never had an issue before. But after I factory reset my phone and clean flashed the 4.1.6 update I ended up with the stock recovery. Unless I'm mistaken, I can't flash Magisk until I have TWRP again. I know how to get it back, I was more curious as to how this may have happened in the first place. What would have caused my root and custom recovery to disappear?
Click to expand...
Click to collapse
My mistake, I meant to ask SuperSU version, not TWRP. If SuperSU failed to root your phone after dirty flashing OOS (even if there was not error message), OOS will replace your recovery with the stock one.
Anova's Origin said:
My mistake, I meant to ask SuperSU version, not TWRP. If SuperSU failed to root your phone after dirty flashing OOS (even if there was not error message), OOS will replace your recovery with the stock one.
Click to expand...
Click to collapse
I was using version 2.8.2. Regardless, you answered my question as to how it happened in the first place, so thanks.
Can anyone help me with the steps to update to Android Oreo (OOS 5) from OOS 4.5.1 retaining root?
Below are the current setup of my phone
Rooted - Yes (Magisk version 14.0)
Recovery - TWRP version 3.1.1-2
Current Rom - Stock OOS 4.5.1
I haven't had any problems in updating earlier but now when I try to flash the full oreo rom from TWRP, I am getting error 7.
Below are the steps I followed.
Downloaded the full OTA zip.
Rebooted to recovery.
Unistalled Magisk.
Tried to flash the Oreo OTA zip. At this point TWRP showed error 7.
Reinstalled Magisk and rebooted to system.
Phone is working fine.
you need to use latest twrp for oreo, for example blue spark version, search for it on xda...
Follow this guide here:
https://forums.oneplus.net/threads/how-to-install-oos-5-0-over-rooted-4-5-1.684519/#post-17134194
It's exactly what you need.
All Oreo ROM threads clearly state under the "Instructions" heading, that you need either AkhilNarangs Modified TWRP or Blu_Sparks TWRP V50. Using stock TWRP would result in an error.
If the error may still persist, try flashing a different firmware.
Just to get some more clarity.
I have the original OTA full zip. Should I download the zip file from your thread?
Can I install the custom version of TWRP using the official TWRP app? I am bit confused on how to install it.
Is it important that I should use Magisk 14.3 or will v 14 have the same effect?
Hey there,
I can tell you how I have done it yesterday (successfully).
1. Update TWRP - I prefer blu sparks version 8.52 (Link: https://forum.xda-developers.com/devdb/project/dl/?id=27225); you can do it by using your installed TWRP Version (Install .img)
2. Dirty flash OOS 4.5.1 again (to remove root / magisk) - once finished DO NOT reboot into system, reboot into Recovery/TWRP to verify the new version and afterwards to system
3. flash OOS 5.0 (Oreo) - dirty flash is okay
4. flash magisk Version 14.3
These are the steps I have followed yesterday and all is running perfect and without any problems.
BR
Which recovery is mentioned in this linked discussion resp. in the linked download? Is it blu_spark TWRP?
Regards
Clark
This worked perfectly for me.
Glad to hear that everything is good ?
I did the same and I was suddenly encrypted and no chance to get my data back. Still forcing clean my phone because I cannot format the device. I get always an error message in TWRP like: unable to format to remove encryption
I go crazy...
Enter recovery and wipe data and then cache.
Then reflash the rom and probably you will be good to go.
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.