I cannot get su file manager working with superuser permissions. When I try to start it up I get taken to q black screen with "SU request" at the top, but no options to do anything from that point on. No buttons work and I'm just stuck looking at that blank black screen.
I tried opening up superuser permission alone (with su fm closed) to see if I could whitelist su fm, but I get to the same screen with no options.
What am I doing wrong here?
Turn USB Debugging Mode on in Application settings.
Worked a charm, thanks
Related
I have a phone that came pre-installed with su, busybox and superuser; but the permissions are not set correctly for the user to access su and get root. The phone is running Android 1.6 and when you connect it to a computer in debug mode it is not recognized as an Android device; even though the phone says it is plugged into a computer and in debug mode. The only thing that comes up is the drive to access the SD card. My question is thus: Is there any way to change the permissions of su on the device itself? I have tried running a terminal emulator but when I type "su" the result is permission denied. Since I don't have permissions I cannot do a chmod on the device itself. If anyone knows a method I can do this I would appreciate it very much.
Edit: I've researched my options more fully and now have a much more detailed problem. See Below
Okay,
So I've smashed my display into little bits, but the phone still works. Has power, receives calls and texts, but cannot be controlled due to the broken screen.
I'm trying to get access to the file system and my contacts, but its proving to be quite difficult without use of the screen.
I've had partial luck so far using Droid Explorer. When I connect with Droid Explorer and boot into recovery, I am able to view my file system but unable to copy any files to my PC.
When I access the phone in non-recovery mode, I am unable to view the file system but am able to use the Screencast feature to display my home screen. I am NOT able to control the screen through screen cast, however.
I believe (but may be wrong) that I am unable to do backup my files or command the phone due to a lack of Superuser rights to ADB, thus I only have read-only access and not read-write. Is there any way to restore these privileges through the command prompt?
I tried following a video on using Droid Explorer to command the phone, but I get held up at the chmod 777 /data/dalvik-cache command as I do not have access to makes changes that system, due to (I think) never granting SU to ADB while my phone had a working screen.
I am running the latest Madhi ROM along with AK Kernel and SuperSU 2.16. I am having an issue where the root prompt is not being shown. I have uninstalled and reinstalled SuperSU and initially the grant root privileges prompt is shown for some apps that require root. However, if I reboot or wait a period of time and then check for root, the prompt is not being displayed. If I uninstall/reinstall SuperSU the same process holds true - prompt initially shown, then after a little while the prompt will not be shown (for new apps requiring root and/or root checker).
If I go into SuperSU and change the settings to "Grant" rather than "Prompt" all the apps are granted Root Privileges. Almost like something is blocking the prompts from being displayed.
Thanks.
I have a rooted s6 edge, I used cf's auto root method, however my phone is not encrypting properly (let it run for 4 hours last night before interrupting process) Will the s6 not encrypt if rooted, or if knox has been broken? Any advice on how to resolve this?
try a different method like rooting apk
i know i'm late but here's the fix:
1. The latest busybox needs to be installed.
2. After enabling USB Debugging on your phone, you need to go to adb shell on your PC and type su for root access . Accept the root permission request on your phone. You will then see in adb that the $ will turn into #
3. Type following command: pkill -KILL daemonsu
This will temporarily disable supersu/root. (You see that the # will turn back into $. Also you'll see your apps won't be able to gain root access). After encrypting your phone will be automatically rooted again.
4. Do NOT open SuperSu afterwards or reboot. Just start with encryption.
Just an extra note, since I ran into this.
The issue is that the encryption process tries to unmount /data, but doesn't know about the dameonsu process which has one or more files open. The unmount fails and the encryption hangs. The only way out is a hard reboot (hold power + volume down) and a factory reset.
Once you kill the daemon, be sure to exit adb as that will also hold /data mounted.
If it just shows a lock and the word "Encrypting" but no other activity, it's stuck and you'll have to reset it. If it works, it will reboot to the Verizon screen then show a % complete screen.
How to remove SuperSU on unrooted phone? - "there is no SU binary installed..."
Hi,
I lost some SMS data. I tired to use data recovery software. One of the programs was Fonepaw. Apparently fonepaw tried to root my device and failed; or did something else. Yet, somehow fonepaw installed SuperSU as a system application. This is causing problems with the device, a Galaxy S5 (SM-G900V) running Android 6.0.1.
When I run the SuperSU application it reports:
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
My only option is to select 'OK'. Which closes the app.
SuperSU won't uninstall via application manager due to being a system application.
The "adb backup" command no longer works since my attempts at using Fonepaw and a few other applications.
ADB see's my device via "adb devices". I can explore directories. If I enter "adb shell su" I get "[email protected]:/ #".
But when I try to run "adb backup" the phone doesn't go into the prompt where you say 'okay' and set a password. Adb backup has worked just fine in the past. It's been useful, and I need to use it again as part of changing to a new phone.
Android also is showing in notification a "Security notice" stating "Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes."
Restarting does nothing. Even booting to safe mode doesn't stop the security notice. SuperSU being a system app runs in safe mode.
Root Checker app comfirms the phone isn't rooted.
I have never attempted to root the phone and have been the only owner/operator.
I would like to uninstall the SuperSU application and any data it stored on the phone without losing any data on the phone. Since the phone is not rooted and no SuperSU binary was installed, I'm hoping this is possible.
My search for information has provided limited insight.
I'm hoping someone on XDA might know what to do.
Edit: Additional info.
https://android.stackexchange.com/questions/103611/remove-su-after-unroot
I do the following:
"[email protected]:/ # cd system/xbin"
"[email protected]:/systems/xbin # ls"
output:
"Dexdump
dexdump
jack_connect
jack_disconnect
jack_lsp
jack_showtime
jack_simple_client
jack_transport
jackc
su"
The commenter at stack exchange would suggest the phone I have has root, but root check says otherwise.
Another edit:
I'm not sure, but it looks like a Custom Recovery was installed on the phone. Unsure if that's what came with phone or not, vol down+home+power brings me to a screen without the "Android" icon/statute/person thingy. Same for booting into vol up+home+power. However, in the recovery I get 'reboot to bootloader' and when I select that I go to stock android download mode/odin mode. And when I boot the system, boot/splash screen "Samsung Galaxy S5" on top, a lock icon that is unlocked with "Custom" in the middle, and "powered by Android" at the bottom.
command "adb root" returns "adbd is already running as root".
So, I'm not sure what's going on here. Found a post stating you can have adb root without root in androids system. So...I'm a noob at all this. *CONFUSED*. Hoping for someone to help.
Fonepaw support has not been helpful at all.