Hey guys, this is the first time I have seen this error from the play store (Latest update as of this post)
I have tried everything I can (Google search results from 100+ sources) besides getting a new phone.
I've tried going back to stock, I've tried CM10.1, I have tried Wiping and fixing permissions in every single menu on recovery AND in the phone.
I am running the USCC Variant of the SGS3 (Almost identical to the D2VZW) I even went as far as installing an older AND New CWM/TWRP recovery.
Is there a one tick fits all method to fixing this error?
"Package File Invalid" Only happens to a few applications (Whether it is Updating OR Downloading a new app altogether.)
Related
Hi XDA,
For the past several days I've tried to Safestrap a custom ROM to my phone. I'm running a rooted Samsung Galaxy S4 with ME7 (Verizon), Android 4.2.2. It's worth noting that the phone has not received an official Verizon update since August; I tried using Loki back then before knowing about the locked bootloader, and it has not affected anything except that the phone softbricks into the ODIN screen whenever it tries to install a Verizon update. (I hope this is not the cause of the problem, but let me know if you think it is.) It's also worth noting that I deleted the stock messaging app (SecMMS.apk and SecMMS.odex.) I am using Safestrap 3.65.
So far, I've tried three different ROMs (Hyperdrive RLS10.2, Jelly Beans Build 7, Google Play Edition for 4.2.2.) Each install produced the same results: it installs just fine in the ROM slot (along with the ME7 modules afterwards), but when I reboot the system, it shows the Samsung logo, the Safestrap splash screen, and then the screen goes black indefinitely. A battery removal is required.
I've tried every trick I could find to get the ROMs working. I've done a full factory reset each time (data + both caches), tried downloading each mod several times on both my phone and my computer (verified MD5 each time) and same with the modules, waited at least 20 minutes during each boot attempt, tried installing each ROM with default settings and minimal apps, used Stock kernels each time, made sure the modules are installed before rebooting (I also tried without the modules to make sure they weren't the problem--same result.) Each time I try an install, I delete the ROM slot and format it again (usually a 1GB-2GB-300MB split.) I've searched and searched and can't seem to find anyone with this problem that hasn't solved it through one of the fixes I've unsuccessfully tried.
I'm plum out of ideas now, and am hoping someone may have more wisdom to share. Please help!
Hey all
So after a botched Cyanogenmod install on my AT&T GS3, I am having some issues with the stock ROM. Here's what happened: I tried to install CM using the windows installer, everything went well until the end and then I got a prompt on the phone prior to it rebooting "Root access lost, fix? Yes/No". Regardless of choice, phone would always boot back to stock ROM. Asked for some advice on the CM forum and was told KNOX was the issue. I then rooted the phone using Towelroot, and then installed Super SU. Super SU when opened for the first time said KNOX was installed, did I want to disable it, I chose YES. Re-tried CM installer, same issue, just boots back to stock ROM.
At this point I gave up and just re-installed all my apps and settings, synched my Google account etc. Since then I can no longer download anything from any Google app, it just says "Download failed". So Gmail attachments, links, Chrome etc. nothing downloads. Although stock Internet downloads are fine. Swiftkey now errors saying "Cannot save language pack" then crashes, Swype keyboard keeps on re-enabling itself after I turn it off, and apps that worked fine before are crashing like crazy.
Last night I performed a wipe/factory reset after starting in recovery mode. This did not help. I also noticed that recovery mode boot screen is Cyanogenmod boot screen still, so guessing factory reset is not exactly a full factory reset and it just wipes data/cache etc.
Seems to me like some kind of permissions issue. I downloaded Root Explorer and had a poke around. Permissions look fine (read/write etc.) on Downloads folder. Only thing that looked odd was there are 3 different file system areas so 3 different downloads folders (ie sdcard0/0/Downloads, storage/0/downloads and storage/legacy/downloads). Not sure if that is normal.
Just want to put it back to how it was. Any suggestions what to do next?
Cheers.
Hi All,
I have finally signed up today, after reading numerous threads over the last few days. My problem is that a few days ago I changed ROMs from Omega to CW10.1. After the change the camera is black, clicks repeatedly and crashes after a short while. I therefore reinstalled the Omega ROM, however the problem remained. I next used Odin to flash to a stock Samsung JB ROM. The problem remains. I am now on the standard JB Rom with a Siyah Kernel. I have wiped cache, dalvik cache and perfomed factory reset several times, all to no avail.
Checking the phone/camera firmware reveals TBEC28 for both.
I have downloaded the camera update apk from a thread on here, however upon entering airplane mode this too crashes.
What I would like to know is how, if at all possible to manually change the firmware? I have found the individual rs_m5ls_** .bin files from the camera apk but do not know how to install these, in order to try different versions?
Thanks in advance
In addition to this I found another thread saying to place the .bin camera firmware files in sys/etc/firmware, however no such file exists in the etc folder?
I have tried placing the .bin files on the sd card and also in the /data file, however when using the *#34971539# to update the phone always shows the same TBEC28 for both phone and cam.
Clicking the update always shows the same, 'this is the latest firmware'.
Any experts out there with knowledge of what I am doing wrong or a way around this problem?
Ok
Well im progressing slowly and am now able to flash the camera firmware to various versions using the bin file.
However although varoius versions have stopped the camera clicking the display remains black and crashes
I see many people have had similar troubles. Did anybody fix this?
Hi XDA,
first, I greatly appreciate all the effort you are putting into this. You have made using my age-old i9300 a blessing multiple times. So thank you for that!
Now on to my problem. I have recently wiped&clean-installed the CM-13.0-20151222-NIGHTLY build and appear to have lost root-access. I did enable it in the developer options (I have tried both app and adp and "just" app access) but rootChecker ist still returning a negative result and any app using root doesn't function (titanium back-up for example). Primarily I want to use it to stop some apps from auto-starting that I hardly ever use.
I had read that when updating the ClockWorkRecovery (latest verison.. 6.0.4.7) prompts you if you want to re-enable root access (like it did when I first auto-updated from CM11 to CM13 (which obviously didn't work which is when I wiped everything and flashed the CM-13.0-20151222-NIGHTLY)). Today a new nightly came out and I thought I'd give it a shot but the checksum constantly fails from within the updater and it won't allow me to flash it claiming the download is bad (multiple downloads tried, always same result).
Is anyone else experiencing these issues with the checksum Fail and the lost "full" root access? Did you manage to find a solution to it?
Kind regards,
kidd
Tried two times downloading update and both times got checksum error, then downloaded manually and dirty flashed in TWRP, everything went fine.
Do an error test on your hdd and power cycle your router.
If the hdd is corrupt it will corrupt data. If the routers network address translator is borked it will corrupt data.
I wish I stole my HTC M9.
The issue has appears to have resolved itself. The Update went through fine after I had tried the next day.
Is there any fix for the converting the pseudo-root back to the full root you know of?
Best,
Kidd
Hi fellow,
I recently decided to flash CM13 on my XT1524.
First, I've unlocked the bootloader, then I've flashed TWRP, I've flashed latest CM13 nightly and latest OpenGapps (nano). All goes fine, but Play Store is not able to install/update any apps under WiFi: a notification with a progress bar appears but this ends up with error 495. All seems to works pretty good under mobile data.
A strange error. Having no time to lose, I flashed back the original firmware.
Honestly, by restoring original MM firmware I thought that all problems gone but didn't. In fact I get exactly the same problem with original ROM.
Since the only difference between actual situation and latest working one, is the unlocked bootloader, maybe I have to do something else to restore the phone... Help!
PS: I've already tried all known methods
1- reboot
2- clear data/cache of google play store, of download manager, of google play services, of google services framework
3- remove google account
4- factory reset
5- uninstall google play store update (in reality, I have no updates to uninstall, so...)