Hey Guys, apparently Samsung just pushed out a firmware update to all S4 KitKats and upon my attempt to install it, I receive the following error:
(Tried install in Rooted and UnRooted mode)
Finding update package...
Opening update package...
Verifyting update package...
Installing update...
Verifying current system...
"/syste/priv-app/zone.apk" has unexpected contents
E:Error in /cache/e9fcadf8ac86f2c1b6c99b9fad9b16b13a49a6a.lSER_L720_SPT_NAE_CSB_user_RP_to_NG2_CSB_user_RP_Update_FWD.zip
(status7)
Installation aborted.
My phone info: (Sprint - rooted-Stock ROM)
Software: L720VPUFNAE
Hardware: L720.08
Model: SPH-L720
KitKat 4.2.2
Kernel Version: 3.4.0-481102
I did see a few post regarding status 7 but all for custom ROM install only.
Wanted to know if anyone heard of any fixes for this specific error.
I appreciate everyone's time.
Seems like you probably froze or deleted an app like Sprint Zone, I'm assuming. Either replace the apps moved/removed or skip the OTA which sucks anyway and manually install the firmware via Odin. This is the preferred method as it is cleaner and you won't need to worry about fixing errors in the system like missing apps. Here is the latest version:
http://forum.xda-developers.com/galaxy-s4-sprint/development/rom-stock-ng2-odin-flashable-t2861576
es0tericcha0s said:
Seems like you probably froze or deleted an app like Sprint Zone, I'm assuming. Either replace the apps moved/removed or skip the OTA which sucks anyway and manually install the firmware via Odin. This is the preferred method as it is cleaner and you won't need to worry about fixing errors in the system like missing apps. Here is the latest version:
http://forum.xda-developers.com/galaxy-s4-sprint/development/rom-stock-ng2-odin-flashable-t2861576
Click to expand...
Click to collapse
Good call on the Sprint Zone. This was the first app I got rid of once i got the phone. Thanks for the quick respond. I will have to flash it and re-root it; no biggie.
I did notice that tar file is for these versions and I have L720VPUFNAE
L720VPUFNG2; L720SPTFNG2; L720VPUFNG2
Would be ok to flash it to this NG2 instead of AE?
Chumpster9 said:
Good call on the Sprint Zone. This was the first app I got rid of once i got the phone. Thanks for the quick respond. I will have to flash it and re-root it; no biggie.
I did notice that tar file is for these versions and I have L720VPUFNAE
L720VPUFNG2; L720SPTFNG2; L720VPUFNG2
Would be ok to flash it to this NG2 instead of AE?
Click to expand...
Click to collapse
Yea, NG2 is the newest.
es0tericcha0s said:
Yea, NG2 is the newest.
Click to expand...
Click to collapse
Excellent; greatly appreciate it.
Related
I have a rooted Amaze with just some bloatware removed. Yesterday I received a notification in the status bar that a system update was available. When I try to run the update the phone reboots and then freezes with a big green X on the screen. Doesn't look like something official. Has anyone seen this before or know what it's about? I'm thinking maybe it's just failing to run the update because of being rooted or a related issue but can't find any info on Google about the green X.
I finally pulled the battery out because it wouldn't respond and then turned the phone on again. It booted fine and I still have the notice about the update. I'm reluctant to try again until I find out what's going on. Thanks.
I don't think you're able to install an update through a custom recovery..There should be a ROM with that update already in it.
If you have a Custom ROM you can't take the update that is intended for stock unrooted ROMS.
Sent from my HTC Amaze 4G using xda premium
Thanks for the feedback. I don't have a custom rom - just the stock minus some bloat. I can see how the custom recovery, however, might interfere.
I can't find any info on the update and what it includes or why I might want/need it but assuming it would be good to install then is there an easy way to remove the custom recovery? Would running the stock update.zip do this or do I need to go through the full un-root process?
If you have CWM recovery already,
1. Go to /downloads folder inside the internal Storage. You can find the OTA.
2. Rename it to "update.zip" and copy to External SD.
3. Reboot the device to recovery.
4. Select update.zip and update manually.
5. After update & reboot, delete both original files to get rid of notification.
Thanks for the directions. Tried and got this error
Code:
verifying current system...
assert failed: apply_patch_check("/system/app/FriendStream.odex", "some very long hex number", "some other long hex number")
E:Error in /sdcard/update.zip
(stage 7)
Installation aborted.
droidux said:
Thanks for the directions. Tried and got this error
Code:
verifying current system...
assert failed: apply_patch_check("/system/app/FriendStream.odex", "some very long hex number", "some other long hex number")
E:Error in /sdcard/update.zip
(stage 7)
Installation aborted.
Click to expand...
Click to collapse
Seems its not possible as you have removed some programs
Think you removed friendstream also.
It seems to work only if the ROM is unmodded
skr_xd said:
Seems its not possible as you have removed some programs
Think you removed friendstream also.
It seems to work only if the ROM is unmodded
Click to expand...
Click to collapse
Yes, I removed facebook and friendstream. Not sure why those would be necessary to run a system update but you may be right about not being able to update a modified phone. Maybe the update isn't anything I need anyway if it wants to update an app I don't want.
Thanks for the help.
In case anyone has a similar issue, here is what I've figured out.
The update won't run on a modified system - even if it's a stock, but changed, rom. In the interest of exploration, I restored my backup using clockwork and then ran the update. It still didn't work, but following skr_xd's advice above I was able to run the update manually. The result was a more or less stock phone without root but with the most current software. I then re-rooted the phone and re-removed all the bloat with no apparent ill effects.
Thanks for the help.
Btw, I didn't know what the green X was all about, but I think it's related to clockwork mod. Could be wrong though.
droidux said:
In case anyone has a similar issue, here is what I've figured out.
The update won't run on a modified system - even if it's a stock, but changed, rom. In the interest of exploration, I restored my backup using clockwork and then ran the update. It still didn't work, but following skr_xd's advice above I was able to run the update manually. The result was a more or less stock phone without root but with the most current software. I then re-rooted the phone and re-removed all the bloat with no apparent ill effects.
Thanks for the help.
Btw, I didn't know what the green X was all about, but I think it's related to clockwork mod. Could be wrong though.
Click to expand...
Click to collapse
yes its the custom clockworkmod i made
xboarder56 said:
yes its the custom clockworkmod i made
Click to expand...
Click to collapse
Thanks for the confirmation and awesome software. I noticed there is work on version 5.0.2.7. Assuming it would be wise to update once released.
Same issue here. I have stock rom without any bloatware removal.
I just unlocked the bootloader than installed CWM and rooted the phone.
when I try to update phone OTA it stucks in splash screen (With Big Green X logo)
Flash prerooted rom you good to go
Sent from my HTC Amaze 4G using xda premium
I just spent abut 4 hours trying t figure this out...
This is my journey..
Relock bootloader
Flash one of the stock tmobile ruby rom in development section
Did the OTA update on stock
Unlocked my bootloader again
Then i tried to root using one click zerg method but it didnt work
So i flashed clockwork mod using fast boot
Then applied a su binary update i found in the development section.
In less than a minute i got root back.
Then i restored my data from nandroid backup.
My phone is pretty much rooted, bootloader unlocked, bloatware free alongside having the ota update that enabled wifi calling installed.
You don't need to relock your phone to do the update. If you do xboarder's recover to stock method just skip the relock part you can update your phone. So far going back to stock is the only way to get the radio updated as well which I am noticing way better 4g coverage than before!
bmbrad said:
You don't need to relock your phone to do the update. If you do xboarder's recover to stock method just skip the relock part you can update your phone. So far going back to stock is the only way to get the radio updated as well which I am noticing way better 4g coverage than before!
Click to expand...
Click to collapse
working on a way maybe this weekend will have it ready
xboarder56 said:
working on a way maybe this weekend will have it ready
Click to expand...
Click to collapse
NICE! Dude you must never sleep! Always the first to get something done!
I figured out what to do. You just need to rename this update file to update.zip. then reboot in recovery and choose install update from sd card. Next navigate to download folder and install update.zip file. You will be updated and stay rooted at the same time.
This worked for you because you didn't remove any of the t-mobile bloatware from your phone.. This will not work for people who messed with the pre-installed bloatware.
darll said:
This worked for you because you didn't remove any of the t-mobile bloatware from your phone.. This will not work for people who messed with the pre-installed bloatware.
Click to expand...
Click to collapse
Maybe, but 8m I've got another problem after updating this way. Wifi doesn't work anymore. I receive an error while trying to switch on wifi.
Hello all,
I am having trouble upgrading from 2.3.6 to ICS. I got an OTA notification for my Fido XT910 and when I tried to apply it, it told me that I did not have enough memory and to try performing a factory reset. After searching, I found that this was happening because my device was rooted. I removed root and tried again. Now, the update seems to work! It gets halfway through, then fails and reboots. I searched some more and found that something may be amiss in my file system.
So, I let the OTA upgrade download again, but this time I told it to "Install Later". I re-rooted my phone, copied the OTA file from my /cache folder to SD-EXT, unrooted, booted into recovery and finally tried to apply the update again. This time I found out what is preventing the upgrade from going through. It looks like it cannot find the file Videos.apk. Now, I don't know what this file is. I thought it might be Google Play Movies so I dumped into my /system/app/ folder as Videos.apk. No luck. I looked through the 2.3.6 upgrade file to find the Videos.apk file, but it only contained a binary update file (Videos.apk.p) and not the complete apk. I don't know what I can do to get the update to run successfully, without wiping!
Can anyone help me? Does anyone still have a Fido branded XT910 running 2.3.6 that they could extract the Videos.apk file from and send my way?
Any help is appreciated! Thanks in advance!
If it helps, here is the error message I get when applying the upgrade file:
##############################
-- Install /sdcard/Update ...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: apply_patch_check("system/app/Videos.apk", "fd8e2bd8f5e6050df232ec23e1532302c6ae3668", ce95a9afaad166d4d28c1b5f3c58c13e97f1e9d9")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
##############################
Thanks again!
Anyone have any ideas? I really can't find anything like this by searching through the XDA or other forums. I'm so close to fixing this, I would hate to stumble on this final step. Thanks again!
I dont know, I am in the same boat as you.
Accept im trying to flash from the released zip of the same file you are getting OTA.
I have temp unrooted with voodoo and same error.
Did a factory reset and still get same error.
Any help would be greatly appreciated.
cnmsales said:
I dont know, I am in the same boat as you.
Accept im trying to flash from the released zip of the same file you are getting OTA.
I have temp unrooted with voodoo and same error.
Did a factory reset and still get same error.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
What's the error you're getting? I've worked past several issues so far, so maybe I can help you. I'm just stuck on this latest one.
I am getting
- Install /sdcard/Update ...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: apply_patch_check("system/app/Videos.apk", "fd8e2bd8f5e6050df232ec23e1532302c6ae3668", ce95a9afaad166d4d28c1b5f3c58c13e97f1e9d9")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
But after some research It appears I need to go back to stock ICS using the Droid Razr utility by matt. Then temp unroot with voodoo tool, flash the new update, then reroot with voodoo tool.
cnmsales said:
I am getting
- Install /sdcard/Update ...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: apply_patch_check("system/app/Videos.apk", "fd8e2bd8f5e6050df232ec23e1532302c6ae3668", ce95a9afaad166d4d28c1b5f3c58c13e97f1e9d9")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
But after some research It appears I need to go back to stock ICS using the Droid Razr utility by matt. Then temp unroot with voodoo tool, flash the new update, then reroot with voodoo tool.
Click to expand...
Click to collapse
OK, so you're getting the exact same error message as me!
I had a tough time find Matt's utility. Were you able to download it? Did it correct your issue? Thanks in advance!
dhomas said:
OK, so you're getting the exact same error message as me!
I had a tough time find Matt's utility. Were you able to download it? Did it correct your issue? Thanks in advance!
Click to expand...
Click to collapse
Havent tried yet. At work right now. Will be working on it when I get home.
cnmsales said:
Havent tried yet. At work right now. Will be working on it when I get home.
Click to expand...
Click to collapse
OK, I'm downloading Matt's utility right now. It's huge! About 1GB. I'll let you know how it goes.
If im reading http://forum.xda-developers.com/showthread.php?p=38877887#post38877887 correctly then the update that went out today is only for those who got the xmas update.
If thats the case we will have to find the original xmas update first, then flash todays update.
cnmsales said:
If im reading http://forum.xda-developers.com/showthread.php?p=38877887#post38877887 correctly then the update that went out today is only for those who got the xmas update.
If thats the case we will have to find the original xmas update first, then flash todays update.
Click to expand...
Click to collapse
Yes, this is my understanding as well. I need to update to ICS before I can update to JB.
dhomas said:
Yes, this is my understanding as well. I need to update to ICS before I can update to JB.
Click to expand...
Click to collapse
Right, and then we have to find the JB update that was released at xmas.
---------- Post added at 03:55 PM ---------- Previous post was at 03:49 PM ----------
Pretty sure this is the JB xmas file
http://d-h.st/8l1
Yes, that is the correct file. It's for phones with the 211 ICS build. Also, Droid Life has the separate new JB file for phones on the 211 build, in case you want to install JB in one step.
Sent from my DROID RAZR using xda app-developers app
DHomas did you get it sorted?
Ive got it figured out and am now on JB. BAM.
Step1: First of all, you will need to use the droid razr utility to go back to ICS.
You can get this tool at http://www.droidrzr.com/index.php/topic/11872-droid-razr-utility-190-windows-mac-linux-all-in-one/
IMPORTANT. Make sure you install moto drivers, and rsd lite. Both included with this utility download.
Make sure phone has usb debugging mode enabled.
Make sure when plugging phone into computer you disable mass storage mode.
Step2: Once on ics use the utility to also root again.
Step3: Once rooted, install voodoo and create a root backup.
Step4a: Put this file on your external SD card.
Droid life actually has the whole new file. So no need to flash xmas leak.
You can get it here - http://www.mediafire.com/?5ca5825kzojfv49
Step4b: Boot into recovery and install from sd. Choose the above linked file. Let it do its thing.
Enjoy.
---------- Post added at 07:53 PM ---------- Previous post was at 07:23 PM ----------
Just a warning, after doing this even though the utility indicated root was done, and after JB installed voodoo is showing root but when trying to update the SU app it says FAIL when trying to gain root access.
Luckily root can be gained in JB using this http://www.droidrzr.com/index.php/topic/6935-rootwindows-razr-blade-droid-razr-41-jb-root-exploit/
Just threw together a video showing how to manually update your Nexus 10 to 4.4 KitKat.
Hopefully this cuts down the questions. You must be on the 4.3 JWR66Y build to update.
Video:
http://youtu.be/damDoq1xGNo
Followed the guide but the upgrade fails.
ADB sends the file correct but recovery refuses to install it.
First i thought it was because of the unlocked bootloader but i get the same error even after i locked it
what to do?
EDIT: just tried to redownload the file still the same.
Full error is:
Warning: No file_contextsVerifying current system...
"system/bin/app_process" has unexpected contents.
E: Error in /tmp/update.zip
(status 7)
Installation aborted
Working perfectly. Having no driver for Nexus 10, downloading from qbkink77 site (comming from Win 8 64 bit)
Thnx for perfect instructions!
qbking77 said:
Just threw together a video showing how to manually update your Nexus 10 to 4.4 KitKat.
Hopefully this cuts down the questions. You must be on the 4.3 JWR66Y build to update.
Video:
http://youtu.be/damDoq1xGNo
Click to expand...
Click to collapse
Worked perfectly for me.
mbeltoft said:
Followed the guide but the upgrade fails.
ADB sends the file correct but recovery refuses to install it.
First i thought it was because of the unlocked bootloader but i get the same error even after i locked it
what to do?
EDIT: just tried to redownload the file still the same.
Full error is:
Warning: No file_contextsVerifying current system...
"system/bin/app_process" has unexpected contents.
E: Error in /tmp/update.zip
(status 7)
Installation aborted
Click to expand...
Click to collapse
you have a modified stock rom. you will first need to flash pure stock and then try again.
yeah i figured that out - apparently it was xposed framework that gave the problems.
mbeltoft said:
yeah i figured that out - apparently it was xposed framework that gave the problems.
Click to expand...
Click to collapse
Hey man.
I have the same problem as you. When I push the .zip it fails at 100%.
I have twrp 2.6.3.1, stock 4.3, root access and unlocked bootloader.
Where to find a pure stock rom and how to flash it?
EDIT: Nevermind. Dit it via Toolkit.
I have KitKat installed now.
qbking77 said:
Just threw together a video showing how to manually update your Nexus 10 to 4.4 KitKat.
Hopefully this cuts down the questions. You must be on the 4.3 JWR66Y build to update.
Video:
http://youtu.be/damDoq1xGNo
Click to expand...
Click to collapse
thank u , i did it and working :good::good::good:
Thanks for the guide! Now i'm enjoying kitkat
Thanks worked perfect
Strangely enough, I manually updated last week, apparently successfully (Android version, build changed, etc.). Eveything was working pretty well. This week, I got a OTA alert and figured why not? Performed the OTA, re-upgraded to 4.4, and things are working even better now. Not sure what the difference was, but performing the OTA cleared the minor issues I was seeing with 4.4 when manually pushed (i.e. Launcher selection wouldnt stick, home screen animations now smoother).
mevensen said:
Strangely enough, I manually updated last week, apparently successfully (Android version, build changed, etc.). Eveything was working pretty well. This week, I got a OTA alert and figured why not? Performed the OTA, re-upgraded to 4.4, and things are working even better now. Not sure what the difference was, but performing the OTA cleared the minor issues I was seeing with 4.4 when manually pushed (i.e. Launcher selection wouldnt stick, home screen animations now smoother).
Click to expand...
Click to collapse
4.4 got a bug-fix version which happened the last week or so, from 4.4 KRT16O to 4.4 KRT16S. I got the same puzzlement on a Nexus 4, I flashed it to 4.4 via toolkit then to find it was offering a 4.4 upgrade.
mbeltoft said:
yeah i figured that out - apparently it was xposed framework that gave the problems.
Click to expand...
Click to collapse
Did disabling/uninstalling Xposed framework in the app work?
I just got the update for Kit Kat on my DNA and started the upload. It has sat there at about 20% complete for over 45 minutes. I pushed the volume up an power buttons to bring up the log and this is what it says:
Finding update package
Opening update package
Verifying update package
Installing update
Warning: No file_contextsPreparing wr_bin tool
Preparing recovery.zip
Running wr_bin tool
Can someone please help me?
Hmm...
mjondle said:
I just got the update for Kit Kat on my DNA and started the upload. It has sat there at about 20% complete for over 45 minutes. I pushed the volume up an power buttons to bring up the log and this is what it says:
Finding update package
Opening update package
Verifying update package
Installing update
Warning: No file_contextsPreparing wr_bin tool
Preparing recovery.zip
Running wr_bin tool
Can someone please help me?
Click to expand...
Click to collapse
I'm currently running a custom rom, so as far as the update actually goes i'm not too sure. The only advice i can give is to wait for a little longer. If nothing, then you might need to pop out your SIM card and download update via wifi. That's all the advice I can give. i'll do some research and get back to you on that!:good:
EDIT:
Just to verify, you had TWO updates before this installation began right? one 18.3MB file then a 618.0MB, correct?
4.4.2 OTA broke blinkfeed
I have an issue to where I did the OTA update to 4.4.2 and I did a factory reset through 2 different ways and now my BlinkFeed is nonexistent. I was wondering if there is a RUU for Verizon for the 4.4.2 update so I can just reset it that way because it seems the BlinkFeed files are corrupted or missing. Thanks.
WestTexasCoder said:
I'm currently running a custom rom, so as far as the update actually goes i'm not too sure. The only advice i can give is to wait for a little longer. If nothing, then you might need to pop out your SIM card and download update via wifi. That's all the advice I can give. i'll do some research and get back to you on that!:good:
EDIT:
Just to verify, you had TWO updates before this installation began right? one 18.3MB file then a 618.0MB, correct?
Click to expand...
Click to collapse
Yes, there were supposed to be 2 updates but this is freezing on the first one. It's actually my wife's phone and we let it sit for awhile the day I first posted and it never did update. It restarted and worked as normal but it keeps wanting to update the software. We're trying again right now but it looks like it is stuck again.
I just received a notice from Verizonwireless that there is a new software update available. So I went ahead and downloaded the update and attempted to install it. After a few seconds a new window opened showing the stupid Android robot laying on its back and the word "error" displayed. Thinking something bogus is going on with my phone I did a factory erase and retried the software update - same results.
Any way to determine what the error is and correct it so I can do the SW update? Out of curiosity I tried using ClockworkMod Rom Manager to install a custom ROM but got the same error indication.
My phone is a Verizon Galaxy S4 with Andriod version 4.3. The baseband version is I545VRUEMK2.
Thanks.
bmwmcrider said:
I just received a notice from Verizonwireless that there is a new software update available. So I went ahead and downloaded the update and attempted to install it. After a few seconds a new window opened showing the stupid Android robot laying on its back and the word "error" displayed. Thinking something bogus is going on with my phone I did a factory erase and retried the software update - same results.
Any way to determine what the error is and correct it so I can do the SW update? Out of curiosity I tried using ClockworkMod Rom Manager to install a custom ROM but got the same error indication.
My phone is a Verizon Galaxy S4 with Andriod version 4.3. The baseband version is I545VRUEMK2.
Thanks.
Click to expand...
Click to collapse
Sounds like your phone has been rooted / modified. This would be why. Samsung + VZW conspire to make it a mess to update officially when you have modded the phone. Just install the update via the PC and Odin. It is more reliable anyway than OTAs. If there is not an official 4.4 Odin version yet, then install the MK2 update that way and then factory reset then take the OTA.
But sounds like you really aren't sure what you are doing because you should NOT be attempting to use ClockWorkMod Rom Manager on a Verizon S4 with that update!! With the whole locked bootloader fiasco, this operation is not permitted as you can only use the SafeStrap recovery system to load custom roms. Really have to read up some more before you get your phone into a situation it might not find it's way out of...
es0tericcha0s said:
Sounds like your phone has been rooted / modified. This would be why. Samsung + VZW conspire to make it a mess to update officially when you have modded the phone. Just install the update via the PC and Odin. It is more reliable anyway than OTAs. If there is not an official 4.4 Odin version yet, then install the MK2 update that way and then factory reset then take the OTA.
But sounds like you really aren't sure what you are doing because you should NOT being attempting to use ClockWorkMod Rom Manager on a Verizon S4 with that update!! With the whole locked bootloader fiasco, this operation is not permitted as you can only use the SafeStrap recovery system to load custom roms. Really have to read up some more before you get your phone into a situation it might not find it's way out of...
Click to expand...
Click to collapse
Hi es0tericcha0s - Thanks for pointing out that Rom Manager shouldn't be used on a VZW Galaxy S4. I knew that but totally forgot about that fact.
bmwmcrider said:
Hi es0tericcha0s - Thanks for pointing out that Rom Manager shouldn't be used on a VZW Galaxy S4. I knew that but totally forgot about that fact.
Click to expand...
Click to collapse
You're welcome. What you need is here:
http://nasirtech.blogspot.com/2014/04/i545vrufnc5-android-442-kitkat-firmware.html
Or a 100 other places, but that one came up first.
I also find it best to factory reset after the update for best results.