Related
Hey guys,
I've done some searching around on this issue, and it looks like Snapchat is not allowing me to login as my device is rooted. However, I had the factory OxygenOS ROM (rooted as well) installed before and never had this issue. Now that I have installed Sultanxda's "Unofficial CyanogenMod 13.0 with custom kernel", I can no longer get Snapchat to login. Like I said, from the searching that I've done it look like it is root related, so I went into SuperSU and did a complete unroot. This still hasn't solved the issue yet, so now I'm stuck and not sure what to do. Is there something I'm missing or is there a way to solve this without having to reflash a different ROM and loose all the time spent setting this one up?
Thanks for the help!
saleenman95 said:
Hey guys,
I've done some searching around on this issue, and it looks like Snapchat is not allowing me to login as my device is rooted. However, I had the factory OxygenOS ROM (rooted as well) installed before and never had this issue. Now that I have installed Sultanxda's "Unofficial CyanogenMod 13.0 with custom kernel", I can no longer get Snapchat to login. Like I said, from the searching that I've done it look like it is root related, so I went into SuperSU and did a complete unroot. This still hasn't solved the issue yet, so now I'm stuck and not sure what to do. Is there something I'm missing or is there a way to solve this without having to reflash a different ROM and loose all the time spent setting this one up?
Thanks for the help!
Click to expand...
Click to collapse
Hi, the searching can be useful sometimes
http://forum.xda-developers.com/search/forum/5476?query=snapchat
You need an fully unrooted rom to login into snapchat, after that you can flash supersu.
NevaX1 said:
Hi, the searching can be useful sometimes
http://forum.xda-developers.com/search/forum/5476?query=snapchat
You need an fully unrooted rom to login into snapchat, after that you can flash supersu.
Click to expand...
Click to collapse
Ah, looks like I just didn't search enough. This seems to have done the trick, thanks!
I think you just need to uninstall Xposed Framework for Snapchat to login and then after login you can install Xposed again.
This sounds weird but what worked for me was to download superkiwi via xposed installer, it's supposed to bypass root detection for banking apps in New Zealand but works with snapchat [emoji14]
I found this workaround in a thread somewhere and thought that it wouldn't hurt to try but actually works mighty fine!
Sent from my ONEPLUS A3003 using Tapatalk
Leaving this here in the hopes it helps someone else, took me a bit to find the correct steps.
Currently running the last official CM 13 build for the Droid Turbo (will be moving to LOS soon), rooted with SuperSU Pro, Xposed framework v87, on the newest TWRP.
Nothing worked, not Xposed Switch, Root Switch, nothing. In fact I had to reinstall Xposed Switch to be able to turn root back on, while Root Switch simply uninstalled the SuperSU binary, I had to reflash it. Finally I put it all together and in the following order I got Snapchat to work.
Make sure any OS root (my case CMroot) was turned off.
Download the correct version of Xposed framework Installer, Xposed Uninstaller, and the SuperSU binary (all flashable zip files) for your device to a location on your system that you can easily access from recovery. For me its my TWRP folder.
Uninstall Snapchat. Open a File Explorer and delete the entire Snapchat folder left over.
Select the uninstall "permanently unroot" option from SuperSU, but DON'T let it install the original... Whatever it is, the name escapes me. But don't let it!
Phone will reboot automatically after taking out root, boot to recovery, run Xposed Uninstaller, wipe Cache & Dalvik, reboot phone.
When the phone boots, confirm it is unrooted and Xposed Framework is uninstalled. A root checker app and opening the Xposed App worked for me here.
Install Snapchat, sign into Snapchat. It will accept your login if you did everything correctly.
*This step I did to save myself work in the future, but you can do it later. Turned on CMroot and took a TiBackup of logged in Snapchat in case I ever have to login again, I can just reload the data.*
Boot to recovery. Flash the Xposed framework and the SuperSU binary (in that order), wipe Cache and Dalvik, reboot system.
Open Snapchat to confirm its still logged in. If so grab a TiBack of it for use as needed later.
I hope this helps!
Sent from my DROID Turbo using XDA-Developers Legacy app
sorry guys Magisk currently does not pass safetynet checks (24-06-2017) so this guide is a bit out of date but you can still use it, I will make another guide for this once magisk v13 comes out and fixes this problem
Hi guys! just a quick guide on how to install magisk, re-enable use of Samsung Health, and pass SafetyNet and be play store certified.
This guide will be pretty brief as i don't have the time or commitment to do an in-depth guide and I believe if you are here that you should know what you are doing (if anyone wants to make this in-depth, please be my guest).
this guide is for people who have tripped knox and still want to use s health while still getting the most out of their phone
You will need:
Odin:
https://www.androidfilehost.com/?fid=529152257862705230
TWRP for your device (you should be able to find guides with the download link)(you should also flash back to complete stock if you are already rooted to avoid any problems with previous roots)
no-verity-no-encrypt_ashyx.zip:
https://www.androidfilehost.com/?fid=24591000424951049
Magisk v12.0:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Now that you have those 4 files we can start.
Skip steps 1-6 if you already have root and only wish to use samsung health
1. put magisk v12.0 and dm-verity patch onto the sdcard in the phone
2. flash TWRP using odin
3. boot into recovery and swipe to allow modifications.
4. under wipe there should be a button to format data (its in the bottom right). you will need to do this to flash magisk and dm verity.
5. flash Magisk and THEN dm verity
6a. boot into phone and complete setup to get to home page.
6b. download any systemless root app that you want (adaway works you just have to turn on systemless host files in magisk settings + viper4andriod has a module in magisk that you download for it to work)
(DO NOT TURN ON HIDE MAGISK UNTIL THE END)
7. download the app buildprop editor, open it and grant it root. search for the line ro.config.tima=1 and change the value from 1 to 0.
8. reboot the phone and you should now be able to use s health.
continue following if you wish to pass safetynet and be playstore certified (set up your root apps like viper and adaway before doing this)
9. go into magisk settings and enable the setting Magisk Hide. reboot phone. check that you pass safetynet in magisk manager after booting up again
10. go into app manager, find google play store, tap storage and then clear the data.
11. open app again and you should be certified. (this took me a few tries. not sure if it was play store needing to update the property or me needing to reboot the phone)
12. Yay! your device should now be able to pass safetynet and will be play store certified in the play store app. you should soon be able to see netflix in the play store again.
source: I done this on my a520 just on the weekend to be able to update netflix
I'll try this next update, thnx!
Does this require an external sd card?
korwynkim said:
Does this require an external sd card?
Click to expand...
Click to collapse
Yes i believe so, although I have never tried doing it without
According to the XDA page of Magisk it already supports dm-verity and forceencrypt. So is the separate download of no-verity-no-encrypt_ashyx.zip still necessary?
Edit: What does the change " ro.config.tima=0" do?
reayard said:
According to the XDA page of Magisk it already supports dm-verity and forceencrypt. So is the separate download of no-verity-no-encrypt_ashyx.zip still necessary?
Edit: What does the change " ro.config.tima=0" do?
Click to expand...
Click to collapse
oh i did not know that it supported it already so maybe its not? not sure, try it out and see what happens?
the config change make it so that the rom thinks you still have knox enabled to you are able to use samsung health still (it got a "security update" that makes it so that phones with knox tripped will not be able to use it)
Good to know ! Thank so much !
But what's the real possibilities of this recent "magisk" ?
It can root with systemless ?
And in theory with systemless-root ,that don't trip the knox and we can use all apps and full hardware ....because it consider that the system is safe and untouched ===> i'm truth or wrong ?
Loulou-13 said:
And in theory with systemless-root ,that don't trip the knox...
Click to expand...
Click to collapse
According to some other threads (and if I remember correctly from my own experience with the S7) Knox gets triggered as soon as you flash a custom recovery.
A positive effect of Magisk vs. SuperSU could be that system updates are still possible as the system partition is still unchanged. On the other hand the custom recovery will most probably cause the update to fail.
What seems to make Magisk superior to SuperSU is MagiskHide so that the system appears to be unchanged for PlayStore and apps using SafetyNet.
reayard said:
According to some other threads (and if I remember correctly from my own experience with the S7) Knox gets triggered as soon as you flash a custom recovery.
A positive effect of Magisk vs. SuperSU could be that system updates are still possible as the system partition is still unchanged. On the other hand the custom recovery will most probably cause the update to fail.
What seems to make Magisk superior to SuperSU is MagiskHide so that the system appears to be unchanged for PlayStore and apps using SafetyNet.
Click to expand...
Click to collapse
Thank so much for sharing Samsung experience
Before i have had olds goods samsung fully customised ! It was funny before ,at this time ....and then always have had LG phones and just an unlock of bootloader+Systemless root din't have problem at all (full playstore&experience)
Now with the samsung evolution and my new A5 ,i don't want at all loose OTA updates,knox flag.... and all functions+playstore as you have said . And magisk is recent...
I want to be sure at 100....0000% that "magisk" systemless root doesn't affect anything .
i'm not interested at all by TWRP ...completely useless until there eventually have "real" customs developments and many things can be flashed by flashfire,flashify....
Loulou-13 said:
I want to be sure at 100....0000% that "magisk" systemless root doesn't affect anything .
i'm not interested at all by TWRP ...completely useless until there eventually have "real" customs developments and many things can be flashed by flashfire,flashify....
Click to expand...
Click to collapse
I doubt that FlashFire or Flashify can flash anything without root. The website of FlashFire for example says "FlashFire is the most advanced on-device firmware flasher available for rooted Android devices.". And the same for Flashify: [APP][4.0+][ROOT] Flashify.
reayard said:
I doubt that FlashFire or Flashify can flash anything without root. The website of FlashFire for example says "FlashFire is the most advanced on-device firmware flasher available for rooted Android devices.". And the same for Flashify: [APP][4.0+][ROOT] Flashify.
Click to expand...
Click to collapse
Yes yes....sure...i didn't have precised...
Root with a method who din't need twrp and don't touch samsung things....and then flash what we want with these apps ...
Hi, Im XxViRUsPRO.
1.You Need Magisk Manager (Removed Form PlayStore) So this is the Download Link https://mega.nz/#!olRzFRTZ!eNOb6yVtvsAlb3V8sIOaRRfsHtQG952_WU--3TCDvck
2.To Use S Health On Rooted Phone You Need To Edit /System/Build.prop
and Change ro.config.tima=1 to ro.config.tima=0 using (Es File Explorer or Root Browser)
safety net check does not pass in Samsung galaxy a5 2015
What is this dm verity and for encryption? I have the latest magisk and i see those options in my magisk manager but donot know its utilization! and probably for the same reason my safety net check does not pass in Samsung galaxy a5 2015
reayard said:
According to the XDA page of Magisk it already supports dm-verity and forceencrypt. So is the separate download of no-verity-no-encrypt_ashyx.zip still necessary?
Edit: What does the change " ro.config.tima=0" do?
Click to expand...
Click to collapse
Dis any one could enable the fm chip in nougat once rooted ,in Canada Samsung disable the fm chip and i would get it back
why does flashing magisk wipes all user data including internal storage?
Samsung A5 sm-a500f
Hi all,
I have installed Magisk 16.0 based on Maik93's post, and Xposed Framework SDK27 90.2-beta3 (Systemless), through Magisk modules.
When I enable the Xposed module, the phone first shows endless boot animation, and when restarting it again, it boots, but the Xposed app seems not installed (not listed in Settings->Apps and its icon is not present in chooser), although, in Magisk, it is visible in the Modules and it's checkbox is checked.
Did anybody successfully installed Xposed with A2 Lite? What can be the problem?
Thanks a lot,
Circum
Did you install the apk of xposed?
---------- Post added at 11:51 PM ---------- Previous post was at 11:46 PM ----------
https://forum.xda-developers.com/attachment.php?attachmentid=4393082&d=1516301692
Here is the link from xda
No, sorry, I was not aware that it is a separate thing.
Now I have installed, but it says that no Xposed Framework is installed. If I try to install a framework from inside the installer (90-beta3), it -- obviously -- reports an error that /system/framework/XposedBridge.jar already exist...
Because of this, I cannot enable any module from Xposed Installer.
Any tips what do I do wrong?
I want to use Xposed too but we will have to wait for TWRP I guess.
Not sure what happened to you, did you tried ti reboot your phone? Mine is working just fine
mik.y said:
I want to use Xposed too but we will have to wait for TWRP I guess.
Click to expand...
Click to collapse
You can install now through Magisk if you want, if yiu get bootloopbfor any xposed module, just flash thr original boot.img
HoangP05 said:
You can install now through Magisk if you want, if yiu get bootloopbfor any xposed module, just flash thr original boot.img
Click to expand...
Click to collapse
I was able to install it somehow,but stuck after each reboot in process. Now some apps are diying like call enhancement and some test app. So its quite dirty. I have Magist 16.0 installed.
Lol,I cant connect to internet with xposed to download any module. Useless
mik.y said:
I was able to install it somehow,but stuck after each reboot in process. Now some apps are diying like call enhancement and some test app. So its quite dirty. I have Magist 16.0 installed.
Lol,I cant connect to internet with xposed to download any module. Useless
Click to expand...
Click to collapse
Not all are working apparently, but if it is bootloop, you so try to let it boot again, press power and volume down as the same time while it bootloop, the second boot always work for me
There is TWRP for Mi A2 Lite.
Search on google.
NOTICE: For now there isn't official TWRP. There'w unofficiak fork which can you install using fastboot. :good:
Not sure what happened, AFAIK I have rebooted the phone at least once, but after rebooting again, it said that the framework is installed, but has some problem with it and not functioning (yellow background, sorry, I forgot to take a screenshot), and rebooting once again solved the problem, I can confirm that Xposed works.
But as others mentioned, installing Magisk itself makes problems with the boot. Booting always stucks, I always needed (even before installing Xposed) to long-press power after several minutes and the second try usually boots up.
Now having Magisk and Xposed (and GravityBox) installed usally need to restart booting twice (i.e., the 3rd boot works).
Any suggestions how to debug / get logs about this problem?
HoangP05 said:
Not sure what happened to you, did you tried ti reboot your phone? Mine is working just fine
Click to expand...
Click to collapse
Xposed's Gravity box module works on Mi A2 lite?
Yes, GravityBox is working, although as I mentioned, there are issues with boot - I have to reboot several times until it succeeds...
performace drops significantly when i install the xposed module for magisk. i hope they fix it.
So far everything works fine on my end, I'm not noticing any performance drops in my day to day use. Then again I haven't used it much without Magisk + exposed but from what i'm seeing it's working well, no noticeable lag or stuttering.
I have gravity box, Amplify and Greenify modules running.
circum said:
Not sure what happened, AFAIK I have rebooted the phone at least once, but after rebooting again, it said that the framework is installed, but has some problem with it and not functioning (yellow background, sorry, I forgot to take a screenshot), and rebooting once again solved the problem, I can confirm that Xposed works.
But as others mentioned, installing Magisk itself makes problems with the boot. Booting always stucks, I always needed (even before installing Xposed) to long-press power after several minutes and the second try usually boots up.
Now having Magisk and Xposed (and GravityBox) installed usally need to restart booting twice (i.e., the 3rd boot works).
Any suggestions how to debug / get logs about this problem?
Click to expand...
Click to collapse
Magisk alone didnt give me boot problems. What rooting guide did you follow?
fake__knv said:
Magisk alone didnt give me boot problems. What rooting guide did you follow?
Click to expand...
Click to collapse
I used this one: https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-device-t3825626
But before the update. Since that I have removed Magisk to enable the OTA update, and did not put it back yet -- although, there are many small areas I feel the lack of root...
circum said:
I used this one: https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-device-t3825626
But before the update. Since that I have removed Magisk to enable the OTA update, and did not put it back yet -- although, there are many small areas I feel the lack of root...
Click to expand...
Click to collapse
I can assure you @BubuXP's guide is good. Used his rooting guide, followed the steps for updates and its good to go. I rooted my phone when Im on August update. Now Im in September update
MODIFIED EXCLUSIVELY FOR MOTO G7 PLAY
WARNING
Do not try to install this via fastboot, remove the magisk, to remove just reinstall the Stock Rom
MAIN FEATURES
Root modified by Spaceminer
More speed
Added multiple apps
Several useless apps removed
Black theme automatically enabled in all supported applications
Gapps already installed
Notch fix
And more
DOES NOT WORK
Fingerprint
Automatic brightness
INSTALLATION INSTRUCTION
1. Download and extract
2. Put the GSI on your memory card
3. Restart your phone in Bootloader / Fastboot mode
4. Open fastboot on your computer
use the command: fastboot -w
use the command: fastboot boot twrp.img
5. TWRP: Install> Install image> Choose image file> Flash on the system
DOWNLOADS
TWRP by Spaceminer: https://mega.nz/#!roRzBCTK!THHq0VMWqgtowJNkY-Id3b9S9H9dhzsJhE83k0Kvt2k
GSI: https://www.drive.google.com/file/d/1000HaJJqMdGyOtEd7ribp4n5Eb9l-3my/view
Works great apart from when I make calls the microphone doesn't work...whatsapp calls are fine it only seems to be a problem on cellular!
When I select the image I get 4 options and it does not let me install with any
With this my G7 play stay 32bits or can change for 64 bits?
RafaelItape said:
With this my G7 play stay 32bits or can change for 64 bits?
Click to expand...
Click to collapse
until we get a 64 bit kernel, it'll stay 32. i want to build a 64 kernel cause i want to bring ubuntu touch to this phone, that requires a 64 bit boot image, if we are to use erfan's (only method for android 9 devices rn)
Thanks man.
Managed to get magisk working with this rom..alongside twrp
Simply install latest magisk canary APK (284). Give it super user when it asks and restart the app
Then when clicking install...it gave me option of direct install (make sure recovery is selected). It should install successfully
I then rebooted to bootloader and to get to twrp hold volume up after selecting recovery and dont hold anything to boot back to Los..
Can't share my boot image if that helps anyone
CFKod said:
Thanks man.
Managed to get magisk working with this rom..alongside twrp
Simply install latest magisk canary APK (284). Give it super user when it asks and restart the app
Then when clicking install...it gave me option of direct install (make sure recovery is selected). It should install successfully
I then rebooted to bootloader and to get to twrp hold volume up after selecting recovery and dont hold anything to boot back to Los..
Can't share my boot image if that helps anyone
Click to expand...
Click to collapse
I gave it a try. It did indeed let me patch directly. It was very unstable. Things asking for su multiple times and not remembering my choice, certain modules not installing, and I always seemed to lose root entirely after rebooting
BobbyBlunt said:
I gave it a try. It did indeed let me patch directly. It was very unstable. Things asking for su multiple times and not remembering my choice, certain modules not installing, and I always seemed to lose root entirely after rebooting
Click to expand...
Click to collapse
yup... sorry, forgot to post... I assumed it was after installing modules.
Lockscreen not work for me, in all gsi roms.
Only stock works.
rom works great, feels like a new phone.
model XT1952-4.
not working unfortunately is the FM radio.
based on the error message when trying to install FM apps, it looks like the kernel driver was not included in the rom?
I can deal with the fingerprint not working, it would be really nice to get the FM driver included so I don't have to use data.
Overall the phone is so much better with this rom, Thank You!!!!
Hi, probably a stupid question, considering I'm new: what does this differ from the Lineage OS instructions for Moto G7 Play at their web site? I mean, why shouldn't I stick with their instructions?
I just want to understand what is at stake here (again, I'm new at this world of smartphone os's)
I'm really interested in replacing Android (which I like, but it's... Google ) and all carrier bloatware stuff by a free OS.
EDIT: Nevermind. I've just realized that it isn't for the G7 Play, it's for G7 only. Sorry about this (maybe useful for other newbies like me)
Thanks for all the work
Everything seems stable been using on daily driver for 2 days now. Only issue is bluetooth audio not working. I'm wondering if the Motorola face unlock app would work however current version isn't available.
gadolf said:
Hi, probably a stupid question, considering I'm new: what does this differ from the Lineage OS instructions for Moto G7 Play at their web site? I mean, why shouldn't I stick with their instructions?
I just want to understand what is at stake here (again, I'm new at this world of smartphone os's)
I'm really interested in replacing Android (which I like, but it's... Google ) and all carrier bloatware stuff by a free OS.
EDIT: Nevermind. I've just realized that it isn't for the G7 Play, it's for G7 only. Sorry about this (maybe useful for other newbies like me)
Click to expand...
Click to collapse
I'm using this on a Moto g⁷ Play in the USA, currently it's pretty stable. As for what's at stake, you lose access to Bluetooth audio, fingerprint & faceunlock unless you have SD card formated as portable storage and manage to get magisk working. There's a fix for Bluetooth Audio with magisk or ADB but I don't remember what the command was. Also as for magisk you should be able to fix atleast faceunlock because Motorola uses an app for it.
XxLilJeepXx said:
I'm using this on a Moto g⁷ Play in the USA, currently it's pretty stable. As for what's at stake, you lose access to Bluetooth audio, fingerprint & faceunlock unless you have SD card formated as portable storage and manage to get magisk working. There's a fix for Bluetooth Audio with magisk or ADB but I don't remember what the command was. Also as for magisk you should be able to fix atleast faceunlock because Motorola uses an app for it.
Click to expand...
Click to collapse
Thank you very much for sharing. I await your further results if any new issues arise to proceed with installing Lineage OS 17
Good job with the notch feels good to swipe down properly I’m encountering a issue the captive login appears to be broken I can’t sign into any WiFi’s that need a portal entry the portal screen doesn’t come up also I found how to get magisk to work properly With twrp u need the newest canary version and u have to patch directly (have recovery option enabled) which u use the root of this rom to achieve that after that backup boot image in twrp which will leave it with the magisk patched and twrp after reinstall the rom remove the phh root and restore yeh boot image in twrp and reboot to recovery from twrp and install magisk manager just note it’s lineage that makes magisk act up hence certain apps not obtaining root is lineage fault cause with another GSI like havoc which this method works for also (works with all GSIs to my knowledge) there no root app issues or modules not working just noticed that on lineage
workin on fixing phone
yashor said:
Thank you very much for sharing. I await your further results if any new issues arise to proceed with installing Lineage OS 17
Click to expand...
Click to collapse
phone no longer working because of trying to install magisk but I'll be trying to fix with LMSA and then using @PoochyX's instructions tomorrow
Edit: LMSA is now Rescue and Smart Assistant, I just tried to restore it with this but it needs to be on stock firmware to restore.
XxLilJeepXx said:
phone no longer working because of trying to install magisk but I'll be trying to fix with LMSA and then using @PoochyX's instructions tomorrow
Edit: LMSA is now Rescue and Smart Assistant, I just tried to restore it with this but it needs to be on stock firmware to restore.
Click to expand...
Click to collapse
Why not just boot into bootloader mode and fast boot stock firmware to recover your device ?
PoochyX said:
Good job with the notch feels good to swipe down properly I’m encountering a issue the captive login appears to be broken I can’t sign into any WiFi’s that need a portal entry the portal screen doesn’t come up also I found how to get magisk to work properly With twrp u need the newest canary version and u have to patch directly (have recovery option enabled) which u use the root of this rom to achieve that after that backup boot image in twrp which will leave it with the magisk patched and twrp after reinstall the rom remove the phh root and restore yeh boot image in twrp and reboot to recovery from twrp and install magisk manager just note it’s lineage that makes magisk act up hence certain apps not obtaining root is lineage fault cause with another GSI like havoc which this method works for also (works with all GSIs to my knowledge) there no root app issues or modules not working just noticed that on lineage
Click to expand...
Click to collapse
Hi,
From your experience which GSI is better for MOTO G7 Play 1952-2:
Havoc or Lineage ?
It depends on what u trying to do exactly if u a heavy Magisk user u want to stay away from lineage and use havoc since magisk plays well with it if u don’t care about magisk and just want a simple root then this rom be a good experience for other then rom WiFi portal issues this rom it’s excellent cause it’s the only one with the notch fix if that fix was easily implemented out this rom and could be used with another GSI that would of been fantastic...
PoochyX said:
It depends on what u trying to do exactly if u a heavy Magisk user u want to stay away from lineage and use havoc since magisk plays well with it if u don’t care about magisk and just want a simple root then this rom be a good experience for other then rom WiFi portal issues this rom it’s excellent cause it’s the only one with the notch fix if that fix was easily implemented out this rom and could be used with another GSI that would of been fantastic...
Click to expand...
Click to collapse
Thank you for your reply.
I favor stability and performance over Magisk.
In my case, do your recommend Lineage as my best option to try?
Viper4Android for Google Pixel 6/6 Pro and most other devices on Android 12...
It the time of testing this Method, it worked in November 2021 and December 2021 builds for my Google Pixel 6....
1) Make sure your BL is unlocked and you are ROOTed via Magisk.
2) 1st I installed the attached Viper4Android file WITHOUT opening it.
3) The 2nd file Which is the FIX for Android 12. That can be flashes via Magisk BUT DONOT REBOOT.
4) Once you have installed apk and flash FIX.zip via Magisk, now Grant Magisk SU Rights, Install Driver's, let it automatically reboot.
5). Viper ~~>Settings~~> Legacy Mode Flipped On
6) Enjoy
*Edit*
ADDED Status Screenshot
that's just copying the same post-fs-data.sh file we've been using since like 2019
Roll3r said:
that's just copying the same post-fs-data.sh file we've been using since like 2019
Click to expand...
Click to collapse
And is stolen from here, without any credit
Typhus_ said:
Hello!
I've got Viper4Android version 2.7.2.1 working on Android 12 without the need for any other module installed and with SELinux enforcing.
I've found another thread where other users where talking about Viper on Android 12 and saw THIS post by @TheExoduser.
That solution, in fact, works, so I came up with a simple Magisk module that just changes the script.
All that this "fix module", attached bellow, does is to update the post-fs-data.sh script, included on official installer by @Team_DeWitt and deletes itself after replacing the script.
This is done after 20 seconds upon the reboot, we have to do on Magisk, after installing the fix.
As soon as the script is changed and the fix gets deleted by itself, you may need to enable Legacy mode, on Viper4Android app, choose your desired options and reboot the device again.
If you don't reboot again you won't notice any audio change.
Sometimes a second reboot is needed (faced that during my tests).
Hope this helps.
Cheers!
Click to expand...
Click to collapse
No problem. As long as it helps other users I don't mind that anyone shares it to the world. Credits would be nice though but... whatever...
Merry Christmas to everyone.
Cheers!
DanielF50 said:
And is stolen from here, without any credit
Click to expand...
Click to collapse
Stolen fair and square yo!