Database Develop

Root OnePlus 3T running 7.1.1 Android Nougat and Oxygen 4.1.1.

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?

N950F Exynos how to root Oreo please?

Good Morning,
I have a carrier unlocked Australian N950F Exynos Note 8 running 7.1.1 with OEM Unlock showing in developer settings (took a week or so). My phone has downloaded but not yet installed this OTA:
N950FXXU3CRC7/N950FOLN3CRC7/N950FXXU3CRC7 (1021.03MB)
I think it'll be Oreo but I haven't checked which exact version.
I have not installed TWRP or rooted this phone yet but I'd like to do so. I'd also like to move to Oreo before I proceed as my battery life could be better.
What is the best way to proceed? I've read through some long threads and ended up confused about exactly what's the best procedure.
Is some kind or decryption required at some point? Will I lose the data currently on my phone?
I haven't installed the OTA update yet.
Thank you.

CRC7 is Oreo, 8.0 which is currently the latest for Note8 (8.1 may be a long while out if we even get it officially).
The process for rooting Oreo is basically the same as Nougat, for Oreo just be sure you are using the updated TWRP that fixes the data mount issue.
If you root Nougat first, you won't be able to update OTA so you'll then need to install a custom rom to get Oreo.
You can update to Oreo via OTA first & your data will be intact but regardless if Oreo or Nougat, after installing TWRP you'll need to wipe data to remove encryption. So yes, you will loose data. You won't loose internal or external storage unless you choose to format them but it's a good idea to make a backup of them just in case.
As for data, you'll need to use smart switch, helium, etc if you want to back it up. I have no experience with backing up data without root so I'm not sure what methods work best.

It seemed to work. I restored all my contacts, apps etc in Oreo. When I went to restart the phone and enter TWRP to flash magisk I get a message about only official binaries are allowed. Now the phone won't even boot. I'm guessing I now need to re-flash official firmware with odin just to get my phone working? Another week for OEM unlock? I waited this long because I thought the problem was resolved

Unfortunately if you have the OEM lock issue, that will never go away. So yes, you have to flash official firmware to boot again. If you were on Oreo, you can try flashing Nougat to see if you might get lucky & get OEM unlock back.
Since you have the OEM lock issue, remember to always flash the RMM state fix even if you flash a custom rom that has the fix built in. Always flash RMM fix right after flashing a custom rom. If not flashing a custom rom, flash RMM fix before booting to system after you install TWRP.

Thanks for the reply.
Was I supposed to install Samsung AntiRoot Removal and RMM State Bypass as per this guide? Is this guide the correct method?
galaxynote8root.com/galaxy-note-8-root/how-to-root-galaxy-note-8-on-android-8-0-oreo/
I'm currently downloading Oreo 8.0 XSA (unbranded Australian rom) to reload my phone and wait another week.
I would like to use the XSA Samsung rom rather than a custom rom. Is OEM Unlock available in Oreo after a week?
Thank you

I use the method listed in any of the TWRP threads. I've never heard of Samsung Anti Root Removal. By the sound of it on the page it sounds like dm no verity. You need to flash that & RMM state fix. Flash the XSA firmware you want to use. Log into your Samsung account, don't reboot for 168hrs & OEM unlock should appear. Then follow a guide for installing TWRP.

PLEASE help with annoying A6 & magisk problem

Firstly, I apologize if this is posted in the wrong place and topic has been covered before, but I really need your help!
I got the A6 brand spanking new 4 days ago, and have managed to flash TWRP (TWRP-3.2.3-TwrpBuilder-a6ltexx-2018-11-26_20-43.tar) successfully and get RMM-State_Bypass_Mesa_v2.zip, Magisk-v18.0.zip & no-verity-opt-encrypt-6.0.zip (in that exact order) and I thought was all good.... BUT here lies the problem, after I have flashed the above files, I need to update Magisk to the latest version to be able to use the Magisk Hide & Superuser functions.. Whenever I have updated Magisk, either by direct install or download only then install in TWRP, it makes the phone reboot at random intervals..
it can be hours between reboots or it can be minutes, it goes blank and restarts from the android boot animation, where I have to enter my pins to be able to use it again.. WHY is Magisk causing this random reboot and how can I fix it??
Ive re-flashed the A600FNXXU3ARL1_A600FNOBE3ARL1_EVR (Android 8.0.0) a good few times now, but this random reboot bug Isn't present since I flashed it back to stock..
Also, a separate question; WHY are certain android apps refusing to run due to phone being rooted?? I thought once you re flash official stock firmware the phone appears "warranty intact"?
I used to be up-to-date with android rooting & modifying back in the day, but I have been out of the loop for a long time.
Thanks for your patience reading this and thanks in advance for any help/answers/time taken by me.
Arty.

Magisk on Oreo doesn't work well if you don't have the one with anti defex version as the kernel keeps avoiding you to use superuser commands as part of security feature even after rooting.
About the stock apps refusing to work after flashing the stock rom, you already tripped knox while flashing twrp which once gone you won't be able to turn back. But flashing a custom kernel would fix such problems most of the time.

