What's this about?
I'm starting this thread in order to keep track of the state of Xposed on the Galaxy A8 (2018). Current status: Working. (Updated Jan 2019.) Model: SM-A530F. Android: 8.0.0 (Oreo). ROM: stock, baseband A530FXXU2BRG1, kernel 4.4.13-13824581-QB18772733 from Mon Jul 2, 2018.
Why wouldn't Xposed be working? Xposed works on Oreo!
Yes, but not necessarily for Samsung. Samsung has custom ART libraries, and additional quirks such as xz compression, custom methods etc. There were custom Xposed builds made for Samsung LP/MM ROMs, but there are currently none that are confirmed working for stock N/O (no longer the case!). Symptoms of a non-working Xposed include lag, freezes, spontaneous reboots, bootlops and dissapearing baseband info in settings "about phone" (inability to recognize SIM).
How can I live without Xposed if I can't/won't get it working?
Depends on what modules you need. Things like Greenify or microG/UnifiedNLP can work without Xposed, by installing them as system apps. (Yes, you lose SafetyNet, but SafetyNet is lost anyway with Xposed.) XPrivacy can in theory be replaced with things like AppOps or the LineageOS permissions system (yes, I know that there's no LineageOS build for A8 2018 at this time, sadly.) You can also mitigate privacy implications by using a firewall like AFWall+ (it's a good idea even with XPrivacy). Feel free to suggest other alternatives in comments.
Requirements:
You should be familiar with the current state of custom kernel/recovery/root/magisk for the A8 2018. In short, in order to be able to try Xposed builds, you should have on hand the following:
1. Odin 3.13 or later. (Heimdall will NOT work, it cannot unpack the latest Samsung images. JODIN is not confirmed to work either. Use Odin in a virtual machine such as VirtualBox if you're on Mac/Linux.)
2. The official stock images for your device. Download from sammobile.com, updato.com, samdb.org. It is recommended to re-flash clean stock images whenever you try new versions of anything (recovery, kernel, magisk etc.)
3. TWRP version 3.2.3 or later. (courtesy of BlackMesa)
4. Also from the TWRP thread, you MUST get the RMM and no-verity fixes! RMM bypasses the Samsung theft "protection", which can soft-brick your phone for several days if tripped. no-verity removes the system partition anti-tamper protection, which would otherwise not allow you to boot.
5. Last but not least, Magisk and Magisk Manager are confirmed to work well. Install the latest Magisk (v18.0 at the time of writing this).
BlackMesa's Custom Kernel is OPTIONAL and in fact I haven't been able to get it working 100% perfectly. All the kudos to BlackMesa for the work he's put into it, it's the closest thing we have to a potential future LineageOS build, and includes LOTS of useful fixes, but remember that YMMV. If you install the kernel you don't need the opt-verity and RMM fixes. If you don't, Xposed works fine on stock kernel too. Again, this is OPTIONAL as far as Xposed is concerned.
In the same vein, if you're only interested in testing Xposed you can flash it from TWRP, you don't necessarily need Magisk (but it's highly recommended).
Before you start:
SafetyNet will be lost if you install non-systemless Xposed. Period. This can't be fixed by hiding Magisk from specific apps, it's about getting that green "SafetyNet check" in the main Magisk screen. If you don't get that, there are apps that will refuse to work, end of story.
You can live with it by installing older versions of certain apps (if you can get your hands on the APKs), back when they were not SafetyNet-enabled. Works fine for older version of Netflix for example (4.15.1 build 14947). Also works for my local bank's app.
INSTALL PROCEDURE:
Follow this procedure carefully. It will hurt if you don't.
* Get the RMM and no-verity fixes from the TWRP thread linked above. Get Magisk from the link above. Put them all on the SD card and put the SD card inside the phone.
* With the phone booted to system normally, turn ON the "OEM unlock" option in developer settings and never, ever turn it off again. If you do, the phone will soft-brick and you'll have to reflash stock images to make it work again.
* If you are starting from a pristine install you don't need to [re]flash the stock images. However, it's strongly recommended to perform a factory reset before you continue. If you're coming from a different kernel/ROM etc. you have to flash the stock images, this guide assumes you're on stock Oreo.
* Turn off the autoreboot option in Odin. Flash the TWRP .tar image in the AP slot in Odin. I repeat, DO NOT BOOT TO SYSTEM. From this moment and until you install the RMM fix you can potentially trip Samsung's theft protection. Proceed exactly as described below.
* Remove the USB cable from the phone. Press and hold Power+VolumeUp+VolumeDown to reboot and immediately after the reboot press and hold Power+VolumeUp to enter TWRP recovery. Do not reboot to system yet.
* Swipe to allow modifications when entering TWRP.
* Format /data. Reboot to recovery. Do not install TWRP when prompted.
* Swipe to allow modifications when entering TWRP.
* Verify that data is mounted, in the mount menu.
* Install RMM and no-verity fixes from SD card. (Alternatively, you can install BlackMesa's kernel instead at this point. It includes the RMM/no-verity fixes. Please note that I've personally experienced some problems with it. Using the stock kernel + RMM/no-verity fixes seems rock solid on the other hand.)
* You can now reboot to system. Do not install TWRP when prompted.
* This first boot to system can take as much as 15-20 minutes. The Samsung logo and the blue led will flash throughout this time. Let it work, be patient.
* Verify that the phone seems to work ok.
* Reboot to TWRP recovery (restart the phone then use Power+VolumeUp immediately after reboot).
* Swipe to allow modifications when entering TWRP.
* Install Magisk.
* Reboot to system. Do not install TWRP when prompted.
* Verify that Magisk Manager shows green SafetyNet check passed.
* Install Xposed Framework from Magisk Manager modules (NOT Xposed Framework SDK systemless).
* Start the Xposed app and use its own reboot option, to make it ask for root. Grant root forever. The phone will restart.
* Verify that Xposed shows green (working) message, and that Magisk shows red (SafetyNet check not passed) message.
* You may need to reboot one more time if Xposed says that it was installed but not active. You want Xposed Manager to show a solid green background banner in the main screen.
You can now install Xposed modules.
* If you want XPrivacy, you need to install XPrivacyLua. The old XPrivacy module is available and can be installed but it will NOT work, it is simply incompatible with Android version past Marshmallow. Yes, XPrivacyLua is different but it works well after you get used to it.
* I recommend also installing AFWall+ or NetGuard firewall, because in Oreo access to Internet is no longer an app permission (all apps get access to Internet; crazy huh? Google privacy FTW) so there's nothing that XPrivacy can do about it.
* Alternatively there's an XPrivacyLua hook which can fake apps into thinking there's no network connection, but it can be bypassed if the app is aware of it; an actual firewall is the best solution.
How should I test Xposed?
The main issues are those described above: freezes, lag, reboots, kills baseband. Xposed itself is working. You can install modules and they will work as expected. This is not a problem with Xposed itself, but rather the bad side-effects when combined with a Samsung ROM. So in order to declare a build as "working" please make sure that none of the above issues appear when you install it, activate it, install various modules, and use it for a while. When the bad things happen you'll know it, they will be very obvious.
What Xposed versions have been tested?
* Xposed-Framework-Unity v89/90b3r18 (non-systemless Magisk module or installed via TWRP). Working.
* Xposed Framework (SDK 26) 90.2-beta3 (systemless Magisk module). Not working. Red error message in Xposed.
What Xposed modules are working?
Here are modules that have been reported working. Doesn't mean these are the only ones that work, but it's not a guarantee either. Try it for yourself.
* XPrivacyLua [added Jan 11, 2019]
* GravityBox [O] [added Jan 11, 2019]
* AFWall+ [added Jan 11, 2019]
* Greenify [added Jan 11, 2019]
* MinMinGuard [added Jan 11, 2019]
* AlwaysCorrect [added Jan 11, 2019]
* RootCloak [added Jan 14, 2019]
* Screenshot Delay Remover [added Jan 14, 2019]
* App Settings [added Feb 5, 2019]
* Disable Flag Secure [added Feb 5, 2019]
* Play Store Fixes [added Feb 5, 2019]
Xposed modules confirmed NOT working
The following modules have been confirmed not to work:
* UnifiedNLP: the Xposed module is abandoned and was never updated for Oreo+, so it's not patching framework-res.apk correctly to add org.microg.nlp to the list of accepted location providers. So the status check will report unable to hook into the location service, and without that it won't work. I'm trying to research an alternative solution in this thread. [added Jan 14, 2019]
Useful links
Links to bug reports, XDA development threads, useful forum threads etc. You would be well advised to read through these links to gain a better understanding of the issues involved:
* Xposed v90 beta 1 framework incompatible with Samsung Oreo beta
I have used Xposed on 8.0 with only one issue it boots up slower but I lost too much on updating to 8.0 so I went back to 7.1.1.
mchlbenner said:
I have used Xposed on 8.0 with only one issue it boots up slower but I lost too much on updating to 8.0 so I went back to 7.1.1.
Click to expand...
Click to collapse
What build was it, and from where?
I can't say I've noticed it booting slower (with Xposed installed from Magisk).
If you want to use Xposed I recommend using SuperSU with it.
mchlbenner said:
If you want to use Xposed I recommend using SuperSU with it.
Click to expand...
Click to collapse
Can you recommend a combination of Xposed/SuperSU/A8 ROM that worked for you? I haven't had much luck with the latest official versions on Oreo.
Did you also flash one of BlackMesa's kernels, or used the no-verity and RMM fixes?
In what order did you flash all these things?
wirespot said:
Can you recommend a combination of Xposed/SuperSU/A8 ROM that worked for you? I haven't had much luck with the latest official versions on Oreo.
Did you also flash one of BlackMesa's kernels, or used the no-verity and RMM fixes?
In what order did you flash all these things?
Click to expand...
Click to collapse
Yes i did flash his kernel.
Well you have to be rooted then download xposed for oreo.
That all i did it work only one thing boots up slower.
Sent from my SM-A730F using xda premium
All rom galaxy j500f
parvesz said:
All rom galaxy j500f
Click to expand...
Click to collapse
Not the forum for you
Has anyone tried this, i currently don't own this phone but my friend does..he would like to have xposed for one reason, to run Xinsta module
https://github.com/android-hacker/VirtualXposed
I've been holding off installing Xposed to hear more from others' experience. But I'm getting really tired of the unnecessary icons in the status bar (alarm clock, do not disturb, vibrate, etc.) and I'm not interested in installing a 3rd party launcher. So who else has installed Xposed on the A8? Has anyone else gotten it running without a problem?
shunsai said:
I've been holding off installing Xposed to hear more from others' experience. But I'm getting really tired of the unnecessary icons in the status bar (alarm clock, do not disturb, vibrate, etc.) and I'm not interested in installing a 3rd party launcher. So who else has installed Xposed on the A8? Has anyone else gotten it running without a problem?
Click to expand...
Click to collapse
If you dont like the icons in status bar, install good lock, that is the most official way to change ur status bar icons, you can find good lock in the galaxy apps store
jizzy001 said:
Has anyone tried this, i currently don't own this phone but my friend does..he would like to have xposed for one reason, to run Xinsta module
https://github.com/android-hacker/VirtualXposed
Click to expand...
Click to collapse
Been trying this for a few days with and without root and doesn't seem to do anything, seems like it's not supporting Samsung ROMs atm or something like that (i've been also trying to use Xinsta as it's pretty much the only Xposed module i normally use)
Xposed on Oreo
shunsai said:
I've been holding off installing Xposed to hear more from others' experience. But I'm getting really tired of the unnecessary icons in the status bar (alarm clock, do not disturb, vibrate, etc.) and I'm not interested in installing a 3rd party launcher. So who else has installed Xposed on the A8? Has anyone else gotten it running without a problem?
Click to expand...
Click to collapse
I'm on a A530F, with (Oreo T-Mobile Netherlands, Baseband A530FXXU3BRG1).
Rooted phone, Magisk v17.1 and have Mesa's MCK v2 kernel installed, included official TWRP recovery 3.2.3.0.
I can confirm that I use Xposed for more than a day now, and it is running perfect with 4 modules installed still no loss of baseband or spontaneous reboots, and it does not boot up slow when you restart your device.
Battery live is good, you can boost it with Greenify.
I use Xposed framework version 90-beta3, only not installed from magisk did that before but unsuccessfully, so I tried it again this time it holds with the v2 Mesa kernel.
So this way works for me, you can try it but do not install Xposed systemly through Magisk.
One more thing, be aware that it is a beta version not official so not all modules will work, what works for me are GrafityBox, Seraj Xperia Home X (0), Flat Style Bar Indicators and Greenify Xposed module, try different modules for yourself see what works.
Its bin three days now since I have installed Xposed, and still running smooth. No freezes, dissapearing baseband or fc.
No problems at all!
solamente said:
I'm on a A530F, with (Oreo T-Mobile Netherlands, Baseband A530FXXU3BRG1).
Rooted phone, Magisk v17.1 and have Mesa's MCK v2 kernel installed, included official TWRP recovery 3.2.3.0.
I can confirm that I use Xposed for more than a day now, and it is running perfect with 4 modules installed still no loss of baseband or spontaneous reboots, and it does not boot up slow when you restart your device.
Battery live is good, you can boost it with Greenify.
I use Xposed framework version 90-beta3, only not installed from magisk did that before but unsuccessfully, so I tried it again this time it holds with the v2 Mesa kernel.
So this way works for me, you can try it but do not install Xposed systemly through Magisk.
One more thing, be aware that it is a beta version not official so not all modules will work, what works for me are GrafityBox, Seraj Xperia Home X (0), Flat Style Bar Indicators and Greenify Xposed module, try different modules for yourself see what works.
Its bin three days now since I have installed Xposed, and still running smooth. No freezes, dissapearing baseband or fc.
No problems at all!
Click to expand...
Click to collapse
Thanks for the heads-up. I've been meaning to get around to installing it as I have on my other previous phones, but have just been lazy. Good to know GravityBox seems to be working fine, as it's the only module I use.
View attachment 4629438
View attachment 4629440
View attachment 4629441
View attachment 4629442
View attachment 4629446
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
shunsai said:
Thanks for the heads-up. I've been meaning to get around to installing it as I have on my other previous phones, but have just been lazy. Good to know GravityBox seems to be working fine, as it's the only module I use.
Click to expand...
Click to collapse
You're welcome! Wow, you had a lot of cell phones.
Yeah at first I was also lazy, but I got some spare time and started to research Xposed on my Phone.
Now Xposed is active for 6 days on my phone whithout a problem.
So I guess that Xposed version 90-beta3 is working at least for me, if you are used to Xposed then try it out!
I hope that the official stable version for Oreo comes out soon for compatibility with almost all modules, but for now I am satisfied with the beta-version.
Here are some screenshots of my phone with Xposed installed.
solamente said:
View attachment 4629438
View attachment 4629440
View attachment 4629441
View attachment 4629442
View attachment 4629446
View attachment 4629447
View attachment 4629448
You're welcome! Wow, you had a lot of cell phones.
Yeah at first I was also lazy, but I got some spare time and started to research Xposed on my Phone.
Now Xposed is active for 6 days on my phone whithout a problem.
So I guess that Xposed version 90-beta3 is working at least for me, if you are used to Xposed then try it out!
I hope that the official stable version for Oreo comes out soon for compatibility with almost all modules, but for now I am satisfied with the beta-version.
Here are some screenshots of my phone with Xposed installed.
Click to expand...
Click to collapse
Thanks. Yup, I already installed it last night. Only took a couple minutes and have had no problems with it today at work. I rarely have had issues with Xposed in the past. Even though it's called beta3, don't expect an upgrade. It's pretty much as good as its going to get. I think it's called a beta only to let people know there are no guarantees, but it's usually a pretty solid piece of software.
shunsai said:
Thanks. Yup, I already installed it last night. Only took a couple minutes and have had no problems with it today at work. I rarely have had issues with Xposed in the past. Even though it's called beta3, don't expect an upgrade. It's pretty much as good as its going to get. I think it's called a beta only to let people know there are no guarantees, but it's usually a pretty solid piece of software.
Click to expand...
Click to collapse
Thanks for your confirmation, I'm glad that Xposed worked out for you too.
I've tried the other betas but they didn't work for me, and gave me the baseband and sudden unstable reboot, freezing issues, so maybe there will be an upgrade in the future.
But I think you're right, its pretty solid, as for me with the beta-3 version.
shunsai said:
I've been holding off installing Xposed to hear more from others' experience. But I'm getting really tired of the unnecessary icons in the status bar (alarm clock, do not disturb, vibrate, etc.) and I'm not interested in installing a 3rd party launcher. So who else has installed Xposed on the A8? Has anyone else gotten it running without a problem?
Click to expand...
Click to collapse
You don't need root or xposed for that. Goodlock. Or systemui tuner wirh adb to grant permission.
---------- Post added at 03:54 AM ---------- Previous post was at 03:53 AM ----------
Just not vibrate. But most of that can be straightened out yesterday with ease.
mindlery said:
You don't need root or xposed for that. Goodlock. Or systemui tuner wirh adb to grant permission.
---------- Post added at 03:54 AM ---------- Previous post was at 03:53 AM ----------
Just not vibrate. But most of that can be straightened out yesterday with ease.
Click to expand...
Click to collapse
Quite satisfied with Xposed and root. Have had zero problems with it on the A8. Not interested in an app solution, but thanks for the suggestion anyway.
Root... xposed... those are app solutions. But for sure some very good ones. I know what you're getting at.
I was implying solutions that are not ad filled junk.
Hi,
I have Samsung S9 phone (Exynos version) with official Lineage OS 17 installed. Also I have Magisk (package renamed, Magisk Hide is active) as root control app.
Recently I've bought Galaxy Watch (not 2 or 3), installed Wearable, changed system props to be able to run it (as described here: https://forum.xda-developers.com/ga...earable-app-rooted-phone-help-t3838503/page10) and everything works OK, except inability to pay with watch.
When I run Samsung Pay from Wearable app, it tells about unauthorized modifications and exit.
I've found this interesting log, named com.samsung.android.samsungpay.gear.log in the root of internal storage.
In this log (which is XML) I see a section "detections", and there I see next stuff:
<Detection>
Date Time Source Policy Summary Current Warning Ver Name Description
2020-08-15 09:14:31 [7107] 52355100 00004000 00004000 00004000 5.3.0 (ROOTED ) com.topjohnwu.magisk
2020-08-15 09:19:06 [7107] 52355100 00004000 00004000 00004000 5.3.0 (ROOTED ) com.topjohnwu.magisk
</Detection>
I've double-checked, in Magisk I hide it from this Samsung app.
So, my question is - why it still able to detect magisk? And what I can do to be able to pay with watch?
Thank you for pointing this file out. Exactly what I was looking for.
Mine, too, says Magisk is found.
I still can't get the Samsung Wear App to work, but good to get confirmation what it is detecting, Magisk in this case.
I was getting this error on LineageOS even before Magisk. I specifically installed Magisk to see if that hide feature would help.
Now at least I can go back to plain LineageOS without Magisk and see what it says.
Thanks.
DulacLancelot said:
Thank you for pointing this file out. Exactly what I was looking for.
Mine, too, says Magisk is found.
I still can't get the Samsung Wear App to work, but good to get confirmation what it is detecting, Magisk in this case.
I was getting this error on LineageOS even before Magisk. I specifically installed Magisk to see if that hide feature would help.
Now at least I can go back to plain LineageOS without Magisk and see what it says.
Thanks.
Click to expand...
Click to collapse
Eh. I uninstalled Magisk. And the LineageOS root functionality is disabled. Wear Samsung Pay still detects root, and flags it multiples times as "MAGISK-11" or "MAGISK-2" or "framework".
Samsung Pay will never work on rooted devices. It's related to knox services.
w41ru5 said:
Samsung Pay will never work on rooted devices. It's related to knox services.
Click to expand...
Click to collapse
Wrong. I've had Samsung pay working on my watch with rooted pixel 3a xl
And i have it on my rooted Pixel 2 XL....
Install Magisk
Enable MagiskHide
MagiskHide all Samsung apps
Rename Magisk Manager
Do this before opening Samsung Pay
i root my sm-t970 but i cant use app like netflix because my safetynet is locked...someone of you can advise me of to do that? or any other solutions?
davidlu333392 said:
i root my sm-t970 but i cant use app like netflix because my safetynet is locked...someone of you can advise me of to do that? or any other solutions?
Click to expand...
Click to collapse
Magisk hide.
Magisk hide seems to require props fingerprint. Currently there are no official fingerprint for galaxy tab s7, or plus
Waiting for this
I'm about to become your favorite person ever, everyone! I am currently passing SafetyNet after flashing the kdrag0n safetynet-fix to my Samsung Galaxy Tab S7+ SM-T970 and enabling the MagiskHide Props Config module in Magisk.
HOWEVER, as was the case with literally all of the stock-based ROMs for the Galaxy S8, it appears that there will still be issues with a select few apps. For example, you will get soft-banned from Snapchat every few days. Also, certain healthcare apps will still be able to detect root (likely all related to Knox, since a Pixel 5 rooted via the same methods will launch the same apps without issue).
All the best from your fellow tinkerer - Godless1
(P.S. I'm going to copy and paste this into its own thread for better visibility.)
Godless1 said:
I'm about to become your favorite person ever, everyone! I am currently passing SafetyNet after flashing the kdrag0n safetynet-fix to my Samsung Galaxy Tab S7+ SM-T970 and enabling the MagiskHide Props Config module in Magisk.
HOWEVER, as was the case with literally all of the stock-based ROMs for the Galaxy S8, it appears that there will still be issues with a select few apps. For example, you will get soft-banned from Snapchat every few days. Also, certain healthcare apps will still be able to detect root (likely all related to Knox, since a Pixel 5 rooted via the same methods will launch the same apps without issue).
All the best from your fellow tinkerer - Godless1
(P.S. I'm going to copy and paste this into its own thread for better visibility.)
Click to expand...
Click to collapse
It worked on my samsung galaxy tab s7 (sm-t870) thanks!
So I downloaded Netflix today on a rooter Poco F3 with Xiaomi.eu and it throws me a 5.2 error meaning that I can't watch any videos. I have tried a method with a magisk module called liboemencrypt disabler but it didn't help at all. Any help?
stavrosbin said:
So I downloaded Netflix today on a rooter Poco F3 with Xiaomi.eu and it throws me a 5.2 error meaning that I can't watch any videos. I have tried a method with a magisk module called liboemencrypt disabler but it didn't help at all. Any help?
Click to expand...
Click to collapse
ianmacd said:
Apps that use liboemcrypto.so to play content protected by DRM, such as Netflix and My5, will fail when playback is attempted on a rooted device.
The symptoms displayed by affected devices vary by brand and Android version. Some devices may display an obscure error message when you attempt playback. Others may just appear stuck loading the requested content.
This Magisk module fixes the problem by masking liboemcrypto.so with a zero byte replacement. Whilst the same effect could be achieved by simply deleting or renaming liboemcrypto.so with a root-enabled file manager, this has the disadvantage of altering your /system partition by writing to the file-system. The advantage of the Magisk method is that no actual changes are made to the device. The problematic file is merely concealed from the apps that attempt to use it.
To use the module, flash it in the Modules section of Magisk Manager and then reboot your device.
The module works when the library in question is located at either /system/lib/liboemcrypto.so or /system/vendor/lib/liboemcrypto.so. If your library is located elsewhere (or missing), this module will have no effect (but it's harmless to try it).
The module has been verified working on a Samsung Galaxy S9+ (SM-G965F/DS) running Magisk 16.x/17.x/18.x on a variery of ROMs, on a Samsung Tab S3 (SM-T820) running stock Android 8.0 and Magisk 16.x/17.x, and on a Samsung Tab S4 (SM-T830) running stock Android 8.1 and Magisk 17.x/18.x. It was created because a similar module on XDA did not work on my devices. It is being released by popular request, because a number of other users contacted me with the same complaint.
The module was integrated into the official Magisk module repository on 2018-06-27, and can therefore be directly downloaded from within the Magisk Manager app.
Please note that a consequence of using this module is that Widevine DRM will fall back to using L3 instead of L1. This means that Netflix will play all content in SD quality, regardless of your subscription type. Of course, without this module, you won't be able to play anything on a rooted device, so beggars can't be choosers.
Change log:
2020-12-20: v1.5
Updated for Magisk v21 template format.
2019-03-29: v1.4
Updated for Magisk v19 template format.
Issue a warning if installed on an S10e (G970F), S10 (G973F) or S10+ (G975F).
2018-12-06: v1.3
Added support for devices that have the library under either /system/lib64 or /system/vendor/lib64.
Added support for devices that have the library in multiple locations.
2018-07-22: v1.2
Added logic to install in only the appropriate library directory, rather than in both.
2018-05-29: v1.1
Added support for devices that have the library under /system/vendor/lib instead of /system/lib.
2018-04-23: v1.0
Initial release.
Click to expand...
Click to collapse
Here
Kenora_I said:
Here
Click to expand...
Click to collapse
cant you use magisk hide and then use netflix?
That dosent work lmao, because of widevine
Netflix dosent allow rooted devices to use it or smth with rooting messes up with the widevine drm so.
Kenora_I said:
Here
Click to expand...
Click to collapse
Oh so that means I am losing L1? Is there a way to dodge this somehow?
You lose L3 not L1 why this is an issue I'm not sure.
Im not well versed in DRM bypasses
stavrosbin said:
So I downloaded Netflix today on a rooter Poco F3 with Xiaomi.eu and it throws me a 5.2 error meaning that I can't watch any videos. I have tried a method with a magisk module called liboemencrypt disabler but it didn't help at all. Any help?
Click to expand...
Click to collapse
You messed EU rom with some doubtfully modification.
EU rom is full L1 level and NETFLIX compliant.
lolo9393 said:
You messed EU rom with some doubtfully modification.
EU rom is full L1 level and NETFLIX compliant.
Click to expand...
Click to collapse
Yeah I deleted Netflix and reinstalled it and everything works again.