Related
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
Sorry as I don't have a solution for your problem....
But still as far as I know Super user 2.46 is not fully compatible with android 5 & above.
On other hand I would suggest you to give a try to super user 2.49 beta which is the latest but still under development.
Hope you find this useful.
ayushbpl10
DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
If you want to make SuperSU a user app:
If SuperSU was "updated" by the Play Store (ie there's an eu.chainfire.supersu-*.apk in /data/app), then delete /system/app/SuperSU.apk and reboot. If it's flashed *and* the afore mentioned apk is *not* in /data/app, then move /system/app/SuperSU.apk to /data/app and reboot.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
Sent from my Aqua i5 mini using xda-developers.com, powered by appyet.com
DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
If all you wanted to do was make it a user app, reroot, open supersu, go to cleanup and choose for reinstallation. After choosing that, if it says to reboot then press it again, do so, else reboot and install supersu from play. Done, supersu as a user app
mmonaghan34 said:
If all you wanted to do was make it a user app, reroot, open supersu, go to cleanup and choose for reinstallation. After choosing that, if it says to reboot then press it again, do so, else reboot and install supersu from play. Done, supersu as a user app
Click to expand...
Click to collapse
That doesn't work (v2.46 on LG G3 running v5.0.1). It loops trying to uninstall. After a couple minutes, I forced a reboot. SuperSU was still there, and as a system app.
Edit: The same thing happens when I tell SuperSU to completely unroot the LG G3. Since I needed to unroot in order to apply an LG/Verizon OTA update, I used LG's Flash Tool to replace the system partition (THAT removed SuperSU!), and then the OTA update was successful.
Since LG now supplies an on-phone backup/restore tool for the G3 as part of the Settings menu, I no longer need to run Titanium Backup, which means I no longer need root. Given the nuisance issues with rooting/unrooting/system updating/etc, I've decided to remain unrooted on the LG G3 for the time being. Quite a change for me, since this is the first Android device in well over a dozen for which I've made this decision.
I've researched and tried every method to get AdAway to work. I uninstalled some system apps which allowed me to install it but I cannot get past that because of the S-off warning screen.
I am rooted and bootloader is unlocked. Ive attatched a screenshot of my kernel etc
Do you have a folder called init.d in system/etc?
I have installed Adaway on at least 6 different Marshmellow ROM's with no issue.
Switch ROM and Kernels and see what happens.
Just FYI, this is a development area. You will have more luck posting in the Q&A section.
You seem to be using system less root, that's probably the issue. In the adaway thread there is a zip that must be flashed if you're using system less root.
Also questions belong in the Q&A section not dev section. I've reported the thread, a mod should move it but just letting you know for next time.
miguelito18 said:
Do you have a folder called init.d in system/etc?
Click to expand...
Click to collapse
No i do not
Mike02z said:
I have installed Adaway on at least 6 different Marshmellow ROM's with no issue.
Switch ROM and Kernels and see what happens.
Click to expand...
Click to collapse
Do you have a suggestion on a kernel? And id like to stay stock on the ROM if possible
Mike02z said:
Just FYI, this is a development area. You will have more luck posting in the Q&A section.
Click to expand...
Click to collapse
Ya sorry, i was tryng to post it quick on my phone and didnt look at all the options as to where the best place to post would be
Khizar said:
You seem to be using system less root, that's probably the issue. In the adaway thread there is a zip that must be flashed if you're using system less root.
Also questions belong in the Q&A section not dev section. I've reported the thread, a mod should move it but just letting you know for next time.
Click to expand...
Click to collapse
What is system less root if i may ask? and ill look for that zip you mentioned
*update* installed that zip. attempted to install and get the same error about s-off
@trbomp5 Adaway working flawless on systemless (2.66) rooted stock rom, @ OP do you have busybox installed?
Quote: *update* installed that zip. attempted to install and get the same error about s-off
What do you mean with s-off?
gee2012 said:
@trbomp5 Adaway working flawless on systemless (2.66) rooted stock rom, @ OP do you have busybox installed?
Quote: *update* installed that zip. attempted to install and get the same error about s-off
What do you mean with s-off?
Click to expand...
Click to collapse
Yes busybox is installed.
and if you look at the op youll see the screenshots where i get the s-off error message
trbomp5 said:
Yes busybox is installed.
and if you look at the op youll see the screenshots where i get the s-off error message
Click to expand...
Click to collapse
Symlink to /data/data/hosts in settings.
gee2012 said:
Symlink to /data/data/hosts in settings.
Click to expand...
Click to collapse
yes.
its seems fine till it says symlink missing. then when i click yes to create i get the symlink creation failed. like in the screenshot.
just tried it again
trbomp5 said:
yes.
its seems fine till it says symlink missing. then when i click yes to create i get the symlink creation failed. like in the screenshot.
just tried it again
Click to expand...
Click to collapse
Clear all Adaway data in /settings/apps/ and try again. It should work fine as it does for me. What rom/kernel/recovery are you running?
gee2012 said:
Clear all Adaway data in /settings/apps/ and try again. It should work fine as it does for me. What rom/kernel/recovery are you running?
Click to expand...
Click to collapse
cleared data and tried again same results.
stock rom, unlocked bootloader, kernel is 3.10.40-ElementalX-N6-3.00, twrp 2.8.7.1
Universal init.d install it from play store and follow instructions
miguelito18 said:
Universal init.d install it from play store and follow instructions
Click to expand...
Click to collapse
downloaded it, installed fine. Opened it, granted it SU and then it says "unfortunately, Universal init.d has stopped"
trbomp5 said:
downloaded it, installed fine. Opened it, granted it SU and then it says "unfortunately, Universal init.d has stopped"
Click to expand...
Click to collapse
I don't have an init.d folder as I run the stock kernel. There must be another problem.
I was facing the same problem, for every one trying to get adaway to work on android 6.0.1, follow these steps
Boot to TWRP recovery -> Mount system
adb shell
cd system
cd etc
rm hosts
ln -s /data/data/hosts /system/etc/hosts
In AdAway -> Settings -> hosts file to use is /data/data/hosts
gee2012 said:
I don't have an init.d folder as I run the stock kernel. There must be another problem.
Click to expand...
Click to collapse
ill find the guide i used to root and link it here to see if anyone see's a problem there
http://nexus5.wonderhowto.com/how-to/root-nexus-device-running-android-6-0-marshmallow-0165131/
Yasharkhan said:
I was facing the same problem, for every one trying to get adaway to work on android 6.0.1, follow these steps
Boot to TWRP recovery -> Mount system
adb shell
cd system
cd etc
rm hosts
ln -s /data/data/hosts /system/etc/hosts
In AdAway -> Settings -> hosts file to use is /data/data/hosts
Click to expand...
Click to collapse
just to clearify, those steps are all done in recovery? And im not the best at ADB on the computer, used to odin on samsung the last 3 years
any way i can get you to step by step these with all i need to do?
trbomp5 said:
ill find the guide i used to root and link it here to see if anyone see's a problem there
http://nexus5.wonderhowto.com/how-to/root-nexus-device-running-android-6-0-marshmallow-0165131/
Click to expand...
Click to collapse
Look in the stickies thread in general for how to root.
Usually what i do is:
Flash or boot into TWRP
Flash superuserSU
Install BusyBox
That's it as i use the stock rom, kernel and recovery. I just need root.
---------- Post added at 01:59 AM ---------- Previous post was at 01:57 AM ----------
trbomp5 said:
just to clearify, those steps are all done in recovery? And im not the best at ADB on the computer, used to odin on samsung the last 3 years
Click to expand...
Click to collapse
No, when the device is turned on.
Hi fellows ...
well, I did this (xposed module repository: description)
Phone: GT-I9070P Samsung Galaxy S Advance
OS: (4.4.4)OptiROM (i9070-i9070P), ROM for the Samsung Galaxy S Advance I9070
Xposed Modules 1.0.8
Xposed Installer 2.7 experimental1
RootCloak 3.0-beta_20160731_2
RootCloak Plus 1.2
SecureGo 1.42-03
SecureGo still realises that the phone is rooted ... so no banking possible :crying: Thanks for help
b*_gently_*d said:
Hi fellows ...
well, I did this (xposed module repository: description)
Phone: GT-I9070P Samsung Galaxy S Advance
OS: (4.4.4)OptiROM (i9070-i9070P), ROM for the Samsung Galaxy S Advance I9070
Xposed Modules 1.0.8
Xposed Installer 2.7 experimental1
RootCloak 3.0-beta_20160731_2
RootCloak Plus 1.2
SecureGo 1.42-03
SecureGo still realises that the phone is rooted ... so no banking possible [emoji14] :crying: Thanks for help
Click to expand...
Click to collapse
In rootcloak, did you specifically add the securego app to it's block list?
Sent from my SCH-R220
Hi there!
Yes, in "RootCloak Plus", the entry de.fiducia.smartphone.android.securego.wl does exist.
There's another confusing circumstance: I don't know how to launch the Xposed Installer programme. The only way - for me right now - is to navigate to "downloads", and then to re-install some downloaded *.apk as an update. Then, and only then, I'm inside the Xposed Installer.
Under "Remove native root detection for apps", the box "SecureGo" is checked.
b*_gently_*d said:
Hi there!
Yes, in "RootCloak Plus", the entry de.fiducia.smartphone.android.securego.wl does exist.
There's another confusing circumstance: I don't know how to launch the Xposed Installer programme. The only way - for me right now - is to navigate to "downloads", and then to re-install some downloaded *.apk as an update. Then, and only then, I'm inside the Xposed Installer. [emoji14]
Under "Remove native rott detection for apps", the box "SecureGo" is checked.
Click to expand...
Click to collapse
In your app drawer (if Xposed is properly unstalled) should be the Xposed app. After you install an Xposed module you have to activate the module in the Xposed app and reboot for it to work. Sounds like that hasn't been done. How did you install Xposed?
Sent from my SCH-R220
OK, let's have a look: I've got a sort of menu that is pushed from the left side into the app "Xposed modules". Within this menu drawer, there's: Modules, Install Xposed Framework, More modules, Root, XDA, latest 24 hours, all unread, all marked, downloads, synchronise now, settings (translated from German).
The apps "Xposed modules" and "RootCloak" are installed from stalk Google Play Store.
The device was restarted several times, and from a certain moment on, everytime it started, I had to confirm elevated privileges (for rootcloak).
:angel:
b*_gently_*d said:
OK, let's have a look: I've got a sort of menu that is pushed from the left side into the app "Xposed modules". Within this menu drawer, there's: Modules, Install Xposed Framework, More modules, Root, XDA, latest 24 hours, all unread, all marked, downloads, synchronise now, settings (translated from German).
The apps "Xposed modules" and "RootCloak" are installed from stalk Google Play Store.
The device was restarted several times, and from a certain moment on, everytime it started, I had to confirm elevated privileges (for rootcloak).
:angel:
Click to expand...
Click to collapse
Ok, that doesn't sound can you post a screenshot of what you are talking about including the list of modules installed in Xposed?
Sent from my SCH-R220
Pardon. What does it sound like? :cyclops: Anyway, I was wrong about the Installer. I actually can access it. But I still can't launch SecureGo properly. I'm posting a *.zip file containing a log and several shots.
b*_gently_*d said:
Pardon. What does it sound like? :cyclops: Anyway, I was wrong about the Installer. I actually can access it. But I still can't launch SecureGo properly. I'm posting a *.zip file containing a log and several shots.
Click to expand...
Click to collapse
Sorry, didn't notice the typo, it looks like you are using and old version of Xposed and a BETA version of rootcloak, have you tried the stable version?
Sent from my SCH-R220
Let's have a look on what has changed:
uninstalled the beta and experimental versions
now, there's only one "RootCloak" v2.1.1 (and no longer a "RootCloak Plus" next to it), downloaded and installed from "Xposed Installer"
downloaded and installed the *.apk of "Xposed Installer" v2.6.1
I took the version numbers from the Android OS settings menu
the icon for "Xposed Modules" is no longer shown
however, I did not remove SecureGo while making changes.
I didn't have to grant elevated privileges (only when Xposed Installer installed RootCloak)
I'm posting the latest log-file!
Still not working ...
b*_gently_*d said:
Let's have a look on what has changed:
uninstalled the beta and experimental versions
now, there's only one "RootCloak" v2.1.1 (and no longer a "RootCloak Plus" next to it), downloaded and installed from "Xposed Installer"
downloaded and installed the *.apk of "Xposed Installer" v2.6.1
I took the version numbers from the Android OS settings menu
the icon for "Xposed Modules" is no longer shown
however, I did not remove SecureGo while making changes.
I didn't have to grant elevated privileges (only when Xposed Installer installed RootCloak)
I'm posting the latest log-file!
Still not working ...
Click to expand...
Click to collapse
Have you taken a look at this, maybe this could help : http://forum.xda-developers.com/showthread.php?t=3450396
Sent from my SCH-R220
Quoting the article linked above: "Requirements ... Android 6.0" ... Don't know if an OS-installation would defeat the object ...
b*_gently_*d said:
Quoting the article linked above: "Requirements ... Android 6.0" ... Don't know if an OS-installation would defeat the object ...
Click to expand...
Click to collapse
It would allow you to utilize this workaround
Sent from my SCH-R220
I don't even see the mere possibility to install Android 6 ... Or do you detect anything on the specific page?
b*_gently_*d said:
I don't even see the mere possibility to install Android 6 ... Or do you detect anything on the specific page?
Click to expand...
Click to collapse
b*_gently_*d said:
Hi fellows ...
well, I did this (xposed module repository: description)
Phone: GT-I9070P Samsung Galaxy S Advance
OS: (4.4.4)OptiROM (i9070-i9070P), ROM for the Samsung Galaxy S Advance I9070
Xposed Modules 1.0.8
Xposed Installer 2.7 experimental1
RootCloak 3.0-beta_20160731_2
RootCloak Plus 1.2
SecureGo 1.42-03
SecureGo still realises that the phone is rooted ... so no banking possible [emoji14] :crying: Thanks for help
Click to expand...
Click to collapse
Check the thread for your device, a quick Google search shows some MM ROMs for your GT-I9070P
Sent from my SCH-R220
still failure
Inspired by your previous posts and having followed your advice, I now have a phone running Android 6.0.1 Marshmallow.
I tried to install Suhide and SuperSU systemlessly [?] (or at least I think, I did it that way because I was in Recovery Mode/TWRP. There, I simply clicked "install" and did nothing but install both zip-files.
The line that stated, that a boot image had not been found and therefore the process was aborting patching the boot.img, attracted my attention.
Within the restarted Android-OS, I never found an app icon for SuperSU or Suhide. Nevertheless, I found out SecureGo's UID (10xxx) and gave the following command:
Code:
/data/adb/suhide-add 10xxx
for adding SecureGo to the blacklist.
But nothing has changed ... SecureGo still denies its job.
b*_gently_*d said:
Inspired by your previous posts and having followed your advice, I now have a phone running Android 6.0.1 Marshmallow.
I tried to install Suhide and SuperSU systemlessly [?] (or at least I think, I did it that way because I was in Recovery Mode/TWRP. There, I simply clicked "install" and did nothing but install both zip-files.
The line that stated, that a boot image had not been found and therefore the process was aborting patching the boot.img, attracted my attention.
Within the restarted Android-OS, I never found an app icon for SuperSU or Suhide. Nevertheless, I found out SecureGo's UID (10xxx) and gave the following command:
Code:
/data/adb/suhide-add 10xxx
for adding SecureGo to the blacklist.
But nothing has changed ... SecureGo still denies its job.
Click to expand...
Click to collapse
Check the suhide thread, other people have the same sort of issue, in that you are using CM SuperSU that is not systemless, need to disable it for systemless su to work
Sent from my SCH-R220
By "CM SuperSU", do you mean Cyanogenmod S.SU? Are there versions different to Chainfire's one?
I realised that, in TWRP, I can also give commands in a terminal (surprise :good. But I do believe this is Busybox ... read it somewhere, but can't tell where or when exactly.
Do I need ADB installed? I'm asking because it appears in the commands.
I noticed that, when running the Android-OS, Jack Palevich's "Terminal Emulator" is not rooted (showing $ instead of #).
But the strangest thing of all is: I cannot detect any signs that suhide or supersu are installed ... how could I possibly check this?
b*_gently_*d said:
By "CM SuperSU", do you mean Cyanogenmod S.SU? Are there versions different to Chainfire's one?
Click to expand...
Click to collapse
Yes, at least how it's implemented in the ROM
[*]I realised that, in TWRP, I can also give commands in a terminal (surprise :good. But I do believe this is Busybox ... read it somewhere, but can't tell where or when exactly.
Click to expand...
Click to collapse
Is your Busybox up to date?
[*]Do I need ADB installed? I'm asking because it appears in the commands.
Click to expand...
Click to collapse
If you have to issue these commands from your computer to the phone you would need ADB on your computer. Is ADB turned on in developer options?
[*]I noticed that, when running the Android-OS, Jack Palevich's "Terminal Emulator" is not rooted (showing $ instead of #).
Click to expand...
Click to collapse
Did you type su in Terminal Emulator?
[*]But the strangest thing of all is: I cannot detect any signs that suhide or supersu are installed ... how could I possibly check this?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Give me some time, I'll do a backup and see what you are seeing.
Sent from my SCH-R220
---------- Post added at 12:33 PM ---------- Previous post was at 12:11 PM ----------
b*_gently_*d said:
By "CM SuperSU", do you mean Cyanogenmod S.SU? Are there versions different to Chainfire's one?
I realised that, in TWRP, I can also give commands in a terminal (surprise :good. But I do believe this is Busybox ... read it somewhere, but can't tell where or when exactly.
Do I need ADB installed? I'm asking because it appears in the commands.
I noticed that, when running the Android-OS, Jack Palevich's "Terminal Emulator" is not rooted (showing $ instead of #).
But the strangest thing of all is: I cannot detect any signs that suhide or supersu are installed ... how could I possibly check this?
Click to expand...
Click to collapse
In looking at Chainfire's thread to install Systemless root, I discovered that there are special boot.img files that need to be flash, my device is not on that list. But he does have some things that might shed some light on the issue.
1) Is your device one of the supported devices?
2) If so, did you do a clean flash? Did you flash the boot.img and su zips immediately? The thread says you need to make sure to flash the systemless stuff before the built in su does anything because the systemless flashing doesn't clean up other root implementations and can create problems. That's why it is mandatory for a clean flash of the ROM.
3) After you do all that, install the SuperSU app from the play store and see what happens
Sent from my SCH-R220
I don't know how to check whether Busybox is up to date or not (I was talking about the TWRP-Terminal outside Android-OS).
When I type 'su' into the Terminal Emulator - similarly to GNU/Linux -, I have no longer got the first line, but the second of the following:
Code:
[email protected]:/ $ su
1|[email protected]:/ $ sudo
/system/bin/sh: sudo: not found
127|[email protected]:/ $
(This is a true quote from my in-OS terminal.)
I'll have to look for those boot images and the list of the supported devices ... Or would you give me a direct link? (I already gave the exact name of my device.)
What exactly is a "clean flash", and which *.img or *.zips would have to be flashed? Do you mean something like from my own smarty history? From this list I basically only did step 4 when installing MM/CM13.
There's something else: Under "Developers' options/settings" (don't know how it is in English), you can choose between "never", "when debugging via USB" and "when loading". Has this something to say?
Please give me a short reply if I should perform the whole list of steps or similar or not because I don't want to waste time only to repeat it again and again
b*_gently_*d said:
I don't know how to check whether Busybox is up to date or not (I was talking about the TWRP-Terminal outside Android-OS).
When I type 'su' into the Terminal Emulator - similarly to GNU/Linux -, I have no longer got the first line, but the second of the following:
Code:
[email protected]:/ $ su
1|[email protected]:/ $ sudo
/system/bin/sh: sudo: not found
127|[email protected]:/ $
(This is a true quote from my in-OS terminal.)
I'll have to look for those boot images and the list of the supported devices ... Or would you give me a direct link? (I already gave the exact name of my device.)
What exactly is a "clean flash", and which *.img or *.zips would have to be flashed? Do you mean something like from my own smarty history? From this list I basically only did step 4 when installing MM/CM13.
There's something else: Under "Developers' options/settings" (don't know how it is in English), you can choose between "never", "when debugging via USB" and "when loading". Has this something to say?
Please give me a short reply if I should perform the whole list of steps or similar or not because I don't want to waste time only to repeat it again and again
Click to expand...
Click to collapse
http://forum.xda-developers.com/app...rshmellow-t3219344/post63197935#post63197935
Sent from my SCH-R220
Disclaimer: I will take no responsibility if flashing this zip somehow causes you to go deaf, scares your cat, receiving of noise complaints from your neighbors, development of anti-social behavior, getting hit by a bus, a twerking grandmother, broken windows and/or any other imaginable royally screwed possibility.
Q: Will this work on other Samsung devices?
A: Maybe, I see no reason for it not to work on the S8 or S8+. Feel free to test it out and report back.
Credits: @zhuhang for ViPER4Android FX & XHiFI.
@partcyborg, @me2151, and @elliwigy for hooking us up with root.
Features: Systemwide ViPER4Android FX 2.3.4.0 (higher audio processing than newer versions) and ViPER4Android XHiFi.
Installation steps (make sure to read these before downloading the ZIP):
1) Make sure you're rooted.
2) Download either FlashFire (Snapdragon - thank you, @Chainfire) or install TWRP (Exynos).
3) Install BusyBox, to /system/xbin (otherwise, XHiFi will not work, only FX will).
4) Get Titanium Backup, ROM Toolbox PRO, or any similar application.
6) Freeze "Adapt Sound" and "SoundAlive".
5) Flash the attached zip.
6) Grant root permissions to both FX and XHiFi (you might have to uninstall the FX driver within the in-app settings to trigger this, if so, simply reflash the ZIP after having done so and reboot).
7) Reread step six.
8) Profit & enjoy.
Paradoxumical said:
Disclaimer: I will take no responsibility if flashing this zip somehow causes you to go deaf, scares your cat, receiving of noise complaints from your neighbors, development of anti-social behavior, getting hit by a bus, a twerking grandmother, broken windows and/or any other imaginable royally screwed possibility.
Q: Will this work on other Samsung devices?
A: Maybe, I see no reason for it not to work on the S8 or S8+. Feel free to test it out and report back.
Credits: @zhuhang for ViPER4Android FX & XHiFI.
@partcyborg, @me2151, and @elliwigy for hooking us up with root.
Features: Systemwide ViPER4Android FX 2.3.4.0 (higher audio processing than newer versions) and ViPER4Android XHiFi.
Installation steps (make sure to read these before downloading the ZIP):
1) Make sure you're rooted.
2) Download either FlashFire (Snapdragon - thank you, @Chainfire) or install TWRP (Exynos).
3) Install BusyBox, to /system/xbin (otherwise, XHiFi will not work, only FX will).
4) Get Titanium Backup, ROM Toolbox PRO, or any similar application.
6) Freeze "Adapt Sound" and "SoundAlive".
5) Flash the attached zip.
6) Grant root permissions to both FX and XHiFi (you might have to uninstall the FX driver within the in-app settings to trigger this, if so, simply reflash the ZIP after having done so and reboot).
7) Reread step six.
8) Profit & enjoy.
Click to expand...
Click to collapse
Won't installing busybox to system/xbin trip up safety net flagging your device as tampered/rooted? Also, if you have magisk, can't you just install the v4a module right from within magisk? I don't see the point in going through all these extra steps and flagging your device in safety net when you can just install the v4a magisk module. Not trying to be a ****, asking honest questions.
Works perfectly on my T-Mobile N950U! Thanks!
Sent from my SM-N950U1 using Tapatalk
xxx42069 said:
Won't installing busybox to system/xbin trip up safety net flagging your device as tampered/rooted? Also, if you have magisk, can't you just install the v4a module right from within magisk? I don't see the point in going through all these extra steps and flagging your device in safety net when you can just install the v4a magisk module. Not trying to be a ****, asking honest questions.
Click to expand...
Click to collapse
If you have a Snapdragon device, SafetyNet is already tripped due to the nature of the rooting process.
But if you have an Exynos device, by all means, use the Magisk module. This ZIP was intended for the Snapdragon variant (since that's what I have), but works on Exynos variants as well.
i flashed it n nuthin,i cant even find the in-app u wrote about
Was anyone able to install busybox and viper4android after getting rooted? I tried flashing the viper4android zip using flashfire but it doesn't seem to do anything and busybox installer will not install to any system location. Thanks in advance. Also, I have the snapdragon version and rooted using samfail.
lilviet93 said:
Was anyone able to install busybox and viper4android after getting rooted? I tried flashing the viper4android zip using flashfire but it doesn't seem to do anything and busybox installer will not install to any system location. Thanks in advance. Also, I have the snapdragon version and rooted using samfail.
Click to expand...
Click to collapse
same problem with me i flashed it n nothing happened..also u need to use busybox root it's the red icon version u probably using the old gray busybox
mister_propa said:
same problem with me i flashed it n nothing happened..also u need to use busybox root it's the red icon version u probably using the old gray busybox
Click to expand...
Click to collapse
Yeah, I used the old busybody version. I just went back to stock after a few hours of messing around with no results. My main reason for root and accepting the 80% battery limit is viper but since I can't get it working I went back to stock for now. Will try again once there is more development. Let me know if you do get it working.
mister_propa said:
i flashed it n nuthin,i cant even find the in-app u wrote about
Click to expand...
Click to collapse
mister_propa said:
same problem with me i flashed it n nothing happened..also u need to use busybox root it's the red icon version u probably using the old gray busybox
Click to expand...
Click to collapse
lilviet93 said:
Was anyone able to install busybox and viper4android after getting rooted? I tried flashing the viper4android zip using flashfire but it doesn't seem to do anything and busybox installer will not install to any system location. Thanks in advance. Also, I have the snapdragon version and rooted using samfail.
Click to expand...
Click to collapse
When you guys flashed it with Flashfire, which options did you enable/disable? Mind taking a screenshot of the preflash stage for me? Do you see the Flashfire installation screen? You should be able to see the ZIP flash progress script.
As for those having problems with installing BusyBox, if you're using Stericson's, you have to manually grant the storage permission.
Paradoxumical said:
When you guys flashed it with Flashfire, which options did you enable/disable? Mind taking a screenshot of the preflash stage for me? Do you see the Flashfire installation screen? You should be able to see the ZIP flash progress script.
As for those having problems with installing BusyBox, if you're using Stericson's, you have to manually grant the storage permission.
Click to expand...
Click to collapse
Just select the zip and start the flashing process. It went black then the flashfire process starts then phone reboots but no sign of the viper app anywhere. How do I manually grant permission? What is the best way to install busybox?
lilviet93 said:
Just select the zip and start the flashing process. It went black then the flashfire process starts then phone reboots but no sign of the viper app anywhere. How do I manually grant permission? What is the best way to install busybox?
Click to expand...
Click to collapse
I personally used BusyBox Pro by Stericson (he's an amazing developer), but I did have to manually grant the storage permission first by going to: App info > Permissions > Storage (toggle it on).
If this doesn't work, use BusyBox Installer (warning: it's riddled with ads).
As for Flashfire, try enabling the "mount system read/write" option.
Paradoxumical said:
I personally used BusyBox Pro by Stericson (he's an amazing developer), but I did have to manually grant the storage permission first by going to: App info > Permissions > Storage (toggle it on).
If this doesn't work, use BusyBox Installer (warning:it's riddled with ads).
As for Flashfire, try enabling the "mount system read/write" option.
Click to expand...
Click to collapse
Thank you for your help bro. I did what you said, busybox installed successfully. But after flashing with flashfire, even when checking mount, there's still no sign of viper after reboot
Sent from my SM-N950U1 using Tapatalk
kidbranz01 said:
Thank you for your help bro. I did what you said, busybox installed successfully. But after flashing with flashfire, even when checking mount, there's still no sign of viper after reboot
Sent from my SM-N950U1 using Tapatalk
Click to expand...
Click to collapse
That is the strangest thing, I can't imagine why the ViPER apps wouldn't show up. The only thing that comes to mind is... If you ran the fsck script after rooting, did you?
kidbranz01 said:
Thank you for your help bro. I did what you said, busybox installed successfully. But after flashing with flashfire, even when checking mount, there's still no sign of viper after reboot
Sent from my SM-N950U1 using Tapatalk
Click to expand...
Click to collapse
I had the same issue, but then in FlashFire, under settings I disabled Emulate framebuffer.. Now Viper4android is installed and working.
Does anyone who has this installed get freezes after reboots from time to time?
kirschdog1 said:
Does anyone who has this installed get freezes after reboots from time to time?
Click to expand...
Click to collapse
It freezes up all the time, even when requesting SU.
Sent from my SM-N950U using Tapatalk
Does anyone on Snapdragon have this and FM Radio working together? Unfortunately, I'm finding I can't run both. I don't know if it's my Viper settings or what. Any input would be appreciated as I don't want to have to choose between the two features if I don't have to
For those who had trouble on snapdragon try using latest Sam fail v2 if possible it works perfect on here if you follow directions. Few key things, disable emulate framebuffer in flashfire and when flashing enable mount read and write system, also make sure you install drivers in both v4a apps to enable root as root access is need for v4a to work properly after unistalling drivers and granting root reflash zip in flashfire to restore drivers and profit
I have problem with viper4android hifi can't read root access
jomolocco said:
I have problem with viper4android hifi can't read root access
Click to expand...
Click to collapse
If I remember correctly, there was something that said if you had this trouble, open app, uninstall the driver, Grant the permission, then re-flash the app.
Could someone please point me at instructions on how to root LN14.
I've searched the HD/HD+ forums for 'root LN14' and 'rooting LN14' and got no results (which by itself is suspicious).
have you enabled Developer Options?
I, for one, had no luck with either SuperSu or addon su. The first would put the HD+ into a permanent boot loop necessitating a re-install from scratch,and the latter would install but the unit still indicated it was not rooted. Doing the Dev Op made no difference. A real mystery!
harryzee said:
I, for one, had no luck with either SuperSu or addon su. The first would put the HD+ into a permanent boot loop necessitating a re-install from scratch,and the latter would install but the unit still indicated it was not rooted. Doing the Dev Op made no difference. A real mystery!
Click to expand...
Click to collapse
The file addonsu-14.1-arm.zip in the main folder is the one to use. As I seem to recall, you might have to enable, disable, then re-enable, in order for root access to take effect.
digixmax said:
The file addonsu-14.1-arm.zip in the main folder is the one to use. As I seem to recall, you might have to enable, disable, then re-enable, in order for root access to take effect.
Click to expand...
Click to collapse
That is the one I flashed using 3.0.1.0 TWRP. Not clear on your second sentence: "...enable, disable,, then re-enable...". Forgive me for being lost as to what you physically/specifically mean. Please explain.
Thanks.
harryzee said:
That is the one I flashed using 3.0.1.0 TWRP. Not clear on your second sentence: "...enable, disable,, then re-enable...". Forgive me for being lost as to what you physically/specifically mean. Please explain.
Thanks.
Click to expand...
Click to collapse
I meant "enable, disable,, then re-enable" the root access option in "Developer Options".
Aha! Will give it a go. Thanks.
5/2/2018:
Okay: I d/l three android root checkers and titanium backup. The first root checker (Clivin Inc. with small green android robot graphic) told me I was not rooted both before following your above instructions and after. The other two (d/l after following the above) both say I am rooted. However, I was not and am still not able to get "TB" to run. It says "failed" and that I am not rooted.
Since the HD+ is running really well now in its stripped down mode, I can "leave well enough alone" or try to get "TB" working so I can remove anything not needed for my chosen minimal functionality (ereader, viewing videos, photo review/minor editing) that would further reduce unnecessary battery drain.
Thanks again for the above clarification and any additional thoughts.
I am having this same problem
- Root options *do* appear in my Developer settings, but no amount of toggling on/off/on seems to enable root
- I have flashed the Lineage SU addon, log shows successful in TWRP but no change after boot
- SuperSU from Play Store says "SU Binary occupied"
- Adaway says "Rooted Android required- Either the su binary could not be found or you did not allow root permission for Adaway" ie I believe I am indeed *not* rooted.
- SuperSU flashable zip is a broken link on their website.... http://www.supersu.com/download
Out of ideas here, anyone got anything else I can try?
Edit: I was able to obtain Root properly by flashing Magisk & installing the Magisk Manager APK from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
You got it. Use Magisk. Works wonders and way better than SuperSU or any other root permission tool I've came across. It's even akin to, and even has within it, xposed and other magical rooted modules for you to try out for a day or two and then decide you don't need it.
pchc_lx said:
I am having this same problem
- Root options *do* appear in my Developer settings, but no amount of toggling on/off/on seems to enable root
- I have flashed the Lineage SU addon, log shows successful in TWRP but no change after boot
- SuperSU from Play Store says "SU Binary occupied"
- Adaway says "Rooted Android required- Either the su binary could not be found or you did not allow root permission for Adaway" ie I believe I am indeed *not* rooted.
- SuperSU flashable zip is a broken link on their website.... http://www.supersu.com/download
Out of ideas here, anyone got anything else I can try?
Edit: I was able to obtain Root properly by flashing Magisk & installing the Magisk Manager APK from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse