Rooted phone, now cant log into Snapchat - Samsung Galaxy On5 Questions & Answers

Basically my daughters phone had no space. So I rooted it, installed app2sd, and it appeared to be ok for the last week.
Now it signed her out of some apps, and she cant log into snapchat. Also netflix isnt showing up anymore.
I opened SuperSU and disabled root, snapchat still doesnt work. I uninstalled supersu and app2sd, everything besides twrp recovery, and still not working.
What options do I have? Do i need to remove twrp and go full stock again?

You don't need to unroot or re-install stock firmware. Just install "Root Switch" allow it root access and switch off root previliges. Now Run Snapchat it will run like a Boss.
Link: https://androidfilehost.com/?fid=817550096634777108
---------- Post added at 08:19 AM ---------- Previous post was at 08:16 AM ----------
Link: https://androidfilehost.com/?fid=817550096634777108
Just download and install.
Give Root Access and uncheck the box.
Now run Snapchat It will work.

Related

[GUIDE][VIDEO] How To Install OxygenOS

OnePlus has finally released Oxygen OS!
This tutorial is noob friendly, so it's very easy.
If you have any questions, just ask
Links:
Toolbox: http://inthiaano.com/oneplus-one-toolbox/
OxygenOS: https://forums.oneplus.net/threads/oxygenos-is-here-installation-guide.289398/
TWRP: http://dl.twrp.me/bacon/
Flashed O2 no problem, runs perfectly fine, but root access is where I'm having trouble
Flashed SuperSU2.46 in TWRP opened SU app and it says binary not found and can't be downloaded.
Unistalled SU updates and updated from PlayStore, still nothing. Tried insalling SU2.01 from TWRP, opened app, same thing no binary found.
Back to CM11S until I can get root in O2 and a Ti restore
mooseknuckles1 said:
Flashed O2 no problem, runs perfectly fine, but root access is where I'm having trouble
Flashed SuperSU2.46 in TWRP opened SU app and it says binary not found and can't be downloaded.
Unistalled SU updates and updated from PlayStore, still nothing. Tried insalling SU2.01 from TWRP, opened app, same thing no binary found.
Back to CM11S until I can get root in O2 and a Ti restore
Click to expand...
Click to collapse
When I installed OOS, TWRP asked if I wanted to install SuperSU. It then claimed to have done this, but on reboot I also had the same as you. Installed SuperSU v2.46 manually from TWRP and rebooted, all working perfectly.
TL;DR - try installing SuperSU manually again yourself to be sure.
SimonTS said:
When I installed OOS, TWRP asked if I wanted to install SuperSU. It then claimed to have done this, but on reboot I also had the same as you. Installed SuperSU v2.46 manually from TWRP and rebooted, all working perfectly.
TL;DR - try installing SuperSU manually again yourself to be sure.
Click to expand...
Click to collapse
I did the same thing, no problems here
huh, yea I did the same. I'll give it another whirl and see if it works. thanks
---------- Post added at 10:49 AM ---------- Previous post was at 09:57 AM ----------
Ya I'm not sure why it isn't working. My steps are as follows, and I already have my bootloader unlocked and TWRP installed:
1. Ti Backup
2. TWRP backup
3. Wipe - dalvik, system, data, cache
4. Flash O2 OS, after OS install when asked to flash SuperSU i swipe yes
5. Reboot, not rooted
6. Manually Flash SU 2.46 in twrp
7. Not rooted
When I open the SU app I still get the message "there is no SU binary intalled, and SuperSU cannot install it. This is a problem"
---------- Post added at 10:58 AM ---------- Previous post was at 10:49 AM ----------
While it is still giving me that message, it is however granting me permission for Titanium BU. So it is letting root access apps run...
SO Flash Oxy rooted and slim without crap.

[Q] SuperSU not detecting/granting access (prompt) to newly downloaded root apps

