Database Develop

how to install busybox? :)

hello. i have flashed stock rom (1.23.708.3),and i want to use xposed statusbar. so the problem is whenever i wanr to apply the change in xposed statusbar,it directed me to playstore and ask me to install busybox.
so i went to install the busybox.apk from playstore,and then i open the apps,and try to install using smart install & normal install to the xbin,but both of them were unsuccesful.
my Butterfly s went to reboot but still cant use xposed status bar because busybox not installed.
and btw i already installed and updated the xposed framework.
can someone please explain to me how to install it? tq

among4239bulan said:
hello. i have flashed stock rom (1.23.708.3),and i want to use xposed statusbar. so the problem is whenever i wanr to apply the change in xposed statusbar,it directed me to playstore and ask me to install busybox.
so i went to install the busybox.apk from playstore,and then i open the apps,and try to install using smart install & normal install to the xbin,but both of them were unsuccesful.
my Butterfly s went to reboot but still cant use xposed status bar because busybox not installed.
and btw i already installed and updated the xposed framework.
can someone please explain to me how to install it? tq
Click to expand...
Click to collapse
The problem is most likely that the Butterfly S has some kind of write protection in place on the /system filesystem. You can circumvent this by installing it from recovery, you can use the following package I just built on my Butterfly S and put together:
http://amerhippus.x64.me/~johnny64/901S/busybox-DLXPUL-1.21.1-koniiiik.zip
This build contains just about every tool available in busybox, even those you most probably won't ever need.

koniiiik said:
The problem is most likely that the Butterfly S has some kind of write protection in place on the /system filesystem. You can circumvent this by installing it from recovery, you can use the following package I just built on my Butterfly S and put together:
http://amerhippus.x64.me/~johnny64/901S/busybox-DLXPUL-1.21.1-koniiiik.zip
This build contains just about every tool available in busybox, even those you most probably won't ever need.
Click to expand...
Click to collapse
thanks alot,it went well and now i can use sense toolbox and xposed statusbar. thanks also for the stock rom.:laugh:

Magisk (MagiskSU) - Busybox won't install, says "Systemless root is not configured".

Magisk (MagiskSU) - Busybox won't install, says "Systemless root is not configured".
I've installed/flashed the latest stable Magisk version: v13.2. (Since version v13.1 I believe the bundled busybox included with Magisk was removed because it caused a lot of issues)
I've tried to install BusyBox to "/su/xbin" but it always throws up the error "Systemless root is not configured".

bseos said:
I've installed/flashed the latest stable Magisk version: v13.2. (Since version v13.1 I believe the bundled busybox included with Magisk was removed because it caused a lot of issues)
I've tried to install BusyBox to "/su/xbin" but it always throws up the error "Systemless root is not configured".
Click to expand...
Click to collapse
Install Osm0sy's BusyBox zip on twrp (it's a magisk module as well). It works here.
You can find it at his official thread below:
https://forum.xda-developers.com/showthread.php?t=2239421

double_post

abacate123 said:
Install Osm0sy's BusyBox zip on twrp (it's a magisk module as well). It works here.
You can find it at his official thread below:
https://forum.xda-developers.com/showthread.php?t=2239421
Click to expand...
Click to collapse
Tried adding it as a module to Magisk however it reports it's not a magisk module "this zip is not a magisk module".
Flashed it with TWRP and it installed in su/xbin. Thanks :good:

abacate123 said:
Install Osm0sy's BusyBox zip on twrp (it's a magisk module as well). It works here.
You can find it at his official thread below:
https://forum.xda-developers.com/showthread.php?t=2239421
Click to expand...
Click to collapse
I flashed that zip in my Xperia XA and I'm still having the "systemless root is not configured". I need to install busybox in su/bin or su/xbin/ to make Viper4android work. Can u help me?

https://forum.xda-developers.com/android/software-hacking/tool-busybox-flashable-archs-t3348543

