Themes / Apps / Mods [APP][XPOSED/MAGISK] KnoxPatch v0.5.2 - Restore Samsung Knox features

[waterpolo]

Tried, but could not get to safemode anymore with the keycombo
Tested the procedure before the bootloop and was working fine

Tried the knoxpatch on an older phone and was working fine,
maybe it's due to the newer zygisk module in Magisk 26.0+ or the Ambasadii Cruel Kernel ?

Why Ambasadii Cruel Kernel? Is this released for Samsung S23?
My previous device was Samsung S10e with Ambasadii ROM.

 

[ReMiOS]

Why Ambasadii Cruel Kernel? Is this released for Samsung S23?
My previous device was Samsung S10e with Ambasadii ROM.

My device is a Samsung S10+ SM-G975F with no Ramdisk
In order to get Magisk root after a reboot i have to use a key combo to load the recovery before loading system.
The Ambasadii Cruel Kernel makes it possible to have root after a normal reboot

Dit the knoxpatch work on your S10E device without bootlooping ?
and did you also have Android12 and Magisk 26.1 ?

 

[waterpolo]

My device is a Samsung S10+ SM-G975F with no Ramdisk
In order to get Magisk root after a reboot i have to use a key combo to load the recovery before loading system.
The Ambasadii Cruel Kernel makes it possible to have root after a normal reboot

Dit the knoxpatch work on your S10E device without bootlooping ?
and did you also have Android12 and Magisk 26.1 ?

I installed Ambasadii ROM. I read that there was some issue with Magisk 26, but later release (26.1) should be working fine. That is Android 12.

But this is off topic for KnoxPatch.

 

[ReMiOS]

I installed Ambasadii ROM. I read that there was some issue with Magisk 26, but later release (26.1) should be working fine. That is Android 12.

But this is off topic for KnoxPatch.

Thanks for your reply

I don't believe this is off topic, since i get a bootloop after installing knoxpatch on my device (twice)

I would like to know how to get out of the bootloop without wiping all data
and if there are other users who have knoxpatch working with Magisk 26.1 (and possibly a Cruel Kernel)

 

[qounik]

Will it work if I sideload the apps, i.e., Secure Folder. I don't have it with my ROM also anyway to patch dual Messager for all apps.
Edit Secure Folder hasn't work, Says Contact Manufacturer But SHealth Works And Secured Folder isn't even recommended on module page tho selected It and still doesn't work. Please Advice

 

[BlackMesa123]

Will it work if I sideload the apps, i.e., Secure Folder. I don't have it with my ROM also anyway to patch dual Messager for all apps.
Edit Secure Folder hasn't work, Says Contact Manufacturer But SHealth Works And Secured Folder isn't even recommended on module page tho selected It and still doesn't work. Please Advice

If Secure Folder isn’t already installed in your device it means it is not supported (eg. your device hasn’t Knox or has One UI Core), consider installing a custom ROM if your device has any.

 

[krism0156]

It works only on oneui android? I need working method to install shealth, sgear on aosp rom.

 

[DanGLES3]

It works only on oneui android? I need working method to install shealth, sgear on aosp rom.

GitHub - Simon1511/WearableSpoof: Uses LSPosed to let you run Samsung's Wearable apps on non-OneUI ROMs

Uses LSPosed to let you run Samsung's Wearable apps on non-OneUI ROMs - GitHub - Simon1511/WearableSpoof: Uses LSPosed to let you run Samsung's Wearable apps on non-OneUI ROMs

github.com

 

[DanGLES3]

It works only on oneui android? I need working method to install shealth, sgear on aosp rom.

GitHub - abrahamgcc/SHealthBypass: Avoid Samsung Health restrictions

Avoid Samsung Health restrictions. Contribute to abrahamgcc/SHealthBypass development by creating an account on GitHub.

github.com

Not sure any of these will work as I'm on stock

 

[BlackMesa123]

It works only on oneui android? I need working method to install shealth, sgear on aosp rom.

Yes, the module is One UI-only since Samsung apps work fine on AOSP due to the missing Knox API’s.

 

[BlackMesa123]

GitHub - abrahamgcc/SHealthBypass: Avoid Samsung Health restrictions

Avoid Samsung Health restrictions. Contribute to abrahamgcc/SHealthBypass development by creating an account on GitHub.

github.com

Not sure any of these will work as I'm on stock

This app a similar patch to the KnoxPatch one. However it is not required on AOSP since it does not have Knox, Samsung Health will work out of the box.

 

[krism0156]

Nothing work on pixelexperience aosp rom, try many method and samsung gear still dont work, app on phone find watch but cant instal plugin on watch and play store give me notice (Your device is not compatible with this version) but safetynet in yasnac show pass cts and basic integrity. I havent ideas how to connect watch 5 to phone with aosp rom.

Edit. lsposed and googlespoofforwear module in magisk and clear cache Samsung gear app finally solved problem.

 

[nicoco19]

Hello everyone, I installed and tested on my Samsung Galaxy Z Flip 4 and it works very well. Again a big thank you for the work of the developers and also the sharing with all.

 

[ReMiOS]

Without any debug logs it's hard for me to tell what's the cause.

I've opened an issue on Github and attached logs

 

[ReMiOS]

I highly doubt your issue is caused by this module. Try setting up your phone without any extra Magisk module first and see if the issue persists.

I flashed full stock firmware (BL, AP, CP, CSC) with AP=Magisk_Patched-26100_Recovery.tar
But did not install the "multidisabler-samsung-3.5-corsicanu" in TWRP
Now installing Knoxpatch gave no issues !

