Adb permission denied error

On a recent attempt to pull a realm database file created by an application that I built on my device, I got an error with the following message:

$ adb pull /data/data/com.example.test/files/default.realm .
adb: error: failed to stat remote object '/data/data/com.example.test/files/default.realm': Permission denied

Let’s see how we can solve this!

TLDR

Long story short, you can run the following command from the Terminal to create a copy of the file in your machine’s file system:

adb shell "run-as om.example.test cat /data/data/com.example.test/files/default.realm" > default.realm

This only works for Debug builds and not for a production app.

But let’s break it down to pieces!

Explanation

You can use adb shell to connect to the device’s shell. Then, if you want to access the data of an app with an applicationId set to com.example.test, you will have to run the command run-as com.example.test inside the adb shell.

Once you execute this command, the working directory will change to the /data/data/com.example.test. From there, you can use commands like ls to get a list of the available directories and cat to get the content of a specific file.

The last step (> default.realm) is to redirect the content of the file to a file on my machine’s file system.

And that’s it! Now you will be able to copy the file from a device for an application that you have built without any error!

9 ответов

adb root                     - restarts the adbd daemon with root permissions

root access is disabled by system setting - enable in settings -> development options

Android permission doesn’t work even if I have declared it

I’m trying to write code to send an SMS from an Android app, but when I try to send the SMS it sends me back the error:

I checked but I have the permissions in the manifest, as follows:

I searched the internet but all the errors were about the syntax, could you help me please?

11 Answers 11

The big reason for not getting your permission nowadays is because your project has a targetSdkVersion of 23 or higher, and the permission that you are requesting is «dangerous». In Android 6.0, this includes:

• ACCEPT_HANDOVER
• ACCESS_BACKGROUND_LOCATION
• ACCESS_MEDIA_LOCATION
• ACTIVITY_RECOGNITION
• ANSWER_PHONE_CALLS
• ACCESS_COARSE_LOCATION
• ACCESS_FINE_LOCATION
• ADD_VOICEMAIL
• BODY_SENSORS
• CALL_PHONE
• CAMERA
• GET_ACCOUNTS
• PROCESS_OUTGOING_CALLS
• READ_CALENDAR
• READ_CALL_LOG
• READ_CELL_BROADCASTS
• READ_CONTACTS
• READ_EXTERNAL_STORAGE
• READ_PHONE_STATE
• READ_SMS
• RECEIVE_MMS
• RECEIVE_SMS
• RECEIVE_WAP_PUSH
• RECORD_AUDIO
• SEND_SMS
• USE_SIP
• WRITE_CALENDAR
• WRITE_CALL_LOG
• WRITE_CONTACTS
• WRITE_EXTERNAL_STORAGE

For these permissions, not only does your targetSdkVersion 23+ app need to have the element(s), but you also have to ask for those permissions at runtime from the user on Android 6.0+ devices, using methods like checkSelfPermission() and requestPermissions() .

As a temporary workaround, drop your targetSdkVersion below 23.

However, eventually, you will have some reason to want your targetSdkVersion to be 23 or higher. At that time, you will need to adjust your app to use the new runtime permission system. The Android documentation has a page dedicated to this topic.

Источник

Android can’t open file, FileNotFoundException(Permission denied), but PermissionRead is granted [duplicate]

Android can’t open file with FileNotFoundException(Permission denied), but PermissionRead is granted.

java.io.FileNotFoundException: /mnt/obb/»file detailed path»: open failed: EACCES (Permission denied)

obb file is ERROR_ALREADY_MOUNTED.

PermissionRead is granted.

Android OS ver.6.0 device.

3 Answers 3

Try to give runtime permission

have you implemented runtime permission?, first you grant manually storage permission from settings and check exception occur or not, if not then you have mistake in permission implementation.

Thank you for answers.

This is a very strange phenomenon. Once, I was able to fix it to work properly.

Conclusion: Solution

Create an obb file with jobb command with the same name as renamed on Google Play side.

That is. Before the fix was done like this.(example)

And if you upload «main1.obb» to Google Play, «main.1.com.test.testapp.obb» will be downloaded along with apk download.

But this is not good.

After the correction, it was programmed like this.

Why: Reasons to fix

I thought that there was a problem with obb mount when the following error occurred:

So I tried to unmount obb after the error. Then an error came back.

If I try to unmount an already mounted obb, it is a permission error. This is strange.

As I looked it up on the Internet, the problem is obb filename made with the jobb command? Or package name? It was said that it occurred.

Therefore, I changed the obb file name generated by the jobb command. There is no problem with this. Of course, «READ_EXTERNAL_STORAGE» has always acquired.

I did not understand anything more. Just the application is working correctly.

Источник

Android: adb: Permission Denied

Whatever I type after adb shell it fails with Permission denied :

10 Answers 10

According to adb help :

Which indeed resolved the issue for me.

Without rooting: If you can’t root your phone, use the run-as

command to be able to access data of your application.

