Unable to use viper4android in miui 8 and 9 - Xiaomi Redmi 4X Questions & Answers

I've tried using viper4android on miui8.It asks me for installation of v4a driver ,given su rights( magisk ) and rebooted ,still the driver status says abnormal and neon disabled. I've tried it using on resurrection remix, it worked like a charm. And now i flashed miui9 and now i once again not able to use viper4android .The same thing happened once again.(i downloaded the v4android directly from the website(zip file including nougat fix)......
thank u...

There you go, I have got another user like me facing the same issue. I am also unable to use Viper4android on my redmi 4 running MIUI 9.
By any chance, did you get to find a solution for this?

flash the latest viper4android zip from twrp. it worked for me in lates MIUI 9.7.15 global.

Related

Magisk bootloop. Messed up my phone

Hello guys.
I have a Zenfone 2 Z00A running latest LOs14.1 Nightly
Yesterday I installed three modules for Magisk. Night light and Android WhatsApp emoji.
Night light is useless so I uninstalled after trying it. So far so good.
I activated the WhatsApp emojis and rebooted the phone but the phone never booted again, it entered bootloop...
First thing I did was uninstalling Magisk through TWRP. It also bootlooped. So I installed magisk and the Magisk Module manager and
tried deactivating the module viaTWRP but it still bootloops.
I extracted the boot.img out of the latest lineage ROM and flashed it but it also didn't work. Dirty flashing the latest build of lineage doesn't work... I think it is because it runs a Magisk script at the end of flashing. I don't want this script to run
What I did was run the uninstall .zip and dirty flash the ROM again. But now I can't dirty flash because of TWRP Error 7
I'm going crazy, nothing works... It just bootloops.
Please help

Anyone had success with xposed on mi 8?

Has anyone got Xposed working yet? I've tried a few different methods of install. via magisk or a direct install through twrp but i end up in a bootloop
Worked fine with EU rom
ermacwins said:
Worked fine with EU rom
Click to expand...
Click to collapse
did you install via magisk? I get stuck in a bootloop and it loads into twrp after it tried to boot into android for 5 minutes. I'm on xiaomi.eu weekly atm
WakeUpFilthy said:
did you install via magisk? I get stuck in a bootloop and it loads into twrp after it tried to boot into android for 5 minutes. I'm on xiaomi.eu weekly atm
Click to expand...
Click to collapse
Oops sorry my mistake, I only flashed magisk not xposed.
i need xposed too
Are they the news? I have a global rom but I could not install xposed for magisk
Its not working yet on miui. Now the kernel is out maybe it will be made. I have xposed working on my mi 8 because I have installed a Treble rom. If you are willing to install a treble rom it works fine but the only problem is the treble roms themselves are filled with bugs. It just depends how much you want xposed. The problems I have with treble is bluetooth doesnt work in calls, Screen brightness control is broken and some apps the notch is covering somethings. I would probably wait for a official xiaomi custom rom then install xposed. Hopefully we will see one soon
any update on xposed + Mi8?

Any Soundmod for android 10.0

Im running Pixel experience on my Xiaomi Mi 8 and viper just causes my phone to get stuck on the Mi Logo (before boot animation) any ideas?
For viper4android use this method :
install apk from this link https://forum.xda-developers.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651
don't open the app yet
download zip file from this link and flash it through twrp https://zackptg5.com/downloads/v4afx-rootless_08.18.2019.zip
if viper4android isn't processing then uninstall any audio modification library in your rom and reboot
Wow! This actually worked. Thank you.
Whoa! Finally! Thanks a lot, this worked. Although, there was some weird stuff going on at first.
It got stuck at manufactur logo like usual, after flashing from twrp and installing the driver. I thought this also failed, like my attempts through magisk.
Then I went into magisk manager for recovery, saw a v4a magisk module installed and removed it.
After booting up, v4a was still there, and processing, lol.
Zip file?
Zip file has been removed from the link
I'm on pixel experience android 10
singh44 said:
Zip file has been removed from the link
I'm on pixel experience android 10
Click to expand...
Click to collapse
https://zackptg5.com/downloads/v4afx-rootless_01.15.2020.zip
Just found by navigating on zackptg5's website
https://zackptg5.com/android.php

magisk 20.1 causes bootloop to recovery!

i run china k20 pro on indian miui 11.01.0
i installed twrp -21 version
installing magisk 20 provides root access however magisk manager asks to something which results in bootloop to recovery
ignoring that request, the module i wanted to install [energized ] asks for updating to magisk 20.1 which also leads to bootloop to recovery.
is there anything to do ? or just wait for magisk 20.2 to be released and then try it
p.s installing magisk was the only way to prevent redmi recovery from overwriting twrp, i don't know if this has any importance
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
eLcTrOn said:
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
Click to expand...
Click to collapse
yeah i used magisk uninstaller to make the phone work normally
Glad it worked . Are u able to install magisk again ?
eLcTrOn said:
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
Click to expand...
Click to collapse
Dont install Viper4android via magisk. Just download the package and install in via TWRP. Use this guide
I have this exact problem right now but even with other versions of magisk, I encounter the same issue. Any suggestions?
Same problem here with magisk I guess it is a compatibly issue with MIUI 11
Yep, it's a MIUI11 issue and the reason I haven't shifted over to it. I suspect whatever release of magisk is in the pipeline will fix it provided it's been reported.
In the meanwhile I've read 19.4 works; you could try the canary builds if that seems to old for your liking... just be careful.
Had the same problem, its because of data encryption.
You guys need to format data before installing magisk.
winesh said:
Had the same problem, its because of data encryption.
You guys need to format data before installing magisk.
Click to expand...
Click to collapse
Even with data formatting 20.1 causes issues: In fact, it seems latest Magisk build seems to be causing issues on all (or, many) builds of MIUI 11.
For k20 pro, 19.3/.4 seems smartest to install and then update via magisk manager
I believe other phones (mi 9?) need even older versions like 17.2, so I wouldn't be surprised if future updates continue to push the installation build back.
AvgZing said:
Even with data formatting 20.1 causes issues: In fact, it seems latest Magisk build seems to be causing issues on all (or, many) builds of MIUI 11.
For k20 pro, 19.3/.4 seems smartest to install and then update via magisk manager
I believe other phones (mi 9?) need even older versions like 17.2, so I wouldn't be surprised if future updates continue to push the installation build back.
Click to expand...
Click to collapse
I'm hoping the Magisk situation gets fixed. I checked the Magisk support thread and only saw one post about a bootloop with a Mi9T Pro (again, likely data encryption) so I'm given the impression MIUI might be off the radar for Magisk bug fixes.
I've had a couple of issues with Magisk 20.1 on MIUI10 - nothing critical but a couple times Magisk Manager has frozen (i.e. kill the process, relaunch and it works) and a couple hangs when root apps have been launched for the first time (again, kill + relaunch, a few times if necessary). Smooth sailing otherwise but gives me the impression that Magisk isn't without flaws on MIUI. One response was to dump MIUI altogether but I'd rather have a stable hardware experience for now. I tested a lot of custom ROMs on my last device and based on that, I'd like to stick to MIUI for a while.
Out of curiousity what are the other bugs with MIUI11 aside from it not working with encryption?
droident said:
I'm hoping the Magisk situation gets fixed. I checked the Magisk support thread and only saw one post about a bootloop with a Mi9T Pro (again, likely data encryption) so I'm given the impression MIUI might be off the radar for Magisk bug fixes.
I've had a couple of issues with Magisk 20.1 on MIUI10 - nothing critical but a couple times Magisk Manager has frozen (i.e. kill the process, relaunch and it works) and a couple hangs when root apps have been launched for the first time (again, kill + relaunch, a few times if necessary). Smooth sailing otherwise but gives me the impression that Magisk isn't without flaws on MIUI. One response was to dump MIUI altogether but I'd rather have a stable hardware experience for now. I tested a lot of custom ROMs on my last device and based on that, I'd like to stick to MIUI for a while.
Out of curiousity what are the other bugs with MIUI11 aside from it not working with encryption?
Click to expand...
Click to collapse
Other than standard app compatibility issues, I haven't heard of any major MIUI11 bugs, which is fantastic to hear.
I have tried all sorts. MI9T MIUI 11.0.1.0 and magisk just causes recovery bootloop . Gonna try magisk 19.4 if thats a thing mentioned in a previous reply
I use Miui 11.0.3 together with Magisk. I used the following procedure:
1. Copy Magisk 20.1 (for twrp) to your internal storage (e.g. downloads)
2. Install Magisk via TWRP
3. Don't reboot (it will cause bootloop).
4. Do factory reset (it will remove your Data). Your bootloader will remain patched.
5. Reboot your phone, do initial config.
6. Install Magisk Manager and run it so you will see that Magisk is installed.
7. DON'T install additional files suggested by Magisk Manager (or you will end up in bootloop again)
8. Enjoy your rooted K20Pro!
I got the same problem on my k20 pro (with MIUI EU).I try driffent ways provided by magisk official but no one works.I have to flash the system. It's not a good idea for intalling V4A on this phone
XedosMD said:
I use Miui 11.0.3 together with Magisk. I used the following procedure:
1. Copy Magisk 20.1 (for twrp) to your internal storage (e.g. downloads)
2. Install Magisk via TWRP
3. Don't reboot (it will cause bootloop).
4. Do factory reset (it will remove your Data). Your bootloader will remain patched.
5. Reboot your phone, do initial config.
6. Install Magisk Manager and run it so you will see that Magisk is installed.
7. DON'T install additional files suggested by Magisk Manager (or you will end up in bootloop again)
8. Enjoy your rooted K20Pro!
Click to expand...
Click to collapse
Does your phone remain encrypted after you do these steps? I doubt...
For some reasons, I wanna keep my phone encrypted.

Flyme 8 - SuperSU & Magisk SU problem / Meizu Pro 6 [NOT Plus]

Hi, anybody had a successful install SuperSU or Magisk SU?
Magisk used to be installed direct method, but since It had been upgraded to patch boot.img model, I can`t find a way how to install it.
SuperSU install work right after system root and cause a boot loop after reboot. There were a successful stories for Flyme 7, but I can`t find an exact flash version, which works with that.
Meizu Pro 6
Android 7.1.1, Flyme 8.0.5.0A

Categories

Resources