I tried to run a command via Android terminal, but when I execute my command:
"svc data enable/disable" this error appears:
"Warning: l
Relocations error is caused by the fact that xposed framework replaces genuine app_process with a custom one, which is somehow unoptimized as it has been built to work on every modern (well, almost every...) android device/system. After uninstalling/reverting to stock (thru xposed installer or by flashing uninstall zip created on sdcard during installation) you'll find out that the warning is gone (as well as all xposed related customizations). If ur writing a script and don't want to see the warning, just forward the error output somewhere else than STDERR, i.e: svc data enable 2>/dev/null
Permission denied for svc data enable...? seems uncasual, as it shall retry in 1sec intervals even if failed (displaying appropriate output). Didn't have htc ever, so dunno if it may be somehow protected by them... HOWEVER, android terminal which is quite limited in many situations manages to print permission denied error if it did not find something at all (instead of ie. "not found"). Here however, as u have 4.4.2 it's more likely selinux context issue preventing something to be done, it happens often when modding, usually not resulting in any issues (and sometimes resulting with a bootloop). You may try: su mount -o rw,remount /system restorecon -Rv /system
(-R only for non-verbose/silent mode) It's a one time operation, persistent until messing with files again. Try the command after that (dunno if reboot is needed).
PS: it is a risky operation, do a nand backup of /system before and restore if bootlooped (and dont blame me) PS2: it shall NOT set su binary context as it will be busy (as u r running a root shell atm), displaying warning. That's not an issue. In fact it's perfect! Changing su context will result in losing root privileges (seems that stock config forces context PREVENTING root usability - at least samsung one...). It MAY happen, thou, that u will lost root, that is why i highly recommend to keep recent supersu flashable zip nearby, on sdcard for example, and flash it with recovery if needed. SuperSU installer sets the appropriate context for installed files with chcon and root will be back again. PS3: do not run that within custom recovery (twrp console/aroma terminal), context config provided by its dev may be differ than the device's stock and may cause trouble. Use adb or terminal after booting with android kernel.
The text relocations is a warning, not an error. It was only added to Android comparatively recently.
As it appears that the program in question (app_process) was one furnished with the system rather than compiled by you, there is nothing you can or need to do about it, unless you feel like rebuilding/replacing the system component in question.
Were you building your own program, your question could be marked as a duplicate of
mylib.so has text relocations. This is wasting memory and is a security risk. Please fix
However, that would only apply to software you were compiling yourself.
In this case, you will probably just have to ignore it, unless you are somehow (?) using app_process
to launch something with a custom native library that you did build, in which case you should update your NDK as explained in the other question.
Your permissions denied
is unrelated to the previous error message, and most likely a problem with the command you are trying to run (for example, you think you are root but you are not). If you want help with that, you are going to have to be more specific about the command you are running and the mechanism used to launch it.
I faced same error:
WARNING: linker: libvc1dec_sa.ca7.so has text relocations. This is wasting memory and is a security risk. Please fix.
WARNING: linker: libvc1dec_sa.ca7.so has text relocations. This is wasting memory and is a security risk. Please fix.
pkg: /data/local/tmp/com.example.ashv.takeinput
Failure [INSTALL_FAILED_INVALID_APK]*
This error started after I rooted my android mobile. In order to un-root my mobile, I messed up with its Firmware. Therefore, I had to take Service Center help and they formatted and re-installed Kitkat. After which it works fine.