Installing Viper4Android

Lossyx

Senior Member
Jan 14, 2014
1,320
492
103
Still not seeing modules?? Am I doing wrong commands? When I CD adb it says no file or directory?
You sure you have magisk installed?

Do
"cd data", then "ls" and post back.
If there adb folder is there, take a picture, cd into it and "ls" again and take a picture.

Sent from my OnePlus7TPro using XDA Labs
 

Calvin1997

Senior Member
Jan 21, 2016
60
9
0
Gelsenkirchen
This worked perfectly for me! It was a bit akward to cause a non-bootable state to the device but everything was fine. Had to install V4A driver and remove the post-fs file twice but after that it worked! Now I can enjoy my Music again. Thanks for your guide!
 

elmor0

Senior Member
Mar 20, 2009
527
81
58
Rooted HD1913 (still on stock recovery). No SE-linux permissive.

I installed V4A module via Magisk --> rebooted fine --> agreed to install V4A driver as per prompt --> now stuck in fastboot loop.

What is the best way out of this? - Without loss of data or any wipe.
 

kirschdog1

Senior Member
May 12, 2010
1,377
173
93
Saint Paul
you seem to be doing "is" instead of "ls".

try doing ls
I tried both Is and is neither worked. Both ways said inaccessible. I have a feeling that this is not working on my device OnePlus 7t pro 5g as whatever modded recovery I'm using (tried multiples) is not able to access adb. I get as far as cd data and then the next command for adb says inaccessible. I'm highly skeptical that anyone has this working on OnePlus 7t pro McLaren 5g model!!
 
Last edited:

chiiiiiiippppppp

Senior Member
Dec 14, 2013
69
32
38
I tried both Is and is neither worked. Both ways said inaccessible. I have a feeling that this is not working on my device OnePlus 7t pro 5g as whatever modded recovery I'm using (tried multiples) is not able to access adb. I get as far as cd data and then the next command for adb says inaccessible. I'm highly skeptical that anyone has this working on OnePlus 7t pro McLaren 5g model!!
I did have a similar problem after I upgraded from 10.0.3 to 10.0.4.

I could do an ls in the root folder and see everything including the data folder. I could cd to data, but then couldn't see anything inside the data folder.

Basically the upgrading process had encrypted my device.

The only way I found to sort this out was to use the MSM / Unbrick tool to get back to 10.0.3. I then applied the recovery with adb access and was once again able to see everything inside data and cd to adb and below.

Not sure if this is the same problem, but sounds very similar.
 

kirschdog1

Senior Member
May 12, 2010
1,377
173
93
Saint Paul
I did have a similar problem after I upgraded from 10.0.3 to 10.0.4.

I could do an ls in the root folder and see everything including the data folder. I could cd to data, but then couldn't see anything inside the data folder.

Basically the upgrading process had encrypted my device.

The only way I found to sort this out was to use the MSM / Unbrick tool to get back to 10.0.3. I then applied the recovery with adb access and was once again able to see everything inside data and cd to adb and below.

Not sure if this is the same problem, but sounds very similar.
Won't work for my device. I'm on OnePlus 7t pro McLaren and there is no msm or firmware as of yet. Thanks for letting me know!
 

kirschdog1

Senior Member
May 12, 2010
1,377
173
93
Saint Paul
It is definitely working. Looks like once you typed adb shell you were able to get cd data but I don't know what happened after that. I hope you get it figured out. Wish I could help more.
It never asks me for my password Even after using msm.

---------- Post added at 03:03 AM ---------- Previous post was at 03:02 AM ----------

I did have a similar problem after I upgraded from 10.0.3 to 10.0.4.

I could do an ls in the root folder and see everything including the data folder. I could cd to data, but then couldn't see anything inside the data folder.

Basically the upgrading process had encrypted my device.

The only way I found to sort this out was to use the MSM / Unbrick tool to get back to 10.0.3. I then applied the recovery with adb access and was once again able to see everything inside data and cd to adb and below.

Not sure if this is the same problem, but sounds very similar.
Used msm still no go. I am losing my mind. Don't get why I can't get this to work just can't get past cd data and then I type adb and it always says inaccessible
 
Last edited:

pyaa

Member
Mar 20, 2008
44
12
0
I just wanted to share some info. I have been trying to get this working for a while and kept getting stuck at fastboot. So last night I tried again. I have the T-Mobile McLaren 5g and I know kirschdog1 has been trying to figure this out so hope this helps.

Installed SE permissive switcher app
Set to permissive
Installed Viper4android
Installed driver then reboots to fastboot
I downloaded the 10.0.5 recovery with adb because the previous version didn't work for me.
Flashed recovery
Reboot recovery
Type password
Adb shell
cd data/adb/modules/ViPER4AndroidFX
rm post-fs-data.sh
Reboot
Open V4A and enable everything
Reboot

This is exactly how I typed and installed it and it worked. Hope this helps out.
I tried this on my 5G using the 10.0.5 recovery with ADB and couldn’t replicate. I could adb shell but my data folder was empty. Where you on 10.0.19 or 10.0.13?
 

aleck0112

Senior Member
Jan 5, 2017
192
53
0
guys I used the latest 2.7.10 apk and did not need to do the adb step. But I can't get viper to process, it shows Status abnormal, audio format unsupported and not processing. I disabled absolute volume, switched SElinux back to permissive, even installed audio mod library and it doesnt work. Please help
 

v.konvict

Senior Member
Dec 1, 2012
1,657
928
143
Mwanza
guys I used the latest 2.7.10 apk and did not need to do the adb step. But I can't get viper to process, it shows Status abnormal, audio format unsupported and not processing. I disabled absolute volume, switched SElinux back to permissive, even installed audio mod library and it doesnt work. Please help
Dude there is a reason why this thread was created. Please read the instructions and follow them if you want viper working on your phone.