$ adb exec-out run-as com.yourcompany.app ls -R /data/data/com.yourcompany.app/

exec-out executes the command without starting a shell and mangling the output.

The reason for «permission denied» is because your Android machine has not been correctly rooted. Did you see $ after you started adb shell ? If you correctly rooted your machine, you would have seen # instead.

If you see the $ , try entering Super User mode by typing su . If Root is enabled, you will see the # — without asking for password.

You might need to activate adb root from the developer settings menu. If you run adb root from the cmd line you can get:

Once you activate the root option (ADB only or Apps and ADB) adb will restart and you will be able to use root from the cmd line.

None of the previous solutions worked for me but I was able to make it work using this command

The data partition is not accessible for non-root users, if you want to access it you must root your phone.

ADB root does not work for all product and depend on phone build type.

in the new version of android studio, you can explore /data/data path for debuggable apps.

update 2022

Android Studio new versions have some tools like Device Explorer and App Inspection to access application data. (app must be debuggable).

Источник

Android Studio error 13=permission denied in linux

i am using android studio latest version in linux(elementary luna to be specific). I installed jdk, android studio and sdk successfully, android studio opens us perfectly and even i can work on my app. but when i bulid app it gives error 13: permission denied and it opens a black circle image png in new tab.

i dont understand the problem. i did searched on internet and tried many methods like

changing permissions with chmod:

chmod +x /home/alex/android-studio/sdk/build-tools/android-4.2.2/dx

it executes successfully but with no effect on the problem itself,

2.closing and re-importing project,

3.i also tried this,

and i get following result

i guess this is not issue since my system is 32 bit and this is for 64 bit systems.

Can anyone help? since i am really counting on it.

my system configurations:(if useful)

-OS Version: 0.2.1 «Luna» ( 32-bit ), Built on: Ubuntu 12.04 ( «Precise» )

-installed OpenJdk 7: java version «1.6.0_34» OpenJDK Runtime Environment (IcedTea6 1.13.6) (6b34-1.13.6-1ubuntu0.12.04.1)

OpenJDK Client VM (build 23.25-b01, mixed mode, sharing)

14 Answers 14

I’m running android studio 1.0.2 on ubuntu 14.04 (LTS) 32 bit and i had the same problem. just go to «/home/suUs12/Android/Sdk/build-tools/21.1.2/» and then right click on ‘aapt‘ file , properties -> permissions and check ‘Allow executing file as program‘. then close the window.

In my case,after giving permission for ‘aapt‘ file, I had to give the same permission for ‘dx‘ and ‘zipalign‘ files in the same directory (/home/suUs12/Android/Sdk/build-tools/21.1.2/) and I was able to run my first app using android studio.

Give Root permission to your android studio by using

chmod -777 YourAndroidStudioFolder

This problem is about insufficient authority. If you change your user as ‘root’ and you open android studio, this problem will be resolved. For ex;

[enter your password] : ********

$ cd /home/username/. /android-studio/bin

If this can help, I solved after giving full execution permissions ( chmod a+x ) to all executables in /opt/android-bundle/sdk/build-tools/$VERSION/ ( aapt , dx and zipalign ).

The permissions problem with file not found with aapt wasn’t with this file itself but with the *.so files it tries to use. The first thing to do which I didn’t at first was run the following sudo yum install zlib.i686 ncurses-libs.i686 bzip2-libs.i686 to get the necessary 32 bit *.so files installed. I found out about the missing *.so files by running aapt outside the studio. I also found there were a number of files that were read or read write only that needed to be executable in these directories. android-studio/bin android-studio/jre/bin android-studio/jre/jre/bin android-studio/gradle/gradle-2.14.1/bin

The fsnotifier files and the 2 *.sh file in the first bin directory. All the files in the two jre directories and the gradle file in the last directory needed to be chmod 755. After I did that I no longer get the pop up box about the fsnotifier and the gradle build doesn’t get the permission error. Running as root doesn’t help when the problem is with files not being executable.

I Solved This Problem By : Right Click On Main Folder Like Android-Studio and then Go to Properties and then Click On Permission and check CheckBox For Allow Executing File As a Program Then Run Android Studio In Terminal 🙂

Remove the build tool and re download it fixes my problem.

just reinstall the build tool version and then go into folder where sdk is installed and in build tool version’s «aapt» file and change permissions from «property» all to read and write and check mark to «Allow executing file as a program» and then close it. same problem is solved by doing this.

You can reinstall androidstudio in /opt/ folder.This is a shared folder.I refer to official web’s vedio on how to install androidstudio and solve the problem.I almost tried every way on the internet,but it didn’t work.In fact,this is just a question about permission.

In my case the partition in which I saved the Sdk was mounted with the defaults option in /etc/fstab, which in turn enabled the default noexec option which forbids execution for all files in that partition.

Then I edited that line in fstab appending exec, resulting in the options list ‘user,defaults,exec’ for that partition.

Источник

SecurityException: Permission denied (missing INTERNET permission?)

