Fix for QMI_ERR_ACCESS_DENIED
Re: Fix for QMI_ERR_ACCESS_DENIED
I received the log, it will take a bit to investigate.
Re: Fix for QMI_ERR_ACCESS_DENIED
Are the sent logs sufficient to analyze?
Any progress?
Rsap is the only thing that stops me to move to new phone...
Any progress?
Rsap is the only thing that stops me to move to new phone...
Re: Fix for QMI_ERR_ACCESS_DENIED
Hi,
New installer do his job!
rSAP files installed successfully in the phone.
but sometimes I noticed, Connection to socket failed..
Any advise with that?
edit:
Reinstalled app - confirmed another question to root access, maybe there was a problem.
Will see.
New installer do his job!
rSAP files installed successfully in the phone.
but sometimes I noticed, Connection to socket failed..
Any advise with that?
edit:
Reinstalled app - confirmed another question to root access, maybe there was a problem.
Will see.
Re: Fix for QMI_ERR_ACCESS_DENIED
The socket connection problem is caused by SELinux and the fact that I now additionally open a socket in the new installer app. There seem to be only a few sockets available with enforced SELinux, maybe some party is not allowed to properly close it? I don't know... I'll have to do more research what can be done about this. A reboot should always help.
In normal operation this should not be an issue because the rSAP app opens a socket and never closes it (at least that's the plan).
In normal operation this should not be an issue because the rSAP app opens a socket and never closes it (at least that's the plan).
-
- Posts: 2
- Joined: Wed Feb 12, 2014 10:17 pm
Re: Fix for QMI_ERR_ACCESS_DENIED
Hi, is there any progress with this bug?
I've a One Plus One (bacon) with LineageOS14.1 and rsap isn't working.
I get the QMI_ERR_ACCESS_DENIED error. In rsap installer app too.
I've attached a screenshot.
I've a One Plus One (bacon) with LineageOS14.1 and rsap isn't working.
I get the QMI_ERR_ACCESS_DENIED error. In rsap installer app too.
I've attached a screenshot.
- Attachments
-
- Screenshot_20170414-182224.png (99.76 KiB) Viewed 50368 times
Re: Fix for QMI_ERR_ACCESS_DENIED
See here: http://www.android-rsap.com/enable-qual ... ccess.html
Special link to XDA for the OPO
Special link to XDA for the OPO
Re: Fix for QMI_ERR_ACCESS_DENIED
Hi all,
I have rooted Xiaomi Redmi 4X with ROM from http://www.miuios.cz - MUII8.6/Android: 7.1.2.
After installation of necessary system files with app V3.05 I got QMI_ERR_ACCESS_DENIED.
I tried copy sap_security_restrictions file with EFS Explorer. Before it I set phone in Set Factory Test Mode with QXDM. But still unable write sap_security_restrictions to /nv/item_files/modem/qmi/uim...
Any idea how to write sap_security_restrictions to my phone?
PS: i tried it with QPST 2.7.460 and QXDM 3.14.1144
I have rooted Xiaomi Redmi 4X with ROM from http://www.miuios.cz - MUII8.6/Android: 7.1.2.
After installation of necessary system files with app V3.05 I got QMI_ERR_ACCESS_DENIED.
I tried copy sap_security_restrictions file with EFS Explorer. Before it I set phone in Set Factory Test Mode with QXDM. But still unable write sap_security_restrictions to /nv/item_files/modem/qmi/uim...
Any idea how to write sap_security_restrictions to my phone?
PS: i tried it with QPST 2.7.460 and QXDM 3.14.1144
Re: Fix for QMI_ERR_ACCESS_DENIED
Same issue. Stuck at "sap_security_restrictions" copy using EFS Explorer. 
EFS Explorer crashes during copy of file.
Nevertheless, I noticed that I can copy the file to any other directory, and can copy this specific file into /nv/item_files/modem/qmi/uim if I change the name, i.e., "sap_security_restriction" or "sap_security_restrictions1". Seems to be that this name is forbidden to be written at this directory.
Any ideas how to solve this?

EFS Explorer crashes during copy of file.
Nevertheless, I noticed that I can copy the file to any other directory, and can copy this specific file into /nv/item_files/modem/qmi/uim if I change the name, i.e., "sap_security_restriction" or "sap_security_restrictions1". Seems to be that this name is forbidden to be written at this directory.
Any ideas how to solve this?
Re: Fix for QMI_ERR_ACCESS_DENIED
The crash is a bug in EFS Explorer. It doesn't handle the internal error return from the copy operation correctly. The internal error is a security error i.e. it is not allowed to create the file, although I don't understand why you can create files with a different name. So far the only way to allow access is the activation of the "Factory Test Mode". I don't have any further information.