Error: Requires permission android.permission.WRITE_SECURE_SETTINGS #5

CoderBuck · 2017-04-06T09:33:11Z

XiaoMi4 Android 6.0 MIUI8

$ ./gnirehtet rt
Starting gnirehtet...
'adb' reverse tcp:31416 tcp:31416
'adb' shell am startservice -a com.genymobile.gnirehtet.START
Starting service: Intent { act=com.genymobile.gnirehtet.START }
Error: Requires permission android.permission.WRITE_SECURE_SETTINGS
'java' -jar relay.jar
2017-04-06 17:31:05.886 I Main: Starting server...
Stopping gnirehtet...
'adb' shell am startservice -a com.genymobile.gnirehtet.STOP
Starting service: Intent { act=com.genymobile.gnirehtet.STOP }
Error: Requires permission android.permission.WRITE_SECURE_SETTINGS

[Edit by @rom1v] Solution: #302 (comment)

The text was updated successfully, but these errors were encountered:

rom1v · 2017-04-06T09:38:29Z

Arf, it seems that your shell user does not have this permission… It should have it.

This requirement (a bit hacky) had been introduced by commit e7b8407 (the commit message provides some details).

Does anyone have an idea to get the same "restriction" without the WRITE_SECURE_SETTINGS permission?

yashrajtalan · 2017-04-10T09:19:13Z

Have same issue with Xiaomi Redmi 3S Prime MIUI8 Android 6.0.1
Permissions granted to the app according to the phone are 'full network access' and 'view network connections'.

When I try
adb shell pm grant com.genymobile.gnirehtet android.permission.WRITE_SECURE_SETTINGS
I get
Operation not allowed: java.lang.SecurityException: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.

rom1v · 2017-04-12T14:14:02Z

@CoderBuck @yashrajtalan Could you give the permissions of your Android shell, please?

First, locate Shell.apk:

$ adb shell pm list package -f com.android.shell
package:/system/priv-app/Shell/Shell.apk=com.android.shell

Then pull it:

adb pull /system/priv-app/Shell/Shell.apk

Finally, print its permissions:

aapt d permissions Shell.apk

(aapt is available in $ANDROID_SDK/build-tools/25.0.2/aapt, or there is an aapt package in Debian)

Maybe we could find a better permission which works also for your devices ;-)

CoderBuck · 2017-04-12T14:49:26Z

$ adb shell pm list package -f com.android.shell
package:/system/priv-app/Shell/Shell.apk=com.android.shell

$ adb pull /system/priv-app/Shell/Shell.apk
adb: error: remote object 'D:/Develop/Git/Git/system/priv-app/Shell/Shell.apk' does not exist

CoderBuck · 2017-04-12T15:04:03Z

I am not familiar with this ;-0

rom1v · 2017-04-12T15:13:37Z

@CoderBuck It seems you are using git bash on Windows: http://stackoverflow.com/questions/16344985/how-do-i-pass-an-absolute-path-to-the-adb-command-via-git-bash-for-windows

Try with cmd.exe instead, since git bash mangles pathes at some point.

EDIT: or:

adb pull //system/priv-app/Shell/Shell.apk

CoderBuck · 2017-04-12T15:17:40Z

thanks ;-)

