Related
A few days ago I posted a question about not being able to install any Xposed modules here, so far no one answered: https://forum.xda-developers.com/xposed/xposed-framework-installed-running-t3567230
I thought this problem had something to do with the modules specifically, but it turns out that on my phone, for whatever reason, installing the framework subsequently prevents ALL apps from installing, even those from Google Play itself, displaying a "-504" error.
I see people have asked this question before, but are also not getting answers: https://forum.xda-developers.com/xposed/install-apps-installing-framework-t3430922
Please, if anyone has any idea of why this can be and how to fix it, let me know. Any help will be infinitely appreciated!
What phone and ROM are you using?
One thing you could try is to install systemless Xposed through Magisk. Then use MagiskHide to hide both root and Xposed from all Google apps and potential sources of conflict. If it's a software limitation/conflict, this may be a workaround.
Keep in mind that you will have to root your phone with Magisk rather than SuperSU or any other form of root.
Anova's Origin said:
What phone and ROM are you using?
One thing you could try is to install systemless Xposed through Magisk. Then use MagiskHide to hide both root and Xposed from all Google apps and potential sources of conflict. If it's a software limitation/conflict, this may be a workaround.
Keep in mind that you will have to root your phone with Magisk rather than SuperSU or any other form of root.
Click to expand...
Click to collapse
Hey, thank you for your answer!
I am using a Sony Xperia M4 Aqua E2306, rom is 26.1.A.1.112 Latin America Generic. It is rooted and with TWRP installed accroding to this thread: https://forum.xda-developers.com/m4-aqua/general/root-e2306-m4-aqua-guide-t3270521
I also have a locked bootloader, and it cannot be unlocked, so unfortunately that shuts the door on most rooting options.
I never heard of Magisk before, but from what I'm seeing, it looks it TWRP is required to get root with Magisk, but some kind of root is already required on my phone in order to get TWRP. So I'm not sure how to go about this.
If your phone is already rooted, then you can download Magisk Manager application and have it installed it's necessary frameworks through the app itself. You won't be able to use Magisk's root, but you'll still be able to install systemless Xposed and hide it from other apps.
Edit: Ignore all of that actually, I just realized that magisk requires boot image modifications so you have to have an unlocked bootloader to use it.
Anova's Origin said:
If your phone is already rooted, then you can download Magisk Manager application and have it installed it's necessary frameworks through the app itself. You won't be able to use Magisk's root, but you'll still be able to install systemless Xposed and hide it from other apps.
Edit: Ignore all of that actually, I just realized that magisk requires boot image modifications so you have to have an unlocked bootloader to use it.
Click to expand...
Click to collapse
Oh well, thanks anyway. I might try it anyways, maybe it will work, you never know. Don't have much to lose at this point
Anova's Origin said:
What phone and ROM are you using?
One thing you could try is to install systemless Xposed through Magisk. Then use MagiskHide to hide both root and Xposed from all Google apps and potential sources of conflict. If it's a software limitation/conflict, this may be a workaround.
Keep in mind that you will have to root your phone with Magisk rather than SuperSU or any other form of root.
Click to expand...
Click to collapse
FIY Magisk cannot hide Xposed...
I also facing these problem on my rooted Asus zenfone 2 (ze550ml 2gb ram version, Stock ROM, bootloader unlocked) and Asus Zenpad C 7 (p01y, stock rom, bootloader unlocked). The xposed firmware (version 86) is successfully install but can't install any apps from play store and using apk...
I really hope that dev team can solve it.....
Sorry for any grammatical mistakes....
The only way is to flash the firmware
I'm getting the same problem on my LG G4 with v88.2 of Xposed :/
I don't Know if this is too late,but I also have this problem. But there is a work around, go into the xposed installer and turn the switch off so its disabled on the next boot. rebot the device and exposed and its modules are disabled, allowing you to install apps from play store and downloaded .apk files... it would still be nice to install applications while its still on.
Sent from my LG-K550 using XDA Labs
I had this issue on my LGG3. This happens when you have Lucky Patcher enabled in your xposed modules. Disabling it (Lucky Patcher) should solve the problem.
Hey guys,
Just wanted to know how many of you ditched the Xposed on marshmallow for the latest 7.1.1 Android based oxygenos?
Since we don't know when nougat will be supported by xposed, is staying on marshmallow worth it?
Even though most of the modules I use are more or less esthetical, there's one thing I can't live without - youtube background playback and ad block.
Share your thoughts!
Xposed over any OS without Xposed. I have never even flashed Nouget because I know its just a waste of time for me. Ive been on cm13 since the day it came out. DEC 11 2016.
If all you need is the youtube modules, there's modded youtube apps out now with adblock and background playback. Check it out here.
I've also packaged the app in a convenient Magisk module, which you can find here.
It works exactly like the xposed-modified YouTube app, but it works on Nougat.
Anova's Origin said:
If all you need is the youtube modules, there's modded youtube apps out now with adblock and background playback. Check it out here.
I've also packaged the app in a convenient Magisk module, which you can find here.
It works exactly like the xposed-modified YouTube app, but it works on Nougat.
Click to expand...
Click to collapse
Hey Anova, what is this Magisk thingy you're talking about?
Also... For me The most important is gravitybox then come youtube modules and mock mock locations.
You think it's worth the upgrade? I personally never had a phone that would get updates so quickly or even at all. So I have no idea what to expect.. Would I have to reroot, reinstall recovery or it's all a piece of cake and only the exposed won't affect anything? Lemme know.
Crishien said:
Hey Anova, what is this Magisk thingy you're talking about?
Also... For me The most important is gravitybox then come youtube modules and mock mock locations.
You think it's worth the upgrade? I personally never had a phone that would get updates so quickly or even at all. So I have no idea what to expect.. Would I have to reroot, reinstall recovery or it's all a piece of cake and only the exposed won't affect anything? Lemme know.
Click to expand...
Click to collapse
Magisk is a framework that allows you to make temporary changes to your /system partition at boot, without actually modifying the partition. It works by superimposing user-defined changes to files in /system during boot; changes are reverted to their stock state afterwards. These user-defined changes are loaded into Magisk through Magisk modules. While a lot of people may think it's similar to Xposed, they're really nothing alike. I mentioned Magisk for the YouTube app because it is merely convenient. You could manually replace the YouTube APK in system without any additional software, but Magisk will do it for you while applying all the correct permissions, etc. As a bonus, Magisk also includes its own rooting method that works, for the most part, as well as SuperSU. This means that you can flash only Magisk to root your phone (flashing SuperSU is optional and is really based on personal preference, Magisk will work with SuperSU if you flash that first).
Because of what Magisk is and how it works, it is not able to modify your device in the same way that Xposed can. This means that mods like gravitybox and mock mock locations cannot be implemented with Magisk. Technically, all Magisk modules can be installed without Magisk by manually editing/replacing things in the /system partition. What is special about it is that Magisk does these things systemlessly, meaning that (with the proper configurations), you can modify /system without triggering safetynet.
For the modified YouTube app I was talking about, that was actually modded and compiled as a stand-alone APK by someone on XDA. It does not alter your current YouTube app, but rather outright replaces it.
As for upgrading to Nougat, it's really up to personal choice. I personally never used Xposed for anything other than YouTube Adaway and Background Playback, and to top it off I rarely use YouTube on my phone anyways so upgrading was an easy choice for me. If you do end up wanting to upgrade, do the following:
1) Download the full ROM of whatever version of OOS you want to use (4.1.0 is the latest, on Android 7.1.1). Do not use the "Upgrade Phone" option in settings if you are already rooted or have modified anything in your /system partition, as it will cause problems.
2) Flash the full zip in TWRP, wipe cache/Dalvik, then immediately flash the latest Magisk.zip (from the main Magisk thread on XDA)
3) Boot, then download Magisk Manager from the Play Store
At this point, Magisk will have been fully installed and your phone should be rooted. You can confirm through the Magisk Manager app
Anova's Origin said:
Magisk is a framework that allows you to make temporary changes to your /system partition at boot, without actually modifying the partition. It works by superimposing user-defined changes to files in /system during boot; changes are reverted to their stock state afterwards. These user-defined changes are loaded into Magisk through Magisk modules. While a lot of people may think it's similar to Xposed, they're really nothing alike. I mentioned Magisk for the YouTube app because it is merely convenient. You could manually replace the YouTube APK in system without any additional software, but Magisk will do it for you while applying all the correct permissions, etc. As a bonus, Magisk also includes its own rooting method that works, for the most part, as well as SuperSU. This means that you can flash only Magisk to root your phone (flashing SuperSU is optional and is really based on personal preference, Magisk will work with SuperSU if you flash that first).
Because of what Magisk is and how it works, it is not able to modify your device in the same way that Xposed can. This means that mods like gravitybox and mock mock locations cannot be implemented with Magisk. Technically, all Magisk modules can be installed without Magisk by manually editing/replacing things in the /system partition. What is special about it is that Magisk does these things systemlessly, meaning that (with the proper configurations), you can modify /system without triggering safetynet.
For the modified YouTube app I was talking about, that was actually modded and compiled as a stand-alone APK by someone on XDA. It does not alter your current YouTube app, but rather outright replaces it.
As for upgrading to Nougat, it's really up to personal choice. I personally never used Xposed for anything other than YouTube Adaway and Background Playback, and to top it off I rarely use YouTube on my phone anyways so upgrading was an easy choice for me. If you do end up wanting to upgrade, do the following:
1) Download the full ROM of whatever version of OOS you want to use (4.1.0 is the latest, on Android 7.1.1). Do not use the "Upgrade Phone" option in settings if you are already rooted or have modified anything in your /system partition, as it will cause problems.
2) Flash the full zip in TWRP, wipe cache/Dalvik, then immediately flash the latest Magisk.zip (from the main Magisk thread on XDA)
3) Boot, then download Magisk Manager from the Play Store
At this point, Magisk will have been fully installed and your phone should be rooted. You can confirm through the Magisk Manager app
Click to expand...
Click to collapse
Thanks for such a detailed description of everything! You're the best! I seriously decided to upgrade tomorrow.
Just last couple questions before I do... Should I delete anything? Like xposed itself with it's modules, or does the system upgrade wipe everything itself? Should I perform any backups other than usual titanium ones?
Thanks in advance
Crishien said:
Thanks for such a detailed description of everything! You're the best! I seriously decided to upgrade tomorrow.
Just last couple questions before I do... Should I delete anything? Like xposed itself with it's modules, or does the system upgrade wipe everything itself? Should I perform any backups other than usual titanium ones?
Thanks in advance
Click to expand...
Click to collapse
You should delete the Xposed modules prior to updating, as they are saved as user apps and will not be wiped with an upgrade. Delete the Xposed framework app as well for the same reason. Updating should erase all of the background stuff that the Xposed originally installed in /system. Take a nandroid prior to updating just in case.
Anova's Origin said:
You should delete the Xposed modules prior to updating, as they are saved as user apps and will not be wiped with an upgrade. Delete the Xposed framework app as well for the same reason. Updating should erase all of the background stuff that the Xposed originally installed in /system. Take a nandroid prior to updating just in case.
Click to expand...
Click to collapse
Thanks again, mate!
Is this the one I should download? https://forum.xda-developers.com/oneplus-3t/how-to/rom-oos4-0-nougat-op3t-leaked-t3523482
Crishien said:
Thanks again, mate!
Is this the one I should download? https://forum.xda-developers.com/oneplus-3t/how-to/rom-oos4-0-nougat-op3t-leaked-t3523482
Click to expand...
Click to collapse
Yes, that will work. OnePlus has not yet released the official zip through their website at this time, otherwise I would advise you to use the official zip.
Anova's Origin said:
Yes, that will work. OnePlus has not yet released the official zip through their website at this time, otherwise I would advise you to use the official zip.
Click to expand...
Click to collapse
Great, thank you. Imma let you know how it goes later today.
Anova's Origin said:
Yes, that will work. OnePlus has not yet released the official zip through their website at this time, otherwise I would advise you to use the official zip.
Click to expand...
Click to collapse
Not sure if I did anything wrong or I'm just impatient... But I flashed the update successfully and deleted dalvik. But got stuck at boot logo. Been hanging like this for 15 minutes, phone got hot and drained half its juice. So I reverted for now.... I'll try again at home with a charger... ?
954wrecker said:
Xposed over any OS without Xposed. I have never even flashed Nouget because I know its just a waste of time for me. Ive been on cm13 since the day it came out. DEC 11 2016.
Click to expand...
Click to collapse
what can xposed do that you actually need that you can't do with magisk?
EuEra said:
what can xposed do that you actually need that you can't do with magisk?
Click to expand...
Click to collapse
I don't think magisk can handle what xposed can handle.
954wrecker said:
I don't think magisk can handle what xposed can handle.
Click to expand...
Click to collapse
Indeed I will miss gravitybox. But if there is any other way to make my buttons do what I like which is (on the left - menu button with double tap for previous app/ home is home and recents on long press / right is back.)
Other than that it's all purely visual enhancement such as perfect color bar, media visualizer, and ****.
On the other hand I've just encountered a slight difficulty... Magisk won't work properly if I had Supersu previously installed, right?
Crishien said:
Indeed I will miss gravitybox. But if there is any other way to make my buttons do what I like which is (on the left - menu button with double tap for previous app/ home is home and recents on long press / right is back.)
Other than that it's all purely visual enhancement such as perfect color bar, media visualizer, and ****.
On the other hand I've just encountered a slight difficulty... Magisk won't work properly if I had Supersu previously installed, right?
Click to expand...
Click to collapse
What are you gaining if I may ask? I have never tried 7.0 or magisk because I see ZERO benefit and Id lose all my favorite modules.
954wrecker said:
What are you gaining if I may ask? I have never tried 7.0 or magisk because I see ZERO benefit and Id lose all my favorite modules.
Click to expand...
Click to collapse
That's what I wanna find out. I wanna see what's the new Android about. And I'm sure rovo will find a solution soon. And we will see xposed for nougat.
GravityBox is terrible and has slowed down every phone it's ever been put on (from my experience).
Xposed is a hack and it's shameful how it's holding back advancement.
Nougat > any hack
MattBooth said:
GravityBox is terrible and has slowed down every phone it's ever been put on (from my experience).
Xposed is a hack and it's shameful how it's holding back advancement.
Nougat > any hack
Click to expand...
Click to collapse
My phone is just as fast with xposed as it is without. All my apps work perfectly so I say any OS with Xposed is > Nougat
954wrecker said:
I don't think magisk can handle what xposed can handle.
Click to expand...
Click to collapse
Most of that is either completely unnessecary, pointless, or magisk can do it if people start developing for it. I have none of it (except no ads on youtube and the ability to turn off the screen) and i am completely fine. I think you tell yourself you need all that stuff but you actually don't, staying versions behind on the OS for it seems stupid.
954wrecker said:
My phone is just as fast with xposed as it is without. All my apps work perfectly so I say any OS with Xposed is > Nougat
Click to expand...
Click to collapse
Well that's your opinion and you're entitled to it, but I've noticed the total opposite across several devices. I always try Xposed on a new phone and I always massively dislike the way it works. Intercepting code that was not supposed to be intercepted just adds overhead. There's a good reason AOSP devs will refuse to look at any bug report that has Xposed in the logs.
EDIT:
Anyway, the battery savings from Nougat are too good to pass over. The only thing I need to customise on my phone is having the Google Dialer, and AdAway, whilst still keeping SafetyNet as passing, which Magisk does perfectly.
EuEra said:
Most of that is either completely unnessecary, pointless, or magisk can do it if people start developing for it. I have none of it (except no ads on youtube and the ability to turn off the screen) and i am completely fine. I think you tell yourself you need all that stuff but you actually don't, staying versions behind on the OS for it seems stupid.
Click to expand...
Click to collapse
Exactly, unless you use every setting on GravityBox then it's not entirely necessary, yet even if those functions are off or there are features of GravityBox you don't use, their code is still run. The bigger it gets the more the overhead there is. If you don't use, say, the network speed monitor, it's hook is still active. I could be wrong, but last time I dabbled with Xposed, this was the case.
If anything, smaller more granular modules would be better for GB. One module for network speed. One module for changing the on-screen buttons, etc. That way you only install modules that you use, rather than a whole library of them where you might only use 2-3 of the actual features.
I am a big idiot who can't follow directions I know and I will give many details so that someone may help me out of this situation.. please have patience.
I managed to unlock the bootloader, get custom recovery, and bypass dm verity on my new oneplus 3t a3000 running 4.5.1 stock. The issue is I rooted with supersu because that's what I'm use to and then flashed xposed into the system the old fashioned way (it's been a LONG time since I rooted and didn't really want to mess with magisk). I realize now that safety net has come to get me and I realized too late that magisk is superior.
I tried android pay and snapchat log in after rooting and flashing the 88.1 version of xposed framework and neither worked. I have everything almost but the safety net nonsense is annoying me because I use snapchat often but have to use another phone. I realize my stupid mistake in not flashing with magisk.
Besides being accustomed to supersu, you're wondering why I chose it and got xposed rather than magisk+ systemless xposed? I wanted to get certain modules such as youtube background playback and such quickly which I did but now I can't bypass safety net. I heard that even with safety net triggered, I could use Titanium Backup to move over a backed up version of snapchat that I had already logged in to my phone... problem is I had no backup and when I tried logging into my old rooted phones, snapchat refused to log in. I tried backing up snapchat on a non rooted phone through adb and moving that to the oneplus for Titanium Backup to restore but that didn't work.
So I guess my best bet is to disable root (uninstall supersu and xposed framework) and get magisk in replacement in hope that magisk hide works so I pass safety net then I can log in to snapchat and back it up. Can someone please guide me through the process? The amount I already know would imply I can figure this out but me trying to figure stuff out only caused much frustration today and yesterday.
In clarity, I want supersu gone (and xposed temporarily? I am not sure what is actually triggering snapchat to block me) and magisk in so I can pass safety net then I want (systemless xposed is what it's called? so I can add back my xposed modules). I am running blu spark twrp if that makes a difference.
Hugeee thanks to whomever can help me. Again I know I am dumb
If you want to pass safety net you will have to ditch xposrd all together. And magisk doesn't support bypassing safety net. It's one of those it may work but they are not making an active effort to get around it. Time is coming to make a choice. Mods or safety net.
Things triggering SafetyNet:
- root
- Xposed
- unlocked bootloader
- custom kernel (most of OP3/3T kernels already hide bootloader/kernel status)
- userdebug / dev-keys in build.prop
If you want to pass SN to log in to Snapchat, you have to remove root and Xposed, migrate to Magisk, log in to Snapchat and then install Xposed.
You can't use SN-enabled apps along with Xposed (although there is a module "No Device Check", which makes CTS return true, but for example Android Pay won't work still, because of basicIntegrity).
PS Look up iYTBP - this is a better version of YouTube with background playback built-in with no root needed.
Uninstall the xposed framework, login to snapchat and then reinstall xposed. You will have to repeat this process every time you logout, reinstall the app or clean flash a rom.
Edit- I see that you have supersu. I think you'll have to use magisk to pass safetynet.
At least 2 of my Apps refuse to start. One is my banking app and they do not offer any other way of interaction.
The problem is that the phone in fact is not rooted! It's just "OEM unlocked" to be prepared for root (which I need for E.g. titanium backup, but only maybe once a month).
Please give me a way out of this vicious circle!
I cannot remove the OEM unlock because it requires full wipe every time. Or is there a way?
Or what can I possibly tell the App Provider to improved their Code so that Oneplus phone state is being recognized (more) correctly?
Any help would be greatly appreciated.
Use Magisk I guess? Use it to hide root from that app.
Reeb_Lam said:
Use Magisk I guess? Use it to hide root from that app.
Click to expand...
Click to collapse
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?
ako673de said:
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?
Click to expand...
Click to collapse
You need to do some reading about Safetynet. If you're OEM unlocked you fail Verified Boot checks. Most custom Kernels include a bypass for this. Magisk alone should also work. I think you missed one important step:
Open Play Store Settings. Scroll down. It says 'Uncertified' at the bottom, right? Now install and set up Magisk. Go to system App Settings and clear Data and Cache for Play Store. Return to the Play Store Settings and scroll down. Now it should say 'Certified'. It might not be immediate, but it will happen. Now your Banking Apps work.
If you don't want, or have no luck with Magisk, simply flash a Custom Kernel that bypasses Verified Boot, and works with OOS.
Simple.
Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?
ako673de said:
Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?
Click to expand...
Click to collapse
Link to other Thread?
I don't know Magisk but are you hiding Root from your Banking App? Have you cleared Data and Cache for the Banking App since getting Certified?
First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?
ako673de said:
Any other idea?
Click to expand...
Click to collapse
Nope. If Play Store says Certified you should be good to go. I can only imagine it's a Magisk issue. Post screenshots of your config and let the Magisk experts pick through them. Maybe there's something not set up correctly.
ako673de said:
First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?
Click to expand...
Click to collapse
Hide Magisk Manager. I had to do that to get my banking app to work.
Edit: you may need to reboot after hiding Magisk Manager and clear you banking app's data before it works.
Sent from my OnePlus3T using XDA Labs
Thank you, indeed that WORKED! Well, at least for 2 out of 3 Apps. I think I can tell which one: "HVB banking". Maybe could somebody cross-check this one on his/her phone?
After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?
ako673de said:
After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?
Click to expand...
Click to collapse
Did you reflash custom kernel after update?
I'm not using any. What I did right after the update is to disable dm-verity (with a patched boot.img), like I did last time. But magisk is not yet re-installed because I wanted to see at least once the HypoVereinsbank App working, which it in fact does (different to last time when the phone was not rooted as well, and the store not certified!).
ako673de said:
But magisk is not yet re-installed
Click to expand...
Click to collapse
That's why... You can't pass the ctsProfile check if your bootloader is unlocked, and if you can't pass the ctsProfile check the Play Store won't be certified. You need Magisk for that...
Now I'm getting confused. The initial mail of this thread explains the situation as it was when I opened this thread:
--> Original ROM, no root, and banking apps didn't work <--
The advice to clear data of the PlayStore immediately brought the PlayStore back to "certified".
This is clearly in contrast to what you're saying now.
I can imagine only one reason: Maybe the older PlayStore had a bug and therefore was able to "certify" even with unlocked bootloader?
Sidenote: My main intention to do the firmware upgrade was that the "safety net checks" in Magisk suddenly stopped working one day (with the error message "invalid response", most probably you know what I'm talking about, I've read some comments from you on this issue). Therefore it's maybe really not too unlikely that Google has changed something very basic. Could you please confirm?
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).
ako673de said:
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/MagiskHide#hn_The_response_is_invalid
Sorry, now comes a probably often asked question: do I need the safetynet check option in magisk for something real? Or do the alternative apps fulfill all possible needs? What are these needs? Isn't that exactly what the PlayStore does to determine "certified"?
After quite some months of absolutely no "root" problems with any of my apps, since today o2banking again doesn't work.
I tried to update Magisk, but after update of the Magisk manager app to v7.1.1(203) it reports that Magisk is not installed at all, and any update of Magisk itself resulted in just the same. So I reverted back to v6.1.0(165) and everything seems to be okay, except that o2banking doesn't work. SafetyNet is clean, Magisk is hidden for o2banking and Magisk manager is repacked.
Does anybody know what the problem might be? Especially with that new version of the manager app, but also with Magisk v19.0 which cannot be installed from v6.1.0 (max. is v18.1). Any ideas welcome! I'm now on OOS 5.0.8 by the way.
SOLVED it myself: As mentioned somewhere in the update FAQ of Magisk there was a bug in manager v6.1.0 that causes the updated v7.1.1 to co-exist with the old version if the old version has been re-packed. If anybody encounters the same problem, the solution is at the bottom of this page: https://www.didgeridoohan.com/magisk/ManagerIssues.
o2banking will then still not work. Update to v19.0 is mandatory. But that is no problem then any more...
probably your banking app identified oxygen os as custom rom and have root. 1 out of 3 banking app in my phone doesn't work with lineageos even though i already hide magisk, but when running oxygen os with magisk hide, and also hide magisk manager (turn it on in magisk manager setting) all 3 banking app work just fine. maybe try sending a message to bank app developer to add oxygen os as exception.
Did you notice my edit? It was a problem with magisk manager update and magisk main version. Now everything is back up and running.
Hey, I rooted my phone just yesterday, and today I went to musescore just to see that they for whatever reason don't allow rooted phones to use their app?
So I tried enabling zygisk, DenyList, and I added musescore to the denylist and restarted my phone, but somehow musescore still knows that I'm rooted.
Is it possible that vbmeta is somehow related? if so then what file exactly am I supposed to flash as vbmeta (I use custom ROM).
If not, then what can I do to hide root from the app?
YayJohn said:
Hey, I rooted my phone just yesterday, and today I went to musescore just to see that they for whatever reason don't allow rooted phones to use their app?
So I tried enabling zygisk, DenyList, and I added musescore to the denylist and restarted my phone, but somehow musescore still knows that I'm rooted.
Is it possible that vbmeta is somehow related? if so then what file exactly am I supposed to flash as vbmeta (I use custom ROM).
If not, then what can I do to hide root from the app?
Click to expand...
Click to collapse
After force deny list did you've deleted caches of google play and google services and reboot? check also google play store inside settings if certified, if certified then it should work for your app too.
Maybe try installing Universal SafetyNet Fix?
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
And some applications can be extra finicky. LIke for me, Google Pay always takes its time to get persuaded about not being rooted. Also there might be other components either of this app or for system apps that might need hiding. I would generally try following guides for making banking apps work.
YayJohn said:
Hey, I rooted my phone just yesterday, and today I went to musescore just to see that they for whatever reason don't allow rooted phones to use their app?
So I tried enabling zygisk, DenyList, and I added musescore to the denylist and restarted my phone, but somehow musescore still knows that I'm rooted.
Is it possible that vbmeta is somehow related? if so then what file exactly am I supposed to flash as vbmeta (I use custom ROM).
If not, then what can I do to hide root from the app?
Click to expand...
Click to collapse
I'm not familiar with that app, but I know that some apps also check for the presence of the Magisk Manager app. If you've already tried Zygisk and the deny list, then another thing to do would be to hide the Magisk app. It the Magisk Manager, go to Settings > Hide Magisk app.
What worked for me is installing Insular ( from Fdroid) and then clone the App that complains about root to the work environment.
I just downloaded musescore and installed it. It hasn't detected root on my phone. I use Shamiko to hide root. Get Fox's magisk module manager from fdroid. Then use it to install Shamiko. Make sure you turn off Enforce Denylist in magisk so Shamiko can enforce the deny list. Hide the magisk app using the feature in magisk. It works for me.
YayJohn said:
Hey, I rooted my phone just yesterday, and today I went to musescore just to see that they for whatever reason don't allow rooted phones to use their app?
So I tried enabling zygisk, DenyList, and I added musescore to the denylist and restarted my phone, but somehow musescore still knows that I'm rooted.
Is it possible that vbmeta is somehow related? if so then what file exactly am I supposed to flash as vbmeta (I use custom ROM).
If not, then what can I do to hide root from the app?
Click to expand...
Click to collapse
Oh yes I can't seem to open musescore too even with safety net pass. But it is because I am using MicroG. I tried it on my other phone with Play Services and it works fine with hidden root (shamiko and magisk disabled) and safety net pass.
BigChungus321 said:
Oh yes I can't seem to open musescore too even with safety net pass. But it is because I am using MicroG. I tried it on my other phone with Play Services and it works fine with hidden root (shamiko and magisk disabled) and safety net pass.
Click to expand...
Click to collapse
I use MicroG as well. I can load the app and use it, I just can't subscribe because it requires GSF to make payment.
IrishJames said:
I use MicroG as well. I can load the app and use it, I just can't subscribe because it requires GSF to make payment.
Click to expand...
Click to collapse
You can open it right? But can you select and open a random piano piece or something like that. For me, the piece loads up then detects something (root, safety net idk) then just tells me I can't for root reasons. I tried using shamiko too and all the root hiding methods I know and I still couldn't open a piece. It does load the main menu for me too on MicroG+patch playstore but can't open the contents.
It's been roughly a month. Has anyone found a fix for this issue yet? There was discussion about the issue here where a dev 'fixed' the app for someone with a rooted phone. However I cant tell what the dev did because all his messages are deleted, for all I know he could of shared an apk or something, guess I'll never know. I've decided to try to get in contact with one of the people whose issue managed to get fixed, although I don't know if he'll ever respond. Apparently in the forum, he told the dev that he assumed the block was intentional. Maybe this could hint us towards a fix because maybe the block doesn't target rooted users?
BigChungus321 said:
I tried using shamiko too and all the root hiding methods I know and I still couldn't open a piece.
Click to expand...
Click to collapse
If thats the case then perhaps the app isin't checking for root? Theres no way musescore has more sophisticated anti-root software than some banking apps out there. Perhaps it's detecting the os that the user uses instead? I can confirm this because my samsung s7 edge with the same lineage os version as my Xiaomi doesn't want to play any scores either. This issue also happens to people who have no custom rom or even no root, it has to do with the os that you use rather than being an issue with root.
So what, did I type 2 paragraphs on a one month old forum just to rant? No. I will find the issue (well, I already found the reason in the text above), and I will try to fix it, not by making any workarounds such as cloning the app but getting the app to reliably work on a rooted / custom rom phone.
EDIT: Maybe using something to spoof the OS to make apps think it's a different OS?
POTENTIAL FIX: So in new versions of magisk, the developer decided to remove magiskhide. Turns out that having magiskhide turned on makes musescore actually be able to function. I tested this on my samsung s7 edge (didn't want to brick my Xiaomi phone by accident just yet and it worked. However I labelled this 'POTENTIAL' as downgrading magisk isin't really a plausible fix and could still be considered a workaround.
RoboNinjaR said:
It's been roughly a month. Has anyone found a fix for this issue yet? There was discussion about the issue here where a dev 'fixed' the app for someone with a rooted phone. However I cant tell what the dev did because all his messages are deleted, for all I know he could of shared an apk or something, guess I'll never know. I've decided to try to get in contact with one of the people whose issue managed to get fixed, although I don't know if he'll ever respond. Apparently in the forum, he told the dev that he assumed the block was intentional. Maybe this could hint us towards a fix because maybe the block doesn't target rooted users?
If thats the case then perhaps the app isin't checking for root? Theres no way musescore has more sophisticated anti-root software than some banking apps out there. Perhaps it's detecting the os that the user uses instead? I can confirm this because my samsung s7 edge with the same lineage os version as my Xiaomi doesn't want to play any scores either. This issue also happens to people who have no custom rom or even no root, it has to do with the os that you use rather than being an issue with root.
So what, did I type 2 paragraphs on a one month old forum just to rant? No. I will find the issue (well, I already found the reason in the text above), and I will try to fix it, not by making any workarounds such as cloning the app but getting the app to reliably work on a rooted / custom rom phone.
EDIT: Maybe using something to spoof the OS to make apps think it's a different OS?
Click to expand...
Click to collapse
Its not opening for me because I'm using MicroG. Like banking apps, MuseScore checks for specific Play Services version. Since microg uses idk android4.4 play services, it will fail to load any Banking Apps or apps of the same kind that uses that check regardless of root 'cause that version's too old and a potential for security. For the OS check, I guess it does check it too. I tried on two emulators and both failed to load a piece as well (might be because of safetynet cuz emulators can't pass it). There are xposed and magisk modules that can spoof OS and even prevent the app from seeing user installed apps. I haven't tried that method because I switched ROM now and got MuseScore working fine even without hiding root.
BigChungus321 said:
Its not opening for me because I'm using MicroG. Like banking apps, MuseScore checks for specific Play Services version. Since microg uses idk android4.4 play services, it will fail to load any Banking Apps or apps of the same kind that uses that check regardless of root 'cause that version's too old and a potential for security. For the OS check, I guess it does check it too. I tried on two emulators and both failed to load a piece as well (might be because of safetynet cuz emulators can't pass it). There are xposed and magisk modules that can spoof OS and even prevent the app from seeing user installed apps. I haven't tried that method because I switched ROM now and got MuseScore working fine even without hiding root.
Click to expand...
Click to collapse
Weird. I have microG and I managed to get musescore working without switching roms. All I did was use safety net fix, enabled zygisk and added it to the deny list. Tried it before and it didn't work, probably because I didn't install safetynet fix. Who knows, maybe it's related to what type of GApps you install. I guess this issue is fixed for now.