Hello all.,,
I checked and read many thread slowly and steadily ,but couldn't find a good solution to root this phone 3T.
I just bought this Beautiful Device runing so smooth but with Hands tied too hard unable to run many apps and many ads and Bloatwares..
Thought to Root this device ,but all are mostly either Oxygen 3 or Marshmallow or 7.0. Version of ANdroid..and DW Error,is also a major concern to look out..
So Please help me to root this device running O2 4.1.1 (I literally dont want to change the stock,as of now) and Android 7.1.1 ,some simple steps...
Thanks and Regards
Awaiting for replies!!
I'm about to get this phone so I've been doing a lot of research myself. It looks like you can follow the steps in this thread and you can flash supersu through TWRP once you've unlocked the bootloader.
Unlock bootloader.
Flash TWRP.
Flash your preferred root zip in TWRP (SuperSU or Magisk are two good choices, I prefer Magisk).
That's about it...
i too tried the above method,,But I got struck with Logo of TWRP and got enabled only after 6 Hours.. But to my fate,,i'm still running on Stock recovery.. Not on TWRP !!
Use the latest official TWRP (currently 3.1.0-1). Works just fine.
i can relate to your question.
however, i discovered how to root the 3t and flash the usual zips files the finally the freedom rom, on my own.
it was a thrill.
i advise you to just take the blue pill.
I installed Blusparks Version of TWRP ,,but still no use,,SuperSU or Magisk both says My phone is not rooted!!!!
I want to live the Stock ROM and just to root the device,,But the steps are not futile for me!
What I would do if i was you.
Unlock bootloader
Flash TWRP
Flash latest Magisk 13.2 zip
Hey,
Is this method still valid for rooting the 3T?
https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.475142/
Yes, that is still valid, more or less. Might be a more current version of blue_spark's TWRP (official TWRP is on 3.1.1.2) although the link only says 3.1.1-x, so I don't know what that means. But probably won't make a huge difference.
Can't see what version Magisk is linked (my office network is blocking the link). If you choose Magisk, flash latest version 13.3, especially if you want to hide root (from Snapchat, banking apps, etc.). Older versions of Magisk will fail to hide, due to recent changes Google made to SafetyNet.
And what if we want to flash this beta to a brand new device?
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_12/
Should we first unlock the device, then install the TWRP recovery, then flash this beta rom and then root?
Hello dear community. Today, i just recieved my OP3T and I am super happy. Since I am a manian with new android versions + root + xposed, what i did is charge my new device and then start experimenting.
Firstly, i used this tool (https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729) to unlock bootloader, flash TWRP.
Then I used some VPN to change my location to Canada, and get the Oreo OTA.
Oreo OTA replaced TWRP, so I did some research to find out if its safe to reinstall TWRP 3.1.1, but i stumbled uppon some contradicting opinions both for TWRP and for Root. In the guides I read, some users commented that it might be very dangerous to either reinstall TWRP and/or supersu, so since I am not a guru, and my technical knowledge is kinda limited, I thought I'd create this thread before doing something stupid.
So, is it safe to reinstall TWRP in the latest Oreo OTA? (ONEPLUS A3003_28_171116)? Which version of TWRP do you suggest?
Is it safe to use the latest supersu?
Also, should i do a factory reset after the update?
I know for sure that xposed is not available for Oreo, so I wont be asking anything for it here.
Thanks in advance!
For Oreo, the latest TWRP is not recommended. You need the bluspark TWRP for Oreo. Here is the link. https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Careful, there are two Bluspark TWRP, one for nougat and one for Oreo. Also it is unified for both op3 and op3t
I do not know about SuperSU but the beta version of Magisk works on Oreo. The stable version does not work yet. Here is the link for beta https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
I am using the beta Magisk and BluSpark TWRP atm. It works fine. I did a clean flash using the full Oreo zip file (1.5gb). I think you can find this as a download on the XDA forum since OnePlus has not put it online yet. DO NOT CLEAN FLASH THE PARITAL OTA.
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.
I need to get something straight, as I didn't quite get it. So the options for someone who'd like to root his S10 are 3:
1) Rooting with Topjohnwu method: This will get you root on the stock rom, but will keep the default recovery which is pretty much useless if one wanted to flash a custom rom.
2) Rooting with a prepatched version of TWRP and then, if desired, flash any custom rom (compatible with the TWRP version installed). This method is said to be less stable that the previous one.
3) Install TWRP after rooting with john wu method and then using it to flash custom rom.
First of all, is all this correct?
If so, then one has to choose between rooting safely, but keeping his phone stock, or rooting and then installing twrp and then flash whatever he desires.
Hopefully, somebody will be so kind to clarify this that is an unusually complicated situation about rooting this phone! I already regret passing my perfectly rooted S9 to my son
Thanks for whatever help you'll be willing to provide.
Cheers
I would say you summoned it up nicely.
The advantage of stock Magisk root is you can e.g. use Substratum, Magisk modules and update monthly security releases by yourself but, of course, no Custom ROMs.
The advantage of TWRP Magisk root is clearly the Custom ROM possibility but here you cannot update the monthly security releases by yourself and are dependent on the ROM creator to release the security updates.
I had been using Topjohnwu Magisk root on stock rom since released mainly to use Substratum/ some Magisk Modules and did the AP-patching everytime the monthly security was released.
However, doing the November security AP-patching something went wrong and I ended in boot-loop. So thought, as I had to reflash anyway I would try TWRP/ Custom ROM - I went with yash92Duster's lightrom / geiti94's magisk TWRP both which I find very stable.
Norup58 said:
I would say you summoned it up nicely.
The advantage of stock Magisk root is you can e.g. use Substratum, Magisk modules and update monthly security releases by yourself but, of course, no Custom ROMs.
The advantage of TWRP Magisk root is clearly the Custom ROM possibility but here you cannot update the monthly security releases by yourself and are dependent on the ROM creator to release the security updates.
I had been using Topjohnwu Magisk root on stock rom since released mainly to use Substratum/ some Magisk Modules and did the AP-patching everytime the monthly security was released.
However, doing the November security AP-patching something went wrong and I ended in boot-loop. So thought, as I had to reflash anyway I would try TWRP/ Custom ROM - I went with yash92Duster's lightrom / geiti94's magisk TWRP both which I find very stable.
Click to expand...
Click to collapse
One more doubt, if I may ask : once rooted the safe way, if I wanted to install twrp I would need to find the build that is compatible with the already patched firmware on my phone? And then only the roms that are exactly for the same build?
This is the most complicated rooting process that I have ever faced. And I've been rooting my phones and tablets since a very long time
Thanks
Hello,
I have a One Plus 5 with a Custom AOSP Rom 11.0 and TWRP 3.4.0.1 and I'm trying to install Magisk like it's explained here.
But whatever I try - it does not work.
When I flash it via TWRP it says everything went well, but in the end my Magisk Manager does not have the "green ticks" and my apps say I have no root access.
I also tried this with my current ROM but there is an error. I'll attach all logs and files in case it's helpful.
Thank you very much.
Edit:
I was now able to create a flashed boot.img file, but when I flash that it always boots into the bootloader and cannot boot my phone anymore normally anymore.
Quite simple... Magisk v20.4 isn't compatible with Android 11. Currently you need to switch to the beta update channel if you want root on A11.
Didgeridoohan said:
Quite simple... Magisk v20.4 isn't compatible with Android 11. Currently you need to switch to the beta update channel if you want root on A11.
Click to expand...
Click to collapse
Awesome thank you... A little bit embarissing since I spend so much time before but thank you very much