package: com.android.shell
uses-permission: name='android.permission.SEND_SMS'
uses-permission: name='android.permission.CALL_PHONE'
uses-permission: name='android.permission.READ_PHONE_STATE'
uses-permission: name='android.permission.READ_CONTACTS'
uses-permission: name='android.permission.WRITE_CONTACTS'
uses-permission: name='android.permission.READ_CALENDAR'
uses-permission: name='android.permission.WRITE_CALENDAR'
uses-permission: name='android.permission.READ_USER_DICTIONARY'
uses-permission: name='android.permission.WRITE_USER_DICTIONARY'
uses-permission: name='android.permission.ACCESS_FINE_LOCATION'
uses-permission: name='android.permission.ACCESS_COARSE_LOCATION'
uses-permission: name='android.permission.ACCESS_LOCATION_EXTRA_COMMANDS'
uses-permission: name='android.permission.ACCESS_NETWORK_STATE'
uses-permission: name='android.permission.ACCESS_WIFI_STATE'
uses-permission: name='android.permission.BLUETOOTH'
uses-permission: name='android.permission.EXPAND_STATUS_BAR'
uses-permission: name='android.permission.DISABLE_KEYGUARD'
uses-permission: name='android.permission.REAL_GET_TASKS'
uses-permission: name='android.permission.CHANGE_CONFIGURATION'
uses-permission: name='android.permission.REORDER_TASKS'
uses-permission: name='android.permission.SET_ANIMATION_SCALE'
uses-permission: name='android.permission.SET_PREFERRED_APPLICATIONS'
uses-permission: name='android.permission.WRITE_SETTINGS'
uses-permission: name='android.permission.WRITE_SECURE_SETTINGS'
uses-permission: name='android.permission.BROADCAST_STICKY'
uses-permission: name='android.permission.SET_DEBUG_APP'
uses-permission: name='android.permission.SET_PROCESS_LIMIT'
uses-permission: name='android.permission.SET_ALWAYS_FINISH'
uses-permission: name='android.permission.DUMP'
uses-permission: name='android.permission.SIGNAL_PERSISTENT_PROCESSES'
uses-permission: name='android.permission.KILL_BACKGROUND_PROCESSES'
uses-permission: name='android.permission.FORCE_BACK'
uses-permission: name='android.permission.BATTERY_STATS'
uses-permission: name='android.permission.INTERNAL_SYSTEM_WINDOW'
uses-permission: name='android.permission.INJECT_EVENTS'
uses-permission: name='android.permission.RETRIEVE_WINDOW_CONTENT'
uses-permission: name='android.permission.SET_ACTIVITY_WATCHER'
uses-permission: name='android.permission.READ_INPUT_STATE'
uses-permission: name='android.permission.SET_ORIENTATION'
uses-permission: name='android.permission.INSTALL_PACKAGES'
uses-permission: name='android.permission.MOVE_PACKAGE'
uses-permission: name='android.permission.CLEAR_APP_USER_DATA'
uses-permission: name='android.permission.DELETE_CACHE_FILES'
uses-permission: name='android.permission.DELETE_PACKAGES'
uses-permission: name='android.permission.ACCESS_SURFACE_FLINGER'
uses-permission: name='android.permission.READ_FRAME_BUFFER'
uses-permission: name='android.permission.DEVICE_POWER'
uses-permission: name='android.permission.INSTALL_LOCATION_PROVIDER'
uses-permission: name='android.permission.BACKUP'
uses-permission: name='android.permission.FORCE_STOP_PACKAGES'
uses-permission: name='android.permission.STOP_APP_SWITCHES'
uses-permission: name='android.permission.ACCESS_CONTENT_PROVIDERS_EXTERNALLY'
uses-permission: name='android.permission.GRANT_RUNTIME_PERMISSIONS'
uses-permission: name='android.permission.REVOKE_RUNTIME_PERMISSIONS'
uses-permission: name='android.permission.INSTALL_GRANT_RUNTIME_PERMISSIONS'
uses-permission: name='android.permission.SET_KEYBOARD_LAYOUT'
uses-permission: name='android.permission.GET_DETAILED_TASKS'
uses-permission: name='android.permission.SET_SCREEN_COMPATIBILITY'
uses-permission: name='android.permission.READ_EXTERNAL_STORAGE'
uses-permission: name='android.permission.WRITE_EXTERNAL_STORAGE'
uses-permission: name='android.permission.WRITE_MEDIA_STORAGE'
uses-permission: name='android.permission.INTERACT_ACROSS_USERS'
uses-permission: name='android.permission.INTERACT_ACROSS_USERS_FULL'
uses-permission: name='android.permission.CREATE_USERS'
uses-permission: name='android.permission.MANAGE_DEVICE_ADMINS'
uses-permission: name='android.permission.BLUETOOTH_STACK'
uses-permission: name='android.permission.GET_ACCOUNTS'
uses-permission: name='android.permission.RETRIEVE_WINDOW_TOKEN'
uses-permission: name='android.permission.FRAME_STATS'
uses-permission: name='android.permission.BIND_APPWIDGET'
uses-permission: name='android.permission.UPDATE_APP_OPS_STATS'
uses-permission: name='android.permission.MODIFY_APPWIDGET_BIND_PERMISSIONS'
uses-permission: name='android.permission.INSTALL_GRANT_RUNTIME_PERMISSIONS'
uses-permission: name='android.permission.CHANGE_APP_IDLE_STATE'
uses-permission: name='android.permission.MOUNT_UNMOUNT_FILESYSTEMS'
uses-permission: name='android.permission.MOUNT_FORMAT_FILESYSTEMS'
uses-permission: name='android.permission.MODIFY_PHONE_STATE'
uses-permission: name='android.permission.REGISTER_CALL_PROVIDER'
uses-permission: name='android.permission.REGISTER_CONNECTION_MANAGER'
uses-permission: name='android.permission.REGISTER_SIM_SUBSCRIPTION'
uses-permission: name='android.permission.GET_APP_OPS_STATS'

