Database Develop

How to root 3T on OOS4.0 ?

Hey,
I bought my phone 2 days ago, after charging it I updated to OOS4.0 through the system updates using VPN, when I got home I unlocked the bootloader but did nothing else afterwards. I'm seeing a lot of threads with people having issues with TWRP and encryption, considering my last device was the OPO and I was running Lollipop (was too lazy to update it ) I'm kinda out of the loop.
How can I root it now that it's running Nougat ? simply flashing the twrp img using fastboot and then flashing the SuperSU zip or is there a different method ?
Any kind of help is greatly appreciated.
Also, one more question, is Xposed working on Nougat ? I had quite a few useful modules on my OPO, wanted to know if that's possible on the 3T as well.

The beta builds of the TWRP which are compatible with the OOS 4.0.0 are available. You can find them from the thread.
If you want to use the Xposed modules, you should downgrade to 3.5.4.

WeirdSoup said:
The beta builds of the TWRP which are compatible with the OOS 4.0.0 are available. You can find them from the thread.
If you want to use the Xposed modules, you should downgrade to 3.5.4.
Click to expand...
Click to collapse
And where should I download SuperSU from ? Heard the project is being taken over or smth like that

B00steed said:
And where should I download SuperSU from ? Heard the project is being taken over or smth like that
Click to expand...
Click to collapse
http://www.supersu.com/download
Actually, I'm using the Magisk instead. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

WeirdSoup said:
http://www.supersu.com/download
Actually, I'm using the Magisk instead. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Is it better to install this instead of SuperSU ?

If you are interested in using apps which detect root or a modified system/bootloader (Android Pay, Pokémon Go, some banking apps) then yes. Otherwise, no benefit of Magisk (v10.2) for you and may as well use SuperSU which is simpler to install.

B00steed said:
Is it better to install this instead of SuperSU ?
Click to expand...
Click to collapse
It's case by case, and I don't know which one is good for you. Do some research and figure out yourself.
---------- Post added at 11:30 AM ---------- Previous post was at 11:24 AM ----------
23Six said:
If you are interested in using apps which detect root or a modified system/bootloader (Android Pay, Pokémon Go, some banking apps) then yes. Otherwise, no benefit of Magisk (v10.2) for you and may as well use SuperSU which is simpler to install.
Click to expand...
Click to collapse
Magisk is open source, and it is also easy to install. You can also install the Magisk modules. It's not a simple root-hide app as many people still misunderstand.

So, with oxygen 4.0.1 the procedure will be the same?

TWRP Stuck Mount password
Greetings guys..
Yesterday I got my 3T and upgraded OTA latest OxygenOS 4.0.1. I was able to unlock bootloader and install TWRP 3.0.3 but when I access bootloader the first screen ask me to provide "Decrypt password" to mount, and if I ignore and slide to start modification I don't have access to internal card (assume its READ-ONLY), just folders are visible but unable to find or install SU package.
I check all the forums but didn't find any relevant information how to get out of TWRP "Decrypt password" issue. I don't want my phone to be encrypted, so I would appreciate if you can please help me to root my 3T.
Cheers

junostik said:
Greetings guys..
Yesterday I got my 3T and upgraded OTA latest OxygenOS 4.0.1. I was able to unlock bootloader and install TWRP 3.0.3 but when I access bootloader the first screen ask me to provide "Decrypt password" to mount, and if I ignore and slide to start modification I don't have access to internal card (assume its READ-ONLY), just folders are visible but unable to find or install SU package.
I check all the forums but didn't find any relevant information how to get out of TWRP "Decrypt password" issue. I don't want my phone to be encrypted, so I would appreciate if you can please help me to root my 3T.
Cheers
Click to expand...
Click to collapse
I think you need latest twrp beta 1, it should be in twrp tread, look in last pages or here https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074

bertozzi243 said:
I think you need latest twrp beta 1, it should be in twrp tread, look in last pages or here https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
Click to expand...
Click to collapse
Thanks for quick reply, I'll check it.

