Related
Anyone got Viper to work on latest Magisk?
None of them install the driver and does anything soundwise, even you can turn the effects on.
I believe It's because it requires new magisk template. Give developers some time to update.
working absolutely fine here on latest FreedomOS CE, which is based on BETA 19.
MarcTremonti said:
working absolutely fine here on latest FreedomOS CE, which is based on BETA 19.
Click to expand...
Click to collapse
may i ask which module are you using!!! and if you did something after installing it, or just installed via Magisk!
that's said, to OP, this is the wrong forum for the post, there's a questions forums where this will be more appropriate.
theduke7 said:
may i ask which module are you using!!! and if you did something after installing it, or just installed via Magisk!
that's said, to OP, this is the wrong forum for the post, there's a questions forums where this will be more appropriate.
Click to expand...
Click to collapse
Latest freedomOS came with magsik 13 beta, but also this worked.
But i updated magisk manually also to 13.1. installed magisk manager update und flashed magisk13.1.zip. done.
FreedomOS also comes with compatibility modules for Arise, but afaik these are only needed because freedomOS comes with enforcing kernel. And the kernel i use now (bluspark) is also enforcing.
Stock OOS comes with permissive kernel and these modules shouldnt be needed there.
AFAIK, dont quote me on that.
MarcTremonti said:
Latest freedomOS came with magsik 13 beta, but also this worked.
But i updated magisk manually also to 13.1. installed magisk manager update und flashed magisk13.1.zip. done.
FreedomOS also comes with compatibility modules for Arise, but afaik these are only needed because freedomOS comes with enforcing kernel. And the kernel i use now (bluspark) is also enforcing.
Stock OOS comes with permissive kernel and these modules shouldnt be needed there.
AFAIK, dont quote me on that.
Click to expand...
Click to collapse
i;m using Blu_Spark too, so i think my kernel is Enforcing, are these Magisk modules (for freedom) available to download!!!
theduke7 said:
i;m using Blu_Spark too, so i think my kernel is Enforcing, are these Magisk modules (for freedom) available to download!!!
Click to expand...
Click to collapse
Yea bluspark is enforcing. I guess they are on gitlab from freedomOS.(check FOS thread for gitlab link)
But i guess easiest way would be just to flash freedomOS. Its nothing else anyway, than debloated stock ROM with a few tweaks. Everything selectable in aroma to your needs.
Try this...
kokesh said:
Anyone got Viper to work on latest Magisk?
None of them install the driver and does anything soundwise, even you can turn the effects on.
Click to expand...
Click to collapse
You can try this:
Update to the latest Magisk version and get everything set. for example, Snapchat and other apps that you might need to pass safety.
After that, you can downgrade to the V.12.0. And V4A it should work fine.
The only bad thing here is that you can't use Android pay or pass safetynet.
This one is working fine for me with OB19/Magisk13/FCkernel25:
https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
also with dolby atmos:
https://forum.xda-developers.com/apps/magisk/soundmod-axon-7-dolby-atmos-t3412342
I use the one from ahrion, too. Works fine.
I am 6
Sent from my ONEPLUS A3000 using Tapatalk
siwan05 said:
This one is working fine for me with OB19/Magisk13/FCkernel25:
https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
also with dolby atmos:
https://forum.xda-developers.com/apps/magisk/soundmod-axon-7-dolby-atmos-t3412342
Click to expand...
Click to collapse
I've tried both. It installs, but once I launch Viper, it asks either for driver install, or shows the driver state as abnormal. Never has any effect on the audio.
So, I've been reading posts about the Magisk version that is safer to install with OOS 5.1.8. A lot of them say that Magisk 16.0 stable is safe, some other say that you need the 16.6 version cause it creates less problems. So, my question is: which one do I use?
Also, if for some reason I use a version that creates problems, does using the Magisk uninstaller remove all the problems?
rickyjumb said:
So, I've been reading posts about the Magisk version that is safer to install with OOS 5.1.8. A lot of them say that Magisk 16.0 stable is safe, some other say that you need the 16.6 version cause it creates less problems. So, my question is: which one do I use?
Also, if for some reason I use a version that creates problems, does using the Magisk uninstaller remove all the problems?
Click to expand...
Click to collapse
I used 16.0 on 5.1.8 without any Problems.
I've been using 16.42(1642) beta up until 16.6 was released a week or so ago. It flashed just fine in the Magisk app and have had zero issues. Works well with ex kernel as well.
16.4 until last week, now 16.6 here, no problems at all
(started with OOS 5.1.6 - 5.1.8 now)
rickyjumb said:
So, I've been reading posts about the Magisk version that is safer to install with OOS 5.1.8. A lot of them say that Magisk 16.0 stable is safe, some other say that you need the 16.6 version cause it creates less problems. So, my question is: which one do I use?
Also, if for some reason I use a version that creates problems, does using the Magisk uninstaller remove all the problems?
Click to expand...
Click to collapse
Uninstaller will remove any problems unless you used something to debloat something. Then you would have to reflash system.
Lol
hi all
sorry if this post is off topic
i am having a problem with the latest magisk 17.1 ,where my banking app is not working as it triggered thaf the phone was rooted.
i do not have this problem with 16.1 stable version
my question is how can i install back the old version without twrp?
I've been dealing with this for a few months now. I'm currently on OxygenOS 9.0.7 stable, i updated today. I noticed a while back in OxygenOS 5.8.5 (oreo) that when i opened the magisk app it said that i had magisk installed, after some seconds the app crashed and said that magisk (19.1 at the time) wasn't installed so i decided to update to pie (oos 9.0.4 iirc) and flashed magisk 19.1 but yet again, i got the same results. I flashed magisk 17 and it did the same thing so i decided to flash magisk 18 and disable magisk updates and that worked but only on pie. Now i updated today to OOS 9.0.7 and when i flash magisk 18 right before the boot animation completes the phone shuts off so i can't use magisk 18. I flashed 19.3 and the app didnt crash but it uninstalled itself after a few hours after the first boot on 9.0.7. I noticed the same behavior with custom kernels and with oos beta.
This only happens with OxygenOS and not in custom roms, i don't want to use a custom rom because of high idle battery drain.
Also, this wasn't happening when i bought the phone. It started occurring in may after i returned to OOS from a custom rom.
I don't know what to do now, i guess i'll roll back to 9.0.6 untill i find a solution.
If someone has had or has the same problem please let me know.
People had this issue a long time. Many reports on 9.0.6 aswell (and prior tho this). Customs saved me from this, I'm on latest oos now and doesn't have any issues (yet I suppose) . I did a format tho when 9.0.7 got released.
Ever since I started to flash Magisk to both slots, I haven't encountered this issue.
For me just uninstall it full, flash full rom(optional but I did)
Reboot then install magisk again, hide all app in magisk hide, hide magisk manager and enable core magisk mode only for 1 day and use it after that it become stable
loque036 said:
I've been dealing with this for a few months now. I'm currently on OxygenOS 9.0.7 stable, i updated today. I noticed a while back in OxygenOS 5.8.5 (oreo) that when i opened the magisk app it said that i had magisk installed, after some seconds the app crashed and said that magisk (19.1 at the time) wasn't installed so i decided to update to pie (oos 9.0.4 iirc) and flashed magisk 19.1 but yet again, i got the same results. I flashed magisk 17 and it did the same thing so i decided to flash magisk 18 and disable magisk updates and that worked but only on pie. Now i updated today to OOS 9.0.7 and when i flash magisk 18 right before the boot animation completes the phone shuts off so i can't use magisk 18. I flashed 19.3 and the app didnt crash but it uninstalled itself after a few hours after the first boot on 9.0.7. I noticed the same behavior with custom kernels and with oos beta.
This only happens with OxygenOS and not in custom roms, i don't want to use a custom rom because of high idle battery drain.
Also, this wasn't happening when i bought the phone. It started occurring in may after i returned to OOS from a custom rom.
I don't know what to do now, i guess i'll roll back to 9.0.6 untill i find a solution.
If someone has had or has the same problem please let me know.
Click to expand...
Click to collapse
Keep magisk out of battery optimization.
°Washy said:
Keep magisk out of battery optimization.
Click to expand...
Click to collapse
That will not keep it from uninstalling. Needs to be installed to both slots and the issue is gone
qbanlinxx said:
Ever since I started to flash Magisk to both slots, I haven't encountered this issue.
Click to expand...
Click to collapse
I will install it in both slots to see what happens. Thanks for the advice.
°Washy said:
Keep magisk out of battery optimization.
Click to expand...
Click to collapse
That doesn't work
qbanlinxx said:
That will not keep it from uninstalling. Needs to be installed to both slots and the issue is gone
Click to expand...
Click to collapse
For me, keep magisk out of battery optimization solved my issue.
loque036 said:
I will install it in both slots to see what happens. Thanks for the advice.
Click to expand...
Click to collapse
How's it been working for you?
qbanlinxx said:
How's it been working for you?
Click to expand...
Click to collapse
No issues so far
I am currently on 9.5.9 GM21BA, twrp and magisk installed, bootloader unlocked.
What would be the best way to upgrade to stock 10.0.3, install smurfkernel and xxxnolimits magisk rom?
I would like to do a clean install, wipe all my data first.
Thanks
{s3rious} said:
I am currently on 9.5.9 GM21BA, twrp and magisk installed, bootloader unlocked.
What would be the best way to upgrade to stock 10.0.3, install smurfkernel and xxxnolimits magisk rom?
I would like to do a clean install, wipe all my data first.
Thanks
Click to expand...
Click to collapse
u answered your own question!
Hey guys, haven't been in the root scene for a few years now and I'm thinking about getting back into it.
Is xposed still a thing?
I have updated to android 12.. will I need to revert in order to do any flashing?
Anyone just running stock with root/xposed? Unless I see a compelling ROM I feel like this would be my choice. How do you like it? Does everything work correctly? Is there a way to add small features like 'hold power for flashlight,' stuff like that?
Do you recommend a particular ROM? What is compelling about it over stock?
Thanks!
I used this guide and running stock android 10 with Magisk root:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
I am using:
TWRP 3.4.0.0
Magisk 21.4
Magisk Manager 8.0.7
Riru 23.5
Riru - EdXposed 0.5.2.1_4677
EdXposed Manager 4.6.2
All running with No problems!
systemshock869 said:
Hey guys, haven't been in the root scene for a few years now and I'm thinking about getting back into it.
Is xposed still a thing?
Click to expand...
Click to collapse
Well, kind of. It now exists as a Magisk module. You need to install Riru module and LSposed module to get an "Xposed like" feature.
BUT, latest Magisk versions (Beta and Canary who are more compatible with Android 12) now have a new feature called zygisk. That feature is not compatible with Riru and LSposed. So if you're going to LSposed, use latest stable Magisk, which still works.
systemshock869 said:
I have updated to android 12.. will I need to revert in order to do any flashing?
Click to expand...
Click to collapse
No.
systemshock869 said:
Anyone just running stock with root/xposed? Unless I see a compelling ROM I feel like this would be my choice. How do you like it? Does everything work correctly? Is there a way to add small features like 'hold power for flashlight,' stuff like that?
Click to expand...
Click to collapse
I'm running stock with latest Magisk Canary and besides that, I only use my Addon features module (which adds some cool custom stuff into stock ROM).
systemshock869 said:
Do you recommend a particular ROM? What is compelling about it over stock?
Thanks!
Click to expand...
Click to collapse
The only ROMs I know that exist for Pixel 4a are ABC and Proton AOSP ROMs. But, if I'm not mistaken, there aren't any ones built for Android 12.
Cheers!
Thanks so much! It's always frustrating, as a casual user, to come back to the mod scene and have to try to re-learn the current meta for both android modding and your particular device by wading through scattered forum posts.
Typhus_ said:
systemshock869 said:
I have updated to android 12.. will I need to revert in order to do any flashing?
Click to expand...
Click to collapse
No.
Click to expand...
Click to collapse
Are there any guides for doing all this in Android 12? Seems like most guides are a bit outdated..
JohnC said:
I used this guide and running stock android 10 with Magisk root:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
I am using:
TWRP 3.4.0.0
Magisk 21.4
Magisk Manager 8.0.7
Riru 23.5
Riru - EdXposed 0.5.2.1_4677
EdXposed Manager 4.6.2
All running with No problems!
Click to expand...
Click to collapse
I was hoping to keep Android 12.. That's exactly the type of guide I'm looking for but seems a bit outdated! Any particular reason you've stuck with A10?
systemshock869 said:
Are there any guides for doing all this in Android 12? Seems like most guides are a bit outdated..
I was hoping to keep Android 12.. That's exactly the type of guide I'm looking for but seems a bit outdated! Any particular reason you've stuck with A10?
Click to expand...
Click to collapse
It depends on what you want to do.
If you want to just root your device, you only need to do 2 things:
1 - Unlock your bootloader (see HERE )
2 - Flash Magisk patched boot.img (see HERE )
For custom ROMs and etc, you should just check the ROMs, Kernels, Recoveries, & Other section. I bet there's a lot of info there about that.
systemshock869 said:
Any particular reason you've stuck with A10?
Click to expand...
Click to collapse
Just that some Xposed apps and modules only work with android 10, and I don't see any features of A11 or A12 that I would use.
Typhus_ said:
It depends on what you want to do.
If you want to just root your device, you only need to do 2 things:
1 - Unlock your bootloader (see HERE )
2 - Flash Magisk patched boot.img (see HERE )
For custom ROMs and etc, you should just check the ROMs, Kernels, Recoveries, & Other section. I bet there's a lot of info there about that.
Click to expand...
Click to collapse
Awesome. Thanks! There seem to be some concerns in the Magisk thread about safetynet.. do you have root successfully hidden?
Is TWRP required for installing the addon module zips from your first post?
systemshock869 said:
Awesome. Thanks! There seem to be some concerns in the Magisk thread about safetynet.. do you have root successfully hidden?
Is TWRP required for installing the addon module zips from your first post?
Click to expand...
Click to collapse
SafetyNet will fail as soon as you unlock your bootloader.
There is a Magisk module provided by kdrag0n that fixes that but the free version, for the time being, needs Riru and Lsposed to work properly. That means you need to root your device using stable Magisk 23.0 if youwant to fixe SafetyNet right away.
The magisk patched boot.img version that I've shared on that post I've pointed out to you is Canary Magisk, where Magisk Hide feature no longer exists and it's incompatible with Riru and LSposed, as I've already said.
I'm running my device with SafetyNet failing and I couldn't care less since it's not problematic for my daily usage. Any app I cannot install through playstore can be installed using apkmirror. As for Magisk hide, it doesn't exit anymore but there's a "App deny list" that works as well to "hide" Magisk from banking apps (for instance).
I'm not using TWRP since there's really no need for it on Pixel 4a.
Everything can be done through fastboot and Magisk.
Anyway, if you really want to have SafteyNet passing, you need to manually patch stock boot.img (that you may find as well on that thread I've shared) with latest Magisk stable and flash that version. Afterwards install Riru, LSposed and SaftyNet fix by kdrag0n.
Cheers!
Typhus_ said:
I'm not using TWRP since there's really no need for it on Pixel 4a.
Click to expand...
Click to collapse
I use TWRP to do image Backups/Restores.
JohnC said:
I use TWRP to do image Backups/Restores.
Click to expand...
Click to collapse
I don't need to do that. Everything I have is backed up on my Google account.
Sure, /data and stuff like games or whatever needs to be downloaded again but, it's fine by me.
Furthermore, I don't use custom ROMs any more. Just stock Pixel ROM with my mods installed and I get by just fine, smooth and happy.
Cheers!
systemshock869 said:
I have updated to android 12.. will I need to revert in order to do any flashing?
Click to expand...
Click to collapse
Depends on the ROM. LineageOS staff say to install the latest Android 11 image before flashing a LineageOS 18.1 rom. I'd assume that to be true for any other roms based on LineageOS.
Typhus_ said:
It depends on what you want to do.
If you want to just root your device, you only need to do 2 things:
1 - Unlock your bootloader (see HERE )
2 - Flash Magisk patched boot.img (see HERE )
For custom ROMs and etc, you should just check the ROMs, Kernels, Recoveries, & Other section. I bet there's a lot of info there about that.
Click to expand...
Click to collapse
Do u have to disable OTA updates to keep from a calamity? If so, are manual updates a pain? Can u retain ur data with manual OTAs?
Zaxx32 said:
Do u have to disable OTA updates to keep from a calamity?
Click to expand...
Click to collapse
Yes.
Zaxx32 said:
If so, are manual updates a pain?
Click to expand...
Click to collapse
No.
Zaxx32 said:
Can u retain ur data with manual OTAs?
Click to expand...
Click to collapse
Yes.
Everytime a new build comes up, download the factory image directly from Pixel Official firmware site, extract it, open flash_all.bat, on the update command you see a "-w" flag. Delete the "-w" and save flash_all.bat. Connect device to PC, reboot to fastboot and run edited flash_all.bat.
If you don't delete the -w, you'll lose your data.
Cheers!
Awesome....thanx!