Develop Bugs

snapchat login issue, rooted [m8ql]

hello mates,
yesterday i uninstalled snapchat. cause i got beta tester and i downloaded the beta. tried to login again but yeah.. see the picture
i rooted with unlocking bootloader, flashed twrp and rooted with supersu
i searched up the issue, some say you have to uninstall the xposed framework.. did not installed it first.
also tried it with installing xposed, installed the snappref module (what sometimes did work) but this also did not work.
installed it again but no positive progress.
the snapchat webside says that rooted phones may have issues.. i have rooted my phone now almost have an year and had never issues like that.
i just don't want to fully unroot and root again.
has anyone of you a idea? or is it possible to unroot the phone for some time? like in cyanogen mod, where you can unroot your phone in the dev options.
here the webside on the pic if u want to re-read it: https://support.snapchat.com/en-GB/a/failed-login
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Well Snapchat detects if you have xposed installed or not at login. It works on rooted phones otherwise.
I would suggest, install your custom ROM again , login into snapchat and then install Xposed framework. that's what I do and snapchat works.

Maybe a sync issue ?
How to fix 'Snapchat login temporarily failed' error on Android
here with root: https://www.reddit.com/r/LGG3/comments/3vqnaj/oh_no_your_login_temporarily_failed_snapchat/
Uninstall xposed
Download correct snapchat version for snappreffs
Disable automatic updates so you wont need to downdate and have to sign out
Log in
Install xposed and snappreffs plus reboot and stuff
Click to expand...
Click to collapse
Download correct snapchat version for snappreffs
Click to expand...
Click to collapse
<-- Maybe snappreffs is not compatible with the beta
http://snapchat-download.net/fix-oh-no-your-login-temporarily-failed-on-snapchat/
To manually sync your account
On your mobile device, open Settings Settings > Accounts > Google.
Touch the account whose data you want to sync.
In the top-right corner, touch menu More > Sync now.
After your Google Account is successfully synced, make sure that you have the latest version of Google Play Store and Snapchat app. To ensure this, update all your installed app under “My apps and game” on your Play Store account, then reinstall Snapchat to get the latest version of this app.
Click to expand...
Click to collapse

Have to reinstall updates after restart or else no SIM or IMEI

Please give me some suggestion to get out of this mess
OOS 10.0.14.HD65AA
Magisk 20.4 only modules are Google dialer framework, Native OOS call recording, systemless hosts
While on 10.0.12 I installed/uninstalled the Aurora Services module.
A few days later I updated to 10.0.13, phone had not been rebooted between module & update. After update my phone could not see ANY SIM/phone network related info (see pics).
Redid the update and all of the functions were restored. The problem is that the SIM disappears after each reboot.
I reinstall the update, reboot, and everything is fine, until the next reboot. The SIM functions disappear, I reinstall the update, reboot everything fine, until the next reboot, on & on.
I've tried pulling/reinserting the card and inserting card after restart, but that doesn't help.
Now on 10.0.14 and the problem persists.
I believe the OTA updates are the full OOS so I'm at a loss as to why the SIM would disappear on the second boot after update.
Any help would be appreciated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

It is because of OOS native call recording, it is very important to UNINSTALL the module before every update (not just disable, UNINSTALL) it is very well explained in the tread of that specific module why it is needed. I made the mistake to only disabling it instead of uninstalling before an update, fortunately I only needed to uninstall/reinstall it to fix the problem, but if you left it enabled and updated, then you might need to dirty flash the whole update again to fix it. You can find more info on the OOS native call recording thread, I hope it helped you

jacobyo7 said:
It is because of OOS native call recording, it is very important to UNINSTALL the module before every update (not just disable, UNINSTALL) it is very well explained in the tread of that specific module why it is needed. I made the mistake to only disabling it instead of uninstalling before an update, fortunately I only needed to uninstall/reinstall it to fix the problem, but if you left it enabled and updated, then you might need to dirty flash the whole update again to fix it. You can find more info on the OOS native call recording thread, I hope it helped you
Click to expand...
Click to collapse
:good:
Thank you, that was it. I had disabled it before the update, but missed that it had to be uninstalled.

MAGISK HIDE DOESN'T WORK

Hello i just root my MI 10T with latest magisk installer (v21.4) and everything is working fine, safetynet passed and everything.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But the problems comes when i tried to play games, it has something like appguard that detect root. i can't bypass the security guard with magisk hide. and i assume there is something wrong with my magisk, because my old phone (MIA2) can bypass that with magisk hide and my MIA2 doesn't even bypass safetynet.
Installed magisk module:
-Magisk hide props
-Busybox
-Riru
-Riru edxposed
-Systemless host
-Universal safetynet fix
What i tried byfar:
-Change the magisk manager package
-Turn off developer mode
-Using Xprivacylua to prevent the game to read my installed app
None of them fix the problem

Try using my app VD INFOS, you can see every detectable thing. (Root/Magisk/Xposed/Riru/and others.)
And then you can fix what needs to be fixed.
[APP][v1.10] VD Infos (Package: com.vitaodoidao.vdinfos)
(Para quem fala PORTUGUÊS, o próximo post está totalmente traduzido !) VD Infos v1.10 As we all know, Android is a super powerful and super versatile operating system. What nobody tells you is that all your personal details and confidential...
forum.xda-developers.com

