Entrust recently made a change that does not allow rooted devices. Does anyone have an older version Pre-February 28th.
Thanks
RashAPu said:
Entrust recently made a change that does not allow rooted devices. Does anyone have an older version Pre-February 28th.
Thanks
Click to expand...
Click to collapse
Here the link : https://www.dropbox.com/s/bu0di8w734ghy1i/Entrust IdentityGuard Mobile 1.0.4.48.apk
Have fun
shinbi said:
Here the link : https://www.dropbox.com/s/bu0di8w734ghy1i/Entrust IdentityGuard Mobile 1.0.4.48.apk
Have fun
Click to expand...
Click to collapse
Thank you for this. We just switched at work to this app being mandatory instead of the keyfob. And nothing I can find will block the app from the Play Store from finding root. You saved my life!
hawkeyejoe said:
Thank you for this. We just switched at work to this app being mandatory instead of the keyfob. And nothing I can find will block the app from the Play Store from finding root. You saved my life!
Click to expand...
Click to collapse
Don't mentioned bro. Have fun
Thanks for the download!
FWIW, after installing this, I tried to install RootCloak via the Xposed Framework (http://www.droidviews.com/how-to-hide-root-access-from-apps-that-detect-root-on-android/), then added Entrust to the custom app list and then upgrade to the latest version via the Google Play Store and it's working! Not sure if it's necessary to install this old version first or not though.
dmbfan36_23 said:
Thanks for the download!
FWIW, after installing this, I tried to install RootCloak via the Xposed Framework (http://www.droidviews.com/how-to-hide-root-access-from-apps-that-detect-root-on-android/), then added Entrust to the custom app list and then upgrade to the latest version via the Google Play Store and it's working! Not sure if it's necessary to install this old version first or not though.
Click to expand...
Click to collapse
Good stuff dmbfan36_23! I can confirm that this indeed works with Entrust IdentityGuard Mobile using the Xposed Framework version of RootCloak. As a side note, I installed the older version first. Next I setup Entrust IdentityGuard Mobile. Then I used the directions from the link above. Afterwards, I updated the app through the Google Play Store. For the final step, I confirmed that the app still worked after the update.
For more information regarding RootCloak:
http://forum.xda-developers.com/xposed/modules/mod-rootcloak-completely-hide-root-t2574647
Sorry to bump this old thread but it comes up in the search quite often and I found this xposed module which fixes the issue:
http://repo.xposed.info/module/ca.pr0ps.xposed.entrustunblocker
It works great for the latest app version.
Not working for me
I tried this. I rebooted but it didn't work. I thought my phone was rooted, but Titanium app says it's not. I copied the linked apk file to my PC, dropped it to a folder on my LG G2 (build LRX22G) LS980ZVI Android 5.0.2. I opened the file, clicked INSTALL, waited for confirmation. Rebooted the phone (turned it off/on); re-installed Entrust current version on Google Play (updated Aug 27, 2016 supports Nougat 7.0) and get the same error: "Manual activation is not supported on an unsecured device"
What more do I need to do?
What's the latest with Entrust? I'm trying to get the latest Google Play version running with Magisk and some build.prop edits but I'm not having much luck. Anyone have some pointers on what's working now?
ROM: Pure Nexus
Android Version: 7.1.1
Phone: Nexus 6P
Magisk: 11.1
Rooted w/ Magisk
Hide Enabled for Entrust
SafetyNet Passes
clambert11 said:
What's the latest with Entrust? I'm trying to get the latest Google Play version running with Magisk and some build.prop edits but I'm not having much luck. Anyone have some pointers on what's working now?
ROM: Pure Nexus
Android Version: 7.1.1
Phone: Nexus 6P
Magisk: 11.1
Rooted w/ Magisk
Hide Enabled for Entrust
SafetyNet Passes
Click to expand...
Click to collapse
Any update on this? I have a similar setup and I also cannot get Entrust to work. When trying to add a token I receive the error message:
"Manual activation is not supported on an unsecured device"
ROM: Pure Nexus
Android Version: 7.1.1
Phone: Pixel
Magisk: 11.6
Rooted w/ Magisk
Hide Enabled for Entrust
SafetyNet Passes
mfr122887 said:
Any update on this? I have a similar setup and I also cannot get Entrust to work. When trying to add a token I receive the error message:
"Manual activation is not supported on an unsecured device"
ROM: Pure Nexus
Android Version: 7.1.1
Phone: Pixel
Magisk: 11.6
Rooted w/ Magisk
Hide Enabled for Entrust
SafetyNet Passes
Click to expand...
Click to collapse
Nope. Not for me. Still using an Entrust FOB until I figure something out. There is a beta version of Magisk out (v. 13) but I have not tried it yet. I'm running v. 12 without success on this app.
Hey guys... Has anyone managed to use entrust with Magisk hide? I'm running version 14.4 and have tried everything without success. Even though Magisk is hidden, entrust app checked under Magisk hide, developer and adb/usb is disabled... I still get the "can't add manual identities on an unsecured device" message. Any help will be appreciated.
mindol81 said:
Hey guys... Has anyone managed to use entrust with Magisk hide? I'm running version 14.4 and have tried everything without success. Even though Magisk is hidden, entrust app checked under Magisk hide, developer and adb/usb is disabled... I still get the "can't add manual identities on an unsecured device" message. Any help will be appreciated.
Click to expand...
Click to collapse
Remove Busybox
LeoPosas said:
Remove Busybox
Click to expand...
Click to collapse
Dat MVP answer... Thanks for that, ggwp :good:
LeoPosas said:
Remove Busybox
Click to expand...
Click to collapse
SonicGold said:
Dat MVP answer... Thanks for that, ggwp :good:
Click to expand...
Click to collapse
That sounds great but:
1 - I didn't install busybox, nor can I see it under settings/apps.
2 - could you please post detailed instructions on how to get rid of busybox?
This still seems to be a problem in 2021.
And the current version of Entrust ST doesn't even need root to not run, it detects custom ROMs (like the LineageOS 17.1 I'm running on my phone) which are already enough for it to spew out its "unsecured device" message even without being rooted.
At the same time there hasn't been any progress here, I suppose?
Hubertus Bigend said:
This still seems to be a problem in 2021.
And the current version of Entrust ST doesn't even need root to not run, it detects custom ROMs (like the LineageOS 17.1 I'm running on my phone) which are already enough for it to spew out its "unsecured device" message even without being rooted.
At the same time there hasn't been any progress here, I suppose?
Click to expand...
Click to collapse
Hi, a couple of days ago I stumbled onto this issue and there is a fix using an Xposed module called Entrust IdentityGuard Unblocker. To enable it on Android +9, you need to install Riru, EDXposed (both Magisk modules) and then install the IdentityGuard Unblocker module. You can find more detailed guidance online, but you probably already know this. Even though the module per se is a little bit old, it works with the current Entrust IdentityGuard version to this day.
Hope this helps!
Related
This is a simple Xposed module to help you get rid of ads on the official YouTube App.
Requirements:
- Xposed Framwork
How to Install:
- Install Xposed Installer and framework
- Install YouTube AdAway App
- Enable the module on Xposed installer (ex, LSXposed)
- Reboot
Notes:
- Reboot is a MUST after updating the module.
- This application is NOT a modified YouTube App
Bugs Report:
- If you still get an IN-VIDEO ad, please report an issue here with your xposed logs.
Download.
Mirror.
I dont have any issues while using Vanced and SC, along with Magisk too. lol
It was last week. I used the root method.
I got banned from Snapchat 2 days after installing Lucky Patcher & Youtube Vanced. I went to Lucky Patcher and " reinstalled " Snapchat as it was supposed to delete android patches related to Snapchat.
2 days later I got banned once again. I have uninstalled Lucky Patcher and Youtube Vanced, since then no ban from Snapchat (for 1 week)
I think I will try one more time with only Youtube Vanced installed to see what happens but I fear I will definitively banned
Other people have experienced the same issue.
aladdins4ne said:
It was last week. I used the root method.
I got banned from Snapchat 2 days after installing Lucky Patcher & Youtube Vanced. I went to Lucky Patcher and " reinstalled " Snapchat as it was supposed to delete android patches related to Snapchat.
2 days later I got banned once again. I have uninstalled Lucky Patcher and Youtube Vanced, since then no ban from Snapchat (for 1 week)
I think I will try one more time with only Youtube Vanced installed to see what happens but I fear I will definitively banned
Other people have experienced the same issue.
Click to expand...
Click to collapse
Don't use the root method. I never have. Best practice for security in general is to only provide root for apps that truly need it. It's considered bad security design to achieve something with root that could also be achieved without root, hence YouTube Vanced providing a non-root version. Just make sure magisk hide is enabled while you're at it
wanam said:
*snip*
Click to expand...
Click to collapse
Good job! Will you upload to official Xposed repo?
polobunny said:
Good job! Will you upload to official Xposed repo?
Click to expand...
Click to collapse
Done!
wanam said:
Done!
Click to expand...
Click to collapse
Awesome as usual.
Perfect, absolutely without error
Is it possible to disable this app in Xposed, or is it self-enabling?
Thanks
Thanks Mate
The ads Are Still There
Usin iT With Wanamlite 3.3 And Latest Xposed beta Version And Nothin Changed
ameshiya said:
The ads Are Still There
Usin iT With Wanamlite 3.3 And Latest Xposed beta Version And Nothin Changed
Click to expand...
Click to collapse
I'm on the same Rom + Xposed beta with no issues, just make sure the module is enabled, clear YouTube App data. and and reboot.
This application was tested against the latest YouTube update (5.3.24) and it's been downloaded more than 1500 in the last 10 hours with no such reports! if you are using any other version upload it.
EDIT: YouTube AdAway V1.1 posted.
The new update V1.1 requires Xposed framework 2.3+ (API 31+), because it includes some check helpers to detect Xposed installation status.
I am getting ads.. I am on Temasek (cm10.2)
Edit :after updating YouTube nw its working..
Sent from my GT-I9300 using Tapatalk 4
Could you incorporate this into your other wanam xposed?
Sent from my SM-N900T
hisee said:
I am getting ads.. I am on Temasek (cm10.2)
Edit :after updating YouTube nw its working..
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Do you have a backup of the old one, i want to take a look at it.
ktetreault14 said:
Could you incorporate this into your other wanam xposed?
Sent from my SM-N900T
Click to expand...
Click to collapse
I don't think Google will appreciate it on the PlayStore.
Works like a charm on a 2013 gnex7. For some reason youtube had fcs until I rebooted again. Fixed now.
Sent from my Nexus 7 using XDA Premium 4 mobile app
wanam said:
The new update V1.1 requires Xposed framework 2.3+ (API 31+), because it includes some check helpers to detect Xposed installation status.
Click to expand...
Click to collapse
So since you said that this module requires that we be on Xposed Framework 2.3+ (API 31+), I'm gonna assume that this also includes people that are running the new Xposed Framework BETA...? I know for a fact that I haven't installed the BETA yet, but I'm not too sure how I can check and see which Xposed Framework "API" I'm running. When I open up Xposed, I can click on "About" and under "Version of this app:" it shows "2.3.1". How can I check and see which Xposed Framework API I'm running?
Thanks! :good:
jsdecker10 said:
So since you said that this module requires that we be on Xposed Framework 2.3+ (API 31+), I'm gonna assume that this also includes people that are running the new Xposed Framework BETA...? I know for a fact that I haven't installed the BETA yet, but I'm not too sure how I can check and see which Xposed Framework "API" I'm running. When I open up Xposed, I can click on "About" and under "Version of this app:" it shows "2.3.1". How can I check and see which Xposed Framework API I'm running?
Thanks! :good:
Click to expand...
Click to collapse
I'm running the beta2 of Xposed Installer too.
You can check the API version on the framework tab of Xposed installer.
Anyway you will get a notification on the Xposed installer modules list if you are running a lower API level, and you won't be able to activate it, also my App should let you know if the module is not enabled.
Sent from my GT-I9500 using Tapatalk
wanam said:
I'm running the beta2 of Xposed Installer too.
You can check the API version on the framework tab of Xposed installer.
Anyway you will get a notification on the Xposed installer modules list if you are running a lower API level, and you won't be able to activate it, also my App should let you know if the module is not enabled.
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
Thanks for the key info! I took a lil break from fiddling with my phone, but I just now went and messed around a little bit with YouTube and I haven't seen one single embedded "In-Video" ad ! So far, so good!! Thanks man!!! Oh yea, one quick question..how's this module gonna be affected when Google spits out another update to the YouTube app? Is it possible for an update to the YouTube app to "break the functionality" of this module, or do we not really have much to worry about when taking any YouTube updates? Thanks in advance for the info! :good:
wanam said:
i'm on the same rom + xposed beta with no issues, just make sure the module is enabled, clear youtube app data. And and reboot.
This application was tested against the latest youtube update (5.3.24) and it's been downloaded more than 1500 in the last 10 hours with no such reports! If you are using any other version upload it.
Edit: Youtube adaway v1.1 posted.
Click to expand...
Click to collapse
nope im using the latest version with latest xposed beta 2 and i enable it inside the app " disable youtube ads " with latest youtube app ans still the same
i will try to downgrade to non-beta version of xposed and see what happen
regards.
Thanks for the module!
Feature request: provide an option to hide the app icon. It serves me no purpose once the module is installed, and I prefer not to have extraneous apps in my launcher.
after rebootin it seems to work flawless
thanks
goldenratio said:
Feature request: provide an option to hide the app icon..
Click to expand...
Click to collapse
+1
SBXposed bypasses the Xposed restriction in the Sparkasse(+) App.
Requirements
- Xposed Framework
- Sparkasse / Sparkasse+ app at least version 3.0.0
- Android 4.4+
Usage
1. Install SBXposed
2. Activate module in XposedInstaller
3. Reboot
4. Have fun with unblocked app.
Download
You can download the mod via XposedInstaller or directly from Repository: repo.xposed.info/module/tmh.sbxposed
Github: https://github.com/tmhzxy/SBXposed
Support
The module was tested by me on latest CM13 nightly for the latest version of the app. It should be working fine on other ROMs.
Please leave feedback with an Xposed log and the apk from Sparkasse(+) app if not working, so I can take a look at it.
I will not add any new features. This module is only for skipping the Xposed / partial root restriction.
Changelog
1.0: Initial module.
1.1: Fix min. XposedBridge version to 53 for Kitkat.
Works like a charm on Sultans latest cm13 (op3) with xposed and Sparkasse+! Thank you very much!
Works pefectly. I knew this Module would come. Like i statet in my Playstore Review. Thank you very much.
I can run the Sparkasse+ app v3.0.0 without this module. And I have Xposed installed, of course. Why do you need it?
Won't work for me
Hi there,
is there any possibilty for me to activate this app under xposed v.2.6.1? The module keeps telling my xposed is too old (though there are no updates available for me).
Galaxy Note 4, Stock 4.4.4
meiser said:
I can run the Sparkasse+ app v3.0.0 without this module. And I have Xposed installed, of course. Why do you need it?
Click to expand...
Click to collapse
Meanwhile, Xposed detection is installed. Unfortunately, the detection works at most, so I created the module. If this is not the case, your setup would interest me.
Musikologin said:
Hi there,
is there any possibilty for me to activate this gem under xposed v.2.6.1? The module keeps telling my xposed is too old (though there are no updates available for me).
Galaxy Note 4, Vanilla 4.4.4
Click to expand...
Click to collapse
New version published. Should work now.
Thank you! Works great!
@tmh_: Dude i love you ?
Sent from my LG-D855 using XDA Labs
tmh_ said:
Meanwhile, Xposed detection is installed. Unfortunately, the detection works at most, so I created the module. If this is not the case, your setup would interest me.
Click to expand...
Click to collapse
I'm running CM 13.0 nightly (latest version from 2016/11/07) on a OnePlus3, I installed SuperSU 2.78 SR5, suhide 0.55 and seamless Xposed 86.1 by romracer.
tmh_;69867331
New version published. Should work now.[/QUOTE said:
Thank you for your quick update! Unfortunately it still won't work - module is installed and activated via xposed, but after a reboot my sparkasse app (which I have uninstalled and reinstalled again) still thinks I'm a dangerous criminal or whatever... still detects my installed xposed framework.
(BTW cloak root module wouldn't work either.)
Maybe I will just stick with version 2.9.1 as long as possible.
Update: I tried same thing with my daughter's z1 compact running CM11. It doesn't work here either - so it has probably something to do with kitkat roms, no matter if stock or custom.
I'm too old fashioned, can't say goodbye to kitkat...
Click to expand...
Click to collapse
Musikologin said:
tmh_;69867331
New version published. Should work now.[/QUOTE said:
Thank you for your quick update! Unfortunately it still won't work - module is installed and activated via xposed, but after a reboot my sparkasse app (which I have uninstalled and reinstalled again) still thinks I'm a dangerous criminal or whatever... still detects my installed xposed framework.
(BTW cloak root module wouldn't work either.)
Maybe I will just stick with version 2.9.1 as long as possible.
Click to expand...
Click to collapse
I need the Xposed log to understand the error.
Click to expand...
Click to collapse
tmh_ said:
I need the Xposed log to understand the error.
Click to expand...
Click to collapse
Sure, it says:
SBXposed: Try to find protect classes...
SBXposed: 1 classes found
Nothing more I can find related to this module.
Musikologin said:
Sure, it says:
SBXposed: Try to find protect classes...
SBXposed: 1 classes found
Nothing more I can find related to this module.
Click to expand...
Click to collapse
I have built a version in which more things are logged. This logging is explicit only for Android <5.0 and only for debugging, as this is a performance loss.
After testing app, I need the complete Xposed log.
tmh_ said:
I have built a version in which more things are logged. This logging is explicit only for Android <5.0 and only for debugging, as this is a performance loss.
After testing app, I need the complete Xposed log.
Click to expand...
Click to collapse
I really appreciate your effort!
My request now is somewhat embarrassing *cough*:
How exactly do I extract an apk file from the attached zip?
After unzipping all I I get is a bunch of folders and for me rather uncommon file types.
Musikologin said:
I really appreciate your effort!
My request now is somewhat embarrassing *cough*:
How exactly do I extract an apk file from the attached zip?
After unzipping all I I get is a bunch of folders and for me rather uncommon file types.
Click to expand...
Click to collapse
The attachment is the apk. Sometimes the apk may be opened by a program as a zip file.
tmh_ said:
The attachment is the apk. Sometimes the apk may be opened by a program as a zip file.
Click to expand...
Click to collapse
Although it's named apk, it's only shown as a zip file after the download. On my Windows device as well as on my smartphones. I can only flash zips on my phone but that's probably not the way it should work.
Edit: The download via QR worked. I will test it and tell you. Tomorrow. Short baby night ahead .
Thank you!
Thanks man, works flawlessly on my Note 4 with 6.0.1
Thanks, i first used my old sparkasse app from titanium backup until i saw this modul.
Works as expected, thanks for your work.
Works as expected. Great! And thanks [emoji122] [emoji122] [emoji122]
Sent from my XT1562 using XDA-Developers mobile app
Thank you for sharing the module, works just fine. I don't understand how Sparkasse can block everyone out using Xposed...
If xposed is installed Freecharge closes with error message "App has been hooked by third party app, please uninstall third party app and continue" .This module can be used to bypass this restriction.
Requirements
- Xposed Framework
- Freecharge app at least version 7.9.9
- Android 4.0+ (tested only in 6.0, but should be working in other version too)
Usage
1. Install FreeChargeUnblocker
2. Activate module in XposedInstaller
3. Reboot
4. Have fun with unblocked app.
Download
You can download the mod from repo via XposedInstaller
Support
The module was tested by me on 6.0.1 with latest version of the app (7.9.9). It should be working fine on other ROMs.
Please leave feedback with an Xposed log and the version of Freecharge app if not working, so I can take a look at it.
I will not add any new features. This module is only for skipping the Xposed restriction
Changelog
1.0: Initial module.
I am having Android 7.1. Please tell us more about what this application exactly do?
Xaif said:
I am having Android 7.1. Please tell us more about what this application exactly do?
Click to expand...
Click to collapse
As described in thread description, If xposed is installed, freecharge won't start. With this module, freecharge will start even xposed is installed.
Thanks so much, could you be kind enough to brief us about how exactly this module overcomes the issue?
creativo89 said:
Thanks so much, could you be kind enough to brief us about how exactly this module overcomes the issue?
Click to expand...
Click to collapse
ha ha asks the freecharge developer or employee
tovarish said:
ha ha asks the freecharge developer or employee
Click to expand...
Click to collapse
Nope, I was just curious, I had earlier followed the other hack around of recompiling the apk as told by some other author here on XDA, but now this module works like a charm on my redmi Note3, so I'm just curious
It just took 2 lines of code to bypass, I just hooked to their checking method and returned false. I didn't have any prior experience in developing Android app or Java. But was too much annoyed by their strategy
works.. thank u..
Sent from my Redmi Note 3 using Tapatalk
Great work @Web_E
Sent from my SM-N9005 using Tapatalk
Not support in my xposed
Hi. Skrilo is alos not working in xposed installed phones. is it possible to develop same unblocker for skrilo app too? Thanks
It does not work on the latest version
[email protected] said:
It does not work on the latest version
Click to expand...
Click to collapse
It works.
I'm running Freecharge 8.0.3. Installed last night
Sent from my SM-N9005 using Tapatalk
Still it is not showing promo code option
Sent from my LG-K330 using XDA Free mobile app
purval6300 said:
Still it is not showing promo code option
Click to expand...
Click to collapse
When i used xrivacy to randomize imei value...
purval6300 said:
When i used xrivacy to randomize imei value...
Click to expand...
Click to collapse
The tweak has nothing to do with promo code option. It just bypass freecharge's check of xposed binary. It doesn't bypass any other check performed by freecharge app.
latest 8.0.7 doesnt allow to even sign in. :/
Can you update? @Web_E
ravijani said:
latest 8.0.7 doesnt allow to even sign in. :/
Can you update? @Web_E
Click to expand...
Click to collapse
Thanks for notification. Since I have moved to Nougat, I wasn't aware of the changes.
I have released a beta version, can you please test and confirm whether this is working?
If working I will mark the release as stable.:fingers-crossed:
http://dl-xda.xposed.info/modules/xposed.webe.freechargeunblocker_v1_1d8c8e.apk
Web_E said:
Thanks for notification. Since I have moved to Nougat, I wasn't aware of the changes.
I have released a beta version, can you please test and confirm whether this is working?
If working I will mark the release as stable.:fingers-crossed:
http://dl-xda.xposed.info/modules/xposed.webe.freechargeunblocker_v1_1d8c8e.apk
Click to expand...
Click to collapse
Thanks working now properly for me.
Didnt try transaction but logged in. Checked app and no warnings or anything.
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?
Lately, I've been facing issue with Magisk,
Google Pay's new update is detecting root, even though I've enabled "hide root" toggle in magisk.
I'm using Magisk's latest version and it's able to hide root for other app but for Google pay.
I've tried many apps but that doesn't seem to be working.
thanks in advance.
Edit - Not just google play, every other app is detecting root and blocking me from making any payment.
aman9_6 said:
Lately, I've been facing issue with Magisk,
Google Pay's new update is detecting root, even though I've enabled "hide root" toggle in magisk.
I'm using Magisk's latest version and it's able to hide root for other app but for Google pay.
I've tried many apps but that doesn't seem to be working.
thanks in advance.
Click to expand...
Click to collapse
I think you posted in wrong place. Try Magisk realated forums.
I have baypassed it by remove latest google pay. Download older version from apk mirror. Install hide it in Magisk and reboot. ( do not update at this point) register your details . Set up google pay and after check that everything is ok you can update google pay to latest version.
Hpe it will help
Sent from my Galaxy S9+ using XDA Labs
yarpiin said:
I think you posted in wrong place. Try Magisk realated forums.
I have baypassed it by remove latest google pay. Download older version from apk mirror. Install hide it in Magisk and reboot. ( do not update at this point) register your details . Set up google pay and after check that everything is ok you can update google pay to latest version.
Hpe it will help
Click to expand...
Click to collapse
I wanted to post on Magisk's forum but somehow that thread is locked. And the trick worked, thank you for that.