[OOS][Stable][OP6T Global][OP6T Tmobile] Oneplus 6T stable OOS guide thread

Search This thread
Hey team,
Having a bit of an issue with my OnePlus 6T.
On a fresh OOS 10.3.2 I cannot pass cts Profile with latest version of Magisk 2.4, it works perfect with Magisk 2.3 and both cts profile and basic integrity passes as true. But with the latest version of Magisk 2.4 no matter what I do I always get cts Profile: false...
I followed same installation procedures as always, flash magisk>downloads>+>osmosis BusyBox>install>reboot.
The back again to Magisk the install magiskhide props config then reboot, then after boot go to termix terminal and su>grant>props> chose finger print etc etc... Chose the one for OnePlus 6t android 10 install and reboot and still after boot the cts profile is false! Have tried everything and nothing with latest Magisk 2.4 but if I uninstall everything all modules and Magisk properly and flash magisk but this time the older version of Magisk 2.3 everything works fine after following all mentioned steps above and now cts profile is true and everything checks.
So is this a known issue with latest version of Magisk?
If so is there a workaround to be able to update to latest version? Or I'm I doing something wrong here. Trust me I googled it couldn't find anything in specific.
I thank you for your time in advance! ??

If you look through topjohnwu's tweets, it will begin to make sense.

I'm not certain I can post this link. But, here it is.

https://mobile.twitter.com/topjohnwu

Hope it helps.
 
  • Like
Reactions: badpanda

hachamacha

Senior Member
Jun 15, 2010
1,364
749
If you look through topjohnwu's tweets, it will begin to make sense.

I'm not certain I can post this link. But, here it is.

https://mobile.twitter.com/topjohnwu

Hope it helps.

I did the dirty update from 9.x to 10.3.2 from this thread on an international op6t (so using magisk 20.3 & TWRP latest).

I didn't clear out magisk or anything and booted back after just reinstalling magisk 20.3 afterward. It worked fine for cts test. Afterward from Magisk 20.3, I updated it to 20.4 and rebooted and cts is still showing TRUE.

I barely use any Magisk modules lately but for Busybox & NoLimits - Attached a pic - good luck.
 

Attachments

  • ssmagisk.jpg
    ssmagisk.jpg
    119.8 KB · Views: 392

zymphad

Senior Member
Jul 17, 2013
893
512
OnePlus 9
Hey team,
Having a bit of an issue with my OnePlus 6T.
On a fresh OOS 10.3.2 I cannot pass cts Profile with latest version of Magisk 2.4, it works perfect with Magisk 2.3 and both cts profile and basic integrity passes as true. But with the latest version of Magisk 2.4 no matter what I do I always get cts Profile: false...
I followed same installation procedures as always, flash magisk>downloads>+>osmosis BusyBox>install>reboot.
The back again to Magisk the install magiskhide props config then reboot, then after boot go to termix terminal and su>grant>props> chose finger print etc etc... Chose the one for OnePlus 6t android 10 install and reboot and still after boot the cts profile is false! Have tried everything and nothing with latest Magisk 2.4 but if I uninstall everything all modules and Magisk properly and flash magisk but this time the older version of Magisk 2.3 everything works fine after following all mentioned steps above and now cts profile is true and everything checks.
So is this a known issue with latest version of Magisk?
If so is there a workaround to be able to update to latest version? Or I'm I doing something wrong here. Trust me I googled it couldn't find anything in specific.
I thank you for your time in advance! ??

Magiskhide props. Fixed for me. I didn't do any of what you did, just installed. Worked on my girl's phone too since Pokemon was failing.
 

alryder

Senior Member
Apr 15, 2012
496
204
Lansing, MI
Hey team,
Having a bit of an issue with my OnePlus 6T.
On a fresh OOS 10.3.2 I cannot pass cts Profile with latest version of Magisk 2.4, it works perfect with Magisk 2.3 and both cts profile and basic integrity passes as true. But with the latest version of Magisk 2.4 no matter what I do I always get cts Profile: false...
I followed same installation procedures as always, flash magisk>downloads>+>osmosis BusyBox>install>reboot.
The back again to Magisk the install magiskhide props config then reboot, then after boot go to termix terminal and su>grant>props> chose finger print etc etc... Chose the one for OnePlus 6t android 10 install and reboot and still after boot the cts profile is false! Have tried everything and nothing with latest Magisk 2.4 but if I uninstall everything all modules and Magisk properly and flash magisk but this time the older version of Magisk 2.3 everything works fine after following all mentioned steps above and now cts profile is true and everything checks.
So is this a known issue with latest version of Magisk?
If so is there a workaround to be able to update to latest version? Or I'm I doing something wrong here. Trust me I googled it couldn't find anything in specific.
I thank you for your time in advance! ?