A brief background:
My Device: Samsung Note 4 SM-N910C
What I did:
1. Flashed stock BOE3 firmware
2. Rooted phone using CF-Autoroot
3. Flashed TWRP
4. Flashed Wanam Lite ROM
5. Flashed Stock BOE3 Kernel
SuperSU can easily detect my previously installed root apps like Greenify, Titanium Backup, ROM Toolbox Pro, etc. once I activate them. However, when downloading new root apps (My Android Tools, GSAM Root Companion), SuperSU does not detect/no prompt for root access. I was trying to disable some receivers in My Android Tools, but it gets stuck on loading and I have to close the app.
What seems to be the problem? Is there anything that I can do to fix this issue?
Your expert advice/opinion matters to me.
Thanks!
I'm seeing the same problem. T-Mo Note Edge 915T on Lollipop, just updated from KK, flashed the ROM and running into the same. Reinstalling SuperSU did not help.
---------- Post added at 06:19 PM ---------- Previous post was at 06:14 PM ----------
BTW, if I set the default mode to "Grant", new apps work fine. The new app does not get added to the SuperSU list, nor do I want to leave it like this. I want to use the "Prompt" setting.
https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
2.49 solved my problem...

Root, Rom, for Sprint 5.0.1

Is there simple instructions on how to root and install a rom for the latest lollipop update on the sprint s4 ? Ive been able to use kingroot and it worked but ive read you have to use supersu to be able to install custom rom so I deleted everything and its basically back to stock again. I'm just wondering if there is simple step by step instructions without bouncing all over the place to get it done ?
Took me a while. I used twrp and it wanted a su binary update. Couldn't figure it out so I installed kingroot and it somehow gave me the su binary that I needed and I acquired root. Now the backup (recovery) that was a whole different story. Go to the Thread on everything for your specific device. It has complete instructions on rooting S4 mine was Sph-l720t. I takes patients you can figure it out. The good news is you can always reflash your firmware if all fails.
Sent from my SPH-L720T using Tapatalk
---------- Post added at 08:05 PM ---------- Previous post was at 08:03 PM ----------
Odin and cf-autoroot is the easiest. Was for me. Has super su in the zip file.
Sent from my SPH-L720T using Tapatalk
thanks engine... I can never get supersu to work with lollipop so I can get it rooted is my problem.
Kingroot works but THEN you need to use super_sume from the play store. I used an older version of super_sume in my full 2 part video of the entire process... https://www.youtube.com/watch?v=IWnYFDQ1Vio
To install a custom ROM, you need a custom recovery OR you can try Flashfire without a custom recovery...

Nexus 7 Xposed installation error

Hello. I would like to ask everyone here that why can't I install Xposed on my N7 2012 (WiFi) ? I'm currently using stock rooted 5.1 with TWRP installed along with SuperSU 2.82. When I try to install Xposed through the it's installer, I always get the message "Error 1". It says I haven't got enough space in /system, even though I deleted the Google Sheets app before.
So far, what I've done is:
- I get back to stock
- I installed TWRP after setup wizard
- I sideloaded SuperSU
- Then it comes to the installation of Xposed Installer.
If I use the official version, it returns error 1. If I use the systemless version (Magisk) , it install successfully, but the Xposed Installer says Xposed is not active.
Any help is really appreciated.
minhducsun2002 said:
Hello. I would like to ask everyone here that why can't I install Xposed on my N7 2012 (WiFi) ? I'm currently using stock rooted 5.1 with TWRP installed along with SuperSU 2.82. When I try to install Xposed through the it's installer, I always get the message "Error 1". It says I haven't got enough space in /system, even though I deleted the Google Sheets app before.
So far, what I've done is:
- I get back to stock
- I installed TWRP after setup wizard
- I sideloaded SuperSU
- Then it comes to the installation of Xposed Installer.
If I use the official version, it returns error 1. If I use the systemless version (Magisk) , it install successfully, but the Xposed Installer says Xposed is not active.
Any help is really appreciated.
Click to expand...
Click to collapse
Hey!
I know it's kind of an old topic, but did you manage to do it? I'm in the same situation as you, I'd appreciate your help!
Thanks!
---------- Post added at 03:21 PM ---------- Previous post was at 03:19 PM ----------
minhducsun2002 said:
Hello. I would like to ask everyone here that why can't I install Xposed on my N7 2012 (WiFi) ? I'm currently using stock rooted 5.1 with TWRP installed along with SuperSU 2.82. When I try to install Xposed through the it's installer, I always get the message "Error 1". It says I haven't got enough space in /system, even though I deleted the Google Sheets app before.
So far, what I've done is:
- I get back to stock
- I installed TWRP after setup wizard
- I sideloaded SuperSU
- Then it comes to the installation of Xposed Installer.
If I use the official version, it returns error 1. If I use the systemless version (Magisk) , it install successfully, but the Xposed Installer says Xposed is not active.
Any help is really appreciated.
Click to expand...
Click to collapse
Hey!
I know it's kind of an old topic, but did you manage to do it? I'm in the same situation as you, I'd appreciate your help!
Thanks!
Martin-cai said:
Hey!
I know it's kind of an old topic, but did you manage to do it? I'm in the same situation as you, I'd appreciate your help!
Thanks!
---------- Post added at 03:21 PM ---------- Previous post was at 03:19 PM ----------
Hey!
I know it's kind of an old topic, but did you manage to do it? I'm in the same situation as you, I'd appreciate your help!
Thanks!
Click to expand...
Click to collapse
Sorry for late reply. Well, after searching I eventually came to the fact that the /system partition wasn't large enough...I guess if you're rooted, you may consider deleting some pre-installed apps (or at least move them out of /system).
If you aren't, sorry, I can't