rom1v · 2017-04-12T15:28:05Z

OK so it declares using android.permission.WRITE_SECURE_SETTINGS.

Could you give the result of the following commands, please:

adb shell id
adb shell cat /proc/'$$'/status

EDIT: in fact, these commands will not help.

CoderBuck · 2017-04-12T15:43:20Z

Ok.

adb shell id

* daemon not running. starting it now on port 5037 *
* daemon started successfully *
uid=2000(shell) gid=2000(shell) groups=2000(shell),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0

adb shell cat /proc/'$$'/status

/system/bin/sh: cat: /proc/$$/status: No such file or directory

rom1v · 2017-04-12T15:55:22Z

To summarize:

android.permission.WRITE_SECURE_SETTINGS has protection level "signature"
sending the intent from shell leads to error Requires permission android.permission.WRITE_SECURE_SETTINGS
shell declares using the permission android.permission.WRITE_SECURE_SETTINGS

One possibility is that Shell.apk is not signed with the same signature as the ROM. Which is very strange…

rom1v · 2017-04-12T16:08:06Z

Could you replace android.permission.WRITE_SECURE_SETTINGS by android.permission.WRITE_SETTINGS (a permission with normal protection level) here, build, and try again, please?

If it works, it suggests that the problem is related to Shell.apk signature…

CoderBuck · 2017-04-13T01:45:03Z

error

Error: Requires permission android.permission.WRITE_SETTINGS

rom1v · 2017-04-13T12:48:51Z

So you have a shell with no permissions… Can you find a permission listed from Shell.apk that does work?

rom1v · 2017-04-14T19:42:17Z

What about:

adb shell am startservice -a com.genymobile.gnirehtet.START --user 0
adb shell am startservice -a com.genymobile.gnirehtet.START --user -2
adb shell am startservice -a com.genymobile.gnirehtet.START --user -3

?

rom1v · 2017-04-14T20:30:13Z

The result of this command may also be interesting:

adb shell dumpsys package com.android.shell

rom1v · 2017-04-18T11:45:21Z

@CoderBuck @yashrajtalan Could you please give the result of:

adb shell dumpsys package com.android.shell

And also try these commands.

Thank you :)

yashrajtalan · 2017-04-25T14:20:36Z

The issue seems to be resolved by heading over to Developer Options on MIUI, and enabling the following:
USB debugging -Debug mode when USB is connected
Install via USB -Allow installing apps via USB
USB debugging (Security Settings)- Allow granting permissions and simulating input via USB debugging

The first was already enabled, and I installed the apk file manually so I didn't need the second option.

I'm guessing the issue can be pinned down to the last option, which allows granting the necessary permissions. @CoderBuck please confirm.

Thank you @rom1v for this amazing app. This is a worthy free replacement for ReverseTethering NoRoot.

CoderBuck · 2017-05-01T12:05:10Z

@rom1v @yashrajtalan Sorry to replay late! @yashrajtalan you are right!

thanks a lot!

rom1v · 2017-05-01T12:06:12Z

Great, thank you 👍 So I close the issue.

Biswa96 · 2017-10-28T07:23:37Z

