can't seem to find the answer to this anywhere, so hopefully someone can help.
I'm running rooted 4.2.1 stock ROM with CMW recovery. Trying to update to 4.2.2 with absolutely no luck. Whether I try to update OTA or from zip, I consistently get a failed install with this error:
assert failed: apply_patch_check ("/system/app/phonesky.apk"
I've tried everything I can think of. Wiping cache/dalvik, factory reset within CMW, overwriting the phonesky.apk with the stock version. Nothing seems to solve the problem. The 4.2.2 zip file I have is the one downloaded from here.
Any advice on where to go next? I'm completely at a loss.
EDIT: I should also note I had previously cracked the Google Play store with the ChelpUS mod
bump?
noday42 said:
can't seem to find the answer to this anywhere, so hopefully someone can help.
I'm running rooted 4.2.1 stock ROM with CMW recovery. Trying to update to 4.2.2 with absolutely no luck. Whether I try to update OTA or from zip, I consistently get a failed install with this error:
assert failed: apply_patch_check ("/system/app/phonesky.apk"
I've tried everything I can think of. Wiping cache/dalvik, factory reset within CMW, overwriting the phonesky.apk with the stock version. Nothing seems to solve the problem. The 4.2.2 zip file I have is the one downloaded from here.
Any advice on where to go next? I'm completely at a loss.
EDIT: I should also note I had previously cracked the Google Play store with the ChelpUS mod
Click to expand...
Click to collapse
Have you already tried flashing the 4.2.2 stock rom with fastboot? Also, what's your bootloader version and do you have a device with or without 3g (grouper or tilapia).
The OTA works by *patching* existing files.
That can not possibly succeed under any circumstance if a file it expects to patch has been altered or removed. So, the OTA patch process checks all files it intends to patch first to make sure they are identical to the stock version. If even a single file is out of whack, nothing is changed and the install halts immediately with an error message.
The error message is telling you about the first file encountered with this problem, namely
/system/app/phonesky.apk
So, put the original file back. Get it out of your backups. You do make backups, right? (Note that because of the halt-on-first-fail behavior, there may be more problem files awaiting you.)
Either that, or pretend you are installing a new ROM and proceed accordingly.
OTAs are not meant for upgrading arbitrarily-modified stock ROMs.
thanks guys. I had previously tried replacing the modded app, but it didn't seem to fix anything. Ended up unrooting and restoring to factory 4.2.1, upgrading to 4.2.2 over the air, and re-rooting/restoring apps with TiBu. Thanks for your advice!
noday42 said:
can't seem to find the answer to this anywhere, so hopefully someone can help.
I'm running rooted 4.2.1 stock ROM with CMW recovery. Trying to update to 4.2.2 with absolutely no luck. Whether I try to update OTA or from zip, I consistently get a failed install with this error:
assert failed: apply_patch_check ("/system/app/phonesky.apk"
I've tried everything I can think of. Wiping cache/dalvik, factory reset within CMW, overwriting the phonesky.apk with the stock version. Nothing seems to solve the problem. The 4.2.2 zip file I have is the one downloaded from here.
Any advice on where to go next? I'm completely at a loss.
EDIT: I should also note I had previously cracked the Google Play store with the ChelpUS mod
Click to expand...
Click to collapse
I'm encountering the same with 4.3 update.... I unrooted my device.... CAN YOU PLS POST THE PHONESKY. APK FROM STOCK 4.2.2 urgently
Related
I'm getting an error in recovery I've never seen before in my 3+ years with Android, rooting, etc. The error is this:
"assert failed: apply_patch_check("/system/vendor/lib/hw/power.grouper.so"
I get the error when I try to apply the 4.2 OTA .zip package in Clockworkmod Touch Recovery. I am on the newest (3.41) bootloader and obviously I have root. The system files all pass the check, but I'm getting this error and despite having Googled some answers, I've come up empty handed. Apart from flashing back to full stock, I am not sure what to do. Any thoughts from anyone?
JFMFT said:
I'm getting an error in recovery I've never seen before in my 3+ years with Android, rooting, etc. The error is this:
"assert failed: apply_patch_check("/system/vendor/lib/hw/power.grouper.so"
I get the error when I try to apply the 4.2 OTA .zip package in Clockworkmod Touch Recovery. I am on the newest (3.41) bootloader and obviously I have root. The system files all pass the check, but I'm getting this error and despite having Googled some answers, I've come up empty handed. Apart from flashing back to full stock, I am not sure what to do. Any thoughts from anyone?
Click to expand...
Click to collapse
dont know how to fix the error, but there is a newer bootloader version (4.13)
http://forum.xda-developers.com/showthread.php?t=1989319
Have you flashed a custom kernel? Some of the custom kernels also update that file so it is no longer stock, and hence it fails the assertion check on upgrade.
You can download the original stock 4.1.2 file here:
http://forum.xda-developers.com/showpost.php?p=34057950&postcount=221
:good:
Forgot to mention, you'll also need the stock 4.1.2 kernel installed if it isn't already, you can grab a copy here:
http://forum.xda-developers.com/showpost.php?p=33030559&postcount=4
Cheers,
Dave.
I have the same issue with assert failed: apply_patch_check("/system/vendor/lib/hw/power.grouper.so").
I have the stock kernel 4.1.2 and even installed 4.13 bootloader but this error is still there.
I'm under 4.1.2 stock, unlocked/rooted, that's all.
Any idea how to solve that ?
Hello.
As of like a week I've been trying to update my 4.2.2 to 4.3, but each time I enter CWM and run the update it gets stuck here.
Assert failed: apply_patch_check ("/system/app/Maps.apk", "MD5 checksum", "MD5 checksum")
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
I'm unlocked and rooted (stock).
Does anyone happen to know what I can do to solve that?
I have tried:
- restoring the original maps from the 4.2.2 image file (google devs)
- downloading the original maps from the playstore (after uninstalling the updates from the original)
- uninstalled busybox (have read that it could help)
-----------
PS: For the rest the only real changes I've made to the system is Franco Kernel.
Any help would be very welcome because google is not my friend on this one, at least not with valuable help.
Foxnov1990 said:
Hello.
As of like a week I've been trying to update my 4.2.2 to 4.3, but each time I enter CWM and run the update it gets stuck here.
I'm unlocked and rooted (stock).
Does anyone happen to know what I can do to solve that?
I have tried:
- restoring the original maps from the 4.2.2 image file (google devs)
- downloading the original maps from the playstore (after uninstalling the updates from the original)
- uninstalled busybox (have read that it could help)
-----------
PS: For the rest the only real changes I've made to the system is Franco Kernel.
Any help would be very welcome because google is not my friend on this one, at least not with valuable help.
Click to expand...
Click to collapse
If I were you, I would try remove all the assert code from the update-script, that way it will skip all the checking and apply the patch.
BUT it "might" get you into bootloop, so make a full backup before you try.
EDIT: If everything else fail, there is still Nexus 4 Factory Images to install directly. There are guides how to avoid full wipe the phone when applying these factory images.
I'm on JSS15R, and I am trying to apply the OTA Zip floating around using TWRP.
I'm getting a very frustrating message:
Code:
Verifying current system...
"/system/etc/gps.conf" has unexpected contents.
E:Error executing updated binary in zip '{zipname}'
I then tried to get a factory binary to get the stock gps.conf file, but it is proving difficult for me.
Because I also accidentally wiped my data in the process (I was rushing and fracked it up - grrrr), would it be easier to flash the factory JSS15R binary zip from google, and then load on the OTA update Zip?
I'm not sure if I just replace the gps.conf file that the next file the OTA zip installer finds will get me back to the same position I am in now.
Any help would be appreciated.
jaredmorgs said:
I'm on JSS15R, and I am trying to apply the OTA Zip floating around using TWRP.
I'm getting a very frustrating message:
Code:
Verifying current system...
"/system/etc/gps.conf" has unexpected contents.
E:Error executing updated binary in zip '{zipname}'
I then tried to get a factory binary to get the stock gps.conf file, but it is proving difficult for me.
Because I also accidentally wiped my data in the process (I was rushing and fracked it up - grrrr), would it be easier to flash the factory JSS15R binary zip from google, and then load on the OTA update Zip?
I'm not sure if I just replace the gps.conf file that the next file the OTA zip installer finds will get me back to the same position I am in now.
Any help would be appreciated.
Click to expand...
Click to collapse
This happened to me since I made changes to system apps and installed DSP manager. Only fix is to restore the files you have changed one by one or just flash the factory image without wiping user data. Instructions on how to do that is here. http://forum.xda-developers.com/showthread.php?t=2377307
Since you wiped your data, you may as well restore the factory JSS15R image from google and adb sideload the ota update.
racerklm said:
This happened to me since I made changes to system apps and installed DSP manager. Only fix is to restore the files you have changed one by one or just flash the factory image without wiping user data. Instructions on how to do that is here. http://forum.xda-developers.com/showthread.php?t=2377307
Since you wiped your data, you may as well restore the factory JSS15R image from google and adb sideload the ota update.
Click to expand...
Click to collapse
I decided to install scrosler's Stock 4.4 ROM, which now has the update applied. It's working great.
Thanks for the advice either way. Would love to know why gps.conf was blocking the update.
I am currently running Kangakat 4.3 and am trying to update to 4.4.2. I am using TWRP 2.6.0.3 and have not had any issues with updating the ROM in the past. However this time I keep getting an Install Failed error message. I performed a factory reset and have downloaded the ROM from different sites however it does not matter. It still fails to update.
TWRP states unable to open ZIP file.
I updated to TWRP 2.6.3.0 and still receive unable to open zip file. I have downloaded the zip file from both the primary and mirror sites.
I am rather frustrated at this point and am hoping for some help.
AMG_Roadster said:
I am currently running Kangakat 4.3 and am trying to update to 4.4.2. I am using TWRP 2.6.0.3 and have not had any issues with updating the ROM in the past. However this time I keep getting an Install Failed error message. I performed a factory reset and have downloaded the ROM from different sites however it does not matter. It still fails to update.
TWRP states unable to open ZIP file.
I updated to TWRP 2.6.3.0 and still receive unable to open zip file. I have downloaded the zip file from both the primary and mirror sites.
I am rather frustrated at this point and am hoping for some help.
Click to expand...
Click to collapse
Have you tried to re-download the rom ? It could be a bad zip file and you just need to redo it.
hednik said:
Have you tried to re-download the rom ? It could be a bad zip file and you just need to redo it.
Click to expand...
Click to collapse
I tried downloading it to the phone multiple times and still encountered the install fail error.
Once I downloaded it to the computer and moved it over to the phone it installed without issue. I am not sure what the problem was but it is working now.
AMG_Roadster said:
I tried downloading it to the phone multiple times and still encountered the install fail error.
Once I downloaded it to the computer and moved it over to the phone it installed without issue. I am not sure what the problem was but it is working now.
Click to expand...
Click to collapse
That's been an issue in the past with many devices. Sometimes the rom you download on your phone just won't flash but always best to check the MD5 anyway. Glad it got ironed out.
I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
EDIT: Flashed Recovery.img (Only recovery.img, via fastboot)
Results: Recovery is flashed and working.
Phone does boot up perfectly fine, no issues
Data is NOT lost.
Flashing the 7.0 update(A2017UV110B15) (Via stock recovery) [Remember to put it on your SDCard]:
Verifying update package...
Verified.
"EMC /dev/block/bootdevice/by-name/boot****load of numbers)" has unexpected contents
Aborted
Click to expand...
Click to collapse
( Same error as when I removed device verification.. maybe this is a user error and not a system/update error )
( Maybe I failed to download the update zip properly? I'll try the OTA update instead )
Downloading..
Rebooting..
Installing System Update...
Has unexpected contents
Package mixmatched
Aborted
Click to expand...
Click to collapse
( No, not a user error I suppose.. I don't know what is wrong then! This is odd )
System update failed
Reason: The system update package did not match the phone
Click to expand...
Click to collapse
And for the record, I am on A2017UV1.0.0B29
Andrew S.S. said:
I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
Click to expand...
Click to collapse
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
lafester said:
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
Click to expand...
Click to collapse
Read my updated comment; Sorry that I didn't just edit the thread. And that makes sense. I think it would be wise for me to just wait.
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
WesTD said:
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
Click to expand...
Click to collapse
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Only use ota if you don't want twrp/root anymore.
Andrew S.S. said:
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Click to expand...
Click to collapse
Here you go; https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2