So i got my OnePlus 2, rooted it, flashed xposed framework, installed it, and then got xposed gels from playstore. Activated the module and then rebooted. Launched XGELS and i get a massage saying:
"Lucky Patcher is installed on your device. This will break the Google InApp-Billing service and therefore your purchase can NOT be verified nor can you purchase XGELS Premium. Please disable 'Billing emulation' and uninstall Lucky Patcher. If the issue persists flash your ROM and GAPPS again."
But the thing is, I never installed Lucky Patcher. I didn't even know about it until this error came up. It's a new phone that i haven't even used yet. Now XGELS is not working. All I can do is remove the google search bar from homepage, that's it. I can't even resize icons or change the grid. Nothing's working.
Please help?
It happends to me too and, as I read, to many more people.
Seems to be a OxygenOS thing.
Same issue on Hydrogen OS as well.
Related
So few apps I have do not want to activate their premium features as they claim I have a and I quote "Lucky Patcher" installed on my system.
It asks me to disable "Billing Emulation".
I know what Lucky patcher is and I do not have it. Is that normal for Oxygen OS?
I have
LG V20 H990DS, rooted, TWRP installed, custom kernel (as per dirtysanta post), xposed installed
Since installing xposed (might be coincidental) I can not install any app (either via Play Store or adb install. The error I get in logcat is:
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION: Failed reading classes.dex in [email protected]: META-INF/MANIFEST.MF has invalid digest for classes.dex in classes.dex]
I posted this in the n00b-friedly Q&A forum and someone suggested it was an issue with signatures, so I googled and there are ways to disable signature verification. Not sure if this is a wise thing to do, but I think i need to try. The problem is the solutions all require Lucky Patcher or some Xposed app. But I can't install any app.
So, knowing I am falling for the whole XY Problem, can anyone suggest a way of disabling signature verification (or indeed solving the actual problem) without re-flashing everything again. I am thinking of some V20-compatible flashable zip or something maybe???
In my opinion I would suggest to reflash, stay with stock kernel with Xposed. You don't want to go through all of this just to install an app when clearly something you flashed isn't working right
Right, I have been experimenting with all sorts to avoid reflashing but nothing worked so I reflashed, and... still not working.
Any other ideas?
interruptingcow said:
Right, I have been experimenting with all sorts to avoid reflashing but nothing worked so I reflashed, and... still not working.
Any other ideas?
Click to expand...
Click to collapse
When you mean reflashed, do you mean dirty or clean installation?
Still_living714 said:
When you mean reflashed, do you mean dirty or clean installation?
Click to expand...
Click to collapse
dirty. Am just preparing all the files now for a clean install which is only option left available as far as I can see. I wonder if a different kernel would help?
I have an update on this.
I did a totally clean wipe and re-root, which in itself had issues but eventually worked. All was working fine right up until I installed modded google play. Since then I get the same issue as mentioned. I uninstalled it and reverted to normal googple play but I still get the error. I guess I have sort of found the issue, and next time I won't install it.
So, any ideas on
1. Why I am getting the issue?
2. How to fix it without going through the re-root.
Thank you.
interruptingcow said:
I have an update on this.
I did a totally clean wipe and re-root, which in itself had issues but eventually worked. All was working fine right up until I installed modded google play. Since then I get the same issue as mentioned. I uninstalled it and reverted to normal googple play but I still get the error. I guess I have sort of found the issue, and next time I won't install it.
So, any ideas on
1. Why I am getting the issue?
2. How to fix it without going through the re-root.
Thank you.
Click to expand...
Click to collapse
I've had the same problem installing Modded playstore. For some reason Modded playstore works on all my devices except my V20. I would suggest giving up installing it as I did. Also why would you have to reroot?
Also why would you have to reroot?[/QUOTE said:
Because that is the only way I have found to be able to install any new apps. Otherwise I get errors similar to
PackageInstaller: Commit of session 1370272024 failed: Failed reading classes.dex in [email protected]: META-INF/MANIFEST.MF has invalid digest for classes.dex in classes.dex
Click to expand...
Click to collapse
Well I found the solution and a way of installing modded google play. Although I don't really understand the reason. As I was going to wipe the phone anyway I thought I would play around. So...
I tried to install modded google play - still same issue
From Lucky Patcher I removed patches from core.jar - suddenly I could install apps again.
I successfully installed modded google play - this needs Signature Verification True
I patched Signature Verification - modded google play works and I can install apps
So the issue was with the Lucky patcher "Disable .apk Signature Verification". When patched I got the dex error from my post. With it unpatched all works fine.
Thanks for all who helped.
does this still work? I seem to always end up with playstore not functioning correctly, shows as though the applications I purchased as not purchased; and in-app purchase emulation doesn't function?.... not sure if I'm following your instructions on removing core.jar but I tried removing it and instaling core patch to disable signiture verification through edxposed but I'm not sure???
Yes it still works fine. IAP and everything works as normal.
Lucky patcher -- Patch to Android -- Remove all patches from core.jar
Lucky Patcher -- Patch to Android -- Signature Verification status always True
Lucky Patcher -- Patch to Android -- Disable .apk signature verification
Lucky Patcher -- Patch to Android -- Disable Signature Verification in the pacvkage manager
interruptingcow said:
Yes it still works fine. IAP and everything works as normal.
Lucky patcher -- Patch to Android -- Remove all patches from core.jar
Lucky Patcher -- Patch to Android -- Signature Verification status always True
Lucky Patcher -- Patch to Android -- Disable .apk signature verification
Lucky Patcher -- Patch to Android -- Disable Signature Verification in the pacvkage manager
Click to expand...
Click to collapse
thanks for the reply and instructions...... I managed to get lp working(emulation and all) using either corepatch or the module for magisk.... but there's still something funky that either stops stuff from installing off playstore and/or not as apk's without resigning them; will try this method and see how it does in comparison....... unrelated question, any clue if m3u's work at all or if there's a method to get them to open in music players?(not sure if user issue or device issue)
Sorry I don't use m3u so I do not know.
I have a rooted LG Stylo 2 Plus (T-Mobile model). I recently encountered a problem where when I sideload some apks I get "App not installed. The package appears to be corrupt" and when downloading and then installing apps through the Google Play Store, I would get error 507. The apk work on other devices, and some apk will install, but there is other ones I need to install. I have tried clearing the cache of the package installer and Google play store and services. What should I do?
I have the exact same problem, same model (lgms550) running 7.0 (rooted, twrp and supersu, otherwise stock). Mine initially started when I installed xposed. When I flashed the uninstaller zip the package installer worked again (for a while...) Now every package throws "appears corrupt" and Playstore gives the 507 error. I've transferred the apps to my other phone (gs5) and they install fine so they're not bad downloads. Frankly I'm stumped and after hours of combing google for answers this is the first post that matches and oddly it's the same device. Maybe it's the ms550?
Fixed this by reflashing system from twrp.
First off, I feel it necessary to say WITHOUT THE CREW WORKING ON TWRP THERE WOULD HAVE BEEN DOZENS OF ANDROIDS BEING USED FOR SKEET SHOOTING BY MYSELF! A huge thanks. Thank God I took the time to do a quick backup with twrp before starting anything stupid. I still am unsure as to the original cause, it was only noticed after installing xposed but I've done any number of changes to this phone. If needed i can reset, make a backup, and upload for flashing in twrp for whoever wants it.
Seems like I had same or close to same with my T-Mobile Stylo 2 plus. (now unlocked on metro PCS)
A while back I had a weird issue where my default package installer would not install qpks. I downloaded another app from playstore and worked fine. I didn't pay much attention to it as I resolved the issue using a different app to install qpks.
Sent from my ph2n using XDA Labs
SM210 said:
Seems like I had same or close to same with my T-Mobile Stylo 2 plus. (now unlocked on metro PCS)
A while back I had a weird issue where my default package installer would not install qpks. I downloaded another app from playstore and worked fine. I didn't pay much attention to it as I resolved the issue using a different app to install qpks.
Sent from my ph2n using XDA Labs
Click to expand...
Click to collapse
I've traced the problem to having Mod Edit: warez installed. Seems the issue has been resolved with updates to Mod Edit: warez. The problem persisted even when using another app to install.
Hello,
I'm experienced a weird bug - when installing an APK file the phone hangs and I need to force restart it. After restarting the phone and trying to open the app being updated - a crash occurs. The update process is seemingly corrupting the app as I need to uninstall it and install again to make it work, making the associated data gone. It is frustrating, because it happens like I'd say 50/50 of times.
Happens while installing an app manually and using root in Yalp. Play Store not tested as it is not present on the phone.
The setup is Xperia X compact running latest .118 Oreo with microg, no GAPPS, Magisk, official Xposed 90 beta3,
Xposed modules: BatteryCare+, FakeGAPPS, GravityBox, XposedGmsCoreUnifiedNlp, XPrivacyLua
It did happen on Xperia X and Xperia XZ with similar setup on Oreo. I wonder if it might be caused by Xposed bundled with Xperia Software?
Actually I'm facing similar issue. I concluded it's caused by Xposed and certain modules. In fact, it's a known issue of Xposed for Oreo. According to rovo89, existing Xposed has problem with ART in Oreo.
As a workaround, now whenever I need to install/uninstall anything, I disable Xposed in Magisk first.
https://github.com/rovo89/Xposed/issues/325
Thank you @itandy for replying. Have you tried installing EdXposed instead of the regular Xposed?
Well it is basically for Pie but it is supposed to work on oreo too. Whenever I tried to install it on X compact running Oreo I got bootloop.
I have found that only some apps installation would cause a freeze and reboot. But your solution is safer of course.
Vixificent said:
Thank you @itandy for replying. Have you tried installing EdXposed instead of the regular Xposed?
Well it is basically for Pie but it is supposed to work on oreo too. Whenever I tried to install it on X compact running Oreo I got bootloop.
I have found that only some apps installation would cause a freeze and reboot. But your solution is safer of course.
Click to expand...
Click to collapse
Unfortunately EdXposed doesn't work last time I tried. It fails to boot at all.
I've installed adaway from f-droid.
Now I find that it gives the message "Update available", I can download the update but it fails to install, gives message "App not installed"
And not only does this happen om my s6 lite, it also happens on my Moto g7 plus. and my wifes Moto g5s
All have magisk, on the s6 with systemless host enabled.
I've tried complete removal and reinstall, no difference.
Do any of you have the same behaviour?
Yes, same for me with Pixel 5 and Magisk. Been happening the last couple days. Everything else seems to be working fine.
Do you know if they changed the package name? This can happen if the package name is changed in the app store, but the system package name is the old one. The solution would be to uninstall the current APK on the system and then install the new version from the app store.
Uninstalling and reinstalling didn't work. However, I noticed the version in f-droid was 5.1.0 from 2 months ago, but the latest release on github was 5.2.1 and it said it fixed something with the f-droid store. So I uninstalled again, then downloaded the apk from github and installed that. Everything is working fine and no update anymore.
Thanks guys. My wife's phone was updatet today but mine refused.
Then just now, after updating f-droid it updated from f-droid where before I tried updating from within adaway.
And s6 is ok now too!