Can't use Android Pay or PoGo on the OP3T.
Stock rom, just bootloader unlocked and TWRP. No rooted yet.
yes, you need kernel patch to hide unlocked boot loader
Yeah, go try out the kernels from the Rom/Kernel thread. They both have the verified boot status fix you need.
Sent from my OnePlus 3T using XDA Labs
dustin_b said:
Yeah, go try out the kernels from the Rom/Kernel thread. They both have the verified boot status fix you need.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
There must be another layer other than the kernel , (e.g.) the safety net xposed module. Mine has Tyranus v12 kernel, and comes up with a 1) valid response and then 2) something else, you can see it in the following screenie:
hachamacha said:
There must be another layer other than the kernel , (e.g.) the safety net xposed module. Mine has Tyranus v12 kernel, and comes up with a 1) valid response and then 2) something else, you can see it in the following screenie:
Click to expand...
Click to collapse
I'm running bootloader unlocked, twrp, and Tyrannus and have no issues. Use Android pay everyday.
justibasa said:
I'm running bootloader unlocked, twrp, and Tyrannus and have no issues. Use Android pay everyday.
Click to expand...
Click to collapse
I'm not even sure I want to use anything that requires safety net, but in case I do, could you give some more details? Are you using SuperSU Systemless, or that other rooting util? Are you using stock 3.5.3 (other than Tyranus). Are you a) using exposed and if you are b) using one of the safety net modules, and if so c) which one?
Thanks. I don't care about Android Pay but I don't like it when something shows a flaw like that test. I just tried Android pay and it says something like "the phone isn't designed for it" .
hachamacha said:
There must be another layer other than the kernel , (e.g.) the safety net xposed module. Mine has Tyranus v12 kernel, and comes up with a 1) valid response and then 2) something else, you can see it in the following screenie:
Click to expand...
Click to collapse
I have the exact same problem using Elemental Kernel, any solution?
Related
I recently found this method of getting past safety net without losing xposed mods: https://www.reddit.com/r/TheSilphRo...y_have_found_a_workaround_for_the_pokémon_go/
I haven't tried it out yet, but I was checking to see if anyone had as I know that unrooting on the turbo is a dangerous prospect. Would this be recommended?
jedibob7 said:
I recently found this method of getting past safety net without losing xposed mods: https://www.reddit.com/r/TheSilphRo...y_have_found_a_workaround_for_the_pokémon_go/
I haven't tried it out yet, but I was checking to see if anyone had as I know that unrooting on the turbo is a dangerous prospect. Would this be recommended?
Click to expand...
Click to collapse
There's nothing dangerous about this, but it won't work. Magisk is incompatible with our devices, so forget anything involving that. In order for suhide to work, you need a stock marshmallow rom that will pass safetynet on its own, and we don't have that. Your best bet is to install the Resurrection Remix rom and use the iSu app that the dev made for it to hide the built in CM root, but you still won't be able to use xposed.
That worked until two days ago. Now safety net has patched it and isu doesn't work anymore. This is confirmed by BHB27.
So sad. I only got to enjoy android pay with cm13 for 3 days..
TheSt33v said:
There's nothing dangerous about this, but it won't work. Magisk is incompatible with our devices, so forget anything involving that. In order for suhide to work, you need a stock marshmallow rom that will pass safetynet on it's own, and we don't have that. Your best bet is to install the Resurrection Remix rom and use the iSu app that the dev made for it to hide the built in CM root, but you still won't be able to use xposed.
Click to expand...
Click to collapse
fmz0507 said:
That worked until two days ago. Now safety net has patched it and isu doesn't work anymore. This is confirmed by BHB27.
So sad. I only got to enjoy android pay with cm13 for 3 days..
Click to expand...
Click to collapse
Lame. Well, Chainfire did warn us that this was a losing battle. I guess he was right.
Actually there's some light to the end of the tunnel lol It was some later changes that broke it. BHB is still figuring out what caused it.
But if you use isu1.2 and kernel 202.1 it still works (also must enable SE linux in the kernel editor). I didn't have to do all that to get it to work but for now this config still works..
But yes, this is a hard battle to fight.
TheSt33v said:
Lame. Well, Chainfire did warn us that this was a losing battle. I guess he was right.
Click to expand...
Click to collapse
UPDATE: Not even 24 hours and it fails SafetyNet now. I'm currently working on another solution.
Hi all. Long time lurker, first time developer. I created a modified version of the Xposed Framework that doesn't cause you to fail SafetyNet, even while it's enabled and active. Instructions:
Remove any existing Xposed versions
Get your phone in a state where it passes SafetyNet without Xposed (install a custom kernel to hide an unlocked bootloader, hide root with RootSwitch, etc.)
Install the Xposed Installer app if you don't already have it
Go to https://github.com/josephcsible/Xposed/releases/tag/v86a and download xposed-v86a-safetynet-josephcsible-sdk23-arm.zip
Flash xposed-v86a-safetynet-josephcsible-sdk23-arm.zip from recovery
Wipe cache and dalvik
Reboot
You should now have Xposed installed and enabled, with all of your modules working, without failing SafetyNet. Notes:
Do not turn off Xposed with RootSwitch with this build. It will probably break things because of differences in how app_process sits, and the entire point of this build is that you don't need to do this.
The only build I made was for ARM and Marshmallow, because that's all I have to test on
The official uninstaller won't work right with this version, so use my version of the uninstaller instead
This passes SafetyNet as of November 2nd. It probably won't for very long.
Technical details:
I made this build by compiling my own app_process, then editing it into the stock installer zip. I didn't recompile anything else or use the tools to make the zip.
app_process32 is now a regular file instead of a symlink to app_process32_xposed.
XposedBridge.jar is now called YqptfeBridge.jar (since SafetyNet checks the classpath for a file called XposedBridge.jar)
I obfuscated many of the strings in the app_process binary with a simple Caesar cipher. The source for this is in the GitHub with the download link.
Enjoy it while it lasts!
Great work, thanks! Though I think the method is kind of dirty.
Yeah, but I'm not overly concerned since I expect at best a few weeks before it gets patched and I have to redo it all anyway.
aviraxp said:
Great work, thanks! Though I think the method is kind of dirty.
Click to expand...
Click to collapse
You mean that it's not good to install it ?
MrMikeTyson said:
You mean that it's not good to install it ?
Click to expand...
Click to collapse
He means in terms of code quality and maintainability from developers' standpoints. It's perfectly fine from the users' ends.
josephcsible said:
He means in terms of code quality and maintainability from developers' standpoints. It's perfectly fine from the users' ends.
Click to expand...
Click to collapse
Ah ! Okay !! What about safetynet not passing ? See screenshots... What can i do please ?
MrMikeTyson said:
Ah ! Okay !! What about safetynet not passing ? See screenshots... What can i do please ?
Click to expand...
Click to collapse
It no longer passes for me either. I can't believe Google fixed it so fast. I'm working on another release now.
josephcsible said:
It no longer passes for me either. I can't believe Google fixed it so fast. I'm working on another release now.
Click to expand...
Click to collapse
Okay, i'll wait it and good luck for your work
Status update: My app_process is still not detected at all. It's now detecting something that's happening in Java (XposedBridge).
josephcsible said:
Status update: My app_process is still not detected at all. It's now detecting something that's happening in Java (XposedBridge).
Click to expand...
Click to collapse
So it means you cannot just rename the method/class, if I am right?
aviraxp said:
So it means you cannot just rename the method/class, if I am right?
Click to expand...
Click to collapse
I tried stubbing out the main method in XposedBridge to just call the real main method, and that made it pass. That leads me to conclude that it's a behavior thing and not a name thing.
So this version of xposed is passing?
Barfelonous said:
So this version of xposed is passing?
Click to expand...
Click to collapse
REREAD THE OP Please
josephcsible said:
UPDATE: Not even 24 hours and it fails SafetyNet now. I'm currently working on another solution.
Click to expand...
Click to collapse
: (
Any news on this?
meiser said:
Any news on this?
Click to expand...
Click to collapse
I haven't had time to work on it since my last update. I expect to have more time in June.
Hi is there an other way to use Xposed modules while passing safatynet check ? Its usefull on POGO !
Regards, Devilo !
What is involved in taking a ROM, and making it into a systemless ROM module?
Can they be of a different Android version than the main ROM?
As far as I learned the Magisk ROM has to be compatible to your stock firmware and ROM.
And I can tell that they are possible. On the HTC 10, Team Venom build the fist Magisk ROM. They are now followed by LeeDrOiD and BadBoyz ROMs which are getting available as Magisk Module ROM, as well as as full ROM.
I can't tell you how they did it, as I'm not a developer, but you could ask in their ROM threads. Maybe they'll tell you.
Sent from my htc_pmeuhl using XDA Labs
5m4r7ph0n36uru said:
As far as I learned the Magisk ROM has to be compatible to your stock firmware and ROM.
And I can't tell that they are possible. On the HTC 10, Team Venom build the for Magisk ROM. They are now followed by LeeDrOiD and BadBoyz ROMs which are getting available as Magisk Module ROM, as well as as full ROM.
Click to expand...
Click to collapse
OK. Yes it appears that their Magisk ROM is very specific to what is running underneath.
Thanks!
jhedfors said:
OK. Yes it appears that their Magisk ROM is very specific to what is running underneath.
Thanks!
Click to expand...
Click to collapse
Yes and it'll always be, as Magisk adds/alters mount points on boot up, but otherwise uses the existing system and system files as well as data partition. Thus the ROM and Magisk Module got to be highly compatible. It's quite logical.
Sent from my htc_pmeuhl using XDA Labs
5m4r7ph0n36uru said:
Yes and it'll always be, as Magisk adds/alters mount points on boot up, but otherwise uses the existing system and system files as well as data partition. Thus the ROM and Magisk Module got to be highly compatible. It's quite logical.
Click to expand...
Click to collapse
I guess I will have to be patient, and wait for the full Magisk multirom functionality to be developed!
jhedfors said:
I guess I will have to be patient, and wait for the full Magisk multirom functionality to be developed!
Click to expand...
Click to collapse
Well, we'll see what pleasures this will bring. Would be nice to implement MultiROM via Magisk. Question is if it'll help. The new - Samsung build - Snapdragon 835 seems to come with a security chip, which will be able to recognize if you try to boot a custom ROM and won't boot the device at all in that case. As Samsung build it, I'd guess Exynos will have the same "security" feature.
Sent from my htc_pmeuhl using XDA Labs
5m4r7ph0n36uru said:
Well, we'll see what pleasures this will bring. Would be nice to implement MultiROM via Magisk. Question is if it'll help. The new - Samsung build - Snapdragon 835 seems to come with a security chip, which will be able to recognize if you try to boot a custom ROM and won't boot the device at all in that case. As Samsung build it, I'd guess Exynos will have the same "security" feature.
Click to expand...
Click to collapse
If it is still "systemless", it seems like a Magisk solution could possibly be the answer. We shall see, I am wondering if the solution will be like the Magisk module ROM, but just replacing most everything, rather than just select parts.
I'm using ResurrectionRemix Rom on my LG G3 Beat and Pokemon GO v. 0.67.2 and as soon as I install Magisk (used MagiskHide and tried many things) v. 12 or v. 13 beta it stops working. My device passes SafetyNet so it should not be a issue. Someone having this issue too? How can I fix that?
Edit: I finally found the issue. It's KernelAdiutor.
Thinkofname said:
I'm using ResurrectionRemix Rom on my LG G3 Beat and Pokemon GO v. 0.67.2 and as soon as I install Magisk (used MagiskHide and tried many things) v. 12 or v. 13 beta it stops working. My device passes SafetyNet so it should not be a issue. Someone having this issue too? How can I fix that?
Click to expand...
Click to collapse
Why do you use a pogo version that isn't forced yet? 0.67.1 works totally fine.
No need to update, especially not, if you don't know what the update contains and what it is doing.
Go to magisk settings and then to tick the "core only mode" checkbox. Reboot and you are done.
Google has strenghten SN policies and now Magisk modules functionality makes you fail SN check. The temporary solution is to disble all modules related functionality following the steps above.
Sent from my SM-G930F using Tapatalk
I've created a Pokemon Trainer Club account, just for these occasions, when once in a while someone comes in and have issues with PoGo not starting. Anyway...
Tried both 0.67.1 and 0.67.2 and they start up just fine on Magisk v13.0 (54e6a79) beta, OnePlus 3T, OxygenOS 4.1.6, Franco Kernel r24 and nothing else done except having enabled Magisk Hide. Does Resurrection Remix have ro.build.tags set to "release-keys" (and so on)?
DaSoul said:
Why do you use a pogo version that isn't forced yet? 0.67.1 works totally fine.
No need to update, especially not, if you don't know what the update contains and what it is doing.
Click to expand...
Click to collapse
On 0.67.1 I had the same issues
coto39 said:
Go to magisk settings and then to tick the "core only mode" checkbox. Reboot and you are done.
Google has strenghten SN policies and now Magisk modules functionality makes you fail SN check. The temporary solution is to disble all modules related functionality following the steps above.
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
Tried it, but it won't work, I'm using this module to fix my safetynet bypass but it still don't work with it.
Didgeridoohan said:
I've created a Pokemon Trainer Club account, just for these occasions, when once in a while someone comes in and have issues with PoGo not starting. Anyway...
Tried both 0.67.1 and 0.67.2 and they start up just fine on Magisk v13.0 (54e6a79) beta, OnePlus 3T, OxygenOS 4.1.6, Franco Kernel r24 and nothing else done except having enabled Magisk Hide. Does Resurrection Remix have ro.build.tags set to "release-keys" (and so on)?
Click to expand...
Click to collapse
Checking that, I'll edit this comment when I've done that
Edit: Universal SafetyNet Fix edits them already
Are you able to pass safetynet check?
Sent from my SM-G930F using Tapatalk
coto39 said:
Are you able to pass safetynet check?
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
That's what it says in the OP...
Didgeridoohan said:
That's what it says in the OP...
Click to expand...
Click to collapse
Ups. My bad.. I forgot about that.
Sent from my SM-G930F using Tapatalk
Btw. I found out using Magisk v. 13 beta with Core Modules Only does not pass SafetyNet, not even Basic Integrity. Seems a bit strange.
Found something in the magisk logs, there is a entry for every app that is listened in my Magisk hide List but not for pokemon go
Thinkofname said:
Found something in the magisk logs, there is a entry for every app that is listened in my Magisk hide List but not for pokemon go
Click to expand...
Click to collapse
It doesn't have to be on the list. It's using SafetyNet that is on there by default.
Didgeridoohan said:
It doesn't have to be on the list. It's using SafetyNet that is on there by default.
Click to expand...
Click to collapse
But what exactly makes it don't run?
Rootbeer sample in hide-list does not detect root at all...
Thinkofname said:
But what exactly makes it don't run?
Rootbeer sample in hide-list does not detect root at all...
Click to expand...
Click to collapse
No idea... If you're passing SafetyNet you've got some other issue than it detecting root.
Thinkofname said:
Btw. I found out using Magisk v. 13 beta with Core Modules Only does not pass SafetyNet, not even Basic Integrity. Seems a bit strange.
Click to expand...
Click to collapse
Try Using Universal SafetyNet Fix v2 Beta 3 with Magisk v12
and, what did you mean when says doesn't work? I guess you may have mock locations in dev settings enabled or Xposed installed.
I think I found the issue! I completly reinstalled RR, Magisk etc. with my apps but don't configured my other apps. Pokemon GO worked fine. After configuring Kernel Adiutor it doesn't let me in.
Edit: Yep, uninstalled it, reboot and started PoGo, it's working.
Thinkofname said:
I think I found the issue! I completly reinstalled RR, Magisk etc. with my apps but don't configured my other apps. Pokemon GO worked fine. After configuring Kernel Adiutor it doesn't let me in.
Edit: Yep, uninstalled it, reboot and started PoGo, it's working.
Click to expand...
Click to collapse
Would interesting know what configuration you did in Kernel Adiutor, it can helps others.
Edit: @Didgeridoohan how many times did occurs this to we? xd
Thinkofname said:
I think I found the issue! I completly reinstalled RR, Magisk etc. with my apps but don't configured my other apps. Pokemon GO worked fine. After configuring Kernel Adiutor it doesn't let me in.
Edit: Yep, uninstalled it, reboot and started PoGo, it's working.
Click to expand...
Click to collapse
Great. I'm curious as to what you're doing with Kernel Adiutor to cause this issue?
Edit: Ninja'd!
Didgeridoohan said:
Great. I'm curious as to what you're doing with Kernel Adiutor to cause this issue?
Edit: Ninja'd!
Click to expand...
Click to collapse
Just lowered my max. cpu freq, max. gpu freq, edited some cpu governor settings and edited my lmk settings.
Guys, I wonder, is anyone able to run Pokemon Go with other modules enabled in Magisk or is it still not possible ? With Viper4Android to be precise.
MartinMGS said:
Guys, I wonder, is anyone able to run Pokemon Go with other modules enabled in Magisk or is it still not possible ? With Viper4Android to be precise.
Click to expand...
Click to collapse
Did you try Universal SafetyNet Fix v2 Beta 4? Is in the first page of this sub-forum
I know a while back Xposed tripped Pokemon GO even with Magisk. Is this still the case with the most up to date version of Xposed and Magisk? I only want Xposed for privacy tools like XPrivacyLua
https://forum.xda-developers.com/xposed/modules/xprivacylua6-0-android-privacy-manager-t3730663
ShapeShifter499 said:
I know a while back Xposed tripped Pokemon GO even with Magisk. Is this still the case with the most up to date version of Xposed and Magisk? I only want Xposed for privacy tools like XPrivacyLua
https://forum.xda-developers.com/xposed/modules/xprivacylua6-0-android-privacy-manager-t3730663
Click to expand...
Click to collapse
ed-xposed does not trip pokemon go/safety net currently
thebenjibenji said:
ed-xposed does not trip pokemon go/safety net currently
Click to expand...
Click to collapse
I'm sorry "ed-xposed"? I never heard of that one before, I thought it was called Xposed. Is this a different program?
ShapeShifter499 said:
I'm sorry "ed-xposed"? I never heard of that one before, I thought it was called Xposed. Is this a different program?
Click to expand...
Click to collapse
https://forum.xda-developers.com/xposed/list-xposed-modules-android-pie-ed-t3892768
when i flash the zips i do
1. magisk-riru-core-v18.zip (riru apk is option i think, i dont use it)
2. magisk-EdXposed-v0.3.1.7_beta-release.zip
3. apk can be installed before or after
oh you might be not on 9.0 pie, forgot that part
thebenjibenji said:
https://forum.xda-developers.com/xposed/list-xposed-modules-android-pie-ed-t3892768
when i flash the zips i do
1. magisk-riru-core-v18.zip (riru apk is option i think, i dont use it)
2. magisk-EdXposed-v0.3.1.7_beta-release.zip
3. apk can be installed before or after
oh you might be not on 9.0 pie, forgot that part
Click to expand...
Click to collapse
I'm not, I'm still running Nougat 7.0 Sorry I should have specified that at the top.