Related
wich viper for android should i use,? i downloaded the apk one..how should i know its working i see no difference.?
raptorddd said:
wich viper for android should i use,? i downloaded the apk one..how should i know its working i see no difference.?
Click to expand...
Click to collapse
There is a thread about V4A for our G2
http://forum.xda-developers.com/showthread.php?t=2456073&page=79
post n. 783 is what you need and it will guide you here
http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137/post57021246#post57021246
and I suggest to use the zip file at the end of post 1 of Guitarhero page named:
ViperAudio 5.4 stock
don't use others version, no D+, no SonyBeats, because there are some issue in some cases, use the most basic zip file with only Viper and its driver.
When instaled in recovery simply open it and disable and reenable viper and it will be ok, simply try EQ or other setting and you will ear difference and in this case it works.
Romagnolo1973 said:
There is a thread about V4A for our G2
http://forum.xda-developers.com/showthread.php?t=2456073&page=79
post n. 783 is what you need and it will guide you here
http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137/post57021246#post57021246
and I suggest to use the zip file at the end of post 1 of Guitarhero page named:
ViperAudio 5.4 stock
don't use others version, no D+, no SonyBeats, because there are some issue in some cases, use the most basic zip file with only Viper and its driver.
When instaled in recovery simply open it and disable and reenable viper and it will be ok, simply try EQ or other setting and you will ear difference and in this case it works.
Click to expand...
Click to collapse
thanks let me see if am right .. downloaded
viperaudio 5.4 stock.. an thats ii? flash install drivers reboot and ready to go.?
raptorddd said:
thanks let me see if am right .. downloaded
viperaudio 5.4 stock.. an thats ii? flash install drivers reboot and ready to go.?
Click to expand...
Click to collapse
yes, if something goes wrong and no working go to 3 dots in Viper anuninstall driver from it. But 99% will be ok and Viper working. No use other zip with modded V4A because with Dorimanx kernel it will result some unexpected reboot (tested by me and dori too). With the simple Viper zip everithing is ok.
Welcome Guys!!!
Whats this for?:-
Many users face issues while installing V4A drivers on their device. Here is the ultimate fix for it.
Requirements:-
1. Root explorer like ES File Explorer.
2. The flashable zip of V4A.
3. Some knowledge about flashing, modifying system directory.
Procedure:-
1. Install busybox and make sure device is rooted properly.
2. Go to System > Vendor > Etc and check for the file named audio_effects.conf and copy it and paste it to System > etc (Overwrite).
3. (Not compulsory but do it if it doesn't work) Rename the System > Vendor > Etc > audio_effects.conf to audio_effects.conf.bak
4. Now flash the V4A zip in recovery and Voila!!
Please Hit Thanks If I Helped
How to add effects .irs files.
isas123 said:
How to add effects .irs files.
Click to expand...
Click to collapse
Pls google all that stuff. No off topic here.
Devam03 said:
Voila!!
Click to expand...
Click to collapse
thanks a bunch!
works like a charm (after few other unsuccessul methods)
latest miui.eu 7.2.24_v8-6.0 (kenzo)
ViperFX_2.5.0.5_by_guitardedhero
valuable post :good:
crullick said:
thanks a bunch!
works like a charm (after few other unsuccessul methods)
latest miui.eu 7.2.24_v8-6.0 (kenzo)
ViperFX_2.5.0.5_by_guitardedhero
valuable post :good:
Click to expand...
Click to collapse
Your welcome. Please hit thanks if I helped!
i still stuck at instal driver, it says i need to instal latest busybox
aldichuy said:
i still stuck at instal driver, it says i need to instal latest busybox
Click to expand...
Click to collapse
Did u install busybox?
Devam03 said:
Did u install busybox?
Click to expand...
Click to collapse
yes i have
edit: i just uninstal both and reinstall viper first and then the busybox, i did soft restart the phone before instal viper driver, and works
4. Now flash the V4A zip in recovery and Voila!!
Where is the V4A zip. I downloade zip from official site but ita just an apk file ???
nice effort
c_/\/\_k said:
nice effort
Click to expand...
Click to collapse
Thx. Hit the thanks button if i helped.
Hey everyone! I seem to have found put together 3 methods of installing/bypassing the V4A App on android. These methods include:
Regular Installation, and 2 Error bypasses/fixes.
If you get the error "superuser manager doesn't allow app to access su or you don't have root at all. fix this to use this selinuxmodechanger!", then you've come to the right place.
Requirements: ROOT, (maybe) TWRP (or anything you can flash the zip onto your phone with. With this tutorial I'll be using TWRP.)
If you don't have TWRP, here's the link to that \\ https://twrp.me/Devices/
Type in/select your device, click download, and flash it to your phone.
====================================================================================
Regular installation:
1.) Download V4A from Google Play Store \\ https://play.google.com/store/apps/details?id=com.vipercn.viper4android_v2_fx&hl=en
2.) Open, and grant root permission.
3.) Install drivers, and reboot phone. DONE!
==================================================================================================
V4A SuperSU Manager Error:
1.) Download V4A from Google Play Store (the newest one) \\ https://play.google.com/store/apps/details?id=com.vipercn.viper4android_v2_fx&hl=en
Open it, grant permissions, click "install drivers" <- just get through the driver menu. This is a troubleshoot test. If it fails, keep going on with the tutorial. If not, You're A-Okay.
2.) Download V4A Flashable ZIP from here \\ https://drive.google.com/file/d/0By-5wpCgi7OHMjFZRU1PYXljbDQ/view
Drag and drop from your computer onto your phone in your "Downloads" folder.
3.) Open TWRP and click "Install" and navigate to your "Downloads" folder where you Installed the V4A Flashable ZIP (Viper4AndroidMM_v2.4.0.1.zip)
Install the ZIP in TWRP, and reboot.
4.) Open your apps/app menu, navigate to the new (it's an older version, but it's newly installed) V4A. It should be a purple logo instead of a blue logo. At this point in the tutorial, you should have both the Google Play Store APK, and the TWRP Flashed APK. Open the PURPLE V4A, and Install drivers now.
5.) Reboot phone, go to the NEW (blue logo) V4A, and install drivers on that one too.
The rest is clean-up. You may now delete the older version of V4A (purple logo).
========================================================
Bypass/fix #2, The SELinuxModeChanger issue:
1.) Download V4A (newest version) from \\ https://play.google.com/store/apps/details?id=com.vipercn.viper4android_v2_fx&hl=en
2.) (Grant root access) Attempt to install drivers. If this succeeds, then Idk why you're still here.
3.) Download SELinuxModeChanger APK from \\ http://forum.xda-developers.com/devdb/project/dl/?id=12506
4.) Open it, grant root access, and click "Permissive".
5.) Re-boot phone, and open V4A when done.
6.) Install drivers!
Sources/credit go to:
https://forum.xda-developers.com/showthread.php?t=2524485
^ SELinuxModeChanger
https://forum.xda-developers.com/lg-g3/themes-apps/app-viper4android-v2-4-0-1-lg-g3-t3311403
^ Driver install failure/ Disc I/O error/"superuser manager doesn't allow app to access su or you don't have root at all. fix this to use this selinuxmodechanger!" error
https://twrp.me/about/
^ Team Win
https://forum.xda-developers.com/member.php?u=7249915
^ Me, I contributed very small amounts, that's why I'm last (I guess I contributed some common sense .. ?)
what if you already have permissive kernel , and still get i\o error during driver install?
using android auto 7.1.1 head unit.
masri1987 said:
what if you already have permissive kernel , and still get i\o error during driver install?
using android auto 7.1.1 head unit.
Click to expand...
Click to collapse
Follow this guide for installation if already permissive
https://forum.xda-developers.com/moto-x-2014/themes-apps/mod-viper-4-android-oreo-tested-t3700287
For i\o error you should do step No.8
zahidm said:
Follow this guide for installation if already permissive
https://forum.xda-developers.com/moto-x-2014/themes-apps/mod-viper-4-android-oreo-tested-t3700287
For i\o error you should do step No.8
Click to expand...
Click to collapse
my head unit doesn't have vendor/etc or the audio effects configuration file....
Thanks
I had the Viper.apk from their website and the Google play version loaded also and I was getting the I/O error when trying to load the driver and the Google Play version didn't work at all. I did try to load SuperSU and busybox before attempting to load the driver again and it still didn't work. I don't know about permissive kernel, I'm running Resurrection ROM on a Rooted Note 3. The way I got this to work was to uninstalled the V4A Viper APK version that I had retrieved and loaded from their website. Next I booted into TWRP recovery and installed the V4A Flashable ZIP from the link that I found here. Next I ran the flashed version and granted SU permissions when asked during the install driver process. The driver finally loaded and bingo it works now.
Viper4android
Hi I have installed viper4android fx but in Driver status it shows no processing my phone(samsung j700f) is rooted with Supersu and using Wycked custom Rom nougat based I have done All the method like rename audio_effect.conf file but nothing to happened. All are waste of time.i spend too much time on xda site for solution but not found any solution...can anybody help me please?...Sorry for my bad English.. Thanx in Advance
Banty448 said:
Hi I have installed viper4android fx but in Driver status it shows no processing my phone(samsung j700f) is rooted with Supersu and using Wycked custom Rom nougat based I have done All the method like rename audio_effect.conf file but nothing to happened. All are waste of time.i spend too much time on xda site for solution but not found any solution...can anybody help me please?...Sorry for my bad English.. Thanx in Advance
Click to expand...
Click to collapse
Follow simple steps, first Rename file.bak
Then flash V4A,
Than open V4a it will ask to install driver
Just hit install and wait, it freez for sometime.. and it will say done
Reboot
zahidm said:
Follow simple steps, first Rename file.bak
Then flash V4A,
Than open V4a it will ask to install driver
Just hit install and wait, it freez for sometime.. and it will say done
Reboot
Click to expand...
Click to collapse
But I did it already many times but U tell me little bit different you said rename it before flashing but I did it After flashing .I flashed the zip file and after that rename than open Viper4android fx...ok I will try it...Thanx
Banty448 said:
But I did it already many times but U tell me little bit different you said rename it before flashing but I did it After flashing .I flashed the zip file and after that rename than open Viper4android fx...ok I will try it...Thanx
Click to expand...
Click to collapse
You have to rename file before opening V4A app for the first time, now you rename it before or after flashing no matter,
Sent from my Nokia 5.1 Plus using Tapatalk
0
zahidm said:
You have to rename file before opening V4A app for the first time, now you rename it before or after flashing no matter,
Sent from my Nokia 5.1 Plus using Tapatalk
Click to expand...
Click to collapse
I already told u that I did it before opening the v4a
Banty448 said:
0
I already told u that I did it before opening the v4a
Click to expand...
Click to collapse
The error you are saying it never been seen, please try again
Sent from my Nokia 5.1 Plus using Tapatalk
zahidm said:
The error you are saying it never been seen, please try again
Sent from my Nokia 5.1 Plus using Tapatalk
Click to expand...
Click to collapse
I have done it many times but nothing happened. I tired to install this so now I install Devinebeats it's working fine.Thanx for us replies?
Banty448 said:
I have done it many times but nothing happened. I tired to install this so now I install Devinebeats it's working fine.Thanx for us replies[emoji106]
Click to expand...
Click to collapse
You didn't followed this guide?
https://forum.xda-developers.com/mo...od-viper-4-android-oreo-tested-t3700287/page2
Sent from my Nokia 5.1 Plus using Tapatalk
When I install drivers for ViPER4Android FX I get "Driver installed, please reboot your device." and when I reboot, I'm asked to install drivers again. Did anyone figure out how to successfully install these drivers? I saw fixed around the forum, but they don't seem to work for me.
My phone huawei p10 lite rom Resurrection Remix OS Beta 3!
I've finally figured out how to get the ViPER4Android Magisk module properly working on a Galaxy S6 running Nougat.
Open the Download section of the Magisk Manager app; flash ViPer4Android FX and App Systemizer.
Reboot.
Install a ViPER4Android APK. I prefer the Material verzion on XDA Labs, but the original will work just fine.
Put LazerL0rd's script in /magisk/.core/post-fs-data and change the permission to 0755.
Replace the audio_effects.conf file in /magisk/.core/v4a/system/etc with Vaira's version. Copy that same file to /magisk/.core/v4a/vendor/etc. Make sure that the permission on both is set to 0644.
Open AppSystemizer in your app drawer and select ViPER4Android FX. Remember to hit the green save button.
Reboot.
Tried this on an HTC One M8 with LOS and Team M8 Kernel - it caused a bootloop for me.
Help with step 4 please...
EncryptedCurse said:
I've finally figured out how to get the ViPER4Android Magisk module properly working on a Galaxy S6 running Nougat.
Open the Download section of the Magisk Manager app; flash ViPer4Android FX and App Systemizer.
Reboot.
Install a ViPER4Android APK. I prefer the Material verzion on XDA Labs, but the original will work just fine.
Put LazerL0rd's script in /magisk/.core/post-fs-data and change the permission to 0755.
Replace the audio_effects.conf file in /magisk/.core/v4a/system/etc with Vaira's version. Copy that same file to /magisk/.core/v4a/vendor/etc. Make sure that the permission on both is set to 0644.
Open AppSystemizer in your app drawer and select ViPER4Android FX. Remember to hit the green save button.
Reboot.
Click to expand...
Click to collapse
Sorry new to modding,
Step 4: not sure exactly where to paste? I tried but when saving I get error no permission..? I've been trying to get this working for weeks...
SM-G925F
Stock Rom
Magisk 13.3
Busybox. Stericson
As current and all previous Magisk releases can break any fire tv on update from manager, I made custom build of Magisk 25.1 for Fire TV
Releases GitHub URL
Changes:
- Manager doesn't have direct install / update options
- Dark theme by default
- Amazon orange color for default and AMOLED themes
- Grant root permission by default
- Fix issue of enabled Zygisk with Xposed Framework
- Change version to 25.1.FTV (25777)
Fixes:
- fix D-PAD navigation on Grant / Deny root dialog
- fix D-PAD navigation on Log section
- fix D-PAD navigation on Zygisk DenyList
- fix D-PAD navigation on Reboot button after flash
Install:
- Install APK (uninstall previous Manager version if exist 1st),
- Rename apk to zip and flash from TWRP recovery
Have fun!
p.s. maybe someday devs will apply those changes to source, now they call it "offtopic"
Hey, it hangs at CHECKING for digest. Magik 23.0 worked before. Any idea?
Isn't to grant / deny root access with the remote working by default for fireTV devices?
Never saw a problem like that, for tank/sheldon/mantis/sloane, works fine here!?
Sus_i said:
Isn't to grant / deny root access with the remote working by default for fireTV devices?
Never saw a problem like that, for tank/sheldon/mantis/sloane, works fine here!?
Click to expand...
Click to collapse
It works on Android 9, but on Mantis (4K with 7.1.2) dialog worked with Magisk 20.4 (old manager) and broken (don't have any focus so user can't press any button in it) with any Magisk 21+ and new Manager GUI
mamcho said:
Hey, it hangs at CHECKING for digest. Magik 23.0 worked before. Any idea?
Click to expand...
Click to collapse
hm, it's apk from studio, tesed it on TWRP from Fire TV 4K and it installs fine. Try to disable digest check in TWRP options.
Im on sloane and disabling digets check doesnt change anything. I ve read that 24.3 is problematic for sloane. 23.0 works tho
Hi,
I'm on 4K stick and I have Magisk 24.3 installed (apk from their github).
If I want to switch to this I have to uninstall current Magisk Manager even if I flash from TWRP?
BTW: guys on magisk github page asnwer really bad to your suggestion, no reason to do that
The manager UI is not tv-friendly so it's really easy to press update by mistake. It was the 1st thing I though when I saw it after installation...
Noisemaker00 said:
Hi,
I'm on 4K stick and I have Magisk 24.3 installed (apk from their github).
If I want to switch to this I have to uninstall current Magisk Manager even if I flash from TWRP?
Click to expand...
Click to collapse
You need to uninstall Manager in any case because app signature differs. After install you need o flash apk renamed to zip from recovery to match daemon / apk signatures. Magisk in 1s post updated to v25.0.FTV.
tsynik said:
You need to uninstall Manager in any case because app signature differs. After install you need o flash apk renamed to zip from recovery to match daemon / apk signatures. Magisk in 1s post updated to v25.0.FTV.
Click to expand...
Click to collapse
So the steps are:
uninstall current magisk-manager version
download and rename your .apk to .zip
reboot to twrp and flash the zip
reboot the system
is it correct?
hiding the app is not working propertly. if i generate a new app it fails to load and want to download full manager again.
mamcho said:
hiding the app is not working propertly. if i generate a new app it fails to load and want to download full manager again.
Click to expand...
Click to collapse
Yes, probably it's some kind of bug in Magisk. When hiding, Magisk replaced with stub app, which download full apk from https://github.com/tsynik/Magisk/releases, but failing to load it's classes and initialize app context.
Fixed with v25.1.FTV release
tsynik said:
As current and all previous Magisk releases can break any fire tv on update from manager, I made custom build of Magisk 25.1 for Fire TV
Releases GitHub URL
Changes:
- Manager doesn't have direct install / update options
- Dark theme by default
- Amazon orange color for default and AMOLED themes
- Grant root permission by default
- Fix issue of enabled Zygisk with Xposed Framework
- Change version to 25.1.FTV (25777)
Fixes:
- fix D-PAD navigation on Grant / Deny root dialog
- fix D-PAD navigation on Log section
- fix D-PAD navigation on Zygisk DenyList
- fix D-PAD navigation on Reboot button after flash
Install:
- Install APK (uninstall previous Manager version if exist 1st),
- Rename apk to zip and flash from TWRP recovery
Have fun!
p.s. maybe someday devs will apply those changes to source, now they call it "offtopic"
Click to expand...
Click to collapse
Hello tsynik
I flashed this version, but never granted su permissions .
The Magisk Mannager is missing in fireOS.
When reinstall, it crashes and disappear .
Can you give me instructions on how to uninstall this version?
thanks
What I did was to rename .apk to .zip, flash with twrp. manager was not to be found on apps. then I manually installed the .apk and it appeared on apps.
yakovperelman69 said:
Hello tsynik
I flashed this version, but never granted su permissions .
The Magisk Mannager is missing in fireOS.
When reinstall, it crashes and disappear .
Can you give me instructions on how to uninstall this version?
thanks
Click to expand...
Click to collapse
I am having the same issue
BTW to uninstall rename the apk to uninstall.zip then flash it in twrp
I have a tank (2nd gen stick) with latest firmware (5.2.9.5 at time of writing)
Now that Magisk v26 has dropped support for android 5, it would be wise to release a final version for old fire sticks.
Anyway the UI does not start at all, both on your fork and on the original v25.2 . (and, both of them do not remember superuser permissions - they get asked every time)
I just tried to flash Magisk v26.1 via TWRP. FireOS6 (mantis - FTV4K)
First fresh Kernel followed by Magisk v26.1.zip.
All seams to work but I noticed that the repacking step went unusual fast!
After rebooting and updating Magisk app to v26.1 it seams to work.
But now I get after a fresh start/reboot a warning message in Magisk app that an reflash is necessary!
I now went back to 25.2 (again Kernel + Magisk.zip) and all is good again.
I do not know what happens here or if something went wrong or if 26.1 is not fully compatibe to FireOS6 (Android 7)...
Anyway - Just wanted to let you all know.