AkayamiShurui
Senior Member
You follow a guy on the website he updated it so it stays you only need the boot image and not to flash it but the boot your phone from it so they're both saying the same thing though
You follow a guy on the website he updated it so it stays you only need the boot image and not to flash it but the boot your phone from it so they're both saying the same thing though
I have the problem that I can't watch Disney or Netflix, I have a certified play store, everything you mention, I read that the problem is that I have l1 but it's broken, and I don't know how to fix that, to make it l3I have YTTV, Netflix, Disney+ etc working successfully. Initially none of them were working while rooted. It takes some fairly big changes, but I thought I'd share.
Explanation:
Essentially, widevine needs to be set to L3 (lower quality as it's not protected). There is a module called liboemcryptodisabler that typically accomplishes this but it doesn't work for our device. Oneplus moved the library (liboemcrypto.so) to the "odm" partition which both the module and Magisk don't support. There is a fork of Magisk called Magisk Delta (by HuskyDG) that allows magic mounting of extra partitions, including "odm". I made some tiny and "hacky" changes to the module and now widevine shows as L3 and video apps work for me.
TL;DR
Use at your own risk, I'm not responsible for any damage, etc, etc.
- Magisk Delta - Required. I'm currently using delta-5. Zygisk and MagiskHide enabled and DenyList configured.
- Universal Safety Net Fix - Module. Needed to download the media apps from Play Store (and maybe other reasons). I'm currently using v2.4
- liboemcryptodisablerodm - My custom module attached here. Based on the original liboemcryptodisabler by ianmacd.
thanks, man. your module worked like a charm.I have YTTV, Netflix, Disney+ etc working successfully. Initially none of them were working while rooted. It takes some fairly big changes, but I thought I'd share.
Explanation:
Essentially, widevine needs to be set to L3 (lower quality as it's not protected). There is a module called liboemcryptodisabler that typically accomplishes this but it doesn't work for our device. Oneplus moved the library (liboemcrypto.so) to the "odm" partition which both the module and Magisk don't support. There is a fork of Magisk called Magisk Delta (by HuskyDG) that allows magic mounting of extra partitions, including "odm". I made some tiny and "hacky" changes to the module and now widevine shows as L3 and video apps work for me.
TL;DR
Use at your own risk, I'm not responsible for any damage, etc, etc.
- Magisk Delta - Required. I'm currently using delta-5. Zygisk and MagiskHide enabled and DenyList configured.
- Universal Safety Net Fix - Module. Needed to download the media apps from Play Store (and maybe other reasons). I'm currently using v2.4
- liboemcryptodisablerodm - My custom module attached here. Based on the original liboemcryptodisabler by ianmacd.
Thank you. I gave it a shot, worked like a charm. And I actually enjoyed magisk delta because of the builtin bootloop protector, eventhough I didn't test itI have YTTV, Netflix, Disney+ etc working successfully. Initially none of them were working while rooted. It takes some fairly big changes, but I thought I'd share.
Explanation:
Essentially, widevine needs to be set to L3 (lower quality as it's not protected). There is a module called liboemcryptodisabler that typically accomplishes this but it doesn't work for our device. Oneplus moved the library (liboemcrypto.so) to the "odm" partition which both the module and Magisk don't support. There is a fork of Magisk called Magisk Delta (by HuskyDG) that allows magic mounting of extra partitions, including "odm". I made some tiny and "hacky" changes to the module and now widevine shows as L3 and video apps work for me.
TL;DR
Use at your own risk, I'm not responsible for any damage, etc, etc.
- Magisk Delta - Required. I'm currently using delta-5. Zygisk and MagiskHide enabled and DenyList configured.
- Universal Safety Net Fix - Module. Needed to download the media apps from Play Store (and maybe other reasons). I'm currently using v2.4
- liboemcryptodisablerodm - My custom module attached here. Based on the original liboemcryptodisabler by ianmacd.
Try USNF 2.4are there any known bugs with this process? 1+11 currently cannot use PIN or fingerprint unlock once rooted, anything similar to that here?
also, since this is using an india image, does that change anything region specific things after root, or just for the original exploit?
For me this was never an issue on the 10t, but was on the 11. Also when booting the Indian image for root, this does not change the phone firmware, because you are just booting it, not flashing it like early 1+ 11 root.I didn't actually buy the phone yet, just read the root notes and saw it mentioned it is broken for OP11, was curious if it is the same for 10t
Does it work with cph2413_11_A.06?if anyone needs, already patched boot from OxygenOS A.10 IN (CPH2413)
patched and verified by me
not hard at all. use oxygen updater from google playHow i can get oneplus 10t firmware? its really hard to find cph2413 firmware
T-mobile version can't be rooted afaikAnyone have the files to do this on the new CPH2419? Or can I use the same files on it?
What do you mean by install to inactive slot? I'm coming from Samsung and trying to understand the terminologies. I read the entire thread, I have 2417.11.A.08 and want to root.I used the following steps to go from A12 to A13. This is slightly different than I previously posted but is faster and with less steps.
1. Download update zip with Oxygen Updater
2. Unroot with Magisk app (restore images)
3. Install update using OPLocalUpdate apk (the one that does not auto reboot and lets you install zip from storage)
4. Use Magisk to install to inactive slot (After OTA)
5. Reboot
This is for if you are rooted already and updating I think. If you have not rooted yet, you may have to follow the steps earlier in this thread.What do you mean by install to inactive slot? I'm coming from Samsung and trying to understand the terminologies. I read the entire thread, I have 2417.11.A.08 and want to root.
sure, this is the last boot.img (android 13.1)Unfortunately, I can not root this phone after last incremental update. Old patched boot.img causes reboot during boot. Does anyone have the new boot.img and can upload it?
ops, my bad!Can you make it public? I don't have access to this file. Thanks.
After downloading from oxygen updater, the new 13.1 system update always stuck and failed at 65% for me when updating via the 'system update' app.
Anyone else has similar issues?
@Jager any ideas?
Thanks.
oh, my bad. Since it has been a while, i forgot the `restore images` step...I have not updated yet but would assume that the steps from my previous post would still work. These are the steps I'm going to try myself when I feel like doing the update.
And if not then you can take the long way around with these other instructions I posted. Just would need the new boot.img. Can make yourself from the update zip if needed usually.
Are you not listening to me? I just told you how to do it. Boot the patched image and run the direct install. Magisk installer will do what needs to be done for you. This is also the same thing the OP has done. Ignore those other instructions you found, they are incorrect and pose problems when you take OTA updates as OnePlus is moving away from full OTAs to incremental ones that will not flash to a phone with modified images.I understand that, but in the instructions, the repaired vendor_boot.img is also flashed
I have YTTV, Netflix, Disney+ etc working successfully. Initially none of them were working while rooted. It takes some fairly big changes, but I thought I'd share.Nah... I'd suggest your feeling on this to be somewhat "Chicken Little"ish.
Don't get me wrong... it's completely annoying that so many apps are coded with kill switches triggered by any sign of root or root related settings and/or modifications. However, the cat and mouse game that is "apps detecting root and developers creating ways to avoid being detected" has been going on for years... and will continue to do so.
I suspect what sets these streaming apps apart from other apps which DO have working methods to evade root detection is their usage of DRM. If I understand things correctly, just an unlocked bootloader (without having root or any other modifications) can cause the DRM check to fail. And, hiding and unlocked bootloader from DRM is apparently difficult to impossible.
The part of this that I fail to get my head around is: Why do certain companies block app usage if root is detected, yet have no issue if I access the same content on my Linux box? Disney+ is a perfect example.![]()
Don't follow that guide. You just need to boot (not flash) a patched boot image and then run direct install. This also creates backups of your stock images which you'll need when you OTA.You followed this guide
https://www.droidwin.com/root-oneplus-10t-via-magisk-patched-boot-img/
or did you only flash the patched boot.img?
While in adb in cmd type "adb devices" it will show your device serial number and then run the .bat file as run as administrator your device will be unlocked,It says it failed with a timing. OEM unlock is enabled in settings. To avoid clutter or adding confusion here, if it is ok please private message. Thanks a lot for your support