aocboe said:
https://forum.xda-developers.com/android/software-hacking/tool-busybox-flashable-archs-t3348543
Click to expand...
Click to collapse
But which do I install?

Evedammo said:
But which do I install?
Click to expand...
Click to collapse
Install "Busybox-1.27.1-YDS-ARM.zip" in the Magisk Manager

aocboe said:
Install "Busybox-1.27.1-YDS-ARM.zip" in the Magisk Manager
Click to expand...
Click to collapse
I've installed that. In the magisk modules it doesn't appear I flashed from TWRP, and I'm still having the "systemless root" message in busybox.

Evedammo said:
I've installed that. In the magisk modules it doesn't appear I flashed from TWRP, and I'm still having the "systemless root" message in busybox.
Click to expand...
Click to collapse
If you want to use it as a Magisk module, maybe you should install it from the Magisk Manager instead of flashing from TWRP.
Besides, I didn't catch your meaning. You mean the busybox app notice? Now that busybox is installed, you don't have to mind that notice.

Why are you guys trying to install to /su? Unless you're still on Magisk v12, you shouldn't be using SuperSU...

Rain X
I'm new, so I can't post links, but a youtuber named Rain X may have a solution. I tried his method and it worked for me:good:

Soumy1234 said:
I'm new, so I can't post links, but a youtuber named Rain X may have a solution. I tried his method and it worked for me:good:
Click to expand...
Click to collapse
What method would that be? No, I'm not gonna go hunting for some random Youtuber...
If the aim is to get a functioning busybox up and running, the easiest way is to just install @osm0sis busybox module from the downloads section in the Manager. No other apps needed...