bertozzi243 said:
I think you need latest twrp beta 1, it should be in twrp tread, look in last pages or here https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
Click to expand...
Click to collapse
Installed TWRP 3.0.3.1 BETA .... How long does it really take to decrypt new phone without any apps? Just to have an idea. When I started TWRP it asked for password and I used the PIN assigned to login to screen ... now going on for 5 minutes now.
Following on the screen:
Mount
Try Decryption
Updating partition details...
....done
Unable to mount storage
Full SELinux support present
---------blue animation-----------

junostik said:
Installed TWRP 3.0.3.1 BETA .... How long does it really take to decrypt new phone without any apps? Just to have an idea. When I started TWRP it asked for password and I used the PIN assigned to login to screen ... now going on for 5 minutes now.
Following on the screen:
Mount
Try Decryption
Updating partition details...
....done
Unable to mount storage
Full SELinux support present
---------blue animation-----------
Click to expand...
Click to collapse
I read that it takes some minutes if you are f2s and encrypted but I don't know how to proceed since I haven't flashed twrp and root yet.
Sorry but you may have to wait someone who has already done it

OP3T Locked Bootloader Stock Rom Safety Net still fails

Hey there!
I wanted to use my banking app, so I decided to get full to stock. Before I used OxygenOS Beta 20 with Magisk.
Currently:
Stock Recovery
OxygenOS Beta 20 or OxygenOS 5 (Same Problem)
Locked Bootloader
Now with a clean OS Safety Net still fails and the Google Play Store says "not certified".
Do you have any tips to get it working again?

kaisims said:
Hey there!
I wanted to use my banking app, so I decided to get full to stock. Before I used OxygenOS Beta 20 with Magisk.
Currently:
Stock Recovery
OxygenOS Beta 20 or OxygenOS 5 (Same Problem)
Locked Bootloader
Now with a clean OS Safety Net still fails and the Google Play Store says "not certified".
Do you have any tips to get it working again?
Click to expand...
Click to collapse
Did you flash all partitions (boot, recovery, cc system) including data, full wipe, before locking boot loader?
Sent from my Nexus 6 using Tapatalk

ben_pyett said:
Did you flash all partitions (boot, recovery, cc system) including data, full wipe, before locking boot loader?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
As far as I know, Yes. I know it doesnt make much sense.

I'd suggest that you unlock bootloader and then reflash, do a full wipe to be sure
Then lock again if that's the way you want to go
Sent from my Nexus 6 using Tapatalk

ben_pyett said:
I'd suggest that you unlock bootloader and then reflash, do a full wipe to be sure
Then lock again if that's the way you want to go
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Did that again now, but its still failing sadly.

kaisims said:
Did that again now, but its still failing sadly.
Click to expand...
Click to collapse
Try using unbrick guide if that is feasible for you. That way the error is reproducible if you still get it after the "unbrick" guide since all your partitions will be the same as ours.

Unlocked bootloader and Magisk by themselves shouldn't trip Safety Net, as long as you have Magisk Hide working. Now, that doesn't mean your specific banking app isn't doing other checks besides Safety Net (I think folks have seen this happen with some apps). But you mention Safety Net failing specifically, so I thought that worth mentioning.
Did you use the full update zip to get back to "full stock"? That would be the recommended approach, to make sure all partitions were returned to stock.

redpoint73 said:
Now, that doesn't mean your specific banking app isn't doing other checks besides Safety Net
Click to expand...
Click to collapse
Exactly that was the problem in the first place, why I started to lock my bootloader again. And yes I always had the full OS as a zip.
ZVNexus said:
Try using unbrick guide if that is feasible for you.
Click to expand...
Click to collapse
I used this: https://forums.oneplus.net/threads/guide-oneplus-3-3t-unbrick.531047/ unbrick guide and that worked!!
I am so happy!

kaisims said:
Exactly that was the problem in the first place, why I started to lock my bootloader again. And yes I always had the full OS as a zip.
I used this: https://forums.oneplus.net/threads/guide-oneplus-3-3t-unbrick.531047/ unbrick guide and that worked!!
I am so happy!
Click to expand...
Click to collapse
Yep, figured. Had to be some partition.

[OxygenOS Pie] Closed Beta *** Leaked build available ***

