After days of trying numerous different ways I've finally managed to get Viper to work my Oneplus 7T Pro
You will need to have a modded recovery with adb enabled:-
https://forum.xda-developers.com/7t-pro/development/recovery-oxygen-os-stock-recovery-adb-t3991865
First I removed the any previous Viper module in Magisk and rebooted.
I then uninstalled the Viper App and rebooted again.
So I then had a clean starting point.
I installed The SELinux Switch app from XDA to set SELinux mode to Permissive:-
https://forum.xda-developers.com/and...witch-t3656502
I turned off Google Play Protect.
I then installed the version 2.7.1.0 module in Magisk.
Installed driver and it rebooted.
Stuck at Fastboot screen.
Reboot to Recovery
I then did the following in adb to delete the post-fs-data.sh file which is the file that stops the phone booting.
1) adb shell
2)cd to /data/adb/modules/ViPER4AndroidFX
3)rm post-fs-data.sh
4)exit
reboot to Fastboot and then Start
Then it just worked.
Hopefully this method will work for others.
Sounds cool. Congratulations
Wrong thread!
Legend!!!
Wouldn't it be easier to just make a viper zip without postfs data?
f41lbl0g said:
Wouldn't it be easier to just make a viper zip without postfs data?
Click to expand...
Click to collapse
I don't know how to do that.
That would be a question for the people who write Viper.
f41lbl0g said:
Wouldn't it be easier to just make a viper zip without postfs data?
Click to expand...
Click to collapse
We don't have the source of the module, and you can't just take the installed module folder and zip it to a module so I don't think it's possible.
Might be wrong though.
Sent from my OnePlus7TPro using XDA Labs
thanks mate. worked for me too. finally
Edit: it is not processing on Bluetooth devices
Here try this zip I modified, it should work fine on the OP7T and OP7T Pro if this fix does indeed work. Shouldn't need any custom recovery or adb. Can someone report if my modified file works? If it doesn't just use the custom recovery with adb to remove the module.
Note: Selinux will need to be changed to permissive before installing the module using this:
https://forum.xda-developers.com/android/apps-games/app-selinux-switch-t3656502
All credits to:
- @ahrion
- @zhuhang
- @osm0sis
- Viper's Audio (Official blog)
- @viper520
- @Team_DeWitt
f41lbl0g said:
Here try this zip I modified, it should work fine on the OP7T and OP7T Pro if this fix does indeed work. Shouldn't need any custom recovery or adb. Can someone report if my modified file works? If it doesn't just use the custom recovery with adb to remove the module.
Note: Selinux will need to be changed to permissive before installing the module using this:
https://forum.xda-developers.com/android/apps-games/app-selinux-switch-t3656502
All credits to:
- @ahrion
- @zhuhang
- @osm0sis
- Viper's Audio (Official blog)
- @viper520
- @Team_DeWitt
Click to expand...
Click to collapse
You will have to make this steps to make it work.These steps are from the original thread and for my situation the module It didnt worked properly.
I have flashed your zip with magisk manager,I havent rebooted,I have installed the drivers from Viper and then I rebooted. I got stucked in fastboot. I had to make rm post-fs-data.sh to force the phone get fixed from the loop.Then I have opened Viper and then asked me again to install the drivers.Then I got stucked again and I had to put the same command through adb shell rm post-fs-data.sh. After that It did worked but I dont know why its not working with your module.
Alexisd1 said:
You will have to make this steps to make it work.These steps are from the original thread and for my situation the module It didnt worked properly.
I have flashed your zip with magisk manager,I havent rebooted,I have installed the drivers from Viper and then I rebooted. I got stucked in fastboot. I had to make rm post-fs-data.sh to force the phone get fixed from the loop.Then I have opened Viper and then asked me again to install the drivers.Then I got stucked again and I had to put the same command through adb shell rm post-fs-data.sh. After that It did worked but I dont know why its not working with your module.
Click to expand...
Click to collapse
Did you make selinux permissive?
f41lbl0g said:
Did you make selinux permissive?
Click to expand...
Click to collapse
Yes i turned the selinux permissive from the beginning. I haven't mentioned that because I forgot it by mistake
Alexisd1 said:
You will have to make this steps to make it work.These steps are from the original thread and for my situation the module It didnt worked properly.
I have flashed your zip with magisk manager,I havent rebooted,I have installed the drivers from Viper and then I rebooted. I got stucked in fastboot. I had to make rm post-fs-data.sh to force the phone get fixed from the loop.Then I have opened Viper and then asked me again to install the drivers.Then I got stucked again and I had to put the same command through adb shell rm post-fs-data.sh. After that It did worked but I dont know why its not working with your module.
Click to expand...
Click to collapse
I had the same. I had to install and delete the .sh twice until it worked. And it works fine.
Alexisd1 said:
You will have to make this steps to make it work.These steps are from the original thread and for my situation the module It didnt worked properly.
I have flashed your zip with magisk manager,I havent rebooted,I have installed the drivers from Viper and then I rebooted. I got stucked in fastboot. I had to make rm post-fs-data.sh to force the phone get fixed from the loop.Then I have opened Viper and then asked me again to install the drivers.Then I got stucked again and I had to put the same command through adb shell rm post-fs-data.sh. After that It did worked but I dont know why its not working with your module.
Click to expand...
Click to collapse
c0caine_train said:
I had the same. I had to install and delete the .sh twice until it worked. And it works fine.
Click to expand...
Click to collapse
At this point just flash the zip from the original post, don't use my zip. I'll test it out more once my phone arrives.
Do you need to keep selinux permissive to continue to use Viper due to deletion of the .sh? Or can one toggle it back post this process?
Wow, this Viper4android seems to be a pain for our phones. I already tried it approximately 5 times and having to use the MSM tool to be able to boot up again from scratch I'm coming from a different flagship and I never had a problem rooting and installing apps like Viper4android before. I don't know if it would be too much to ask. that once someone has found a proven successful method to please share. I don't want to seem lazy I've been searching all over and so far the methods are not definite and very frustrating. Ive had my phone for a week still adjusting. Anyway any help would be appreciated and please no offensive comments. Thanks
slapman said:
Wow, this Viper4android seems to be a pain for our phones. I already tried it approximately 5 times and having to use the MSM tool to be able to boot up again from scratch I'm coming from a different flagship and I never had a problem rooting and installing apps like Viper4android before. I don't know if it would be too much to ask. that once someone has found a proven successful method to please share. I don't want to seem lazy I've been searching all over and so far the methods are not definite and very frustrating. Ive had my phone for a week still adjusting. Anyway any help would be appreciated and please no offensive comments. Thanks
Click to expand...
Click to collapse
Yeah, read the first post...
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
Yeah, read the first post...
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Yes, I did read the post but I just don't want to mess up the phone again. Maybe Ill try again when my mind is fresh had to many mishaps but thanks.
slapman said:
Yes, I did read the post but I just don't want to mess up the phone again. Maybe Ill try again when my mind is fresh had to many mishaps but thanks.
Click to expand...
Click to collapse
Which version do you have? EU or international?
This recovery works fine in EU version, if there's is anything that messes up it's likely a module, which can easily be removed with the modded recovery.
Sent from my OnePlus7TPro using XDA Labs
When I try to cd to /data/adb/modules/ViPER4AndroidFX I get cd: bad substitution
I'm on OOS 10.0.4 (international ver.) with modified recovery for ADB.
Related
(Unlocked Model, Unlocked, S-Off, Verizon RUU, rooted)
I have tried installing V4A, but after installing drivers it hangs upon opening, eventually causing the phone to reboot.
I have tried both backing up and renaming the htc_audio_effects.conf file, as well as editing it to include the V4A info. Nothing seems to work.
Any ideas?
First of all you need root. You have to set Android to permissive, then install V4A using TWRP and ZIP. Install drivbers and it will work AFTER you set V4A driver mode to "compatible". Just tested using latest Leedroid custom rom (nightly R34) on HTC 10 (s-off).
dragon-tmd said:
First of all you need root. You have to set Android to permissive, then install V4A using TWRP and ZIP. Install drivbers and it will work AFTER you set V4A driver mode to "compatible". Just tested using latest Leedroid custom rom (nightly R34) on HTC 10 (s-off).
Click to expand...
Click to collapse
What version did you use? I'm using Venom and I've done exactly what you did and Viper keeps prompting me to install the driver
holofractal said:
What version did you use? I'm using Venom and I've done exactly what you did and Viper keeps prompting me to install the driver
Click to expand...
Click to collapse
Uninstall the apk
Grab the 2 zips from this post:
http://forum.xda-developers.com/showthread.php?p=66996528
Flash in recovery. Spent all afternoon looking for proper install instructions and found nothing until that nice fellow posted those.
Viper4android did not work 100% using Leedroid: systemsound got crippled
Viper4android is working 100% with ViperROM. Just flash the above ZIP and all is working fine.
dragon-tmd said:
Viper4android did not work 100% using Leedroid: systemsound got crippled
Viper4android is working 100% with ViperROM. Just flash the above ZIP and all is working fine.
Click to expand...
Click to collapse
I'm on Leedroid 1.2 stable and works perfectly.
I did experience the crippled audio you're referring to during a failed installation. Make sure the /system/etc/htc_audio_effects.conf exists and wasn't deleted.
Heisenberg420 said:
Uninstall the apk
Grab the 2 zips from this post:
http://forum.xda-developers.com/showthread.php?p=66996528
Flash in recovery. Spent all afternoon looking for proper install instructions and found nothing until that nice fellow posted those.
Click to expand...
Click to collapse
I've tried this and it seems to not be working. The driver says it's active.
holofractal said:
I've tried this and it seems to not be working. The driver says it's active.
Click to expand...
Click to collapse
Try uninstalling the drivers and flash zip again
dragon-tmd said:
Viper4android did not work 100% using Leedroid: systemsound got crippled
Viper4android is working 100% with ViperROM. Just flash the above ZIP and all is working fine.
Click to expand...
Click to collapse
Which specific version did you flash? What changes did you make to get the best audio out of the 10?
holofractal said:
I've tried this and it seems to not be working. The driver says it's active.
Click to expand...
Click to collapse
Having the same problem. Tried everything.
Sent from my HTC 10 using Tapatalk
Do you have any idea whether it would work on stock rom or not? Of course I'm rooted and s-off.
Jonzu said:
Do you have any idea whether it would work on stock rom or not? Of course I'm rooted and s-off.
Click to expand...
Click to collapse
Check your selinux status it needs to be permissive for V4A to work.
Actually I installed it and it works. Kinda. And yes I used a script to get permissive selinux. It only works with music, (spotify, google music). Youtube has no sound whatsoever ar audible is crackling and fussing all over. "Fixed" it by changing the htcaudioeffect file back to normal, which disables viper4android. I just wish it worked with all sound.
First off I will say I am on Stock Rooted ROM and it works perfectly, I have confirmed its 100% compatible, You DO NOT have to use permissive, I have an Enforcing Patch in my thread along with more info on what you need to do to get it working, also for HTC 10 there is a specific file to flash that I also made, without it V4A will not work, and keep asking to install drivers!
My Thread
V4A HTC 10 Fix
After this, if you can't get it working either there is something you still haven't done or your ROM developer has messed up a certain system file associated with Audio, I have seen this before.
One last thing I should note, S-ON can cause issues, you should either have S-OFF or System Write Protection Disabled via a kernel module, S-ON can prevent a script from making changes to /System.
About V4A
On the A9 it will work but it will put Boomsound to Off all the time, is it the same on the 10 or you can use both without problem?
vegetaleb said:
About V4A
On the A9 it will work but it will put Boomsound to Off all the time, is it the same on the 10 or you can use both without problem?
Click to expand...
Click to collapse
I use both no problem, personal Profile and V4A works great, Dolby Headphone effect works perfectly as well.
I installed the 2 zips a couple of days ago and the sound is pretty great for me. I see people mentioning different profiles, enabling speaker and other modes, etc., but how can you do that without installing the APK (as advised not to)? I don't know of any other UI to control those types of things?
Heisenberg420 said:
Check your selinux status it needs to be permissive for V4A to work.
Click to expand...
Click to collapse
how do i change my selinux status to permissive?? i want to try viper4android and make sure i install it correct. i dont know this step.
Can't install SuperSU on Huawei Watch 1 "Patching sepolicy ---Failure, aborting"
I apologize if this is a noob question. I'm no stranger to modding Android devices; only new to modding Wear devices, and unfortunately information about rooting this watch is so sparse (understandably) and I couldn't find anyone with the same issue when searching. So like the title says, I can't get SuperSU installed on my Hwatch running AW 2.0. When I try to install SuperSU via TWRP, it gets stuck when trying to patch sepolicy.
Do I need a custom kernel for this? Is there one with no modifications other than the sepolicy? Or is there a way to change the sepolicy on the stock kernel. Between the guides I've read and WinDroid Toolkit, nothing has mentioned needing to do anything else to allow flashing SuperSU, but I can't think of what else would be the cause of the issue and I suppose things could have changed since those guides and Windroid were written.
I kind of want to avoid custom kernels as they almost always have issues in my experience with running them on phones (no offense to any kernel devs out there) and I can't deal with that on something simple as a watch. I just want this rooted mostly so I can test out underclocking and powersave governor when needing some extra battery time and so the next time I flash or upgrade my phone, I don't have to wipe the watch.
Any help will be greatly appreciated. And if I must install a custom kernel, I would love recommendations on the most reliable and/or closest to stock one.
For me, WinDroid Toolkit doesn't work for rooting Android Wear 2.0. I am on AW2.0 with the stock kernel and I have rooted the device using Magisk v13.2. Magisk Manager works on Android Wear (even though it may be hard to use on a round screen), but SuperSU (app) crashes when I launch the app. All you have to do to install Magisk is to flash the latest Magisk installer in TWRP and sideload the latest Magisk Manager using adb. You can download Magisk here. I have tried SuperSU, but I would get an every time I try to flash the latest SuperSU zip.
Tristan Phan said:
For me, WinDroid Toolkit doesn't work for rooting Android Wear 2.0. I am on AW2.0 with the stock kernel and I have rooted the device using Magisk v13.2. Magisk Manager works on Android Wear (even though it may be hard to use on a round screen), but SuperSU (app) crashes when I launch the app. All you have to do to install Magisk is to flash the latest Magisk installer in TWRP and sideload the latest Magisk Manager using adb. You can download Magisk here. I have tried SuperSU, but I would get an error every time I try to flash the latest SuperSU zip.
Click to expand...
Click to collapse
Thank you! Sounds like we encountered the same issue when flashing SuperSU. I had thought about trying Magisk, but wasn't sure if it would cause some issues on Wear. Thanks to your positive report, though, I'm going to try it out when I get home later. :good:
neonixxx said:
Thank you! Sounds like we encountered the same issue when flashing SuperSU. I had thought about trying Magisk, but wasn't sure if it would cause some issues on Wear. Thanks to your positive report, though, I'm going to try it out when I get home later. :good:
Click to expand...
Click to collapse
I'd like to know if it works for you. ?
Tristan Phan said:
I'd like to know if it works for you.
Click to expand...
Click to collapse
It worked! I was unable to sideload Magisk Manager, though, but that's fine. I'm just stuck on v5.0.5 which works just fine for handling root requests.
That's great! The only real difference between Magisk Manager v5.0.6 and v5.0.5 is that v5.0.6 fixes a crash when downloading modules from the repo, so you shouldn't be that affected. If you want any modules, you can just download them from XDA or something and flash it in TWRP.
Tristan Phan said:
That's great! The only real difference between Magisk Manager v5.0.6 and v5.0.5 is that v5.0.6 fixes a crash when downloading modules from the repo, so you shouldn't be that affected. If you want any modules, you can just download them from XDA or something and flash it in TWRP.
Click to expand...
Click to collapse
Yeah, that's why I'm not bothering with it. I don't feel a need for any modules on my watch at the moment Thanks again for tipping me off that Magisk would work.
neonixxx said:
Yeah, that's why I'm not bothering with it. I don't feel a need for any modules on my watch at the moment Thanks again for tipping me off that Magisk would work.
Click to expand...
Click to collapse
Just saying (sorry to bother), but Magisk v13.3 came out and fixed SafetyNet bypass. If you want, you can update by flashing Magisk-v13.3 by flashing it in TWRP without needing to uninstall the previous version. Installing this should also update Magisk Manager to v5.1.0.
Tristan Phan said:
Just saying (sorry to bother), but Magisk v13.3 came out and fixed SafetyNet bypass. If you want, you can update by flashing Magisk-v13.3 by flashing it in TWRP without needing to uninstall the previous version. Installing this should also update Magisk Manager to v5.1.0.
Click to expand...
Click to collapse
No worries, haha. Yeah I already updated on my phone. Thought about updating the watch, but too lazy at the moment :silly: since I don't really need to pass SafetyNet on my watch for anything. Probably will do it later on.
I'm thinking that the reason that you couldn't install Magisk Manager v5.0.6 was that it was already installed by the Magisk-v13.2 zip and ADB wasn't able to install over the existing APK, but I'm still a noob so I have no idea.
Tristan Phan said:
I'm thinking that the reason that you couldn't install Magisk Manager v5.0.6 was that it was already installed by the Magisk-v13.2 zip and ADB wasn't able to install over the existing APK, but I'm still a noob so I have no idea.
Click to expand...
Click to collapse
Check the adb install switches in adb help to solve that. Use the -r or -d switch.
Code:
adb install [-lrtsd] <file>
- push this package file to the device and install it
(-l: forward lock application)
(-r: replace existing application)
(-t: allow test packages)
(-s: install application on sdcard)
(-d: allow version code downgrade)
Hello I have installed magisk and tried to install some module's but they're not showing up. Is magisk working fine on Android p beta 3?, Especially in terms of installing modules?
marvi0 said:
Hello I have installed magisk and tried to install some module's but they're not showing up. Is magisk working fine on Android p beta 3?, Especially in terms of installing modules?
Click to expand...
Click to collapse
Yes, it works for me and I installed couple of modules as well...
Great thanks will try again.
Wow I thought I was the only one. Modules not showing up here either and I've tried reinstalling in a bunch of different ways.
marvi0 said:
Hello I have installed magisk and tried to install some module's but they're not showing up. Is magisk working fine on Android p beta 3?, Especially in terms of installing modules?
Click to expand...
Click to collapse
marvi0 said:
Great thanks will try again.
Click to expand...
Click to collapse
gigatex said:
Wow I thought I was the only one. Modules not showing up here either and I've tried reinstalling in a bunch of different ways.
Click to expand...
Click to collapse
There's a list of modules out there that do/don't work on the developer previews. If I can find it again, I'll post a link :good:
Badger50 said:
There's a list of modules out there that do/don't work on the developer previews. If I can find it again, I'll post a link :good:
Click to expand...
Click to collapse
For me I noticed I have to reboot when I install each and every module. On my oneplus-5t I could install a bunch and then reboot once but on the pixel presumably due to the new firmware, you have to reboot after each module is installed and this definitely helped me.
Badger50 said:
There's a list of modules out there that do/don't work on the developer previews. If I can find it again, I'll post a link :good:
Click to expand...
Click to collapse
I don't think its a module specific compatibility issue. Every single module I try to install seems to install fine but just doesn't show up in the list of modules. I've tried a lot of different ones.
gigatex said:
I don't think its a module specific compatibility issue. Every single module I try to install seems to install fine but just doesn't show up in the list of modules. I've tried a lot of different ones.
Click to expand...
Click to collapse
Interesting. That's kinda weird because I've seen many users running them on the DP's. Does clearing magisk manager app cache/data help at all? And I'm sure you've granted storage permissions as well.
Badger50 said:
Interesting. That's kinda weird because I've seen many users running them on the DP's. Does clearing magisk manager app cache/data help at all? And I'm sure you've granted storage permissions as well.
Click to expand...
Click to collapse
Yep, tried that and also installing through manually patching boot image, flashing through TWRP and installing through direct installation through magisk manager. Sometimes the installation fails and on reboot it'll say it's installed but safetynet will fail. Even when it installs fine modules never work though. Module downloading is all fine, during installation it goes ahead just fine as well but the modules just don't show up in the list after installation/reboot.
gigatex said:
Yep, tried that and also installing through manually patching boot image, flashing through TWRP and installing through direct installation through magisk manager. Sometimes the installation fails and on reboot it'll say it's installed but safetynet will fail. Even when it installs fine modules never work though. Module downloading is all fine, during installation it goes ahead just fine as well but the modules just don't show up in the list after installation/reboot.
Click to expand...
Click to collapse
Don't know what to tell you my friend. Grab some install logs and head over to the magisk forums for some additional help is all I can suggest. I wish you luck :good:
I'm trying to figure out where i went wrong, because the last time i tried ROOTing PDP3, i couldnt boot and i am yet to see and PDP3 Patched_Boot.img or TWRP Recovery...
I did the following:
-Fastboot Flash-ALL PDP3
-Boot and set-up device PIN
-Boot into Fastboot
-Fastboot boot TWRP3212.img
-Use TWRP Installer to install Custom Recovery on device
-Reboot Recovery
-Flash Magisk v16.4
-REBOOT SYSTEM
-I think i ended up Looping @ G
Hey Can someone please find out a supported Viper4android for OP7T.
Installing through magisk gives a bootloop
Installing drivers directly through the Viper4android app too gives a Bootloop
Already tried the existing method updated on xda for getting Viper4android to work on android 10. Unfortunately it gives a bootloop too.
I've been racking my brain trying to find a solution, have yet to find one. All thus far end in bootloop.
Not giving up hope.
oneszero said:
I've been racking my brain trying to find a solution, have yet to find one. All thus far end in bootloop.
Not giving up hope.
Click to expand...
Click to collapse
Have you managed to remove the module? Or still in a bootloop?
Also, have you tried this one?
https://zackptg5.com/downloads/v4afx-rootless_08.18.2019.zip
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
Have you managed to remove the module? Or still in a bootloop?
Also, have you tried this one?
https://zackptg5.com/downloads/v4afx-rootless_08.18.2019.zip
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Is this one functional?
oneszero said:
Is this one functional?
Click to expand...
Click to collapse
I am not sure, I just thought if you've factory reset to remove the bootloop, I guess you have nothing to lose if you try this one. If that's not the case, you're in the same boat as me, not wanting to risk a factory reset in case it doesn't work. Not having a recovery really sucks...
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
Have you managed to remove the module? Or still in a bootloop?
Also, have you tried this one?
https://zackptg5.com/downloads/v4afx-rootless_08.18.2019.zip
Click to expand...
Click to collapse
I was able fix the boot loop if i flash the stock boot img. However someone posted a custom boot img just to get out of such a situation without any sort of factory reset.
Lossyx said:
Have you managed to remove the module? Or still in a bootloop?
Also, have you tried this one?
https://zackptg5.com/downloads/v4afx-rootless_08.18.2019.zip
Click to expand...
Click to collapse
Is it suppose to be flashed via magisk?
And can you share the original thread where you got this link from?
passi77 said:
I was able fix the boot loop if i flash the stock boot img. However someone posted a custom boot img just to get out of such a situation without any sort of factory reset.
Click to expand...
Click to collapse
Can you link the custom boot image?
https://forum.xda-developers.com/an...iper4android-fx-2-6-0-0-t3774651/post80054209
https://forum.xda-developers.com/an...iper4android-fx-2-6-0-0-t3774651/post80053180
This should be able to flash in EXKM or Franco kernel Manager. It zip uses anykernel which makes be believe it only modifies the boot image. If I'm correct, you should be able to restore with just flashing stock boot.
Also,
https://forum.xda-developers.com/an...iper4android-fx-2-6-0-0-t3774651/post80721099
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
Can you link the custom boot image?
https://forum.xda-developers.com/an...iper4android-fx-2-6-0-0-t3774651/post80054209
https://forum.xda-developers.com/an...iper4android-fx-2-6-0-0-t3774651/post80053180
This should be able to flash in EXKM or Franco kernel Manager. It zip uses anykernel which makes be believe it only modifies the boot image. If I'm correct, you should be able to restore with just flashing stock boot.
Also,
https://forum.xda-developers.com/an...iper4android-fx-2-6-0-0-t3774651/post80721099
Click to expand...
Click to collapse
This doesn't seem to work. Everything installs without a bootloop but the driver does not seem to detect the installation or the driver doesn't successfully install.
Sent from my OnePlus7TPro using XDA Labs
I guess its because of the Dolby Atmos which is built in. I tried to tweak the settings to match Viper, but no where close.
sathya said:
I guess its because of the Dolby Atmos which is built in. I tried to tweak the settings to match Viper, but no where close.
Click to expand...
Click to collapse
Can you try freezing Dolby and redo everything?
grandpajiver said:
Can you try freezing Dolby and redo everything?
Click to expand...
Click to collapse
I've tried that and it didn't work for me unfortunately. (Getting viper to work)
Sent from my OnePlus7TPro using XDA Labs
I tried to install viper4android as well, I should have researched this thing first.
Here is my story so far:
the module did not seem to do anything.
Installed the apk, which wanted to install drivers, I finally gave in and allowed it to install.
After a reboot the device rebooted to fastboot, hit start.
Device goes back to fasstboot (does not reach bootanimation, then restarts to fasstboot)
Clearing cache from Recovery did not help.
No TWRP, full SE Linux and no way to mount those secured filesystems
So I tried booting the unpatched boot image, this works, my phone is not dead yay.
-> flashed unpatched boot.img, phone able to boot again, but no root
Opened Magisk manager, repatched a stock boot image,
20.2 a6e62e07 (20102)
Tried booting:
-> patched with safe mode (not sure what this does), hangs at fasstboot mode screen, force turn off
-> patched without safe mode, restarts to fasstboot
I can boot the test-TWRP, but I could not find anything relevant to either extract or replace / disable.
I tried finding a way to flag something so that Magisk would not try to load the viper module
The only logs I could find were related to the TWRP boot, so I cant see what error might be causing this.
I flashed the OTA 10.0.4 again in the hopes it would unpatch whatever the viper install did.
Luckily I got to keep data, but now I fear there might be something lingering somewhere...
Anyone have any advice on what to try next?
Is a factory reset really the only way to get back Magisk?
Hey guys, here is a zip I modified for the OP7T and 7T Pro. Please report if viper from this file works. All credits to:
- ahrion
- zhuhang
- osm0sis
- Viper's Audio (Official blog)
- viper520
- Team_DeWitt
EDIT: This may work with a permissive selinux. Use this app before installing the magisk module. If it doesn't work, just boot the magisk core only image and then delete the magisk module.
https://forum.xda-developers.com/android/apps-games/app-selinux-switch-t3656502
f41lbl0g said:
Hey guys, here is a zip I modified for the OP7T and 7T Pro. Please report if viper from this file works. All credits to:
- ahrion
- zhuhang
- osm0sis
- Viper's Audio (Official blog)
- viper520
- Team_DeWitt
Click to expand...
Click to collapse
doesnt work its the same as the other one. hangs at fastboot. flashed stock boot image to boot back up.
Now am stuck without root unless I perform a factory reset and start the whole process again
v.konvict said:
doesnt work its the same as the other one. hangs at fastboot. flashed stock boot image to boot back up.
Now am stuck without root unless I perform a factory reset and start the whole process again
Click to expand...
Click to collapse
Try to boot (not Flash) the magisk core-only image from this post :
https://forum.xda-developers.com/newreply.php?do=newreply&p=80775151
Then uninstall the V4A module and reflash your magisk patched boot.
sasho36 said:
Try to boot (not Flash) the magisk core-only image from this post :
https://forum.xda-developers.com/newreply.php?do=newreply&p=80775151
Then uninstall the V4A module and reflash your magisk patched boot.
Click to expand...
Click to collapse
Thanks already did a clean install of everything. Am gonna stay away from anything viper for a while now. Until it is confirmed working
v.konvict said:
doesnt work its the same as the other one. hangs at fastboot. flashed stock boot image to boot back up.
Now am stuck without root unless I perform a factory reset and start the whole process again
Click to expand...
Click to collapse
I'm so sorry. I don't have a 7T yet so I was not able to test. According to a 7T pro thread it is because of post-fs-data that viper causes the phone to go to fastboot. So i removed the lines in there that lead to post-fs-data but it still crashes.
EDIT: Forgot to add that you may need to change your selinux to permissive before installing the module. Use this app.
https://forum.xda-developers.com/android/apps-games/app-selinux-switch-t3656502
f41lbl0g said:
I'm so sorry. I don't have a 7T yet so I was not able to test. According to a 7T pro thread it is because of post-fs-data that viper causes the phone to go to fastboot. So i removed the lines in there that lead to post-fs-data but it still crashes.
EDIT: Forgot to add that you may need to change your selinux to permissive before installing the module. Use this app.
https://forum.xda-developers.com/android/apps-games/app-selinux-switch-t3656502
Click to expand...
Click to collapse
It's not working because you are just modifying the installed module, not the actual installer, which we do not have the source code of.
If anyone is interested, follow this to create your custom recovery. Then you can remove the post-fs-data via adb from the recovery.
https://forum.xda-developers.com/7t...n-os-stock-recovery-adb-t3991865/post80866897
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
It's not working because you are just modifying the installed module, not the actual installer, which we do not have the source code of.
If anyone is interested, follow this to create your custom recovery. Then you can remove the post-fs-data via adb from the recovery.
https://forum.xda-developers.com/7t...n-os-stock-recovery-adb-t3991865/post80866897
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
I am pretty sure the installer is open source. It is called Unity. And I did modify the installer. Post-fs-data is magisk file that loads a script on boot. In the case of the OP7T, this script causes it to crash to fastboot. I'm pretty sure the only reason it didn't work for the other user was because their selinux was enforcing instead of permissive.
i've been trying for 2 whole days now to install viper4android on my oneplus 9 pro, i just can't get it to install. I'm basically stuck in an install loop and i've tried almost everything (permissive, AML, clean install, v4a repackaged, android 12 fix) but none of them work.
I wonder if anyone got viper working on their device running a custom android 12 rom
Take a look:
Viper4Android
Hi guys i used V4A on all of my 1+ devices. Started from the 1+1, 5, 7Pro and now i own the 9 Pro. The phone is rooted with a patched img, Magisk 24.3 installed, stock recovery. OOS Version is 11.12.10.10 Somehow i cant get V4A get to work...
forum.xda-developers.com
Hammerhand.17 said:
Take a look:
Viper4Android
Hi guys i used V4A on all of my 1+ devices. Started from the 1+1, 5, 7Pro and now i own the 9 Pro. The phone is rooted with a patched img, Magisk 24.3 installed, stock recovery. OOS Version is 11.12.10.10 Somehow i cant get V4A get to work...
forum.xda-developers.com
Click to expand...
Click to collapse
tried that too and just now tried it on just stock lineage os on A11 but still no luck nstalling v4a
This method worked for me in several custom ROMs in A12 and A12, bit just following the steps exactly and rebooting in every step (and you have to activate legacy mode).
Hammerhand.17 said:
This method worked for me in several custom ROMs in A12 and A12, bit just following the steps exactly and rebooting in every step (and you have to activate legacy mode).
Click to expand...
Click to collapse
i did follow every step with the reboots after each module but i'm still stuck in an install loop so i cant even get to the settings unfortunately... i've never had so much trouble with a device
Uninstall all the modules, try the procedure again with these files. I tried with other and got driver loop as you did, but it worked with these.
Hammerhand.17 said:
Uninstall all the modules, try the procedure again with these files. I tried with other and got driver loop as you did, but it worked with these.
Click to expand...
Click to collapse
Awesome, i'll try as soon as a custom rom is up and running
Hammerhand.17 said:
Uninstall all the modules, try the procedure again with these files. I tried with other and got driver loop as you did, but it worked with these.
Click to expand...
Click to collapse
So install magisk, reboot, AML, reboot, JamesDSP, reboot, V4A, install drivers and let it reboot? kernel can stay in enforcing?
After last reboot, you have to substitute the fs file as stated in the other thread, reboot again and set legacy mode.
I am in enforced kernel, yes.
Hammerhand.17 said:
After last reboot, you have to substitute the fs file as stated in the other thread, reboot again and set legacy mode.
I am in enforced kernel, yes.
Click to expand...
Click to collapse
Got it working finally!! Could you supply me with the modification i need to make in the post fs file? So i follow you exactly? Also can i remive jamesdsp now or does it need to stay installed?
You have to replace this file in /data/adb/modules/Viper4AndroidFX and reboot. About JamesDSP I don't really use it so I disabled the app, although I have to do it in every reboot
Hammerhand.17 said:
You have to replace this file in /data/adb/modules/Viper4AndroidFX and reboot. About JamesDSP I don't really use it so I disabled the app, although I have to do it in every reboot
Click to expand...
Click to collapse
But can i remive jamesdsp from magisk or does it need to be installed in order to keep viper working? Like the moment you remove it viper just stops working?
Don't know, never tried. If you try, tell me, but I didn't want to do more tests.
Hammerhand.17 said:
Don't know, never tried. If you try, tell me, but I didn't want to do more tests.
Click to expand...
Click to collapse
If you uninstall it viper is once again stuck in an install loop so you do need jamesdsp to stay installed
Ok. Good to know. Will left it installed, then.