Hi. I started with android builds and i was able to build my own images of lineage os 17 for lg nexus 4(mako) and xiaomi mi 9t(davinci). For xiaomi i have a problem that system detects unlocked bootloader. Do you know what need to be changed in android code to hide bootloader status for safetynet?
Likely this:
https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/
Didgeridoohan said:
Likely this:
https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/
Click to expand...
Click to collapse
Thanks. I tried those patches https://github.com/ProtonAOSP/android_system_security/commit/qt but still safety net detect unlocked bootloader. Do you have any idea how to fix it? I rebuild lineage os from scratch. I removed out dir and execute mka clean. So i think that changes are included in new build.
skoczo said:
Thanks. I tried those patches https://github.com/ProtonAOSP/android_system_security/commit/qt but still safety net detect unlocked bootloader. Do you have any idea how to fix it? I rebuild lineage os from scratch. I removed out dir and execute mka clean. So i think that changes are included in new build.
Click to expand...
Click to collapse
Well, besides those patches you'd probably also have to change the props that are associated with an unlocked bootloader. Just like Magisk does it:
https://github.com/topjohnwu/Magisk...bc1/native/jni/magiskhide/hide_policy.cpp#L12
Didgeridoohan said:
Well, besides those patches you'd probably also have to change the props that are associated with an unlocked bootloader. Just like Magisk does it:
https://github.com/topjohnwu/Magisk...bc1/native/jni/magiskhide/hide_policy.cpp#L12
Click to expand...
Click to collapse
I can't find place where those properties are set :/. I'm thinking about creating new app in c++ and run it together with android, like service. Do you know how to do this? Currently i'm looking on frameworks/native/services but i'm not sure if this is a right way. This service will monitor system parameters which magisk is chainging in hide_policy and change to 'proper' values.
skoczo said:
I can't find place where those properties are set :/. I'm thinking about creating new app in c++ and run it together with android, like service. Do you know how to do this? Currently i'm looking on frameworks/native/services but i'm not sure if this is a right way. This service will monitor system parameters which magisk is chainging in hide_policy and change to 'proper' values.
Click to expand...
Click to collapse
you ever some up with a solution? i hear this is more of a issue now with some apps on Lineage and OPO devices running android 12
any one can help me to bypass broken TEE (Trusted Execution Environment)
I Have redmagic 7 pro global edition
i m on MAGISK 24.3
(android 12)
i have installed this module (safetynet-fix-v2.2.1) and (shamiko-v0.5.0-112-release)
thanks
Aliak96 said:
any one can help me to bypass broken TEE (Trusted Execution Environment)
I Have redmagic 7 pro global edition
i m on MAGISK 24.3
(android 12)
i have installed this module (safetynet-fix-v2.2.1) and (shamiko-v0.5.0-112-release)
thanks
Click to expand...
Click to collapse
Plz tell me how to fix
My devic infinix zero x neo
How to fix my device infinix zero x neo
Am installed module
Safety net fix latest
And
Shamiko latest
TahirXmehmood said:
View attachment 5678729
Click to expand...
Click to collapse
how to fix plz plz
You cannot hide bootloader status
huskydg said:
You cannot hide bootloader status
Click to expand...
Click to collapse
Yes we can =) Need to be more clever and do not try to hide or fake. Try to flash some partitions with correct info .
newbe1 said:
Yes we can =) Need to be more clever and do not try to hide or fake. Try to flash some partitions with correct info .
Click to expand...
Click to collapse
could you please elaborate? I'd very much like to use an app that refuses to run on phones with unlocked bootloader (while still beeing rooted which requires an unlocked bootloader...)
Just stopped by with the same question. I've used MagiskHide and hidden the Magisk app to do what I can. The unlock bootloader setting is still turned on with a message saying the bootloader is locked.
"fastboot flashing lock" would change that and I may be able to install the patched boot.img with SP Flash Tool.
Device is an RFinder B1+(14), similar to the RFinder B1+ and the Runbo E81. It has a MTK 6765 (Helio P35) chipset. I'm hesitant to screw with the bootloader again on a $2,000 device. I already had bricked it once and recovered, even the developers were stumped.
Just thinking out loud here. BTW, this idea may work with several MTK devices and I know the 22 Moto G Power runs the same CPU with less RAM (6765 Helio p37). My B1+ has 6GB of RAM, the 'Power only has 4.
Related
Hello guys has anyone found a way to pass safety net/ play PoGo (Pokémon GO) on a MM/N custom roms? I did everything and still doesnt pass. Unroot w/ Super SU, change policy permissions, but still nothing in any MM rom. If u did find the way of passing Safetynet/ playing PoGo please share it with me would be so much grateful. Thanks for your time reading this
eskocz said:
Hello guys has anyone found a way to pass safety net/ play PoGo (Pokémon GO) on a MM/N custom roms? I did everything and still doesnt pass. Unroot w/ Super SU, change policy permissions, but still nothing in any MM rom. If u did find the way of passing Safetynet/ playing PoGo please share it with me would be so much grateful. Thanks for your time reading this
Click to expand...
Click to collapse
Setup dualboot with MIUI then you can use it.
I got sth better search in Google:
Microg
Follow installation instructions and you're good
Did you try Magisk?
Deic said:
Did you try Magisk?
Click to expand...
Click to collapse
i totally unrooted phone
eskocz said:
i totally unrooted phone
Click to expand...
Click to collapse
Try replace these props in /system/build.pop with this
Code:
ro.build.description=hermes-user 5.0.2 LRX22G V8.2.1.0.LHMCNDL release-keys
ro.build.fingerprint=Xiaomi/hermes/hermes:5.0.2/LRX22G/V8.2.1.0.LHMCNDL:user/release-keys
and use Magisk to have root and enable Magisk Hide in the Magisk Manager settings.
Deic said:
Try replace these props in /system/build.pop with this
Code:
ro.build.description=hermes-user 5.0.2 LRX22G V8.2.1.0.LHMCNDL release-keys
ro.build.fingerprint=Xiaomi/hermes/hermes:5.0.2/LRX22G/V8.2.1.0.LHMCNDL:user/release-keys
and use Magisk to have root and enable Magisk Hide in the Magisk Manager settings.
Click to expand...
Click to collapse
Check the name of thread. I can pass safetynet on 5.0 but cant on MM
eskocz said:
Check the name of thread. I can pass safetynet on 5.0 but cant on MM
Click to expand...
Click to collapse
man, I saw the name of the thread... Try that props equally without modify that Android version in them and tell me the result
Deic said:
man, I saw the name of the thread... Try that props equally without modify that Android version in them and tell me the result
Click to expand...
Click to collapse
It worked!!! Thanks so much!! (Using Dioleks lineage 6.0)
I've finally figured this out!
This is a scientific breakthrough! Not really... lol
So, I've managed to make SafetyNet pass using a "custom" Magisk build.
I grabbed it from here and so far I've flashed this build and it coaxed SafetyNet into passing. On one treble ROM, ToxycOS, it completely made SafetyNet pass, both ctsProfile and basicIntegrity. On RR official though, it only made basicIntegrity pass. However, that's completely better than nothing at all!
This is how I got SafetyNet to pass completely, it only works if basicIntegrity is passing while ctsProfile if failing.
•Magisk builds: https://github.com/ianmacd/MagiskBuilds
•Magisk I flashed that got SafetyNet to pass: https://github.com/ianmacd/MagiskBuilds/blob/master/Magisk-v16.5-20180621-ianmacd.zip
•Guide to get SafetyNet to pass: https://github.com/phhusson/treble_experimentations/issues/116
Thanks to @topjohnwu for making Magisk possible
Big thanks to @ianmacd for making these Magisk builds
Why did I post this?
I posted this because Magisk 16.6 kept on bootlooping for me, no matter what I did. I'm pretty sure it patches the kernel instead of the ramdisk so it causes a bootloop, again, not 100% sure what it's doing, but either way, it's bootlooping for me. These builds *hopefully* don't bootloop. I flashed 16.5 and it's working great.
crayonicle said:
Why did I post this?
I posted this because Magisk 16.6 kept on bootlooping for me, no matter what I did. I'm pretty sure it patches the kernel instead of the ramdisk so it causes a bootloop, again, not 100% sure what it's doing, but either way, it's bootlooping for me. These builds *hopefully* don't bootloop. I flashed 16.5 and it's working great.
Click to expand...
Click to collapse
yo you can always change the device's fingerprint in order to make safetynet pass using a magisk module
crayonicle said:
Why did I post this?
I posted this because Magisk 16.6 kept on bootlooping for me, no matter what I did. I'm pretty sure it patches the kernel instead of the ramdisk so it causes a bootloop, again, not 100% sure what it's doing, but either way, it's bootlooping for me. These builds *hopefully* don't bootloop. I flashed 16.5 and it's working great.
Click to expand...
Click to collapse
Which version on 16.5 did you use i meant the build date
adb debug working?
huawei p8 lite 2017
phh treble rom gsi vanilla v22
Thanks to everyone but the guy who actually discovered and documented this? Hmph!
It works on BDN-L34
I passed the test successfully following this guide.
I used a Huawei Mate SE (BND-L34) running phusson's [AOSP 8.1 - Phh-Treble] v22. Then downloaded iammacd'smagisk build that the op provided and zip flashed it through TWRP. Then logged on android and uninstalled the magisk manager app (which was an older version) and then downloaded the newest one available and installed it as an apk. After that I opened the app and went to "downloads" and looked for MagiskHide Props, installed the module and rebooted phone. Then as the op did, I followed cawilliamson's instructions on how to set up MagiskHide Props the only difference being that I set up the fingerprint using Huawei mate 9 since Honor 7x were not listed.
I was running and failing at different points the SafetyNet test until I completed the process. Thats it, thanks to crayonicle for research and compiling such great information and to the other people that made it possible. :good:
IonDEfeso said:
I passed the test successfully following this guide.
I used a Huawei Mate SE (BND-L34) running phusson's [AOSP 8.1 - Phh-Treble] v22. Then downloaded iammacd'smagisk build that the op provided and zip flashed it through TWRP. Then logged on android and uninstalled the magisk manager app (which was an older version) and then downloaded the newest one available and installed it as an apk. After that I opened the app and went to "downloads" and looked for MagiskHide Props, installed the module and rebooted phone. Then as the op did, I followed cawilliamson's instructions on how to set up MagiskHide Props the only difference being that I set up the fingerprint using Huawei mate 9 since Honor 7x were not listed.
I was running and failing at different points the SafetyNet test until I completed the process. Thats it, thanks to crayonicle for research and compiling such great information and to the other people that made it possible. :good:
Click to expand...
Click to collapse
Have an Mate 9. What can I do for now? The Magisk-v16.5-20180621-ianmacd.zip dosen´t work for me. It´s bootloped!
chrisaw said:
Thanks to everyone but the guy who actually discovered and documented this? Hmph!
Click to expand...
Click to collapse
I got his permission to post this on Telegram.
Don't worry.
krlosoul said:
adb debug working?
huawei p8 lite 2017
phh treble rom gsi vanilla v22
Click to expand...
Click to collapse
It seems to be. You can always try and test it yourself.
Ashley david said:
Which version on 16.5 did you use i meant the build date
Click to expand...
Click to collapse
2018-6-21
BTW ive just updated to the "MagiskManager-v16.8-2018071902" which is ianmacd's lastest build posted and (first of all isnt bootlooping) and is also passing all of the SafetyNet tests. Also installed the lastest version of the Magisk Manager app 5.8.3 (129) successfully. Not sure if is helpful to report that but since it boot-looped me when I tried to update it last time, so now I consider it an achievement lol. I first uninstalled magisk manager through android uninstall (not the magisk uninstall, which unroots you and delete modules) then installed the new version manually.
-----------------------------------------------------------------------
mcc2005 said:
Have an Mate 9. What can I do for now? The Magisk-v16.5-20180621-ianmacd.zip dosen´t work for me. It´s bootloped!
Click to expand...
Click to collapse
I am no expert but what ROM are you running? I used to have RRO v6 and the boot loping happened to me when I updated magisk to lastest version through the app. Try flashing the older magisk you had before?
If not I think you will have to go back to stock which is what I had to do when that happened to me. I used a stock oreo zip rom for my device (BND-L34) and this guide now since you have the MATE 9 I dont know what the procedures and files needed for that one.
Using a BDN-L34 (Mate SE)
Back to report that I successfully flashed [8.1.0][TREBLE] Pixel Experience [AOSP][r36][2018/07/14] by jhenrique09 (8.1.0-20180714-0200-OFFICIAL) and sucessfully installed the last Magisk version (and app) and passed all the tests (even better it help me bypass the "google uncertified device" messages i was getting). To pass the SafetyNet I downloaded the MagiskHide on the Magisk app "Downloads" then ran a terminal emulator with the following commands.
Code:
su
props
Then only needed to set the fingerprint by doing:
1 > F > * > ** > Y > Y (This last option will make the device reboot, needed to pass SafetyNet, but you can reboot later by writing N)
*Note that you need to select your phones brand in the options given there.
**Select your phone model (or any other model with the same fingerprint reader or compatibility, guess you can try out different models and check if any works, at your own risk though, I dont know if there could be grave repercussions.)
IonDEfeso said:
*Note that you need to select your phones brand in the options given there.
**Select your phone model (or any other model with the same fingerprint reader or compatibility, guess you can try out different models and check if any works, at your own risk though, I dont know if there could be grave repercussions.)
Click to expand...
Click to collapse
You dont exactly need to select your device model. I followed this guide using an Honor 7x. Worked well.
crayonicle said:
You dont exactly need to select your device model. I followed this guide using an Honor 7x. Worked well.
Click to expand...
Click to collapse
Yeah I selected honor 9 for my Mate SE, I just mentioned that since I dont know how serious would it be the implications of selecting a totally different model for another phone but yeah just didn't wanted to tell people to select whatever and then suddenly their fingerprint isn't working or something like that haha. Btw i used the same guide you provided the first time i did everything he pointed but then realized that only the first step was enough so only did that.
steven360 said:
You dont exactly need to select your device model. I followed this guide using an Honor 7x. Worked well.
Click to expand...
Click to collapse
I did it on a Moto G5 with the latest Viper OS Oreo release, it doesn't work, can you help me please?
HourlongTuna5 said:
I did it on a Moto G5 with the latest Viper OS Oreo release, it doesn't work, can you help me please?
Click to expand...
Click to collapse
I'm afraid that this fix might be for Huawei only (no proof yet), maybe perhaps you can try with a similar moto phone?
Hi all,
I just modified the module from @snowwolf725 to have a newer template so it can run on oreo rom
If you need to use nfc-sim on oneplus 3/3t you could try this module.
[Install]
1. Get Magisk
2. In the download area search for "OnePlus 3/t NFC Sim Enabler"
3. Reboot
4. If your manage app require permission you can give it at settings-apps-app permissions-additional permissions, toggle smartcardservice for it
I only test it on OOS Oreo ROM, it may not work on custom rom due to different framework built in.
You can report here so I'll check what other MOD have to add to make other ROM work.
the smartcardservice is modified from SEEK for Android by Johnzweng
Repo link
crazymika said:
Hi all,
I just modified the module from @snowwolf725 to have a newer template so it can run on oreo rom
If you need to use nfc-sim on oneplus 3/3t you could try this module.
[Install]
1. Get Magisk
2. In the download area search for "OnePlus 3/t NFC Sim Enabler"
3. Reboot
4. If your manage app require permission you can give it at settings-apps-app permissions-additional permissions, toggle smartcardservice for it
I only test it on OOS Oreo ROM, it may not work on custom rom due to different framework built in.
You can report here so I'll check what other MOD have to add to make other ROM work.
the smartcardservice is modified from SEEK for Android by Johnzweng
Repo link
Click to expand...
Click to collapse
Any chance that this mod used on htc m9 with aicp 13.1, rooted with magisk?
tombbb said:
Any chance that this mod used on htc m9 with aicp 13.1, rooted with magisk?
Click to expand...
Click to collapse
I don't think so, it's NFC chip specified so if you have a different device it's xml config would be different.
For m9 you could look through it's stock rom to adjust configuration, I believe the M9 stock ROM support NFC-SIM card.
What does nfc sim means?
prasant737 said:
What does nfc sim means?
Click to expand...
Click to collapse
In some places we have our payment/transportation card integrated in SIM card.
so we can use our phone to pay/take public transportation.
hi sir able to update it for oneplus 6t android pie?
laocheebye said:
hi sir able to update it for oneplus 6t android pie?
Click to expand...
Click to collapse
according your ID I assume you are Taiwanese, there is modification for oneplus 6 on mobile01, i think that will also work for 6t
I didn't have 6t so I can't test on it.
crazymika said:
according your ID I assume you are Taiwanese, there is modification for oneplus 6 on mobile01, i think that will also work for 6t
I didn't have 6t so I can't test on it.
Click to expand...
Click to collapse
i am singaporean actually. can u link me the thread? i can read chinese so its fine. thank you deep deep.
---------- Post added at 02:27 PM ---------- Previous post was at 02:12 PM ----------
i found the thread and the download link if anyone is interested to try for oneplus 6 or 6t.
forum link in chinese
flashable zip
i havent tried cos there is no decrypt twrp for 6t yet so at your own risk people.
I had asked about it to the author directly on github since since my test are not successful. No update since then...
https://github.com/Magisk-Modules-Repo/oneplus3simnfc/issues/2
NoobZik said:
I had asked about it to the author directly on github since since my test are not successful. No update since then...
https://github.com/Magisk-Modules-Repo/oneplus3simnfc/issues/2
Click to expand...
Click to collapse
I'll update this to pie compatible when oos pie released
crazymika said:
I'll update this to pie compatible when oos pie released
Click to expand...
Click to collapse
Hello, any news ?
Hi, just tried the latest v1.2.1, but it seems HamiPay detects root even MagiskHide enabled for it. Would you please share how to prevent HamiPay from detecting root? Thank you.
jekyll530 said:
Hi, just tried the latest v1.2.1, but it seems HamiPay detects root even MagiskHide enabled for it. Would you please share how to prevent HamiPay from detecting root? Thank you.
Click to expand...
Click to collapse
I think they changed the root detection, now it's can only use with iPASS, EasyCard or icash.
Creditcard function have been lock with rooted devices.
crazymika said:
I think they changed the root detection, now it's can only use with iPASS, EasyCard or icash.
Creditcard function have been lock with rooted devices.
Click to expand...
Click to collapse
Thank you for replying. The above seems work fine. Can this module be ported for OP5/T, 6/T (OOS 9.0) or even 7/Pro?
Cuvillier said:
Hello, any news ?
Click to expand...
Click to collapse
I've update to Pie rom, and confirm that we still can use sim NFC at it, just need some path adjustments, use the attached zip file replace your system/vendor/etc/libnfc-nxp.conf, put the SmartcardService folder in system/priv-app folder
add this line "persist.nfc.smartcard.config=SIM1,eSE1" in system/build.prop file, and should work as before.
I forgot how to make it into proper Magisk Module~the module i made tonight can't not be installed.... so strange. I'll update once i get it to work.
P.S.
I tried custom ROMs, they have many differences about NFC config, I can not get it to work even replace the framework and permission file, tried everything I know but still failed, maybe they missed something at more lower level.
updated for OOS Pie
I just found what's wrong.
Here's the updated Module for OOS Pie.
Later i'll update to Modules-Repo
jekyll530 said:
Thank you for replying. The above seems work fine. Can this module be ported for OP5/T, 6/T (OOS 9.0) or even 7/Pro?
Click to expand...
Click to collapse
@snowwolf725 have created the OP5 module, 6/6t have other method to make it working,but I need check some of it's file to make sure, op7 should work in theory, but it still depend on some rom configuration. I only have a op3t, do don't know how other models work.
Currently OOS have proper components (driver, config, frameworks...) installed, so it easier to enable them, for custom rom or future builds(which OP3 won't have)
I believe that require more adjustments to have this feature working.
crazymika said:
@snowwolf725 have created the OP5 module, 6/6t have other method to make it working,but I need check some of it's file to make sure, op7 should work in theory, but it still depend on some rom configuration. I only have a op3t, do don't know how other models work.
Currently OOS have proper components (driver, config, frameworks...) installed, so it easier to enable them, for custom rom or future builds(which OP3 won't have)
I believe that require more adjustments to have this feature working.
Click to expand...
Click to collapse
The OP5/T module is not available via Magisk download now. I'm currently using OP5 and will buy a 7 Pro. If you need, I can help testing.
crazymika said:
@snowwolf725 have created the OP5 module, 6/6t have other method to make it working,but I need check some of it's file to make sure, op7 should work in theory, but it still depend on some rom configuration. I only have a op3t, do don't know how other models work.
Currently OOS have proper components (driver, config, frameworks...) installed, so it easier to enable them, for custom rom or future builds(which OP3 won't have)
I believe that require more adjustments to have this feature working.
Click to expand...
Click to collapse
thanks but it doesn't work on lineage os 16. in logcat i get keymaster operation failed and unsupported digest on km1 hal issue. i hope you can fix it
regards
No information, because xda`s moder delete some my post
Gaspaddar said:
Description:
-normal AOSP
-must unlock bootloader
Positive
Play Market is pre-installed
Root is pre-installed, it works fully (the magic analog can change the system)
Minuses
Bad headphone signal
GPay won't work
Maybe something else @Gaspadar
Installation
Reboot into Bootloader
Connect your smartphone to your computer
Register via adb
fastboot flash system AOSP.img
Link
Click to expand...
Click to collapse
Nice bro
Can you share some screenshots?
Can i rollback to emui if i want after installing this?
I'm very happy with this
How to flash magisk and root?
Can we get twrp?
Is there any hope for android 11 and 12 for our device in future?
alisadeghian said:
Is there any hope for android 11 and 12 for our device in future?
Click to expand...
Click to collapse
1) Check guide, root yet, screen not have, because working with my version emui
2) Instruction in guides
3)In our device R has yet, but many problem with vendor
Gaspaddar said:
1) Check guide, root yet, screen not have, because working with my version emui
2) Instruction in guides
3)In our device R has yet, but many problem with vendor
Click to expand...
Click to collapse
Aw
Ok Thanks
This is a magisk module that patches/enable Secure Folder and more to work on rooted phones. A52 5G EditionFor more mods for the A52, also try: A52-Hidden-ModsNote: It should only be used on the Galaxy A52 (SM-A526B). Testing on other devices is at your own risk.
In case something doesn't work, remove the module. It will revert everything to its normal state.
If you bootloop (Which is extremely unlikely), boot into safe mode and remove the module.
If you stumble on any problems, please open a new issue on GitHub. I will take care of it ASAP.
Known bugs:
None. Please report if you find any.
Current Patches:
Fixed Secure Folder
Fixed Secure Wifi
Fixed Private Share
Coming in the future:
S-Health Fix
Samsung Pass Fix
If you're interested, you can find it here.
https://github.com/Sloobot/A52-Patches
Could a future fix also include getting the galaxy wearable app to install from play Store + actually work?
Is the stored information still encrypted in Secure folder using this mod?
Caaapri said:
Could a future fix also include getting the galaxy wearable app to install from play Store + actually work?
Click to expand...
Click to collapse
That's strange that it doesn't work for you because, for me, it works normally. But you can try https://adil.hanney.org/SamsungAppsPatcher/. This patches Samsung health galaxy wearables etc.
Zdrawko0o said:
Is the stored information still encrypted in Secure folder using this mod?
Click to expand...
Click to collapse
From what I know, it should still be encrypted.
Just gonna post a plain reply cause I have no idea how to quote. I'm not sure of it's just the Patched app for my specific watch (GWA2) but it gets to the pairing process than just repeatedly crashes. Would a fix be on the table in the future for this module?
Caaapri said:
Just gonna post a plain reply cause I have no idea how to quote. I'm not sure of it's just the Patched app for my specific watch (GWA2) but it gets to the pairing process than just repeatedly crashes. Would a fix be on the table in the future for this module?
Click to expand...
Click to collapse
I had that problem before when I had a GWA2. You should try SamsungAppsPatcher, and it should fix the problem. If not, send another reply on this thread. https://adil.hanney.org/SamsungAppsPatcher/
Sloobot said:
I had that problem before when I had a GWA2. You should try SamsungAppsPatcher, and it should fix the problem. If not, send another reply on this thread. https://adil.hanney.org/SamsungAppsPatcher/
Click to expand...
Click to collapse
Yep, have tried that aswell as the prop config tweaks and hiding root from every Samsung app. Nothing works haha
Sloobot said:
This is a magisk module that patches/enable Secure Folder and more to work on rooted phones. A52 5G EditionFor more mods for the A52, also try: A52-Hidden-ModsNote: It should only be used on the Galaxy A52 (SM-A526B). Testing on other devices is at your own risk.
In case something doesn't work, remove the module. It will revert everything to its normal state.
If you bootloop (Which is extremely unlikely), boot into safe mode and remove the module.
If you stumble on any problems, please open a new issue on GitHub. I will take care of it ASAP.
Known bugs:
None. Please report if you find any.
Current Patches:
Fixed Secure Folder
Fixed Secure Wifi
Fixed Private Share
Coming in the future:
S-Health Fix
Samsung Pass Fix
If you're interested, you can find it here.
https://github.com/Sloobot/A52-Patches
Click to expand...
Click to collapse
I would love to have smartview unlocked...
Demandred1957 said:
I would love to have smartview unlocked...
Click to expand...
Click to collapse
To fix smartview use the A52-Mods. Its linked in the post
Sloobot said:
To fix smartview use the A52-Mods. Its linked in the post
Click to expand...
Click to collapse
Sadly I have a USA version of the phone, SM-A526U1
Unless you know for sure that would work with my model..
I used to root my own stuff, Note 2-3 but have been out of the scene for quite a while.
Don't want to risk bricking it.
Thanks for the quick reply btw.
Demandred1957 said:
Sadly I have a USA version of the phone, SM-A526U1
Unless you know for sure that would work with my model.
I used to root my own stuff, Note 2-3 but have been out of the scene for quite a while.
Don't want to risk bricking it.
Thanks for the quick reply btw.
Click to expand...
Click to collapse
I'm not really sure but you can always remove the module if it doesn't work. In case of bootloop you can enter safe mode and all the modules will turn off automatically and then restart the phone normally and delete the module and enable the rest that you have.
Sloobot said:
I'm not really sure but you can always remove the module if it doesn't work. In case of bootloop you can enter safe mode and all the modules will turn off automatically and then restart the phone normally and delete the module and enable the rest that you have.
Click to expand...
Click to collapse
ok, thanks!
I may man up and try it then, since it really irked me that Samsung software locked what I would consider a basic function of the phone, to force USA customers to buy a flagship phone for that feature.
Demandred1957 said:
ok, thanks!
I may man up and try it then, since it really irked me that Samsung software locked what I would consider a basic function of the phone, to force USA customers to buy a flagship phone for that feature.
Click to expand...
Click to collapse
Well sad news for you, U.S. phones have their bootloaders permanently locked so you won't be able to use Magisk to gain root access or even install this module.
ShaDisNX255 said:
Well sad news for you, U.S. phones have their bootloaders permanently locked so you won't be able to use Magisk to gain root access or even install this module.
Click to expand...
Click to collapse
I bought the unlocked model direct from Samsung.
So Maybe I can.
Demandred1957 said:
I bought the unlocked model direct from Samsung.
So Maybe I can.
Click to expand...
Click to collapse
Nope, both U and U1 variants have permanent locks on their bootloaders unfortunately.
ShaDisNX255 said:
Nope, both U and U1 variants have permanent locks on their bootloaders unfortunately.
Click to expand...
Click to collapse
You have one of U or U1 varients to test this on?
Demandred1957 said:
You have one of U or U1 varients to test this on?
Click to expand...
Click to collapse
Don't believe me? Go right ahead, just try to get OEM Unlock in developer options. Hope you don't spend too much time trying to get it to appear with those date tricks you see online
Sloobot said:
This is a magisk module that patches/enable Secure Folder and more to work on rooted phones. A52 5G EditionFor more mods for the A52, also try: A52-Hidden-ModsNote: It should only be used on the Galaxy A52 (SM-A526B). Testing on other devices is at your own risk.
In case something doesn't work, remove the module. It will revert everything to its normal state.
If you bootloop (Which is extremely unlikely), boot into safe mode and remove the module.
If you stumble on any problems, please open a new issue on GitHub. I will take care of it ASAP.
Known bugs:
None. Please report if you find any.
Current Patches:
Fixed Secure Folder
Fixed Secure Wifi
Fixed Private Share
Coming in the future:
S-Health Fix
Samsung Pass Fix
If you're interested, you can find it here.
https://github.com/Sloobot/A52-Patches
Click to expand...
Click to collapse
I compiled and then stuck on the machine，What did you use to compile knoxsdk.jar?What tool did you use to compile it? thanks