After flashing HavocOS 2.9 I can't log into Snapchat. I have Havoc running on my Redmi Note 5 and Snapchat works fine.
Any ideas on how to get around this?
You could try to backup snapchat on the device where you're logged in already to an SD card and then restore that snapchat to the device its not working on then once its restored it should be logged in already. Just don't log back out in case it doesn't let you log in again.
Related
So I have completely wiped the phone. Internal storage, sd card and all and I still get the error from snapchat. I do not have Xposed installed, or anything for that matter.
So I've installed and ran Nougat (AICP) and snapchat ran perfectly. Reverting to 6.1 (TruePure) to see if this has fixed my problem.
ive also, returned to stock and since then got error msg and not being able to log snap
the-light said:
ive also, returned to stock and since then got error msg and not being able to log snap
Click to expand...
Click to collapse
So, I'm not completely sure how it worked but I got a reccomedation to use Magisk. After a clean install of TruePure 2.9 (remember in aroma to set root to systemless) I installed Magisks, and somehow it just worked. I was able to sign in.
http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
kspreco said:
So, I'm not completely sure how it worked but I got a reccomedation to use Magisk. After a clean install of TruePure 2.9 (remember in aroma to set root to systemless) I installed Magisks, and somehow it just worked. I was able to sign in.
http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
thx. might give it a shot
Hello so I was using snapprefs so with that Said, I did a backup of sc and downgraded the app and restored data and everything worked fine intill One Day snapchat wouldnt update/refresh my snaps so and so updated the snapchat again and proceeded to repeat the original steps but no matter how much Ive tried fixing the problem i End up with having to be forced to update to the latest snapchat for me to accses all my snapchats I get.
Any1 More them Me with this problem?
>Older version of snapchat works for a while till it completely stöps working (cant refresh my snap)
I did find a solution to this which we'll... Clean your host file
Hi amm my G7102 enters bootloop immediately after installing whatsapp application has been tested on lolipop CM and Recuression remix, knowing that it was working fine before that. also note I flashed many times and used stock firmware.
how to fix that issue?
same problem for me... hav u found any fix???
Yup..I was to using cm and RR...But Whatsapp issue didn't came ..But installing other apps such as magisk manager...The problems come.. there is not fix to solve the problem..But if you want to use RR only then use RR Xperia mod ROM..In tht ROM apps installed properly... Or change the rom
I also had this issue, running LineageOS 13 6.0.1 on a Redmi Note 4 SD, and the latest WhatsApp update just crashed all the background apps and after a reboot it just stuck in a bootloop. Luckily I had a somewhat recent TWRP backup, so I recovered it and just removed Whatsapp. I wonder what happened there... I DO had the beta version installed, but I've been using Whatsapp beta without problems for years. :S
Same issue w/ cm12...only after installing the wapp.
Tried recerting by manually downloading to march ver. Still the same.. The moment wapp is installed, phone goes into bootloop. No other option to factory reset..
Any possible clues.. Had someone tried a more old version 2017??
i have same problem using CM12.1. Try this :
if your phone bootloop : uninstall whatsapp from safe mode ( press vol - ) while boot.
uninstall whatsapp from play store.
download whats app apk from apkmirror.com ( i'm using whatsapp 2.18.117 (beta).
and it's work fine now.
Now using CM12.1
I ran into the same problem when I installed greenify on CM12.1. Dunno if there's a fix or not but I figured out how to get out of the bootloop. My theory was, If any app installation caused bootloops, it means the app installation was somehow interrupted and this app is now in a broken state. You just have to boot into TWRP, use TWRP's file manager or aroma file manager to delete all app related files from data/apps or other app related folders. I deleted all Greenify related files and my phone got out of bootloop and booted normally.
Thank you sir, you helped me greatly!
CM 110.0 boot looks
Updates of several apps including Whatsapp are causing my phone to go into boot loop. I had to do a factory reset and sideload of older versions of the apps (where available).
I am running Cyogenmod 11.0 Android 4.4.4 on a Oneplus One.
Does anyone have a solution for this problem? I have been using an older version of Whatsapp but support for that version is going to be cut off by Whatsapp in a few days.
Thanks for any help.
Hello,
I've been trying to flash a new Rom after I got sick of AOSPEX on my gprimelte. I first went to Lineage OS 16, which went fine until I realized XDA Labs crashes. I then went to RR oreo but had some problems with my apps. I can't login to my google account as it gets stuck on "checking info" then goes to a black screen (The only way to remedy this for me is to install an old version of Mind the Gapps, probably because of Play Services). Sometimes Photos say that it hasn't been installed correctly, and other apps like GBoard say to update play services. After that's fixed, I see that ROM toolbox crashes and Magisk Manager also crashes when I try to check info on a downloadable module. I tried Lineage OS 15.1 GO and DotOS using TWRP 3.2.1 with the same results. Could it be the Gapps, the Roms (as they were all made by the same person), or the TWRP (also made by the same person).
I restored a backup which I just made a few hours before. As expected everything worked but Google photo. It crashes as soon I open a photo or video or album.....
I deleted cache and data, Uninstalled the update and updated it again. I'm on Resurrection remix 6.2.
Someone have a idea how to solve that issue?