Related
Hi y'all, first off I have the G920P, just recently upgraded to Nougat QC7 stock ROM, modified and running the SkyHigh kernel v5.01 with Magisk v12. Everything runs pretty smooth, even got Liveboot working successfully (there's a reason I mention Liveboot.) Now I decided to try to get Viper4Android to work. Of course, installing the standard apk fails when it comes to installing the driver. So I tried the V4A Magisk module and it installed fine, however on reboot, my Liveboot no longer works and when opening the V4A app it asks to install the driver, I hit yes and it says it successfully installed and to please reboot. I reboot and of course Liveboot still doesn't show, but otherwise it boots fine. Once I re-open the V4A app it is asking me to install the driver yet again, and the whole system at times seems a bit unstable until I disable the V4A module in Magisk Manager. Does anyone have any ideas, or has anyone gotten this to successfully work? If so I'd love a suggestion lol. I really would like to keep my Liveboot working, but I'd kinda like to get Viper working too. Thanks in advance for any help, suggestions, ideas, etc.
Chuck
I could not get the V4A module to install under Magisk 12; however, it works just fine with Magisk 13.
This is the version that I used: https://www.androidfilehost.com/?fid=745425885120735287
Magisk Uninstaller (should not be needed, but if you want it) is here: https://www.androidfilehost.com/?fid=745425885120735289
NOTE: You are, I believe using the @tdhite kernel, which is based in Magisk 12. Not sure what the impact of installing Magisk 13 will be.
The kernel is fine with Magisk v13 (beta, to be sure is all that is released there). Magisk v13 beta still has problems, so beware. The SkyHigh kernel and module are v13 compatible as much as v12, just so you know. The reason v12 is packaged in is v12 is the only stable Magisk version at this point.
The bigger issue is Magisk v13 beta working stably and reliably, but if you are willing to debug its failures, it's ok. There should be no need to uninstall to upgrade if you want to play. Reloading the kernel flash will cleanly load up v12 if all goes badly.
Sent from my iPad using Tapatalk
@koop1955 Thank you for that information! I will bookmark those so I can get back to them once v13 is reliable and stable enough for my kernel
@tdhite Thanks bud as Well! I think I will just stay where I am until the kernel and v13 play nicely. Just got this thing as perfect as I can for now, well other than ram use creeping up, but that's only every now and then, and for another topic. I *might* get my nandroid current and play a little if I get bored and want to tinker. I guess I can safely assume then the reason Liveboot stops working with the V4A module installed is because of Magisk v12...?
Thank you to both of you guys for the help and advice. At least now I know it's not some dumb issue with my device lol.
Chuck
@digitalchaos1980 and @tdhite, I have had a good experience with one particular version of Magisk 13, which is why I added it to my AFH. Other and newer versions...not so much. To be expected with a work in progress.
At some point, Magisk 13 will be final and we can move forward.
koop1955 said:
@digitalchaos1980 and @tdhite, I have had a good experience with one particular version of Magisk 13, which is why I added it to my AFH. Other and newer versions...not so much. To be expected with a work in progress.
At some point, Magisk 13 will be final and we can move forward.
Click to expand...
Click to collapse
No doubt! Version 13 gives me something to look forward to for sure
Chuck
digitalchaos1980 said:
Hi y'all, first off I have the G920P, just recently upgraded to Nougat QC7 stock ROM, modified and running the SkyHigh kernel v5.01 with Magisk v12. Everything runs pretty smooth, even got Liveboot working successfully (there's a reason I mention Liveboot.) Now I decided to try to get Viper4Android to work. Of course, installing the standard apk fails when it comes to installing the driver. So I tried the V4A Magisk module and it installed fine, however on reboot, my Liveboot no longer works and when opening the V4A app it asks to install the driver, I hit yes and it says it successfully installed and to please reboot. I reboot and of course Liveboot still doesn't show, but otherwise it boots fine. Once I re-open the V4A app it is asking me to install the driver yet again, and the whole system at times seems a bit unstable until I disable the V4A module in Magisk Manager. Does anyone have any ideas, or has anyone gotten this to successfully work? If so I'd love a suggestion lol. I really would like to keep my Liveboot working, but I'd kinda like to get Viper working too. Thanks in advance for any help, suggestions, ideas, etc.
Chuck
Click to expand...
Click to collapse
if you kindly Tell me the process how did you end up using Live boot in magisk , It would be very helpful . I have tried various method but failed
Saafir said:
Place a copy of audio effects.conf in vendor/etc. Should get you working. Be sure to set permissions as well.
Click to expand...
Click to collapse
Just to be sure, folks realize there is full equalizer support in my SkyHigh kernel and the bands are all adjustable, even per channel if desired, in Synapse, right? Just noting in case that's all you need, because it is a no-CPU-load way of getting it done.
Sent from my iPad using Tapatalk
Disclaimer: I am not a developer (I don't code), but I have been flashing ROMs for many devices over the years. This is more of a practical guide from an end-user perspective in pursuit of finding the best ROM for this magnificent hardware. This is more of a compilation of all the relevant information I found. I'm very open to suggestions/corrections that could improve this.
Disclaimer: Only tested with RR, PixelExperience, and ArrowOS GSI.
I haven't seen a proper guide to flash GSI ROMs for Mi Mix 3, thus I decided to share what I know that works. I put a brief explanation for each step below.
1. Unlock Bootloader - If you haven't done so yet, I recommend following the instructions in https://www.reddit.com/r/Xiaomi/wiki/bootloader
2. Install TWRP
a) I recommend to use the official TWRP from this link https://twrp.me/xiaomi/xiaomimix3.html or refer to the forum https://forum.xda-developers.com/mi-mix-3/development/recovery-unofficial-twrp-recovery-t3901261.
b) To install TWRP, I recommend to follow the instructions from Xiaomi.eu. For those not familiar, the "twrp.img" in the code should be the full path of the file. Something like "D:\folder\twrp.img"
c) If you have an older version of TWRP, I suggest to update it to the official.
3. Install Xiaomi.eu - Start from this step in case of bootloops or issues (especially caused by Magisk modules by my experience)
a) This is what I do instead of the 'flash vendor.img from Chinese Dev' prerequisite mentioned in other threads. This is an easier step (just one flash in TWRP) and a better fallback (a working ROM) in case things go wrong. I have had no issues (fingerprint, calls, etc..) with this and I've done this thrice.
b) Download the latest MIUIv10.2 Stable for MIMix3 from the link https://xiaomi.eu/community/threads/miui-10-0-10-1-10-2-stable-release.47170/.
c) Wipe > Format Data (prevents problems, and removes encryption if you had it). Also do Factory Reset (idk, just to be sure).
d) Copy xiaomi.eu ROM to internal storage, then Install > Flash. No need to boot/restart, proceed to the next step.
4. Install GSI ROM - wth is GSI? https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-(FAQ)
a) We can actually install any GSI in https://forum.xda-developers.com/project-treble/trebleenabled-device-development but there is an issue in installing Google Apps (Open GApps) as many people mentioned in https://forum.xda-developers.com/mi-mix-3/development/9-0-resurrection-remix-v7-0-t3891975 and as confirmed by the official TWRP thread https://forum.xda-developers.com/mi...p-recovery-t3901261/post79035909#post79035909
b) Given the above, the only feasible options are GSI ROMs with built-in GApps and the only 2 I found are PixelExperience GSI and ArrowOS GSI. As GApps is integrated in the system.img, no need to flash Open GApps thus no issues. Having tried both, I personally recommend ArrowOS due to the performance and additional customization options.
c) Download the arm64 AB version (ArrowOS as an example) https://forum.xda-developers.com/pr...abled-device-development/gsi-arrowos-t3835111
d) Copy the resulting system.img to internal storage (extract if its a .zip), in TWRP click Install > Install Images > select system.img of ArrowOS > select System partition. You can now boot, or follow next step to root with Magisk.
5. Install Magisk
a) The Magisk version that passes SafetyNet is the builds from ianmacd https://github.com/ianmacd/MagiskBuilds look for v18.2 (newer versions might work but I haven't tried them yet). You can still use the official Magisk Manager and the ianmacd version will be recognized. Just change the update channel in Magisk to https://goo.gl/yZpnrf. Credits to this thread https://forum.xda-developers.com/mi-mix-3/how-to/root-magisk-18-2-mix-3-t3905754
b) After flashing Magisk, boot, install Magisk Manager, then download and install the module "SafetyPatch". SafetyNet check will now be success.
c) Even though SafetyNet is passed, some banking apps still are not working. Hopefully someone can share a solution (probably MagiskHide Props Config, or canary builds?) to make banking apps work.
Final Thoughts
ArrowOS GSI seems to be stable enough and I'm using it as my daily driver now. I am so much happier compared to when using MIUI Global ROM. I really like the performance (very fluid), battery life (a lot better than MIUI Global), customizations (like traffic indicator, status bar stuff), unli Google Photos, and everything that makes AOSP/stock android awesome. No more bloatware, annoying non-dismissable notifications, and horrible auto brightness from MIUI.
The only real issue I encountered so far is the bluetooth audio/music issue, but this seems to be a common problem in GSI ROMs. Bluetooth calls work though. There is no app to handle the slider (but I don't care. lol). Lastly, the AI button becomes useless, but see below for the fix.
Optional stuff that makes things better:
1. Remapping AI button - When using GSI ROMs, AI button becomes useless. But to map it back to Google Assistant (or anything actually), follow the instructions from this thread (needs some knowledge about Tasker). https://forum.xda-developers.com/showpost.php?p=78523778&postcount=38 For the Tasker Task, I selected Input > Voice Command. This now assigns the button to open Google Assistant. Does not work well when screen is off though, but its just easy to unlock.
2. Google Camera - The main reason why I bought this phone. Google Camera brings out the best in the awesome camera - Use this version https://forum.xda-developers.com/mi-mix-3/themes/gcam-6-manual-focus-long-exposure-t3885610
3. Stereo Speaker Mod - https://forum.xda-developers.com/mi-mix-3/themes/magisk-stereo-speaker-mod-mix-3-t3900580 Makes the phone earpiece into a speaker, increasing overall volume. I personally use version 3 and I'm very happy.
4. Fluid NG - App in Google Play Store to have the same recents/home/back gestures from MIUI 10.
reasonablebasis said:
Disclaimer: I am not a developer (I don't code), but I have been flashing ROMs for many devices over the years. This is more of a practical guide from an end-user perspective in pursuit of finding the best ROM for this magnificent hardware. This is more of a compilation of all the relevant information I found. I'm very open to suggestions/corrections that could improve this
I haven't seen a proper guide to flash GSI ROMs for Mi Mix 3, thus I decided to share what I know that works. I put a brief explanation for each step below.
1. Unlock Bootloader - If you haven't done so yet, I recommend following the instructions in https://www.reddit.com/r/Xiaomi/wiki/bootloader
2. Install TWRP
a) I recommend to use the official TWRP from this link https://twrp.me/xiaomi/xiaomimix3.html or refer to the forum https://forum.xda-developers.com/mi-mix-3/development/recovery-unofficial-twrp-recovery-t3901261.
b) To install TWRP, I recommend to follow the instructions from Xiaomi.eu. For those not familiar, the "twrp.img" in the code should be the full path of the file. Something like "D:\folder\twrp.img"
c) If you have an older version of TWRP, I suggest to update it to the official.
3. Install Xiaomi.eu - Start from this step in case of bootloops or issues (especially caused by Magisk modules by my experience)
a) This is what I do instead of the 'flash vendor.img from Chinese Dev' prerequisite mentioned in other threads. This is an easier step (just one flash in TWRP) and a better fallback (a working ROM) in case things go wrong. I have had no issues (fingerprint, calls, etc..) with this and I've done this thrice.
b) Download the latest MIUIv10.2 Stable for MIMix3 from the link https://xiaomi.eu/community/threads/miui-10-0-10-1-10-2-stable-release.47170/.
c) Wipe > Format Data (prevents problems, and removes encryption if you had it). Also do Factory Reset (idk, just to be sure).
d) Copy xiaomi.eu ROM to internal storage, then Install > Flash. No need to boot/restart, proceed to the next step.
4. Install GSI ROM - wth is GSI? https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-(FAQ)
a) We can actually install any GSI in https://forum.xda-developers.com/project-treble/trebleenabled-device-development but there is an issue in installing Google Apps (Open GApps) as many people mentioned in https://forum.xda-developers.com/mi-mix-3/development/9-0-resurrection-remix-v7-0-t3891975 and as confirmed by the official TWRP thread https://forum.xda-developers.com/mi...p-recovery-t3901261/post79035909#post79035909
b) Given the above, the only feasible options are GSI ROMs with built-in GApps and the only 2 I found are PixelExperience GSI and ArrowOS GSI. As GApps is integrated in the system.img, no need to flash Open GApps thus no issues. Having tried both, I personally recommend ArrowOS due to the performance and additional customization options.
c) Download the arm64 AB version (ArrowOS as an example) https://forum.xda-developers.com/pr...abled-device-development/gsi-arrowos-t3835111
d) Copy the resulting system.img to internal storage (extract if its a .zip), in TWRP click Install > Install Images > select system.img of ArrowOS > select System partition. You can now boot, or follow next step to root with Magisk.
5. Install Magisk
a) The Magisk version that passes SafetyNet is the builds from ianmacd https://github.com/ianmacd/MagiskBuilds look for v18.2 (newer versions might work but I haven't tried them yet). You can still use the official Magisk Manager and the ianmacd version will be recognized. Just change the update channel in Magisk to https://goo.gl/yZpnrf. Credits to this thread https://forum.xda-developers.com/mi-mix-3/how-to/root-magisk-18-2-mix-3-t3905754
b) After flashing Magisk, boot, install Magisk Manager, then download and install the module "SafetyPatch". SafetyNet check will now be success.
c) Even though SafetyNet is passed, some banking apps still are not working. Hopefully someone can share a solution (probably MagiskHide Props Config, or canary builds?) to make banking apps work.
Final Thoughts
ArrowOS GSI seems to be stable enough and I'm using it as my daily driver now. I am so much happier compared to when using MIUI Global ROM. I really like the performance (very fluid), battery life (a lot better than MIUI Global), customizations (like traffic indicator, status bar stuff), unli Google Photos, and everything that makes AOSP/stock android awesome. No more bloatware, annoying non-dismissable notifications, and horrible auto brightness from MIUI.
The only real issue I encountered so far is the bluetooth audio/music issue, but this seems to be a common problem in GSI ROMs. Bluetooth calls work though. There is no app to handle the slider (but I don't care. lol). Lastly, the AI button becomes useless, but see below for the fix.
Optional stuff that makes things better:
1. Remapping AI button - When using GSI ROMs, AI button becomes useless. But to map it back to Google Assistant (or anything actually), follow the instructions from this thread (needs some knowledge about Tasker). https://forum.xda-developers.com/showpost.php?p=78523778&postcount=38 For the Tasker Task, I selected Input > Voice Command. This now assigns the button to open Google Assistant. Does not work well when screen is off though, but its just easy to unlock.
2. Google Camera - The main reason why I bought this phone. Google Camera brings out the best in the awesome camera - Use this version https://forum.xda-developers.com/mi-mix-3/themes/gcam-6-manual-focus-long-exposure-t3885610
3. Stereo Speaker Mod - https://forum.xda-developers.com/mi-mix-3/themes/magisk-stereo-speaker-mod-mix-3-t3900580 Makes the phone earpiece into a speaker, increasing overall volume. I personally use version 3 and I'm very happy.
Click to expand...
Click to collapse
Not all GSI work ontop of Xiaomi Eu
Flashing magisk and safety net patch also doesn't guarantee safety net passing on a few of the GSI as well. CTS will fail for obvious reasons
Mackay53 said:
Not all GSI work ontop of Xiaomi Eu
Flashing magisk and safety net patch also doesn't guarantee safety net passing on a few of the GSI as well.
Click to expand...
Click to collapse
Noted. Which GSI have you tried that do not work on top of Xiaomi.EU? I tried RR, PixelExperience, and ArrowOS and all work well. I can put this as a disclaimer.
Any solution for the Magisk safetynet, or is this really the best solution available so far?
reasonablebasis said:
Noted. Which GSI have you tried that do not work on top of Xiaomi.EU? I tried RR, PixelExperience, and ArrowOS and all work well. I can put this as a disclaimer.
Any solution for the Magisk safetynet, or is this really the best solution available so far?
Click to expand...
Click to collapse
Can't remember as it was a while ago, possibly OctoOS and descendant and 1 other, omni ROM maybe.
For the ones that come with SU you need to navigate to the xbin folder in the system and remove the SU file.
Then cause Xiaomi EU uses the wrong fingerprint props you need to use the magisk props config module and manually type in the mix 3 fingerprint (unless the module has been updated to include mix 3).
If you installed the Chinese dev vendor then the props will be there ready to be used so the magisk module can make them active without manually typing it. This will sort out both safety net fails.
If this was sometime ago, the features in China Dev would have already been integrated in the latest China Stable, which is the basis of Xiaomi.EU.
Maybe you can test it now to see if Xiaomi.EU really works. I tried it with RR, PixelExperience, and ArrowOS and I'm facing no issues. So flashing China Dev vendor.img seems to be an outdated instruction.
reasonablebasis said:
Noted. Which GSI have you tried that do not work on top of Xiaomi.EU? I tried RR, PixelExperience, and ArrowOS and all work well. I can put this as a disclaimer.
Any solution for the Magisk safetynet, or is this really the best solution available so far?
Click to expand...
Click to collapse
Pixel dust gsi too....
reasonablebasis said:
If this was sometime ago, the features in China Dev would have already been integrated in the latest China Stable, which is the basis of Xiaomi.EU.
Maybe you can test it now to see if Xiaomi.EU really works. I tried it with RR, PixelExperience, and ArrowOS and I'm facing no issues. So flashing China Dev vendor.img seems to be an outdated instruction.
Click to expand...
Click to collapse
The 3 GSI you mention is a very small sample of the GSI available so you can't say it's an outdated instruction. Have you tested them all like I have? No you haven't.
Xiaomi EU does not use the correct mix3 vendor.img, that's what causes the issue.
Mackay53 said:
The 3 GSI you mention is a very small sample of the GSI available so you can't say it's an outdated instruction. Have you tested them all like I have? No you haven't.
Xiaomi EU does not use the correct mix3 vendor.img, that's what causes the issue.
Click to expand...
Click to collapse
Ok, I'll put a disclaimer that this only works on RR, PixelExperience, and ArrowOS. Anyway, I'm sure that the latest stable Xiaomi.EU vendor works without any issues with ArrowOS, else why would I be using it as my daily driver.
[deleted, duplicate post]
Someone know if there is a GSI with gapps and that don't have issue with bluetooth?
SafetyPatch module
reasonablebasis said:
5. Install Magisk
a) The Magisk version that passes SafetyNet is the builds from ianmacd https://github.com/ianmacd/MagiskBuilds look for v18.2 (newer versions might work but I haven't tried them yet). You can still use the official Magisk Manager and the ianmacd version will be recognized. Just change the update channel in Magisk to https://goo.gl/yZpnrf. Credits to this thread https://forum.xda-developers.com/mi-...mix-3-t3905754
b) After flashing Magisk, boot, install Magisk Manager, then download and install the module "SafetyPatch". SafetyNet check will now be success.
c) Even though SafetyNet is passed, some banking apps still are not working. Hopefully someone can share a solution (probably MagiskHide Props Config, or canary builds?) to make banking apps work.
Click to expand...
Click to collapse
Mate, I can't find this module via Magisk Manager... Please help!
jonny908 said:
Mate, I can't find this module via Magisk Manager... Please help!
Click to expand...
Click to collapse
You sure? Try searching for "SafetyPatch"
reasonablebasis said:
You sure? Try searching for "SafetyPatch"
Click to expand...
Click to collapse
Strange....
reasonablebasis said:
You sure? Try searching for "SafetyPatch"
Click to expand...
Click to collapse
Issue resolved. I had to use Magisk Manager 7.x.x, I was trying using 6.0.
Installed, MagiskHide working as it should now.
---------- Post added at 18:23 ---------- Previous post was at 18:15 ----------
@reasonablebasis
Sorry for third post in a row., but.... I have no issues with bluetooth audio/music that everyone is talking about. Listening to Spotify on my QCY bluetooth earphones now.....
jonny908 said:
Issue resolved. I had to use Magisk Manager 7.x.x, I was trying using 6.0.
Installed, MagiskHide working as it should now.
---------- Post added at 18:23 ---------- Previous post was at 18:15 ----------
@reasonablebasis
Sorry for third post in a row., but.... I have no issues with bluetooth audio/music that everyone is talking about. Listening to Spotify on my QCY bluetooth earphones now.....
Click to expand...
Click to collapse
On Arrow ?
Wahoux said:
On Arrow ?
Click to expand...
Click to collapse
Yep! Not sure how to prove that though xD
Android Q GSI !
https://www.xda-developers.com/android-q-gsi-project-treble/
Wahoux said:
Android Q GSI !
https://www.xda-developers.com/android-q-gsi-project-treble/
Click to expand...
Click to collapse
Dare to try? xD
jonny908 said:
Dare to try? xD
Click to expand...
Click to collapse
ahah no xD
Right now i'm about to flash Arrow, I hope I won't have bluetooth issue . On the non-GSI Pixel Experience, some reported issue with bluetooth whereas it was working fine for me... so let's see :fingers-crossed:
jonny908 said:
Mate, I can't find this module via Magisk Manager... Please help!
Click to expand...
Click to collapse
jonny908 said:
Issue resolved. I had to use Magisk Manager 7.x.x, I was trying using 6.0.
Installed, MagiskHide working as it should now.
---------- Post added at 18:23 ---------- Previous post was at 18:15 ----------
@reasonablebasis
Sorry for third post in a row., but.... I have no issues with bluetooth audio/music that everyone is talking about. Listening to Spotify on my QCY bluetooth earphones now.....
Click to expand...
Click to collapse
Wow good for you. You flashed xiaomi.eu prior to GSI right? enumerate the steps you did, so that we we hopefully can replicate your success. Hehe
XPOSED and Safety Net PASS -- Instructions How To
I've been using Xposed because it has functionality that I don't want to give up. But "regular" Xposed won't pass Safety Net.
Thanks to @drewcu, I now have found a way to use Xposed and PASS Safety Net.
This is important enough it deserves its own Guide thread. All credit goes to @drewcu -- and of course the edXposed devs! Go here and THANK this post. Full exchange is below, but please go thank @drewcu in that post.
_______
drewcu said:
Installed Magisk and edXposed and all is well.
Thanks!
Click to expand...
Click to collapse
ChazzMatt said:
First hearing about "edXposed". Quick Google search, sounds interesting, and some say it allows you to pass Safety Net, which regular Xposed (I use) doesn't. Is that true?
Which Magisk version are you installing with that?
Click to expand...
Click to collapse
drewcu said:
Latest Magisk 19.3.
YES, EdXposed absolutely passes Safetynet (both ctsProfile and basicIntegrity)! Install instructions here: https://github.com/ElderDrivers/EdXposed but see below for the specific EdXposed version I recommend using.
I personally use magisk-EdXposed-sandhook-v0.4.0.1_beta-SNAPSHOT-release.zip found https://www.lanzous.com/b642738. Newer Sandhook versions with resource hooking like v0.4.1.2_beta and v0.4.2.3_alpha (and the YAHFA versions too) found https://github.com/ElderDrivers/EdXposed/releases introduce some LAG for me that isn't present on 0.4.0.1. Haven't tried newer ALPHA versions like 0.4.3.7 but you are welcome to see if you experience the same lag. Would have to separately install both versions, start opening apps, clicking around, and counting time till the V30 responds to see the lag I am referring to. Is subtle but most noticeable in 0.4.1.2 and less so in 0.4.2.3.
The only Xposed module I use is GravityBox(O) and there is a version specifically for EdXposed -- 8.5.3.1-edxposed (https://github.com/GravityBox/GravityBox/releases/tag/v8.5.3.1-edxposed_o), although I updated to general version 8.5.4 (https://forum.xda-developers.com/xposed/modules/app-gravitybox-v8-0-0-beta-1-tweak-box-t3739929) and have no resource hooking problems with 0.4.0.1 like I thought there might be and had with general version 8.5.3. If you use any OTHER Xposed modules that require resource hooking, you will need to use an EdXposed version 0.4.1.2 or above which has resource hooking but also possibly some lag (perhaps none in the latest alpha I don't know).
So I stay on magisk-EdXposed-sandhook-v0.4.0.1_beta-SNAPSHOT-release because it works with the latest version of GravityBox no problem, has 0 lag unlike newer versions (I think an Oreo problem), and passes Safetynet just fine.
Not sure if some of the steps I took after reading a forum about Safetynet were necessary but I did them anyway -- namely:
1) EdXP Settings - Enable Black/White List
2) Black List Google Play Services and Google Play Store
3) Magisk Hide - ALL of Google Play Services
Enjoy!
Click to expand...
Click to collapse
TotallyAnxious said:
Thanks. I've been meaning to check out the new Xposed offshoots.
Click to expand...
Click to collapse
_________
@drewcu:
edXposed INSTRUCTIONS
Install instructions here: https://github.com/ElderDrivers/EdXposed but see below for the specific EdXposed version I recommend using.
I personally use magisk-EdXposed-sandhook-v0.4.0.1_beta-SNAPSHOT-release.zip found https://www.lanzous.com/b642738. Newer Sandhook versions with resource hooking like v0.4.1.2_beta and v0.4.2.3_alpha (and the YAHFA versions too) found https://github.com/ElderDrivers/EdXposed/releases introduce some LAG for me that isn't present on 0.4.0.1. Haven't tried newer ALPHA versions like 0.4.3.7 but you are welcome to see if you experience the same lag. Would have to separately install both versions, start opening apps, clicking around, and counting time till the V30 responds to see the lag I am referring to. Is subtle but most noticeable in 0.4.1.2 and less so in 0.4.2.3.
The only Xposed module I use is GravityBox(O) and there is a version specifically for EdXposed -- 8.5.3.1-edxposed (https://github.com/GravityBox/GravityBox/releases/tag/v8.5.3.1-edxposed_o), although I updated to general version 8.5.4 (https://forum.xda-developers.com/xposed/modules/app-gravitybox-v8-0-0-beta-1-tweak-box-t3739929) and have no resource hooking problems with 0.4.0.1 like I thought there might be and had with general version 8.5.3. If you use any OTHER Xposed modules that require resource hooking, you will need to use an EdXposed version 0.4.1.2 or above which has resource hooking but also possibly some lag (perhaps none in the latest alpha I don't know).
So I stay on magisk-EdXposed-sandhook-v0.4.0.1_beta-SNAPSHOT-release because it works with the latest version of GravityBox no problem, has 0 lag unlike newer versions (I think an Oreo problem), and passes Safetynet just fine.
Not sure if some of the steps I took after reading a forum about Safetynet were necessary but I did them anyway -- namely:
1) EdXP Settings - Enable Black/White List
2) Black List Google Play Services and Google Play Store
3) Magisk Hide - ALL of Google Play Services
Enjoy!
When I go to download the file, it's in, I assume, Chinese characters.
Any help.
Never mind, figured it out.
This is great. I'm so happy to have Gravity Box again.
I too had a problem with lag with newer versions of edxposed. I switched to the version recommend in the OP and all is well.
If you comfortable using "chinese" app. Taichi is simpler solution (personally), although not much modules currently supported. Both edxposed and taichi are available on magisk repo
Thanks @ChazzMatt, finally got around to installing Xposed again. Thank god for GravityBox!
edit: after playing around for a day, I'm disabling edx. I'm getting lag, force closes, unresponsive back button, and major battery drain. Sad to see the framework hasn't changed much in 1-2 years. It's not worth it for a single Xposed module.
Gravitybox system framework not respondinhlg.
On us996k
Guess I'm missing something?
qwas7899 said:
Gravitybox system framework not respondinhlg.
On us996k
Guess I'm missing something?
Click to expand...
Click to collapse
Edit; figured it out
qwas7899 said:
Edit; figured it out
Click to expand...
Click to collapse
share with the class.
Right. Didn't have riru-core module installed.
Thanks a lot for this guide . It's great to have xposed and safety net passing.
soo I tried to install edxposed sandhook (latest version), after a couple reboot, all went fine, but now I lost wifi and data connection (they cant be turned on), any ideas or fix? is it linked to that version of edxposed? I have a Lg ls998 converted to Us998h, thank you
LeTerrible said:
Just wanted to share my experience with NFC banking and FullHD working Netflix. Managed to delete everything google and installed Microg only (to get Gcam to work), my banking app, Netflix app, Canary EdXposed and it works flawlessly! Could never get FullHD and NFC banking to work previously with Xposed. Of note was the fact I am running Xprivacy, too. Just make sure you blacklist the apps in EdXposed and also hide them in Magisk and it all works
Hope this helps others as it really made my NoGapps/Rooted stock phone experiences significantly better.
Click to expand...
Click to collapse
Great.
I'm having trouble getting EdXposed to activate. I'm on a fresh clean install of the TWRP flashable version of US998 30b with Magisk 20.1 installed and working, and while i've got the Riru - Core module installed (v19.5), no matter which Riru - Ed Xposed module I use I get the following error message from EdXposed Manager 4.5.2 explaining why it's installed but not activated:
There seems to be a known issue("Wrong base directory: /mnt/expand/7f941a12-b7aa-4d2a-a664-f89a46b7d86c/user_de/0/org.meowcat.edxposed.manager") with your ROM.
Suggestions on where I go from here?
radwolf76 said:
I'm having trouble getting EdXposed to activate. I'm on a fresh clean install of the TWRP flashable version of US998 30b with Magisk 20.1 installed and working, and while i've got the Riru - Core module installed (v19.5), no matter which Riru - Ed Xposed module I use I get the following error message from EdXposed Manager 4.5.2 explaining why it's installed but not activated:
There seems to be a known issue("Wrong base directory: /mnt/expand/7f941a12-b7aa-4d2a-a664-f89a46b7d86c/user_de/0/org.meowcat.edxposed.manager") with your ROM.
Suggestions on where I go from here?
Click to expand...
Click to collapse
Solution Found. My EdXposed Manager had been installed to External Storage. It only works on Internal Storage.
Safety Net Fail w/ Gravitybox
It looks like as soon as I enable the Gravitybox module that you recommend, safetynet fails. Are you still passing with your setup (I'm wondering if there has been some update that this version of Gravitybox no longer passes)?
UPDATE: even though safetynet shows up as failing in Magisk, I am still able to use Google Pay, so maybe it is working? I'll update this post once I've tried using Google Pay to pay for something.
UPDATE again: after a couple of days, Google Pay showed a pop up message saying that it would no longer work. Uninstalling and reinstalling gets it working temporarily again it seems.
Dear @ChazzMatt
Should I install the old beta in the last page or the latest canary to avoid safety net and which versions is the best?
Note to everyone: installing xposed framework will trigger safetynet....and uninstalling it will do as well
And i don't know how to solve this except flashing a new rom
Hi, folks. I have a redmi note 8t.
I would like to know if installing a custom rom from miui (EU, MIglobe...) keeps the NFC for payments . I have heard that you can't, that you have to do root and install a magistk module...I hope you can help me with this doubt, since I have unlocked the bootloader...thank you very much!
I have MiUiMix on Android 9 with preinstalled root. I just downloaded magisk manager app and enabled magisk hide. Payments in Poland works.
Lineage 17.1 with Magisk & MagiskHidePropsConf.
Google Pay works fine (france).
Edit: Also, Widevine still L1 so Netflix in HD, Banks app, Pokemon Go works, etc..
_PePe_ said:
Hi, folks. I have a redmi note 8t.
I would like to know if installing a custom rom from miui (EU, MIglobe...) keeps the NFC for payments . I have heard that you can't, that you have to do root and install a magistk module...I hope you can help me with this doubt, since I have unlocked the bootloader...thank you very much!
Click to expand...
Click to collapse
If I got you right, you're asking if unlocking bootloader doesn't allow using NFC. If I'm not mistaken, I could use NFC when I unlocked the phone, but I'm not exactly sure.
If you ask after installing a custom ROM NFC works, for that yes, you definitely need to install magisk. Don't be scared though, it's an easy process. Just flash a ROM, then finalize it (ie. start the mobile and setup the ROM). Once you're done with it, go back to twrp and flash magisk. Then install magisk manager (apk).
When in magisk manager both parts are green (that both are installed and working right), rename magisk manager (change it to something other than manager), let it download magisk manager again, and turn on magisk hide. Restart the phone, and in the menu you'll find from which apps manager should hide itself. Choose the banking apps and you're all ready to go.
I use the same mobile, and these are the steps I took. It's simple, straightforward and intuitive. Don't worry, you'll have NFC once you follow these simple steps.
Thank you so much for your answer... I'm sorry I didn't answer sooner, but I couldn't because of my job...
Now I have the EU stable (miui11) waiting for me to update to 12 .... recommend me another rom based on miui ? .... thanks again and a greeting!
_PePe_ said:
Thank you so much for your answer... I'm sorry I didn't answer sooner, but I couldn't because of my job...
Now I have the EU stable (miui11) waiting for me to update to 12 .... recommend me another rom based on miui ? .... thanks again and a greeting!
Click to expand...
Click to collapse
First, you're most welcome!
Second, I didn't use any miui based ROM. Of those I tried, I fancied them in decreasing order as follows:
crDroid
LineageOS
Pixel Experience / Paranoid Android
In general, I can't say I'm dissatisfied with any. It's just minor stuff that put one over another, and all have been good in general. I use crDroid now simply because it allows more customizations - albeit I can't use front and aux cams. It's a singular issue though, as I don't read this from other users.
So I'd say try any, if you want. Because I use it now, I'd recommend crDroid but you'll find fans of all, and others that I didn't mention. It comes down to trial and error in the end.
NFC works with all four that I mentioned. In the beginning, when I first rooted and installed a custom ROM, my banking app warned me that I use a rooted phone and whatever, yet it's simple to fix. Don't worry about making NFC work, it really is easy. Step by step,
Install magisk from twrp
Install magisk manager
Rename magisk manager app
Open the app and let it install magisk again
Restart
Enable magisk hide
Restart
Then install your banking app and from magisk manager, add the banking app to hidden apps
And that's it. It seems a long process but takes five minutes.
Thank you very much for your comment my friend .....I have it in mind to install these roms ....greetings!
Hey guys, has anyone gotten Gpay to work on lineage 19.1? I have done the following and have had very odd results. Firstly, I am passing safteynet and my device is registered as play certified in Google play store. I'm seeing where sometimes gpay won't open at all and when it does it says it is unable to load my payment methods.
Specs:
OS - linageOS 19.1 (latest build as of this post)
GAPPS - Mindthegapps (latest build as of this post)
Steps taken:
Installed magisk, enabled zygisk and rebooted
Installed magisk hide props module then rebooted
Installed shamiko module then rebooted
Installed universal safteynet fix (zygisk) then rebooted
Configured denylist in magisk checking GPS (all), and Gpay (all) rebooted
Changed device fingerprint with magisk hide props module to a certified one then rebooted
Additional steps taken:
I cleared data from GPS, play store and Gpay and rebooted
I tried a different device fingerprint and rebooted (clearing data like above afterwards and rebooting again)
I have done a complete fresh install of my OS and tried again from scratch.
I also tried seeing is renaming magisk would help at all, it didn't
It appears I'm getting nowhere with this. If anyone has gotten it to work and has some insight it's be greatly appreciated!
Nevermind, looks like it was an issue from having the pixelify module installed as well. After I removed it it started working just fine.
deathblade said:
Nevermind, looks like it was an issue from having the pixelify module installed as well. After I removed it it started working just fine.
Click to expand...
Click to collapse
Hey deathblade!
Thanks for helping me out on the other thread.
Just wanted to check in, did you use the official build or the unofficial one with the Pixel Goodies? I'm intending/hoping to have full functionalities of Google Pay using the unofficial build, but from your post it seems that I can't have the Pixel experience if I want the ROM to work with Google Pay?
HW898 said:
Hey deathblade!
Thanks for helping me out on the other thread.
Just wanted to check in, did you use the official build or the unofficial one with the Pixel Goodies? I'm intending/hoping to have full functionalities of Google Pay using the unofficial build, but from your post it seems that I can't have the Pixel experience if I want the ROM to work with Google Pay?
Click to expand...
Click to collapse
I'm using the official build. I think the unofficial has everything needed to use Gpay and have some pixel things baked in. So might be worth a look in your case
deathblade said:
I'm using the official build. I think the unofficial has everything needed to use Gpay and have some pixel things baked in. So might be worth a look in your case
Click to expand...
Click to collapse
Aite, I will try out the unofficial one and see if GPay works there too. Thanks for the headsup!
HW898 said:
Aite, I will try out the unofficial one and see if GPay works there too. Thanks for the headsup!
Click to expand...
Click to collapse
I just remembered, the unofficial is setup to pass safteynet out the box, but more maybe needed for Gpay to work. Once you flash it try it out, if you run into issues I can provide what I did to get Gpay working
deathblade said:
Nevermind, looks like it was an issue from having the pixelify module installed as well. After I removed it it started working just fine.
Click to expand...
Click to collapse
Hi there, trying out the official build after experiencing some problems on the unofficial one. Any alternatives to pixiel-ing the ROM?
HW898 said:
Hi there, trying out the official build after experiencing some problems on the unofficial one. Any alternatives to pixiel-ing the ROM?
Click to expand...
Click to collapse
Not that I've found, however I did notice if you install the pixelify module then uninstall it, it does seem to leave some stuff behind. Like I still have the option to use Hold for me and direct my call. So it might work out where you can install it to get the things you want then remove it to get Gpay working
deathblade said:
Not that I've found, however I did notice if you install the pixelify module then uninstall it, it does seem to leave some stuff behind. Like I still have the option to use Hold for me and direct my call. So it might work out where you can install it to get the things you want then remove it to get Gpay working
Click to expand...
Click to collapse
I see... So these also means stuff like Now playing etc. will be gone too right?
Also, did you experience the problems I've faced in the unofficial build? sounds cannot change etc. as posted in main thread
HW898 said:
I see... So these also means stuff like Now playing etc. will be gone too right?
Also, did you experience the problems I've faced in the unofficial build? sounds cannot change etc. as posted in main thread
Click to expand...
Click to collapse
Nope now playing is still there. I really only used it the module to force call screening to show up. But I have pretty much everything I remember from stock plus a few phone related goodies. I never tried the unofficial build but on the official I do not have that issue
deathblade said:
Nope now playing is still there. I really only used it the module to force call screening to show up. But I have pretty much everything I remember from stock plus a few phone related goodies. I never tried the unofficial build but on the official I do not have that issue
Click to expand...
Click to collapse
I see... I will try installing the official one without magisk as I won't want to meddle with rooting stuff for now, will get back with results asap!
deathblade said:
Hey guys, has anyone gotten Gpay to work on lineage 19.1? I have done the following and have had very odd results. Firstly, I am passing safteynet and my device is registered as play certified in Google play store. I'm seeing where sometimes gpay won't open at all and when it does it says it is unable to load my payment methods.
Specs:
OS - linageOS 19.1 (latest build as of this post)
GAPPS - Mindthegapps (latest build as of this post)
Steps taken:
Installed magisk, enabled zygisk and rebooted
Installed magisk hide props module then rebooted
Installed shamiko module then rebooted
Installed universal safteynet fix (zygisk) then rebooted
Configured denylist in magisk checking GPS (all), and Gpay (all) rebooted
Changed device fingerprint with magisk hide props module to a certified one then rebooted
Additional steps taken:
I cleared data from GPS, play store and Gpay and rebooted
I tried a different device fingerprint and rebooted (clearing data like above afterwards and rebooting again)
I have done a complete fresh install of my OS and tried again from scratch.
I also tried seeing is renaming magisk would help at all, it didn't
It appears I'm getting nowhere with this. If anyone has gotten it to work and has some insight it's be greatly appreciated!
Click to expand...
Click to collapse
Just also wanted to clarify in the case I decide to install magisk, which module do you install exactly? All of them? Zygisk/hide props module/shamiko/universal safetynet fix?
HW898 said:
Just also wanted to clarify in the case I decide to install magisk, which module do you install exactly? All of them? Zygisk/hide props module/shamiko/universal safetynet fix?
Click to expand...
Click to collapse
Ok so here is the breakdown:
Zygisk is not a module, but an implementation method used by modules. Magiskhide props is used to change the device fingerprint to a valid one that registers as protected by google play. Shamiko is for hiding root from Google play services, and Gpay (and whatever other apps may need it). Universal safteynet fix is used to help pass google safteynet checks (security). Not listed is the pixelify module used to add pixel exclusive features but of course with it install it cause havoc on Gpay and other apps so once installed it should be uninstalled.
TLDR
Yes all of them
deathblade said:
Ok so here is the breakdown:
Zygisk is not a module, but an implementation method used by modules. Magiskhide props is used to change the device fingerprint to a valid one that registers as protected by google play. Shamiko is for hiding root from Google play services, and Gpay (and whatever other apps may need it). Universal safteynet fix is used to help pass google safteynet checks (security). Not listed is the pixelify module used to add pixel exclusive features but of course with it install it cause havoc on Gpay and other apps so once installed it should be uninstalled.
TLDR
Yes all of them
Click to expand...
Click to collapse
Aite thanks for the help mate! just installed but apparently, i couldn't find gapps despite sideloading it.. might have to reinstall again
Hmm safetynet fix seems to fail, can't pass cts profile.. any step by step guides by any chance?
deathblade said:
Ok so here is the breakdown:
Zygisk is not a module, but an implementation method used by modules. Magiskhide props is used to change the device fingerprint to a valid one that registers as protected by google play. Shamiko is for hiding root from Google play services, and Gpay (and whatever other apps may need it). Universal safteynet fix is used to help pass google safteynet checks (security). Not listed is the pixelify module used to add pixel exclusive features but of course with it install it cause havoc on Gpay and other apps so once installed it should be uninstalled.
TLDR
Yes all of them
Click to expand...
Click to collapse
HW898 said:
Hmm safetynet fix seems to fail, can't pass cts profile.. any step by step guides by any chance?
Click to expand...
Click to collapse
That's where magisk hide props comes in. I don't have a full guide that I know of but I could do a quick wtite up tomorrow for you
deathblade said:
That's where magisk hide props comes in. I don't have a full guide that I know of but I could do a quick wtite up tomorrow for you
Click to expand...
Click to collapse
I got it working after following a guide~
Unfortunately features like now playing isn't working. the rest is pretty much okay tho
HW898 said:
I got it working after following a guide~
Unfortunately features like now playing isn't working. the rest is pretty much okay tho
Click to expand...
Click to collapse
You install the pixelify module? Also can you explain how it's not working?
deathblade said:
You install the pixelify module? Also can you explain how it's not working?
Click to expand...
Click to collapse
Nope, I didn't. Other than the modules to hide from banking apps as mentioned above, I installed a pixel launch module here to make it for pixel-like: https://forum.xda-developers.com/t/app-mod-pixel-launcher.4442077/
Other than that nothing else.
It doesn't;t work in the sense that it does not pick up music, even popular ones. The settings are there though, I can see them. It just doesn't identify any songs
HW898 said:
Nope, I didn't. Other than the modules to hide from banking apps as mentioned above, I installed a pixel launch module here to make it for pixel-like: https://forum.xda-developers.com/t/app-mod-pixel-launcher.4442077/
Other than that nothing else.
It doesn't;t work in the sense that it does not pick up music, even popular ones. The settings are there though, I can see them. It just doesn't identify any songs
Click to expand...
Click to collapse
This is the pixelify module I installed then removed, you can give it a try.
GitHub - Kingsman44/Pixelify: Magisk module to enables pixel exclusive features and ui
Magisk module to enables pixel exclusive features and ui - GitHub - Kingsman44/Pixelify: Magisk module to enables pixel exclusive features and ui
github.com