Related
Did anyone of you got Viper4Android working on the unified builds of LineageOS for the 3T? And if so could you explain how? I tried the flashable zips of Viper4Arise but the driver was unsupported everytime and when i installed the Viper apk, installed the drivers and rebooted the app asked me again to install drivers and so on.
Thanks in advance
mittey68 said:
Did anyone of you got Viper4Android working on the unified builds of LineageOS for the 3T? And if so could you explain how? I tried the flashable zips of Viper4Arise but the driver was unsupported everytime and when i installed the Viper apk, installed the drivers and rebooted the app asked me again to install drivers and so on.
Thanks in advance
Click to expand...
Click to collapse
Install Magisk as your root solution, not SuperSU and install the module for Viper from the "downloads" section of the Magisk Manager (you will need to update Magisk Manager from play store). Reboot. After reboot, get a root file explorer and follow the instructions here: https://forum.xda-developers.com/oneplus-3t/themes/v4a-fix-processing-using-magisk-t3572819
Reboot Again. Then download the official Viper APK from: http://www.mediafire.com/file/xonl4jha2e4vez1/ViPER4Android_FX_v2505.zip (official link is from http://vipersaudio.com/blog/?page_id=48) and install it.
Done
I would clean install your rom to get rid of any existing system installs of Viper4arise or similar though. Dirty Flash should also work. @mittey68
manor7777 said:
Install Magisk as your root solution, not SuperSU and install the module for Viper from the "downloads" section of the Magisk Manager (you will need to update Magisk Manager from play store). Reboot. After reboot, get a root file explorer and follow the instructions here: https://forum.xda-developers.com/oneplus-3t/themes/v4a-fix-processing-using-magisk-t3572819
Reboot Again. Then download the official Viper APK from: http://www.mediafire.com/file/xonl4jha2e4vez1/ViPER4Android_FX_v2505.zip (official link is from http://vipersaudio.com/blog/?page_id=48) and install it.
Done
I would clean install your rom to get rid of any existing system installs of Viper4arise or similar though. Dirty Flash should also work. @mittey68
Click to expand...
Click to collapse
Worked! Thanks man
mittey68 said:
Worked! Thanks man
Click to expand...
Click to collapse
Anytime! Can't take credit for the original find though
I flashed the latest SuperSU zip with TWRP to a MotoG 2015 with the latest Lineage. After that, I noticed that there is a native SuperSU for Lineage, which I would prefer to use.
I was not able to find a "remove" package so I uninstalled the SuperSU app from the launcher. Now I'm not sure if that really removed everything from the system because I installed it in the first place by flashing it with TWRP.
My question is, can I safely install the native SuperSU (by flashing with TWRP) or do I have to remove any files from the former SuperSU manually?
There's a full unroot option in the app. Reinstall from the Play store and run that...
Or if you have any issue with the unroot option in the app, you can always flash the unSU Script zip from here.
Didgeridoohan said:
There's a full unroot option in the app. Reinstall from the Play store and run that...
Click to expand...
Click to collapse
You're right, I did not see that before. Works pretty good, now I've installed the native SuperSU and everything works fine. Thank you.
Hello everyone, my question is simple: is there a way to install Viper4Android on Oxygen OS 5.x?
https://drive.google.com/file/d/1an_JvpfjR_KNQJYeidqKBTJJeL_Bnddj/view?usp=drivesdk
Should be rooted
Use test fix apk
Use oreo audio library
Gauravlonkar said:
https://drive.google.com/file/d/1an_JvpfjR_KNQJYeidqKBTJJeL_Bnddj/view?usp=drivesdk
Should be rooted
Use test fix apk
Use oreo audio library
Click to expand...
Click to collapse
test fix apk doesn't work... Always ask to install drivers.
Yes install the driver the screen will freez for some time until installation
Gauravlonkar said:
Yes install the driver the screen will freez for some time until installation
Click to expand...
Click to collapse
it does not work. I have already done it many times and when restarting it asks again to install the driver
Viper4Android requires permissive SELinux to work in OOS Oreo. Turn on developer mode in the Viper app and use it to switch SELinux status and see if Viper works (provided that you've already made the necessary changes to audio libraries). Your phone will reset SELinux every time it reboots though, so you will have to manually disable it again after every reboot. Alternatively, you can set up something like Tasker to automatically switch SELinux into permissive mode on reboot using the following shell command with superuser privaledge:
setenforce 0
Am using viper4android on oreo for weeks, follow these steps:
1) install magisk 14.3 in twrp and reboot (I reccomend latest blue_spark version of twrp), get magisk here
2) Install Magisk Manager, get it here
3) Download V4A from here
4) Go to Magisk Manager and click on Modules, click + icon and choose V4A zip you just downloaded, reboot device
5) you are done, enjoy working V4A
Nexus5-32GB said:
Am using viper4android on oreo for weeks, follow these steps:
1) install magisk 14.3 in twrp and reboot (I reccomend latest blue_spark version of twrp), get magisk here
2) Install Magisk Manager, get it here
3) Download V4A from here
4) Go to Magisk Manager and click on Modules, click + icon and choose V4A zip you just downloaded, reboot device
5) you are done, enjoy working V4A
Click to expand...
Click to collapse
Just curious... Why the Mega links? All those downloads are available through official sources.
Didgeridoohan said:
Just curious... Why the Mega links? All those downloads are available through official sources.
Click to expand...
Click to collapse
Of course they are. Get it wherever you want, it is your choice. This was faster way for me to include dl links and I can say that combination of these files works without any issue. I cannot guarantee when you get different version on V4A it will still work.
For example the V4A module available in Magisk Manager never worked for me on any Oreo rom.
Nexus5-32GB said:
Am using viper4android on oreo for weeks, follow these steps:
1) install magisk 14.3 in twrp and reboot (I reccomend latest blue_spark version of twrp), get magisk here
2) Install Magisk Manager, get it here
3) Download V4A from here
4) Go to Magisk Manager and click on Modules, click + icon and choose V4A zip you just downloaded, reboot device
5) you are done, enjoy working V4A
Click to expand...
Click to collapse
It didn't work for me. When I open Viper4Android and try to install the drivers, it gives me an I/O error.
https://drive.google.com/file/d/13OopG8QnHisqB0hyDflFS5EgJAG4xCjQ/view?usp=drivesdk
Try this one flash using TWRP and choose only v⁴a and Dolby other just skip or uninstall set Linux to permissive
And even if this doesn't work again flash and select uninstall for every option and try test fix APK it should fix io error
Markster93 said:
It didn't work for me. When I open Viper4Android and try to install the drivers, it gives me an I/O error.
Click to expand...
Click to collapse
Don't bother telling me it doesn't work when you clearly didn't follow the steps above. On top of that your ROM is already messed up. Start with clean flash and follow the steps above.
Gauravlonkar said:
https://drive.google.com/file/d/13OopG8QnHisqB0hyDflFS5EgJAG4xCjQ/view?usp=drivesdk
Try this one flash using TWRP and choose only v⁴a and Dolby other just skip or uninstall set Linux to permissive
And even if this doesn't work again flash and select uninstall for every option and try test fix APK it should fix io error
Click to expand...
Click to collapse
Thank you, I already solved with the classical procedure for Nougat, deleting audio_effects.conf and installing the test fix apk but with SELinux Mode Changer in order to set SELinux to permissive too.
Nexus5-32GB said:
Don't bother telling me it doesn't work when you clearly didn't follow the steps above. On top of that your ROM is already messed up. Start with clean flash and follow the steps above.
Click to expand...
Click to collapse
"don't bother"
Dude, calm down and relax.
"you clearly didn't follow the steps"
I followed every steps you wrote, and they didn't work for me. Did you watch me working with my phone?
"your ROM is already messed up"
No, you didn't watch me working with my phone, otherwise you would know I have the absolutely clean OxygenOS 5.0.
Too much arrogance.
Markster93 said:
It didn't work for me. When I open Viper4Android and try to install the drivers, it gives me an I/O error.
Click to expand...
Click to collapse
Of course you didn't follow my steps as this error you got never comes up when you use my files I have uploaded for you. There is no need to play with Linux mode nor the I/o fix etc. I have flashed these files on many oreo ROMs, in total like 30x and everytime works as a charm. So before you say something doesn't work, make yourself a favour and do a clean flash because clearly you didn't.
Only trying to help you.
I've only ever had viper working on Oreo on the 3t with SElinux permissive. there are other threads where others have said the same.
I've tried multiple v4a magisk modules all of which have given me abnormal status.
If you wish to get it working inside the following magisk modules
Magisk SElinux Permissive script
Viper4Android FX for magisk v14+
Apart from that I think we may have to wait for an update to fix the SElinux permissions for enforcing
Nexus5-32GB said:
Of course you didn't follow my steps as this error you got never comes up when you use my files I have uploaded for you. There is no need to play with Linux mode nor the I/o fix etc. I have flashed these files on many oreo ROMs, in total like 30x and everytime works as a charm. So before you say something doesn't work, make yourself a favour and do a clean flash because clearly you didn't.
Only trying to help you.
Click to expand...
Click to collapse
You don't understand me, or maybe you don't want to. I did a clean flash of the OxygenOS 5.0, then I flashed your Magsisk 14.3 zip. After that, I installed your Magisk Manager apk, and I added your Viper4Android module. Everytime I tried to open the Viper4Android app, it was always asking me to install the drivers, who always failed because of an I/O error.
So has anyone installed Viper succesfully? I tried Nexus5-32GB's solution, but the magisk module would not install, there was magisk_merge.img mount failed error.
Anova's Origin said:
Viper4Android requires permissive SELinux to work in OOS Oreo. Turn on developer mode in the Viper app and use it to switch SELinux status ...
Click to expand...
Click to collapse
Thanks a lot man. I followed your advice and V4A is working on OOS oreo
JiiJii said:
So has anyone installed Viper succesfully? I tried Nexus5-32GB's solution, but the magisk module would not install, there was magisk_merge.img mount failed error.
Click to expand...
Click to collapse
Try my solution. I followed the Nougat procedure, deleting audio_effects.conf and installing the test fix apk, but setting SELinux to permissive too.
V4A showing that to install driver I need to have Busybox, I installed BusyBox and the driver installed later rebooted. But again when I open it, It is asking to install driver and reboot. I am running V4A version 2.3.4.0, OOS 5 Magisk 14.6 and Manager 5.5.0.
Not able to find V4A developer mode, appreciate some help, please.
Hi guys.
I'm facing an issue with Magisk (stable and beta) that I never had before. I'm on OP5, PixelExperience, Android Pie (but I've tried also on a Oreo ROM yesterday, not sure if it was stable or beta version of Magisk). Here's the flash routine I do for every single ROM:
- Wipe everything, internal storage included
- Flash ROM
- Flash Magisk
- Boot
In the past few days, Magisk isn't installing MM, don't know why. It always installed MM on every single flash I did in my life, now suddenly it isn't installing it anymore. I haven't changed my flashing "habits", I do the exact steps I wrote above on every single flash (not on updates, of course).
This issue also leads to not being able to install modules from MM, but I can install them via TWRP (I've got the latest blu_spark, I'm decrypted, flashed no_verity_v2 for OP5). When I install modules via MM it says:
! /data/adb/magisk_merge.img mount failed.
I tried re-installing Magisk, using the uninstaller and then first time the stable, then the beta, but they won't installing MM after flashing.
What do you guys think?
Thanks.
EDIT: I've recreated the issue, I've attached the log. I tried 2 different modules, Sysconfig Patcher and Busybox. The first one is installing only via TWRP (via MM it produces the log in the attachments), the second one is istalling via MM correctly.
"update-binary: line 203: make_ext4fs: not found"
Unable to format the .IMG to ext4 it seems so there's no magisk merge image to be mounted
Not entirely sure where to go with that but it could be a start.
Bad version of twrp?
If I understand you correctly, the Busybox module install just fine, no matter if installed through the Manager or TWRP.
Have you tried other modules?
The Sysconfig Patcher module isn't using the official module template, so it's very likely that @VR25 need to fix something in his install script.
Didgeridoohan said:
If I understand you correctly, the Busybox module install just fine, no matter if installed through the Manager or TWRP.
Have you tried other modules?
The Sysconfig Patcher module isn't using the official module template, so it's very likely that @VR25 need to fix something in his install script.
Click to expand...
Click to collapse
Indeed, there's stuff to "fix". I've been working on that for a few days now. I noticed [some] recent ROMs lack a bunch of useful binaries, such as make_ext4fs and resize2fs. So, I'm migrating to Magisk Module Template and relying on Magisk's util_functions.sh for better "future-proof" compatibility.
Didgeridoohan said:
If I understand you correctly, the Busybox module install just fine, no matter if installed through the Manager or TWRP.
Have you tried other modules?
The Sysconfig Patcher module isn't using the official module template, so it's very likely that @VR25 need to fix something in his install script.
Click to expand...
Click to collapse
I tried YTVanced module, downloaded via MM and it installed just fine. So I think that, as VR25 said, the ROMs I've tried these days might have lacked of those utilities. So we might have "solved" this issue.
And what about the fact that flashing Magisk from TWRP doesn't install MM? Is it also related to the fact that those ROMs are recent?
Pipodi93 said:
And what about the fact that flashing Magisk from TWRP doesn't install MM? Is it also related to the fact that those ROMs are recent?
Click to expand...
Click to collapse
That happens once in a while, and may very well be ROM related. Fortunately, it's easy to install manually...
Didgeridoohan said:
That happens once in a while, and may very well be ROM related. Fortunately, it's easy to install manually...
Click to expand...
Click to collapse
Yeah, I thought so too. Because when I was on AICP, MM was installed after flashing. My concern was that "mount failed" was related to the fact that MM wasn't installed during the flashing operation, but I'm glad to see that's not the case and my phone isn't cursed. Thank you!
Since mm isn't working on new Magisk 19, I took it for inspiration and created a simple manager, just for bypass some "bootlooper" module.
Just install it using recovery and run on terminal /data/media/magisk.
v1.0 - Initial build. Enabling and disabling functions
v2.0 - Added module removal function
v2.5 - No need to use storage to work. May avoid issues. Some others minor changes.
All thanks to
- topjonhwu for Magisk
- VR25 for mm
- TWRP team
- Me? Idk
Great work dev[emoji106], thanks
doesn't works for me (doesn't list modules)
mrhamed said:
doesn't works for me (doesn't list modules)
Click to expand...
Click to collapse
To list modules the script needs to write on /cache or /data. It will choose by itself.
Please send some screenshot of issue.
Looks very promising, especially enjoy having a GUI for this.
mrhamed said:
doesn't works for me (doesn't list modules)
Click to expand...
Click to collapse
I'm working to make script use no external files, so script will depends completely on your recovery binaries.
Hope to release it soon.
I suffer a boot freeze because of a bad module.
Cannot use TWRP and don't have module like Magisk Core Only installed.
I cannot boot to rooted system because of bad module.
Can boot non-rooted system only.
For my device LYA (Mate 20 Pro) which for rooting is using root-through-recovery-boot I can patch boot image with whatever Magisk edition which I assume is the best way to recover the device without full wipe.
Can a Magisk version be easily built which will either skip loading custom modules or delete them during boot? After successfully booting rooted I would flash a standard Magisk.
mikeos said:
I suffer a boot freeze because of a bad module.
Cannot use TWRP and don't have module like Magisk Core Only installed.
I cannot boot to rooted system because of bad module.
Can boot non-rooted system only.
For my device LYA (Mate 20 Pro) which for rooting is using root-through-recovery-boot I can patch boot image with whatever Magisk edition which I assume is the best way to recover the device without full wipe.
Can a Magisk version be easily built which will either skip loading custom modules or delete them during boot? After successfully booting rooted I would flash a standard Magisk.
Click to expand...
Click to collapse
I don't know if I got it correctly.
Well... commonly modules won't survive after Magisk removal.
If you can't access TWRP for flash Magisk uninstaller or disable the problematic module, you can try to flash or even boot the ROM's stock kernel through fastboot.
But if such module did others modifications into data, so you'll have to reflash whole ROM.
Are you planning on publishing this on magisk repo?
This has saved my bacon at least 4 times since installing it, many thanks Adriano
Saved me from bootloop module, works like a charm!
Adriano-A3 said:
Since mm isn't working on new Magisk 19, I took it for inspiration and created a simple manager, just for bypass some "bootlooper" module.
Just install it using recovery and run on terminal /data/media/magisk.
v1.0 - Initial build. Enabling and disabling functions
v2.0 - Added module removal function
v2.5 - No need to use storage to work. May avoid issues. Some others minor changes.
All thanks to
- topjonhwu for Magisk
- VR25 for mm
- TWRP team
- Me? Idk
Click to expand...
Click to collapse
It gives me the error "WTF?! The directory was here just now! It's gone! Please try again... Exiting..."
Thx bro, you saved my day
PixelHead0_0 said:
It gives me the error "WTF?! The directory was here just now! It's gone! Please try again... Exiting..."
Click to expand...
Click to collapse
Same here, on Samsung S10+ with August update, latest Magisk and Twrp.
very useful for android 10, thank you sir !
I can't understand how to run it on the terminal
will it work with Magisk 20.0??
Sivabalan said:
will it work with Magisk 20.0??
Click to expand...
Click to collapse
have you tried it? does it work on magisk 20.1
Confirmed working with Magisk 20.1, thanks a ton for this!
working on 20.2 + android 10