@yashrajtalan Your procedure requires MI account in Xiaomi Redmi phones. You just remove android.permission.WRITE_SECURE_SETTINGS in manifest file (mentioned in #40).

SonalDalal · 2018-10-11T10:48:26Z

@yashrajtalan,
Thanks a lot, your solution worked for me.

rom1v · 2021-10-20T08:06:51Z

Please test enabling "security settings" in developer options: appium/appium#13802 (comment)

Deepjyoti7147 · 2021-10-27T16:36:27Z

Could you replace android.permission.WRITE_SECURE_SETTINGS by android.permission.WRITE_SETTINGS (a permission with normal protection level) here, build, and try again, please?

If it works, it suggests that the problem is related to Shell.apk signature…

I am having similar issues
is there any way I can overwrite the permission?

rom1v · 2021-11-19T08:46:42Z

See #302 (comment)

predi · 2022-10-17T07:23:29Z

On my OnePlus Nord 2T 5G (Android 12, OxygenOS 12.1), I also had to tick Developer options > Disable permission monitoring along with USB Debugging to get past a similar exception.

P.S.: apologies for reviving this old issue.

flocsy · 2023-02-26T11:46:06Z

I had the same problem on OnePlus 8t, and the solution was to go to the Developer Settings on the phone and enable:
Developer Options > Apps > Disable permission monitoring

rezyyyy · 2023-03-10T07:03:58Z

The issue seems to be resolved by heading over to Developer Options on MIUI, and enabling the following: USB debugging -Debug mode when USB is connected Install via USB -Allow installing apps via USB USB debugging (Security Settings)- Allow granting permissions and simulating input via USB debugging

The first was already enabled, and I installed the apk file manually so I didn't need the second option.

I'm guessing the issue can be pinned down to the last option, which allows granting the necessary permissions. @CoderBuck please confirm.

Thank you @rom1v for this amazing app. This is a worthy free replacement for ReverseTethering NoRoot.

turning on the install via usb option requires an internet connection and currently am unable to do that. Is there a way to do this without having to connect to the internet. Note: the option is turned on in the screenshot but it automatically switches off after a couple of seconds..

HoussemNasri · 2023-08-23T21:41:18Z

I had the same problem on OnePlus 8t, and the solution was to go to the Developer Settings on the phone and enable:
Developer Options > Apps > Disable permission monitoring

The same solution worked for Oppo.

maciejkrol18 · 2023-10-07T12:56:10Z

I had the same problem on OnePlus 8t, and the solution was to go to the Developer Settings on the phone and enable:
Developer Options > Apps > Disable permission monitoring

Also works on OnePlus Nord

onyedikachi-david · 2023-12-11T14:23:10Z

I had the same problem on OnePlus 8t, and the solution was to go to the Developer Settings on the phone and enable: Developer Options > Apps > Disable permission monitoring

This solution worked for me. Thanks.
Oppo CPH2269

rom1v closed this as completed May 1, 2017

rom1v mentioned this issue Sep 10, 2017

gnirehtet can not run as service in Android #40

Closed

rom1v mentioned this issue Oct 25, 2017

Permission denied problem on Redmi Note3 Android 6.0.1 #53

Closed

rom1v mentioned this issue Dec 30, 2017

The Android client does not start #65

Closed

rom1v mentioned this issue Jan 31, 2018

MI redmi note3: unable to connect to internet #81

Open

rom1v mentioned this issue Jun 21, 2018

GnirehtetControlReceiver: requires android.permission.WRITE_SECURE_SETTINGS #120

Closed

rom1v mentioned this issue Aug 31, 2018

Cannot start client #140

Closed

rom1v mentioned this issue Dec 14, 2018

Connection request dialog box does not appear (not Asus) #161

Closed

StephanStanisic mentioned this issue Jan 2, 2019

Problems setting android.permission.WRITE_SECURE_SETTINGS on MIUI devices. michaelschattgen/ColorBreeze#2

Open

rom1v mentioned this issue Feb 16, 2021

Unable to work on android 10 #360

Closed

This was referenced Mar 7, 2021

help me please! my cell phone is a redmi note 5 and is giving this error. #367

Closed

android resolution adb #368

Closed

FinlayDaG33k mentioned this issue Mar 21, 2021

Doesn't work with MIUI12 #374

Closed

rom1v mentioned this issue Dec 25, 2021

When I use gnirehtet-autorun to connect normally, calling the adb command will cause the connection to be lost. Is there any way to ensure the connection? #423

Closed

gilbertoca mentioned this issue Apr 11, 2022

os error 13 #417

Open

rom1v mentioned this issue Apr 28, 2022

gnirentet.exe run displays an error and wont open up the connection prompt thing on my phone #437

Closed

rom1v mentioned this issue May 17, 2022

--stay-awake isn't working on Pixel3a (Android 11) Genymobile/scrcpy#2612

Open

2 tasks

rom1v mentioned this issue Jul 4, 2022

Exception occurred while executing start #448

Closed

casper mentioned this issue Sep 25, 2022

Auto-Stop and WiFi-Simulation #328

Open

rom1v mentioned this issue Nov 21, 2022

Can't establish connection #471

Open

rom1v mentioned this issue Mar 9, 2023

How do I fix this Error in running gnirehtet? #485

Closed

rom1v mentioned this issue May 21, 2023

--stay-awake erroring out on console Genymobile/scrcpy#4021

Closed

2 tasks

This was referenced Oct 11, 2023

Android 13 error with stay_on_while_plugged_in Genymobile/scrcpy#4346

Closed

Welp friend, any idea about how to solve it? #511

Open

Trying to make it work in my job's office... #512

Open

rom1v mentioned this issue Jan 10, 2024

anyone knows how to fix this? #525

Open

rom1v mentioned this issue Mar 7, 2024

someone help me fix this issue please where it says error cannot start client #518

Open

pimterry mentioned this issue Mar 7, 2024

[Bug]: Working with real root devices httptoolkit/httptoolkit#556

Closed

1 task

rom1v mentioned this issue Mar 23, 2024

scrcpy --stay-awake Genymobile/scrcpy#4778

Open

2 tasks

rom1v mentioned this issue Mar 31, 2024

gnirehtet cannot start the client issue #532

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error: Requires permission android.permission.WRITE_SECURE_SETTINGS #5

Error: Requires permission android.permission.WRITE_SECURE_SETTINGS #5

CoderBuck commented Apr 6, 2017 •

edited by rom1v

rom1v commented Apr 6, 2017 •

edited

yashrajtalan commented Apr 10, 2017 •

edited

rom1v commented Apr 12, 2017 •

edited

CoderBuck commented Apr 12, 2017 •

edited

CoderBuck commented Apr 12, 2017

rom1v commented Apr 12, 2017 •

edited

CoderBuck commented Apr 12, 2017

rom1v commented Apr 12, 2017 •

edited

CoderBuck commented Apr 12, 2017

rom1v commented Apr 12, 2017

rom1v commented Apr 12, 2017

CoderBuck commented Apr 13, 2017

rom1v commented Apr 13, 2017

rom1v commented Apr 14, 2017

rom1v commented Apr 14, 2017

rom1v commented Apr 18, 2017

yashrajtalan commented Apr 25, 2017

CoderBuck commented May 1, 2017

rom1v commented May 1, 2017

Biswa96 commented Oct 28, 2017

SonalDalal commented Oct 11, 2018

rom1v commented Oct 20, 2021

Deepjyoti7147 commented Oct 27, 2021

rom1v commented Nov 19, 2021

predi commented Oct 17, 2022

flocsy commented Feb 26, 2023

rezyyyy commented Mar 10, 2023

HoussemNasri commented Aug 23, 2023

maciejkrol18 commented Oct 7, 2023 •

edited

onyedikachi-david commented Dec 11, 2023

Error: Requires permission android.permission.WRITE_SECURE_SETTINGS #5

Error: Requires permission android.permission.WRITE_SECURE_SETTINGS #5

Comments

CoderBuck commented Apr 6, 2017 • edited by rom1v

rom1v commented Apr 6, 2017 • edited

yashrajtalan commented Apr 10, 2017 • edited

rom1v commented Apr 12, 2017 • edited

CoderBuck commented Apr 12, 2017 • edited

CoderBuck commented Apr 12, 2017

rom1v commented Apr 12, 2017 • edited

CoderBuck commented Apr 12, 2017

rom1v commented Apr 12, 2017 • edited

CoderBuck commented Apr 12, 2017

rom1v commented Apr 12, 2017

rom1v commented Apr 12, 2017

CoderBuck commented Apr 13, 2017

rom1v commented Apr 13, 2017

rom1v commented Apr 14, 2017

rom1v commented Apr 14, 2017

rom1v commented Apr 18, 2017

yashrajtalan commented Apr 25, 2017

CoderBuck commented May 1, 2017

rom1v commented May 1, 2017

Biswa96 commented Oct 28, 2017

SonalDalal commented Oct 11, 2018

rom1v commented Oct 20, 2021

Deepjyoti7147 commented Oct 27, 2021

rom1v commented Nov 19, 2021

predi commented Oct 17, 2022

flocsy commented Feb 26, 2023

rezyyyy commented Mar 10, 2023

HoussemNasri commented Aug 23, 2023

maciejkrol18 commented Oct 7, 2023 • edited

onyedikachi-david commented Dec 11, 2023

CoderBuck commented Apr 6, 2017 •

edited by rom1v

rom1v commented Apr 6, 2017 •

edited

yashrajtalan commented Apr 10, 2017 •

edited

rom1v commented Apr 12, 2017 •

edited

CoderBuck commented Apr 12, 2017 •

edited

rom1v commented Apr 12, 2017 •

edited

rom1v commented Apr 12, 2017 •

edited

maciejkrol18 commented Oct 7, 2023 •

edited