/////
THIS GUIDE WAS FROM THE NOVEMBER SECURITY PATCH ON NOUGAT!!! DO NOT DO THIS IF YOU ARE ON OREO CAUSE YOU WILL LOSE ALL SOUND!
IF YOU WOULD LIKE TO USE VIPER ON OREO/PIE DEVICES. PLEASE USE THE MAGISK MODULE AND/OR FIND A BETTER GUIDE WITH A COMPATIBLE ZIP
//////
Okay I have confirmed that sound mods work on the Moto z2 force with no issues whatsoever many probably know that
How to Install:
1.
make sure you have root and TWRP installed on your Moto Z2 force
2.
download this version of A.R.I.S.E.
https://androidfilehost.com/?fid=457095661767141554
3.
Place the zip file in the Internal storage of your device (so its easy to find)
4.
Boot into TWRP recovery and click install
5.
Find the file you put in your internal storage named;
ARISE+Deuteronomy+2.94+Modular+AROMA+Installer.zip
And then swipe to install
6
An install wizard should appear and assuming that you haven't used this before select easy mode on the wizard and make sure you have it set to "install core engine then modules" and spam the hell out of the next button besides those 2 things
7.
TWRP screen should appear and you should boot into your device like normal
8.
ENJOY
SOME NOTES:
A.R.I.S.E AM3D DOES NOT WORK BUT OTHER THAN THAT EVERYTHING ELSE IS FINE
Update: DO NOT ATTEMPT TO INSTALL MAGNUM OPUS IT WILL FAIL
!!!!DISCLAIMER!!!!!
-I AM NOT RESPONSIBLE FOR A INCREASE IN GAS PRICES GETTING CHEATED ON BY YOUR WIFE OR A BRICKED DEVICE
Man.. I was going to try ARISE, but with all the concerns that I couldn't restore a nandroid because of data partition encryption, I just said screw it and I installed the v4a 2.3.4 module right from Magisk, and it works great with both USB Type-C to 3.5mm and Bluetooth.
I don't know if anyone's noticed or not, but Oreo has an entire section on Bluetooth audio protocol under the development options. Things like sample rate, bit rate, etc etc. I do know that v4a works with all protocols (SBC, AAC, aptX, aptX HD and LDAC), but if you up the sample rate to 96khz, it will NOT process. I usually use 48khz and it sounds great.
I installed arise and lost all audio on device . I don't know if it's a setting or something in aroma I should not have added or if it's viper settings I messed with .
I need to uninstall this how do I
Or how do I get sound back this is weird
joesee said:
Man.. I was going to try ARISE, but with all the concerns that I couldn't restore a nandroid because of data partition encryption, I just said screw it and I installed the v4a 2.3.4 module right from Magisk, and it works great with both USB Type-C to 3.5mm and Bluetooth.
Are you on Oreo 8.0 running V4A? Thanks!
Click to expand...
Click to collapse
climbhigh77 said:
Are you on Oreo 8.0 running V4A? Thanks!
Click to expand...
Click to collapse
Yes sir, I am. Since I got it working, I haven't touched anything in fear that it'll stop working. I haven't even made a nandroid. Twrp isn't installed, I just booted in it from adb.
Right on! I was also advised not to install TWRP. I flashed it and it seems to be working so far. Having other issues though like my camera and flash (flashlight) don't work now since installing magisk or the v4a which one I'm not sure but I assume magisk.
3/12/18 Update: camera and Flash are working properly now after a wipe Dalvik, cache and reboot.
Is anyone else having issues with viper4android working intermittently on Oreo? Sometimes it works but mostly it doesn't and I have no way to control it, toggling the switches does nothing and it doesn't matter if I reboot or not. It does work sometimes so I know the drivers are installed, and I've tried a fresh install a few times using the 2.3.4 version and the newest 5.0 version which produces the same result.
Is there a setting in magisk or Viper that I need to apply to to get it working seamlessly? I have systemless hosts check-in magisk already for ad blocking. There's got to be something I'm missing here. Any help is greatly appreciated thanks!
I was having this situation, the I disabled the music FX and it's gone for now
Flashlight stops because of selinux
Dolby Atmos for oreo works fine without any problems. You just have to find the working version in the last few pages of the mod thread.
Was able to get the latest ARISE, plus V4A, and Dolby ATMOS Oreo from guitardedhero working. I'm using SuperSU as I'm not a fan of Magisk. Flashed the latest ARISE, including the V4A 2.5.0.5. Crap, I made sure V4A opened and checked that the drivers were installed. But I may have flashed the ViPER4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk over the ARISE loaded v4a apk....? Try to see if the loaded apk works first. If not, flash Nougat_IO_test_fix.apk over: ViPER4Android_FX_v2505.zip Anyway, use this to set permissive: The.SELinux.Switch.ver.6.0.3.build.603.apk. Reboot. ARISE libs will be there and V4A should work. Sometimes you have to turn off the main power button for the V4A mod, go up to the corner button and exit. Clear out anything in recents. Then open V4A back up, and enable the power button. If music is playing, you will hear the change.
Ok.....Dolby. Go HERE and download the normal zip. Thank the dude, he's done a lot for us audiophiles. Flash it. Reboot. Apps will be there, and will likely forceclose. You have to extract the dolby zip and copy the libs from the dolby/lib and dolby/lib/soundfx files and paste them in the related folders in root /system/vendor and system/vendor/soundfx. You need to set the permissions to rw-r-r (644). Now save/reboot. Apps should work. I'm betting other libs/files weren't installed either, but just those got Atmos working, working well. Still looking through things and will verify later what else wasn't placed.:good:
Quick Question, I have used ARISE and Viper before and really like them but this is a Software Mod. I would just like to clarify that this Software Mod works on the actual Hardware Mod and if it does, does this Software Mod work on the Hardware Mod using a Custom ROM or Kernal? Can anyone confirm that yet?
androidddaaron said:
I installed arise and lost all audio on device . I don't know if it's a setting or something in aroma I should not have added or if it's viper settings I messed with .
I need to uninstall this how do I
Or how do I get sound back this is weird
Click to expand...
Click to collapse
Sorry about this... You may have to back up your internal then flash back to stock. This guide was from when our device was still on nougat. For Oreo I need you to install the module from MAGISK or find the magnum opus zip
"Can't load Android system" and "Factory data reset" tried and does not work
Hi all,
I bought a Pixel 3a, unlocked the bootloader, upgraded it to Android 10, and then tried to root it with Magisk. I must somehow have missed a step because now the phone only boots to:
Android Recovery
google/sargo/sargo
9/PQ3B.190801.002/5674421
user/release-keys
Use volume up/down and power.
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
Try again
Factory data reset
If I "Try again" I end up in the same place after a long time with the Google logo and a reboot. If I "Factory data reset" I also end up in the same place.
My desktop has adb and fastboot, and was able to access the phone until the failed attempt at rooting. Now it does not detect the phone despite the system "bleeping" as if it has found a new device:
>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
>adb devices
List of devices attached
Is there a way out of this mess?
FD
You're still on P by what recovery says. 0801 image. PQ3B is P. You want QP1A. Please try downloading the recent Q image and follow the official instructions from Google in the link and try again.
https://developers.google.com/android/images
Uzephi said:
You're still on P by what recovery says. 0801 image. PQ3B is P. You want QP1A. Please try downloading the recent Q image and follow the official instructions from Google in the link and try again.
https://developers.google.com/android/images
Click to expand...
Click to collapse
Thank you very much! Using the flash-all script I have managed to get my phone back. I have flashed the original Android 9 the phone came with.
Now, one further question, are there some good (as in unlikely to brick my phone again) instructions on how to root my Pixel 3a? I believe that Android 9 is preferred when using Magisk to Android 10, and I do not mind staying with Android 9, but I would like some instructions on how to root it without bricking it again.
Again, thanks for your prompt reply.
Yours,
FD
Frederick Davies said:
Thank you very much! Using the flash-all script I have managed to get my phone back. I have flashed the original Android 9 the phone came with.
Now, one further question, are there some good (as in unlikely to brick my phone again) instructions on how to root my Pixel 3a? I believe that Android 9 is preferred when using Magisk to Android 10, and I do not mind staying with Android 9, but I would like some instructions on how to root it without bricking it again.
Again, thanks for your prompt reply.
Yours,
FD
Click to expand...
Click to collapse
I followed this guide. it's for a pixel 3 but it's exactly the same for a 3a. There is no TWRP for 10 so doing it this way is the only way for now.
https://android.gadgethacks.com/how-to/root-your-pixel-3-android-10-0200295/
Just use magisk to patch Android 10 boot IMG and Flash it and your rooted on Android 10
Frederick Davies said:
Now, one further question, are there some good (as in unlikely to brick my phone again) instructions on how to root my Pixel 3a? I believe that Android 9 is preferred when using Magisk to Android 10, and I do not mind staying with Android 9, but I would like some instructions on how to root it without bricking it again.
Again, thanks for your prompt reply.
Yours,
FD
Click to expand...
Click to collapse
I have created a (IMHO) very thorough quide on how to root your Pixel 3a. It walks you through rooting with both Android Pie and Android 10 with very clear and precise steps. If you have any questions about it, feel free to post in that thread or reach out to me via a direct message.
There is no limitation on using Magisk or rooting under Android 10. The only thing you cannot do with Android 10 is use TWRP, but that isn't a deal breaker. TWRP is good for making backups of your OS, but as you have found you can still recover from just about any situation using the Google factory images, so while a backup might be beneficial at times, it isn't a necessity. Personally I would definitely recommend using Android 10 because Pie isn't being updated by Google anymore, so you are going to be behind on security updates, etc if you stick with Pie.
Watch this video and you shouldn't have any problems
sic0048 said:
I have created a (IMHO) very thorough quide on how to root your Pixel 3a. It walks you through rooting with both Android Pie and Android 10 with very clear and precise steps. If you have any questions about it, feel free to post in that thread or reach out to me via a direct message.
Click to expand...
Click to collapse
Very detailed indeed, but I still have a question: in your instructions you seem to boot into TWRP to install Magisk, but you do NOT install TWRP itself, just boot it for the installation of Magisk. Is that correct? Why?
sic0048 said:
There is no limitation on using Magisk or rooting under Android 10. The only thing you cannot do with Android 10 is use TWRP, but that isn't a deal breaker. TWRP is good for making backups of your OS, but as you have found you can still recover from just about any situation using the Google factory images, so while a backup might be beneficial at times, it isn't a necessity. Personally I would definitely recommend using Android 10 because Pie isn't being updated by Google anymore, so you are going to be behind on security updates, etc if you stick with Pie.
Click to expand...
Click to collapse
I am going through all this rigmarole to be able to install XPrivacyLua through the Xposed Framework, but the instructions for Xposed (https://www.xda-developers.com/xposed-framework-hub/) seem to indicate you need TWRP as a requisite, hence I think am stuck with Android P (9.0).
On the other hand, I get conflicting information as to whether Xposed for Magisk does (https://www.xda-developers.com/xposed-framework-hub/) or does not (https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268) pass SafetyNet. Most confusing...
FD
Frederick Davies said:
Very detailed indeed, but I still have a question: in your instructions you seem to boot into TWRP to install Magisk, but you do NOT install TWRP itself, just boot it for the installation of Magisk. Is that correct? Why?
FD
Click to expand...
Click to collapse
There is no need to install or boot into TWRP (btw. there is even no working TWRP for Android 10 yet) to install Magisk. It's sufficents to install Magisk Manager on your phone and patch the boot.img extracted from the factory image. Just follow the instructions which have been quoted here in the thread already.
AndDiSa said:
There is no need to install or boot into TWRP (btw. there is even no working TWRP for Android 10 yet) to install Magisk. It's sufficents to install Magisk Manager on your phone and patch the boot.img extracted from the factory image. Just follow the instructions which have been quoted here in the thread already.
Click to expand...
Click to collapse
Dear AndDisa,
As I said, I am rooting my Pixel 3a because I want to install XPrivacyLua, which requires the Xposed Framework; and to install Xposed with Magisk, it lists TWRP as a pre-requisite (see "Method 2: Magisk" in https://www.xda-developers.com/xposed-framework-hub/). Since it seems there is some kind of reluctance to use/install TWRP in this thread, I am asking why that is so. I understand it is possible to install Magisk without TWRP, I am just asking "why?"
Again, thank you all for your help.
FD
TWRP doesn't work on Android 10 at this point so you can't flash it.
Frederick Davies said:
Dear AndDisa,
As I said, I am rooting my Pixel 3a because I want to install XPrivacyLua, which requires the Xposed Framework; and to install Xposed with Magisk, it lists TWRP as a pre-requisite (see "Method 2: Magisk" in https://www.xda-developers.com/xposed-framework-hub/). Since it seems there is some kind of reluctance to use/install TWRP in this thread, I am asking why that is so. I understand it is possible to install Magisk without TWRP, I am just asking "why?"
Again, thank you all for your help.
FD
Click to expand...
Click to collapse
If you read closely in the guide sic linked, he does state the TWRP method is only for P because you can't use TWRP on 10. It is the way partitions are handled in 10 where you really can't read your internal storage and it would have to require a code rework. Until that's done, no TWRP.
Edit: quote from twrp developer about it. https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
https://github.com/ElderDrivers/EdXposed/pull/354
https://github.com/ElderDrivers/EdXposedManager/releases
You can flash xposed without TWRP. Just install edxposed by downloading and installing through magisk and install the edxposed manager. You don't need TWRP
Frederick Davies said:
Very detailed indeed, but I still have a question: in your instructions you seem to boot into TWRP to install Magisk, but you do NOT install TWRP itself, just boot it for the installation of Magisk. Is that correct? Why?
FD
Click to expand...
Click to collapse
As other have noted, TWRP does not work with Android 10. However, I also wanted to answer your question because it is valid.....
With Android Pie (9), you cannot permanently install TWRP unless you first flash a custom kernel that supports LZMA compression. Using the stock kernel, you can load TWRP using ADB and use it just like normal, but when you reboot the phone TWRP will not be loaded anymore. My instructions are about rooting the phone and not about installing TWRP permanently on the phone and therefore I provided the simplest method to accomplish that goal.
Most custom kernels have been updated with LZMA support, but you should really read the TWRP thread for more information on how to permanently install TWRP on Android Pie
Dear All,
Thank you for all your help and explanations concerning my questions.
I have now rooted my Pixel 3a running Android 9 following the instructions supplied (no TWRP installation), and It seems that Magisk is installed and happy (at least it thinks it is and FX has root access), but I am afraid that EdXposed and XPrivacyLua are not working as expected.
After Magisk, I installed the "Riru - Core" and "Riru - EdXposed (YAHFA)" modules. I then installed the "EdXposed Framework (YAHFA)" (giving the EdXposed Installer superuser privileges; EdExposed reports it is installed and active), and the XprivacyLua module inside it. But now Magisk complains that the SafetyNet checks are failing (this coincides with installing XPrivacyLua, but it is the only module I have in EdXposed), and XPrivacyLua is not actually blocking anything at all (that is, even when I supposedly block access to some functions, the apps just go ahead and use them).
Why do I get the impression Google does not want people to root their phones?
Yours,
FD
Frederick Davies said:
Dear All,
Thank you for all your help and explanations concerning my questions.
I have now rooted my Pixel 3a running Android 9 following the instructions supplied (no TWRP installation), and It seems that Magisk is installed and happy (at least it thinks it is and FX has root access), but I am afraid that EdXposed and XPrivacyLua are not working as expected.
After Magisk, I installed the "Riru - Core" and "Riru - EdXposed (YAHFA)" modules. I then installed the "EdXposed Framework (YAHFA)" (giving the EdXposed Installer superuser privileges; EdExposed reports it is installed and active), and the XprivacyLua module inside it. But now Magisk complains that the SafetyNet checks are failing (this coincides with installing XPrivacyLua, but it is the only module I have in EdXposed), and XPrivacyLua is not actually blocking anything at all (that is, even when I supposedly block access to some functions, the apps just go ahead and use them).
Why do I get the impression Google does not want people to root their phones?
Yours,
FD
Click to expand...
Click to collapse
It is most certainly the things you have installed that are breaking the SafetyNet check. I don't know anything about XprivacyLua, but I would assume there is a support thread here on XDA for it. I would read that support thread and see if there is a solution to the Safetynet issue.
Dear All,
OK, I have now rooted my Pixel 3a: I am running Android 9, and I flashed Magisk (Magisk Manager version 7.4.0; Magisk version 20.1) without installing TWRP as per the instructions. Then I installed the Riru - Core (version 10) and Riru - Ed Exposed (version 0.2.8_beta) modules, which allowed me to install EdXposedInstaller (version 2.2.5). I am currently running Xposed Framework (version 90.0-0.2.8) with XPrivacyLua (version 1.25).
The result is that XPrivacyLua is working with a few caveats: the SafetyNet Check fails both the ctsProfile and basicIntegrity checks (this is triggered by XPrivacyLua, not (Ed)Xposed), and when I limit access of WhatsApp to the Contacts list, there are constant errors whenever WhatsApp tries to read it (though it seems to work as expected). Also, the Contacts list keeps disappearing from the Contacts app itself, despite WhatsApp actually seeing those contacts in there (go figure).
Other apps that require root (like FX) are working as expected.
In the end, I have decided that since I am not interested in using my mobile for Google Pay, I will have to live with it as it is now, but I have a couple of points for others that may want to follow in my footsteps (this is not necessarily related to the method of rooting; those who helped me here are certainly not at fault for the following):
1. XPrivacyLua is in no way as capable and easy to use as XPrivacy was (XPrivacy is the main reason why I am rooting my phone). If I could install Android 4 on my Pixel 3a, I would do so and go back to XPrivacy (my venerable Nexus 5's second battery is shot, so I had to get new hardware). There is nothing in Android 9 that I actually need that was not there in Android 4.
2. We really need a Nexus Toot Toolkit for Pixel phones. The multitude of versions and steps required in rooting them successfully is too much for those like me who will root their phone for one or two apps and then leave it as it is. I know that these forums are really for tinkerers who want to extract the maximum from their hardware, and hence my point of view is not representative here, but I just want a mobile that will not spy on me, the rest is irrelevant to me.
I guess I will have to open a thread in the XPrivacyLua forums to see if I can sort out my problems, but I would like to thank you all for your help in getting me here and answering my questions (no matter how pointless they may have seemed).
Yours,
FD
Frederick Davies said:
Dear All,
OK, I have now rooted my Pixel 3a: I am running Android 9, and I flashed Magisk (Magisk Manager version 7.4.0; Magisk version 20.1) without installing TWRP as per the instructions. Then I installed the Riru - Core (version 10) and Riru - Ed Exposed (version 0.2.8_beta) modules, which allowed me to install EdXposedInstaller (version 2.2.5). I am currently running Xposed Framework (version 90.0-0.2.8) with XPrivacyLua (version 1.25).
The result is that XPrivacyLua is working with a few caveats: the SafetyNet Check fails both the ctsProfile and basicIntegrity checks (this is triggered by XPrivacyLua, not (Ed)Xposed), and when I limit access of WhatsApp to the Contacts list, there are constant errors whenever WhatsApp tries to read it (though it seems to work as expected). Also, the Contacts list keeps disappearing from the Contacts app itself, despite WhatsApp actually seeing those contacts in there (go figure).
Other apps that require root (like FX) are working as expected.
In the end, I have decided that since I am not interested in using my mobile for Google Pay, I will have to live with it as it is now, but I have a couple of points for others that may want to follow in my footsteps (this is not necessarily related to the method of rooting; those who helped me here are certainly not at fault for the following):
1. XPrivacyLua is in no way as capable and easy to use as XPrivacy was (XPrivacy is the main reason why I am rooting my phone). If I could install Android 4 on my Pixel 3a, I would do so and go back to XPrivacy (my venerable Nexus 5's second battery is shot, so I had to get new hardware). There is nothing in Android 9 that I actually need that was not there in Android 4.
2. We really need a Nexus Toot Toolkit for Pixel phones. The multitude of versions and steps required in rooting them successfully is too much for those like me who will root their phone for one or two apps and then leave it as it is. I know that these forums are really for tinkerers who want to extract the maximum from their hardware, and hence my point of view is not representative here, but I just want a mobile that will not spy on me, the rest is irrelevant to me.
I guess I will have to open a thread in the XPrivacyLua forums to see if I can sort out my problems, but I would like to thank you all for your help in getting me here and answering my questions (no matter how pointless they may have seemed).
Yours,
FD
Click to expand...
Click to collapse
Cool story bro
Hi,
with pleasure I share the module for right clock in the status bar, the module is created by @Tulsadiver, tested by me on Oneplus 7 with firmware version as specified file name.
ESSENTIAL PREREQUISITE: BEFORE INSTALLING THE MOD, IT IS NECESSARY TO INSTALL, IF NOT PRESENT, THE "OVERLAY MOUNT FIX" MODULE BY @Zackptg5 DOWNLOADABLE FROM MAGISK MANAGER, WITHOUT THIS THE CLOCK MODULE WILL NOT WORK!
It is a magisk module and I want to repeat that it can only be used on Oneplus 7.
The module can only be used with the firmware release indicated in the file name, it will be my commitment to update the thread with the release of future updates.
I'm trying it and it doesn't seem to show any problems but I still recommend making a backup before trying it.
To remove the mod, simply uninstall the module using magisk manager or, if this is not usable, from recovery twrp, using the file manager deleting the module "OP7_VrThemer_OPSystemUI" that you find at the following path:
/data/adb/modules
My biggest, massive, THANKS go to @Tulsadiver, for sending me his xml file with the modifications necessary to obtain the movement of the clock and for passing me Its VRThemer module, without your help I could not have avoided the bootloop ... I can say that the mod is all from @Tulsadiver, the mod is all the result of his work and his expertise, I have only been a tester and shared his fantastic work with you.
Thanks also to @dladz, for giving me his support and advice!
Attention each module you find in this post is specific to the firmware indicated in the file name, with each new firmware it will be my concern to release the new updated module.
Flashing always at your own risk!!!
To be installed only with Magisk Manager, if installed by TWRP it does not work.
Please read all indications before proceeding with the installation, module has been tested and is working on the latest OxygenOS OpenBeta 18 Android 10 based firmware, NOT tested with other firmware and non-OxygenOS based roms.
P.S. To complete the information, I have not had the opportunity to try the same module with other firmware versions, it could work but I have no way of knowing, if you decide to try remember that it should only be used on Oneplus 7, only with Android 10 and that you do at your own risk, I have tested it and use it with latest Openbeta 18 firmware without any problem.
Update OxygenOS Open Beta 19: The module for open Beta 18 can also be used with Open Beta 19 firmware, I will always update you on any compatibility of old versions of the mod with new firmware released, in case there is no compatibility, I will release the updated module.
Nice. :good:
I confirm that the OPSystemUI.apk file has not changed compared to version Beta 18 (same md5 as the modified .xml file) for this reason the module created for the Open Beta 18 firmware version can be used without problems even with the new Open Beta 19
Thread closed on request of OP @dianoandr as the OP doesn't possess the device any longer!
I should be getting the device in a few days and want to install EdXposed ASAP. I have found a few references of folks who did this but it's not clear whether it's on Android 11 or not.
If any one has been able to install EdXposed and get it running, it would be great if they can share the links to the framework and manager they used. And of course, their experience and tips
This would help the community of Pixel 4a users
Here is how I got it working
Obviously you have a rooted device running Android 11, with Magisk installed.
Install EdXposed Manager v4.5.7.
From the canary tab download the YAHFA/ Sandhook drivers (zip) . Note that downloaded version may have a different name from the file name in canary tab, in my case
Which one did you flash? Yahfa or Sandhook?
Neither one of those show up for me. I tried flashing framework and it says incompatible device.
Okluzhion said:
Which one did you flash? Yahfa or Sandhook?
Click to expand...
Click to collapse
Sorry for the delay. I didn't get the notification
YAHFA. But note that when I flashed, every thing was fine. In between, probably some Play Store updates broke camera and recorder. Uninstalling updates fixed the problem