Hi
In latest open beta with Magisk 15.3 , used debloater and made space in system , but on flashing anything no error is there but nothing shows in app drawer , same is happening with Magisk also . Managed to flash viper but the drivers are not getting installed showing io error while same works fine for others without manual driver installation, no idea what's wrong !!!!
Yikes. Sounds like something is glitched in there. Try wiping : system and cache ( only )and reloading the rom and then rebooting into recovery and then booting up in system.
.
If it's still glitched ( ugg ) then its wipe all ( less external data ) and factory reset and start over.
.
Um, did you make yourself a nandroid backup ?
AKHIL.cochin said:
but on flashing anything no error is there but nothing shows in app drawer.
Click to expand...
Click to collapse
What do you mean by this? Do you mean that you don't see any apps after flashing a Magisk module? Many modules don't install any apps and you either don't have to do anything to configure or run a terminal command. What modules are you talking about?
Managed to flash viper but the drivers are not getting installed showing io error while same works fine for others without manual driver installation, no idea what's wrong !!!!
Click to expand...
Click to collapse
That's a known issue with V4A on OxygenOS Oreo. Some don't experience it though, which is incredibly frustrating...
Also what version of twrp r u using
old_fart said:
Yikes. Sounds like something is glitched in there. Try wiping : system and cache ( only )and reloading the rom and then rebooting into recovery and then booting up in system.
.
If it's still glitched ( ugg ) then its wipe all ( less external data ) and factory reset and start over.
.
Um, did you make yourself a nandroid backup ?
Click to expand...
Click to collapse
did a clean flash and checked , its still there , no idea whats wrong ..
Bradl79 said:
Also what version of twrp r u using
Click to expand...
Click to collapse
twrp-3.2.1-0
Didgeridoohan said:
What do you mean by this? Do you mean that you don't see any apps after flashing a Magisk module? Many modules don't install any apps and you either don't have to do anything to configure or run a terminal command. What modules are you talking about?
That's a known issue with V4A on OxygenOS Oreo. Some don't experience it though, which is incredibly frustrating...
Click to expand...
Click to collapse
" not only magisk , have u read my post , on flashing arise magnum on twrp also gave no errors and i selected viper , dolby , dolby atmos , xperia music etc and all flashed fine but none was showing in there thats what i have mentioned i also tried many viper and dolby modules in magisk , nothing s working "
AKHIL.cochin said:
" not only magisk , have u read my post , on flashing arise magnum on twrp also gave no errors and i selected viper , dolby , dolby atmos , xperia music etc and all flashed fine but none was showing in there thats what i have mentioned i also tried many viper and dolby modules in magisk , nothing s working "
Click to expand...
Click to collapse
Yes, I did read your post, but it was lacking in detail so I needed to ask some clarifying questions. Unfortunately, your answer is also somewhat lacking in detail...
But, I'm guessing you're trying to install some audio mods. V4A isn't working properly on OOS Oreo for the OP3T. A few users have it running fine, but it seems like those are a minority.
There are not that many Dolby mods that work on Oreo yet, so you might have to look around a bit to find one that does. There'll most likely be some more readily available soon though.
Didgeridoohan said:
Yes, I did read your post, but it was lacking in detail so I needed to ask some clarifying questions. Unfortunately, your answer is also somewhat lacking in detail...
But, I'm guessing you're trying to install some audio mods. V4A isn't working properly on OOS Oreo for the OP3T. A few users have it running fine, but it seems like those are a minority.
There are not that many Dolby mods that work on Oreo yet, so you might have to look around a bit to find one that does. There'll most likely be some more readily available soon though.
Click to expand...
Click to collapse
THE FRUSTRATING THING S ITS WORKING FOR ALL THE OTHERS WITHOUT ANY ISSUES IN SAME ROM KERNEL COMBO
AKHIL.cochin said:
THE FRUSTRATING THING S ITS WORKING FOR ALL THE OTHERS WITHOUT ANY ISSUES IN SAME ROM KERNEL COMBO
Click to expand...
Click to collapse
Yes, it's frustrating, but there's no need to shout. And it does NOT work for everyone else. I haven't had an audio mod working properly on my OP3T since updating to OOS 5+...
It works for some, but not for others. You could try the OOS beta. It seems like some have better luck with that.
Either you try to help, if possible, or you change to a working ROM combo, or you wait until someone finds a fix.
I had a problem that some modules wouldn't activate (they install successfully, but after reboot I would still see "module will be updated at next reboot"). As I didn't have time and will to debug this, I reverted to OOS 4.5.1.
Related
Hi I'm having this issue consistently ever since nougat based ROMs are released for Mi5
Whenever i root the nougat based miui ROM, it boots fine but after some time it starts stuttering/lagging so much that one becomes totally inoperable.
I have tried various ways but no success.
I have tried with SuperSU 2.78, 2.79, 2.79SR3 and also eu roms n China global as well but the results are same.
I have also tried wiping the whole internal partition to remove device encryption but the lag don't go away.
When dirty flash the ROM again from twrp, Everything comes back to normal.
Not sure if anybody else is facing the same issue or probably know the solution.
Cheers!
Did you already tried stable version 8.1.9.0 rom from xiaomi.eu that's based 7.0 too..?, coz before..i'm using that rom for a month i think...and doesn't found any lag..even already rooting with supersu 2.79.
Please make sure..this time not just a wiping..but do a format system, data and cache as ext4 from official twrp 3.0.2-3 before flasing
JJeamy said:
Did you already tried stable version 8.1.9.0 rom from xiaomi.eu that's based 7.0 too..?, coz before..i'm using that rom for a month i think...and doesn't found any lag..even already rooting with supersu 2.79.
Please make sure..this time not just a wiping..but do a format system, data and cache as ext4 from official twrp 3.0.2-3 before flasing
Click to expand...
Click to collapse
Let me try formatting system also, but i don't think that would help much
after flashing suhide the lag is back again, looks like suhide issue
chhapil said:
after flashing suhide the lag is back again, looks like suhide issue
Click to expand...
Click to collapse
Yup..i think compatibility suhide is causing that lag..coz i'm never tried that before..but with just standard supersu..all running normally in mine..
JJeamy said:
Yup..i think compatibility suhide is causing that lag..coz i'm never tried that before..but with just standard supersu..all running normally in mine..
Click to expand...
Click to collapse
Just to confirm my doubt, can you try flashig suhide? its very easy uninstall as well. it just adds a script to su partition.
it will help me report the issue in suhide thread.
thanks for your support
chhapil said:
Just to confirm my doubt, can you try flashig suhide? its very easy uninstall as well. it just adds a script to su partition.
it will help me report the issue in suhide thread.
thanks for your support
Click to expand...
Click to collapse
I can't test it that now..coz now mine currently back using 8.1.3.0 that's based 6.0, to test raw format of camera coz in 7.0 doesn't work before.. so the result will be different from yours..
JJeamy said:
I can't test it that now..coz now mine currently back using 8.1.3.0 that's based 6.0, to test raw format of camera coz in 7.0 doesn't work before.. so the result will be different from yours..
Click to expand...
Click to collapse
Np, let me know if you switch back N again
chhapil said:
Np, let me know if you switch back N again
Click to expand...
Click to collapse
Will testing it later..and letting know the result to you..
Installed the new Magisk 11, everything smooth as butter now.
magisk hide works fine!
Has anyone gotten Viper4Android to work on OB12? I've tried SpasilliumNexus' version and the ones in the Magisk repo. They all flash without error, but my 3T fails to boot. Any tips would be appreciated.
Edit: fixt. Thanks @Stephen.
HampTheToker said:
Edit: fixt. Thanks @Stephen.
Click to expand...
Click to collapse
Please post the solution, for the benefit of others that may have a similar question/problem.
redpoint73 said:
Please post the solution, for the benefit of others that may have a similar question/problem.
Click to expand...
Click to collapse
Whoops. I meant thanks for moving my post. I originally posted in the themes apps and mods subforum by mistake. Stephen bumped it over for me pretty quick.
I still can't install viper. It fails to boot and uninstalling Magisk to get it to boot trips dm-verity and it still fails to boot. I imagine getting kicked in the a** on a pirate ship feels much the same. I'm getting tired of restoring backups.
I've seen others report success on OB12...I'm not just one of them even after a clean flash and wiped internal.
Works for me. Used the version with the latest magisk template. Viper 2.3.4.0 Super high quality. It apparently doesn't play well with bluspark kernel
nagi_007pk said:
Works for me. Used the version with the latest magisk template. Viper 2.3.4.0 Super high quality. It apparently doesn't play well with bluspark kernel
Click to expand...
Click to collapse
I'm on Franco's kernel r25. Never had issues using viper previously.
HampTheToker said:
Whoops. I meant thanks for moving my post. I originally posted in the themes apps and mods subforum by mistake. Stephen bumped it over for me pretty quick.
I still can't install viper. It fails to boot and uninstalling Magisk to get it to boot trips dm-verity and it still fails to boot. I imagine getting kicked in the a** on a pirate ship feels much the same. I'm getting tired of restoring backups.
I've seen others report success on OB12...I'm not just one of them even after a clean flash and wiped internal.
Click to expand...
Click to collapse
I would suggest for you to avoid using the magisk based viper 4 android files since it mess up the boot sequence on 13 above.
I follow this steps instead and was able to successfully install viper4android without the boot issue.
Also if you experience the driver abnormal status I would suggest that you grab the SELinux changer and set it to permissive first thing after the device boot.
I never did successfully get v4a to boot, Magisk or otherwise. Magisk 13.5 is right around the corner. Ahrion just announced a partnership with Zackptg5 to improve his audmodlib and multiple different submodules for it. Hopefully, that'll work out.
Hi all, i'm using a stock rom, rooted with magisk and debloated (manually). I always faced this problem, the 90% of the modules i try to install ends with something like that:
See Screen below
However i've never asked help because i tought it was a Magisk problem resolvible with an update...but every update ended always in the same way for me when trying to install some modules. I've also attached some logs here of when i tried to update xposed systemless if someone could help me it will be really apprecciated!
P.s Anyone facing the same problem? I've read somewhere that a similar problem is common with Motorola devices but idk if this is the case
Giuskiller said:
Hi all, i'm using a stock rom, rooted with magisk and debloated (manually). I always faced this problem, the 90% of the modules i try to install ends with something like that:
See Screen below
However i've never asked help because i tought it was a Magisk problem resolvible with an update...but every update ended always in the same way for me when trying to install some modules. I've also attached some logs here of when i tried to update xposed systemless if someone could help me it will be really apprecciated!
P.s Anyone facing the same problem? I've read somewhere that a similar problem is common with Motorola devices but idk if this is the case
Click to expand...
Click to collapse
Is this via Magisk manager?
ashyx said:
Is this via Magisk manager?
Click to expand...
Click to collapse
Yes this is via Magisk Manager, however the same error (could not mount something) appears also when i try to install a module via twrp. The "best" thing is that some module just works both way (Busybox NDK for example) while other fails both ways. No module work in a way and doesn't work in another. So basically if a module work in magisk can be installed also via twrp otherwise it cannot be installed, no matter what i try
I have the same problem. Trying to install viper4a.
I have no clue how to fix it
Giuskiller said:
Yes this is via Magisk Manager, however the same error (could not mount something) appears also when i try to install a module via twrp. The "best" thing is that some module just works both way (Busybox NDK for example) while other fails both ways. No module work in a way and doesn't work in another. So basically if a module work in magisk can be installed also via twrp otherwise it cannot be installed, no matter what i try
Click to expand...
Click to collapse
I think this is a bug in Magisk with the way some modules attempt to install and mount, which is why some work.
I'm surprised though that they don't install in TWRP. Is your device encrypted, can you mount /data in recovery?
ashyx said:
I think this is a bug in Magisk with the way some modules attempt to install and mount, which is why some work.
I'm surprised though that they don't install in TWRP. Is your device encrypted, can you mount /data in recovery?
Click to expand...
Click to collapse
Actually i'm at university, but when i come back home i will try and let you know. What i can say for now is that every zip i've flashed so far worked just flawlessy (well, apart magisk's ones)
Downloaded atmos dolby only module for nougat....rebooted snd stucked on samsung logo. Ohhhh.... How to get rid of this module, is anyway to do it?
Please help
Edit:
installed module uninstaller and followed it - > https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
working now.
Looking for info how to install viper4Android....
netgar said:
Downloaded atmos dolby only module for nougat....rebooted snd stucked on samsung logo. Ohhhh.... How to get rid of this module, is anyway to do it?
Please help
Edit:
installed module uninstaller and followed it - > https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
working now.
Looking for info how to install viper4Android....
Click to expand...
Click to collapse
Well as far as i know, if you're on stock rom you won't be able to install audio mods because they're in conflict with something in the Rom. You should use a custom rom instead. However not sure 100% about this, maybe some audio mods can work, but you should ask someone else, i'm not so informed
It calling me all time for the driver. I do that every time and I give him magisk root to do that. Any suggestion?
Did i get here some help or not? Then i looking maybe for a other Forum...
Install as system app and allow it to install through the not recommended settings.
U now have to delete it and reinstall it.. Watch the instructions in the thread pls before you become sow passive agressive mate. It is not our fault, ok?
Use this module. Flash in Magisk manager. Choose latest driver, material app, system app, lib workaround, and choose no for the last. (I don't remember what was it)
Hi, I've a Mi9 and tried to install Viper4AndroidFx.. Installation ok, driver installed, but no effect.. tried to set all to highest value to ear some difference but nothing..
Uninstalled it, i tried Viper4Android Legacy, installed as system app and by magisk and chosen all installation option with up volume button..
But still no difference with the stock speaker.. can you help me?
I would like to encrease the volume during a calling. thanks bye
take a look on mi8 or mi a1 forum in xda, there is described exactly which modules in Magisk must be installed to allow a proper function of the ViperFX. Still bootloader locked, so I cannot support by then.
catalindobre said:
take a look on mi8 or mi a1 forum in xda, there is described exactly which modules in Magisk must be installed to allow a proper function of the ViperFX. Still bootloader locked, so I cannot support by then.
Click to expand...
Click to collapse
my bootloader is unlocked to flash magisk, why it doesn't works with unlocked bootloader?
nikzodiac said:
my bootloader is unlocked to flash magisk, why it doesn't works with unlocked bootloader?
Click to expand...
Click to collapse
It only works with unlocked BL ofc. Did you tried installing "Audio Modification Library", and "Audio Compatibility Patch" from Magisk repo?
darek1995 said:
It only works with unlocked BL ofc. Did you tried installing "Audio Modification Library", and "Audio Compatibility Patch" from Magisk repo?
Click to expand...
Click to collapse
no, what I've to do exactly? I'm not an expert of modding.. thanks
make sure to have installed Magisk Manager, also latest Magisk root installed via TWRP. After this it should be pretty simple, look for the afore mentioned modules in Magisk install them one by one (each single one might require a reboot). After installing them you may install ViperFX, (version 2.3.4 as a system app).
catalindobre said:
make sure to have installed Magisk Manager, also latest Magisk root installed via TWRP. After this it should be pretty simple, look for the afore mentioned modules in Magisk install them one by one (each single one might require a reboot). After installing them you may install ViperFX, (version 2.3.4 as a system app).
Click to expand...
Click to collapse
hi, I tried to do everything you said, no one difference..
in a few days when the unlocking time will end will try it myself and in case will make it work, I will post here the process steps.
You have to install the legacy version with lib workaround. For me its working or you can try the rootless version from team_dewitt (look here in xda for it) you only need twrp and init.d injector.
Try this one.
https://forum.xda-developers.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651
Just to install the apk, nothing else.
Working here like a charm
Hi, I tried the version linked by pokko, it works, but I can't find the way to encrease volume, it works just to have a lower volume, If I set the master volume value higher it doesn't encrease, seems like the stock volume.. is there a way to have an higher volume for the speakers?
thanks
2.7.0/2.7.1 working great on MIUI but with GSI roms it's a different story
if someone can tell me how to get an higher volume please let me know soon.. I'm really thinking to remove root frome my phone.. I've found no one good reason to have it, I don't want to change rom, so I did it just to have 3 things: adaway, encrease volume and use ps3 controller with bluetooth...
adaway doesn't block anything in site that I tried it,
with viper4android my speaker volume is still the same..
miui seems not compatible with ps3 controller.. sixaxis compatibility checker can't works with bluetooth..
the only good thing I've found is the modded youtube version with no ads and background player.. but I've seen exist a versione for no rooted phones too..
Has anyone been able to get Viper4Android working an Android 11? i flashed using the April 2021 Factory Image and have tried following multiple threads and guides, but have never gotten V4A to work consistently/completely.
Viper4android Android 11??
There is viper4android for android11 or I need to wait?
forum.xda-developers.com
This is the Viper4Android I've used for 6+ months. Its the only working, plug and play version I've found for Android 11. You simply download the zip, flash in magisk -- and done. There's nothing else you need to do.
Its 100% safe. Its 100% working. So easy.
I can vouch for it... And love it!
Click on the youtube link, and the zip is in the info there. No need to watch the video. Just flash with magisk or a kernel manager... and done.
I'm on LineageOS for microG 18.1, Proton kernel 1.4, Magisk rooted and this is not working for me. Further more, it mess up with SElinux making it disabled. Fortunatelly, there is an app SElinux switch, that on every boot make it Enforcing again.
I have the 5a but there are no posts yet.....
are any of you getting V4a to work using the USB port ? I run my phone usually into a dac via the usb, but Viper's only working on my phone through the headphone jack.
That YouTube video has been removed. Any chance someone could post the .zip? TIA
Root with magisk and install the Viper plugin, works like a charm on my 4a 5G. Not much else to it.
mmarcz said:
Root with magisk and install the Viper plugin, works like a charm on my 4a 5G. Not much else to it.
Click to expand...
Click to collapse
Not as simple as that for me I'm afraid. Magisk module causes bootloop.
Had the ViperFX_Android11.zip before from that same YT vid (purple/white GUI) and it worked well.
No luck or erratic performance with other versions (black/green GUI), the one from the guy with the name that looks Thai -- Pittanddwwitt idk lol.
Are you rooted normally with magisk per the instructions in this forum? Thats all I've done. Do you have a phone from google or from a carrier?
I got mine from google. Im rooted per the normal instructions. I have magisk v2.7.2.1 and the magiskhide props config modules installed. Ive never had a bootloop with either.
Not really sure what else to try. For what its worth, I cant get viper working on a rooted pixel 3, no bootloops, but the status always says abnormal.
Danny St. Angelo said:
Not as simple as that for me I'm afraid. Magisk module causes bootloop.
Had the ViperFX_Android11.zip before from that same YT vid (purple/white GUI) and it worked well.
No luck or erratic performance with other versions (black/green GUI), the one from the guy with the name that looks Thai -- Pittanddwwitt idk lol.
Click to expand...
Click to collapse
mmarcz said:
Are you rooted normally with magisk per the instructions in this forum?
Click to expand...
Click to collapse
Yes. And updating using this thread (thank you @drdionysius).
(Thanks for the reply btw.)
mmarcz said:
Do you have a phone from google or from a carrier?
Click to expand...
Click to collapse
Bought from a 3rd party actually, sealed box, no carrier branding or firmware.
Magisk version (from Canary channel) is f822ca5b (23001) -- that doesn't look right lol... oh, and Systemless hosts module installed only.
I only lost Viper when I updated to the September factory image
<shrug> idk why </shrug->
don't think it happened with other updates.
I'm pretty sure tho that I'd be in top shape, also indebted, if someone could post ViperFX_Android11.zip since the above referenced YouTube vid is gone and, with it, the link and I can't find the same version anywhere else. Thank you very much.
I just received my used 4a 5g. Got V4A v2.7.2.1 downloaded from Magisk v23 working last night...but it was a long trial & error ordeal. First download it showed Unsupported and Abnormal. Thought maybe it needed the Audio Mod Library but that didn't work. Then I tried the Audio Compatibility Patch to no avail. I tried V4A Legacy. Mulitple installs and uninstalls of all the various modules and combinations. At this point I'm not even sure what I did, or in what order/combination, but V4A is installed and working as intended. I do NOT have any of the Audio modules installed, just V4A. Don't know why it didn't work originally, or what made it finally work after fiddling with it for about an hour, but for me, that's my story/advice. Wish I could give an exact process to follow.
Here you go
mmarcz said:
Here you go
Click to expand...
Click to collapse
Top man!
Thank you
mmarcz said:
Here you go
Click to expand...
Click to collapse
Thanks for posting this! The version I had (v2.7.2.1) didn't work as reliably as it should. Often times it wasn't "processing". I uninstalled it and installed yours. So far it seems to be working well.
BIG BONUS - your version allows to view settings for the speaker, ear-buds, & blue-tooth without actually being connected to said devices. I never liked that "feature" of the newer V4A versions.
what about android 13?