Tested Samsung Health wich works fine

I suspect the FBE in the multidisabler caused the issues

For reference i've installed the following on my Samsung S10+ SM-G975F ( Android 12 / OneUI 4.1 )
Magisk 26.1 ( Zygisk=Yes / Denylist=No )
TWRP v3.7.9_9.2 in recovery
TWRP_Bootlogo_patcher_v1.7
Ambasadii_Cruel-HVJ5-G97xF-v6.9-S Kernel ( OS patch level 01-03-2023 )
safetynet-fix-v2.4.0-MOD_1.2
Shamiko-v0.7.1-166-release
LSPosed-v1.8.6-6712-zygisk-release
KnoxPatch-v0.5.2.apk
KnoxPatch-Enhancer-v0.3-fix.zip
BluetoothLibraryPatcher_magisk_2.6.3

 

[xShottaZx]

GitHub - Simon1511/WearableSpoof: Uses LSPosed to let you run Samsung's Wearable apps on non-OneUI ROMs

Uses LSPosed to let you run Samsung's Wearable apps on non-OneUI ROMs - GitHub - Simon1511/WearableSpoof: Uses LSPosed to let you run Samsung's Wearable apps on non-OneUI ROMs

github.com

YOU SIR, have saved my life. Spend hours and hours and this was the answer. Finally got my S10e on latest A13 LineageOS working with my Watch4.

 

[russel5]

@BlackMesa123 hi, can you tell me this is normal too or not. In Lsposed this logs is too much

Spoiler: log

[ 2023-06-04T13:30:12.933    10424: 27168: 27168 I/LSPosed-Bridge  ] [KnoxPatch][E][com.samsung.android.shealthmonitor]-->
[ 2023-06-04T13:30:12.933    10424: 27168: 27168 E/LSPosed-Bridge  ] java.io.IOException
    at uh.d(Unknown Source:298)
    at uh.a(Unknown Source:53)
    at hy.b(Unknown Source:18)
    at hf.beforeHookedMethod(Unknown Source:31)
    at cJIBxLrOWwU.wzalvDPYGT.XposedBridge$AdditionalHookInfo.callback(Unknown Source:87)
    at LSPHooker_.exec(Unknown Source:11)
    at com.samsung.android.shealthmonitor.util.RootingCheckUtil.checkSuExists(RootingCheckUtil.java:126)
    at com.samsung.android.shealthmonitor.util.RootingCheckUtil.isRooted(RootingCheckUtil.java:178)
    at com.samsung.android.shealthmonitor.ui.activity.BaseAppCompatActivity.checkRootingDevice(BaseAppCompatActivity.java:447)
    at com.samsung.android.shealthmonitor.ui.activity.BaseAppCompatActivity.onStart(BaseAppCompatActivity.java:160)
    at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1510)
    at android.app.Activity.performStart(Activity.java:8616)
    at android.app.ActivityThread.handleStartActivity(ActivityThread.java:4204)
    at android.app.servertransaction.TransactionExecutor.performLifecycleSequence(TransactionExecutor.java:221)
    at android.app.servertransaction.TransactionExecutor.cycleToPath(TransactionExecutor.java:201)
    at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:173)
    at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2574)
    at android.os.Handler.dispatchMessage(Handler.java:106)
    at android.os.Looper.loopOnce(Looper.java:226)
    at android.os.Looper.loop(Looper.java:313)
    at android.app.ActivityThread.main(ActivityThread.java:8757)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:571)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067)

 

[BlackMesa123]

@BlackMesa123 hi, can you tell me this is normal too or not. In Lsposed this logs is too much

Spoiler: log

[ 2023-06-04T13:30:12.933    10424: 27168: 27168 I/LSPosed-Bridge  ] [KnoxPatch][E][com.samsung.android.shealthmonitor]-->
[ 2023-06-04T13:30:12.933    10424: 27168: 27168 E/LSPosed-Bridge  ] java.io.IOException
    at uh.d(Unknown Source:298)
    at uh.a(Unknown Source:53)
    at hy.b(Unknown Source:18)
    at hf.beforeHookedMethod(Unknown Source:31)
    at cJIBxLrOWwU.wzalvDPYGT.XposedBridge$AdditionalHookInfo.callback(Unknown Source:87)
    at LSPHooker_.exec(Unknown Source:11)
    at com.samsung.android.shealthmonitor.util.RootingCheckUtil.checkSuExists(RootingCheckUtil.java:126)
    at com.samsung.android.shealthmonitor.util.RootingCheckUtil.isRooted(RootingCheckUtil.java:178)
    at com.samsung.android.shealthmonitor.ui.activity.BaseAppCompatActivity.checkRootingDevice(BaseAppCompatActivity.java:447)
    at com.samsung.android.shealthmonitor.ui.activity.BaseAppCompatActivity.onStart(BaseAppCompatActivity.java:160)
    at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1510)
    at android.app.Activity.performStart(Activity.java:8616)
    at android.app.ActivityThread.handleStartActivity(ActivityThread.java:4204)
    at android.app.servertransaction.TransactionExecutor.performLifecycleSequence(TransactionExecutor.java:221)
    at android.app.servertransaction.TransactionExecutor.cycleToPath(TransactionExecutor.java:201)
    at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:173)
    at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2574)
    at android.os.Handler.dispatchMessage(Handler.java:106)
    at android.os.Looper.loopOnce(Looper.java:226)
    at android.os.Looper.loop(Looper.java:313)
    at android.app.ActivityThread.main(ActivityThread.java:8757)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:571)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067)

Similar to issue #29, nothing to worry about.