Which one
Which one
I used the USNF (modified and non), magisk/zygisk hide enforce and in play store I had certified device, wallet seemed to work, L1 as well. But, Netflix and Disney+ didn't work still. Were you able to get Netflix (SD or HD) working in your configuration? It no longer affects me, I'm just curiousThanks, root is working well for me in A07. Passes safety net, wallet works, vine level 1.
After using saftey net patch module of course.
Cheers!
I guess not. My Netflix app asks for an update and then in the play store it says my device is no longer compatible. So I guess Netflix doesn't work at all for me currently.I used the USNF (modified and non), magisk/zygisk hide enforce and in play store I had certified device, wallet seemed to work, L1 as well. But, Netflix and Disney+ didn't work still. Were you able to get Netflix (SD or HD) working in your configuration? It no longer affects me, I'm just curious
*Edit: I also tried a device spoofing module with magisk to attempt a force of L3. The devices would show as the correct device and fingerprint in Device Info but still, couldn't get it to behave
do you have a kind of guide to share?
Yess...
Dual boot Linux. Solves all driver problems forever lol.I get accros the issue of the driver when the phone is in FastbootD, how did you solve it?
the Oneplus driver folder doesnt have such a driver
EDIT
found the way to do it.
It does exactly that.Does booting the initial patched image (before actually installing magisk) give temporary root access that then goes away after a reboot?
SystemI just got the notification for update A.08. Who wants to test it out and report back?
I might try to update and keep root later tonight if I get bored.
Why was I quoted here? Have you tried the update? I don't understand what you are referencing in my message.System
• Optimizes the display effect of Dark mode in low brightness scenarios.
• Optimizes the touch experience.
Network
• Optimizes Wi-Fi stability and improves network experience.
• Optimizes communication stability.
Camera
• Optimizes the exposure effect of the front camera in the backlight environment.
Other
• Fixes the occasional issue of notification delay.
• Fixes the occasional issue of dark stripes when taking photos.
• Fixes the occasional issue of ghost effect in group photo scenarios with the front camera.
Nothing, It's the changelog for update you mentioned
My installation fails each time on a.08. I am guessing due to root, but it appears magisk did not back up the stock boot image when originally rooting.I just got the notification for update A.08. Who wants to test it out and report back?
I might try to update and keep root later tonight if I get bored.
The backup should be located in /data/magisk_backup_*** it is a gziped image.My installation fails each time on a.08. I am guessing due to root, but it appears magisk did not back up the stock boot image when originally rooting.
It is not, that is why I need it.The backup should be located in /data/magisk_backup_*** it is a gziped image.
The installation will fail without full OTA zip. To go from A06 to A07 update with incremental OTA I had to unroot, install update, boot patched image, re-root.
The stock A06 kernel from the original post will work to boot the phone running A07, I have used that. Do not flash it though, just do fastboot boot with the image. Either that or you can download the EU full OTA zip and extract the boot image that way, that's how Marco589 made the patched image in the first post.It is not, that is why I need it.
I am already on A07, the A08 update fails, so I want to unroot to update and need the stock boot image from A07 to restore.
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