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
Related
Just trying to figure out how I can upgrade to 4.1.2 w/o reflashing to the stock kernel.
My Nexus is rooted running the stock ROM with Motley kernel.
Using CWM. Tried to flash the update.zip file available only thru CWM but was getting some errors (mainly about the Gmail.apk). I'm also not sure that the Motley kernel will work with the update since it's built on 4.1.1.
I haven't been able to pull the OTA update from my Nexus yet (and I'm in the US)... tried everything, just doesn't show the update as available.
ok so I've reflashed the stock Kernel.
I'm not still having issues getting the 4.1.2 update, giving an error about the Gmail.apk (which I don't recall touching besides the updates).
Any ideas?
samw52000 said:
ok so I've reflashed the stock Kernel.
I'm not still having issues getting the 4.1.2 update, giving an error about the Gmail.apk (which I don't recall touching besides the updates).
Any ideas?
Click to expand...
Click to collapse
Just a heads up to let you know that the motley kernel has been updated for 4.1.2
What is the error message for the gmail.apk?
samw52000 said:
Any ideas?
Click to expand...
Click to collapse
Yes, find a gmail apk and install it.
Saying this:
**********************
Installing: /sdcard/Downloads/03a4eaf95f73.signed-najasi-JZO54K-from-JRO03D.03a4eaf9.zip
Finding update package...
Opening update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/Gmail.apk", "2261fcf892d17cdede74cc637eb054e88f7dc274", "627b6ee7c9ab5f23blab70dc0f774e5c28495717")
E: Error in /sdcard/Download/03a4eaf95f73.signed-najasi-JZO54K-from-JRO03D.03a4eaf9.zip
(Status 7)
Installation aborted.
**********************
I checked my installed apps, and all apps (including running apps) but I find no traces of Gmail. When opening up the Play Store it's clearly listing it as installed, just not showing up in the installed program list (or all programs under settings).
Not sure what else to try at this point. I'd like to avoid wiping out the rom.
and it looks like i'm missing my gmail.odex file from /system/app/
samw52000 said:
Saying this:
**********************
Installing: /sdcard/Downloads/03a4eaf95f73.signed-najasi-JZO54K-from-JRO03D.03a4eaf9.zip
Finding update package...
Opening update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/Gmail.apk", "2261fcf892d17cdede74cc637eb054e88f7dc274", "627b6ee7c9ab5f23blab70dc0f774e5c28495717")
E: Error in /sdcard/Download/03a4eaf95f73.signed-najasi-JZO54K-from-JRO03D.03a4eaf9.zip
(Status 7)
Installation aborted.
**********************
I checked my installed apps, and all apps (including running apps) but I find no traces of Gmail. When opening up the Play Store it's clearly listing it as installed, just not showing up in the installed program list (or all programs under settings).
Not sure what else to try at this point. I'd like to avoid wiping out the rom.
Click to expand...
Click to collapse
You didn't freeze by any chance? See if Google Play will let you install again, if not, perhaps you have a titanium backup you can use to restore it.
Install this: http://www.androidpolice.com/2012/1...ed-gmail-4-2-apk-with-pinch-to-zoom-and-more/
Not frozen... I tried to move the Gmail.apk file and was able to reinstall Gmail from the Play Store w/o any issues.
Then I tried to push the update again via CWM and now I'm getting another apk error (patch_update or something like this). Not sure what's up with these packages giving me an error.
Any other ideas? Gmail is currently uninstalled from the device so it's not the issue any longer.
I'm pretty sure you're gonna need gmail installed.
*edit*
I read yesterday that someone took the update and removed all of the system checks out of it. Since these checks are causing you problems, you might want to go this route. Read this post: http://forum.xda-developers.com/showpost.php?p=32752631&postcount=20
Others here have used it successfully, and I wouldn't have any issues using it myself if I were in a situation where it was applicable.
Yeah, you're gone to need gmail. It has to have a stock ROM and kernel.
Did you do any of the performance tweaks motley listed in his OP. They may have to be undone.
nah, just flashed the Motley Kernel and installed SetCPU.
I reflashed the Kernel fine to stock. Reinstalled Gmail.
I just tried it again, still getting assert failed: apply_patch_check error for Gmail.apk. Grrrrrr
Now for the other noob question.
If I was to backup the device with Titanium backup (I have the Pro version linked to my Dropbox account), wipe the device and de-root, return to stock then restore the backup would I have any issues with the restore process (maybe not compatible from one rom version to another).
Are the settings retained in the restore process (like wallpapers, Wifi networks, installed apps and settings) or would these need to be manually restored?
I haven't gone thru the process before (at least on an Android) so I figured I would ask.
samw52000 said:
I just tried it again, still getting assert failed: apply_patch_check error for Gmail.apk. Grrrrrr
Click to expand...
Click to collapse
Did you consider the option I typed in the 10th post of this thread?
ya unfortunately same result still stuck with a bad Gmail. apk
Sent from my Nexus 7 using xda app-developers app
Getting ready for a full wipe and load of CM10 since I can't seem to come up with any other methods....
Don't feel like risking to brick my device with a non signed package that doesnt' verify APKs.
Hello,
I just noticed 1 hour ago I have 4.3 OTA update for my Nexus 10. However the update has been failed, due to vfxsound mod as far as I understand. I deactivated this app but I cant see OTA update again if I check the system updates manually it states that your system is current(4.2.2). What can I do to have this system update notification again?
My configuration:
rooted (supersu)
CWM recovery
Thank you.
Same here!
mbt28 said:
Hello,
I just noticed 1 hour ago I have 4.3 OTA update for my Nexus 10. However the update has been failed, due to vfxsound mod as far as I understand. I deactivated this app but I cant see OTA update again if I check the system updates manually it states that your system is current(4.2.2). What can I do to have this system update notification again?
My configuration:
rooted (supersu)
CWM recovery
Thank you.
Click to expand...
Click to collapse
I can't update to 4.3 because of the same reason.
In my case, I installed both vfx and vhifi.
I deactivated and turned both of them into safe mode and tried to flash the update with stock recovery.
However, I still got "assert failed: apply_patch_check system/vendor/etc/audio_effects.conf"
There is a way to get the OTA update back, but I repeatedly failed, and ended up with error.
Someone please help us!
This happens because those files have been modified and are no longer the originals. Extract the files it is having issues with from the 4.2.2 factory image, replace them and try again, or just flash system.img from the factory 4.2.2 image and run the OTA again.
Edit: Also, to get the OTA notification again, go to Settings>Apps>All and force stop "Google Services Framework" then "Clear Data". Immediately return to the "About" screen and check for a system update. If any popups come up regarding allowing location services, choose "No" or otherwise don't allow it.
While the system update downloads, remove your google account, and re-add it to avoid any issues with sync, etc. on your google account. Keep in mind if you use 2-factor authentication via google, you'll need to add a new application password for your tablet.
I succesfully upgraded the system. As you said I replaced these file with the original ones. Now It works fine. The only problem is mx player doesnt work. I think they will update it soon.
plastikowl said:
This happens because those files have been modified and are no longer the originals. Extract the files it is having issues with from the 4.2.2 factory image, replace them and try again, or just flash system.img from the factory 4.2.2 image and run the OTA again.
Edit: Also, to get the OTA notification again, go to Settings>Apps>All and force stop "Google Services Framework" then "Clear Data". Immediately return to the "About" screen and check for a system update. If any popups come up regarding allowing location services, choose "No" or otherwise don't allow it.
While the system update downloads, remove your google account, and re-add it to avoid any issues with sync, etc. on your google account. Keep in mind if you use w-factor authentication via google, you'll need to add a new application password for your tablet.
Click to expand...
Click to collapse
Thanks for your guide , my problem is same as above problem with little difference , when I click on OTA update my phone restart and go to CWM recovery and say "it is not safe package , do you want to install ?" I click yes but nothing happened . I also try to get OTA notification back as same as your instruction but nothing happened . please help me . thanks
sabx13 said:
Thanks for your guide , my problem is same as above problem with little difference , when I click on OTA update my phone restart and go to CWM recovery and say "it is not safe package , do you want to install ?" I click yes but nothing happened . I also try to get OTA notification back as same as your instruction but nothing happened . please help me . thanks
Click to expand...
Click to collapse
Did you mean, "phone"? I can only speak for how this behaves on the Nexus 10. Also, if you enable location services (sometimes it tries when the google services framework starts back up) and you allow it, the OTA doesn't seem to show up (at least not for me, perhaps it's region-based?).
I had to redo mine several times while I replaced system files that had been modified, so I know it works if it's done the way I described. 60% of the time, it worked every time.
Also, try removing your custom recovery. I don't know how this affects things for the OTA but it's a factor I didn't have to contend with.
I'm pretty sure he meant tablet. I'm having the exact same problem on my N10.
plastikowl said:
Did you mean, "phone"? I can only speak for how this behaves on the Nexus 10. Also, if you enable location services (sometimes it tries when the google services framework starts back up) and you allow it, the OTA doesn't seem to show up (at least not for me, perhaps it's region-based?).
I had to redo mine several times while I replaced system files that had been modified, so I know it works if it's done the way I described. 60% of the time, it worked every time.
Also, try removing your custom recovery. I don't know how this affects things for the OTA but it's a factor I didn't have to contend with.
Click to expand...
Click to collapse
I'm getting the OTA update to Android 5.1, it downloads, asks me to restart, then fails with an error screen and the robot lying on its back. The phone then reboots itself into the 5.0.1 firmware.
The phone is rooted, is anyone else getting the same issue. Are there any logs I can look at to find out why?
Thansk
i have troubles as well. i unrooted, installed stock recovery (via n4 toolkit) and tryed to install. it takes longer then before but i stell get an error. SuperSU is gone in my app drawer.. any other help?
PS: i am on stock rom 5.0.1
i tryed to use sideload ADB update. it says: "/system/bin/app_process32" has unexpected contents. Error in sideload/package.zip. Status 7
any tipps?
I used the excellent Wug Nexus Toolkit http://www.wugfresh.com/nrt/
Through there I unrooted. Then applied the new update.
rowdybeans said:
I'm getting the OTA update to Android 5.1, it downloads, asks me to restart, then fails with an error screen and the robot lying on its back. The phone then reboots itself into the 5.0.1 firmware.
The phone is rooted, is anyone else getting the same issue. Are there any logs I can look at to find out why?
Thansk[/Q
I tray everything but don't work, it tell me , cache file fail.
Click to expand...
Click to collapse
In my case, this did the trick: aaronhastings.me/updating-to-android-5-1-0-on-rooted-nexus-5
I hope it will help you, too.
Regards.
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.
Ive just rebooted my fire tablet after installing some minecraft mods, when I turnt it back on it came up with a promt saying it was installing the latest software or what ever it does when doing the ota, I knew this from upgrading to 5.0.1.
is it possible it was just doing what happens when normal android optimises apps on boot. is there a app to check the installed software version as im not near my pc to unhide and go in and check what firmware im on. I put this in general as it wasnt a question but just to inform that my tablet possibly had a update despite the proper steps taken to hide the ota and updates.
Saw Same Message But No Update (whew)!
For a split second I saw that same message too when first starting the Fire up. But nothing happened and nothing updated. So I think it's still blocked. Even checking for updates still fails.
So I think we're OK!
dubliner52 said:
For a split second I saw that same message too when first starting the Fire up. But nothing happened and nothing updated. So I think it's still blocked. Even checking for updates still fails.
So I think we're OK!
Click to expand...
Click to collapse
Have you tried unhiding to see the software version
Sent from my HTC One_M8 using Tapatalk
I didn't unhide it, but it says I'm still on 5.0.1. There was no update.
I saw the same thing but it didn't seem to update. I know the method i provided works for 5.0.0 to 5.0.1. Until there is a bump to 5.0.2 or whatever we don't know for sure if the "fix" works under 5.0.1.
Same thing happened to me but it was 3 days ago. I had been trying all day to install my adb drivers without success and switched off the device. When I restarted it immediately went into an update and I went into a panic that the new update would block the ability to access google play but immediately after the assumed "update" I successfully installed the adb drivers and google play without problem. I also checked the version and it still showed 5.0.1 so I wondered if my initial update on switching on the fire for the 1st time had somehow been unsuccessful and that had been what had been causing the inability to load the adb drivers although the tablet hadn't seemed to have any other problems and I had already downloaded and used several apps from Amazon.
I let it update upon first booting my Fire to 5.0.1. I was still successful in installing Google Playstore and hiding ads on lockscreen.
I'm not sure but i think that 'installing the latest software' screen is the android OS updating the dalvik runtime files after rebooting when an apk is modified. nothing to do with an ota.
julianpaul said:
I'm not sure but i think that 'installing the latest software' screen is the android OS updating the dalvik files after rebooting when an apk is modified. nothing to do with an ota.
Click to expand...
Click to collapse
That is my conclusion also.
I had this happen to me also. Considering amazon patched a root method I made sure to root and nuke any chance of a future OTA unless I wanted it too. That was a cheap move, Amazon.