unlocked bootloader - Nougat (7.0) - want Android Pay

I screwed up and left the bootloader unlocked when I flashed the 7.0 OTA. So, SafetyNet test fails and Android Pay refuses to work. Based on what I have found and read, I believe it is impossible (currently) to simply relock the bootloader. I think I need to root with Magisk and then use the appropriate module to hide root and unlocked status from Android Pay. Is that the possible? Is that the correct approach? I have been searching and reading but my mind is swimming now. Must be getting too old for this stuff.
Thanks in advance.
Root with magisk - hide is inbuilt - don't need add. module.
How to:
Boot twrp - fastboot boot NameTwrp3xx.img
Backup all with twrp
Restore boot with twrp
Install Magisk14+.zip
Reboot.
If you need - you can flash twrp.
---------- Post added at 07:21 AM ---------- Previous post was at 07:21 AM ----------
@BigBadger
dzidexx said:
Root with magisk - hide is inbuilt - don't need add. module.
How to:
Boot twrp - fastboot boot NameTwrp3xx.img
Backup all with twrp
Restore boot with twrp
Install Magisk14+.zip
Reboot.
If you need - you can flash twrp.
---------- Post added at 07:21 AM ---------- Previous post was at 07:21 AM ----------
@BigBadger
Click to expand...
Click to collapse
So I did this, and Magisk is installed, set to hide for Android Pay, and it's still not working. It still recognizes the unlocked bootloader. Is there anything else I can do?
What is in magisk manager - safety net status?
Magisk 14? Stock Nougat? @yaoverstand
@dzidexx
ctsProfile: false
basicIntegrity: false
stock nougat
Magisk 14
Latest TWRP
Sorry, I don't know why.
Wipe all, restore boot + system, format data and try again.
---------- Post added at 08:08 PM ---------- Previous post was at 08:07 PM ----------
@yaoverstand
yaoverstand said:
So I did this, and Magisk is installed, set to hide for Android Pay, and it's still not working. It still recognizes the unlocked bootloader. Is there anything else I can do?
Click to expand...
Click to collapse
Go into Settings in the Magisk app, scroll down about halfway, and make sure the Magisk hide slider is on.
If it shows on toggle it off then back on and again then reboot and try the safety net check again. I've had to do this once or twice right after flashing Magisk.
@jason2678
Tried this just now, and I'm still failing the safety net check in the same manner.
Could it have to do with the fact that I flashed a stock nougat image instead of taking the ota?
What did you flashed?
Give here link to thread.
Your model is...? Give full info. @yaoverstand
dzidexx said:
What did you flashed?
Give here link to thread.
Your model is...? Give full info. @yaoverstand
Click to expand...
Click to collapse
Just an update. I flashed the official image from the when the OTA came out.
I restarted Magisk with hide slider off, and then turned it on when the phone came back on. Then I restarted again, and all is well. Passed safetynet and everything. Thanks guys!
jason2678 said:
Go into Settings in the Magisk app, scroll down about halfway, and make sure the Magisk hide slider is on.
If it shows on toggle it off then back on and again then reboot and try the safety net check again. I've had to do this once or twice right after flashing Magisk.
Click to expand...
Click to collapse
I think in magisk 14.3 it's on by default now
Spencervb256 said:
I think in magisk 14.3 it's on by default now
Click to expand...
Click to collapse
I think so too, but I've had it happen a few times where hide wasn't really on until I turned it off, then back on again. That might have been pre 14 versions. I don't flash my phone too often.

Categories

Resources