henok.gk said:
Magisk on Oreo doesn't work well if you don't have the one with anti defex version as the kernel keeps avoiding you to use superuser commands as part of security feature even after rooting.
About the stock apps refusing to work after flashing the stock rom, you already tripped knox while flashing twrp which once gone you won't be able to turn back. But flashing a custom kernel would fix such problems most of the time.
Click to expand...
Click to collapse
Thank you for your reply!
How do I get said anti defex version? Ive tried googling it but only found unrelated results, could you please point me in the right direction in how to proceed please? thanks
Arty.

I can't point you a direct link with a magisk version you need to flash to get rid of defex. If you're lucky you may get a custom kernel built including it. Try one of the oxygen/phoenix kernels through this A6 thread.
The kernels will also help you byass all knox security related stuff which in turn will help most stock apps get back to working state expect for samsung pay and secure folder.

Help getting root access on the Note 9

Hi all,
I have been trying to root my phone since this last saturday and have been unable to do it successfully. I am using TWRP recovery to install Magisk. I have tried it with the RMM bypass and the no verify too. I have tried it with RMM and no verify flashed and I have tried it without. I also tried Dr. Magens package and still the same issue. I noticed my device was running really slow and got extremely hot when I tried this way.
On one of my attempts I got, "Only official binaries are allowed to be flashed" When I went into download mode it said KGG state prenormal and my warranty was void, I think I tripped Knox. I did the RMM flash and these messages went away and I reflashed to stock android now I am looking to start over again
I flashed back to stock andriod and some people say you have to wait 7 days but I still have the OEM unlock option ticked. I would really like to root my phone.
I have an Imgur link but i have a new account so i cant post links. Please pm me or I will see if I can put it in the comments.
Any links or tips or anything is greatly appreciated.
Device info since i cant post links:
Model: SM-N960F
Android Version 10
Kernel Version 4.9.118-17594460
Knox Version 3.4.1 API level 30
Security patch level: 01/01/2020
Do I need to flash a custom ROM once i have TWRP installed or do you guys have any links or recommendations? I have tried following 5 different tutorials on the internet and so far none have worked

Im a goober
If anyone reads this i was not flashing a ROM before flashing these files so I was just flashing the Magisk application I think but since i didnt flash a rom it just overwrote it with the factory rom and bricked my device. I reflashed back to stock via odin then flashed again with OneUI and it went fine very easy

Hello
Patch file "APxxxxxxx" in Magisk manager v7.5.1
And with Odin 14 flash rom with magisk_patched in AP and add CP, BL, CSC_xxx
Work fine
https://forum.xda-developers.com/galaxy-note-9/how-to/guide-root-note-9-magisk-android-10-q-t4039783

Stock MIUI flash (from MiFlash) gives me ctsprofile False

I was having trouble getting cts profile = true on Pixel Experience ROMs and someone gave me a vbmeta to flash...now I have ctsprofile - true on Pixel Experience ROMS but even after doing a full stock flash on MiFlash, stock MIUI gives me ctsprofile - FALSE...Any ideas on how I can fix this issues,? Thanks in advance!

Because you have a unlocked bootloader lol. Good custom roms like PE and eu.miui do some sweet trickery to fix this. Only way to fix is relock bootloader on stock rom or root and use magisk hide and see how Google is feeling today.

hoopsnake said:
Because you have a unlocked bootloader lol. Good custom roms like PE and eu.miui do some sweet trickery to fix this. Only way to fix is relock bootloader on stock rom or root and use magisk hide and see how Google is feeling today.
Click to expand...
Click to collapse
As far as I know, this is untrue, as before, i switched from PE to MIUI and still had SafetyNet check out. This time, I flashed a patched VBMeta someone sent me though, which could have caused the issue.

There's too many variables involved, was this before March? What build? What did you wipe in twrp? Root?
Having a unlocked bootloader on all devices on stock rom as of March fails safetynet end of story.
"John Wu has shared more details on the change on Twitter. He confirms that MagiskHide will continue to conceal root, but it might soon not hide the fact that your bootloader is unlocked anymore, since that's what SafetyNet checks for. Other than that, he expands on why he doesn't see a way around Google's new implementation"

hoopsnake said:
There's too many variables involved, was this before March? What build? What did you wipe in twrp? Root?
Having a unlocked bootloader on all devices on stock rom as of March fails safetynet end of story.
"John Wu has shared more details on the change on Twitter. He confirms that MagiskHide will continue to conceal root, but it might soon not hide the fact that your bootloader is unlocked anymore, since that's what SafetyNet checks for. Other than that, he expands on why he doesn't see a way around Google's new implementation"
Click to expand...
Click to collapse
Nope, got this phone only in April...I wiped everything in TWRP. The thing that changed is when I tried to boot PE and got DMVERIFY issues and couldnt get past the Mi boot screen, installed a patched VBMeta and now PE has CTSPROFILE TRUE and MIUI doesn't

I reflashed stock and locked my bootloader and as was said before, it now has ctsprofile true. Sadly, now anytime i unlock my bootloader, cts fails.

You shouldn't need to do that, PE boots fine without DM Verity, disable force encryption and vbmeta. All you do is format data, reboot recovery, wipe everything then immediately flash rom and reboot. Anyway when you flash fastboot rom vbmeta is replaced, I wouldn't mess around with that. The Google cts fix is coming very soon it'll fail on all custom roms so if it's that important for you then stock recovery locked bootloader is the only way.