Database Users

[Q] My Epic4G w/Syndicate Frozen keeps getting Swype/MMS errors

Many months back I did my first rooting of my Epic 4G and I installed the Syndicate Frozen Rom version 2.1.1. Kernal version 2.6.32.9 and Build number Twilight Zone v1.1.1 - Hajime-taisho.
Lately I get this when the phone rebooted:
su binary outdated
When I tried to update it says the updater is incapable of updating my binary since it is installed in /sbin.
That was fine for a while but a few days later I am getting all these popups that say "Sorry! The application Swype (process com.swype.android.inputmethod) has stopped unexpectedly. Please try again. Then gives a force close button.
The MMS process also pops up and several others. I cleared some of the caches last night like I read to do here and it worked over night but this morning it is back and making the phone unusuable.
Tried to go to into CMR and clear the caches there and reboot but that didn't help.
Any ideas of what I can do? Can I reflash the rom without losing all my data?
Thanks for any help you can provide.
Note: Also getting this gapps error. And the phone is just rebooting on its own.

You need to upgrade to the newer superuser. Maybe try going to the market and getting it, or someone here may have the apk for you.

Went to the Market and downloaded the SuperUser Update Fixer and it said it didn't have anything to fix. I updated Superuser, ran the update fix and I am still getting that su binary outdated message. And my phone keeps rebooting.
Another error I am getting is an "acore" process needing a force close too.

Did you clear data in Google Framework Services?
Sent from my SPH-D700 using XDA App

kennyglass123 said:
Did you clear data in Google Framework Services?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Thanks just tried that but still not working. Getting all these force stop windows from acore to mms to gaaps and swype and then it reboots.

Then you are left with Factory data reset and restoring apps from the mrket so you don't restore any corrupted data. Make sure when you get a good working phone again to flash the journal on script.
Sent from my SPH-D700 using XDA App

Hmmmm. OK. Should I do a backup in CMR? I am in the process of doing a Titanium backup right now.
Do you think I should update the ROM or just reflash the one I had before?
Not sure what flash the journal on script is.

ryan4sc said:
Hmmmm. OK. Should I do a backup in CMR? I am in the process of doing a Titanium backup right now.
Do you think I should update the ROM or just reflash the one I had before?
Not sure what flash the journal on script is.
Click to expand...
Click to collapse
Your choice but updated rom* never hurts ..
*/ F u autocorrect

Something had to be corrupted. I flashed Syndicate Frozen ROM 1.2 and a new kernal and was still getting those errors. So I had to do a backup, wipe the phone and then reinstall and that fixed everything. I reinstalled most of the apps and so far no more errors. Thanks for the help!

4.1.2 update fails

My wife's nexus 7 won't update to 4.1.2. I wasn't paying attention to it, just noticed today she is still on 4.1.1. I keep going to update after stopping and clearing the Google services framework and I keep getting the red triangle. The error says assert failed... no app is listed, but it does say tegra 3 in the long error message.
More info:
Bone stock, never been rooted.
I have wiped cache.
I do NOT want to do a factory reset as she has stuff everywhere.
I am guessing I will have to load the update from the Google servers, but even then it might fail.
Of course I have done a Google search and got nothing useful other than to root and load a Rom. This is not mine and I am frequently gone, don't want to root it or anything as I am rarely home to fix any issues.

Could you please share the exact error here? It will be much easier to find a solution to the problem once we see what the error is.
Sent from my Nexus 4

Here is the messages during the update:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
Assert failed: apply_patch_check("Emmc:/dev/ block/ platform/sdhci-tegra.3/by-name/lnx:5007360:089ca623419a5766da5b95b17352cffcbf1c610:5013504:c48f8e86c73fb2c2ba1794f5ec98e27c9e206ed5")
Installation aborted.

That error means that the update was attempting to patch the kernel and failed. That is very strange if the device has not been modded at all.
Has the bootloader been unlocked?
Sent from my Nexus 4

Ya positive its never been unlocked. And I know it is still locked as one of the screens I went into last night showed this.
After sleeping on it, I got to thinking I can probably just call Google for tech support. This is actually a legit issue I didn't cause by playing with it! For once. Lol

