34

enter image description here

How can I overcome this problem?

Devices:

  1. Samsung Galaxy TabS - Android 4.4.2

  2. HTC M8 - Android 5.0.1

The two devices have the same problem.

Improve this question
4
  • 11
    Are the devices rooted? su binary doesn't come with factory shipped devices. You need to root the device (which involves finding and pushing the su binary into /system/bin/ or /system/xbin/). See What is rooting? Commented Nov 3, 2015 at 12:14
  • no roots in the device. Is this procedure is not done without roots? Commented Nov 3, 2015 at 12:23
  • 3
    The procedure I told you is part of rooting. In order to switch to UID 0 (the userId of root user) you need access to su and in order to access su it has to be present first. How would you move the binary depends upon the device you're using. Some methods are mentioned here: How do I root my Android device? Commented Nov 3, 2015 at 12:26
  • Had the same issue after deleting my "device" which Visual Studio 2017 created and made a new one. Solution was to make sure to leave "GooglePlayStore" ticked off. Commented Mar 30, 2019 at 15:40

2 Answers 2

Reset to default
13

Your device is not rooted. To see what Rooting is and how to go about doing it:

Once you have rooted your device, you will be able to access the Super User state of your device (SU). Just be aware that rooting could brick your device if done incorrectly, as could tampering with files in the root directory.

Improve this answer
0
1

This also happened to me.

I use Infinity X (the GApps Variant) and have it rooted with KernelSU.

When running adb shell and su, I have the same error.

The solution is very simple:

  • Open KernelSU,
  • Switch to the Super user tab,
  • Find Shell (the one with com.android.shell),
  • And grant it Super user priviledge.
Improve this answer

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.