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.
Related
Hi all,
I'm trying hard to bypass the 'no sim card' locked screen that I am currently getting on my G1 Android Dev Phone 1 RC29 that I recently installed DREAIMG.nbh on. Ideally, I would like to run the android scripting environment on my phone with wireless access.
So far, my primary document that I've used to consult this matter has been this one from JesusFreke: forum.xda-developers.com/showthread.php?t=452316.
The first thing the document suggests is, "to connect to your phone with adb shell and get root access, and then type the following command:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO system (name, value) VALUES ('device_provisioned', 1);"
When I run this command, I get a 'sqlite3: permission denied' error (see below).
3.bp.blogspot.com/_scN4BTBqXiY/S-dOBTo8LiI/AAAAAAAAAfU/rtmnXywBPzI/s1600/sqlite3+permission+denied1.jpg
I recognize now that the assumption with this command is that your phone is running on RC30, as the article notes. Mine is running on RC29. In order to make this command functional, it appears as though I need to ADB push the busybox binary.
As you can see in the image above, I was able to successfully adb push the busybox binary to the /data/local of the G1.
Furthermore, I ran the wireless command in step two of the above tutorial just to see what would happen and I get this message:
3.bp.blogspot.com/_scN4BTBqXiY/S-dMU3sO2-I/AAAAAAAAAfM/Z9r_glscNvU/s1600/Wireless.jpg
With all of this being said, however, I still can't seem to bypass my original screen that says 'No Sim Card'
3.bp.blogspot.com/_scN4BTBqXiY/S-dLhIjpQ7I/AAAAAAAAAfE/JkbHfOgW3f0/s1600/DSCN5623.JPG
If someone out there knows that is going on that I should change, please let me know, because I am really running into a dead end here.
Thank you very much!
I don't remember if RC29 has this, but in the initial setup wizard you should be able to press the menu key and access a wireless setup utility to connect to wifi.
Also, after you wipe and flash (or turn the phone on the first time), and if you get the "touch the android to begin" screen you can touch each of the 4 corners of the black background in a clockwise pattern starting in the upper left to go to the home screen.
That sqlite3 command needs to be run in a root shell. Make sure you're root. The $ prompt is the regular phone user. The root prompt will be # instead. Try running "su" after connecting with "adb shell" to become root. Is the rom you're using rooted?
I've just rooted my Nexus 5 but when I open apps like Superuser it displays the following issues (see attached files). I verified my root status with the Root Checker App as well and it shows roughly the same problem. I've have attached some screenshots. I'm sorry but my language is Italian.
How did you root it ?
Perhaps you missed something
SimoPiersi said:
I've just rooted my Nexus 5 but when I open apps like Superuser it displays the following issues (see attached files). I verified my root status with the Root Checker App as well and it shows roughly the same problem. I've have attached some screenshots. I'm sorry but my language is Italian.
Click to expand...
Click to collapse
I hate Superuser personaly and would advice you to unroot and uninstall the superuser app and flash the superSU.zip 1.94 in recovery. Link http://download.chainfire.eu/supersu.
Charlus97 said:
How did you root it ?
Perhaps you missed something
Click to expand...
Click to collapse
I don't like at all that in stock android you have only a certain number of toggles, so I've searched the web in order to find a way to add more of them. I've found first the Cyanogenmod, then the Xposed Framework. I've read that I have to root my device to do that, so I've searched the web again in order to find the easiest way to root it without strange methods. I've found a post in the CM forum which explained to me how to root my Nexus 5 with terminal commands, so I followed it.
I can't post links yet, so here's the content of the CM forum page:
Configure your computer for fastboot.
Enable USB debugging on the device.
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
$ adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation for more info.
If you see "no permissions fastboot", try running fastboot as root.
From the same terminal, type the following command to unlock the bootloader:
$ fastboot oem unlock
A disclaimer will display on the device that must be accepted. Use the volume keys to cycle through the options. Pressing the power button should confirm your selection.
If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked. You can confirm this is the case if you see an unlocked icon at the bottom of the Google boot screen during reboots.
Since the device resets completely, you will need to re-enable USB debugging on the device to continue.
Hi,
I am looking for some help as I did something stupid...
I came across some posting that explained that the moto has an unused partition under /cache that could be used for the dalvik-cache.
So I tried to move the dalvik-cache there and link /data/dalvik-cache to this new location.
Now the problem is that I get an "unfortunately the location-service has stopped" message all the time that makes the device unusuable (as soon as I press ok the same warning appears again).
When I try to boot into recovery I get a "dead android robot".
I can however access the device via adb, unfortunately I am not able to get a root shell. My device is rooted, but su in an adb-shell just hangs.
If I could only get a root-shell I could undo my changes and hopefully my device will work again, but I have to idea on what to try...
Can anone help me here?
morgonhed said:
Hi,
I am looking for some help as I did something stupid...
I came across some posting that explained that the moto has an unused partition under /cache that could be used for the dalvik-cache.
So I tried to move the dalvik-cache there and link /data/dalvik-cache to this new location.
Now the problem is that I get an "unfortunately the location-service has stopped" message all the time that makes the device unusuable (as soon as I press ok the same warning appears again).
When I try to boot into recovery I get a "dead android robot".
I can however access the device via adb, unfortunately I am not able to get a root shell. My device is rooted, but su in an adb-shell just hangs.
If I could only get a root-shell I could undo my changes and hopefully my device will work again, but I have to idea on what to try...
Can anone help me here?
Click to expand...
Click to collapse
The dead android bot is normal for stock recovery, if you didn't install a custom one. You can always flash a custom recovery using fastboot, and wipe the dalvik-cache and regular caches. Or, in the "dead android bot" screen, you can press the Vol+ key for about 15 secs, then tap the Power button, then scroll using the Vol buttons to something that says wipe cache. You might have to wipe dalvik-cache as well, if you can. I forget where the options are, since I haven't used the stock recovery in so long, sorry!
Ok, I managed to get beyond the "dead android" and from the menu I did a "wipe cache parition". That ran for some minutes, then it rebooted.
But after that I still have the same problem. The continuous "unfortunately the location-service has stopped" messages still persist.
Any other ideas?
Do you have an unlocked bootloader? If you do, the simplest solution may be to flash back to a stock ROM.
audit13 said:
Do you have an unlocked bootloader? If you do, the simplest solution may be to flash back to a stock ROM.
Click to expand...
Click to collapse
Yes my bootloader is unlocked. But I don't want to loose too much...
I believe the problem is only a permission-problem in my new /cache/dalvik-cache directory (/data/dalvik-cache now links there).
So all I would need is a way to get a root-shell (the device is rooted).
I can do a "adb shell" as normal user but that does not have the permissions to even look into /cache and for whatever reason when I type "su" I don't get an error nor do I become root but the command simply hangs...
The system as such still seems to work, e.g. my Moto still connects to my hotspot and I can ping it from there.
The even seems to be an "adb root" command, but that does not work on my adb. Is there a version of adb somewhere that would honor adb root?
Anyone with another idea on how to get a root-shell in my situation
Sorry, I don't know enough about adb commands to change the directory back to the default.
I assume you have usb debugging enabled and your computer is a trusted machine?
USB debugging is definitely enabled, whether or not I've set up my PC as trusted I don't remember.
If I didn't could that explain why I can get a shell but not as root or would you without a trusted computer not even get a shell?
Ok, issue resolved.
I've flashed clockworkmod recovery and cleared the dalvik-cache with that. That did the trick.
And moving my 300MB dalivk-cache to /cache seems to have worked and frees up memory for me, even better.
Finally the reason I could not get root in the adb shell was that when I type su in the adb-shell a superuser-request pops up on the phone that you have to acknowlege. But with constant warnings poping up I did not even see that...
Thanks for all support.
For the Developer options, look under Root access. Did you grant root access to ADB and apps?
When you type su, look at the phone's screen. Are you prompted to grant root access to ADB?
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.
MTK ADB gets you a privileged shell at the push of a button, allowing you to run commands directly on your MediaTek device. Some might wonder if rooting hasn't already solved this. Firstly, root access is persisted by modifying system files. When the real binary gets substituted by that of the root app's, if the device is rebooted, the init daemon running as root runs the binary giving the app root. What's wrong with this? If you have “purist” tendencies, you probably would want your phone as stock as possible, or at least with your permission. Sadly, not only binaries are dumped. Extra temp files, logs and helper binaries too, that manually removing them is like dancing on floor of pins and a prick means a brick. Not only that, consider yourself blocked from updates. If you're unfortunate enough, an update could result in bricking your phone as the files supposed to be present had been changed. This is more common than you think. MTK ADB makes no changes to your files whatsoever. Also, there's the matter of security/privacy. Root apps tend to always do something in the background. Either sneaking in a new app, or phoning home with your private data, or both. MTK ADB doesn't steal your data. The Internet permission is for Telnet, etc. On some devices, MTK ADB can get root access (depending on manufacturer) while all devices can get shell access. You just have to check which yours belongs.
IMPORTANT
•Refresh before (and after) clicking Start to check ADB status.
•Supports all ADB functionality. Just run "adb <command>" eg "adb pull" (without quotes).
•The minimalist terminal is for those who haven't any. Feel free to use your regular terminal (I use Terminal IDE) and keyboard (Hacker's Keyboard is really good). Just run "adb shell" on it.
•You can connect to your device using another phone, PC, or anything with a terminal and in the same network by running "adb connect IP_address".
•If you get a " device offline" error, disable and enable USB debugging. Next time connect to the network before running the app.
http://www.youtube.com/watch?v=_bt8BVaDCf0
http://slaycode.WordPress.com
Bump
Proof:
http://forum.xda-developers.com/gen...iled-error-t3191150/post62611445#post62611445
More Proof:
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546/page10
Proof:
http://forum.xda-developers.com/gen...iled-error-t3191150/post62611445#post62611445
More Proof:
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546/page10
When I open the app it opens but it doesn't work when I enter the commands and moreover the app when I try to start the adb it says unsupported device
Am using infinix hot 4 pro running NOUGAT xos 2.2
LordFME said:
MTK ADB gets you a privileged shell at the push of a button, allowing you to run commands directly on your MediaTek device. Some might wonder if rooting hasn't already solved this. Firstly, root access is persisted by modifying system files. When the real binary gets substituted by that of the root app's, if the device is rebooted, the init daemon running as root runs the binary giving the app root. What's wrong with this? If you have “purist” tendencies, you probably would want your phone as stock as possible, or at least with your permission. Sadly, not only binaries are dumped. Extra temp files, logs and helper binaries too, that manually removing them is like dancing on floor of pins and a prick means a brick. Not only that, consider yourself blocked from updates. If you're unfortunate enough, an update could result in bricking your phone as the files supposed to be present had been changed. This is more common than you think. MTK ADB makes no changes to your files whatsoever. Also, there's the matter of security/privacy. Root apps tend to always do something in the background. Either sneaking in a new app, or phoning home with your private data, or both. MTK ADB doesn't steal your data. The Internet permission is for Telnet, etc. On some devices, MTK ADB can get root access (depending on manufacturer) while all devices can get shell access. You just have to check which yours belongs.
IMPORTANT
•Refresh before (and after) clicking Start to check ADB status.
•Supports all ADB functionality. Just run "adb <command>" eg "adb pull" (without quotes).
•The minimalist terminal is for those who haven't any. Feel free to use your regular terminal (I use Terminal IDE) and keyboard (Hacker's Keyboard is really good). Just run "adb shell" on it.
•You can connect to your device using another phone, PC, or anything with a terminal and in the same network by running "adb connect IP_address".
•If you get a " device offline" error, disable and enable USB debugging. Next time connect to the network before running the app.
http://slaycode.WordPress.com
Click to expand...
Click to collapse
Are you familiar with an APK that utilizes mtk_bypass to directly flash firmware to device.
I'm looking for an APK that basically does what sp flash tool does because I don't have a computer.