Dear brother's I have facing issue with viper4android fx, I have installed from magisk module and install driver but it show status-abnormal, I have seen many videos on youtube and check XDA thread but still same issue.
Pls help me...
wakram001 said:
Dear brother's I have facing issue with viper4android fx, I have installed from magisk module and install driver but it show status-abnormal, I have seen many videos on youtube and check XDA thread but still same issue.
Pls help me...
Click to expand...
Click to collapse
Use the guide as in that post (the same can be also found in the XDA V4A general thread):
zgfg said:
There is actually an easier way to fix Viper4Android, follow the original post where the fix was described:
[APP][ALL ROOT SOLUTIONS][6.0+]ViPER4Android FX 2.7
ViPER4Android FX By pittvandewitt and MrWhite214 Introduction Many users are enhancing their smartphone audio experience with the popular ViPER4Android software, but some of us have a hard time installing the driver or they don't like the look...
forum.xda-developers.com
In other words, replace (use TWRP or root explorer like MiXplorer)
/data/adb/modules/ViPER4AndroidFX/post-fs-data.sh
with the attached file (download and unzip) and reboot
Still make sure that Legacy mode in V4A Settings is enabled
AML module makes no harm but it's not needed (unless you install additional audio modules like mi9tpbitrate320.zip)
---
In case of installing V4A from scratch:
- install ViPER4Android_FX-v2.7.2.1.zip from Repo (through Magisk) and reboot
- open Viper4Android app and let it install the driver, it will reboot
- replace post-fs-data.sh as above and reboot once again
- open Viper4Android app and enable Legacy mode in its Setrings
- also, don't forget to enable Master limiter for e.g. speaker or headphones
Check the driver status, it must show Status Normal (and Processing Yes when playing nusic)
---
I have Xiaomi.eu A11 beta and I regularly update every week when they release (by dirty flashing their new MIUI zip release, wiping Dalwik and Cache and by flashing the new boot img patched by Magisk)
Up to the two weeks ago I had to re-do the relatively complicated procedure for V4A as was described in this thread upon every Xiaomi.eu update
Since two weeks ago when I replaced the post-fs-data.sh as described above, I just dirty flash Xiaomi.eu, apply root/Magisk, and my V4A continues to work as my all other installed Magisk modules (and root apps), with no needs to fix the V4A driver anymore
PS: This 'new' method with the modified post-fs-data.sh is specifically useful for Magisk Canary 22006 since Magisk 22006 has a known bug with processing the sepolicy.rule files (also in /data/adb/modules/ViPER4AndroidFX), and hence the 'old' method from this thread does not work with Magisk 22006 - but the 'new' method does work (I currently use that Magisk 22006)
Click to expand...
Click to collapse
Can AML fix this issue...
I can't understand which files I replace.
I am a bigner user of magisk.
wakram001 said:
Can AML fix this issue...
I can't understand which files I replace.
I am a bigner user of magisk.
Click to expand...
Click to collapse
In the thread I gave you the link, use of AML was also described. But I'm no more using AML and cannot/won't support you about
In my previous post there is s link to my post with the guide using post-fs-data.sh (sorry, I'm not going to send the link again)
Click on that post and inside you will find post-fs-data.zip.
It was described in details, so once again but only shortly here:
- download the zip, extract post-fs-data.sh
- use your favorite root File Manager (like MiXplorer - google on XDA to find its thread and installation if needed) or use TWRP, Advanced, its File Manager (again, google if needed to learn how to use).
Anyway, those skills and tools will be useful for you in future if you decided to go with Magisk, its modules, etc
- go to /data/adb/modules/Viper4Android FX and rename the existing post-fs-data.sh to post-fs-data.bak (just in case) and paste instead the post-fs-data.sh you extracted from my zip (see screenshot)
-reboot
- open V4A app, go to its settings and enable Legacy mode (again, see the screenshots in my post with the guide)
Dear brother
I have understood what you said, but I can't find zip file from your previous post, one more thing v4a fx working with legacy mode, but when I close legacy mode it cannot support.
Thanks for replying on my post.
zgfg said:
In the thread I gave you the link, use of AML was also described. But I'm no more using AML and cannot/won't support you about
In my previous post there is s link to my post with the guide using post-fs-data.sh (sorry, I'm not going to send the link again)
Click on that post and inside you will find post-fs-data.zip.
It was described in details, so once again but only shortly here:
- download the zip, extract post-fs-data.sh
- use your favorite root File Manager (like MiXplorer - google on XDA to find its thread and installation if needed) or use TWRP, Advanced, its File Manager (again, google if needed to learn how to use).
Anyway, those skills and tools will be useful for you in future if you decided to go with Magisk, its modules, etc
- go to /data/adb/modules/Viper4Android FX and rename the existing post-fs-data.sh to post-fs-data.bak (just in case) and paste instead the post-fs-data.sh you extracted from my zip (see screenshot)
-reboot
- open V4A app, go to its settings and enable Legacy mode (again, see the screenshots in my post with the guide)
Click to expand...
Click to collapse
Dear brother
I have understood what you said, but I can't find zip file from your previous post, one more thing v4a fx working with legacy mode, but when I close legacy mode it cannot support.
Thanks for replying on my post.
wakram001 said:
Dear brother
I have understood what you said, but I can't find zip file from your previous post, one more thing v4a fx working with legacy mode, but when I close legacy mode it cannot support.
Thanks for replying on my post.
Dear brother
I have understood what you said, but I can't find zip file from your previous post, one more thing v4a fx working with legacy mode, but when I close legacy mode it cannot support.
Thanks for replying on my post.
Click to expand...
Click to collapse
Zip attachement was there, you have to go to that post and scroll down through the whole post, it was the last attachement (scrollshot below, click to open and scroll down, it's very long)
Do not read just my post there but study the whole thread and you will see that bobod made it working without Legacy mode on Mi 9T (Pro or not Pro). Google for the general V4A thread on XDA and you will see that most of users/phones can only work with Legacy mode. If you don't like, don't use V4A. Btw, what's wrong with, besides that is called 'legacy'
Dear brother
Still I can't find the zip file, I have goes through whole post and I can't get zip files.
I request you to pls upload once more....
Thanks for guidance...
wakram001 said:
Dear brother
Still I can't find the zip file, I have goes through whole post and I can't get zip files.
I request you to pls upload once more....
Thanks for guidance...
Click to expand...
Click to collapse
Go back to my first answer in this thread (post #2), answer to your original question about V4A.
Click on to the cited post there, to JUMP INTO
When you jumped to that other thread and the post there, scroll down till the end of the long post where ATTACHMENTS begin
CONTINUE SCROLLING through all atrachements, skip three screenshots and CLICK on the ZIP (last attachement) to start downloading
Really so hard?
Related
NOTE:
This post is/was only relevant for users of the original modded stock recovery for YP2. For the newer & better TWRP recovery for YotaPhone 2 installing unsigned packages such as Xposed framework is not an issue.
Please note that the Xposed version below is outdated, Xposed alpha 4 is available. See Xposed for Lollipop thread.
Old post content:
Not exactly a proper development thread, but posting it here anyway because of the relation with the modded recovery, ad the slightly technical angle.
Xposed framework for Lollipop allows you to install modules that tweak/change many aspects of Android. It's pretty powerful as it can hook into existing software and change it's functionality. The version referred to in this post is an alpha version.
Therefore:
Warning: I recommend you don't install this unless you're a nerd. It's not yet stable, and may cause trouble (such as boot-loops).
Also: by the time you read this there may be newer versions, so read the Xposed thread for updates.
Background
The modded recovery image allows to install software signed by either Yota Devices (such as ota update zips) or signed with testkeys, but it does not allow to flash UNsigned zips. Many flashable zips are signed with testkeys (like SuperSU) but rovo89's Xposed flashable zip for LP in the current 20150430 version are unsigned, so we can't flash them as-is.
Flashing it anyway:
There's two ways: the harder and slightly educational way (useful for e.g. when new Xposed versions are released) and the lazy but convenient way.
1) Signing the Xposed framework zip yourself:
You need:
- signapk.jar plus test key and certificate
Get SignApk.jar from somewhere (build it from AOSP source, or download a zip from this thread (I used zipaligner 1.2, linux). This zip contains other stuff, but we need testkey.pk8, testkey.x509.pem and signapk.jar
- Xposed framework zip for LP 5.0 (xposed-sdk21-arm-20150430.zip) from the official thread from here
- java environment (JDK or JRE)
To sign the file put all files in one dir (including xposed-sdk21-arm-20150430.zip) and run:
Code:
java -jar signapk.jar -w testkey.x509.pem testkey.pk8 xposed-sdk21-arm-20150430.zip xposed-sdk21-arm-20150430_signed.zip
You just created xposed-sdk21-arm-20150430_signed.zip that you can flash.
2) Using a pre-Signed zipfile:
I attached a testkey-signed version of rovo89's file xposed-sdk21-arm-20150430.zip to this post for convenience, so you can skip the steps above.
Steps to install the Xposed framework for LP
1) put device in fastboot/download mode and boot the modded recovery image (see recovery thread)
2) choose "apply update from ADB" from recovery menu
Code:
adb sideload <yourpath>/xposed-sdk21-arm-20150430_signed.zip
3) reboot
4) choose allow 'unknown sources' in settings->security
5) copy the file XposedInstaller_3.0-alpha2.apk to your phone (or scan the QR code on the Xposed page to download this file to your phone directly.
6) use a file manager (like ES File Explorer, or the built-in Cabinet) to browse to and open XposedInstaller_3.0-alpha2.apk and install it.
Now you can download Xposed modules through the Xposed Installer app. I tried GravityBox [LP] (make sure you select the right version!) to change the launcher grid to 5x5 instead of 4x4. After a reboot that worked. I'm not saying that using GravityBox is safe, they warn that it may cause trouble with non-standard ROM's (such as ours).
Please not that I can't/won't provide any support for Xposed itself, please see the relevant Xposed threads for that.
Credits:
rovo89, author of the Xposed Framework
nice one, many thanks
Does anyone have then latest version please that's signed for this device
Sent from my YD201 using Tapatalk
read the start topic good, every thing you need is in there with links
Gojira-r32 said:
read the start topic good, every thing you need is in there with links
Click to expand...
Click to collapse
Which version of xposed is for yotaphone I see a few different versions on the xposed thread. Link From the op
Sent from my YD201 using Tapatalk
I used xposed-v68-sdk21-arm.zip just two days ago, and signed it myself according to the instructions.
It seems to play well, at least for two days
I just booted TWRP and sideloaded it, I never flashed the TWRP.
Had a little mess getting the driver to install in windows, when TWRP sideloads, it had a new identity in the device manager and I was unable to make accept the drivers I had. So I made a little manual edit in the .inf file from the yotaphone flashtool package, and then was able to load the driver needed. Google was my friend, but I can paste the change here later if someone want it.
Those who are using xposed do you notice any long freeze on the epd and reboots.
Sent from my YD201 using Tapatalk
adamo86 said:
Those who are using xposed do you notice any long freeze on the epd and reboots.
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
Nope. I am running latest Xposed framework with gravitybox and youtube adaway. No crashes or freezes, but the battery life does fluctuate quite a bit sometimes. But I think that that is because of Lollipop.
No issues with xposed here either. Running alpha4 I believe.
Installed but not active.. That's what i get! Why is thaT?
Thanks!
I signed the last version of xposed using the method in the first post, and flashed (file attached) using TWRP. no issues so far.
no need to say, make sure you backup first!
Bootloop
I have accidentally flashed the xposed-sdk21-arm-20150430_signed.zip...so my phone stuck in bootloop. How can I uninstall it?
Wanderess said:
I have accidentally flashed the xposed-sdk21-arm-20150430_signed.zip...so my phone stuck in bootloop. How can I uninstall it?
Click to expand...
Click to collapse
SOLVED. Stock rom (4.4.3 HK) flashed with Yota Flasher. After this everything went smoothly.
Oficial Xposed running with no problems, well just one named Lollipop
Jeopardy said:
Nope. I am running latest Xposed framework with gravitybox and youtube adaway. No crashes or freezes, but the battery life does fluctuate quite a bit sometimes. But I think that that is because of Lollipop.
Click to expand...
Click to collapse
The same with me, Lollipop because using the EPD is so much better, otherwise I would happily be on KitKat, battery life on Lollipop is awfull, I also have the Xposed installed the official one with no problems, running some Modules to prevent battery from draining as much as possible in this Google Sucking Lollipop...
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!
For anyone who's interested, here's what I did. based on the directions given by quinny899 in the thread here: https://forum.xda-developers.com/pixel-2-xl/help/viper4android-8-1-0-t3711474
I used the contents of the ZIP posted by quinny899 (for step 9, below) in post #8 on that thread: https://forum.xda-developers.com/showpost.php?p=74681544&postcount=8
The steps I took were:
1. Clean install of the Android 8.1 full factory images (with the -w option removed from the flash-all.bat file)
2. Completed the initial set up, then got rid of the lockscreen PIN (so that I wouldn't have decryption issues with TWRP in the next steps)
3. Put phone into fastboot, then booted into the TWRP 3.2 image
4. Installed Magisk (version 14.1456 beta)
5. Rebooted
6. Installed Buysbox for Magisk, and downloaded (did not install) the Vipe4Android Magisk module by ShadySquirrel
7. Extracted the Viper4Android.apk from the Magisk module that I downloaded
8. Rebooted
9. Copied the contents of quinny89's zip file into root/Magisk (using SolidExplorer, after granting it root privileges)
10. Rebooted. Now, Magisk thinks it has Viper installed (but it doesn't, yet!)
11. Install the Viper4Android.apk that I extracted in Step 7, as a normal user app
12. Reboot
13. In Viper4Android, put it in Compatibility mode, enable Developer mode, and disable seLinux (or use some other method to set seLinux to permissive, I suppose)
14. Reboot, and Viper is working for phone speakers, and Bluetooth, tested with Spotify and Poweramp. Convolvers, and all
All credit to quinny899 for figuring this out for the PixelXL.
anyone have a link to this busybox? man I search and get all kinds of junk but not the one I need. thanks
quinejh said:
anyone have a link to this busybox? man I search and get all kinds of junk but not the one I need. thanks
Click to expand...
Click to collapse
Can't you download and install it directly from MagiskManager?
pavanmaverick said:
Can't you download and install it directly from MagiskManager?
Click to expand...
Click to collapse
Strangest thing. The one that the manager downloads doesn't work. But I found another link in I believe it was the xl thread and after flashing it when I start playing music I get a viper has stopped error but u can hear it processing
quinejh said:
Strangest thing. The one that the manager downloads doesn't work. But I found another link in I believe it was the xl thread and after flashing it when I start playing music I get a viper has stopped error but u can hear it processing
Click to expand...
Click to collapse
Weird, indeed! Glad you got it working though!
I couldn't get it working using the apk from the magisk viper 14+, but using the apk from v4afx_v2.2.zip worked perfect.
---------- Post added at 04:02 AM ---------- Previous post was at 03:44 AM ----------
I notice with this method for viper it takes a sec to kick in when I change songs, which makes a little shift at the beginning. Anyone know how to get rid of that?
This works.
https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058/page126
Did any of you have to use a Magisk SELinux Permissive Script to get Viper to work?
If i disable the script in Magisk, Viper doesnt, work but if the script is enabled, it works.
IF you guys aren't using a script how did you get viper to work?
Im using the following Magisk Modules
Audio Modification Library v2.5 by ahrion, zackptg5
Busybox for Android NDK v1.27.2 by osm0sis
Magisk SElinux Permissive Script v1.1 by jman420
ViPER4Android FX v2.5 (2.3.4.0) by ahrion, zackptg5
I'm using the permissive script. Permissive is required for viper.
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.
Has anyone been able to use v4afx on 13? It keeps asking to install the drivers.
Basically you have to remove everything from V4A first like in Magisk and the app itself. After the reboot you do the installation process again with Magisk but do not open V4A yet.
Put the attached file into /data/adb/modules/ViPER4AndroidFX and overwrite it if necessairy.
Now reboot and it should work with legacy mode on.
To make it work, v4a must "patch" audio_effects.xml file, but there is a problem, because earlier androids up to OOS11 have it stored in /vendor/etc, and it patched it without problem. OOS12 and 13 have that file too in this location, but it's generic file, don't contain Dolby Atmos, Nokia Ozo processing, Dolby VQE (message enhancer), and system don't use it...
From OOS 12, oneplus decided to store and use this file in /odm partition, exactly in /odm/etc.
V4a don't have possibility to patch it, that's why it tries to install "driver" again and again.
One more info.
mount -o bind /vendor/etc/audio_effects.xml /odm/etc/audio_effects.xml from post-fs-data.sh will replace that file in odm, and yes, it will work, but it also will kill your Dolby Atmos, OZO processing, VQE, because this file in /vendor/etc don't contain them.
Thanks for the input. I will give it a shot.
Idk if u have looked thoroughly, but I made a guide to install V4A: https://forum.xda-developers.com/t/...tall-viper4android-for-oneplus-8-pro.4388799/
Instead of using these weird files and workarounds to install V4A...
I would suggest downloading DDC and kernel files which can be found on my XDA thread.
Just download them and extract the .zip file only
Then download, install V4A repackaged, reboot and done
Try installing V4A repackaged: https://github.com/programminghoch10/ViPER4AndroidRepackaged/releases
The weird file you're referring to is from dorimanx himself.
[APP] [FIX] 100% working Viper4Android for Android 10-11-12 devices
If you are someone like me who encountered countless problems while installing Viper4Android on your Android 10 or 11 device and have no idea what to do then you are in the right place. Just download and install the apk from the attachment below...
forum.xda-developers.com