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
Related
is there anyone who can help me fix my safetynet ? im on magisk 14 and ive tried everything ive read in the forums from flashing fixes to trying terminal commands. im sure someone knows how to fix this. plez halp. ty
1. Flash the fix file from twrp
2. boot device
3. open Magisk and click "tap to start safety check" ONCE
ctsProfile=false
basicintegrity=false
4. Reboot device
5. check again and see
ctsProfile=true
basicintegrity=true
punkhawaiian said:
1. Flash the fix file from twrp
2. boot device
3. open Magisk and click "tap to start safety check" ONCE
ctsProfile=false
basicintegrity=false
4. Reboot device
5. check again and see
ctsProfile=true
basicintegrity=true
Click to expand...
Click to collapse
i did and now my phone wont boot. :crying:
Sorry to here worked perfectly for me. Try a fresh install of the rom and data files and fix.
punkhawaiian said:
Sorry to here worked perfectly for me. Try a fresh install of the rom and data files and fix.
Click to expand...
Click to collapse
cant, i just made a post about whats happening and why i cant.
Hi all!
I'm new here and have just recently rooted my Google Pixel 2 with Magisk and a custom kernel " Flash ". I have tried many guides and tutorials on how to install viper audio's drivers but after rebooting nothing works and asks me to install the drivers again once I open the app. I do also have the latest APK installed on my phone if that helps.
Is there any proper tutorials on where I can rectify the problem? As I think the Pixel 2's audio is a bit quiet and want to enjoy my Bose Wireless Earphones with my phone and have custom equalizer controls like I have with my iPhone 6s that's jailbroken.
I would also like some more info on how to flash zips to my phone as I think I may have done it wrong. Booting to TWRP than sideloading the zip.
Cheers,
xD3CrypTionz
I guess you have to install it via magisk
DumbleCore said:
I guess you have to install it via magisk
Click to expand...
Click to collapse
I tried that but it still comes up with the same error
Did you read the Viper4Android thread? Flash kernel has issues with V4A.
Switch to Snoke kernel and see if that fixes it.
Sent from my Pixel 2 using Tapatalk
Diesel_Jeremiah said:
Did you read the Viper4Android thread? Flash kernel has issues with V4A.
Switch to Snoke kernel and see if that fixes it.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Can you link me to the Viper4Android thread where it says this as there is alot of pages to sift through?
Also how do you re flash a kernel? do you have to flash the stock and then a custom? Or can you just flash a custom one over an already custom kernel?
xD3CrypTionz said:
Can you link me to the Viper4Android thread where it says this as there is alot of pages to sift through?
Also how do you re flash a kernel? do you have to flash the stock and then a custom? Or can you just flash a custom one over an already custom kernel?
Click to expand...
Click to collapse
Flash stock boot & dtbo.
In TWRP: flash Snoke kernel zip (R1 is for 8.1 and at the top of the download page)
If issues, uninstall and reinstall Viper4Android 2.5.0.4 through Magisk
Sent from my Pixel 2 using Tapatalk
I have ElementalX kernel and I just downloaded the Ahrion ViPER4Android FX and flashed through Magisk. Works like a charm.
xD3CrypTionz said:
Hi all!
I'm new here and have just recently rooted my Google Pixel 2 with Magisk and a custom kernel " Flash ". I have tried many guides and tutorials on how to install viper audio's drivers but after rebooting nothing works and asks me to install the drivers again once I open the app. I do also have the latest APK installed on my phone if that helps.
Is there any proper tutorials on where I can rectify the problem? As I think the Pixel 2's audio is a bit quiet and want to enjoy my Bose Wireless Earphones with my phone and have custom equalizer controls like I have with my iPhone 6s that's jailbroken.
I would also like some more info on how to flash zips to my phone as I think I may have done it wrong. Booting to TWRP than sideloading the zip.
Cheers,
xD3CrypTionz
Click to expand...
Click to collapse
I ran the 2.3.4.0 apk and it works great. It is in this zip. http://www.mediafire.com/file/cnqqdme51qy9ft4/ViPER4Android_FX_v2340.zip http://www.mediafire.com/file/cnqqdme51qy9ft4/ViPER4Android_FX_v2340.zip
kitanderson said:
I ran the 2.3.4.0 apk and it works great. It is in this zip. http://www.mediafire.com/file/cnqqdme51qy9ft4/ViPER4Android_FX_v2340.zip http://www.mediafire.com/file/cnqqdme51qy9ft4/ViPER4Android_FX_v2340.zip
Click to expand...
Click to collapse
Does this work on the " Flash " kernel?
Installed the APK and it now comes up with an error saying " Driver install failed: The busybox instalation found on your device does not work".
I currently have the latest busybox installed via play store
kitanderson said:
I ran the 2.3.4.0 apk and it works great. It is in this zip. http://www.mediafire.com/file/cnqqdme51qy9ft4/ViPER4Android_FX_v2340.zip http://www.mediafire.com/file/cnqqdme51qy9ft4/ViPER4Android_FX_v2340.zip
Click to expand...
Click to collapse
Works for Oreo???
elmor0 said:
Works for Oreo???
Click to expand...
Click to collapse
Yes it works for oreo. I'm rooted with Magisk on Flash kernel and this is what i did and am running on 8.1:
-Go in to Magisk and download the ViPER4Android FX v2.9 by ahrion, zackptg5
-Install it and when it prompts you, select new driver (vol up) and material version (volume up)
-Let Magisk install everything and simply reboot your phone
Running V4A with bluetooth, aux, etc working perfectly
djer34 said:
Yes it works for oreo. I'm rooted with Magisk on Flash kernel and this is what i did and am running on 8.1:
-Go in to Magisk and download the ViPER4Android FX v2.9 by ahrion, zackptg5
-Install it and when it prompts you, select new driver (vol up) and material version (volume up)
-Let Magisk install everything and simply reboot your phone
Running V4A with bluetooth, aux, etc working perfectly
Click to expand...
Click to collapse
Tried this way but for me (custom ROM on Oreo 8.0) it did not work.
However, neyesor's method & files have done the trick:good:
elmor0 said:
Tried this way but for me (custom ROM on Oreo 8.0) it did not work.
However, neyesor's method & files have done the trick:good:
Click to expand...
Click to collapse
Will you link to the post you used to get this to work?
If I don't wanna flash any kernel and keep the original kernel will this still work ?
djer34 said:
Yes it works for oreo. I'm rooted with Magisk on Flash kernel and this is what i did and am running on 8.1:
-Go in to Magisk and download the ViPER4Android FX v2.9 by ahrion, zackptg5
-Install it and when it prompts you, select new driver (vol up) and material version (volume up)
-Let Magisk install everything and simply reboot your phone
Running V4A with bluetooth, aux, etc working perfectly
Click to expand...
Click to collapse
can confirm this worked for me too. im on elementalx 1.02.
djer34 said:
Yes it works for oreo. I'm rooted with Magisk on Flash kernel and this is what i did and am running on 8.1:
-Go in to Magisk and download the ViPER4Android FX v2.9 by ahrion, zackptg5
-Install it and when it prompts you, select new driver (vol up) and material version (volume up)
-Let Magisk install everything and simply reboot your phone
Running V4A with bluetooth, aux, etc working perfectly
Click to expand...
Click to collapse
does v4a require xposed to be installed? i'd like to use this but since xposed doesn't pass safetynet i'm cautious as to what modules i'm using in magisk
daddy's.fist said:
does v4a require xposed to be installed? i'd like to use this but since xposed doesn't pass safetynet i'm cautious as to what modules i'm using in magisk
Click to expand...
Click to collapse
I installed this without xposed. using this method.
infamousvincci said:
can confirm this worked for me too. im on elementalx 1.02.
Click to expand...
Click to collapse
Didn't work for me I'm on the EX kernel
dviree said:
Didn't work for me I'm on the EX kernel
Click to expand...
Click to collapse
Thats weird. Im on 1.02. you?
daddy's.fist said:
does v4a require xposed to be installed? i'd like to use this but since xposed doesn't pass safetynet i'm cautious as to what modules i'm using in magisk
Click to expand...
Click to collapse
No, V4A does not require Xposed to be installed as it can be downloaded as a Magisk module which is patched to pass safteynet. I love Xposed and modules are just now starting to pop up for Oreo.... but i use android pay way too much to not have safteynet pass. So just download from Magisk
I've managed to solve all problem by rooting and installing magisk
1. Some apps may not work properly
I have tried every app I used in oreo and each app works fine (I know this is not a solution )
2. Google pay not works
Solution-Google pay works by using a magisk module called
*tezhider4magisk*
https://androidfilehost.com/?fid=5862345805528042557
3. Google play shows device not certified
Solution - Google play shows device is certified using magisk module called
*ClearPlayStoreWithServiesData4Magisk*
https://androidfilehost.com/?fid=890278863836289937
4. Safety net not passed in magisk on open beta 1/2/3
Solution - for safety net to pass in magisk we need to edit a line in build.prop (have to some file explore like es file explorer or root explorer to edit build.prop)
Replace
ro.build.fingerprint=OnePlus/OnePlus6/OnePlus6:9/PKQ1.180716.001/1808301430:user/release-keys
Click to expand...
Click to collapse
With
ro.build.fingerprint=OnePlus/OnePlus6/OnePlus6:8.1.0/OPM1.171019.011/06140300:user/release-keys
Click to expand...
Click to collapse
5. For rooting oxgyen os open beta 1/2/3
Follow guide from developer [Manikandanguru] (all thanks to him?)
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
Is there a fix yet for aod/ambient display yet?
Gmos24 said:
Is there a fix yet for aod/ambient display yet?
Click to expand...
Click to collapse
Try this maybe? It worked for me on OOS Oreo at least. Didn't try it on P yet but should work I think...
https://www.google.co.in/amp/s/www....always-on-display-oneplus-6-oneplus-5-5t/amp/
For me my nfc is not working for some reason, the option in settings is greyed out and it's causing so many wakelocks that it's also killing my battery.
sahu.prashant said:
Try this maybe? It worked for me on OOS Oreo at least. Didn't try it on P yet but should work I think...
https://www.google.co.in/amp/s/www....always-on-display-oneplus-6-oneplus-5-5t/amp/
Click to expand...
Click to collapse
Doesn't work, crashes display settings.
sahu.prashant said:
Try this maybe? It worked for me on OOS Oreo at least. Didn't try it on P yet but should work I think...
https://www.google.co.in/amp/s/www....always-on-display-oneplus-6-oneplus-5-5t/amp/
Click to expand...
Click to collapse
Edited message to fix the quote to the correct person.
I had to uninstall it on oos ob1 because it was making the display settings crash. I just reinstalled it on hydrogen os beta 4 and it works again however the status bar doesn't turn black. Any idea on how this could be fixed or if it's an easy fix?
Gmos24 said:
Is there a fix yet for aod/ambient display yet?
Click to expand...
Click to collapse
For me aod/ambient display works perfectly
Have you dirty flashed new beta
Try doing a factory reset I hope that will fix it
BossNexusS said:
For me my nfc is not working for some reason, the option in settings is greyed out and it's causing so many wakelocks that it's also killing my battery.
Click to expand...
Click to collapse
Try clearing cache from recovery that solves a lot of issues
Gmos24 said:
Edited message to fix the quote to the correct person.
I had to uninstall it on oos ob1 because it was making the display settings crash. I just reinstalled it on hydrogen os beta 4 and it works again however the status bar doesn't turn black. Any idea on how this could be fixed or if it's an easy fix?
Click to expand...
Click to collapse
Woah! Sorry about that, I guess I should have tested it first on P. I'll flash OOS Open Beta 2 today and then try this mod. Will update if it works.
And status bar issue is a strange one, no idea about that!
Can we get incremental ota update even when unlocked and magisk installed (no twrp)?
I cant boot once I flash Magisk 17.1
Every time I flash magisk, I get in boot loop. I have used official and Blue TWRP both to flash magisk every time I am in boot loop.
I have to reflash everything to get booting. How to root OB 2 now
droid-devz,
Flash Oos ob02, then twrp blu spark.
Reboot to twrp to check if it's working. Flash Magisk 17.1.
Reboot to system.
Veestaai said:
Can we get incremental ota update even when unlocked and magisk installed (no twrp)?
Click to expand...
Click to collapse
Yess i just updated from beta 1 to beta 2 no problem
You'll just lose root everytime you update and have to install just magisk again
Don't install custom recovery that causes problems I guess use the above method (in the thread)
droid-devz said:
I cant boot once I flash Magisk 17.1
Every time I flash magisk, I get in boot loop. I have used official and Blue TWRP both to flash magisk every time I am in boot loop.
I have to reflash everything to get booting. How to root OB 2 now
Click to expand...
Click to collapse
Official twrp doesn't work only blue star twrp works
Veestaai said:
Can we get incremental ota update even when unlocked and magisk installed (no twrp)?
Click to expand...
Click to collapse
Probably not..magisk root rewrites the boot image..safest bet would be to use update manager to flash whole rom updates, then reinstall magisk.
CAUTION:
With the latest update of the BETA 2, once you give the command in fastboot "fastboot boot twrp.img" the phone goes into softbrick with a Qualcomm screen. Has anyone found an alternative method?
JRevenge said:
CAUTION:
With the latest update of the BETA 2, once you give the command in fastboot "fastboot boot twrp.img" the phone goes into softbrick with a Qualcomm screen. Has anyone found an alternative method?
Click to expand...
Click to collapse
does not happen with me !!!
Sadly the build.prop fix for SafetyNet only worked on Open Beta 1.
Anyone got SafetyNet passing on Open Beta 2?
digidude512 said:
Sadly the build.prop fix for SafetyNet only worked on Open Beta 1.
Anyone got SafetyNet passing on Open Beta 2?
Click to expand...
Click to collapse
safety net passes with current canary build of magisk
plug this into the custom section in the magisk settings under update channel: https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/canary.json
sorry, hit send before it finished uploading
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
That's why I bought this mobile with stock Android to be sure I'm not install something on it and the truth it's not worth to change something on it.
This mobile work pretty good without needing to root it.
No offense only my opinion.
Thanks
Mi A2 Lite using Tapatalk
wenna.speedy said:
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
Click to expand...
Click to collapse
Same happened to me on Android Pie, it completely broke my phone and when restarting it I had bootloop as well.
Had to flash ROM from scratch.
Maj3sty said:
That's why I bought this mobile with stock Android to be sure I'm not install something on it and the truth it's not worth to change something on it.
This mobile work pretty good without needing to root it.
No offense only my opinion.
Thanks
Mi A2 Lite using Tapatalk
Click to expand...
Click to collapse
I dont think so. you havent right, because of magisk. Did you ever try viper4android? Its really some kind of magic! this is only one case. no root = no lot of great stuff. If anything bad happened, you have ever last option = flash vanilla rom
For anyone who gets bootloops caused by a magisk module: Just flash back stock kernel! Then Magisk is gone and the module doesn´t work too. You can delete the module from your magisk manager and root again - voilla!
Voodoojonny said:
For anyone who gets bootloops caused by a magisk module: Just flash back stock kernel! Then Magisk is gone and the module doesn´t work too. You can delete the module from your magisk manager and root again - voilla!
Click to expand...
Click to collapse
I tried it and doesnt work. It seems the module changed any files in system(via root).
wenna.speedy said:
I dont think so. you havent right, because of magisk. Did you ever try viper4android? Its really some kind of magic! this is only one case. no root = no lot of great stuff. If anything bad happened, you have ever last option = flash vanilla rom
Click to expand...
Click to collapse
Nice try, but looks like you are not the only person with the same issue! I'm using Jetaudio and I have great sound with my JBL (Bluetooth) & Sennheiser wired headsets. I'm pass!!!
Mi A2 Lite using Tapatalk
lbsilva said:
Same happened to me on Android Pie, it completely broke my phone and when restarting it I had bootloop as well.
Had to flash ROM from scratch.
Click to expand...
Click to collapse
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
hckrm said:
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
Click to expand...
Click to collapse
Did you place system.img into your fastboot folder? It sounds like fastboot can´t find the file you want to flash!
Voodoojonny said:
Did you place system.img into your fastboot folder? It sounds like fastboot can´t find the file you want to flash!
Click to expand...
Click to collapse
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
hckrm said:
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
Click to expand...
Click to collapse
You can try install twrp and mount internal storage. I dont know if exists new version with working mounting.
hckrm said:
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
Click to expand...
Click to collapse
Did you try using MiFlashTool?
hckrm said:
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
Click to expand...
Click to collapse
Hmm, as told above, then your only option is a backup with twrp. If you can't decrypt data with twrp (after you installed it - not booting) you can try to boot to slot b - that sometimes help. Just select under reboot in twrp or type "fastboot set_active b"...
wenna.speedy said:
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
Click to expand...
Click to collapse
There is no wipe required, I just got caught in the loop as well.
Two things you need:
-TRWP installed
-Uninmod installed (magisk module remover)
1. If you are stuck in the loop, boot into fastboot,
- connect your pc and run ADB & fastboot cmd, run the command fastboot boot recovery.img(or your TRWP image) and run TRWP
2. Download Uninmod zip, transfer to phone. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242&nocache=1
- Use TWRP to install Uninmod,
- remove the Notchkiller mod
- credits to veez21
3. find this file overlays.list and delete it from /data/resource-cache/overlays.list https://github.com/Magisk-Modules-Repo/NotchBarKiller/issues/3
- credits to MatChung
Reboot and there was like a minute of delay on same boot screen, but then it should boot fine.
If you are not stuck in the loop but just installed the module:
-remove the module in magisk
-find the file and delete it.
TLDR: remove the Notchbarkiller mod and remove overlays.list file. Reboot!
Hope it works. It did for me. Poco F1
I flashed this madule last night and found that it break calls. Could not make and receive phone calls. Huawei P20 Pro with EMUI 8.1 running.
Guys don't flash that LITERALLY SHIET module. It's bricking phones, i dirty flashed my rom and still couldn't recover it! I used Poco btw
D1stRU3T0R said:
Guys don't flash that LITERALLY SHIET module. It's bricking phones, i dirty flashed my rom and still couldn't recover it! I used Poco btw
Click to expand...
Click to collapse
Written in the first post...
wenna.speedy said:
Written in the first post...
Click to expand...
Click to collapse
I know...
Strange, I was using the January update when I first installed it and everything worked fine, no issues what so ever. I haven't tried it on the latest update but xiaomi's update might have messed the module. There's no reason what so ever to blame the module for not working on the latest update as they tend to break things. Just report back to the developer with something helpful like a logcat instead of making useless threads.
As of the bootloop there's no reason to wipe your data or reflash the ROM unless you have to. Just boot up in twrp and flash the magisk uninstaller which might be in the Magisk Manager folder or just search it online. Another way to do it is just to mount magisk in twrp and delete the module. Learn about how to mount magisk here: https://forum.xda-developers.com/apps/magisk/magisk-mount-resize-img-t3675853
SnoopDoggyStyleDogg said:
Strange, I was using the January update when I first installed it and everything worked fine, no issues what so ever. I haven't tried it on the latest update but xiaomi's update might have messed the module. There's no reason what so ever to blame the module for not working on the latest update as they tend to break things. Just report back to the developer with something helpful like a logcat instead of making useless threads.
As of the bootloop there's no reason to wipe your data or reflash the ROM unless you have to. Just boot up in twrp and flash the magisk uninstaller which might be in the Magisk Manager folder or just search it online. Another way to do it is just to mount magisk in twrp and delete the module. Learn about how to mount magisk here: https://forum.xda-developers.com/apps/magisk/magisk-mount-resize-img-t3675853
Click to expand...
Click to collapse
UPDATE: This thread is a false alarm as I managed to install the module on the March update and the only crash I get is from google play services with no bootloop and everything working. Maybe the OP has another phone and except that a module that is on the Mi A2 Lite thread should work on any phone or he's done something wrong. I will attach some screenshots to confirm that the module is indeed working and OP's post is a false alarm for stock A2 Lite ROMs (No custom ROM and not other phones)
NOTE: As you can see in the YouTube screenshot there's no black back on the left side of the screen as it should be without the module installed
Oneplus 6 Oxygen OS 10.3.0 With Root,TWRP,Viper4Android FX,Xposed & Youtube Vanced.
Anybody can pick whichever state they are in and start from there.
Step 1. Use the latest MSM tool to install the corresponding OS version on to the chipset.
Step 2. Upgrade till you reach Android Version 10.0.
Step 3. Enable Developer options from there enable boot loader Unlocking and advanced power menu and usb debugging.
Step 4. Unlock Bootloader and let it wipe it all and reboot.
Step 5. Then boot into the Stock Bootloader.
Step 6. Flash the Android 10 Patched recoveries .img using fastboot commands.
Step 7. Then Boot into TWRP recovery menu from there flash the Android 10.0 os.
Step 8. Then Flash the zip file of the android 10 recovery & reboot to the recovery.
Step 9. Then from the twrp menu flash magisk and wipe cache and dalvik and reboot to system.
Step 10. Then setup the phone on reboot.
Rooted Device with twrp
Step 11. Then upgrade to 10.3.0 version of android. But do not reboot.
Step 12. Instead go to magisk and flash TWRP A/B retention script.
Step 13. Then go to the magisk and install it into an inactive slot.
Step 14. Reboot the device to find it to be in the Android 10.3.0 with root and twrp .
New Method : Less time Consuming.
Step 1: Use the latest MSM tool to install the corresponding OS version on to the chipset. Decrypted 10.3.0
Step 2: Login to the device set it up and enable the dev ops .
Step 3: Allow Unlocking Bootloader.
Step 4: Reboot to the fastboot and unlock the bootloader.
Step 5: Then reboot again into the fastboot mode and Flash the Android 10 Patched recoveries .img using fastboot commands.
Step 6: Then go into recovery and flash with the captured ota Zip of Android 10.3.0.
Step 7: DO NOT REBOOT , Then Flash the zip file of the android 10 recovery & reboot to the recovery.
Step 8: Then Flash the magisk installer and boot into the system.
Updated Rooted device with twrp.
Step 15. Then Disable the auto updates for the youtube in the play store .
Step 16. Flash Youtube Vanced from the Magisk.
Step 17. Install Viper4android App and open it but dont install the drivers.
Step 18. Then Go to the magisk and flash audio modification library but do not reboot.
Step 19. Then go back to the Viper4Android and install the drivers Hence rebooting the device.
Step 20. After the reboot Disable the audio modification library from the magisk .
Step 21. Go to the Viper4Android and install the drivers again rebooting the device and successfully installing the Viper4Android .
Step 22. Install EDXposed Apk then go the magisk and flash both RIRU Core and Yahfa Framework 4.5.5 beta or the Sandhook Framwork and reboot.
I have sourced these links from various posts so thanks to all the original providers.
Links to files:
https://androidfilehost.com/?fid=4349826312261684578 Decrypted 10.3.0 OOS
https://androidfilehost.com/?fid=4349826312261679648 OOS 10.3.0 OTA File.
https://androidfilehost.com/?fid=6006931924117936338 Decrypted 9.08 OOS
https://github.com/topjohnwu/Magisk/releases Magisk 20.1
https://androidfilehost.com/?fid=4349826312261678087 TWRP zip for oxygen OS 10.0 and up
https://androidfilehost.com/?fid=4349826312261678088 Twrp image for oxygen os 10.0 and up
https://www.mediafire.com/folder/773e97cz2ezx1/AddFree_Youtube_BackgroundPlay_Enabled youtube vanced.
Thanks a lot
sp0979 said:
Thanks a lot
Click to expand...
Click to collapse
Sure Dude.
Hey thanks for the instructions !
I didn't have to install the audio library mod to make Viper to work ! What does it do ?
Do you experience a huge battery drain with Viper ?
I mean, even when nothing is playing, i can't deactivate the speaker modifications and it seems to pump a huge amount of battery (OOS 10.3.0) !
Thanks in advance !
Is there anyway to log into your YouTube account using this apk? When I try I get a popup message "There was a problem signing in, please tap to retry."
fonebone2 said:
Is there anyway to log into your YouTube account using this apk? When I try I get a popup message "There was a problem signing in, please tap to retry."
Click to expand...
Click to collapse
Usually it fixes itself after a few tries . Otherwise forcestop the application then give it permission to the contacts and then sign in.
jnkyrd9 said:
Hey thanks for the instructions !
I didn't have to install the audio library mod to make Viper to work ! What does it do ?
Do you experience a huge battery drain with Viper ?
I mean, even when nothing is playing, i can't deactivate the speaker modifications and it seems to pump a huge amount of battery (OOS 10.3.0) !
Thanks in advance !
Click to expand...
Click to collapse
Yes it consumes a bit of battery i get a SOT of 4 to 4:30 hours at max and that to on a good day. But I dont regret it becuz of the dash charging .
Just Forcestop the application and dont open it the system reverts to its original sound.
what audio modification library does is it helps the system to make changes in the audio library to enable the installation of neon drivers of the viper. One time i didnt get it done properly and my neon enable status remained No. which meant that the drivers didnt install properly. From thence i have been following this method to the T.
Follow the guide just for get viper working and it is! Thank you very very much, finally
Shaky93 said:
Usually it fixes itself after a few tries . Otherwise forcestop the application then give it permission to the contacts and then sign in.
Click to expand...
Click to collapse
Thank you! I also had to clear storage/cache, but after doing so it logged into my account automatically when I restarted the app.
Is someone experiencing no audio in whatsapp voice Message during registration?
Deltalfa said:
Is someone experiencing no audio in whatsapp voice Message during registration?
Click to expand...
Click to collapse
I don't think this is thread related
Experiencing only since using this version. Tried another kernel too but same thing. Also its only whatsapp releated
Deltalfa said:
Experiencing only since using this version. Tried another kernel too but same thing. Also its only whatsapp releated
Click to expand...
Click to collapse
Sorry, can you be more precise? "This version" of what?
deleted
I'm on a Oneplus 7 Pro with 10.3.0 and cannot get EdXposed to work. The EdXposed manager opens but as soon as I click on Modules or Download the app closes. And there's no superuser permission for it on Magisk.
I have tried to read all of this thread carefully but still dont understand how To install TWRP and root my Oneplus 6.
I'm on OFFICIAL 10.3.0
from which state I have to start to install new twrp.
Boot loader is Unlocked yet
Sent from my OnePlus6 using XDA Labs
iruleSHtar_1922 said:
I have tried to read all of this thread carefully but still dont understand how To install TWRP and root my Oneplus 6.
I'm on OFFICIAL 10.3.0
from which state I have to start to install new twrp.
Boot loader is Unlocked yet
Sent from my OnePlus6 using XDA Labs
Click to expand...
Click to collapse
x2, please help
iruleSHtar_1922 said:
I have tried to read all of this thread carefully but still dont understand how To install TWRP and root my Oneplus 6.
I'm on OFFICIAL 10.3.0
from which state I have to start to install new twrp.
Boot loader is Unlocked yet
Sent from my OnePlus6 using XDA Labs
Click to expand...
Click to collapse
"new method" worked just fine for me, since I already have my boot loader unlocked, I just
start Fastboot mode,
flash the Recovery.img,
flash OSS 10.3
flash recovery.installer
reboot recovery
flash magisk 20.2
and done :3
Ryan-sv said:
"new method" worked just fine for me, since I already have my boot loader unlocked, I just
start Fastboot mode,
flash the Recovery.img,
flash OSS 10.3
flash recovery.installer
reboot recovery
flash magisk 20.2
and done :3
Click to expand...
Click to collapse
Will it wipe out all of our data?
#sorryfor badenglish
iruleSHtar_1922 said:
Will it wipe out all of our data?
#sorryfor badenglish
Click to expand...
Click to collapse
Since the user you are asking flashed 10.3, but you are already on 10.3, perhaps you are in the same situation I faced. I was in this thread looking for a solution after loosing root by taking the OTA update and rebooting which left me with an unrooted phone on the official 10.3. If you are in that situation, the thread that saved me is
https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213
I used the newer files in the above thread to root again with the same method I followed the last time from
https://www.youtube.com/watch?reload=9&v=dL2XwYDDW2s
It's not entirely clear from your wording whether your bootloader is unlocked. If not, my bootloader was unlocked a while back, using the instructions from
https://www.youtube.com/watch?v=_8u-KwXsKIw
I was worried I would have a problem, since many people in the thread had hiccups, but it went smoothly. I did have a problem flashing the enchilada file, but it must have been corrupted or incomplete. I downloaded it again, and it worked. I lost nothing in the process, but I did back up all my date to be safe, as I suggest you should.