I just installed Lineage OS on my Nexus 5 and i checked via root checker my phone is not rooted. But still whenever i try to login in Snapchat it doesn't let me in. I tried many solutions like removing root access from SuperSu(when it was rooted) but still it doesn't help. So can anyone help with that?
vsaery said:
I just installed Lineage OS on my Nexus 5 and i checked via root checker my phone is not rooted. But still whenever i try to login in Snapchat it doesn't let me in. I tried many solutions like removing root access from SuperSu(when it was rooted) but still it doesn't help. So can anyone help with that?
Click to expand...
Click to collapse
Same issue with the note 4
It is an issue of kernel not passing "SafetyNet", which required to complete the login of Snapchat and some other applications.
Easy fix that worked for me on other ROM with same issue is,
1.) Download latest Franco Kernel (Franco Kernel currently passes SafertyNet, that's why).
2.) Backup your "Boot" partition in TWRP.
3.) Flash Franco Kernel. Then reboot.
4.) Login in your Snapchat, it should work this time around.
5.) Go back to TWRP, and use restore function to restore the previous "Boot" partition to get LineageOS kernel back.
Let me know how it goes.
parth7667 said:
It is an issue of kernel not passing "SafetyNet", which required to complete the login of Snapchat and some other applications.
Easy fix that worked for me on other ROM with same issue is,
1.) Download latest Franco Kernel (Franco Kernel currently passes SafertyNet, that's why).
2.) Backup your "Boot" partition in TWRP.
3.) Flash Franco Kernel. Then reboot.
4.) Login in your Snapchat, it should work this time around.
5.) Go back to TWRP, and use restore function to restore the previous "Boot" partition to get LineageOS kernel back.
Let me know how it goes.
Click to expand...
Click to collapse
this didn't work.. i tried installing franco kernel but still not logging in Snapchat
vsaery said:
this didn't work.. i tried installing franco kernel but still not logging in Snapchat
Click to expand...
Click to collapse
it worked.. thanks alot man.. i had to unroot again and then flash franco kernel to make it work
parth7667 said:
It is an issue of kernel not passing "SafetyNet", which required to complete the login of Snapchat and some other applications.
Easy fix that worked for me on other ROM with same issue is,
1.) Download latest Franco Kernel (Franco Kernel currently passes SafertyNet, that's why).
2.) Backup your "Boot" partition in TWRP.
3.) Flash Franco Kernel. Then reboot.
4.) Login in your Snapchat, it should work this time around.
5.) Go back to TWRP, and use restore function to restore the previous "Boot" partition to get LineageOS kernel back.
Let me know how it goes.
Click to expand...
Click to collapse
this works.. thanks
vsaery said:
this works.. thanks
Click to expand...
Click to collapse
No problem. Glad to be of service.
vsaery said:
I just installed Lineage OS on my Nexus 5 and i checked via root checker my phone is not rooted. But still whenever i try to login in Snapchat it doesn't let me in. I tried many solutions like removing root access from SuperSu(when it was rooted) but still it doesn't help. So can anyone help with that?
Click to expand...
Click to collapse
Do you have Xposed installed?
If yes, this is the issue. I have read, that the only soluton is to unistall Xposed, then install Snapchat, then login normally, then download Titanium Backup and backup the app, then reinstall xposed and use the backup to get yourself logged in.
Because this was too bothersome for me, I just installed CASPER, which is an alternative client for Snapchat, just make sure not to save too many snaps, you could get banned for that (I also read somewhere), in fact disable auto downloading snaps in the settings.
Nottrueuser said:
Do you have Xposed installed?
If yes, this is the issue. I have read, that the only soluton is to unistall Xposed, then install Snapchat, then login normally, then download Titanium Backup and backup the app, then reinstall xposed and use the backup to get yourself logged in.
Because this was too bothersome for me, I just installed CASPER, which is an alternative client for Snapchat, just make sure not to save too many snaps, you could get banned for that (I also read somewhere), in fact disable auto downloading snaps in the settings.
Click to expand...
Click to collapse
thanks for answering but i already found a solution.. you can check in other comment.
Franco kernel worked for me on my Nexus 5.
If you get logged out of Snapchat, the process must be repeated.
Curiously, my Nexus 7 can log on to Snapchat with the lineage kernel from lineage-14.1-20170228-nightly-flo-signed.zip ROM, no Franco kernel required.
Related
Hi Guys,
I'm having problems with my Nexus 5, which is running a custom recovery after root access, with CM mode. I then installed Franco Kernel, which worked on the 2nd try. NOW I want to tweak Franco, BUT my SuperUser app isn't allowing it access. I've tried cleaning the superuser logs, I even went into settings to make sure it allows everything, but nothing is happening.
How can I re-gain access to Franco Kernel (I contacted him, but never got anything in return..., and I have the paid app)
Thanks for your help
JustinMorinC said:
Hi Guys,
I'm having problems with my Nexus 5, which is running a custom recovery after root access, with CM mode. I then installed Franco Kernel, which worked on the 2nd try. NOW I want to tweak Franco, BUT my SuperUser app isn't allowing it access. I've tried cleaning the superuser logs, I even went into settings to make sure it allows everything, but nothing is happening.
How can I re-gain access to Franco Kernel (I contacted him, but never got anything in return..., and I have the paid app)
Thanks for your help
Click to expand...
Click to collapse
flash SuperSU with your recovery http://download.chainfire.eu/supersu
Thanks + Recovery
Thanks, will try that, how do it save all my data?
JustinMorinC said:
Thanks, will try that, how do it save all my data?
Click to expand...
Click to collapse
huh? you wont lose any data from flashing it. you will have yo give permission to your root apps when you open them the first time.
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Matthewlawson3 said:
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Click to expand...
Click to collapse
First of all, stop using the stock recovery.
Since you had root access, were you using any modifications such as Xposed?
You can pull your internal storage with adb pull /sdcard/, and your app data with adb pull /data/data/ while in custom recovery.
You can also try pushing a stock ROM .zip downloaded from here to your device with ADB push, then dirty flashing it in recovery (obviously after flashing a custom recovery, also assuming you're on stock ROM).
Also, don't use toolkits. Click the first link of my signature and read some threads if you don't know how to use ADB/fastboot.
On a sidenote I do have xposed framework installed. However, I've never had any problems out of it and I have not modified anything in months.
Matthewlawson3 said:
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Click to expand...
Click to collapse
Matthewlawson3 said:
On a sidenote I do have xposed framework installed. However, I've never had any problems out of it and I have not modified anything in months.
Click to expand...
Click to collapse
Read my previous post, and since you're running Xposed try using it's safemode disable feature, explanation on how that works here: http://forum.xda-developers.com/showpost.php?p=51306764&postcount=9879
Do you think this is caused by Xposed? You want me to disable it to see I assume?
Matthewlawson3 said:
Do you think this is caused by Xposed? You want me to disable it to see I assume?
Click to expand...
Click to collapse
It's entirely possible that a module/Xposed itself is causing a SystemUI crash, it's happened to me before. I'd do it just to be sure, then proceed to what I said in my previous post if it still happens.
Ok its been awhile since I dirty flashed. If I have to do that, what are the exact things that need to be cleared to maintain data after recovery?
Lethargy said:
It's entirely possible that a module/Xposed itself is causing a SystemUI crash, it's happened to me before. I'd do it just to be sure, then proceed to what I said in my previous post if it still happens.
Click to expand...
Click to collapse
Matthewlawson3 said:
Ok its been awhile since I dirty flashed. If I have to do that, what are the exact things that need to be cleared to maintain data after recovery?
Click to expand...
Click to collapse
What do you mean? No data is lost if you dirty flash a ROM, it only reformats /system.
Custom recovery, download stock ROM flashable zip, ADB push zip to your device while it's in recovery, then flash it.
It looks like I may not have to flash anything. The Xposed Disable worked. But how do I proceed if I want to use Xposed still?
Lethargy said:
What do you mean? No data is lost if you dirty flash a ROM, it only reformats /system.
Custom recovery, download stock ROM flashable zip, ADB push zip to your device while it's in recovery, then flash it.
Click to expand...
Click to collapse
Matthewlawson3 said:
It looks like I may not have to flash anything. The Xposed Disable worked. But how do I proceed if I want to use Xposed still?
Click to expand...
Click to collapse
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
OK.
My modules are AC Display, Bootmanager, DS Battery Saver, Google Search API, Gravity Box (KK), Greenify, Immerse Me, Notify Clean, Swype Tweaks, Xblast Tools, and Youtube Adaway.
Lethargy said:
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
Click to expand...
Click to collapse
Matthewlawson3 said:
OK.
My modules are AC Display, Bootmanager, DS Battery Saver, Google Search API, Gravity Box (KK), Greenify, Immerse Me, Notify Clean, Swype Tweaks, Xblast Tools, and Youtube Adaway.
Click to expand...
Click to collapse
Continue with what I've said to try, a few of your modules modify the system and could be causing it.
Go to the xposed module repository and find which of those modules updated recently. I'd bet that's the culprit. Or at least it's a good place to start looking.
Ok before I proceed. I have went into Xposed and disabled all modules. I am now in Root Explorer and have dug down to the "disabled" file following the path indicated. Do I just delete "disabled" and then reboot?
Lethargy said:
Continue with what I've said to try, a few of your modules modify the system and could be causing it.
Click to expand...
Click to collapse
Matthewlawson3 said:
Ok before I proceed. I have went into Xposed and disabled all modules. I am now in Root Explorer and have dug down to the "disabled" file following the path indicated. Do I just delete "disabled" and then reboot?
Click to expand...
Click to collapse
Yep, delete the folder named "disabled"
It may be faster to see which module updated recently and see if that fixes the problem first before going one by one. What do you think?
Lethargy said:
Yep, delete the folder named "disabled"
Click to expand...
Click to collapse
Matthewlawson3 said:
It may be faster to see which module updated recently and see if that fixes the problem first before going one by one. What do you think?
Click to expand...
Click to collapse
Worth a shot. In the end it's probably a single module, or a combination of conflicting modules, that's causing the issue.
Looks like the latest updated was Bootmanager on July 26.
Lethargy said:
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
Click to expand...
Click to collapse
Matthewlawson3 said:
Looks like the latest updated was Bootmanager on July 26.
Click to expand...
Click to collapse
Try enabling them one by one by update date.
I'll reboot with all modules off first. Ok, I no longer am getting the error message. At least it's not Xposed itself!
Matthewlawson3 said:
Looks like the latest updated was Bootmanager on July 26.
Click to expand...
Click to collapse
Hey guys! I got problem. I can not logged to snapchat with my NOTE EDGE (SM-N915FY) on THAT ROM. I try backup by titanium backup in stock rom where I can log in before I rooted it. But when i restore apk+data after few second snapchat automaticly logged of me. I have no idea why this don't work. Maybe someone have the same problem and solve it. Help me! I use magisk root with hide but on stock and custom rom they don't pass SafetyNet and i don't know why.
Hey just saw this by coincidence and know the problem and the solution:
Snapchat gets blocked on rooted ROMs including rooted stock ROMs. I managed to get it to work by doing Titanium backup of a working version and then restoring it on my rooted device. Have a look at the two links below. Instead of Bluestacks as some recommend, I'd probably use the Nox Android player. Getting root on it is easy:
https://forum.xda-developers.com/xposed/snapchat-rooted-phones-xposed-t3283198
https://forum.xda-developers.com/xposed/how-to-getting-snapchat-to-login-rooted-t3558412
Good luck.
Do have xposed installed? I had to remove it first and reinstall it after I logged in
Jay1324 said:
Do have xposed installed? I had to remove it first and reinstall it after I logged in
Click to expand...
Click to collapse
Sir how can I go back in kitkat version of note smn9w816
I have a Oneplus 1 running CM11 44s Kitkat 4.4.4
I did a clean flash of CM11 and now I am unable to install any app from playstore. As soon as an app finishes installing, the phone hardboots and enters bootloop or I get continuous error messages Trebuchet stops working, Play Store stopped working
I have to goto Safe Mode and unistall app to recover phone.
Apps which I have tried to install and have been unsuccessful Greenify, Nova Launcher, Facebook, Gboard, Microsoft SMS Organiser
Basically, I am unable to install anything at all! All these were running fine before, now dont understand whats wrong!
I cleaned whole phone, formatted all with fastboot and reinstalled CM11, but the problem remains.
Please help!!
soniabajaj said:
I have a Oneplus 1 running CM11 44s Kitkat 4.4.4
I did a clean flash of CM11 and now I am unable to install any app from playstore. As soon as an app finishes installing, the phone hardboots and enters bootloop or I get continuous error messages Trebuchet stops working, Play Store stopped working
I have to goto Safe Mode and unistall app to recover phone.
Apps which I have tried to install and have been unsuccessful Greenify, Nova Launcher, Facebook, Gboard, Microsoft SMS Organiser
Basically, I am unable to install anything at all! All these were running fine before, now dont understand whats wrong!
I cleaned whole phone, formatted all with fastboot and reinstalled CM11, but the problem remains.
Please help!!
Click to expand...
Click to collapse
What about installing apps from other sources?
Does that work?
Mr.Ak said:
What about installing apps from other sources?
Does that work?
Click to expand...
Click to collapse
No installing from other sources also dont work, I downloaded apks from apkmirror, same issue, as soon as installation finishes, it will hardboot and enter bootloop or will start giving continuous errors
My phone is not a smartphone anymore!! :crying: :crying:
soniabajaj said:
No installing from other sources also dont work, I downloaded apks from apkmirror, same issue, as soon as installation finishes, it will hardboot and enter bootloop or will start giving continuous errors
My phone is not a smartphone anymore!! :crying: :crying:
Click to expand...
Click to collapse
I doubt it.
Why don't you flash cos13.1.x?
Mr.Ak said:
I doubt it.
Why don't you flash cos13.1.x?
Click to expand...
Click to collapse
Yeah I could do that, but I would like to understand whats going wrong in present case, I have had flashed CM11 many times since past 4 yrs but never faced such an issue.
I even installed TWRP and SuperSU latest version and also Old versions, I tried installing old versions of apps, but phone keeps crashing! Wonder whats wrong?!
Is this a firmware issue?(Tried flashing firmwares too)
or Partitions gone bad?
I tried searching but couldnt find any resource on how to recreate partitions.
Can anyone help please?
soniabajaj said:
Yeah I could do that, but I would like to understand whats going wrong in present case, I have had flashed CM11 many times since past 4 yrs but never faced such an issue.
I even installed TWRP and SuperSU latest version and also Old versions, I tried installing old versions of apps, but phone keeps crashing! Wonder whats wrong?!
Is this a firmware issue?(Tried flashing firmwares too)
or Partitions gone bad?
I tried searching but couldnt find any resource on how to recreate partitions.
Can anyone help please?
Click to expand...
Click to collapse
Wait,what if you flash cm11? I mean you just wanna stay on KitKat,so why don't cm11?
https://www.androidfilehost.com/?fid=24052804347767866
Clean flash this cm11 nightly+gapps you like.
Make sure you use latest twrp.
Same issue here. Happens not to all apps though. Just particular ones after updating certain apps. Not sure what happened. Only solution is to avoid installing those kind of apps.
Hey all,
Over the last few months, I haven't been able to get Google assistant to make phone calls or send text messages. All other functions work.
When I say, 'call my wife', or 'send text message to wife', it tells me that function is unavailable.
It used to work flawlessly.
I have changed nothing to cause it. I just woke up one morning and it didn't work.
So far I have tried:
-Factory reset
-clear cache, etc
-Magisk hide on assistant app, call manager, Google play services and google text to speech
I am on latest stable Oos with latest XxX Rom.
The issue started around 3 months ago.
Where should i be looking to fix this?
Thanks in advance for any help.
Does anyone know of any other forums I can post this question? I can't post in the OnePlus forums yet because of new member restrictions. I'm just trying to get more coverage for my issue so that I can get help solving it.
Do you know what day this happened?
spr33 said:
Do you know what day this happened?
Click to expand...
Click to collapse
I'm not sure. It was roughly 3 months ago.
cubic25 said:
Does anyone know of any other forums I can post this question? I can't post in the OnePlus forums yet because of new member restrictions. I'm just trying to get more coverage for my issue so that I can get help solving it.
Click to expand...
Click to collapse
Not sure but that happened to me too but here's what i did
1. Boot into twrp
2. Wipe system, vendor and cache no need to wipe data unless you don't care losing your files DO NOT REBOOT
3. Flash latest oos either 9.0.9 or beta Q is up to you DO NOT REBOOT
4. Flash twrp REBOOT
You'll all set if you need root just flash magisk
Let me know if it worked for you
J0nhy said:
Not sure but that happened to me too but here's what i did
1. Boot into twrp
2. Wipe system, vendor and cache no need to wipe data unless you don't care losing your files
3. Flash latest oos either 9.0.9 or beta Q is up to you
4. Flash twrp
You'll all set if you need root just flash magisk
Let me know if it worked for you
Click to expand...
Click to collapse
I did all this on Sunday hoping that it would fix the issue. It hasn't.
Additional info: I have also just discovered that if I open the assistant app and type in 'call.........' or 'message........' , it says there is no app installed to perform that function.
J0nhy said:
Not sure but that happened to me too but here's what i did
1. Boot into twrp
2. Wipe system, vendor and cache no need to wipe data unless you don't care losing your files DO NOT REBOOT
3. Flash latest oos either 9.0.9 or beta Q is up to you DO NOT REBOOT
4. Flash twrp REBOOT
You'll all set if you need root just flash magisk
Let me know if it worked for you
Click to expand...
Click to collapse
Don't think this will be useful, this is an Assistant issue, reflashing the ROM probably won't help.
cubic25 said:
I did all this on Sunday hoping that it would fix the issue. It hasn't.
Additional info: I have also just discovered that if I open the assistant app and type in 'call.........' or 'message........' , it says there is no app installed to perform that function.
Click to expand...
Click to collapse
Can you check in the settings, under Apps, and Default Apps, if you correctly have a Phone app and an SMS app set as default ? Or maybe the Google App does not have the permissions it needs (Phone Calls and SMS permissions), you could also check that. This is probably a little thing like this, it's 99% sure it's an app or configuration issue.
Both apps are set as default and all apps have all permissions ticked.
I too have the issue and have tried several things with no luck.
I've also been experiencing this. It's been pretty frustrating when trying to use the assistant with android auto.
What ROM are you guys running? I wonder if there is any similarities between our devices.
cubic25 said:
What ROM are you guys running? I wonder if there is any similarities between our devices.
Click to expand...
Click to collapse
I'm on beta 28
Well today I installed Android Auto, I was also able to install Google speech to text and bam, I'm able to use Okay Google to text and call again.