Related
Super SU by CF
SuperSU is the Superuser access management tool of the future
Features include:
- Superuser access prompt
- Superuser access logging
- Superuser access notifications
- Per-app notification configuration
- Temporary unroot
- Deep process detection (no more unknowns)
- Works in recovery (no more segfaulting)
- Works when Android isn't properly booted
- Works with non-standard shell locations
- Trusts ADB connection
- Always runs in ghost mode
- Wake on prompt
The Pro version additionally offers:
- OTA survival mode (no guarantees)
- Full color-coded command content logging (input/output/error)
- Per-app logging configuration
- Per-app user override
- PIN protection
Who, What Why ? - said by CF
As you may know, I make a lot of apps that use or require root. I also release rooted kernels. I run into a lot of issues with existing Superuser tools. More importantly, a lot of my users run into these issues as well and then email me about it. So I decided to do something about this. Doesn't mean these were problems you have ever seen, or will ever see.
And thus, I have written - pretty much from scratch - SuperSU. I have taken the su binary command line parameter parsing from Superuser, to make sure that is compatible. Aside from that, it is completely rewritten, because how I wanted to do a number of things was incompatible with the existing codebase.
This is not a stab at ChainsDD, or his skills. He has done great work and will no doubt continue to do so, however, I felt the need for some of these changes, and thus made them. This is an early release, so I expect there will be some unforseen issues somewhere.
From now on, all CF-Root and Mobile ODIN Pro (EverRoot) releases will be built around SuperSU.
Please note that SuperSU is not hardened-security-tested or reviewed, and may be exploitable (... as may other solutions ...).
Install :
Flashable Zip v0.93
Market :
Lite
Pro
Note : Pro is key only, you need to install lite version first.
If you install from market, you will have two superuser, remove older one with system appl remover, or any other application can perform same job.
Remember, if you remove older first without installing newer one, you will lose Root n newer won't run.
One more thing market version will be regular application, so hard reset can delete it. So better install with flashable zip, to make it system application.
Source : http://forum.xda-developers.com/showthread.php?t=1538053
Thanks a lot doc. Gonna give it a try.
---------- Post added at 05:52 PM ---------- Previous post was at 05:50 PM ----------
Sorry to say but this belongs to General Section.
Nice one, Dr.Ketan.
Perhaps your fine installation instruction could also include this:
"Superuser (the old one) is a system app and should be removed from /system/app/ folder using Root Explorer, ES Eplorer with root permissions, or similar explorer app. Titanium Backup does not show Superuser in its app list, and therefore cannot remove it."
Otherwise you'll be swamped with Titanium questions.
This is modding
any thing android Mod, should be better place under development.
thogh let's leave it upon moderator..
dr.ketan said:
This is modding
any thing android Mod, should be better place under development.
thogh let's leave it upon moderator..
Click to expand...
Click to collapse
i think it doesnt work if USB debugging is enabled and if it is disabled then it works fine...
grgsiocl said:
i think it doesnt work if USB debugging is enabled and if it is disabled then it works fine...
Click to expand...
Click to collapse
CF says he has fixed that bug in v0.74, and that's the one posted here.
I have no issue with USB debugging ON
Confirmed working fine! Recommended to install via CWM. It will replace the other automatically so you don't have to manually remove it.
Sent from my GT-N7000 using XDA
kopitalk said:
Confirmed working fine! Recommended to install via CWM. It will replace the other automatically so you don't have to manually remove it.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Newbie question here, (sorry) so you don't just download from the market/play store..... open and it will install on it's own?
Sent From my Two Tin Cans & String Device on The Wookie Network
It will install, but not as system application. So it is recommended to flash with CWM. as well you have to remove old manually, if you install from market
dr.ketan said:
It will install, but not as system application. So it is recommended to flash with CWM. as well you have to remove old manually, if you install from market
Click to expand...
Click to collapse
Another newbie question... Is there enough of a difference between superuser & supersu for a newbie to risk mucking up their phone?
Thanks!
EDIT : are there instructions as to how to flash with CWM? SORRY!!
Sent From my Two Tin Cans & String Device on The Wookie Network
Superuser v0.75 has been released.
Changelog:
10.03.2012 - v0.75
- Adjustment to OTA survival (better!)
- Slight speedup in Settings
- Fixed native settings update after temp-re-root
- Clear data no longer clears PIN code
- Layout: Prompt: Grant and Deny switch positions (ICS style)
- Layout: AppDetail: Save and Cancel switched positions (ICS style)
- Layout: Added xlarge PIN layout
http://forum.xda-developers.com/attachment.php?attachmentid=940641&d=1331395344
P.S. Dr.Ketan, when I try to download CWM flashable zip from your 1st post I get a 404.
Ya b'coz link replaced by CF with new version
updated now
dr.ketan said:
Ya b'coz link replaced by CF with new version
updated now
Click to expand...
Click to collapse
even mobile Odin is updated with 2.25
Very Slow Boot Up Following Switch to SuperSU Pro
My Note is running rooted stock ROM with Franco.kernel v6. After installing the SuperSU v.75.zip with CWM and installing the Pro key, and removing Superuser.apk my Note is VERY slow to boot up. It took less than 1 minute immediately prior to SuperSU and now takes 5-6 minutes. It runs wifi and mobile data and sync together EVERY time it boots. It never did this before. It also runs "Media Scanning 6-8 times before it finishes booting.
I'm not complaining, just informing. I realize that this is a new work in progress as posted in the OP post #1. Is anyone else having these issues? If not, any suggestions to correct these problems? I have tried clearing Dalvik and cache partition through CWM app.
Thank you for any help and/or advice.
kraz
krazman325 said:
My Note is running rooted stock ROM with Franco.kernel v6. After installing the SuperSU v.75.zip with CWM and installing the Pro key, and removing Superuser.apk my Note is VERY slow to boot up. It took less than 1 minute immediately prior to SuperSU and now takes 5-6 minutes. It runs wifi and mobile data and sync together EVERY time it boots. It never did this before. It also runs "Media Scanning 6-8 times before it finishes booting.
I'm not complaining, just informing. I realize that this is a new work in progress as posted in the OP post #1. Is anyone else having these issues? If not, any suggestions to correct these problems? I have tried clearing Dalvik and cache partition through CWM app.
Thank you for any help and/or advice.
kraz
Click to expand...
Click to collapse
what you said was true...it slows up booting...but what i did was, in supersu app, i selected grant as default and there is no need for prompt...after that, booting as speed up!
I actually found my own solution as you were posting! Thanks for your help, grgsiocl!!! I did leave default access set to PROMPT though as it will only show the first time until i grant permission.
MY SOLUTION: I unchecked the show Notification Toasts, rebooted and total boot up took 50 seconds!
Sorry for wasting space in this thread!!! Hopefully, anyone else having similar trouble will see this.
kraz
Thanks Doc!flashing now
krazman325 said:
I actually found my own solution as you were posting! Thanks for your help, grgsiocl!!! I did leave default access set to PROMPT though as it will only show the first time until i grant permission.
MY SOLUTION: I unchecked the show Notification Toasts, rebooted and total boot up took 50 seconds!
Click to expand...
Click to collapse
Yeah, this is what CF has to say about it in his original thread:
Chainfire said:
PROTIP:
For extra performance, disable notifications. Logging does not impact performance much.
Click to expand...
Click to collapse
I think it would have been better to just link to chainfires thread rather than repost what he posted.
hey guys i have one problem with supersu.
i installed clean master and do cleaning **** and startup cleaning things and after reboot all apps that have granted root permission( foldermount, gmd gestures, lightflow, etc), these apps shows no toast popup after boot and to make them grant permissions i have to open them. Same thing when i installed boot manager and did not do anything but boot and again no supersu toast popups about root permissions after boot.
is there a way to keep the root grants after the boot? ( i have checked default acces to grant in supersu app)
I'm having problems with clean master working with SuperSu too.
clean master is so powerfull that disables supersu permissions.
They probably change some file permissions that SuperSU frowns at.
Chainfire said:
They probably change some file permissions that SuperSU frowns at.
Click to expand...
Click to collapse
i want to maintain supersu permissions after every boot no matter what. is there some option in supersu to be activated for that?
i'm on note 3 rooted with stock tw.
''enable supersu during boot''
please explain to me for what is this option
thx :good:
bump
dancapitan said:
''enable supersu during boot''
please explain to me for what is this option
thx :good:
Click to expand...
Click to collapse
This option has a summary that's pretty unclear. I've emailed the dev, hope to receive an answer soon. Fact is apps running during the boot_completed seem to get root randomly if this option is not enabled! Let me insist on the random fact, as my apps get root on boot frequently but not all the time. Other users have reported the same random behavior. Once the option is enabled everything works as expected!
However the option seem to imply that any root request on boot will be granted!? Regardless of user choice????
To make it short, check the option "enable supersu during boot" and root apps will receive root on boot as they used to!
3c said:
This option has a summary that's pretty unclear. I've emailed the dev, hope to receive an answer soon. Fact is apps running during the boot_completed seem to get root randomly if this option is not enabled! Let me insist on the random fact, as my apps get root on boot frequently but not all the time. Other users have reported the same random behavior. Once the option is enabled everything works as expected!
However the option seem to imply that any root request on boot will be granted!? Regardless of user choice????
To make it short, check the option "enable supersu during boot" and root apps will receive root on boot as they used to!
Click to expand...
Click to collapse
You should turn this into a proper bug report in the proper thead (either the beta or its own new thread) with all the useful information you think may be relevant. There is no email support, all support is here.
The option itself is for apps that run before Android is fully up and running, or su from adb shell during a bootloop, etc. I thould not influence apps running su from bootcomplete receivers, and if it does, then that needs to be investigated.
Is there currently any way to enable this feature via ADB on a boot looped phone? I really wish I would have known about this! I wouldn't be stuck where I'm at if I had only checked this option. Device is stuck at LG logo, no download or recovery, but has access to ADB. SU was installed, but I don't have root via ADB since the phone isn't finished booting...thus I'm not able to copy over the proper system.img or change the recovery/laf. Dang!
I have the problem too, when I install Fake Wifi, the automatic SuperSU granted is not working. Please help some advance. Thank's.
Hey guys why root required apps request for root access after installing super su
I have the same problem, have to add a task in tasker, auto open supersu and root granted apps once after boot,
Hello.
So I installed a custom recovery, flashed lollipop fw and installed supersu.
Today I was trying to install Viper4Android but, unfortunately, it does not work.
I also installed the drm restore patch (audio clear + is working).
Is there any fix ? Is Viper working for someone here?
Thanks in advance.
Interested too, have a z3c too and have found a few threads describing the installation in 2 steps, flashing via recovery and installing an .apk but nothing specific for z3c.
will update this thread once I have a full nandroid backup and am ready to play around.
I was in the same situation as you guys and couldn't live without V4A.
You/we forgot 1 step
You need to set SELinux mode to permissive and then install V4A driver:
Use this simple app:
https://play.google.com/store/apps/details?id=com.mrbimc.selinux
Amy more advice? Tried that, then set it back, yet viper doesn't seem to be getting used although the driver is installed, where do I select viper as the processor for audio?
ovizii said:
Amy more advice? Tried that, then set it back, yet viper doesn't seem to be getting used although the driver is installed, where do I select viper as the processor for audio?
Click to expand...
Click to collapse
You don't, I was also looking for that for a while, but PowerAmp picks that up automatically and so I guess the entire OS
Sent from my D5803 using XDA Free mobile app
Dsteppa said:
I was in the same situation as you guys and couldn't live without V4A.
You/we forgot 1 step
You need to set SELinux mode to permissive and then install V4A driver:
Use this simple app:
https://play.google.com/store/apps/details?id=com.mrbimc.selinux
Click to expand...
Click to collapse
any idea what happened that google play store link is no longer valid? shall I chose another one or restore from backup?
ovizii said:
any idea what happened that google play store link is no longer valid? shall I chose another one or restore from backup?
Click to expand...
Click to collapse
Nope, seems like they removed it from the store
I've had a backup with TItaniumBackup but I was just curious what happened there...
Did as Dsteppa sayed. Worked for 10 sec. closed music app and viper and start again. Same thing. Btw I have force enable V4A. Then i went to viper settings and changed FX compatible mode to compatible and restart phone. Works perfectly! Thanks so much!
The solution is disable or froze "Sound Enhancement" app, and that's all, V4A is going to work fine without need of change the option to "Compatible Mode".
iFlasher said:
The solution is disable or froze "Sound Enhancement" app, and that's all, V4A is going to work fine without need of change the option to "Compatible Mode".
Click to expand...
Click to collapse
Thank i try now
MrPingle
Also make sure that Equalizer (in settings, not Viper) is set to Off mode.
I try to install V4A (through Apk) but when i install the drivers, a message says: "Driver install failed: the busybox installation on you device does not work... etc."
I have just installed the last version of busybox in /system/xbin and set Selinux permissive.
How can i resolve it?
I get root with Kingroot e after change binaries to Supersu's binaries.
POST IS UPDATED REGULARLY.
LINK 1 - Parallel Space: https://play.google.com/store/apps/details?id=com.lbe.parallel.intl&hl=en[/URL][/URL]
LINK 2 - Parallel Space 64-Bit Support: https://play.google.com/store/apps/details?id=com.lbe.parallel.intl.arm64&hl=en[/URL][/URL]
Salutations. (That means 'Hello').
NOTE: For those who are interested, I will include background information about how I came to the solution. All that other jazz too. First and foremost however; the fix!
SOLUTION:
Right at the top of the post, you will find two links. This being a new account and all (don't ask), until I create 10 posts I cannot include any outside links. So once I've done so, I will update the post.
STEP **: So at the top of the post, there are clearly two links. 64-Bit Android devices are becoming increasingly common. This architecture may pose a few problems. give the application framework. Should you own a 64-Bit device, I recommend installing this application too (LINK 2). This will theoretically prevent any obstacles.
Pre-requisite(s): Make sure you have the 'Snapchat' application installed. It is recommended to have installed the latest update from the Google Play Store.
STEP ONE: Download the application appended to LINK 1. This is called Parallel Space. You might recognize the name (its creators are the same who allow you to seamlessly virtualize Windows OS on Mac OS).
STEP TWO: Launch the application.
STEP THREE: You should be prompted with a grid-like interface. Here you will be greeted with a range of familiar icons. In the top right corner of each icon, you will notice a blue check-mark. Make sure that there is one next to the 'Snapchat' icon. This will ensure that the app is 'cloned'.
STEP FOUR: In the 'Parallel Space' app, tap on the 'Snapchat' icon. This will launch the application.
STEP FIVE: From here it is pretty self-explanatory. You are greeted by the standard 'Snapchat' interface. Tap on 'Log In'. Then proceed to do so.
STEP SIX: 'Snapchat' should be functioning as normal.
STEP SEVEN (BONUS): During testing, this worked on and off. --
Remain logged-in to the 'cloned' 'Snapchat' application within the 'Parallel Space' application.
Then proceed to launch the stock 'Snapchat' application.
Next attempt to 'Log-In'.
Should this operation be successful, you are then free to uninstall 'Parallel Space' and any related assets from your device.
HOWEVER, I personally do not recommend this. When logging out or updating the 'Snapchat' application, errors may be re-encountered.
Instead, I recommend that if possible, do use the stock application, but leave 'Parallel Space' installed. Using the stock app will improve efficiency and reduce the load on system resources. But keeping the 'Parallel Space' application on the device, well; you get the point.
Enjoy the fix! If it does not work, please let me know [Device Name and Model No.]. I've tested on various devices, succeeded every-time. Do keep in mind that this is a loop-hole, so may be patched in future or not work at all for some devices.
Background (Because I know someone will ask): The idea came to mind while using a LG G5 as a daily driver. I had tested every custom ROM available for the device. The problem was that with custom ROM's, there was always an issue, Malfunctioning sensors, camera's not working persistently, etc , etc.
The G5's stock ROM left me wanting more. The overbearing interface made it a living hell. Plus, the device just being rooted (NO XPOSED) meant that 'Snapchat' did not work. I looked for fixes for a time, but could not find any.
Development of ROM's for the device is on-going, and I am an active member. But I just couldn't handle not being able to use the camera (one of the device's best features) and no accelerator, screen-rotation, etc. So I went back to stock again. Do keep in mind that I was alternating/dual-booting between custom and stock ROM's just because of the camera; mainly.
This most recent time. instead of flashing stock MM, I flashed stock N for the G5. For 850, it has been officially released in some countries, and a manual flash via TWRP was a peice of cake.
This update is a lot better. I am running Nova Launcher again. So it makes it look a little better. Themes have also been improved. I am using an in-built dark one which makes the device look a lot better aesthetically. Additionally, I'm rocking a white carbon-fibre skin on the exterior; improving grip and overall security. The only issue was again, no 'Snapchat'.
After a few days, I had the idea to attempt this. I tested my theory and it worked! That's it.
Please do keep in mind that I will update this post as often as possible.
P.S This was tested just after updating to the latest version of 'Snapchat' which was a significant update. It included Shazam, Groups, etc. So you know, pretty cool that it worked.
Did not work on Google Nexus 5 running Android 7.1.1. Still gives error message saying that I can't connect to the server.
Same here, not working on freshly reinstalled and rooted 7.1.1 Nexus 5x. No Xposed, no nothing. I get the infuriating "temporarily failed" message in both cloned and regular modes.
It didn't worked. S7 edge exynos (6.0.1)
Holyphe said:
It didn't worked. S7 edge exynos (6.0.1)
Click to expand...
Click to collapse
I'm pretty sure if you get Xposed framework, there's a module that allows you to hide root from apps. Problem is that there is no Xposed framework for Android 7 yet. Hope this helps.
hot_potato said:
I'm pretty sure if you get Xposed framework, there's a module that allows you to hide root from apps. Problem is that there is no Xposed framework for Android 7 yet. Hope this helps.
Click to expand...
Click to collapse
Whats the name of it?
Holyphe said:
Whats the name of it?
Click to expand...
Click to collapse
I personally tried the module on cm13 but it doesnt work for me. I think that somehow snapchat knows when you use xposed too.
The thing is that on aosp roms with root already build in sometimes snapchat do not catch it but if you have xposed, no way you can get in. For that freaky snapchat app here is what i did: install any rom, if if had root build in i then install su uninstaller zip with twrp then log in into snapchat and after that, rooting with super su zip again. The catch is that once you log out of the app and attempt to log in again, you cant get in and you have to repeat the proccess. It's annoying as hell!!! They need to disable the security check, if people want to cheat che system somehow they will, so whats the point. Also there are much more tweaks for jailbroken iphones and they have no problem with it .
Sorry for the rant here buqt im super frustrated.
AndroidFL said:
I personally tried the module on cm13 but it doesnt work for me. I think that somehow snapchat knows when you use xposed too.
The thing is that on aosp roms with root already build in sometimes snapchat do not catch it but if you have xposed, no way you can get in. For that freaky snapchat app here is what i did: install any rom, if if had root build in i then install su uninstaller zip with twrp then log in into snapchat and after that, rooting with super su zip again. The catch is that once you log out of the app and attempt to log in again, you cant get in and you have to repeat the proccess. It's annoying as hell!!! They need to disable the security check, if people want to cheat che system somehow they will, so whats the point. Also there are much more tweaks for jailbroken iphones and they have no problem with it .
Sorry for the rant here buqt im super frustrated.
Click to expand...
Click to collapse
That's the only solution I've seen working so far. unroot and reroot. Root cloak doesn't work, parallel doesn't work. I should've logged in before rooting and I hate to do it again.
Any work arounds yet? I've seen ppl do it using titanium backup but I'm not sure if that works. Can anybody help?
Samsung s5 G900v Not working
I have been searching and searching and still haven't found a way to sign into snapcat. It took me about 6 months to be able to find out how to root my phone.
Dukeboyty said:
I have been searching and searching and still haven't found a way to sign into snapcat. It took me about 6 months to be able to find out how to root my phone.
Click to expand...
Click to collapse
Well todays your lucky day.
Step one turn off xposed.
Step two reboot
Step three sign into snapchat
Step four turn xposed back on
Step five reboot
You should be able to snap now.
Okay. I will try this on monday and will let youknow how it goes. Right now I decided to unroot to use snapchat, so I didn't loose my streaks. Thanks in advane will let you know how it goes.
immorality said:
Well todays your lucky day.
Step one turn off xposed.
Step two reboot
Step three sign into snapchat
Step four turn xposed back on
Step five reboot
You should be able to snap now.
Click to expand...
Click to collapse
Now that i think of it, when i uninstalled xposed it didn't work still. but after i "fully unrooted" through Super su and tried to sign in it worked. so it has to do with root or maybe both but the xposed didnt work for me. Thanks even though it didn't/wouldn't have worked for me!
Dukeboyty said:
Now that i think of it, when i uninstalled xposed it didn't work still. but after i "fully unrooted" through Super su and tried to sign in it worked. so it has to do with root or maybe both but the xposed didnt work for me. Thanks even though it didn't/wouldn't have worked for me!
Click to expand...
Click to collapse
Snapchat detects xposed framework.
Though at a time they did do root they since moved to blocking xposed due to the security concerns with money and also privacy of the user.
Though with certain phones and ect that could be the case I am using a s5 and have no issues.
just install magisk and systemless xposed and turn on magisk hide in magisk manager now snapchat won't detect root
then when u wanna log in just turn off xposed in xposed installer and reboot "it won't take time booting optimizing app when reactivated now" so reboot is easy
and u can have multiple accounts by backing up snapchat with titanium backup and don't ever log out just wibe its data and when u want to relog just restore the backup
and if u want to have multiple accounts access just patch the titanium backup with luckypatcher and have multiple backups (accounts)
ahmedsasker said:
just install magisk and systemless xposed and turn on magisk hide in magisk manager now snapchat won't detect root
then when u wanna log in just turn off xposed in xposed installer and reboot "it won't take time booting optimizing app when reactivated now" so reboot is easy
and u can have multiple accounts by backing up snapchat with titanium backup and don't ever log out just wibe its data and when u want to relog just restore the backup
and if u want to have multiple accounts access just patch the titanium backup with luckypatcher and have multiple backups (accounts)
Click to expand...
Click to collapse
Can u make a instructions how to do it step by step? How can i turn off xposed in xposed installer? It also works when SuperSu is installed or i have to unistall it first?
Fnn.09 said:
Can u make a instructions how to do it step by step? How can i turn off xposed in xposed installer? It also works when SuperSu is installed or i have to unistall it first?
Click to expand...
Click to collapse
make a nandroid backup if u want
1- full unroot by opening supersu and going to settings and press Full unroot and wait till it finishes and restart
2- download xposed uninstaller if u have xposed framework installed and flash it
3- install magisk manager from playstore
4- download and flash last magisk which is (12v) now from : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
5- flash magisk v12.0 which you downloaded now your phone will have systemless root
6- go into magisk manager app and go to settings and toggle "Magisk Hide" (ON) and restart now your root is hidden
7- remove your current xposed app and install this one : https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
8- flash systemless xposed : https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
9- reboot and go to the xposed installer app and toggle the xposed off or on as you want when u restart it won't take time optimizing apps like before so fast now
your root is hidden now but xposed is not but you can disable it and enable it easily
Instead of using Parallel Space (which I believe to be insecure) use Island to clone your apps. It's a little more advanced to setup, but it's a lot more secure. It works for rooted and non-rooted devices. On the 1st page of the thread, it explains how Parallel Space and others repack the apk file locally, which is dangerous. https://forum.xda-developers.com/android/apps-games/closed-beta-test-incoming-companion-app-t3366295
Island never repack apk file locally, which is inherently insecure for users, since all your app data (including password input) are technically in the hand of MoboClean. (The same applies to other similar tools, e.g. LBE Parallel Space)
Instead, Island takes advantage of the underlying mechanism used by "Android for Work". This ensures that all your apps run natively in Android system and their data are securely stored in internal location of Android which is never accessible by Island. It has the same level of security as "Android for Work".
Click to expand...
Click to collapse
Be sure to read the disclaimer!!! The app is still only available in closed beta at the time of writing this, and could possibly cause you're device to bootloop or even possibly brick it, but root, xposed, or other modifications {in my opinion) has a higher chance of bootloops or bricking your device.
You follow the same steps in island to clone snapchat as you would in Parallel Space to login to snapchat. It might be possible to use the play store inside island to download snapchat inside island and login that way. I can't remember exactly how it works. I believe that island is a good way to test apps in a "sandbox environment" to keep the data excluded, safe and secure from the regular apps that you have installed outside of island.
I use Magisk now which bypasses SafetyNet which is what snapchat uses to "block access" to modified/rooted devices.
Probably the easiest method is to download Casper which is an alternative snapchat client that allows you to save snaps, and many other features that the official snapchat client can't do. Find Casper at www.casper.io
FYI Netflix has started to change how they do things as well by hiding the app's play store page from devices that have been modified or rooted, but it's still possible to simply sideload Netflix for now.
Device info:
Oneplus 3T, OOS 5.0.1 (Android 8.0), rooted with Magisk v15.3
Recently, my phone has been giving me an error message "Files has stopped " whenever I do anything that requires me to pick a file. and sometimes for no reason. Some examples include selecting a module to install in Magisk Manager, or selecting a file to attach in Gmail.
I highly doubt my root is involved, as I even reflashed the OOS 5.0.1 OTA to try to fix it. I've also tried wiping the cache of the apps File Manager, Files, and all caches in TWRP recovery.
The problem disappears if I reboot into safe mode, meaning it might be due to a rogue app. The problem also seemed to start after I used a USB OTG thumbdrive if it helps, that's the only major thing I remember doing.
Any ideas? Is there any info I can find in logcat to diagnose the problem?
Emeraldscorpion said:
...
I've also tried wiping the cache of the apps File Manager, Files, and all caches in TWRP recovery.
...
Click to expand...
Click to collapse
Try clearing the apps' data in Settings>Apps.
Also, have you installed a theme using Substratum? If so, try disabling it for the File* apps.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
Try clearing the apps' data in Settings>Apps.
Click to expand...
Click to collapse
Yup, already tried clearing data in Settings.
BillGoss said:
Also, have you installed a theme using Substratum? If so, try disabling it for the File* apps.
Click to expand...
Click to collapse
Not using Substratum. I think it's safe to rule out any modifications to /system or any that require root, as the problem persisted even after I reflashed the 5.0.1 OTA.
If you're by chance using Xposed, then Scoop app might be helpful. But if not, you would have to connect your phone to PC, run logcat from there and pause when crash occurs.
With logs it will be easier to debug
przemcio510 said:
If you're by chance using Xposed, then Scoop app might be helpful. But if not, you would have to connect your phone to PC, run logcat from there and pause when crash occurs.
With logs it will be easier to debug
Click to expand...
Click to collapse
I've tried to browse it on-device using the app CatLog, but I have no idea what I'm supposed to be looking for! Any tips on what I should be focusing on?
Emeraldscorpion said:
I've tried to browse it on-device using the app CatLog, but I have no idea what I'm supposed to be looking for! Any tips on what I should be focusing on?
Click to expand...
Click to collapse
Maybe do it another way - start logging in an app, make Files crash and then stop. Paste the log at pastebin.com and link it here, we will see what's wrong
Been MIA due to exams.
I was trying the adb logcat method when I realised that the problem disappeared! Weird. Maybe the app causing it update again. Anyway, thanks for the help!