Finally they made it real!! Closed Beta is now opened for Oneplus 3/3t owners
If you want to be part of this beta testing, follow this link: https://www.xda-developers.com/oneplus-3-3t-closed-beta-oxygenos-9-android-pie/
IMPORTANT : Use leaked builds at your own risk
Download
(OP3 OnePlus3Oxygen_16_OTA_073_all_1903190037_c3d5b3a79f9b4895.zip)
(OP3T OnePlus3TOxygen_28_OTA_073_all_1903190038_308835b6760c41bd.zip)
Instructions (Read carefully)
* Flash through TWRP (by @dianlujitao) and do a Factory Reset before boot the device (source)
* Your device will became encrypted during boot (data partition may be corrupted on encrypted devices)
* magisk v18.1 is working
(source)
* Stock recovery will overlap TWRP unless you flash magisk before reboot.
Bugs:
None so far...
Thanks for initial testers:
@Chuck Bartowski
@himsin

Sounds amazing, waiting to see the final version coming out

FSadino said:
Finally they made it real!! Closed Beta is now opened for Oneplus 3/3t owners
If you want to be part of this beta testing, follow this link: https://www.xda-developers.com/oneplus-3-3t-closed-beta-oxygenos-9-android-pie/
Click to expand...
Click to collapse
How will I know of I get selected for closed beta testing?? And when will close beta be available for testing

alrd apply hope this early appril can roll out

Closed beta pie for op3/t leaked

helderfp said:
Closed beta pie for op3/t leaked
Click to expand...
Click to collapse
Where?

helderfp said:
Closed beta pie for op3/t leaked
Click to expand...
Click to collapse
and why do you think that?

abhibnl said:
and why do you think that?
Click to expand...
Click to collapse
Because i download the rom from a leaked link

helderfp said:
Because i download the rom from a leaked link
Click to expand...
Click to collapse
Can you share a link via PM?

abhibnl said:
While I won't ask you to post a leaked build, can you post some SS running that ROM and showing this thread in XDA app to show that you are not just joking around and have actually used the ROM?
Or you can download AIDA64 and post SS from that app.
Click to expand...
Click to collapse
Review from techibee
https://www.youtube.com/channel/UCAL31QQ9hsw8utl2GSgOchg

jay_snake said:
Where?
Click to expand...
Click to collapse
https://yadi.sk/d/Dj_6zddVg5-yog

Thread cleaned
Link restored
Please see rule 12
XDA has been the place to find leaked builds since there were leaked builds
Thank you for your cooperation

Does it work as a daily driver or still too buggy?
(he said, before inevitably rushing to install it)

helderfp said:
Review from techibee
https://www.youtube.com/channel/UCAL31QQ9hsw8utl2GSgOchg
Click to expand...
Click to collapse
Appreciate it. I'll find and download it to test it over weekend.

Thanks for the build!
Any way to decrypt?
I tried flashing Magisk (18.1) after flashing the ROM but it didn't work.
I also tried flashing Magisk + Universal DM-Verity ForceEncrypt disabler (https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389) but that gave me a bootloop.

To everyone who will rush to flash it - please don't just download and flash. Make sure you are ready for broken device, storage encryption and decryption errors, and data errors.
Make sure to take a complete backup of internal storage and then attempt to flash it using stock or twrp recovery.
Or you should rather wait til a developer figures out a way to make twrp compatible with its firmware for encryption/decryption errors

Just flash it and do a factory reset before booting rom. That will do the trick. My phone was decrypted and first boot took around 15 mins and encrypted phone.
BTW anyone tried if magisk is working on closed beta?

himsin said:
Just flash it and do a factory reset before booting rom. That will do the trick. My phone was decrypted and first boot took around 15 mins and encrypted phone.
BTW anyone tried if magisk is working on closed beta?
Click to expand...
Click to collapse
Magisk is working, I'm now using the closed beta with Magisk 18.1.
At first boot Magisk Manager (the application) was not installed and I had to install it manually. Also, Magisk Manager was saying that Magisk was not installed, but a reboot solved it. Now it is working perfectly.
And, if you were responding to me, I'm sorry I wasn't very clear, I wanted to keep the phone decrypted (disabling force encrypt at first boot), but I have failed and I'm using the phone encrypted at the moment.

