Snapchat and Magisk Hide - Magisk

Hi.
I used to have snapchat working perfectly using magisk hide but yesterday my stories were not updating so I tried to logout and loging.
When I tried to login it says
'Oh no! Your login has temporarily failed ....'
I have then updated magisk to 14.5 but it is still not working.
Anyone else having this issue.

Same here. I will try to update to 14.5 when it will come out not gonna risk beta relase

Do you have the Busybox module installed? If so disable it, try to log into snapchat and then re-enable it

i have the same problem

Same problem here... solutions?

If you have Magisk Xposed installed then disable in Magisk Manager -> Reboot -> Login to Snapchat -> re-enable Xposed -> reboot

Thanks, gkornaks. It was the original XPosed that I still had on the device for me. With that gone and hiding on, it works.

Related

Snapchat on rooted Moto G4 Plus running Oreo

So I recently updated my ROM to the Nitrogen OS. Everything went fine till I tried logging into Snapchat. Tried magisk hide and rootswitch but the app still doesn't allow me to login. Don't have xposed installed either.
Additional: Rootswitch has a pink banner on the top saying "Magisk not fully supported"
Solutions?
On OnePlus 5T it wouldn't let me login with Xposed installed so i had to remove that before logging in. Since you've already figured that out you could try two things.
1. Remove xposed using xposed uninstaller. Uninstall magisk and login. You can reinstall magisk after snapchat has logged you in. Don't install xposed, snapchat will log you out again. Also clear snapchat cache and data from applications in settings.
secondly if it still doesn't work install latest magisk, use magisk hide then goto applications and clear snapchat all data and cache and try to login.

App crashed after hide on Magisk 17.1

Again I face a problem, now if I hide any application the application doesn't work or open, every time it crashed.
My device: Honor 8
This is happening with me on LG G6. Hide is enabled in options and when I want to enter Magisk Hide to enable it then Magisk crashes.
Logs?
Aid777 said:
This is happening with me on LG G6. Hide is enabled in options and when I want to enter Magisk Hide to enable it then Magisk crashes.
Click to expand...
Click to collapse
I had that problem on LG V30. I reverted to 16.0 with Manager 5.9.1, and the problem persisted. I then downgraded Manager to 5.8.3, and it's working fine again with the older version of Manager.
MechanicaIMan said:
I had that problem on LG V30. I reverted to 16.0 with Manager 5.9.1, and the problem persisted. I then downgraded Manager to 5.8.3, and it's working fine again with the older version of Manager.
Click to expand...
Click to collapse
5.9.1 seems to be 17.0 zip. I assume you meant that
5.8.3 is 16.7
When you downgrade do you just flash the zip or do you need to uninstall the 17.1 Magisk then flash this downgraded one?
I'm getting this exact same issue, I've attached logcat and magisk logs after hiding the Play Store with Magisk Hide, then attempting to open it (and having it immediately crash). Magisk 17.1, latest Magisk Manager app, Pixel 2XL, Oreo 8.1 (July patch). Apps open again after deselecting them from Magisk Hide. Was working fine on 16.4, stopped working after 17.1, and a complete Magisk uninstall/reinstall did not fix it.
Magisk Log, Logcat.
Aid777 said:
5.9.1 seems to be 17.0 zip. I assume you meant that
5.8.3 is 16.7
When you downgrade do you just flash the zip or do you need to uninstall the 17.1 Magisk then flash this downgraded one?
Click to expand...
Click to collapse
I had the problem after updating from 16.0 with 5.8.3 to 17.1 with 5.9.1, but I also tried using the newest manager with 16.0, and that didn't work either. So there must be some kind of issue with the newest version(s) of the manager. I completely uninstalled 17.1, flashed 16.0, updated manager to 5.9.1 (crashing returned), then uninstalled 5.9.1 and installed the 5.8.3 apk without changing Magisk. If you have 17.1 installed now, then you might want to try just replacing manager with an older version before you bother with completely uninstalling/downgrading Magisk. You can simply uninstall the manager app without uninstalling Magisk, but I don't know if Magisk 17 will work okay with the older versions of manager, since I haven't tried that myself and don't really know anything about Magisk.
It is the same with me
Google Play Store crashed
Same here guys with LG g6, I installed the 17.1 by direct installation (within the app) and then when I go to magisk hide, it keeps crashing!
I've had the exact same experience as @mechanicalman on my V30+ (US998).
Any solution guys.
same with me, would appreciate somebody to have a look.
Magisk Hide tickboxes in Magisk Manager make Oreo crash
Hi, same with me: Oneplus3 with stock OOS 5.0.5 (oreo), dm-verity warning at boot since when I was a superSU user.
Everything was fine with Magisk 16. Since update to 17.1 and MagiskManager 5.9.1, the Magisk Hide menu keeps crashing. I've reflashed the stock ROM, reinstalled magisk 16 and 17.1, used the magisk deinstaller. The problem seems tied with MagiskManager 5.9.1
- In the MagiskHide menu, sometimes I can check 5 to 10 apps before it crashes.
- In the MagiskHide menu, sometimes only 1 check or 1 uncheck makes the phone crash.
When MagiskHide crashes it:
- blacks out the screen for a few seconds
- then starts a reboot (a soft reboot where I am not asked my device password, which I have set to be asked during boot)
- then it eventually launches Android after a very long time (usually OOS 5.0.5 opens after 20 cycles of the animation, but after a MagiskHide crash, it can take 200 cycles (from which I stop counting))
I attached the Magisk log immediately after reboot, which doesn't say much (some lines similar to previous and following ones removed).
MagiskManager: "Preserve force encryption" is on (default), "Preserve AVB 2.0/dm-verity" is off (default), Modulues are Busybox, MM for recovery, Xposed, YouTube Vanced, rest of settings are default.
I hope that helps narrowing down the problem.
I'm coming here with this issue occurring on my LG V30+ and Magisk 17.1
Hi, I'm having the same problem as a couple of people, magisk 17.1, newest Magisk Manager, then when I try to go into the magisk hide menu, the app crashes to home screen.
I enabled core only mode to see if it was any of my modules but the problem persists.
lenovo p2 same problem of manager crashing when entering hide menu
Same problem on my Nexus 5, Dirty Unicorn with Oreo 8.1
Same problem here on the V30+. Anyone able to confirm downgrading works?
Also, what do most of y'all use hide for? I was gonna try to use it to set up chase pay for that 5% rewards. lol
Didgeridoohan said:
Logs?
Click to expand...
Click to collapse
Magisk Manager v6.0.0, OOS9.0 OnePlus 6. App crashes while opening Magisk hide menu. Thanks

