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 tried to install Gcam on Mi A1 , but unfortunately the installation shows "app not installed"
the following are the steps i did. pls point out if i missed any.
1. unlocked bootloader
2.Root and installed Magisk without installing TWRP (used TWRP by booting )
3. downloaded and installed Gcam using Magisk (inside downloads)
-didnt showed any new gcam icon, also tried in the stock camera
The stock camera takes longer to start. (noticed every time).
So i tried to install Gcam apk by scrubber.
Installation shows (App not installed)
Even tried to enable camera2api using build prop and install gcam. No luck
Now the issue is the camera ( stock , and all other camera apps) taking longer to start and Gcam not installed.
any guess what went wrong ?
I hope Twrp was not the issue coz i didnt installed it.
will unrooting and relocking makes camera fast again
Search in Magisk the Module: MI A1 Camera Lag Fix Oreo.
And that's it. The problem it's with SELINUX.
Set selniux to permissive. There is a magisk module for it.
Angrydr0id said:
Search in Magisk the Module: MI A1 Camera Lag Fix Oreo.
And that's it. The problem it's with SELINUX.
Click to expand...
Click to collapse
thanks alot man.
but does this setting selinux permissive have aany draw back. Sorry if my question is noob
karthi2 said:
thanks alot man.
but does this setting selinux permissive have aany draw back. Sorry if my question is noob
Click to expand...
Click to collapse
Nah, don't worry about it.
I'm running AospExtended-5.8, no Gapps installed and Xposed/FakeGapps, with microG.
From what I've read Xposed needs to be either uninstalled or disabled, so I disabled it, unchecked FakeGapps, and rebooted.
SafetyNet is enabled in microG and 'Use Offical Server'.
When I try to do a SafetyNet check in Magisk, I get a popup saying Magisk has stopped.
I have two different model phones, and each one does the same thing, running different versions of Magisk and different ROMs. I don't know why Magisk keeps stopping running the SafetyNet check?
I hope someone knows how to work this out?
Thanks
DoR3M3 said:
I'm running AospExtended-5.8, no Gapps installed and Xposed/FakeGapps, with microG.
From what I've read Xposed needs to be either uninstalled or disabled, so I disabled it, unchecked FakeGapps, and rebooted.
SafetyNet is enabled in microG and 'Use Offical Server'.
When I try to do a SafetyNet check in Magisk, I get a popup saying Magisk has stopped.
I have two different model phones, and each one does the same thing, running different versions of Magisk and different ROMs. I don't know why Magisk keeps stopping running the SafetyNet check?
I hope someone knows how to work this out?
Thanks
Click to expand...
Click to collapse
Because of Google have changed the SafetyNet api
Old safetynet check won't work at the time of this comment.
topjohnwu already have fixed SN check u have to wait until new version of magisk release or u can install unofficial magisk version from this developer
Link : https://github.com/ianmacd/MagiskBuilds
Actually since I don't have Gapps installed, that means no Play Services, I was told that's the problem and Magisk should of given me a message saying this...
As in the title i haven't seen talk about Arcore in a long time. And i just wanted to ask if anyone has tried the method successfully here: https://www.celsoazevedo.com/files/android/google-camera/ar/
It describes 2 different ways (both require magisk). Both ways are changing the fingerprint to match that of a compatible arcore device (like google pixel 2).
So was anyone successful getting it to work with those methods?
Did you try it? Just saw there is an update for the magisk module
I installed it a few weeks ago. It worked, but after a while the stickers became sticky. It worked again after a restart of the phone.
I don't know why but my phone always gets in a boot loop after installing custom roms.I think the main culprit is the android secure boot/dm verity. Tried all ways mentioned in internet but it didn't work. So any help on how to disable it would be great.