Thank you for your app, it seems like riru is the cause of my problems

QuaZero said:
Thank you for your app, it seems like riru is the cause of my problems
Click to expand...
Click to collapse
You are welcome, my friend. Enjoy.
Unfortunately, no one cares to hide riru and I'm not sure what libriruhide really does.
So, it's easily detectable.

VD171 said:
You are welcome, my friend. Enjoy.
Unfortunately, no one cares to hide riru and I'm not sure what libriruhide really does.
So, it's easily detectable.
Click to expand...
Click to collapse
yeah, I use hidding feature and it does nothing, the app still detected it, i just downgrade to riru v21.3 and the problem solved.

do the new version of riru 23.9 have this problem?

@QuaZero @paul999 any update? wish i can do this trick
i have magisk hide, EDxposed and LSposed installed, with hiddencore module + XprivacyLua.
use EDxposed hide too, none of them hide the root from the game, still detect root.
mine android 10, can it be the problem?

yes i found a trick to get around the bank app of mine... it may not work on every app....first open the app, it will said you are rooted blah blah blah... then wipe the the app clean from memory, reopen the app and you are done. remember to go lsposed and in xprivacy to select the app you want to prevent from getting your app list

Question Rooted and debloated with C.47 update (some apps, mainly google, would open and crash)

I don't know if it's just me, but I updated to C.47 by:
Magisk uninstall, restoring stock images.
installing the update
Magisk install to inactive after OTA completes
Reboot.
I have 4 modules. USNF, osm0sis busybox binary, debloater and systemless hosts.
The only way I was able to get them to work was by disabling all modules, rebooting, finding the google play store APK download from APKMirror and installing it.
Now, I have randomly cloned APKs, but they were only ones I debloated. I debloated again and they vanished.
I admit this thread might be a huge waste of your time to read, but if someone is having this trouble, it might bail them out

I am in same situation like u with Google play store and Google services play crash .I try everything but no luck .finally idowngrade to os 11. But I'm very intested to know why Google applications crash .The only magisk module installed is : Octavia dialer A12.

Wow, good to know this is happening and that you found a workaround. I guess I'll probably wait a few days to install this and see if other people are having issues.

In c47 version, the 5G option returned in network settings?

DavidKalil10 said:
In c47 version, the 5G option returned in network settings?
Click to expand...
Click to collapse
Not for me

Skenderbeggar said:
Not for me
Click to expand...
Click to collapse
I've just discovered a workaround isign the app force LTE/5G. With this app is possible to open the Network settings and force the 5G as it was possible in Android 11 using *#*#4636#*#*
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

It fails when reaching the middle

Moka UA said:
It fails when reaching the middle
View attachment 5566125
Click to expand...
Click to collapse
are you rooted?

Yes

Moka UA said:
Yes
Click to expand...
Click to collapse
go to magisk, uninstall magisk. pick restore images. DO NOT REBOOT. install the update. go back to magisk. install magisk to inactive slot. reboot
i'd disable whatever modules you have enabled.

aNGERY said:
go to magisk, uninstall magisk. pick restore images. DO NOT REBOOT. install the update. go back to magisk. install magisk to inactive slot. reboot
i'd disable whatever modules you have enabled.
Click to expand...
Click to collapse
Ok..i have root zygisk ..Is there a problem with that?

Moka UA said:
Ok..i have root zygisk ..Is there a problem with that?
Click to expand...
Click to collapse
Zygisk is fine, only installed modules should be disabled when you update to avoid possible issues. Most modules won't have any issues, though.

Question Google Wallet Contactless not working with root

I've tried to get contactless working on my Pixel 6 Pro, but I'm still getting the same error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've turned on Zygisk and the DenyList, and marked all Google Play Services along with Google Wallet to be on the DenyList (see attached screenshots), and tried resetting all Google {Play Services, Wallet, Play Store} cache and data but that's hasn't fixed the issue either. Magisk is hidden as well. ~~I do pass SafetyNet using `Universal SafetyNet Fix` when tested using `YASNAC` (see attached)~~ I *did* pass SafetyNet until 2 minutes ago it seems, as I ran `YASNAC`, passed, then re-ran it, and failed (see attached for both results). I'm not why I've suddenly stopped passing SafetyNet, but could that be the problem?

I've had a similar problem. I worked out the latest version of Google Wallet has some weird safety check that doesn't work for denylist.
I solved it by uninstalling Google Wallet and downloaded an older version from an APK website (Google 'Google Wallet' and go back a couple of versions). I'm currently using V2.189 from APKPure and it's working on my Nothing Phone 1 (Android 13).
Also, before you install the new (older version) wallet and add it to the denylist, clear the storage and cache from all Play Services Apps in your App Settings. Once you've installed the APK (might need to allow permissions), go straight into the Google Play Store, go your downloaded apps, find Google Wallet, tap on the dots in the top right hand corner and disable automatic updates. This will stop it happening again. I'd do a reboot before opening Wallet as well. Once you've done that, go into Magisk and add it to the deny list. I also use SafetyNetFix on my device. You can find that by googling it and add it to your Magisk modules.
Do a reboot and hopefully it will work for you