Related
I have find a new supersu here
http://forum.xda-developers.com/showthread.php?p=23427715
It is working good so far. Is it possible to remove the original super user bundeled with the custom roms. Or it can get some bad effect on custom rom.
Yerp saw this back in march...see it's been updated....:thumbup:
Thx
Probably not that great. Superuser is used universally for a reason.
wayzata said:
Probably not that great. Superuser is used universally for a reason.
Click to expand...
Click to collapse
guess you know this because.....
Actual it is....but you prob installed it and ran it huh?
I have deleted the /system/app/SuperUser.apk through Root Explorer
SuperSu is working fine.
(It should only be done after installing SuperSU from the market, then run it a popup will come up asking to update binary say yes.)
Bought it a while back to support Chainfire.
wayzata said:
Probably not that great. Superuser is used universally for a reason.
Click to expand...
Click to collapse
And you would be wrong. SuperSU comes from a well respected developer (Chainfire), and was created because Superuser has some major bugs that ChainsDD still hasn't fixed - such as su crashing if Android wasn't fully booted. (This was a pain for me for CM9 work when combined with their new "don't default to root in ADB" policy. ADB not going straight to root + broken su = pain)
Most I9100 and N7000 firmware developers have switched over, and when on Touchwiz firmwares I have too. Superuser's one advantage - it's open source which is why it is in CM9, I don't believe SuperSU is.
Entropy512 said:
And you would be wrong. SuperSU comes from a well respected developer (Chainfire), and was created because Superuser has some major bugs that ChainsDD still hasn't fixed - such as su crashing if Android wasn't fully booted. (This was a ****ing pain in the ass for me for CM9 work when combined with their new "don't default to root in ADB" policy. ADB not going straight to root + broken su = pain)
Most I9100 and N7000 firmware developers have switched over, and when on Touchwiz firmwares I have too. Superuser's one advantage - it's open source which is why it is in CM9, I don't believe SuperSU is.
Click to expand...
Click to collapse
Would you recommend using SuperSU over superuser in CM9?
stratatak7 said:
Would you recommend using SuperSU over superuser in CM9?
Click to expand...
Click to collapse
Not in CM9
Entropy512 said:
Not in CM9
Click to expand...
Click to collapse
so for any ROM other than cm9, you recommend it? and if so, how would you recommend we install? i assume we need to install it first, then update, then delete the "regular superuser"?
TDuran said:
so for any ROM other than cm9, you recommend it? and if so, how would you recommend we install? i assume we need to install it first, then update, then delete the "regular superuser"?
Click to expand...
Click to collapse
Just for kicks, I installed it and tried it. This probably isn't the "proper" method and you could possibly mess something up but anyway here is what I did: 1. Delete superuser.apk from your app folder in /system. 2. In Play store download superSU and install. It will ask you to update binaries. Do it and you should be golden.
**Delete files at your own risk** I used Root explorer and make sure you mount app folder as r/w before deleting and then put it back to normal when you're done.
failed... on galnet miui.. time to reinstall old SU
I have flashed the infusion kernel and old super user came back again. It means rooted kernel got Super User pre-packed with them
Working great for me on the infuse and the nook. Both cm9. CF is a great dev.
Sent from my NookColor using Tapatalk 2
ndhanta said:
I have flashed the infusion kernel and old super user came back again. It means rooted kernel got Super User pre-packed with them
Click to expand...
Click to collapse
Yes. Many Rom devs include SU.
Sent from my Emancipated Infuse having Communion.
ndhanta said:
I have flashed the infusion kernel and old super user came back again. It means rooted kernel got Super User pre-packed with them
Click to expand...
Click to collapse
This is one of the reasons I removed autorooting from my kernels.
In my case, I just flashed the CWM-flashable SuperSU package in CWM - It will automatically remove legacy Superuser I believe.
I personally would like to see it in CM9 (or at least the Superuser problems that caused Chainfire to write SuperSU fixed) - but I believe that the free version of Superuser is open source while SuperSU is not (I could be wrong about this).
I am not getting any source information of SuperSu. It seems closed source.
Entropy512 said:
This is one of the reasons I removed autorooting from my kernels.
In my case, I just flashed the CWM-flashable SuperSU package in CWM - It will automatically remove legacy Superuser I believe.
I personally would like to see it in CM9 (or at least the Superuser problems that caused Chainfire to write SuperSU fixed) - but I believe that the free version of Superuser is open source while SuperSU is not (I could be wrong about this).
Click to expand...
Click to collapse
SuperSU is free on the market (there is also a $$ pro version). I'm seeing the same thing ndhanta is with the infusion kernel. There is a script called install_su.sh which does the old ef su install but I haven't been able to track down the parent script that calls it, or figure out where the $source and $dest variables are being set... I'm assuming it may be possible to stop the script from performing the su install by changing the modify date of the file specified in the $dest var.
Any chance a version of the 4.4.12 GB kernel might materialize that supports OC? (Or an update to the infusion kernel that removes the su installer?) This would help eliminate the issue...
I just Re-rooted my SGS2 and I now have SU and SuperSU ??
Im assuming that SuperSU was installed automatically with the root ROM??
I have puirchased the Pro Version of SU .. so is it safe to Remove SuperSU without messing something up ?
Yes no problem
Just update the binaries of SU.
I was wondering if anyone knows why I my tablet won't root, does the paranoid android rom have a special root file, cause I tried with my regular root file and it says before I reboot that the root needs to be fix, why is that?
does anyone know how to solve this problem? pm me on [email protected]
alexjojo946 said:
does anyone know how to solve this problem? pm me on [email protected]
Click to expand...
Click to collapse
This room has a built-in superuser so yes, it's rooted. But since the superuser is built-in you won't see any superuser app. If you don't like it then you can disable it and use any superuser app, otherwise don't bother cuz it works anyway...
unclefab said:
This room has a built-in superuser so yes, it's rooted. But since the superuser is built-in you won't see any superuser app. If you don't like it then you can disable it and use any superuser app, otherwise don't bother cuz it works anyway...
Click to expand...
Click to collapse
yeah but i installed apps like titanium backup, no frills cpu, game boosters and I can't start them cause it says i need to check if my rom is rooted i tried to disable superuser in app manager and tried installing my own version, still nothing happens
alexjojo946 said:
yeah but i installed apps like titanium backup, no frills cpu, game boosters and I can't start them cause it says i need to check if my rom is rooted i tried to disable superuser in app manager and tried installing my own version, still nothing happens
Click to expand...
Click to collapse
First, install your own superuser, but don't disable the built-in one. Launch your superuser, let him update its binaries if needed, and let him get superuser permissions from the built-in superuser.
Here you go, now you can disable the built-in superuser and use your one.
I did it this way and it worked, so it should be the same for you.
But for now if your superusers are messed just flash again the rom, wipe dalvik and cache and start fresh.
Good luck!
unclefab said:
First, install your own superuser, but don't disable the built-in one. Launch your superuser, let him update its binaries if needed, and let him get superuser permissions from the built-in superuser.
Here you go, now you can disable the built-in superuser and use your one.
I did it this way and it worked, so it should be the same for you.
But for now if your superusers are messed just flash again the rom, wipe dalvik and cache and start fresh.
Good luck!
Click to expand...
Click to collapse
I just cleared everything and flashed again, i'm gonna try and do what u told me, hope this works
alexjojo946 said:
I just cleared everything and flashed again, i'm gonna try and do what u told me, hope this works
Click to expand...
Click to collapse
Its working, i updated the rom superuser and fixed system xbin su pathway, thanks for the help man ))
please give me a link too the rom... i want to flash that...
Sent from my GT-P6200 using Tapatalk HD
ali.cheeta said:
please give me a link too the rom... i want to flash that...
Sent from my GT-P6200 using Tapatalk HD
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2221328
its not that hard to find it...
I'm using a CM11 ROM, and Superuser is giving me problems - throws up errors now & again. I like and want to use SuperSU, but Superuser is integrated into the ROM.
How can I get rid of Superuser and replace with SuperSU (preferably just using my phone, no ADB).
setspeed said:
I'm using a CM11 ROM, and Superuser is giving me problems - throws up errors now & again. I like and want to use SuperSU, but Superuser is integrated into the ROM.
How can I get rid of Superuser and replace with SuperSU (preferably just using my phone, no ADB).
Click to expand...
Click to collapse
in the integrated superuser menu(can be found in device settings), if you open settings, you have the option of giving superuser access to "disabled" (by default it is apps only).
after disabling you just have to flash the supersu zip file(can be found on the supersu xda forum) via recovery mode. and you're done.
I flash the superSU.zip after flashing CM11 and Gapps so superSU is the main root app. Never had an issue.
Please keep it friendly and there is no need for name calling of any kind. We tend not to like people resurrecting old threads, but seen as this came in handy for someone there's no harm done.
Thread cleaned.
wedgess said:
Please keep it friendly and there is no need for name calling of any kind. We tend not to like people resurrecting old threads, but seen as this came in handy for someone there's no harm done.
Thread cleaned.
Click to expand...
Click to collapse
Thank you, mod. Wasn't trying to cause any problems, just trying to help a new member.
rdx93 said:
in the integrated superuser menu(can be found in device settings), if you open settings, you have the option of giving superuser access to "disabled" (by default it is apps only).
after disabling you just have to flash the supersu zip file(can be found on the supersu xda forum) via recovery mode. and you're done.
Click to expand...
Click to collapse
i'm having some problems in cm11 with superuser too so i took your advice and disabled it and flashed the supersu.zip but still no root and then i went back to enable it again under settings but now the superuser option is gone.
how do i fix this?
Just make clean flash of CM, then get SuperSU via store
JimZiii said:
i'm having some problems in cm11 with superuser too so i took your advice and disabled it and flashed the supersu.zip but still no root and then i went back to enable it again under settings but now the superuser option is gone.
how do i fix this?
Click to expand...
Click to collapse
In the SuperSU settings, there is a setting called something like "Respect Cyanogenmod Settings". Uncheck that.
Thnx alot! Works great! Now i just have to change that stupid google dialer that's in cm11
Sent from my GT-I9300 using Tapatalk
Hello,
i finally got my Nexus 5 today and first thing I did was unlocking the bootloader, installed TWRP custom recovery, flashed CM11-nightly and Franco Kernel (r31).
Next thing I usually do is to uninstall some apps with Titanium Backup (Pro). But I can't uninstall any system apps (e. g. Browser.apk). Titanium says "successful" but after refreshing the application list, the app is still there.
Does anyone have an idea what is going wrong here? Is it a problem with CM11's superuser or with Titanium Backup?
Thanks.
Cloonix said:
Hello,
i finally got my Nexus 5 today and first thing I did was unlocking the bootloader, installed TWRP custom recovery, flashed CM11-nightly and Franco Kernel (r31).
Next thing I usually do is to uninstall some apps with Titanium Backup (Pro). But I can't uninstall any system apps (e. g. Browser.apk). Titanium says "successful" but after refreshing the application list, the app is still there.
Does anyone have an idea what is going wrong here? Is it a problem with CM11's superuser or with Titanium Backup?
Thanks.
Click to expand...
Click to collapse
What happens if you delete the file with a file manager and reboot?
Aerowinder said:
What happens if you delete the file with a file manager and reboot?
Click to expand...
Click to collapse
I used Solid Explorer as a file manager and tried to delete /system/app/Browser.apk. The root-confirmation (CM11 superuser) pops up, asks for superuser (i grant) and Solid Explorer deletes the file without error. But the file is still there (without reboot).
Issue with superuser?
Edit: Stop... I noticed /system is mounted as read-only.
I tried to analyze the problem... and the only conclusion is, that my superuser is not working. Also Super SU ist not working. I also flashed Omni ROM instead of CM11 with no success. I used an older version of TWRP without success. Does anybody has an idea?
Edit: Before with Stock ROM and Super SU it was working.
I don't know why I'm the only person with this issue... But I solved it with the following steps:
1. Flash CM11 (nightly)
2. Start the OS
3. Reboot to recovery and wipe cache/dalvik
4. Install "Super SU"
5. Start the OS
Titanium Backup is asking for root rights. Other apps also didn't get root in CM11. Whenever I install a new CM11 nightly root rights for TB are gone and I have to do the same steps again.
But why no one else has this problem? I googled like crazy. Is it CM11 or me?
Me to, cm11 for a850L build on crdroid nexus4
Cloonix said:
I don't know why I'm the only person with this issue... But I solved it with the following steps:
1. Flash CM11 (nightly)
2. Start the OS
3. Reboot to recovery and wipe cache/dalvik
4. Install "Super SU"
5. Start the OS
Titanium Backup is asking for root rights. Other apps also didn't get root in CM11. Whenever I install a new CM11 nightly root rights for TB are gone and I have to do the same steps again.
But why no one else has this problem? I googled like crazy. Is it CM11 or me?
Click to expand...
Click to collapse
Did you leave out Franco kernel this time?
This is the fix for your issue:
http://forum.xda-developers.com/showthread.php?t=2592456
es0tericcha0s said:
This is the fix for your issue:
http://forum.xda-developers.com/showthread.php?t=2592456
Click to expand...
Click to collapse
Thanks a lot!
Changing selinux to "permissive" did solve all my problems. I also had issues with other applications.
How can I change the selinux mode directly in the CM11-Zip? Under Redhat/CentOS is a configuration file unter /etc/selinux. In CM11 I can't find something similar.
And how it comes that this issue is not well-known? I think there are more 4.4 KK / CM11 users with problems.
Aerowinder said:
Did you leave out Franco kernel this time?
Click to expand...
Click to collapse
No I flashed Franco after CM.
Cloonix said:
Thanks a lot!
Changing selinux to "permissive" did solve all my problems. I also had issues with other applications.
How can I change the selinux mode directly in the CM11-Zip? Under Redhat/CentOS is a configuration file unter /etc/selinux. In CM11 I can't find something similar.
And how it comes that this issue is not well-known? I think there are more 4.4 KK / CM11 users with problems.
No I flashed Franco after CM.
Click to expand...
Click to collapse
No problem. I know that problem was starting to annoy me. Got the idea from playing with a new Note 3. The newer Samsung 4.3 roms are like that too. If you don't change to Permissive then Xposed and other mods won't work either.
I guess it's possible that it's just something strange with certain CM11 and Franco kernel combos?
es0tericcha0s said:
I guess it's possible that it's just something strange with certain CM11 and Franco kernel combos?
Click to expand...
Click to collapse
Even without Franco (which was my first guess) CM11 (my root) behaves that way.
I will look for a method to set selinux to permissive directly in the ZIP of CM11 and will update this post.
Cloonix said:
Even without Franco (which was my first guess) CM11 (my root) behaves that way.
I will look for a method to set selinux to permissive directly in the ZIP of CM11 and will update this post.
Click to expand...
Click to collapse
I'd imagine adding something like this in: http://forum.xda-developers.com/showpost.php?p=48006307&postcount=65 would do the trick, though I have not had that issue in awhile. I switch roms often.
es0tericcha0s said:
I'd imagine adding something like this in: http://forum.xda-developers.com/showpost.php?p=48006307&postcount=65 would do the trick, though I have not had that issue in awhile. I switch roms often.
Click to expand...
Click to collapse
I tried this. And it was successfully changing selinux to permissive with every reboot. But doing this I noticed that even permissive doesn't solve the problem. CM11 built-in superuser just don't work for me. Only "Super SU" by Chainfire works well. And permissive solves a few other problems besides TiBa.
Personally I've always eventually had issues with Superuser unmounting the system as rw causing issues with apps like Titanium. Had it happen many many times on my old phone as well as the Nexus 5 across multiple ROMs. I just stick with SuperSU now.
Haven't had too many issues with that part it seems, but glad you narrowed down the problems.
I find this issue sometimes on varous flashes of CM 11 on different devices.
I use ROM toolbox fo manage apps, and sometimes it just wont delete. The solution is strange: I install adaway - somehow, that "unlocks" something that lets you delete apps. You can uninstall adaway once you have run it!
Galaxy Nexus
I'm replying just to help out anyone who has this issue, but doesn't have a Nexus 5. I was trying to find a fix for me and my Galaxy Nexus running the latest Paranoid Android beta 4.4.2 because I kept having this same problem.. It wouldn't uninstall... and I would only keep getting directed to this specific post. So....
I tried the 'selinux' fix first, and that alone would not do a thing...
I then tried installing the 'Wanam Xposed' app and it worked perfectly.
Just change selinux to permissive and make sure both selinux and Wanam have SU access and then try to uninstall via Titanium... or whatever method you usually use.
Hope it's okay for me to post here. Thanks for the help, everyone!
es0tericcha0s said:
No problem. I know that problem was starting to annoy me. Got the idea from playing with a new Note 3. The newer Samsung 4.3 roms are like that too. If you don't change to Permissive then Xposed and other mods won't work either.
I guess it's possible that it's just something strange with certain CM11 and Franco kernel combos?
Click to expand...
Click to collapse
Hi,
unfortunately the SElinuxModeChanger seems not to work for me (Samsung Galaxy S2, CM 11 m6) and I do not really get how I should install Supersu (the first described solution). I guess I should not just install it from the play store - right? But were do I get an installable zip-file to install it from the CWM?
Or is there anything else that might be wrong in my system - so that I do not need to install supersu at all?
regards
Daniel
daniu said:
Hi,
unfortunately the SElinuxModeChanger seems not to work for me (Samsung Galaxy S2, CM 11 m6) and I do not really get how I should install Supersu (the first described solution). I guess I should not just install it from the play store - right? But were do I get an installable zip-file to install it from the CWM?
Or is there anything else that might be wrong in my system - so that I do not need to install supersu at all?
regards
Daniel
Click to expand...
Click to collapse
If you are already using CM11, then yes, you can install SuperSu from the Play Store. Once you do and open the app, it will prompt you to update the SuperUser binary. You should be able to do the "normal" method, and then once that updates, reboot, then try the SELinux app again and then everything should start to work like you would expect. If the normal method doesn't work, then you can let it download the newest zip for you if you choose the CWM/TWRP method, and then boot to recovery and install the zip it downloads for you.
SeEsAw12 said:
I'm replying just to help out anyone who has this issue, but doesn't have a Nexus 5. I was trying to find a fix for me and my Galaxy Nexus running the latest Paranoid Android beta 4.4.2 because I kept having this same problem.. It wouldn't uninstall... and I would only keep getting directed to this specific post. So....
I tried the 'selinux' fix first, and that alone would not do a thing...
I then tried installing the 'Wanam Xposed' app and it worked perfectly.
Just change selinux to permissive and make sure both selinux and Wanam have SU access and then try to uninstall via Titanium... or whatever method you usually use.
Hope it's okay for me to post here. Thanks for the help, everyone!
Click to expand...
Click to collapse
No clue why, but this worked for me. Permissive didn't do it (was already permissive using CM 11 for tf201) and AdAway didn't do it. Didn't matter that Wanam Xposed is for Samsung devices, once given root to this app, Titanium got its head out of its rump.
UPD: So, if i uninstall Wanam Xposed then TB sticks its head back up its rump. Whatever giving root to that app does, its fixing usage issues with TB.
I cant figure out how to do it, I am rooted and I can't figure it out!
Brava27 said:
I cant figure out how to do it, I am rooted and I can't figure it out!
Click to expand...
Click to collapse
Need a SeLinux Permissive Kernel for S7Edge first. Have you found one?
Brava27 said:
I cant figure out how to do it, I am rooted and I can't figure it out!
Click to expand...
Click to collapse
Seems this guy has the answer on an enforcing kernel.
http://forum.xda-developers.com/s7-edge/review/audio-quality-t3336558
If you haven't seen this thread already, check it out. I successfully installed V4A on my 935F with it.
http://forum.xda-developers.com/showthread.php?t=3335007
And FYI... it sounds fantastic!
You DON'T need permissive kernel for v4a any more..after hundereds of trials and errors I just downloaded newest apk from original v4a thread, put it in private-apps folder then set correct permitions rw-r-r, restarted device and it works flowellesly ! I have stock enforced kernel.
tin2404 said:
You DON'T need permissive kernel for v4a any more..after hundereds of trials and errors I just downloaded newest apk from original v4a thread, put it in private-apps folder then set correct permitions rw-r-r, restarted device and it works flowellesly ! I have stock enforced kernel.
Click to expand...
Click to collapse
Does it work with Spotify as well?
Why don' you try? I don't use it.
tin2404 said:
You DON'T need permissive kernel for v4a any more..after hundereds of trials and errors I just downloaded newest apk from original v4a thread, put it in private-apps folder then set correct permitions rw-r-r, restarted device and it works flowellesly ! I have stock enforced kernel.
Click to expand...
Click to collapse
Tried hundered of ways here as well,
Mine just keeps asking to install the damn driver all the time mate, and even if installed, after reboot - it just asks again to install/update the driver again.
Tried with the su.policy zip flash as well. Still cant get it to work!
Tried with the MM compatible newest APK and placed it in Priv-app. Guess that's what you did too. Cant figure out what I'm missing here.
It happens to me also.That means you did NOT properly root device.Error with constant driver install is because busybox..I rerooted device ,wiped data for SU, and granted permission to busybox again.DO NOT use any other Viper app then original one from thread !
tin2404 said:
It happens to me also.That means you did NOT properly root device.Error with constant driver install is because busybox..I rerooted device ,wiped data for SU, and granted permission to busybox again.DO NOT use any other Viper app then original one from thread !
Click to expand...
Click to collapse
Youv'e been a lot helpful mate,
I think I'm getting somewhere, Could you please tell me which busybox did you use?
Is it the Stericsson version, or the Meefik ?
Stericsson one. I hac problems as you did and concluded the most simple one was the best..All that modded Viper apps doesn't do any use.Just use original one,give permissions in private-apps, restart device and that is it
which music players support this? cuz so far all i see is status normal processing no
tin2404 said:
Stericsson one. I hac problems as you did and concluded the most simple one was the best..All that modded Viper apps doesn't do any use.Just use original one,give permissions in private-apps, restart device and that is it
Click to expand...
Click to collapse
Men! You put so much hope in my heart. Please, could you be so nice and prepare step by step to do list? I personally would ask you about 'give permissionso in private-apps'. Could you explain? Do you copy v4a to priv-apps? Where from? What permissions? And about busy box: when I open it it shows me that it is installed in su/xbin... in what folder did you install busybox? And one about reroot: did you go to su and choose: full unroot before flashing su again? And what about mount namespaces: checked or unchecked in su? Have to tell you that I've tried so much different ways and still v4a doesn't work. I would love to try your way but please put some lights here. Thanks!
SM-G935F powered by Echoe
I've tried my best, in all possible variables and finally decided to give up after wasting 3 straight days of a perfect weekend.
My Driver just doesn't stick and I've tried all alternative installation methods. I've kept backups of system/*.* so all damages were reversed without any flashing. Root, Busybox everything runs perfectly and tested everything for integrity.
So far I've cornered the issue to Systemless Root, which seems to be the only entity having issues with v4a. Until a proper answer is digged up, I'm gonna stick with my Note 5 which has this working on System-Mode Root. (The driver didn't stick on the Note 5 when I tried to use it with System-less) Luckily the Note 5 is still on LP, with Su 2.64.
Good Luck to those who are trying, and thanks to all who helped!
OK...I made comprehesive tutorial here
http://forum.xda-developers.com/s7-edge/themes/viper4android-proper-installation-t3340525
JazonX said:
I've tried my best, in all possible variables and finally decided to give up after wasting 3 straight days of a perfect weekend.
My Driver just doesn't stick and I've tried all alternative installation methods. I've kept backups of system/*.* so all damages were reversed without any flashing. Root, Busybox everything runs perfectly and tested everything for integrity.
So far I've cornered the issue to Systemless Root, which seems to be the only entity having issues with v4a. Until a proper answer is digged up, I'm gonna stick with my Note 5 which has this working on System-Mode Root. (The driver didn't stick on the Note 5 when I tried to use it with System-less) Luckily the Note 5 is still on LP, with Su 2.64.
Good Luck to those who are trying, and thanks to all who helped!
Click to expand...
Click to collapse
FRM300 said:
Men! You put so much hope in my heart. Please, could you be so nice and prepare step by step to do list? I personally would ask you about 'give permissionso in private-apps'. Could you explain? Do you copy v4a to priv-apps? Where from? What permissions? And about busy box: when I open it it shows me that it is installed in su/xbin... in what folder did you install busybox? And one about reroot: did you go to su and choose: full unroot before flashing su again? And what about mount namespaces: checked or unchecked in su? Have to tell you that I've tried so much different ways and still v4a doesn't work. I would love to try your way but please put some lights here. Thanks!
SM-G935F powered by Echoe
Click to expand...
Click to collapse
Has anyone managed to get it working? I've tried every single method to install it and still nothing!
csr.rocha said:
Has anyone managed to get it working? I've tried every single method to install it and still nothing!
Click to expand...
Click to collapse
Yes. Actually there is a perfect package from @guitardedhero. You have to be rooted, busyboxed, twrp'ed. Flash this: http://forum.xda-developers.com/attachment.php?attachmentid=3701983&d=1459364213
It is Viper Atmos Sony Beats edition working beautifully on ny S7E. Three more step to do after flashing: 1. freeze SoundAlive and AdaptSound, reboot. 2. go to system preferences and check whether Viper has memory access granted. 3. go to SuperSu and DISABLE 'Mount namespace separation', reboot. Done!
Btw. If you want to play with Profiles inside Viper, go to your internal memory using root explorer and inside Viper folder create folder called 'Profiles'.
Btw2. 6.0.1new abowe destroy your conf files. Hope you have backup.
Better flash @guitardedhero mod on fresh rooted rom. hope you enjoy.
Btw3. Sound is AMAZING!
S7E powered by Echoe™ v5
Thanks for your reply!
Just after I asked for help here, i found a driverless package from @guitardedhero that worked! Glad to know you did it too, mate! :highfive:
Working but 10 second later turn normal mod
Why do you think's going on?
For example in youtube, 10 second viber4android active, later deactivate.
SM-G935F cihazımdan Tapatalk kullanılarak gönderildi