I have unlocked the bootloader and rooted my OP11 and am no longer able to run Netflix on my device. I am aware that this appears to be a known issue in some cases. I have tried hiding the Magisk app, downloading a new APK from APKMirror all to no avail. In the Google Play store, it says that the app won't work with my device. It's currently working fine on my OP8 Pro, which is also rooted with an unlocked bootloader.
Any suggestions on how to get it wokring? Thanks!
Have you flashed the universal safenet fix and hide root for netflix ?
azsl1326 said:
I have unlocked the bootloader and rooted my OP11 and am no longer able to run Netflix on my device. I am aware that this appears to be a known issue in some cases. I have tried hiding the Magisk app, downloading a new APK from APKMirror all to no avail. In the Google Play store, it says that the app won't work with my device. It's currently working fine on my OP8 Pro, which is also rooted with an unlocked bootloader.
Any suggestions on how to get it wokring? Thanks!
Click to expand...
Click to collapse
ChrisFeiveel84 said:
Have you flashed the universal safenet fix and hide root for netflix ?
Click to expand...
Click to collapse
It does not work :/
regards
q.
qriozum said:
It does not work :/
regards
q.
Click to expand...
Click to collapse
Test magsik delta canary (with magsik hide ) and the safenetfix
On my op9p it works
ChrisFeiveel84 said:
Test magsik delta canary (with magsik hide ) and the safenetfix
On my op9p it works
Click to expand...
Click to collapse
But here we talk about OP11 and not about OP9Pro.
I have a rooted and unlocked bootloader side by side by side, despite this "Netflix" works perfectly at the "L1" level.
On the other side I have OP11 and "Netflix" when trying to run he sent to Googleplay and there is red warning that he would not be on my device. After uninstalling and downloading from Apkmirror, the instalotra, only the "Netflix" logo is displayed and it hangs like that
So I do not suggest to other users that "after all, it works on OP8PRO, it also has to".
qriozum said:
But here we talk about OP11 and not about OP9Pro.
I have a rooted and unlocked bootloader side by side by side, despite this "Netflix" works perfectly at the "L1" level.
On the other side I have OP11 and "Netflix" when trying to run he sent to Googleplay and there is red warning that he would not be on my device. After uninstalling and downloading from Apkmirror, the instalotra, only the "Netflix" logo is displayed and it hangs like that
So I do not suggest to other users that "after all, it works on OP8PRO, it also has to".
Click to expand...
Click to collapse
that the google playstore says that netflix does not work with your device is usually because the root is not hidden from google and co (that's why i use magisk delta which also has magiks hide in it)
ChrisFeiveel84 said:
that the google playstore says that netflix does not work with your device is usually because the root is not hidden from google and co (that's why i use magisk delta which also has magiks hide in it)
Click to expand...
Click to collapse
What do I miss in "Hide applications"?
This is a drop from OP11:
Chris, you finally have OP11 or are you still writing about acting on OP9Pro?
qriozum said:
What do I miss in "Hide applications"?
This is a drop from OP11:
Chris, you finally have OP11 or are you still writing about acting on OP9Pro?
Click to expand...
Click to collapse
With magisk delta ? Or stock magisk ?
Stock magisk have no hide
magisk delta comes with magisk hide and works a little different than stock magisk
And have you q china op11 ?
There's a new app for safetynet that needs to be added to magisk hide or magisk deny list.
It's "Google Play protect service".
Then it's needed to clear data for it and also for play store and play services and reboot.
jes0411 said:
There's a new app for safetynet that needs to be added to magisk hide or magisk deny list.
It's "Google Play protect service".
Then it's needed to clear data for it and also for play store and play services and reboot.
Click to expand...
Click to collapse
Where can you get that app? I don't see it listed in Fox's Magisk Modules App? Thanks!
azsl1326 said:
Where can you get that app? I don't see it listed in Fox's Magisk Modules App? Thanks!
Click to expand...
Click to collapse
That app installs itself.
It's a new app Google implemented for integrity check (safetynet).
It should be added to magisk deny list/hide list.
Package name is com.google.android.odad
jes0411 said:
That app installs itself.
It's a new app Google implemented for integrity check (safetynet).
It should be added to magisk deny list/hide list.
Package name is com.google.android.odad
Click to expand...
Click to collapse
Thanks!
I didn't see it listed in the deny list in Magisk, so I added it via terminal for the MM I have installed that does the same thing. It just loads the splash screen and then stays stuck. I have the Magisk App hidden as well. I cleared data in both NF and Play Store. Still no luck with NF.
Mine works, but there is a bit of tinkering involved. I followed a guide from 10pro. You must use the shamiko magisk module, then hide magisk app and add all of Google play services to denylist. You then have to download a specific Netflix APK from that thread. I will try to find and attach it in an edit. Let me know if this works, I'm not 100% sure on the steps because I cloned my files from op10t and so my Netflix worked immediately.
azsl1326 said:
Thanks!
I didn't see it listed in the deny list in Magisk, so I added it via terminal for the MM I have installed that does the same thing. It just loads the splash screen and then stays stuck. I have the Magisk App hidden as well. I cleared data in both NF and Play Store. Still no luck with NF.
Click to expand...
Click to collapse
By seeing the NF error message, i suppose you have your bootloader unlocked and DRM info apk still shows L1 but a strange thing you will find on DRM info is system id just above L1 status and that is abnormal almost 8-9 digits of system id and that is causing your Netflix not to recognised your device and revoking the licence, i don't know the fix if you see others who has Netflix working with L1 he has system id of length 5 that is listed in drm devices list
shadowjynxs said:
By seeing the NF error message, i suppose you have your bootloader unlocked and DRM info apk still shows L1 but a strange thing you will find on DRM info is system id just above L1 status and that is abnormal almost 8-9 digits of system id and that is causing your Netflix not to recognised your device and revoking the licence, i don't know the fix if you see others who has Netflix working with L1 he has system id of length 5 that is listed in drm devices list
Click to expand...
Click to collapse
You can indeed be right.
In OP8Pro where Netflix works "L1" and a 5-digit "System-Id" ID. But in OP11 despite "L1" I have a 1-digit "System-Id" and Netflix does not work.
In addition, I notice that in the "Clearkey CDM" section as "Version" in OP8Pro is "1.2" but in OP11 there is already the phrase: "aidl-1".
jes0411 said:
It should be added to magisk deny list/hide list.
Package name is com.google.android.odad
Click to expand...
Click to collapse
There is no such package in my system :/
Of course, in "Hide-App" Magisk marked "system applications" and "OS applications".
qriozum said:
You can indeed be right.
In OP8Pro where Netflix works "L1" and a 5-digit "System-Id" ID. But in OP11 despite "L1" I have a 1-digit "System-Id" and Netflix does not work.
In addition, I notice that in the "Clearkey CDM" section as "Version" in OP8Pro is "1.2" but in OP11 there is already the phrase: "aidl-1".
Click to expand...
Click to collapse
Yes the same issue wan in OnePlus 9 pro and it was fixed in firmware update but then L1 dropped to L3 and got 5 digit system id then Netflix is opening but lost L1
qriozum said:
There is no such package in my system :/
Of course, in "Hide-App" Magisk marked "system applications" and "OS applications".
Click to expand...
Click to collapse
I got my OnePlus 11 yesterday and rooted with magisk delta canary. I can confirm that app is not here
qriozum said:
You can indeed be right.
In OP8Pro where Netflix works "L1" and a 5-digit "System-Id" ID. But in OP11 despite "L1" I have a 1-digit "System-Id" and Netflix does not work.
In addition, I notice that in the "Clearkey CDM" section as "Version" in OP8Pro is "1.2" but in OP11 there is already the phrase: "aidl-1".
Click to expand...
Click to collapse
I think that clearkey cdm is the problem.
I can pass safetynet, drm info shows L1, but I have that "aidl-1"
The cause of the problem is the 'TEE' hardware.
Because current Android 13 phones come with a hardware "TEE" and oppo disables the "TEE" when you unbootlock. If lock The BootLoader will then recover.
Similar to Samsung's unlock logic，The difference is that oppo can be restored.
Solution:
1. Lock the BootLoader
2. The 'TEE' hardware authentication is returned to the software level, but the DRM is changed to L3.
Related
Has anyone tried magisk 14?
I installed it (upgraded from previous release), no issues
Updated from within magisk. Seams to work fine
Someone could install modules?
Someone was able to pass on safetynet?
Modules NO, Safetynet YES
atheart said:
Modules NO, Safetynet YES
Click to expand...
Click to collapse
Safetynet yes? How?
I don't know anything about safetynet but when I run it using magisk 14 I get
Safetynet Check Was Successful
ctsprofile: false
basicIntegrity: false
both ctsprofile and basicIntegrity have a white x in a small red circle in front of them.
Every thing including root apps work fine. I'm very pleased that magisk Hide works so my banking apps work.
scallawag said:
I don't know anything about safetynet but when I run it using magisk 14 I get
Safetynet Check Was Successful
ctsprofile: false
basicIntegrity: false
both ctsprofile and basicIntegrity have a white x in a small red circle in front of them.
Every thing including root apps work fine. I'm very pleased that magisk Hide works so my banking apps work.
Click to expand...
Click to collapse
if what you said is true then you did not pass the safetynet.
What I said is true. I still don't know what difference it makes to me.
Why would you question what I said?
> Why would you question what I said?
If SafetyNet Check is successful, basicIntegrity will be "true". But that does not mean you are lying, it could be also a bug in Magisk
romhippo.com said:
> Why would you question what I said?
If SafetyNet Check is successful, basicIntegrity will be "true". But that does not mean you are lying, it could be also a bug in Magisk
Click to expand...
Click to collapse
I checked again this morning and the same results. Must be a bug. I wish someone else would jump in and tell us there findings.
I did a little reading on SafetyNet to see what it does and than downloaded the stand alone "SafetyNet Test" app from the play store.
It said the following
"Your Moto Z2 Play Failed"
"Safety Net Request: success" (Could this be what magisk 14 is saying was successful?)
every thing else failed
I can pass safety net.
Try clearing the Magisk app cache and data (Settings->Apps->Magisk Manager->Storage then click "Clear Data"). Then open Magisk Manager, go to settings and disable then enable the Magisk Hide option. Then try the SafetyNet check again.
> "SafetyNet Request: success"
That just means, Magisk was able to "check SafetyNet" (if you don't have internet access, you won't be able to check, for example). But your device did not pass the check.
romhippo.com said:
> "SafetyNet Request: success"
That just means, Magisk was able to "check SafetyNet" (if you don't have internet access, you won't be able to check, for example). But your device did not pass the check.
Click to expand...
Click to collapse
I realize that. What I'm trying to ask is could "SafetyNet Request: success" in the "Safety Net Test" app mean the same as "Safety Net Check was successful" in Magisk.
If so that would explain why Safety Net Check in Magisk was successful and every thing else failed.
Could I check this by taking my phone offline turning Mobile Data and WiFi off and running the SafetyNet checks in both apps?
> Could I check this by taking my phone offline turning Mobile Data and WiFi off and running the SafetyNet checks in both apps?
I don't really know what you want to check? Your device failed the SafetyNet check ("ctsProfileMatch" and "basicIntegrity"). It is that simple.
https://developer.android.com/training/safetynet/attestation.html#possible-results
This really seems like an error because even though the magisk indicates that safetynet has passed, Playstore apps that are not available to root devices (for example: Netflix) are not available.
Has anyone reported this bug?
Navegante13 said:
This really seems like an error because even though the magisk indicates that safetynet has passed, Playstore apps that are not available to root devices (for example: Netflix) are not available.
Has anyone reported this bug?
Click to expand...
Click to collapse
I can see Netflix on the Play Store. Pokemon GO works too.
Guys sorry I m a little lazy.
Yes I can install all this stuff. But what about ota update?
There's no factory images on motorola. So I have no idea for the future
Crostantin said:
There's no factory images on motorola. So I have no idea for the future
Click to expand...
Click to collapse
There is one motorola stock image mirrored at https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
However it is not really clear for what variant this image is for. For all? Or just one?
atheart said:
I can see Netflix on the Play Store. Pokemon GO works too.
Click to expand...
Click to collapse
But I do not see.
Have you made any settings?
I don't know what happen but SafetyNet starts passing. I have rooted Moto Z3 Play, unlocked bootloader, Magisk 20.4, EdXposed 91.0 (YAHFA v0.4.6.4, updated today), a few Magisk, and EdXposed modules. Before hardware SafetyNet checks I could pay by phone. After Google forcing SafetyNet hardware attestation I could not. I accepted it because I was more concerned with control than with the possibility of paying by phone in the store.
Today morning I updated Riru - EdXposed (YAHFA) module in Magisk Manager. Then reboot. During the day I rebooted the phone once again. In the evening I ran Google Play Store to update my apps. I was surprised that Play was updating Netflix. Normally I updated it manually by downloading the apk file. Then I was testing Safety Net with Magisk, SafetyNet attest and SafetyNet test - all green. I was able to add a card to GPay. Even "attest" records in dg.db has 0, without blocking write mode. Here some screenshots.
The new update of EdXposed in the Magisk Manager passes SN, nothing new.
But John Wu (Magisk developer) said there was no way for hardware attestation on unlocked devices. Any software hiding will not work. That what he said.
QkiZMR said:
I don't know what happen but SafetyNet starts passing. I have rooted Moto Z3 Play, unlocked bootloader, Magisk 20.4, EdXposed 91.0 (YAHFA v0.4.6.4, updated today), a few Magisk, and EdXposed modules. Before hardware SafetyNet checks I could pay by phone. After Google forcing SafetyNet hardware attestation I could not. I accepted it because I was more concerned with control than with the possibility of paying by phone in the store.
Today morning I updated Riru - EdXposed (YAHFA) module in Magisk Manager. Then reboot. During the day I rebooted the phone once again. In the evening I ran Google Play Store to update my apps. I was surprised that Play was updating Netflix. Normally I updated it manually by downloading the apk file. Then I was testing Safety Net with Magisk, SafetyNet attest and SafetyNet test - all green. I was able to add a card to GPay. Even "attest" records in dg.db has 0, without blocking write mode. Here some screenshots.
Click to expand...
Click to collapse
Will gpay work, can you pay in shops?
Sent from my BASIC using Tapatalk
I added card successfully to gpay. I suppose that it will be working but I need to check. I wasn't in shop yet ?
I think that is working because evaluation type is basic.
QkiZMR said:
I added card successfully to gpay. I suppose that it will be working but I need to check. I wasn't in shop yet [emoji846]
I think that is working because evaluation type is basic.
Click to expand...
Click to collapse
When you're in the gpay app and you turn on nfc, does it say-hold to reader?
Sent from my BASIC using Tapatalk
Al765436 said:
When you're in the gpay app and you turn on nfc, does it say-hold to reader?
Click to expand...
Click to collapse
Text in Polish, but it means "move closer to the reader".
QkiZMR said:
Text in Polish, but it means "move closer to the reader".
Click to expand...
Click to collapse
Yes that means it should be working, thx
Sent from my BASIC using Tapatalk
Al765436 said:
Yes that means it should be working, thx
Click to expand...
Click to collapse
I confirm payments works fine.
QkiZMR said:
I don't know what happen but SafetyNet starts passing.
Click to expand...
Click to collapse
I second you mate ( see it here ) :good:
Hardware attestation hack to basic attestation is needed, I gotta say.
serajr said:
I second you mate ( see it here ) :good:
Hardware attestation hack to basic attestation is needed, I gotta say.
Click to expand...
Click to collapse
I know. I said it in my third post. The best thing is that I not needed to clear any google play/google services data. It just began working ?
Hello everyone,
I haven't unlocked my P6P's bootloader or rooted yet, but have read that banking apps won't work after rooting/unlocking the bootloader.
Does anybody use Monzo and can confirm the app doesn't work? Also, do you think they'll find a solution to this issue any soon?
Thanks a lot!
Monzo won't work if device is rooted. Magisk used to have the Hide feature but I'm not sure if it's still working as I no longer root.
Many apps like banks or GPay also won't work if SafetyNet is tripped, again something MagiskHide used to be able to mask.
Yes all working here gpay, Banking apps and so on. Just use the guide for rooted and safety net pass here on xda. And additional do one thing:
Install Airfrozen app from Playstore,
Freeze magisk app in Airfrozen that's it all will work, if you need root just unfreeze it again use your root stuff and freeze again
All banking apps working for me...rooted.. without safetynet fix...
This is not Pixel 2 forum lol
Nekromantik said:
This is not Pixel 2 forum lol
Click to expand...
Click to collapse
I mean if you read the contents of the post you'd know he was talking about the pixel 6 pro lol
Nekromantik said:
This is not Pixel 2 forum lol
Click to expand...
Click to collapse
Thanks for heads up! Just fixed the title
And thanks everyone else for your replies! Good to know it's still possible to use banking apps, though with some tweaks.
This guide has all you need: https://forum.xda-developers.com/t/working-safetynet-with-pixel-6-pro-android-12.4354149/
Basically as long as you hide the Magisk app, and use the USNF module (latest Zygisk version is available for free now), you should be golden with most banking apps - just add them to the exception list.
anyone able to get fingerprint working with the Chase and Amex apps? both of these were fine, but now they won't let me unlock with fingerprint. running the latest Canary with 2.2 USNF
dimm0k said:
anyone able to get fingerprint working with the Chase and Amex apps? both of these were fine, but now they won't let me unlock with fingerprint. running the latest Canary with 2.2 USNF
Click to expand...
Click to collapse
I got chase working fine. I made sure chase was in deny list then cleared chase data/cache. Reboot. I uninstalled magisk app then was able to get fp to work. Even works after I installed Magisk app again.
eg1122 said:
I got chase working fine. I made sure chase was in deny list then cleared chase data/cache. Reboot. I uninstalled magisk app then was able to get fp to work. Even works after I installed Magisk app again.
Click to expand...
Click to collapse
when you added the Chase app to the deny list, did you select both entries under it or just the default one?
dimm0k said:
when you added the Chase app to the deny list, did you select both entries under it or just the default one?
Click to expand...
Click to collapse
Both
I didn't have to deny a single thing for GPay or Chase.
Install Magisk alpha. Enable zygisk. Install newest zygisk-based Universal SafetyNet Fix. Confirm that YASNAC shows you passing. Done.
There's no need to do exotic stuff but it's best to do this before ever trying your apps to avoid having to clear their storage.
Monzo does work on a rooted device. Starling doe not.
If you rooted using the method on this forum, and your Google Pay app was recently upgraded to Google Wallet, you will probably find that it doesn't work anymore. Even if you have the Universal SafetyNet Fix installed and SafetyNet shows as passing, the new payment app will still detect your device as rooted. This is because it now uses Google Play Integrity instead of SafetyNet.
There's a lot of discussion in this thread. But the short version is, if you want to get payments working again:
1. Install MagiskHide Props Config.
2. Follow the instructions on that page to change your device fingerprint to Samsung Galaxy S21 (A11).
That's it! Some people in the thread also cleared data for Google Play Services but I don't think I did. Also in that thread is a verification app (first version, official version) for Google Play Integrity that you can use to make sure your device fingerprint setting is correct.
So far I haven't noticed any side effects from changing the fingerprint. I was unable to receive any SMS messages after first changing, but I rebooted a second time and that issue went away.
Just install safetynet-fix-v2.3.1-MOD.zip in Magisk. That worked on my OnePlus Nord CE (EU).
Vattu said:
Just install safetynet-fix-v2.3.1-MOD.zip in Magisk. That worked on my OnePlus Nord CE (EU).
Click to expand...
Click to collapse
Yeah this thread is now out of date. The updated safetynet fix is a much better option now.
You don't need just the safetynet module. You need Shamiko along that.
So latest Safetynet + Shamiko 0.5.2 (the latest version right now) and you're all set. You gotta whitelist the banking apps you use and they'll work perfectly fine. These 2 were enough to allow my preferred ridiculous banking app to work without an issue, without any other modules or tweaking and such.
dragos281993 said:
You don't need just the safetynet module. You need Shamiko along that.
Click to expand...
Click to collapse
You only need Shamiko if you use LSposed, right? I don't use LSposed and it's been enough for me to put all of my annoying apps on the Magisk denylist.
aurny said:
You only need Shamiko if you use LSposed, right? I don't use LSposed and it's been enough for me to put all of my annoying apps on the Magisk denylist.
Click to expand...
Click to collapse
No. I only had Magisk installed with Zygisk turned on. I first installed Safetynet Fix then Shamiko. The first module wasn't enough for my preffered banking app to not detect that the bootloader was unlocked. Shamiko fixed that. I simply installed it as a module in Magisk
Thanks, good to know. I haven't had that issue yet but I'll remember this in case I need it in the future!
aurny said:
If you rooted using the method on this forum, and your Google Pay app was recently upgraded to Google Wallet, you will probably find that it doesn't work anymore. Even if you have the Universal SafetyNet Fix installed and SafetyNet shows as passing, the new payment app will still detect your device as rooted. This is because it now uses Google Play Integrity instead of SafetyNet.
There's a lot of discussion in this thread. But the short version is, if you want to get payments working again:
1. Install MagiskHide Props Config.
2. Follow the instructions on that page to change your device fingerprint to Samsung Galaxy S21 (A11).
That's it! Some people in the thread also cleared data for Google Play Services but I don't think I did. Also in that thread is a verification app (first version, official version) for Google Play Integrity that you can use to make sure your device fingerprint setting is correct.
So far I haven't noticed any side effects from changing the fingerprint. I was unable to receive any SMS messages after first changing, but I rebooted a second time and that issue went away.
Click to expand...
Click to collapse
Thank you very much, it worked perfectly.
This actually worked, thank you!
Hi there,
You can find attached the patched boot image for the first stable OOS 13 firmware (IN2023 = 8 Pro European/Global version)
Steps :
Unlock the phone bootloader
Install ADB and Fastboot on your computer
Download the patched boot.img below
Reboot your phone to fastboot mode and link it to your computer
Open a terminal prompt in the directory where the boot.img is located
type in the cmd
fastboot flash boot IN2023_11_F13-Patched.img
Click to expand...
Click to collapse
and press enter
Reboot the phone
Open the magisk app, hit Install then use the recommended method
Reboot and you're rooted
Google Drive
Thanks for this. Where can you download the oos13 firmware?
MR0808 said:
Thanks for this. Where can you download the oos13 firmware?
Click to expand...
Click to collapse
The update is available through Oxygen Updater app
First thoughts on OOS 13 are really positive, smoothness is the first thing I noticed, it's day and night with OOS 12
The UI revamp is very satisfying to me
Overall, it feels more polished than OOS 12, with the sense of details in every feature/setting, and some new unique features
Thanks. Looks like I'm getting IN2025, so will have to do the patched boot.img myself.
Time to find my old notes somewhere
Is your Fingerprint Sensor working with A13? Mine not.
I assume same issues as we had with A12 and USNF
GhostRider86 said:
Is your Fingerprint Sensor working with A13? Mine not.
I assume same issues as we had with A12 and USNF
Click to expand...
Click to collapse
i kept all my magisk modules after the update which fix SafetyNet and Fingerprint issue, so i don't know
Neil_Armstrong_ said:
i kept all my magisk modules after the update which fix SafetyNet and Fingerprint issue, so i don't know
Click to expand...
Click to collapse
I keepted mine as well, SafetyNet and gPay are working, but Unlock with Fingerprint Sensor is not. No reaction to sensor at all, not able to register new Finger...
Edit: Working now. Needed to disable USNF module, no reboot, Fingerprint Sensor working, register Fingers, screen lock, test, enable USNF module, enjoy
Neil_Armstrong_ said:
The update is available through Oxygen Updater app
First thoughts on OOS 13 are really positive, smoothness is the first thing I noticed, it's day and night with OOS 12
The UI revamp is very satisfying to me
Overall, it feels more polished than OOS 12, with the sense of details in every feature/setting, and some new unique features
Click to expand...
Click to collapse
I already have the fil, but I can't install it from system update apk,
am I missing something ?
EDIT:
re-downloaded the file again from Oxygen updater, but still it fails to install nd also "verification failed" in system local update.
Edit 2:
I re MSM back to OOS11 and upgraded directly to OOS 13 F3.
Tanks you so much it worked for me.
Can we use google pay with this version rooted ?
Edit. Gpay works
Hey guys, what version of Magisk (and branch) are you using to root OOS13?
I am still on 11.0.11.11 with Magisk 23.
What is the procedure to upgrade to OOS13 from OOS11 without losing root, Magisk modules and all my data?
I tried downloading full OOS12 using Oxygen Updater app, ran Local System Upgrade, it finished normally, then installed Magisk to inactive slot (after OTA) and rebooted BUT after reboot - the system stays 11.0.11.11. And the attempt to Local System Upgdate for OOS13 fails right on start.
What am I missing?
Please help
VBBoston said:
Hey guys, what version of Magisk (and branch) are you using to root OOS13?
I am still on 11.0.11.11 with Magisk 23.
What is the procedure to upgrade to OOS13 from OOS11 without losing root, Magisk modules and all my data?
I tried downloading full OOS12 using Oxygen Updater app, ran Local System Upgrade, it finished normally, then installed Magisk to inactive slot (after OTA) and rebooted BUT after reboot - the system stays 11.0.11.11. And the attempt to Local System Upgdate for OOS13 fails right on start.
What am I missing?
Please help
Click to expand...
Click to collapse
I updated from oos 13 unrooted. Lost my root using oos12
I was able to get OOS13 installed but now need to restore root.
Could someone please share
Magisk patched boot.img for Global OOS13 (IN2025_11_F.13) for rooting?
Thank you ~
VBBoston said:
I was able to get OOS13 installed but now need to restore root.
Could someone please share
Magisk patched boot.img for Global OOS13 (IN2025_11_F.13) for rooting?
Thank you ~
Click to expand...
Click to collapse
They have already been shared here.
Thank you very much!
stell52 said:
Tanks you so much it worked for me.
Can we use google pay with this version rooted ?
Edit. Gpay works
Click to expand...
Click to collapse
I have two problems:
1. Netflix and hotstar are not working.
2. Hdfc and Axis apps are not working.
Are they working for u ? I have tried a lot of fixes but couldn't get them to work. If someone can help it would be highly appreciated
Neil_Armstrong_ said:
Hi there,
You can find attached the patched boot image for the first stable OOS 13 firmware (IN2023 = 8 Pro European/Global version)
Steps :
Unlock the phone bootloader
Install ADB and Fastboot on your computer
Download the patched boot.img below
Reboot your phone to fastboot mode and link it to your computer
Open a terminal prompt in the directory where the boot.img is located
type in the cmd
and press enter
Reboot the phone
Open the magisk app, hit Install then use the recommended method
Reboot and you're rooted
Google Drive
Click to expand...
Click to collapse
I have rooted it successfully. Everything is working except Netflix, Disney Hotstar and a few banking apps. I have tried enforcing denylist, shamiko.etc. nothing is getting them to work.
If u have any fix please let me know.
Thanks
MrBloB said:
I have two problems:
1. Netflix and hotstar are not working.
2. Hdfc and Axis apps are not working.
Are they working for u ? I have tried a lot of fixes but couldn't get them to work. If someone can help it would be highly appreciated
Click to expand...
Click to collapse
In magisk go to settings then make sure zygisk is checked and activate denylist. In the denylist check google services is check.
Then install the module universital safetynetfix v 2.3.1 by kdrag0n
To me netflix and other apps work.
In the google play store you have many apps that can check if your safetynet is verified after it. If its verified it should work
To me vanced manager do not work when i try to install youtube vanced. It says that i tried to downgrade paquet but i did not. I uninstalled every youtube upgrade. If somebody know
MrBloB said:
I have rooted it successfully. Everything is working except Netflix, Disney Hotstar and a few banking apps. I have tried enforcing denylist, shamiko.etc. nothing is getting them to work.
If u have any fix please let me know.
Thanks
Click to expand...
Click to collapse
Flash Universal SafetyNet module in magisk (kdrag0n) and Magisk Bootloop Protector (just in case)
Check your status after a reboot with YASNAC from Play Store
Force the Magisk DenyList, and when configuring it, develop the apps and check all the tick boxes manually (to be sure)
Uninstall Netflix and install the latest .apk from APKMirror, can't help as other app (banking too) works fine
Isn't vanced dead ?
YouTube Premium Argentina is very affordable fyi ....
stell52 said:
To me vanced manager do not work when i try to install youtube vanced. It says that i tried to downgrade paquet but i did not. I uninstalled every youtube upgrade. If somebody know
Click to expand...
Click to collapse
stell52 said:
In magisk go to settings then make sure zygisk is checked and activate denylist. In the denylist check google services is check.
Then install the module universital safetynetfix v 2.3.1 by kdrag0n
To me netflix and other apps work.
In the google play store you have many apps that can check if your safetynet is verified after it. If its verified it should work
Click to expand...
Click to collapse
Yes i have done this. Tried shamiko as well. M passing safetynet checks, still it doesnt work.