"As part of the Android security model, Android uses Security-Enhanced Linux (SELinux) to enforce Mandatory Access Control (MAC) over all processes, even processes running with root/superuser privileges (a.k.a. Linux capabilities). SELinux can operate in one of two global modes: permissive mode, in which permission denials are logged but not enforced, and enforcing mode, in which permission denials are both logged and enforced." Read more here...
Requirements:
- Rooted Device
- Root/FS/ES Explorer
- busybox & init.d support
Click to expand...
Click to collapse
How to:
- Add the 01selinux script to /system/etc/init.d
- Set file permissions to 0755 (rwx r-x r-x)
- Power off, wait for a few seconds & power on
Click to expand...
Click to collapse
If you'd like to add this script to your ROM, just copy 01selinux script to /system/etc/init.d !
Downloads:
[08/21/2014] Permissive SELinux v1.0: 01selinux
Click to expand...
Click to collapse
Status:
- Fully working on NC4 Kernel - Verizon Samsung Galaxy Note 3 (N900V)
- Not working on NCG/NE9 Kernel - Verizon Samsung Galaxy S5 (G900V)
Click to expand...
Click to collapse
Thanks to @Misterxtc for making all S5 testing.
If you've any question, you may contact him.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It didn't work for me. I set permissions to 755, rebooted and it still says enforcing.
Misterxtc said:
It didn't work for me. I set permissions to 755, rebooted and it still says enforcing.
Click to expand...
Click to collapse
It should be 775.
Have you tested init.d before? Check if it created an SELINUX log file on /data. If not, test init.d support!
hsbadr said:
It should be 775.
Have you tested init.d before? Check if it created an SELINUX log file on /data. If not, test init.d support!
Click to expand...
Click to collapse
The log says Permissive SELinux by @hsbadr but in about phone and running the getenforce command in terminal mode it says enforcing. Yes, I have init.d support. Permissions are 775.
Misterxtc said:
The log says Permissive SELinux by @hsbadr but in about phone and running the getenforce command in terminal mode it says enforcing. Yes, I have init.d support. Permissions are 775.
Click to expand...
Click to collapse
Do you've any other init.d scripts? Try to rename it 99selinux & report me!
hsbadr said:
Do you've any other init.d scripts? Try to rename it 99selinux & report me!
Click to expand...
Click to collapse
Still dind't work renaming it. I have 99SuperSUDaemon and 00ARCHOID_INITD in the init.d directory also.
Misterxtc said:
Still dind't work renaming it. I have 99SuperSUDaemon and 00ARCHOID_INITD in the init.d directory also.
Click to expand...
Click to collapse
I've just tested it on NC4 kernel (Note 3) & it works,
Unfortunately, I don't have S5 device for now !
hsbadr said:
I've just tested it on NC4 kernel (Note 3) & it works,
Unfortunately, I don't have S5 device for now !
Click to expand...
Click to collapse
I'll have to try this on the NCG kernel it may be blocked on NE9. I'll report back in a few.
Misterxtc said:
I'll have to try this on the NCG kernel it may be blocked on NE9. I'll report back in a few.
Click to expand...
Click to collapse
Thanks @Misterxtc! Yes, test it on NCG kernel & maybe another ROM if you can.
Update: Compare the following values in your build.prop:
Code:
ro.build.selinux=1
ro.kernel.qemu=0
ro.kernel.android.checkjni=0
ro.config.tima=0
ro.config.timaversion=3.0
ro.config.knox=0
it doesnt work for me either on my ne9 rom. although it also didnt create a log under /data either
Sent from my SM-G900V using XDA Free mobile app
---------- Post added at 08:01 AM ---------- Previous post was at 08:00 AM ----------
shouldnt perms be set same as other scripts in init.d folder?
Sent from my SM-G900V using XDA Free mobile app
elliwigy said:
it doesnt work for me either on my ne9 rom. although it also didnt create a log under /data either
Click to expand...
Click to collapse
If it didn't create /data/SELinux.log, your init.d doesn't work. Try a simple init.d test & it'll fail too!
hsbadr said:
If it didn't create /data/SELinux.log, your init.d doesn't work. Try a simple init.d test & it'll fail too!
Click to expand...
Click to collapse
so i had in wrong folder lol. moved to system/etc/init.d tried perms 0775 and 0755.. i have log file now but still says enforcing..
Sent from my SM-G900V using XDA Free mobile app
---------- Post added at 08:12 AM ---------- Previous post was at 08:12 AM ----------
elliwigy said:
so i had in wrong folder lol. moved to system/etc/init.d tried perms 0775 and 0755.. i have log file now but still says enforcing..
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
also tried renaming it to 99 as suggested
Sent from my SM-G900V using XDA Free mobile app
elliwigy said:
so i had in wrong folder lol. moved to system/etc/init.d tried perms 0775 and 0755.. i have log file now but still says enforcing..
Click to expand...
Click to collapse
It should be 0775; Compare the following values in your build.prop:
Code:
ro.build.selinux=1
ro.kernel.qemu=0
ro.kernel.android.checkjni=0
ro.config.tima=0
ro.config.timaversion=3.0
ro.config.knox=0
Power off, wait for a few seconds & power on!
hsbadr said:
It should be 0775; Compare the following values in your build.prop:
Code:
ro.build.selinux=1
ro.kernel.qemu=0
ro.kernel.android.checkjni=0
ro.config.tima=0
ro.config.timaversion=3.0
ro.config.knox=0
Power off, wait for a few seconds & power on!
Click to expand...
Click to collapse
i have init.d.. i tested it and also tried universal init.d with no luck ill compare build.prop now
Sent from my SM-G900V using XDA Free mobile app
elliwigy said:
i have init.d.. i tested it and also tried universal init.d with no luck ill compare build.prop now
Click to expand...
Click to collapse
Also, test the following commands in shell/terminal emulator & report me back:
Code:
getenforce
setenforce 0
getenforce
hsbadr said:
Also, test the following commands in shell/terminal emulator & report me back:
Code:
getenforce
setenforce 0
getenforce
Click to expand...
Click to collapse
I tried the build.prop and it didn't work. I'm doing a full tar install of NCG right now because my NCG backup failed and locked my phone. I'll try it again after I'm done restoring the phone.
Misterxtc said:
I tried the build.prop and it didn't work. I'm doing a full tar install of NCG right now because my NCG backup failed and locked my phone. I'll try it again after I'm done restoring the phone.
Click to expand...
Click to collapse
Great! Consider all troubleshooting options here including terminal commands. I know you've had a Note 3 & NC4 kernel caused many problems because of the Enforcing SELinux. My ROM is running now on NC4 kernel using this script.
i chqnged build.prop to match as well as tried the term emu and still enforcing..
Sent from my SM-G900V using XDA Free mobile app
elliwigy said:
i chqnged build.prop to match as well as tried the term emu and still enforcing..
Click to expand...
Click to collapse
Thanks! This is very weird In terminal, you wrote setenforce 0 & this didn't change it to Permissive lol Please try it again with su!
hsbadr said:
Thanks! This is very weird In terminal, you wrote setenforce 0 & this didn't change it to Permissive lol Please try it again with su!
Click to expand...
Click to collapse
i did in bottom screen but tried again... also selinux changer didnt work either to change it lol
Sent from my SM-G900V using XDA Free mobile app
Related
Hey :good:
I patched Teamviewer Quick Support APK (originally for Samsung ROMs) and signed it with Cyanogenmod platform keys.
Runs flawlessly on my SGS i9000 running CM9!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download (CWM flashable ZIP)
* Remember, you need at least 4+ MB of free space on /system to flash those ZIPs!
v7.0.719 ARMv7: http://d-h.st/BAF
Getting FC (force close) when app starts? Try this ARMv7 ZIP!
v7.0.719 ARMv6: http://d-h.st/NpF
Older builds: here
How-to patch it yourself
http://forum.xda-developers.com/showpost.php?p=32375573&postcount=187
Enjoy!
Why not sign it with your own key like a regular app dev so everyone can use it?
bradgog said:
Why not sign it with your own key like a regular app dev so everyone can use it?
Click to expand...
Click to collapse
Because this app requires some permissions that are granted only to applications that are signed with the same key as the platform (ROM).
What you're asking is impossible unfortunately.
"signature" A permission that the system grants only if the requesting application is signed with the same certificate as the application that declared the permission. If the certificates match, the system automatically grants the permission without notifying the user or asking for the user's explicit approval.
Click to expand...
Click to collapse
http://developer.android.com/guide/topics/manifest/permission-element.html
That being the case can you sign it with the platform key that Pete Alfonso is using on Bugless Beast?
theos0o said:
Because this app requires some permissions that are granted only to applications that are signed with the same key as the platform (ROM).
What you're asking is impossible unfortunately.
http://developer.android.com/guide/topics/manifest/permission-element.html
Click to expand...
Click to collapse
bradgog said:
That being the case can you sign it with the platform key that Pete Alfonso is using on Bugless Beast?
Click to expand...
Click to collapse
Did you try it and it's not working?
Keys look the same as CM
https://github.com/peteralfonso/platform_build/tree/jb/target/product/security
OP updated with ARMv6 flashable ZIP
thanks a lot!
works great with CM10 on my SGSII.
I am glad I can use this app now
hey i downloaded the zip to my galaxy tab (i know this is the sgs iii forum) and renamed the extension to apk, but i cant install it, the apk seems to be invalid. i am running cm10 do they not share the same signature?
edit: wait, those are cwm flashable?
Localhorst86 said:
hey i downloaded the zip to my galaxy tab (i know this is the sgs iii forum) and renamed the extension to apk, but i cant install it, the apk seems to be invalid. i am running cm10 do they not share the same signature?
edit: wait, those are cwm flashable?
Click to expand...
Click to collapse
Yep, CWM flashable.
And this is the general Android section not the GS3 one
Yeah, i just realized. Unfortunatelly it wont work on my gtab. The app fcs on launch (armv7 binary)
Sent from my GT-P7510 using xda app-developers app
Localhorst86 said:
Yeah, i just realized. Unfortunatelly it wont work on my gtab. The app fcs on launch (armv7 binary)
Sent from my GT-P7510 using xda app-developers app
Click to expand...
Click to collapse
If you can get & upload a logcat of the FC, I will check it tomorrow
Will do so when i am at home
Sent from my GT-P7510 using xda app-developers app
---------- Post added at 10:47 PM ---------- Previous post was at 09:59 PM ----------
here's the logcat.
uname -a
Linux localhost 2.6.36.4-cyanogenmod+ #1 SMP PREEMPT Mon Aug 13 09:42:21 EDT 2012 armv7l GNU/Linux
mine crashed too, usiing CM7. logcat:
https://www.box.com/shared/57f6353adde0bb2733ad
oh one more thing: the app FCs when someone has connected... they can see me for one sec, then the app crashes
EDIT: nevermind, i forgot to fix the libs permissions... ii didn't flash the zip, i extracted and copied, then changed permissions, but i miissed one .so file
———————————————————
i didn't mean to mock you or to offend you in any kind of way
The apk block JB rom, this is possible to modify too?
Ty.
i tried both versions and on my computer is coming out a black screen any ideas?
SGS II CM 10 Working!
Thanks!
Localhorst86 said:
Will do so when i am at home
Sent from my GT-P7510 using xda app-developers app
---------- Post added at 10:47 PM ---------- Previous post was at 09:59 PM ----------
here's the logcat.
uname -a
Linux localhost 2.6.36.4-cyanogenmod+ #1 SMP PREEMPT Mon Aug 13 09:42:21 EDT 2012 armv7l GNU/Linux
Click to expand...
Click to collapse
could not load needed library 'libsurfaceflinger_client.so' for 'libjniscreenshot23.so'
Maybe you should get a copy of libsurfaceflinger_client.so and push it to /system/lib ?
Ask your ROM dev for more info.
---------------------------------------------------
For those of you who get the firmware incompatible message, ROM name / link please.
If we can get your ROM's platform keys, we can fix it.
theos0o said:
could not load needed library 'libsurfaceflinger_client.so' for 'libjniscreenshot23.so'
Maybe you should get a copy of libsurfaceflinger_client.so and push it to /system/lib ?
Ask your ROM dev for more info.
Click to expand...
Click to collapse
Grabbed that lib (from goo.im), dropped it to system/lib, and changed the permissions, the app still crashes.
Sent from my GT-P7510 using xda app-developers app
Localhorst86 said:
Grabbed that lib (from goo.im), dropped it to system/lib, and changed the permissions, the app still crashes.
Sent from my GT-P7510 using xda app-developers app
Click to expand...
Click to collapse
extract the lib from the zip file from OP... and do the ssame thing.
i didn't flash the zip, i exctracted it and copied each file and changed the permissions
———————————————————
i didn't mean to mock you or to offend you in any kind of way
Riro Zizo said:
extract the lib from the zip file from OP... and do the ssame thing.
i didn't flash the zip, i exctracted it and copied each file and changed the permissions
———————————————————
i didn't mean to mock you or to offend you in any kind of way
Click to expand...
Click to collapse
hm... the libsurfaceflinger_client.so lib is not in that zipfile. Can you upload yours?
Localhorst86 said:
Grabbed that lib (from goo.im), dropped it to system/lib, and changed the permissions, the app still crashes.
Sent from my GT-P7510 using xda app-developers app
Click to expand...
Click to collapse
Looks like that lib you got is not compatible..
Here's mine from CM9, I don't think it'll work but try it.
http://www.mediafire.com/download.php?5c4u3qt33jb0a5o
Definite speed and smoothness engine for sgy! copy this in your init.d folder
(delete any other script that you have)
this is SmokingHAL_V2.2
lol no other info... just some scripts i made for my rom and i some Others that are deleted(geeky,modified by me)
solves also the wakelock/reboot issue on merruk kernel
Hacked and cleaned the scripts, and made them cmw flashable. Be sure to delete ANY OTHER SCRIPTS IN INIT.D FOLDER
you really won't believe at the phone reactivity and smoothness.
BEWARE V2 might affect battery life, testers advised.
sireangelus said:
Definite speed and smoothness engine for sgy! copy this in your init.d folder
http://www.mediafire.com/?buyy95vg89jexsd(Delete any other script that you have)
Click to expand...
Click to collapse
More info...?
sireangelus said:
Definite speed and smoothness engine for sgy! copy this in your init.d folder
http://www.mediafire.com/?buyy95vg89jexsd(Delete any other script that you have)
Click to expand...
Click to collapse
damn!
Sent from my Android System using Busybox Commands.
sireangelus said:
Definite speed and smoothness engine for sgy! copy this in your init.d folder
http://www.mediafire.com/?buyy95vg89jexs (delete any other script that you have)
lol no other info... just some scripts i made for my rom and i some Others that are deleted(geeky,modified by me)
solves also the wakelock/reboot issue on merruk kernel
Click to expand...
Click to collapse
does it really fix reboots and delay wake up
really?
what is wakelock?
yabyuh22 said:
what is wakelock?
Click to expand...
Click to collapse
Wakelock 1= when you press the button and screen have some delay to turn on
Wakelock 2= Some Cases an specific app dont give permission to phone enter in deep sleep mode
Anyone tested it? How is it going??
---------- Post added at 05:25 PM ---------- Previous post was at 05:15 PM ----------
WTH!Am I the only one seeing that whenever I click the link it opens just mediafire.com??? Are you referring??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EliTSamsunG said:
Wakelock 1= when you press the button and screen have some delay to turn on
Wakelock 2= Some Cases an specific app dont give permission to phone enter in deep sleep mode
Click to expand...
Click to collapse
ohh!!! thanks sir..:victory: i have that issue but i have built in scripts in buildprop
amanbhalla04 said:
Anyone tested it? How is it going??
---------- Post added at 05:25 PM ---------- Previous post was at 05:15 PM ----------
WTH!Am I the only one seeing that whenever I click the link it opens just mediafire.com??? Are you referring??
Click to expand...
Click to collapse
try this http://www.mediafire.com/?buyy95vg89jexsd
old old old old reserved
up for new version in first post.
Link is broken sir
Sent from my GT-S5360 using xda premium
vanhalen35 said:
Link is broken sir
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
fixed
is true to fix restarting problem of merruk ?
yes it does. also DELETES lag and everything runs at an idiotic smoothness(you can see it even when battery is charging.. it's like the system as a whole produces frames at a higher rate, even if top performance as a whole don't change) , at the price of having the cpu unable to scale in frequency between deepsleep and max freq..(if you force the cpu to a lower freq BAD thing happens.) and it does not affect governors but this trick uses 3 lines of code.
Thanks, hmm how to install this? flash via cwm? or flash via odin? or manually push to init.d folder?
rmhoh said:
Thanks, hmm how to install this? flash via cwm? or flash via odin? or manually push to init.d folder?
Click to expand...
Click to collapse
delete all init.d files.then you can install it through cwm. should even work with stock recovery
sireangelus said:
delete all init.d files.then you can install it through cwm. should even work with stock recovery
Click to expand...
Click to collapse
I am In Hyperion Latest Build.It has pre-installed tweaks.So Should I delete them and then flash these scripts or just remove them temporary and then after flashing paste it in directory.Will it Conflict?
this script is very interdependent from one and another and also it has some special tweaks that might get overwritten. so i raccomand to delete them.store them if you want to test the results before doing anything
like seriously? no test and no reports?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Before we can take a bite on the new KitKat, some of us may encounter the set_metadata.. error at flashing.
Problem:
The new updater-scritpt use set_metadata and set_metadata_recursive to assign the permissions to the newly copied files.
Most of the existing /system partition doesn't support the "capabilities" option. Script in android/build would assign 0x00 to "capabilities".
However, assigning a "capabilities" with 0x00 to the unsuported partition also cause error!
If you are lucky, you might find an updated custom recovery to solve that.
For those who don't have a workable recovey or don't want to update the recovery yet. Here is a solution
Solution:
I patched the script when building my 4.4 rom for GT-7.7. The included "update-binary" would solve that problem at flashing.
Open the zip of the ROM or gapps. Replace the file in /META-INF/com/google/android with this one.
Now you can flash the 4.4 rom and gapps without an recovery update..
It works for cm11 & aosp based ROMs and gapps.
Cheers!
Edit:
Silly me, how can it be hardware independent... This one is compiled for armv7. Different cpu surely need a recompile.
Here is the change in the source: http://forum.xda-developers.com/showpost.php?p=47692333&postcount=15
Thanks dude
Sent from my LG-P500 using xda premium
Thanks daniel_hk
It works fine on my SGS :good:
@daniel_hk
Thanks for this. But it does not work for my armv6 device (lg p500). Could you please tell us what you changed, so that it can be "ported" to older devices. I have read that some recoveries have merged changes to source, but these devices do not yet have a ported version. So if you have time, this would be much appreciated by my device community.
Sent from my LG-P500 using Tapatalk 2
ibub said:
@daniel_hk
Thanks for this. But it does not work for my armv6 device (lg p500). Could you please tell us what you changed, so that it can be "ported" to older devices. I have read that some recoveries have merged changes to source, but these devices do not yet have a ported version. So if you have time, this would be much appreciated by my device community.
Sent from my LG-P500 using Tapatalk 2
Click to expand...
Click to collapse
The theory of what I have done is already mentioned in the thread.
In details, I changed the file in the source of the recovery. The update-binary is generated there.
In the function ApplyParsedPerms, when encounter a 0x0 for "capabilities", I drop the flag .
The attached file was from the rom I built.
For ROMs using the CyanogenMod cm-11 or AOSP 4.4 source, it should work.
Send me the link of your ROM which fail. Let me take a look.
Thank you so much. But I may have spoken too soon. I found an updated recovery (4.3), and new update binary for my phone. I will try it later to see if it works, before asking you to waste your time.
Sent from my LG-P500 using Tapatalk 2
Ok, I tried but had no success. So here is a link to the rom:
http://jenkins.androidarmv6.org/job/submission-test/755/
Again, thanks.
Sent from my LG-P500 using Tapatalk 2
ibub said:
Ok, I tried but had no success. So here is a link to the rom:
http://jenkins.androidarmv6.org/job/submission-test/755/
Again, thanks.
Sent from my LG-P500 using Tapatalk 2
Click to expand...
Click to collapse
Is your error "set_metadata_recursive"... "fail"? Can you list the exact messages at flash. Take a photo to avoid typing.
I think you might get an assert error not set_metadata related
Yeah, it's set_metadata_recursive error or fail. I think my recovery will copy messages to SD. Will record soon. The devs for this device are now trying to add set_metadata tags in boardconfig.mk, and then use set metadata =false. But I'm not really sure if that would be an actual fix, or just a temporary work around to get it to flash. So I'd rather try to do it your way. Just wish my 32-bit system would compile newer Android.
Sent from my LG-P500 using Tapatalk 2
---------- Post added at 06:37 AM ---------- Previous post was at 06:06 AM ----------
Ok, here's my recovery log.
Sent from my LG-P500 using Tapatalk 2
---------- Post added at 06:38 AM ---------- Previous post was at 06:37 AM ----------
http://www.mediafire.com/view/?dddwi6vtbo3a1fg
Sent from my LG-P500 using Tapatalk 2
ibub said:
Yeah, it's set_metadata_recursive error or fail. I think my recovery will copy messages to SD. Will record soon. The devs for this device are now trying to add set_metadata tags in boardconfig.mk, and then use set metadata =false. But I'm not really sure if that would be an actual fix, or just a temporary work around to get it to flash. So I'd rather try to do it your way. Just wish my 32-bit system would compile newer Android.
Sent from my LG-P500 using Tapatalk 2
---------- Post added at 06:37 AM ---------- Previous post was at 06:06 AM ----------
Ok, here's my recovery log.
Sent from my LG-P500 using Tapatalk 2
---------- Post added at 06:38 AM ---------- Previous post was at 06:37 AM ----------
http://www.mediafire.com/view/?dddwi6vtbo3a1fg
Sent from my LG-P500 using Tapatalk 2
Click to expand...
Click to collapse
in line 1260:
-> ApplyParsedPerms: removexattr of /system/xbin/su to 0 failed: Operation not supported on transport endpoint
seems the file system doesn't support XATTR, remove a non exsist attr probably cause error.
Did the log come from my update-binary?
If so, you need to tell the rom developer to check the kernel source:
if the kernel support selinux and file system is EXT, you need the following
CONFIG_EXT4_FS_XATTR=y
or
CONFIG_EXT3_FS_XATTR=y
Either one must be enabled dependent on the file system.
If kernel doesn't support selinux, disable it.
For YAFFS, there might be similar config for kernel need to enable or disable
Good luck!
daniel_hk said:
in line 1260:
-> ApplyParsedPerms: removexattr of /system/xbin/su to 0 failed: Operation not supported on transport endpoint
seems the file system doesn't support XATTR, remove a non exsist attr probably cause error.
Did the log come from my update-binary?
If so, you need to tell the rom developer to check the kernel source:
if the kernel support selinux and file system is EXT, you need the following
CONFIG_EXT4_FS_XATTR=y
or
CONFIG_EXT3_FS_XATTR=y
Either one must be enabled dependent on the file system.
If kernel doesn't support selinux, disable it.
For YAFFS, there might be similar config for kernel need to enable or disable
Good luck!
Click to expand...
Click to collapse
No, that was the original update binary, built with the rom. I don't know for certain, but have read that the binary is specific to the chipset. Anyway, I'm gonna search through the commits to see if the xattr has been used. Remember seeing it... somewhere. Again thanks.
Sent from my LG-P500 using Tapatalk 2
ibub said:
No, that was the original update binary, built with the rom. I don't know for certain, but have read that the binary is specific to the chipset. Anyway, I'm gonna search through the commits to see if the xattr has been used. Remember seeing it... somewhere. Again thanks.
Sent from my LG-P500 using Tapatalk 2
Click to expand...
Click to collapse
I think you haven't try my update-binary. I don't know why you said it fail?
You better try my update-binary again. "capacities" is one of the xattr. update-binary is just a set of functions calling the kernel's routine to do
things. I don't know who told you its hardware related. I already point you out where in the source creating it. Take a look at that part of the source is what you needed...
It would not waste our time if you have tried.I don't know how to help if you don't try it.
Good luck!
Thank you. I did try with your binary previously. But I will try again with an updated recovery and your binary. And then copy the recovery log again. Sorry for misunderstanding.
Sent from my LG-P500 using Tapatalk 2
---------- Post added at 09:56 PM ---------- Previous post was at 09:08 PM ----------
Ok, I tried again with no luck. And here is the log:
http://www.mediafire.com/view/?hcibdddd1vxtcr3
Again... thanks.
Sent from my LG-P500 using Tapatalk 2
Ok, I don't see any indication in the log as to what caused the error with binary. But I opened it in hex viewer. On line 044f21 the platform is listed as arm v7. I think my arm v6 device cannot use this. Anyway, thanks for helping. I guess I have MORE research to do.
Sent from my LG-P500 using Tapatalk 2
ibub said:
Thank you. I did try with your binary previously. But I will try again with an updated recovery and your binary. And then copy the recovery log again. Sorry for misunderstanding.
Sent from my LG-P500 using Tapatalk 2
---------- Post added at 09:56 PM ---------- Previous post was at 09:08 PM ----------
Ok, I tried again with no luck. And here is the log:
http://www.mediafire.com/view/?hcibdddd1vxtcr3
Again... thanks.
Sent from my LG-P500 using Tapatalk 2
Click to expand...
Click to collapse
Just returned and studied your log. It is not set_metadata fail issue. The update-binary can not run on the devices
I found that p500 use Qualcomm MSM7227 (ARM11) on the web. I can't find the cm11 device tree for p500 nor the kernel source. However, I think the update-binary is not work on the kernel and/or cpu.
The easiest way would be including the following commit and rebuild again: (I simplify it for you, just change one line)
Change the file in (cm11 source):
<cm11 source dir>/bootable/recovery/updater/install.c
in line 694 (under the function ParsePermArgs(int argc, char** args):
694:- parsed.has_capabilities = true;
694:+ parsed.has_capabilities = false;
That is the simpliest way I can think of to fix the set_metadata fail in your device.
Good luck!
Thank you so much. I would have never found it. Now I just need to fork the repo, make the change, init repo, build/envsetup sh, sync, add to local manifest, and try to compile. ... Or just submit a pull request. That code is interesting. I think I'm gonna learn some more soon.
Sent from my LG-P500 using Tapatalk 2
I have a galaxy SIII (at&t). I have gotten this error instantly when trying to flash a 4.4 rom. Once I replace the aforementioned file with the contents of your zip, won't I need to re-zip the rom and somehow sign it? And if so, do you have a zip "signer"?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
thanks :good: working on my tab with CM11
Thanks bro.
Ahah too bad I saw the thread only today.
I had this error yesterday and had to waste a lot of time finding a solution. I finally had to flash a stock recovery , a stock system partition and adb sideload the update to resolve it without losing any data.
Sounds like your solution would have been a lot easier, I hope people can see it before attempting more complicated things like me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This Is The Official Thread Of XForce™
To All Moderators:
If You Found Same Thread Of This, Please Delete It... Sorry For Inconvienience...
Thank You...
Disclaimer
1. Terms Of Usage
-- You Can Use This Script For Free And Also, You Can Integrate This Script To Your ROM But It Doesnt Mean That This Script Is Opensource. Take Note That Dont Forget To Include My Name On Credits/Thanks List And Ask My Permission Regarding To This Script
2. Technical
-- If You've Encountered Any Bugs With This Script, Use This Format For Reporting Any Bugs
Bug Reason:
Phone Model:
Android Version:
Post It On XForce™ XDA Thread.
3. Warranties And Liabilities
-- In Case Of Emergency Such As Bricked/Broken Devices, sdcard And More, Dont Blame Me. This Script Does Not Provides Warranties For Your Device. Take Note That By Using This Script, Your Device Warranty Is Void.
4. Thread Rules
-- No Spamming
-- No Yelling
-- Be Patient
-- No Asking Of ETA(Estimated Time Of Arrival)
By Downloading XForce™, You Have Agree With This.
Click to expand...
Click to collapse
Description
XForce™ Is A Script That Provides High Definition Experience On Gaming. XForce™ Is Still On Beta Stage So Report It To This Thread If You Encountered Them.
Click to expand...
Click to collapse
Features
-- [NEW]Drops Filesystem Cache To Gain More Free RAM
-- Tuned Low Memory Killer Settings For Gaming
-- Reduced CPU Usage For RAM
-- Tuned Kernel Performance For System
-- Safe Mount To Prevent System Files Deletion
-- HD Graphics Resolution
-- More Features Will Coming As Updated Soon
Click to expand...
Click to collapse
Requirements
-- Device Running With Android 4.0.X And Above
-- Busybox 1.21 Binaries
-- Haveged Binary
-- Low Memory Killer Support
-- Custom ROM, Kernel And Recovery
-- Terminal Emulator
Warning! You Must Uninstall Some Script From XDA You've Downloaded To Prevent Some Errors.
Click to expand...
Click to collapse
Instructions
-- Download v1.0, v1.1, Or v1.2(Select The Version You Want) Of XForce™ And Move It To /system/xbin directory
-- Set Permission To 777(rwxrwxrwx) And Ownership To 0:0(root:root) Using Root Explorer
-- Done
-- To Use, Open Terminal Emulator Then Type The Following Commands:
Code:
su
xforce
-- To Uninstall, Open Terminal Emulator Then Type The Following Commands:
Code:
su
rm -rf /system/xbin/xforce
Click to expand...
Click to collapse
Downloads
Version 1.3 DXT-7110 -- Run This With Script Manager(Dont Forget!!!)
Version 1.2 RC
Version 1.1 R1
Version 1 R1
Haveged Installer(FIXED) -> Flash This With CWM/TWRP
Changelog
Version 1.3 DXT-7110 | 2014-02-05
Code:
-Changed Interface
-Improved Script To Avoid Random Reboots
-Updated Haveged Install(WIP)
Version 1.2 RC | 2014-02-04
Code:
-Added New Feature: Cache Dropping
-Improved Script Syntax
-RC Version
Version 1.1 R1 | 2014-01-31
Code:
-Improved Syntax For New Users
-Fixed Incomplete Logging
Version 1 R1 | 2014-01-31
Code:
-Initial Release
-Beta Version
Click to expand...
Click to collapse
Credits
-zeppelinrox - One Of Greatest Developers @ XDA
-LENAROX - For Some Recommendations
-andiroxu/andeveloper - For Giving His Permission To Me
-Exit_Only - One Of Greatest Developers @ XDA
-nobodyAtall - For Update-Binary
-fivefour And idcrisis - For Haveged Binary
Click to expand...
Click to collapse
Please Press Thanks Button At The Bottom Of This Post If You Like This Script... Thats It Bro...
Reserved
Wow! Seriously? 4 threads? Including this! Stop being greedy for THANKS & follow rules!
Reporting Mod!
http://forum.xda-developers.com/showthread.php?t=2630166
http://forum.xda-developers.com/showthread.php?t=2630160
http://forum.xda-developers.com/showthread.php?t=2630158
:...::::Recognized TDT™ member:::...
....::◀Press Thanks if I helped▶:::...
^ Could have been an error on his part..
DeveDroid said:
Wow! Seriously? 4 threads? Including this! Stop being greedy for THANKS & follow rules!
Reporting Mod!
http://forum.xda-developers.com/showthread.php?t=2630166
http://forum.xda-developers.com/showthread.php?t=2630160
http://forum.xda-developers.com/showthread.php?t=2630158
:...::::Recognized TDT™ member:::...
....::◀Press Thanks if I helped▶:::...
Click to expand...
Click to collapse
Im Not Creating This Script For Thanks. I Just Want To Help Peoples Sufferring With Laggy Devices. And Also I Follow The XDA Rules. Stop Being So Nerd Bro.
EDIT
Thats My Network Connection Problem So I Duplicated This Thread... Try To Ask Why? Before Posting Like That!
Thanks. Loving this script. It should note to remove ".txt" from the file name though.
I've downloaded the installer haveged, but in the folder xbin there is no file haveged, busybox files only
is it true?
-Rhoby|™-Bugs said:
I've downloaded the installer haveged, but in the folder xbin there is no file haveged, busybox files only
is it true?
Click to expand...
Click to collapse
The Fixed Version Of Haved Installer Is Uploaded... See OP
RenzkiPH said:
The Fixed Version Of Haved Installer Is Uploaded... See OP
Click to expand...
Click to collapse
The haveged installer fails in recovery. I just installed it manually.
Thank For The Gaming
Version 1.2 RC Is Now Available
Changes
-Added New Feature: Cache Dropping
-Improved Script Syntax
-RC Version
Downloads
Proceed To Original Post/First Post
XForce™ Gaming DXT-7110(Version 1.3) | 02/05/2014
This Is The New Version Of XForce Gaming As Of February 5,2014
Changes
-- Changed Interface
-- Improved Script To Avoid Random Reboots
-- Updated Haveged Install(WIP)
Downloads
XForce™ Gaming DXT-7110 Installer -- Run This With Script Manager(Dont Forget)
For Questions And Feedbacks, Post It After This Post Or Quote This Post With Your Post.
NOTE: I Release A New Version Quickly To Know What Is Wrong, Comments Or Feedbacks
RenzkiPH said:
XForce™ Gaming DXT-7110(Version 1.3) | 02/05/2014
This Is The New Version Of XForce Gaming As Of February 5,2014
Changes
-- Changed Interface
-- Improved Script To Avoid Random Reboots
-- Updated Haveged Install(WIP)
Downloads
XForce™ Gaming DXT-7110 Installer -- Run This With Script Manager(Dont Forget)
For Questions And Feedbacks, Post It After This Post Or Quote This Post With Your Post.
NOTE: I Release A New Version Quickly To Know What Is Wrong, Comments Or Feedbacks
Click to expand...
Click to collapse
Hi RenzkiPH,
Updated Haveged Install(WIP) is still error unable Flash This With CWM/TWRP, Please solve the bugs thanks
bbivan said:
Hi RenzkiPH,
Updated Haveged Install(WIP) is still error unable Flash This With CWM/TWRP, Please solve the bugs thanks
Click to expand...
Click to collapse
Sorry For That Bro... I Will Release The 2nd Fixed Version Later...
Sent from my SHV-E160L using Tapatalk
RenzkiPH said:
Sorry For That Bro... I Will Release The 2nd Fixed Version Later...
Sent from my SHV-E160L using Tapatalk
Click to expand...
Click to collapse
I manually installed this, set propper permissions and terminal emulator can't find the script, and root explorer says it can't run it??
Setting.Out said:
I manually installed this, set propper permissions and terminal emulator can't find the script, and root explorer says it can't run it??
Click to expand...
Click to collapse
What Version Are Using???
Sent from my SHV-E160L using Tapatalk
Your latest script.. I only downloaded it today..
Sent from my Nexus S using XDA Premium 4 mobile app
Setting.Out said:
Your latest script.. I only downloaded it today..
Sent from my Nexus S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You Must Run It With Script Manager...
Sent from my SHV-E160L using Tapatalk
RenzkiPH said:
You Must Run It With Script Manager...
Sent from my SHV-E160L using Tapatalk
Click to expand...
Click to collapse
Script manager gives the option to run but nothing happens.. I checked to see if any values were changed, and they weren't...
Sent from my Nexus S using XDA Premium 4 mobile app
★ ViPER4Android MK-Mod ★
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Changelogs | Downloads | Extensions | Screenshots | Website | Fixes
Introduction:
ViPER4Android is very popular audio mod around the world of Android and probably the best audio mod ever made. But there is so many complexity ViPER4Android couldn't go further through, so I wish "ViPER4Android MK-Mod" could be a project to let our beloved ViPER4Android step in advance. Original V4A details at ViPER4Android Official forum.
# Track this thread using the URL below.
URL: http://forum.xda-developers.com/showthread.php?t=3300821
Click to expand...
Click to collapse
Latest Features:
ViPER4Android MK-Mod App:
+ All Apps/System audio Processing.
+ Integrated V4A post-boot script.
+ 4D rotation mode.
+ ViPER4Android v2.4.0.1 based.
+ Material Design and Icon.
+ New UI Settings.
+ Forum link added.
+ Update link added.
ViPER4Android post-boot script:
+ Enforcing Override.
+ LPA (Low Power Audio) Tweaks.
+ MK-Audio Engine.
+ V4A Memory Injection.
Click to expand...
Click to collapse
Recommendation:
* Root Access.
* CPU architecture: arm / armv7 / arm64 / x86 / x64
* Android version 4.x-6.x.
* Init.d support.
* SuperSU or Install using flashable zip.
* BusyBox installed.
* Keep turn off Audio FX (if exists).
* Custom recovery (for flashable zip).
Note: Some mods and patches of recommendation are included in 'Extension' tab.
Click to expand...
Click to collapse
Instructions:
Without SuperSU
Support: flashable zip
For device that rooted using King root/similar and installed its root handler app.
1. Go to STEP-A
With SuperSU
Support: apk, flashable zip
For rooted device that uses SuperSU as root handler app.
1. SuperSU app > SETTINGS > If Ticked "Mount namespace separation" then Untick it and Reboot.
2. SuperSU app >APPS > remove permission for ViPER4Android/V4A MK-Mod if exists.
3. For apk install go to STEP-B or For flashable zip install go to STEP-A
STEP-A
2. Reboot to recovery.
1: Flash UPDATE-Kernel_init.d_Injector-AK2-signed.zip
2: Flash UPDATE-Busybox.Installer.v1.24.2-ALL-signed.zip
3: Flash 'V4A-MK-Mod-xx-flashable.zip'
4: Reboot to system.
5: Goto STEP-B
STEP-B
5: Increase your screen/sleep time from settings to 5min. You can set it back later.
6: Open V4A MK-Mod app install driver when or if asked.
7: Grant root access when or if asked.
8: Wait and don't do anything here until it confirm you that the driver installed.
6: Reboot
Click to expand...
Click to collapse
Thanks To:
Code:
[user=3901724]@zhuhang[/user] and ViPER520 (Founders of ViPER4Android).
[user=631273]@Chainfire[/user] for legendary SuperSU.
[user=4544860]@osm0sis[/user] for osm0sis' Odds and Ends (multi mod/scripts).
[user=4445176]@guitardedhero[/user] | [user=5704037]@repey6[/user] | [user=5210243]@exodius48[/user] | [user=6118476]@#mrk[/user]
for helping/support/testing.
...and those I forgot to mention.
I spend dedicated time, made pressure on brain and did hard work to make this perfect
If you like my post please hit Thanks and give a rate....
~~ Feel The power of ViPER4Android ~~
XDA:DevDB Information
V4A-MK-Mod, App for all devices (see above for details)
Contributors
metaspook
Version Information
Status: Stable
Current Stable Version: 3.6
Stable Release Date: 2016-06-07
Created 2016-01-25
Last Updated 2016-06-10
[ Fixes ]
* These issues are not related to modification of V4A MKM please submit these on Official ViPER4Android thread.
# Effect Profile save/load issue.
# V4A IRS related issues.
[ Extensions ]
Impulse Response Sample (IRS)
# Official Impulse Response Sample Index
SuperSU / BusyBox / init.d
SuperSU (flashable)
SuperSU_beta (flashable)
BusyBox (flashable)
'init.d' Patcher (flashable)
Fix / Mod / Guide.
HTC Disable system write protection.
Fix brimmed ' /system' partition.
Note:
* You can Submit Custom V4A Profile, IRS etc. and selected will be published in this section.
* Inform me if any link isn't working.
Any screenshots ?
Phuclun510 said:
Any screenshots ?
Click to expand...
Click to collapse
Given in the Screenshots tab look at the Top menu...
@metaspook will this app replace installed v4a on my device?
exodius48 said:
@metaspook will this app replace installed v4a on my device?
Click to expand...
Click to collapse
Yes.. :good:
So, do i need to uninstall installed v4a's driver & v4a app?
exodius48 said:
So, do i need to uninstall installed v4a's driver & v4a app?
Click to expand...
Click to collapse
No need, my Installer is intelligent enough to detect installed V4A and uninstall it before it going Install itself.
:angel::angel::angel:
Download link? Cant find it
radz_ said:
Download link? Cant find it
Click to expand...
Click to collapse
This is XDA devDB , download link already present in above of this thread http://forum.xda-developers.com/devdb/project/?id=13594#downloads
---------- Post added at 11:37 PM ---------- Previous post was at 11:14 PM ----------
@metaspook AFter flashing, v4a disappear on app drawer? is this compatible with kitkat?
exodius48 said:
This is XDA devDB , download link already present in above of this thread http://forum.xda-developers.com/devdb/project/?id=13594#downloads
---------- Post added at 11:37 PM ---------- Previous post was at 11:14 PM ----------
@metaspook AFter flashing, v4a disappear on app drawer? is this compatible with kitkat?
Click to expand...
Click to collapse
No. I already mentioned in Supported Devices list...
Don't worry friend I will try to make one for KitKat also.. OK :good:
@exodius48
V4A by default causes a very high level of distortion in Oneplus 2.
Any changes here that'll maybe solve it(I know its a long shot but I really want v4a)?
Tried the app now and it doesn't work. Unless there's something special I need to do... This was on a Nexus 5, Android 6.0.1, rooted with SuperSu 2.66 systemless, TWRP.
Sent from my Nexus 5 using Tapatalk
Co.Tibi said:
Tried the app now and it doesn't work. Unless there's something special I need to do... This was on a Nexus 5, Android 6.0.1, rooted with SuperSu 2.66 systemless, TWRP.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Maybe you need the latest busybox?
metaspook said:
Don't worry friend I will try to make one for KitKat also.. OK :good:
@exodius48
Click to expand...
Click to collapse
Sorry my mistake,, i did not read your thread very well.. hehe
Waiting for your kitkat mod. :good:
Co.Tibi said:
Tried the app now and it doesn't work. Unless there's something special I need to do... This was on a Nexus 5, Android 6.0.1, rooted with SuperSu 2.66 systemless, TWRP.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
What problem u have got n what special thing u did give me feedback plz
I also tested on device with Android 6.0.1, rooted with SuperSu 2.66 systemless, TWRP.
and worked fine...
exodius48 said:
Sorry my mistake,, i did not read your thread very well.. hehe
Waiting for your kitkat mod. :good:
Click to expand...
Click to collapse
Thanks bt try upgrade Android Nowadays KitKat used to be old.
metaspook said:
What problem u have got n what special thing u did give me feedback plz
I also tested on device with Android 6.0.1, rooted with SuperSu 2.66 systemless, TWRP.
and worked fine...
Click to expand...
Click to collapse
In driver status I see abnormal. After rebooting from driver installation it asks me to download the driver again. Are there any particular steps I have to follow to get this working?
Sent from my Nexus 5 using Tapatalk