Related
https://www.xda-developers.com/official-xposed-framework-android-nougat/
https://forum.xda-developers.com/showthread.php?t=3034811
https://forum.xda-developers.com/xposed/discussion-xposed-nougat-t3685687
Let's share what does/doesn't work
Since I made the post, it's only fair I go first.
On A2017G, stock and updated via OTA to 7.1, the flash was successful. The first boot took ~10 minutes. I will now start testing modules and update this post with what does/doesn't work.
Modules I tried so far:
LP: Works
Amplify Battery Extender: Works
Greenify: Does NOT work - The module is active, however, the app does not seem to be aware that it is.
-I'm looking for the old Youtube Background Playback module. It seems to have been pulled from the download list inside xposed manager. If anyone has a copy of it, it would be great to see if it's still working. The LP patch for background play stopped working for me on 3 different devices about 2 weeks ago.
Great!
Maybe a stupid question, but will installing xposed still break safetynet checks? That was the only benefit of running.g without xposed; aps like horizon / Ziggo Go worked, hate to have to do without it.
TIA,
Cheers,
/Cacti
Sent from my ZTE A2017G using XDA-Developers Legacy app
Amplify can't see wakelock or service...greenfy continue to tell me to activate the module. (I just set on the module and reboot many times)
UPDATE: other users with different device have the same problem, I think we need an update of these apps for working with the new version of exposed.
https://forum.xda-developers.com/xposed/discussion-xposed-nougat-t3685687
Running A2017UV1.1.0B32 (android 7.1.1) rooted by Magisk Version 14.0.
all was good but when installed xposed (SDK 25/API 25) something is wrong;
SafetyNet is faild at check and in Magisk , when pressing Menu->Superuser I get "Magisk Manager has stopped"
but root is working and Xposed modules are working.
mb0 said:
Running A2017UV1.1.0B32 (android 7.1.1) rooted by Magisk Version 14.0.
all was good but when installed xposed (SDK 25/API 25) something is wrong;
SafetyNet is faild at check and in Magisk , when pressing Menu->Superuser I get "Magisk Manager has stopped"
but root is working and Xposed modules are working.
Click to expand...
Click to collapse
I had the magisk FC too. Fixed it by switching to stable channel reinstalling both the zip and the launcher. Safety net is broken with magisk hide setting and the "universal safety net fix" module.
rzarectha said:
I had the magisk FC too. Fixed it by switching to stable channel reinstalling both the zip and the launcher. Safety net is broken with magisk hide setting and the "universal safety net fix" module.
Click to expand...
Click to collapse
Thanks. Not what I wanted to hear but still [emoji4]
Cheers,
/Cacti
Sent from my ZTE A2017G using XDA-Developers Legacy app
@rzarectha thank you, but it didn't help. even tried install beta version;
tried to complete uninstall and install again the zip and apk - it worked and no more FC.
Im also on B32 with Magisk, but currently running the official Xposed for Magisk. Should I use the Xposed uninstaller or just remove and uninstall the Magisk Xposed module before starting with the official Xposed process?
Regarding YouTube background play:
I found the .apk on their github page, it's in the first thread that mentions it being removed from the repo. I tested it and it works!
For whatever reason, I cannot get past a bootloop after installing via TWRP. Interestingly, I can install the unofficial module from back in August. I can uninstall that just fine, but reinstalling the proper one does nothing but bootloop. Anyone else having this problerm?
Could anyone try running Fate Grand Order?
After update to V88 the boot time is longer for 45-50 second on my A2017G with Stock 7.1.1B06. With inofficial V87 boots better
This is what I have setup so far. Crappalinks, YouTube Adaway, XInsta, all work. Greenify doesn't and neither did Amplify, not properly anyway. Also it does break Safety net. We'll have to wait for the Magisk Module
rzarectha said:
Since I made the post, it's only fair I go first.
On A2017G, stock and updated via OTA to 7.1, the flash was successful. The first boot took ~10 minutes. I will now start testing modules and update this post with what does/doesn't work.
Modules I tried so far:
LP: Works
Amplify Battery Extender: Works
Greenify: Does NOT work - The module is active, however, the app does not seem to be aware that it is.
-I'm looking for the old Youtube Background Playback module. It seems to have been pulled from the download list inside xposed manager. If anyone has a copy of it, it would be great to see if it's still working. The LP patch for background play stopped working for me on 3 different devices about 2 weeks ago.
Click to expand...
Click to collapse
why use Xposed for youtube adaway and background player when they make a separate app for that over here https://forum.xda-developers.com/android/apps-games/app-iytbp-injected-youtube-background-t3560900 I have been using this for a while now and it is great
reV17 said:
This is what I have setup so far. Crappalinks, YouTube Adaway, XInsta, all work. Greenify doesn't and neither did Amplify, not properly anyway. Also it does break Safety net. We'll have to wait for the Magisk Module
Click to expand...
Click to collapse
There is a magisk module on the repo but to my knowledge it still breaks safetynet
For those with issues with magisk and xposed, you can't use them both together, if you want to then you have to use the specific xposed magisk module here https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268 also flashing xposed regardless magisk or not its going to break safetynet no matter what. Will explain in that magisk xposed thread.
If someone got problems like me, heres my way i installed it successfully and get everything to work (Magisk!):
- disable xposed modules
- restart to recovery
- install Xposed v88.2 by topjohnwho (from xposed thread) via recovery
- reboot to system (first boot took ~9min)
- install Xposed Installer 3.1.2 for Magisk
- activate modules in xposed installer
- reboot phone and its done.
If you dont deactivate the xposed modules before flashing xposed, you maybe have to reinstall them and maybe set up everything new, if you cant save the settings for the modules. This was happening in my first try. In my second try i disabled them before and activated after flashing and dont have do setup every xposed module again.
A2017G with B06 and Magisk v14.2.
Can you use gravity box module on the stock rom? Is miflavor "close enough" to aosp to be compatible with mods made for that?
rzarectha said:
Can you use gravity box module on the stock rom? Is miflavor "close enough" to aosp to be compatible with mods made for that?
Click to expand...
Click to collapse
Yes. Not all is working, but center clock, battery mod in statusbar, RAM usage in recents, down-/uploadspeed in statusbar and some other things ... enough for me.
Hello guys!
If you update to the latest Magisk version (v16.4), you will notice that it will now pass SafetyNet check.
Check attached screenshots!
rzarectha said:
Hello guys!
If you update to the latest Magisk version (v16.4), you will notice that it will now pass SafetyNet check.
Check attached screenshots!
Click to expand...
Click to collapse
Thats nice to know. I mean i havent used magisk yet (on previous phone it didnt work at all). Currently still on supersu. But its good to know that it works again, so i might switch in the future.
Sent from my ZTE A2017G running V1.2.0B08 using XDA Labs
GodOfPsychos said:
Thats nice to know. I mean i havent used magisk yet (on previous phone it didnt work at all). Currently still on supersu. But its good to know that it works again, so i might switch in the future.
Sent from my ZTE A2017G running V1.2.0B08 using XDA Labs
Click to expand...
Click to collapse
I think it's just as good as SuperSU in handling root apps. The way Magisk stands out though is the modules. I would recommend that you install only the magisk manager (it does not mess with anything in your phone if you just install it), and browse through the list of modules it has. It's very similar to the way modules in xposed look like. Maybe you can find some interesting functionality in there.
I am using the greenify module (works much like boost mode on xposed), busybox, adblocker, systemiser (turns user apps in sys apps), debloater (completely uninstall user apps). There's a ton of mods though, I don't even understand what most actually do.
Keep in mind that having xposed installed will break safetynet no matter what. Magisk can't hide it.
rzarectha said:
I think it's just as good as SuperSU in handling root apps. The way Magisk stands out though is the modules. I would recommend that you install only the magisk manager (it does not mess with anything in your phone if you just install it), and browse through the list of modules it has. It's very similar to the way modules in xposed look like. Maybe you can find some interesting functionality in there.
I am using the greenify module (works much like boost mode on xposed), busybox, adblocker, systemiser (turns user apps in sys apps), debloater (completely uninstall user apps). There's a ton of mods though, I don't even understand what most actually do.
Keep in mind that having xposed installed will break safetynet no matter what. Magisk can't hide it.
Click to expand...
Click to collapse
Edit: i moved this issue to the Q&A and help section since more issues keep coming
https://forum.xda-developers.com/axon-7/help/finally-decided-to-switch-supersu-to-t3787201
just switched to latest stock rom (1.2.0 B10) and installed magisk (16.4). it works and safetynet passes. the problem i got now is that the greenify module fails to install in magisk (see screenshot)
do i gotta flash the module through TWRP maybe? still a newbie to magisk since the axon 7 is the first phone to have it working
EDIT: for some reason magisk doesn't remember which apps have requested root after a reboot. everytime i reboot i get a prompt to allow root access to all my root apps (like greenify). idk why this is happening. i mean, root itself is working as it should. i already uninstalled bloatware and disabled/freezed things like the powermanagement
I'm interested in knowing where Magisk is at
On Angler (Nexus 6p) I flashed the latest stock rom. (After a complete wipe) Afterwards I flashed TWRP and unzipped Magsik. Subsequently I did update to the latest version. After that I changed the packagename of Magsik manager. Furthermore I installed Xposed framework. Afterwards I enabled root hide for the TAN app:
https://play.google.com/store/apps/details?id=com.starfinanz.mobile.android.dkbpushtan&hl=en
This software is meant to give you the tan without using sms services.
Still, the app crashed right at the start without any error notification. Android Version is 8.1 and Magsik is v16. While I did the test, the bootloader was unlocked and TWRP was still the recovery. Can these two things affect the verification of the Banking app? I tried this several times ago in the past, but I was never to make this app running.
If anyone would be able to give helpful advice here, it would be very much appreciated.
Best,
scarline
I have heard that DKB Tan2Go does not work with newer Android versions like Oreo 8.1.x at all.
I can also confirm that. I tried it on a Sony cellphone. The cellphone was not rooted and with a completely new and 'clean' ROM. It was to no avail.
A friend has been forced to buy a chip reader. I am fortunate to be able to use normal TAN lists at the moment. If the DKB tries to exclude me from online banking, I will change the bank.
DKB Tan2Go seems to be one of the worst and most insecure apps ever. The reviews in Google PlayStore confirm this conclusion.
Maybe there will be a solution someday?
DKB TAN2go works with Magisk:
1. Install the TAN2go app (but don't open it)
2. Add the TAN2go app in Magsik Manager in the menu "Magisk Hide"
3. Reboot the phone (I don't know if this is necessary)
4. Open TAN2go, works fine.
**** DKB and this stupid security features which bring absoltuely no security.
That's exactly what I tried - without success. I read that it only worked with an old, obsolete version of Tan2Go. However, I could not find this version and I'm not sure if it still works at all. Did you have the latest version of Tan2Go from Google PlayStore? According to DKB, the recent Tan2Go does not work with devices that was once rooted or had a CustomROM. Even if you go back to stock the Root Counter changed and DKB Tan2Go will never work on this device. Unfortunately, I have to confirm that.
I am working on it to change the bank, because of that.
exaveal said:
DKB TAN2go works with Magisk:
**** DKB and this stupid security features which bring absoltuely no security.
Click to expand...
Click to collapse
Indeed!
Yes, I have installed the latests version of LineageOS, latest version von Magisk and the latests version of the TAN2go app.
I tried that to no avail. I heard once the root counter has a value other than 0, one can't go back. Probably it is also the Sony bootloader and it is different with other devices?
exaveal said:
Yes, I have installed the latests version of LineageOS, latest version von Magisk and the latests version of the TAN2go app.
Click to expand...
Click to collapse
I have a Xiomi Mi5 rooted with Magisk and Tan2go used to work for the last year or so. But yesterday I tried to make a transaction and BOOM! App crashed without an error message. Tried to use a newer Magisk, tried reinstalling the App, nothing helped.
The worst thing is that I do not know if some of my programs have a battery checker or a screen reader plugin that I am not aware of, or if Tan2Go suddenly detects my root. Regardless, crashing without an explanation is like the worst programming practice ever.
Since I do not need this kind of ****e in my life I will probably change Bank, I mean what good is an internet Bank if you cannot do transactions over your mobile device?
Well, willy-nilly I try to use the only other option from DKB: the German TAN Generator. Every other bank equips you with such a device, if they want you to use it. The DKB does not. Actually, I ordered the 3rd TAN Generator and fully paid for it. The first one drains the battery within days. The second one let me type in all the numbers and for no reason the TAN code does not show up on display.
These devices are very annoying anyway, because you have to type in a lot of numbers for every money transfer, the characters are very small (on the laptop) and you have to carry the TAN Generator + the DKB debitcard all the time. Of course this is less secure.
I would change the bank immediately, but want to keep the Visa credit card. I have higher limits on it. That's the only reason. As soon as I found an alternative bank in Europe, I will leave the DKB for good.
It dont worked with Lineage 14.1 but with 15.1 unoffical build on Samsung S4 together with latest Magisk .Rom from here
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-galaxy-s4-lte-android-8-1-oreo/
Works for me
Just tried again. It hasn't been working for me in the past. When downloading & opening the app, I had the same problems.
Then I simply followed the above advice: downloading the app again, didn't open it, hide with Magisk, reboot and opened the app - worked well and was able to register for tan2go.
I am using Lineage 16.0 and Magisk v18.0
DKB already updated their app - they patched it
kyodhin said:
Just tried again. It hasn't been working for me in the past. When downloading & opening the app, I had the same problems.
Then I simply followed the above advice: downloading the app again, didn't open it, hide with Magisk, reboot and opened the app - worked well and was able to register for tan2go.
I am using Lineage 16.0 and Magisk v18.0
Click to expand...
Click to collapse
The app version from September (version 2.3.0) does work, the newer app version from 4.4.19 (version 2.4.0) does not...
Tested working combination: Magisk 18.0, Magisk Manager 6.1, DKB version 2.3.0
Can confirm that, working with magisk and 2.3.0. Not working anymore with 2.4.0.
I have another Tan app from another bank and with the new version it also stops working. Seems that magisk is now quite to popular and they working on better detection. Magisk hide is useless on the recent version of these tan apps.
That really sucks. No way to get 2.4.0 working. Hoping for a magisk fix. Are the magisk developer informed that there are problems with magisk hide? I think others will have similar problems too.
I successfully got 2.4 working again, after it got updated and refused to start.
Following the steps from this post made it work again (German):
https://www.android-hilfe.de/forum/...trotz-magisk.901517-page-2.html#post-11532359
I installed Magisk 19.0 (beta) but contrary to the above mentioned post I left my Magisk modules installed as they were before the update.
Both the Magisk modules as well as TAN2Go 2.4 are now working again.
I had to authenticate the new TAN2Go installation by adding it as a "new device" using SMS verification.
I was not able to get it to run with the above mentioned instuctions.
Device: Nexus 6P (angler), ROM: LineageOS 15.1-20190419, Magisk modules: MagiskHide Props Config (required for ctsProfile test), Busybox for Android NDK (required for MagiskHide Props Config).
DKB Tan2Go crashes immediately when started.
Same for me. The above instruction doesn't work.
Downgrade to 2.3.0
I experienced the same problem. Had to do an important transfer yesterday. And of course Tan2Go-2.4.0 crashed. I'm using Magisk v18.1.
Today I did a downgrade via Aptoide to 2.3.0 and had to register the smartphone again via SMS. This worked without any problems.
To avoid the update problem and keep with 2.3.0:
Start Titanium Backup
Select the DKB Tan2Go App
Long click on the App.
Connect with Google Play Store (forced)
Long click the App again.
Disconnect from Google Play Store
Hope it helps. I don't think there's much to change in the DKB Api. I'll use 2.3.0 until they block it via the API.
If more people confirm the proposed solution with Magisk v19, I'll try it maybe.
I got it working with v2.4.0, but don't know which step was the solution. Switching to the "Canary" channel of Magisk or hiding the Magisk Manager in the settings. I think the last one was the solution.
Can you guys try and give feedback?
Don't forget to uninstall and install the app before testing again.
musv said:
If more people confirm the proposed solution with Magisk v19, I'll try it maybe.
Click to expand...
Click to collapse
I have the same issue. Hopefully it can be fixed via Magisk one day.
Worked with T2G 2.4, 19, 7.1.1
Walhalla said:
I got it working with v2.4.0, but don't know which step was the solution. Switching to the "Canary" channel of Magisk or hiding the Magisk Manager in the settings. I think the last one was the solution.
Can you guys try and give feedback?
Don't forget to uninstall and install the app before testing again.
Click to expand...
Click to collapse
Hi Walhalla,
Hi All
In Settings "General">"Hide" via other apk name it worked for me. V19.0, v7.1.1, Tan2Go 2.4
Has anyone updated their Magisk version after initial install?
I'm on Magisk 22, and version 22.1 is available. I don't have a burning need for 22.1 but have found from experience that it's best to not lag behind too much; eventually some or other module will require a recent version.
I'm guessing it's similar to initial install, but done from within the Magisk app using 'Recovery Mode'. First for me doing this, so figured I'd ask about pitfalls to avoid from folks who have already done this.
EDIT: To answer my own question (since I'm so impatient), yes. Just remember to rename Magisk-v22.1.apk to .zip before rebooting to save you some time after Magisk reboot takes you to TWRP.
Arobase40 said:
This is indeed an important update so better do the update but prepare yourself to update more stuffs if you want to keep EdXposed and his modules working...
I didn't think about downloading Magisk-v22.1.apk and to rename to .zip before flashing it with TWRP so I had to update the Magisk manager before I could update Magisk itself.
After that you may or may not update the Riru and Riru edXposed modules as the edXposed was not working anymore for me . So I had to also update the edXposed manager.
And don't forget to reboot many times...
Finally you could also update the AFWall+ from the PlayStore... ^
Click to expand...
Click to collapse
All working well here with:
Magisk 22.1
Riru v25.3.3.r393.ed83041
Riru - EdXposed v0.5.2.2_4683-master
EdXposed Manager 4.6.2
Arobase40 said:
This is not related with the Magisk update but can you tell what is actually your Tab S6 SafetyNet status ?
Click to expand...
Click to collapse
I have no idea. I've never looked in to what it even means; sonething that is needed for some apps, from what I've read?
What do want me to look for?
Arobase40 said:
Well, to be short the SafetyNet status indicates what you can potentially do with a rooted device such as creating Secure Folder, installing and use banking apps, probably use Netflix or some other apps or features you would be able to run with a non-rooted device.
So, to know your SafetyNet status you simply have to open your Magisk manager and tap the "Verify SafetyNet" option on the Magisk welcomm screen. Then it may ask or may not ask you the permission to download external modules,do so and then it will tell you if you pass this test or not !
If I ask you that it because some weeks ago I passed all the test with my Tab S6 and my 2 Galaxy Note 9 and now they all fail for some unknown reasons and as I changed nothing in the Magisk environment and the edXposed environment except updating some Samsung and Google apps ! ^^
So I want to try to understand how it comes and when it comes this SafetyNet compatibility was broken... ^^
If other users could also check their SafetyNet status and indicate if there was a change it may help.
Click to expand...
Click to collapse
I tapped 'Check SafetyNet' and got (see screenshot). Not interested in going any further. I hope you understand. fwiw, I too have an S6 with all Google and most Samsung apps either frozen or deleted; at last count 149 of them.
As the title says, is it possible.and how to successfully install Viper4Android to Renoir, running MIUI 12.5+, A11 - assuming that the phone is already rooted by Magisk
Or at least, how to successfully install JanesDSP
If you have already Magisk and rooted your phone, you can install the module of Viper with it.
Thoiareg said:
If you have already Magisk and rooted your phone, you can install the module of Viper with it.
Click to expand...
Click to collapse
Did you try and does it really work for you?
I've posted to Viper4Android thread with more details - Viper4Android apk can never find drivers:
- It asks to install drivers and to reboot
- After rebooting and reopening, Viper4Android apk again does not find drivers and asks to install and to reboot
- It can go endlessly
I tried with AML, by debloating' MusixFM, no avail
---
Similarly, I tried but cannot properly install JamesDSP
It's app always crashes, with exception saying that it cannot find drivers
Reported also to JamesDSP thread
---
In both threads there are several other users with the new A11 phones who report the same problems (cannot install Viper4Android, neither JamesDSP)
Frankly, I don't have Renoir - I have Lisa (Xiaomi 11 Lite 5G NE), with MIUI 12.5.8, A11.
Still, I wanted to ask if somebody with the similar Renoir (Mi 11 Lite 5G) succeeded to install V4A or JamesDSP?
zgfg said:
Did you try and does it really work for you?
I've posted to Viper4Android thread with more details - Viper4Android apk can never find drivers:
- It asks to install drivers and to reboot
- After rebooting and reopening, Viper4Android apk again does not find drivers and asks to install and to reboot
- It can go endlessly
(...)
Click to expand...
Click to collapse
The magisk module is not a apk. It't a zip file.
Best Magisk modules
Looking for some of the best Magisk modules for modding? We’ve got all the information you need to get started right here. Read on!
www.xda-developers.com
Thoiareg said:
The magisk module is not a apk. It't a zip file.
Best Magisk modules
Looking for some of the best Magisk modules for modding? We’ve got all the information you need to get started right here. Read on!
www.xda-developers.com
Click to expand...
Click to collapse
Sorry, I'm 5 years user of V4A, used successfully on 5 phones so far - I perfectly know what is Magisk, Magisk modules, V4A module, how it installs, etc
I'm talking about the Viper4Android application that installs with the module and serves for managing presets, kernels, etc
If you have practical advice how to install to the new MIUI release.(that you can prove that it works), fine - otherwise please let's stop wasting the time
Good night
zgfg said:
Sorry, I'm 5 years user of V4A, used successfully on 5 phones so far - I perfectly know what is Magisk, Magisk modules, V4A module, how it installs, etc
I'm talking about the Viper4Android application that installs with the module and serves for managing presets, kernels, etc
If you have practical advice how to install to the new MIUI release.(that you can prove that it works), fine - otherwise please let's stop wasting the time
Good night
Click to expand...
Click to collapse
Sorry, but I don't know you.
So, I answer according to the information you give in your message.
You have a problem installing Viper, I suggest you install it via Magisk. And you answer by talking about an apk file. So your answers don't make sense.
Now be nicer to people who respond to you and try to help you.
Good luck in your problem.
Solved by temporarily disabling USNF 2.2.1 - then JamesDSP installed correctly.
Later I re-enabled USNF and now both modules work correctly
Still I wasn't able to make V4A working
Anyway, closing the thread
THREAD LOCKED
Requested by OP.
Regards,
shadowstep
Forum Moderator