Database Info

How do I install Viper4Android on pixel 2 8.1?

Asking this because the installing the drivers give me i/o error message unable to install.

atifaslam7 said:
Asking this because the installing the drivers give me i/o error message unable to install.
Click to expand...
Click to collapse
I have Viper4Android working on ElementalX kernel, Magisk 14.5 using Ahrion's Viper4Android downloaded through Magisk. The module was also flashed though Magisk. Working great so far!

kinfam said:
I have Viper4Android working on ElementalX kernel, Magisk 14.5 using Ahrion's Viper4Android downloaded through Magisk. The module was also flashed though Magisk. Working great so far!
Click to expand...
Click to collapse
Thanks I just tried it, yep it installed the drivers, time to test if everything works perfect now

[MOD] Remove Navbar - Root 8.1 beta 1

I had a request to make a Magisk friendly mod to remove the navbar. I don't have this phone and so this has not been tested by me. Thanks to @Fede Luzzi for the necessary files and testing. His steps for a successful install is as follows:
Version 8.1 beta 1, disable lockscreen security for twrp to work.
Flash twrp via fastboot via :
Fastboot flash boot xxxx.img
Boot into recovery
Flash boot IMG for versión 8.1 beta.
Flash magisk 15.3
Flash Tulsadiver zip
Boot
Navbar Gone Magisk zip
https://www.androidfilehost.com/?fid=890129502657583766

@Fede Luzzi,
I have an Magisk aroma mod module maker for you or someone to try. Flash in TWRP. Install the first selection that is a base (it is already selected). Select any mods you want in the Aroma. Hit next. Magisk module maker is already selected for you. Hit next again. A magisk.zip is created on your sdcard in a folder called Magisk. When back in TWRP go find that zip and flash it.
Have a backup though I included a return to stock mod.
There are center clock mods which obviously do you no good with that sensor in the middle of your screen but I left them there anyway.
https://www.androidfilehost.com/?fid=673956719939820683

Tulsadiver said:
@Fede Luzzi,
I have an Magisk aroma mod module maker for you or someone to try. Flash in TWRP. Install the first selection that is a base (it is already selected). Select any mods you want in the Aroma. Hit next. Magisk module maker is already selected for you. Hit next again. A magisk.zip is created on your sdcard in a folder called Magisk. When back in TWRP go find that zip and flash it.
Have a backup though I included a return to stock mod.
There are center clock mods which obviously do you no good with that sensor in the middle of your screen but I left them there anyway.
https://www.androidfilehost.com/?fid=673956719939820683
Click to expand...
Click to collapse
Thanks man!I'll try it during the week and let you know!

Fede Luzzi said:
Thanks man!I'll try it during the week and let you know!
Click to expand...
Click to collapse
Hey, I didn't need any if the mods but anyway I tested it, and it didn't work, it breaks magisk I needed to reinstall it.

Fede Luzzi said:
Hey, I didn't need any if the mods but anyway I tested it, and it didn't work, it breaks magisk I needed to reinstall it.
Click to expand...
Click to collapse
That's too bad. Works great on the pixels and Nexus phones.

Tulsadiver said:
I had a request to make a Magisk friendly mod to remove the navbar. I don't have this phone and so this has not been tested by me. Thanks to @Fede Luzzi for the necessary files and testing. His steps for a successful install is as follows:
Version 8.1 beta 1, disable lockscreen security for twrp to work.
Flash twrp via fastboot via :
Fastboot flash boot xxxx.img
Boot into recovery
Flash boot IMG for versión 8.1 beta.
Flash magisk 15.3
Flash Tulsadiver zip
Boot
Navbar Gone Magisk zip
https://www.androidfilehost.com/?fid=890129502657583766
Click to expand...
Click to collapse
Hi !
I had an issue with my phone and i made a full wipe, when i was trying to install your mod (i love it ) i found out that with the last magisk 16, your installer is not able to detect magisk so it wont install. I had to install magisk 15.3, install your mod, then update to magisk 16.
I want to inform you because probably this is happening with all your magisk mods.
THanks for the great work!!

Fede Luzzi said:
Hi !
I had an issue with my phone and i made a full wipe, when i was trying to install your mod (i love it ) i found out that with the last magisk 16, your installer is not able to detect magisk so it wont install. I had to install magisk 15.3, install your mod, then update to magisk 16.
I want to inform you because probably this is happening with all your magisk mods.
THanks for the great work!!
Click to expand...
Click to collapse
Nope, still working on all my phones ?

..

【HELP!】Installed a module in Magisk Download manager and now i'm f*****

Sup guys, i had this problem with the SafetyNet Check that always kept failing, done some tutorials here at the forum but none of them worked, so i gave up... yesterday i was searching for some modules at the download page in the Magisk Manager app and found a module that was supposed to correct SafatyNet problema, after that installation my Magisk don't want to open anymore, all my modules still installed but i can't open the app anymore, i rooted my cellphone without TWRP so i can't use it to manage the dependencies of the app... any suggestion?
obs.: I'm not using TWRP cuz i just keep having a problem at the installation, i'm runnig the last version of the Android Pie OS (Beta 3)

