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
Related
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?
I've always used SuperSu on my previous devices. I just got my OP3T about a month ago. I was running SuperSu until I got the OOS 4.5 update 2 days ago. I did a full wipe and started from scratch. I decided to try Magisk. So far it's been awesome. Stock ROM.
I've been trying to search for an answer but haven't found a clear one.
I want to upgrade to a custom kernel. Franco to be exact. I want to be able to use DriveDroid, and I've read that this kernel enables the functionality it needs.
Will I lose AndroidPay and other non root features / break Magisk by flashing a new kernel? What do I need to do? Is there any prep, or can I just flash it and be good to go?
Just flash the kernel first and then the latest magisk zip and your good to go.
spotopolis said:
I've always used SuperSu on my previous devices. I just got my OP3T about a month ago. I was running SuperSu until I got the OOS 4.5 update 2 days ago. I did a full wipe and started from scratch. I decided to try Magisk. So far it's been awesome. Stock ROM.
I've been trying to search for an answer but haven't found a clear one.
I want to upgrade to a custom kernel. Franco to be exact. I want to be able to use DriveDroid, and I've read that this kernel enables the functionality it needs.
Will I lose AndroidPay and other non root features / break Magisk by flashing a new kernel? What do I need to do? Is there any prep, or can I just flash it and be good to go?
Click to expand...
Click to collapse
Android Pay should be affected by Magisk, not by the custom kernel.
And since you say that u had custom kernels before, you should already know that the installation of custom kernels doesn't affect the root.
Unleashed by ONEPLUS 3T rooted
Magisk hide will allow you to use Android Pay, it'll be in the settings.
Root will still work great too, I've used it for ages, never had an issues.
RASTAVIPER said:
Android Pay should be affected by Magisk, not by the custom kernel.
Click to expand...
Click to collapse
If the kernel is not prepared to hide boot flag, then it'll definitely affect SafetyNet.
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.
Hello all,
so I have a op3t with SuperSU. I was wondering when the android P update comes out eventually will I be able to OTA update and keep root, or will I have to reflash SuperSU(Using temp TWRP environment).
bradcubed said:
Hello all,
so I have a op3t with SuperSU. I was wondering when the android P update comes out eventually will I be able to OTA update and keep root, or will I have to reflash SuperSU(Using temp TWRP environment).
Click to expand...
Click to collapse
You will definitely have to reflash SuperSU.
Sent from my OnePlus 3T
BillGoss said:
You will definitely have to reflash SuperSU.
Click to expand...
Click to collapse
What he said. That goes for most updates of most Android devices (need to root again after an update).
Further, a new Android build (particularly a major update, like Oreo to P) will often require updated root methods. Since SuperSU development is basically dead, it may not work on Android P. You may need to move to Magisk root method (not a bad thing).
Best way to apply updates on rooted 3T, is to get it from the following thread and basically follow the install instruction for root users on Post #3 of that same thread:
https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
I would also advise to backup your data before updating, as a clean install (wipe data) is not unheard of (possibly even recommended), when installing major updates.
Note that failure to flash Magisk/SuperSU after applying the update, will not only cause you to lose root, but also lose TWRP (will be overwritten by stock recovery if you reboot before flashing a root file or alternately a modified kernel).
I installed Magisk with a patched image on a Pixel 4. This process appears to always patch boot.img with the latest version of Magisk. Is there any way to patch an image with an old version of Magisk? Specifically I'd like to install 21.2 (coming from 21.4).
If not, I assume I need to install a custom recovery to downgrade to an older version?
I'm assuming you mean that you want to downgrade from 21.4 to 21.2. You have a couple of possibilities actually.
You could setup your own custom update channel with the Magisk zip of your choice. I've described that here:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84290797
But since you want to use the stable releases you can find the old update channel in Github's commit history. It takes a little bit of insight into how Github works though... I've had plans to write down the steps required in my Magisk guide for ages, but somehow I never get around to it.
Using this as your custom update channel would give you Magisk v21.2:
https://raw.githubusercontent.com/topjohnwu/magisk_files/d10a630a4d4a3c54cf57abc7411f698f0ff79161/stable.json
If you want to use TWRP you do not need to install it though. It's perfectly possible to boot TWRP without having to install it:
fastboot boot twrp.img
Keep in mind that no official support is given for old releases...
Excellent. That worked!
I ask as the instructions seem to imply that installing from recovery is a thing of the past. Is that just for certain devices?
Any difference with using the custom channel to do a direct install vs patch for downgrades?
amw2320 said:
Excellent. That worked!
I ask as the instructions seem to imply that installing from recovery is a thing of the past. Is that just for certain devices?
Any difference with using the custom channel to do a direct install vs patch for downgrades?
Click to expand...
Click to collapse
If there is a custom recovery available for your device it's very often a viable option for installation. But, as it says in the instructions, it may fail and patching the image may be your only option. Boot image patching or the direct install option are the recommended methods (since there it's possible for @topjohnwu to control exactly what's going on).
Once you have Magisk installed already it's generally recommended to use the direct install option, but since Android is Android and there are way too many different setups out there to even count there is going to be instances where the direct install fails and patching a boot image is needed, or even that installing through recovery is the only option.
There's no practical difference between direct install and patching the image manually. The only difference is in who's doing the flashing of the image (you or the Manager).
You've got a Pixel device, so you should be good on all accounts. @topjohnwu uses his Pixel devices to test a lot of stuff with Magisk and they'll pretty much always be fully supported.
Thanks, super useful