I've been trying to complete the ICS OTA with no success. I was rooted. I defrosted all previously frozen bloatware. I used Voodoo OTA rootkeeper to hide root, I uninstalled superuser and Bionic Bootstraper. The log info is below. Any help would be appreciated. Thanks.
Deleting facebook cache foler . . .
Verifying current system . . .
file "/system/etc.gps.conf" doesn't have any expected sha1 sums: checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed:
apply_patch_check ("/system/etc/gps.conf",
"c61f40cc6c50788f13bde331391bd9ea8e2f6ba",
"f2c571930e2d347f2a76ba48a555c979f4dddbe7")
assert failed: apply_patch_check ("/system/etc/gps.conf",
"c61f40cc6c50788f13bde331391bd9ea8e2f6ba",
"f2c571930e2d347f2a76ba48a555c979f4dddbe7")
E: Error in /cache/Blur_Version.6.12.181.XT912.Verizon.en.US.zip
(Status 7)
Installation aborted.
I tried to get individual files like that (eventually got them all) but the install still failed with a sideload error in the preinstall part of the process. You may have to resort to wiping the phone to get that config file (and probably many others) back to stock. Titanium backup is your friend.
Here are the instructions I used (second set, but I didn't need to use the Modified 1.6, just the regular 1.6): forum.xda-developers.com/showthread.php?t=1692694
-Snags
When removing bootstrap did you just delete the app or did you open the app and use the uninstall feature? That makes a difference
Sent from my DROID RAZR MAXX via XDA Premium
Related
Hello everyone.
It seems my transformer prime is missing an odex file and cannot run the new system update.
I have tried factory reset and everything now i can think of, nothing helped.
How the file has even got missing is beyond me, but the device is rooted and i have OTA rootkeeper and titanium backup.
the file it says is missing is the Galaxy4.odex, located in /system/app/
the error_log from failed update state:
Code:
failed to stat "/system/app/galaxy4.odex": No such file or directory.
file "/system/app/galaxy4.odex" does not have any of the expected sha1 sums; checking cache
failed to load cashe file
script aborted: assert failed: apply patch:check("/system/app/Galaxy4.odex", ---list of numbers---, --list of numbers--not the same")
E:Error in /cache/dlpkgfile
(Status 7)
Installation Aborted
I:result code 410
Does anyone have an idea how i can restore this file to do the update?, or can make some kind of copy /backup that i can install of this file?
All help appreciated!
Silverdream
FYI:
I have WW_epad-9.4.2.14-20120214
Silverdream said:
Hello everyone.
It seems my transformer prime is missing an odex file and cannot run the new system update.
I have tried factory reset and everything now i can think of, nothing helped.
How the file has even got missing is beyond me, but the device is rooted and i have OTA rootkeeper and titanium backup.
the file it says is missing is the Galaxy4.odex, located in /system/app/
the error_log from failed update state:
Code:
failed to stat "/system/app/galaxy4.odex": No such file or directory.
file "/system/app/galaxy4.odex" does not have any of the expected sha1 sums; checking cache
failed to load cashe file
script aborted: assert failed: apply patch:check("/system/app/Galaxy4.odex", ---list of numbers---, --list of numbers--not the same")
E:Error in /cache/dlpkgfile
(Status 7)
Installation Aborted
I:result code 410
Does anyone have an idea how i can restore this file to do the update?, or can make some kind of copy /backup that i can install of this file?
All help appreciated!
Silverdream
Click to expand...
Click to collapse
Do you have a root file manager of some sort, if so, check if that file is:
A) Actually present
B) Has the correct permissions
I do have that odex file on my computer from a system dump that I did at some point, but I honestly can't be sure which version it is.
You could of course download the full update from ASUS website and run it from external SDcard. Search the forum, you should find the exact method of doing this fairly easily.
You could also try to update to .15 first from ASUS website and then do the .21 update. WW versions are present in the download section of the TF201 minisite.
I hope one of these suggestions is of use to you.
Thanks for reply.
I tried most of those, before you wrote it, It just did not want to update when missing files. Then i figured out to hell with it, installed the bootload enabler and a new custom .21 ROM instead.
Bricked once, but now it seems just fine
I've been trying to install ICS OTA for last couple of day...
I did Factory Reset Data,, formatted the SD Card and downloaded all the updates from 1.35.707.1 to 1.50.707.1
I downloaded the update around 10 times but every time i encountered the same problem.
I would highly appreciate if anyone could help...Contacted HTC and done all what the said to do...(Factory Reset Data, SD Card Format etc.)
here is the installation message i see when i press the Volume Up +Power button, once stuck at red triangle icon.
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Copying fotaBoot to /data/system for customize reload...
Verifying current system...
assert failed: apply_patch_check("/system/app/Maps.apk","3ae09b2fee344a1d13930ea36b8cf9791d06e10 a","cafac724385e245557e1f969eca53713cea10438")
E:Error in /sdcar/OTA_PYRAMID_ICS_hTC_Asia_WWE_3.32.701.10_R-1.50.707.1_release_2515911s4ge59w5atckzzw.zip (Status 7)
Installation aborted.
Talked to HTC Support via Web Chat.... They suggested to Format the SD card with Fat32 and try to install.. did so and no new result.
Other option suggested by HTC Help is to factory rest... which i did... No different.
Install Maps ...
just update the google maps to 6.5.0 and tried installing the OTA for ICS... same result.
Solution
There is only one solution:
you have to find your original Maps.apk and restore it in the correct location.
often Maps.apk is wiped by rooting scripts to free-up space.
your Maps.apk MUST have this SHA1 hash: cafac724385e245557e1f969eca53713cea10438
1) download your old original ROM
2) extract from system.img the Maps.apk file
3) verify the SHA1 hash of the file
4) if you found the correct file, copy it in the /system/app folder of your mobile, you must use a software able to mount the system partition as writable, like ES file manager ( take a look at settings )
5) reinstall the OTA update
Hey been on these forums forever since i was installing themes on my hp ipac or htc shadow. Not a noob by any meens. Been flashing android since my G1. Now that thats out of the way im trying to flash a ICS leak to mess with the webtop 3.0. I was coming from a stock/rooted .181...
1. I fastbooted to .181 using the droid razr 1.6 utility.
2. then i root using ICS installer Combo.
3. Next i use the ICS installer Combo to install the .79 leak.
4. allowed rom manager and su user permissions. i get an error that it can not mkdir to /sdcardEXT.. is this a normal error? Either way once the phone reboots it starts install but then gets the ! in the triangle and what i assume, fails and reverts back to .181.... What am i doing wrong iv been at it for like 3 hours and im pulling my hair out trying to figure out what im missing. My battery is at 40%, is that an issue? Assuming not since if i can fastboot to .181 i should be able to install .79
Hopefully this makes sense and thanks for taking a look
I had something similar to this happen to me when downgrading-rooting-upgrading my Transformer Prime. It failed the upgrade OTA part because I had modified the build.prop and that kept it from installing the upgrade and I got the ! triangle. Have you changed anything? Frozen any apps? Changed your build.prop from stock?
There is a directory you can look in for the log file of why it failed the upgrade. I think it is under /cache/recovery directory from root. (you have to be rooted to see it and use a root explorer). Open the log file and see why its failing.
Thanx for the quick reply. if memory serves me right i modified the build prop to mess with the s-voice app. so your saying fastbooting wouldnt restore this? if not i guess il have to figure out how i changed it and change it back before trying this install again
Well, I would have thought fastbooting would bring it to total stock, but I had made a change in my build.prop AFTER I had downgraded I believe. I think I would check that directory if you can /cache/recovery for the log file and see whats causing your failure specifically. Again, you'll need a good root explorer (like "Root Explorer") and make sure you have it do root so you can see the sub directories too. I was using ES Explorer and it was not seeing the /cache/recovery directory, just /cache and using Root Explorer showed me the sub folder.
PS> Changing your build.prop back to what it looked like before the change didn't work for me. I had to get a stock, unmodified build.prop form another user on here for it to work.
PPS> Why are you wanting to install the leak? Its pretty much been all but confirmed its happening OTA very soon.
Ok i checked out the build.prop alot of stuff in there but seems to all be correct.
I checked that log file and at the very bottom i get this.
Finding update package...
I:Update location: /cache//Blur_Version.6.12.181.XT912.Verizon.en.US.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
E:failed to open /cache//Blur_Version.6.12.181.XT912.Verizon.en.US.zip (No such file or directory)
I:verify_file returned 1
E:signature verification failed
Installation aborted.
Have no idea what that means tho... If anyone needs the whole log to help me out let me know
Well, thats a lot different than what mine said so your problem is different, but I'm sure someone can help with that info. Heres what mine said when it was the build.prop:
file "/system/build.prop" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/build.prop"
etc...
Shinare said:
Well, thats a lot different than what mine said so your problem is different, but I'm sure someone can help with that info. Heres what mine said when it was the build.prop:
file "/system/build.prop" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/build.prop"
etc...
Click to expand...
Click to collapse
Yeah hopefully someone can, i mean with the ota around the corner this is not too big of an issue as long as it doesn't effect the official ota. Thanks for taking the time tho.
Well, the only other thing I can think of thats happened in the past is the wrong "region" file for the phone you are trying to update.
Like you are on US_ENG on your phone and you are trying to flash a WW_ENG or something so its not matching up? *shrug* just a blind guess. Hope someone can help you out.
This may or may not help, but I got that error back in the day flashing a ROM on my D2. In clockwork there was a option to disable and enable signature verification.
Or maybe the zip is messed up?
See the thing is i did this all through the guide in the dev section. i would have posted it there but i didnt have enough posts to post there, im more of a reader than a preacher. i only downloaded the 2 files with the 2 different batch scripts. 1 to fastboot to .181 and 1 to install ICS. Il figure it out eventually, but thanks guys. hopefully someone gets me there sooner.
**fixed it, i ended up using the permissions option in rom manager and also made sure the phone was over 50% and it worked so hopefully this helps soeone eles if they stumble across it.
I got the following error when I tried to load an OTA package from the SD card using CWM recovery with signature verification enabled.
Finding update package ...
Opening update package ...
Verifiyng update package ...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted
Following are the details of the steps I followed -
1) I rooted my Galaxy Tab 2 7.0 (P3113) following the instructions posted on
http://www.androidauthority.com/galaxy-tab-2-7-0-p3113-root-clockworkmod-recovery-96474/.
2) Then I built an AOKP jellybean custom ROM following the instructions on
http://rootzwiki.com/topic/31166-tutorial-so-you-want-to-build-aokp-jb-ubuntu-1204/
3) Then I followed http://www.kandroid.org/online-pdk/guide/release_keys.html to create a distribution release and my own private signing certificates, and signed the APKs in the target files. Then I used ota_from_target_files to create an OTA zip signed with my own key.
4) I copied the signed OTA package to mSD card and boot the tablet to Recovery, then I wiped everything (factory/data reset, cache, ectc) including formating /system partition, then I enabled the Signature Verificaiton, and then selected the zip to install, and got the "Failed to verify the whole-file signature" error message.
By the way, if I disable the signature verification, I can load the zip successfully.
Can someone tell me what I did wrong or if I missed any necessary steps? Much appreciated.
Hi all. I have a US I535 Verizon S3 which I rooted when I got it and kept rooted through an update with Voodoo Rootkeeper. I have since temp unrooted and tried to apply the OTA update to 4.3 (I don't have time to wipe, install via recover, and put everything back) and the upgrade is failing to apply around 25% with this message found in /data/log/recovery_log.txt:
Installing update...
try_update_binary(path(/cache/fota/update.zip))
radio.diff not found
Register_libbootloader_updater Qcom msm8960
[DEBUG] setprocattrcon: open failed, errno=2
[DEBUG] setprocattrcon: open failed, errno=2
Verifying current system...
file "/system/csc/feature.xml" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
failed to stat "/data/.saved.file": No such file or directory
failed to load data file
script aborted: "/system/csc/feature.xml" has unexpected contents.
"/system/csc/feature.xml" has unexpected contents.
E :Error in /cache/fota/update.zip
(Status 7)
E:Error in /cache/fota/update.zip
(Status 7)
FOTA_update_success_log_result()
Update Fail. File is written. status = 7
Installation aborted.
Does anyone know how to correct this either by updating the xml file or fixing whatever may be the "true cause" of that error?
UPDATE: I remembered thanks to an old post on xda:
Luckily I recovered root on my Vzw S3 after the 4.1.1 OTA. I discovered that you can move GPS/BT toggle widgets to /system/app/ and it no longer asks for confirmations. Super fast toggles with no hassle! There's a small app in the Play store called "/system/app mover" to do it.
Click to expand...
Click to collapse
Would that be detected and block the update? I'm going to use TiBU to convert Power Toggles back to a user app and see if that gives me the green light, but it doesn't seem like it would be related to the xml error.
Thanks a bunch!
my /ssyte/csc/feature.xml (4.1.2)
CPngN said:
Hi all. I have a US I535 Verizon S3 which I rooted when I got it and kept rooted through an with Voodoo Rootkeeper. I have since temp unrooted and tried to apply the to . (I don't have time to wipe, install via recover, and put everything back) and the is failing to apply around 25% with this message found in /data/log/recovery_log.txt:
Click to expand...
Click to collapse
Here's the text of my /system/csc/feature.xml that the is complaining about:
http://pastie.org/private/8argqzzxwlgafxfceuhepq
Thanks all