Okay, I called Google and they just told me to do what I did, which of course wasn't helpful. They said to do a factory reset, which didn't work. I tried to do the following update to 4.1.2, and that had the same error:
http://www.youtube.com/watch?v=PwlXQoAzrBE
I am still on 4.1.1 build JRO03S. I am trying to do this without root but clearly I can sideload files with adb. I read someone else had the same problem but the display was changed from 213. My bootloader is locked and everything, so no root, not sure how mine could have been changed.
Anyone know how to manually update to 4.1.2 without root? (other than the instrucitons above, I see there is more than one version of 4.1.1, so maybe I used the wrong update file when I manually tried).
Please help!!!
Thanks

Use wugs toolkit to unlock boot loader, then reflash your nexus with the update you want. Once that finishes simply relock the boot loader. I had your same problem. Just make sure to use wugs to backup as boot loader unlocks wipe the device.
Sent from my Nexus 7 using Tapatalk HD

Getting error msg with latest verizon update

After i read that you could keep root with the latest update i gave it a try. Im just rooted with stock recovery. I deleted some bloatware and installed hide soft keys was all i did. I downloaded the update and when it went to install i get an error msg. Message was er: 0x1117008. Then would reboot and a message would pop up saying was a problem during installation, no changes were made. I have since restored all the bloat i deleted thinking that may help, tried again and get same message. Anyone have an idea what it may be?

jmickel99 said:
After i read that you could keep root with the latest update i gave it a try. Im just rooted with stock recovery. I deleted some bloatware and installed hide soft keys was all i did. I downloaded the update and when it went to install i get an error msg. Message was er: 0x1117008. Then would reboot and a message would pop up saying was a problem during installation, no changes were made. I have since restored all the bloat i deleted thinking that may help, tried again and get same message. Anyone have an idea what it may be?
Click to expand...
Click to collapse
Not sure, but you may have to unroot first to install the update. What they probably meant by you can keep root is that they didn't patch it to prevent root. So, once you unroot, install update, then you can reroot again. Just my guess.
Sent from my LG-G2 using Tapatalk

jmickel99 said:
After i read that you could keep root with the latest update i gave it a try. Im just rooted with stock recovery. I deleted some bloatware and installed hide soft keys was all i did. I downloaded the update and when it went to install i get an error msg. Message was er: 0x1117008. Then would reboot and a message would pop up saying was a problem during installation, no changes were made. I have since restored all the bloat i deleted thinking that may help, tried again and get same message. Anyone have an idea what it may be?
Click to expand...
Click to collapse
I get the same error. Any update?

You'll need to restore all bloat. Pretty much need to be completely stock before updating. I was rooted with tethering provisions removed and Stock LG Browser installed. I has to fix the provisioning and remove the Browser (also adding any system/app files I removed) before the update was successful.

Kaiken said:
You'll need to restore all bloat. Pretty much need to be completely stock before updating. I was rooted with tethering provisions removed and Stock LG Browser installed. I has to fix the provisioning and remove the Browser (also adding any system/app files I removed) before the update was successful.
Click to expand...
Click to collapse
i'm am getting this same error and i have restored all bloat and even temporarily unrooted using Voodoo's OTA RootKeeper. i dont know what else to do at this point. any thoughts/suggestions?

brianj320 said:
i'm am getting this same error and i have restored all bloat and even temporarily unrooted using Voodoo's OTA RootKeeper. i dont know what else to do at this point. any thoughts/suggestions?
Click to expand...
Click to collapse
Have you restored your hide nav keys? You can also download a completely stock rooted rom somewhere on here and make sure your system apps are the same. I had to do this to find my BrowserProxyProvider.apk/odex I accidentally deleted and pushed them back into system/app.

Apk Parse Error