I just installed it via stock recovery with locked bootloader... Everything is fine..

himsin said:
Just flash it and do a factory reset before booting rom. That will do the trick. My phone was decrypted and first boot took around 15 mins and encrypted phone.
BTW anyone tried if magisk is working on closed beta?
Click to expand...
Click to collapse
Did you used stock or TWRP recovery?

Root galaxy S10 (July security patch update)

hi to all, has anyone managed to root on galaxy s10 with the July security patch update? I tried the same method with magisk but there is nothing to do, every time it gives me a different error. In the last attempt I made during the boot phase, in the upper left corner, it was written: "only official released binaries are allowed to be flashed" or something like that.

You didnt do it right. I would suggest youtube the magisk rooting process

Same tried to root it
I, was able to get it to root but the camera still makes my device rebooted
And tried to do it with ap file by changing recovery inside to the patched twrp that didn't work just booted into stock recovery instead

Cristian-104 said:
hi to all, has anyone managed to root on galaxy s10 with the July security patch update? I tried the same method with magisk but there is nothing to do, every time it gives me a different error. In the last attempt I made during the boot phase, in the upper left corner, it was written: "only official released binaries are allowed to be flashed" or something like that.
Click to expand...
Click to collapse
I have already tried EVERYTHING, in download mode I can not get the> Prenormal <to> Check ing <. The option of OEM lockdown is there, has always been there.

TheUndertaker21 said:
Same tried to root it
I, was able to get it to root but the camera still makes my device rebooted
And tried to do it with ap file by changing recovery inside to the patched twrp that didn't work just booted into stock recovery instead
Click to expand...
Click to collapse
TWRP ≠ Root.
With the latest patch the camera crashes if TWRP is flashed. With stock recovery everything should work fine.
I'm on Exynos ASG8 without any issues, except slow wifi in apps (not browser).

Jannomag said:
TWRP ≠ Root.
With the latest patch the camera crashes if TWRP is flashed. With stock recovery everything should work fine.
I'm on Exynos ASG8 without any issues, except slow wifi in apps (not browser).
Click to expand...
Click to collapse
OH that's a known issue then?
I need my custom rom and twrp lol

