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.
Related
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!
I ran the new towlroot today. Installed busy box and su. Granted access to everything. I then downloaded the latest safestrap for my Verizon note 3. After download I tried to install the apk from my file explorer. It states something about describe error, trouble parsing every time. I've researched but the only person to have this issue had to do a factory reset a few times.
cterrell16 said:
I ran the new towlroot today. Installed busy box and su. Granted access to everything. I then downloaded the latest safestrap for my Verizon note 3. After download I tried to install the apk from my file explorer. It states something about describe error, trouble parsing every time. I've researched but the only person to have this issue had to do a factory reset a few times.
Click to expand...
Click to collapse
If you haven't already keep trying. I was getting the same error and after re-downloading 5-6 times it finally installed.
I finally got it. I had to download it to the installer instead of trying to open it uaing a file explorer.
Hello.
My Galaxy S4 was dying so T-Mobile just replaced it with an S5. It came with:
LMY47X.G900TUVS1FOJ4
I clicked on Software updates in About device and it did whatever updates, but the version stayed the same. Then I went to autoroot [dot] chainfire [dot] eu and downloaded the correct file to root. I unzipped the file and ran Odin 3.10.6 that came with it. I was able to root the device no problem.
What seemed like a problem afterward was that I couldn't find SuperSU in the Application list. I know the phone was rooted though because I could launch Titanium Backup to restore all my stuff from the S4. I went to the Play Store to download SuperSU. It kept complaining that I needed a new binary, but it would fail every time to update. I even tried downloading the latest SuperSU zip to install in the recovery mode, but that failed too. I really wasn't too worried about this.
While looking up how to root the S5, I saw some posts where people mentioned their root access stopped after 24 hours. I just experienced this when I launched Titanium Backup to begin uninstalling bloatware. I was informed that I didn't have root access anymore.
I figured I'd try to reflash the auto-root through Odin. According to Odin, everything passed, but looking at the device, it said it's already patched and the restore failed, so it aborted.
Now the device is stuck in an infinite reboot loop. I can access both the download and recovery modes, but that's it.
I'd really really like to not have to do a factory wipe as it was a pain to get everything copied over from the S4.
Can I flash it with something else?
Once I can get back in the device, how do I keep the device rooted? Do I have to flash TWRP or CWM?
The only root program I use is Titanium Backup and would really really like to keep using it to makr regular backups.
Thanks a lot.
Try booting into recovery and wiping the CACHES
If it still won't boot, grab a stock ROM from sammobile .com for your model S5 (G900T by the looks of the ROM name) and flash it with ODIN from download mode
That won't wipe your data or anything you've restored, as long as you don't reset
If it still won't boot, you might have to suck it up and factory reset after flashing stock
Was the TiBu backup you restored, rooted? Maybe restoring the backup restored an old version of SuperSU and broke the CF AR version
Might need to go down the TWRP and SuperSU from TWRP recovery route to get it rooted properly if CF AR isn't woprking 100%, which it doesn't for a fair few people
I tried clearing the cache, but that didn't work.
Is there a way to download the stock ROM without having to create an account on the download site?
The Titanium Backup I restored was rooted. Everything was totally fine, until I went back to TB and it suddenly told me I wasn't rooted anymore.
I did try TWRP after I made the original post. I think messed up the device, but I can get in now. I flashed the latest version and booted into Recovery Mode. I clicked on Fix Permissions and possibly one other thing. It let booted farther before the infinite bootloop. It'd show my lock screen and give me 1-2 seconds before rebooting. If I swiped quickly, I could see the home screen with most of my icons gone. Clicked on Apps shows most of the apps are gone. When I removed the SIM card, I stopped getting the infinite bootloop. Here are the list of important programs I have left:
Contacts (all cleared out), Gallery (all present), Messages (all present), My Files (shows files from previously installed programs that I can no longer access), Phone (works when I put the SIM card back in), Settings
Unfortunately, TB and the Play Store are both gone. I might be able to install stuff using adb or by copying files over. I haven't tried, but it doesn't look good. I tried reflashing the CF ROM. It didn't change anything. I suspect I may be looking at a factory reset at this point. I'm happy to try any other suggestions.
Thank you.
whynoteel said:
Is there a way to download the stock ROM without having to create an account on the download site?
Click to expand...
Click to collapse
Wut? lol, just make one, it's free...
XDA does not spoon feed
I created an account and downloaded the stock ROM. I flashed the device and got most of the programs to appear again though the Play Store was still missing. I decided to cut my losses and just do a factory reset. I rooted again and put everything back in place. Now I'm experiencing the problem where I lost root after a day or so of use. I'll start a new thread.
Thanks for your help.
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.
I did a full unroot of SuperSu to root with Magisk. After I root with Magisk, I get a few 'App has stopped working', I get
Unfortunately Logs Provider has stopped working
Unfortunately Media Storage has stopped working
Unfortunately Contacts Storage has stopped working
Unfortunately TouchWiz Home has stopped working*
Unfortunately User Dictionary has stopped working
Unfortunately Weather has stopped working
*I use Nova Launcher
I usually get them upon boot but sometimes I get them during regular usage
I've Tried
Reflashing correct firmware through Odin
Wiping Cache and Dalvik
Factory Resetting
Unrooting Magisk and Rerooting
How do I fix it, I am Running OS 5.0.2
Edit: Download Manager doesn't work as well when downloading APKs
Reflash it
ghg1 said:
I did a full unroot of SuperSu to root with Magisk. After I root with Magisk, I get a few 'App has stopped working', I get
Unfortunately Logs Provider has stopped working
Unfortunately Media Storage has stopped working
Unfortunately Contacts Storage has stopped working
Unfortunately TouchWiz Home has stopped working*
Unfortunately User Dictionary has stopped working
Unfortunately Weather has stopped working
*I use Nova Launcher
I usually get them upon boot but sometimes I get them during regular usage
I've Tried
Reflashing correct firmware through Odin
Wiping Cache and Dalvik
Factory Resetting
Unrooting Magisk and Rerooting
How do I fix it, I am Running OS 5.0.2
Edit: Download Manager doesn't work as well when downloading APKs
Click to expand...
Click to collapse
U need to flash the factory version of firmware .. I mean firmware that was given when u bought it .. check it sammobile website
Anu Darang said:
U need to flash the factory version of firmware .. I mean firmware that was given when u bought it .. check it sammobile website
Click to expand...
Click to collapse
Hi, I fixed this problem by updating my phone using smart switch on PC, thanks for the suggestion.
ghg1 said:
Hi, I fixed this problem by updating my phone using smart switch on PC, thanks for the suggestion.
Click to expand...
Click to collapse
No problem