Bear with me here, tis a long and windy tale!
I'm getting a "Parse Error: there is a problem while parsing this package" whenever I try and install an apk copied to my phone.
Used to work fine until the following:
Have a Galaxy S5, SM-G900F.
Came with carrier firmware when I got it last year, flashed stocked btu, rooted with towelroot, and updated it to 4.4.2
Worked like a charm.
With EE now offering Wifi-Calling, decided to update to lollipop, and that's were **** started to go wrong.
Looked into this, and discovered that FlashFire would keep the root, and update to a newer fimware.
Using the stock btu, did it. Everything went great.
Couldn't find the wifi-calling option
Read up about it a bit more, some places said needed to clear the cache.
Did so, nope.
Tried a deodex firmware: http://forum.xda-developers.com/galaxy-s5/development/rom-t3078179
Still no luck.
Then I came across EE support forums, which said it had to be carrier firmware, to use wifi-calling.
Grabbed the latest version, Used Flashfire to flash it.
Encountered a ton of errors.
Constant "system ui has stopped working" "weather ui has stopped working" errors.
Tried clearing the cache again, no luck.
Didn't factory reset at this point, and probably where I made another mistake.
Flashed it back to ambadasii, decided to follow some instructions by clearing the davlik cache. Bad choice :crying:
Flashed twrp, forgetting that this would trip knox. :silly:
Cleared cache, cleared davlik. Still no luck.
At this point, with knox tripped, there was nothing really stopping me.
So used odin to flash the EE evr firmware to the phone.
Same "ui has stopped working" errors.
Cleared cache, reset to factory default.
All errors stopped.
And finally have the Wifi-calling option (f*cking yay )
Flashed twrp again, installed SuperSu to root it.
And now busy using Titanium backup to restore my apps and settings.
Tl:dr Wanted the new wifi-calling option on lollipop, got impatient and screwed something up during flashing.
Thanks for reading this far!
Edit: Forgot to mention.
Yes it used to install apk's from the phone and sd card perfectly fine before.
Yes usb debugging and allow unsigned apps are both on.
Apk is fine, installs on my nexus tablet fine (5.1)

amaru007 said:
Bear with me here, tis a long and windy tale! [emoji14]
I'm getting a "Parse Error: there is a problem while parsing this package" whenever I try and install an apk copied to my phone.
Used to work fine until the following:
Have a Galaxy S5, SM-G900F.
Came with carrier firmware when I got it last year, flashed stocked btu, rooted with towelroot, and updated it to 4.4.2
Worked like a charm.
With EE now offering Wifi-Calling, decided to update to lollipop, and that's were **** started to go wrong.
Looked into this, and discovered that FlashFire would keep the root, and update to a newer fimware.
Using the stock btu, did it. Everything went great.
Couldn't find the wifi-calling option
Read up about it a bit more, some places said needed to clear the cache.
Did so, nope.
Tried a deodex firmware: http://forum.xda-developers.com/galaxy-s5/development/rom-t3078179
Still no luck.
Then I came across EE support forums, which said it had to be carrier firmware, to use wifi-calling.
Grabbed the latest version, Used Flashfire to flash it.
Encountered a ton of errors.
Constant "system ui has stopped working" "weather ui has stopped working" errors.
Tried clearing the cache again, no luck.
Didn't factory reset at this point, and probably where I made another mistake.
Flashed it back to ambadasii, decided to follow some instructions by clearing the davlik cache. Bad choice :crying:
Flashed twrp, forgetting that this would trip knox. :silly:
Cleared cache, cleared davlik. Still no luck.
At this point, with knox tripped, there was nothing really stopping me.
So used odin to flash the EE evr firmware to the phone.
Same "ui has stopped working" errors.
Cleared cache, reset to factory default.
All errors stopped.
And finally have the Wifi-calling option (f*cking yay )
Flashed twrp again, installed SuperSu to root it.
And now busy using Titanium backup to restore my apps and settings.
Tl:dr Wanted the new wifi-calling option on lollipop, got impatient and screwed something up during flashing.
Thanks for reading this far!
Edit: Forgot to mention.
Yes it used to install apk's from the phone and sd card perfectly fine before.
Yes usb debugging and allow unsigned apps are both on.
Apk is fine, installs on my nexus tablet fine (5.1)
Click to expand...
Click to collapse
Open/install terminal emulator and do "pm install /path/to/application.apk", it will give you aore detailed error about whats going wrong.
Sent from my Tw5ted SM-G900A using Tapatalk