You could temporarily boot into TWRP via ADB and a PC and flash the uninstaller.

DiGtal said:
You could temporarily boot into TWRP via ADB and a PC and flash the uninstaller.
Click to expand...
Click to collapse
He can boot it through fastboot, adb push the uninstaller and flash it.*
But isn't the safetynet fix just a build.prop tweak?
He can technically adb pull the build.prop, fix it and put it back in. Or just take a working build.prop from a fellow OB3 user ( me included ) and push it into the system through adb.

The Marionette said:
He can boot it through fastboot, adb push the uninstaller and flash it.*
But isn't the safetynet fix just a build.prop tweak?
He can technically adb pull the build.prop, fix it and put it back in. Or just take a working build.prop from a fellow OB3 user ( me included ) and push it into the system through adb.
Click to expand...
Click to collapse
I think the OP mentioned the problem they are having is from a Magisk module that is incompatible with the OP6. My recommendation, without TWRP on the phone, might be a Fastboot Rom to get your phone functional again.

tabletalker7 said:
I think the OP mentioned the problem they are having is from a Magisk module that is incompatible with the OP6. My recommendation, without TWRP on the phone, might be a Fastboot Rom to get your phone functional again.
Click to expand...
Click to collapse
I know that and the OP probably does too, but I guess they don't want to lose their current data?

The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
I don't know if that can be helped at this point. That bad Magisk module may have made that decision for him

The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
That's right, i know that i can fix this issue just installing the ROM again but i don't want to lose my data, i just want to delete a specific module from Magisk

s3nn4 said:
That's right, i know that i can fix this issue just installing the ROM again but i don't want to lose my data, i just want to delete a specific module from Magisk
Click to expand...
Click to collapse
restore stock boot.img. no root, no mods to load. fix it then reroot.

You don't need to restore. Follow this guide: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
It's called CoreOnlyMode4Magisk and it's flashed through TWRP. Magisk modules are systemless and this module will fix your problem.

mdl054 said:
You don't need to restore. Follow this guide: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
It's called CoreOnlyMode4Magisk and it's flashed through TWRP. Magisk modules are systemless and this module will fix your problem.
Click to expand...
Click to collapse
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3

MrSteelX said:
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
Click to expand...
Click to collapse
Oh sorry I missed that part

You can use the modified boot.img with TWRP preinstalled from the OB3 thread:
https://forum.xda-developers.com/showpost.php?p=77390204&postcount=2

Just reflash OB3 from system updater and that will get rid of root and also keep your data. Then start over.
Sent from my OnePlus6 using XDA Labs

The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
MrSteelX said:
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
Click to expand...
Click to collapse
Already fixed it, installed the last version of blu spark TWRP along with the Magisk 17.2, all perfect, had a problem with my OS at the beginning but just flashed again and did all the process to root, thanks for your help!

Next time don't be a twrp and use twrp

dgunn said:
Next time don't be a twrp and use twrp
Click to expand...
Click to collapse
The last update wouldn't let me install it, the Blu stuff made my day when I saw the compatible update

Guide to get Viper working on Android 10 custom ROMs

Here's what I did to get Viper working on Android 10 custom ROMs on Poco F1, I've looked at various methods from different sources and this finally worked for me.
Note that I'm not responsible for anything that happens to your device!
1. Reboot into recovery, flash v4a_rootless zip (drivers)
2. Flash Audio-Modification-Library in recovery
3. Reboot to system
4. Flash v4afx_2.7.1.0 in magisk
5. Change SELinux to permissive and reboot
Note that if your ROM is already permissive then it must work after step 4 and reboot
Tested on Havoc OS 3.0
Need SELinux enforcing? Try this: https://forum.xda-developers.com/showpost.php?p=81138825&postcount=16

It worked! I can't believe finally something worked! I can't thank you enough man!

Will this magisk module cause bootloop?

It worked for me too. Thanks so much

3arllscn said:
Will this magisk module cause bootloop?
Click to expand...
Click to collapse
Not if you followed the instructions prior to flashing it (manual drivers and aml from twrp)

viv29 said:
Here's what I did to get Viper working on Android 10 custom ROMs on Poco F1, I've looked at various methods from different sources and this finally worked for me.
Note that I'm not responsible for anything that happens to your device!
1. Reboot into recovery, flash v4a_rootless zip (drivers)
2. Flash Audio-Modification-Library in recovery
3. Reboot to system
4. Flash v4afx_2.7.1.0 in magisk
5. Change SELinux to permissive and reboot
Note that if your ROM is already permissive then it must work after step 4 and reboot
Tested on Havoc OS 3.0
Click to expand...
Click to collapse
How about Bluetooth headset?

viv29 said:
Not if you followed the instructions prior to flashing it (manual drivers and aml from twrp)
Click to expand...
Click to collapse
Thanks man it's 100% :working ?