I didn't have to use magiskhide props or do anything special, Magisk worked once it was installed. The only modules I am using are Busybox and Google Dialer Framework.
 

Attachments

  • Screenshot_20200420-170042.jpg
    Screenshot_20200420-170042.jpg
    152.4 KB · Views: 470
  • Screenshot_20200420-170205.jpg
    Screenshot_20200420-170205.jpg
    199.8 KB · Views: 466
  • Screenshot_20200420-170139.jpg
    Screenshot_20200420-170139.jpg
    238.9 KB · Views: 466

Striatum_bdr

Senior Member
May 29, 2011
4,650
2,176
Marseille
I did the dirty update from 9.x to 10.3.2 from this thread on an international op6t (so using magisk 20.3 & TWRP latest).

I didn't clear out magisk or anything and booted back after just reinstalling magisk 20.3 afterward. It worked fine for cts test. Afterward from Magisk 20.3, I updated it to 20.4 and rebooted and cts is still showing TRUE.

I barely use any Magisk modules lately but for Busybox & NoLimits - Attached a pic - good luck.

OnePlus 6t phones are an exception for now, due to specific design of OOS. But it will probably won't last forever
 

carlost24

Senior Member
Jul 30, 2009
493
9
I converted my TMO OP6T into a international version, thru non-root method. I am now looking to root and therefore need to unlock my bootloader, unfortunately the tmo device unlock app is no where to be found (device or play store. Any suggestions on how i can get the app or at least revert back to tmo version so that i can root and get back to int. version with root after i unlock the bootloader?
 

meciu99

Senior Member
Oct 9, 2010
140
36

Rinku221

Senior Member
Aug 24, 2014
69
12
New delhi
Update Available on Oxygen Upadter App-10.3.3

---------- Post added at 01:47 PM ---------- Previous post was at 01:43 PM ----------

10.3.3 Update for FAJITA is Available on Oxygen Updater App
 

xBane_

Senior Member
Feb 12, 2017
162
11
I converted my TMO OP6T into a international version, thru non-root method. I am now looking to root and therefore need to unlock my bootloader, unfortunately the tmo device unlock app is no where to be found (device or play store. Any suggestions on how i can get the app or at least revert back to tmo version so that i can root and get back to int. version with root after i unlock the bootloader?
You can unlock the bootloader without that app- you just cannot carrier unlock without that app. Unlock the bootloader through fastboot as you normally would.
 

jhpdroid

Senior Member
May 13, 2011
78
37
OnePlus 6T
Last edited:

lilbrat

Senior Member
Jun 13, 2011
998
373
Amman
OnePlus 8T
Folks, I apologise , I have read through the thread and I still a bit lost.. I downloaded the newest update got the stock boot image and have a patch boot image , and TWRP installer..
My device is rooted with TWRP installed.. can I flash the new update through TWRP if I uninstall Magisk ..

1) reboot to recovery
2) flash full ota (no reboot)
3) flash TWRP
4) flash Magisk

I want/need to make sure as we're are locked down there and I don't have my laptop ... Hmm
 

kevk60

Senior Member
Dec 21, 2012
293
121
U.S.A
Folks, I apologise , I have read through the thread and I still a bit lost.. I downloaded the newest update got the stock boot image and have a patch boot image , and TWRP installer..
My device is rooted with TWRP installed.. can I flash the new update through TWRP if I uninstall Magisk ..

1) reboot to recovery
2) flash full ota (no reboot)
3) flash TWRP
4) flash Magisk

I want/need to make sure as we're are locked down there and I don't have my laptop ... Hmm

First I would disable your magisk modules and then magisk will ask to reboot for changes to take effect. No need to uninstall magisk. I never have. Then...
1- reboot to twrp and flash new oos
2- flash the latest twrp installer
3- reboot twrp ( to make sure it sticks )
4- flash newest magisk
5- Reboot system from twrp.
Once rebooted to new oos, enable magisk modules ( reboot for changes to take effect) and you should be good to go. I personally flash new OOS using local update and then flash twrp from magisk and then flash magisk to inactive slot after OTA in magisk. Works flawless. Good luck.
 
Last edited:
  • Like
Reactions: lilbrat

A30NI_Y

