Any way to use viper4android on Android 10 roms. - Asus Zenfone Max Pro M2 Questions & Answers

Anybody found a way to install viper4android and use it without being stuck in the bootloop?

Root using magisk canary build 19.5
Flash audio modification library
Flash v4afx-rootless
Install latest v4afx apk 2.7.1.0
Install driver and reboot
Phone will be stuck on boot logo
Boot into recovery mode
Last step(without this phone will be stuck on boot logo)-
Disable v4afx module from recovery mode and reboot(I use magisk_manager_for_recovery_mode for this)
Now you have functional v4afx on your phone.
If not processing at first, go to settings and toggle Attach audio effects.
Currently using on SuperiorOs and have tried it on Arrow and Pixel experience .

Related

lg g2 cm stuck on logo after installing supersu twrp

im using cm13 on g2. works very well.
But when install #supersu via twrp. its get stuck on the cm logo. can't even enter in recovery mode. Pls I badly Need help.
Make sure you're using SuperSu Beta (2.65+) link. CM13 has a built in root manager (developer options) though, installing supersu is not required. Have you tried accessing recovery using the hardware keys? here's how to

p10 lite set linux permissive fails for viper4android, help needed

stock ROM, installed viper4android both ways:
standard apk for nougat from viper homepage
zip guitarhero modified through twrp
both ends in driver install loop at every startup
google says linux should be set to permissive (due to writing rights?) and then modify an audio effects file in vendor...dev...tree with root explorer
even after trying to change linux to permissive with selinux chnager app, the discontinued one, i never get that entry audio effects in vendor dev etc somewhat
so whenever i reboot the phone, restart viper4android it wants to install the driver, says success, re same thing.
never had these problems on custom but on stock ROM, how to solve the issue please on p10 lite?
thanks ;D
Did you find a fix?

Bluetooth not working after Magisk installation

Hey everyone,
I have a bit of a problem.
I used the root method that doesn't disable stock OTAs, but noticed that whenever I'm using a Magisk patched boot image (hence I have root access), my Bluetooth doesn't turn on, and sends me 'Bluetooth keeps stopping' error messages.
Tried on 8.0, 8.1, 9.0, the problem persists.
Stock ROM + kernel, no TWRP
What could be the solution?
Please help, I want root access but I'd prefer staying on stock.
Thanks in advance.
Check if you using proper boot image to create patched_boot. If you use older version, wifi and bluetooth may not work.
Try flash stock boot, than fastboot boot patched_boot, than install magisk with magisk manager (full install), than reboot. Not flash patched_boot with fastboot, just boot phone with it.

Help from Rooting to Xposed, rookie explanation

Hi guys. I had a multiple day struggle and all the manuals were only partial, so I try to summarize all the steps taken to unlock my phone, root it with magisk and install Xposed SDK28.
1) Unlock bootloader
It takes time and I had to wait that mentioned 168h (it may differ) and there is nothing you can do about it on your K20/9T
I used the official xiaomi unlock tool, latest version, and followed all the steps there.
2) Install TWRP
Oh god, on this phone it gave me headache and I almost bricked my phone and it convinced me to write you a manual just in case you are lost as I had been. Here you go.
There are three versions of TWRP on this forum and I selected the Chinese one (no greek nor russian)
After unlocking the bootloader, I only flashed the twrp (no other files, just the img with the rom) and then did fastboot reboot.
It stucked on booting. Here I pressed volume up and power and it took me to the newly installed TWRP. This didn't work with an other TWRP than Chinese. I ended up in the bootloop to fastboot only.
Then I installed the ROM. In my case Pixel Experience, latest version. The manual mentioned in this forum tells you to install Magisk together with your ROM. It again caused a bootloop on my device, so I wiped my device in TWRP, installed clean Pixel Experience ROM, and let it boot without magisk and permissive.
I checked via root checker if my device is rooted. And it was not.
3) Root via Magisk/SU applicable
Then I downloaded
Magisk Manager 7.3.2.apk and installed it with confirmation in settings that I allow the whatever file manager to install apps from unknown source.
In the Magisk Manager I downloaded a zip with Magisk and rebooted to TWRP (turn off the device, and then volume up and power)
I flashed the zip downloaded by that manager - no wipe
rebooted back to system and checked the root. Rooted.
4) Xposed
Download Magisk manager 7.3.2.
Install modules via Magisk Manager
- Riru Core v19.4 or higher
- Riru - EdXposed v0.4.5.1._beta(4463) (YAHFA)
restart your device
Then install EdXposedInstaller_V2.2.4-release.apk and check if it works.
restart your device and you can start installing modules. Even Gravitybox (P) works!
I really hope I briefly helped you guys. Viva la modding and enjoy your cool Xiaomi. Thanks to all the contributors on xda, thanks to them I was able to summarize this little manual.
In case you stuck somewhere and need to recover anything such as boot.img or any other shananingans you did with your phone, as I did too, you need to download the miflash tool, in this case the latest version didn't work so I used 2014.05.09.0, and downloaded the official fastboot rom davinci_eea_global_images_V10.3.7.0.PFJEUXM_20190602.0000.00_9.0_eea_eab1d1cc52, flashed it with miflash (around 6 minutes), stucked again in bootloop, rebooted to TWRP via volume up and power during the bootloop, and followed the steps from flashing the TWRP (after MiFlash it has only the default MiRecovery) and installed my ROM.

[S10+ F/DS] Magisk won't show as installed.

Hello! Hoping to get some help here. I installed Magisk using John Wu's guide (https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root) and the boot animations show that the firmware is modified, but Magisk doesn't show up as installed after I boot (even with the recovery key combo). Is there any way to fix it besides flashing the modified rom all over again?

Categories

Resources