This was my original setup stock unit:
Px3 (1024x600 0)
Android 7.1.2
Patch lvl may 5 2017
Kernel 3.0.101+
Mcu version mtcd_xrc_v2. 58_1
Cpu arm cortex-a9 @1.6ghz (x4
I flashed Hal9k Rom and currently have magisk v18 installed. I then used magisk to install Sony framework to be able to use Sony apps.
I installed remote play and psvue. I then proceeded to hide them with magisk hide. I still get errors for remote play (the one saying my device is rooted) and psvue comes on without the black screen saying it isn't supported for rooted devices. However I can't scroll down the screen to click sign in my account.
If anyone at all can help me, I would be very grateful and so would my children during long commutes to and from.
UPDATE: I got PSVue to work flawlessly. And I though I got remote play working but unfortunately, it will not register ps4, however the app itself isn't blocker or detects my root. Getting closer to my overall goal.
Related
Has anyone successfully paired either a Sixaxis or DS3 controller to their Pixel 2 XL
I changed the MAC address to match the device and I've tried all of the following with Magisk.
Stock 8.1
Stock 8.1 w/ Flash Kernel
LineageOS
Are there any build.prop mods that I could use to force bluetooth to make this connection?
I read of someone having trouble on their LG V20 using Magisk instead of SuperSU, but I'm not convinced that would help. I have two Le Eco S2's running crDroid (based on LineageOS) with Magisk, and it syncs perfectly.
Sixaxis compatibility app says the device is capable, but the 4 red dots just blink endlessly when trying to pair after the server has been initiated.
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
Hi all,
I currently have Package Disabler Pro installed and it works well to stop all the bloatware running.
Has anyone tried this with the new update?
Thanks - Keith
Is not supported and (at least for my Sm-976V) the boot kernel is upped to 5 trapping me on 11 with the bloat unless rooted
It does work on the latest update, you just need to save the XML, uninstall, run tne OS update, reinstall and load the XML.
Working perfectly well here.
Hi ! My young children had a Galaxy A5 2017 and I flash the custom Rom Rise Q Android 10 OneUi port and work fine.
Just I have a bug with Netflix.
The A5 are root but pass SafetyNet and magisk hide Netflix. I can download it on play store no mistake and connect it I paid for Hd but when she want see a video after 5min error -57 all the time !?
I have test all data cache restart etc but Always when see vidéo after 5/10 minutes of viewing blocks with error -57 ???
I don't understand ? It's the custom Rom ? Or the Soc Exynos ? Or the Ram ?
Thanks
As the workaround section of the XDA thread says you need to install this magisk module: https://github.com/Magisk-Modules-Repo/liboemcryptodisabler
Since the system itself still detects that you are rooted Netflix forbids playback.
The choice you have is to either keep magisk installed and install the module from above (which will make Netflix fall back to DRM L3, which means no HD content) or un-install magisk which will keep DRM L1 and HD content.
Also, since Rise-Q passes SafetyNet out of the box I would recommend to uninstall Magisk, but the choice is up to you
Picked up another 10 III for my dad. It came with Android 12 so I was wondering if I should keep it on 12, upgrade to 13, or downgrade to the last 11 (which I believe is 62.0.A.9.11)?
My own 10 III is on 11 and I've been extremely pleased with it but then again my dad is not a power user and won't care too much about the UI changes. And he's coming from Android 9 so whatever I install is going to be different anyway.
Are there any other glaring pros and cons to 12 or 13 that you guys have noticed?
Do they work fine with Magisk btw? I know 11 does. I don't necessarily want to root his phone but root seems the only reliable method of app backup and restore nowadays unfortunately.
I have already used Android 11, 12 and 13. In each case with the Linageos GSI and was very satisfied with all of them.
It has only turned out that the firmware version must match the Android version used and the original vbmeta should be patched and flashed because otherwise the build keys do not match and that can probably lead to problems.
Currently I use LOS 13 (GSI) in conjunction with MindTheGapps and Magisk-Delta and am very happy with the constellation.
That sounds very good. Are you passing safety net well enough to run Netflix, bank apps etc. with LOS?
wirespot said:
Are you passing safety net well enough to run Netflix, bank apps etc. with LOS?
Click to expand...
Click to collapse
Yes.
I use Magsik-Delta in Zygisk mode and hide the app with the Hide function.
Additionally, I use the MagiskHide function to hide Magisk from other applications.
I have also activated LSposed and installed HideMyApplist as a module there. There I created a blacklist with the apps that use root and applied it to the apps that should not see the root apps.
Applist Detector as well as Oprek Detector and Root Beer Sample do not find any residues of Magisk or signs of rooting.
With the Universal SafetyNet Fix (mod version by Displax), YASNAC then also shows me a "Pass" for Basic integrity and CTS profile match.
The PlayStore certifies that it is a certified device.
I use several banking apps and so far I haven't had one that didn't work.
By the way, I still use your UnifiedNlp enabler on the device.