this error is really really really strange and I don’t know how to reproduce it and how to fix it because I made a lot of searches but nothing was useful.

Here’s the stacktrace:

Here’s my AndroidManifest.xml

Please don’t bother asking me if I have the correct INTERNET permission in my manifest because this app is in market since 2 years 😛

I’ve also noticed that (from Crittercism) all bugs are coming from Android 4.1.x version (JB). I don’t know if device are rooted or what (I can’t see this information for the moment)

13 Answers 13

NOTE: I wrote this answer in Jun 2013, so it’s bit dated nowadays. Many things changed in Android platform since version 6 (Marshmallow, released late 2015), making the whole problem more/less obsolete. However I believe this post can still be worth reading as general problem analysis approach example.

Exception you are getting ( SecurityException: Permission denied (missing INTERNET permission?) ), clearly indicates that you are not allowed to do networking. That’s pretty indisputable fact. But how can this happen? Usually it’s either due to missing entry in your AndroidManifest.xml file or, as internet permission is granted at installation not at run time, by long standing, missed bug in Android framework that causes your app to be successfully installed, but without expected permission grant.

My Manifest is correct, so how can this happen?

Theoretically, presence of uses-permission in Manifest perfectly fulfills the requirement and from developer standpoint is all that’s needed to be done to be able to do networking. Moreover, since permissions are shown to the user during installation, the fact your app ended installed on user’s device means s/he granted what you asked for (otherwise installation is cancelled), so assumption that if your code is executed then all requested permissions are granted is valid. And once granted, user cannot revoke the permission other way than uninstalling the app completely as standard Android framework (from AOSP) offers no such feature at the moment.

But things are getting more tricky if you also do not mind your app running on rooted devices too. There’re tools available in Google Play your users can install to control permission granted to installed apps at run-time — for example: Permissions Denied and others. This can also be done with CyanogenMod, vendor brand (i.e. LG’s) or other custom ROM, featuring various type of «privacy managers» or similar tools.

So if app is blocked either way, it’s basically blocked intentionally by the user and if so, it is really more user problem in this case (or s/he do not understand what certain options/tools really do and what would be the consequences) than yours, because standard SDK (and most apps are written with that SDK in mind) simply does not behave that way. So I strongly doubt this problem occurs on «standard», non-rooted device with stock (or vendor like Samsung, HTC, Sony etc) ROM.

I do not want to crash.

Properly implemented permission management and/org blocking must deal with the fact that most apps may not be ready for the situation where access to certain features is both granted and not accessible at the same time, as this is kind of contradiction where app uses manifest to request access at install time. Access control done right should must make all things work as before, and still limit usability using techniques in scope of expected behavior of the feature. For example, when certain permission is granted (i.e. GPS, Internet access) such feature can be made available from the app/user perspective (i.e. you can turn GPS on. or try to connect), the altered implementation can provide no real data — i.e. GPS can always return no coordinates, like when you are indoor or have no satellite «fix». Internet access can be granted as before, but you can make no successful connection as there’s no data coverage or routing. Such scenarios should be expected in normal usage as well, therefore it should be handled by the apps already. As this simply can happen during normal every day usage, any crash in such situation should be most likely be related to application bugs.

We lack too much information about the environment on which this problem occurs to diagnose problem w/o guessing, but as kind of solution, you may consider using setDefaultUncaughtExceptionHandler() to catch such unexpected exceptions in future and i.e. simply show user detailed information what permission your app needs instead of just crashing. Please note that using this will most likely conflict with tools like Crittercism, ACRA and others, so be careful if you use any of these.

Notes

Please be aware that android.permission.INTERNET is not the only networking related permission you may need to declare in manifest in attempt to successfully do networking. Having INTERNET permission granted simply allows applications to open network sockets (which is basically fundamental requirement to do any network data transfer). But in case your network stack/library would like to get information about networks as well, then you will also need android.permission.ACCESS_NETWORK_STATE in your Manifest (which is i.e. required by HttpUrlConnection client (see tutorial).

Addendum (2015-07-16)

Please note that Android 6 (aka Marshmallow) introduced completely new permission management mechanism called Runtime Permissions. It gives user more control on what permission are granted (also allows selective grant) or lets one revoke already granted permissions w/o need to app removal:

This [. ] introduces a new permissions model, where users can now directly manage app permissions at runtime. This model gives users improved visibility and control over permissions, while streamlining the installation and auto-update processes for app developers. Users can grant or revoke permissions individually for installed apps.

However, the changes do not affect INTERNET or ACCESS_NETWORK_STATE permissions, which are considered «Normal» permissions. The user does not need to explicitly grant these permission.

See behavior changes description page for details and make sure your app will behave correctly on newer systems too. It’s is especially important when your project set targetSdk to at least 23 as then you must support new permissions model (detailed documentation). If you are not ready, ensure you keep targetSdk to at most 22 as this ensures even new Android will use old permission system when your app is installed.

Источник