[OnePlus 7T] [OTA] [GLOBAL] Oxygen OS 11.HD65AA

Search This thread

HueyT

Senior Member
Apr 3, 2014
4,838
2,206
New Albany, IN
OnePlus 7T
Oxygen updater app can download oos11.0.0
I am currently on India 10.0.37 version and rooted with Magisk. Rooting works even though Magisk manager crashes immediately on opening. So I can't update Magisk.
I got OTA update to v11. If I update and can't update Magisk will I just loose root or will the phone go into bootloop?
How do I root Android 11? Is TWRP now working?
Magisk Canary zip can root OOS11.0.0.2 fine
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    CnaZrtG.jpg


    Download: OnePlus7TOxygen_14.O.25_OTA_0250_all_2103170010_42034d7f.zip
    2
    I'm on beta 4 and I'm hesitant to update to the stable update. The international stable build is dated 2 days before Open Beta 4:
    1. Stable: 2103170010 = 2021, March 17 @ 00:10
    2. Open Beta 4: 2103190108 = 2021, March 19 @ 01:08
    My HD1907 has no issues on OB4.
    1
    I'm on beta 4 and I'm hesitant to update to the stable update. The international stable build is dated 2 days before Open Beta 4:
    1. Stable: 2103170010 = 2021, March 17 @ 00:10
    2. Open Beta 4: 2103190108 = 2021, March 19 @ 01:08
    My HD1907 has no issues on OB4.
    i tried to install this new version over beta4 and i cant

    he says that my current version (beta4) is newer than stable 11
    1
    Anyone on converted tmobile to global with any issues? Gpay works? Device certified in play store?

    Hello, I have the conversion from T-Mobil to Global version. I can't tell you about GPay, but in my case about the device, the build number is unknown, and in its photo it shows a One Plus 6T ... This happened in all A11 betas. I don't know if the same will happen to you.
    1
    Hello, I have the conversion from T-Mobil to Global version. I can't tell you about GPay, but in my case about the device, the build number is unknown, and in its photo it shows a One Plus 6T ... This happened in all A11 betas. I don't know if the same will happen to you.

    I'm getting this too. I assume all we'll have to do is flash the next update and it will fix it though, right?