Banks app detects root after update v18.0 (with Magisk Hide and hidden Manager)

Hi, thanks for reading.
I've used Magisk 17.3 with all my bank apps perfectly, with Magisk hide and Magisk manager hidden.
After update to 18.0 and update manager to 6.1, the bank apps start detecting root status, and stop working.
So, I've flashed back to 17.3 and old manager 6.0.1, and everything's back to working normally.
My system:
Poco F1
LineageOS 16.0 built 27/11/2018
The apps are from Thai's banks:
SCB EASY: detected root, still working
TMB Touch: detected root, stop working
KTB Next: detected root, working partially
If you'd want any log or anything, please also tell me how to get them.
Adios2nd said:
Hi, thanks for reading.
I've used Magisk 17.3 with all my bank apps perfectly, with Magisk hide and Magisk manager hidden.
After update to 18.0 and update manager to 6.1, the bank apps start detecting root status, and stop working.
So, I've flashed back to 17.3 and old manager 6.0.1, and everything's back to working normally.
My system:
Poco F1
LineageOS 16.0 built 27/11/2018
The apps are from Thai's banks:
SCB EASY: detected root, still working
TMB Touch: detected root, stop working
KTB Next: detected root, working partially
If you'd want any log or anything, please also tell me how to get them.
Click to expand...
Click to collapse
1.restore magisk manager with original package.
2.disable hide app.
3.reboot.
4.rehide msgisk manager.
5.rehide app.
6.reboot.
it work for nexus 6p.
Sent from my Nexus 6P using Tapatalk
Can confirm that this works, thanks.
For me, it started getting detected on 17.x even before updating to 18, right after the banking app (Sparkasse) was updated.
LG G6.
hsiehboss said:
1.restore magisk manager with original package.
2.disable hide app.
3.reboot.
4.rehide msgisk manager.
5.rehide app.
6.reboot.
it work for nexus 6p.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
This didn't work for me. I had to downgrade back to 17.1 to get my banking app working again. Appears that the root detection prevention is a regression in this latest version.
-- SSS
hsiehboss said:
1.restore magisk manager with original package.
2.disable hide app.
3.reboot.
4.rehide msgisk manager.
5.rehide app.
6.reboot.
it work for nexus 6p.
Click to expand...
Click to collapse
This doesn't work for me.
Did all of these...still got detected.
I have the same problem. Magisk says: ctsProfile: False and Google Pay don't work. Also my Banking App detects root.
I flashed today the latest Los 15 build and the crt false error is till there after flashing magisk 18. The same error is also with 17.4...
Tell me if I'm wrong but I believe we have two different reports: the original report where root is detected, and the ctsProfile/basicIntegrity failing. The second one is a regression fixed by rebooting device (however, it is annoying to reboot 10 times a day because suddenly SafetyNet fails for no reason).
I am using Magisk Hide Props module, and after 18.0 update Santander App detects root, even with Magisk Manager says I pass safetynet
It's happened with my bank app as it detected root & saftynet false and have to downgrade to ver.17.2
Sent from my SM-C900F using Tapatalk
See in install app delete old magisk manager, after install magisk 18.0 new magisk manager rename to manager.
I have same problem. After install v18 magisk, same bank app can detect the system is rooted. Downgrade to v17.2, all bank app become normal.
Same here since Magisk 18 my BankApp (Intesa Sanpaolo) start and says that there is a safety problem and it close, if I choose Magiskhide it doesn't start at all.
SafetyNet check spin without an end.
With Magisk 17.1 and 17.3 no problem at all.
Same problem here, after upgrading to Magisk 18 claiming to better hide root in the history, apps now suddenly detect root.
This affects also the Safety Net check and Google Pay... so far, Root Hiding in 18.0 seems COMPLETELY broken.
A solution would be great.
Later... after downgrading to Magisk 17.2, MagiskHide is working for me again and Safetynet checks succeed. The dev is aware of the problem, an issue is open on the Magisk Github (#907)
After uninstalling and reinstalling my bankapp now works without any problem and doesn't detect root even if is not under Magisk hide
I can confirm the v18 update breaks something and BOTH safety net checks fail. So all apps detect you are rooted, especially bank apps and Get Pay. Downgrading back to v17 restored everything to normal.
The only thing I could think of is the installation method. I did the direct install rather than installing the zip via recovery. Not sure if it makes a difference but I will wait for next release.
I am on a Pixel 2 with Android Pie updated to the Aug 2018 release.
---------- Post added at 12:47 PM ---------- Previous post was at 12:43 PM ----------
Harlock1978 said:
After uninstalling and reinstalling my bankapp now works without any problem and doesn't detect root even if is not under Magisk hide
Click to expand...
Click to collapse
I did not uninstall but tried clearing bank app data and cache and the problem persisted. Magisk still showing all red for safetyNet. Just sharing testing feedback.
@Djtrip83 Did you try just toggling MagiskHide off and on once after updating to v18? Sometimes MagiskHide simply needs a restart after an update...
I did that too. Toggled Hide on and off for all apps. Repackaged Magisk. Turned off USB debugging. Removed modules installed. Tried everything I thought would work. Even restored hosts in case Ad Away affected something on /system.
The only thing I did not do was remove root apps and re-install them to re-grant permissions after the Magisk update. And I wonder now if uninstalling Magisk completely and make a brand new clean install with v18 would work rather than upgrading.
I was at a loss so I downgraded. Sorry I don't have a log to share. However, v17 works fine.
Djtrip83 said:
I did that too. Toggled Hide on and off for all apps. Repackaged Magisk. Turned off USB debugging. Removed modules installed. Tried everything I thought would work. Even restored hosts in case Ad Away affected something on /system.
The only thing I did not do was remove root apps and re-install them to re-grant permissions after the Magisk update. And I wonder now if uninstalling Magisk completely and make a brand new clean install with v18 would work rather than upgrading.
I was at a loss so I downgraded. Sorry I don't have a log to share. However, v17 works fine.
Click to expand...
Click to collapse
We might be misunderstanding each other, but what I'm talking about is simply to go to the Manager settings and change the toggle for MagiskHide to off and then on. No need to do anything to the Hide list or anything else... Did you do that? As I said, that's sometimes something you the to do after an update, but it's rare.

[Mate 10 PRO] Magisk 18 gives me root but no SafetyNet or Magisk Hide

I'm running, on a Huawei Mate 10 PRO, an official Huawei ROM BLA-L29 8.0.0.157 (C432) with no custom kernel or script installed via TWRP. I only have Magisk 18 running with a couple of modules such as Android Pie Fonts, Busybox, DNSCrypt-Proxy 2, Pixel Experience, Youtube Vanced. Root works perfectly on the device with many applications. Now I'm struggling with two things that don't work at all:
- SafetyNet check: it takes many minutes to complete and at the end I get an "Invalid answer"
- Magisk Hide: as soon as I register an application in Magisk Hide I can no longer launch it. Clicking on the icon doesn't do anything.
FYI: On Magisk I have the "Keep forced encryption" set and "Keep AVB 2.0/dm-verity" unchecked. I tried with "Keep AVB 2.0/dm-verity" set and re-installed Magisk but problem is still there.
I looked at Magisk's log but can't see any outstanding issue or error message.
Can someone help me to solve this issue since some banking applications are now blocking me? Thanks a lot.
PS: I tried to use an alternativel fingerprint via the MagiskHide Props Config module but that didn't help.
SafetyNet with Magisk 18.0
alphazo said:
- SafetyNet check: it takes many minutes to complete and at the end I get an "Invalid answer"
- Magisk Hide: as soon as I register an application in Magisk Hide I can no longer launch it. Clicking on the icon doesn't do anything.
Click to expand...
Click to collapse
Hi alphazo,
I had the same problem with my Huawei Mate 10 Pro since I went from 17.3 to 18.0.
I tried several solutions like you, but nothing worked. The only thing that worked was to downgrade to version 17.3, there, everything was functional.
For my part, I completely uninstalled Magisk from my phone and then reinstalled it. After that, everything works perfectly and I have no problems with SafetyNet.
You just have to reconfigure the Magisk Manager application and choose which applications you want to hide.
I hope it will work for you too ! :good:
Thanks a lot for your pointers. I finally got it working and thus even with Magisk 18
It was a combination of many factors.
Here is what I did first:
Fully uninstalled Magisk 18
Installed Magisk 17..3
Selected applications lilke a simple Safetynet checket app under Magisk Hide
Started the Safetynet checker app and it worked.
Then I started to re-install my Magisk modules including Pix3lify (former Pixel Experience module) for an alternate launcher and found out that this was causing the issue.
I uninstalled this module and then decided to upgrade to Magisk 18. Magisk Hide didn't work at first since a simple Safetynet checker app wouldn't pass.
I had to go back to Magisk Hide panel and unselect all the apps that were previously registered before selecting them again and this time it worked.
Thanks again for your pointers and I hope the above will help other people.
PhilippeSX4 said:
Hi alphazo,
I had the same problem with my Huawei Mate 10 Pro since I went from 17.3 to 18.0.
I tried several solutions like you, but nothing worked. The only thing that worked was to downgrade to version 17.3, there, everything was functional.
For my part, I completely uninstalled Magisk from my phone and then reinstalled it. After that, everything works perfectly and I have no problems with SafetyNet.
You just have to reconfigure the Magisk Manager application and choose which applications you want to hide.
I hope it will work for you too ! :good:
Click to expand...
Click to collapse

Snapchat won't sign in, how to fix?

Alright so I'm running magisk 18.0 on OnePlus 3T with xposed framework. I was able to sign into Snapchat before xposed when I used magisk hide and all the other things you're supposed to do. I'm obviously aware I triggered safety net by using xposed, what's the fastest way to get safetynet to pass again so I can sign into Snapchat? Is it as simple as disabling xposed? Please walk me through this, thanks
JayTheKid said:
Alright so I'm running magisk 18.0 on OnePlus 3T with xposed framework. I was able to sign into Snapchat before xposed when I used magisk hide and all the other things you're supposed to do. I'm obviously aware I triggered safety net by using xposed, what's the fastest way to get safetynet to pass again so I can sign into Snapchat? Is it as simple as disabling xposed? Please walk me through this, thanks
Click to expand...
Click to collapse
The reason I'm having this issue is because Snapchat randomly signed me out today and my restore point in titanium backup was too old
I had it too. Sign out clear data and cache and forced stop
Go hide in Magisk.
Reboot.
Clear data and storage again m
Open MM & turn off Magisk Hide.
Wait a few seconds.
Toggle Magisk Hide back on.
Force stop and clear Snapchat again.
Now before rebooting go ahead give it the permissions you want it to have.
Theory: don't give it the "phone" permission at first it at all if you can help it.
Reboot
Let everything finish loading and settling in, wait a couple minutes then try again.
If it's still messed up, is the account locked on their end until you call?
Let me know.
JayTheKid said:
Alright so I'm running magisk 18.0 on OnePlus 3T with xposed framework. I was able to sign into Snapchat before xposed when I used magisk hide and all the other things you're supposed to do. I'm obviously aware I triggered safety net by using xposed, what's the fastest way to get safetynet to pass again so I can sign into Snapchat? Is it as simple as disabling xposed? Please walk me through this, thanks
Click to expand...
Click to collapse
vonDubenshire said:
I had it too. Sign out clear data and cache and forced stop
Go hide in Magisk.
Reboot.
Clear data and storage again m
Open MM & turn off Magisk Hide.
Wait a few seconds.
Toggle Magisk Hide back on.
Force stop and clear Snapchat again.
Now before rebooting go ahead give it the permissions you want it to have.
Theory: don't give it the "phone" permission at first it at all if you can help it.
Reboot
Let everything finish loading and settling in, wait a couple minutes then try again.
If it's still messed up, is the account locked on their end until you call?
Let me know.
Click to expand...
Click to collapse
I turned off xposed in magisk and the installer, retoggled magisk hide for Snapchat and rebooted. Account was locked, what triggers this? I was using snap with Xposed undetected for months and then it randomly acts up. You mentioned not giving it phone permission, is that how they catch you? The only other thing I could think of that caught me was my cable app (spectrum TV) makes me disable usb debugging to use it
JayTheKid said:
I turned off xposed in magisk and the installer, retoggled magisk hide for Snapchat and rebooted. Account was locked, what triggers this? I was using snap with Xposed undetected for months and then it randomly acts up. You mentioned not giving it phone permission, is that how they catch you? The only other thing I could think of that caught me was my cable app (spectrum TV) makes me disable usb debugging to use it
Click to expand...
Click to collapse
The phone permissions allows the app to see the phone's IMEI code. I think maybe that detected you are on a rooted phone using that information.
How to use Snapchat with magisk (After Ban)
Follow these steps to use Snapchat with magisk -
1.) Update to latest Magisk stable build v20.0 - https://github.com/topjohnwu/Magisk/releases/download/v20.0/Magisk-v20.0.zip
2.) After updating magisk, Go to Magisk Manager > Magisk Hide and check/enable Snapchat and Google Services (all services have to be marked).
3.) Hide Magisk Manager by it self, go to Magisk Manager > Settings and "Hide Magisk Manager" so it will repack Magisk Manager with random name.
4.) Delete "busybox" binary from /system/xbin directory and install BusyBox module from Magisk Manager > Downloads.
5.) Clear data and cache of Snapchat, try to login this time, it will work for sure, if it doesn't, login to this and click unlock my account - https://accounts.snapchat.com/accounts/login?continue=https://accounts.snapchat.com/accounts/welcome
I have tried this myself and it works, my first main account was permanent banned on magisk canary build, After that I deleted that account and started out with fresh new account.
Tested on -
Samsung Galaxy S9+
Rom - Ultimate Rom v11.3
Magisk - v20.0 (Stable)
Kernel - ElementalX
No such item in xbin
I tried that too but i dont find any item such as busybox my Snapchat account can't be locked because its has been open in different phones
So give a solution what should i do i uninstall edxposed tried everything root switch root clock hut none of them really works its say oh on your temporarily login fails please try again later help needed seriously its been days
Running
Magisk 20.4 stable
Ed xposed 0.4.5.6 justins forks snadhook
Android 10

Categories

Resources