Tried that, and got the following error: Error: java.lang.SecurityException: Neither user 10312 nor current process has android.permission.INSTALL_PACKAGES.

amaru007 said:
Tried that, and got the following error: Error: java.lang.SecurityException: Neither user 10312 nor current process has android.permission.INSTALL_PACKAGES.
Click to expand...
Click to collapse
Ah, try doing su first so you are running as root.
Sent from my Tw5ted SM-G900A using Tapatalk

Okay.
tried with su:
pkg: whatever.apk
Failure [INSTALL_FAILED_INVALID_URI]
Looking like Titanium restore hasn't worked properly either, loads of programs needing to be reinstall again.
Dunno if its connected to this problem or not.

Invalid uri means you did the path wrong, tab complete the path(volup+t i think, if not voldown+t) so you have it exactly correct, it doesnt matter if you are already in the directory containing the apk it needs the full path.
Sent from my Tw5ted SM-G900A using Tapatalk

Ah ok.
With the full path: Failure [INSTALL_FAILED_INVALID_APK]
Funny enough, some apk's install this way some don't.

amaru007 said:
Ah ok.
With the full path: Failure [INSTALL_FAILED_INVALID_APK]
Funny enough, some apk's install this way some don't.
Click to expand...
Click to collapse
So the error is consistently failed invalid apk? The ones that install fine on other devices?
Sent from my Tw5ted SM-G900A using Tapatalk

Did a complete wipe of the phone, dalvik, cache and phone.
Reinstalled all apps from Play store from recovery.
Restored just system and app data with Titanium backup.
Other apk's are now installing fine on this device now, just not this one.
Uninstalled and tried reinstalling the apk on the other device, and it failed.
Looked into it further, seems there's been an update to the apk recently, downloaded it and now it works!
Weird since it worked on 5.0 and 5.1 before on the tablet, but once uninstalled, got the apk parse error on that too.
Thanks for all the help Rakuu.

amaru007 said:
Did a complete wipe of the phone, dalvik, cache and phone.
Reinstalled all apps from Play store from recovery.
Restored just system and app data with Titanium backup.
Other apk's are now installing fine on this device now, just not this one.
Uninstalled and tried reinstalling the apk on the other device, and it failed.
Looked into it further, seems there's been an update to the apk recently, downloaded it and now it works!
Weird since it worked on 5.0 and 5.1 before on the tablet, but once uninstalled, got the apk parse error on that too.
Thanks for all the help Rakuu.
Click to expand...
Click to collapse
No problem, glad you got it figured out.
Sent from my Tw5ted SM-G900A using Tapatalk

I'm wondering what the issue might be where one day APK files are installing correctly then the next day every attempt to install, whether through:
1) a file manager,
2) separate installer program, or
3) via each individual program's update feature,
all fail with the "there was a problem while parsing this package" error.
I used the great suggestion from Rakuu to try via the terminal (e.g. `# pm install /storage/emulated/0/Download/filename.apk`) and like magic, it works (installs successfully) with no error whatsoever.
However, no package file irrespective of source (all tested fine with archive programs and including previously successfully installed apk's) can be installed via the android interface.

Risk3 said:
I'm wondering what the issue might be where one day APK files are installing correctly then the next day every attempt to install, whether through:
1) a file manager,
2) separate installer program, or
3) via each individual program's update feature,
all fail with the "there was a problem while parsing this package" error.
I used the great suggestion from Rakuu to try via the terminal (e.g. `# pm install /storage/emulated/0/Download/filename.apk`) and like magic, it works (installs successfully) with no error whatsoever.
However, no package file irrespective of source (all tested fine with archive programs and including previously successfully installed apk's) can be installed via the android interface.
Click to expand...
Click to collapse
No clue, usually if it errors in the visual installer it will also with command line, maybe try a factory reset? I'm not too sure, that's odd.
Sent from my SAMSUNG-SM-G900A using Tapatalk

Turns out that the inability to install from the user interface coincides with a Cyanogenmod 13 (6.0.1) nightly upgrade. I'll either go back to a snapshot or try another nightly next week and see if that helps things along.
Thanks for your reply.

Disable signature verification for V20 specifically

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.