faxel said:
How about Bluetooth headset?
Click to expand...
Click to collapse
Don't have one so can't check.

Viper and music players crash/hang when I have viper activated on bluetooth devices
tested on latest cRdroid 6.0

Not working

Sunemol said:
Not working
Click to expand...
Click to collapse
You need to connect to the internet. The installer downloads the latest apk, then the installation will continue.
---------- Post added at 08:00 AM ---------- Previous post was at 08:00 AM ----------
Works like a charm, thank you very much!!!!!

Sunemol said:
Not working
Click to expand...
Click to collapse
Viper installation in magisk needs internet connection

Edit: fixed after installing drivers zip again n removing audio mod from magisk.
But V4a stops working once u toggle on off button. U gotta stop the app and start it again to make it work with V4a ? if u toggle on button on V4a without fcing app it won't work

And what about Dolby Atmos there is any solution

abdohop said:
And what about Dolby Atmos there is any solution
Click to expand...
Click to collapse
haven't tried it myself yet.

I found another method which works with SELinux enforcing. Needs magisk installed.
1. Install the 2.7.1.0 viper apk from XDA Labs
2. Open the apk, grant it superuser access and press restart on the popup
3. Press power+volume up to go into recovery while it is restarting (dont let it restart, go into recovery instead)
4. Go to terminal in TWRP and navigate to /data/adb/modules/ViPER4AndroidFX by doing this:
cd /data/adb/modules/ViPER4AndroidFX
5. Now rename the post-fs-data.sh to something else like post-fs-data.sh.bak or delete it by doing this:
mv post-fs-data.sh post-fs-data.sh.bak
6. You're all done, restart into system now.
NOTE: Turning off master limiter and setting it back on doesnt work. It has to be on by default all the time (probably it enables at startup and cant be toggled)
If you encounter a bootloop delete ViPER4AndroidFX inside /data/adb/modules
rm -rf /data/adb/modules/ViPER4AndroidFX

For some reason, the above method is not working for me. On latest Havoc OS build 8/12/19. First time I follow the above steps Viper still gives a pop up saying drivers not installed. I click on install again, follow the same renaming method. Second time Viper opens but driver status is abnormal.

Anubhav997 said:
For some reason, the above method is not working for me. On latest Havoc OS build 8/12/19. First time I follow the above steps Viper still gives a pop up saying drivers not installed. I click on install again, follow the same renaming method. Second time Viper opens but driver status is abnormal.
Click to expand...
Click to collapse
Try changing selinux to permissive :/ looks like there's no other option for now :/

Anubhav997 said:
For some reason, the above method is not working for me. On latest Havoc OS build 8/12/19. First time I follow the above steps Viper still gives a pop up saying drivers not installed. I click on install again, follow the same renaming method. Second time Viper opens but driver status is abnormal.
Click to expand...
Click to collapse
Working for me OnePlus 3T and OnePlus 5 both with Newest Havoc Rom.

viv29 said:
Try changing selinux to permissive :/ looks like there's no other option for now :/
Click to expand...
Click to collapse
Yup this works. No doubt.
I guess I'll stay with android 9 for a while. Need SELinux enforcing and Viper also

Busybox for CrDroid Android 9

Hey, I needed a little help. I was trying to get busybox installed so I can run Viper4Android. Downloaded the busybox installer from the market and went through the typical in-App installation. Went for the reboot and got into a bootloop.
So my question is... How do we get busybox for our G7 Power? What's the preferred method?
Thanks in advance!

Their is a module on magisk for it

DonSolo said:
Hey, I needed a little help. I was trying to get busybox installed so I can run Viper4Android. Downloaded the busybox installer from the market and went through the typical in-App installation. Went for the reboot and got into a bootloop.
So my question is... How do we get busybox for our G7 Power? What's the preferred method?
Thanks in advance!
Click to expand...
Click to collapse
BusyBox is not needed. I have Viper 4 Android running on CrDroid and just have Magisk installed. Magisk root has BusyBox working already in the background.

vi
Rondeau79 said:
BusyBox is not needed. I have Viper 4 Android running on CrDroid and just have Magisk installed. Magisk root has BusyBox working already in the background.
Click to expand...
Click to collapse
B__B said:
Their is a module on magisk for it
Click to expand...
Click to collapse
Every time I try to run Viper4Android without busybox it gives me errors about it not being installed. I'll try the magisk module and report my findings here. Thanks guys

This happens each time I try without magisk
Tried the magisk busybox module.... bootloop lol

DonSolo said:
This happens each time I try without magisk
Tried the magisk busybox module.... bootloop lol
Click to expand...
Click to collapse
im using this module without any issue on crdroid

vinoxflame said:
im using this module without any issue on crdroid
Click to expand...
Click to collapse
WTF lol
What version of Magisk are you running?

Ok so I got it to work... Turns out I was using the "HiFi" version... Tried the regular FX and it worked like a charm.
Thanks you guys! This is why XDA exist! I've been around for a very long time and this site never disappoints!!
If a Mod could close the thread that'd be cool... Problem solved here!