TheUndertaker21 said:
OH that's a known issue then?
I need my custom rom and twrp lol
Click to expand...
Click to collapse
It is...nearly everytime Samsung throws out a new security patch TWRP is crashing the camera.
This is what I found out after having the same issue. I don't know if there's a new version for the latest patch.
Aren't the custom roms based on One UI? Shouldn't the stock recovery still work? (I really don't know)

Jannomag said:
It is...nearly everytime Samsung throws out a new security patch TWRP is crashing the camera.
This is what I found out after having the same issue. I don't know if there's a new version for the latest patch.
Aren't the custom roms based on One UI? Shouldn't the stock recovery still work? (I really don't know)
Click to expand...
Click to collapse
TWRP is good to have if something goes wrong.
I can have custom rom without twrp but that's not the whole of it.
Hope it gets patch soon

TheUndertaker21 said:
TWRP is good to have if something goes wrong.
I can have custom rom without twrp but that's not the whole of it.
Hope it gets patch soon
Click to expand...
Click to collapse
It's easy to flash it, even without running system.

Hi everyone, I'm still ASD4 and basically haven't update since because everything is a hassle these days. Now I thought maybe it's time to update, but keep reading things like this and camera, wifi bootloops problems etc.
Are these issues a real thing? or just some individual cases where it happens?

It's real like a $2 dollar bill.

bininga59 said:
I have already tried EVERYTHING, in download mode I can not get the> Prenormal <to> Check ing <. The option of OEM lockdown is there, has always been there.
Click to expand...
Click to collapse
You have to turn off all data ( wi-fi and 4g) and manually set the date to 7 days back.

FlatOutRU said:
You have to turn off all data ( wi-fi and 4g) and manually set the date to 7 days back.
Click to expand...
Click to collapse
I have already made. As I said, I unlock the bootloader and lock (developer option or download mode) as I want,> prenormal <does not go away.

Did a root today without issues on my S10 with ASG8

ru_dimka said:
Did a root today without issues on my S10 with ASG8
Click to expand...
Click to collapse
everything works? twrp installed? magisk etc.?

chieco said:
everything works? twrp installed? magisk etc.?
Click to expand...
Click to collapse
There is no twrp for ASG8. Others stuff works well!

ru_dimka said:
There is no twrp for ASG8. Others stuff works well!
Click to expand...
Click to collapse
I'm always afraid that I install something or make a small change and end up in a bootloop... I wish twrp and everythign work just fine like before and I could make a backup after installing a rom and doing the most basic stuff.

Since this is the first post that comes on Google for "only official released binaries" "s10".
I had this problem again and again, and it seems that it was caused by one of the reboot not being done with the correct timing with the 3 buttons.
The thing I was missing was after flashing the patched AP files (and the other files).
When you restart, keep the 3 buttons pressed until you see the blue screen and then release only power (keep vol up + bixby) to get into reset mode.
I think I didn't keep them pressed long enough.
If the device restarts, keep pressing the 3 buttons (never let it restart without pressing them).
Once the factory wipe has been done: Restart with the 3 buttons, and keep them pressed until 1 to 2 sec after the screen that asks you to press the power button to continue.

General [IMG] Boot + magisk patched boot images

Hi, I have decided to gather boot images and magisk patched images to one thread for now. I will try to edit this thread to be up-to-date. You can let me know what could you want next or if anything is wrong etc.
Stock boot.img files (direct links): ​
EU NE2213_11_A.12​
Stock boot.img - link
EU NE2213_11_A.10​
Stock boot.img - link
​Magisk patched boot.img are here a file that can be downloaded (I am using magisk canary usually, but in Magisk, you can change the channel from the canary to stable etc.) - names as the versions come. ​
Below this there are those magisk patched files which you just flash (or boot and then flash directly from the Magisk app) via fastboot ​

Reserved

Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?

HessNL said:
Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?
Click to expand...
Click to collapse
Apparently not. I have patched that stock boot via magisk, then via fastboot boot <patchedimage.img> booted (and also tested if it actually boots) and when it booted, via magisk app I did "Direct install (recommended)", rebooted and done.

Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it

Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.

HessNL said:
Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it
Click to expand...
Click to collapse
Yes, because this is probably and currently the most secure option to root it as we haven't got twrp available yet.
BuBbLeFIZzY said:
Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.
Click to expand...
Click to collapse
That's not that you have it early. The phone itself is early in spite of rooting and doing things like rooting, custom recoveries, ROMs etc. I currently can't find boot img for your model, but once I do, I will post it here for you with patched one.

Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future

fozzy056 said:
Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future
Click to expand...
Click to collapse
You're really welcome, I wanted to unite those currently quite hard rooting stuff!
And yes, I can't wait to see twrp too!

Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.

GeekMcLeod said:
Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.
Click to expand...
Click to collapse
Not yet unfortunately. Or I don't know about it yet. :/

kouzelnik3 said:
Not yet unfortunately. Or I don't know about it yet. :/
Click to expand...
Click to collapse
Yeah.. I googled a lot last night once I got my phone trying to find it to root it. I need me that extra bit of customization.
Is there a way I can get it from my phone?

what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this

Johnstan725 said:
what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this
Click to expand...
Click to collapse
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone

Johnstan725 said:
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone
Click to expand...
Click to collapse
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.

g96818 said:
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.
Click to expand...
Click to collapse
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?

Johnstan725 said:
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?
Click to expand...
Click to collapse
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.

g96818 said:
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.
Click to expand...
Click to collapse
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?

Johnstan725 said:
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?
Click to expand...
Click to collapse
Hmmm. Well you should be fine if you patched the boot and let magisk do the install. I only suggested wiping since you said you flashed the img from the bootloader.
You might run into the same problem I have with the 9RT. I too upgraded from color to oos and couldn’t update at all, even though I rooted from the magisk app. I had to wait for someone to make a fastboot rom. I had no problems updating color following my method, but not oos after switching. Hopefully that’s not the case for you.