Senior Member
  • Jun 17, 2012
    637
    245
    First I would disable your magisk modules and then magisk will ask to reboot for changes to take effect. No need to uninstall magisk. I never have. Then...
    1- reboot to twrp and flash new oos
    2- flash the latest twrp installer
    3- reboot twrp ( to make sure it sticks )
    4- flash newest magisk
    5- Reboot system from twrp.
    Once rebooted to new oos, enable magisk modules ( reboot for changes to take effect) and you should be good to go. I personally flash new OOS using local update and then flash twrp from magisk and then flash magisk to inactive slot after OTA in magisk. Works flawless. Good luck.

    Right, I have updated a few times using the above mentioned magisk method instead of twrp method. The one time I used the twrp method I screwed up and have to use the msm tool.
     

    kevk60

    Senior Member
    Dec 21, 2012
    293
    121
    U.S.A
    Right, I have updated a few times using the above mentioned magisk method instead of twrp method. The one time I used the twrp method I screwed up and have to use the msm tool.

    I used to use the twrp method for every update but a few updates ago, I started using the magisk method and I can say I prefer it over the twrp method. Have a good one and stay safe!
     

    Top Liked Posts

    • There are no posts matching your filters.
    • 54
      OOS stable for Oneplus 6T Global

      This thread is an attempt to make things clean for OP6T users.
      It will contain latest zip links for OOS stable.
      It will contain a brief guide on how to root, install TWRP , how to update with or without those elements.

      6T global edition is supported by thread readers and me, and T Mobile converted specific concerns will be handled by community under the supervision of @Scott, thanks to him for the help.

      It will not contain basics like ADB and Fastboot connection
      with a computer. Experiment, read, there are many and many tutorials on the internet for that. Don’t forget there is a world outside XDA and that you can perform a search on any search engine to grab information.

      It will not cover by decision the ‘patching boot.img’ method for gaining root. It’s not necessary to use it when we have a working TWRP and Fastboot. If you want to try it search on the internet about ‘extracting boot.img from payload.bin’ and then use Magisk Manager to patch it.

      Please NO discussion about:
      Magisk itself, custom kernels, debloating (whatever method you want to use), custom ROMS… Only STOCK STABLE OOS.
      If you just want to flash custom kernels, no need to have TWRP, Ex Kernel Manager and Franco Kernel Manager for example can take care of that (see Play Store to grab those apps), and backup your stock kernel.

      ALWAYS USE LATEST VERSIONS of the different tools used. Don’t ask for help if you’re using 6 months old TWRP or Magisk. Update it first.
      First a bit of what I have understood about our phone, and its main specificity, i.e A/B slots.

      A/B slots, what else ?

      This structure is meant to enable to have two different versions of the SAME ROM, one slot will contain the previous version of the ROM, the other slot will contain the updated one. If you are on slot A and running 10.3.0, the update process will lead to have 10.3.0 on slot A and 10.3.1 on slot B. On next boot the bootloader will automatically boot updated one (i.e slot B will be flagged as the active one). In case of issues during boot process the bootloader will switch the active slot back to the ‘old’ version(here slot A) that was booting fine.
      This means that IT’S NOT a dual boot feature!! If you want to run a custom ROM it’s better to have the same custom ROM on both slots and not a mix of OOS and custom ROM. But that’s already OT so let’s stay focus, each custom ROM should provide clear instructions about that.
      Having a slot phone means that there is no Recovery partition. So if you ‘fastboot flash boot twrp.img’ it will overwrite your boot partition and thus the ROM kernel and can lead to issues. The .img file is only meant to be temporarly booted. Recovery (stock or TWRP) is a part of the boot ramdisk.

      Some simple facts about slots and flashing in TWRP:
      • Flashing a whole ROM (OOS for example) will automatically flash it to the currently inactive slot and switch it to be the active one (that works also with stock recovery, when performing a ‘local update’)
      • Flashing a ROM overwrites completely the boot partition (in recent Android versions, flashing process is using partition RAW images and not files like it was before): that means that TWRP and Magisk (if present) will be ERASED.
      • Flashing TWRP installer will flash it AUTOMATICALLY ON BOTH SLOTS (and will erase Magisk if present)
      • Magisk (and GAPPS but it only applies to custom ROMs), when flashed with TWRP is only flashed in ACTIVE slot. That’s why you must REBOOT to recovery BEFORE flashing Magisk to have it installed on the active updated slot. And that explains why you must flash it last.
      • That said, if you stay on OOS, YOU DON’T care about slots, just remember those basics to understand why you have to respect some steps, and let the recovery take care of slots. Messing manually with them results often in soft bricks


      Downloads


      OOS stable full signed zips: thanks to @Some_Random_Username, @Titokhan, @trollavin (their thread here)
      If the above doesn’t work anymore just let me know I’ll find something else.

      FYI you can still go to Oneplus website but they take time to update it to latest version… And there is no archives.




      XDA:DevDB Information
      OOS Stable thread support, ROM for the OnePlus 6T

      Contributors
      Striatum_bdr, Scott
      ROM OS Version: Android 10
      ROM Kernel: Linux 4.x

      Version Information
      Status: Stable

      Created 2020-02-05
      Last Updated 2020-02-06
      20
      Rooting

      CHANGELOGS

      OOS 10.3.4:


      • System
        Updated launcher version to 4.1.6
        Updated Android Security Patch to 2020.05
        Improved system stability and fixed general bugs
      • Phone
        Fixed the issue with default country in assisted dialing when SIM2 is in roaming state
        Newly added Work-Life Balance to help prioritize notifications and allocate time wisely (India only)
        Newly added Epic Games in Game Space (India only)



      OOS 10.3.3:


      • System
        Fixed the issue with a black screen randomly appearing while playing games
        Updated GMS package to 2020.02
        Updated Android Security Patch to 2020.04
        Improved system stability and fixed general bugs
      • Network updates
        Integrated VoLTE & VoWifi support for Telenor – Denmark
        Integrated VoWifi support for RJIO – India
      • Phone
        Newly added OpSoprts features in the shelf
        Added OnePlus Roaming feature: choose a plan without worrying about the SIM card while traveling
      • Cloud Sync updates [India only]
        Updated the CloudService to Version 2.0



      OOS 10.3.2:


      Changelog 10.3.2
      System

      • Fixed the screen flickering issue while swiping up to unlock

      • Improved system stability and fixed general bugs

      • Updated Android security patch to 2020.02


      OOS 10.3.1:

      Changelog 10.3.1

      System
      • Fixed the issue with a black screen appearing after unlocking the device using fingerprint
      • Fixed the issue with the animation logo while rebooting the device
      • Fixed the issue with device heating up while charging
      • Fixed the random disconnection issue with 5Ghz Hotspot
      • Improved system stability and fixed general bugs
      • Updated Android security patch to 2019.12
      Camera
      • Optimized the image preview time in the Pro mode
      • Fixed the camera crash issue
      Gallery
      • Fixed the issue with videos and images not displaying in Gallery


      OOS 10.3.0:

      Changelog 10.3.0

      System
      • Updated system to Android 10
      • Brand new UI for Android 10
      • Fixed the automatic reboot issue
      • Added the notch area display option in the Settings (Settings - Display - Notch display - Hide the notch area)
      • Fixed the issue with lock screen appearing even after unlocking the device with the password
      • Fixed the issue with Navigation bar after upgrade
      • Fixed the Digital wellbeing option missing in the settings
      • Updated Android security patch to 2019.11
      Fingerprint
      • Fingerprint unlock functionality improvement
      • Enhanced the fingerprint animation
      Camera
      • Camera performance improvement
      Wifi Connectivity
      • Fixed the issue of Wifi connection to 5Ghz networks


      OOS 10.0.1:

      Changelog 10.0.1

      System
      • Updated system to Android 10
      • Brand new UI for Android 10
      • Updated Android security patch to 2019.10
      • Fixed the fingerprint identification issue
      • Fixed the animation lag for fingerprint unlock
      • Fixed the automatic reboot issue after upgrade
      Camera
      • Improved the performance and fixed known issues
      Wifi Connectivity
      • Fixed the 5Ghz WiFi connection

      OOS 10.0.0:

      Changelog 10.0.0

      System
      • Upgraded to Android 10
      • Brand new UI design
      • Enhanced location permissions for privacy
      • New customization feature in Settings allowing you to choose icon shapes to be displayed in the Quick Settings
      • General bug fixes and improvements
      Full Screen Gestures
      • Added inward swipes from the left or right edge of the screen to go back
      • Added a bottom navigation bar to allow switching left or right for recent apps
      Game Space
      • New Game Space feature now joins all your favorite games in one place for easier access and better gaming experience
      Contextual Display
      • Intelligent info based on specific times, locations and events for Ambient Display (Settings - Display - Ambient Display - Contextual Display)
      Message
      • Now possible to block spam by keywords for Message (Messages - Spam - Settings - Blocking settings)
      16
      Just an FYI: I will be helping to support the T-Mobile version of the device in this thread.
      15
      UPDATING WITHOUT ROOT


      If your bootloader is locked (meaning no root no TWRP, factory state)
      , the update process is trivial, OOS (or Oxygen Updater if you use it) will grab a patch file (around 100MB max usually) and will apply it and will ask you to reboot. Everybody should be able to do this as it’s the normal way every phone on earth updates itself… If major changes are present sometimes you’ll have the whole ROM file. It doesn’t matter anyway it leads to the same destination.

      If your bootloader is unlocked but without root, the only difference is that OOS (or Oxygen Updater) will download the WHOLE ROM (around 1.8GB) and will apply it then ask for rebooting


      UPDATING WITH ROOT (+/- TWRP)

      Whole ROM update is mandatory. You can wait for System Update to download it or grab manually the zip file or use Oxygen updater. You then go in Settings > System > System Update > clic on the upper right cogwheel then choose ‘Local Update’ and select the zip file (If you download the OTA .zip file manually you must place it in the root of user data, like /data/media/0/ i.e the user internal storage, or eventually in the .OTA folder if there's one. If you use Oxygen Updater or System automatic donwload it will be right placed).

      The following update method is the preferred one (even if you have TWRP, recommended by some TWRP devs) due to frequent changes in partitions by OnePlus

      1. apply the ROM update via Settings > System > System Update > Local Update
      2. DON’T REBOOT
      3. Open Magisk Manager
      4. [If you have TWRP, go in Modules menu, clic on ‘+’ and choose latest TWRP installer zip file on your phone. Don’t use Retention A/B Script Magisk Module I had issues with it] [then stay in Magisk Manager and do the next step]
      5. On main screen of the app clic on ‘install’ next to Magisk paragraph
      6. On the pop up menu confirm ’Install’
      7. On the next pop up menu clic on the last entry: install on inactive slot (after OTA update)
      Then only reboot.

      The order can be changed (the most important thing to preserve is Magisk, TWRP is easy to flash back):

      • Update without taking care of TWRP, just Magisk part ("install to other slot after OTA thing")
      • Once rebooted to updated system, flash TWRP as a module with Magisk Manager
      • Install Magisk again using Magisk Manager ("direct install" option)

      There are infinite debates about uninstalling or not Magisk Modules before updating. Most of the times nothing to touch, sometimes there could be issues, instead of uninstalling perhaps just inactivate them by precaution before updating.

      Note: If you are rooted and run an OOS version older than 10.3.1, the above method should work, but you can also update your ROM to latest stable without taking care of root/TWRP and then root again as described in post #2

      If you want to try TWRP way:

      • Reboot to TWRP
      • Flash OOS update
      • Flash TWRP installer
      • Reboot to Recovery
      • Flash Magisk
      • Reboot System



      IF YOU ARE INTO A SOFT BRICK

      Don't forget the Vol+/Vol-/Power_button combo that can save you from a non responding phone...

      If you can boot in fastboot mode, flash the stock ROM with fastboot. A little trick is to edit the flash-all-partitions**.bat and remove ‘-w’ (-w means that the partition will be wiped before flashing) from the script, it will prevent personal data wipe. Or flash manually all partitions one by one, without ‘-w’ flag evidently. Some partitions can’t be flashed with fastboot, for that once booted back to OOS, download and install by ‘local update’ method the same ROM version you’ve just restored with fastboot (see the linked thread to know why, emojis issues for example sometimes).
      If you can’t go in fastboot mode, use Oneplus MSM tool. See there and there.
      14
      ROOTING (+/- TWRP)

      Magisk zip is to be found here
      TWRP latest .img and installer are to be found here
      Don’t use all-in-one tools, you’re a grown up person you can to it by yourself. Yes you can.

      If you're not rooted and run an OOS version older than 10.3.1, update your phone normally to latest OOS stable version then do as below

      If you’re not rooted and running 10.3.1 or higher, those are the simplest steps to gain root.

      Unlock your bootloader (will wipe everything…): “fastboot oem unlock” from a computer (see beginning of OP to know why I don’t detail this) with phone in fastboot mode
      Grab latest Magisk zip on your phone and latest TWRP .img on your computer (AND TWRP installer .zip on your phone if you want to install TWRP permanently). Boot in fastboot mode your phone.

      Then :
      • “fastboot boot twrp_latest.img” (adapt to the name and path of your twrp file)
      • within TWRP, flash TWRP installer .zip if you want to keep TWRP
      • flash Magisk zip (always AFTER flashing TWRP)
      Reboot
      (you can theoretically use the TWRP feature ‘install recovery ramdisk’ to avoid flashing twrp installer but never tested)

      Note: please STOP using blue_spark TWRP!!! Support for OP6T has been stopped long time ago, only OP6 twrp is still actively supported by eng.stk (errors are mandatory if you flash it on 6t). I even see people that use a 3.2.x version of blue_spark...