He installed busybox in system/xbin
He made a folder called "Viper4Android" in the "system/priv-app" folder and copied a Viper4Android APK in there
He set the permissions of said APK to -rw-r--r-- (I set to -rwxrwxrwx for good measure)
He went to "system/vendor/etc" ("system/etc" if it's not there) folder, made a copy of the "audio_effects.conf" file
He renamed the "audio_effects.conf" file in the etc folder to "audio_effects.conf.bak"
He pasted the original "audio_effects.conf" file back in the "etc" folder, so now he has a "audio_effects.conf" and a "audio_effects.conf.bak" file in the "etc" folder
He changed the permissions of the "audio_effects.conf" file to "-rw-r--r--"
He rebooted, opened V4A, installed drivers, then rebooted
Hope this helped.

Didgeridoohan said:
What method would that be? No, I'm not gonna go hunting for some random Youtuber...
If the aim is to get a functioning busybox up and running, the easiest way is to just install @osm0sis busybox module from the downloads section in the Manager. No other apps needed...
Click to expand...
Click to collapse
I tried that,but it didn't work for me. If it doesn't work for you, I've already written some instructions on what the YouTuber did... Hope that helps.

Soumy1234 said:
I tried that,but it didn't work for me. If it doesn't work for you, I've already written some instructions on what the YouTuber did... Hope that helps.
Click to expand...
Click to collapse
That busybox module works perfectly for me.
And I'm using Magisk partly because it makes system modifications like V4A systemless. Therefore I would not follow those instructions...
I do have V4A working though, with this Magisk module and by utilising this workaround until the module has been updated. Nice and systemless...
The above mentioned workaround hasn't worked for everyone, but several other ways of getting it to work have been discussed in that thread.

Didgeridoohan said:
That busybox module works perfectly for me.
And I'm using Magisk partly because it makes system modifications like V4A systemless. Therefore I would not follow those instructions...
I do have V4A working though, with this Magisk module and by utilising this workaround until the module has been updated. Nice and systemless...
The above mentioned workaround hasn't worked for everyone, but several other ways of getting it to work have been discussed in that thread.
Click to expand...
Click to collapse
Oh, okay. Can you at least tell me how much the BusyBox zip work for you? I tried installing it through Magisk and TWRP, but it gave some errors.

Soumy1234 said:
Oh, okay. Can you at least tell me how much the BusyBox zip work for you? I tried installing it through Magisk and TWRP, but it gave some errors.
Click to expand...
Click to collapse
You'll need to provide some details for that... After flashing the module in TWRP, can you save the recovery log (Advanced - Copy log) and attach it to a post here.
And I forgot to say, but for the V4A module I linked, I don't even need busybox installed. YMMV...

Didgeridoohan said:
You'll need to provide some details for that... After flashing the module in TWRP, can you save the recovery log (Advanced - Copy log) and attach it to a post here.
And I forgot to say, but for the V4A module I linked, I don't even need busybox installed. YMMV...
Click to expand...
Click to collapse
Funny. It seemed to work this time. The last time I tried it literally said it failed.

Soumy1234 said:
Funny. It seemed to work this time. The last time I tried it literally said it failed.
Click to expand...
Click to collapse
Doesn't look like it succeeded when looking at the log...
What's the error message when you install through the Manager?

Using Link2SD on the R1HD?

Has anyone got Link2SD to work on the R1 HD? It always seems to give the error: mount script cannot be created "mount:No such file or directory" when trying to create mount script. Any ideas what going on.?

darkensx said:
Has anyone got Link2SD to work on the R1 HD? It always seems to give the error: mount script cannot be created "mount:No such file or directory" when trying to create mount script. Any ideas what going on.?
Click to expand...
Click to collapse
yes. the android toybox/ toolbox used by blu has been altered and the mount function is not working properly. Same issue some have had with adaway, and other mods. The solution should be to install busybox and fully symlink it to /sbin.
I have not done it but based on your reported error it should be the correct solution.
old disscussion about "mount" linked here.
https://forum.xda-developers.com/showpost.php?p=71359910&postcount=201

mrmazak said:
yes. the android toybox/ toolbox used by blu has been altered and the mount function is not working properly. Same issue some have had with adaway, and other mods. The solution should be to install busybox and fully symlink it to /sbin.
I have not done it but based on your reported error it should be the correct solution.
old disscussion about "mount" linked here.
https://forum.xda-developers.com/showpost.php?p=71359910&postcount=201
Click to expand...
Click to collapse
Where should BusyBox be installed? ( mines currently in /system/xbin ) which BusyBox is best for this solution? ( mines v1.27.1.YDS )

darkensx said:
Where should BusyBox be installed? ( mines currently in /system/xbin ) which BusyBox is best for this solution? ( mines v1.27.1.YDS )
Click to expand...
Click to collapse
that should be correct. I made typo , didnt mean "sbin" meant "xbin"

mrmazak said:
that should be correct. I made typo , didnt mean "sbin" meant "xbin"
Click to expand...
Click to collapse
Ok so what should be symlink then I thought busybox install took care of the symlinking. What's the command too? Also I'm trying to use Link2SD instead of the lovely Android m adoptive sdcard stuff basically keep sd as portable while using Link2SD so I can have my PC see the fat32 partition if i needed.

darkensx said:
Ok so what should be symlink then I thought busybox install took care of the symlinking. What's the command too? Also I'm trying to use Link2SD instead of the lovely Android m adoptive sdcard stuff basically keep sd as portable while using Link2SD so I can have my PC see the fat32 partition if i needed.
Click to expand...
Click to collapse
the symlinking is done from in the bustbox installer.
so, you still have problem with busybox installed?
not so sure what to try next. Ah, check in the list of installed links for busybox and see if "mount" is shown as installed.
you can try to install the "toybox" from V12. It is untested method and you would need to know how to undo if needed.
link to the twrp install of that file is in my earlier post.

mrmazak said:
the symlinking is done from in the bustbox installer.
so, you still have problem with busybox installed?
not so sure what to try next. Ah, check in the list of installed links for busybox and see if "mount" is shown as installed.
you can try to install the "toybox" from V12. It is untested method and you would need to know how to undo if needed.
link to the twrp install of that file is in my earlier post.
Click to expand...
Click to collapse
Got it to work had to tell BusyBox installer to overwrite and symlink it apparently it's unchecked by default as its "not recommended to replace the systems version" :silly: go figure maybe under normal circumstances with a correctly functioning mount its bad but it fixed it stericson BusyBox installer did others weren't tested but I assume same result. But thanks for your help greatly appreciated it.

Just a note to anyone who comes across this thread if you use Titanium Backup at all don't use "BusyBox X" it seems to break T.B.'s ability to detect root this might be just magisk... or both SuperSU and magisk. but i had this happen with other devices some on SuperSU Some magisk but un-install "BusyBox X" (install any other busybox) and problem goes away not sure what direct cause is in "BusyBox X" might be because X is 1.26.1 and others are 1.27.1 ( ATM ) seems its always one version behind.

darkensx said:
Just a note to anyone who comes across this thread if you use Titanium Backup at all don't use "BusyBox X" it seems to break T.B.'s ability to detect root this might be just magisk... or both SuperSU and magisk. but i had this happen with other devices some on SuperSU Some magisk but un-install "BusyBox X" (install any other busybox) and problem goes away not sure what direct cause is in "BusyBox X" might be because X is 1.26.1 and others are 1.27.1 ( ATM ) seems its always one version behind.
Click to expand...
Click to collapse
magisk is working well in the r1?

dark8899 said:
magisk is working well in the r1?
Click to expand...
Click to collapse
yes but because of the way we have to initially unlock/root the r1 it doesn't pass safety net with magisk unless android is not passing safety net again with magisk. but like i mentioned some things can break root "busy box X" with certain apps. also xposed framework systemless and normal seem to work well.

[SNAPDRAGON][EXYNOS] ViPER4Android [ZIP][FLASHABLE]

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.

[Guide][Magisk]Viper4Android on OOS Oreo with Magisk. (Easy Method)

Hello all ,
Update August 7th 2018.
Wirh recent versions of v4a , theres no need to use this method unless you tried the latest official v4a magisk module or zip and it didn't work, current v4a magaik module works perfectly with latest 5.0.4 stable rom and all betas from oos, and moat if not all 8.1 custom roms
The following is not necessary as of August 7th 2018, unless you tried official zip or module and faced issues:
a lot are asking and searching for a way to make V4A work on OOS Oreo, sadly so far most posible ways either require a lot work or setting Linux to permissive wich breaks saftynet.
the bad news is this method also Sets SELinun to Permissive but it's simulated through Magisk so it doesn't break SafetyNet...
Method:
1- download and install busybox (make sure it's installed) i personally use a pro version, some of the ones on playstore wont install so try until you find a working one.
2- Update , using the latest V4A 2.5+ version by ahrion you don't need to use Magisk SELinux Permissive Scrip because he added to his module a detection script that will detect OOS Oreo and set permissive automatically
Download and flash LatestViPER4Android FX 2.5.0.5 [Unity/AML] by @ahrion
3-reboot and have fun
if the above doesn't work
2a- download and install Magisk SELinux Permissive Script module v1.1 (all thanks to @Jman420 ) and reboot.
3a- download ViPER4Android FX 2.3.4.0 (Super High Quality) v2.1
4a- install V4A module downloaded in the past step then reboot.
5a- now V4A should be perfectly working...and It Passes SafetyNet
Screens Attached.

Excellent job, works like a charm with oos 5.
Big thx!

is bluetooth also working on this method?

I have tried your method but V4A is still not working. Thanks anyway

NOSTALGIA said:
is bluetooth also working on this method?
Click to expand...
Click to collapse
yes, it's specifically for Bluetooth
Soerdroid said:
I have tried your method but V4A is still not working. Thanks anyway
Click to expand...
Click to collapse
make sure Busybox app is installed and open it and inside it click install, the app itself has to install somethings... there's no reason for it not to work, if you've done that and it's not working please share a screen of v4a driver status while playing music .

It didn't worked for me either

Works fine!

weriwd said:
It didn't worked for me either
Click to expand...
Click to collapse
Working fine here, after following the instructions.
Be sure to Enable ViperFX in the UI (Master Power) as well.

Gamm86 said:
Working fine here, after following the instructions.
Be sure to Enable ViperFX in the UI (Master Power) as well.
Click to expand...
Click to collapse
Well for me the drivers just wont install. Which app are you using for busybox? I think this is causing the problem.

weriwd said:
Well for me the drivers just wont install. Which app are you using for busybox? I think this is causing the problem.
Click to expand...
Click to collapse
Busybox for Android by JRummy Apps

Gamm86 said:
Busybox for Android by JRummy Apps
Click to expand...
Click to collapse
Nope not working again . Drivers wont install for some reason.

weriwd said:
Nope not working again . Drivers wont install for some reason.
Click to expand...
Click to collapse
Have you correctly installed the zip's through Magisk modules?

Gamm86 said:
Have you correctly installed the zip's through Magisk modules?
Click to expand...
Click to collapse
Well I am just flashing them through Magisk what could I mess up

weriwd said:
Well I am just flashing them through Magisk what could I mess up
Click to expand...
Click to collapse
You could have tried flashing them in recovery.
Anyway, I'm sorry to inform you I'm out of ideas.

Gamm86 said:
You could have tried flashing them in recovery.
Anyway, I'm sorry to inform you I'm out of ideas.
Click to expand...
Click to collapse
It's not a big deal. I will wait for stable release. Thank you for the help anyways.

I flash viper4arise (Deuteronomy 2.4), it contains viper4android 2.5.0.5. To get it to work with selinux enforcing I used to install the magisk module Allow audio server on Nougat (https://forum.xda-developers.com/on...sk-modules-oneplus-3t-t3548446/post70819460). On Oreo I doesn't work anymore. Now I set selinux to permissive in developer settings in viper. It'll last till you reboot, then selinux is enforcing again.
Link to viper4arise: https://forum.xda-developers.com/an...stems-auditory-research-t3379709/post71959306
Downloadlink: https://androidfilehost.com/?w=files&flid=146718

weriwd said:
Nope not working again . Drivers wont install for some reason.
Click to expand...
Click to collapse
Sadly jrummy app is the one that works for me too, i use the pro version...
Make sure it has root access , and maybe try to change the installation directory
You can try the buaybox module fromt he following thread
https://forum.xda-developers.com/oneplus-3t/themes/magisk-magisk-modules-oneplus-3t-t3548446
You may also want to check the following
http://support.jrummyapps.com/topic/magisk

This works on OP3 with Magisk and is 2.5.0.5...
Install the APK separately.

skymera said:
This works on OP3 with Magisk and is 2.5.0.5...
Install the APK separately.
Click to expand...
Click to collapse
Can you also upload the apk? There are a lot of apks with ads.. Thank you

theduke7 said:
Hello all ,
a lot are asking and searching for a way to make V4A work on OOS Oreo, sadly so far most posible ways either require a lot work or setting Linux to permissive wich breaks saftynet.
the bad news is this method also Sets SELinun to Permissive but it's simulated through Magisk so it doesn't break SafetyNet...
Method:
1- download and install busybox (make sure it's installed) i personally use a pro version, some of the ones on playstore wont install so try until you find a working one.
2- download and install Magisk SELinux Permissive Script module v1.1 (all thanks to @Jman420 )
3-reboot
4- download ViPER4Android FX 2.3.4.0 (Super High Quality) v2.1 (i couldn't get the 2.5.0.5 version to work, if someone has a module of that version that works please mention it and i'll add it here as well)
5- install V4A module downloaded in the past step then reboot.
6- now V4A should be perfectly working...and It Passes SafetyNet
Screens Attached.
Click to expand...
Click to collapse
Вот кажется работает
https://drive.google.com/file/d/1Q3uzrZLpn9kK9O_YKA4GJ31YxO5gQt0X/view?usp=drivesdk